|
Joined: May 2005
Posts: 90
Member
|
Member
Joined: May 2005
Posts: 90 |
Our InterTel Axxess 5.x PBX is throwing a 104 alarm every morning for the last week.
From what I remember from last time this happened, I need to backup the database, shut down the PBX, pull the battery strap, and reload the database.
Could this be happening because the battery on the CPU is bad? Should I be replacing that?
Also... when I shut down... what's the proper procedure for the EVMC card... I don't want to mess up its hard drive in the shut down process.
Thanks!
Last edited by philodendrin; 01/18/13 05:11 PM.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
if memory serves me, 104 is a T1 alarm. I would check the message print and find out why it is flaming out before I would go to that much trouble. To shutdown the EVMC there should be a button on the card to do a proper shutdown. If you just jerk power, you could corrupt your avdap DB. You could also attach a monitor and keyboard and do it that way as well.
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
Alarm 104 indicates a CPU database corruption, possibly due to faulty memory chips. Contact your dealer for assistance.
To shut down the EVMC, press the power down button. The OK To Remove Card light will flash, then light steady. It's now ok to remove the card.
T1 is Alarm 114.
|
|
|
|
Joined: May 2005
Posts: 90
Member
|
Member
Joined: May 2005
Posts: 90 |
Here's what I see in the logs... not much to go on, as far as whether or not it's a battery or faulty memory chips.
01:276- 01:00 01-12 A104 ALARM CPU: Database Corruption -01:277- 01:00 01-13 A104 ALARM CPU: Database Corruption -01:278- 01:00 01-14 A104 ALARM CPU: Database Corruption -01:279- 01:00 01-15 A104 ALARM CPU: Database Corruption
As the network admin, I generally act as the vendor... any more troubleshooting I should do on my own? Should I proceed with trying to reset and reload database?
|
|
|
|
Joined: Sep 2010
Posts: 59
Member
|
Member
Joined: Sep 2010
Posts: 59 |
The manual says. CAUSE: The database stored in battery-backed memory on the CPU board did not checksum properly. The system performs the checksum test once a day to verify the integrity of the database. The memory chips may be faulty. However, there is one way this condition can occur without the memory being faulty. If the processor is doing a write into protected memory at the exact moment an external interruption occurs (loss of power, pressing the reset button, etc.), the data written to the write-protected memory may be corrupted. ACTION: Save the database to the computer via an “axx†file as soon as possible. Do not save the “axx†file on top of a previously known-good database because this database may be too corrupted in a critical location. Keep in mind that the “Backup Database†may be a non-corrupted database. If the existing database appears corrupted, default the system's database, without the voice processor connected. After the system powers up, the default database LED will be on. Reset the system one time to force a “Backup Restoreâ€. If the “Backup Restore†reveals a corrupted database, restore the last known “axx†file.
Answer The Phones Telephone Engineer UK
|
|
|
Forums84
Topics94,515
Posts639,947
Members49,847
|
Most Online5,661 May 23rd, 2018
|
|
2 members (Carl Navarro, C5Z),
241
guests, and
29
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|