Setup Guide

Symptom I2C bus errors are appearing in the switch log.
Probable cause and recommended action I2C bus errors generally indicate defective hardware or poorly seated
devices or blades; the specific item is listed in the error message. Refer to
the Fabric OS Message Reference for information specific to the error that
was received. Some Chip-Port (CPT) and Environmental Monitor (EM)
messages contain I2C-related information.
If the I2C message does not indicate the specific hardware that may be
failing, begin debugging the hardware, as this is the most likely cause.
Symptom Core file or FFDC warning messages appear on the serial console or in
the system log.
Probable cause and recommended action Issue the supportSave command. The messages can be dismissed by
issuing the supportSave -R command after all data is confirmed to be
collected properly.
Error example:
*** CORE FILES WARNING (10/22/08 - 05:00:01 ) ***
3416 KBytes in 1 file(s)
use "supportsave" command to upload
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 collected by entering
supportsave -U -d MySupportSave. Not every type of reboot reason activates the Rolling Reboot Detection feature. For example,
issuing the reboot command multiple times in itself does not trigger rolling reboot detection.
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
General Troubleshooting
Brocade Fabric OS Troubleshooting and Diagnostics Guide
53-1004126-01 25