Cisco Cisco Nexus 5010 Switch Guia Do Desenho

 

 

Design Guide 

© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 32 of 38 

 

Figure 21.    vPC Peer-Link Failure on the Cisco Nexus 5000 Series 

 

The case of fabric extender dual-connected to the Cisco Nexus 5000 Series in vPC mode is slightly different from that 

of other vPC designs. 

Starting from Cisco NX-OS 4.1(3), you can connect a fabric extender to two Cisco Nexus 5000 Series devices 

configured for vPC. The fabric extender is a satellite switch that depends on the Cisco Nexus 5000 Series for both 

configuration and forwarding. 

In such a design, both Cisco Nexus 5000 Series Switches have equal rights to configure the fabric extender switch 

ports. 

To address this design, in which each fabric extender is controlled by two entities (the two Cisco Nexus 5000 Series 

Switches), the implementation relies on the modeling of each fabric extender port as if it were two independent ports 

configured for vPC. The same fabric extender port appears on each Cisco Nexus 5000 Series Switch, and the Cisco 

Nexus 5000 Series vPC peers operate as if these two ports were forming a PortChannel - and in fact the Cisco 

Nexus 5000 Series Switches are configured in vPC mode according to all the previously described guidelines. 

The 10 Gigabit Ethernet ports connecting the Cisco Nexus

®

 5000 to the fabric extender (switch-port mode fabric) are 

configured as vPC member ports, and the individual ports on the fabric extender, such as port eth100/1/1, appear on 

both nexus5k01 and nexus5k02, as shown in Figure 22.