Cisco N5K-C5010P-BF Troubleshooting Guide - Page 147

Peer-link issues, Possible Cause, Solution, show cdp neighbor - n5k c5020p bf

Page 147 highlights

Chapter 8 Troubleshooting Virtual Port Channel Issues Improper Configurations Send document comments to [email protected]. !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 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: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 500 Peer status : peer link not configured vPC keep-alive status : peer is alive 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 S - Switch, H - Host, I - IGMP, r - Repeater, V - VoIP-Phone, D - Remotely-Managed-Device, s - Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability Platform Port ID switch2(SSI1324033X)Eth1/25 switch2(SSI1324033X)Eth1/26 128 S I s 128 S I s N5K-C5020P-BF Eth1/25 N5K-C5020P-BF Eth1/26 OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 8-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

Send document comments to [email protected].
8-5
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 8
Troubleshooting Virtual Port Channel Issues
Improper Configurations
!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
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:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id
: 500
Peer status
: peer link not configured
vPC keep-alive status
: peer is alive
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
S - Switch, H - Host, I - IGMP, r - Repeater,
V - VoIP-Phone, D - Remotely-Managed-Device,
s - Supports-STP-Dispute
Device-ID
Local Intrfce Hldtme Capability
Platform
Port ID
switch2(SSI1324033X)Eth1/25
128
S I s
N5K-C5020P-BF Eth1/25
switch2(SSI1324033X)Eth1/26
128
S I s
N5K-C5020P-BF Eth1/26