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 rebooting constantly 2

Status
Not open for further replies.

khaloudovic

Technical User
Dec 26, 2014
20
TN
Hello,

I have a 500v2 IP office that reboot every 25 seconds, so every time i put the IPO in the power it stay rebooting constantly, i can't even ping it.

So i formatted the sd card using the manager application then i have recreated it, and i have tried all system versions : 9.1, 8.1, 6.0, 5.0 and always the same problem.

Shen i remove the memory card the IPO do not reboot any more.

So i have connected an rs232 cable and this is what i get :

CPU Board Version is: 0x03
CPU PLD Version is: 0x24
CPUID: 0x12 Present: 0xAF Present2: 0x02
Using FPGA build 0x00000824
Programming FPGA ...
FPGA ID 0x01 Version 0x00 Build 0x00000824
Initialising NAND device.. registering..
Added device: Samsung 64MB NAND (small block) - 0x0001

SMXFS: This is a SD 2.0 card
OPTIONAL SD Card not present/recognised
Initialising FileSys device.. registering..
Added FileSys device
Running:
A:\system\primary\ip500v2.bin
Reading main image file..
Read complete


Directly after the Read complete the IPO reboot
Any ideas ?

Thanks.
 
Tried another SD Card?

"Trying is the first step to failure..." - Homer
 
Pull out all modules, disconnect everything except power and Ethernet, try again. Is this the initial startup? May simply be a bad unit.
 
Default the IP Office using the serial port?

Maybe old corrupted config is present in the system.

 
hello, and thanks for your replies,

I have tried another SD Card and i have the same problem, i have disconnected the modules and every think, it still rebooting again,
and now i have default the config using the serial port DTE cable and always the same problem.

Could this be a hardware problem ? how can i diagnose this issue.

Thanks.
 
I assume this is an Avaya SD card? =)
Try the same card in another IP500, if it works there you have a bad unit.

"Trying is the first step to failure..." - Homer
 
Yes it's an Avaya SD card and it works fine in another IPO.

So you mean that i have a hardware problem with my IP500 ?

Because when the IPO charge the ip500v2.bin file it reboots, that's why i was thinking that there is a software problem.
Anything i can do to fix the firmware or something ?
 
You could try to erase the software if you already tried eraseconfig and ereasenvconfig through DTE.

To erase the core software using Debug
1. Run IP Office Manager.
• In the BOOTP entries, check that there is an entry that matches the MAC Address, IP Address and .bin file used by the system. An entry is normally automatically created when a configuration has been loaded from that IP Office. .
• If an entry is not present, create a new entry manually. The first two details can be found in the Control Unit settings in the configuration file. Then close and restart IP Office Manager.
• Under File | Preferences ensure that IP Office Manager is set to 255.255.255.255. Also check that Enable BootP Server is checked.
• Select View | TFTPLog.
• Check that the required .bin file is present in Manager's working directory.
2. Attach the serial cable between the PC and the RS232 DTE port on the IP Office control unit.
a. Start the terminal program on your PC. Ensure that it has been setup as listed in RS232 DTE Port Settings. Within a HyperTerminal session, the current settings are summarized across the base of the screen.
b. Enter AT (note upper case). The control unit should respond OK.
c. Enter AT-DEBUG. The control unit should response with the time and date and then Hello> to show it is ready to accept commands.
3. To erase the current configuration in RAM memory enter upgrade.
4. The IP Office will erase its current software and then send out a BootP request on the network for new software. IP Office Manager will respond and start transferring the software using TFTP.


"Trying is the first step to failure..." - Homer
 
Janni78 thanks for your support,

I did every think you said until the 2.c when enter AT i get OK but when i enter AT-DEBUG i get nothing, the system don't give me any response. I did this without the SD card because when i put it the IPO will reboot and don't give me the opportunity to enter any command.

I have also tried to erase the software by pressing the reset button for 30 to 40 seconds but no response.

Is there any other method to erase the software please ?
 
I've had to return a chassis that did similar, don't waste too much time as a faulty chassis is far from impossible :)

 
First load a 9.0 firmware on the SD card insert it in the IP Office and power it up, then press and hold the reset button for at least ten seconds but no more then 15 seconds.
See what happens, show the log from the serial port.
Erasing the config and firmware is of no use, today i've had a similar issue and the above solved it for me on two systems with the same issue.
You don't have to recreate the card, just copy the 9.0 ip500v2.bin file to the SD card in the folder "system/primary".
 
Thank you amriddle01 for your response, i think you are right because there is no way to solve the problem.

hi intrigrant, yes i did what you said with by copying only the file ip500v2.bin in the SD card system/primary for the versions : 9.0, 9.1, 8.1, 6.0 and 5.0 but always the same problem, in the log with the serial port i get like always :

Running:
A:\system\primary\ip500v2.bin
Reading main image file..
Read complete


Then reboots again every time
 
Hi , Thanks intrigrant my non responsive IPO just came back to life - was running 9.1.4 , non responsive to default with reset button, non responsive to default using debug on the rs232 . I loaded 9.0.3 ip500v2 bin file on the SD card , replacing the 9.1.4 bin file and rebooted - hey presto system is alive. Thankyou
 
there is a problem with IPO V2 cabinets with PCS 14 AND LOWER MUST BE FORMATTED AT 8.1.65 OR HIGHER BEFORE YOU CAN TAKE THEM TO 9.0 OR HIGHER.
IP Office Technical Tip
Tip Number: 276
Release Date: 10 February 2015
Region: GLOBAL
Upgrading IP500 V2 Control Units to Release 9.1 Software
This Technical Tip is to advise customers upgrading IP500 V2 Control Units to Release 9.1 Software to check the Product Change Status (PCS) level of the unit before upgrading.
Control Units identified as PCS 14 and below must first install release 8.1(65) (or higher 8.1 release) or any 9.0 release before upgrading to release 9.1. This is necessary to expand the loader to accommodate the 9.1 software image. The PCS level can be found on the printed label at the rear of the unit or the shipping box.
If the Control Unit has not been used previously, care should be taken to ensure that no calls are made before the upgrade to Release 9.1; otherwise the system will require a 9.1 upgrade license despite being a "new" unit.
If a pre-built SD card loaded with 9.1 software is to be used in a new Control Unit that is PCS14 and below, the SD card must first be recreated using 8.1(65) or above, or any 9.0 release.
Control Units at PCS 15 were manufactured from November 2014. Units at PCS 15 and above already have an updated loader and do not require the interim upgrade step.
Issued by: Avaya SMEC Customer Product Engineering Support
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top