can't get RX1600 to POST

[Alan_152]

I ended up with a pile of parts that when put together turned out to be an RX1600. I finally managed to get the MP working again, but I can't get the unit to POST or into EFI.

Here is the system event log for the current boot cycle:

# Location|Alert| Encoded Field | Data Field | Keyword / Timestamp
-------------------------------------------------------------------------------
5 BMC 0x20000001AB020060 FFFF036F00070300 Type-02 076f03 487171
00:07:07
4 BMC 2 0x2000000133020050 FFFF006FFA220300 Type-02 226f00 2256640
00:05:07
3 BMC 2 0x2000000133020040 FFFF027000120300 Type-02 127002 1208322
00:05:07
2 BMC 2 0x2000000130020030 0781A37000120300 Type-02 127003 1208323
00:05:04
1 BMC 2 0x2000000111020020 FFFF056FFA220300 Type-02 226f05 2256645
00:04:33
0 BMC 2 0x2000000111020010 0780A37000120300 Type-02 127003 1208323
00:04:33


Here is the VFP:

LEDs | LOCATOR | SYSTEM | POWER
-----------------------------------------------------------------------------
| OFF | FLASH RED | ON GREEN
-----------------------------------------------------------------------------
Status | Fatal System State detected. Check System Event Log (SL) for error me
ssages.
| Reading System Event Log will turn off the Attention LED.

Nothing shows up on the console at all...

Here's the VRU list from DF. I don't see anything out of whack here, either. Anything I should look for?


FRU Entry # 0 :
FRU NAME: MP Board ID:06
CHASSIS INFO:
BOARD INFO:
Mfg Date/Time : 0
Manufacturer : hp
Product Name : management processor card
S/N : 40CTMJZ0BM
Part Number : A7231-66580
Fru File ID : 10
Custom Info : B
Custom Info : 4343
Custom Info : B
Custom Info : 0


FRU Entry # 1 :
FRU NAME: Processor 0 ID:20
PROCESSOR DATA
S-spec/QDF: Q93Z
Sample/Prod: 00
CORE DATA
Arch Revision : 00
Core Family : 1F
Core Model : 02
Core Stepping : 01
Max Core Freqency : 1300 MHZ
Max SysBus Freqency : 200 MHZ
Core Voltage : 1150 mV
Core Voltage Tolerance,High : 17 mV
Core Voltage Tolerance,Low : 17 mV
CACHE DATA
Cache Size : 3072 Kb
PACKAGE DATA
Package Revision : INT3
Substrate Revision: 00
PROC PART NUMBER DATA
Part Number : 80543KC
Electronic Signature : AAF6E14FF9AD0100
THERMAL REF DATA
Upper Temp Ref : 101 C
Calibr Offset : 0 C
FEATURES DATA
IA-32 Proc Core Feature Flags: FFFB8743
IA-64 Proc Core Feature Flags: 1B81806300000000
Package Feature Flags : 0B000000
Devices on TAP Chain : 1

FRU Entry # 2 :
FRU NAME: Processor 1 ID:21
PROCESSOR DATA
S-spec/QDF: Q93Z
Sample/Prod: 00
CORE DATA
Arch Revision : 00
Core Family : 1F
Core Model : 02
Core Stepping : 01
Max Core Freqency : 1300 MHZ
Max SysBus Freqency : 200 MHZ
Core Voltage : 1150 mV
Core Voltage Tolerance,High : 17 mV
Core Voltage Tolerance,Low : 17 mV
CACHE DATA
Cache Size : 3072 Kb
PACKAGE DATA
Package Revision : INT3
Substrate Revision: 00
PROC PART NUMBER DATA
Part Number : 80543KC
Electronic Signature : AAEEFDD96D6B0300
THERMAL REF DATA
Upper Temp Ref : 101 C
Calibr Offset : 0 C
FEATURES DATA
IA-32 Proc Core Feature Flags: FFFB8743
IA-64 Proc Core Feature Flags: 1B81806300000000
Package Feature Flags : 0B000000
Devices on TAP Chain : 1


FRU Entry # 3 :
FRU NAME: Processor 0 RAM ID:24
Invalid Checksum


FRU Entry # 4 :
FRU NAME: Processor 1 RAM ID:25
Invalid Checksum




FRU Entry # 5 :

