Hi all,
I want to ask some question abaout problem that happen in our UAT earlier.. We follow recommendation on Cisco to set "delay-restore" and "auto-recovery" below "vpc domain x" configuration.. But we think there is some inconsistency, we don't know if this is bug, or "normal".. Maybe someone have experienced the same case like we have..
This is the configuration (2 Nexus 5468 with OS 7.0(5)N1(1) ):
!Command: show running-config vpc all
!Time: Wed Feb 11 17:08:21 2015
version 6.0(2)N1(2)
feature vpc
vpc domain 130
role priority 1000
system-priority 1000
peer-keepalive destination 192.168.151.2 source 192.168.151.1 udp-port 3200 vrf management interval 1000 timeout 5 precedence 6 hold-timeout 3
no peer-config-check-bypass
delay restore 30
no dual-active exclude interface-vlan
no peer-gateway
no auto-recovery
delay restore interface-vlan 10
graceful consistency-check
no fabricpath switch-id
We've set delay restore to minomum (30), so when primary operational vpc reload, there is no RTO.. But "magically", the delay restore value change to 150..! We've try this so many times, so we decided to change the value to 35, and its working, and after reload it is still 35...
Second, for auto-recovery, we've set it to default (no auto-recovery), so when peer-link and keep-alive shutdown in primary, connection still up.. But after no shut the port (keep-alive and peer-link), then we reload the primary / secondary, after we type "sh run vpc all", the auto-recovery is enabled with value 240.. Another "magic" or bug ?! XD
If anyone have the same problem or experienced this, please share your story or let us know on comment below... :)
Thanks,
MY
