Switch Rebooting FATAL TLB Data Error 1

[MrIPO]

Does anybody know what the following error means just before a switch running 2.0(1602)reboots

66988mS PRN: .FATAL TLB Data Error address=aa55aa55 d=5 pc=0152115c 0a20e064 015d1e18 015d2200 015d99b8 015d6fe0 IP 406 2.0(1602)

I seems to be seeing this error at a lot of sites running V2 but nobody even AVAYA can explan what it exactly means.

See below extract from tracing covering the reboot.

Thanks for your help
-----------

66979mS ISDNL3Evt: v=5 stacknum=5 State, new=Present, old=NullState id=1
66980mS PRN: National Number in prefix 0
66980mS CMLineRx: v=5
CMSetup
Line: type=Q931Line 5 Call: lid=5 id=1 in=1
Called[42273955] Type=SubscriberNumber (4) SndComp Calling[0242286020] Type=National (2) Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=1
66981mS CD: CALL: 5.1.1 State=0 Cut=1 Music=0.0 Aend="Line 5" (0.1) Bend="" [] (0.0) CalledNum=42273955 () CallingNum=0242286020 () Internal=0 Time=1 AState=0
66982mS CMTARGET: LOOKUP CALL ROUTE:8 type=4 called_party=42273955 sub= calling=0242286020 in=1 complete=1
66988mS PRN: .FATAL TLB Data Error address=aa55aa55 d=5 pc=0152115c 0a20e064 015d1e18 015d2200 015d99b8 015d6fe0 IP 406 2.0(1602)

********** contact lost with 10.32.224.100 at 11:05 13/3/2004 - reselect = 89 **********
******************************************************************


********** SysMonitor [Version 4.0 (11)] **********

********** contact made with 10.32.224.100 at 11:11 13/3/2004 **********

********** System (10.32.224.100) has been up and running for 15secs(15583mS) **********

1mS PRN: Monitor Started IP=10.32.224.101 IP 406 2.0(1602) St Mary
3mS PRN: LAW=A PRI=0, BRI=4, ALOG=0, ADSL=0 VCOMP=5, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=0)
244mS RES: Sat 13/3/2004 11:11:36 FreeMem=7513288(1) CMMsg=2 (2) Buff=100 632 496 1369 Links=9819
732mS PRN: Token::Token() -1: token added:
733mS PRN: 00:e0:07:00:5e:f0
750mS RES: Sat 13/3/2004 11:11:37 FreeMem=7514944(2) CMMsg=2 (2) Buff=100 632 496 1369 Links=9818
1832mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=4,p4=127,s1=
1834mS PRN: LINE 1 IS DOWN
1834mS ISDNL3Evt: v=2 p1=2,p2=1001,p3=4,p4=127,s1=
1836mS PRN: LINE 2 IS DOWN
1837mS ISDNL3Evt: v=3 p1=3,p2=1001,p3=4,p4=127,s1=
1838mS PRN: LINE 3 IS DOWN
1842mS CMLineRx: v=1
CMLineDown
Line: type=Q931Line 1 Call: lid=0 id=-1 in=0
1843mS CMLineTx: v=1
CMRestart
Line: type=Q931Line 1 Call: lid=0 id=-1 in=0

 

[IPGuru]

Last time I saw tlb errors it was caused by a virus on the cutomers network.

It may also be worth checking Tech Bulletin 22, it seems that a number of things could cause a reboot on 2.0(16)
2.0(18) may resolve this problem

 

[SPIPOffice]

I did have a similer problem(s)
1 - On one site, I have to re-write the config, NOT using the wizard.

2 - High network traffic.

3 - Virus on the network - althought the monitor would of pick this up.

4 - Maybe a faulty compression card.

Depending on how often this is happening, I would take out the VCM card.

 

[telepaul]

This is a known problem in 2.0(1602) and solved in 2.0(18)
Only on IPO406 2.0(1602) has to do with RAS settings.
It is not a problem on 2.0(16)

 

[SPIPOffice]

where can I get 2.0(18) from? I cannot see it on the support.avaya.com web site anywhere, can someone point me to where it is?

 

[GrandmasterOPI]

Have also seen on SO 2.0.16 as follows


********** Logging to File Stopped on 22/3/2004 09:49 **********

********** SysMonitor [Version 4.0 (11)] **********

********** contact made with 10.15.56.40 at 09:49 22/3/2004 **********

********** System (10.15.56.40) has been up and running for 4days, 16hrs, 28mins and 55secs(404935871mS) **********



********** Warning: LOGGING TO FILE DISABLED **********

0mS PRN: Monitor Started IP=10.15.56.99 IP 401 NG DS 2.0(16) Drager
0mS PRN: LAW=A PRI=0, BRI=0, ALOG=4, ADSL=0 VCOMP=3, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=0 TYP=3) CALLS=1(TOT=517)
80mS RES: Mon 22/3/2004 10:49:30 FreeMem=5678308(45) CMMsg=6 (7) Buff=100 646 485 1465
81mS IP Routing Table - section 1
Destination Netmask Gateway Interface Metric Type
255.255.255.255 255.255.255.255 0.0.0.0 LAN1 0 I
224.0.0.0 240.0.0.0 0.0.0.0 LAN1 0 I
255.255.255.255 255.255.255.255 0.0.0.0 LAN2 0 I
224.0.0.0 240.0.0.0 0.0.0.0 LAN2 0 I
10.15.56.0 255.255.255.0 0.0.0.0 LAN1 0 I
192.168.43.0 255.255.255.0 0.0.0.0 LAN2 0 I
192.168.99.0 255.255.255.0 0.0.0.0 RemoteManager 0 S
3032mS PRN: +++ START OF ALARM LOG DUMP +++
3032mS PRN: ALARM: 26/02/2004 15:15:32 IP 401 NG DS 2.0(16) <TLB Data Error> CRIT RAISED addr=00000000 d=5 pc=ff61d488 ff5c0880 ff5c0704 ff5aaab0 ff6a4f90 ff69f158
3033mS PRN: ALARM: 05/03/2004 16:09:24 IP 401 NG DS 2.0(16) <TLB Data Error> CRIT RAISED addr=000000c0 d=5 pc=ff5c4210 ff5c41e8 ff5aff7c ff5b02a0 ff5b04d8 ff5c409c
3033mS PRN: ALARM: 11/03/2004 11:29:21 IP 401 NG DS 2.0(16) <TLB Data Error> CRIT RAISED addr=000000c0 d=5 pc=ff5c4210 ff5c41e8 ff5aff7c ff5b02a0 ff5b04d8 ff5c409c
3033mS PRN: ALARM: 17/03/2004 09:22:28 IP 401 NG DS 2.0(16) <TLB Data Error> CRIT RAISED addr=b0830008 d=5 pc=ff61d8d4 ff5afd8c ff5b3460 ff5b307c ff5c4248 ff5aff7c
3033mS PRN: +++ END OF ALARM LOG DUMP +++
15070mS RES: Mon 22/3/2004 10:49:46 FreeMem=5683796(45) CMMsg=6 (7) Buff=100 646 485 1465
15767mS CMExtnRxP: v=7
CMShortCode
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
ShortCode GetSystemInfo (99) = []
BC: CMTC=Speech