Nortel Meridian Meridian 1 Implementation Manual page 155

Error messages format
The general format of error messages is as follows:
Table 43 describes the error message fields.
Table 43
Error message field formats
Field
<serial number>
<severity>
<error code>
<timestamp>
<error text>
Meridian Integrated Conference Bridge
<serial number> <severity> <error code> <timestamp> <error text>
Description
Four digits that provide a sequence for the messages. It starts at 0001 at
power-up and increments by one for each message issued. It wraps around
when it reaches 9999.
Severity levels are as follows:
CRITICAL – indicates immediate corrective action is required (for example, the
application cannot continue and/or the card must be restarted).
MAJOR – indicates urgent corrective action is required (for example, the BUI
doesn't work, but call processing continues to operate).
MINOR – indicates the existence of a fault condition; corrective action should be
taken to prevent a more serious fault. For example, a problem affecting a single
channel is minor, so long as the system is still fully operational.
WARNING – indicates a low level failure that almost does not impact a customer.
No corrective action is required, because auto-recovery is performed. Frequent
appearance can indicate a more serious problem.
INFO – shows normal operational event notifications (for example, state
changes in hardware or software; time and date changes).
DEBUG – for use by designers only.
Unique identifier of the event being reported. It is made up of the following two
parts:
• a string of up to six letters indicating the firmware component that originates
the message.
• three decimal digits comprising the error number within this component
Date and time of the message in the format MM-DD hh:mm:ss:ff, where:
MM = month number.
DD = day of the month.
hh = hour (in 24-hour format).
mm = minutes.
ss = seconds.
fff = fraction of second, in milliseconds.
Short description of the problem or event, and related parameters (for example,
port number).
Page 155 of 208
Service Implementation Guide