The Aux Data field may be 0 or the return code from a bad software call, and the following examples in no way exhaust the possibilities. Often, two errors are logged at the same time for each problem.
Table 1: SYSTEM error log entries
Error type |
Aux Data |
Associated Test |
Alarm Level |
On or Off board |
Command to resolve the error |
0 (a) |
0 |
Any |
Any |
Any |
|
8 (b) |
0 |
|
|
|
|
9 (c) |
Any |
|
|
|
|
10 (d) |
Any |
|
|
|
|
21 (e) |
|
|
|
|
|
355 (f) |
Any |
|
|
|
|
356 (g) |
Any |
|
|
|
|
601 (h) |
|
|
|
|
|
602 (i) |
|
|
|
|
|
603 (j) |
|
|
|
|
|
Note:
Error type 0: run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures.
Error type 8: a System Restart Level 3 was requested.
Error type 9: a System Restart Level 2 was requested. This can happen due to a loss of tones due to a faulty Tone-Clock circuit pack.
Error type 10: a System Restart Level 1 was requested.
Error type 21: a process trapped.
Error type 355: a Restart Level 2 occurred due to a power loss.
Error type 356: a Restart Level 2 occurred due to a tone clock loss.
Error type 601: an error occurred during initialization.
Error type 602: an error occurred while loading translations and the system requested a Restart Level 3.
Error type 603: a process was reset.
