Integrity Servers
1753907 Members
8476 Online
108810 Solutions
New Discussion юеВ

Re: can't get RX1600 to POST

 
SOLVED
Go to solution
Sameer_Nirmal
Honored Contributor

Re: can't get RX1600 to POST

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
Honored Contributor

Re: can't get RX1600 to POST

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
Honored Contributor

Re: can't get RX1600 to POST

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
Honored Contributor

Re: can't get RX1600 to POST

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.