Brocade SAN Switch Firmware Upgrades

Overview

This is my guide/template to upgrading Fabric OS (FOS) – Firmware – on the Brocade SAN Switches. If you have any additions, comments or questions please go ahead and comment or if you have any questions you can find my e-mail on https://guldmyr.com. The post has been updated over 173 times according to my WordPress revisions, first update in January 2011.

This article was originally built from my experience with HP branded Brocade SAN Switches – not with any other OEM or pure Brocade switches. I have however since beginning this document gotten experience with other vendors.
I do not think others are different except for licenses and some default fabric.ops.
I made a comparison of two downloads of the 6.3.1b Fabric OS Firmware (one via IBM and one from HP). You can find a link to the “IBM” firmware and release notes after 6.x in that article too. I found that they are very similar and the HP firmware works on the IBM switch and vice versa. Another example is that firmware gotten from HDS works on an HP branded Brocade switch.

When you see 7.2.x this means any version in the Fabric OS 7.2.x series. For upgrades, this would generally mean the latest available in that series (like 7.2.1g for 7.2.x or 8.0.2d for 8.0.x) unless of course there is a problem with the latest. Sign up for your vendor’s security and update alerts to get notified about new releases.

Carefully plan the upgrade, it takes time but it is rewarding and worth it.

Updates in this article:

Old Updates

2011-02-22: Updated links because the release notes I had before to 6.1.x and above did not work anymore. Also changed the sub-versions in 6.1.x and above to the latest released one by HP.
2011-02-24: Found link to 5.2.x and 6.0.x FOS on HP.com with the help of an ITRC thread.
2011-04-21: Added links for correlating Brocade Product name, model number and HP name. Latest in 6.4.x series is now 6.4.1b
2011-05-05: Added link to Web Tools for 6.2.x with reference to how to upgrade Firmware via the web tools.
2011-05-15: A note added about compatibility regarding the ‘HP’ firmware files and other vendors – as far as I can tell the ones downloaded from HP will work on other non-HP switches. Also posted a new blog post about that. Added link to IBM.com – for correlating product names and for getting (all Fabric OS) firmwares. EMC also has Brocade products.
2011-05-18: Added a link to a post on HP’s support forum where the post helped a bit. Also made post a little easier, wrote a little about the release.plist confusion.
2011-05-24: Added example to show that driver updates are important. Some more restructuring of the article.
2011-07-12: Added FOS 7.0.0a
2011-07-14: Added link to HP knowledge base and updated a link to an ITRC forum thread to point to the new forum.
2011-09-29: Added FOS 7.0.0b and section about CF cards.
2011-10-19: Wrote a bit about firmware upgrade order.
2011-10-24: The HP links to 6.0.0c and 5.3.x seems to not work anymore. I could not find either of these for download on HP’s website. The IBM one still has 6.0.0c (release notes anyway).
2011-12-05: Went through all links to make sure they worked. Re-wrote some of the steps and re-ordered so that ‘decide’ is before ‘prepare’. Added output from switch when doing the firmware upgrade via CLI.
2011-12-10: Added table of contents via a plugin.
2012-01-02: Added FOS 7.0.0c
2012-01-09: Added EMC branded switches default pw
2012-02-14: Added HP’s link to FOS 5.x. firmware.
2012-02-15: Added IBM’s link to FOS 7 info and downloads.
2012-02-21: Some notes about which switches can do which firmware. Re-wrote a part of the upgrade order section.
2012-02-27: Note about licenses.
2012-02-29: Added note about 5.1.x to 5.3.x, made upgrade path clearer. Also made how to find 5.3.x and 6.x firmwares a little clearer for HP’s page.
2012-03-01: Added 6.2.2f and 7.0.1 and note about plist/ftp for 5.1.x
2012-04-03: Addeed 6.3.2e
2012-04-24: Added 7.0.1a
2012-04-27: Rewrote some part of the upgrade section.
2012-06-07: Added 6.4.3 and 7.0.1b
2012-06-14: Added link to Brocade FOS Target Path in decide section.
2012-10-27: Some grammar updates and 16G FOS 7.x requirement. 6.4.3b and 7.0.2.
2012-11-05: Updated links to release notes. Perhaps it’s time to condense the updates list. Notes about passive/active ftp, ifmodeshow|ipaddrshow and java version required (listed in release notes).

2013-03-10: 7.0.2b and 6.4.3c added some notes about compatibility. Improved list of which FOS works with which FC speeds.
2013-03-29: Added 7.1.0a and 7.0.2c. Only HP is out with 7.1.0a as of now. Brocade may have it non-publicly, at least I cannot see it in my brocade. Other minor updates.
2013-04-04: Added link to 6.4.3d
2013-05-02: Updated link to FOS Target Path.
2013-06-23: Changed some ftp:// links to http://
2013-07-16: Added link to IBM’s pdf with pictures for firmware upgrade.
2013-08-03: 6.4.3e by IBM – not available by HP yet. Disruptive upgrades are OK from 6.2 to 6.4.
2013-08-05: Added 7.1.1, updated some links to release notes.
2013-10-03: Made it a bit clearer regarding which is the earliest firmware you can upgrade from. Newer revisions of some Brocade release notes. 7.0.2d out and 6.4.3e link to hp.com
2013-11-14: Removed comment that B300 does not support 6.4.x – it does! It should have been the 200E! Thanks Eugene :)

2014-02-01: As of 2014-02-01 HP does not allow anybody without a valid support agreement to download firmwares. Release notes and at least some firmware links appears to still be working. Expect difficulty and broken links while hunting for firmwares. Fabric OS firmwares downloaded from IBM’s site works on HP switches too, but there might be some differences (although I couldn’t find any important ones when I compared 6.3.1b). So far it seems this restriction of access to firmwares only applies to HP servers.

2014-02-07: Added new link to HP’s page for FOS 5.2 to 6.3  Thanks Leo R!

2014-02-11: Added 7.2.0b and 7.1.1c (HP have 7.1.1c release notes up but IBM does not – to find Brocade version go to IBM’s download the firmware page that’s on Brocade.com and get the release notes from there). Also 3 years anniversary on this post on 2014-02-01!
2014-02-17: But be careful with 7.2.0b – IBM has a note on their 7.x page about 7.2.0b saying: “IBM recommends that customers not deploy FOS 7.2.0b if virtual switch capability is needed. Virtual switch users should migrate to an earlier version as soon as possible.
2014-03-17: The problem with 7.2.0b was likely DEFECT000491192 fixed in 7.2.0c and later also DEFECT000494570 was fixed in 7.2.0d. 7.2.0x seems a bit unstable at the moment. 7.2.1 is currently available for download via HP’s pages but not via IBM/Brocade’s. Also no release notes available. Archived 2013 updates.
2014-04-18: Added 6.4.3f and 7.1.1c and 7.1.2 is out. Updated migration paths a bit. The Brocade release notes of 7.1.x actually have a decent list of the migration path needed now. See the section “Recommended Migration Paths to FOS v7.1.2”.
2014-08-06: 7.2.1a, 7.1.2a, 7.0.2e. Updated some links that had gone bad (FOS Target Path) and made the “Show/Hide” Updates work again.
2014-09-28: 7.1.2b and 7.2.1b is out.
2014-10-01:  7.3.0a is out but can’t find any release notes for it.
2014-10-25: 7.2.1c
2015-01-18: 7.2.1d, 7.3.0c. “HP’s” release notes are too hard to find.. Added a note about FileZilla being a good ftp server. Thanks Harry Redl!
2015-02-20: 6.2.2g, 6.4.3g
2015-04-06: 7.3.1a from HP
2015-04-21: 7.3.1a from IBM
2015-06-19: Note about FileZilla being hosted off sourceforge – installer might contain malware.
2015-07-07: 7.4.0a, 7.3.1b, 7.2.1e. Removed link to HP’s webkey license page. Doesn’t work anymore. Note about BNA version required to manage Fabric OS v7.4 switches.
2015-08-31: 6.4.3g and 7.3.1b new revision of release notes. 7.2.1f, 7.4.0b
2015-09-01: 7.3.1c
2015-09-16: New versions of release notes.
2015-10-25: 7.4.1 is out for the brave and 6.4.3h (Fixes to OpenSSL CVE-2015-0286, CVE-2015-0288, CVE-2015-0289, CVE-2015-0292)
2015-12-05: 7.2.1g and 7.3.1d. Updated some links. Need to go through a lot of the HP ones here to point to HPE..
2016-02-24: 7.4.1b
2016-03-15: 7.3.2
2016-05-17: 7.4.1c
2016-08-13: 7.3.2a, 7.4.1d
2016-12-19: 7.3.2b, 7.4.1e

New Updates

2017-03-10: 8.x has been out for a while
2017-04-29: new links to Brocade FOS target path and better links for where to fetch firmwares
2017-05-03: 8.0.2b and added links to Upgrade Guides for 8.0.0 and 7.4.0)
2017-05-13: 7.4.2
2017-08-07: 8.1.0c
2017-11-09: 8.1.1a
2017-12-05: 8.0.2c
2018-01-01: 8.1.2a and 7.4.2b
2018-02-08: 7.4.2c and 8.0.2d
2018-06-15: 8.2.0a and 8.1.2d and 8.0.2e
2018-10-11: fixing some links, Brocade is now Broadcom so some links are not working anymore surprise. Some HP links no longer work so removed those too.
2018-12-07: 7.4.2d and 8.0.2f and 8.1.2f
2019-04-18: FOS Target Path on Broadcom.  From a reader got a link to NetApp’s Brocadeassist portal where newer firmware can be found than on IBM’s. Some more link updates and link to 8.2.1b
2019-04-19: More link fixes.  FOS 6.x – 8.x firmwares can all be downloaded from the brocadeassist portal.
2019-04-20: 8.1.2g and 8.2.1b on IBM release notes so updated links
2019-07-17: BlueChris in a comment found a nice HPE link to older Firmwares!
2019-08-23: 8.2.1c is on NetApp’s link but there are no release notes – I’d pass

