Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

System re-booting every couple of mins

Status
Not open for further replies.

davea2

Technical User
Mar 14, 2005
742
GB
Hi,

have a system that constantly re-boots.
This may last for a few hours and then stop for a few days, and the it off again

Get this in Monitor just before it goes down:
56929mS PRN: .FATAL TLB Data Error address=01010018 d=5 pc=ff5d92f8 ff5d92c4 ff5c7150 ff5c6d9c ff5c6ea4 ff5c43bc

Can anyone shed any light on this for me?

Thx

UK Based IP Office Discussion
 
I have had this happen to me in the past... In one case a VCM module went bad and in the other a T1 modula went bad. Both causing a reboot to system... I ended up removing all daughter boards and making sure the unit stayed up. then I added one board back at a time till I found the one that caised reboot.
You can also use the DTE port to check the boards. If the system sees them on the reboot you should see the information about them.
 
davea2

In sys monitor do you have any alarms? If so you may have to go in and default the unit thru the DTE port. If it's not hardware as already mentioned you could have a dirty config.

Miles
 
I had experienced this problem with a 412 with a VCM30 and 50 4620SWs. Something in the software was causing the VCMs to hang after the last user in a group ring hunt group handled 2 calls and the second was picked up first. Worked with AVAYA for several weeks while having to reboot the switch every 5 days to make sure enough VCMs were available for day-to-day opps. They came up with an upgrade .bin file that fixed it. All is well now. The IPO has been known to reboot if VCM channels are all being utilized and multiple simultaneous attempts are made to access the resources, also heard of it with an ip phone page attempt in previous releases.

 
I have got this problem now with a customer running 2.1(27) on a 403DS + POTS16. They have no VCM cards, only 2 BRI cards, locks up once every 7 to 8 days requiring hard reset. Stinks of a memmory leak in the programing, are AVAYA doing their garbage collection properly in the programing?
You know, that fact that other people "milestoned" for example, are stating dirty configs is pretty scarry! Can avaya not see that their customer base does NOT trust their systems, there should be no DIRTY configs, when a system is properly programmed there should be no reason for the underlying database to get all screwy and cause the issues we see on an almost daily basis, and that says nothing about how many new unqalified features (bugs) arrive with every new release of firmware
 
thes sorts of problems can also be caused by rouge network activity (virus attack).
if a hardware swap does not cure the problem then I would do a thorough Virus sweep on the customers network.
 
I think maybe network activity is a suspect.
The FDs PC was logged on to the network at the time.
We he disconnected, problem stopped for a few days.
He is on today, with no probs.
Upgraded to 2.1(27) to see if that helps.
cant do 3.0 as the have DT's!

56929mS PRN: .FATAL TLB Data Error address=

Whats the above mean?

UK Based IP Office Discussion
 
Your unlikely to ever get an exact answer for what "56929mS PRN: .FATAL TLB Data Error address=" means.

Something (currently unknown) upset the IP Office sufficiently that it stopped working and reset (which you have seen). The data after the "Error address=" part can be used by Avaya to locate exactly where in the code the IP Office was when this occured but to do that the issue has to be escalated all the way up to Tier 4.
 
Not that we have any info of how to read Monitor, Iv found that by going to Trace options / System Tab, tick development traceing. Say ok. Then in the upper tool bar
"Status is now avaliable, this will tell how many vcms are in use, how much mem is avaliable and some other things avaya like to keep a secret.

If anyone has a Magic decoder ring for Monitor that would be way cool info
 
I would definetly perform a virus scan of the FD's PC
Rouge network activity is a known cause of IPO reboots

I would also aggree with your decision to go with V2.1(27) or V2.1(31), Investigations on my home system suggest that V3.0(DT) is virtualy a rebadged V2.1(31), V2.1(31) Bugs are still present & some ectras that were added to V2.1 too late to make the V3.0 release are still present

 
I would remove patch cords from the ports. Both LAN and DT and see if it stops rebooting.

I have seen all of the LAN ports die and the symptom is rebooting. In this case, rebooting stops when no LAN ports are patched.

I have seen a MLX phone take down a module when plugged into a DS port.

I have seen bad cabling take down a DS module.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top