display errors

Last Updated : Aug 14, 2023 |
Use display errors to select the errors that appear on the hardware error report.
Errors can result from in-line firmware errors, periodic tests, failures detected while executing a test command, software inconsistency, or a data audit discrepancy. The error log is restricted in size. A new entry overwrites the oldest unalarmed entry. The overwritten entry must be at least six minutes old, or the new entry is dropped.
Prolog information
Metadata
Keywords:

Syntax

display errors [ high-resolution ] [ schedule ] 
high-resolution
Include high resolution time stamps for the first occurrence and last occurrence of the error. This shows seconds and a sequence count within a second. The sequence count starts over for each second.
See Error Log Report High Resolution.
schedule
Specify a time to run the command.

Help messages

  • When the first page of a multiple page list of alarms/errors or after the Prev Page key is pressed:
    Press CANCEL to abort or NEXT PAGE for next page
  • After the Next Page key is pressed and there are more pages of alarms/errors to be displayed:
    Press CANCEL to abort, NEXT PAGE for next page, PREV PAGE for previous page.
  • After the Next Page key is pressed and there are no more alarms/errors to be displayed:
    Press CANCEL to abort, NEXT PAGE to complete, PREV PAGE for previous page.

System Reboots and Error and Alarm logs

Avaya Aura® Communication Manager 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 screen).
  • A demand or software-escalated system reboot takes place.
Whenever the Communication Manager 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 for more information. Information that could not be logged during a system reset may be found here.

display errors input field descriptions

The display errors input screen specifies which errors display on the report. When every selection has been made, press ENTER. If no selections are made or if the schedule option is specified, the system displays every error from the last day that are associated with active alarms.
Field
Description
Error Type
The report can be restricted to specific error codes. Default is every error.
Error List
The report can be restricted to errors from one of three lists described below: active-alarms, errors, or cleared-errors. Default is active-alarms.
Interval
Specifies error records for the last month, hour, day, week, or all errors (m, h, d, w, a). The default is all.
From
Specifies error records starting from the time specified by (month/day/hour/minute). If no From date is entered, errors from the earliest record in the log are displayed.
To
Specifies every error record up to the time specified by mm/dd/hh/mm. If no To date is entered, every error up to the current date appears.
Equipment Type
To limit the report to a specific group of components, enter the location of a type of equipment in one of the following fields. If no entry is made, errors for the entire system are displayed.
  • Gateway: Enter the gateway number.
  • Board: Enter the media gateway slot address of the media module (for example, 41v4). If the cabinet number is omitted, it defaults to 1.
  • Port: Enter the media gateway slot circuit address of the media module (for example, 1v408).
  • Category: Enter a category to restrict the report to maintenance objects in a specific category. The HELP key displays a list of categories.
  • Extension: Enter the extension number of a port.
  • Trunk (group/member): Enter a trunk-group number, or a trunk-group and member number separated by a slash (for example, 78 or 78/1).

display errors output field descriptions

Field
Description
Port
The physical location of the alarmed object.
  • For media module based MOs, the location is media-gateway-[slot]-[circuit].
  • For MG based objects, such as TDM-BUS, the location displays as 1v4.
Maintenance Name
The name of the MO as it appears in the alarm and error logs.
The alternate name depends upon the type of the object. For example:
  • Station MO — alternate name is nnnnn (extension)
  • Trunk MO — alternate name is nn/n (trunk-group number/member number)
  • Personal CO line MO — alternate name is P/xx (P/personal CO line group number)
Error Type
Numerical error code that identifies the type of problem. The meanings of these codes are explained under the name of the MO in the Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.
Aux Data
Additional numerical information about the error type. Only the most recent auxiliary data for each error type appears.
First line: Month, day, hour, and minute (and second, if the high-resolution command-line option is used) that the error was first recorded.
Second line: The month, day, hour, and minute (and second, if the high-resolution command-line option is used) of the most recent error. If the system is unable to retrieve the time of day when the error occurred, a dummy date will be stamped in the log so as to distinguish it from reliable data. It appears as 00/00/01:07.
Seq Cnt
Sequence Count. These numbers give the order in which the errors were logged. Each sequence covers a period of one second. Sequence numbers are assigned to the first and last occurrences of a given error within the one second period given in the time stamp. There may be gaps in the sequence numbers within a given second because the last occurrence of an error may replace an existing entry and because sequence numbers are also assigned to software events not shown in the hardware error log. This information appears when the high-resolution option is specified on the command line.
Err Cnt
The total number of times that the error type has occurred. The maximum entry is 999.
Err Rt
Average hourly rate at which the error has occurred from the first occurrence to the present. The maximum entry is 999.
Rt/Hr
An approximation of the rate at which this error occurred in the last hour. The maximum entry displayed is 999.
Al St
Alarm Status. A character indicating the status of this MO in the error and alarm logs.
  • a — active alarm entry
  • r — resolved alarm entry
  • c — resolved alarm entry due to long clear option of test
  • s — resolved alarm entry due to a software-requested (non-demand) system restart
  • t — resolved alarm entry due to a technician-requested system restart
  • n — not alarmed
Ac
y/n — Whether the maintenance object is still under active consideration by the maintenance subsystem.