View and Download Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base manual online. Brocade Fabric OS Documentation Addendum. A primary and a secondary partition for firmware, enabling you to commit or restore when doing firmware downloads. Note: Fabric Manager v3.0.2b is the minimally required version that can be run on the SilkWorm 3900. Brocade Documentation. In addition to these release notes, this release is supported by the following.
Hey, Anybody did 3900 firmware upgrade that can point to me, which file or directory to put in when prompt for firmware filename? I'm looking at 4.4.0c and looks like whole bunch of directories and files unzipped from the downloaded package. I did on 3800 and it's just a single file but looks like 3900 has more than one after extracted. So should I use the directory name instead of single file?
There is no readme or any instruction from that directory, neither release.plist, which was referenced by some instruction to put in as the filename for fw. However, I can see a create_release_file command under */sbin and looks like I need to upload all that onto the /flash, then 'cd /sbin' and execute 'create_release_file', then upgrade using the newly created release.plist? Would appreicate your helps. Yes, finding the instructions can be a bit hard - here is a pointer: 〈=English+%28US%29&pnameOID=315679&prodSeriesId=315102&prodTypeId=12169&basePartNum=COL5590&locBasepartNum=co-30715-1&os=Cross+OS&tech=Firmware&attTypeId=106 Please note that you need an FTP server - the old RSHD/CAT mechanism is no longer used. Unpack the files in a subdirectory (v4.4.0c) into the FTP root. The follow the instructions I have mentioned above literally. Enter: File Name: v4.4.0c/release.plist You don't need to put the switch type between 'v4.4.0c' and 'release.plist', at least *I* have never done this and it has always worked fine for me.
I assume fabric os command 'firmwaredownload' will call 'install' script from the unpacked package. By looking at the 'install' script, I noticed that it actually have 'create_release_file' subrountine in it. Then it doesn't make any sense of having ' /v Shillingburg Fundamentals Of Fixed Prosthodontics 4th Edition Pdf Free Download. 4.4.0c/release.plist' as the syntax, why not just ' /v4.4.0c'?! Well, it's a Brocade call! Just makes people confusing like me:) Any ways, you guys have any good ftp server software to recommend?
I had 3com, but it ain't work for big size of files like this. Another story about my MDS9509 fw upgrade I had with.
By looking at the 'install' script, I noticed that it actually have 'create_release_file' subrountine in it. Then it doesn't make any sense of having ' /v4.4.0c/release.plist' as the syntax, why not just ' /v4.4.0c'?! Well, it's a Brocade call! Just makes people confusing like me:) heh! You're not the only one, I totally agree with this statement. Someone at Brocade was too clever by half.
When reading the instructions, it's easy to think that 'release.plist' could be a placeholder, especially when embedded in what one would think is a valid unix filespec. When this 'file' does not exist after one follows the terse unpacking instructions, one thinks it is a placeholder, or that unpacking was done wrong. This is compounded by the fact that in the web interface typing in the correct 'magic' filespec that does a correct install from the CLI does NOT work. Unnecessary 'FM' is a time-waster for the end user of the product.