vmotion between clusters, with vmotion in a DVS switch - GUIDs don't match?

[TedH256]

Apparently each DVS has it's own guid - and when you try to vmotion across clusters when each cluster has it's own DVS - the vmotion fails because the DVS guids don't match?

Is it possible to have a dvport group span clusters, and would that "work" to enable the flexibility of being able to vmotion workloads between clusters?

[HeathReynolds]

Yeah, each DVS would be a live migration boundary.

Over time the VMware VDS configuration maximums have gotten much larger. We are going to a design with a core fabric and a secure fabric, and each DC will only have two distributed switches. You can have a distributed switch that spans multiple clusters, as long as they are under the same datacenter object in vCenter.

[chriswahl]

Refer to the configuration maximums for VDS: http://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdf

• 1,016 active ports per host
• 6,500 port groups per VDS
• 60,000 ports per VDS

You can quite easily span a VDS across many clusters inside a common datacenter object.