Paginas

10 February 2018

Upgrade Firmware Brocade SAN Switch

 

In this post I will show you how to Upgrade the Brocade Switches Firmware.

Requirements:
  • Filezilla FTP Server (or similar)
  • Filezilla FTP Client (or similar)
  • Putty
  • Java JRE (the version will depend of the Switch Brocade. Probably you will need version 7)
  • Log on credential for Brocade website or vendor website
  • Downloaded upgrade firmware. Read the Release Notes because you might need more than one firmware

Let's start with the Upgrade Paths and then with the procedures.

 


Notes about the Upgrade Paths

  • If you have many steps to upgrade, you should upgrade to the latest in the series (or if it’s very new, probably it's safest to go with the second newest. Just check the release notes of the newest to make sure nothing related is fixed);
  • What I usually recommend is this path (non disruptive):
  • 5.0.1d --> 5.2.3 --> 5.3.2c --> 6.0.0b or 6.0.1a --> 6.1.2c --> 6.2.2g --> 6.3.2e --> 6.4.3h --> 7.0.2e --> 7.1.2b --> 7.2.1g --> 7.3.2a --> 7.4.2 --> 8.0.1 or 8.0.2b --> 8.1.1a
  • Upgrade from a version earlier than 6.4.1b to 7.0.x or from 7.0.x to 7.2.x is possible but disruptively;
  • If the switch is on 5.1.x you can go directly to 5.3.x;
  • Fabric OS 6.2.2f is allowed only from Fabric OS 6.1.0a or later
  • Sometimes you have to use the firmwaredownload -s switch to Upgrade;
  • You could in principle also say that:
    • 2G cannot upgrade to Fabric OS 6.x
    • 4G and 8G can be on Fabric OS 6.x
    • All 4G except some HP’s P and C-class 4G blade switches (4012 & 4024) can run 6.4.x
    • 8G can run Fabric OS 6.4.x
    • 8G and above can run Fabric OS 7.x
    • 16G (Gen5) needs to be on Fabric OS 7.x or Fabric OS 8.x
    • 32G (Gen6) needs Fabric OS 8.x
  • Upgrading to Fabric OS 7.1.2 can be non-disruptively upgraded from 7.0.x and 7.1.x with caveats: For example, any previously existing error log entries with FOS v7.1.0 will be permanently lost once upgraded to FOS v7.1.2;
  • Upgrading to Fabric OS 7.2.x can be done non-disruptively from 7.1.x. Disruptively from 7.0.x is supported;
  • Upgrading to Fabric OS 7.3.x can be done non-disruptively from 7.2.x. Disruptively from 7.1.x is supported;
  • Upgrading to Fabric OS 7.4.x can be done non-disruptively from 7.3.x. From 6.4.x with firmwarecleaninstall switch;
  • Upgrading to Fabric OS 8.1.x can be done non-disruptively from Brocade platform running 8.0.2 or later. From 7.4.x disruptively with "firmwaredownload -s"
 
A disruptive upgrade means that all ports will go offline/online during upgrade.
 
 

 

Upgrade Procedure


Step 1: Turn off firewall.
Turn off firewall on Windows machine where you will install Filezilla FTP server.
 
Step 2: Configure FTP server
Download Filezilla FTP server for windows here.
Install Filezilla FTP server. Just run the installer GUI and accept the defaults. You may find there are third party software embedded with Filezilla, decline first two and then click next to install FTP server. Once installed. Click Edit, Click Settings. Select following. Setup timed out value to 9999.

clip_image001
 
Enable logging, so that you can see brocade is connecting to FTP server:
clip_image002

Create an anonymous user account and set password to none / "blank":
clip_image004

Set shared folder location and click "Set as home dir":

 
Actual location of firmware in my PC. Don't forget to unzip all the files:
clip_image008
 
Step 3: Test FTP connectivity
Now install Filezilla client and test connectivity. You can download it here.

clip_image010
 
Step 4: Upgrade Firmware in Switch Brocade
Open Putty, Type IP address of the brocade switch. leave the default port 22.
 
image
 
Log on to brocade fabric using root or another admin and enter the credentials and type the following:
  • firmwaredownload
  • IP address: IP address of your PC where you configured Filezilla FTP server
  • Username: blank or Hit enter I am using anonymous FTP. No need to type username
  • Path: /v7.1.2b or the path where you saved firmware
  • Password: blank Hit enter I am using anonymous FTP. No need to type password
clip_image011
  • Do you want to continue? [y/n]: y
clip_image013

clip_image015
 
Close putty session now. This procedure will reboot the Brocade switch and you are done.
Once Brocade Fabric is rebooted, reconnect using putty, log on and type the command to see the current version of firmware:
  • firmwareshow

If you would like to upgrade from v7.1.2b to v7.3.0c directly use the following command (This is a disruptive upgrade procedure):
  • firmwareDownload -s
  • IP address: IP address of your PC where you configured Filezilla FTP server
  • Username: blank or Hit enter I am using anonymous FTP. No need to type username
  • Path: /v7.3.0c or the path where you saved firmware
  • Password: blank Hit enter I am using anonymous FTP. No need to type password
  • Do you want to continue? [y/n]: y
  • Do Auto-Commit after Reboot [Y]: y
  • Reboot system after download [N]: y

Firmware is being downloaded to the switch. This step may take up to 30-45 minutes to complete. Have a drink and relax. That's it!

Thanks for reading. See you next time!

46 comments:

  1. A disruptive upgrade means that all ports will go offline/online during upgrade. How this is different from non-disruptive upgrade because we need to reboot switch anyhow?

    Can i update OS directly from v7.2.1c1 to v8.1.2a disruptively.

    ReplyDelete
  2. Hello, you can upgrade first to version 7.2.1g and then to 8.1.2a disruptively. You will need to reboot your SAN Switch a few times. If you have redundancy in all your ports you shound have no problems.
    Regards.

    ReplyDelete
  3. Does anyone has the link to prior to 7.4 versions?
    Thank you!

    ReplyDelete
    Replies
    1. It's been a while, but I remember that I could download versions prior to 7.4.X in IBM sites.

      Delete
  4. I would like to upgrade from 7.1.1b to 7.4.2c. Can you give me the exact upgrade path?
    I want to upgrade as few times as possible.

    ReplyDelete
    Replies
    1. Hello, you can use this Upgrade path: 7.1.x ---> 7.2.x ---> 7.3.x ---> 7.4.2c

      Delete
  5. Hi , Can I upgrade only the Principal switch to 8.2.x while subordinate in 7.1.x?


    ReplyDelete
    Replies
    1. Hi, Are the switches on the same fabric?
      If not, you can upgrade your brocade to FOS 8.2.x (if the Storage or servers hardware are compatible).
      If yes, it will depend of you model. Most of them only support FOS 7.3.1 with 8.2.X, but some support also 7.1.2.
      Check the FOS 8.2.1 Release Notes:
      https://downloads.hpe.com/pub/softlib2/software1/pubsw-windows/p1561111106/v158170/FOS8.2.1_RN.pdf -> Page 31.

      Delete
  6. Pls help me to upgrade to 8.2.2c from
    7.4.1d, non disruptive upgrade

    ReplyDelete
    Replies
    1. Hello,
      The upgrade path is the following:
      7.4.X --> 8.0.1 (nondisruptive upgrade) --> 8.2.2 (disruptive upgrade)
      You can read more about the Upgrade in tis document (page 6):
      https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00046367en_us

      Delete
    2. Thank Sergio .. now my prob is am not able to get 8.0.1 from brocade site.. 7.4 , 8.1 and 8.2 is there.. 8.0 is missing

      Delete
    3. Can you try here? You must provide a valid SN from your brocade.
      https://datacentersupport.lenovo.com/us/en/products/storage/fibre-channel-switches/brocade-6510-fc-san-switch/3873/downloads/ds119514

      Delete
  7. hi Sergio

    do you have the link to down load the 7.3 and 8.0 please

    ReplyDelete
  8. Hello Sergio,
    I would like to upgrade from 7.1.2f to 8.2.x, could you give me the path please ?
    Thanks you in advance.

    ReplyDelete
  9. Hello Sergio,
    I would like to upgrade from 7.1.2f to 8.2.x, could you give me the path please ?
    Thanks you in advance.

    ReplyDelete
  10. Hello,
    You must follow this path:
    7.1.2f -> 7.2.X -> 7.3.X -> 7.4.X -> 8.2.X (disruptive)

    https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00046367en_us

    ReplyDelete
  11. Hello Sergio,
    Thanks you very much for your response.
    It is possible instead to have a non-disruptive path upgrade please ? (from 7.1.2f to 8.2.x)
    Thank you in advance.

    ReplyDelete
  12. No, it's not possible.
    Please check the above article on the last reply.

    ReplyDelete
  13. Hi,
    Okay thanks you very much for your response.
    Have a good day !

    ReplyDelete
  14. Good afternoon!

    I need to update from version 7.0.2c to version 7.4.2d.
    I need the appropriate FabricOS versions for this, which are not easily available anymore.

    Who can help me here?

    Thanks in advance for your efforts.

    ReplyDelete
  15. Hi Sergio,
    I tried to upgrade the 8.0.1b firmware to 8.1 non-disruptively.
    I got this error:
    Free space=21770240, fabos-swbd117 package size=24586182, Required space=26683334.
    Not enough free space on the secondary partition.
    Firmware download failed - Out of disk space. (0x24)
    Aborting firmwaredownload now.
    Firmwarecommit has started on the local CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
    Validating the filesystem ...


    Do You have any idea to fix this?

    ReplyDelete
    Replies
    1. Hi Tamas,
      You should delete some files on your SAN Switch. Probably files from previous upgrades.
      Can you SSH to your SAN Switch and check those files? Delete them and then try the upgrade again.

      Delete
  16. Hey,
    During the update from version v7.1.0a to version v7.2.1g I have this message "
    The firmware download has failed because the firmware signature cannot be verified. "
    Maybe someone encountered something like this during the update?

    ReplyDelete
    Replies
    1. Hi I found a solution to the problem. "Checking system settings for firmwaredownload...
      Firmwaredownload failed because the signature for the firmware could not be validated."
      It was on my side in the wrong ftp server configuration. The blog description helped solve my problem. is very useful. Very good job Sergio Alves.

      Delete
    2. Hi, I encounter the same problem, how did exactly solved this problem?

      Delete
  17. Hi There, my current fabric has 12 Switches(6 in each) and these are on different FOS levels, i am planning to bring these to single FOS i.e. 7.4.x, can you recommand the path to do this non-disruptive?
    7.0.0a>
    7.1.0a>
    7.2.1.c>
    7.4.1e>
    due to being old models i can't take these to 8.x.x i belive, advice on this as well please?
    Brocade 5100
    Brocade 6510
    IBM SAN80B-4
    Brocade DCX-4S
    Thanks,
    Santhosh

    ReplyDelete
    Replies
    1. Hello,
      I usually recommend this path (non disruptive):
      7.0.0a --> 7.0.2e --> 7.1.2b --> 7.2.1g --> 7.3.2a --> 7.4.2

      What I could check, all the models that you have can only be in FOS 7.4.x

      https://www.dell.com/support/home/pt-pt/product-support/product/brocade-5100/docs
      Brocade 5100 -> support up to 7.4.x

      https://www.dell.com/support/home/pt-pt/product-support/product/brocade-6510/docs
      Brocade 6510 -> support up to 7.4.x

      https://www.ibm.com/support/pages/ibm-san-b-type-firmware-version-7x-qualification
      IBM SAN80B-4 -> support up to 7.4.x
      Brocade DCX-4S -> support up to 7.4.x

      Delete
    2. thanks a lot Sergio, i will plan the same. it's difficult to find these FOS now..
      in my inventory only 6510 is the 16Gig switch rest all 8Gig once, if i want to add a new 16Gig switch it's better to Trunk that with the 6510 only? or trunking to 8gig switch will effect on?

      Delete
    3. You can ISL trunk with the Switch 6510 at 16Gbps or more (if you put more ports in the aggregated ISL, and additional license may be required). You can also Trunk ISL to the Switch 6510 but you only get 8Gbps speed (although the new one works at 16Gbps). Pay attention to the compatibility between all Swicthes before doing ISL Trunk.

      Delete
    4. Hi Sergio,
      i got 2 Refurbished EMC(Brocade) 6520 Switches and need to add these into existing fabric.
      All existing switches configured FID's when i login any switch they promt "pvl-6510-1:FID128:admin>" and Fabric A has FID10 where all the ports display(FID128 has nothing, a switch show just display switch details, no ports).
      so how can i achive the same thing on the new switches? beore i add these into fabric i want to make sure they have same config.

      pvl-6510-1:FID128:admin> switchshow
      switchName: pvl-6510-1
      switchType: 109.1
      switchState: Online
      switchMode: Native
      switchRole: Principal
      switchDomain: 1
      switchId: fffc01
      switchWwn: xx:xx:xx:xx:xx:xx:xx:xx
      zoning: OFF
      switchBeacon: OFF
      FC Router: OFF
      Allow XISL Use: OFF
      LS Attributes: [FID: 128, Base Switch: No, Default Switch: Yes, Address Mode 0]

      Index Port Address Media Speed State Proto
      ==============================================
      ================================
      No ports found in the system!!!
      pvl-6510-1:FID128:admin> setcontext 10
      pvl-6510-10-1:FID10:admin> switchshow
      switchName: pvl-6510-10-1
      switchType: 109.1
      switchState: Online
      switchMode: Native
      switchRole: Subordinate
      switchDomain: 2
      switchId: fffc02
      switchWwn: xx:xx:xx:xx:xx:xx:xx:xx
      zoning: ON (fcsw01_prod)
      switchBeacon: OFF
      FC Router: OFF
      Allow XISL Use: ON
      LS Attributes: [FID: 10, Base Switch: No, Default Switch: No, Address Mode 0]

      i believe the Domain ID in FID10 should not be same?
      Thanks .

      Delete
    5. Hello,
      All switches within the same fabric must have unique IDs. The firmware versions within the same fabric should be the same or compatible.

      Delete
    6. all my SAN Switches are on 7.x.x ( strting from 7.0.0a to 7.4.1e) i had a plan to make all FW version to same level but lot of dependency and not able to get a downtime.
      my question still not answered, How can i set FID 128 and FID10/20(FabricA/B) .. so when i login to switch i should land in FID128 and no ports and when i change to FID10 i should see all the ports in.

      Delete
    7. Hello, Can you check the Broadcom documentation?
      https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-administration/9-1-x/v26769804/v26769614/v26770101.html

      Delete
  18. you mean the FOS? we bought 2 refurbished Switches (6520B) which has 16Gig ports and we want to add these 2 into the fabric(1 in each), so before adding that i want to make all switch FOS to same.

    ReplyDelete
    Replies
    1. Correct. Its best practice to have all the SAN Switches in the same FOS version in the Fabric.

      Delete
  19. compatability in terms of FOS version between all the switches? I am planning to level all the FOS before adding new switches, the new switches are on FOS 7.4 and i will upgrade current fabric switches to 7.4 then i will add. this is the plan.

    ReplyDelete
  20. Hi Sergio,
    i tried a lot to get the FOS version you suggested but it was really very hard to get these, i managed to find the below FOS Versions, not the versions you suggested earlier!!
    7.0.2e>>7.1.2b>>7.2.1g>>7.3.1d>>7.3.2b>>7.4.2c>>7.4.2d>>7.4.2g
    i am still okay to procedd with?
    i hope these can go any Brocade OEM switches right or does these specefically goes to only specefic manufactures? like i have Brocade and IBM swithces so i can use the FOS to upgrade both?

    ReplyDelete
    Replies
    1. Hello,
      It is advisable to read the Release notes of each Firmware, but I think you can proceed in the order indicated. Regarding the IBM, they are Brocade b-type, so you can use the same firmware.

      Delete
  21. Hi, I have a situation
    we currently have 2 different SAN Environment (Ex SAN A and SAB B). My manager wanted if we can present Storage in SAN A to Blade servers in SAB B, both the environments are not connected by any means, both have different active cfg. (But both the devices are in same DC but different Rows/Racks)He also has a thought of merging both the fabrics if the first situation can't be achived.
    Need your help to solve this in a simple way.
    Thanks in advance.

    ReplyDelete
    Replies
    1. Hello, if I understand correctly, you want the SANA Blades to have access to the SANB correct? You'll need to connect fiber cables from the Blades to the SANB and then it's a matter of Switch Zoning. In the end the Blades will have access to SANA and SANB for access to Storage in both SANs for example.

      Delete
    2. thanks a lot Sergio :), this is very helpful, i will plan this fos upgrade sooner.

      Delete
    3. thanks, i had same solution in my mind but just wated to see if there are other options .

      Delete
  22. Hi Sergio,
    i have a situation here, we have 2 DC and the Main DC1 has a 16gig Brocade Switch and DC2 we have 2 SAN Switches(8gig), now i want to install a new 16gig SAN Switch in DC2, how can i install a 16gig new Switch in DC2, what's the process. Can this be done without Downtime?
    I mean if i want to establish a ISL from DC1 16gig to DC2 16gig(new one) then already connected 2 8gig Switch on DC2 need to be disconnected? DC1 to DC2 the distance is about 40miles.

    Thanks,
    Santhosh Kumar

    ReplyDelete
  23. Hi Sergio,
    How to connect/add a new 16gig SAN Switch into existing fabric when all the SAN Switches are in existing Fabric has all 8GB SAN Switches?
    ID 0: Switch is 16GB, ID:1, 2 are 8GB Switches and now i got 16gig Switch, if i want to add this new 16gig switch what are the options i have?

    ReplyDelete
    Replies
    1. Hello,
      Is there already an ISL connection between the two Datacenters? If so, is there any other fiber that can be used to interconnect the SW-DC1(16gb) to the SW-DC2(16Gb)?
      I think the steps will be as follows (assuming you can create an ISL trunk between the two switches without interrupting the current connection to the 8Gb ones)
      - Check FW compatibility between SW-DC1(16gb) and SW-DC2(16Gb)
      - Create the ISL Trunking over Long-Distance connection (check if it is supported, have the appropriate transcievers and pay attention to the Fabric IDs)
      - After the connection is established and operational, perform the correct zoning
      - Connect the devices that are on the old 8Gb switches in a phased manner to the new DC2 Switch (there may be some downtime if it is not possible to connect a Host to the new SW and the old SW)
      - Validate that everything is operational with the first Host migrated and go to the next one (if you have any storage to be migrated, it's better to do in offline mode)
      - After everything is migrated, discontinue the old Swicthes 8Gb

      Delete