AVAYA IP OFFICE REBOOTING (COLD START)

[SN 5060]

AVAYA IP OFFICE V2 RUNNING IN 8.1 (85) CONSTANTLY REBOOTING AND IT IS GETTING An ERROR OF ABNORMAL TERMINATION, WE WERE GETTING THIS ISSUE AFTER CONFIGURING SCN IN 3 SITES BUT WE ARE NOT SURE IF THAT WAS THE PROBLEM.
WE TRY SOME ISOLATION LIKE UPGRADING AND DOWNGRADING THE SYSTEM BUILD NUMBER STILL NO LUCK.

 

[derfloh]

Your CapsLock button is damaged...

If you think it is the SCN start to remove those lines and see what happens.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[SN 5060]

We already removed the scn connection, yet the problem still occurs.
and we have already changed the vcm 64 v2 and the issue still exists.

 

[Nortel4Ever]

8.1 is quite old, have you considered the possibility of bad hardware, a failing power supply or a bad cabinet?. Doing a cabinet swap at 8.1 if you have a brand new 500V2 (not V2A) is easy.

 

[sizbut]

8.1(85) wasn't the last 8.1 service pack.

Stuck in a never ending cycle of file copying.

 

[SN 5060]

i already upgrade it at 8.1(95) and issue still occurs

 

[IPGuru]

try a default config
if the fault persists then as previously suggested replace the IP500V2
i have seen this once many years ago & we never did find the actual cause.


Do things on the cheap & it will cost you dear

ACSS

 

[Westi]

There are many issues that can cause reboots and finding them is sometimes just luck but have you tried running Monitor to see what happens just before the reboots?

Maybe there is the same action happening every time and that causes it. Maybe a user tries to get messages or dials a certain extension ... many options and Monitor could really help.

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[SN 5060]

We already replaced the control unit only and the issue still occur

this was our trace when it is being reboot
09:57:02 54149727mS PRN: Begin Stack Trace
09:57:02 54149727mS PRN: pc=f1405740
09:57:02 54149727mS PRN: lr=f140599c
09:57:02 54149727mS PRN: findfunc f1405994 f1405a5c f1404030 f14017c8 f1402cc8 f1402b84 f1402c7c f133c108 f13508c0 f133db5c
09:57:02 54149727mS PRN: findfunc f1350b98 f139a894 f13581d4 f04c037c f0406a44 f0405894 f0452478 f0452a18 f09ff6f4 f09b988c
09:57:02 54149727mS PRN: findfunc f09bb4f4 f09bbb9c f07332d4 f0736e3c f0fdb66c f0736f2c f03120f4 f03a4150 f030b200 f030b1ac
09:57:02 54149727mS PRN: End Stack Trace
09:57:02 54149727mS PRN: ScheduleHistory NOT enabled: Task = CM File = ../platform/platform.cpp Line = 1186
09:57:02 54149727mS PRN: .FATAL Program Exception address=00000000 d=5 pc=f1405740 f1405994 f1405a5c f1404030 f14017c8 f1402cc8 IP 500 V2 8.1(95)

********** SysMonitor v11.0.4.7.0 build 6 [connected to 172.19.21.7 (TRICOM PHILS)] **********

********** contact lost with 172.19.21.7 at 09:56:13 24/5/2024 - reselect = 5 **********
******************************************************************

********** SysMonitor v11.0.4.7.0 build 6 **********

********** contact made with 172.19.21.7 at 09:57:44 24/5/2024 **********

********** System (172.19.21.7) has been up and running for 53secs(53928mS) **********

********** Warning: BINARY File Logging selected **********

 

[IPGuru]

Do you get this behaviour with a default config?
if not then it is a programming error somewhere

one cause I saw some time ago (not sure what release was when reception diverted hunt group calls back to the reception group.
when a call came in round & round it went until it caused a stack overflow & a reboot.

Do things on the cheap & it will cost you dear

ACSS