Hi UCS Community!
I've heard from Cisco that using a single vNIC for vMotion and Management AND having the "Enable Failover" checkbox checked in UCSM, so UCS manages the redundant links through Fabric A and B is the way to go.
And then, for Fibre Channel, iSCSI and guest networking, presenting two vNICS to ESXi- one pinned to Fabric A and the other pinned to Fabric B (no failover on them)- and letting ESXi manage the failover for those.
Is this a practice UCS / ESXi shops are following?
That is an option but I personally haven't been using hardware failover for ESXi hosts. I have been letting ESXi handle the failover. My typical setup has been 2 vNICs for mgmt, 2 for vMotion, 2 for VM traffic and if needed 2 for IP storage. Each pair has a vNIC in Fabric A and B.
I usually use hardware failover for Windows and Linux servers.
I would try to keep things as simple as possible. I'm not sure where the single vnic with fabric failover recommendation came from, but in the past we've always said no fabric failover when you are using a hypervisor vSwitch. That includes vSwitch, vDS, and Nexus 1000V.
I can understand that by using a single nic you are keeping all the vmotion traffic on one FI but then you have to make sure you are always using the right NIC for vmotion.
Keep it simple :-)
I was wondering if thought about just using 2 vNIC for everything under the idea to keep it simple now with multiple 10G on each vNIC? vNIC a on fabirc A and vNIC b on fabric B with no failover? Pros / Cons?
There are a few reasons why I break everything out:
Excellent perspective, there are a lot of different ways however not a “best" guide… I do like some of your examples on why.