Cisco N5K-C5010P-BF Troubleshooting Guide - Page 126

Troubleshooting Fibre Channel forwarding issues, When troubleshooting FC performance problems

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

Registers and Counters Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. When troubleshooting FC performance problems, review the R_RDY, Link Reset, and Link Reset Response counters. These help determine buffer to buffer credit problems that could lead to performance issues. Troubleshooting Fibre Channel forwarding issues To troubleshoot Fibre Channel forwarding issues, it is important to know that GATOS is the MAC/Forwarding ASIC on the Nexus 5000 switch. This section describes commands specific to this ASIC. Each Fibre Channel interface is assigned a GATOS number. To understand forwarding issues, you must find the GATOS number for the specific FC interface. Consider the following example: switch# sh platform fwm info pif fc2/1 dump pif info: ifindex 0x1080000 dump_all 0 verbose 1 fc2/1: slot 1 port 0 state 0x0 pi_if 0x88bbb74 fwimpd ctx 0x889d4ec fc2/1: oper_mode 0x1 rcvd_rbind: No fc2/1: iftype 0x1 encap 0x5 bound_if? N #lifs 1 fwimpd ctx 0x88bd74c fc2/1: lif_blk(pi) 0x8523da4 vif_id_alloc_bmp 0x887360c fc2/1: cfg_lif_blk_size 0 lif_blk_base(pi) 1922 lif_blk_size(pi) 1 fc2/1: cfg_lif_blk_size(pi) 0 fc2/1: if_flags 0x0 num_sub_lif_tbls 0 Num HIFs pinned 0 fc2/1 pd: lif_entries 1 if_map_idx 49 if_lid 33 if_fcoe_lid 34 fc2/1 pd: reverse ifmap lookup 'same' ifmap_idx 49 fc2/1: SAT_HIF Port?: No In the following part of the example, notice that gatos_num 13 is the GATOS instance for Fibre Channel interface 2/1: fc2/1 pd: slot 1 logical port num 4 gatos_num 13 fwm_inst 0 fc2/1 pd: pif_type 'data fc'(2) hw_present 1 port map idx 49 fc2/1 pd: fabric a info: voq 0-1 port_id 29 connected 1 up 1 fc2/1 pd: fabric b info: voq 0-1 port_id 29 connected 1 up 1 fc2/1 pd: subported 1 primary 1 atherton 0 fc2/1 pd: sup_src_dst_if 17 lif_blk 0-0 fc2/1 pd: policer info: uc (sel 2) mc (sel 1) bc (sel 0) fc2/1 pd: mac-addr 000d.eca4.02b4 fc 0 In the following part of the example, notice that the command also provides forwarding drop and discard informatio: fc2/1 pd: tx stats: bytes 4958178736 frames 36360131 discard 0 drop 0 fc2/1 pd: rx stats: bytes 2421909296 frames 36390924 discard 0 drop 0 You can also display GATOS errors for the GATOS instance that corresponds to the FC interface. In the following part of the example, notice that the command only shows non-zero counters. switch# show platform fwm info gatos-errors 13 Printing non zero Gatos error registers: DROP_FCF_SW_VSAN_IDX_MISS: res0 = 60 res1 = 0 DROP_FCF_SW_DOMAIN_IDX_MISS: res0 = 489036 res1 = 0 DROP_FCF_SW_TBL_MISS: res0 = 489036 res1 = 0 DROP_NO_FABRIC_SELECTED: res0 = 489036 res1 = 0 DROP_VLAN_MASK_TO_NULL: res0 = 489036 res1 = 0 In the first of the two parts, drops and discards were described. Notice that the drop and discard counters are separate for vEthernet and VFC interfaces. Review the output in the second example to help correlate the reason for the drops. 5-54 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-54
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Registers and Counters
When troubleshooting FC performance problems, review the R_RDY, Link Reset, and Link Reset
Response counters. These help determine buffer to buffer credit problems that could lead to performance
issues.
Troubleshooting Fibre Channel forwarding issues
To troubleshoot Fibre Channel forwarding issues, it is important to know that GATOS is the
MAC/Forwarding ASIC on the Nexus 5000 switch. This section describes commands specific to this
ASIC.
Each Fibre Channel interface is assigned a GATOS number. To understand forwarding issues, you must
find the GATOS number for the specific FC interface.
Consider the following example:
switch# sh platform fwm info pif fc2/1
dump pif info: ifindex 0x1080000 dump_all 0 verbose 1
fc2/1: slot 1 port 0 state 0x0 pi_if 0x88bbb74 fwimpd ctx 0x889d4ec
fc2/1: oper_mode 0x1 rcvd_rbind: No
fc2/1: iftype 0x1
encap 0x5
bound_if? N #lifs 1 fwimpd ctx 0x88bd74c
fc2/1: lif_blk(pi) 0x8523da4 vif_id_alloc_bmp 0x887360c
fc2/1: cfg_lif_blk_size 0 lif_blk_base(pi) 1922 lif_blk_size(pi) 1
fc2/1: cfg_lif_blk_size(pi) 0
fc2/1: if_flags 0x0 num_sub_lif_tbls 0 Num HIFs pinned 0
fc2/1 pd: lif_entries 1
if_map_idx 49
if_lid 33 if_fcoe_lid 34
fc2/1 pd: reverse ifmap lookup 'same' ifmap_idx 49
fc2/1: SAT_HIF Port?: No
In the following part of the example, notice that gatos_num 13 is the GATOS instance for Fibre Channel
interface 2/1:
fc2/1 pd: slot 1
logical port num 4
gatos_num 13
fwm_inst 0
fc 0
fc2/1 pd: pif_type 'data fc'(2) hw_present 1
port map idx 49
fc2/1 pd: fabric a info: voq 0-1
port_id 29 connected 1 up 1
fc2/1 pd: fabric b info: voq 0-1
port_id 29 connected 1 up 1
fc2/1 pd: subported 1 primary 1 atherton 0
fc2/1 pd: sup_src_dst_if 17
lif_blk 0-0
fc2/1 pd: policer info: uc (sel 2) mc (sel 1) bc (sel 0)
fc2/1 pd: mac-addr 000d.eca4.02b4
In the following part of the example, notice that the command also provides forwarding drop and discard
informatio:
fc2/1 pd: tx stats: bytes 4958178736 frames 36360131 discard 0 drop 0
fc2/1 pd: rx stats: bytes 2421909296 frames 36390924 discard 0 drop 0
You can also display GATOS errors for the GATOS instance that corresponds to the FC interface. In the
following part of the example, notice that the command only shows non-zero counters.
switch# show platform fwm info gatos-errors 13
Printing non zero Gatos error registers:
DROP_FCF_SW_VSAN_IDX_MISS: res0 = 60 res1 = 0
DROP_FCF_SW_DOMAIN_IDX_MISS: res0 = 489036 res1 = 0
DROP_FCF_SW_TBL_MISS: res0 = 489036 res1 = 0
DROP_NO_FABRIC_SELECTED: res0 = 489036 res1 = 0
DROP_VLAN_MASK_TO_NULL: res0 = 489036 res1 = 0
In the first of the two parts, drops and discards were described. Notice that the drop and discard counters
are separate for vEthernet and VFC interfaces. Review the output in the second example to help correlate
the reason for the drops.