element manager port locked up

[ramblingrebel]

Hi.
I'm trying to figure out an issue with a "deployed" bcm50. its been in service, i'm guessing 8 years
it has suddenly stopped letting the element manager access it
i plug into the OAM port
i can get to the webpage and login
i can login to the callpilot
but element manager says its an unknown device
i tried multiple things, and finally decided to power cycle the unit
and i could then get into the bcm with element manager
but that lasted 24 hours
i think its due to be swapped out and am speaking to curlycord regarding that
but in the meantime, has anybody had this happen?
it almost seems like the bcm is closing the port the element manager talks on
but only that port?
any direction is appreciated
regards rr

 

[curlycord]

Go to Java Control Panel, Java Tab, View button, how many versions listed and note if they are X86 or 64.

 

[ramblingrebel]

I have 2 laptops for servicing all my customers
win8.1 to take on site it has no java installed on it
win10 for vpn or port forward access has one version installed and its x86

no other bcm is giving me this issue
and a reboot gets me access from both machines on the LAN port side
and onsite with the win8.1 on the OAM port

but only last about 1 day

 

[curlycord]

"win8.1 to take on site it has no java installed on it"

Regardless of the fix, you should double check since Java is required for BEM to work.
Also (curious), on the Update tab of the Java console, is it Auto or disabled?

Due to site construction/access I would proceed with the swap out then as partially discussed, in lab:
-Restore/from Factory Default/ only the Data Services & Network Interfaces
-Test connection for a few days

Since you will have restored a backup I would wait to see if you get the same issue.
If you do then do the same Factory Default/ Data Services & Network Interfaces and reprogram from scratch.

 

[Firebird Scrambler]

What version of Element Manager are you using?

The older Nortel version should work, but you can't access the SIP trunking area.

The later Avaya version will require Java as Curlycord has mentioned.