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

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 .
In this example, the destination IP is not correct. The correct IP is 172.18.118.163, which is the peer IP
address.
Peer-link issues
Possible Cause
The peer link is not configured.
Solution
Configure the peer link correctly.
Example:
In this example, the problem is that the vPC peer-link does not exist.
switch1# show vpc brief
Legend:
vPC domain id
Peer status
vPC keep-alive status
Configuration consistency status: failed
Configuration consistency reason: vPC peer-link does not exists
You can use the show cdp neighbor command to determine which physical ports are connected to the
other Nexus switch.
switch1# show cdp neighbor
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
Device-ID
switch2(SSI1324033X)Eth1/25
switch2(SSI1324033X)Eth1/26
OL-25300-01
!Time: Tue Mar 8 03:53:53 2011
version 4.2(1)N2(1)
interface mgmt0
ip address 172.18.118.162/24
switch2# sh run vpc
!Command: show running-config vpc
!Time: Tue Mar 8 03:54:01 2011
version 4.2(1)N2(1)
feature vpc
vpc domain 500
peer-keepalive destination 172.18.118.162
(*) - local vPC is down, forwarding via vPC peer-link
S - Switch, H - Host, I - IGMP, r - Repeater,
V - VoIP-Phone, D - Remotely-Managed-Device,
s - Supports-STP-Dispute
Local Intrfce Hldtme Capability
: 500
: peer link not configured
: peer is alive
128 S I s N5K-C5020P-BF Eth1/25
128 S I s N5K-C5020P-BF Eth1/26
Cisco Nexus 5000 Series Troubleshooting Guide
Improper Configurations
Platform Port ID
8-5