Maintenance 183
Error message handling
The ICB provides enhanced message handling that includes the following:
•Fixed message format and unique message codes.
•Categorization of messages by severity.
•Message analysis tool that provides
•Message filtering based on such items as severity and firmware component.
•Advanced troubleshooting.
Note: Since the
Error messages format
The general format of error messages is as follows:
<serial number> <severity> <error code> <timestamp> <error text>
Table 48 describes the error message fields.
Table 48
Error message field formats
Field | Description |
|
|
<serial number> | Four digits that provide a sequence for the messages. It starts at 0001 at |
| |
| when it reaches 9999. |
|
|
<severity> | 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 |
| 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. |
|
|
Nortel Integrated Conference Bridge Service Implementation Guide
