Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 47

Troubleshooting a marginal link, Loopback modes

Get Dell Brocade 6520 PDF manuals and user guides View all Dell Brocade 6520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

Marginal links 3 Only one frame is transmitted and received at any given time. An external cable is not required to run this test. The port LEDs flicker green rapidly while the test is running. Table 5 shows the different loopback modes you can use when using portLoopbackTest to test a marginal link. TABLE 5 Loopback modes Loopback mode Description 1 Port Loopback (loopback plugs) 2 External Serializer/Deserializer (SerDes) loopback 5 Internal (parallel) loopback (indicates no external equipment) 7 Back-end bypass and port loopback 8 Back-end bypass and SerDes loopback 9 Back-end bypass and internal loopback Troubleshooting a marginal link 1. Enter the portErrShow command. 2. Determine whether there is a relatively high number of errors (such as CRC errors or ENC_OUT errors), or if there are a steadily increasing number of errors to confirm a marginal link. Sample the data every 5 minutes until you see the counters increment. • The frames tx and rx are the number of frames being transmitted and received. • The crc_err counter are frames with CRC errors. If this counter goes up, then the physical path should be inspected. Check the cables to and from the switch, patch panel, and other devices. Check the SFP by swapping it with a known good working SFP. If you see this issue on an 8 Gbps blade, use the portCfgFillWord command to reduce EMI. • The crc_g_eof counter are frames with CRC errors and a good EOF. The first port detecting a CRC error marks the frame with a bad EOF and passes the frame on to its destination. Subsequent ports in the path also detect the CRC error and the crc_err counter increments on these ports. However, since the first port marked the frame with a bad EOF, the good EOF counter on the subsequent ports does not increment. The marginal link associated with the port with an increasing good EOF counter is the marginal link and the source of the errors. • The enc_out are errors that occur outside the frame and usually indicating a bad primitive. To determine if you are having a cable problem, take snapshots of the port errors by using the portErrShow command in increments of 5 to 10 minutes. If you notice the crc_err counter go up, you have a bad or damaged cable, or a bad or damaged device in the path. NOTE ICLs see enc_out errors when ports on one side of the link are disabled. • The disc_c3 errors are discarded class 3 errors, which means that the switch is holding onto the frame longer than the hold time allows. One problem this could be related to is ISL oversubscription. Fabric OS Troubleshooting and Diagnostics Guide 31 53-1002751-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
Fabric OS Troubleshooting and Diagnostics Guide
31
53-1002751-01
Marginal links
3
Only one frame is transmitted and received at any given time. An external cable is not required to
run this test. The port LEDs flicker green rapidly while the test is running.
Table 5
shows the different loopback modes you can use when using
portLoopbackTest
to test a
marginal link.
Troubleshooting a marginal link
1.
Enter the
portErrShow
command.
2.
Determine whether there is a relatively high number of errors (such as CRC errors or ENC_OUT
errors), or if there are a steadily increasing number of errors to confirm a marginal link. Sample
the data every 5 minutes until you see the counters increment.
•
The
frames tx
and
rx
are the number of frames being transmitted and received.
•
The
crc_err
counter are frames with CRC errors. If this counter goes up, then the physical
path should be inspected. Check the cables to and from the switch, patch panel, and other
devices. Check the SFP by swapping it with a known good working SFP.
If you see this issue on an 8 Gbps blade, use the
portCfgFillWord
command to reduce EMI.
•
The
crc_g_eof
counter are frames with CRC errors and a good EOF. The first port detecting
a CRC error marks the frame with a bad EOF and passes the frame on to its destination.
Subsequent ports in the path also detect the CRC error and the crc_err counter
increments on these ports. However, since the first port marked the frame with a bad EOF,
the good EOF counter on the subsequent ports does not increment. The marginal link
associated with the port with an increasing good EOF counter is the marginal link and the
source of the errors.
•
The
enc_out
are errors that occur outside the frame and usually indicating a bad primitive.
To determine if you are having a cable problem, take snapshots of the port errors by using
the
portErrShow
command in increments of 5 to 10 minutes. If you notice the crc_err
counter go up, you have a bad or damaged cable, or a bad or damaged device in the path.
NOTE
ICLs see enc_out errors when ports on one side of the link are disabled.
•
The
disc_c3
errors are discarded class 3 errors, which means that the switch is holding
onto the frame longer than the hold time allows. One problem this could be related to is
ISL oversubscription.
TABLE 5
Loopback modes
Loopback mode
Description
1
Port Loopback (loopback plugs)
2
External Serializer/Deserializer (SerDes) loopback
5
Internal (parallel) loopback (indicates no external equipment)
7
Back-end bypass and port loopback
8
Back-end bypass and SerDes loopback
9
Back-end bypass and internal loopback