Monitoring the History of System and Module Resets
Purpose
Display the history of system and module resets. You can display the current reboot.hty file or a saved reboot history file. If you have a redundant router, it can be convenient to copy the redundant module’s reboot.hty file to another filename for viewing with the show reboot-history command.
Action
To display the history of system and module resets:
host1#show reboot-history *** Entry 1 *** time of reset: TUE APR 10 2001 20:25:59 UTC run state: unknown image type: diagnostics location: slot (7) build date: 0x3abf4337 MON MAR 26 2001 13:25:11 UTC reset type: user reboot, task "scheduler", reason "not specified" *** Entry 2 *** time of reset: TUE APR 10 2001 20:25:44 UTC run state: unknown image type: diagnostics location: slot (8) build date: 0x3abf5d5f MON MAR 26 2001 15:16:47 UTC reset type: user reboot, task "scheduler", reason "not specified" *** Entry 3 *** time of reset: TUE APR 10 2001 20:25:03 UTC run state: unknown image type: diagnostics location: slot (4) build date: 0x3abf3ee0 MON MAR 26 2001 13:06:40 UTC reset type: user reboot, task "scheduler", reason "not specified"
Meaning
Table 1 lists the show reboot-history command output fields.
Table 1: show reboot-history Output Fields
Field Name | Field Description |
|---|---|
Entry | Number of entry in the reboot history; numbers range from lowest (most recent reset) to highest (oldest reset) |
time of reset | Timestamp for reset |
run state | State of system at reset |
image type | Type of image running when the record is written:
|
location | Slot that reset; location is offset by two slots at slot 7 and above (the SRP module in slot 6 shows location as slot 7, the SRP module in slot 7 shows location as slot 9, and slots 8-13 show location as 10-15, respectively) |
build date | Build date of software version |
reset type | Cause of reset |
