beautypg.com

Trace logs, Auto save on crash or rollover – Dell PowerEdge FX2/FX2s User Manual

Page 271

background image

Please make sure that stacking/fanout not configured for Diagnostics

execution.

Also reboot/online command is necessary for normal operation after the

offline command is issued.

Proceed with Offline [confirm yes/no]:yes

Dell#

2. Confirm the offline status.

EXEC Privilege mode

show system brief

Dell#show system brief

Stack MAC : 00:1e:c9:de:03:7b

-- Stack Info --

Unit UnitType Status ReqTyp CurTyp

Version Ports

----------------------------------------------------------------------------

--------

0 Management offline PE-FN-410S-IOA PE-FN-410S-IOA

1-0(0-1862) 12

1 Member not present

2 Member not present

3 Member not present

4 Member not present

5 Member not present

Dell#

Trace Logs

In addition to the syslog buffer, the Dell Networking OS buffers trace messages which are continuously

written by various software tasks to report hardware and software events and status information.

Each trace message provides the date, time, and name of the Dell Networking OS process. All messages
are stored in a ring buffer. You can save the messages to a file either manually or automatically after
failover.

Auto Save on Crash or Rollover

Exception information for MASTER or standby units is stored in the flash:/TRACE_LOG_DIR directory. This

directory contains files that save trace information when there has been a task crash or timeout.

• On a MASTER unit, you can reach the TRACE_LOG_DIR files by FTP or by using the show file

command from the flash://TRACE_LOG_DIR directory.

• On a Standby unit, you can reach the TRACE_LOG_DIR files only by using the show file command

from the flash://TRACE_LOG_DIR directory.

NOTE: Non-management member units do not support this functionality.

Example of the dir flash: Command

Dell#dir flash://TRACE_LOG_DIR

Directory of flash:/TRACE_LOG_DIR

1 drwx 4096 Jan 17 2011 15:02:16 +00:00 .

2 drwx 4096 Jan 01 1980 00:00:00 +00:00 ..

3 -rwx 100583 Feb 11 2011 20:41:36 +00:00 failure_trace0_RPM0_CP

Debugging and Diagnostics

271