Migration from DvS to N-VDS

Planning and executing the migration from the old switches to the new N-VDS(NSX) can be a big thing. And often there is no redundant network doing the migration. We needed the migration to go very fast to minimize risks and not doing it by hand.

The network design we had on the DvS was 2 vmnics, A and B side for the particular DvS we migrated.

The way we did the migration was taking one cluster at a time. We did remove one vmnic on each host from the DvS and added the removed vmnic to the new N-VDS. Our old DvS had 1 physical uplink and our new N-VDS had 1 as well, so no redundancy at the time of the migration.

I made a small script to migrate all the virtual machines from the old switches to the new N-VDS, as we only migrated one cluster at a time, we needed a script that could handle that operation.

Making the Transport node profiles

The first thing we need is a Transport-node profile containing all the n-vds information including the transport-zones.
It is very important to make one transit/migration profile, so you are able to take only the first vmnic. Your virtual machines connected to the old switch still have access to the network through the “old” vmnic.

Doing the migration, you will move the load from the “old” vmnic to the new N-VDS and virtualmachines will appear into the NSX-Manager(s).

Then the migration is finish you now switch from your transit profile to the normal transport-node profile containing all the necessary vmnics, and then the N-VDS switch will be redundant and happy 😉

You May Also Like

About the Author: Søren Isager

IT-Specialist and Technical Service Responsible for the biggest company in Denmark, my primary work areas is infrastructure with automation. I have more than 14 years of experience and started in the IT Industry since i was 14 years old

Leave a Reply

Your email address will not be published. Required fields are marked *