If you’re like most people, you’re probably thinking, “Why should I switch from the tried-and-true VMware NSX for vSphere to the new kid on the block, NSX-T?” Well, let me tell you, there are plenty of good reasons! Here are just a few:
VMware NSX-T is more scalable than NSX for vSphere (NSX-v). With NSX-v, you’re limited to a maximum of 32 hosts per cluster. With NSX-T, that number is increased to 64 hosts per cluster. This means that you can support twice as many virtual machines with NSX-T as you can with NSX for vSphere.
Support for VMware NSX-v has ended in January 2022 with technical guidance set to expire on January 2023. So all customers who are still using VMware NSX-v must migrate away to NSX-T.
NSX-T supports a wider range of hypervisors than NSX for vSphere. In addition to VMware vSphere, NSX-T also supports Microsoft Hyper-V and KVM. This means that you can use NSX-T in a mixed environment if you so choose.
NSX-T has a lower total cost of ownership than NSX for vSphere. This is due to the fact that NSX-T requires less hardware than NSX for vSphere. With NSX for vSphere, you need a dedicated physical network interface controller (NIC) for each host. With NSX-T, you only need two NICs per host: one for management traffic and one for data traffic. This can lead to significant savings on hardware costs.
Migration Planning and Support for VMware NSX-T
Here’s Migration from NSX for vSphere to NSX-T Works
In general, there are two ways to migrate from NSX for vSphere to NSX-T: Parallel Migration and In Place Migration. This blog post offers a comprehensive summary of both the two migration methods mentioned above.
In Parallel Migration
The NSX-T infrastructure is implemented in parallel with the current NSX-V infrastructure in this approach. Although some NSX-V and NSX-T elements, including management, may collaborate, compute clusters running workloads would require their own hardware.
Workload migration in this approach may take different strategies:
- Cattle: On NSX-T, new workloads are implemented, and the old workloads can expire over time.
- Pets: Lift and shift workloads to the new NSX-T infrastructure.
In Place Migration
In Place Migration is usually considered the simpler option as it doesn’t require additional hardware to migrate. This method makes use of the Migration Coordinator, a built-in tool in the NSX-T Data Centre.
Migration Coordinator is built in to NSX-T Data centre and is available with the NSX-T 2.4 release. It can be accessed from the NSX-T Data Centre GUI by selecting System->Migrate.
Because migrating is not a common task, it is disabled by default. Start the migration process by typing start service migration-coordinator into the NSX-T manager console.
It also aids in the migration of exact configuration from NSX for vSphere to NSX-T Data Centre. It transfers both of the networking components and their configuration, as well as the configured security controls, which includes rules and groups.
Steps That are Required Before Migration
- Install the NSX-T
- Install the NSX-T Edges
- Create a Tunnel Endpoint pool.
- Create a Compute Manager that points to the vCenter that is connected to NSX-V.
- Because no changes are permitted during the process, ensure that NSX-V is in a stable, healthy condition without any pending changes.
The Migration Process in 7 Easy Steps
1. Download the Migration Coordinator
The first step is to download the migration tool from the VMware website. The tool will help you convert your NSX for vSphere configuration into an NSX-T compatible format.
2. Import and Backup Configuration
Once you have the migration tool, connect and import all configurations from NSX-V and to backup your current configuration. This is critical in the event that anything goes wrong throughout the migration process. To backup your configuration, you can use either the vSphere Web Client or the NSX Manager UI.
3. Convert Your Configuration
After you have backed up your configuration, the next step is to convert it into an NSX-T compatible format using the migration tool. The tool will generate a new JSON file that you can then use to import your configuration into NSX-T.
4. Resolve Any Misconfigurations
This stage offers a graphical user interface for editing and accepting the imported configuration to accommodate NSX-T. On this page, we’ll also specify the VLAN for the NSX-T Edge Transport Nodes.
5. Configuration Migration
Next import your configuration into NSX-T. You can do this using Migration Coordinator
6. Migrate Edges
In this next step you will need to migrate edges.
7. Migrate Hosts
Lastly, transfer the hosts. There will be several options such as if the migration happens serially or in parallel, and if there needs to be a time delay after migrating each group, and so on. . Once hosts has been migrated, you’re all set! You can now start using NSX-T in your environment.
Migration from NSX for vSphere to NSX-T is a relatively simple process that can be completed in just a few steps. By following the steps outlined in this blog post, you’ll be able to successfully migrate your configuration and start using NSX-T in no time.
For additional information visit the NSX-T Migration page by VMware
Speak to a VMware Consultant
Schedule a Call
