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

 

 

Design Guide 

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

Page 22 of 38 

 

track 10 list boolean OR 

  object 1 

  object 2 

  object 3 

 

! If object 10 goes down on the primary vPC peer,  

! system will switch over to other vPC peer and disable all local vPCs 

vpc domain 1 

  track 10 

In presence of vPC, you can upgrade a device such as a Cisco Nexus 7000 Series Switch using In-Service Software 

Upgrade (ISSU) with no disruption to the traffic. However, if someone modifies the vPC configuration during the 

upgrade, it will cause an inconsistency between the vPC peer devices (the one being upgraded and the other device). 

To avoid this undesirable situation, vPC can lock the configuration on the device that is not undergoing the upgrade 

and release it when the upgrade is complete. 

Starting from Cisco NX-OS 4.2(1)N1(1), you can upgrade the Cisco Nexus 5000 Series with ISSU. In this case, the 

control plane can be unavailable for up to 80 seconds, while the data plane continues to forward traffic. Because of 

this behavior, for Cisco Nexus 5000 Series Switch to undergo ISSU, it cannot be the root switch of a Layer 2 

topology, nor can it have designated ports (except edge ports and the vPC peer-link). 

To use ISSU on a Cisco Nexus 5000 Series vPC topology, make sure that the peer keepalive is not a Layer 2 link 

between the Cisco Nexus 5000 Series Switch(this would be designated port). 

ISSU on the Cisco Nexus 5000 Series requires Bridge Assurance to be disabled on all links except the vPC peer link. 

You can then use ISSU with the vPC peer link configured for Bridge Assurance (which is the default configuration). 

vPC and routing concurrently coexist without problems on the same switch. A Layer 3 switch configured for vPC 

provides an aggregation layer that is Layer 3 connected to the core and Layer 2 connected to the access layer with 

vPCs. 

Be sure to distinguish between a design where the vPC switch routing on Layer 3 or 2 links, and a design where the 

vPC switch is specifically exchanging routing updates over the Layer 2 vPC links. This latter scenario is typically 

relevant only to data center interconnect (DCI) designs, a topic that is not discussed in this guide. 

The use of HSRP in the context of vPC does not require any special configuration. The active HSRP interface 

answers ARP requests like normal HSRP deployments do, but with vPC both HSRP interfaces (active and standby) 

can forward traffic. 

HSRP Configuration and Best Practices for vPC 

The configuration on the HSRP primary device looks like this: 

interface vLAN50 

  no shutdown 

  ip address 10.50.0.251/24 

  hsrp 50 

    preempt delay minimum 180 

    priority 150