Dell Brocade 1020 Brocade Adapters Troubleshooting Guide - Page 56

Network interface problems (CNA or NIC), Ethernet loopback test problems

Page 56 highlights

2 Network interface problems (CNA or NIC) Network interface problems (CNA or NIC) Use the following information to isolate problems that are more specific to the function of a CNA or Fabric Adapter port configured in CNA or NIC mode. For additional information on troubleshooting problems on mezzanine and expansion card adapters, refer to "Troubleshooting mezzanine card problems" on page 55. NOTE Switch command examples used in this section are for the Brocade 8000 Switch. Ethernet loopback test problems Errors occur during BCU Ethernet loopback tests. 1. Symptom: Loopback test returns "Check link/cable or SFP" error when executed with -t cable option (stand-up adapters only). Possible Cause: Loopback cable not inserted in tested port. Action: Verify that loopback cable is securely inserted in the port that you are testing. 2. Symptom: Loopback test returns a "port not disabled" error. Possible Cause: Port is enabled. Action: Disable the port using the port --disable BCU command before running loopback test. 3. Symptom: Loopback test returns a "port not disabled" error. The error.displays even after disabling the port. Possible Cause: Network load balancing service is enabled. This will cause the adapter to disable and enable, and the previously configured state (port disable) is lost. Action: Disable network load balancing and retest. 4. Symptom: The loopback test returns "Device busy - Retry operation" or "diag busy." Possible Cause: Other users or sessions are running another instance of loopback tests. Action: Check if instances of this diagnostic are running using ps -ef for Linux and VMware, and Task Manager for Windows systems. Action: If instances are still running, wait a few minutes, then again check if the tests done using the ps -ef command or Task Manager. 5. Symptom: The loopback test returns "Missing frame check and replace SFP/cable" (stand up cards only). Possible Cause: The loopback cable was pulled during the test and the test is run in external mode (not serdes mode). Action: Restart the test with the cable connected. 32 Brocade Adapters Troubleshooting Guide 53-1002145-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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172

32
Brocade Adapters Troubleshooting Guide
53-1002145-01
Network interface problems (CNA or NIC)
2
Network interface problems (CNA or NIC)
Use the following information to isolate problems that are more specific to the function of a CNA or
Fabric Adapter port configured in CNA or NIC mode. For additional information on troubleshooting
problems on mezzanine and expansion card adapters, refer to
“Troubleshooting mezzanine card
problems”
on page 55.
NOTE
Switch command examples used in this section are for the Brocade 8000 Switch.
Ethernet loopback test problems
Errors occur during BCU Ethernet loopback tests.
1.
Symptom:
Loopback test returns “Check link/cable or SFP” error when executed with
-t cable
option (stand-up adapters only).
Possible Cause:
Loopback cable not inserted in tested port.
Action:
Verify that loopback cable is securely inserted in the port that you are testing.
2.
Symptom:
Loopback test returns a “port not disabled” error.
Possible Cause:
Port is enabled.
Action:
Disable the port using the
port --disable
BCU command before running loopback test.
3.
Symptom:
Loopback test returns a “port not disabled” error. The error.displays even after
disabling the port.
Possible Cause:
Network load balancing service is enabled. This will cause the adapter to
disable and enable, and the previously configured state (port disable) is lost.
Action:
Disable network load balancing and retest.
4.
Symptom:
The loopback test returns “Device busy - Retry operation” or “diag busy.”
Possible Cause:
Other users or sessions are running another instance of loopback tests.
Action:
Check if instances of this diagnostic are running using
ps -ef
for Linux and VMware, and
Task Manager for Windows systems.
Action:
If instances are still running, wait a few minutes, then again check if the tests done
using the
ps -ef
command or Task Manager.
5.
Symptom:
The loopback test returns “Missing frame check and replace SFP/cable” (stand up
cards only).
Possible Cause:
The loopback cable was pulled during the test and the test is run in external
mode (not serdes mode).
Action:
Restart the test with the cable connected.