Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office 406v1 attempted upgrade and now won't boot?

Status
Not open for further replies.

leadacid44

Technical User
Jan 20, 2011
13
US
Hi folks-

I was digging through our spare parts closet the other day and I came across an old IP Office 406 V1. I got it up and running today with a laptop and was hoping to use it for training/testing, etc. when I make changes to our production 406 V2.

So since it was on the V2.X (not 100% sure what it was) of the firmware, I figured I'd attempt an upgrade to the newer version. Unfortunately I think I must have done something wrong. The auto-upgrader application worked just fine, did the validate, the whole nine yards. Unfortunately I'm not sure what version I attempted to upgrade it to. 3.something for sure.

Anyway, whenever the system reboots, it looks like it is going to start booting (where it would flash all of the lights on the front of the unit and start counting down to the left) but it flashes all of the lights very quickly (less than a half second) then it reboots again. If I hadn't JUST done a firmware update I'd have thought it was a bad power supply.

So I attempted to do a DTE restore, following the instructions from here:
And I was able to reset the configuration (so its not totally dead, so probably not power supply) and perform the BOOTP and TFTP download, but as soon as it attempts to load the software again (the only thing I can think it's doing) it does the light flash and restarts.

I tried using the oldest firmware I could get my hands on, but I can only seemingly find stuff from the 3.X series, nothing from the 2.x series.

Can anyone help me figure this out?

Thanks!
 
1.x and 2.x was a finnicky thing adn depending on which release you needed to either broadcast or put the exact IP address in to upgrade.
But that is besides the point as it is too late for that.

Try and DTE it again and make sure that you have a bottp entry with the correct MAC address, default IP address (192.168.42.1) and also pointing to the correct file IP406.bin also if you have that browse to that correct file as that sometimes helps.
Make sure you have Manager running and you can see in the TFTP log that your system requests the files. If you don't see these requests then something is wrong and just redo the DTE reset again. I had it happen that I had to do it 10 times until the system finally did what it was supposed to do and do also a hard reboot every so often if you have troubles with it.

IP406 V1 is the one without any extension ports in the front just to clarify, any V2 has extension ports.

Joe W.

FHandw, ACSS

 
Joe, thanks for the response. Yep, its a V1, no ports on the front. I was successful with manager and TFTP. It seems that even uploading a different IP406.bin causes the same issue, the flashing lights and then reboot. To be fair, I can't confirm its doing that specifically, but I've seen my fair share of bad firmware uploads that it looks an awful like some I've worked with in the past.

I've been reading and apparently the 2.X->3.X version update upgrades the bootloader. Is this true? If so, I suspect it could be possible to upload a new 3.x binary image that is incompatible with the 2.x bootloader.

Should I try to find a 2.x series binary? Any idea where I could? I haven't yet been able to find one, just the 3.x series.

Or am I barking mad and there's now way to get this thing working again? :)

Thanks!
 
If you wipe the system completely then you should be fine, but see if there is a 406.bin in any of the folders that are interim releases (3.0.999 ; 3.1.999 etc) but I think those were only used for 406V2 units.
TBH I am not even sure how far the V1 can go in the releases so I had a quick look in TB52 and it says that you need the 3.0.999 to make room for the larger 3.1 (and following) bin files.
So if you have that release then go ahead and use that one before going to 3.1 or higher.

Joe W.

FHandw, ACSS

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top