Chapter 40: Diagnostics
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1029
11:42:14 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=23: testID=4.7:
testName=BCM1480 / MCC Loopback Test: timestamp=: result=Passed
11:46:07 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=36: testID=3.12:
testName=BCM5461 - Phy 0 Function Test: timestamp=: result=Passed
11:46:17 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=37: testID=3.7:
testName=BCM5461 - Phy 1 Register Test: timestamp=: result=Passed
11:46:28 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=38: testID=3.12:
testName=BCM5461 - Phy 1 Function Test: timestamp=: result=Passed
11:46:38 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=39: testID=3.7:
testName=BCM5461 - Phy 4 Register Test: timestamp=: result=Passed
11:46:48 19 info: <DIAG> DiagnosticControllerCard: Test Done: testCnt=40: testID=3.12:
testName=BCM5461 - Phy 4 Function Test: timestamp=: result=Passed
11:46:58 19 info: <DIAG> DiagnosticControllerCard: Cmd Done: cmd=configure diag 5 : Timestamp=THU
APR 14 11:46:58 2008
11:46:58 19 info: <DIAG> Slot 11: Diagnostic test completed, status = Passed
11:46:58 19 notc: CLI command:(No Auth):10.5.7.166:configure diag 5
Diagnostic Failure and Recovery
Diagnostic failures generate error reports that isolate faults, and necessitate user action to expedite recovery.
Diagnostic Failure
When a module fails diagnostics, an error report is printed to the CLI console and to the log.
Error reports are similar to what is shown in the following examples:
------------------------------
Generating Function: BlockMemDiag::memTestAllBits
Result :Failed
Result Note :Memory integrity failure
Expected Result :0x29
Actual Result :0x00
XOR Exp vs Actual :0x29
Fault Location :0x0001.1e00; Physical Address: 0x0000.23c0
------------------------------
Slot 17: Test #9 - FLAK Memory Test (ID 2.22) Failed
Slot 17: Diagnostic test completed, status = Failed