Partner ACS 3.0 Dying

[DJohn100]

Our Partner ACS 3.0 system has died twice.

When this happens, phone LCDs remain lit, so they're still getting power, but nothing works. All intercom and line buttons are dead. Incoming calls on Line 1 are answered with a generic message that says the line isn't programmed and then hangs up. All other lines do NOT answer.

The first time I was offsite and only able to talk someone through a POR. The 2nd time, I looked at the system unit.

The processor led was out, and the VM led had turned yellow. The first 2 module leds were green. Did POR again.

Have since been able to connect via remote access (slowly), but diagnostic file is empty. Took backup to B/U card and to my PC.

I'm afraid CPU is slowly dying. Haven't had much luck finding refurbed 3.0 processor, but can find plenty of R6 and R7 modules. I'm thinking of upgrading the system to R6 (I've read R7 has bugs) and then taking backup and buying another R6 CPU so that if system dies hard, I can go forward without rebuilding system from scratch.

Does this sound like a good idea, or am I barking up the wrong tree?

Any advice is welcome. Thanks!

 

[Dexman]

The R3 is an old revision. Upgrading to a new R6 sure can't hurt! The only problem you will have is that the processor will need to be programmed from scratch.

 

[allisland]

Why not just buy an Rel6 upgrade/backup/remote access card(make sure it's new or no upgrade)upgrade old unit then backup to card. When the old "R3" now R6 goes then buy a new Rel6 and restore from card.

 

[skip555]

partners such a easy system to program what the big deal about programing from scratch ?

 

[Dexman]

While it is possible to upgrade the existing processor to the R6 level, if the CPU, or some other component, is causing problems, a hardware update would seem to be a better way to go.

 

[DJohn100]

What I was suggesting is to upgrade the current cpu to R6. and then buying a backup (R6) processor module so that if (when?) it goes, I have one in stock to replace it without taking significant outage. As for the programming, why take the time and trouble to re-enter everything when I can just restore via remote access or backup card?

 

[Dexman]

I want to make sure I understand the situation. If my description is wrong, please let me know.

Are you are looking to backup the existing R3 configuration to the PC card, then upgrade the processor from the R3 to R6 level and then restore the R3 configuration that was saved on the PC card to the now R6 processor?

If so, it won't work. You can only backup & restore to the same revision (R3 to R3 or R6 to R6)

 

[DJohn100]

No, I was planning to upgrade the current system to R6, and then backing it up (again) to my laptop. Then if the processor finally dies I would install a new R6 processor, restore from backup and hopefully be good to go.

I'm also assuming this is the best way to migrate to a new R6 processor card if I don't want to wait for a failure.

Yes?

 

[Dexman]

The only thing that has me scratching my head is wanting to upgrade the R3 to the R6. In order to do that, you will need to purchase the upgrade card in addition to a spare R6 processor.

I would lean towards just purchasing a new R6 processor, program it and replace the existing R3 with it.

Much less fuss & work to deal with.

 

[1043]

I carry with me a multiuse ACS R6 upgrade card. Whenever I replace an ACS R3 or higher with an R6, I will do the following.
1. backup the ACS R3
2. upgrade the R3 to an R6
3. backup upgrade R6 to back up card.
4. restore backup to new R6
5. test config.
6. upgrade new R6 to "K" patch.

Upgrade should work on ACS 1.1 or higher but not always. R1.0 should not be upgrade higher than 5.0. Sometimes it works sometimes it doesn't. I use R3.0 as the cut off point because they are actually labeled on the processor and I know they are not upgraded from a 1.0.