When creating the Dynamic vNIC Connection Policy I note the option “Protection” in which you can preference FabA or FabB, however, this is for the entire DVS, correct?
If I want for example a VMotion Port-Profile with ALL traffic switched locally on FabA with failover to FabB, how can this be achieved? Can Pin Groups still be used with VMFEX??
I recommend placing vMotion and Management vmkernel interfaces on standard a vSwitch and use the VM-FEX for VM networking only. VM-FEX and Nexus 1000v are really designed as VM networking access switches and not physical host access switches.
Our standard config for UCS is this:
- vmnic0 and vmnic1 - uplinks on standard vSwitch0 and used for Management vmkernel, QoS applied for silver class
- vmnic2 and vmnic3 - uplinks on standard vSwitch1 and used for vMotion vmkernel, vmnic2 is active and vmnic3 is standby. This forces vMotion to stay on one fabric interconnect or the other. QoS applied for bronze class
- vmnic4 and vmnic5 - uplinks to either a VMware Distributed switch, Nexus 1000v or VM-FEX. QoS applied for Platinum class
If IP storage is in the mix then we create 2 additional vmnics for that using the Platinum class