Hi Guys,
i don't know how but i got this procedure from some really dark area. i had to dust off few layers until i found this.
This procedure is good for cases where your switch OS is still functioning but the switch ASIC firmware itself got corrupted. for any other cases (e.g. you can't even access the switch b/c the OS is corrupted), don't wast your time.
And i am saying this upfront: USE IT AT YOUR OWN RISK !!!!!!!!!!!!!!!!!!!!!
This is an old procedure for recovery ISR9024D firmware from corrupted flash situation. Please read carefully and use technical and common sense :-)
let me start by showing the default env parameters for those of you who were looking to get things back to were they were originally:
=> printenv
loads_echo=1
baudrate=38400
filesize=235
bootargs=console=ttyS0,38400 root=/dev/ram0 rw
addip=setenv bootargs $(bootargs) ip=$(ipaddr):::$(netmask):$(hostname):eth1:none
sec=echo booting secondary, press ^c to abort; sleep 5; echo booting...; bootm d0a00000
prim=echo booting prim...; bootm d3500000
serial#=0
ecc=on
pci_enum=on
pci_listing=short
ethaddr=00.80.f9.69.fc.18
eth1addr=00.80.f9.69.17c.18
gatewayip=0.0.0.0
hostname=0.0.0.0
ipaddr=0.0.0.0
netmask=255.255.255.0
serverip=0.0.0.0
bootcmd=tftpboot;go
bootfile=path/file.bin
bootdelay=-1
loadaddr=80000
stdin=serial
stdout=serial
stderr=serial
Environment size: 602/2556 bytes
l
Next, the procedure itself:
if your switch is showing things like the following that procedure is the right for your situation. for other situations, use your own judgment:
Anafa not found
Start Firmware upgrade
\nError: Firmware upgrade FAILED (retry 1)
\nError: Firmware upgrade FAILED (retry 2)
\nError: Firmware upgrade FAILED (retry 3)
Firmware upgrade failed, call support
From attempted logins:
ISR-9024 login: admin
Password:
connecting
connect: No such file or directory
connect: Illegal seek
ConnectToServer::ERROR:Server not responding
connect: No such file or directory
connect: Illegal seek
ConnectToServer::ERROR:Server not responding
To recover from this failure:
1) We must retrieve the GUID from a sticker inside the 9024. We do not have a way to retrieve the GUID once the switch is in this state without reading the sticker.
a. Disconnect power and open the cover. (three screws and the cover slides back)
b. Look on the bottom of the sheet metal case. You will see a sticker with 2 serial numbers. The 16 digit numbers will start with 0008F1xxxxxxxxxx.
c. Right down the number and put the cover back on the switch.
2) Using a serial port connection to the 9024 login as root (default password is br6000)
3) Assign an IP address to the eth1 interface:
a. ifconfig eth1 10.0.2.170 netmask 255.255.255.0
4) Download the recovery files attached with this procedure ("ISR9024-i2c-upgrade.tar.gz")
5) Using FTP or WGET place the i2c-switch-burn.tar on the 9024
6) Create a directory, (mkdir /temp) and expand the tar into it, (cd /temp ; tar -xvf ../i2c-switch-burn.tar)
7) Make the files executable. (Chmod 777 /temp/*)
8) Copy the files: eburn and i2c to /usr/Voltaire/bin. (cp eburn i2c /usr/voltaire/bin)
9) Run gunzip against the firmware image.
gunzip firmware.ISR9024_SM.img.gz
10) Run the script using the first number recorded from the sticker (sn#1)
./ibswlrm-fw-burn.sh 0008F1xxxxxxxxxx 0008F1xxxxxxxxxx firmware.ISR9024_SM.img.gz
# ./ibswlrm-fw-burn.sh 0008F1040041082A 0008F1040041082A firmware.ISR9024_SM.iIg
FW_VER = 0.8.6
sysimage_GUID = 0008f1040041082a
Node_GUID = 0008f1040041082a
Burning ...
BURN -
100%
Verifying ...
VERIFY - 100%
11) Power cycle the 9024 (mandatory)
May the force be with you..