Tag Archives: HP

Command View P6000 EVA Simulator 10.0

Due to somewhat popular demand here’s another post detailing the steps for somewhat successfully installing HP P6000 Command View Simulator on Windows 7 x64. It can be a bitch.

The older post is from 2011 with CV 9.4, this one also has PA – performance advisory bundled.

  • Download: http://software.hp.com
  • Two files: EVA Simulator 10.0 (Z7550-00252_EvasimInstaller_100fr_v1.exe) and a readme
  • There is an e-mail listed in the readme!
    • But if you want to, you can put in a comment below saying how sexy I am :p
  • The readme is quite long but most of it is about how to use the PA (performance analyzer), Appendix B is a required read. It describes how to add the Groups so you can log on to CV.
    • A previous blog post by myself truly also goes through how to add a user group :)

For lazy hounds:

  1. (optional) Disable UAC in Windows and make yourself admin.
  2. Put an account in the Windows Group called “HP Storage Admins”.
  3. Launch the downloaded file (it extracts a setup.exe and .msi file)
  4. Launch setup.exe – it’s located in the same directory where you launched the Z7550-00252_EvasimInstaller_100fr_v1.exe
  5. Next, next, next, next, yes, yes, Wait, yes, Installed!
  6. Try out the “Start HP P6000 EVA Simulator” new icon on your desktop, does it work? Profit!

“XF application has stopped working” – some friendly error I got and CV simulator did not start.. Most likely permission issue. Peaking through one of the command-prompts it repeats access denied.

It’s amazing that the CV simulator still relies on .bat scripts. Guess it’s for backwards compatibility with XP and Vista? Only one file necessary for all those Windows OS variants.

With default Windows security, the Simulator runs into a problem when it tries to write to files under c:\program files (x86)\ . There are probably many ways to remedy that, one might be step 1 above. This worked:

  1. Go to C:\Program Files (x86)\Hewlett-Packard\HP P6000 EVA Simulator\evasim
  2. Right-click on ‘start_bundle.bat’ and run it as an administrator. This should start the simulator.
  3. Open up a command prompt with Admin Privileges, cd your way into evasim directory and type: “start startcv.bat”
  4. That should launch the Command View process and also IE pointing to CV.
  5. If not, point your web-browser to: https://localhost:2374/SPoG/ or https://localhost:2374/
  6. Log in with the user/password you added into the “HP Storage Admins” group earlier.

Some tips:

In one of the “DOS” windows, there might be more clues as to what’s going on.

Open a command prompt with admin privilieges by typing “cmd” in the search bar then right-clicking and starting as administrator.

Inside the Simulator DOS prompt you can hit enter and if you see some commands (save, stop, exit, start) then that’s the simulator window.

If you want your changes to be kept, type “save” in the simulator window before quitting.

Some thoughts:

It feels a bit ruggish. I bet this whole mess could be improved quite easily with some decent scripts. Here’s one I’d like to see:

if $os == Win7:
    if $write_read_permissions_in_program_files != "allowed":
        print_in_big_letter("You need more axx! Do $THIS")


To create a new user group in Windows 7

This post is created upon request by a reader.

May or may not be needed for the P6000 Simulator. It is however required when you install the real HP P6000 Command View.

First you need to get into ‘Computer Management’, do this by right-clicking on ‘My Computer’. Then click your way into ‘Local Users and Groups’, and then into the ‘Groups’ section. In there, right-click somewhere and create a new group called ‘HP Storage Admins’ (or HP Storage Users for read-only). While creating it you can add a user (the one you log in with probably), you can also add it later by right-clicking the group.

P6000 – EVA – Command View Simulator


Command View EVA is HP’s web based management tool for their EVA/P6000 products.
It’s been looking the same for quite some time except the quite old ones. It’s simple to use compared to other management softwares but sure it has its limitations too. It’s not based on JAVA anyway :)


Run the install file, this extracted the files but then it said something about it not being correctly installed. I then went to the folder and started the install manually. This completed after a while. After this:

To run it in Windows 7 x64:

Go to start menu -> accessories -> right-click on Command Prompt -> choose “run as Administrator”.

In there type:
cd C:\Program Files (x86)\Hewlett-Packard\HP P6000 EVA Simulator\evasim

Then hit:
wait for it to complete

Then hit:

Which will start the simulation services and open a web browser (IE for me even if Firefox is default). It looks like it works fine in Firefox 7 too – just surf to . There is no password required when logging in manually.

