Chassis Hardware Monitor (Events)

Event 1

Severity: INFORMATION

Event Summary: Error chassis code or non-urgent operator attention required.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN2NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 2

Severity: MINORWARNING

Event Class: System

Event Summary: System blocked waiting for operator input.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN3NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 3

Severity: MINORWARNING

Event Class: System

Event Summary: Unexpected configuration change detected.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN4NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 4

Severity: MINORWARNING

Event Class: System

Event Summary: Boot possible, environmental problem exists.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN5NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 5

Severity: MAJORWARNING

Event Class: System

Event Summary: Boot possible pending failure - action required (e.g. boot disk error rate above threshold, power failure, overtemp medium).

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN6NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 6

Severity: CRITICAL

Event Class: System

Event Summary: HPMC detected.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN7NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 7

Severity: MINORWARNING

Event Class: System

Event Summary: Boot possible, performance impaired.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN8NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 8

Severity: MINORWARNING

Event Class: System

Event Summary: Undefined alert level for this chassis code.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNN9NNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 9

Severity: SERIOUS

Event Class: System

Event Summary: Boot possible, functionality lost.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNaNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 10

Severity: MINORWARNING

Event Class: System

Event Summary: Undefined alert level for this chassis code.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNbNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 11

Severity: SERIOUS

Event Class: System

Event Summary: Software failure.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNcNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 12

Severity: CRITICAL

Event Class: System

Event Summary: System hang detected via timer popping.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNdNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 13

Severity: CRITICAL

Event Class: System

Event Summary: Fatal power or environmental problem prevents operation.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNeNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 14

Severity: CRITICAL

Event Class: System

Event Summary: Fatal hardware or configuration problem prevents operation.

Problem Description: The first encoded field of this chassis log was not found in the internal chassis code table. Therefore, no description text is available for this chassis log. Please check http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm to search by the chassis code.

Probable Cause / Recommended Action: The first encoded field (0xNNNNNNfNNNNNNNNN) of this chassis log was not found in the internal chassis code table. This chassis code may have been added since the monitor was last changed. Possible ways to decode this chassis code:

Load a more current version of the OnlineDiag software depot (Support Tools). Installing this depot automatically installs the EMS hardware monitors (if you have modified the default settings, additional configuration may be required.) Almost all chassis codes for a computer system should be supported in the dm_chassis monitor in the first diagnostic release that appears after the computer system has been released. The EML monitor release notes for the diagnostic release may have more information.

Contact HP support. They may have access to a more current set of chassis codes, for example, through a chassis code decoder program.

Note: N means a digit 0 to 9.

Event 200

Severity: MAJORWARNING

Event Summary: The chassis code logging daemon (cclogd) is not currently running.

Event Class: System

Problem Description: The chassis code logging daemon supplies all the chassis logs monitored by dm_chassis. Cclogd must be running for dm_chassis to get the system chassis codes.

Probable Cause / Recommended Action: This chassis code logging daemon has been shut-down. To re-start cclogd, run cstm as root. If diagmond is not running, issue the command cstm>stmstartup. If diagmond is running, issue the command cstm>daemonstartup. From the list, select "cclogd".

Event 1000

Severity: SERIOUS

Event Summary: XBC to XBC link not viable.

Event Class: System

Problem Description: Chassis Code Keyword FABRIC_XBC_2_XBC_ERR. The link between two XBCs has failed and is not a viable link. Data Field: 1st XBC # << 32 | 2nd XBC # (link that failed is between this two XBCs)

Probable Cause / Recommended Action: XBC to XBC link not operational. Reset the cell. Reset the system backplane. Contact HP Support personnel to troubleshoot the problem.

Event Details:
Chassis Code Encoded Field : 0x180008f051002fef
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 5 (fabric connector)
   Source FRU Detail       : 1 (cross bar)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (config)
   Caller Subactivity      : 254 (implementation dependent)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000010
Event 1001

Severity: SERIOUS

Event Summary: Power Up Aborted, Over Temp.

Event Class: System

Problem Description:
Chassis Code Keyword ABORT_POWERUP_OTH.

The Cabinet Power Up request was aborted due to ambient air over temperature.

Probable Cause / Recommended Action:

Cause:

Computer Room over temp

Action:

Cool Computer Room

Cause:

Environment immediately surrounding cabinet.

Action:

Correct local environmental problem

Cause:

Reporting Error

Action:

