Monitor log and monitor messages

[slovic]

Hi there,


I've got IPO 403 w/two IP 400 DS (16 and 30 ports) and ISDN PRI + VoIP link toward Definity system. Does anyone know how to interpret following messages from System Monitor (what do they mean):


3013mS PRN: +++ START OF ALARM LOG DUMP +++
3013mS PRN: ALARM: 30/04/2004 15:50:13 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=09ebdd80 d=5 pc=ff5ca0dc ffe98298 ff6a9a08 ff5e27c8 ff5e27e8 ff5e2cc8
3013mS PRN: ALARM: 10/05/2004 11:39:27 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000000 d=5 pc=ff6ab308 ff6ab29c ff6aa9a4 ff504b30 ff5c3ac8 ff5c3aa4
3014mS PRN: ALARM: 03/06/2004 14:58:02 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000048 d=5 pc=ff5c6324 ff02ffd8 ff5c62f0 ff5ccbe0 ff7ade44 ff609ee4
3014mS PRN: ALARM: 22/10/2004 13:08:27 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000000 d=5 pc=ff5c9384 00000000 ff5c9404 ff61b80c ff6a3bc8 ff6a1994
3014mS PRN: ALARM: 27/10/2004 14:54:26 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=0060a18c d=5 pc=ff5c972c 00000000 ff607544 ff70aaf8 ff70995c ff604ba8
3015mS PRN: ALARM: 10/11/2004 18:43:39 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000000 d=5 pc=ff5c9384 00000000 ff5c9404 ff61c114 ff61bc50 ff6a3bc8
3015mS PRN: ALARM: 16/11/2004 18:06:43 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=000000a0 d=5 pc=ff6059e0 ff650fac ff70a7c4 ff70aaf0 ff70995c ff604ba8
3016mS PRN: ALARM: 27/11/2004 15:46:44 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=3b830000 d=5 pc=ff5c6324 ffe8ec54 ff5c62f0 ff5ccbe0 ff7ade44 ff70ea40
3016mS PRN: ALARM: 20/12/2004 14:39:48 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000003 d=5 pc=ff6059e0 ff650fac ff70a7c4 ff70aaf0 ff70995c ff604ba8
3016mS PRN: ALARM: 25/01/2005 09:37:30 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000004 d=5 pc=ff6059e0 ff650fac ff70a7c4 ff70aaf0 ff70995c ff604ba8
3017mS PRN: ALARM: 31/01/2005 14:21:35 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=389f0008 d=5 pc=ff5c5de0 ffddf4d8 ff500f10 ff500cbc ff5c69d4 ff5c6620
3017mS PRN: ALARM: 05/02/2005 16:43:08 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00000003 d=5 pc=ff6249a0 ff679284 ff74f8bc ff74fc34 ff751eb0 ff625520
3017mS PRN: ALARM: 07/02/2005 08:12:47 IP 403 2.1(24) <Machine Check Exception> CRIT RAISED addr=083fc767 d=5 pc=ff7f4994 ff7f4628 ff7f4874 ff7f4968 ff74f6e4 ff74fc34
3018mS PRN: ALARM: 07/02/2005 11:16:02 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00a2fb4b d=5 pc=ff7f4994 ff7f4628 ff7f4874 ff7f4968 ff74f6e4 ff74fc34
3018mS PRN: ALARM: 07/02/2005 17:05:50 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00de5e64 d=5 pc=ff5dd7b4 ff5e4d7c ff5dd800 ff5e4cbc ff7f4a88 ff7f35c8
3019mS PRN: ALARM: 09/02/2005 12:07:42 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00000018 d=5 pc=ff5dd624 ff628994 ff5dd6fc ff5e4d7c ff7f4af0 ff7f3068
3019mS PRN: ALARM: 12/02/2005 16:11:37 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00000018 d=5 pc=ff5dd624 ff628994 ff5dd6fc ff5e4d7c ff7f4af0 ff7f3068
3019mS PRN: ALARM: 14/02/2005 17:00:23 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=0986b0a4 d=5 pc=ff7f4994 ff7f4628 ff7f4874 ff7f4968 ff74f6e4 ff74fc34
3020mS PRN: ALARM: 21/02/2005 16:51:57 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=00871918 d=5 pc=ff5dd624 ff628994 ff5dd6fc ff5e4d7c ff7f4af0 ff7f3068
3020mS PRN: ALARM: 21/02/2005 17:08:18 IP 403 2.1(24) <TLB Data Error> CRIT RAISED addr=000e6d4a d=5 pc=ff7f4994 ff7f4628 ff7f4874 ff7f4968 ff74f6e4 ff74fc34
3020mS PRN: +++ END OF ALARM LOG DUMP +++


Furthermore, could anyone advise me where I can get some additional documents with explanations of System Monitor messages.


Thanks,

 

[IPGuru]

You will get no documents regarding monitor.
Officialy it is only to be used under instruction from Avaya tech support.

Unofficialy it is one of the best tools available to the IPO engineer, but only experience & pot luck help with the trasnlation.
some sections (ISDN, PPP, Call etc.) can give reasonably human readable results.

your trace indicates that the IPO is unhappy about something but I could not say what.

 

[sizbut]

Even with Monitor documentation all it would tell you about the Alarm Log entires it that they can't be interpreted in the field.

They usually relate to some error causing the IP Office software to freeze and then be restarted by a watchdog timer. The alarm itself is just a marker to whichever piece of core code the system was last executing, but it means nothing without access to the source code.

The system stores the last twenty alarms and shows them in Monitor. You can clear them through Monitor also. Select Status and then Alarms. This will display the alarms and allows you to clear them by clicking Clear Alarms. Might be worthwhile doing as your 16 alarms go back almost a year now.

I would be worried by the frequency of the alarm dates since you've gone to 2.1(24), your system is resetting every few days. You might want to consider 2.1(27).

 

[intrigrant]

I assume you upgraded the system from 2.0.16 to 2.1.24 and then to 2.1.27.
These alarm messages are old and meaningless and can be deleted.
Open SysMon and select Status -> Alarms, a new window will open and select "Clear Alarm log".
Then the alarm messages will be deleted.
If you check later and see any alarm message you should contact Avaya for a explanation.

 

[IPGuru]

Didnt spot the V2.1(24) reference.

This Version has more Bugs than the entymology house at london zoo. Upgrade to V2.1(27), this may cause problems with call listen but it is generaly stable.
a final maintanence release should be available soon & that will hopefully resolve the last remaning niggles with this version.

 

[slovic]

Thanks,

I will try with upgrade...