BCM Monitor will not connect

[jsaad]

I can't connect with BCM Monitor at all. I can log in with element manager but BCM Monitor will not come up. Do I need to do a reboot? It's BCM 400 4.0

 

[Dasheen]

Have you tried uninstalling it and downloading it again from the BCM 4.0?

If you can get into EM with the same IP & pswd, no reason you shouldn't get in.

 

[acewarlock]

Verify that the Published IP is correct, it has to be the same one that the EM is using.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[jsaad]

I checked, everything is correct. I've been using BCM Monitor for about 6 months to monitor my 8 remote IP phones. Just on Monday it stopped working. I may have disconnected from BCM monitor abruptly that day. I am monitoring it over a VPN link but to be clear, element manager works fine and I can go the BCM IP web page just fine.

Sounds like a reboot is in order. Is there any way to see if the BCM monitor service is running or can be restarted? I think there is...

 

[jsaad]

i tried on site, without a reboot and get error 80011

 

[jsaad]

can i reboot directly from element manager? how long would it take to come back completely, i have 20 tels, PRI, 8 IP phones and 20 mailboxes/autoattendant?

any ideas about that error?

 

[CTCINY]

Yes you can. Adminsistration -> Utilities -> Reset -> Reboot System. I will only take down your IP phones and voicemail. Digital sets and PRI should stay up.

What doesn't kill you only makes you stronger.

 

[option11newby]

There was a solution from Nortel for this issue on the BCM50 Release 1.0

Error 80011 is an error when a secure socket connection fails.

The reason why BCM Monitor is unable to establish a connection, or maintain the connection, with the BCM is due to the MSM service in the BCM. The MSM service sometimes experience problems with secure connections with the BCM Monitor, and once this happens, the service is unable to accept new connection requests from BCM Monitor. The MSM service is unable to recover from this problem when it happens and this is why the BCM needs to be rebooted. But rebooting the BCM will not help to solve the problem, because the MSM service will still have difficulty handling secure connections

The fix was:
Apply patch BCM050.161-MSM, or a later version. Remember to refer to the patch release notes. Applying this patch will help to solve this issue, and BCM Monitor will be able to maintain a secure connection with the BCM.

I do not know whether there is a similar fix for the BCM400 V4, or whether there was a corresponding MSM patch for V4.

Just thought this might be associated.



NCSS, NCDS, NCTS