3300 MXe II MIPS (L2 Switch Manager) not up

[jaevans77]

Not sure if this is the bad L2 Switch problem or not...

System boots up, phones connect and 2 mins later I get this error in the logs and the phones will no longer connect. Also nothing appears in the logs after that for 8 hours until I telnet to the VXWorks. Logging in to the webpage doesn't appear in logs.

MIPS (L2 Switch Manager) not up, resetting MIPS processor..

You can still ping the system, access the webpage and Telnet to VXWorks. Seems like the other posts said all that was inaccessible.

Everything was fine until a power outage, hoping it's a corrupt drive and not the L2 Switch.

I'm attaching some logs as there are some other strange things in it.

I did apply the "period 900,mips_reset" this morning and phones did register not sure if working as I am not on site.

Thanks for any help with this.

 

[AH64Armament]

Unfortunately, the controller's motherboard Ethernet (MIPS) is no longer responding. That command does not survive a reboot.

There's 2 ways to resolve this issue permanently -
1st - replace the controller
2nd - if you're not using VLAN's directly on the the system L2 or the WAN port, then you can remove the L2 IP address, reboot the controller and it MAY work. My recommendation though is to replace the controller.

If you need a replacement controller, please message me as I have several (used) that we can sell on the cheap.

 

[TheMitelGuy]

Question - when was the last time the MXe II was upgraded? Our company found an issue where you upgrade the system (specifically on MXe IIs only) and the phone system will reboot and come right into service. The phone system will work for months (perhaps over a year), but then at some wild point in time, the controller is rebooted and you get MIPS issues. Once that happens the only thing you can do is buy a new ICP (if you can get one at all). I would not recommend MXe IIs at all. Our company actually stopped servicing MXe II specifically and would not support them under maintenance, customers had to upgrade to a MXe III or IIIL. We didn't like forcing customer to do this, however we could not guarantee how long the ICP would last after the upgrade. What's the weirdest thing about it was, after the install/upgrade of the software, the controller does reboot and come right up into service (no issues). However if it's rebooted at again - it becomes an expensive boat anchor. We had many techs suck on sites trying for hours (in one case - the very first case - almost a day). It's a "known issue" to our company, but I don't think it was ever fixed/corrected. It only affected MXe IIs.