FRU NAME : DIMM0A

FRU ID : 0x80

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x05

JEDEC Mfg Serial # : 0x450A78D9

Mfg Unique Serial # : 0x00CE010405450A78D9


Type for next entry, or Q to quit:


FRU Entry # 6 :

FRU NAME : DIMM0B

FRU ID : 0x81

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x05

JEDEC Mfg Serial # : 0x4504796D

Mfg Unique Serial # : 0x00CE0104054504796D


Type for next entry, or Q to quit:


FRU Entry # 7 :

FRU NAME : DIMM3A

FRU ID : 0x84

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x03

JEDEC Mfg Serial # : 0x410F5CDF

Mfg Unique Serial # : 0x00CE010403410F5CDF


Type for next entry, or Q to quit:


FRU Entry # 8 :

FRU NAME : DIMM3B

FRU ID : 0x85

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x05

JEDEC Mfg Serial # : 0x450A79BC

Mfg Unique Serial # : 0x00CE010405450A79BC


Type for next entry, or Q to quit:


FRU Entry # 9 :

FRU NAME : DIMM1A

FRU ID : 0x88

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x03

JEDEC Mfg Serial # : 0x41045CC5

Mfg Unique Serial # : 0x00CE01040341045CC5


Type for next entry, or Q to quit:


FRU Entry # 10 :

FRU NAME : DIMM1B

FRU ID : 0x89

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x05

JEDEC Mfg Serial # : 0x450F791C

Mfg Unique Serial # : 0x00CE010405450F791C


Type for next entry, or Q to quit:


FRU Entry # 11 :

FRU NAME : DIMM2A

FRU ID : 0x8C

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x03

JEDEC Mfg Serial # : 0x410A5CDA

Mfg Unique Serial # : 0x00CE010403410A5CDA


Type for next entry, or Q to quit:


FRU Entry # 12 :

FRU NAME : DIMM2B

FRU ID : 0x8D

JEDEC SPD Rev : 16

JEDEC Mfg ID : 0xCE00000000000000

JEDEC Mfg Location : 0x01

JEDEC Mfg Part # : M3 12L2920BTS-CB0

JEDEC Mfg Revision Code : 0x5342

JEDEC Mfg Year : 0x04

JEDEC Mfg Week : 0x03

JEDEC Mfg Serial # : 0x41055CC6

Mfg Unique Serial # : 0x00CE01040341055CC6


Type for next entry, or Q to quit:


FRU Entry # 13 :

FRU NAME: Motherboard ID:00


CHASSIS INFO:

Type:Rack Mount Chassis

Part Number : A9901-62001


BOARD INFO:

Mfg Date/Time : 4259878

Manufacturer : JABIL

Product Name : server rx1600 system board

S/N : 52JAPE4406111376

Part Number : A9901-60001

Fru File ID : 10

Custom Info : A

Custom Info : 4405

Custom Info : A3

Custom Info : 0


PRODUCT INFO:

Manufacturer : hp

Product Name : server rx1600

Part/Model : A9901A

Version : PP3

S/N : USE44136F1

FRU File ID : 11

Custom Info : 108

-> This is the last entry in the selected list.


MP Host Name: uninitialized

MP:CM>

[KVK]

Hi Alan ,

It seems to be some H/W error with your system . Some major component has become faulty that's the reson it not even doing the POST test .


In front of system 4 diagnostic LED will be there mentioned 1,2,3,4 what is the status ?

If you press the locator button wat u r hearing ? Locator button engaged with BLUE LED

[Alan_152]

I can turn on and off the locator at will... The fans power up to 50%, then full, then 75%, then back to 50% as the MP engages.

The VFP shows this:
Here is the VFP:

| OFF | FLASH yellow | ON GREEN


LEDs 1-4 stay off all the time

[KVK]

If you refer the service manual at location
chapter 6

http://docs.hp.com/en/rx1600_OpMaint/rx1600_OpMaint.pdf

With it's refering fault indiacation & attention required stare .. Locator LED are off it's shoudn't be

please post the output of mp:CM > ps

also

mp>sl -> e

[Sameer_Nirmal]

Hi,

I believe the cause of the problem could be the Failed FRU Identification for FRUs 3 and 4. Either those FRUs are failed or could not be queried.
Can you provide the System Event Log /Forward Progress Log and MP -> SL -> D

