GRE Tunnels & Dynamic Routing in NSX 6.4
GRE Tunnels & Dynamic Routing in NSX 6.4
VMware NSX 6.4 has a new hidden feature: GRE tunnels. You can only manage them through the API and here’s a howto on how to create a GRE tunnel between ESGs
GRE Tunnels & Dynamic Routing in NSX 6.4
VMware NSX 6.4 has a new hidden feature: GRE tunnels. You can only manage them through the API and here’s a howto on how to create a GRE tunnel between ESGs
Take a look at this VMware NSX-v Brownfield Design and Deployment Guide for version 1.2 here on #VMTN
This document is targeted toward virtualization and network architects interested in deploying the VMware® NSX Network virtualization solution in a Brownfield vSphere environment.
Free course: VMware vSphere: What’s New Fundamentals [V6.0 to V6.5]
This course highlights the new features and enhancements in vSphere 6.5. It also presents use cases that describe how the new features align with customer needs.
I wanted to share with you the steps required to upgrade a typical multi-site vSphere/ SDDC implementation. This particular implementation had the following products.
Product | Current version | Planned Version |
vCenter Server | 6.0 U3 | 6.5 U1 |
ESXi | 6.0 U3 | 6.5 U1 |
vSAN | 6.2 | 6.6.1 |
NSX | 6.2.4 | 6.3.5 |
vROPS | 6.3.0 | 6.6.1 |
vRLI | 3.3.1 | 4.5 |
vDP | 6.1.0.173 | 6.1.5 |
vSphere Replication | 6.1.1 | 6.5.1 |
VMware Tools | 6.0 U3 | 6.5 U1 |
In order to understand the upgrade order here is some background information on this fictitious environment.
The environment has a Production site and a DR site. NSX is deployed across both sites using universal objects, SRM and vSphere Replication are in use with vSAN being used locally at each site. It also has a deployment of vROPS and vRLI at both sites.
|
Action |
Site |
Impact to vSphere |
Required |
VM downtime |
1. |
Carry out Health Check of VC & PSC before starting (Go or No Go) |
Both Sites |
N/A |
Yes |
No |
2. |
Backup All Components |
Both Sites |
N/A |
Yes |
No |
3. |
Backup PSC’s with vDP & Data Protect |
Both Sites |
N/A |
Yes |
No |
4. |
Deploy second PSC at each site – Configure replication see KB 2131191 for justification |
Both Sites |
vCenter management of ESXi hosts unavailable during upgrade. |
Yes |
No |
5. |
Disable vSphere Replication |
Both Sites |
No protection of VMs (Backup is the only method of restoring) |
Yes |
No |
6. |
Upgrade the external Platform Services Controller server 6.0.x to vCenter 6.5 for both sites |
Both Sites |
vCenter management of ESXi hosts unavailable during upgrade. |
Yes (if using an external Platform Services Controller) |
No |
7. |
Upgrade vDP at both sites |
Both Sites |
Backups unavailable during upgrade |
Yes in order to restore in to 6.5 during the upgrade |
No |
8. |
Upgrade NSX Manager at the DR Site |
DR Site |
No Changes to DR NSX during Upgrade |
Yes |
No |
9. |
Upgrade NSX Controller Cluster at the DR Site |
DR Site |
NSX reverts to read only mode Change Window Required |
Yes |
Yes – No Disruption as long as VM’s don’t move or any changes made |
10. |
Upgrade NSX Host preperation at the DR Site |
DR Site |
Hosts require Reboot |
Yes |
No |
11. |
Upgrade NSX DLR’s at the DR Site |
DR Site |
Disruption to Service |
Yes |
Yes |
12. |
NSX Edges at the DR Site |
DR Site |
Outage required while edge is redeployed and upgraded |
Yes |
Yes |
13. |
Upgrade vCenter from vCenter 6.0.x to vCenter 6.5. at the DR Site |
DR Site |
vCenter management of ESXi hosts unavailable during upgrade. |
Yes |
No |
14. |
Upgrade vROPS |
Both Sites |
N/A |
Yes |
No |
15. |
Upgrade Log Insight |
Both Sites |
N/A |
Yes |
No |
16. |
Use vSphere Update Manger to scan and remediate an ESXi host. |
DR Site |
1 host not available, reduced capacity. |
Yes |
No |
17. |
Repeat steps for remaining hosts in the cluster. |
DR Site |
One host will always be unavailable while it is being upgraded with vSphere Update Manager. |
Yes |
No |
18. |
Upgrade vSAN at the DR Site |
DR Site |
Possible Performance and increased risk of failure during upgrade – upgrade could take several days. |
Yes |
No |
19. |
Upgrade NSX Manager at the Prod Site |
Prod Site |
No Changes to DR NSX during Upgrade |
Yes |
No |
20. |
Upgrade NSX Controller Cluster at the Prod Site |
Prod Site |
NSX reverts to read only mode Change Window Required |
Yes |
Yes – No Disruption as long as VM’s don’t move or any changes made |
21. |
Upgrade NSX Host preperation at the Prod Site |
Prod Site |
Hosts require Reboot |
Yes |
No |
22. |
Upgrade NSX DLR’s at the Prod Site |
Prod Site |
Disruption to Service |
Yes |
Yes |
23. |
NSX Edges at the Prod Site |
Prod Site |
Outage required while edge is redeployed and upgraded |
Yes |
Yes |
24. |
Upgrade vCenter from vCenter 6.0.x to vCenter 6.5. at the Prod Site |
Prod Site |
vCenter management of ESXi hosts unavailable during upgrade. |
Yes |
No |
25. |
Upgrade vSphere Replication at Both Sites |
Both Sites |
Replication unavailable until this points it has to be disabled before starting the upgrade process |
Yes |
No vSphere Replication protection during upgrade |
26. |
Use vSphere Update Manger to scan and remediate an ESXi host. |
Prod Site |
1 host not available, reduced capacity. |
Yes |
No |
27. |
Repeat steps for remaining hosts in the cluster. |
Prod Site |
One host will always be unavailable while it is being upgraded with vSphere Update Manager. |
Yes |
No |
28. |
Upgrade vSAN at the Prod Site |
Prod Site |
Possible Performance and increased risk of failure during upgrade – upgrade could take several days. |
Yes |
No |
29. |
Optional: Update VMware Tools on each VM with a vSphere Update Manager baseline. |
Prod Site |
Virtual machine reboot. |
Recommended |
Reboot |
30. |
Optional: Update virtual hardware on each VM with a vSphere Update Manager baseline. |
Prod Site |
Virtual machine shutdown, 1+ reboots. |
No |
Yes; upgrade during shutdown |
This step includes the upgrade of all components and installation of new components that were not previously addressed.
During the upgrade, the vCenter Server will be unavailable to perform any provisioning operations or functions such as vSphere vMotion and vSphere DRS. Once started, the vCenter database is upgraded first, followed by the vCenter binary upgrade. After the upgrade, the hosts are auto-reconnected.
Before starting the vSAN upgrade process, ensure that the following requirements are met:
Host Preparation
Ensure you choose the right maintenance mode option. When you move a host into maintenance mode in vSAN, you have three options to choose:
Exit maintenance mode and resync
For detailed information please refer to the NSX Upgrade guide.https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.3/nsx_63_upgrade.pdf
For detailed information please refer to the vROPS Upgrade guide.
For detailed information please refer to the vRLI Upgrade guide.
For detailed information please refer to the vDP Upgrade guide.
https://docs.vmware.com/en/VMware-vSphere/6.5/vmware-data-protection-administration-guide-61.pdf