IE9 will complain about certificate, say that you agree and then you’re in!


Well, this is where you learn how to do the things in Command View.

For example, create a vdisk, create a replication group, try out continuous access (data replication) and business copy (snapshots, clones). It’s really like the real deal except that probably the error logs aren’t there and you can’t really present any disks to a host. But you can do everything simulated anyway :)

The firmware in the simulator is 10000090 (or CD1528lesl-10000090 ) on HSV300. A pre-release of the XCS firmware? Also the 6100/8100 EVAs in the simulator is on 6.220 – why not on 6.240?

Also do try the SSSU it is installed here C:\Program Files (x86)\Hewlett-Packard\HP P6000 EVA Simulator\evasim\cveva and it works. So you can try scripting, try out scripts before you actually run them in your production system and stuff like that.

Even cvutil is installed. In the same directory as SSSU, just hit ‘cvutil paths’ for example to see the paths your machine has to the EVAs.

To shut down the simulator you can type ‘exit’ in the command windows that are opened by the software. Or just hit CTRL+C or the X in the window :)

P6000 Firmware & Command View

The P6000 firmware XCS 10000000 is out, or has been for a while now.
You can find it on http://software.hp.com or the link above.

The Command View 9.4 release notes are here.

Extra nice stuff (besides the obvious ones like new hw support):

  • HDD upgrades via management module / ABM
  • Disk Drive Remote Power cycling (apparently works after 09500000?)
  • Thin Provisioning (requires extra license but with the P6300/6500 it comes with the normal CV license)
  • Online migrations (change vraid lvl or disk group without impacting i/o – cool)
  • Manage it over FCoE (so via an MPX200 for example)
  • EVA3000/5000 events not propogated to Windows Event Log – I knew it!
  • SSSU 9.4 – took away the 10s delay when executing commands.

And release notes for the XCS 10M is here.

More hw stuff ;)

  • For HSV300 and above
  • P6300 is HSV340 and P650 is HSV360
  • M6612 is LFF (3.5″ disks) and M6625 is SFF (2.5″ disks)
  • So are they smaller than the EVA8400?
  • Both P6300 and P6500 have a management module (ABM)
  • Events that indicate back-end cabling is incorrect -> NICE
  • Some more SPOF fixes

It’s confusing to read the release notes as it says P6000 everywhere but it refers to all EVAs. Also the older generations like EVA3000/5000 are called P6000!

I also wonder why the P6300/P6500 is named HSV340 and HSV360.
So they’re not better than the EVA6400?

This would put them on or slightly above the EVA6400/HSV400 series level:

“Up to 10 M6612 or M6625 are supported with the P6300 EVA
up to 20 M6612 or up to 18 M6625 are supported with the P6500 EVA”

In terms of sizing it would make more sense to call them HSV420 and HSV440 or something like that :)

On this page it says active/active on the redundancy options, but it doesn’t say this on the x400. Does this mean it’s no longer asymmetrical A/A like it was on the previous EVAs?

Latest FOS ( Fabric OS ) Firmware on HP’s Brocade SAN switches

How to find the latest firmware for an HP Brocade SAN switch:

How to find out which Brocade Firmware is the latest and which is the last supported one?

  1. On HP SPOCK: http://h20272.www2.hp.com/ (this required an HP Passport, they are free to create).
  2. Go to Switches, then click on B-series connectivity stream.

The B-series conenctivity stream document gets updated often and it has the recommended (usually latest) and the supported Fabric OS releases for each switch type.

How to find the last supported firmware for an HP Brocade SAN switch:

Usually the EOL of a firmware is announced when a new one is released.
See this customer notice of 6.4.1b:

Server and Storage Tips from the ITRC

Just a good howto – tip – solution. It’s a little hard to find good threads.

Hard to find something.. should probably write it in here when I think of it.
Also the ITRC are moving to another platform in June 2011 so maybe these won’t be available after this.

** Update 2011-06-27: Yes, these do not work after the ITRC move. They take you to the main page of the new forum. Tried to find the posts again but couldn’t on the first two so I’ve given up :/


EVA Parity Groups – RSS
EVA Control RSS position while replacing disks.
Command View EVA cannot find EVA
SCSI Sense errors with HP SC11xe and Tape Drives
EVA DR resume
Go from PID Extended Edge to PID CORE format with Unix.


