Cisco Cisco Nexus 5010 Switch Designanleitung
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 86 of 119
Best Practices with Cisco Nexus 2000 Series Fabric Extenders
In addition to the best practices already listed for the Cisco Nexus 5000 Series, when deploying the Cisco Nexus
2000 Series, you should consider the design options listed here.
Note that spanning tree and LACP are not running between the Cisco Nexus 5000 Series Switches and the Cisco
Nexus 2000 Series Fabric Extenders, so the user does not need to configure these protocols between the Cisco
Nexus 5000 Series and the Cisco Nexus 2000 Series devices. Fabric extender ports are host ports, and so they
are configured for BPDU filtering and for PortFast.
Additional best practices include the following:
●
Each fabric extender module should be assigned a unique number. This unique number enables the same
fabric extender to be deployed in single-attached mode to one Cisco Nexus 5000 Series Switch only or in
fabric extender vPC mode (that is, dual-connected to different Cisco Nexus 5000 Series Switches).
●
Fabric connectivity between the fabric extender and the parent Cisco Nexus 5000 Series Switch should
consider buffering requirements and oversubscription ratios. The more fabric links there are, the more buffer
space is available for N2H traffic and the less oversubscription for H2N traffic.
●
Use fabric extender preprovisioning as much as possible.
●
Single-attached servers should be connected to a fabric extender dual-homed when possible so that the
failure of one Cisco Nexus 5000 Series Switch does not isolate the server.
●
Dual-connected servers that require PortChannels must be connected to fabric extenders single-homed or
dual-homed with two or more ports in the PortChannel and half of the ports attached to each fabric
extender.
●
Dual-homed servers connected to straight-through fabric extenders can be configured for active-standby or
active-active transmit load balancing, and the fabric extender ports should be configured with the vpc
orphan-ports suspend option (Figure 41).
●
FCoE is supported for both fabric extender straight-through and fabric extender active-active topologies, but
the fabric extender straight-through topology provides more equal load distribution than does the fabric
extender active-active topology on the fabric links.
●
When connecting a server with CNAs in a vPC topology, if you want to use FCoE you should connect only
one 10 Gigabit link per fabric. This link is seen as part of a vPC for Ethernet traffic and as a separate SAN
fabric link from a Fibre Channel perspective.