Alarm Dumps

[rsenio]

We have been getting these alarms on a IP406 and a SOE unit for some time now. Throughout this we have been experiencing strange problems with our system as well. Any ideas as to what this alarm means? Please help!! Thank you in advance.


1mS PRN: LAW=U PRI=0, BRI=0, ALOG=0, ADSL=0 VCOMP=20, MDM=0, WAN=0, MODU=3 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=2) CALLS=1(TOT=2077)
207mS RES: Wed 31/5/2006 15:03:58 FreeMem=2695200(19) CMMsg=6 (6) Buff=100 537 500 1396 5 Links=3563 Elements=154
3001mS PRN: +++ START OF ALARM LOG DUMP +++
3002mS PRN: ALARM: 22/08/2005 11:35:54 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3002mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3003mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3003mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3004mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3004mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3005mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3005mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3006mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3006mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3006mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3007mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3007mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3008mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3008mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3009mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3010mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3010mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3011mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3018mS PRN: ALARM: 22/08/2005 11:35:-1 <corrupt IDS> <<corrupt ES>> CRIT RAISED addr=ffffffff d=-1 pc=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
3019mS PRN: +++ END OF ALARM LOG DUMP +++

 

[rsenio]

bump

 

[sizbut]

bang

 

[MrIPO]

Clear your alarm log via Sys-Monitor and then see if they have been removed never to come back !

If this trace was taken recently I looks like the Alarm log has not been cleared since an event on the date 22/08/2005
Looking at the TOT being (TOT=2077) I am guessing this is the case and the switch has not been rebooted for a while too.

Clear the Log and reboot the IPO !

http://www.iporesource.com

"Launching late 2006