MisterLister
Technical User
i have an ipo403 on 2.1.15, and has been that way for over a year without any problems until now.
the avaya box reboots at different times of the day, and i have run out of possible tests to do.
i have
check with bt that the pri line is ok
check the cable between the ipo403 and the nte
replaced the ipo403 with a new 403
replaced the pri card with a card
confirmed there is no corruption within the config using the wizrd.
erased the config and reloaded it.
check all the phone connections
check all the ethernet connections
check all the pcs connected to the network for a virus
check the hub/switches links to each other
check for new equipment on the lan and ruled it out as it is on the other side of a router.
while testing i used monitor and ping command to the ipo403, this kept the ipo403 from rebooting as often. monitor only shows a .FATAL message just before the reboot (alarm dump at end)
moved the voicemail server ethernet connection from one of the external switches to the intergrated switch on the ipo403, this only increased the frequency of reboots.
replaced the network card and drivers in voicemail server. the ipo403 still rebooting. replaced the ethernet cable with a known good one. still rebooting.
moved the ipo403 ethernet connection from one hub/swicth to another until the ipo403 has been on all of them, still the pig403 reboots.
help is there anything else i can try? apart from upgrading the firmware as the inhouse software was developed around this version (2.1.15). updates to later version 2.1.27 just killed the inhouse software.
Alarm Dump:
3016mS PRN: ALARM: 02/10/2006 09:10:27 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5e00b8 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3016mS PRN: ALARM: 03/10/2006 16:23:57 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff64baa0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3017mS PRN: ALARM: 04/10/2006 09:14:25 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5db3e0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3017mS PRN: ALARM: 04/10/2006 09:19:58 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 00000000 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3018mS PRN: ALARM: 06/10/2006 17:34:04 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff64baa0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3018mS PRN: ALARM: 10/10/2006 17:29:07 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5e00b8 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
the avaya box reboots at different times of the day, and i have run out of possible tests to do.
i have
check with bt that the pri line is ok
check the cable between the ipo403 and the nte
replaced the ipo403 with a new 403
replaced the pri card with a card
confirmed there is no corruption within the config using the wizrd.
erased the config and reloaded it.
check all the phone connections
check all the ethernet connections
check all the pcs connected to the network for a virus
check the hub/switches links to each other
check for new equipment on the lan and ruled it out as it is on the other side of a router.
while testing i used monitor and ping command to the ipo403, this kept the ipo403 from rebooting as often. monitor only shows a .FATAL message just before the reboot (alarm dump at end)
moved the voicemail server ethernet connection from one of the external switches to the intergrated switch on the ipo403, this only increased the frequency of reboots.
replaced the network card and drivers in voicemail server. the ipo403 still rebooting. replaced the ethernet cable with a known good one. still rebooting.
moved the ipo403 ethernet connection from one hub/swicth to another until the ipo403 has been on all of them, still the pig403 reboots.
help is there anything else i can try? apart from upgrading the firmware as the inhouse software was developed around this version (2.1.15). updates to later version 2.1.27 just killed the inhouse software.
Alarm Dump:
3016mS PRN: ALARM: 02/10/2006 09:10:27 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5e00b8 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3016mS PRN: ALARM: 03/10/2006 16:23:57 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff64baa0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3017mS PRN: ALARM: 04/10/2006 09:14:25 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5db3e0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3017mS PRN: ALARM: 04/10/2006 09:19:58 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 00000000 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3018mS PRN: ALARM: 06/10/2006 17:34:04 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff64baa0 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24
3018mS PRN: ALARM: 10/10/2006 17:29:07 IP 403 2.1(15) <TLB Data Error> CRIT RAISED addr=0086ca04 d=5 pc=ff5dbe60 ff5e00b8 ff5dbfc8 ff5e3460 ff7f06ac ff7eec24