System Logs | 105Using the Persistent Event LogIn addition to the optional buffered System log described above, the switch maintains a persistent Eventlog in NVRAM. Persistent logging is always enabled to memory and disabled to the console or to syslogservers. The log does not require configuration.The purpose of the Event log is to save system exception information to persistent memory for analysis byDell 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 CommandBecause the show eventlog command monitors a persistent log database, it is important to correlate anyERROR entries with the timeline using the time designator. The Time column in the output is the systemup-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 softwarefile, 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 youcan 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 callsNote: You can copy the Event log from the switch to a TFTP server. See Downloading andUploading 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 eventlogEvent Log---------TimeFile Line TaskID Code d h m sEVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 12ERROR> unitmgr.c 3325 0E41CD38 00000000 3 6 8 34EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 9ERROR> unitmgr.c 3339 0E22B298 00000000 14 22 9 4EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 11EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 11ERROR> reset603.c 177 0D6007A8 09A60110 3 13 31 59EVENT> bootos.c 434 0FFFFE00 AAAAAAAA 0 0 0 8
