BCM 400 No access

[fssfireinc]

New user here been searching the forums for days for an answer but coming up dry. We have a bcm400 with 3.6 software, accessing the unit from the HTTP ip worked fine until one day it said it could not communicate with a part. I rebooted the system and the http or telnet never came back up, I have rebooted a few more times and nothing. I can ping the ip address on both lan2 and lan1 all status lights are fine and we have access to feature 981 so the drives must be good. Im at a loss on where to go from here.

Our original vendor went out of business but about ready to track down a new one to get this sorted out. If no one has any suggestions.

Thanks
Chris

 

[fssfireinc]

After further reading the forums it looks like maybe it was hit with the SSL bug of something happened after 2008. So I guess I will need to pull a vendor in here and do the patch as I think it might be beyond my technical skills of the system.

 

[phoneguy610]

id track one down

have you tried to plug directly into the bcm? Both Lan ports?

patching is always a good idea either way



ddcommllc.com
Avaya/Toshiba/Nortel

ACIS

 

[Firebird Scrambler]

For the BCM 400 models, you can try and use the serial port that is located on the front.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[telcodog]

The patch you're looking for is referred to as the "Apache Fix" patch. If you're vendor is anywhere decent, their techs should have that one right on their laptops. If you can't get a copy, post back here and we'll get you fixed up somehow.

 

[fssfireinc]

The vendor came out and was hesitant to work on it. He seemed to think if he touched it the whole system would go down. Not to mention he said the http browser had to be in working order before patches could be applied, But he was nice enough to leave me the patches, And After he left I applied the Apache patch and it came right back up and is working. He kept saying the system is old outdated no longer supported.

Thank you all for the help just glad to be back up and running.

 

[norstarboy125]

How did you apply the patch if you were unable to access the system?

Jeremy J. Carter
Charm City Communications

http://www.charmcitycommunications.com

Norstar. BCM. CS1000 Programmer

 

[telcodog]

It's a 3.6 and this patch addressed the issue of not being able to access the system due to an expired SSL certificate. All you do is open the patch, tell it the ip address of the BCM and let it go. It fixes the problem all by itself and once it's done, you are able to access the system normally.

 

[norstarboy125]

I totally didn't even pay attention to the software release being 3.6, I actually like the older NT way of patching versus the newer Linux way. That being said it's probably the only thing that I liked better, I very seldom work on any BCM's below 4.0 these days.

Jeremy J. Carter
Charm City Communications

http://www.charmcitycommunications.com

Norstar. BCM. CS1000 Programmer