restoring ip 406 ds not sucessful

[ICruz5]

Hello to everyone!

We want to restore a IP Office 406 DS stuck in reboot loop, after a simple config upload.
This is the original config, and version

we followed the procedure mentioned here

http://www.tek-tips.com/faqs.cfm?fid=6158

all of this with a manager 3.2

the ipo still stuck on this:

Programming FPGA ...
FPGA Version 0xFC
CPLD Revs: 0xC1 0xD4
CardID: 0x3A Modules: 0xEF
Expanding MPPC image ...

Expansion complete

.WATCHDOG TIMEOUT TASKname StartUp stack ff6eb8b4 ff544ea4 ff544ed4 ff457c74 ff4546b8 ff4723bc ff45aae4 ff4556b4 ff4723c4 ff54be30 ff549e28 ff4fce24 ff4fce2c ff4fca84 ff54d1f0 ff54d77c ff54cad8 ff5463dc ff45e618 ff6edf40

and repeats and repeats...

and this if we press esc key

Expanding MPPC image ...

Expansion complete

Alarm Logging enabled (max entries=8, in use=8)
Audit Logging enabled (max entries=251, in use=0)
NoCacheStaticHeap=4031852 NoCacheDynamicHeap=359060 Overflow=0
Constructor StaticHeap=-60612116 DynamicHeap=50324240
Factory Test Status 00000001
Product Variation Status ffffffff
Small Office Gateway Status ffffffff
RTC not initialised or reading is incorrect , Initialise ...
NVConfiguration:: No NV Stored default..
found FLASH file: ..\modem\zmbin004.s37, len=790
found FLASH file: ..\modem\mcode.bin, len=40000
found FLASH file: ..\vcomp\48105ak.310, len=e2
found FLASH file: ..\vcomp\48105ae3.312.03, len=1ee4e
found FLASH file: ..\platform\onehz.bin, len=3e80
found FLASH file: ding.pcm, len=40a
found FLASH file: ..\vcomp\482ak.311.09, len=10e
found FLASH file: ..\vcomp\48204ae6.311.09, len=1da6a
Re-programming FPGA ...
FPGA Version 0xfe
MAC=00:E0:07:01:BD3
htl 00010000 hth 20600000
Broadcom Switch Mode was 0xf5 now 0xf6
EthChipRevId: 0x37 EthPhyId: 0x00370037

IP406 V2 Self test
------------------
IP406 V2 DS variant
DSP conference chip detected
Sipex WAN port detected
PIPR = ff00ff00

Got to go till 28800000mS, Been testing for 3124mS
Status num=1000 pass=0 Serial Tests
HelloWorld on the SerialPort
Failed code=2000 Testnum=1000


what we do?
repeat the recovery procedure with manager 8.1 ?
check the right bin file?

within the folder of manager, this file is located

and outside this is the file

the IP office is a 406 ds

We hope anyone can help to "unstuck" this IPO.
Thanks to everyone

 

[intrigrant]

You need the "ip406u.bin" file.
You need a serial cable.
You need comms software like PuTTy.
You need a PC or Laptop with a network interface and a serial port.
You need the Avaya Management suite installed.
In Manager you need to set in preferences the Working directories to "C:\Program Files\Avaya\IP Office\Manager", enable BootP and TFTP server.
In Manager you need a BootP record with the MAC address of the IP Office 406v2, a IP Address (set it to 192.168.42.1) and the filename must be "ip406u.bin"
Set the IP4 settings to a fixed IP Address 192.168.42.9.
Connect the network interface with the IP Office, make sure there are no other network connections and disable the PC firewall if there is any active.
Start Manager and open the TFTP monitor found in the menu bar uder "View" > "TFTP log"
Connect the serial cable between PC and IP Office and open PuTTy, set the connection with the right serial port speed 38400,8,n,1.
Verify connection by typing AT followed with Enter, there should be a reaction. if not check serial cable, com port settings and only continue if the connection work.
Power cycle the IP Office while repeatingly press the escape button, in PuTTy it will show at a certain moment the bootloader.
Now type "AT-X3", wait for completion then type "AT-X2" and again wait for completion then type "AT-X".
With the last command the firmware wil be erased and when done IP Office will do a BOOTP request, Manager will respond if there is a valid BootP record telling IP Office to load "ip406u.bin" and use the IP Address "192.168.42.1", in TFTP log you must see the upload progress.
When sucessfully uploaded either IP Office will reboot or you have to power cycle IP Office manually (I forgot wether it is automatic or not).
Once rebooted the IP Office will be at factory default and can be accessed on IP Addres 192.168.42.1 with the Administrator/Administrator credentials.
In PuTTy the reboot is completed if you see a message with the string "ATA started"
If after the upload of the firmware the systeem keeps rebooting then there may be a hardware failure.

This used to be a FAQ but I deleted it as the IP406v2 is out of production for some years and you would be better off buying a IP500v2 chassis.