08-28-2015 02:30 PM
Hello,
Recently I have implemented vPC on Nexus 5500 switches. On other side Router is connected with. The port-channel is configured in On mode.
I got strange output from primary nexus:
Nexus1# show vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary, operational primary
Number of vPCs configured : 4
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po1 up 31,42,61, 221
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
1 Po7 up success success 31,42,61,221,
2 Po8 up success success 31,42,61, 221,
5 Po9 up success Type checks were bypassed 61
for the vPC
On Second Nexus2, hire is output:
Nexus2# show vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary, operational secondary
Number of vPCs configured : 4
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po1 up 31,42,61, 221
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
1 Po7 up success success 31,42,61,221,
2 Po8 up success success 31,42,61, 221,
5 Po9 up success success 61
I am interesting what does, Type checks were bypassed 61 for the vPC message indicate ? Is it something to be afraid of ?
Solved! Go to Solution.
09-01-2015 01:18 AM
Hi,
The message is due to the vPC auto recovery feature and is usually an indication that there has been a combination of failures that has led to the switches not being able to detect each other on either the vPC peer link or the peer keepalive link.
Originally this situation would result in the vPC member ports never being initialised, but the “auto recovery” feature now allows a switch to bypass the consistency checks and enable vPC member ports after 240 seconds i.e., the timeout seen for the “Auto-recovery status” in the show vpc command.
There’s a document, vPC Auto-Recovery Feature in Nexus 7000, that describes the vPC Auto recovery command and the situations that require it that should clarify things. Whilst it’s written for the Nexus 7000 it’s equally applicable to the Nexus 5000 series.
Regards
09-01-2015 01:18 AM
Hi,
The message is due to the vPC auto recovery feature and is usually an indication that there has been a combination of failures that has led to the switches not being able to detect each other on either the vPC peer link or the peer keepalive link.
Originally this situation would result in the vPC member ports never being initialised, but the “auto recovery” feature now allows a switch to bypass the consistency checks and enable vPC member ports after 240 seconds i.e., the timeout seen for the “Auto-recovery status” in the show vpc command.
There’s a document, vPC Auto-Recovery Feature in Nexus 7000, that describes the vPC Auto recovery command and the situations that require it that should clarify things. Whilst it’s written for the Nexus 7000 it’s equally applicable to the Nexus 5000 series.
Regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide