ucs fabric interconnect learns dynamic MAC address

In a VMware setup, failover and load-balancing is usually configured at the vSwitch level. Note: This setup is not typical for an ESXi deployment, but more common for Windows or Linux bare-metal deployments. vNIC eth0 has fabric A as the primary fabric with failover to B and vNIC eth1 has fabric B as the primary fabric with failover to A. So to start, I created a service profile for a VMware ESXi host that has two separate vNICs, named eth0 and eth1. This serves a dual purpose: Gaining more insight in the actual implementation of the fabric failover feature and getting more familiar with some essential UCS screens and commands. Instead of rehashing the basic principles of fabric failover, I intend to dive a bit deeper into the UCSM GUI, UCSM CLI and NX-OS CLI to examine and illustrate the operation of this feature inside UCS.

So if you need a quick primer or refresher on this feature, then I recommend that you read Brad Hedlund’s classic post “ Cisco UCS Fabric Failover: Slam Dunk? or So What?“. In this post I do not intend to cover the basics of Fabric Failover, as this has already been done excellently by other bloggers. This is especially true for bare-metal Windows or Linux servers on UCS blades or rack servers. Therefore, I think that a feature that offers resiliency against path failures for Ethernet traffic without any need for teaming configuration inside the operating system, is very interesting. However, due to missing or misconfigured teaming, these servers would still lose their connectivity if the primary link failed. I have often encountered servers that were supposed to be redundantly connected to the network, as they were physically connected to two different switches. This function is entirely transparent to the operating system running on the server and does not require any configuration inside the OS. I think that this feature is quite useful, because it creates resiliency for UCS blades or rack servers, without depending on any drivers or configuration inside the operating system. Fabric failover is a unique feature of the Cisco Unified Computing System that provides a “teaming-like” function in hardware.

Ucs fabric interconnect learns dynamic MAC address