Brocade Switch: Shutdown and Startup Sequence of Principal and Subordinate Switches

Asset ID:	1-71-2195220.1
Update Date:	2016-10-25
Keywords:

Solution Type Technical Instruction Sure

Solution 2195220.1 : Brocade Switch: Shutdown and Startup Sequence of Principal and Subordinate Switches

Applies to:

Brocade 300 Switch - Version All Versions to All Versions [Release All Releases]
Brocade 5100 Switch - Version All Versions to All Versions [Release All Releases]
Brocade SAN Switch Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

This document explains about the shutdown and startup sequences of principal and subordinate Brocade FC switches and it's impact in the SAN fabric.

Solution

For shutdown: (1) shutdown host(s) (2) shutdown storage (3) shutdown subordinate switch(es) (4) shutdown principal switch

For startup reverse the order:
For startup (1) startup principal switch (2) startup subordinate switch(es) (3) startup storage (4) startup host(s)

It is recommended to take on the switch the supportsave / supportshow and configupload before performing any activity.

sysshutdown <----- This command gracefully shut down a Brocade switch

Impact:

When the 'principal' switch has been rebooted or removed, (If customer is not following the proper procedure as updated above) one of the 'subordinate' switches will assume the role of the 'principal' switch, its expected behavior in the Fabric.
If you want another switch i.e. one of the original principals; to be the principal again, then run fabricprincipal 1, it appears that it needs a fabric rebuild to pick up the change (which is disruptive to I/O).

Switch> fabricprincipal 1

Switch> fabricprincipal -f 1

References

<NOTE:1016713.1> - Brocade - How to save a switch configuration off to a file
<NOTE:1015100.1> - Brocade - How is the principal switch determined?

Attachments

This solution has no attachment