Avaya S8700 Series, Maintenance Manual

Page: 368 / 2618

Maintenance Commands
555-233-143 7-112 Issue 1 May 2002
System Reboots and the Error and Alarm Logs
The Avaya Call Processing (ACP) software attempts to save the error and alarm
logs to the disk 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.
Whenever the ACP software reloads, the error log is restored from the disk. Since
the logs are saved to the disk, the versions restored at reload time may not be
current. This occurs when either:
— The attempt to save at reload did not succeed.
— The server that is active coming out of reload 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 server that became active with the
reboot. When looking at errors that precede the last reload, look for indications
preceding the reload to determine whether the logs restored at reboot are
complete.
System resets less severe than a reload rarely affect the error and alarm logs.
NOTE:
If there are SYSTEM errors in the error log, use display initcauses to
obtain additional information. Information that could not be logged during a
system reset may be found here.
Parameters
For more information, see the section: ‘‘Common Input Parameters’’ .
high-resolution This option specifies an error report with high resolution time stamps for the first
occurrence and last occurrence of the error. The high resolution time stamp
includes seconds and a sequence count within a second. The sequence count
starts over for each second.