Moreover, Did you have some hardware fault before as you are saying making MP working?
Which parts you piled up?

You need to know the events with alert level 3 and above to diagnose the possible cause of the problem.

[Roger Faucher]

Alan:

The A9901 variant was a single CPU version. I would try making it work with one CPU first.

Make a great day!

Roger

[Alan_152]

KVK: Currently, the VFP looks like this (having restared the unit since I wrote last):

LEDs | LOCATOR | SYSTEM | POWER
-----------------------------------------------------------------------------
| OFF | FLASH RED | ON GREEN
-----------------------------------------------------------------------------

leds 1-4 are also off.

The output you request is as follows:

MP:CM> ps


PS
System Power state: On
Temperature : Normal


Power supplies State
-----------------------------------------------------------
Power Supply 1 Normal


Fans State
-----------------------------------------------------------
Fan 1 (PSU) Normal
Fan 2 (Mem) Normal
Fan 3 (CPU) Normal


MP:SL> e

l


# Location|Alert| Encoded Field | Data Field | Keyword / Timestamp
-------------------------------------------------------------------------------
4 BMC 0x20000001EC020050 FFFF036F00070300 Type-02 076f03 487171
00:08:12
3 BMC 2 0x2000000175020040 FFFF006FFA220300 Type-02 226f00 2256640
00:06:13
2 BMC 2 0x2000000170020030 0781A37000120300 Type-02 127003 1208323
00:06:08
1 BMC 2 0x2000000152020020 FFFF056FFA220300 Type-02 226f05 2256645
00:05:38
0 BMC 2 0x2000000151020010 0780A37000120300 Type-02 127003 1208323
00:05:37
-> This is the first entry in the selected log.



Log Entry 4: 00:08:12
Alert Level : Unknown
Keyword: Type-02 076f03 487171
Logged by: BMC; Sensor: Processor
Data1: FRB2/Hang in POST failure
0x20000001EC020050 FFFF036F00070300


Log Entry 3: 00:06:13
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: BMC; Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x2000000175020040 FFFF006FFA220300




Log Entry 2: 00:06:08
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x07
0x2000000170020030 0781A37000120300


Log Entry 1: 00:05:38
Alert Level 2: Informational
Keyword: Type-02 226f05 2256645
ACPI state S5 (soft-off)
Logged by: BMC; Sensor: System ACPI Power State - ACPI State
Data1: S5/G2 soft-off
0x2000000152020020 FFFF056FFA220300



Log Entry 0: 00:05:37
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x07
0x2000000151020010 0780A37000120300


-> This is the first entry in the selected log.


Sameer: I have no idea what FRU3 and FRU4 are. Also, as I said, the MP wasn't talking until I removed the battery for about 6 weeks. The rest of the machine came to me as parts; it was at one point a working box but people have been raiding it for parts. The CPUs and memory are known good.


The output you request is "an invalid input".

How do I determine the events associated with level 3?


Roger: OK, as recommended, I removed CPU1. All that is left is CPU0. No change in performance, btw...

[Sameer_Nirmal · Accepted solution]

Alan,

Alert events could be collected using
MP -> sl -> e -> D
MP -> sl -> e -> a -> 3 ( for Warning Alert Level 3 )
MP -> sl -> e -> a -> 5 (Critical Alert Level )
MP -> sl -> e -> a -> 7 (Fatal Alert Level)
MP -> ss
MP -> sysrev

Are the CPU Power Pods are known working good?

I do suspect the most probable problem could be with the system board.

[Alan_152]

Sameer: The power pods are known good as well...

One of my teammates concurs with you on it being the system board, and recommends reflashing the system -- except that it'll be tough to do that without being able to get to the EFI.

[Alan_152]

Sameer: The alerts you requested I look at include:

A dump of the entire log after 15 minutes after power up (no alert levels 3 or higher were noted):

Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x07
0x2000000017020010 0780A37000120300


Log Entry 1: 00:00:24
Alert Level 2: Informational
Keyword: Type-02 226f05 2256645
ACPI state S5 (soft-off)
Logged by: BMC; Sensor: System ACPI Power State - ACPI State
Data1: S5/G2 soft-off
0x2000000018020020 FFFF056FFA220300


Log Entry 2: 00:00:53
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x07
0x2000000035020030 0781A37000120300


Log Entry 3: 00:00:57
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: BMC; Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x2000000039020040 FFFF006FFA220300


Log Entry 4: 00:02:56
Alert Level : Unknown
Keyword: Type-02 076f03 487171
Logged by: BMC; Sensor: Processor
Data1: FRB2/Hang in POST failure
0x20000000B0020050 FFFF036F00070300



SS shows this (which I don't understand, so I'll switch out processors):

SS

System Processor Status:

Monarch Processor: 0

Processor 0: Not Installed
Processor 1: Not Installed


Sysrev shows this:

SYSREV

Current firmware revisions

MP FW : E.02.23
BMC FW : 02.26
System FW : 01.10

[Sameer_Nirmal]

Alan,

SEL log entry 4 is co-related with the MP -> SS output and that makes a sense.
Unless atleast one workable CPU is installed , the POST won't complete.

As far the "Invalid Checksum" error for those FRUs are concerned , it is a bug in the current BMC firmware.
This is fixed in the BMC firmware version 03.48. Refer following release note for the latest MP/BMC/SF firmware.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=447332&swItem=ux-31822-1&prodNameId=406201&swEnvOID=54&swLang=13&taskId=135&mode=4&idx=0

So you need to update the firmware once POST issue is resolved.

By the way which processors you are using ? I doubt because as per the FRU info , the CPUs you have are 1.3GHz !!
Be-aware rx1600 support 1GHz CPU ( AB220A ) . Verify them.

Just make sure once again the parts you are using are supported for rx1600.

If you could succeed to go further assuming the CPU issue is resolved, then you can watch SEL logs, maybe in that case
system board could be a culprit.

[Alan_152]

Sameer -- what you suggest does seem to be part of the problem... the CPUs are from a 1620, are part # AB481, and are 1.3Ghz CPUs... I'll go find some slower ones...

[Alan_152]

Sameer -- OK, got a proper CPU installed:

SS

System Processor Status:

Monarch Processor: 0

Processor 0: Installed and Configured
Processor 1: Not Installed

My system event logs get a little further than before now:

Log Entry 7: 01 Jan 1998 00:01:21
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: BMC; Sensor: System Event
0x2034AADCD10200A0 FFFF027000120300


Log Entry 6: 01 Jan 1998 00:01:18
Alert Level 2: Informational
Keyword: BOOT_START
CPU starting boot
Logged by: System Firmware 0
Data: Major change in syst
0x5480006300E00080 0000000000000000


Log Entry 5: 01 Jan 1998 00:01:18
Alert Level 2: Informational
Keyword: Type-02 1d0a00 1903104
CPU starting boot
Logged by: SFW-redundant; Sensor: System Boot Initiated
Data1: transition to Running
0xC134AADCCE020070 FFFF000A001D0300


Log Entry 4: 01 Jan 1998 00:01:18
Alert Level 2: Informational
Keyword: BOOT_START
CPU starting boot
Logged by: System Firmware 0
Data: Major change in system state
0x5480006300E00050 0000000000000000


Log Entry 3: 01 Jan 1998 00:01:18
Alert Level 2: Informational
Keyword: Type-02 1d0a00 1903104
CPU starting boot
Logged by: SFW-redundant; Sensor: System Boot Initiated
Data1: transition to Running
0xC134AADCCE020040 FFFF000A001D0300


Log Entry 2: 01 Jan 1998 00:01:15
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Rese
Logged by: BMC; Sensor: System Event
0x2034AADCCB020030 FFFF027000120300


Log Entry 1: 01 Jan 1998 00:01:12
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x01
0x2034AADCC8020020 0181A37000120300


Log Entry 0: 01 Jan 1998 00:00:42
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x01
0x2034AADCAA020010 0180A37000120300

And so do my forward progress logs:


Log Entry 17: 01 Jan 1998 00:01:21: uninitialized
Alert Level 2: Informational Log Viewer Menu:
Keyword: Type-02 127002 1208322 Entries % Full
Soft Resetstamped En
Logged by: BMC; Sensor: System Event
0x2034AADCD10200A0 FFFF027000120300-----------------------------------


Log Entry 16:
Alert Level 0: Minor Forward Progress


Log Entry 15:- Clear All L
Alert Level 0: Minor Forward Progressvents

