Cisco Nexus - vPC Peer-Switch

The vPC Peer-Switch feature allows a pair of vPC peer devices to appear as a single logical Spanning Tree Protocol root.

With vPC Peer-Switch enabled downstream devices see both switches as the STP root.



Without vPC Peer-Switch enabled downstream devices still have to funnel Layer 2 traffic via the STP root using the traditional STP traffic flow.




The main advantage of vPC peer-swtich is the improvement in term of convergence time during vPC primary peer device failure/recovery. 

  •  Without vPC peer-switch feature
    • vPC primary peer device failure and recovery can create around 3 seconds of traffic disruption 
  • With vPC peer-switch
    • traffic disruption is lowered to sub-second value 
      • This is since peer device down an up events do not generate any Rapid Spanning Tree Protocol Sync behavior, because, there is no logical change in the L2 topology.


Things to keep in mind:

  • It is a Cisco recommended best practice to activate vPC peer-switch within a vPC environment.
  • vPC peer-switch must be configured on both vPC peer devices
  • When vPC peer-swtich is activated, both vPC peer devices MUST have the same spanning tree configuration 
    • This means the Spanning Tree Protocol priority must match for all vPC VLANs


Configuration Example

vPC Peer Device #1

NEXUS-SW01# conf t
NEXUS-SW01(conf)# spanning-tree vlan 1,10,20,100 priority 12288
NEXUS-SW01(conf)# vpc domain 1
NEXUS-SW01(conf-vpc-domain)# peer-switch
NEXUS-SW01(conf-vpc-domain)# end
NEXUS-SW01# copy running-config startup-config

vPC Peer Device #2
NEXUS-SW02# conf t
NEXUS-SW02(conf)# spanning-tree vlan 1,10,20,100 priority 12288
NEXUS-SW02(conf)# vpc domain 1
NEXUS-SW02(conf-vpc-domain)# peer-switch
NEXUS-SW02(conf-vpc-domain)# end
NEXUS-SW02# copy running-config startup-config

Comments

Post a Comment

Popular posts from this blog

Cisco Fiber Channel Port Types

 Quick reference for which Fiber Channel port types can be used for are likely to show up on 350-601 and 300-625 Cisco Exams: • E Port • F Port • NP Port • TE Port • SD Port • Auto Mode E Port In expansion port (E port) mode, an interface functions as a fabric expansion port.  This port can be connected to another E port to create an inter-switch link between two switches. E ports carry frames between switches for configuration and fabric management.  They serve as a conduit between switches for frames destined for remote N ports.  An E port connected to another switch can also be configured to form a port channel.  F Port In fabric port (F port) mode, an interface functions as a fabric port.  This port can be connected to a peripheral device (host or disk) operating as an N port.  An F port can be attached to only one N port. NP Ports An NP port is a port on a device that is in NPV mode and connected to the core switch via an F port.  NP ports function like N ports, except that in add
Read more

Cisco ACI - Logging in from Postman Using the API

Image
 Most Network Engineers I know are like me, and are largely stuck in our ways of using the CLI. Cisco ACI is almost entirely GUI-based and really there isn't much you can do via the CLI.  Tasks that used to be so simple are now increasingly time-consuming. For Example; I had to configure an access port last week and it took me 10 minutes to get all the options correctly selected before I was done configuring the port. What used to be an easy procedure, whether manual or not, is now far more complicated, with several steps that can be easily missed.  To that end: I've started using the Postman Collection Runner to ensure I'm not missing any of the steps needed to complete these tasks.  Anyway, the first step to using the API is knowing how to get the API Token, which I'll now go over using Cisco's sandbox APIC found at sandboxapicdc.cisco.com. Open Postman, and click "+New Collection." Name it whatever name you prefer, and click "Create". Under yo
Read more