IP Office in Continuous Reboot 1

[SSMaterials]

I have an IP Office Small Office Edition that goes into continuous reboot. This happened after an upgrade. I upgraded it from 2.2 to 4.7.

Any advise would be helpful i.e. reason why this happen, advise on fixing the issue, comment from users who had similar problems.

 

[kwing112000]

usually you will need to go in the DTE port for this. THere is a great FAQ up above on how to do it. Make sure you have everything right or it will not work. Maybe that was too big a jump to go in one step. I dont think there is a 2.2. Maybe 2.1?

 

[mattKnight]

I'll bet you missed the 3.2.999 intermediate build....

Tech tip 80 on the avaya website is worth a read

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[ProviderReborn]

As above. To put an SOE on a 4.0 version you need to use the intermediate firmware mentioned above.

Use this document to get your unit up again. Do not use 4 yet.

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

Then upgrade to 3.2 999 when that is done then upgrade to your desired 4.0 level. Pref 4.07 / 4.010

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement (Aug 30th)

 

[mattKnight]

BTW provider

if you type [ignore]FAQ940-6158[/ignore]

the forum software will link it like this faq940-6158

and you can do it with threads too [ignore]thread940-1414305[/ignore]

and it'll show like this thread940-1414305

There's neat!

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[SSMaterials]

I had a continuous reboot problem with IP Office Small Office Edition, because I did not use the intermediate firmware before upgrading to IP Office 4.0(7). I used the DTE fix FAQ940-6158: DTE Port Maintenance. The BIN file is not reloading.

I am getting this message on the hyperterminal screen.

Programming FPGA ...
FPGA Version 89
Ethernet Switch: PortId=0520, PhyId1/2=01410C1F
P6 Loader 1.1
CPU Revision 0x0502

Received BOOTP Response :C0.A8.1D.09 ip401ng.bin


I am getting this in the Manager.

Wednesday, October 10, 2007 12:35:21 PM : Log started
Wednesday, October 10, 2007 12:35:21 PM : Received BOOTP request for 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:35:21 PM : Sending BOOTP response to 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:35:21 PM : Received BOOTP request for 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:35:21 PM : Sending BOOTP response to 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:40:06 PM : Received BOOTP request for 001302a899f3, 0.0.0.0:68, unable to process
Wednesday, October 10, 2007 12:41:50 PM : Received BOOTP request for 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:41:50 PM : Sending BOOTP response to 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:41:50 PM : Received BOOTP request for 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:41:50 PM : Sending BOOTP response to 00e00701646d, 0.0.0.0:68
Wednesday, October 10, 2007 12:44:42 PM : Received BOOTP request for 0015c53f1086, 0.0.0.0:68, unable to process
Wednesday, October 10, 2007 12:46:56 PM : Received BOOTP request for 00e007014b25, 192.168.42.10:68, unable to process

The TFTP server is timing out when trying to transfer the data.

Please help in reloading a good bin file.

 

[MrBob622]

Point your Bootp entry file to the ip401ng.bin in the V3_2_999 floder under the manager directiory. Once this file is loaded on your SOE you can upgrade to 4.0.7

 

[mattKnight]

You don't have a BOOTP entry in your manager.
(that is you either have the wrong IP or MAC address)

The following in the TFTPLog indicates that a matching BOOTP entry was not found. If this occurs use Manager to add or edit the required BOOTP entry.
: Received BOOTP request for 00e007000123 192.168.42.1 napremis.bin, unable to process.

At a guess you don't have the correct IP address on your laptop....
Is your laptop 192.168.29.9 by any chance (C0.A8.1D.09)

Change your laptop's IP address to be 192.168.4.2.100 255.255.255.0 and make sure you are plugged directly into the Small Office.

It is best to do this with a low version manager (or at least point it a a version 2.1 bin file)

Also
check that the manager is set to seek on the broadcast setting rather than a targetted address.
check that the bootp entry in the manager is correct - MAC address from the system (is written on it), IPaddress is probably 192.168.42.1 unless you are plugged in to the WAN / LAN 2 port and filename is IP401NG.bin
Ensure that the "bin file" path is pointing to a location that has a IP401NG.bin file in it - use a 2.1 version (download a copy of the 2.1.78 bins from [link ftp://ftp.avaya.com/incoming/Up1cku9/SoftwarePub/2_1GA_Builds/2_1_78BINS.zip]here[/link ] if you don't have them
power cycle the Small office and monitor the TFTP log

Good luck



Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[SSMaterials]

I changed the IP address to my laptop and the bin file loaded.

Thanks

 

[Tier2_Maracaibo]

SSMaterials, exactly what you did? I have the same problem that you (by the image of the viewer is the same). As arranged?

 

[ChristianF]

The TFTP server in manager is questionable, use a 3rd party tftp server and you do not need a bootp entry. I use 3CDaemon and it works just fine.

Use 4.0(14) not any previous versions.

 

[Bas1234]

For a SOE it sometimes does an IP request on 192.168.42.10 instead of 192.168.42.1 look for it in the tftp log and change the Bootp (in the Manager) to the 192.168.42.10

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________