11-14-2012 07:07 AM
Hello,
in the past it was always a problem to move ESX-Hosts with n1v to a new vcenter. The only possibility was to migrate all hosts/VMs back to vswitch before, what's a big effort in large environments.
The procedure to do that was already discussed in this community, for example here:
https://supportforums.cisco.com/thread/2119884
However, it was not only a problem with n1v. VMware DVS switch had the same restriction.
But with VCenter version 5.1 VMware had a new feature implemented to avoid using the vswitch for such a migration, see here:
It's like an Import/Export function for DVS information and it works only for VMware DVS switch.
What's about n1v ? Iwatta wrote in the thread (first link) that cisco is working on a solution for n1v too. What is the current status about that?
Regards
Hendrik
11-14-2012 10:17 AM
Hendrik,
Still no changes in the process for migrating to a new vCenter.
You'll need to migrate to vswitch, move to hosts, reconnect vsm, add hosts back to n1kv.
louis
11-16-2012 01:42 AM
Louis,
is it planed to implement a solution for n1v ?
It would be very,very helpful. One of our n1v environments has for example 62 host in one DC with ~800vnics. All this have to me migrated to vswitch and , after the move to the new VCenter, back to the n1V. It's really a big effort.
And my VMWare colleagues are not happy about that. Especially because VMWare has now a solution for their own DVS I think there should be also a solution for n1v very soon.
Hendrik
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide