HPE 9000 and HPE e3000 Servers
1753762 Members
4708 Online
108799 Solutions
New Discussion юеВ

Re: rp3440 can not boot normal ,with some error

 
SOLVED
Go to solution
хР┤шГЬщФж
Occasional Advisor

rp3440 can not boot normal ,with some error

next is some MP log . pls HELP me

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


Log Entry 1: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127001 1208321
BMC firmware initializing
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x51
0x2000000001020020 5103A17000120300


Log Entry 2: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x1F
0x2000000001020030 1F81A37000120300


Log Entry 3: 00:00:11
Alert Level 2: Informational
Keyword: MP_SELFTEST_RESULT
Management Processor Firmware Selftest Result
Logged by: Management Processor 0
Data: Reset type and cause - Cold reset
0x5E800A7A00E00040 0000000000000000


Log Entry 4: 28 Mar 2011 01:40:16
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FE700020060 FFFF027000120300


Log Entry 5: 28 Mar 2011 01:40:16
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FE700020070 FFFF027000120300


Log Entry 6: 28 Mar 2011 01:40:21
Alert Level 2: Informational
Keyword: Type-02 056f00 356096
Chassis intrusion detected
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Intrus
Data1: General Chassis Intrusion
0x204D8FE705020080 FFFF006F01050300


Log Entry 7: 28 Mar 2011 01:40:21
Alert Level 3: Warning
Keyword: Type-02 050301 328449
The server's built-in sensors have detected an open chassis door.
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open
Data1: State Asserted
0x204D8FE705020090 FFFF010302050300


Log Entry 8: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1R (Power)
Data1: Performance Met
0x204D8FE7060200A0 FFFF0006E8040300


Log Entry 9: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1L (Power)
Data1: Performance Met
0x204D8FE7060200B0 FFFF0006E9040300


Log Entry 10: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU0 (R)
Data1: Performance Met
0x204D8FE7060200C0 FFFF0006EA040300


Log Entry 11: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU1 (L)
Data1: Performance Met
0x204D8FE7060200D0 FFFF0006EB040300


Log Entry 12: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2F (Memory)
Data1: Performance Met
0x204D8FE7060200E0 FFFF0006EC040300


Log Entry 13: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2B (Memory)
Data1: Performance Met
0x204D8FE7060200F0 FFFF0006ED040300


Log Entry 14: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3F (Disk)
Data1: Performance Met
0x204D8FE706020100 FFFF0006EE040300


Log Entry 15: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3B (Disk)
Data1: Performance Met
0x204D8FE706020110 FFFF0006EF040300


Log Entry 16: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 0
Data1: Device Inserted/Device Present
0x204D8FE706020120 FFFF0108F10D0300


Log Entry 17: 28 Mar 2011 01:40:22
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 1
Data1: Device Inserted/Device Present
0x204D8FE706020130 FFFF0108F20D0300


Log Entry 18: 28 Mar 2011 01:40:23
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: Baseboard Management Controller;
Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x204D8FE707020140 FFFF006FFA220300


Log Entry 19: 28 Mar 2011 01:40:23
Alert Level 2: Informational
Keyword: Type-02 c00301 12583681
Time set
Logged by: Baseboard Management Controller;
Sensor: SEL Time Set
Data1: State Asserted
0x204D8FE707020150 FFFF0103FDC00300


Log Entry 20: 28 Mar 2011 01:41:02
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x07
0x204D8FE72E020160 0783A37000120300


Log Entry 21: 28 Mar 2011 01:41:03
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FE72F020170 FFFF027000120300


Log Entry 22: 28 Mar 2011 01:41:03
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FE72F020180 FFFF027000120300


Log Entry 23: 28 Mar 2011 01:42:16
Alert Level 3: Warning
Keyword: Type-02 076f03 487171
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x204D8FE778020190 FFFF036F00070300


Log Entry 24: 28 Mar 2011 01:42:32
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x07
0x204D8FE7880201A0 0780A37000120300


Log Entry 25: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127001 1208321
BMC firmware initializing
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x51
0x20000000010201B0 5103A17000120300


Log Entry 26: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x1F
0x20000000010201C0 1F81A37000120300


Log Entry 27: 00:00:11
Alert Level 2: Informational
Keyword: MP_SELFTEST_RESULT
Management Processor Firmware Selftest Result
Logged by: Management Processor 0
Data: Reset type and cause - Cold reset
0x5E800A7A00E001D0 0000000000000000


Log Entry 28: 28 Mar 2011 02:03:19
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FEC670201F0 FFFF027000120300


Log Entry 29: 28 Mar 2011 02:03:19
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FEC67020200 FFFF027000120300


Log Entry 30: 28 Mar 2011 02:03:24
Alert Level 2: Informational
Keyword: Type-02 056f00 356096
Chassis intrusion detected
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Intrus
Data1: General Chassis Intrusion
0x204D8FEC6C020210 FFFF006F01050300


Log Entry 31: 28 Mar 2011 02:03:24
Alert Level 3: Warning
Keyword: Type-02 050301 328449
The server's built-in sensors have detected an open chassis door.
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open
Data1: State Asserted
0x204D8FEC6C020220 FFFF010302050300


Log Entry 32: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1R (Power)
Data1: Performance Met
0x204D8FEC6D020230 FFFF0006E8040300


Log Entry 33: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1L (Power)
Data1: Performance Met
0x204D8FEC6D020240 FFFF0006E9040300


Log Entry 34: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU0 (R)
Data1: Performance Met
0x204D8FEC6D020250 FFFF0006EA040300


Log Entry 35: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU1 (L)
Data1: Performance Met
0x204D8FEC6D020260 FFFF0006EB040300


Log Entry 36: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2F (Memory)
Data1: Performance Met
0x204D8FEC6D020270 FFFF0006EC040300


Log Entry 37: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2B (Memory)
Data1: Performance Met
0x204D8FEC6D020280 FFFF0006ED040300


Log Entry 38: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3F (Disk)
Data1: Performance Met
0x204D8FEC6D020290 FFFF0006EE040300


Log Entry 39: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3B (Disk)
Data1: Performance Met
0x204D8FEC6D0202A0 FFFF0006EF040300


Log Entry 40: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 0
Data1: Device Inserted/Device Present
0x204D8FEC6D0202B0 FFFF0108F10D0300


Log Entry 41: 28 Mar 2011 02:03:25
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 1
Data1: Device Inserted/Device Present
0x204D8FEC6D0202C0 FFFF0108F20D0300


Log Entry 42: 28 Mar 2011 02:03:26
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: Baseboard Management Controller;
Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x204D8FEC6E0202D0 FFFF006FFA220300


Log Entry 43: 28 Mar 2011 02:03:26
Alert Level 2: Informational
Keyword: Type-02 c00301 12583681
Time set
Logged by: Baseboard Management Controller;
Sensor: SEL Time Set
Data1: State Asserted
0x204D8FEC6E0202E0 FFFF0103FDC00300


Log Entry 44: 28 Mar 2011 02:05:19
Alert Level 3: Warning
Keyword: Type-02 076f03 487171
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x204D8FECDF0202F0 FFFF036F00070300


Log Entry 45: 28 Mar 2011 02:09:04
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x07
0x204D8FEDC0020300 0780A37000120300


Log Entry 46: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127001 1208321
BMC firmware initializing
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x51
0x2000000001020310 5103A17000120300


Log Entry 47: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x1F
0x2000000001020320 1F81A37000120300


Log Entry 48: 00:00:11
Alert Level 2: Informational
Keyword: MP_SELFTEST_RESULT
Management Processor Firmware Selftest Result
Logged by: Management Processor 0
Data: Reset type and cause - Cold reset
0x5E800A7A00E00330 0000000000000000


Log Entry 49: 28 Mar 2011 02:22:48
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF0F8020350 FFFF027000120300


Log Entry 50: 28 Mar 2011 02:22:48
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF0F8020360 FFFF027000120300


Log Entry 51: 28 Mar 2011 02:22:53
Alert Level 2: Informational
Keyword: Type-02 056f00 356096
Chassis intrusion detected
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Intrus
Data1: General Chassis Intrusion
0x204D8FF0FD020370 FFFF006F01050300


Log Entry 52: 28 Mar 2011 02:22:53
Alert Level 3: Warning
Keyword: Type-02 050301 328449
The server's built-in sensors have detected an open chassis door.
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open
Data1: State Asserted
0x204D8FF0FD020380 FFFF010302050300


Log Entry 53: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1R (Power)
Data1: Performance Met
0x204D8FF0FE020390 FFFF0006E8040300


Log Entry 54: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1L (Power)
Data1: Performance Met
0x204D8FF0FE0203A0 FFFF0006E9040300


Log Entry 55: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU0 (R)
Data1: Performance Met
0x204D8FF0FE0203B0 FFFF0006EA040300


Log Entry 56: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU1 (L)
Data1: Performance Met
0x204D8FF0FE0203C0 FFFF0006EB040300


Log Entry 57: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2F (Memory)
Data1: Performance Met
0x204D8FF0FE0203D0 FFFF0006EC040300


