Making modification to the VPC domain config

[VinnyB]

Hi,

I have this pair of Nexus 3000 in vPC and I need to add some commands to the vPC domain (peer-config-check-bypass  on both and role priority on the first one).

I just want to know if I can add these commands without any downtime ?

It will be during maintenance period nonetheless but having no downtime is important.

thanks

edit: I did some tests with a pair of Nexus 5000.

Adding the role priority on the primary switch gives me this :

N2(config-vpc-domain)# role priority 1000
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  ::--------

Looks like it won't do anything until I will reboot a switch ?

Right now, the second switch is primary and I need to reboot the first one (which is secondary).

But this message : vPCs will be flapped on current primary vPC switch while attempting role change. Does this mean that when I will reboot the secondary switch, ports will flap too on the primary ??? It's important they don't flap while the other is rebooting.

And finally, looks like peer-config-check-bypass isn't available on my pair of Nexus 3000 even if it's has the latest firmware... any idea why ?

thanks

[Reza Sharifi]

Hi,

After issuing "role priority 1000" you can simply bring down the VPC peer-link Portchannel and than bring it back up.  This will change the role for you without the need to reboot the switch.

example:

config t

int po 20 (this is vpc peer-link Po)

sh

no sh

Verify with "sh vpc brief"

This should be done during a maintenance window.

HTH

[VinnyB]

thanks

but just entering the command should NOT impact anything until you reboot or shut/no shut the peer-link, right ?

[Reza Sharifi]

That is correct.

HTH