You say that vMotion will be fully supported to the 1000v VSM. Does that also mean that the VSM VM can run on the same VEM and ESX cluster that it is managing? If so, that's different from early information I received.

(Sorry to hijack this thread)

Randy

There must be some misconfiguration. I'm able to migrate my VSM to VEM and migrate service console port with no issues. The VSM is not in the datapath. So if the VSM goes away the VEM will continue to foward packets based on the last known configuration from the VSM.

Now you can't migrate the VSM at the same time you add a host to the VEM. That creates a catch-22 condition. The VEM needs to talk to the VSM , but yet you are migrating the VSM so it has no network connection.

If you have two nics create another vswitch and stick the VSM connections on that vswitch. Migrate your service console and vmk interfaces from the initial vswitch and then create port-profiles for control, packet, and management. Once the VEM is connected and the port-profiles are created you can migrate the VSM to the VEM.

louis