Skip to main content
NetApp Knowledge Base

Is a switch reboot required when upgrading the Brocade FOS from v8.2.x to v9.0.X?

  1. Last updated
  2. Save as PDF
Views:
540
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

  • Brocade switch
  • G620 (Switch Type 162.5)

Answer

Yes, it involves a reboot, but it won’t be disruptive in nature. When the switch reboots, there will be a brief disconnection for the host paths, but since multipathing and redundant switches are in place the reboot will be non-disruptive.

NOTE: The Fabric OS software does not support non-disruptive upgrades from any release more than one major release earlier than the one being installed. This means that non-disruptive upgrading to Fabric OS 9.0.x is supported from Fabric OS 8.2.x only. 
In order to upgrade from an earlier version of Fabric OS software (for example, 8.1.x), stepped upgrade should be performed which will include 'intermediate' firmwares in-between.

Additional Information

  • How to upgrade or downgrade Brocade switch firmware
  • Brocade Fabric OS Software Upgrade Guide, 9.0.x

  • In order to perform the upgrade non-disruptively, you should be going up to the next minor release each time.  
    For example:
    If current FOS is 6.4.1b.  The second digit in the firmware designator is the minor release number, in this case ---> 4. There is no 6.5.x release, so the next step will be to go to the next major release, which is 7.0.x.  To make this a little more clear, here's an example of the upgrade path they should take:

6.4.1b > 7.0.2e > 7.1.2b > 7.2.1g > 7.3.2 > 7.4.1c

  • As shown in the above example, the 2nd digit in the firmware version increases by 1 increment, except for the first one due to it being a major release.

  • As long as they are increasing the minor release (2nd digit) by an increment of 1 each time, there shouldn't be any data disruption and the 3rd digit (micro release) doesn't matter.  Look at it this way:

6.4.1b > 7.0.x > 7.1.x > 7.2.x > 7.3.x > 7.4.1c

  • The 'x' can be any number, it doesn't matter.  Only the minor release (2nd digit) matters.
     

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.