Troubleshooting

Using the Event Log for Troubleshooting Switch Problems

N o t e

Using the Event Log for Troubleshooting Switch Problems

The Event Log records operating events in single- or double-line entries and serves as a tool to isolate and troubleshoot problems.

Entries are listed in chronological order, from the oldest to the most recent.

Once the log has received 2000 entries, it discards the oldest message each time a new message is received. The Event Log window contains 14 log entry lines. You can scroll through it to view any part of the log.

The Event Log is erased if power to the switch is interrupted or if you enter the boot system command. The contents of the Event Log are not erased if you:

■Reboot the switch by choosing the Reboot Switch option from the menu interface.

■Enter the reload command from the CLI.

Event Log Entries

As shown in Figure C-6, each Event Log entry is composed of five or six fields, depending on whether numbering is turned on or not:

Severity

Date

Time Event number

System Module

Event Message

 

 

 

 

 

I

08/05/06

10:52:32 00063

ports: port A1 enabled

Figure C-6.Format of an Event Log Entry

Severity is one of the following codes (from highest to lowest severity):

M(major) indicates that a fatal switch error has occurred.

E(error) indicates that an error condition occurred on the switch.

W(warning) indicates that a switch service has behaved unexpectedly.

I(information) provides information on normal switch operation.

D(debug) is reserved for ProCurve internal diagnostic information.

C-22