Scribd
Upload
556 views2 pages

Nexus 7000 VPC Role Change

After a failover, the vPC operational primary and secondary roles may not match the original configuration. To restore the matching roles: 1) change the role priority on the operational primary to the highest value (32768); 2) shut and unshut the peer-link portchannel; 3) the roles will now match the original configuration with the operational secondary as the new primary.

Uploaded by

a_giri1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
556 views2 pages

Nexus 7000 VPC Role Change

After a failover, the vPC operational primary and secondary roles may not match the original configuration. To restore the matching roles: 1) change the role priority on the operational primary to the highest value (32768); 2) shut and unshut the peer-link portchannel; 3) the roles will now match the original configuration with the operational secondary as the new primary.

Uploaded by

a_giri1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

COMMAND SUMMARY:

(On Operational Primary,configured Secondary)


CORE-SEC(config)# vpc domain 1
CORE-SEC(config-vpc-domain)# no role priority 32000
CORE-SEC(config)# int po 301
CORE-SEC(config-if)# sh
CORE-SEC(config-if)# no sh
CORE-SEC(config-if)# sh vpc role
After failover, the vPC operational primary and vPC operational secondary do not match the original
configuration.You can restore matching by following these configuration steps: from the vPC operational
primary, you can change the role priority to the highest value (32768) and then enter a shut/no shut
command on the peer-link PortChannel.
CORE-SEC# sh vpc role
vPC Role status
----------------------------------------------------
vPC role : secondary, operational primary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:01
vPC system-priority : 32667
vPC local system-mac : b4:14:89:e0:fb:41
vPC local role-priority : 32000
CORE-SEC(config)# vpc domain 1
CORE-SEC(config-vpc-domain)# no role priority 32000
Warning:
!!:: vPCs will be flapped on current primary vPC switch while attempting role change ::!!
Note:
--------:: Change will take effect after user has re-initd the vPC peer-link ::--------
CORE-SEC(config-vpc-domain)#
CORE-SEC(config-vpc-domain)# exit
CORE-SEC(config)# int po 301
CORE-SEC(config-if)# sh
CORE-SEC(config-if)# no sh
CORE-SEC(config-if)# sh vpc role
vPC Role status
----------------------------------------------------
vPC role : secondary, operational primary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:01
vPC system-priority : 32667
vPC local system-mac : b4:14:89:e0:fb:41
vPC local role-priority : 32000
CORE-SEC(config-if)# sh vpc role
vPC Role status
----------------------------------------------------
vPC role : secondary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:01
vPC system-priority : 32667
vPC local system-mac : b4:14:89:e0:fb:41
vPC local role-priority : 32667
CORE-SEC(config-if)#
=====================================
vPC Role Change
Sunday, April 27, 2014
14:18
vPC Role Change Page 1
Nexus KT Internal
Monday, June 23, 2014
10:54 PM
vPC Role Change Page 2

You might also like