Troubleshoot ambient air sensor/cable/PM3.

Event Details:
Chassis Code Encoded Field : 0x002008e16100302f
   Alert Level             : 14 (Fatal power or environmental problem prevents
   operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (inlet overtemp)
   Caller Activity         : 3 (power on/off)
   Caller Subactivity      : 2 (high voltage power supply)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1002

Severity: CRITICAL

Event Summary: Too Few Bulk Power Supplies Available.

Event Class: System

Problem Description:
Chassis Code Keyword ABORT_PWRUP_BPS.

The power requirements for the cabinet exceeds the capabilities of the available Bulk Power Supplies. The PM3 section of the Utilities Subsystems keeps a tally of the power requirements for all installed entities in a cabinet. The power available from the Bulk Power Supplies does not meet the requirements of the installed entities, according to the Cabinet Power Tally.

Probable Cause / Recommended Action:

Cause:

One or more Bulk Power Supplies are missing or in fault condition at Cabinet Power Up.

Action:

Contact your HP support representative to check for faulty Bulk Power Supplies Add Bulk Power Supplies, if under populated.

Cause:

Too many entities installed in the cabinet for the Power Available.

Action:

Remove entities until Power Requirements are met. Add Bulk Power Supplies, if under populated.

Event Details:
Chassis Code Encoded Field : 0x002008ee44ff302f
   Alert Level             : 14 (Fatal power or environmental problem prevents
   operation.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 255 (platform dependent)
   Event Detail            : 14 (power overloaded)
   Caller Activity         : 3 (power on/off)
   Caller Subactivity      : 2 (high voltage power supply)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1003

Severity: CRITICAL

Event Summary: No Cabinet Start, Insufficient Blowers.

Event Class: System

Problem Description:
Chassis Code Keyword ABORT_START_BLOWR.

When given a power up request, the cabinet had to abort the start up due to less than the required number of Cabinet Blowers installed.

Probable Cause / Recommended Action:

Cause:

The number of blowers required is a hard number. It is not dependent upon the number of entities installed in a Cabinet. The Utilities Subsystem is not allowing the Cabinet to power up due to an insufficient number of installed blowers.

Action:

Install missing Cabinet Blowers. If proper number of blowers are installed, troubleshoot blower presence detection.

Event Details:
Chassis Code Encoded Field : 0x002008e663ff302f
   Alert Level             : 14 (Fatal power or environmental problem prevents
   operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 3 (cabinet fan)
   Source ID               : 255 (platform dependent)
   Event Detail            : 6 (insufficient number of fans)
   Caller Activity         : 3 (power on/off)
   Caller Subactivity      : 2 (high voltage power supply)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1004

Severity: CRITICAL

Event Summary: No Cabinet Start, Insufficient IO Fans.

Event Class: System

Problem Description:
Chassis Code Keyword ABORT_START_IOFAN.

When given a power up request, the cabinet had to abort the start up due to less than the required number of IO fans present.

Probable Cause / Recommended Action:

Cause:

The number of IO fans required is a hard number. It is not dependent upon the number of entities installed in a Cabinet. The Utilities Subsystem is not allowing the cabinet to power up due to an insufficient number of installed IO fans.

Action:

Install missing IO fans, or if proper number installed, troubleshoot IO fan presence detection.

Event Details:
Chassis Code Encoded Field : 0x002008e664ff302f
   Alert Level             : 14 (Fatal power or environmental problem prevents
   operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 4 (card cage fan)
   Source ID               : 255 (platform dependent)
   Event Detail            : 6 (insufficient number of fans)
   Caller Activity         : 3 (power on/off)
   Caller Subactivity      : 2 (high voltage power supply)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1005
Severity: MINORWARNING

Event Summary: AC power to the PDCA was detected.

Event Class: System
Problem Description:
Chassis Code Keyword AC_ADDED.

The AC power connected to the PDCA (Power Distribution Control Assembly) was added. The data field contains the physical location of the PDCA.

The PDCA can also be identified by the activity status (last byte of chassis code):
        e = PDCA 1
        f = PDCA 0
Probable Cause / Recommended Action:

Cause:

AC power was restored.

Action:

None.

Cause:

AC detection and monitoring circuitry was repaired or replaced.

Action:

None.

Cause:

PDCA was replaced.

Action:

None
Event Details:
Chassis Code Encoded Field : 0x242008484100401e
   Alert Level             : 4 (Unexpected configuration change detected.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 1 (AC mains)
   Source ID               : 0 (platform dependent)
   Event Detail            : 8 (power on)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 1 (AC main)
   Activity Status         : 14 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000015
   FRU Source          = 1 (processor)
   Source Detail       = 5 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1006
Severity: MAJORWARNING

Event Summary: AC power to the PDCA was removed.

Event Class: System
Problem Description:
Chassis Code Keyword AC_DELETED.

The AC power connected to the PDCA (Power Distribution Control Assembly) was removed. The data field contains the physical location of the PDCA.

The PDCA can also be identified by the activity status (last byte of chassis code):
        e = PDCA 1
        f = PDCA 0
Probable Cause / Recommended Action:

Cause:

Circuit breakers on the PDCA are open.

Action:

Close the PDCA circuit breakers.

Cause:

Power source supplying AC to the PDCA has failed.

Action:

Troubleshoot AC power problem.

Cause:

PDCA (Power Distribution Control Assembly) has failed.

Action:

Replace the PDCA with proper type (4-wire or 5-wire) PDCA following power distribution control assembly Remove and Replace procedures.

Cause:

AC Detection and monitoring circuitry failed.

Action:

Troubleshoot and replace failed Field Replaceable Units.
Event Details:
Chassis Code Encoded Field : 0x242008694100401e
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 1 (AC mains)
   Source ID               : 0 (platform dependent)
   Event Detail            : 9 (power off)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 1 (AC main)
   Activity Status         : 14 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000016
   FRU Source          = 1 (processor)
   Source Detail       = 6 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1009

Severity: INFORMATION

Event Summary: Blower Speed Normal.

Event Class: System

Problem Description:
Chassis Code Keyword BLOWER_SPEED_CHG.

The Cabinet Blower speed changed from normal to high.

Probable Cause / Recommended Action:

Cause:

Existing condition causing high blower speed was corrected.

Action:

None

Event Details:
Chassis Code Encoded Field : 0x0420081363002000
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 3 (cabinet fan)
   Source ID               : 0 (platform dependent)
   Event Detail            : 3 (speed change)
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 0 (unspecified)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1010

Severity: MAJORWARNING

Event Summary: Blower Speed High.

Event Class: System

Problem Description:
Chassis Code Keyword BLOWER_SPEED_CHG.

The Cabinet Blower speed changed from normal to high.

Probable Cause / Recommended Action:

Cause:

Front EMI shield was removed. Should see Door_Open chassis code.

Action:

Replace front EMI shield as soon as possible.

Cause:

A Cabinet Blower has failed or been removed leaving 3 (N) functioning blowers.

Action:

Replace failed or missing blower, bringing count to N+1. (4)

Cause:

An IO Fan has failed or been removed leaving 4 (N) functioning IO Fans.

Action:

Replaced failed or missing IO Fan, bringing count to N+1. (5)

Cause:

Ambient Air Over Temperature condition.

Action:

Lower computer room temperature.

Cause:

An installed cell did not report its required fan speed, probably GSP bus problem.

Action:

Use Guardian Service Processor command "DU" to detect any cells known to be installed and not showing in USB topology. Check CELL PDH CONTROLLER LED's on cell boards front edge. LED #1, the one next to the blinking LED, should be on. If not, the USB interface on the cell is down. Replace cell if it is the only one, replace HUB if all are affected.

Event Details:
Chassis Code Encoded Field : 0x042008236300200f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 3 (cabinet fan)
   Source ID               : 0 (platform dependent)
   Event Detail            : 3 (speed change)
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 0 (unspecified)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 2 (power monitor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)  
Event 1013

Severity: CRITICAL

Event Summary: PDC failed to read the cabinet type for another cell in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_CABINET_TYPE_ERR.

PDC attempts to make sure that all of the cells in a partition are installed in the same type of cabinet. PDC failed to read the cabinet type for another cell. Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell reporting the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2004061
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x000000000000001d
   FRU Source          = 1 (processor)
   Source Detail       = 13 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1014

Severity: CRITICAL

Event Summary: PDC failed to read the CPU HVERSION for another cell in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_CPU_HV_ERR.

PDC attempts to insure that all of the CPUs in the partition have the same HVERSION. PDC failed to read the CPU HVERSION for another cell in the partition. Once a cell has rendezvoused with a PD, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell detected the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2004063
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 3 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x000000000000001e
   FRU Source          = 1 (processor)
   Source Detail       = 14 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1015

Severity: CRITICAL

Event Summary: PDC failed to read the CPU ID for another cell in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_CPU_ID_ERR.

PDC attempts to insure that all of the cells in the partition have CPUs with the same CPU ID. There was a failure attempting to read the CPU ID for another cell in the PD. Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell detecting the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2004062
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 2 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x000000000000001f
   FRU Source          = 1 (processor)
   Source Detail       = 15 (firmware)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1016

Severity: CRITICAL

Event Summary: PDC failed to read the CPU speeds for another cell in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_CPU_SPEED_ERR.

PDC attempts to make sure that all of the CPUs in the partition run at the same speed. This chassis code is sent when PDC is unable to perform this check Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell detecting the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2004064
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000020
   FRU Source          = 2 (processor cache)
   Source Detail       = 0 (unknown, no source stated)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1017

Severity: CRITICAL

Event Summary: Could not access local rendezvous set data in cell previously accessed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_LOCAL_RENDEZ_SET_ERR.

All of the cells create a set of cells that they could rendezvous with. This cell tried to read that set on another cell and failed. Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This may indicate that there is an intermittent problem with the fabric. There is a problem with a corrupted data structure in the Penumbra data structures stored in scratch RAM.

Action:

Look for intermittent problems in the fabric. Make sure PDC tests are enabled during the cell's boot so that they test scratch RAM. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000f0a200c025
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 12 (slave rendezvous)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000021
Event 1018

Severity: CRITICAL

Event Summary: Unable to access the PDC version info on cell in rendezvous set.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_PDC_VERSION_ERR.

PDC checks to insure that all of the cells have the same version of PDC. PDC failed accessing the PDC version on another cell. Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell detecting the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2004060
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000022
   FRU Source          = 2 (processor cache)
   Source Detail       = 2 (I cache L1)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1019

Severity: CRITICAL

Event Summary: When walking the fabric, the cell was unable to reach itself.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACCESS_RENDEZ_SET_ERR.

When walking the fabric, the cell was unable to reach itself.

The cell was reset for reconfiguration and will not join the partition on this boot. Once a cell has rendezvoused with a partition, there is no way to unrendezvous it. Therefore PDC resets all of the cells in the partition when this error is detected.

The data field contains the physical location of the cell that detected the event.

Probable Cause / Recommended Action:

Cause:

PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the fabric.

Action:

Look for intermittent problems in the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a200c024
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 12 (slave rendezvous)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000023
   FRU Source          = 2 (processor cache)
   Source Detail       = 3 (I cache L2)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1020

Severity: MAJORWARNING

Event Summary: Wrong bit written to EIR when attempting to wake up a slave processor.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ACTIVE_STRAY_EIR_BITS_SET.

In an attempt to wake up a slave processor, wrong bit was written to the External Interrupt Register.

The data field contains the contents of the EIR. Execution continues, but could be evidence of software problem.

Probable Cause / Recommended Action:

Cause:

Indicates a software problem, could be bad PDC, but is more likely a program launched from ISL.

Action:

Report event to Response Center. Update diagnostics. Update PDC.

Event Details:
Chassis Code Encoded Field : 0x180000c0a20000e0
   Alert Level             : 12 (Software failure.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 14 (implementation dependent)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000024
Event 1021

Severity: INFORMATION

Event Summary: A slave is shooting the monarch.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ASSASSINATION.

A slave CPU was not woken up from a rendezvous in the expected amount of time and figures that the monarch is probably not healthy anymore. The slave will compete with other slaves that want to shoot the monarch, one slave will deconfigure the monarch, mark the monarch as failed (used during next boot), and then reset the cell.

Probable Cause / Recommended Action:

Cause:

Bad timeout values defined by PDC. Defective CC that is not allowing CPUs to execute code at a normal speed Defective CPU that has either starting executing code slowly or stopped executing code altogether.

Action:

Contact HP Support Personnel to troubleshoot the CPU and cell board. Update PDC.

Event Details:
Chassis Code Encoded Field : 0x000000219f004022
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 2 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1022

Severity: MINORWARNING

Event Summary: CPU returned to PDC control in incorrect PST state.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_CPU_PST_STATE.

On return to BCH from ISL, PDC detected that a CPU was not in an allowed PST_STATE.

The data field contains the invalid state.

The system will reboot.

Probable Cause / Recommended Action:

Cause:

ISL or diagnostic program has left CPU in an incorrect state.

Action:

Reboot. If problem persists, report event to the Response Center to contact firmware team and the appropriate owner of program that left CPUs in wrong state.

Event Details:
Chassis Code Encoded Field : 0x180000c0a5001031
   Alert Level             : 12 (Software failure.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 3 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000026
Event 1023

Severity: MAJORWARNING

Event Summary: Boot failed because the IPL address was either zero or not 2K aligned.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_IPL_ADDR.

IPL address is the byte offset from the start of the device to the program IPL. This chassis code comes out when a boot fails because the IPL address was either zero or not 2K aligned.

Probable Cause / Recommended Action:

Cause:

Bad LIF image.

Action:

Replace LIF image.

Event Details:
Chassis Code Encoded Field : 0x00000030a5001010
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1024

Severity: MAJORWARNING

Event Summary: Boot failed because the LIF image's checksum was invalid.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_IPL_CHECKSUM.

Boot failed because the LIF image's checksum was invalid. The system should return to BCH.

Probable Cause / Recommended Action:

Cause:

Bad LIF image.

Action:

Replace LIF image.

Event Details:
Chassis Code Encoded Field : 0x00000030a5001011
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
 
Event 1025

Severity: MAJORWARNING

Event Summary: Boot failed because IPL ENTRY offset was invalid.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_IPL_ENTRY.

IPL ENTRY is the offset into the IPL program where execution starts. A chassis codes is emitted when a boot fails because this offset is not less than the size of the IPL image or is not word aligned.

Probable Cause / Recommended Action:

Cause:

Bad LIF image.

Action:

Replace LIF image.

Event Details:
Chassis Code Encoded Field : 0x00000030a5001012
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 2 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1026

Severity: MAJORWARNING

Event Summary: Boot failed because size of IPL was invalid.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_IPL_SIZE.

IPL size is the total size (in bytes) of the IPL program. This chassis code is emitted on a failed boot due to IPL size being zero, not 2K aligned, or greater than 256 K.

Probable Cause / Recommended Action:

Cause:

Bad LIF image.

Action:

Replace LIF image.

Event Details:
Chassis Code Encoded Field : 0x00000030a5001013
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 3 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1027

Severity: MAJORWARNING

Event Summary: Boot failed - LIF image had an invalid value for magic number.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BAD_LIF_MAGIC.

Boot failed because LIF image had an invalid value for the HP-architected magic number. System should return to BCH.

Probable Cause / Recommended Action:

Cause:

Disk did not have valid HP LIF image

Action:

Check for valid LIF image, replace if bad.

Event Details:
Chassis Code Encoded Field : 0x00000030a5001014
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1028

Severity: MAJORWARNING

Event Summary: A failed monarch CPU is being deconfigured by a slave CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BOOT_ABDICATION.

A failed monarch CPU is being deconfigured by a slave CPU. The slave CPU number is in the reporting entity ID field and the monarch CPU number is in the data field. See the BOOT_CPU_DECONFIG chassis code following this for the physical location of the deconfigured CPU.

Probable Cause / Recommended Action:

Cause:

Defective CPU.

Action:

Contact HP Support Personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000219f004021
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000002c
Event 1029

Severity: INFORMATION

Event Summary: PDC is finished booting.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BOOT_COMPLETE.

This chassis code is sent immediately before the point where PDC branches to ISL. It is the last chassis code sent by the monarch CPU in the core cell before ISL runs and tells the system utilities that ISL is now running in the partition.

Probable Cause / Recommended Action:

Cause:

Forward progress

Action:

None

Event Details:
Chassis Code Encoded Field : 0xa0000010af000065
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 15 (unknown)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 20 (major changes in system state)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000002d
   System State            : 13 (unknown)
   LED Run                 : 2 (steady green)
   LED Attention           : 0 (unknown)
   LED Stopped             : 0 (off (default))
Event 1030

Severity: INFORMATION

Event Summary: The boot process for the partition is beginning.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_BOOT_START.

This is a forward progress marker which indicates the beginning of the PDC boot process. Note: Prior to this chassis code being sent the early CPU init, monarch selection and ICM init have been done.

Probable Cause / Recommended Action:

Cause:

Forward progress

Action:

None

Event Details:
Chassis Code Encoded Field : 0xa00000109f000011
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 20 (major changes in system state)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000002e
   System State            : 14 (unknown)
   LED Run                 : 2 (steady green)
   LED Attention           : 0 (unknown)
   LED Stopped             : 0 (off (default))
Event 1031

Severity: MAJORWARNING

Event Summary: The PDC ROM has a checksum error.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ROM_XSUM_ERR.

The PDC ROM has a checksum error. This could be caused by a defective PDH, errors when loading the image from the GSP or a bit error in the image. The cell is halted.

Probable Cause / Recommended Action:

Cause:

A bit error in the PDC ROM image. Error loading the PDC ROM image from GSP

Action:

Use FWUU to reload PDC Contact HP Support personnel to troubleshoot the cell board, GSP and USB cable

Event Details:
Chassis Code Encoded Field : 0x200000f09f00111f
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 17 (implementation dependent)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x000000000000002f
   FRU Source          = 2 (processor cache)
   Source Detail       = 15 (firmware)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   CPU Slot Number     = 0
   Memory Slot Number  = 0
Event 1032

Severity: SERIOUS

Event Summary: PDC was unable to open the Chassis Code In FIFO.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CCI_FIFO_FAILURE.

PDC failed trying to open the chassis code in (CCI) FIFO on the core cell. The utilities system reflects chassis codes to the core cell in each PD.

Probable Cause / Recommended Action:

Cause:

PDC could not access the CCI on the core cell. There was a problem with semaphores on the core cell.

Action:

Try another cell as the core cell. Contact HP Sdupport personnel to troubleshoot the core cell. Update PDC.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a20020b5
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 11 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)
Event 1033

Severity: MAJORWARNING

Event Summary: At rendezvous, a cell is found to be incompatible with the core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_IS_INCOMPATIBLE.

At rendezvous, a cell is found to be incompatible with the core cell. Data field contains physical location of the incompatible cell. This chassis code should be immediately preceded by a chassis code explaining the specific incompatibility, (e.g. BOOT_INCOMPATIBLE_CPU_ID)

Probable Cause / Recommended Action:

Cause:

Cell is incompatible with core cell.

Action:

See the preceding chassis code in the log for specific incompatibility and proper action.

Event Details:
Chassis Code Encoded Field : 0x200000a0a200406f
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000031
   FRU Source          = 3 (PDH)
   Source Detail       = 1 (Semaphore Registers)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
Event 1034

Severity: CRITICAL

Event Summary: Failed to program the partition set into the CC. Partition not created.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_LOCAL_PD_SET_ERR.

PDC could not program the CC to recognize which cells are in the partition.

Probable Cause / Recommended Action:

Cause:

There was a problem with the CC or the cell board.

Action:

Contact HP Support personnel to troubleshoot the CC and the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000f0a2002054
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000032
Event 1035

Severity: SERIOUS

Event Summary: Cell did not rendezvous with the rest of the cells in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_MISSED_THE_BOAT.

A cell that is booting checks to determine if the other cells in the partition are ready to rendezvous with it. If the other cells in the partition have already rendezvoused, the cell cannot join the partition. PDC accommodates a relatively large skew between cells, but will eventually give up waiting on a cell.

Probable Cause / Recommended Action:

Cause:

The cell booted too slowly. It either started booting too late or has some problem that caused it to boot slowly.

Action:

Reboot the partition from the GSP and see if the cell is able to make it into the partition. If the cell is still too slow, look for the problems on the cell that cause it to boot slowly.

Event Details:
Chassis Code Encoded Field : 0x200000f0a200c002
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 12 (slave rendezvous)
   Caller Subactivity      : 0 (implementation dependent)
   Activity Status         : 2 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000033
   FRU Source          = 3 (PDH)
   Source Detail       = 3 (scratch RAM)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
Event 1036

Severity: INFORMATION

Event Summary: Physical location of the cell from BOOT_CELL_STATE_ERROR_STATUS.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_STATE_ERROR_LOCATION.

The data field holds the physical location of the problem cell from BOOT_CELL_STATE_ERROR_STATUS.

Probable Cause / Recommended Action:

Cause:

There is a fabric problem.

Action:

Check fabric and CC.

Event Details:
Chassis Code Encoded Field : 0x200000a0a200c001
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 12 (slave rendezvous)
   Caller Subactivity      : 0 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000034
   FRU Source          = 3 (PDH)
   Source Detail       = 4 (NVM)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
Event 1037

Severity: SERIOUS

Event Summary: PDC could not read the cell state on another cell in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_STATE_ERROR_STATUS.

PDC timed out attempting to access another cell's state.

The data field contains the cell state that was read.

Probable Cause / Recommended Action:

Cause:

There is a fabric problem.

Action:

Check fabric and CC.

Event Details:
Chassis Code Encoded Field : 0xb80000a0a200c001
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 12 (slave rendezvous)
   Caller Subactivity      : 0 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1038

Severity: MAJORWARNING

Event Summary: Wrong bit written to EIR when attempting to wake up a slave processor.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_STRAY_EIR_BITS_SET.

In an attempt to wake up a slave processor, wrong bit was written to the External Interrupt Register.

The data field contains the contents of the EIR. Execution continues, but could be evidence of software problem.

Probable Cause / Recommended Action:

Cause:

Indicates a software problem.

Action:

Report event to the Response Center. Update PDC.

Event Details:
Chassis Code Encoded Field : 0x180000c0a20000e1
   Alert Level             : 12 (Software failure.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 14 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000036
Event 1039

Severity: INFORMATION

Event Summary: Cell is halting.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELL_WILL_HALT.

Cell is halting

Probable Cause / Recommended Action:

Cause:

Cell is being halted

Action:

Review other chassis codes to determine reason the cell was halted.

Event Details:
Chassis Code Encoded Field : 0x200000009000001a
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 1 (implementation dependent)
   Activity Status         : 10 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000037
   FRU Source          = 3 (PDH)
   Source Detail       = 7 (configuration space)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
Event 1040

Severity: CRITICAL

Event Summary: Cells in the partition have different Stable Complex Data sequence IDs.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_A_SEQ_ID_MISMATCH.

PDC checks the sequence ID of the Stable Complex Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. Since the complex profiles are used to assign resources to a partition, PDC, at this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Stable Complex Data for the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004083
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 8 (implementation dependent)
   Activity Status         : 3 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000038
Event 1041

Severity: CRITICAL

Event Summary: Cells in the partition have different Stable Complex Data checksums.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_A_XSUM_MISMATCH.

PDC checks the sequence ID of the Stable Complex Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. Since the complex profiles are used to assign resources to a partition, PDC, at this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cells bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Stable Complex Data for the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004083
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 8 (implementation dependent)
   Activity Status         : 3 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000038
Event 1042

Severity: CRITICAL

Event Summary: Cells in partition have different Dynamic Complex Data sequence IDs.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_B_SEQ_ID_MISMATCH.

PDC checks the sequence ID of the Dynamic Complex Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cells bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Dynamic Complex Data for the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in the system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004084
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 8 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003a
Event 1043

Severity: CRITICAL

Event Summary: Cells in the partition have different Dynamic Complex Data checksums.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_B_XSUM_MISMATCH.

PDC checks the checksum of the Dynamic Complex Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cells bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Dynamic Complex Data for the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in the system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004074
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 7 (implementation dependent)
   Activity Status         : 4 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003b
Event 1044

Severity: CRITICAL

Event Summary: Cells in partition have different Partition Config Data sequence IDs.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_C_SEQ_ID_MISMATCH.

PDC checks the sequence ID of the Partition Configuration Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cells bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Partition Configuration Data for all of the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in the system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004085
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 8 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003c
Event 1045

Severity: CRITICAL

Event Summary: Cells in the partition have different Partition Config Data checksums.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CELLS_C_XSUM_MISMATCH.

PDC checks the checksum of the Partition Configuration Data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct.

The partition cannot be booted until this problem is resolved.

This chassis code indicates all of the cells that have complex profiles that do not match the core cell's.

The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cells bit indicated that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The Partition Configuration Data for all of the cells in the partition do not match.

Action:

Try to push out a new complex profile. Check for failures in the system utilities. As a last resort, try pushing out a genesis complex profile.

Event Details:
Chassis Code Encoded Field : 0x180000f060004075
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 7 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003d
Event 1046
Severity: MAJORWARNING

Event Summary: Clock generation chips on the cell board have different frequencies.

Event Class: System
Problem Description:
Chassis Code Keyword BOOT_CGC_SETTINGS_DIFFER.

There are two clock generation chips (CGC) on the cell board. Each provides clocks to two CPUs and must run at the same frequency. The two clock generation chips on the cell board are running at different frequencies.

The cell will be halted.

The data field indicates which CGC varied for the CGC that was driving the monarch CPU.
         1 - CGC for CPU 0 and 1
         2 - CGC for CPU 2 and 3
Probable Cause / Recommended Action:

Cause:

Defective / incorrect clock generation chip.

Action:

Contact HP Support personnel to troubleshoot the cell board
Event Details:
Chassis Code Encoded Field : 0x180000f09f0010c2
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 12 (implementation dependent)
   Activity Status         : 2 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003e
Event 1047

Severity: MAJORWARNING

Event Summary: The clock generator chip found on the cell board is unsupported.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CGC_TYPE_UNSUPPORTED.

The type of clock generator chip (CGC) found on the cell board is unsupported. The CPU Speed will be set to slowest default.

Probable Cause / Recommended Action:

Cause:

Incorrect CGC on the cell board Processor dependent hardware (PDH) was programmed incorrectly.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000809f0020c1
   Alert Level             : 8 (Boot possible, performance impaired.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 12 (implementation dependent)
   Activity Status         : 1 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000003f
Event 1048

Severity: CRITICAL

Event Summary: Unable to access core I/O data on another cell that in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CHECK_FOR_CORE_IO_FAIL.

PDC was unable to access data on another cell that rendezvoused with the partition. This data contains information about whether or not the cell has core I/O and is used to determine if the cell is a viable core cell.

Probable Cause / Recommended Action:

Cause:

This should not happen. Check for intermittent problems with the fabric.

Action:

Look for problems with the fabric.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2002050
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (implementation dependent)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000040
   FRU Source          = 4 (power entity)
   Source Detail       = 0 (unknown, no source stated)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1049

Severity: CRITICAL

Event Summary: Unable to determine if a cell's core cell valid bit has been set.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CHECK_OF_CORE_REG_ON_SLAVE_FAILED.

The core cell checks to make sure that all of the slave cells do not have their core cell valid bit set before it writes its number to them and sets their core cell valid bit. This check helps prevent spilt brain problems where multiple cells think they are the core cell. This check failed because PDC could not access the cell's Dillon register that contains the core cell valid register.

Probable Cause / Recommended Action:

Cause:

There was a problem accessing the core cell register in Dillon.

Action:

There was a problem reaching the cell whose physical location was put in the chassis code. Look for problems with the fabric. Contact HP Support personnel to troubleshoot the cell.

Event Details:
Chassis Code Encoded Field : 0x200000f0a2002080
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 2 (rendezvous)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 8 (implementation dependent)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x0000000000000041
   FRU Source          = 4 (power entity)
   Source Detail       = 1 (AC mains)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1050

Severity: MINORWARNING

Event Summary: Specifies which PDH area had its end marker corrupted.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CMPLX_NVM_EM_CORRUPT.

Immediately follows generic, high-alert-level BOOT_END_MARKER_CORRUPTED. Specifies which PDH area had its end marker corrupted.

The data field contains the actual value of the end marker.

Probable Cause / Recommended Action:

Cause:

PDH corruption

Action:

Reset cell Update PDC Contact HP Support personnel to troubleshoot the cell

Event Details:
Chassis Code Encoded Field : 0x180000009f0013ca
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 60 (implementation dependent)
   Activity Status         : 10 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000042
Event 1051

Severity: MINORWARNING

Event Summary: Specifies which PDH area had its end marker corrupted.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CMPLX_SCR_EM_CORRUPT.

Immediately follows generic, high-alert-level BOOT_END_MARKER_CORRUPTED. Specifies which PDH area had its end marker corrupted.

The data field contains the actual value of the end marker.

Probable Cause / Recommended Action:

Cause:

PDH corruption

Action:

Reset cell Contact HP Support personnel to troubleshoot cell Update PDC

Event Details:
Chassis Code Encoded Field : 0x180000009f0013c5
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 60 (implementation dependent)
   Activity Status         : 5 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000043
Event 1052

Severity: SERIOUS

Event Summary: Unable to map the console path to a PCI functional address.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CONSOLE_PATH_TO_PFA_ERR.

PDC attempts to map the console path to a PCI Functional Address (PFA). This allows PDC to map the console into memory-mapped I/O space. This chassis code is sent when PDC is unable to create a PFA for the console. Since the core cell cannot configure the console, PDC resets the partition.

Probable Cause / Recommended Action:

Cause:

There was a problem with the core I/O card or the I/O attached to the core cell.