Lucent Technologies Release 7 User Manual
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-762
ERR-LOG (Error Log)
9
ERR-LOG (Error Log)
The ERR-LOG maintenance object (MO) is responsible for the sanity of the Alarm
Log, the Hardware Error Log, and the Software Error Log. If an inconsistency is
detected in any one of these logs, all logs will be re-initialized and a hardware
error will be logged against ERR-LOG indicating the time of inconsistency. There
are no tests and no alarms for the Error Log MO. This MO exists solely for the
purpose of allowing errors to be logged against it.
Log, the Hardware Error Log, and the Software Error Log. If an inconsistency is
detected in any one of these logs, all logs will be re-initialized and a hardware
error will be logged against ERR-LOG indicating the time of inconsistency. There
are no tests and no alarms for the Error Log MO. This MO exists solely for the
purpose of allowing errors to be logged against it.
Hardware Error Log Entries
Notes:
a. Indicates that an inconsistency was detected in either the Alarm Log, the
Hardware Error Log, or the Software Error Log. The system attempts to
recover the logs but, depending on the extent of the corruption, some or
all entries in the logs may be lost. Any alarms that were active at the time
of this error have been cleared. There is no associated test for this error.
recover the logs but, depending on the extent of the corruption, some or
all entries in the logs may be lost. Any alarms that were active at the time
of this error have been cleared. There is no associated test for this error.
The Aux Data value indicates when the inconsistency was found:
MO Name (in
Alarm Log)
Alarm Level
Initial Command to Run
Full Name of MO
ERR-LOG
none
none
Error Log
Error
Type
Aux Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
510 (a)
See below
none
none
none
none
0
During a periodic audit of the Error Log
1
After an extended reboot
2
After a reboot
4
After a Level-3 System Reset (COLD_1)
8
After a Level-2 System Reset (COLD_2)
16
After a Level-1 System Reset (Warm Start)
100
After an internal software audit
2500
After a single-process (MDM) restart