Using The Persistent Event Log - Dell Force10 S2410-01-10GE-24P Configuration Manual

Using the Persistent Event Log

In addition to the optional buffered System log described above, the switch maintains a persistent Event
log in NVRAM. Persistent logging is always enabled to memory and disabled to the console or to syslog
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
Execute the
show eventlog
Figure 6-72. Using the show eventlog Command
Force10 #show eventlog
Event Log
---------
File
EVENT> bootos.c
ERROR> unitmgr.c
EVENT> bootos.c
ERROR> unitmgr.c
EVENT> bootos.c
EVENT> bootos.c
ERROR> reset603.c
EVENT> bootos.c
Because the show eventlog
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
• "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
Uploading Files on page 44
Note: The show eventlog report is also included in the output of show tech-support.
Figure 6-72.
command (with no keyword), as shown in
Line TaskID
434 0FFFFE00 AAAAAAAA
3325 0E41CD38 00000000
434 0FFFFE00 AAAAAAAA
3339 0E22B298 00000000
434 0FFFFE00 AAAAAAAA
434 0FFFFE00 AAAAAAAA
177 0D6007A8 09A60110
434 0FFFFE00 AAAAAAAA
command monitors a persistent log database, it is important to correlate any
Figure 6-72. The typical log entry following a "bootos.c" entry is either:
in the Getting Started chapter.
Figure 6-72, below.
Time
Code d h
0 0
3 6
0 0
14 22
0 0
0 0
3 13 31 59
0 0
Downloading and
m s
0 12
8 34
0 9
9 4
0 11
0 11
0 8
System Logs | 105