Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch

 

 

Design Guide 

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

Page 33 of 38 

 

Figure 22.    Fabric Extender Active-Active Design 

 

To keep the nexus5k01 and nexus5k02 configurations synchronized, starting from Cisco NX-OS 5.0(2)N1(1) you can 

use the configuration synchronization feature to define the fabric extender port configuration in a switch profile to help 

ensure consistency between the two configurations. 

With this topology, PortChannels work on fabric extenders, but you cannot create a vPC from a server that is split 

between two fabric extenders (for this, you need to use the fabric extender straight-through topology). 

The failure scenarios previously described for vPC member ports apply equally to the fabric extender ports. If the 

peer link is lost, the vPC secondary device shuts down the fabric ports that are connected to the secondary Cisco 

Nexus 5000 Series device. 

vPC Role and Priority 

A domain needs to be defined (as indicated by the domain ID) as well as priorities to define primary and secondary 

roles in the vPC configuration. The lower number has higher priority, so it wins. For two switches (vPC peers) to form 

a vPC system, the domain IDs of these switches need to match. As previously described, the domain ID is used to 

generate the LAGID in the LACP negotiation. 

agg1(config)# vpc domain <domain-id>