Using The Event Log To Identify Problem Sources - ProCurve 6200yl Management And Configuration Manual

Troubleshooting

Using the Event Log To Identify Problem Sources

Severity
I
C-26
Using the Event Log To Identify Problem
Sources
The Event Log records operating events as single-line entries listed in chrono-
logical order, and serves as a tool for isolating problems. Each Event Log entry
is composed of five or six fields, depending on whether numbering is turned
on or not:
Date Time
08/05/06 10:52:32 00063
Severity is one of the following codes:
I
(information) indicates routine events.
W (warning) indicates that a service has behaved unexpectedly.
M (major) indicates that a severe switch error has occurred.
D (debug) reserved for ProCurve internal diagnostic information.
Date is the date in mm/dd/yy format that the entry was placed in the log.
Time is the time in hh:mm:ss format that the entry was placed in the log.
Event Number is the number assigned to the event. This feature can be turned
on with the log-number command.
System Module is the internal module (such as "ports" for port manager) that
generated the log entry. If VLANs are configured, then a VLAN name also
appears for an event that is specific to an individual VLAN. Table C-1 on page
C-27 lists the individual modules.
Event Message is a brief description of the operating event.
The Event Log holds up to 1000 lines in chronological order, from the oldest
to the newest. Each line consists of one complete event message. Once the
log has received 1000 entries, it discards the current oldest line each time a
new line is received. The Event Log window contains 14 log entry lines and
can be positioned to any location in the log.
Event number System Module
ports: port A1 enabled
Event Message