Cisco N5K-C5010P-BF Troubleshooting Guide - Page 145

Connectivity issues, Possible Cause, Solution, show run interface mgmt 0

Page 145 highlights

Chapter 8 Troubleshooting Virtual Port Channel Issues Improper Configurations Send document comments to [email protected]. id Port Status Active vlans 1 Po500 down - 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: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 500 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status: success vPC role : primary, operational secondary Number of vPCs configured : 4 Peer Gateway : Disabled Dual-active excluded VLANs : - vPC Peer-link status id Port Status Active vlans 1 Po500 up 1,19,91,99,757 Connectivity issues Possible Cause vPC peer keepalive link and connectivity issues over mgmt0 might exist. Solution • 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: OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 8-3

  • 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-3
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 8
Troubleshooting Virtual Port Channel Issues
Improper Configurations
id
Port
Status Active vlans
--
----
------ --------------------------------------------------
1
Po500
down
-
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:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id
: 500
Peer status
: peer adjacency formed ok
vPC keep-alive status
: peer is alive
Configuration consistency status: success
vPC role
: primary, operational secondary
Number of vPCs configured
: 4
Peer Gateway
: Disabled
Dual-active excluded VLANs
: -
vPC Peer-link status
---------------------------------------------------------------------
id
Port
Status Active vlans
--
----
------ --------------------------------------------------
1
Po500
up
1,19,91,99,757
Connectivity issues
Possible Cause
vPC peer keepalive link and connectivity issues over mgmt0 might exist.
Solution
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: