Adding second processor to Proliant 3000

[Paul Brown_4]

I just acquired a second processor (both are 300 MHz) so I shut everything down and plugged the new proc in. During bootup, I got the following errors on my monitor...

212-Processor 2 Failed
178-Processor Configuration Invalid

I then used my System Configuration Utility disks to fix the configuration. The utility asked if I wanted it to automagically fix what ailed me and I consented. During this process I got a few errors that said something about a board not being added (unfortunately, I didn't write them down).

I now have two basic problems.

1) I have no video. I can see the boot progress with the LCD but the monitor never displays anything. The LCD reports the following error, which I suspect may be related to this problem...

** 001 of 116***
----CAUTION----
10/21/2002
11:30 PM
POST ERROR
Code: 46h
175-EISA
Configuration/
Slot Mismatch
Device Found
**END OF EVENT*

2) If I remove this new processor, the server will not even try to boot (the fans never spin up or anything). All that happens is that the Board Temp, Temp Trip and IERR LEDs on the processor board will flash red somewhat dimmly. Before introducing this second processor to the server, it would boot without complaint with the original processor.

Any help anyone could provide would be much appreciated.
Thanks

[Paul Brown_4]

I would have edited my post to add/change this info, but it seems we can't do that here. :(

Anyway, I should specify that I have no *on board* video. I am able to get a video display with a seperate video card.

But to be clear, I seem to be able to run the server just fine with both processors as long as I don't want to use the on board video (which did work before adding the second processor).

[Jasmine Davis · Accepted solution]

Hi Paul, I also had CPU problems with a Proliant 3000 with dual 300MHz. I ended up downloading & running the configuration erase utility, then installing the cmos rompaq & then using the configuration utility to set the system up from scratch. That fixed my problem. Just remember though those older Proliants usually error if you remove & refit something, & afterwards can only be fixed by the configuration utility. Good Luck Jasmine

[Paul Brown_4]

Thanks