Steps

  1. decide
  2. prepare
  3. upgrade

Decide

One major release at a time is required for the upgrades after 5.2.x, see details below at the release notes section.

If you have to upgrade many steps, you should upgrade to the latest in the series (or if it’s very new, probably safest to go with the second newest, just check the release notes of the newest to make sure nothing related is fixed).

If the switch is on 5.1.x you can go directly to 5.3.x.

What I usually recommend is this path:
5.0.1d -> 5.2.3 -> 5.3.2c -> 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.2d > 8.0.2f > 8.1.2g > 8.2.1b

It’s also possible to upgrade from a version earlier than 6.4.1b to 7.0.x or from 7.0.x to 7.2.x  – but this is a disruptive upgrade (meaning ports will go offline/online during upgrade). 

Brocade now has a document that describes a process of determining the ‘ideal’ version of Fabric OS you should be running. It is called Brocade FOS Target Path.

Yet one more official document to help is the Brocade Fabric OS Features and Standards Support Matrix, 8.2.x

There is also a section (Recommended Migration Paths to FOS ) in the release notes describing how to get to the release you’re reading notes for. In addition to these, there are Upgrade Guides from Brocade, at least for newer Fabric OS ( 7.4.0 and 8.0.0).

There are newer releases being released every now and then, in several series at the same time. You can think of it as releasing updates for Windows XP and 7 at the same time.
For example, in February 2011 6.4.1a and 6.2.2e were released by HP. You can see this on HP’s site if you look at the date next to the download. Quite often Fabric OS versions are not released by the OEMs at the same time, for example “Customer Notice of 7.1.0a release 25th of March 2013” HP released 7.1.0a before IBM.

Which is the recommended one? Usually it’s the latest one in the highest series that the switch supports. If you have storage from more than one vendor you may want to check with all and see if they all support the version you want to upgrade to. Vendors certify their equipment with different firmware versions. If you have a tape library, ask the vendor if they have a recommended / list of certified versions.

HP: HP B-series Connectivity stream (available in HP SPOCK).
Brocade: “Brocade FOS Target Path
Other: Contact them for their compatibility matrices, for example IBM, HDS, EMC, Fujitsu.
Brocade also has their own “Brocade Fabric OS 7.x Compatibility Matrix” which lists compatibility with other vendors.

You could in principle also say that (some blades in directors are excepted from these generalizations):

2G cannot upgrade to Fabric OS 6.x
4G and 8G can be on Fabric OS 6.x
All 4G except some 4/8 & 4/16 (that’s 200E) and 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

Do you want to use the latest one in each series? Probably.
Do check for published advisories and the release notes in the firmwares.
Some models or blades may work on 7.0.x and not on 7.1.x or vice versa.
Fabric OS 7.3.x supports all hardware that supports 7.2.x.
Basically you need to read the release notes for at least the version you are upgrading to, to confirm that it supports your switch.

Download firmware links:

If you go to downloads for HP’s 4/16 there is a link that also takes you to the older FOS firmware. If you don’t click through it also only have the firmware that this switch supports. So the latest on there at the moment is 6.2.2f.

On the link above you can also download HP’s branded NA (Network Advisor, previously known as DCFM – Data Center Fabric Manager), see notes about that below.

If you click on manuals on the left side you will also be able to download release notes and other guides and references.

5.0.x firmware can also be found at http://ftp.hp.com/pub/softlib/software12/COL22074/co-86832-6/FOS-Drawer_Statement.htm

6.x, 7.x and 8.x. can be found in the IBM and NetApp links.

Firmware Upgrade Order

You also probably want to decide on an order to upgrade the firmware on the switches.
It’s possible to do it via DCFM (now called Network Advisor, used to be something else) one switch at a time or even in parallel. I’d advice against doing it in parallel. One at a time and one step at a time seems the most cautious one. It’s not too bad to run a SAN with switches in different firmwares. One idea is to have all switches of one model on the same firmware. If you need to upgrade in several steps, do one step at a time.

Also, switches that are of higher importance like Principal Switch, Core Switches or Seed Switches for DCFM/NA. Should you start with these or perhaps start with another switch of less importance to make sure the upgrade goes smoothly?

With more recent firmwares (6.4 and 7.x) it’s possible to jump more than one hop – if you are ok with disruptions in the network. Nice if you need to upgrade switches that aren’t in production.

Release notes:

FOS  7.xIBM_Link& 8.x IBM Link

Brocade release notes in .pdf

5.2.3
5.3.1c
6.0.0c
6.1.2c
6.2.2g
6.3.2e
6.4.3h
7.0.2e
7.1.2b
7.2.1g
7.3.2b
7.4.2d
8.0.2f
8.1.2g
8.2.1a
8.2.1b (NetApp) & IBM

Notes from the release notes:

Upgrading from Fabric OS 5.0.x to 5.2.3 is supported
Upgrading from Fabric OS 5.1.x to 5.3.1a is supported, but upgrading from Fabric OS 5.0.x or a previous release directly to 5.3.1a is not.
Upgrading to Fabric OS 6.0.0b is only allowed from Fabric OS 5.3.x. (6.0.0c is a special upgrade version, only meant to be used in between firmware upgrades)
Upgrading to Fabric OS 6.1.2c is allowed only from Fabric OS 6.0.0b
Upgrading to Fabric OS 6.2.2f is allowed only from Fabric OS 6.1.0a or later.
Upgrading to Fabric OS 6.3.2e is allowed only from Fabric OS 6.2.0a or later.
Upgrading to Fabric OS 6.4.3f is allowed only from Fabric OS 6.3.x. You can upgrade non-disruptively from 6.2
Upgrading to Fabric OS 7.0.2 can be done non-disruptively from Fabric OS 6.4.1a or later.
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 (see the FOS_UpgradeGuide_v730.pdf and the Brocade Release notes).
Upgrading to Fabric OS 7.4.x can be done non-disruptively from 7.3.x. From 6.4.x with firmwarecleaninstall
Upgrading to Fabric OS 8.0.x can be done non-disruptively from any Brocade 16G (Gen 5) platform and all blades in the Supported blades table running any FOS v7.4 firmware. From 7.3.0 with “firmwaredownload -s”
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”.
Upgrading to Fabric OS 8.2.x can be done non-disruptively from Brocade platform running 8.1.0a or later. From 8.0.x disruptively with “firmwaredownload -s”.

About non-disruptively: This means you can go to 7.0.xfrom earlier  than 6.4.1a but ports will go offline during the upgrade.
See the release notes or Upgrade Guides for more details.

DCFM: Data Centre Fabric Manager / BNA: Brocade Network Advisor .

From 6.2.2a release notes:

With the introduction of Fabric OS 6.1.1, certain features and functions were removed from Web Tools (resident in the firmware) and migrated to the DCFM management application. HP recommends that, before you upgrade to Fabric OS 6.1.1x or later, if DCFM is not running on your fabric, you review the Web Tools functionality moved to DCFM, page 29 in these release notes and take note of what has changed so you can assess the impact on your fabric.

Fabric OS 7.x cannot be managed by DCFM 10.4 or BNA 11.0. You need BNA 11.1.0, see the release notes for 7.x.

Brocade Network Advisor 12.4.0 or later is required to manage switches running FOS 7.4.0 or later.
Brocade Network Advisor 14.0.1 or later is required to manage switches running Fabric OS 8.0.1 or later

Updates to documents

Sometimes Brocade releases updates to the manuals without actually updating the manuals. On HP’s page you can find them as “Documentation Updates”, “Fabric OS Administrator’s Guide Update”.

Fabric Watch and MAPS with FOS v7.3

Users running Fabric Watch for switch monitoring in FOS v7.3 are advised to convert to MAPS monitoring before upgrading to FOS v7.4. If you don’t, Fabric Watch will stop working.

Also the APM have been replaced with Fabric/Flow Vision.

Interoperability

See the release notes of the firmware for the specifics. For example Fabric OS 8.0.2 cannot be in the same fabric as for example HP C-Class 4/12 FC switches (4024) and one must use Fibre Channel Routing.

Prepare

Download old Brocade Fabric OS Firmware.

Basically, you need to update in steps.

To get FOS 5.2.1b and 6.0.0c firmware: Contact OEM Vendor or Brocade. I’ve found that two vendors have the firmware available online for free: HP and IBM, see below:
Eventually after looking around on HP’s old pages we found to http://ftp.hp.com/pub/softlib/software12/COL22074/co-86832-6/FOS-Drawer_Statement.htm this link sometimes changes.

Link to IBM’s page for downloading FOS 6 firmwares. This has firmwares going back all the way to FOS 2.6, it even has Fabric OS 6.0.0c and 5.2.3. On the page they have listed release notes and a little further down there is a link called “Release 6 Firmware”.
Actually, if you click on ‘Release 6 Firmware’ you are taken to a page on brocade.com where you can find many different firmwares, including 5.x and 7.x
IBM also have a link about FOS 7.x and FOS 8.x

Also note that some features does not exist/work on older Fabric OS. For example on Fabric OS 5.1.x DHCP and SCP may not work (which forces you to use static IP and ftp).

Equivalent Product Names