How are the ports mapped in a a HP BladeSystem c-7000 with Flex-10 Fabric Interconnect modules.

Operating System

How to remote to a Red Hat server:


HP P6000 – EVA – Thin Privisioning and Dynamic Lun Migration – XCS 10.000.000


2011-07-12: Updated with new link to new HP ITRC forum.

Also it looks like VAAI is not implemented in this firmware.

Some more news!

With Google Translate:
“Under the new EVA was also the XCS software updated and is now more stable and effi ¤ competitive. IT IS now available for r the EVA4000/6000/8000 EVA4100/6100/8100 and the version of XCS tion 6240 and for r the EVA 4400/6400/8400 and EVA XCS version of the P6000 10.000.00 to availability, with new features such as thin Provisioning “and” Dynamic LUN migration “for r coming EVA x400 systems.
In addition, the new EVA Command View v.9.4, which for r all generations of EVA systems can be used.”

The newsletter was in German – it mentions Thin Provisioning and Dynamic LUN Migration (a blog post about Tiering). Especially interesting I find that the x400 will also get this 10.000.00 firmware – which kind of makes sense as it’s already on 09.534.000 (one more number?).
I take this to mean that the architecture inside the P6000 Controllers are the same as in the EVA x400 -series (PowerPC etc.).

Sounds like a great move, as long as the new firmware is as stable as they claim.
EVA x400 was for most of the time not stable until the 09534000 firmware was released, unless you were lucky/did not have that many disk shelves.

It will probably be called XCS 10000000 , not 10.000.00 as written in the newsletter above.

HP’s Brocade firmwares compatible with other switches?

After a question in my SAN switch firmware upgrade article I made a comparison of two downloads of 6.3.1b (one via IBM and one from HP) – the only differences were a file called ancillary and one called EULA.pdf. I used examdiff to find the differences.

All the sub-directories were the same, only the above two files were added in the HP one.
I believe quite strongly that you can use the HP firmwares to upgrade Brocade switches that are branded by other vendors.

At least IBM and normal Brocade ones.

As they are using the very same Brocade firmware that Brocade themself use, it might be hard for the vendors to change the switch that much.

It would be interesting to investigate if other vendors add something to make theirs not, but I have no way of acquiring such a firmware.

The EULA looks like a normal HP standard end user license agreement form. The HP ancillary.txt file contains this:

“This ancillary.txt file provides information as to how to obtain the open source or other third party licenses in this distribution. To obtain such licenses, run the following CLI command at the prompt, “opensource”.
This ancillary.txt file also provides the instructions for customers who require a copy of the
machine-readable GPL Source Code by written request.  Upon your written request, HP will provide to You, for a fee covering the cost of distribution, a complete machine-readable copy of the GPL Source Code. Your written request for GPL Source Code can be sent via email to FC_Infrastructure_OpenSourceRequest@hp.com. In the request, include product name, version number, your name, and your shipping address. “

HP Virtual Room Installation on RHEL 6 x64


I couldn’t get it to work.

Eventually I installed Ubuntu 10.04 LTS in a VM in Virtualbox and in there it worked.

However, resolution is only 800×600. So I found this page: 



That told me to install some stuff and then install the Guest Addition stuff. After that and a reboot HP Vroom no longer worked. But resolution was fine! Grah. Then I just used the “Live CD” of Ubuntu instead, or the normal .iso but no need to install, just boot from it.


Next Generation EVA – P6000

On theregister there was recently a post that maybe HP will announce the new EVA’s in Vegas in June – the P6000.

I just opened a discussion on the ITRC forum, maybe we’ll see some more posts there. I myself am hoping for some thin provisioning or why not SAS backends instead of the quite notorious FC loops. How about native iSCSI or FCoE?

*** 2011-05-05 Update, HP has now officially announced some information about it. For example that it will have the SAS-backend! Whoop! No more loop problems :)

*** 2011-05-05 Another one! Now it came – Thin Provisioning!

HEPIX Spring 2011 – Day 1

Got in last night at around 2140 local time.
I should’ve done a little more exact research for how to find my hotel. Had to walk some 30 minutes (parts of it the wrong way) to get to it. But at least I made it to see some ice hockey.. . to bad Detroit lost.

Today’s another day though!

First stop: breakfast.

Wow. What a day, and it’s not over yet! So much cool stuff talked about.

Site Reports

