Addresses are not learned on frames from network ports and frames from Server Ports are allowed to be forwarded only when their source addresses have been learned into the switch forwarding table. The address table is managed so that it only contains MAC addresses of stations connected to Server Ports. Therefore, fabric interconnects don’t learn MAC addresses from external LAN switches, they learn MACs from servers inside the chassis only. A given server interface uses a given uplink regardless of the destination it’s trying to reach. In Ethernet end host mode forwarding is based on server-to-uplink pinning. VSS and vPC are techniques implemented on the LAN switches to allow the Fabric Interconnects to keep using EtherChannel in a traditional manner. In addition, the same problem can also be solved on the Fabric Interconnect by a technique called Ethernet Host Virtualizer (aka End Host Mode). I tried to google if FI supports FP but I was not able to find it (2015). In this case, the spanning tree protocol needs to be enabled and it detects a loop. This is a suboptimal solution although it provides high availability, uplink bandwidth is wasted as half the uplinks are not used by traffic as they are in blocking state. To solve this issue, several different techniques can be used like vPC or VSS. The first possibility is to configure FI as Ethernet switches. As such, it can be configured to behave on the Ethernet uplinks either as a group of hosts or as a switch. In the definition of UCS, it became clear that the system is network centric. The UCS 6100 Fabric Interconnects are derived from the hardware of the Nexus 5000 and as such, they can support a variety of network protocols and are capable of acting as Ethernet switches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |