Mitel mx main analog board

[glennmitel]

i have got a problem with a embedded analog on a mx every month both of the ons ports become very noisy and you are unable to break dial tone, the only way to get them back up is to reboot the mitel.

any ideas

thanks Glenn

 

[paterson]

Have you programmed the controller to do a scheduled re-boot? You can program it for daily, weekly, etc. Mitel has recommended it (see article #04-1000-00016 on Mitel On Line). I program weekly re-boots on my systems and it seems to clear minor stuff like this.

Go to the Maintenance command line:

PROGRAMMED REBOOT DISPLAY - will display what is currently programmed. The default may just need to be activated.

PROGRAMMED REBOOT SCHEDULE <day of week ie SUN> <hh:mm:ss> - this is to set the schedule for weekly reboot.

PROGRAMMED REBOOT SCHEDULE ON - this will activate the scheduled reboot.

other commands to consider:

PROGRAMMED REBOOT COURTESY ON/OFF - will wait for existing calls to disconnect before reboot.

PROGRAMMED REBOOT RESOURCE RECOVERY ON/OFF - Resource Recovery is a feature introduced with Release 4.1 that monitors critical system resources to determine if reboots are necessary for stable system operation. In the unlikely event a resource threshold is exceeded, the system can be automatically rebooted based on a programmed time of day parameter Mitel recommends the default setting of Resource Recovery “on” in software release 4.1.9.4 or greater.

PROGRAMMED REBOOT RECOVERY <hh:mm:ss> for the above command.

 

[glennmitel]

yes the prog re sche is set and is active.

the last thing that i am gonna try is to change the main analog board on the mitel.

would it be worth upgrading to 5.2.6.8 or even 6.0.5.7

thanks

 

[paterson]

I don't know if upgrading will specifically fix your trouble, but there is a similar trouble with the ASUs that has been fixed with Rel 6.

It's funny that when the trouble occurs, the reboot you do then fixes the trouble, but the programmed reboot doesn't. I would try changing the reboot to DAILY (unless it is a 24 hour operation) and see if that helps.

Changing the AOB would be my choice too if the daily reboots don't help.

 

[ianuk1974]

I had this problem earlier in the year. Because of other various issues with site i swapped the whole 3300 Controller but also upgraded to version 5.2.5.4 also reboot the system once a week

and we have had no further problems.

ian

 

[MitelInMyBlood]

We had a similar problem with the Analog board in a 200_ICP. When we finally swapped it out you could see a burn mark on the chassis. Apparently we got a shot of lightning on one of the LS trunk ports and it did some damage to the board. Lesson learned, gas discharge protectors added. Alternatively, if you happen to have a peripheral can (bay/node/whatever you want to call it) you might want to put those on an OPS line card, which has some protection built in.

 

[AlfredSpecial]

You dont need a programmed reboot with software levels 5.2 and above.

So mitel tech say!

 

[glennmitel]

i would not risk not doing a reboot on any 3300
and when do we ever listern to mitel TAC

 

[paterson]

My experience shows it still helps keep the minor trouble numbers down. You may not HAVE TO, but....... Lets face it, these things are computers and what computer doesn't like to have it's RAM and OS refreshed once in a while!

 

[TheMitelGuy]

What happens to your NSUs, do they not reboot as well, when your system reboots?

 

[glennmitel]

i am using a dual framer with e1

i have now had to set the prog re for daily due to this problem the analog main board locking up

and mitel wanna charge £1000 for a new one

 

[paterson]

Fairly confident that the NSUs will do soft resets when it senses that the FIM signal is down.