Filter
Top Products
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-113display errors
8
Examples
display errors
display errors print
display errors schedule
display errors high-resolution print
Description
The display errors command brings up an error report. This screen allows the
technician various different options to select which errors will be displayed on the
hardware error report. There are no query parameters entered on the command
line. Those type of parameters are selected on the error report form instead.
Errors can result from in-line firmware errors, periodic tests, failures detected
while executing a test command, software inconsistency, or a data audit
discrepancy.
System Reboots and the Error and Alarm Logs
The system attempts to save the error and alarm logs to the memory card, on the
active
SPE when any of the following events take place:
— The save translation command is executed.
— Translations are saved as part of scheduled maintenance (as
administered on the maintenance-related system parameters form).
— A demand or software-escalated system reboot takes place.
— The PPN is about to lose all power after having been on battery backup.
Conditions such as unavailability of the MSS can prevent this attempt from
succeeding.
Whenever the system reboots, the error log is restored from the disk on the SPE
that becomes active with the reboot. Since the logs are saved to the disk on the
SPE that was active before the reboot, the versions restored at reboot time may
not be current. This occurs when either:
— The attempt to save at reboot did not succeed.
— The SPE that is active coming out of the reboot is not the same one to
which the logs were last saved.
In such a case, the logs will not show the errors and alarms that have been
logged since the last time a save was made to the SPE that became active with
the reboot. When looking at errors that precede the last reboot, look for
indications preceding the reboot to determine whether the logs restored at
reboot are complete.
System resets less severe than a reboot rarely affect the error and alarm logs.