ProLiant Servers (ML,DL,SL)
1748170 Members
4080 Online
108758 Solutions
New Discussion юеВ

Re: Proliant 1600 Second CPU

 
SOLVED
Go to solution
Wullie
Advisor

Proliant 1600 Second CPU

Hi all,

I have managed to get 2 CPU's for my system but i cannot seem to get them to work together.

Both CPU's work independently, bith processor boards work with each processor and similarly with the VRM's.

Now when i turn on the server i get a 212 error message.

Can anyone help?

Thanks

Wullie
11 REPLIES 11
Brian_Murdoch
Honored Contributor
Solution

Re: Proliant 1600 Second CPU

Wullie,

The dreaded 212 error is a critical error which remains with the server until you clear it using the system configuration utility. You must have had a genuine error at one time and it's been registered by the system. Even though you have good CPU's installed now the system won't let you continue until you clear it.

Run the system configuration utility (F10 at POST) when the cursor jumps to the right top of the screen.

At the Main Menu screen press CTRL-A to enter the Advanced menu mode. You should get a light blue screen appearing to tell you that the last fault was critical and then you can clear it. Follow the screen prompts to clear the 212 error and reset the system back to good health.

You can then insert the second CPU and all should be OK.

I hope this helps,

Brian
Prashant (I am Back)
Honored Contributor

Re: Proliant 1600 Second CPU

Hi,

We can try the following steps also:

1.Power up server.
2. Go to DCU (Default Configuration Utility) via F9 or SCU via F10.
3. Select Advanced Options from menu
4. Select Set CPU Corrected
5.Exit utility

Regards,
Prashant S.
Nothing is impossible
Wullie
Advisor

Re: Proliant 1600 Second CPU

Thats great guys.

I will try this later when i get home and hopefully i can rectify the problem.

Can i also ask another quick question, i am presuming that i don't need to set anything up before i insert the 2nd processor or do i need to change some setting which will then see the processor.

Thanks again
Brian_Murdoch
Honored Contributor

Re: Proliant 1600 Second CPU

Hi Wullie,

Just make sure you have the switch packs on the processor cage set correctly and that you have added a matching CPU and Voltage Regulator Module (VRM) to the board.

The core bus setting for CPU's with speeds of 350Mhz and above is 100Mhz, set by SW2=Off Off (two position switch).

You then set SW1 to match your multiplier for the CPU speed (4 position switch).

I have attached an image which should help you locate the switch packs but here are the values again.


Key 0=Off 1=On

CPU SW1 SW2
Speed 1 2 3 4 1 2

350Mhz 1 1 0 0 0 0
400Mhz 1 0 1 1 0 0
450Mhz 1 0 1 0 0 0
500Mhz 1 0 0 1 0 0
550Mhz 1 0 0 0 0 0
600Mhz 0 1 1 1 0 0

Regards,

Brian



Brian_Murdoch
Honored Contributor

Re: Proliant 1600 Second CPU

Sorry,

Here is the diagram which I forgot to add in my last reply.

Brian.
Wullie
Advisor

Re: Proliant 1600 Second CPU

Thanks Brian but my server is only a P2 300MHz with a 66MHz bus and uses EDO so that diagram doesn't help.
Brian_Murdoch
Honored Contributor

Re: Proliant 1600 Second CPU

Hi wullie,

Pentium II 66Mhz Core image attached.

Regards,

Brian
Wullie
Advisor

Re: Proliant 1600 Second CPU

Thanks again Brian.

I have my system set to run at 300MHz with switch 3 the only one that is on.

I have also tried using 2* P2 450MHz processors, which would be underclocked and recieve the same error.

This is the exact error message i recieve:-

Processor 1 Initialized at 300MHz with 512 cache
Processor 2 Initialized at 300MHz
212-Processor 2 Failed
178-Processor Configuration Invalid

Brian_Murdoch
Honored Contributor

Re: Proliant 1600 Second CPU

Wullie,

Did you manage to get into the system configuration utility and clear the 212 error successfully?

If you don't clear it you will always get this 212 error.

You might also have CPU's which have steppings that the BIOS doesn't like. Update the BIOS using the following link to see if this helps.

http://h18000.www1.hp.com/support/files/server/us/download/8571.html

Regards,

Brian