Moving a provider from NSX-v to NSX-T

Moving from NSX-v to NSX-T without the challenges...

When VMWare discontinued NSX-v and NSX-T was set as it’s successor for network virtualization within the VMware software stack for the SDDC this affected also most cloud providers like this one

The challenge

Customer workloads currently run on the existing, NSX-v based,infrastructure and all needed networking services are working fine, and theinternal team is familiar supporting the customers implementing new neededsolutions. Furthermore, no new clusters will be implemented because there arecurrently enough hardware resources in place.

“Finding a partner understanding the cloud provider business on the onehand and having knowledge and experience in NSX-T migration projects on theother hand is key to successfully finish those projects in time. On top properknowledge transfer is a nice to have.” says the customers leading cloudarchitect.

Thesolution

Having enough hardware resources enabled us to carve afew hosts out of the current clusters and build a new one for NSX-T, based onthe newly created design. This allowed us to migrate to vSphere 7 in the samestep. A side-by-side migration is more work, but reviewing each customerindividually enabled us to minimize needed downtime for each customer.

Together we developed, based on the existing customers,multiple different migration scenarios for the workloads, fitting all needs interms of features and downtime.

Side-by-Side Migration

„We never considered building a new infrastructurebased on different technology and move only the customer workloads over” saysthe service provider. This approach is interesting, because it allows to changedifferent parts of the infrastructure at once. In this case, the SDN andvirtualization stack, because the servers are reinstalled with ESXi version 7.VMware Cloud Director is able to leverage multiple physical deployment targetswhich simplifies the workload migration process.

Knowledge Transfer

“Having a consutling partner being able to educate theinternal IT department on the new technologies during the design,implementation, and initial migration phase was a huge benefit” says the leadcloud architect. “It minimized the time colleagues not being available in theoffice”.

Summary

Working with us as a team, comdivision was able tosatisfy our needs in terms of migration scenario development, educationalexpectations, and designing a new infrastructure.

Outlook

With the initial support our team is now able to migrate the remainingcustomer workload as well as supporting the customers solving diversenetworking challenges they are facing.

Questions?

Questions?

Ask Matthias:

* We will process your email in accordance with our Privacy Policy.
Thank you! Your message has been sent!
Oops! Something went wrong while submitting the form.