Enter menu i
Keyword: BOOT_BUS_CONFIG_VALUE

Current bus config register value

CO: Console
Logged by: System Firmware 0l Front Panel
Data: Actual data CM: Comma
0x0300000600E00000 0000000000000000 CL: Console Log


Log Entry 14: SL: Show
Alert Level 0: Minor F

0x0000024B00E00000 0000000000000000

MP Host Name: uninitialized


MP Host Name: uninitialized


Event Log Viewer M
Timestamped Entry



Log Entry 13:
--------
Alert Level 0: Minor Forward Progress-----------------------------
Keyword: BOOT_SCR_TEST_START
Scratch RAM test System Event
Logged by: System Firmware 0 Jan 1998 00:01:21
Data: Data field unused
0x0000005600E00000 0000000000000000 18 0 % 01 Jan 1


Log Entry 12:
Alert Level 0: Minor Forward Progress
B - Current Boot
Keyword: BOOT_CELL_CONFIG
Timestamped Entry



Log Entry 11:
---------
Alert Level 0: Minor Forward Progress----------------------------
Keyword: Unknown Event
Logged by: Unknown 0
E - System Event
Data: Implementation dependent data field 00:01:21
0x160015B200E00000 0000000001661898


Event Log Navigation Help:


Log Entry 10:

+
Alert Level 1: Major Forward Progresstime, e.g. from 3 to 4)
Keyword: BOOT_CPU_PRESENT
CPU present View pre
Logged by: System Firmware 0


Log Entry 9:

Alert Level 1: Major Forward Progressyword
Keyword: BOOT_CELL_MONARCHw mode configuration - Tex
CPU is the monarch
Logged by: System Firmware 0ilter options
Data: Implementation dependent data fieldel Unfiltered
0x3600000C00E00000 0000000000000000enu


Log Entry 8:it and retur
Alert Level 0: Minor Forward Progress
Keyword: BOOT_CELL_MONARCH_SEL_STARTnd return to the MP Main Menu
CPU at monarch selection





Log Entry 7:01 Jan 1998
Alert Level 0: Minor Forward Progress
Alert Level 2: Informational
Keyword: BOOT_CPU_CONFIGeyword: Type-02 127002 1
starting cpu config
S
Logged by: System Firmware 0 BMC; Sensor: System Event
Data: Implementation dependent data fieldAADCD10200A0 FFFF027000120300
0x1600001D00E00000 001F0105000000006: 01 Jan 1998 00:01:18


Log Entry 6: 01 Jan 1998 00:01:18 Informational
Alert Level 2: Informational
CPU star
Keyword: BOOT_START
Logged by: S
CPU starting bo




Log Entry 7: 01 Jan 1998 00:01:21



Log Entry 5: 01 Jan 1998 00:01:18ational
Alert Level 2: Informational08322
Keyword: Type-02 1d0a00 1903104gged by: BMC; Sensor: System E
CPU starting boot
Logged by: SFW-redundant; Sensor: System Boot Initiated


Log Entry 6: 01 Jan 1998 00:01:18
Data1: transition to Running
Alert Level 2: Informat
0xC134AADCCE020070 FFFF000A001D0300yword: BOOT_START


Log Entry 4: 01 Jan 1998 00:01:18
Logged by: System Firmware 0
Alert Level 2: Informationalta: Major change in syst
Keyword: BO

Log

Keyword: Type-02 1d0a00 1903104



Log Entry 3: 01 Jan 1998 00:01:18ing boot
Logged
Alert Level 2: Informationalystem Boot Initiated
Keyword: Type-02 1d0a00 1903104
Data1: transit
CPU starting boot
Logged by: SFW-redundant; Sensor: System Boot Initiated


Log Entry 4: 01 Jan 1998 00:01:1
Data1: transition to Running
Alert Level 2: Informa


Log Entry 1: 01 Jan 1998 00:01:12
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x01
0x2034AADCC8020020 0181A37000120300


Log Entry 0: 01 Jan 1998 00:00:42
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: BMC; Sensor: System Event
Data2: OEM Code2: 0x01
0x2034AADCAA020010 0180A37000120300

[Alan_152]

It looks like what the issue is is that I have firmware installed on the box that doesn't match the CPUs I'm trying to put in it.