61200305L1-1F © 2002 ADTRAN, Inc. 377
SYSTEM EVENT LOGGING
The ATLAS 550 Event Log is used to log various message types at settable threshold levels. This section
describes the entries that may be logged by the system event log.The Event Log’s CATEGORY is
particularly important – this is the minimum severity level that must be set in order that the event be
logged.
The Event Log is a useful tool for troubleshooting switchboard (or call connection) activities including the
viewing of digits received, digits transferred, and ISDN Messages. Since most of the events discussed in
the following tables are used primarily during troubleshooting, they should be turned off in normal
operation.
CONTENTS
Setting the Event Log Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Viewing the Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
ISDN Cause Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Cause Code Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
TABLES
Table 1. System Controller Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Table 2. Switchboard Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374
Table 3. Nx 56/64 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Table 4. T1 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375
Table 5. Ethernet Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Table 6. ISDN Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Table 7. Circuit Backup Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378
Table 8. DP Outgoing Signaling Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Table 9. Modem Management Module Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Table 10. ISDN Cause Code Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Table 11. Cause Code Log Entry Location Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Table 12. ISDN L2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381
Table 13. ISDN Call Control Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Table 14. Source: ISDN Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Use caution when changing CATEGORY values from their default levels. If too many
sources have their CATEGORY values set too low, the number of messages being logged in
a given period can be very large. If too many messages are being logged too rapidly,
system performance can be adversely affected.