Quick Reference Guide

System Logs | 105

Using the Persistent Event Log

In addition to the optional buffered System log described above, the switch maintains a persistent Event

servers. The log does not require configuration.

The purpose of the Event log is to save system exception information to persistent memory for analysis by

Dell Force10 Engineering. Error messages start with “ERROR”, while event messages start with

“EVENT”, as shown in Figure 6-72.

Execute the

show eventlog command (with no keyword), as shown in Figure 6-72, below.

Figure 6-72. Using the show eventlog Command

Because the show eventlog command monitors a persistent log database, it is important to correlate any

ERROR entries with the timeline using the time designator. The Time column in the output is the system

up-time, shown by number of days (“d”), hours (“h”), minutes (“m”), and seconds (“s”).

Although the structure of the System log and Event log are different, both logs contain the same software

file, line, and task information. For example, a reboot is a common event, indicated in each log by

“bootos.c”. All “bootos.c” entries should be between 8 to 15 seconds after the system restarts, which you

can see in the Time column in Figure 6-72. The typical log entry following a “bootos.c” entry is either:

• “ERROR> unitmgr.c”: Indicates the system rebooted due to a user command.

• “ERROR> reset603.c”: Indicates the system rebooted due to a program error interrupt.

• “ERROR> broad_hpc_drv.c”: Typically indicates failed driver calls

Note: You can copy the Event log from the switch to a TFTP server. See Downloading and

Uploading Files on page 44 in the Getting Started chapter.

Note: The show eventlog report is also included in the output of show tech-support.

Force10 #show eventlog

Event Log

---------

Time

File Line TaskID Code d h m s

EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 12

ERROR> unitmgr.c 3325 0E41CD38 00000000 3 6 8 34

EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 9

ERROR> unitmgr.c 3339 0E22B298 00000000 14 22 9 4

EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 11

ERROR> reset603.c 177 0D6007A8 09A60110 3 13 31 59

EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 8