Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 62 of 119
Eth1/38 - Interface Up. State: Active
Fex Port State Fabric Port Primary Fabric
Eth100/1/1 Down Eth1/37 Eth1/37
[...]
Eth100/1/15 Down Eth1/37 Eth1/37
Eth100/1/23 Down Eth1/38 Eth1/38
[...]
Eth100/1/32 Down Eth1/38 Eth1/38
Eth100/1/33 Down None None
[...]
Eth100/1/46 Down None None
Eth100/1/47 Down None None
Pinning reconfiguration is a disruptive operation, so it is good practice to make the pinning assignment
deterministic using the redistribute command before the Cisco Nexus 2000 Series Fabric Extender is put into
production:
fex pinning redistribute
PortChannels
The links connecting the fabric extender to the Cisco Nexus 5000 Series Switch can be configured as
PortChannels, as shown in Figure 24.
If you are using all the available fabric extender fabric links (four 10 Gigabit Ethernet links), traffic is distributed
across all fabric links based on the PortChannel load-balancing algorithm of your choice, which for the fabric
extender module can hash on Layer 2 and 3 information.
If one fabric link is lost, as in example link 1 here, traffic is distributed across the remaining three links.
Note: On the Cisco Nexus 5000 Series, you can load-balance traffic hashing on the Layer 4 ports, too.
Figure 24. PortChannel Configuration Between Fabric Extender and Cisco Nexus 5000 Series Switches