|
|
|
|
|
The display messages command displays system error and status messages.
Synopsis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Description
The display messages command displays error and status messages that have been logged by the voice system. Various options are provided so that the display can be limited to specific types of messages. If no arguments are supplied to display messages, information is displayed on how to read the messages (the message format) as well as command usage. The messages are written to standard output.
Note:
See Options for display messages command for a description of the options used with this command.
If more messages exist than can be displayed on the screen, you are prompted with
Press the ENTER key to see more, or enter "q" to quit.
If you do not wish to be prompted to press Enter (that is, display all of the messages at once), you may use the -c option.
The priority argument should be used to display messages with specific types of urgencies. Two groups of priorities exist: alarms and events. Alarms are messages that have been reported as *C (critical), ** (major), or * (minor) priorities. Events are all the remaining messages that have no priority, such as status messages. For example, to display the last 25 alarms, type the following:
display messages priority alarms 25
You can also display specific priorities using the priority option. You can specify either the name of the priority or its symbol (for example, critical or *C). To display all critical messages, type the following:
display messages priority critical all
Note:
You should use the priority alarm argument when alarms are needed, otherwise use the priority events argument. The priority argument must be used with this command.
Combinations of priorities can also be displayed by listing each priority separated with a comma. For example, to display the last 100 alarms messages, type the following:
display messages priority `*C',`**',`*'
where *C, **, and * must be enclosed in quotes.
All messages are displayed with two or three lines of information. Messages are separated by a blank line to ease viewing. The table below lists the system message formats along with definitions and examples. Each message displayed conforms to the format shown as follows:
PR DAY MON DD HH:MM:SS ZZZ YYYY SOURCE (Continuation if necessary.)
TTTTTTTT YY UU NUM TEXT...
TEXT
blank line
The formats are defined in the following table:
Format |
Definition |
Examples |
PR |
Priority |
*C (Critical), ** (Major), * (Minor), ""(Event) |
DAY |
Day |
Sun - Sat |
MON DD |
Date |
Jan 1 - Dec 31 |
HH:MM:SS |
Time |
00:00:00 - 11:59:59 |
ZZZ |
Time Zone |
EST, EDT, CST... |
YYYY |
Year |
1992,... |
SOURCE |
Source |
TSM, VROP,... |
TTTTTTTT |
8 char Msg ID (Tag) |
TWIP2104,... |
YY |
FRU Type |
NM, VO, IP |
UU |
Unit Type |
CA (Card) or CH (Channel) or – if N/A |
NUM |
Unit Number |
000 to 999 or –- if N/A |
TEXT |
Message Text |
Varies with message (see example below); can be more than one line long. |
Example
The following example is representative of the output from typing display messages card all:
MESSAGE LOG REPORT
Pr Time Source
-- –-- –----
Mon Sep 30 12:16:22 2002 MTC
MTC002 NM CA 2 (MTC_STATE_EVENT) Changed state from INSERV to FOOS.
Mon Sep 30 12:16:22 2002 MTC
MTC002 IP CA 11 (MTC_STATE_EVENT) Changed state from INSERV to FOOS.
Mon Sep 30 12:16:24 2002 VOIP
VOIP008 VO CA 11 (VOIP_OAMREQUEST_ERROR) Unable to process OA&M request. Reason: Failed to read OA&M message.
Mon Sep 30 12:16:24 2002 VOIP
VOIP012 VO CA 11 (VOIP_ERROR) Error: DevPoll::Poll ioctl error
numReady=-1 errno=4
Press the ENTER key to see more, or enter q to quit
See also
