Apache on BCM200 v3.6

[pronei]

I just replaced the HDD in BCM200 v3.6.

There are no patches installed yet as I can not seem to get into the webserver. I did the universal initialization process and set the IP address. (Apache did not work prior to IP change either)

Is there a way to get apache to start on a BCM200 v3.6?

I can get in through the com port and a cross over cable in LAN1 or LAN2.

This is what I see when I look at services.
Enter selection : 4
No ServiceName DisplayName Type Status LogOn As
----------------------------------------------------------------------------
1> AlarmSvc AlarmSvc Manual Stopped LocalSystem
2> Alerter Alerter Manual Stopped LocalSystem
3> Apache Apache Automatic Stopped LocalSystem

Apache = Stopped = BAD BAD BAD!!

I've tried to hard, cold, & warm restarts.

 

[acewarlock]

Then start it.




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.

 

[pronei]

I tried, doesn't take. I'm going to re-run the Initialize Universal Profile and start from scratch again.

 

[pronei]

Ok, started from scratch with Initialize Universal Profile.

After that, still no apache and I can't make it start either.

Any Ideas?

 

[biv343]

Set the date back on the BCM via the command line (type date at the command prompt and follow the prompts). Change it to something before January 28, 2008.

Reboot.

Run universal profile.

Change date on system back to todays date.

Refer to bulliten 2008008624 for more details.

 

[pronei]

Actually, I figured it out. I had a corrupt SSL certificate. The bcm.cer file was bad.

I hooked 2 different BCM hdd's into a working PC, then copied the certificate files from one bcm hdd to the other. Once I put that hdd back in the BCM, it worked.

 

[acewarlock]

Was that the problem on the origanl HD also or was something else wrong with it?




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.

 

[biv343]

That's what the bulliten is about. The system you copied the certificate from was created before 1/28/2008.

Interesting that you can copy a cert from one system to another. I'll keep that in mind.

Background:
This bulletin is to inform our customers that there is an issue with BCM SSL certificate creation after or on the date of
01/28/2008. This makes Unified Manager inaccessible after performing an upgrade or platform initialization, including BIT
imaging.
Nortel is working toward a permanent solution. This bulletin includes steps to prevent the issue, as well as a workaround.
Analysis:
There is an issue with BCM SSL certificate creation after or on the date of 01/28/2008.
Impact: Unified Manager is inaccessible after performing an upgrade or platform initialization, including BIT imaging.
Recommendations:
PREVENTATIVE STEPS:
This process requires commandline access to the BCM to modifiy the date until the Upgrade (BCM 3.x to BCM 3.x) or
platform initialization process to prevent this condition:
TEMPORARY WORKAROUND:
This process assumes that the PC you are using has IP connectivity to the BCM. (You may need to access the
"configuration menu" via the serial connection to set the LAN IP address and Next Hop Router if required.
A zip file from our ftp server is required to resolve this issue which must be then be transfered to the BCM, and you will
need to be able to access the command line from your PC
For a document with complete list of steps, with screen shots, please access the attachment.
Required Actions: