Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

216 Fabric Manager Administrator’s Guide
53-10000610-02
FDMI device information collection
15
FDMI device information collection
FDMI device information is updated once a day as a server-side service, with a few exceptions:
• Downloading firmware to HBAs starts FDMI data collection so that the data matches the
download.
• FDMI data for a new fabric is collected when it is discovered. Because the devices and ports
must be in the database prior to storing FDMI data, data collection does not start until the
device discovery is complete.
You can, at any time, select Discovery > Refresh to update the FDMI device information.
If FDMI data cannot be collected, an alert appears with a brief description of the problem. The alert
remains unresolved until the server can collect FDMI for that fabric.
NOTE
There must be at least one FDMI-capable switch in the fabric for FDMI information to be collected.
Switch reboot
This section provides information on creating reboot groups and performing sequenced reboots. A
reboot group contains one or more switches from a single fabric. You cannot group switches from
different fabrics, and each switch can belong only to one reboot group.
Create a reboot group containing multiple switches from the same fabric if you want the selected
switches to reboot simultaneously. You might want to create reboot groups containing switches that
run the same firmware, serve the same function, reside in the same physical location, or share any
other attribute. After creating reboot groups, you can then configure a sequential reboot of the
reboot groups.
Create a single-switch reboot group for any switch in your fabric that is not assigned to a
multiswitch reboot group if you want to include it in a reboot sequence.
A sequenced reboot allows different areas of your SAN to reboot and stabilize before other
switches in the fabric begin to reboot. This reduces the load of interswitch traffic on the SAN. For
example, you can use the following reboot strategies:
• Simultaneously reboot switches that run the same firmware.
• Simultaneously reboot switches of the same model.
• Reboot the core switches of a fabric, then the edge switches.
• Reboot the backbone of a large SAN, then reboot other sections.
• Reboot distant physical locations sequentially.
See the following sections for information about reboot groups:
• “Creating a reboot group with multiple switches” on page 217
• “Creating single-switch reboot groups” on page 218
• “Assigning switches to an existing reboot group” on page 219
• “Performing a sequenced reboot” on page 220