Why FEX A/A not support FCoE? https://supportforums.cisco.

com/thread/2067013 First off - Fex Active/Active - we dont support FCoE over Fex A/A because it breaks the idea of SAN A/SAN B is olation. When a single FEX is connected via a vPC to 2 upstream 5ks, the traffi c going through that FEX is hashed between the upstream 5ks. In the SAN world, we would never have this. Devices aren't "meshed" or "dual-homed" and rather we deploy two physical isolated fabrics for HA. Make sense? Now, if we move away from the necessity of deploying two physical fabrics for SA N redundancy, and rely on a single highly available fabric (much like we do in E thernet today) for our SAN traffic, then this may change...however, I don't beli eve we are there yet Second - 4k-->2k limitations - The Nexus 2000 was designed to be spanning-tree edge devices with HOST facing ports. We didnt design the Nexus 2000 to have network ports. In fact, we don't suggest you plug any networking device into a Nexus 2000 (though it can be done with native Ethernet traffic if we follow some special rules regarding spanningtree behavior). For FCoE, the limitation is in the number of FLOGIs we support on a Nexus 5000. IF we did allow a Nexus 4000 to connect to a Nexus 2000 with F CoE, technically up to 512 FLOGIs (16 servers connections per N4k and 32 X N4k p er Nexus 2000) could be logging into a single Nexus 5000 port. Obviously this w ould be dependent on how you designed your network -- but it could happen. We d on't support that many FLOGIs into a single port. So for FLOGI scalability reas ons, we don't support a Nexus 4000 connecting to a Nexus 2000 with FCoE. For FIP Snooping Bridges, like the Nexus 4000 or the Dell Blade you are referenc ing, it is best practice and supported to plug the FIP Snooping device directly into the Nexus 5000 FCF.