IP406 reboot with TLB Error????

[kmefford]

Below is a monitor output of a unit that has been giving me grief all week. This is from when the system was running 4.0.5 but have also had the same error when running 3.2.55 on 2 different 406V2's System consists of 406 with PRI card, a 16 port DS expansion, and 8 port analog expansion module. Using 24 phones 4412's.

The system seems to run fine for several hours but will reboot 2-3 times a day with the error listed below.

Any ideas????!?!?!?!?

PRN: Begin Stack Trace
66249236mS PRN: pc=ff7bb6b4
66249236mS PRN: lr=ff91a918
66249236mS PRN: findfunc ff919918 ff7e2d2c ff7e2b04 ff91e09c ff91eff4 ff91f230 ff7d74c4 ff7d9230 ff931694 ff7d9320
66249236mS PRN: findfunc ff547ef0 ff5d119c ff54385c ff543820 00000000 00000000 00000000 00000000 00000000 00000000
66249236mS PRN: End Stack Trace
66249236mS PRN: .FATAL TLB Data address=00630237 d=5 pc=ff7bb6b4 ff919918 ff7e2d2c ff7e2b04 ff91e09c ff91eff4 IP 406 DS 4.0(5)

 

[mattKnight]

What hardware have you changed?

When you upgraded to ver 4 did you rewrite the config?

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[kmefford]

So far the only hardware to change is the 406.

The configs have been written several times from scratch using matching manager software to the IPO version.

I am going to the site today to put in a temporary magix system while I can try and figure out what the real cause of this error is.

Was just hoping someone might have seen the error before since Avaya shows it as an issue in 4.0.5 Once I get back to the office and don't have a customer breathing down my neck, I'll be calling Avaya to get to the bottom of this.

 

[tlpeter]

probably it is a corrupt config
default it and send back the config again


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[intrigrant]

It is not possible to determine what causes the reboot, for that you need to add the previous minute of the trace as well.

 

[kmefford]

The traces and config are being forwarded to Avaya. Catalyst tech support mentioned others having very similar problems with 3.2.55 and that Avaya has a private build to correct the issue with that version.... as for the same problem with 4.0.5... The guy said he hasn't heard of anything being sent to correct it yet.

The system in question is now out of service and I'm bringing it back to my office in the morning to keep testing it.

The sad solution for this customer was to replace the IPO with a Magix. Hated to do it but at least the customer is satisfied now.

 

[tlpeter]

this is what i found
maybe there is also some kind of problem with the 16 port version (too must power used)

Note: A maximum of twenty-seven 4412D telephones are supported on the DS30 (version 2) expansion module at PCS level 5. Earlier DS30 expansion modules will only support sixteen of these telephones.



______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[andreaspergantis]

When you upgraded the system, did you do it in steps. For example 2.0.99 then 3.0.99 then 4.0.5. I know that especially 406 needs to be upgraded in steps, because with each different version, there are differences in the memory allocation of the system. The intermediate versions can usually be found in separate folders inside the manager installation folder