Loading...
Loading...
Loopback failures are reported on already failed ports. After initial port hardware failures, such as: %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/48 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/47 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/46 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/45 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/44 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/43 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/42 is down (Hardware Failure) %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1%$ Interface fc8/41 is down (Hardware Failure) the diagnostic test continues to run and some time later the following type of syslogs messages are logged: %DIAG_PORT_LB-2-INT_PORT_LOOPBACK_TEST_FAIL: Module:8 Test:Internal PortLoopback failed 10 consecutive times. Faulty module:Module 8 affected ports:41-44 Error:Packets dropped on FCMAC %DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL: Module:8 Test:SnakeLoopback failed 10 consecutive times. Faulty module: affected ports:41-44 Error:Packets dropped on FCMAC %DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL: Module:8 Test:SnakeLoopback failed 10 consecutive times. Faulty module: affected ports:1-40,45-48 Error:Test Failed, Could not identify the Faulty Device
This issue only applies to ports that have already failed and been set to 'hardware failure' state.
Replace the failed module.
The %DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL messages are superflous.
Diagnostic tests are no longer run on already failed ports.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.