Help with Monitor Logs

[eltorodeoro]

We have a 412 3.1(48) that has been rebooting once a day for the past few days. It seems to be vaguley associated with problems on the PRI. We saw some logs from the telephone company, and they are seeing errors come from us. But only once a day, isolated to one hour a day. All the rest of the hours, everything is clean. Is there a way in the Monitor logs to search for errored seconds?

does anybody think I'm barking up the wrong tree?

 

[big70]

If you start the monitor it will say how long its running.

********** contact made with 192.168.1.12 at 20:07:17 20/4/2006 **********

********** System (192.168.1.12) has been up and running for 14days, 14hrs, 26mins and 1sec(1261561969mS) **********



Also it will give you the alarms like.

1mS PRN: LAW=A PRI=0, BRI=4, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=2 LANM=0 CkSRC=3 VMAIL=1(VER=0 TYP=3) CALLS=1(TOT=742)
434mS RES: Thu 27/10/2005 09:09:23 FreeMem=48756976(19) CMMsg=10 (10) Buff=100 603 498 568 5 Links=8740 Elements=0
3001mS PRN: +++ START OF ALARM LOG DUMP +++
3001mS PRN: ALARM: 21/10/2005 09:48:01 IP 406 DS 3.0(59) <TLB Data Error> CRIT RAISED addr=0000000c d=1 pc=ff4f6824 ff857eac 00000000 00000000 00000000 00000000
3002mS PRN: ALARM: 24/10/2005 12:23:16 IP 406 DS 3.0(59) <TLB Instruction Error> CRIT RAISED addr=ff5caf22 d=2 pc=00000000 ff535cc4 00000000 00000000 00000000 00000000
3002mS PRN: ALARM: 25/10/2005 10:34:26 IP 406 DS 3.0(59) <TLB Data Error> CRIT RAISED addr=0000000c d=1 pc=ff4f6824 fee87d7c 00000000 00000000 00000000 00000000
3002mS PRN: +++ END OF ALARM LOG DUMP +++


If you have some like these than you have to reprogram your ip-office.


Greets Peter

 

[Spanning]

you need to upgrade it to 3.1.56