Definity si Duplicated SW-CTL alarms and clock errors

[Nick44]

Hi All,
This has expanded my bald patch. System is a very late (04 build) si duplicated SPE running release 12 with no patches. The SPE interchange had been locked out so that SPE B was doing all the work. An odd intermittent alarm believed to be on the TN2401 on SPE A caused me to change this out, at the same time I noticed the SPE lock (on the interchange hard switches as well as sys maint)so having (allegedly) fixed the alarm I put the SPE interchange back to normal. Now an odd thing happens. At maintenance time 01:00 a SW-CTL alarm [error type 513] and STBY-SPE alarm [error type 1] appears. This clears itself at 08:00. As well as this the system time winds itself forward either 4 or 8 hours. I can't find a PCN or a QPPCN relating to this.
I suspect the processor card in SPE A may have a headache, do you lot have any other thoughts?
Thanks, Nick.

Speak softly and carry a big switch

 

[mikeydidit]

I think you are in the right direction Nick. The errors are coming back in during the nightly maintenance routine. You can go into "disp sys main" and it should show that as the times it is scheduled to run.

I would also look in this doc and run the error and alarm codes against the SW-CTL to see what it come up with.

http://support.avaya.com/edoc/docs/defg1/g1maint8.pdf\

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read thread690-1323977

 

[Nick44]

Maintenance window is 01:00 to 04:00, so this explains the start time of the alarm, the clear time is 4 hours later. Hmmmm. 4 Hours, clock moving in 4 hour chunks too.........
The only thing we know that happens at 08:00 is the PC WOC gets turned on, but I think this is a red herring. I had alreay consulted the big book, for the error codes. several possibilities but all look destructive tests, last resort on 24/7 switch.

Speak softly and carry a big switch

 

[mikeydidit]

On the above Avaya G3I link, On page 2636 section C gives you a test to run on the Netcon circuit pack. It, to me, looks like it could be your source of greif. I would run this test first and see if the aux data looks like it should. The maximum times to run this test is 3 times. If this is indeed your trouble this can be replaced without any down time in a duplicated system.

It does say something about this also having the " Time of day Clock", (The begining of the section) which again leads me to beleive this would be the problem.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read thread690-1323977