Page with the equivalent Brocade and HP product names.
Page with the model number as seen in switchshow and HP’s model and Brocade’s model. This is a good one.
Page for correlating IBM and Brocade product names.

Recommendations

HP recommend that you upgrade one fabric and one switch at a time.
Waiting a week or at least a couple of days after you upgrade the first fabric is a good idea – gives you time to see if anything went wrong, if you can fix it and if you can do anything different next time.
See HP SPOCK for more details in regards to compatibility and interop modes.
The HP B-series Connectivity Stream lists the recommended firmware and all the supported ones for each switch model. It also has a list of the supported SFPs. Find it by clicking on “Switches” in the left-hand navigation pane under the “Other Hardware” section. The Connectivity Stream is great and it is updated often so I will not link directly to it. You need an HP Passport to log on to HP SPOCK – it is free to create and you do not need a contract or product in warranty.

Other vendors have similar matrices. HP for example does not have a list stating which Fabric OS firmware is supported with which HP P6000 firmware. The idea is that you go with the general recommendation of Fabric OS firmware.

Do read the release notes for the firmware(s) you decide on: for example not all 4GB SAN-switches can run the 6.4.x FOS. The 8- and 16-port 4Gbps switches (Brocade 200E) do not run 6.4.x or 6.3.x.
Only 8Gb and 16Gb switches can run the 7.x.x FOS.
The release notes also have the fixes, enhancements, upgrade paths and supported switches.
Generally the Brocade versions of the release notes are more verbose when it comes to fixes, but if you have an HP branded it might be easier to use the HP one as that has the HP names of the products. Also it might be hard to find the Brocade release notes if you do not have a contract with Brocade. Other vendors (like IBM/Fujitsu/HDS) provide you with the Brocade version of the release notes. You can find the release notes from their support pages.

Do  consider updating OS patches, HBA drivers/firmware, management softwares and storage drivers/firmware. For example Qlogic had driver updates to their drivers that prevent HP blades from getting stuck in G_port after a reboot. Another for Qlogic FC cards was to not write a partition table on Dell servers at 2TB on the LUN (not so nice for > 2TB disks)..

Upgrading Tools

SANLoader is an unofficial HP tool to upgrade firmwares. With this you do not have to create an ftpserver etc. Contact HP Support, they may give this to you.
This is meant to be used when the other ways does not work, but it helps out a lot as you do not have to set up an FTP/SCP server.

Sanloader used to (winter 2010) not work well on Windows 7 and may not work flawlessly on the pre 6.x firmwares.

Other ways:

  • Set up a ftp/scp server and upgrade via the CLI (command line interface).
  • Use DCFM ( Data Center Fabric Manager – now called Network Advisory ) to upgrade firmware.
  • Firmware can also be upgraded through the web interface (click on switch admin and then on firmware download). You will still need an FTP/SCP server for this though. See the web tools admin guide page 73-74 (FOS 6.2.x but it hasn’t moved).

FileZilla is a free FTP-server that works well. There are many alternatives around. But unfortunately some don’t work sometimes (not 100% sure but probably combination of older FOS with older ftp client with FTP server that couldn’t handle that client) as listed in the comments thread in this post. FileZilla is however still on sourceforge so you may want to be careful about installing that – it might contain malware. Storing them on a Synology NAS works – thanks Henny!

For FTP clients:

  • /usr/bin/ftp in Ubuntu (also in Ubuntu on Windows)
  • WinSCP for a free opensource Windows alternative that does both ftp and SCP (and more).

For SCP any machine with Linux and sshd on should work. You can also get an scp-server running on Windows, OpenSSH would work. Both protocols are old, SCP is safer while FTP is sending data in clear text.

Personally I like doing this via the CLI. The Network Advisor way gives you the possibility to upgrade in parallel, but that’s also risky. If you use a Linux server to provide the firmwares via SCP don’t forget to let the switches in via firewall or tcp.wrapper ( /etc/hosts.allow ). If you do the upgrade via ftp – make sure that passive and active ftp both works.

How to access the SAN-switch

The most common way is to access the CLI of a Brocade switch by connect to the IP of it with an ssh- or telnet-client, PuTTy is the name of a free Windows client. If you are comfortable with CLI, Windows 10 has WSL and a good ssh and scp client built in. Telnet is unsafe so do try to use the ssh at all costs. Windows 10 has Bash which is in my opinion much nicer to use than putty.
It’s also possible to access the switch CLI via a serial cable, however as the firmware files are several 100MB (approaching 1GB for 6.4.x) that’s not really viable when upgrading firmware. Hyperterminal is a free windows tool that comes by default in some Windows versions. You can also use PuTTy for serial access.
To access the web interface just point the web browser to . It requires Java. The Java version that’s supported is listed in the release notes of the Fabric OS.

Upgrade

Here on HP’s Support Forum are some more notes about v6.x. Basic steps:

Note: version 6 does not require to specify the exact folder location SWBDxx: it just needs the root containing “the install” file

1) Unpack the downloaded firmware in the FTP or SCP download directory
2) Start the FTP/SCP Server and allow access
3) Connect to the CLI of the switch via telnet or ssh
4) Type this in the CLI: firmwaredownload
5) Answer all questions: when it asks for File Name be sure to write /v6.4.1b, that is the folder under which you find all the SWBDxx folders. Failing to do so makes it impossible to download the firmware
6) Wait for reboot of the switch and reconnect, check the firmware version with the “version” command

More notes about the upgrade

CLI Command to start the update process is firmwaredownload – this starts the interactive version, it is possible to specify user, directory, host directly via the CLI. See the Command Reference Guide for details. There are reference guides for each major Fabric OS release.

Specifying Directory

Please use forward slashes when specifying directories.

For example when you unzip the firmware file and it creates a sub-folder in the FTP-root that is called v5.3.1a then you need to specify /v5.3.1a as the directory.

For firmwares prior to 5.3.x you have to specify the release.plist – /v5.2.2a/release.plist.
However it says in the release notes for 5.2.3 that release.plist is no longer needed.

In some cases you may have to specify the sub directory.
For example the 4/16 HP Switch is a Brocade 200E with switchtype 34. So you would then use directory SWBD34 – /v5.3.1a/SWDB34. You can also try with /v5.3.1a/release.plist, /v5.3.1a/SWDB34/release.plist or /v5.3.1a/install. However with 5.3.1a you should not have to so /v5.3.1a should be enough.

firmwaredownload example:

switch:admin> firmwaredownload
Server Name or IP Address: IP.TO.SCP.SERVER
User Name: username
File Name: /path/to/v6.2.2e
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 3
Password:
Server IP: IP.TO.SCP.SERVER, Protocol IPv4
Checking system settings for firmwaredownload...
System settings check passed.
You can run firmwaredownloadstatus to get the status
 of this command.
This command will cause a warm/non-disruptive boot on the switch,
 but will require that existing telnet, secure telnet or SSH sessions
 be restarted.
Do you want to continue [Y]: y
 Firmware is being downloaded to the switch. This step may take up to 30 minutes.
 Preparing for firmwaredownload...
 Start to install packages...
 dir ##################################################
 [[lots of these for all packets]] ##################################################
 [[also stuff like these are seen many times:]]
 warning: /etc/fabos/pki/switch.0.rootcrt created as /etc/fabos/pki/switch.0.rootcrt.rpmnew
 kernel-module-ipsec ##################################################
 Removing unneeded files, please wait ...
 Finished removing unneeded files.
All packages have been downloaded successfully.
 Firmware has been downloaded to the secondary partition of the switch.
 HA Rebooting ...

Transfer Protocol and Connectivity

If you are using SCP and that does not work, please try with FTP. If neither works, see if something else can log on to the FTP/SCP server. And of course, make sure the right permissions/root directory are set on the FTP-server. If your FTP/SCP server has log files, check them. If it works from one client but not from the switch, check the logs and see if there’s a difference. Sometimes if the SCP doesn’t work via CLI it might work by doing SCP (but starting it from the Web Tools, thanks Eric in the comments for this!).

If you are logged on as root on the SAN-switch you can use the scp- or ssh-client on the switch to confirm connectivity, like this:

ssh username@server ls /tmp/v6.0.1a to list the /tmp/v6.0.1a on the SCP server.

You need to be root to run the above command.

If that also does not work, you have some kind of networking problem – you can try direct connecting a laptop to the LAN interface of the switch. To see the network settings on the switch: ifmodeshow and ipaddrshow

Passwords

Sometimes when upgrading from 6.1.1d to 6.2.2 we have seen that the passwords have gotten reset.

Default password is then “password” or “fibranne”.

You can reset the password with the CLI command “passwd admin” to reset password on the admin account.

If you forget all passwords it might be possible to be able to reset it via the serial cable interface while booting the switch.

On EMC branded switches the default password might be: Serv4EMC

CF Cards

If your switch is out of warranty/contract and it’s still working. I’d suggest making a copy(dd  in linux for example) of the CF-card. Then if the CF card decides to fail you can just get a new one from random_electronic store and dd the contents of the flash back.

Licenses

When replacing a switch make sure that the licenses are correct.
If for example you have a switch with ‘power pack’ – then for HP there is a special spare part number for a switch with power pack and one without. Power pack is a grouping of licenses,  which licenses are in the pack differs between models.

