Help diagnose a sick IP500v2

[CTravel]

Hi,

I have an IP500v2 which is failing every 2-3 days and cannot diagnose exactly what is causing the issue as there are no log entries.
The symptoms showing are:

- Immediate disconnection
- No display on any handset
- All red lights on the front. (Port 1,9 and Port 1,9)
- No IP connectivity for management.

Powering off and back on resolves the issue as though nothing had happened ... until the next time.
There are no log entries.

I have the following hardware:
1 IP500v2
2 Combo6210/ATM4
3 Combo6210/BRI4
5 Phone2/PRIS U

Only the PRI is used, along with a handful of SIP channels.

Any pointers in diagnosing and pin pointing the problem would be appreciated.

Thank you in advance.

 

[vztech]

More info needed
Release?
Set type ?
Set firmware?
Did you take a look at the system status alarms?

It's only dialtone!!!

 

[tlpeter]

It looks like it is rebooting.
Open a monitor trace and let it run (and log) until it happens again.
Post the trace here.

BAZINGA!

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

 

[CTravel]

Hello

Thank you for replying.
It is running 6.0.18 and there were no clues in the logs of system status alarm (other than a cold start when I power cycle it)

I've set up logging now and will see if it yields any further information.

Thank you

 

[Okkie26]

Combo card supported from IP Office release 7.0

 

[rdoubrava]

Not correct. Combo cards were introduced with release 6.0

 

[Okkie26]

mm, i found info on the internet that is was supported from 7.0

 

[AACon]

Yeah combo cards are supported from R6, but the V2 combo card is R8.1. Maybe thinking UCM? Those were R7.

-Austin
ACE: Implement IP Office

 

[CTravel]

Hello,

I am still waiting for it to fail again. However, in the meantime I have come across the following error in the Alarm log.

<TLB Data>
Abnormal termination
addr=00000024 d=5 pc=f071abe0 stack=f071bc84 f071ad4c f073ab94 f06f6c88


Doing a quick search seems to indicate that
a) I upgrade and hope that the software bug has been fixed
and /or
b) Format the SD card.

Both seem to be a stab in the dark for a system that has run without hitch for quite some time.

Any thoughts would be appreciated.