Users Guide

19–Troubleshooting
Hardware Diagnostics
Doc No. BC0054508-00 Rev. R
January 21, 2021 Page 281 Copyright © 2021 Marvell
QCS CLI and QCC GUI Diagnostic Tests Failures
If any of the following tests fail while running the diagnostic tests from QCS CLI or
QCC GUI, 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
 Te s t L E D
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.
QCS CLI and QCC GUI Network Test Failures
Typically, QCS CLI or QCC GUI network test failures are the result of a
configuration problem on the network or with the IP addresses. The following
steps are commonly performed 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.
3. Replace the cable that is attached to the NIC or LOM.
4. Verify that the IP address is assigned correctly by issuing the command
ipconfig or by checking the OS IP assigning tool.
5. Verify that the IP address is correct for the network to which the adapter or
adapters are connected.