Brocade 300 firmware

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

jerryxlol

Member
Nov 27, 2016
47
4
8
31
Hello,

i have managed to get two brocade 300 with firmware version 6.4.1. I am not able to get to the UI because of the firmware. Google is not helpful and cannot find the firmwares for download. (Broadcom has the latest 8.x.x, but the path is 6.4.3 => 7.3.0 => 8.x.x

Can someone provide whole path to the latest fw which has HTML5 if its possible?

Any kind of advice for fw update welcomed.

If successfully upgraded i will be selling them soon, because i want to test them if they are fully working and licensed.

Thank you :)

Tom
 

Renat

Member
Jun 8, 2016
57
19
8
41
google gives a lot of links by text "swbd71 ftp" to upgrade bocade 300 to last firmware 7.4.2 (h - is last, but d is also good).

only Java! (1.8 upt 56 should be enough).

HTML5 is only in v9. for Brocade 32G switches.
 

jerryxlol

Member
Nov 27, 2016
47
4
8
31
I have tried, and ftp.adelaide is one valuable result, but without login you cannot download that files from ftp-

And when no HTML access after upgrade then this task wont get benefit. Thank you.
 

Renat

Member
Jun 8, 2016
57
19
8
41
one of dozen variants
ftp://198.85.226.15/Brocade/

all versions that you need for Brocade 300

for ftp login is always "anonymous" with the same or empty password
 
  • Like
Reactions: jerryxlol

funar

New Member
May 17, 2022
10
0
1
Unfortunately, it seems 198.85.226.15 doesn't have all of the files. I'm trying to get to 7.4.2 from v6.3.2a as well. If anyone has any links, I'd appreciate it. My searches have come up with a ton of down sites and sites that don't have the files anymore.
 

Marc_

Always a school day
Jul 22, 2022
66
10
8
Has anyone done a firmware install on these with a new flash card? Been looking around google and here but haven't managed to find anything.
 

Renat

Member
Jun 8, 2016
57
19
8
41
cause full path is not so easy and take 10-15 operaion.

1 way - make dd image from other device.
and dd it to new one.
find address of zImage on new cf card
insert this address in bootrom

this is all (for one generation, and one model generally)

2 way - mount working cf card
make 2 fat partitions on new card and copy data from working card
load zImage by tftp and bootm switch with new card
run firmwarecleaninstall

this is all (system download and reformat cf card itself and set good address in bootrom)
 
  • Like
Reactions: Marc_

Marc_

Always a school day
Jul 22, 2022
66
10
8
cause full path is not so easy and take 10-15 operaion.

1 way - make dd image from other device.
and dd it to new one.
find address of zImage on new cf card
insert this address in bootrom

this is all (for one generation, and one model generally)

2 way - mount working cf card
make 2 fat partitions on new card and copy data from working card
load zImage by tftp and bootm switch with new card
run firmwarecleaninstall

this is all (system download and reformat cf card itself and set good address in bootrom)
Thank you again! Downside is I don't have a working card :( I've got 2 340's here that have failed. I've got the firmware from above and still some new cards left over from doing the vdx's. Was hoping there was a similar process to the netinstall for these.
 

Renat

Member
Jun 8, 2016
57
19
8
41
by second way it could be working:
1. take firmware
2. check where packages for swdb71 (in Common and swbd41 probably folder)
3. unpack all these rpms in one shared folder
4. make 2 partitions on CF-card (wrong fat, ext4 is right)
5. copy all files to / on both partitions
6. take from /boot folder zImage
7. insert card in switch.
8. bootrom - setup ip, tftpboot zImage, bootm
9. ipaddrset on booted system (even with errors of not-handled files)
10. firmwarecleaninstall
 
  • Like
Reactions: Marc_

Marc_

Always a school day
Jul 22, 2022
66
10
8
by second way it could be working:
1. take firmware
2. check where packages for swdb71 (in Common and swbd41 probably folder)
3. unpack all these rpms in one shared folder
4. make 2 partitions on CF-card (wrong fat, ext4 is right)
5. copy all files to / on both partitions
6. take from /boot folder zImage
7. insert card in switch.
8. bootrom - setup ip, tftpboot zImage, bootm
9. ipaddrset on booted system (even with errors of not-handled files)
10. firmwarecleaninstall
Looks like I'm in for a long night. Once the RPM's are unpacked should they show as CPIO files? Sorry for all the questions, still very new to this!
 

Renat

Member
Jun 8, 2016
57
19
8
41
rpm->cpio->folder
need to unpack each rpm+cpio.
you will get root folder which uses all linux systems:
/
/boot
/etc/
/lib/
/usr/
/var/
/root/

etc. just check that /proc /dev /sys exists
each rpm adds own files and links to this root
 
  • Like
Reactions: Marc_

Marc_

Always a school day
Jul 22, 2022
66
10
8
rpm->cpio->folder
need to unpack each rpm+cpio.
you will get root folder which uses all linux systems:
/
/boot
/etc/
/lib/
/usr/
/var/
/root/

etc. just check that /proc /dev /sys exists
each rpm adds own files and links to this root
Do I need to copy the folders or just the files contained in them into 1 folder? Currently using 7zip to delve into them. For example inside apache-1.3.31-10.ppc.cpio I've got:

bin
conf
htdocs
include
libexec
logs
 

Renat

Member
Jun 8, 2016
57
19
8
41
with 7zip you can select all and make "extract to one folder" and not overwrite files if ask.

each partition on CF-card should have all folder structure as on any linux system

apache rpm/cpio packed with his structure (conf and htdocs in /usr/apache folder)

There is no need to think how and where to copy files cause archives packed with folder structure.
 
  • Like
Reactions: Marc_

Marc_

Always a school day
Jul 22, 2022
66
10
8
Unpacked them all so now have folders (files at the bottom). Proc folder is empty though and 7zip couldn't copy all the files due to not having permission so has created a blank file.
 

Renat

Member
Jun 8, 2016
57
19
8
41
proc is temp folder, it should be empty.

maybe you should read a book how *Nix system works.