Log Entry 58: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2B (Memory)
Data1: Performance Met
0x204D8FF0FE0203E0 FFFF0006ED040300


Log Entry 59: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3F (Disk)
Data1: Performance Met
0x204D8FF0FE0203F0 FFFF0006EE040300


Log Entry 60: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3B (Disk)
Data1: Performance Met
0x204D8FF0FE020400 FFFF0006EF040300


Log Entry 61: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 0
Data1: Device Inserted/Device Present
0x204D8FF0FE020410 FFFF0108F10D0300


Log Entry 62: 28 Mar 2011 02:22:54
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 1
Data1: Device Inserted/Device Present
0x204D8FF0FE020420 FFFF0108F20D0300


Log Entry 63: 28 Mar 2011 02:22:55
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: Baseboard Management Controller;
Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x204D8FF0FF020430 FFFF006FFA220300


Log Entry 64: 28 Mar 2011 02:22:55
Alert Level 2: Informational
Keyword: Type-02 c00301 12583681
Time set
Logged by: Baseboard Management Controller;
Sensor: SEL Time Set
Data1: State Asserted
0x204D8FF0FF020440 FFFF0103FDC00300


Log Entry 65: 28 Mar 2011 02:24:48
Alert Level 3: Warning
Keyword: Type-02 076f03 487171
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x204D8FF170020450 FFFF036F00070300


Log Entry 66: 28 Mar 2011 02:25:25
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x07
0x204D8FF195020460 0780A37000120300


Log Entry 67: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127001 1208321
BMC firmware initializing
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x51
0x2000000001020470 5103A17000120300


Log Entry 68: 00:00:01
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x1F
0x2000000001020480 1F81A37000120300


Log Entry 69: 00:00:11
Alert Level 2: Informational
Keyword: MP_SELFTEST_RESULT
Management Processor Firmware Selftest Result
Logged by: Management Processor 0
Data: Reset type and cause - Cold reset
0x5E800A7A00E00490 0000000000000000


Log Entry 70: 28 Mar 2011 02:35:42
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF3FE0204B0 FFFF027000120300


Log Entry 71: 28 Mar 2011 02:35:42
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF3FE0204C0 FFFF027000120300


Log Entry 72: 28 Mar 2011 02:35:47
Alert Level 2: Informational
Keyword: Type-02 056f00 356096
Chassis intrusion detected
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Intrus
Data1: General Chassis Intrusion
0x204D8FF4030204D0 FFFF006F01050300


Log Entry 73: 28 Mar 2011 02:35:47
Alert Level 3: Warning
Keyword: Type-02 050301 328449
The server's built-in sensors have detected an open chassis door.
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open
Data1: State Asserted
0x204D8FF4030204E0 FFFF010302050300


Log Entry 74: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1R (Power)
Data1: Performance Met
0x204D8FF4040204F0 FFFF0006E8040300


Log Entry 75: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 1L (Power)
Data1: Performance Met
0x204D8FF404020500 FFFF0006E9040300


Log Entry 76: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU0 (R)
Data1: Performance Met
0x204D8FF404020510 FFFF0006EA040300


Log Entry 77: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan CPU1 (L)
Data1: Performance Met
0x204D8FF404020520 FFFF0006EB040300


Log Entry 78: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2F (Memory)
Data1: Performance Met
0x204D8FF404020530 FFFF0006EC040300


Log Entry 79: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 2B (Memory)
Data1: Performance Met
0x204D8FF404020540 FFFF0006ED040300


Log Entry 80: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3F (Disk)
Data1: Performance Met
0x204D8FF404020550 FFFF0006EE040300


Log Entry 81: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 040600 263680
Fan performance OK
Logged by: Baseboard Management Controller;
Sensor: Fan - Fan 3B (Disk)
Data1: Performance Met
0x204D8FF404020560 FFFF0006EF040300


Log Entry 82: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 0
Data1: Device Inserted/Device Present
0x204D8FF404020570 FFFF0108F10D0300


Log Entry 83: 28 Mar 2011 02:35:48
Alert Level 2: Informational
Keyword: Type-02 0d0801 854017
Hot swap Cage: Drive inserted
Logged by: Baseboard Management Controller;
Sensor: Drive Slot (Bay) - SCSI Device 1
Data1: Device Inserted/Device Present
0x204D8FF404020580 FFFF0108F20D0300


Log Entry 84: 28 Mar 2011 02:35:49
Alert Level 2: Informational
Keyword: Type-02 226f00 2256640
ACPI state S0 (on)
Logged by: Baseboard Management Controller;
Sensor: System ACPI Power State - ACPI State
Data1: S0/G0 working
0x204D8FF405020590 FFFF006FFA220300


