ELEMENT MANAGER TO BCM1000 UPGRADED FROM 3.7

[TWISTEDAPP]

I've got a BCM1000 that was upgraded from 3.7 to 4.0 and when I try and use Element Manager through a VPN tunnel, it comes up with some error and won't let me in yet it is ok on site? Any ideas?

 

[MagnaRGP]

Check default gateway on the BCM and be sure it knows how to route to your remote user IP.

 

[TWISTEDAPP]

We currently have IP sets working off site so could that still be a problem, or would that have to be correct in order for the IP sets to work? Actually, the IP sets on the other published IP lan and the gateway would be specified different to accomodate that. Let me know if there's a solution.

 

[TWISTEDAPP]

I was rethinking this and I come in through a VPN tunnel they've created and am on their network. I'm then trying to access the BCM through their internal network and have access through Element Manager to the remote sites with BCM50S, but cannot access the 1000 that had been upgraded from 3.7 to 4.0? There are IP sets off prem working off of the second LAN card and hence the default gateway programming would reflect the other gateway as separate provisioning was made for the VOIP sets. i.e Separate DSL line.

 

[MagnaRGP]

put a static route in the bcm for your remote user ip to the internal vpn endpoint ip address. assuming that lan1 on the bcm is on the same subnet as the vpn endpoint, you should be in business.

 

[TWISTEDAPP]

I thought I'd follow up with the exact message that I was receiving when I'd tried to use the element manager.

The message is:

Detector 'BCMDetector' cannot determine the device type for 192.168.11.10

 

[MagnaRGP]

Can you post the full IP scope (LAN2, LAN1 and remote user IP and gateway)?

 

[DBrewsky]

Make sure you are not blocking port 5989 anywhere as it's required for Element Manager to work. I take it you can access the BCM1000 4.0 Webpage?