how to get two 3300 units to reconnect after network outage

[chris_s]

ping works fine, can ping each from the other

ran the busy and the rts, still showing OOS

[v2win]

This is a long shot but go into the ICP/PBX networking on each element and change the IP address to something else then save it then change it back.


I have never had one not recover on its own before.

[sarond]

I've had an issue before similar to this and it end up being a problem with the VPN.

There was some sort of routing issue. I can't remember any further but get the VPN checked as well.

[VinceWhirlwind]

My first thought would be to blame the network, but his ping succeeds, so there is no layer2 or layer3 issue.
 
I'd be looking closely at the trunk config next....

[chris_s]

I tried changing the ICP/PBX addressing, then changing it back, no luck.
tried rebooting routers on both side, no luck

I can ping both devices FROM the other device via maintenance commands. I'm no packet monkey, but IMHO connectivity is connectivity *shrug* in fact I am accessing the web console of the remote unit via the VPN (either direct via web, or by RDP'ing into a server on that side and using web there)

I'm supposed to have the local mitel service providers coming by tomorrow to fix it, I will be watching carefully and reporting back here.

[petr.necas]

Don't you have your network NATed?

[sarond]

In my case I'm not sure if it was the far end MCD that responded to the ping, it may have been something else that was misconfigured in the core.

[ZuluAlpha]

I'm going to file this in the "long shot" category, but I've had systems that could see each other and were convinced the others were in alarm, when in fact they weren't. Our solution ended up being in SNMP Configuration. We changed "Enable SNMP Agent" to no, let it sync, then changed it back to Yes and all was good.

[chris_s]

very unsatisfying resolution, ONE more reboot of each 3300 unit and they decided to start working