i have srx650 already running software 10.0R2.10.
but there have chassis alarm :
Alarm time Class Description
2010-01-05 14:47:58 WIT Minor Host 0 Boot firmware requires upgrade
i found at this forum and KB, by that alarm we must upgrade the u-boot. By following this instruction http://kb.juniper.net/index?page=content&id=KB16317&cat=SRX_650&actp=LIST, also failed.
Then i found this instruction http://kb.juniper.net/index?page=content&id=KB16248&actp=search&searchid=1262673768570 .
But still cannot upgrade the u-boot.
root@SRX% bootupgrade -u /boot/uboot -l /boot/loader
Error: upgrade address wrong 0xbfe00000 0xbfc00000 0
root@SRX% nvram setenv boot.upgrade.uboot 0xbfe00000
nvram: Invalid CRC on Saved Environment
This article hsa just been updated. The info you need should be there. Try these shell commands instead.
kenv boot.upgrade.uboot=0xbf400000kenv boot.upgrade.loader=0xbf600000
Then try the bootupgrade command again and reboot.
thanks for the updates, and working now to update the env value.
But after run that command, and restart the box, i cannot access the srx, even by console also.
I look at RE board, all led is off.
What should i do ?
does anything show up on console after pwoer cycle?
No, srx doesn't show anything after power cycle
any suggestion ?
Hmm, I would suggest
- hard power cycle
If that still fails, no lights on RE, then I think only way is to RMA the RE unfortunately, if nothing is seen from console for boot then there could be some other underlying hardware issue 😞
- hard power cycle -> done, no effect
- reset RE -> done, no effect also.
better i request RMA to TAC to solve this issue.
Is the device still usable? I am affraid that I might get the same issue when I upgrade my SRX240 if I need to RMA it I would like it atleast to be able to perform its features.
which ver are you upgrading from and to?
SRX240 upgrading from Junos 10r1.6 to 10r2
Should be fine, try to upgrade using cli and have console access as well.
do you already upgraded or not ?
upgraded to 10R2 with latest boot loader using the shell worked fine no issues at all from my understanding this issue only happens to the srx650's
do you change this variable on your srx ?
after i change this variable and restart the box, my srx unable to boot up.
Actually that KB is only for SRX650. The bootenv is specific to that. For 240 it should be this:
root@SRX240-A06_31% kenv | grep ubootboot.upgrade.uboot="0xbfc00000 "root@SRX240-A06_31% kenv | grep loaderboot.upgrade.loader="0xbfe00000 "
You need to revert back. If that does not work you need to reload the uboot, loader then install from usb
How can I reload the U boot, I cannot access from the console.....
Is there any literatur to deploy Uboot on the SRX?
for uboot upgrade from tftp :
for uboot from shell:
only for 10.0
you will definitely need console actually.
what if the u boot is crash, can I recover it?
you should be able to break the boot seq then reload the uboot and loader. if you are already at the loader prompt, then if you have usb you can reinstall junos to recover the box.
Just wanted to post that I successfully upgraded u-boot following http://kb.juniper.net/KB16248 for my SRX650. I was getting the CRC errors indicated in the KB.
Did you rebooted your SRX after changes the variable ?
I have a SRX-240H that got the failed to upgrade boot loader:
Upgrading Loader...bootflash write failed: Operation timed outloader upgrade failed: Operation timed out
Tried to down grade back to 10.r2 and now the box is not accessible. I found the KB14175 article. This article references a u-boot-crc.bin and laoder_crc. Where can I find these files? I am assuming once i have them on a TFTP server I can then start the upgrade process again.
Open a case with J-Tac....I had the same with our SRX210...
Be sure to ask specifically for those files and be sure to mention the KB article.
The engineer I had never experienced it before, but after searching he found the 2 files at posted to me.....
After another 5~10 minutes and the box was back up
> do you change this variable on your srx ?
> kenv boot.upgrade.uboot=0xbf400000> kenv boot.upgrade.loader=0xbf600000
> after i change this variable and restart the box, my srx unable to boot up.
When you say your SRX does not boot up, what does it mean?
"does JTAC have tried to power on or anything my failed unit before replace the new one??"
No, those units go back to manufacturing for root-cause analysis. JTAC does not normally have access to returned units.