Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme 57XX User Guide - Page 130

Troubleshooting: Broadcom NetXtreme 57XX User Guide

Get Dell Broadcom NetXtreme Family of Adapters PDF manuals and user guides View all Dell Broadcom NetXtreme Family of Adapters manuals
Add to My Manuals
Save this manual to your list of manuals

Page 130 highlights

Back to Contents Page Troubleshooting: Broadcom NetXtreme 57XX User Guide Hardware Diagnostics Troubleshooting Checklist Checking for Network Link and Activity Checking if Current Drivers are Loaded Running a Cable Length Test Testing Network Connectivity Software Problems and Solutions Hardware Diagnostics Loopback diagnostic tests are available for testing the adapter hardware. These tests provide access to the adapter internal/external diagnostics, where packet information is transmitted across the physical link (for instructions and information on running tests in an MS-DOS environment, see User Diagnostics. For Windows environments, see Running Diagnostic Tests). BACS 3 Diagnostic Tests Failures If any of the following tests fail while running the diagnostic tests from the Running Diagnostic Tests tab in BACS 3, this may indicate a hardware issue with the NIC or LOM that is installed in the system. Control Registers MII Registers EEPROM Internal Memory On-Chip CPU Interrupt Loopback - MAC Loopback - PHY Test LED Below are troubleshooting steps that may help correct the failure. 1. Remove the failing device and reseat it in the slot, ensuring the card is firmly seated in the slot from front to back. 2. Rerun the test. 3. If the card still fails, replace it with a different card of the same model and run the test. If the test passes on the known good card, contact your hardware vendor for assistance on the failing device. 4. Power down the machine, remove AC power from the machine, and then reboot the system. 5. Remove and re-install the diagnostic software. 6. Contact your hardware vendor. BACS 3 Network Test Failures Typically, the BACS 3 Testing the Network failures are the result of a configuration problem on the network or with the IP addresses. Below are common steps when troubleshooting the network. 1. Verify that the cable is attached and you have proper link. 2. Verify that the drivers are loaded and enabled.

  • 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
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
Back to Contents Page
Troubleshooting: Broadcom NetXtreme 57XX User Guide
Hardware Diagnostics
Troubleshooting Checklist
Checking for Network Link and Activity
Checking if Current Drivers are Loaded
Running a Cable Length Test
Testing Network Connectivity
Software Problems and Solutions
Hardware Diagnostics
Loopback diagnostic tests are available for testing the adapter hardware. These tests provide access to the adapter
internal/external diagnostics, where packet information is transmitted across the physical link (for instructions and information
on running tests in an MS-DOS environment, see
User Diagnostics
. For Windows environments, see
Running Diagnostic
Tests
).
BACS 3 Diagnostic Tests Failures
If any of the following tests fail while running the diagnostic tests from the
Running Diagnostic Tests
tab in BACS 3, this may
indicate a hardware issue with the NIC or LOM that is installed in the system.
Control Registers
MII Registers
EEPROM
Internal Memory
On-Chip CPU
Interrupt
Loopback - MAC
Loopback - PHY
Test LED
Below are troubleshooting steps that may help correct the failure.
1. Remove the failing device and reseat it in the slot, ensuring the card is firmly seated in the slot from front to back.
2. Rerun the test.
3. If the card still fails, replace it with a different card of the same model and run the test. If the test passes on the
known good card, contact your hardware vendor for assistance on the failing device.
4. Power down the machine, remove AC power from the machine, and then reboot the system.
5. Remove and re-install the diagnostic software.
6. Contact your hardware vendor.
BACS 3 Network Test Failures
Typically, the BACS 3
Testing the Network
failures are the result of a configuration problem on the network or with the IP
addresses. Below are common steps when troubleshooting the network.
1. Verify that the cable is attached and you have proper link.
2. Verify that the drivers are loaded and enabled.