MCD 6.0 SP2/SP3 networking issues

[MitelJam]

I have two systems MCD 6.0 SP2 and MCD 6.0 SP3 networked but not clustered. Networking is being done via VPN and were working. One system was rebooted Friday morning and the customer discovered that the two were not talking to each other, but we do not know if this happened after we rebooted, or if they stopped communicating before. No changes were done on either system and the customer said no changes were done to the network. Windows applications continue without any discussions. RME responds with TIMEOUT on both sides. Ping and Tracrt work from both sides. I rechecked programming on both systems and that's ok.

Any help would be appreciated.

 

[MitelJam]

Windows applications continue to work without any disruptions.

 

[Billz66]

if programming is ok then it sounds like perhaps ports are being blocked ?

are you running pings from RTC-> other site via maintenance command ?



If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....

 

[MitelJam]

Pings are going through via command line. What port nos. should I allow to go through?

 

[Billz66]

command line on what ? , if you are not doing them from the maintenance command then perhaps pings arent working as you think?

1066 TCP is XNet 1067 TCP is Ip networking SSL

there may be more required for the speech portion , We normally use clustered systems so i dont have a list off hand



If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....

 

[bobcheese]

if you want to know when the IP trunks dropped check the maintenance logs it will show when the heartbeat dropped.

 

[bobcheese]

Also, when you say 'the two systems are not talking to each other' do you mean the IP trunks are down? IE you have an IPCOMMS alarm?

 

[MitelJam]

Billz66- pings from the ESM on either of the 3300's to the other RTC. Are you saying if they were clustered there might not be these problems?

Bob cheese- yes icp comms error. I will check logs for the heartbeat error.

I left the network guy yesterday and will check back with him if had any progress.
HTTPS to the far side was not tested because the guy said VPN would not open up on that type of traffic, so he gave me access via Remote Desktop over the VPN

 

[MitelJam]

Logs were overwritten.

 

[danramirez]

MitelJam, what do you get when entering:

RMESS VERIFY PBX <Number of Remote PBX> LAN

It usually gives you why IP Networking does not come up.

Help on line will give you further details of this command.

Cheers,

Daniel

http://www.hatkana.com

http://www.wtelecom.com