The first half of the day was site reports from various places.

GSI here in Darmstadt (which is where some of the heaviest elements have been discovered). They have started an initiative to keep Lustre alive – as apparently Oracle is only going to develop this for their own services and hardware. They are running some SM – SuperMicro servers that have infiniband on board – and not like the HP ones I’ve seen that has the mellanox card as an additional mezzanine card. Nice. They were also running some really cool water cooling racks that uses the pressure in some way to push the hot air out of the racks. They found that their SM file servers had much stronger fans at the back, and not optimized airflow inside the servers so they had to tape over some (holes?) over the PCI slots on the back of the server to make it work properly for them. They were also running the servers in around 30C – altogether they got a PUE of around 1.1 which is quite impressive.

Other reports: Fermilab (loots of storage, their Enstore has for example 26PB of data on tape), KIT, Nikhef (moved to ManageEngine for patch and OS deployment, and Brocade for IP routers), CERN (lots of hard drives had to be replaced.. around 7000.. what vendor? HP, Dell, SM?), DESY (replaced Cisco routers with Juniper for better performance, RAL (problem with LSI controllers, replaced with adaptec), SLAC (FUDForum for communication).


Rest of the day was about:


Some talk about messaging – for signing and encrypting messages. Could be used for sending commands to servers but also for other stuff. I’ve seen ActiveMQ in EyeOS and it’s also elsewhere as well. Sounds quite nice but apparently not many use it, instead they use ssh scripts to run things like that.


About various threats that are public in the news lately and also presentation of some rootkits and a nice demo of a TTY hack. Basically the last one consists of one client/linux computer that has been taken hacked, then from this computer a person with access to a server sshs there. And then the TTY hack kicks in and gives the hacker access to the remote host. Not easy to defend against.

There was also a lengthier (longest of the day) 1h-1.5h presentation of a French site that went through how they went ahead when replacing their home-grown Batch management system with SGE(now Oracle Grid Engine).

*** Updated the post with links to some of the things. Maybe the TTY hack has another name that’s more public.

Next Days:

Day 5
Day 4
Day 3
Day 2

King in ITRC!

Just got the Royal rank – 2500 points :)


Woop woop!

HP’s ITRC forum is a great place to learn more, help out :)

For me the primary reason is to remember the things I learnt while working at the support, because I do not work with hardware in that respect anymore it’s incredible how fast this kind of stuff is forgotten, at least the specifics :/

I hope the ITRC won’t change into something crap after the move to another forum system now in the summer.

Brocade SAN Switch Firmware Upgrades


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 http://guldmyr.com. The post have 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” firmwares 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 mean 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-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

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.

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.


  1. decide
  2. prepare
  3. upgrade


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.2c > 8.0.2d > 8.1.2d > 8.2.0a

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.
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 firmwares. If you don’t click through it also only have the firmwares 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.

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

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

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  IBM_Link HP_Link

Brocade release notes in .pdf


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.x  from 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.


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.


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:
For HP products: here and click ‘Obtain Software‘, it has from 5.2.3 to 6.3.0d (but you’d rather use 6.3.2e). Eventually the link points 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. Same for 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.


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. 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.


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
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


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.



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.

EMC – Symmetrix and CLARiiON – 2

So we reserved two green old chairs.
Just might need a nut and a metal plate for a bolt that’s missing one then they’ll do nicely!


Also been reading up on the CLARiiON now so far as to what I’ve found.

Hardware base is quite similar to the EVAs with the backend loops, CTS on the CX4 and loop io modules on the CX3. With a max of 120 disks per loop.
The number in the naming of the CX4 (maybe the others too) is that the number is max amount of disks. CX4-960 is 960 disks and 8 loops (120 per loop then?). Loop pairs I hope.

Turns out Dell are selling these.

Hot sparing is used and a raid group is like an EVA disk group.
Quite similar to the way HP’s XP is creating the parity groups.
Navisphere for management on the CLARiiON and System Management Console on the Symmetrix.

Interesting stuff this is!

Symmetrix is high end and CLARiiON is mid range.

So Symmetrix has even more similarities to the XP. For example the blades with the directors(host ports, device ports, disks, memory, cache) and assemblies.

Both appears to have more ways of configuring it than the EVA – the admin interface looks more complex anyway and you can tune the cache which is neat ;)


Both of these are quite extensive but especially the Symmetrix article looks a lot like an advertisement.