BCM 50 Red Status light Flashing Green power light

[DoubleCross]

Hey all, I have a bcm50 that I changed the ip address on through a phone. I did a reboot and the phones won't come up.
I get a red status light and a flashing green power light. I can access the ip through a web page to get to downloads. I
can access callpilot from a web page. I can access the system with bcm monitor. I can't access with element manager.
It shows version 1.00.2.04.j in bcm monitor. Any help would be appreciated. Thanks.

 

[curlycord]

Reboot it again.

Flashing green usually means it's still booting.

________________________________________

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[DoubleCross]

Curlycord, I have rebooted many times. This started yesterday morning. I worked on it onsite most of the day. I took it out and brought it home to work on.
I even let it sit all night, still the same this morning.

 

[exsmogger]

Try booting it up without any Ethernet cables connected, if you haven't already.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

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

 

[DoubleCross]

exsmogger, Pretty sure I did, but I will try again. all kind of a blur now.

 

[DoubleCross]

exsmogger, That didn't work..

 

[ucxguy]

The flashing green LED means that services are still coming up. The red LED indicates that some critical failure occurred. I suspect the critical failure is the reason why the startup of services never completes. Based on the symptoms, it appears the failure is related to the management service (that's why you cannot connect to the system using Element Manager).

Information about the startup as well as the critical error is logged into the file alarms.systemlog - normally located in the directory /var/log. If you remove the hard drive from the BCM50 and connect it to a PC running Linux, you should be able to mount the 8th partition on the drive and find the log file in the directory "log". The line with the critical error should contain the text "critical" - so you should be able to find it easily (for example by running the command "grep critical log/alarms.systemlog" from the Linux command line).

If you have a replacement drive with the same software release (looks like BCM release 1 based on the version reported by BCM Monitor) that you could put into this BCM50, there is a decent chance the system could come up without issues.

 

[exsmogger]

I'd have to guess given the age of the system that the hard drive has gotten corrupted. You can install an R1 or R2 hard drive and restore the current license file.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

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

 

[DoubleCross]

Thanks for the replies. ucxguy, never used Linux, so that's out for me. exsmogger, I have no access to the keycode file. Pretty sure krs is shut down. Weren't the keycodes tied to the motherboard? Forgive me guys, I have worked on bcm since they came out, but not for a while now. Have forgotten a lot. I did put a bcm50 release 3 in and finally got a solid green power light, but took it out because of the version mismatch. I currently have no version 1 or 2 drives.