198 thoughts on “Brocade SAN Switch Firmware Upgrades

  1. Holly Helmick

    This document/posting was excellent! I am preparing to perform a switch upgrade this weekend and getting this information from our local HP representative was like pulling teeth! Thank you very much for this helpful post!

    Reply
    1. guldmyr Post author

      Excellent :)

      Glad to hear that you like it!

      Was there anything you found unclear or missing? I haven’t given the structure of the post much thought :p

      I try to keep it updated but as I don’t do the upgrades that often anymore it’s easy to miss new stuff :)

      Reply
    1. guldmyr Post author

      Hey!

      The IBM version of 6.3.1b is 866 MB (909 037 568 bytes) while the HP one is
      866 MB (908 955 648 bytes).
      The IBM version you actually download through a brocade page.

      In the HP one there are two extra files regarding GPL license and the EULA:
      ancillary.txt
      EULA.pdf

      Everything else is the same.

      This leads me to believe that you can use the firmware files from HP for other switches too.

      Reply
      1. Tom

        To my knowledge there is some slight modifcations to the HP firmware image, so file size might be similar. But default settings like “In Order” delivery and the DLS option for example could be different between the HP image and another Vendors image. So loading the HP image could change these settings. So its worth downloading the firmware image from the OEM vendor.

        p.s found your site while searching for something on Virtual Rooms :)

        Reply
        1. guldmyr Post author

          Welcome Thomas ;)

          If you have the possibility I’d for sure always go with the OEM one.
          But I guess one instance when you’d consider one that’s not your native one, is when you’re out of contract/warranty.

          Silly vrooms on rhel is not my best friend.

          Reply
  2. Pingback: HP’s Brocade firmwares compatible with other switches? | Home

  3. Rizal

    Hi…can i do firmware upgrade to v6.4.2a on existing brocade switch? Do i require to save current config before the upgrade? Thx..

    Reply
    1. guldmyr Post author

      Hi!

      It depends on which switch you have. Which kind do you have? You can see in the release notes if you can upgrade your switch. For example 8 and 16 port 4Gbps SAN switches you cannot upgrade to 6.4.2a. Neither HP’s 4gig blade c-class SAN switches.

      Why not get to 6.4.2b while you’re at it? There were some fix there for ISLs I think..

      You do not have to save the config. But it is a good idea to save it and also save a supportsave before, just in case.

      Reply
  4. Jason

    Thanks for this site, it really helps. In our environment, we have Brocade 4100 (SAN Switch 4/32) with fw 5.3.0. I read the release notes for 5.3.1a but am unable to find a download for it. Is it safe to upgrade from 5.3.0 directly to 6.0.0c or should we upgrade from 5.3.0 to 5.3.1a first? Thank you for any feedback you could give.

    Jason

    Reply
    1. guldmyr Post author

      Hey Jason, glad you like it!

      Should be safe to go from 5.3.0 to 6.0.0c, if you want to be on the double-safe side you could read through the release notes of later releases in the 5.3.x series..

      I should go over the links and path again.

      There is actually a newer/better firmware to use than 5.3.1a.
      It’s 5.3.2c and you can find that in the HP and IBM. On the IBM link it says “Release 6 Firmware” but there is also 5.3.1a. But 5.3.2c will work too.

      Reply
      1. Jason

        The HP link helps but I see in the release notes that the 5.3.2 firmware (b & c included) does not support the 4/32 switch. Still looking for the 5.3.1a download. With all these upgrade paths we’re leaning toward having HP come in and do it…lol. Our issue is that we need to upgrade all this in order to install 600 GB drives into our HP StorageWorks SAN. Thanks again.

        Reply
        1. guldmyr Post author

          I am really surprised you need this to get 600GB disks in your HP array. Is that an EVA3000/5000?
          I presume that your SAN has been stable for a long time, but I guess it’s from a support perspective.

          I just did an upgrade in a SAN with 13 switches in each fabric. We just put the firmware on a linux server and started the upgrades from CLI. It’s not so difficult, it just appears that way and it does take a bit of planning.

          Reply
          1. Jason

            I guess in my comments I was referencing the SAN Switch firmware but we’re trying to get all of our firmware updated. HP installed our SAN system 3-4 years ago and we haven’t updated anything (mostly in fear of breaking something).

            Currently we have this setup in our environment:
            EVA6000 (2 x HSV200) – XCS version 6.1 (6100)
            HP Command View 8.0
            SAN Switch 4/32 – version 5.3
            24 x 300 GB disks – with firmware HP04

            The note that came with the 600 GB drives said that XCS 6.11 or later is required. I read somewhere about problems with 6.11 so we plan to try and update the firmware to 6.24 since its the newest. As for the SAN Switch, I couldn’t find what version is compatible with XCS versions so we figured we need to update that firmware too. Since there is no much that needs updated we might get HP’s help in doing this. I know the basics but we have so many users at our location that we don’t want to cause problems.

            Reply
            1. guldmyr Post author

              Totally understandable. There’s a lot to upgrade. CV needs to be upgraded before you can get to XCS 6.240 for example. HBA firmwares and drivers perhaps as well while you’re at it =)

              Definitely a good idea to get HP to do it as there is a lot to consider. Maybe first an inventory and then upgrade one fabric at a time?

              Yeah HP don’t have a compatibility between the brocade firmwares and the EVAs. They just go with the latest :p

              Reply
                1. Jason

                  One last question for ya as I can’t find this anywhere online:

                  Does the SAN Switch 4/32 have to be at a certain firmware level in order to be compatible with HP Command View/EVA XCS software? Currently we have Command View 8.0.2 installed, which is compatible with XCS 6.22. If we currently just update from 6.1 to 6.22 now, does the SAN Switch firmware (5.3) need to be upgraded? It might save us.

                  Thanks again!

                  Reply
                  1. guldmyr Post author

                    You can ask as many as you want :)

                    There is no “does this FOS work with this XCS” compatibility matrix. At least last time I checked. All there is is a “which XCS is supported” and “which FOS is supported”. Which generally is the latest one and a couple of previous ones.

                    There are good fixes in 6.240 that you do want. Also in later versions of CV. 6.220 is pretty old. It’s not always a matter of compatibility. I think primarily it’s a matter of support. They have to eventually stop testing new releases with really old versions.

                    If you stay on these old versions maybe HP won’t give you support?

                    Reply
    1. guldmyr Post author

      Hey Jason.

      HP StorageWorks 4/32 SAN Switch (Brocade 4100) is supported on 6.4.x.
      You don’t _have_ to go to 6.0.1a. Any in 6.0.x series is OK. But you need to take the steps.

      You can see in release notes for 6.4.x that recommended version for 4/32 is in 6.4.x series. Like here: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=3742051&swItem=co-90276-1&prodNameId=3742052&swEnvOID=54&swLang=8&taskId=135&mode=4&idx=0

      Reply
  5. Bryan

    Fantastic article!!!
    Are these upgrades truly non-disruptive? Looking at the path I need to take it seems to me it is going to take all day just to upgrade one switch in my environment. Also do you know if Brocade is going to make this process better, without the interim upgrades?

    Reply
    1. guldmyr Post author

      Thanks Bryan!

      Well, some switches are faster than others, for example embedded/blade switches are slower than standalone ones.
      The whole firmwaredownload is a long extract process so the newer ones with more powerful processors are faster.
      But maybe 20-25 minutes per upgrade is probably not too far off.

      Yes, they are non-disruptive (meaning ports should not change state).
      If you have two fabrics you are extra safe and it’s particularly useful for when doing upgrades.

      I suppose they entered this scheme to be able to limit the amount of versions they need to test upgrading from when they release a new firmware. So based on that I doubt they will change this scheme, but it appears that FOS 7.0.0 is less strict when it comes to upgrades, so maybe they will be more lenient in the future!

      Reply
  6. Nick McClintock

    Hi,

    Awesome blog as a start :) Now this is long but at a minimum you will get a laugh somewhere along the way.

    If I may ask a few questions? We have just about completed a 4 week firmware upgrade process of well over 100 HP C Class Blades (1700 VM’s) and 4 HP EVA 6400’s across two data centres and this weekend are embarking on the final stage of the firmware update process, HP Virtual Connect, On-board Administrator (4 x Stacked VC Enclosures), 4 x Brocade/HP AM686A Switches and finally 2 x HP EVA 6400.

    Or switches are ISL’d in a 2 x 2 config, all with 6.4.1a on both the Primary and Secondary partition. We had a nightmare failure when HP did the upgrade to this version as we were told it was 100% online however there were small drops in connectivity and this played havoc with most of our Citrix XenApp farm servers, Windows and Hyper-V Servers were fine. As to why we are still unsure.

    But we moved on and decided that the word Firmware was a swear word and not to be used for a few months.

    We are a 24 x 7 x 365 media company that has a reliance on 98% uptime so downtime is not really an option for us. However, because of the issues last time we have managed to get sign off to bring down our entire primary environment and fail most, but not all, critical services over to our geographically separated secondary environment to ensure this works for us and we don’t go through what we did last time.

    So that’s the background and my questions are as follows.

    1. What version of firmware do you believe we should be moving to? Keeping in mind that our Mission Critical Support suggests staying away from the latest versions, however we are starting to lose confidence in their decision making processes and they have suggested v7.0

    2. In an ISL setup do you only need to update the primary switch firmware and the firmware is then updated on the rest of the switches in the fabric via the ISL link?

    2. Is there anything special that we need to consider in regards to the switch ISL links? Do we break them and update, just update the primary switch and let the updates replicate to the others or do all 4 individually?

    3. If we are doing the updates via SANLoader is it true that this will update both the primary and secondary partition on the switches at the same time? This does not seem correct, as would this not offline the ports at some point? I thought the whole purpose of the primary and secondary partitions was so you could have 2 different versions and swap between them if there were issues or are these simply for zoning?

    4. What order would you recommend we do the updates in? VC then switches or the other way around?

    5. is there a specific process to follow in regards to ordering when applying the firmware. i.e 4 switches in a 2 x 2, start at 4 then 2 and let the ISL do the rest or something different.

    I think that is it…….. I think………

    I know enough to be dangerous but I manage get through with lots of reading and my good friend Google and I am always learning, however my concern comes from the fact that we are 2 days out and our Team Lead is still asking questions like the ordering process of applying the updates. I’d like to try and avoid a 48 hour day fixing issues because we were unprepared.

    So any help is good help and apologies if I have TOTALLY got some of this wrong it’s very off the cuff and I’m still new to the whole fibre environment.

    Regards,

    Nick

    Reply
    1. guldmyr Post author

      Hey Nick!

      Glad you like it :)

      Nice setup you got there!

      I cannot find which switch the AM686 is, it sounds to me like a Director / DCX?
      I have seen issues with a cluster behind a c-class 4g virtual connect during SAN switch firmware upgrades too (other ‘real’ san switches had no issues).
      The VC modules in question were not upgraded before the SAN fw upgrade.

      1) 6.4.2b appears to me to be stable (if you discount vc modules during an upgrade). 7.x is still quite new and personally I would be hesitant to upgrade firmwares if they don’t have a fix in them that I really want. But maybe it has some features that you want? You’ll need DCFM/BNA 11.1 to manage FOS 7 switches.
      2) No, you need to upgrade all switches. (individually by logging on to each switch and hit firmwaredownload or via other means like dcfm/bna or sanloader)
      2a) I’d advise against touching the ISLs. Firmware / Fabric OS is not automagically distributed between switches.
      3) I haven’t used or seen anybody use SANloader to upgrade a director. Also I don’t have access to it anymore so don’t know which arguments you can send. If you want to have both belt, lifeboat and suspenders, consider doing it via CLI and firmwaredownload -s or even firmwaredownload -n and there at least you can specify to only upgrade one partition at a time.
      4) Upgrade the VC first (make sure to upgrade each component in the c-class in the right order, so you only got the VC and the OA left, do you upgrade the VC before the OA? HP forums have the answer http://h30499.www3.hp.com/t5/HP-BladeSystem/Blade-System-Firmware-Updates/m-p/5302291/highlight/true#M17500 — OA before VC). But I haven’t gone through the VC release notes if there is some kind of compatibility/requirement on newer VC with newer FOS.
      5) Not sure I understand your question. But, do one fabric at a time and one switch at a time. If you have the possibility I would then wait a day or three to make sure that fabric is stable before doing the second one. But with your downtime requirements maybe only a couple of hours are available. It sounds a little bit safer to me to upgrade the principal switch last in each fabric.

      You can use ‘fabriclog -s’ in the CLI to see what happens on the fabric/switch after an upgrade.
      Run supportsave on all switches before. Why not supportshow and configdownload as well, to be extra safe.

      Glad to help, if you got any more questions feel free to ask!

      Reply
      1. Nick McClintock

        Man, not sure where I got that Switch Model from but im sure that I googled it to make sure I had it right but guess what….. Nope way off we have Brocade SLKWRM 300’s. Make more sense? Hopefully that does not change anything?

        Reply
        1. guldmyr Post author

          Hey. ah okay, no the approach works for B300 as well.

          There’s so many different names, some other vendors than HP call them something with 300 inside the name so you can guess. HP also have another name for the B300: 8/8 and 8/24 :)

          With the B300 you cannot use “firmwaredownload -s” because it only has one CP. That should be the only difference. You can still use “firmwaredownload -n” and then “firmwarecommit” when you’re ready to copy the firmware over to the other partition.

          Reply
  7. brian

    Hi, do you know what are the differences between the various letters in the firmware, for example 6.4.3b and 6.4.3c or a g at the end (like 6.2.0g) I have a EMC branded brocade switches, and so far the HP images worked fine, but Im wondering what these versions mean. thanks!

    Reply
    1. guldmyr Post author

      Hi Brian, different letters at the end mean that they are different releases. A comes before B, so 6.4.3a is older than 6.4.3b.
      In the release notes you can see what is the difference between the two releases. Generally I’d say that the major difference between letters are fixes. New features, older switches becomes unsupported, these kind of things comes in changes from 6.3 to 6.4 for example.

      Reply
  8. Fernando

    Hi,
    First of all, very nice article!!!
    I´m planning to go to FOS 6.2.2b from 6.0.0c
    On 5480 – 4024 – 4012 Brocades models.

    could you please tell me how many and wich previous steps I should take before to reach 6.2.2b version?

    thanks in advance.
    Fernando

    Reply
    1. guldmyr Post author

      Hi!

      Thanks a lot, and welcome to the post :)

      Why are you not going to upgrade to 6.2.2f? There has been quite a lot of fixes in 6.2.2c,d,e and f. Check out the release notes above in the post. Also 6.2.2f has been out for a long time, it was released by HP in February last year. I’d say that means it can be considered stable.

      Anyway, the procedure to go from 6.0.0c (which you’re not supposed to be running for a longer period of time..) to 6.2.2b/f you need to take a stop at a firmware in 6.1.x first, for example as 6.1.2b.

      Reply
  9. Fernando

    Thanks for the response!
    We are going to version 6.2.2b because we need to connect to a new EMC VMAX Storage, and EMC vendor recomends go to that version, so we need to do that (is the customer request)
    I get on a brocade manual we need to take this steps:
    6.0.0c –> 6.0.1a -> 6.1.2b -> 6.2.2b
    You said that is no need to do 6.0.1a stop from 6.0.0c, and go directly to 6.1.x and then 6.2.2b?

    Reply
    1. guldmyr Post author

      If you don’t specify in which manual you found the information in, how can I verify it?

      I wrote about the path for these upgrades in the article above. Did you not find the information there? Was it hard to find it? Is there anything I can do to improve the article?

      Read the release notes for 6.2.2b, it will tell you which version you need to run at a minimum to upgrade to it. Then you can trace your steps backwards until you’re in 6.0.x.

      6.2.2b was released in April 2010.

      Reply
  10. Paul

    Thanks a lot for this. I have been in contact with HP support for instructions on how to upgrade firmware with no luck, their descriptions where not clear enough. But when i have read your blog it was no problem to upgrade the firmware. Thanks for easy and understandable information.

    Reply
  11. Nathan

    Hey, great blog and full of useful information. I just would like to get your clarification on the actual impact of performing the stepped upgrades to get to a current FOS.

    I have a pair of IBM 2498-B24 that are currently running 6.1.1a. I have just installed a second set of switches that we will need to interconnect that are HP 8/24 and are running the current 7.1.1b FOS release. The plan is to upgrade the IBM to 7.1.1c and then join them together. I was planning on running the upgrades as per your instructions (and versions) above starting with an upgrade to 6.1.2b and then 6.2.2f then 6.3.2e then 6.4.3d then 7.0.2c and finally 7.1.0c

    Are you able to confirm if hosts will have any fibre outages as a result of these stepped upgrades (assuming nothing goes wrong)? I am not 100% confident in the multipathing that was configure prior to me arriving into this environment.

    Is the process supposed to be performed with hosts online?
    Thanks for your help!

    Reply
    1. guldmyr Post author

      Hey Nathan, glad to have you here, thanks for your comment and questions!

      Did you mix up 7.1.1c and 7.1.0c and 7.1.1b and 7.1.0b? =) No big difference in terms of upgrading anyway.

      If you always do the upgrades to the next major version from a supported firmware, the upgrade should be non-disruptive and should not cause any problems for the hosts. Some operating systems are more pickier than other. I’ve also seen problems caused for hosts behind HP virtual connect (old firmware on the VC modules) during a Fabric OS upgrade (but not for any other hosts in the quite big fabric).

      Yes, the process is supposed to be performed with hosts online.

      You do not have to go to 6.1.2b before going to 6.2.2f. It says in the release notes that you can get to 6.2.2f from 6.1.0 or later. So that saves you one jump :)

      Generally it’s the second digit that should only increment by one. I put in the latest version of the FOS, but if you’re already on the 6.1.1 you do not have to go to 6.1.2 before going to 6.2.x.

      It’s a bit hard to check out the multipathing setup I suppose, at least on the SAN side it could be done, perhaps at least for your most important hosts. If there are sensible aliases for the WWN in the switch-config you could check if the hosts are present on both fabrics for example and make sure the ports are up. Then on the OS side it varies between OS, ‘multipath -ll’ on linux is a good first stop.

      Hope it works out well for you! If you have more questions I’m right here :)

      // Johan

      Reply
  12. Nathan

    Thanks Johan, much appreciated, Yes, got that wrong twice! I did have another thought about this, as I have not performed a major version upgrade in the past; do I need to regenerate any licenses for the switches when moving from 6.x.x to 7.x.x ?

    Reply
    1. guldmyr Post author

      Hi Nathan, I’m on midsummer fest now during the weekend without a computer.
      We didn’t have to do anything about licenses when the switches that could go to 7.x were upgraded. You can check the release notes for more information. Also probably good to double check that your B300 support the 7.x FOS.

      Reply
  13. Nathan

    Thanks for the follow-up. I completed the updates over the weekend and everything went very smoothly! Thanks again for you advice and assistance!

    Reply
  14. Mike

    I am preparing to migrate to HP8/80 SAN switches with 6.4.1a installed. I want to upgrade the OS before I attached the fiber. I am attempting to upgrade to 7.1.0b. I have attempted upgrading strait to the new version and also stepping up to it by using v7.0.x. Neither way works. I keep getting “cannot access release list (.plist)”. I am downloading the firmware file from HP website.

    Reply
    1. guldmyr Post author

      Hi,

      to skip 7.0 you’d have to add a “-s” as an argument to the firmwaredownload command.

      If your switch cannot access the release.list then perhaps you haven’t extracted the firmware or there is some tcp/ip network issue between the switch and the where the firmware is stored.

      Reply
  15. cj

    Hi, first off all thanks to guldmyr for this blog – this is why google works :)

    To update this great blog with latest information:
    Upgrading to Fabric OS 6.2.2f is allowed only from Fabric OS 6.1.0a or later.
    Upgrading to Fabric OS 7.0.2c can be done non-disruptively from Fabric OS 6.4.1a or later
    Upgrading to Fabric OS 7.1.1 can be done disruptively from 6.4.x. Non-disruptively with Directors from 7.0.x

    “HP recommend that you upgrade one fabric and one switch at a time. Do read the release notes for the firmware(s) you decide on: for example not all 4GB SAN-switches can run the 6.4.x FOS. The 8- and 16-port 4Gbps switches (Brocade 200E) do not run 6.4.x or 6.3.x.
    Only 8Gb and 16Gb switches can run the 7.x.x FOS.

    Reply
  16. Q123we

    We are at 6.4.2a and plan to jump to 7.0.0d on IBM 2498s. When the firmware is extracted there is no release.plist file. Is this required at this level or do I need to select a subdirectory off of the v7.0.0d directory?

    Reply
  17. Troy

    Hi, Great Post,

    I have a Dell PowerConnet B-8000 that does not have a compact flash card in it,(was removed before I purchased it) so no way to Upgrade, How would I go about getting FOS on to a new CF in order to fully boot the unit.

    Thanks for any help

    Reply
    1. guldmyr Post author

      Hi, thanks!

      I’d say get or copy the CF from another switch.
      They might be available as spare parts, perhaps you could contact Dell for some details about that.
      I presume you got a new empty CF?

      Reply
  18. Troy

    Wow,

    Thanks for the fast response, I do have a new 1gb CF
    I usually refurbish Cisco equipment and this is new to me.
    I do not have another power connect to get the files from and I do not even know what files i need exactly, But I really want to figure this out not only to be able to do the resale on it but also so I will know what to do If and when this comes across my desk again.

    I did download a Zip file called v6.2.2f if I just copy that to the CF will that allow a full boot to then Config / Upgrade from there or would I TFTP Download all the files in Zip to CF.
    I am just not sure what to do, Not as easy as a Cisco Switch that I normally do.

    Thanks again for all the help

    Reply
  19. Troy

    Oh I am sorry for not addressing that Dell support Comment,
    I did contact dell support and since the switch is out of warranty they can not help so I am basically on my own to figure this out.

    Thanks Again

    Reply
    1. guldmyr Post author

      Sucks about Dell!

      Perhaps there are resellers of Dell hardware that can help find the right part? But yeah, at least with HP you cannot buy parts from them. And with spare parts you gotta give the broke none back…

      As I haven’t looked at the CF closely I can’t tell you how it should look, but I believe the switch boots from the flash card.

      Some questions and thoughts I have:
      How many partitions should it have?
      Which filesystem?
      Are there other files on it than just the firmware? (For example, boot loader, MBR).
      If it runs a standardish Linux then /boot or /etc/fstab would be good to have. Are those in the firmware?

      Would be nice to have a switch to play with :)

      Reply
      1. guldmyr Post author

        On this note, I’ve started a hunt for a switch to play with.
        No promises but if I do find something I may blog about it :)

        Reply
  20. Eugene

    Thanks for a great write up.

    I have a couple of questions for you. We have the following switches:

    300 / fw 6.2.0d (fabric A; fw 6.2.1.b in fabric B)
    4024 / fw 6.1.0c (same version i fabric A and fabric B)
    5480 / fw 6.2.0d (same version i fabric A and fabric B)
    5000 / fw 6.2.1.b (same version i fabric A and fabric B)
    5100 / fw 6.3.2d (same version i fabric A and fabric B)

    Our goal is for a non disruptive upgrade to 6.4.3e (or whatever latest 6.4.x fw) on all switches. Per HP we need to be at 6.4.x for peer motion to work from EVA to 3PAR.

    Just want to confirm based on your post that to update say our 5000s we’d have to go from 6.2.1b -> 6.3.x -> 6.4.x and so on and then repeat the same on the other other switches starting with the one version above 6.x that each switch is currently on.

    Also you mentioned in your article that some switches don’t go to 6.4.x and included 300s and 4024s in there but I see that 300s look to be supported by 6.4.3e. I’m not seeing 4024s listed in release notes so that’s going to be a problem for us.

    Reply
    1. guldmyr Post author

      Hello and welcome :)

      Ah you are right, B300 does support 6.4.x thanks for finding that, I’ll update the page with that it’s the 200E that doesn’t support 6.4.x

      Your plan looks good.
      True, upgrading them all to the next major revision at a time is a bit painful. But with an SCP/FTP server it is not that bad.
      It’s also possible to do the upgrades in DCFM/BNA. I prefer the CLI over than big java applications.

      The 4024 can be upgraded to 6.2.x.
      The 4024 are compatible with switches running 6.4.x, this can be seen in the “Supported Products and FOS interopability” table in the 6.4.3e page 15 of Brocade’s version release notes.

      // Johan

      Reply
  21. Eugene

    Cool thanks.

    So since 4024 and couple of the others are c7000 Bladesystem switches do you know if there are any pre-requisites for updating any of the associated fw in the chassis? I’m trying to avoid all of this because basically all of the fw in the c7000s is pretty old and our goal is to migrate off of these without downtime i.e. via storage vmotion for VMs and peer motion for windows hosts. The only reason we’d be doing any updates at all is per HP’s peer motion requirements.

    Reply
    1. guldmyr Post author

      It’s ok to do them without upgrading OA, iLO, BIOS or drivers :)
      HP might tell you otherwise if you ask which is the supported way. But I’ve upgraded FOS only on c-class 4G FC switches without any issues.

      Reply
  22. Paul

    I’ve upgraded over a thousand Brocade switches of all varieties and I still refer back to this blog as a great reference for target FOS Upgrades for older than 5.x versions. Thanks for that!

    And to those who are using EMC. Reuqest an RPQ to have them support v6.2.2f. Brocade supports it as their target version so we had them agree to support it as well. Don’t let EMC tell you what versions you need to be on for Brocade switches. Brocade knows far better.

    Reply
  23. Pingback: Merry Christmas Readers • Blog Archive • Home

  24. Nicke

    Hei,

    We tryed to upgrade Brocade 4/12 SAN Switch(AE370A) from fw 5.3.0d to 6.0.1a. All went fine but when we want to upgrade to next version the switch reports that firmware is beeingdownloaded and we cannot do anything see the log:

    Wed Mar 12 19:40:07 2014 Firmware is being downloaded to the switch. This step may take up to 30 minutes.
    [1]: Wed Mar 12 19:45:53 2014 Firmware has been downloaded to the secondary partition of the switch.
    [2]: Wed Mar 12 20:04:51 2014 The firmware commit operation has started. This may take up to 10 minutes.
    [3]: Wed Mar 12 20:09:38 2014 Firmware commit failed – Firmwarecommit failed. (0x1a)

    Do you have any idea wht we can do to fix this ?

    Reply
  25. Nicke

    Hello

    Sorry but it didn´t help. Thesse errors will be in teh log when we try the firmwarecommi command:

    rsync: readlink “/mnt/fabos/share/SWBD51_test_list” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_10port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_20port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_id.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_retimer.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/idcode_condor.xsvf” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/lbist_condor.xsvf” failed: Input/output error (5)
    rsync: symlink “/mnt/fabos/share/SWBD51_test_list” -> “SWBD43_test_list” failed: File exists (17)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer2_10port_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer2_20port_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/icecube_vpddata_id.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/icecube_vpddata_retimer.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/idcode_condor.xsvf”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/lbist_condor.xsvf”: Input/output error (5)
    rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
    Failed to synchronize the partitions (0x1700).

    Nicke

    Reply
  26. Nicke

    Yepp, we think so. We tried to copy a new flashcard from another switch but we dident get the broken switch to start from that card, could it be the licens file or ?

    Reply
  27. Nicke

    Yes we used dd. Fortunately I took a image of the card before I copied the card from the other switch. I restored that image and I’m back to square one. I suppose why the switch did not start was because the license file did not match what the hardware expected. So if I can find the switch license file, copy that into a working image I should get the switch back and try a new upgrade.

    Reply
  28. Nicke

    Ok, switch A has 5.3.0d software and is ok. Switch B has the failed upgrade to 6.0.1a.

    Took a copy of switch A with dd, and wrote that on switch B CF card, booted log says:

    The system is coming up, please wait…
    Read board ID of 0x8c from addr 0x23
    Read extended model ID of 0x1c from addr 0x22
    Matched board/model ID to platform index 10

    Read board ID of 0x8c from addr 0x23
    Read extended model ID of 0x1c from addr 0x22
    Matched board/model ID to platform index 13
    Checking system RAM – press any key to stop test

    Checking memory address: 00100000

    System RAM test using Default POST RAM Test succeeded.

    Press escape within 4 seconds to enter boot interface.
    Booting “Fabric Operating System” image.
    Blk map has an invalid version 16908544
    Blk map has an invalid version 16908544
    ThisOSLoader has an invalid magic number (0x419E0038)
    ThisOSLoader has an invalid magic number (0x419E0038)

    Exception raised!

    Vector SRR0 SRR1 CSRR0 CSRR1 DEAR ESR MSR
    FFC40200 FFC77E80 00029000 FFC8102C 00029000 FFFFFFEF 00000000 00000000ÿ

    Reply
  29. Nicke

    This is the log from the serial port when booting switch B with the failed upgrade (or partially failed), the commit to the secondary partition fails and the upgrade is never finished:

    The system is coming up, please wait…
    Read board ID of 0x8c from addr 0x23
    Read extended model ID of 0x1c from addr 0x22
    Matched board/model ID to platform index 10

    Read board ID of 0x8c from addr 0x23
    Read extended model ID of 0x1c from addr 0x22
    Matched board/model ID to platform index 13
    Checking system RAM – press any key to stop test

    Checking memory address: 00100000

    System RAM test using Default POST RAM Test succeeded.

    Press escape within 4 seconds to enter boot interface.
    Booting “Fabric Operating System” image.
    Entry point at 0x01000000 …

    loading kernel

    loaded at: 01000000 013F8364
    board data at: 013F6324 013F6364
    relocated to: 01005110 01005150
    zimage at: 0100597D 0116ACFF
    initrd at: 0116B000 013F5C00
    avail ram: 013F9000 10000000

    Linux/PPC load:
    BootROM command line: quiet
    Uncompressing Linux…done.
    Now booting the kernel
    PCI: Cannot allocate resource region 0 of device 0000:00:00.0
    Installing Linux 2.6 Kernel
    Attempting to find a root file system on hda2…
    INIT: version 2.78 booting
    Bypassing firmware validation.
    — Partition /dev/hda1 is inconsistent.
    — Its content will be restored to be the same as that of /dev/hda2.
    — Please check the version and re-load firmware if necessary after the system boots up.
    INIT: Entering runlevel: 3
    uptime: 4293889521; sysc_qid: 0

    2014/03/25-03:50:32, [HAM-1004], 151,, INFO, SilkWorm4024, Processor rebooted – sysshutdown

    Fabric OS (swd77)

    swd77 console login: SNMP Research EMANATE/Lite Agent Version 16.2.0.9
    Copyright 1989-2006 SNMP Research, Inc.
    sysctrld: all services Standby
    sec0: Security is initializing……..
    sysctrld: all services Active
    POST1: Started running Tue Mar 25 03:50:44 GMT 2014
    2014/03/25-03:50:44, [IPAD-1000], 152,, INFO, SilkWorm4024, SW/0 Ether/0 IPv4 DHCP 192.168.192.109/24 DHCP On
    2014/03/25-03:50:44, [IPAD-1001], 153,, INFO, SilkWorm4024, CP/0 IPv4 DHCP 192.168.192.5 DHCP On
    POST1: Test #1 – Running turboramtest
    Firmware commit operation has started to restore the secondary partition.
    POST1: Script PASSED with exit status of 0 Tue Mar 25 03:50:46 GMT 2014 took (0:0:2)
    2014/03/25-03:50:47, [SULB-1003], 154,, INFO, SilkWorm4024, Firmwarecommit has started.
    Validating the filesystem …
    POST2: Started running Tue Mar 25 03:50:48 GMT 2014
    POST2: Test #1 – Running portloopbacktest (TXRX INTERNAL)
    POST2: Running diagshow
    POST2: Script PASSED with exit status of 0 Tue Mar 25 03:50:59 GMT 2014 took (0:0:11)
    2014/03/25-03:50:59, [BL-1000], 155,, INFO, swd77, Initializing ports…
    2014/03/25-03:50:59, [BL-1001], 156,, INFO, swd77, Port initialization completed.
    Repairing the secondary partition now.
    Please wait …
    rsync: readlink “/mnt/fabos/share/SWBD51_test_list” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_10port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_20port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_id.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_retimer.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/idcode_condor.xsvf” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/lbist_condor.xsvf” failed: Input/output error (5)
    rsync: symlink “/mnt/fabos/share/SWBD51_test_list” -> “SWBD43_test_list” failed: File exists (17)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer2_10port_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer2_20port_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/blazer_vpddata.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/icecube_vpddata_id.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/icecube_vpddata_retimer.txt”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/idcode_condor.xsvf”: Input/output error (5)
    rsync: recv_generator: failed to stat “/mnt/fabos/share/lbist_condor.xsvf”: Input/output error (5)
    rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
    rsync: readlink “/mnt/fabos/share/SWBD51_test_list” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_10port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer2_20port_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/blazer_vpddata.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_id.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/icecube_vpddata_retimer.txt” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/idcode_condor.xsvf” failed: Input/output error (5)
    rsync: readlink “/mnt/fabos/share/lbist_condor.xsvf” failed: Input/output error (5)

    Reply
    1. guldmyr Post author

      “Press escape within 4 seconds to enter boot interface.”

      There’s some stuff you can do in there. http://community.brocade.com/t5/Fibre-Channel-SAN/200E-Switch-not-booting/td-p/31585 and http://community.brocade.com/t5/tkb/articleprintpage/tkb-id/FibreChannel/article-id/58 has some suggestions. Perhaps finding what the variables are set to with “printenv” on switch B when it fails to boot on old card and then try to boot it with new card and set. ENET_MAC seems important.

      Reply
  30. Mc.Sim

    Good day,
    I found some problem and found solution )
    SCP Firmwaredownload or configdownload failing from SUSE server or other Linux distribution

    Product Type Details
    All SAN products
    Environment
    Secure data centers using SCP for file transfer Software Release All Description Firmwaredownload is failing with the following message:
    Server IP: 10.200.130.42, Protocol IPv4
    Checking system settings for firmwaredownload…
    Failed to access scp://root:******@10.200.130.42/v7.0.0c/release.plist
    The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, and the firmware path are valid, also the correct protocol and authentication are supported.
    Symptoms
    Firmwaredownload and configdownload failing. Configupload is successful.
    Workaround

    Implement a FTP server or where supported USB can be used.
    Root Cause
    sshd_config entry to enable tunneled clear text passwords was set to no.
    PasswordAuthentication yes
    This is in the following section of the file.
    # To disable tunneled clear text passwords, change to no, here!
    PasswordAuthentication yes
    #PermitEmptyPasswords no
    Resolution
    Change the PasswordAuthenication key to yes and reboot the server.
    Product Defect
    None
    Fixed in Version
    External

    Reply
    1. guldmyr Post author

      Hi,

      some comments I have on that advice :)
      Looks like you found this on another page? Where?

      Definitely, if your sshd prevents logging in with password you can’t do scp which uses a password :)
      Many servers have password login disabled – one has to log in with a key or similar.
      Checking out the log of sshd on the scp server is good to see why scp fails, /var/log/messages or /var/log/syslog usually.
      You don’t have to restart the server after changing sshd config, restarting the sshd service is enough.
      Also in the example above is to use the user root to scp. A normal user could be used instead.
      And USB is only supported if you have a Brocade USB disk.

      Reply
  31. Mc.Sim

    The solution was granted by technical support.
    I post it “as is”. I think they get it from some internal knowledge base.
    Trouble was in that I can login by ssh with password, but firmwaredownload did not work. (independently of parameter PermitEmptyPasswords)
    There are I can not find any useful in the log sshd (independently of debug level (( ) and ask technical support. They gave me it solution.
    Also root-user was there because “as-is” ))
    Of course, I used dedicated user with limited right )

    Reply
  32. Roman

    Great article !
    I have one question about firmware compatibility… we have a customer where 2 new Core Switches have been installed
    (HP SN6000B 16Gb 48-port/24-port Active Fibre Channel Switch
    – QK753B) and they are connected with Blade SAN switches in Enclosure ( HP B-series 8/24c SAN Switch BladeSystem c-Class – CN8123B0B6 )

    Now, my question: Core SAN switches have FOS 7.1.2 and Blade SAN switches FOS 6.4.1a … will they communicate together with no problem? or should we upgrade the Blade SAN switches? (it is actually in plan, but because of business reason it will not be possible to do that in next 3-4 weeks).

    Thanks a lot.

    Reply
    1. guldmyr Post author

      Thanks for liking the article Roman!

      Should be fine. I glanced through the 7.1.2 release notes and couldn’t find any obvious problems with 7.1.2 and 6.4.1 in the same fabric. If you are worried, you could check the release notes of latest FW the 8/24c switches support and see if there are any fixes for problems that you’d rather have without before connecting the switches. There’s quite a few fixes in between 6.4.1a and 6.4.3f.

      Reply
  33. Mirko

    Hi i have one HP 4/32 (A7393A) and i need to change internal CF because old one is dead, i cannot find any procedure, what i should do?

    Reply
  34. Mirko

    Hi guldmyr, thank for your answer, i know that calling hp is the best pratice but i bought these 2 switches to study and buy hp spares and maintenance is really too much expensive, i was thinking if some good angel could provide me one image of the original one and to tell me also how big have to be the compact flash … or im wrong?

    Reply
  35. Mirko

    I also read that license are stored in cf.. (really ridiculus, whi not on flash) btw i have serial number and i hope that there is way to retriueve it or not?

    Reply
    1. guldmyr Post author

      Thanks a lot Matthias, and thanks for the note about 7.3.0a!

      Time to read some release notes ;)

      // after a quick look around it seems that it’s available in some places but I can’t find any release notes for it. Can you find any?

      Reply
  36. Randy Woods

    I have two Brocade 4Gb fibre switches in a IBM Blade Center E Chassis. They are currently on version 5.3.1b. The only firmware upgrade available on the IBM site is version 6.2.2f6. When I try to upgrade, I get the message that I have to first upgrade to version 6.1, which as I stated is not available. This switch is not yet in production, so I do not mind if there is a disruption or a configuration loss, so I tried the -c option of firmwaredownload, but it still gave the same error. Can you either give me a workaround for this error, or point me to the 6.1 version of the code?
    Thanks,
    RW

    Reply
    1. guldmyr Post author

      Hi, sorry for the delay. Turns my email notifications aren’t working.. From 5.2 you gotta go to 5.3 or 6.0 as written in this blog post. If IBM don’t have, get it from HP or anywhere. Links in the post :)

      Reply
  37. Pingback: How To Fix Brocade Java 7 Error in Windows

  38. Harry_Redl

    Hello,
    have problem with upgrading FOS on HP 4/8 SAN (SWBD34) switch from 5.0.1b to higher version (tried HP 5.1.0, Brocade 5.1.1b, 5.2.0b) – but it always failed when looking for “fwdl_script” file (as FTP server states). Google did not help much …
    I have other switch of the same type (EMC branded) which I upgraded without problem (well – it came with 5.1 and I was able to get it to 6.2.2f) – so I assume the process should be the same …

    Any hint?

    Harry

    Reply
    1. guldmyr Post author

      Hi,

      please send the exact output and what you type from the console (http://hastebin.com/ is a good place).
      I’m guessing the error lies in what path to specify to the firmware. It’s different in the older 5.0 compared to the newer ones.
      See http://www.guldmyr.com/blog/brocade-san-switch-firmware-upgrades/#Specifying_Directory the Specifying_Directory section of this post for some hints.
      I guess you could list the content of the firmware you have extracted and see where the fwdl_script is?

      // Johan

      Reply
  39. Harry_Redl

    Hello,
    that is the thing – the fwdl_script is not in ANY version of the FOS I have looked at (not in ANY subfolder) – checked (505f, 510, 511b, 520b, 522, 523, 601, 612c, 622f).

    This is the FC switch:
    login as: admin
    admin@192.168.1.119‘s password:
    redfab2:admin> firmwareshow
    Primary partition: v5.0.1b
    Secondary Partition: v5.0.1b
    redfab2:admin> firmwaredownload -s
    Server Name or IP Address: 192.168.1.1
    User Name: foo
    File Name: /v523/release.plist
    Password:
    Do Auto-Commit after Reboot [Y]: n
    Reboot system after download [N]: n
    Firmwaredownload has started.
    Firmwaredownload has completed successfully.

    (the firmware is NOT downloaded!!!!)

    This is the FTP server:
    > connect from 192.168.1.119
    < 220 sfk instant ftp, 60 sec timeout. sft 105.
    USER foo
    client user ok.
    > client pw ok.
    < 230 User logged in
    TYPE I
    < 200 Command OK
    CWD /v523/SWBD34
    < 250 CWD OK. "/v523/SWBD34"
    PORT 192,168,1,119,4,2
    < connect to 192.168.1.119:1026
    < 200 Okay
    RETR fwdl_script
    < 150 Sending File
    send file: "/v523/SWBD34/fwdl_script"
    error: cannot get size of v523\SWBD34\fwdl_script
    send file done, RC 9
    < 226 Closing data connection
    disconnecting client

    It does not even try to download the plist file

    Harry

    Reply
    1. guldmyr Post author

      Try without specifying the release.plist. (5.2.3 release notes says it may not be needed anymore). It might be needed with 5.1.x still then..
      Perhaps the fwdl_script is mentioned inside the release.plist?
      Why the “firmwaredownload -s”? How many CPs does the 4/8 SAN switch have anyway? I guess if you choose yes to the answers it doesn’t work either?

      Reply
    1. guldmyr Post author

      Okay :)

      Do the commands firmwareDownloadStatus or errlog provide any insight?

      But could you perhaps try without any extra flags?

      If that don’t work either, I’d try perhaps 5.0.1d if you can find it. 5.0.5f is not supported on the 4/8 switches.

      Reply
  40. Harry_Redl

    believe it or not, it was the FTP server … I do not understand it but as soon as I have used another (Filezilla instead of SFK commandline tool), I was able to update to 5.2.3. Now I am proceeding to 6.2.2f as with the previous switch using the SFK (just for fun). Thanks for help and great article …

    Reply
  41. Keith

    Similar problem as the fellow with the new CF… I’ve toasted the file systems (hda1 & hda2), and booting stops at the busybox prompt.

    I’ve figured out how to netboot the switch (HP’s variety of the Brocade 4100), but I need an image to boot. If I can get that up and running, and can probably reflash (or manually reinstall) the firmware.

    Any idea if a netboot image for the 4100 exists?

    Reply
  42. JBD

    Any way someone could send the HP SANloader software my way or point me to a link? I have 4 Brocade 5000 switches that are presently running version 4.6.6 with different maladies. I would like to try and re-purpose them but unfortunately this seems a bigger pain than it may be worth. Obviously they are no longer under warranty or support.

    Reply
  43. JBD

    Thanks! Let me know if you find it or have any other creative ways to reload the FABOS onto these 5000’s.

    Reply
    1. guldmyr Post author

      Hey JBD, sorry I couldn’t find it (and anyway seems it’s an HP internal tool so if I had I probably shouldn’t).
      It shouldn’t really be needed for the upgrade though. Have you tried without it?

      Reply
  44. Steven Qualls

    I need to upgrade (2) DCX Backbone 2499-816 directors from 7.0.1 to 7.2.1d. If I go the recommended path 7.0.1 > 7.1.0 > 7.2.1d can this be done non-disruptively without ports going offline.

    Reply
    1. guldmyr Post author

      If you follow the recommended upgrade path yes. Do note that there are exceptions sometimes regarding some port blades. So read the release notes for each upgrade and find out for sure.

      / Johan

      Reply
  45. Sergey

    Hello! The grate article. It helped me to solve the most of problems. But one still makes me unhappy: I have one HP 4/32 sunswitch (brocade 5000) with dead compact flash. May be You have the image of cf card for this model?
    With hope…

    Reply
  46. poekel

    Hello,

    I need to upgrade my Storageworks 4/8 switch which is on 5.0.1b
    Where do i find all the firmware software ?
    Please help!

    Poekel

    Reply
  47. poekel

    Hello,

    I started with v5.2.3 and i used the Data Center Fabric Manager to upload the firmware which went ok.

    But i dont see the change from v5.0.1 to v52.3
    Do i need to activate something ?

    Thanks for all the help and advice ! (Highly appreciated!)

    Reply
  48. poekel

    fcswitch02:admin> version
    Kernel: 2.4.19
    Fabric OS: v5.0.1b
    Made on: Wed Aug 17 21:28:18 2005
    Flash: Wed Dec 28 21:38:52 2005
    BootProm: 4.5.2
    fcswitch02:admin>

    Reply
    1. guldmyr Post author

      Aha, you wrote upload the firmware in DCFM – this is probably to just put the firmware in the DCFM firmware repository. You’ll need to apply/install it to the switch as well.

      Reply
  49. poekel

    Yes i did that, but i ALSO downloaded it to the switch

    See here : http://www.destaken.nl/F-switch.jpg

    Even if i click the overwrite function it does not work …….

    Do i need an earlier version than v5.2.3 for starters?

    I have a difficult question about connecting 2 fibre switches.
    Can you send me you email if you would like to help ?
    sent it to henny@destaken.nl

    Reply
    1. guldmyr Post author

      I don’t use dcfm. So run the firmwaredownloadstatus command in the Cli. Perhaps that can tell more or the switchlogs. Errshow

      About version, see 5.2.3 release notes. Is your current firmware and switch supported to upgrade from?
      It should be fine.

      Reply
  50. Anirudh Sharma

    Greetings,
    Thanks for this fantastic writeup.

    I have sm Brocade 6510 switches in the environment,
    Cn u cnfirm if I cn jump directly from version v7.0.1
    to v7.3.1b ??

    Reply
  51. Rossi

    Hi,

    I’m trying to get FOS 5.1x and 5.3x for IBM. I am unable to get the files via the links you provided. The links to IBM page works fine, but from there the Brocade Site says page not available.. Anyone else could confirm this please.

    Thanks.

    Reply
  52. Rossi

    I can actually see both FOS7.x and 6.x downloads on Brocade site, but not 5.x which I need. Logged a call with Brocade and they said I am not authorized? What?

    Reply
  53. Steven

    Could we do non-disruptive upgrade as below for brocade 300.

    1) non-disruptive from 6.2.0c => 6.3.2e
    2) non-disruptive from 6.3.2e ==> 6.4.3h
    3) non-disruptive from 6.4.3h => 7.0.2e
    4) non-disruptive from 7.0.2e => 7.1.2b
    5) non-disruptive from 7.1.2b => 7.2.1f
    6) non-disruptive from 7.2.1f => 7.3.1c

    We need non-disruptive path for our upgrade.

    Do you we need to apply new license after each stage of the upgrade or after the final version?

    Thanks.

    Reply
    1. guldmyr Post author

      About disruptive.. read the release notes for caveats. For example in 6.3.2e it says “Non-disruptive firmware activation on FOS v6.3 will disrupt I/O traffic on FCIP links.” So if you’re using FCIP then it’s disruptive.

      B300 is listed as supported in 7.3.1c so you should be good.’about the path.
      Licenses should remain and you should not have to reapply them. Some will be changed into Unknown if the feature is free after the upgrade.

      Reply
  54. yalda

    Hi
    I have a 4/8 hp SAN.its some old but i need to upgrade from v5.1.0.b to 6.x.x but cant fount 5.3.x and 6.0.0 .
    Do you have any download link, the old links are not alive.

    Reply
  55. Sujit

    How do you cleanup old firmware from the switch so it can load newer firmware or does it do by itself after ??

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.