Cisco N5K-C5010P-BF Troubleshooting Guide - Page 124

Understanding Fibre Channel interface counters, show interface

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 124 highlights

Registers and Counters Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. 68. cos7OutLost = 0 69. RxPause = 0 70. TxPause = 2266 71. Resets = 0 72. SQETest = 0 73. InLayer3Routed = 0 74. InLayer3RoutedOctets = 0 75. OutLayer3Routed = 0 76. OutLayer3RoutedOctets = 0 77. OutLayer3Unicast = 0 78. OutLayer3UnicastOctets = 0 79. OutLayer3Multicast = 0 80. OutLayer3MulticastOctets = 0 81. InLayer3Unicast = 0 82. InLayer3UnicastOctets = 0 83. InLayer3Multicast = 0 84. InLayer3MulticastOctets = 0 85. InLayer3AverageOctets = 0 86. InLayer3AveragePackets = 0 87. OutLayer3AverageOctets = 0 88. OutLayer3AveragePackets = 0 Understanding Fibre Channel interface counters The show interface command is very useful when troubleshooting physical layer or performance issues with a Fibre Channel interface. In the output of the command, observe the input/output counters and any input/output discards or errors. When input discards increment, the FC packet does not have a valid route in the Forwarding Information Base (FIB). All packets not having a route are considered discards and sent to the supervisor. These packets are NOT dropped; however, they are policed before being sent to the supervisor. You should also check the MAC ASIC for errors. When output discards increment, packets are timing out in egress because the egress is too slow. Check the attached device because it may be a slow draining receiver that is not responding, or not replenishing buffer credits. This causes back pressure to occur on the Nexus 5000 FC interface. Example: switch# show interface fc2/1 fc2/1 is trunking Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 20:41:00:0d:ec:a4:02:80 [snip] 1 minute input rate 5048 bits/sec, 631 bytes/sec, 9 frames/sec 1 minute output rate 6752 bits/sec, 844 bytes/sec, 9 frames/sec 36398816 frames input, 2422447564 bytes 0 discards, 0 errors 0 CRC, 0 unknown class 0 too long, 0 too short 36368010 frames output, 3213593392 bytes 0 discards, 0 errors 1 input OLS, 1 LRR, 0 NOS, 0 loop inits 1 output OLS, 2 LRR, 0 NOS, 0 loop inits 16 receive B2B credit remaining 250 transmit B2B credit remaining 0 low priority transmit B2B credit remaining Interface last changed at Thu Jan 28 18:26:30 2010 5-52 Cisco Nexus 5000 Series Troubleshooting Guide 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].
5-52
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Registers and Counters
68.
cos7OutLost = 0
69.
RxPause = 0
70.
TxPause = 2266
71.
Resets = 0
72.
SQETest = 0
73.
InLayer3Routed = 0
74.
InLayer3RoutedOctets = 0
75.
OutLayer3Routed = 0
76.
OutLayer3RoutedOctets = 0
77.
OutLayer3Unicast = 0
78.
OutLayer3UnicastOctets = 0
79.
OutLayer3Multicast = 0
80.
OutLayer3MulticastOctets = 0
81.
InLayer3Unicast = 0
82.
InLayer3UnicastOctets = 0
83.
InLayer3Multicast = 0
84.
InLayer3MulticastOctets = 0
85.
InLayer3AverageOctets = 0
86.
InLayer3AveragePackets = 0
87.
OutLayer3AverageOctets = 0
88.
OutLayer3AveragePackets = 0
Understanding Fibre Channel interface counters
The
show interface
command is very useful when troubleshooting physical layer or performance issues
with a Fibre Channel interface.
In the output of the command, observe the input/output counters and any input/output discards or errors.
When input discards increment, the FC packet does not have a valid route in the Forwarding Information
Base (FIB). All packets not having a route are considered discards and sent to the supervisor. These
packets are NOT dropped; however, they are policed before being sent to the supervisor. You should also
check the MAC ASIC for errors.
When output discards increment, packets are timing out in egress because the egress is too slow. Check
the attached device because it may be a slow draining receiver that is not responding, or not replenishing
buffer credits. This causes back pressure to occur on the Nexus 5000 FC interface.
Example:
switch# show interface fc2/1
fc2/1 is trunking
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:41:00:0d:ec:a4:02:80
[snip]
1 minute input rate 5048 bits/sec, 631 bytes/sec, 9 frames/sec
1 minute output rate 6752 bits/sec, 844 bytes/sec, 9 frames/sec
36398816 frames input, 2422447564 bytes
0 discards, 0 errors
0 CRC,
0 unknown class
0 too long, 0 too short
36368010 frames output, 3213593392 bytes
0 discards, 0 errors
1 input OLS, 1 LRR, 0 NOS, 0 loop inits
1 output OLS, 2 LRR, 0 NOS, 0 loop inits
16 receive B2B credit remaining
250 transmit B2B credit remaining
0 low priority transmit B2B credit remaining
Interface last changed at Thu Jan 28 18:26:30 2010