Mailing List Archive

On So, Dez 16, 2018 at 03:11:02 +0100, Clement Cavadore <clement@cavadore.net> wrote:
>
> Anyone has some intermediary versions for me ?

Do you already know, what version is needed?

V02 seems to be really antique. However it might be the proper version
if the switch is being used in a historical context :-)




_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Hello Franz Georg,

I was pretty sure you'd be the first to answer my strange question :-))

Actually, the release notes does not inform me regarding the
intermediary version. I found an intermediary (sxs04300.bin) on another
device, but I cannot extract its bootrom code, and trying to move to
4.3 directly from my 2.0 seems to be impossible.

Do you have some choices ? :-)

I am willing to update to the latest 7.2.02 as it will not be used in a
prehistoric context :-D

Thanks !

Clément


On Mon, 2018-12-17 at 10:48 +0100, Franz Georg Köhler wrote:
> On So, Dez 16, 2018 at 03:11:02 +0100, Clement Cavadore <clement@cava
> dore.net> wrote:
> >
> > Anyone has some intermediary versions for me ?
>
> Do you already know, what version is needed?
>
> V02 seems to be really antique. However it might be the proper
> version if the switch is being used in a historical context :-)
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On Mo, Dez 17, 2018 at 10:54:33 +0100, Clement Cavadore <clement@cavadore.net> wrote:
> Hello Franz Georg,
>
> I was pretty sure you'd be the first to answer my strange question :-))
>
> Actually, the release notes does not inform me regarding the
> intermediary version. I found an intermediary (sxs04300.bin) on another
> device, but I cannot extract its bootrom code, and trying to move to
> 4.3 directly from my 2.0 seems to be impossible.
>
> Do you have some choices ? :-)
>
> I am willing to update to the latest 7.2.02 as it will not be used in a
> prehistoric context :-D

You can try to flash the Image without updating the bootcode.
The new version might boot and you could then flash bootcode & Image to
the final version.

However, you might want to flash into secondary flash in case it isn't
able to boot.



Best regards,

Franz Georg
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On Mon, 2018-12-17 at 12:07 +0100, Franz Georg Köhler wrote:
>
> You can try to flash the Image without updating the bootcode.
> The new version might boot and you could then flash bootcode & Image
> to the final version.
>

Already tried, but same problem: seems that 2.0 -> 4.3 is impossible
without another intermediary step :)
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On Mon, 2018-12-17 at 12:10 +0100, Clement Cavadore wrote:
> Already tried, but same problem: seems that 2.0 -> 4.3 is impossible
> without another intermediary step :)

Found some infos on prehistoric manuals:
https://www.manualslib.com/manual/843560/Foundry-Networks-Fesx.html?pag
e=717#manual

I have a FSX I think, as the code filename is FEXS02000a.bin and not
some SXR/S/L format

Thanks to someone who replied off-list, I got a bunch of old codes,
starting at 2201a, however even the boot code does not seem to be
working

SW-FESX424+2XG Switch#copy tftp fla xxxxx FESX4/2201a/sxz02100.bin bootrom
SW-FESX424+2XG Switch#The image type 2.53 is not correct, abort!
File Type Check Failed

TFTP to Flash Error - code 8


Maybe someone has some earlier bootrom code ? :-)


Thanks all for your help, so far !
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Update:

I have been able to upgrade that old FESX with a newer code (4001a),
using a tftpboot from bootrom!!

FEX Boot Code Version 02.0.00
Enter 'b' to stop at boot ...
FEX-Boot>ip add 193.43.xxx.yyy/26
BOOT INFO: load monitor from boot flash, size = 49562
BOOT INFO: prepare tftp client...
IP address = 193.43.xxx.yyy, subnet mask = 255.255.255.192
FEX-Boot(193.43.xxx.yyy)>ip default-gateway 193.43.xxx.zzz
IP default gateway = 193.43.xxx.zzz
FEX-Boot(193.43.xxx.yyy)>boot 
system           System
FEX-Boot(193.43.xxx.yyy)>boot sys
system           System
FEX-Boot(193.43.xxx.yyy)>boot sys 
flash            from flash
tftp             from tftp server
FEX-Boot(193.43.xxx.yyy)>boot sys tftp 
IP address       Server address
FEX-Boot(193.43.xxx.yyy)>boot sys tftp FESX4/4001/4001a/SXL04001a.bin
Syntax error /FESX4/4001/4001a/SXL04001a.bin/
FEX-Boot(193.43.xxx.yyy)>boot sys tftp 193.17.xxx.yyy FESX4/4001/4001a/SXL04001a
BOOT INFO: tftp copy successful!
BOOT INFO: start with hardware reset
BOOT INFO: load monitor from tftp copied image, size = 185563
BOOT INFO: load tftp copied image..........
BOOT INFO: bootparam at 0008c2e8, mp_flash_size = 00302b5b
BOOT INFO: code decompression completed
BOOT INFO: branch to 00400100
Pre Parsing Config Data ...

(...) SW: Version 04.0.01aT3e1 Copyright (c) 1996-2007 Foundry Networks, Inc.
Compiled on Feb 19 2008 at 18:37:10 labeled as SXL04001a
(3156827 bytes) from Tftp FESX4/4001/4001a/SXL04001a.bin
BootROM: Version 02.0.00Te6 (FEv2)
HW: Stackable FESX424+2XG-PREM


==> After that, I have been able to upgrade bootrom to 07.2.00T3e5, and
main code to 07.2.02rT3e3.

Thanks for those who replied privately with older codes and hints, you
will make some nonprofit orgs happy :-)


Clément
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp