crookie

Can anyone help?
I am having a problem with a 406 resetting intermittently.
The error I get is :
22873466mS PRN: .FATAL TLB Data Error address=aaaaaaaa d=5 pc=015a8204 00000000 015a82c8 015b02a8 017ebeb4 017ea9f4 IP 406 2.1(15)

The cpu has been changed along with the PRI.There has been a manual retype.
The system has been disconnected from the network. BT Have checked the lines. System been upgraded to 2.1.

Any help would be welcome.

koelemon

It could be a number of things, run your config through the wizard to check for errors that might lead to corruption, also, what other daughter cards do you have?

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

DaveA

Have you got any machines on the LAN that have any malware installed that could be hitting the IPO with a flood of packets? This may well cause problems, possibly also a device repeatedly broadcasting?
You could check the IPOs routing table via the Monitor app to see if you have anything on the network like NetSky trying a DoS attack.

__________________
------------------------------------------------------------------------------------
Click -->UK IP Office Forum. A new UK based IP Office User Group.

Cephas

If it's still resetting after being disconnected from the network, it's not malware doing a DoS attack. You've changed the CPU and reprogrammed the config from scratch? I would copy and paste that error into an email and send it to your distributor (or whoever your official avaya tech support is) and have them escalate it up the chain until someone can say exactly what that error means. Even if it has to go WAYYY over the cold deep waters until it comes to a drearly little island off the coast of europe where various IP gurus and their faithful adherrents are reputed to live.... :D

Peter

koelemon

as lame as it sounds, also make sure nothing (router, etc) on the network is trying to use the same IP addy as your 406, I have done that once and won't ever live it down :)

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

crookie

The system has now been taken completely off the network, so the only interface to the ip office is via BT isdn, which has been checked as per Avayas recommendation.
The entire system is due to be changed out shortly, so if that doesn't cure the prob I will need a bigger hammer.

PBXtech.info

 

Cephas

Darn, IPGuru didn't take the bait.... how VERY dissapointing! :)

IPGuru

Sorry peter I didnt connecte "Dreary Little Island" with this glorious sunny centre of a (once) Great Empire. :))

__________________
Universal Plan B: - When all else fails CHEAT!

Fozzie

HAve you resolved this issue, we have seen the same problem since Monday on our Avaya switch

Cephas

fozzie are you also on a 406 w/ R2.1? And are you seeing the same error in monitor?

Peter Sherwood

MickM

I have had this on a few sites and it can be resolved by changing hardware but I am sure that it is database related.

The error means the system crashed.

I would check the system config and make sure that;
1) The directory has no more than 1000 entries. I had one site where adding more than this caused reboots.
2) Check the users, groups and directory names and make sure that you have only letters and numbers in the names. I had a site where removing hyphens and underscores from directory names stopped the reboots immediately.

If all this fails you could try exporting the database to notepad as a csv and then re-importing it.
This is supposed to clean the DB up.