Planning and preparation are complete and the Healthcare organization is now ready to proceed with Part 3 of the NSX Data Center for vSphere to NSX-T Data Center migration.
Researching the process for migration from NSX Data Center for vSphere to NSX-T Data Center involves the following processes. These efforts will be covered over a series of blog posts related to each step in the processes:
- Understanding the NSX Data Center for vSphere Migration Process – Part 1
- Checking Supported Features
- Checking Supported Topologies
- Checking Supported Limits
- Reviewing the Migration Process and the prerequisites
- Preparing to Migrate the NSX Data Center for vSphere Environment – Part 2
- Prepare a new NSX-T Data Center Environment and necessary components
- Prepare NSX Data Center for vSphere for Migration
- Migration of NSX Data Center for vSphere to NSX-T Data Center – Part 3
As they started the process in part 1, consulting the official documentation on the processes and what steps to perform are recommended.
MIGRATION OF NSX DATA CENTER FOR VSPHERE TO NSX-T DATA CENTER
The migration to NSX-T Data Center is a multi-step process. The steps are outlined below:
- Import the NSX Data Center for vSphere Configuration
- Resolve Issues with the NSX Data Center for vSphere Configuration
- Migrate the NSX Data Center for vSphere Configuration
- Migrate NSX Data Center for vSphere Edges
- Migrate NSX Data Center for vSphere Hosts
- Finish the NSX Data Center for vSphere Migration
Upon further review of each step, the organization deployed two NSX-T Data Center Edge Nodes which will be used as replacements for the NSX Data Center for vSphere Edge Services Gateways. These Edge Nodes were deployed using the official documentation and added to the NSX-T Manager.
IMPORT THE NSX DATA CENTER FOR VSPHERE CONFIGURATION
To begin the process, the organization needs to enable the Migration Coordinator on the NSX-T Manager that they deployed. A quick SSH session into the NSX-T Manager using the admin account, will provide the means to run the command necessary to start the Migration Coordinator service and enable the user interface that will be used for the migration in the NSX-T Manager:
Now that the Migration Coordinator service is running, the user interface in the NSX-T Manager will be enabled.
The next step in the process is to authenticate to the NSX Manager and the vCenter Server.
With the NSX Data Center for vSphere Manager and vCenter Server added in, the organization can start the import configuration step.
The organization sees ‘Successful’ on importing the existing configuration into NSX-T Data Center. There is an option to ‘View Imported Topology’ which will give them a nice visual diagram of the configuration details that were imported.
A successful import allows the organization to proceed with the next step in the migration process
RESOLVE ISSUES WITH THE NSX DATA CENTER FOR VSPHERE CONFIGURATION
Moving to the next step, the organization is presented with all of the ‘issues’ that need to be resolved to move forward with the migration process. The total number of inputs that need to be resolved are listed and once resolved, will also be listed.
Several of the issues appear to be items that the organization does have already have configured. Each issue has a recommendation by the Migration Coordinator for the organization to consider and move forward with the migration process. The more important issues listed, are the ones that deal with the ‘EDGE’ as those issues will result in new NSX-T Data Center Edge Nodes being deployed to replace the existing Edge Services Gateways.
After selecting the EDGE category of issues to resolve, the organization was met with the following items to remediate before it was able to proceed to the next step.
- IP addresses for TEPs on all Edge transport nodes will be allocated from the selected IP Pool. You must ensure connectivity between Edge TEPs and NSX for vSphere VTEPs.
This issue requires putting in the TEP_POOL that was created for the Edge Nodes already.
- An NSX-T Edge node will provide the connectivity to replace NSX-v edge. Enter an IP address for the uplink.
This issue requires putting in a valid uplink IP address for the NSX-T Edge Node. The organization will want to use the same IP address that the NSX Data Center for vSphere Edge Services Gateway is currently using since the TOR is statically routed to that IP address.
- An NSX-T Edge node will provide HA redundancy for NSX-v edge. Enter an IP address for the uplink on this Edge node. This IP address must be in the same subnet as the uplink of the other NSX-T Edge used to replace this edge.
This issue requires putting in a valid IP address for the HA redundancy that the Edge Node will provide
- An NSX-T Edge node will provide HA redundancy for edge replacing NSX-v edge. Enter an unused fabric ID for Edge node. See System > Fabric > Nodes > Edge Transport Nodes.
This issue requires selecting the UUID that was imported from the NSX-T Edge Nodes and selecting which one will be the replacing the NSX Data Center for vSphere Edge Services Gateway
- An NSX-T Edge node will provide the connectivity to replace NSX-v edge. Enter an unused fabric ID for this Edge node. See System > Fabric > Nodes > Edge Transport Nodes.
This issue is similar to the one above but requires selecting the second NSX-T Edge Node UUID instead.
- An NSX-T Edge node will provide the connectivity to replace NSX-v Edge. Enter a VLAN ID for the uplink on this Edge node.
This issue requires putting in the VLAN ID of the uplink adapter that will be used.
With all of the items resolved, the organization is ready to proceed with the actual migration process. Given that there will be some data plane outages that will need to occur during this process, the Edge Services Gateways will need to migrate to NSX-T Gateways, the organization has decided to perform the actual migration process during a scheduled maintenance window.
MIGRATE THE NSX DATA CENTER FOR VSPHERE CONFIGURATION
Pressing start, the Migration Coordinate begins migrating the configuration over to the NSX-T Data Center Manager. This part of the process does not incur an outage as it’s a copy of the configuration.
Once the configuration has been copied over, the organization can now see all of the components that have been created in NSX-T Data Center from the configuration imported.
The organization can see that a new Tier-0 Gateway has been created and has the routing configuration that the Edge Services Gateways had.
The organization checks the new Group objects and can see that those new Inventory objects have been created
Lastly, the organization checks the security objects, specifically that their Distributed Firewall and Service Composer rulesets are migrated over properly.
MIGRATE NSX DATA CENTER FOR VSPHERE EDGES
The next part will incur an outage as this is the process of migrating the NSX Data Center for vSphere Edge Services Gateways over to the NSX-T Data Center Edge Nodes. This will involve moving the IP addressing over.
Once the Edges have been migrated over, the organization can see that a new Transport Zone is created, Edge Node Cluster created, and N-VDS switch is created.
MIGRATE NSX DATA CENTER FOR VSPHERE HOSTS
The next step involves swapping the ESXi host software components for NSX Data Center for vSphere out with NSX-T Data Center.
With the ESXi hosts now migrated the organization has now been successfully migrated from NSX Data Center for vSphere over to NSX-T Data Center.
Now that the Healthcare organization has migrated over to NSX-T Data Center, they can start the decommissioning of the NSX Data Center for vSphere components that are no longer needed. The topology of their data center environment with NSX-T Data Center now looks like this.