IP Office 500 Startup

[sweetac]

Hello, I purchased a n IP Office 500 that was being used as a demo unit. When I power it up I get 1 LED on the IPO Carrier card, LEDs for DS card ports 9-12 and a flashing LED on VCM 32 card. Every 5 seconds I get an amber LED flash on the carrier card, port 1 on DS card and VCM card.

I can ping the unit and get a response but Manager does not detect it. I have tried resetting by holding reset button down for 35 seconds, as well as through DTE port and terminal session but the IP address remains non-factory and Manager is unable to detect it.

Any ideas what I can do to get this unit reset and working?

Thanks!

 

[tlpeter]

Sweetac, get someone who knows the product.
DTE should not be used and when you use it then use the right commands.
Connect it again and type this:

AT <enter>
at-debug <enter>
system <enter>

Now you will see the ipaddress in hex.

Or you can default the unit this way:

at-debug <enter>
erasenvconfig <enter>
eraseconfig <enter>
reboot <enter>

PS, demo units with all licenses should never ever been sold to customers.
When you have a problem then Avaya will not help you at all!!!


BAZINGA!

I'm not insane, my mother had me tested!

 

[bdelmar]

you try the basics first?

Try going in through the WAN port which is 192.168.43.X?

you sure Manager the same release as the IPO?

You sure the windows firewall is turned of on the PC and you have a static address?

 

[mattKnight]

Does the unit have a smartcard plugged in?

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[tlpeter]

Does the unit have a smartcard plugged in?

That would be a jaw breaker!!!
That message will come by a lot when you use the DTE port
It cannot be overlooked at all!!!

BAZINGA!

I'm not insane, my mother had me tested!

 

[sweetac]

Thanks for the replies. I got it working. I have to mention, though, to tlpeter that many assumptions were made in your reply.

Quote:
"get someone who knows the product" - that's why I'm here

I think it was assumed that I was only trying to change the IP address. That's not the case. I was trying to default the unit. Since the reset button procedure did not work, DTE port IS the correct way to do it, as per Avaya documentation/training. The commands AT-debug and system are not required to view IP address, as it is displayed to console output when the unit boots. The issue was that after following the Avaya-suggested procedure for erasing the flash, the IP address was not changing. Finally, I would never sell a demo unit to a customer. I'm an authorized Toshiba, Nortel and Digium partner but picked up this unit as a lab system to learn about the Avaya IP Office system, as I have several customers that have this system.

Ok, for the fix. It was 2-part. I was finally able to connect to it using IPO Manager after installing Manager on a different PC. I found several posts on Avaya's forum that indicated there is a defect in the Admin Suite that shows up only under certain conditions. The fix in most was to install it on different systems until it works. Luckily for me, the second system I installed it on detected the unit right away. After I was in, I had to perform an upgrade from there and now the unit is in perfect working order. I am now able to change the IP and configure the unit.

Thank you to everyone who responded.

 

[tlpeter]

Sweetac, DTE should only be used when nothing else does not work.

And yes at-debug -> system does show the ipaddress just as a reboot does.
But it goves also the current software version.
I am glad that the demo licenses are not sold to a customer.

I make those assumptions because it was not very clear that you knew what you where doing.

There are a lot of people coming over here that totally not knowing the IPO and try to get it all setup without paying a certified tech.

The at-debug -> erasenvconfig -> eraseconfig -> reboot defaults the IPO completely without erasing the software.

I am glad you have it working now by the way.


BAZINGA!

I'm not insane, my mother had me tested!

 

[TomMills]

I make those assumptions because it was not very clear that you knew what you where doing."

not to mention that the LEDs described suggest that the system was absolutely fine.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[IPGuru]

to reinforce tlpeters statement on the DTE port
the DTE port should only be used to erase the cfg when the only other alternative would be to replace the unit.
If the unit is operational then erasing the cfg is not req.

The IP address as you now can be identified on boot & the security settings can be defaulted via the DTE port without erasing the cfg

I have lost count of the number of systems I have had to resurrect because someone has prematurely reached for the DTE port & erased the firmware by mistake.


I do not Have A.D.D. im just easily, Hey look a Squirrel!

 

[tlpeter]

IPGuru, with at-debug this can be done too (no need to normally)
Also with the command "system" from at-debug you will see the ipaddress in hex just like when you see it when you boot the ipo.
On a live running system you do not want to boot it.
That is why i love the at-debug option so much


BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

As Tom said, the IPO is running fine. if you want to change the IP of the unit, then the unit can be found via layer 2 rather than IP just by opening manager and do a search in the IP field for 255.255.255.255. Once the IPO is discovered, you can then bind the required IP to your network adaptor and manage the newly discovered IP Office.

ACSS - SME
General Geek

 

[sweetac]

The ultimate goal was to erase the config to start from scratch. I wanted to do this from IPO Manager but was unable to connect to it through normal means. This was a test unit before I bought it and am trying to learn it from the ground up. I prefer to "factory default" devices when the device has previously been used, especially if it was a lab device previously. I agree, seeing the LEDs indicated that everything was fine, which was why I was looking for guidance here. As it turned out, the Avaya Admin Suite (at least the version that came with the unit) does not work on all PCs. Both PCs used have XP SP2 but my HP laptop would not detect it. My Dell laptop with the same admin software detected it fine. All security suites were disabled on the HP also. I had run across multiple reports of this on the Avaya forums and, as it turned out, this was the issue.

 

[TomMills]

weird. never seen that before.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[madwok]

Hope this would help .

=== Cut & Paste from IPO installation manual document =====

The IP500 control unit includes a Reset button not found on other IP Office control unit.
Pressing the button while the control unit is starting up will pause the start up until the button is released.
The effect of pressing the button during normal operation will depend on how long the button is pressed and is indicated
by the CPU LED.

(seconds)CPU LED Action Summary
0 to 5. Off None None.
5 to 10. Orange Reboot When Free Reboot when free with new incoming/outgoing call
barring. A reboot using the reset button is recorded in
the Audit Trail.
10 to 30. Flashing orange Erase Configuration/
Immediate Reboot
Erase the configuration, alarm log and audit trail.
Immediate reboot without waiting for active calls to end.
See Erasing the configuration for full details.
30 to 40. Red Erase All. Erase configuration, alarm log and core software. See
Erasing the Operational Software for full details.
Over 40. Flashing green None None