MXE - Can't ping, no GUI access 15 mins after reboot

[MitelInMyBlood]

One of my older 3300 MXe's lost the hard drive (single drive system). I was able to replace the drive & get the licenses back on it, but cannot restore the DB as it keeps losing network connectivity. About 15 minutes or so after a reboot you can no longer ping it nor access the GUI, so I can't see what the alarms are.

S/W load on it is 8.0.11.7

Thoughts?



Original MUG/NAMU Charter Member

 

[kwbMitel]

Ip conflict?
Vlan set on lan port?


**********************************************
What's most important is that you realise ... There is no spoon.

 

[danramirez]

we had a similar situation in the past. We replaced hard drive, formatted, load software and licenses and after some minutes we lost conectivity to controller. Rebooted several times with no luck.

We opened a ticket with support with no chance to provide much info as no access to logs... at the end we replaced controller. We never bother to repair it... It was cheaper and easier to get a brand new one.

As Kwb suggests, look for IP conflict and vlan_off

What I would do is to disconnect that from the network and see if you can make it to work.

Regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[LoopyLou]

Agree with danramirez and kwb pull it from the network. When you installed the new hard drive how did you install the software? did you use Fixpartion?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[bribob]

What kind of drive did you swap in? What happens when you check the status of the web service via the maintenance port?

i WebServer - Checks the web server status

ifShow - Shows network interfaces info

 

[MitelInMyBlood]

Thanks all.
This system was a victim of Thor's mighty hammer (lightning).
The replacement drive (single) was a Hitachi Deskstar (deathstar, imo, not very good luck with themm lots of early failures)

Immediately prior to the storm (day before) the system reported DBMS corruption.

I benched it yesterday and put a new drive in it and brought it up with default address (198.x.x.x etc) and hard coded my laptop on the same subnet. It initially came up, but about 15 mins later you'd lose the ability to communicate with it. Couldn't ping it either, even with direct cable connect from the 3300 to the laptop. Tried rebooting, same symptoms, worked for a few mins, then no communications

Anxious to get the customer back online I pulled the sysid button and drove a spare controller under it, moved the drive over, pulled down the licenses again, restored the DB and Life is good.
The old one has been stripped for parts and is now in the recycle bin.

The new drive is a Seagate barracuda.

Thought briefly about putting Rls 9 on it, but the site is scheduled to be migrated to Cisco in July.



Original MUG/NAMU Charter Member