Lucent Technologies Stinger, Administration Manual

Page: 352 / 374

B-2 Stinger® Administration Guide
Stinger Log Messages
Definitions of fatal errors
OPERATOR RESET:Index: 99 Revision:9.3-170 first-controller (stngrcm2)
Date: 04/30/2002. Time: 14:53:02
Reset from 135.140.144.124, user profile admin.
Clearing the fatal error log
Each entry shows the system software version, the slot on which the error occurred,
and the date and time at which the error occurred. To clear the log, enter the
clr-
history command:
admin> clr-history
Fatal and warning messages have the format shown in the following example:
Warning: Index: 171 Revision: 8.0.0 Shelf 1 (stngrcmb)
Date: 06/14/1999. Time: 16:03:33
Location: 81026460 81069380 81024b38 81024af4 00000000 00000000
The first line indicates the type of error (fatal or warning), the index number of the
error, the software revision number, the shelf and slot on which the error occurred,
and the software load. The fatal log from older software versions display shelf 0.
The second line shows the date and time of the error.
The third line displays the top six program counter addresses from the execution
stack active at the time of the crash.
Definitions of fatal errors
Following are definitions, by index number, of the fatal errors that the Stinger unit
can report. If you experience a fatal error, contact Lucent OnLine Customer Support
at
http://www.lucent.com/support .
Index Definition
1 Assert invoked during program execution
An Assert has been placed in the code. This problem can be either
hardware related or software related.
2 Out of memory during memory allocation
This is an out-of-memory condition, sometimes termed a memory leak.
3 Bad profile (T1 DSL related)
4 Switch type bad
5 LIF error
6 LCD error
7 ISAC (BRI) timeout
BRI physical layer timeout.
8 Processor exception
A processor-exception error caused the reset.
9 Invalid task switch (EXEC)