Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1550
Views
0
Helpful
1
Replies

CSCtb39514 - vPC shows as connected to diff switch after vPC config remove/restore

ajita.shrivastava@ge.com
Level 1
Level 1

‎08-29-2018 09:01 AM

Hi 

i am getting this error "vpc port channel - misconfig due to vpc links in the 2 switches connected to different"

I thought it was a bug and removed the port channel from the vpc and recreated the VPC but still i was getting same error.

 

SwitchA# sh vpc br
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 : 24
Peer Gateway : Enabled
Peer gateway excluded VLANs : -
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 Po10 up 1,20,28,36-42,44,46,48,80,109-110,112,156,176,185,
208,213,224,228,232,240,301,320,498,500,600-601,19
00-1902,2090-2091,2320-2322

vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
20 Po30 up success success 20
40 Po40 up success success 20
50 Po50 down* success success -
1010 Po1010 up success success 110
1020 Po1020 up success success 110
1030 Po1030 up success success 110
1040 Po1040 up success success 110
1050 Po1050 up success success 110
1060 Po1060 up success success 110
1070 Po1070 up success success 110
1100 Po1100 up success success 1,20,28,36-
42,44,46,48
,80,109-110
,112,156,17
6,185,20....
1110 Po1110 up success success 1,20,28,36-
42,44,46,48
,80,109-110
,112,156,17
6,185,20....
1120 Po1120 up success success 1,20,28,36-
42,44,46,48
,80,109-110
,112,156,17
6,185,20....
1130 Po1130 up success success 1,20,28,36-
42,44,46,48
,80,109-110
,112,156,17
6,185,20....
2100 Po2100 down* success success -
2110 Po2110 down* success success -
2120 Po2120 down* success success -
2130 Po2130 down* success success -
2140 Po2140 down* success success -
2150 Po2150 down* success success -
2160 Po2160 down* success success -
2170 Po2170 down* success success -
2180 Po2180 down* failed vpc port channel -
mis-config due to vpc
links in the 2 switches
connected to different
partners
2190 Po2190 down* failed vpc port channel -
mis-config due to vpc
links in the 2 switches
connected to different
partners

=========

SwitchB# sh vpc consistency-parameters int Po1130

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
Shut Lan 1 No No
STP Port Type 1 Edge Trunk Port Edge Trunk Port
STP Port Guard 1 None None
STP MST Simulate PVST 1 Default Default
lag-id 1 [(fa0, 0-23-4-ee-be-1, [(fa0, 0-23-4-ee-be-1,
846a, 0, 0), (1a00, 846a, 0, 0), (1a00,
0-23-e9-c0-1a-0, 1, 0, 0-23-e9-c0-1a-0, 1, 0,
0)] 0)]
mode 1 active active
Speed 1 10 Gb/s 10 Gb/s
Duplex 1 full full
Port Mode 1 trunk trunk
Native Vlan 1 1 1
MTU 1 1500 1500
Admin port mode 1
Allowed VLANs - 1,20,28,36-42,44,46,48 1,20,28,36-42,44,46,48
,80,109-110,112,156,17 ,80,109-110,112,156,17
6,185,208,213,224,228, 6,185,208,213,224,228,
232,240,301,320,498,50 232,240,301,320,498,50
0,600-601,946,1900-190 0,600-601,945,1900-190
2,2090-2091,2320-2322 2,2090-2091,2320-2322
Local suspended VLANs - 946 -

========

SwitchA# sh vpc consistency-parameters int po2180

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
Shut Lan 1 No No
STP Port Type 1 Edge Port Edge Port
STP Port Guard 1 None None
STP MST Simulate PVST 1 Default Default
lag-id 1 [(fa0, 0-23-4-ee-be-1, [(fa0, 0-23-4-ee-be-1,
8884, 0, 0), (8000, 8884, 0, 0), (8000,
2-a0-98-da-3f-d8, b2, 2-a0-98-da-3f-ca, d2,
0, 0)] 0, 0)]
mode 1 active active
Speed 1 10 Gb/s 10 Gb/s
Duplex 1 full full
Port Mode 1 trunk trunk
Native Vlan 1 1 1
MTU 1 1500 1500
Admin port mode 1
Allowed VLANs - 110,498 110,498
Local suspended VLANs - - -

================


SwitchB# sh vpc consistency-parameters int po2180

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
Shut Lan 1 No No
STP Port Type 1 Edge Port Edge Port
STP Port Guard 1 None None
STP MST Simulate PVST 1 Default Default
lag-id 1 [(fa0, 0-23-4-ee-be-1, [(fa0, 0-23-4-ee-be-1,
8884, 0, 0), (8000, 8884, 0, 0), (8000,
2-a0-98-da-3f-ca, d2, 2-a0-98-da-3f-d8, b2,
0, 0)] 0, 0)]
mode 1 active active
Speed 1 10 Gb/s 10 Gb/s
Duplex 1 full full
Port Mode 1 trunk trunk
Native Vlan 1 1 1
MTU 1 1500 1500
Admin port mode 1
Allowed VLANs - 110,498 110,498
Local suspended VLANs - - -
ISSssEUKlonpr01b#

 

 

2 people had this problem
Labels:
0 Helpful
1 Reply 1

Darkmatter
Level 1
Level 1

‎03-26-2021 08:44 AM

I too had this issue with a back to back vPC between N7K and N3K.

 

show vpc 55

The vPC on N7K showed being up and success passed consistency checks.

The vPC on N3K side consistency checks failed and reason was "vpc port channel mis-config due to vpc links in the 2 switches connected to different partners"

 

Carefully investigating the config of every port involved in the vPC on both Nexus switches N7K and N3K did not show any configuration error, as the config was correct.

 

The hint came when i ran the command "show lacp interface ethernet x/y" on the N3K and N7K.

On N7K, the Neighbor stats for LACP for one of the interfaces downstream, to one of the N3K, had basically no info and neighbor MAC was all 00-00-00-00-00-00 (checking this for every interface in the port-channel going downstream)

This way i could narrow it down to one specific switch that posed to be the problem.

Seemed like it was one of the N3K switches that did not properly sent out LACP negotiations to the upstream N7K.

Looks like you can trigger this behaviour if you reconfigure interfaces that were already part of a vPC, but now decided to use these interfaces for another vPC.

 

Bouncing the port-channel on this switch (N3K-B)did the trick!  (so shut -> no shut)

From that point on, port-channel and vPC came up directly on this switch and the issue was resolved.

 

I'm aware this is a very old post, still i hope people who will find it will be supported in their troubleshooting when they come across this issue.

0 Helpful
Customers Also Viewed These Support Documents