Migration of Nexus1000v to Vcenter vDS

[sukhesh01]

Hi All,

I need some help migrating existing vDS Nexus 1000v to vcenter vDS using power shell. Right now i have powercli command to recreate all the port group from existing  N1K to newly created vDS, however the manual task of removing the uplinks and migration is still a pain.

Can somebody help me with powershell script to migrate for the end-end activity.

Thanks in Advance:)

[a_p_]

Welcome to the Community,

I can't really help you with the script, but I will move the post to the appropriate forum.

Anyway, are you aware of VMware's "Discontinuation of third party vSwitch program" (see VMware Knowledge Base) with a link to a migration tool.

André

PS: Discussion moved from PowerShellers to VMware PowerCLI

[LucD]

I assume your Nexus switches have 2 or more uplinks?
And which vSphere version are you using?

[sukhesh01]

Thanks Andre,

Yes i am aware of the Migration tool, but for some reason we are unable to run in it our environment (both 2008 and 2012 OS) That is where we ended up with going with script.

[sukhesh01]

Yes i have two uplinks to it, currently we have mixed environments. Some running in 5.5 and some with 6.0. Our goal is to move all environments to 6.5.

Thanks for you response LucD

[LucD]

One more question, can we place your ESXi nodes in maintenance mode (out of precaution), when we migrate the uplinks?

[sukhesh01]

We were actually looking to migrate one leg and attach it to vds, then test the VM's connectivity(kind of pause in the script) after migration and then move the other while having the Hosts online.

[LucD]

That's one option, but I normally prefer to play it safe(r).

Node in maintenance, disable DRS, migrate 1 uplink, leave maintenance mode, vMotion 1 VM to test connectivity, enable DRS.

But the choice is up to you of course.

[sukhesh01]

Yes i agree, But we are trying to achieve it with less time window, which is reason of not having the Hosts in maintenance. We probably are looking at pausing/confirmation from the user to proceed with each step to mitigate downtime.