Cisco N5K-C5010P-BF Troubleshooting Guide - Page 146

Cisco Nexus 5000 Series Troubleshooting Guide, OL-25300-01,

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 146 highlights

Improper Configurations Chapter 8 Troubleshooting Virtual Port Channel Issues Send document comments to [email protected]. switch1# ping 172.18.118.162 vrf management PING 172.18.118.162 (172.18.118.162): 56 data bytes 64 bytes from 172.18.118.162: icmp_seq=0 ttl=254 time=5.306 ms 64 bytes from 172.18.118.162: icmp_seq=1 ttl=254 time=3.963 ms 64 bytes from 172.18.118.162: icmp_seq=2 ttl=254 time=4.04 ms 64 bytes from 172.18.118.162: icmp_seq=3 ttl=254 time=4.077 ms 64 bytes from 172.18.118.162: icmp_seq=4 ttl=254 time=4.057 ms If the ping fails, it means that the connectivity between both mgmt0 interfaces does not exist or that they are not interconnected properly. Make sure the mgmt0 interface is unshut and that you can ping the switch mgmt0 interface. switch# sh int br | grep mgmt0 mgmt0 -- down 172.16.118.62 -- 1500 If the status shows that it is down, it means there is no physical connection to mgmt0 or that the interface is in admin shutdown. You need to verify the physical connectivity and unshut the port: switch1# config t switch1(config)# int mgmt 0 switch1(config-if)# no shut switch1(config-if)# show int br | grep mgmt0 mgmt0 -- up 172.16.118.62 1000 1500 If pinging the other switch continues to fail, then there is an interconnection issue between the two Nexus 5000 switches. Check the networking in between the switches: - Switch interconnecting in access VLAN mode, using the same VLAN for both Nexus switches. - The VLAN is allowed across and between the switches. • Check the vPC configuration and compare the mgmt0 IP addresses that are used: switch1# show run int mgmt 0 !Command: show running-config interface mgmt0 !Time: Tue Mar 8 03:53:48 2011 version 4.2(1)N2(1) interface mgmt0 ip address 172.18.118.163/24 switch1# show run vpc !Command: show running-config vpc !Time: Tue Mar 8 03:53:57 2011 version 4.2(1)N2(1) feature vpc vpc domain 500 peer-keepalive destination 172.18.118.162 switch2# show run int mgmt 0 !Command: show running-config interface mgmt0 Cisco Nexus 5000 Series Troubleshooting Guide 8-4 OL-25300-01

  • 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-4
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 8
Troubleshooting Virtual Port Channel Issues
Improper Configurations
switch1# ping 172.18.118.162 vrf management
PING 172.18.118.162 (172.18.118.162): 56 data bytes
64 bytes from 172.18.118.162: icmp_seq=0 ttl=254 time=5.306 ms
64 bytes from 172.18.118.162: icmp_seq=1 ttl=254 time=3.963 ms
64 bytes from 172.18.118.162: icmp_seq=2 ttl=254 time=4.04 ms
64 bytes from 172.18.118.162: icmp_seq=3 ttl=254 time=4.077 ms
64 bytes from 172.18.118.162: icmp_seq=4 ttl=254 time=4.057 ms
If the ping fails, it means that the connectivity between both mgmt0 interfaces does not exist or that
they are not interconnected properly.
Make sure the mgmt0 interface is unshut and that you can ping the switch mgmt0 interface.
switch# sh int br | grep mgmt0
mgmt0
--
down
172.16.118.62
--
1500
If the status shows that it is down, it means there is no physical connection to mgmt0 or that the
interface is in admin shutdown. You need to verify the physical connectivity and unshut the port:
switch1# config t
switch1(config)# int mgmt 0
switch1(config-if)# no shut
switch1(config-if)# show int br | grep mgmt0
mgmt0
--
up
172.16.118.62
1000
1500
If pinging the other switch continues to fail, then there is an interconnection issue between the two
Nexus 5000 switches.
Check the networking in between the switches:
–
Switch interconnecting in access VLAN mode, using the same VLAN for both Nexus switches.
–
The VLAN is allowed across and between the switches.
•
Check the vPC configuration and compare the mgmt0 IP addresses that are used:
switch1# show run int mgmt 0
!Command: show running-config interface mgmt0
!Time: Tue Mar
8 03:53:48 2011
version 4.2(1)N2(1)
interface mgmt0
ip address 172.18.118.163/24
switch1# show run vpc
!Command: show running-config vpc
!Time: Tue Mar
8 03:53:57 2011
version 4.2(1)N2(1)
feature vpc
vpc domain 500
peer-keepalive destination 172.18.118.162
switch2# show run int mgmt 0
!Command: show running-config interface mgmt0