Emulex Ethernet device tests

Use this information to resolve Emulex Ethernet device errors.

Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
  • See Parts listing to determine which components are consumable, structural, or CRU parts.
  • If an action step is preceded by "(Trained technician only)," that step must be performed only by a trained technician.
Error code Description Action
516-000-000 Passed the LED beaconing test. N/A
516-040-001 Failed the LED beaconing test.
  1. Make sure that the component firmware or driver is installed correctly, upgrade if necessary; then, rerun the test.
  2. Make sure the OneCommand Manager daemon is running.
  3. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
  4. If the failure remains, reinstall the device driver and OneCommand Manager.
516-040-064 Aborted the test because the device was busy.
  1. Make sure that no critical operation (for example, firmware download) is already running.
  2. Wait until the critical operation is complete; then, run the test again.
  3. If the failure remains, restart the OneCommand Manager daemon.
  4. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
516-000-000 Passed the loopback test at the MAC layer. N/A
516-040-001 Failed the loopback test at the MAC layer.
  1. Make sure that the component firmware or driver is installed correctly, upgrade if necessary; then, rerun the test.
  2. Make sure the OneCommand Manager daemon is running.
  3. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
  4. If the failure remains, reinstall the device driver and OneCommand Manager.
516-040-064 Aborted the test because the device was busy.
  1. Make sure that no critical operation (for example, firmware download) is already running.
  2. Wait until the critical operation is complete; then, run the test again.
  3. If the failure remains, restart the OneCommand Manager daemon.
  4. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
516-000-000 Passed the loopback test at the physical layer. N/A
516-040-001 Failed the loopback test at the physical layer.
  1. Make sure that the component firmware or driver is installed correctly, upgrade if necessary; then, rerun the test.
  2. Make sure the OneCommand Manager daemon is running.
  3. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
  4. If the failure remains, reinstall the device driver and OneCommand Manager.
516-040-064 Aborted the test because the device was busy.
  1. Make sure that no critical operation (for example, firmware download) is already running.
  2. Wait until the critical operation is complete; then, run the test again.
  3. If the failure remains, restart the OneCommand Manager daemon.
  4. Turn off and restart the blade server; then, rerun the test. See Turning off the blade server and Turning on the blade server.
Parent topic: Diagnostics