Users Guide
Table Of Contents
- About This Document
- Introduction
- General Troubleshooting
- Connectivity
- Configuration
- Firmware Download Errors
- Security
- Virtual Fabrics
- ISL Trunking
- Zoning
- Diagnostic Features
- Switch Type and Blade ID
- Hexadecimal Conversion
- Index
14 Fabric OS Troubleshooting and Diagnostics Guide
53-1002930-01
Switch boot
2
Switch boot
Symptom The enterprise-class platform model rebooted again after an initial bootup.
Probable cause and recommended action
This issue can occur during an enterprise-class platform bootup with two CPs. If any failure occurs
on the active CP, before the standby CP is fully functional and has obtained HA sync, the standby CP
may not be able to take on the active role to perform failover successfully.
In this case, both CPs reboot to recover from the failure.
Rolling Reboot Detection
A rolling reboot occurs when a switch or enterprise-class platform has continuously experienced
unexpected reboots. This behavior is continuous until the rolling reboot is detected by the system.
Once the Rolling Reboot Detection (RRD) occurs, the switch is put into a stable state so that only
minimal supportSave output need be collected and sent to your service support provider for
analysis. USB is also supported in RRD mode. The USB device can be enabled by entering
usbstorage -e and the results ccollected by entering supportsave -U -d MySupportSave.Not every
reboot activates the Rolling Reboot Detection feature.
ATTENTION
If a rolling reboot is caused by a Linux kernel panic, then the RRD feature is not activated.
Reboot classification
There are two types of reboots that occur on a switch and enterprise-class platform: expected and
unexpected. Expected reboots occur when the reboots are initialized by commands; these types of
reboots are ignored by the Rolling Reboot Detection (RRD) feature. They include the following
commands:
• reboot
• haFailover
• fastBoot
• firmwareDownload
The RRD feature is activated and halts rebooting when an unexpected reboot reason is shown
continuously in the reboot history within a certain period of time. The period of time depends on
the switch. The following reboots are considered unexpected reboots:
• Reset
A reset reboot may be caused by one of the following:
- Power-cycle of the switch or CP
- Linux reboot command
- Hardware watchdog timeout
- Heartbeat loss-related reboot