upgrade failure 406 1

[pops185]

unit failed upgrading ....getting red light on unit
open tftp log in Manager as 255.255.255.255 unit was
192.168.42.1 ( manager pc 192.168.42.2)

I see nothing in tftp log other then after reboot:

Fri 29/4/2005 08:36:56 : Log starts


Manager still has the boot directory from before:

MAC 00e007005f26
IP ADDRESS 192.168.42.1
FILE NAME ip406.bin
TIME OFFSET 0

----------------------------------------------------------
I went through the upgrade wizard out of box 2.1.15
upgrade to 3.0.40 its a 406 and not 403 so I should not have to go to 2.99 then to 3.0.40

I tried the route of the DTE port as 38400 8-N-1
rebooting the unit shows only this after reboot:

P3 Loader 0.2 (4MB-2x29LV160 Flash-120nS SDRAM-10)
CPU Revision 0x0502

I did not have to press esc key as it seems to stop after this ........power down unit , power back up still
only showing :

P3 Loader 0.2 (4MB-2x29LV160 Flash-120nS SDRAM-10)
CPU Revision 0x0502

......so I tried to do the commands to reset the unit per the instructions (great faq by ipguru !)

AT-X2
0xef00C000H Erase
OK
AT-X3
0xef010000H Erase
OK
AT-X
Multi-Sector Erase
OK

I still can not get into the unit through manager or even
ping the unit as 192.168.42.1 ....still showing red led on the front of the unit .....I have reset a couple of units without this kind of issue .....Thank you for any and all post ....


pops185

 

[IPOUK]

I bet it is still uplinked to your switch? So as you did a AT-X2 and 3, that has defaulted your config..(hope you have it backed up somewhere). Take the uplink out, and do a x2 and x3 again and then pull the power, you should then be back on 192.168.42.1 and should see the file go across! At the moment it is probably on a dhcp address, hence the bootp entry is useless - happened to me before and drove me mad.

 

[NuggiFirst]

If an AT-X has been performed, then the unit has no bin-file, and are not able to boot.

In this case the unit will light steady red.
You'll have to load a new bin into the unit with a TFTP-server (Manager). You can follow IPGuru's excellent FAQ: faq940-5354

Then you should be up and running.

Why did it fail??
Did you have a fixed IP-adress on your maschine when you performed the upgrade?

 

[pops185]

Nugifirst
Yes I did have a fixed address (192.168.42.2 with
255.255.255.0 as netmask) I always set my machine to 192.168.42.2......leaving the manger tftp log open just shows the date .....
I see nothing in tftp log other then after reboot:

Fri 29/4/2005 08:36:56 : Log starts

I will try in the morning when I get a chance as this site is new and not installed yet...Thank you to all !

Pops185

 

[wolfware]

Well I followed the instructions to the letter on our backup IP403 unit and now I have an IP403 that I can't connect to other than through the DTE interface. At the DTE interface it loads and stops at the following message...

IP403Loader 0.81 (4MB-2xLV160 Flash-120nS SDRAM-10) CPU Revision 0x0502

I can AT the unit and have issued AT-X2, AT-X3, AT-X4 commands successfully and received the correct response for these commands.

When I then re-power the unit I get the same message as above.

Because the unit no longer loads beyond this point I cannot reload the firmware.

I have tried pinging it on the address I had it configured to before it went wrong and have also tried pinging the default 192.168.42.1 address, both to no avail.

Pretty screwed, any suggestions?

Thanks, David.

 

[IPGuru]

check for firewalls & other software on your PC/laptop that may interfere with the TFTP requests.

Symantec VPN client software is known to cause these sorts of problems.

once you have resolved this View TFTP log should at least show the tftp requests form the IPO & enable you to manualy creat your Bootp entry if needed.

 

[wolfware]

Will do, not back at the problem until next Tuesday so will let you know how it goes then. Thanks.

 

[wolfware]

Thanks, Checkpoint Secure Remote Client. I had stopped it but I needed to unbind from the protocol stack to truly get it out of the way. Cheers.

 

[IPGuru]

Those things are a right P.I.T.A. Took mne ages to realise what the problem was the 1st time I had it.
I will update my FAQ