Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual page 145

Chapter 8 Troubleshooting Virtual Port Channel Issues
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m .
id
--
1
The two switches in this example have different vPC domain IDs. The vPC domain IDs of these Nexus
switches must be changed to match. This can be done by entering configuration commands, one per line,
and ending each with Cntl + Z.
switch2(config)# vpc domain 500
Changing domain id will flap peer-link and vPCs. Continue (yes/no)? [no] yes
Note:
--------:: Re-init of peer-link and vPCs started
switch2# show vpc brief
Legend:
vPC domain id
Peer status
vPC keep-alive status
Configuration consistency status: success
vPC role
Number of vPCs configured
Peer Gateway
Dual-active excluded VLANs
vPC Peer-link status
---------------------------------------------------------------------
id
--
1
Connectivity issues
Possible Cause
vPC peer keepalive link and connectivity issues over mgmt0 might exist.
Solution
•
OL-25300-01
Port Status Active vlans
---- ------ --------------------------------------------------
Po500 down -
(*) - local vPC is down, forwarding via vPC peer-link
Port Status Active vlans
---- ------ --------------------------------------------------
Po500 up 1,19,91,99,757
Check for the peer keepalive mgmt0 reachability.
On the other Nexus 5000 switch, enter the command:
show run interface mgmt 0
Example:
switch2# sh run int mgmt 0
!Command: show running-config interface mgmt0
!Time: Tue Mar 8 03:20:58 2011
version 4.2(1)N2(1)
interface mgmt0
ip address 172.18.118.162/24
Ensure there is reachability from switch1:
::--------
: 500
: peer adjacency formed ok
: peer is alive
: primary, operational secondary
: 4
: Disabled
: -
Cisco Nexus 5000 Series Troubleshooting Guide
Improper Configurations
8-3