IPO rebooting

[kavsagol]

We have a client with 20+ IPOs. We divided the IPOs into 2 SCNs, and we configured all of them to connect to each other through IP trunks. Those is the SCN have IP networking enabled, the others don't.

One of the IPOs, a 412, started rebooting in a loop, and after a few times it stopped rebooting and now it works fine. The alarm log shows this error:

We contacted Avaya about other problems with this client, they told us they cannot help us unless we upgrade to 3.2, which is impossible at this stage, since SCN will not work with mixed versions and we cannot upgrade 20+ IPOs at once.

Any help would be appreciated.

 

[aarenot]

Sounds like a project to upgrade the 20 units. Looks like you have a weekend of upgrades coming soon. I was not aware Avaya was not supporting 3.1.65 anymore.

 

[mattKnight]

since SCN will not work with mixed versions and we cannot upgrade 20+ IPOs at once.

It is not an ideal situation, but you can run mixed scn's certainly for the duration of an upgrade process of 20 sites. You can work in this scenario if each system is on the top version of its family of software (thus 3.1.65). |The feature set is controlled by the lowest software version's feature. I haven't tested this, but our distributor says that it is ok...

However, isn't 20 sites too big for SCN anyway?

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[kavsagol]

Matt, like I wrote we have 2 SCNs for this client. The second we tried over 16 two IPOs rebooted like crazey, so we had to seperate. Now we have a 16 IPOs SCN and an 8 IPOs SCN.

 

[mattKnight]

like I wrote we have 2 SCNs for this client

So you did!, pity i didn't read it

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[janni78]

Then on the bright side you actually only have to upgrade 8 and then 16 IPO's at once

Only thing I can say that might help is that I've seen a 412 getting stuck in reboot loop due to a faulty VCM card.
Found that out looking at the DTE port when it rebooted. Showed one card invalid.

 

[kavsagol]

I would agree the card is faulty if the monitor would state so and if the rebooting would copntinue all the time. But this happened once (several reboots) and that's it.