Enterasys Networks X-PeditionTM manual Fault Report Commands, Capturing Fault Report Data

Utilizing the Command Line Interface

•Contents of stacks (task stacks, interrupt stack)

•Status of one special task (packet processor by default)

•Code around the crash program counter

•Task message queues

•Memory management statistics

•Task stack traces for all tasks

The router can store one Fault Report, retaining the first Fault Report in case of multiple failures. It is stored in a special RAM memory area which is preserved if the XSR is rebooted but lost if the router is powered down.

A fault report is also captured in case of a catastrophic watchdog interrupt. Typically, the watchdog timer is reset once per second. If the software fails and 2.6 seconds expire, the watchdog hardware will induce an interrupt which initiates the capture of the fault report. After an additional 2.6 seconds, the CPU is reset and the XSR will warm-boot.

Fault reports can be retrieved from the CLI interface and forwarded to Enterasys Support for analysis.

When the XSR automatically reboots after a crash, the following sample message is logged:

<186>May 29 22:20:59 1.1.1.1 PLATF System warm boot from crash

Fault Report Commands

The show fault-reportcommand displays the report. Refer to the XSR CLI Reference Guide for more command details. The clear fault-reportcommand can be used to remove old fault reports and reset the XSR to capture a new one.

Capturing Fault Report Data

Enterasys Networks recommends that you enter the following commands from privileged EXEC mode during capture to assist in analysis and simplify the capture process. The clear fault- report command should only be executed once you are sure that the text has been completely captured since the data is not recoverable afterwards.

•enable

•terminal Length 0

•show fault-report

•show version

•show logging history

•clear fault-report

•terminal length 24

•disable

2-24 Managing the XSR