Lucent Technologies Stinger, Administration Manual

Page: 354 / 374

B-4 Stinger® Administration Guide
Stinger Log Messages
Definitions of warning messages
Definitions of warning messages
Warnings are not the results of reset conditions. Most are detected problems from
which the Stinger unit typically recovers fully. Following are the definitions, by index
number, of the warnings the Stinger unit can report. Warning messages, by
themselves, are not necessarily cause for concern. They are used by development
engineers to determine the cause of fatal errors.
Contact Lucent OnLine Customer Support at http://www.lucent.com/support if
warning messages are accompanied by fatal errors.
39 No priority 2 task
This error occurs if the Stinger has not run a priority 2 task in the last
minute. Tasks in the Stinger are assigned priorities. Because the main
routing task runs at priority 2, this error means that Stinger operation has
been suspended for 1 minute.
40 Protection fault
41 Memory shortage
60 SNMP-related error
60 SNMP-related error
60 SNMP-related error
93
Failure of LIM to respond to control module watchdog message
A Stinger control module continually monitors the status of installed
LIMs by sending a watchdog message to LIMs. Fatal error FE93 occurs
when a LIM fails to respond to three watchdog messages from the control
module.
99 Operator reset
This reset is logged immediately before the Stinger goes down.
Instead of a standard stack backtrace, the message includes the active
security-profile index. 0 (zero) indicates an unknown security profile. On
the Stinger, the Default profile is number 1, and the Full Access profile is
number 9.
100 System up
As a complement to entry 99, this entry is logged as the Stinger is coming
up. For a normal, manual reset, you normally see a fatal error 99
followed by a fatal error 100.
Index Definition
Index Definition
101 Buffer already in use
102 Buffer belongs to wrong pool
103 Buffer belongs to wrong heap