Log Entry 85: 28 Mar 2011 02:35:49
Alert Level 2: Informational
Keyword: Type-02 c00301 12583681
Time set
Logged by: Baseboard Management Controller;
Sensor: SEL Time Set
Data1: State Asserted
0x204D8FF4050205A0 FFFF0103FDC00300


Log Entry 86: 28 Mar 2011 02:35:49
Alert Level 2: Informational
Keyword: Type-02 058301 361217
Chassis door closed
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open
Data1: State Asserted (Deassertion)
0x204D8FF4050205B0 FFFF018302050300


Log Entry 87: 28 Mar 2011 02:36:21
Alert Level 2: Informational
Keyword: Type-02 127003 1208323
Chassis Control request to BMC via IPMI or sensor
Logged by: Baseboard Management Controller;
Sensor: System Event
Data2: OEM Code2: 0x07
0x204D8FF4250205C0 0783A37000120300


Log Entry 88: 28 Mar 2011 02:36:21
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF4250205D0 FFFF027000120300


Log Entry 89: 28 Mar 2011 02:36:21
Alert Level 2: Informational
Keyword: Type-02 127002 1208322
Soft Reset
Logged by: Baseboard Management Controller;
Sensor: System Event
0x204D8FF4250205E0 FFFF027000120300

AND i find this

Log Entry 305: 30 Mar 2011 03:37:04
Alert Level 7: Fatal
Keyword: PDC_BMC_BT_INTERFACE_FAIL
There is a failure with communications between PDC and the BMC's BT interface
Logged by: System Firmware 0
Data: Data field unused
0xE08012FC00E013E0 FFFFFFFFFFFFFFE8

the system can not pass test itself ,can not start
george_hoo
11 REPLIES 11
Torsten.
Acclaimed Contributor

Re: rp3440 can not boot normal ,with some error

From a quick view on your logs I found

The server's built-in sensors have detected an open chassis door.
Logged by: Baseboard Management Controller;
Sensor: Physical Security - Chassis Open





With an open chassis the server will power off after several minutes to prevent overheating.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
хР┤шГЬщФж
Occasional Advisor

Re: rp3440 can not boot normal ,with some error

can you help me check this txt ?

and there is the error like this

Log Entry 23: 28 Mar 2011 01:42:16
Alert Level 3: Warning
Keyword: Type-02 076f03 487171
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x204D8FE778020190 FFFF036F00070300
george_hoo
хР┤шГЬщФж
Occasional Advisor

Re: rp3440 can not boot normal ,with some error

i think

Sensor: Physical Security - Chassis Open

error like this can ignore

george_hoo
Torsten.
Acclaimed Contributor

Re: rp3440 can not boot normal ,with some error

Looks like there is no activity on the CPU - could be a bad CPU or even system board.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
хР┤шГЬщФж
Occasional Advisor

Re: rp3440 can not boot normal ,with some error

yes i think so .
so today i replaced the CPU ,but it does't work .
And i will replace the system board . i hope it will work tomorrow.
george_hoo
хР┤шГЬщФж
Occasional Advisor

Re: rp3440 can not boot normal ,with some error

i have another question , if i unplug the boot disks from the RP3440 (which can not boot normal) and insert into another rp3440 ,can this rp3440 boot normally ? (by the way ,i think the boot disk is good )
george_hoo
Andrew Rutter
Honored Contributor

Re: rp3440 can not boot normal ,with some error

hi,

yes you could take the boot disks out of one server and place them in the same slots of another rp3440 and it will boot up ok.

or will if its cabled up the same internally?

if there at the defaults it will be fine.

I have a rp3440 disk and use it in many servers as a quick test. You just have to keep the disks in the correct/same slots

Andy
hvhari
Esteemed Contributor

Re: rp3440 can not boot normal ,with some error

yes, you can boot another system with the same disk, by setting the bootpath in PDC (if it is set as some thing different from current system)
Regards,
Hari

If this post was useful , click the Kudos Star on the left side to say Thanks!
Bill Hassell
Honored Contributor
Solution

Re: rp3440 can not boot normal ,with some error

> can this rp3440 boot normally

It will probably boot up if the disks are placed in the same slots of the new rp3440. However, all your I/O cards may be a problem if they do not match. HP-UX remembers where the I/O cards were located and on a new server, the LAN cards, SCSI cards, fibre cards may be in different locations or be different models. The best solution is to move all the I/O cards to the new system -- put them in the same slots and it should boot normally. Of course you'll need to move any I/O cables to the new machine.


Bill Hassell, sysadmin