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.

Action:

Make sure that the core I/O card is installed correctly. Make sure the I/O chassis is installed correctly. Contact HP Support personnel to troubleshoot the core I/O card.

Event Details:
Chassis Code Encoded Field : 0x180000f0a3002010
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 3 (console device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000044
Event 1053

Severity: MINORWARNING

Event Summary: Unable to read the IODC header bytes for the console.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CONSOLE_PDC_IODC_HEADER_ERR.

Bootstrap uses PDC_IODC to get the header bytes for the console IODC. This chassis code is sent when PDC_IODC fails.

The data field of the chassis code contains the return status from PDC_IODC.

Probable Cause / Recommended Action:

Cause:

There is a problem with the core I/O card.

Action:

Make sure the core I/O card is installed correctly. Try using another cell as the core cell. Try replacing the core I/O card.

Event Details:
Chassis Code Encoded Field : 0x18000020a3002020
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 3 (console device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 2 (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    : 0x0000000000000045
Event 1054

Severity: MAJORWARNING

Event Summary: A write attempt to the Control Structure failed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CONTROL_STRUCT_WRITE_FAILED.

A write attempt to the Control Structure failed. The most likely reason for this failure is that a remote cell could not be reached.

The data field contains number of cell whose control structure could not be written.

Probable Cause / Recommended Action:

Cause:

Fabric problem. Defective CC.

Action:

Contact HP Support personnel to troubleshoot the system backplane. Contact HP Support personnel to troubleshoot the CC. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000009f0023bf
   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         : 2 (config)
   Caller Subactivity      : 59 (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    : 0x0000000000000046
Event 1055

Severity: MAJORWARNING

Event Summary: The core cell was unable to write its number to one of the slave cells.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CORE_CELL_WRITE_ERR.

The core cell writes its number to the slave cells and sets their core cell valid bit. This write failed because PDC could not access the cell's Dillon register that contains the core cell register.

Probable Cause / Recommended Action:

Cause:

There is a problem with the fabric, preventing the core cell from being able to write to a slave cell The slave cell failed and as a result, the CC-XBC link was brought down and thus other cells are not able to access the failed cell

Action:

Troubleshoot the fabric (run DC connectivity tests, etc.) Troubleshoot the failure of the slave cell (look at chassis logs sent from the slave cell to confirm that it did, in fact, fail, and if so, investigate the cause of the failure for that cell and take the recommended action(s).

Event Details:
Chassis Code Encoded Field : 0x200000f0a200208f
   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         : 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:   0x0000000000000047
   FRU Source          = 4 (power entity)
   Source Detail       = 7 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1056

Severity: INFORMATION

Event Summary: Could not put system into manufacturing mode.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_COULD_NOT_GET_MFG_MODE.

Could not put system into manufacturing mode. GSP determines whether system is in manufacturing mode so this could indicate a failure to communicate with the GSP.

Probable Cause / Recommended Action:

Cause:

An attempt to put system into manufacturing mode failed

Action:

Check communication with GSP Contact HP Support personnel to troubleshoot GSP

Event Details:
Chassis Code Encoded Field : 0x000000009f0003af
   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         : 0 (unspecified)
   Caller Subactivity      : 58 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1057

Severity: SERIOUS

Event Summary: A CPU's data area has overflowed its bounds.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_DATA_OVERFLOW.

A CPU's data area has overflowed its bounds.

The data field contains the physical location of the CPU whose data area overflowed.

Probable Cause / Recommended Action:

Cause:

PDC problem

Action:

Update PDC Contact the Response Center

Event Details:
Chassis Code Encoded Field : 0x200000c09f0013cc
   Alert Level             : 12 (Software failure.)
   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         : 12 (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:   0x0000000000000049
   FRU Source          = 4 (power entity)
   Source Detail       = 9 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1058

Severity: MAJORWARNING

Event Summary: A CPU is being stopped and deconfigured.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_DECONFIG.

A CPU is being stopped and deconfigured. See the previous chassis codes to determine the reason that the CPU is being deconfigured.

Probable Cause / Recommended Action:

Cause:

A CPU is being stopped and deconfigured.

Action:

See previous chassis codes to determine the reason that the CPU is being deconfigured. Contact HP Support personnel to troubleshoot the CPU

Event Details:
Chassis Code Encoded Field : 0x200000409f00302b
   Alert Level             : 4 (Unexpected configuration change detected.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 3 (deconfig)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 11 (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:   0x000000000000004a
   FRU Source          = 4 (power entity)
   Source Detail       = 10 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1059

Severity: MAJORWARNING

Event Summary: An invalid CPU number was passed to a procedure to deconfigure the CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_DECONFIG_INVALID_PARAM.

An invalid CPU number was passed into a procedure to deconfigure the CPU. This is most likely due to either corruption of, or a functional defect in, the PDC firmware.

The cell will be halted.

See BOOT_HALT_DUE_TO_PDC_ERROR following this chassis code for physical location of cell that has been halted.

Probable Cause / Recommended Action:

Cause:

Error in firmware (PDC)

Action:

Use FWUU to reload or update PDC Contact the Response Center

Event Details:
Chassis Code Encoded Field : 0x180000209f004171
   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            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 23 (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    : 0x000000000000004b
Event 1060

Severity: INFORMATION

Event Summary: A CPU has been marked for deconfiguration and will be deconfigured.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_MARKED_AS_DECONFIG.

Forward progress marker indicating that a CPU has been marked for deconfiguration and will be deconfigured. The CPU most likely was marked for deconfiguration due to failures on a previous boot. Refer to the previous chassis codes for the reason for the deconfiguration.

Probable Cause / Recommended Action:

Cause:

The CPU most likely was marked for deconfiguration due to failures on a previous boot.

Action:

Refer to the previous chassis codes for the reason for the deconfiguration. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000009f0010b7
   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      : 11 (implementation dependent)
   Activity Status         : 7 (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    : 0x000000000000004c
Event 1061

Severity: MAJORWARNING

Event Summary: Invalid CPU number passed to procedure to schedule CPU deconfiguration.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_SCHEDULED_DECONFIG_INVALID_PARAM.

An invalid CPU number was passed into a procedure to schedule the deconfiguration of a CPU. This is most likely due to either corruption of, or a functional defect in, the PDC firmware.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Error in firmware (PDC)

Action:

Use FWUU to reload or update PDC. Contact the Response Center.

Event Details:
Chassis Code Encoded Field : 0x180000209f004172
   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            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 23 (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    : 0x000000000000004d
Event 1062

Severity: MAJORWARNING

Event Summary: A CPU's stack has overflowed its allocated area.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_CPU_STACK_OVERFLOW.

A CPU's stack has overflowed its allocated area.

The data field contains the physical location of the CPU whose stack overflowed.

Probable Cause / Recommended Action:

Cause:

Error in firmware (PDC)

Action:

Use FWUU to reload or update PDC Contact the Response Center

Event Details:
Chassis Code Encoded Field : 0x200000c09f0013c0
   Alert Level             : 12 (Software failure.)
   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         : 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:   0x000000000000004e
   FRU Source          = 4 (power entity)
   Source Detail       = 14 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1063

Severity: SERIOUS

Event Summary: Partition is being reset because of failure to cleanup boot device.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_DECONFIG_DEV_FAILED.

While trying to remove a failed boot device from MMIO space and trying to cleanup the device-related data structures, there was an error. This is an indication of a severe problem. Therefore, the partition puts out this chassis log and then all the cells in the partition are reset. This can occur in 3 places:

before reaching BCH

after printing the console messages and before we reach ISL

after returning from ISL

Probable Cause / Recommended Action:

Cause:

A problem with a rope. A problem unmapping the card.

Action:

Replace the IO card for the boot path being tried. Replace the IO chassis for this boot path being tried.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a4002055
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (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 1064

Severity: MAJORWARNING

Event Summary: Slave CPU did not reach expected state in time, will be deconfigured.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_DECONFIG_FAILED_SLAVE.

A slave processor did not reach its expected PST_STATE in the allocated time and will be deconfigured.

The data field contains the "bad" PST_STATE of the failed slave.

Probable Cause / Recommended Action:

Cause:

Defective CPU. Defective CC (look for ERR_RUNWAY_ADDR_PARITY_ERR earlier in boot) Incorrect wait time for processor to reach next PST_STATE. (very unlikely)

Action:

Contact HP Support personnel to troubleshoot the cell board. Update PDC.

Event Details:
Chassis Code Encoded Field : 0x180000229f00102b
   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            : 2 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 2 (implementation dependent)
   Activity Status         : 11 (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    : 0x0000000000000050
Event 1065

Severity: SERIOUS

Event Summary: Core cell failed to write the alive set to all cells in the partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_DISTRIBUTE_ALIVE_SET_ERR.

As soon as the partition is created; which means that a core cell has been selected, an alive set has been created, and the CC has been programmed for communication between the cells in the partition; the core cell writes the alive set to a data structure in scratch RAM on each of the cells in the partition. This chassis log indicates that the alive set was not written to one or more of the cells in the partition.

Probable Cause / Recommended Action:

Cause:

There is a problem with the fabric. One or more of the cells in the partition failed and reset, causing the CC-XBC link to go down.

Action:

Troubleshoot the fabric to determine whether or not this is the problem and if so, exactly what the problem might be. Troubleshoot any failures on any cells in the partition. This involves looking through the chassis logs of all the other cells in the partition to determine whether or not any of the cells reset or failed and if so, why.

Event Details:
Chassis Code Encoded Field : 0x180000f0a2004070
   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      : 7 (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    : 0x0000000000000051
Event 1066

Severity: SERIOUS

Event Summary: Cell is about to be halted because of error initializing CC registers.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_DNA_CSR_INIT_FAILED.

Shortly before early CPU selftests are executed, the monarch CPU programs a number of CC registers (the CELL_ID register, a few CMAP registers – GNI Mask, Line Interleave Mode, and the 44 bit Mode – and the v-cell mapping entries). If there is an error while trying to write the GNI Mask, Line Interleave Mode, or the 44-bit Mode registers, then PDC will determine the physical location of the cell with the problematic CC, send this chassis log, and then halt the cell.

Probable Cause / Recommended Action:

Cause:

Bad Coherency controller (CC) Bad connection between CC and the cell board

Action:

Contact HP Support personnel to troubleshoot the cell

Event Details:
Chassis Code Encoded Field : 0x200000f09100230f
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 1 (cell controller)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (config)
   Caller Subactivity      : 48 (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:   0x0000000000000052
   FRU Source          = 5 (fabric connector)
   Source Detail       = 2 (router)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Level 5 (Impl. Dep.)= 0
Event 1067

Severity: MAJORWARNING

Event Summary: An error was detected in CC before HPMC handling was enabled.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_DNA_ERR_B4_HPMC_ENABLE.

An error was detected in the coherency controller before HPMC handling was enabled.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

An error was detected in the Coherency controller before HPMCs were enabled. Check the data return for the type of error detected.

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x180000f09f00432f
   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         : 4 (user interface)
   Caller Subactivity      : 50 (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    : 0x0000000000000053
Event 1068

Severity: SERIOUS

Event Summary: The end marker separating 2 PDH areas has been overwritten.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_END_MARKER_CORRUPTED.

The end marker separating 2 PDH areas has been overwritten. Data field contains the expected value of the end marker.

Probable Cause / Recommended Action:

Cause:

PDC problem

Action:

Update PDC

Event Details:
Chassis Code Encoded Field : 0x100000c09f0013ce
   Alert Level             : 12 (Software failure.)
   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         : 14 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 2 (expected data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000054
Event 1069

Severity: MINORWARNING

Event Summary: PDC tried to call ENTRY INIT in IODC and IODC failed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERR_EXEC_IODC_ENTRY_INIT.

ENTRY INIT is the IODC entry point used to initialize boot and console devices. It must run successfully for the device to be used. See the PA-RISC IO ARS for details about the ENTRY INIT call. The data in the chassis code Is the return status from the failing call to IODC.

Probable Cause / Recommended Action:

Cause:

IODC failed to initialize the I/O device correctly.

Action:

Figure out what device failed to be initialized. Make sure that the device is functioning and is installed correctly. Try another core cell if console IODC is failing. Try another boot path if the boot device IODC is failing. The chassis codes sent before this chassis code will clearly indicate if the IODC is for the console or a boot device. Make sure boot devices are connected and that the bootp server required for LAN IODC is working.

Event Details:
Chassis Code Encoded Field : 0xb8000020a4001060
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1070

Severity: MINORWARNING

Event Summary: Partition Config Data specified core cell that is not in partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERR_GROUP_C_ROOT_ENTRY_NOT_IN_PD.

The Partition Configuration Data contains four entries that allow the system administrator to specify which cells should be the core cell. PDC tries these entries, in order, to see if they point to a viable core cell. One of the checks performed on the entries is to make sure that each entry that is attempted points to a cell that is in the partition. If the entry points to a cell that did not make the partition rendezvous, this chassis code is sent.

The data in the chassis code is the rendezvous set which contains a one for each cell that made the PD rendezvous. The data sent by this chassis code is a bitmap of cells where the least significant bit represents cell 0 and cell 63 is represented by the most significant bit.

Probable Cause / Recommended Action:

Cause:

Defective cell board Defective core I/O card

Action:

Look at the core cell selections in the PD profile and find the one that it not in the rendezvous set put out by this chassis code. Look for a failed cell or core I/O card.

Event Details:
Chassis Code Encoded Field : 0x18000020a2002051
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   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         : 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    : 0x0000000000000056
Event 1071

Severity: SERIOUS

Event Summary: Core Cell could not read the wakeup vector on a slave cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERR_READING_SLAVE_CELL_WAKEUP_VECTOR_ENTRY.

A core cell cannot access a cell that should be in the partition (affects interleaving, etc.), so reset partition.

The data field contains status of attempt to get wakeup vector - should be failure if seeing this code.

Probable Cause / Recommended Action:

Cause:

A cell is unreachable

Action:

Troubleshoot the fabric.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a5001030
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   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         : 0 (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 1072

Severity: SERIOUS

Event Summary: There was a problem getting to the complex profile.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_ACCESSING_GROUP_A.

There was a problem getting to the complex profile, specifically the Stable Complex Data.

The data field contains status of attempt to access the profile. Depending on when this error occurs, either just the local cell or the entire partition will be reset.

Probable Cause / Recommended Action:

Cause:

Hardware error on cell board (specifically Dillon) ICM corruption caused by either PDC or Utilities (this is unlikely)

Action:

Contact HP Support personnel to troubleshoot the cell board Update PDC Update utilities f/w

Event Details:
Chassis Code Encoded Field : 0xb80000c060004014
   Alert Level             : 12 (Software failure.)
   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      : 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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries) 
Event 1073

Severity: SERIOUS

Event Summary: There was a problem getting to the complex profile.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_ACCESSING_GROUP_B.

There was a problem getting to the complex profile, specifically the Dynamic Complex Data.

The data field contains status of attempt to access the profile. Depending on when this error occurs, either just the local cell or the entire partition will be reset.

Probable Cause / Recommended Action:

Cause:

Hardware error on cell board (specifically Dillon) ICM corruption caused by either PDC or Utilities (this is unlikely)

Action:

Contact HP Support personnel to troubleshoot the cell board Update PDC Update utilities f/w

Event Details:
Chassis Code Encoded Field : 0xb80000c060004024
   Alert Level             : 12 (Software failure.)
   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      : 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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1074

Severity: SERIOUS

Event Summary: There was a problem getting to the complex profile.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_ACCESSING_GROUP_C.

There was a problem getting to the complex profile, specifically the Partition Configuration Data.

The data field contains status of attempt to access the profile. Depending on when this error occurs, either just the local cell or the entire partition will be reset.

Probable Cause / Recommended Action:

Cause:

Hardware error on cell board (specifically Dillon) ICM corruption caused by either PDC or Utilities (this is unlikely)

Action:

Contact HP Support personnel to troubleshoot the cell board Update PDC Update utilities f/w

Event Details:
Chassis Code Encoded Field : 0x180000c060004034
   Alert Level             : 12 (Software failure.)
   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      : 3 (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    : 0x000000000000005a
Event 1075

Severity: SERIOUS

Event Summary: Partition does not have valid Dynamic Complex Data.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_INIT_GROUP_B.

PDC has discovered that either the Dynamic Complex Data checksum is bad or that the Dynamic Complex Data sequence ID is bad and therefore attempted to write the default values to Dynamic Complex Data in an attempt to recover. However, changing Dynamic Complex Data to the default values also did not work, so now the Dynamic Complex Data of the complex profile is not valid. PDC doesn't particularly care about Dynamic Complex Data, so instead of resetting for reconfiguration, we just send out this chassis log and continue booting. The OS should beware that the Dynamic Complex Data is not guaranteed to be valid.

Probable Cause / Recommended Action:

Cause:

There may be a problem with the cell board or possibly PDC. No action is necessary, but some investigation might be prudent.

Action:

Watch the OS boot, and make sure it doesn't declare problems due to the Group B not being valid. Power cycle the cell to see if the problem persists. If it does, there is either a problem with the cell board or PDC. Contact HP Support personnel to troubleshoot the cell board or PDC.

Event Details:
Chassis Code Encoded Field : 0x180000f060004026
   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      : 2 (implementation dependent)
   Activity Status         : 6 (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    : 0x000000000000005b
Event 1076

Severity: SERIOUS

Event Summary: Partition does not have valid Partition Configuration Data.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_INIT_GROUP_C.

PDC has discovered that either the Partition Configuration Data checksum is bad or that the sequence ID is bad and therefore attempted to write the default values to the Partition Configuration Data in an attempt to recover. However, changing to the default values also did not work, so the Partition Configuration Data in the complex profile was not valid. PDC must have valid and compatible Partition Configuration Data throughout the cells in the partition, and if it cannot verify that the partition Configuration Data are valid and compatible, it does a reset for reconfiguration on the partition.

Probable Cause / Recommended Action:

Cause:

There may be a problem with the cell board or possible PDC.

Action:

Carefully watch the chassis logs from the boot following the reset to establish whether or not this problem persists. If the problem persists, then troubleshoot the cell board and inquire about any updates of PDC.

Event Details:
Chassis Code Encoded Field : 0x180000f060004035
   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      : 3 (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    : 0x000000000000005c
Event 1077

Severity: MAJORWARNING

Event Summary: Error occurred initializing the cell state.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_INITIALIZING_CELL_STATE.

Error occurred initializing the cell state

Probable Cause / Recommended Action:

Cause:

Error occurred initializing the cell state. Could be cell hardware or PDC problem.

Action:

Reset cell Contact HP Support personnel to troubleshoot cell Update PDC

Event Details:
Chassis Code Encoded Field : 0xb8000000a100208f
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 1 (data structures)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 8 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries) 
Event 1078

Severity: CRITICAL

Event Summary: PDC was unable to get memory size info from PDH on core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_MMAP_LEN_FAILURE.

While trying to write the memory size constants to Page Zero, PDC discovered that is was unable to get the memory size information from a data structure in PDH memory on the core cell. Because it was unable to get the necessary information the partition is reset for reconfiguration.

Probable Cause / Recommended Action:

Cause:

There was a problem with the fabric A cell in the partition failed and therefore the CC-XBC link went down. There is a bug in PDC in which invalid arguments are passed to the memory map function that put out this chassis log.

Action:

Troubleshoot the fabric. Find out if any of the cells in the partition had failures by looking at their chassis logs, and if so, troubleshoot the cell failure. Inquire about latest PDC in light of this problem and update firmware as appropriate.

Event Details:
Chassis Code Encoded Field : 0x180000f0a1002062
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 1 (data structures)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000005e
Event 1079

Severity: CRITICAL

Event Summary: PDC was unable to get the pointer to the memory size info.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_MMAP_PTR_FAILURE.

While trying to write the memory size constants to page zero, PDC found that it could not access data stored on the core cell.

Probable Cause / Recommended Action:

Cause:

PDC was unable to access data on the core cell.

Action:

Enable PDH tests. Look for problems with scratch RAM being corrupted. Try using a different cell as the core cell. Contact HP Support personnel to troubleshoot the cell board that is having this problem.

Event Details:
Chassis Code Encoded Field : 0x180000f0a1002061
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 1 (data structures)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000005f
Event 1080

Severity: CRITICAL

Event Summary: PDC failed to read the HV Flag in the Partition Configuration Data.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_READING_HV_FLAG_IN_PD_PROFILE.

On Superdome, PDC uses the HV flag to set buddy prefetch in RDR 30 on PA8600 CPUs. Buddy Prefetch makes the CPU prefetch cache lines, giving a performance improvement similar to having 128 byte cache lines. This feature, however causes semaphore contention on applications that store memory semaphores in adjacent cache lines. PDC sets the prefetch using the HV flag in the Partition Configuration Data.

This chassis code is sent when PDC cannot read the complex profile.

Probable Cause / Recommended Action:

Cause:

PDC's semaphore data structure is corrupted.

Action:

Reboot the cell and see if PDC is able to reinitialize semaphores. Make sure the PDH microcontroller has not died while holding the micro semaphore. Make sure PDH tests are enabled in PDC. Contact HP Support personnel to troubleshoot the cell.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a5002090
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 5 (Initial Program Loader (IPL))
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 9 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries) 
Event 1081

Severity: CRITICAL

Event Summary: Core Cell could not read the wakeup vector on a slave cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ERROR_WRITING_SLAVE_CELLS_CPU_WAKEUP_VECTOR.

A core cell cannot access a cell that should be in the partition (affects interleaving, etc.), so reset the partition.

The data field contains status of attempt to set wakeup vector - should be failure if seeing this code.

Probable Cause / Recommended Action:

Cause:

Cell is unreachable

Action:

Contact HP Support personnel to troubleshoot the cell board Contact HP Support personnel to troubleshoot the system backplane

Event Details:
Chassis Code Encoded Field : 0xb80000f0a5001032
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   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         : 2 (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 1082

Severity: INFORMATION

Event Summary: CPU explicitly marked for deconfiguration has been deconfigured.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_EXPLICITLY_DECONFIG_CPU.

Forward progress marker indicating that a CPU that was explicitly marked for deconfiguration has been deconfigured. The CPU may have been marked for deconfiguration due to failures on a previous boot or by the user through the CPUCONFIG command in the Boot Console Handler (BCH).

Probable Cause / Recommended Action:

Cause:

A CPU that was explicitly marked for deconfiguration has been deconfigured.

Action:

Reconfigure the CPU using the CPUCONFIG command in the Boot Console Handler (BCH) if the CPU is functional. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000009f0010b6
   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      : 11 (implementation dependent)
   Activity Status         : 6 (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    : 0x0000000000000062
Event 1083

Severity: CRITICAL

Event Summary: Cell could not communicate with all the other cells in rendezvous set.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FABRIC_RENDEZ_SET_ERR.

PDC checks to make sure that all of the cells in the partition rendezvous set can communicate bilaterally. This cell could communicate with at least one of the other cells in the partition, but could not communicate with every cell that made the rendezvous.

Probable Cause / Recommended Action:

Cause:

Fabric discovery error handling should normally prevent this. If this does happen, it may indicate an intermittent problem with the fabric.

Action:

Look for intermittent problems with the fabric. This cell may also have a problem and need to be replaced. Contact HP Support personnel to troubleshoot.

Event Details:
Chassis Code Encoded Field : 0x200000f0a200c022
   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         : 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:   0x0000000000000063
   FRU Source          = 6 (platform entity)
   Source Detail       = 3 (cabinet fan)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Level 4 (Impl. Dep.)= 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1084

Severity: MINORWARNING

Event Summary: PDC could not obtain a valid cached value for manufacturing mode.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FAIL_1ST_GET_MFG_MODE.

PDC could not obtain a valid cached value for manufacturing mode. This code only comes out on the first failed attempt to get mfg mode, so that the VFP does not come up repeatedly. When this chassis code appears, system continues fine, but assumes manufacturing mode is OFF.

Probable Cause / Recommended Action:

Cause:

Attempting a first boot of the partition with no GSP present

Action:

Reboot with a GSP present

Event Details:
Chassis Code Encoded Field : 0x000000209f0003a1
   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            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 58 (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 1085

Severity: SERIOUS

Event Summary: Failed to clean up rope errors.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FAILED_TO_CLEAN_UP_ROPE_ERRORS.

Failed to clean up rope errors

Probable Cause / Recommended Action:

Cause:

Failed to clean up rope errors

Action:

Reset cell Contact HP Support personnel to troubleshoot cell

Event Details:
Chassis Code Encoded Field : 0xb80000f0a4002057
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (implementation dependent)
   Activity Status         : 7 (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 1086

Severity: CRITICAL

Event Summary: Unable to read the boot timer from the Partition Configuration Data.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FAILED_TO_READ_BOOT_TIMER_FROM_PD_PROFILE.

PDC failed reading the complex profile. This could mean that ICM is corrupted or that there is a problem with semaphores. The fact that PDC does not know the value of the boot timer is not that significant. The real problem is the failure to read the complex profile. PDC needs the configuration information in the Partition Configuration Data and cannot continue booting without it.

Probable Cause / Recommended Action:

Cause:

PDC could not access the Partition Configuration Data. This probably indicates corrupted data structures on the cell.

Action:

Power the cell down and back up and see if the problem persists. Make sure PDH tests are enabled in PDC. If the problem persists, there is either a problem with the cell board or PDC. Contact HP Support personnel to troubleshoot the problem.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a4002056
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (implementation dependent)
   Activity Status         : 6 (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 1087

Severity: CRITICAL

Event Summary: Cell cannot access its primary profile to get the path.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FAILURE_READING_PATH.

Cell cannot access its primary profile to get the path.

The data field contains the status of the attempt to get the path. The partition will reset for reconfig.

Probable Cause / Recommended Action:

Cause:

PDC cannot access its complex profile due to an internal PDC error.

Action:

Power the cell down and back up and see if the problem persists. If it does, there is either a problem with the cell board or PDC. Contact HP Support personnel to troubleshoot the problem.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a4002003
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 0 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1088

Severity: CRITICAL

Event Summary: PDC_IODC failed to read information about the console.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FATAL_PDC_IODC_FAILURE.

There was a problem attempting to use PDC_IODC to read information about the console. This failure in the PDC call is considered fatal.

Probable Cause / Recommended Action:

Cause:

PDC_IODC[Get Entry Point] failed.

Action:

Look for another error chassis code such as BOOT_CONSOLE_PDC_IODC_HEADER_ERR that indicates that a problem occurred. Try rebooting the cell and then changing the core cell. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000f0a3002020
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 3 (console device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 2 (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    : 0x0000000000000068
Event 1089

Severity: MAJORWARNING

Event Summary: Monarch CPU FPU (floating point unit) failed during late CPU selftests.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_FPU_FAILED.

The monarch CPU FPU (floating point unit) failed during late CPU selftests. The CPU will be deconfigured and cell will be reset.

Probable Cause / Recommended Action:

Cause:

Defective CPU - TheBOOT_CPU_DECONFIG chassis code following this chassis code will indicate the physical location of the CPU that has been deconfigured.

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x000000221100104f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 1 (processor)
   Source FRU Detail       : 1 (processor general)
   Source ID               : 0 (platform dependent)
   Event Detail            : 2 (underspeed)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1090

Severity: CRITICAL

Event Summary: PDC failed to read the cell width from the complex profile.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_GET_CELL_WIDTH_FAIL.

PDC failed to read the cell width from the complex profile. Data field contains the status of the attempt to read the profile. Local Cell which failure occurred on will halt.

Probable Cause / Recommended Action:

Cause:

PDC cannot access its complex profile due to an internal PDC error.

Action:

Power the cell down and back up and see if the problem persists. If it does, there is either a problem with the cell board or PDC.

Event Details:
Chassis Code Encoded Field : 0x180000f0a1004010
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 1 (data structures)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000006a
Event 1091

Severity: SERIOUS

Event Summary: Partition monarch CPU cannot communicate to a slave CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_GET_CPU_PST_STATE_FAILED.

User attempted to return to BCH from ISL, but the monarch CPU could not communicate with one of the slaves, so reset PD.

Probable Cause / Recommended Action:

Cause:

CPU is on unreachable cell Defective CPU

Action:

Contact HP Support personnel to troubleshoot cell board Investigate for fabric problem

Event Details:
Chassis Code Encoded Field : 0x000000f0a5001030
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   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         : 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 1092
Severity: SERIOUS

Event Summary: Platform configuration information could not be retrieved from the GSP.

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

The platform configuration information could not be retrieved from the GSP. Default values will be used.

The value in the data field helps to isolate the failure.
        -1: Unknown failure
        -4: USB not functioning
      -128: Command structure not valid
      -129: Command not completed
Probable Cause / Recommended Action:

Cause:

GSP is not present or not responding, or USB is not functioning Utilities / PDC version incompatibility Defect in PDC or Utilities firmware

Action:

If this is the first boot, GSP must be present to proceed! Determine why GSP is not responding. Contact HP Support personnel to troubleshoot GSP and USB cables. Check PDC / utilities versions Update PDC / utilities firmware
Event Details:
Chassis Code Encoded Field : 0x180000609f0000ff
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 15 (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    : 0x000000000000006c
Event 1093

Severity: SERIOUS

Event Summary: An error occurred trying to get the address of the slave vector table.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_GET_SLAVE_VECTOR_ADDR_PROB.

An error occurred trying to get the address of the slave vector table. This could be cause by corruption of, or a functional defect in, the PDC firmware or could be caused by a hardware problem reaching the remote cell. The data return will indicate the failure type. The partition will be reset for reconfiguration.

Probable Cause / Recommended Action:

Cause:

An error occurred trying to get the address of the slave vector table. The data return indicates the type of error -33: PDC defect -65: A hardware error occurred trying to reach the remote cell

Action:

Use FWUU to reload or update PDC Verify the routing between the cells in the partition.

Event Details:
Chassis Code Encoded Field : 0x180000a09f004184
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 24 (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    : 0x000000000000006d
Event 1094

Severity: MAJORWARNING

Event Summary: The requested entry is out of bounds.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_GET_SLAVE_VECTOR_INVALID_ARG.

The requested entry is out of bounds. This is most likely due to either corruption of, or a functional defect in, the PDC firmware. The cell will be halted. See BOOT_HALT_DUE_TO_PDC_ERROR following this chassis code for physical location of cell that has been halted.

Probable Cause / Recommended Action:

Cause:

Error in firmware (PDC)

Action:

Use FWUU to reload or update PDC Contact HP Support personnel

Event Details:
Chassis Code Encoded Field : 0x180000209f004183
   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            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 24 (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    : 0x000000000000006e
Event 1095

Severity: SERIOUS

Event Summary: Unable to deconfigure CPU due to problem releasing semaphores.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_HALT_DUE_CPU_DECONFIG_SM4_PROBLEM.

When trying to deconfigure a CPU, we had a problem releasing semaphores held by that CPU. Any CPUs being deconfigured must also release any semaphores which they have locked or for which they are in line.

Probable Cause / Recommended Action:

Cause:

Cell hardware failure might cause the hardware semaphore not to work properly or may cause PDH memory not to work properly. It could also be a PDC problem with trying to release the semaphores or a corrupted semaphore structure from some other PDC activity.

Action:

Contact HP Support personnel to troubleshoot the cell board Update PDC

Event Details:
Chassis Code Encoded Field : 0x200000f09f0031bf
   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         : 3 (deconfig)
   Caller Subactivity      : 27 (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:   0x000000000000006f
   FRU Source          = 6 (platform entity)
   Source Detail       = 15 (firmware)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Level 4 (Impl. Dep.)= 0
   Level 5 (Impl. Dep.)= 0
   Slot Number         = 0
Event 1096

Severity: SERIOUS

Event Summary: Cell has been halted due to a previous firmware (PDC) error.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_HALT_DUE_TO_PDC_ERROR.

The cell has been halted due to a previous firmware (PDC) error. Previous chassis codes will indicate the actual error in PDC that has occurred.

Probable Cause / Recommended Action:

Cause:

PDC error

Action:

Use FWUU to reload or update the firmware (PDC) Contact HP Support personnel to troubleshoot situation

Event Details:
Chassis Code Encoded Field : 0x200000c09f0002c2
   Alert Level             : 12 (Software failure.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 44 (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:   0x0000000000000070
   FRU Source          = 7 (memory)
   Source Detail       = 0 (unknown, no source stated)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Extender Location   = 0
   DIMMS Rank          = 0
Event 1097

Severity: SERIOUS

Event Summary: Cell has a CPU with an unsupported CPU revision.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_HALT_DUE_TO_UNSUPPORTED_CPU_REV.

PDC found a CPU on the cell board which has an unsupported CPU revision.

The data field reports the physical location of the CPU.

Probable Cause / Recommended Action:

Cause:

PDC found a CPU with an unsupported CPU revision

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x200000f09f001042
   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      : 4 (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:   0x0000000000000071
   FRU Source          = 7 (memory)
   Source Detail       = 1 (controller)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
   Extender Location   = 0
   DIMMS Rank          = 0
Event 1098

Severity: SERIOUS

Event Summary: Error detected in ICM while trying to retrieve configuration from GSP.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ICM_CMD_UNEXPECTEDLY_INVALID.

An error was detected in the ICM while trying to retrieve the configuration from the GSP. The cell is halted.

Probable Cause / Recommended Action:

Cause:

PDC defect PDHC firmware defect Scratch RAM error

Action:

Use FWUU to update PDC and / or the PDHC firmware Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x000000a09f0040ff
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 15 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)  
Event 1099

Severity: SERIOUS

Event Summary: Partition configuration data changed but the checksum did not.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ILLEGAL_GROUP_C_CHANGE.

An update of the partition configuration data must also update the checksum. This chassis code is sent if PDC detected that the partition configuration data changed but the checksum did not.

The data field contains the partition configuration data sequence ID.

Probable Cause / Recommended Action:

Cause:

Software did not update the profile in the architected manner.

Action:

Check for PDC and/or Utilities upgrade.

Event Details:
Chassis Code Encoded Field : 0xb80000c060004036
   Alert Level             : 12 (Software failure.)
   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      : 3 (implementation dependent)
   Activity Status         : 6 (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 1100

Severity: MAJORWARNING

Event Summary: The CPU number supplied to a procedure is out of range.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ILLEGAL_LOCAL_CPU_NUM.

The CPU number supplied to a procedure is out of range. This is most likely due to either corruption of, or a functional defect in, the PDC firmware.

The cell will be halted.

See BOOT_HALT_DUE_TO_PDC_ERR following this for the physical location of the cell that has been halted.

Probable Cause / Recommended Action:

Cause:

Error in firmware (PDC)

Action:

Use FWUU to reload or update PDC Contact HP Support personnel to troubleshoot

Event Details:
Chassis Code Encoded Field : 0x180000259f00405f
   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            : 5 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 5 (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    : 0x0000000000000074
Event 1101

Severity: MAJORWARNING

Event Summary: The monarch CPU has tried to illegally deconfigure itself.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ILLEGAL_MONARCH_SUICIDE.

The monarch CPU has tried to illegally deconfigure itself. This could be cause by corruption of, or a functional defect in, the PDC firmware as the monarch should never be executing this code.

The cell will be halted.

The value in the data field is the monarch CPU number. Previous chassis codes may indicate why a CPU was being deconfigured.

Probable Cause / Recommended Action:

Cause:

The monarch CPU has tried to illegally deconfigure itself. This could be cause by corruption of, or a functional defect in, the PDC firmware as the monarch should never be executing this code. The cell will be halted.

Action:

Use FWUU to reload or update PDC. Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000009f000401
   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         : 0 (unspecified)
   Caller Subactivity      : 64 (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    : 0x0000000000000075
Event 1102

Severity: SERIOUS

Event Summary: Cell attempting rendezvous had different cabinet type than core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INCOMPATIBLE_CABINET_TYPE.

A cell attempting to rendezvous in a partition had a different cabinet type than the core cell.

The data field contains the cabinet type that differed from the core cell's. Differing cell will be added to the dead set.

Probable Cause / Recommended Action:

Cause:

Cells are in cabinets of different types (e.g., SD16000 vs.SD64000)

Action:

Reconfigure complex to not have partitions spanning the cabinets, or don't join different cabinet types together as a SD64000.

Event Details:
Chassis Code Encoded Field : 0x180000a0a2004061
   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         : 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    : 0x0000000000000076
Event 1103

Severity: SERIOUS

Event Summary: Cell attempting rendezvous has CPU HVERSION different than core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INCOMPATIBLE_CPU_HV.

A cell attempting to rendezvous in a partition had Processor Module HVERSION that differed from the core cell's.

The data field contains the HVERSION that differed from the core cell. Differing cell will be added to the dead set.

Probable Cause / Recommended Action:

Cause:

Cells have different CPU HVERSIONS.

Action:

Reassign cells into partitions with uniform HVERSIONS, or contact HP Support personnel to troubleshoot the differing cell boards.

Event Details:
Chassis Code Encoded Field : 0x180000a0a2004063
   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         : 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    : 0x0000000000000077
Event 1104

Severity: SERIOUS

Event Summary: Cell has CPUs with different CPU revision than core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INCOMPATIBLE_CPU_ID.

A cell attempting to rendezvous in a partition had processors with different revisions than the core cell.

The data field contains the revision of the processors in the cell that differs from the core cell. Differing cell will be added to the dead set.

Probable Cause / Recommended Action:

Cause:

Cells have different types of CPUs

Action:

Reassign cells into partitions with uniform CPUs, or contact HP Support personnel to troubleshoot the differing cell boards.

Event Details:
Chassis Code Encoded Field : 0x180000a0a2004062
   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         : 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    : 0x0000000000000078
Event 1105

Severity: SERIOUS

Event Summary: Cell has CPUs with different CPU speed than core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INCOMPATIBLE_CPU_SPEED.

A cell attempting to rendezvous in a partition had a different CPU speed than the core cell for that partition.

The data field contains the speed of processors in the cell that differs from the core cell. Differing cell will be added to the dead set.

Probable Cause / Recommended Action:

Cause:

Cells have different CPUs (should have been resolved by earlier CPU_ID check) or same processors running at different speeds.

Action:

Reassign cells into partitions with uniform CPUs, or contact HP Support personnel to troubleshoot the differing cell boards.

Event Details:
Chassis Code Encoded Field : 0x180000a0a2004064
   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         : 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    : 0x0000000000000079
Event 1106

Severity: SERIOUS

Event Summary: A cell had a different version of PDC than the core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INCOMPATIBLE_PDC_REV.

A cell attempting to rendezvous in a partition had a different PDC revision than the core cell for that partition. Could mean that data structures are laid out in contradictory ways. Cell cannot join PD and is added to the dead set.

The data field contains the PDC revision of the kicked-out cell.

Probable Cause / Recommended Action:

Cause:

Cells in a partition have different PDC revisions

Action:

Either reassign cells into partitions with like revisions, or use FWUU to install the same version of PDC on all cells in the partition

Event Details:
Chassis Code Encoded Field : 0x180000a0a2004060
   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         : 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    : 0x000000000000007a
Event 1107

Severity: MAJORWARNING

Event Summary: The stable complex profile in this cell has an invalid sequence ID.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_A_SEQ_ID.

PDC detected an invalid sequence ID in the Stable complex profile on this cell. This means that the complex profile is not valid and that PDC cannot rendezvous the cells into a partition. The cell will be reset for reconfiguration, allowing another complex profile to be pushed out before it attempts to boot again.

Probable Cause / Recommended Action:

Cause:

The cell did not have a valid complex profile.

Action:

Push a new complex profile out. Make sure that the utilities system is still functioning.

Event Details:
Chassis Code Encoded Field : 0x180000f060004013
   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      : 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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000007b
Event 1108

Severity: SERIOUS

Event Summary: The stable complex profile in this cell has an invalid sequence ID.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_A_XSUM.

PDC detected an invalid checksum in the stable complex profile on this cell. This means that the complex profile is not valid and that PDC cannot rendezvous the cells into a partition. The cell will be reset for reconfiguration, allowing another complex profile to be pushed out before it attempts to boot again.

Probable Cause / Recommended Action:

Cause:

The cell did not have a valid complex profile.

Action:

Push a new complex profile out. Make sure that the utilities system is still functioning.

Event Details:
Chassis Code Encoded Field : 0x000000f060004011
   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      : 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 1109

Severity: MAJORWARNING

Event Summary: The dynamic complex profile in this cell has an invalid sequence ID.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_B_SEQ_ID.

PDC detected an invalid sequence ID in the dynamic complex profile on this cell. PDC does not use the dynamic complex profile. It is intended to be used by the OS.

Probable Cause / Recommended Action:

Cause:

The cell did not have a valid dynamic complex profile.

Action:

The dynamic complex profile is used only by the OS. PDC does not use it. Check the OS documentation to see how the OS uses it.

Event Details:
Chassis Code Encoded Field : 0x1800002060004023
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   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      : 2 (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    : 0x000000000000007d
Event 1110

Severity: MAJORWARNING

Event Summary: The dynamic complex profile in this cell has an invalid checksum.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_B_XSUM.

PDC detected an invalid checksum in the dynamic complex profile on this cell. PDC does not use the dynamic complex profile. It is intended to be used by the OS.

Probable Cause / Recommended Action:

Cause:

The cell did not have a valid dynamic complex profile.

Action:

The dynamic complex profile is used only by the OS. PDC does not use it. Check the OS documentation to see how the OS uses it.

Event Details:
Chassis Code Encoded Field : 0x0000002060004021
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   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      : 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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1111

Severity: MINORWARNING

Event Summary: PDC did not detect a valid partition configuration data Sequence ID.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_C_SEQ_ID.

PDC did not detect a valid partition configuration data Sequence ID.

The data field contains the Sequence ID.

Probable Cause / Recommended Action:

Cause:

Most likely, the partition configuration data has not been initialized

Action:

None, PDC will attempt to initialize the profile.

Event Details:
Chassis Code Encoded Field : 0x1800004060004033
   Alert Level             : 4 (Unexpected configuration change detected.)
   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      : 3 (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    : 0x000000000000007f
Event 1112

Severity: MINORWARNING

Event Summary: PDC detected an invalid partition configuration data checksum.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GROUP_C_XSUM.

PDC detected an invalid partition configuration data checksum.

Probable Cause / Recommended Action:

Cause:

Most likely, the partition configuration data has not been initialized

Action:

None, PDC will attempt to initialize the profile.

Event Details:
Chassis Code Encoded Field : 0x0000004060004031
   Alert Level             : 4 (Unexpected configuration change detected.)
   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      : 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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1113

Severity: SERIOUS

Event Summary: Cell width specified in the stable complex profile is not supported.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_INVALID_GRP_A_CELL_WIDTH.

PDC programs the cell width into the CC based on the cell width field in the stable complex profile. This chassis code is sent when PDC reads a cell width value from the stable complex profile that is not supported on this platform. The data field for this chassis code contains the cell width value from the stable complex profile. The cell width refers to how many bits of an address in memory are used for the cell number. Wider cell widths allow more cells in the system, but require that the cell have less address space since the bits in the address used for the cell number cannot be used for addresses within the cell.

Probable Cause / Recommended Action:

Cause:

The cell width field in the stable complex profile contains an illegal value.

Action:

Push out a new stable complex profile that contains a legal value.

Event Details:
Chassis Code Encoded Field : 0x180008f0a1004013
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 1 (data structures)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000081
Event 1114

Severity: MINORWARNING

Event Summary: IODC requested SPA space.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_IODC_REQ_SPA_ERR.

Soft Physical Address space is not supported on Superdome since Superdome's IO is based on the PCI standard. This chassis code is sent when IODC requests SPA space. This represents a bug in IODC. The data in the chassis code is the SPA space requested by the IODC.

Probable Cause / Recommended Action:

Cause:

IODC for an I/O device requested SPA space.

Action:

Try a different I/O device Update IODC.

Event Details:
Chassis Code Encoded Field : 0x18000020a4002061
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000082
Event 1115

Severity: MAJORWARNING

Event Summary: An error has occurred loading the instruction cache.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_LOAD_ICACHE_ERROR.

An error has occurred loading the instruction cache. Subsequent chassis codes hold the pointers to the code address, actual and expected data and indicate whether the error was a data or tag error? The CPU will be deconfigured.

Probable Cause / Recommended Action:

Cause:

An error occurred loading the instruction cache on the CPU.

Action:

Contact HP Support personnel to troubleshoot

Event Details:
Chassis Code Encoded Field : 0x000000a09f001161
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 22 (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 1116

Severity: SERIOUS

Event Summary: Failed to map vcell entries in coherency controller.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_LOCAL_DNA_VCELL_INIT_FAIL.

Failed to map vcell entries in coherency controller. Cell will halt.

Probable Cause / Recommended Action:

Cause:

Bad Coherency controller (CC)

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Log Timestamp : 04/23/2001 16:17:35
Chassis Code Encoded Field : 0x200000a09f00231f
   Alert Level             : 10 (Boot possible, functionality lost.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 15 (firmware)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 49 (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:   0x0000000000000084
   FRU Source          = 8 (I/O device)
   Source Detail       = 4 (expansion bridge)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   ! !
Event 1117

Severity: MINORWARNING

Event Summary: A slave CPU failed during late CPU selftest.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_LST_FAILED.

A slave CPU failed during late CPU selftest. The CPU will be deconfigured.

Probable Cause / Recommended Action:

Cause:

Defective CPU - TheBOOT_CPU_DECONFIG chassis code following this chassis code will indicate the physical location of the CPU that has been deconfigured.

Action:

Contact HP Support personnel to troubleshoot

Event Details:
Chassis Code Encoded Field : 0x000000201100104f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 1 (processor)
   Source FRU Detail       : 1 (processor general)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1118

Severity: MINORWARNING

Event Summary: Some non-fatal but strange event occurred during late CPU selftests.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_LST_WARNING.

The low-level CPU code (ported from the processor team in Fort Collins) returned an error from the late CPU selftest code. The PDC team does not know exactly what types of events could have occurred to cause this warning.

Probable Cause / Recommended Action:

Cause:

Mostly likely cause of this chassis log is a bad CPU or a CPU that is becoming more unhealthy. It is conceivable that a CPU would have some warning scenario during late selftests but that it is quite healthy and can continue to operate successfully indefinitely.

Action:

Look for other chassis logs that may have been sent that indicate other problems with the CPU. Verify that the CPU (indicated by the global CPU number field of the encoded portion of the log) reached BCH or that it is running at UNIX (via the UNIX "top" command). If you see any signs of CPU problems by the CPU that sent the log, then replace the CPU.

Event Details:
Chassis Code Encoded Field : 0x000000201100104e
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 1 (processor)
   Source FRU Detail       : 1 (processor general)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (implementation dependent)
   Activity Status         : 14 (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 1119

Severity: INFORMATION

Event Summary: A change in the major number of PDC has occurred.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MAJOR_REV_CHANGE.

PDC firmware has been updated and a change in the major number was detected.

Probable Cause / Recommended Action:

Cause:

Update to PDC firmware

Action:

None

Event Details:
Chassis Code Encoded Field : 0x880000039f00012e
   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            : 3 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 18 (implementation dependent)
   Activity Status         : 14 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 17 (revision number)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000087
Event 1120

Severity: MINORWARNING

Event Summary: PDC could not map a Boot Device into MMIO space.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MAP_IN_BOOT_DEV_FAILED.

Before PDC can use a boot device, it must map it's registers into MMIO space. This chassis code is sent when PDC is unable to map a device. The data is the failing status from the function that does the mapping.

Probable Cause / Recommended Action:

Cause:

An I/O card requested I/O port space. Superdome does not support I/O port space. There was a problem accessing the card. There might be a leak in MMIO space allocation.

Action:

Get a supported I/O card. Reboot system Try another I/O card

Event Details:
Chassis Code Encoded Field : 0x18000020a4002053
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (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    : 0x0000000000000088
Event 1121

Severity: SERIOUS

Event Summary: PDC was unable to map the console into Memory Mapped I/O space.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MAP_IN_CONSOLE_DEV_ERR.

Before PDC can use the console, it must map the console's registers into memory mapped I/O space. The core I/O is mapped into MMIO space by PDC programming the Base Address Registers (BARs) in PCI configuration space. This chassis code is sent when the function that maps the card into MMIO space fails. The data in this chassis code in the return status from that function.

Probable Cause / Recommended Action:

Cause:

PDC was unable to map the console into MMIO space.

Action:

Look for a problem with the core IO card attached to the core cell. Try another core cell. Contact HP Support personnel to troubleshoot the core IO card. Contact HP Support personnel to troubleshoot the IO chassis.

Event Details:
Chassis Code Encoded Field : 0x180000f0a3002011
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 3 (console device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000089
Event 1122

Severity: SERIOUS

Event Summary: MBE free area of memory for late CPU selftests could not be found.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MEM_TEST_SPACE_FAILED.

A multi-bit error free area of memory, large enough for late CPU selftests, could not be found. The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Excessive errors due to defective DIMMs Coherency controller seating

Action:

Replace DIMM(s) based on PDT entries or previous chassis codes Contact HP Support personnel to troubleshoot the Cell board

Event Details:
Chassis Code Encoded Field : 0x200000f09f0012ff
   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      : 47 (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:   0x000000000000008a
   FRU Source          = 8 (I/O device)
   Source Detail       = 10 (parallel)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   ! !
Event 1123

Severity: INFORMATION

Event Summary: A change in the minor number of PDC has occurred.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MINOR_REV_CHANGE.

PDC firmware has been updated and a change in the minor number was detected.

Probable Cause / Recommended Action:

Cause:

Update to PDC firmware

Action:

None

Event Details:
Chassis Code Encoded Field : 0x880000049f00012e
   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            : 4 (unknown)
   Caller Activity         : 0 (unspecified)
   Caller Subactivity      : 18 (implementation dependent)
   Activity Status         : 14 (implementation dependent)
   Reporting Entity Type   : 0 (system firmware)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 17 (revision number)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000008b
Event 1124

Severity: MAJORWARNING

Event Summary: The CPU's speed does not match that of the monarch CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MISMATCH_CPU_ACT_SPEEDS.

The CPU's speed does not match that of the monarch CPU. The CPU will be deconfigured.

Probable Cause / Recommended Action:

Cause:

The CPU's speed does not match that of the monarch CPU.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000209f0010b1
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 11 (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    : 0x000000000000008c
Event 1125

Severity: MAJORWARNING

Event Summary: The CPU's speed rating does not match that of the monarch CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MISMATCH_CPU_CAP_SPEEDS.

The CPU's speed rating does not match that of the monarch CPU. The CPU will be deconfigured.

Probable Cause / Recommended Action:

Cause:

The CPU's speed rating does not match that of the monarch CPU.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000209f0010b2
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 11 (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    : 0x000000000000008d
Event 1126

Severity: MAJORWARNING

Event Summary: The CPU's data cache size does not match that of the monarch CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MISMATCH_CPU_DCACHE_SIZES.

The CPU's data cache size does not match that of the monarch CPU.

Probable Cause / Recommended Action:

Cause:

The CPU's data cache size does not match that of the monarch CPU.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000209f0010b4
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 11 (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    : 0x000000000000008e
Event 1127

Severity: MAJORWARNING

Event Summary: CPU's instruction cache size does not match that of the monarch CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MISMATCH_CPU_ICACHE_SIZES.

The CPU's instruction cache size does not match that of the monarch CPU.

Probable Cause / Recommended Action:

Cause:

The CPU's instruction cache size does not match that of the monarch CPU.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000209f0010b3
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 11 (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    : 0x000000000000008f
Event 1128

Severity: MAJORWARNING

Event Summary: The CPU's revision does not match that of the monarch CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MISMATCH_CPU_REV.

The CPU's revision does not match that of the monarch CPU.

Probable Cause / Recommended Action:

Cause:

The CPU's revision does not match that of the monarch CPU.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000209f0010b5
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000090
Event 1129

Severity: INFORMATION

Event Summary: Cell monarch CPU chosen.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MONARCH_SELECTED.

Forward progress marker that indicates which processor on the cell has been selected as the cell monarch. The data field contains the local CPU number the processor selected as the monarch.

Probable Cause / Recommended Action:

Cause:

Forward progress

Action:

None

Event Details:
Chassis Code Encoded Field : 0x180000009f00206d
   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         : 2 (config)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 13 (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    : 0x0000000000000091
Event 1130

Severity: CRITICAL

Event Summary: Couldn't find a large enough area of error free memory to load PDC.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MOVE_ROM_CODE_ERROR.

Couldn't find a large enough area of error free memory to load PDC into memory.

The cell will be hard halted.

Probable Cause / Recommended Action:

Cause:

Excessive errors in memory.

Action:

Contact HP Support personnel to troubleshoot DIMMs based on PDT entries or previous chassis codes Contact HP Support personnel to troubleshoot cell board

Event Details:
Chassis Code Encoded Field : 0x180000f09f0020a1
   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         : 2 (config)
   Caller Subactivity      : 10 (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    : 0x0000000000000092
Event 1131

Severity: SERIOUS

Event Summary: Couldn't find large enough area of error free memory to load PDC.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MOVE_ROM_DATA_ERROR.

Couldn't find a large enough area of error free memory to load PDC ROM into memory.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Excessive errors in memory.

Action:

Contact HP Support personnel to troubleshoot cell board

Event Details:
Chassis Code Encoded Field : 0x180000f09f0020a2
   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         : 2 (config)
   Caller Subactivity      : 10 (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    : 0x0000000000000093
Event 1132

Severity: SERIOUS

Event Summary: Read after write of PDC ROM failed during relocation of PDC to memory.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MOVE_ROM_READ_AFTER_WRITE_ERROR.

Read after write of PDC ROM failed during relocation of PDC to memory.

The cell will be hard halted.

The data field holds the memory address at the time of the failure.

Probable Cause / Recommended Action:

Cause:

This could be caused by memory errors or a processor cache / Coherency controller failure.

Action:

Contact HP Support personnel to troubleshoot the cell board Verify / Replace the memory DIMMS

Event Details:
Chassis Code Encoded Field : 0x180000f09f0010af
   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      : 10 (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    : 0x0000000000000094
Event 1133

Severity: SERIOUS

Event Summary: Test of the number 6 MP Selection register in Dillon failed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MP_REG_6_ERROR.

Test of the number 6 MP Selection register in Dillon failed. PDC was unable to correctly write and read a test pattern to the register.

The cell will halt.

Probable Cause / Recommended Action:

Cause:

PDC cannot communicate properly to the Dillon.

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x000000f23500101f
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 3 (PDH)
   Source FRU Detail       : 5 (platform registers)
   Source ID               : 0 (platform dependent)
   Event Detail            : 2 (write error)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 1 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
 
Event 1134

Severity: SERIOUS

Event Summary: More than one cell in a partition believes it is the core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_MULTIPLE_CORE_CELLS_ERR.

More than one cell in a partition believes it is the core cell. Chassis code from one core cell will contain the physical location of the other core cell in its data field.

Probable Cause / Recommended Action:

Cause:

Cells in partition have different partition configuration data Fabric problem prevents the cells from seeing one another

Action:

Fix utilities problem Check fabric

Event Details:
Chassis Code Encoded Field : 0x200000f0a2002081
   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         : 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:   0x0000000000000096
   FRU Source          = 9 (cell)
   Source Detail       = 6 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
Event 1135

Severity: SERIOUS

Event Summary: On a boot action of "Attempt next path", PDC tries invalid next path.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_NEXT_PATH_FATAL_ERR.

On a boot action of "Attempt next path", PDC tries invalid next path.

The data field contains the invalid path.

Probable Cause / Recommended Action:

Cause:

Should never happen, but it if does it would be caused by an internal PDC error.

Action:

Check for PDC upgrade Contact the Response Center

Event Details:
Chassis Code Encoded Field : 0xb80000f0a4002005
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 0 (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 1137

Severity: CRITICAL

Event Summary: No cell rendezvoused in the partition can be the core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_NO_VIABLE_CORE_CELL.

No cell rendezvoused in the partition can be the core cell.

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

Probable Cause / Recommended Action:

Cause:

No cell has core IO. There is an IO problem with cell(s) that does have core IO

Action:

Configure the partition to include cell with core IO. Check IO and IO connections (REO cables)

Event Details:
Chassis Code Encoded Field : 0x200000f0a200205f
   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         : 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:   0x0000000000000098
   FRU Source          = 9 (cell)
   Source Detail       = 8 (unknown)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 0
   Cell Location       = 0
Event 1138

Severity: MINORWARNING

Event Summary: Error occurred in NVM initialization.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_NVM_INIT_ERR.

Error occurred in NVM initialization

Probable Cause / Recommended Action:

Cause:

NVM error

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x000000009f00226f
   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         : 2 (config)
   Caller Subactivity      : 38 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1139

Severity: SERIOUS

Event Summary: PDC was unable to get a semaphore that it needed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_OBTAIN_CELL_GLOBAL_SM4_FAILED.

PDC could not get the cell global semaphore.

Probable Cause / Recommended Action:

Cause:

Corrupted or failed scratch RAM CPU hung in late boot while holding the semaphore

Action:

Try booting again. Make sure PDH selftests are enabled. Contact HP Support personnel to troubleshoot the cell.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a20020b1
   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         : 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 1140

Severity: SERIOUS

Event Summary: PDC was unable to get a semaphore that it needed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_OBTAIN_MICRO_SM4_FAILED.

PDC could not get the micro semaphore. Both PDC and the PDH micro controller use the micro semaphore.

Probable Cause / Recommended Action:

Cause:

Another CPU or the PDH micro controller could have failed.

Action:

Try booting again. Make sure PDH selftests are enabled. Contact HP Support personnel to troubleshoot the cell.

Event Details:
Chassis Code Encoded Field : 0xb80000f0a20020b2
   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         : 2 (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 1141

Severity: MINORWARNING

Event Summary: AutoBoot attempt failed, so stopping at BCH according to Boot Action.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_ON_FAILURE_GOTO_BCH.

System was configured for AutoBoot. This chassis code indicates that the system attempted and failed to boot off a path whose Boot Action specified to attempt a boot and if the boot failed, return to BCH.

Probable Cause / Recommended Action:

Cause:

No boot disk or defective boot disk. Invalid Path

Action:

Insert a good disk Specify a valid path from the BCH MAin menu

Event Details:
Chassis Code Encoded Field : 0x00000030a4002002
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries) 
Event 1142

Severity: MINORWARNING

Event Summary: Unable to determine whether or not the complex was in MFG mode.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_OPERATING_MODE_UNDEFINED.

Once the Utilities have completed the Retrieve Platform Configuration command (a non-blocking call sent from PDC to the Utilities during boot), PDC should know whether or not the complex is in MFG mode. This chassis log indicates that PDC doesn't know at a point in boot where it should.

Probable Cause / Recommended Action:

Cause:

PDH memory is defective. CC or CPU hardware are bad and PDC cannot access the PDH memory and get accurate results.

Action:

Contact HP Support personnel to troubleshoot the cell board Update PDC.

Event Details:
Chassis Code Encoded Field : 0x000000209f0040b8
   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            : 0 (unknown)
   Caller Activity         : 4 (user interface)
   Caller Subactivity      : 11 (implementation dependent)
   Activity Status         : 8 (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 1143

Severity: SERIOUS

Event Summary: Partition numbers mismatch in stable and partition configuration data.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PARTITION_NUM_MISMATCH_A_C_ERR.

The stable complex profile can be used to get a cell's partition number because it contains the partition number to which the cell is assigned. The partition configuration data also holds a partition number. PDC compares the partition number in the partition configuration data with the partition to which the cell is assigned in the stable complex profile. If the two partition numbers are not the same, PDC sends this chassis code and resets the partition for reconfiguration.

The data field is the partition number from the partition configuration data.

Probable Cause / Recommended Action:

Cause:

The system utilities did not update ICM to contain the partition configuration data for this cell's partition. ICM is corrupted and the utilities system cannot write a corrected partition configuration data to the cell

Action:

Make sure the system utilities are working correctly. Make sure that PDH selftests are enabled. Try rebooting the cell. Try pushing a new complex profile to the cell Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180008f060004000
   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      : 0 (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    : 0x000000000000009e
Event 1144

Severity: SERIOUS

Event Summary: Cell has been assigned to partition number not supported by GSP.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PARTITION_NUMBER_IS_NOT_SUPPORTED.

The stable complex profile has a field that tells PDC the maximum number of partitions that the system utilities will support. If PDC finds itself in a partition with a partition number greater than the maximum number of partitions supported by the system utilities, PDC will reset the cell for reconfiguration, allowing another stable complex profile to be pushed out to fix the problem.

Probable Cause / Recommended Action:

Cause:

The stable complex profile contains an illegal partition number for this cell.

Action:

Run SAM and remove the partition with the illegal number.

Event Details:
Chassis Code Encoded Field : 0x180008f060004001
   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      : 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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x000000000000009f
Event 1145

Severity: INFORMATION

Event Summary: Boot actions specify that the AutoBoot processing should stop at BCH.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PATH_SET_TO_GOTO_BCH.

Boot action for the path specifies that the AutoBoot processing should stop at BCH.

Probable Cause / Recommended Action:

Cause:

Forward progress

Action:

None

Event Details:
Chassis Code Encoded Field : 0x18000030a4002000
   Alert Level             : 3 (System blocked waiting for operator input.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 0 (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    : 0x00000000000000a0
Event 1146

Severity: MINORWARNING

Event Summary: Could not retrieve IODC ENTRY INIT entry point for boot device.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PDC_IODC_ENTRY_INIT_ERR.

The PDC Procedure, PDC_IODC failed to retrieve ENTRY INIT. The data in the chassis code is the status from the PDC Procedure call.

Probable Cause / Recommended Action:

Cause:

PDC could not find IODC for the card.

Action:

Make sure that the card is a supported boot device and make sure that the card is installed correctly.

Event Details:
Chassis Code Encoded Field : 0xb8000020a4001063
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries) 
Event 1147

Severity: MINORWARNING

Event Summary: PDC_IODC was unable to find the ENTRY IO entry point for this card.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PDC_IODC_ENTRY_IO_ERR.

The PDC Procedure, PDC_IODC failed to retrieve ENTRY IO. The data in the chassis code is the status from the PDC Procedure call. This chassis code should not be sent in a normal failure. PDC loads the ENTRY INIT entry point first and any failure to load IODC should be detected then.

Probable Cause / Recommended Action:

Cause:

An intermittent failure in an IO card

Action:

Make sure the IO card is seated correctly and is connected to a supported boot device.

Event Details:
Chassis Code Encoded Field : 0xb8000020a4001068
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 6 (implementation dependent)
   Activity Status         : 8 (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 1148

Severity: MINORWARNING

Event Summary: PDC_IODC failed to load the header bytes for card.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PDC_IODC_HEADER_ERR.

PDC_IODC failed to load the header bytes for card.

The data field is the status from the PDC Procedure call.

Probable Cause / Recommended Action:

Cause:

PDC could not find IODC for the card.

Action:

Make sure that the card is a supported boot device and make sure that the card is installed correctly.

Event Details:
Chassis Code Encoded Field : 0x18000020a4002060
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000a3
Event 1149

Severity: CRITICAL

Event Summary: Cell has different Stable Complex Profile sequence ID then core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_A_SEQ_ID_MISMATCH.

PDC checks the sequence ID of the Stable complex profile 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.

The data field contains the stable complex profile sequence ID from the cell that did not match the core cell.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004080
   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         : 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    : 0x00000000000000a4
Event 1150

Severity: CRITICAL

Event Summary: Cell has different Stable Complex Profile checksum then core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_A_XSUM_MISMATCH.

PDC checks the sequence ID of the Stable complex profile 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.

The data field contains the checksum of the slave cell's stable complex profile.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004070
   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         : 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    : 0x00000000000000a5
Event 1151

Severity: CRITICAL

Event Summary: Cell has different Dynamic Complex Profile sequence ID than core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_B_SEQ_ID_MISMATCH.

PDC checks the sequence ID of the Dynamic complex profile 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 sequence ID from the dynamic complex profile for the slave cell that did not match the core cell.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004081
   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         : 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    : 0x00000000000000a6
Event 1152

Severity: CRITICAL

Event Summary: Cell has different Dynamic Complex Profile checksum then core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_B_XSUM_MISMATCH.

PDC checks the checksum of the Dynamic complex profile 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 the checksum of the slave cell's dynamic complex profile.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004071
   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         : 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    : 0x00000000000000a7
Event 1153

Severity: CRITICAL

Event Summary: Cell has different Partition Config Data sequence ID then core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_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 the sequence ID of the partition configuration data for the slave cell.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004082
   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         : 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    : 0x00000000000000a8
Event 1154

Severity: CRITICAL

Event Summary: Cell has different Partition Config Data checksum then core cell.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_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 the checksum for the PD profile of the slave cell.

Probable Cause / Recommended Action:

Cause:

The core cell detected that a cell in its partition has a different complex profile than it does.

Action:

Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.

Event Details:
Chassis Code Encoded Field : 0x180000f060004072
   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         : 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    : 0x00000000000000a9
Event 1155

Severity: CRITICAL

Event Summary: PDC detected that cells in partition have different complex profiles.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROFILE_MISMATCH_ERR.

PDC on the core cell checks the sequence IDs and checksums for all of the complex profiles (stable, dynamic and partition data) on each of the cells in the partition. If they do not match the core cell's profiles, 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. This chassis code is a summary of the cells that do not have consistent complex profiles.

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 indicates that the cell has a complex profile that did not match.

Probable Cause / Recommended Action:

Cause:

The complex profiles for the slaves cells in the partition do not match the complex profiles on the core cell.

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 : 0x180000f06000406f
   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      : 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               : 3 (actual data)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000aa
Event 1156

Severity: SERIOUS

Event Summary: Unable to write alive set to all coherency controllers in partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROG_PD_IN_DNA_ERR.

Once PDC in the core cell has determined which cells are going to make it into the partition, it programs the coherency controllers on each of the slave cells and its own cell. If the write to the cell fails, PDC will send this chassis code, which contains, in the data field, the status from the function that failed to write to the coherency controllers.

Probable Cause / Recommended Action:

Cause:

A Coherency controller (CC) in the partition failed a read after write test.

Action:

Reboot the partition. Look for chassis codes that indicate a primary or secondary CC error.

Event Details:
Chassis Code Encoded Field : 0x180000f0a20020af
   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      : 10 (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    : 0x00000000000000ab
Event 1157

Severity: SERIOUS

Event Summary: Failed while writing coherency set registers in coherency controller.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_PROGRAM_PD_COH_SET_ERR.

Once PDC in the core cell has determined which cells are going to make it into the partition, it programs the coherency controllers on each of the slave cells and its own cell. If the write to the cell fails, PDC will send this chassis code, which contains, in the data field, the status from the function that failed to write to the coherency controllers.

Probable Cause / Recommended Action:

Cause:

A coherency controller (CC) in the partition failed a read after write test.

Action:

Reboot the partition. Look for chassis codes that indicate a primary or secondary CC error.

Event Details:
Chassis Code Encoded Field : 0x180000f0a20020a0
   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      : 10 (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    : 0x00000000000000ac
Event 1158

Severity: SERIOUS

Event Summary: The speed bin bits are not set correctly for the CPU.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_RDR13_PA8500_SPEED_BIN_BIT_CLEAR.

During the Manufacturing process, CPUs are supposed to have their speed related bits in RDR13 programmed to indicate the capability of the CPU. The PA8500 speed bin bit is supposed to be cleared during manufacturing of the CPU. This chassis log indicates that PDC detected that the speed bin bit was not programmed correctly, and then PDC halts the cell.

Data Field:

Physical location of CPU

Probable Cause / Recommended Action:

Cause:

Mistake in manufacturing of the CPU.

Action:

Contact HP Support personnel to troubleshoot the CPU

Event Details:
Chassis Code Encoded Field : 0x200000f09f000193
   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         : 0 (unspecified)
   Caller Subactivity      : 25 (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:   0x00000000000000ad
   FRU Source          = 10 (protection domain)
   Source Detail       = 13 (unknown)
   ! !
   ! !
   ! !
Event 1159

Severity: MAJORWARNING

Event Summary: Processor id bit is not programmed correctly in the processor.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_RDR13_REPORTS_NOT_PA8600.

PDC expects the CPU to be a PA-8600, but the bits in RDR13 of the CPU were not programmed to indicate that the CPU is a PA-8600. This chassis log indicates that PDC detected this CPU manufacturing error, and then PDC halts the cell.

Data Field:

Physical location of CPU

Probable Cause / Recommended Action:

Cause:

Mistake in manufacturing of the CPU.

Action:

Contact HP Support personnel to troubleshoot the CPU

Event Details:
Chassis Code Encoded Field : 0x200000f09f000191
   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         : 0 (unspecified)
   Caller Subactivity      : 25 (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:   0x00000000000000ae
   FRU Source          = 10 (protection domain)
   Source Detail       = 14 (unknown)
   ! !
   ! !
   ! !
 
Event 1160

Severity: SERIOUS

Event Summary: Speed bin bit is not programmed correctly in the processor.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_RDR13_SD_SPEED_BIN_BIT_SET.

The Superdome speed bin was unused for Superdome. This bit should be clear. PDC detected that this Superdome speed bin bit was set. This was a CPU manufacturing error, and PDC then halts the cell after putting out the chassis log.

Probable Cause / Recommended Action:

Cause:

Mistake in the manufacturing of the CPU.

Action:

Contact HP Support personnel to troubleshoot the CPU

Event Details:
Chassis Code Encoded Field : 0x200000f09f000192
   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         : 0 (unspecified)
   Caller Subactivity      : 25 (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:   0x00000000000000af
   FRU Source          = 10 (protection domain)
   Source Detail       = 15 (unknown)
   ! !
   ! !
   ! !
 
Event 1161

Severity: SERIOUS

Event Summary: PDC could not read the time of day on the RTC.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_READ_TOD_FAILED.

PDC could not read the time of day (TOD) on the real time clock (RTC). Data field contains the status returned from the attempt to read the TOD.

Probable Cause / Recommended Action:

Cause:

Semaphore problem.

Action:

Contact HP Support personnel to troubleshoot the cell board (suspect Dillon chip) Check for PDC upgrade for possible internal software problem

Event Details:
Chassis Code Encoded Field : 0xb80000c0a20000f0
   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      : 15 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries) 
Event 1162

Severity: MINORWARNING

Event Summary: PDC attempted to boot using a boot device and failed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_SELECTED_PATH_FAILED.

PDC attempted to use a boot device and failed. The data in this chassis code is the status from the code that attempted to initialize the boot device.

Probable Cause / Recommended Action:

Cause:

There was a problem using the boot device.

Action:

Look for other chassis codes sent before this one that indicate why the boot device failed.

Event Details:
Chassis Code Encoded Field : 0xb8000020a4002004
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 0 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1163

Severity: CRITICAL

Event Summary: Slave cell picked a different core cell than the one that wrote to it.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_SLAVE_CELL_SPLIT_BRAIN.

The slave cells wait for the core cell to write its cell number to their micro general-purpose register 1. When the slaves see that the core cell has written its cell number to this register, it compares the core cell number in the micro general-purpose register 1 with the core cell that was selected by the slave cell. If the core cells don't match, then the slave cell knows that there is a split-brain problem where the cells did not rendezvous properly.

Data Field:

The core cell that wrote its number to this cell's micro general-purpose register 1.

Probable Cause / Recommended Action:

Cause:

There is a split brain problem.

Action:

Look for fabric problems. Contact the PDC team if this can't be resolved

Event Details:
Chassis Code Encoded Field : 0x180000f0a2004090
   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      : 9 (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    : 0x00000000000000b2
Event 1164

Severity: MAJORWARNING

Event Summary: Slave CPU has noticed the monarch CPU has failed and will deconfig it.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_SLAVE_SEES_MON_FAILED.

A slave CPU has noticed that the monarch CPU has failed and will deconfigure it. The cell will be reset.

Probable Cause / Recommended Action:

Cause:

The monarch CPU has failed. A slave CPU has noticed this and will deconfigure the monarch CPU and reset the cell.

Action:

Contact HP Support personnel to troubleshoot the cell board.

Event Details:
Chassis Code Encoded Field : 0x180000009f00040b
   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         : 0 (unspecified)
   Caller Subactivity      : 64 (implementation dependent)
   Activity Status         : 11 (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    : 0x00000000000000b3
Event 1165

Severity: SERIOUS

Event Summary: Testing the Reset Status register in Dillon failed.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_TEST_RESET_STATUS_REG_ERR.

Testing the Reset Status register in Dillon failed. PDC was unable to correctly write and read a test pattern to the register.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

PDC cannot communicate properly to the Dillon.

Action:

Contact HP Support personnel to troubleshoot the cell board

Event Details:
Chassis Code Encoded Field : 0x000000f23500100f
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 3 (PDH)
   Source FRU Detail       : 5 (platform registers)
   Source ID               : 0 (platform dependent)
   Event Detail            : 2 (write error)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 0 (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               : 0 (data field unused)
   Message ID              : 0 (not associated with other log entries)
Event 1166

Severity: MAJORWARNING

Event Summary: Cell is not configured in partition.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_THIS_CELL_NOT_CONFIGURED_IN_PD.

The cell is not configured into this partition.

The data field has the physical location of the suspect cell

Probable Cause / Recommended Action:

Cause:

Cell was not configured into the partition

Action:

Reset partition

Event Details:
Chassis Code Encoded Field : 0x20000000a200c016
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   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      : 1 (implementation dependent)
   Activity Status         : 6 (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:   0x00000000000000b5
   FRU Source          = 11 (unknown)
   Source Detail       = 5 (unknown)
Event 1167

Severity: MAJORWARNING

Event Summary: Other cells in partition did not create local rendezvous set in time.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_TIMEOUT_CREATING_GLOBAL_RENDEZ_SET.

PDC creates a rendezvous set that consists of all of the cells that can communicate bilaterally. Each cell has to do this at the same time. If some of the cells do not create their local rendezvous set and make it available to the other cells in time for them to make their rendezvous set, the cells that are waiting will timeout and send this chassis code. The data field of the chassis code contains the cells that delivered their local rendezvous set in time.

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 indicates that the cell delivered its local rendezvous set in time.

Probable Cause / Recommended Action:

Cause:

Some of the cells in the partition did not deliver their local rendezvous set in time.

Action:

Look at the data field of the chassis code. Find the cells that are configured to be in the PD that did not deliver their rendezvous set in time and look for problems in those cells

Event Details:
Chassis Code Encoded Field : 0x200000f0a200c026
   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         : 6 (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:   0x00000000000000b6
   FRU Source          = 11 (unknown)
   Source Detail       = 6 (unknown)
Event 1168

Severity: MAJORWARNING

Event Summary: Unable to access the complex serial number in profile.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNABLE_TO_ACCESS_CMPLX_A_SERIAL_NUM.

Unable to access the complex serial number which is stored in the Stable Complex Profile

Probable Cause / Recommended Action:

Cause:

Failure to read complex profile Failure in GSP

Action:

Reset cell Reset GSP

Event Details:
Chassis Code Encoded Field : 0x000000009f0013d3
   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      : 61 (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 1169

Severity: MINORWARNING

Event Summary: PDC was unable to convert the path to PCI Functional Address (PFA).

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNABLE_TO_FIND_PFA_FOR_PATH.

PDC was unable to convert the path to PCI Functional Address (PFA). PFAs are used to configure PCI cards.

Probable Cause / Recommended Action:

Cause:

A failure in the I/O chassis or in the card. No card is installed for the path.

Action:

Look for problems with the I/O chassis or the PCI card. Make sure a card is installed and that the path is correct.

Event Details:
Chassis Code Encoded Field : 0x18000020a4002051
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 10 (protection domain)
   Source FRU Detail       : 4 (boot device)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 5 (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    : 0x00000000000000b8
Event 1170

Severity: MAJORWARNING

Event Summary: Indicates that this CPU is of a revision greater than expected.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNEXPECTED_CPU_REV.

This should not be possible unless there is a roll to the CPUs, to produce a PA-8600 rev 3.2 or greater

Probable Cause / Recommended Action:

Cause:

Unexpected revision of CPU found

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x880000209f001043
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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               : 17 (revision number)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000b9
Event 1171

Severity: MAJORWARNING

Event Summary: A CPU with an unknown CPU revision was detected.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNKNOWN_CPU_REV.

A CPU with an unknown CPU revision was detected. The CPU will be deconfigured.

The BOOT_UNKNOWN_CPU_REV_CPU chassis code indicates the CPU number of the suspect CPU.

Data Field:

CPU revision number

Probable Cause / Recommended Action:

Cause:

A CPU with an unknown CPU revision was detected. Either an incorrect CPU has been installed or the current revision of PDC doesn't recognize these CPU revision.

Action:

Use FWUU to update PDC Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x880000209f001041
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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               : 17 (revision number)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000ba
Event 1172

Severity: MAJORWARNING

Event Summary: A CPU with an unknown CPU revision was detected.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNKNOWN_CPU_REV_CPU.

A CPU with an unknown CPU revision was detected. The CPU will be deconfigured. The BOOT_UNKNOWN_CPU_REV chassis code that follows this will report the unknown CPU revision number.

Data Field:

CPU number

Probable Cause / Recommended Action:

Cause:

A CPU with an unknown CPU revision was detected. Either an incorrect CPU has been installed or the current revision of PDC doesn't recognize these CPU revision.

Action:

Use FWUU to update PDC Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x180000209f001041
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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    : 0x00000000000000bb
Event 1173

Severity: MAJORWARNING

Event Summary: Indicates that this CPU is not a supported revision.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNSUPPORTED_CPU_REV.

PDC checks for PA-8600 rev 3.1 in two different places. At the end of early selftests, PDC will put out this chassis log for non PA-8600 3.1 processors but still allow the cell to boot with that CPU. Immediately after early selftests, PDC ends up checking for this again if and only the cell is NOT in MFG mode. If not in MFG mode and the CPU revision is something from before PA-8600 rev 3.1, this chassis log will be thrown and this cell will be halted. If in MFG mode, PDC will not check for PA-8600 rev 3.1, but PDC will still check for homogeneous CPUs.

Data Field:

CPU Revision

Probable Cause / Recommended Action:

Cause:

A CPU earlier than PA-8600 rev 3.1 is installed in the cell.

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x880000209f001042
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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               : 17 (revision number)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000bc
Event 1174

Severity: MAJORWARNING

Event Summary: The physical location of the CPU that has a CPU rev less than 3.1.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_UNSUPPORTED_CPU_REV_PHYS_LOC.

The physical location of the CPU that has a CPU rev less than 3.1

Probable Cause / Recommended Action:

Cause:

Wrong CPU was installed in the cell.

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x200000209f001042
   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            : 0 (unknown)
   Caller Activity         : 1 (test)
   Caller Subactivity      : 4 (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:   0x00000000000000bd
   FRU Source          = 11 (unknown)
   Source Detail       = 13 (unknown)
Event 1175

Severity: MINORWARNING

Event Summary: The CPU Speed has been set to a default value.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_USING_DEFAULT_CPU_SPEED.

The CPU Speed has been set to default value. The value in the data field indicates the condition that has caused the CPU speed to be set to a default value. Previous chassis code will also indicate the condition.

Data Field:

1 - The clock generation chip type is unsupported. See the previous BOOT_CGC_TYPE_UNSUPPORTED chassis code for more information.

2 - An invalid value was found on the frequency select pins. See the previous BOOT_CGC_FREQ_SELECT chassis code for more information.

3 - An invalid input frequency to the clock generation chips was specified. This could be caused by the GSP returning an incorrect value. See the previous BOOT_CGC_INPUT_FREQUENCY chassis code for more information.

4 - Unable to tabulate a CPU speed. See the previous BOOT_CPU_SPEED_TABULATED for more information.

Probable Cause / Recommended Action:

Cause:

The reason for the CPU setting to a default value is can be determined from the value in the data field and previous chassis codes.

Action:

Review previous chassis codes, based on data field value and take appropriate action. Data Field Value: 1 - The clock generation chip type is unsupported. See the previous BOOT_CGC_TYPE_UNSUPPORTED chassis code for more information. 2 - An invalid value was found on the frequency select pins. See the previous BOOT_CGC_FREQ_SELECT chassis code for more information. 3 - An invalid input frequency to the clock generation chips was specified. This could be caused by the GSP returning an incorrect value. See the previous BOOT_CGC_INPUT_FREQUENCY chassis code for more information. 4 - Unable to tabulate a CPU speed. See the previous BOOT_CPU_SPEED_TABULATED for more information.

Event Details:
Chassis Code Encoded Field : 0x180000809f0020d4
   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      : 13 (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    : 0x00000000000000be
Event 1176

Severity: SERIOUS

Event Summary: Error occurred while writing CPU speed to processor state structure.

Event Class: System

Problem Description:
Chassis Code Keyword BOOT_WRITE_CPU_SPEED_ERROR.

An error occurred while writing the CPU speed to processor state structure. This is most likely a scratch RAM (SCRAM) error. The CPU will be halted.

Data Field:

CPU physical location

Probable Cause / Recommended Action:

Cause:

An error in the scratch RAM on the cell board which contains the CPU

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x200000f01100209f
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 1 (processor)
   Source FRU Detail       : 1 (processor general)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (config)
   Caller Subactivity      : 9 (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:   0x00000000000000bf
   FRU Source          = 11 (unknown)
   Source Detail       = 15 (unknown)
Event 1177
Severity: MAJORWARNING

Event Summary: 48 Volt Converter Failed.

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

A 48 Volt DC Converter powered by the specified PDCA failed on the designated Bulk Power Supply.

The PDCA powering the converter on the BPS that failed can be identified by the activity status (last byte of chassis code):
        e = PDCA 1
        f = PDCA 0
Probable Cause / Recommended Action:

Cause:

The 48 Volt DC Converter powered by the PDCA identified failed in the named Bulk Power Supply.

Action:

Contact HP Support personnel to troubleshoot problem

Cause:

The PDCA identified has failed. This will be evident by many BPS_FAIL codes and probably a AC_DELETED code in the Event Log.

Action:

Contact HP Support personnel to troubleshoot problem
Event Details:
Chassis Code Encoded Field : 0x2420086a4400403e
   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       : 4 (high voltage DC power)
   Source ID               : 0 (platform dependent)
   Event Detail            : 10 (failed or disconnected)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (high voltage power supply)
   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:   0x00000000000000c0
   FRU Source          = 12 (unknown)
   Source Detail       = 0 (unknown, no source stated)
Event 1178
Severity: MAJORWARNING

Event Summary: 5 Volt Converter Failed.

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

The 5 Volt DC Converter powered by the specified PDCA failed on the designated Bulk Power Supply.

The PDCA powering the converter on the BPS that failed can be identified by the activity status (last byte of chassis code):
        e = PDCA 1
        f = PDCA 0
Probable Cause / Recommended Action:

Cause:

The 5 Volt Converter on the BPS power by the specified PDCA has failed.

Action:

Contact HP Support personnel to troubleshoot problem

Cause:

The specified PDCA has failed. This will be evident by many BPS_FAIL codes and probably a AC_DELETED code in the Event Log.

Action:

Contact HP Support personnel to troubleshoot problem
Event Details:
Chassis Code Encoded Field : 0x2420086a4500403e
   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       : 5 (housekeeping)
   Source ID               : 0 (platform dependent)
   Event Detail            : 10 (failed or disconnected)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (high voltage power supply)
   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:   0x00000000000000c1
   FRU Source          = 12 (unknown)
   Source Detail       = 1 (unknown)
Event 1179

Severity: MAJORWARNING

Event Summary: Fan failed in designated Bulk Power Supply.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_FAIL_FANFLT.

The designated Bulk Power Supply is reporting its fan has failed.

Probable Cause / Recommended Action:

Cause:

Fan failure or fan obstructed

Action:

If fan is obstructed, remove obstruction. If no obstruction, Contact HP Support personnel to troubleshoot problem.

Event Details:
Chassis Code Encoded Field : 0x242008624400403f
   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       : 4 (high voltage DC power)
   Source ID               : 0 (platform dependent)
   Event Detail            : 2 (fan underspeed)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x00000000000000c2
   FRU Source          = 12 (unknown)
   Source Detail       = 2 (unknown)
Event 1180
Severity: MAJORWARNING

Event Summary: 1 Side Converter Over Temp.

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

The 48 Volt DC Converter powered by the specified PDCA in the designated Bulk Power Supply, is in over temp condition.

The PDCA powering the converter on the BPS that failed can be identified by the activity status (last byte of chassis code):
        e = PDCA 1
        f = PDCA 0
Probable Cause / Recommended Action:

Cause:

If this code is not accompanied by other codes pointing to the same Bulk Power Supply, then it is an internal component failure.

Action:

Contact HP Support personnel to troubleshoot problem.

Cause:

If there are chassis codes indicating an elevated ambient air temperature, other chassis codes will be generated and system shutdown will be necessary.

Action:

Resolve the elevated ambient air temperature problem as quickly as possible. If the air temperature gets too high, the complex must be shutdown to avoid damage.
Event Details:
Chassis Code Encoded Field : 0x242008614400403e
   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       : 4 (high voltage DC power)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (supply overtemperature)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (high voltage power supply)
   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:   0x00000000000000c3
   FRU Source          = 12 (unknown)
   Source Detail       = 3 (unknown)
Event 1181

Severity: INFORMATION

Event Summary: Previously failed Bulk Power Supply is now functioning.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_FUNCTIONING.

A Bulk Power Supply that showed an error status, has cleared the error and is now functioning properly.

Probable Cause / Recommended Action:

Cause:

A failed supply is now functioning properly.

Action:

None. Monitor and check error logs for previous occurrences. If previous occurrence(s) on same Bulk Power Supply, replace designated Bulk Power Supply following Bulk Power Supply Remove & Replace Procedures.

Event Details:
Chassis Code Encoded Field : 0x2420081b4400403f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 0 (platform dependent)
   Event Detail            : 11 (functioning)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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               : 4 (physical location)
   Message ID              : 0 (not associated with other log entries) 
FRU Physical Location:   0x00000000000000c4
   FRU Source          = 12 (unknown)
   Source Detail       = 4 (unknown)
Event 1182

Severity: MINORWARNING

Event Summary: Bulk Power Supplies are not Redundant.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_NOT_REDNDNT.

The number of functioning Bulk Power Supplies has decreased to where the Cabinet Power supplied (number of available Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed is greater than 0, but less than the output of one Bulk Power Supply.

Probable Cause / Recommended Action:

Cause:

Entities were added to the cabinet, increasing the estimated Power Consumption. Or, a non-functional GSP bus entity has become functional, providing previously missing power consumption information.

Action:

Purchase and install a Bulk Power Supply, if redundancy is desired.

Cause:

Bulk Power Supply failed.

Action:

Contact HP Support personnel to troubleshoot problem.

Event Details:
Chassis Code Encoded Field : 0x0420081d44ff403f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 255 (platform dependent)
   Event Detail            : 13 (non-redundant)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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 1183

Severity: CRITICAL

Event Summary: +48V DC has exceeded its upper limit.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_OVERVOLTAGE.

The PM3 has received a fault condition over the I2C bus from one or more Bulk Power Supplies failing +48VDC and shutting down from an over voltage error. The PM3 may issue a POWER_OVERLOAD chassis code, depending on the amount of available Cabinet Power.

Probable Cause / Recommended Action:

Cause:

One or more Bulk Power Supplies failed in an over voltage condition.

Action:

Contact HP Support personnel to troubleshoot problem.

Event Details:
Chassis Code Encoded Field : 0x042008e544ff403f
   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            : 5 (output overvoltage)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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 1184

Severity: INFORMATION

Event Summary: Number of Bulk Power Supplies is redundant.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_REDUNDANT.

The number of functioning Bulk Power Supplies was increased to where the Cabinet Power supplied (number of Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed is equal to or greater than the power output of one Bulk Power Supply.

Probable Cause / Recommended Action:

Cause:

One or more Bulk Power Supplies were installed, or, one or more entities were removed.

Action:

None

Event Details:
Chassis Code Encoded Field : 0x0420081c44ff403f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 255 (platform dependent)
   Event Detail            : 12 (redundant)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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 1185

Severity: CRITICAL

Event Summary: +48V DC has exceeded its lower limit.

Event Class: System

Problem Description:
Chassis Code Keyword BPS_UNDRVOLTAGE.

The PM3 has received a fault condition over the I2C bus from one or more Bulk Power Supplies failing +48VDC and shutting down from an under voltage error. This may be caused by a "brownout" condition, also.

Probable Cause / Recommended Action:

Cause:

One or more Bulk Power Supplies has failed in an under voltage condition.

Action:

Contact HP Support personnel to troubleshoot problem.

Event Details:
Chassis Code Encoded Field : 0x042008e444ff403f
   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            : 4 (output undervoltage)
   Caller Activity         : 4 (monitor)
   Caller Subactivity      : 3 (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 1186

Severity: CRITICAL

Event Summary: Cabinet Power Turned Off By Command.

Event Class: System

Problem Description:
Chassis Code Keyword CABPWR_OFF.

The +48 VDC Power was turned off by the Guardian Service Processor Command, PE, or the cabinet power switch was moved to the "OFF" position. This powers down the cabinet immediately. Thus, the critical severity level.

Probable Cause / Recommended Action:

Cause:

Someone issued the PE-Cabinet off command.

Action:

Guardian Service Processor Command PE - Cabinet - On with switch in on position.

Cause:

Cabinet switch was transitioned to "OFF".

Action:

Cycle power switch from on to off to on.

Event Details:
Chassis Code Encoded Field : 0x0420082944ff302f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 255 (platform dependent)
   Event Detail            : 9 (power off)
   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 1187

Severity: INFORMATION

Event Summary: Cabinet Power Turned On By Command.

Event Class: System

Problem Description:
Chassis Code Keyword CABPWR_ON.

Cabinet Power Turned On By Command

Probable Cause / Recommended Action:

Cause:

Someone issued the PE-Cabinet On command. Cabinet switch was transitioned to "On"

Action:

None

Event Details:
Chassis Code Encoded Field : 0x0420081844ff302f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 4 (power entity)
   Source FRU Detail       : 4 (high voltage DC power)
   Source ID               : 255 (platform dependent)
   Event Detail            : 8 (power on)
   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 1188

Severity: INFORMATION

Event Summary: Chassis Code incoming FIFO is full.

Event Class: System

Problem Description:
Chassis Code Keyword CCI_FULL.

The buffer (FIFO) holding incoming reflected chassis codes is full. The cell utilities hardware signals the PDC the buffer is full by setting a bit in the Dillon Micro Status Register.

Probable Cause / Recommended Action:

Cause:

The PDC is hung and not reporting to the CCI work bit or the reflected chassis codes are coming in so fast the PDC can't respond fast enough.

Action:

Look for failure information within the partition as to why PDC would hang or not respond quickly. If this is the first occurrence, Reset. If more than once, replace cell board. The physical location in the chassis code should point to a root cell.

Event Details:
Chassis Code Encoded Field : 0x2060082035002fcf
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 3 (PDH)
   Source FRU Detail       : 5 (platform registers)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 252 (unknown)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 6 (PDH controller)
   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:   0x00000000000000cb
   FRU Source          = 12 (unknown)
   Source Detail       = 11 (unknown)
Event 1189

Severity: MINORWARNING

Event Summary: Named Cell Was Installed.

Event Class: System

Problem Description:
Chassis Code Keyword CELL_ADDED.

The named cell was physically installed in the system.

Probable Cause / Recommended Action:

Cause:

The cell board was physically inserted into an empty cell slot in the SPU card cage. This is a normal chassis code during an OL* event.

Action:

If OL*, run appropriate tests, reset, and bring on line. If not, no further action may be required.

Event Details:
Chassis Code Encoded Field : 0x24200811940050ef
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 9 (cell)
   Source FRU Detail       : 4 (cell board)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (added)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 14 (cell board)
   Activity Status         : 15 (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:   0x00000000000000cc
   FRU Source          = 12 (unknown)
   Source Detail       = 12 (unknown)
Event 1190

Severity: MINORWARNING

Event Summary: Clock Margined Externally.

Event Class: System

Problem Description:
Chassis Code Keyword CLOCK_MARGIN_EXTERNAL.

The cabinet clocks were margined to under the control of an external device (special test equipment).

Probable Cause / Recommended Action:

Cause:

For troubleshooting some intermittent errors, clock margining can be an effective tool. An engineer decided to use external equipment to margin outside the normal margin limits built into the machine.

Action:

Upon completion, use "CM" command to ensure clocks are set to normal.

Event Details:
Chassis Code Encoded Field : 0x0050082061002f8f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 248 (unknown)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   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 1191

Severity: MINORWARNING

Event Summary: Cabinet Clock Margined To High.

Event Class: System

Problem Description:
Chassis Code Keyword CLOCK_MARGIN_HIGH.

The cabinet clocks were margined to high by the MFG level GSP command "CM".

Probable Cause / Recommended Action:

Cause:

"CM" command was executed, setting cabinet clocks to 5% above normal range for troubleshooting purposes. The "CM" command is a MFG level GSP command.

Action:

When finished at high margin, use "CM" command and return clocks to normal or normal setting.

Event Details:
Chassis Code Encoded Field : 0x005008206100208f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 8 (clock margin high)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   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 1192

Severity: MINORWARNING

Event Summary: Cabinet Clock Margined Normal.

Event Class: System

Problem Description:
Chassis Code Keyword CLOCK_MARGIN_NORMAL.

The cabinet clocks were margined to normal by the MFG level GSP command "CM".

Probable Cause / Recommended Action:

Cause:

"CM" command was executed, returning cabinet clocks to normal frequency. The "CM" command is a MFG level GSP command.

Action:

None

Event Details:
Chassis Code Encoded Field : 0x005008206100209f
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 9 (clock margin normal)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   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 1193

Severity: INFORMATION

Event Summary: CLU Firmware Updating.

Event Class: System

Problem Description:
Chassis Code Keyword CLU_FIRMWARE_UPDATE.

The firmware on the CLU portion of the UGUY named in the Chassis Code is being updated. This will reset the CLU Microprocessor (SARG) upon completion and may affect all partitions in the left/right cabinet combination.

Probable Cause / Recommended Action:

Cause:

Firmware Revision on CLU portion of Utilities Board was not the proper revision.

Action:

None

Event Details:
Chassis Code Encoded Field : 0x205008106aff701f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 10 (CLU)
   Source ID               : 255 (platform dependent)
   Event Detail            : 0 (no problem detail)
   Caller Activity         : 7 (utility)
   Caller Subactivity      : 1 (firmware update)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   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:   0x00000000000000d0
   FRU Source          = 13 (unknown)
   Source Detail       = 0 (unknown, no source stated)
Event 1194

Severity: CRITICAL

Event Summary: Watchdog Timer Expired.

Event Class: System

Problem Description:
Chassis Code Keyword CLU_WATCHDOG_RESET.

The Watchdog Timer checks for inactivity, or hung state, of the Cabinet Level Utilities (CLU) portion of the Utilities Board. During activity, the timer is continually reset. If the timer expires, it will automatically reset the CLU microprocessor. This will not affect running partitions.

Probable Cause / Recommended Action:

Cause:

Hardware or firmware failure on the Utilities Board.

Action:

Check revision of CLU firmware. If out of date, or known bad revision, use FWUU to update CLU firmware. Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x205008d46aff2fef
   Alert Level             : 13 (System hang detected via timer popping.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 10 (CLU)
   Source ID               : 255 (platform dependent)
   Event Detail            : 4 (internal failure)
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 254 (unknown)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   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:   0x00000000000000d1
   FRU Source          = 13 (unknown)
   Source Detail       = 1 (unknown)
Event 1195

Severity: INFORMATION

Event Summary: A distribution of the complex profile is about to occur.

Event Class: System

Problem Description:
Chassis Code Keyword CMPLX_PROFIL_DIST_PEND.

One or more partitions were reconfigured by SAM and the GSP is waiting for shutdown to distribute the new complex profile to the affected cells.

Probable Cause / Recommended Action:

Cause:

Customer reconfigured one or more partitions via SAM. Once the OS shuts down, the new profile will be distributed to the affected cells. Once the affected cells are booting, the new profile is distributed to the rest of the cells.

Action:

None

Event Details:
Chassis Code Encoded Field : 0xb010081339005010
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 3 (PDH)
   Source FRU Detail       : 9 (complex profile)
   Source ID               : 0 (platform dependent)
   Event Detail            : 3 (distribution awaiting shutdown)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 1 (protection domain)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 22 (implementation dependent data field)
   Message ID              : 0 (not associated with other log entries) 
 
Event 1196

Severity: CRITICAL

Event Summary: Copy of complex profile on sub and cells don't match.

Event Class: System

Problem Description:
Chassis Code Keyword CMPLX_PROFIL_INCOHERENT.

The complex profile is stored in NVRAM on the GSP and each cell. All copies must match. For this error to be generated, not only is the GSP's copy of the complex profile invalid, but not all of the cell's copies match.

Probable Cause / Recommended Action:

Cause:

GSP NVRAM was erased by removing GSP from system without setting "NVRAM SAVE" switch to on. GSP was replaced with cabinet's AC Breakers "off". Either of first two causes and replacing or installing a cell board with cabinet's AC Breakers "off".

Action:

Remove cell board causing problem. Power complex on and allow cells to distribute their copy of complex profile to GSP, then add new cell following proper OLA procedures. Remove improper cell board. Execute GSP Handler "CC" command and choose "Last Profile". This will load the sub with what should be the same copy as the cells. Then add new cell board.

Event Details:
Chassis Code Encoded Field : 0x001008f139005010
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 3 (PDH)
   Source FRU Detail       : 9 (complex profile)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (incoherent)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 1 (protection domain)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   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 1197

Severity: INFORMATION

Event Summary: GSP Reset button was pressed.

Event Class: System

Problem Description:
Chassis Code Keyword DFLT_CNFG_BUTT_PRESSED.

The button on the GSP (Guardian Service Processor) was pressed, resetting all GSP configuration parameters to default settings.

Probable Cause / Recommended Action:

Cause:

The default configuration button was pressed.

Action:

The GSP configuration parameters must be re-entered. Probable GSP commands are: AR, CA, IT, LL, PD, PG, SO, VFC.

Event Details:
Chassis Code Encoded Field : 0x0010084566ff50d0
   Alert Level             : 4 (Unexpected configuration change detected.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 6 (service processor)
   Source ID               : 255 (platform dependent)
   Event Detail            : 5 (default config used)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 13 (service processor)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   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 1198

Severity: MINORWARNING

Event Summary: Front EMI Shield has been removed.

Event Class: System

Problem Description:
Chassis Code Keyword DOOR_OPENED.

The front EMI shield of the named processor cabinet has been removed. This changes the air flow characteristics and could result in overheating some components if left open too long. The EMI shield not only contains EMI emissions, but acts as an air dam.

Probable Cause / Recommended Action:

Cause:

Shield was removed for service.

Action:

Complete service and replace shield promptly.

Cause:

Switch is malfunctioning.

Action:

Troubleshoot switch and connections.

Event Details:
Chassis Code Encoded Field : 0x042008476100400f
   Alert Level             : 4 (Unexpected configuration change detected.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 7 (door opened)
   Caller Activity         : 4 (monitor)
   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 1199

Severity: CRITICAL

Event Summary: Duplicate cabinet number detected.

Event Class: System

Problem Description:
Chassis Code Keyword DUPLICATE_CABINET.

The GSP detected 2 or more cabinets with the same cabinet number.

Probable Cause / Recommended Action:

Cause:

When adding a new cabinet to the complex or replacing the UGUY, the cabinet number switch was set to a number already in use.

Action:

Turn off AC breakers to cabinet with duplicate number. Check all other cabinet numbers in the complex for validity. Set cabinet number switch on UGUY-PCB in new cabinet (s) to proper cabinet number. Turn on AC breakers for cabinet(s).

Event Details:
Chassis Code Encoded Field : 0x201008f9610050ef
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 1 (cabinet)
   Source ID               : 0 (platform dependent)
   Event Detail            : 9 (duplicate ID)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 14 (cabinet)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   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:   0x00000000000000d6
   FRU Source          = 13 (unknown)
   Source Detail       = 6 (unknown)
Event 1200

Severity: CRITICAL

Event Summary: Invalid checksum from EEPROM.

Event Class: System

Problem Description:
Chassis Code Keyword EEPROM_INVALID_CKSM.

An invalid checksum was received when reading the FRUID EEPROM for the device named in the chassis code. If this is a single error, the fault lies with the named FRU. If there are many INVALID_CKSM entries in the Event Log, there is probably a problem with the I2C bus.

Probable Cause / Recommended Action:

Cause:

Data corrupted in the named EEPROM.

Action:

If this is a single entry, replace the FRU.

Cause:

Problem with I2C bus.

Action:

If every entity with a FRUID logs an error, the problem is probably with the CLU portion of the Utilities Board. Replace the Utilities Board following the Utilities Board Remove & Replace Procedures. If there are a few entities reporting checksum errors, but several have reported in properly, chances are one device is causing the problem with the I2C bus. This will take a more concerted effort to find and correct that problem. Probably wish to take the bus to a minimum configuration and test, add, test until the failure is verified.

Event Details:
Chassis Code Encoded Field : 0xb05008f46aff20af
   Alert Level             : 15 (Fatal hardware or configuration problem
   prevents operation.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 10 (CLU)
   Source ID               : 255 (platform dependent)
   Event Detail            : 4 (internal failure)
   Caller Activity         : 2 (operation)
   Caller Subactivity      : 10 (read FRUID)
   Activity Status         : 15 (implementation dependent)
   Reporting Entity Type   : 5 (cabinet controller)
   Reporting Entity ID     : 0 Cabinet 0 Cell 0 CPU 0 
   Data Type               : 22 (implementation dependent data field)
   Message ID              : 0 (not associated with other log entries)
Event 1201

Severity: SERIOUS

Event Summary: Unexpected software path has been taken.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_ASSERT.

A software error has occurred.

Data field consists of file number and line number. Lab involvement is indicated.

Probable Cause / Recommended Action:

Cause:

System Firmware design or code bug is likely.

Action:

Contact the Response Center to report defect Upgrade PDC firmware

Event Details:
Chassis Code Encoded Field : 0x400008c00000600f
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 0 (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               : 8 (code address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000d8
Event 1202

Severity: INFORMATION

Event Summary: Cannot access PDH on another cell.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_CANNOT_REACH_CELL.

Before PD crash rendezvous, connectivity between cells is checked by attempting to access PDH on each cell in the PD.

The data field contains the physical location of the cell that cannot be reached. A fabric error is likely. Cell halt due to fabric loss of lockstep may follow.

Probable Cause / Recommended Action:

Cause:

Loss of fabric connectivity or the other cell is not present/alive.

Action:

Check the fabric for errors Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x20000800000064dc
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 77 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000d9
   FRU Source          = 13 (unknown)
   Source Detail       = 9 (unknown)
Event 1203

Severity: CRITICAL

Event Summary: An HPMC has been encountered.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_CHECK_HPMC.

Each CPU will send this code early in the PDC HPMC handler, as soon as the cause of the machine check is determined to be HPMC.

The data field contains the interrupt instruction address offset.

Probable Cause / Recommended Action:

Cause:

HPMC has occurred.

Action:

Analyze the HPMC to determine the cause of the failure

Event Details:
Chassis Code Encoded Field : 0x40000870000062ef
   Alert Level             : 7 (HPMC detected.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 46 (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               : 8 (code address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000da
Event 1204

Severity: MINORWARNING

Event Summary: TOC has been detected in machine check handler.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_CHECK_TOC.

Each CPU will send this code early in the PDC TOC handler, as soon as the cause of machine check entry is determined to be a TOC.

The data field contains the interrupt instruction address offset.

Probable Cause / Recommended Action:

Cause:

TOC has occurred

Action:

None

Event Details:
Chassis Code Encoded Field : 0x400008100000611f
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   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               : 8 (code address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000db
Event 1206

Severity: INFORMATION

Event Summary: Indicates that a cause for the HPMC cannot be determined by the CPU.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_CPU_RUNWAY_UNKNOWN_ERR.

Indicates that a cause for the HPMC cannot be determined by the CPU

Probable Cause / Recommended Action:

Cause:

HPMC of unknown cause

Action:

Analyze the HPMC to determine the cause of the failure

Event Details:
Chassis Code Encoded Field : 0xb800082011006c6c
   Alert Level             : 2 (Error chassis code or non-urgent operator
   attention required.)
   Source FRU              : 1 (processor)
   Source FRU Detail       : 1 (processor general)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail )
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 198 (implementation dependent)
   Activity Status         : 12 (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 1207

Severity: SERIOUS

Event Summary: Coherency controller (CC) registers indicate a Deadlock Recovery Reset.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_DEADLOCK_RESET_DETECTED.

Early in bootstrap, the coherency controller (CC) registers are checked for Deadlock Recovery Reset. This chassis code indicates that CC logs will be stored for recovery by PDC_PAT_SYSTEM_INFO [Return Errors]. HPMC may be signaled first, in which case PIM will be valid as well as CEC error logs.

Probable Cause / Recommended Action:

Cause:

Coherency controller (CC) resources are deadlocked and the CC is resetting the cell.

Action:

Analyze the Deadlock Recovery logs (like HPMC Error logs) to determine the cause of the failure

Event Details:
Chassis Code Encoded Field : 0xb80008600000645c
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 69 (implementation dependent)
   Activity Status         : 12 (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 1208

Severity: SERIOUS

Event Summary: Blocking timeout detected during Coherency controller (CC) logging.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_DNA_POUT_BT.

The cell controller (CC) POUT has detected a blocking timeout. The data field contains the affected CPU and thereby indicates the CC POUT interface detecting the blocking timeout. This CPU was inhibited from becoming the cell's crash monarch, unless there are no CPUs without BT. After CC logging is complete, this cell will be reset.

Probable Cause / Recommended Action:

Cause:

The cell controller (CC) POUT has detected a blocking timeout.

Action:

Analyze the HPMC to determine the cause of the failure Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x200008600000633c
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 51 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000de
   FRU Source          = 13 (unknown)
   Source Detail       = 14 (unknown)
Event 1209

Severity: SERIOUS

Event Summary: The OS_HPMC vector in the IVA table is misaligned.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_BAD_OS_HPMC_ADDR.

An IVA table has been installed, but the OS_HPMC vector address is misaligned. This is a serious OS software error.

Probable Cause / Recommended Action:

Cause:

IVA table has been incorrectly constructed or corrupted.

Action:

Reboot O/S Report event to the Response Center

Event Details:
Chassis Code Encoded Field : 0xb80008c00000652c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 82 (implementation dependent)
   Activity Status         : 12 (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 1210

Severity: MAJORWARNING

Event Summary: The OS HPMC handler checksum is bad.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_BAD_OS_HPMC_CHECKSUM.

An IVA table has been installed, but the OS HPMC handler checksum is bad. This is a serious OS software error.

Probable Cause / Recommended Action:

Cause:

IVA table has been incorrectly constructed or corrupted, or the OS HPMC handler has been corrupted.

Action:

Reboot O/S Report event to the Response Center

Event Details:
Chassis Code Encoded Field : 0xb80008c00000653c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 83 (implementation dependent)
   Activity Status         : 12 (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 1211

Severity: MAJORWARNING

Event Summary: Attempt to branch to OS HPMC handler failed.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_BR_TO_OS_HPMC_FAILED.

Cannot branch to OS HPMC handler.

Probable Cause / Recommended Action:

Cause:

Specific reason for this failure will be identified by another chassis code.

Action:

Review previous chassis codes to determine reason for branch failure

Event Details:
Chassis Code Encoded Field : 0xb80008c00000657c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 87 (implementation dependent)
   Activity Status         : 12 (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 1212

Severity: SERIOUS

Event Summary: Attempt to reset the cell from within the HPMC handler has failed.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_FALL_THROUGH_RESET.

It should not be possible for the reset to fail. Lab involvement is indicated.

Probable Cause / Recommended Action:

Cause:

Indicates serious software or hardware error.

Action:

Report this to the Response Center Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0xb80008c00000658c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 88 (implementation dependent)
   Activity Status         : 12 (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 1213

Severity: INFORMATION

Event Summary: SBA transactions will be flushed from coherency controller (CC) queues.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_MONARCH_REO_PLUNGE_START.

The partition crash monarch will flush the SBA-sourced transactions from its coherency controller (CC) queues

Probable Cause / Recommended Action:

Cause:

Normal forward progress in error handler

Action:

None

Event Details:
Chassis Code Encoded Field : 0xb80008000000643f
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 67 (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               : 23 (unknown)
   Message ID              : 0 (not associated with other log entries)  
Event 1214

Severity: MAJORWARNING

Event Summary: PDC has detected a nested HPMC.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_MULTIPLE.

PDC HPMC will branch to OS HPMC, which will unmask HPMC. If the OS_HPMC encounters an HPMC, the second entry to PDC_HPMC will cause a cold restart of the partition.

Probable Cause / Recommended Action:

Cause:

HPMC within OS_HPMC handler.

Action:

Analyze the HPMCs

Event Details:
Chassis Code Encoded Field : 0xb80008600000624c
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 36 (implementation dependent)
   Activity Status         : 12 (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 1215

Severity: SERIOUS

Event Summary: NVM flag has been used to halt the cell during HPMC.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_NVM_HALT_CELL.

This chassis code should only be enabled at the direction of the lab. If it is seen inadvertently, it is Equivalent to ERR_ASSERT. The lab must be notified.

Probable Cause / Recommended Action:

Cause:

Cell halt during HPMC has been enabled from the BCH debug menu.

Action:

Contact the Response Center to have flag cleared

Event Details:
Chassis Code Encoded Field : 0xb80008c0000065ac
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 90 (implementation dependent)
   Activity Status         : 12 (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 1216

Severity: SERIOUS

Event Summary: NVM flag has been used to halt the cell during HPMC.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_NVM_HALT_CPU.

This chassis code should only be enabled at the direction of the lab. If it is seen inadvertently, it is Equivalent toERR_ASSERT. Lab must be notified.

Probable Cause / Recommended Action:

Cause:

Cell halt during HPMC has been enabled from the BCH debug menu.

Action:

Contact the Response Center to have flag cleared

Event Details:
Chassis Code Encoded Field : 0xb80008c00000659c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 89 (implementation dependent)
   Activity Status         : 12 (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 1217

Severity: SERIOUS

Event Summary: An IVA table has been installed, but the HPMC vector is zero.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_OS_HPMC_VECTOR_0.

The IVA table is expected to provide an OS HPMC handler. This is a serious OS software error.

Probable Cause / Recommended Action:

Cause:

IVA table has been incorrectly constructed or corrupted.

Action:

Reboot O/S Report event to the Response Center

Event Details:
Chassis Code Encoded Field : 0xb80008c00000654c
   Alert Level             : 12 (Software failure.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 84 (implementation dependent)
   Activity Status         : 12 (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 1218

Severity: MAJORWARNING

Event Summary: Coherency controller (CC) to SBA link cannot be initialized.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_RI_INIT_FAILED.

The SBA is present, but there are persistent errors appearing in the coherency controller RI interface.

Probable Cause / Recommended Action:

Cause:

Defective RIO cable Cable connection

Action:

Check / replace RIO cable Check the SBA error logs

Event Details:
Chassis Code Encoded Field : 0xb8000800000065bc
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 91 (implementation dependent)
   Activity Status         : 12 (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 1219

Severity: INFORMATION

Event Summary: Advises GSP of major change in system state.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_HPMC_STATE_ENTRY.

This code informs GSP that a major change in system state has occurred. This change will be reflected in VFP.

Probable Cause / Recommended Action:

Cause:

Normal HPMC handling

Action:

None

Event Details:
Chassis Code Encoded Field : 0xa00000109f00020a
   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      : 32 (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               : 20 (major changes in system state)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000e9
   System State            : 9 (unknown)
   LED Run                 : 2 (steady green)
   LED Attention           : 3 (unknown)
   LED Stopped             : 0 (off (default))
Event 1220

Severity: SERIOUS

Event Summary: Fabric Loss Of Lockstep detected by the coherency controller (CC).

Event Class: System

Problem Description:
Chassis Code Keyword ERR_LOL_DETECTED.

The coherency controller (CC) has detected fabric loss of lockstep during attempt to rendezvous the partition during HPMC handling. The cell will log fabric errors, if possible, and clear errors from its local XBC port. Fabric link(s) may fail due to propagation of error.

Probable Cause / Recommended Action:

Cause:

Fabric problem detected by the Coherency controller (CC)

Action:

Analyze HPMC Check the state of the fabric. If error was due to a failure in the link between two XBCs the system backplane will need to be reset to clear the error.

Event Details:
Chassis Code Encoded Field : 0xb8000800000064ec
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 78 (implementation dependent)
   Activity Status         : 12 (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 1221

Severity: SERIOUS

Event Summary: Multiple Loss of Lockstep results in cell halt.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_LOL_HALT_CELL.

If a threshold number (currently two) of loss of lockstep occurrences have been detected since the last power-on, the cell will be halted.

Probable Cause / Recommended Action:

Cause:

Fabric problem detected by the Coherency controller (CC)

Action:

Check the state of the fabric. If this condition was caused by an error in a XBC to XBC link the system backplane must be reset to clear the error. Analyze the HPMC.

Event Details:
Chassis Code Encoded Field : 0x20000860000064ec
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 78 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000eb
   FRU Source          = 14 (unknown)
   Source Detail       = 11 (unknown)
Event 1222

Severity: MAJORWARNING

Event Summary: MDP0 has detected a memory subsystem failure.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_MEM_SUBSYS_FAIL_MID0.

MDP0 has detected a memory subsystem failure. This may be caused by an memory bus parity error, a DIMM failure or a failure of MPD0 in the coherency controller (CC). The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Memory bus parity error Coherency controller seating / failure DIMM seating / failure

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x20000860000063cc
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 60 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000ec
   FRU Source          = 14 (unknown)
   Source Detail       = 12 (unknown)
Event 1223

Severity: MAJORWARNING

Event Summary: MDP1 has detected a memory subsystem failure.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_MEM_SUBSYS_FAIL_MID1.

MDP0 has detected a memory subsystem failure. This may be caused by an memory bus parity error, a DIMM failure or a failure of MPD0 in the coherency controller (CC). The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Memory bus parity error Coherency controller seating / failure DIMM seating / failure

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x20000860000063dc
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 61 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000ed
   FRU Source          = 14 (unknown)
   Source Detail       = 13 (unknown)
Event 1224

Severity: INFORMATION

Event Summary: Partition crash monarch is about to plunge the partition CPU queues.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_RENDEZ_PD_PLUNGE.

The partition crash monarch is now wake all slave CPUs in partition to flush their queues, and then will flush its own. This clears packets in all flow control classes.

Probable Cause / Recommended Action:

Cause:

Normal HPMC handling

Action:

None

Event Details:
Chassis Code Encoded Field : 0xb8000800000063ac
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 58 (implementation dependent)
   Activity Status         : 12 (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 1225

Severity: MAJORWARNING

Event Summary: A Runway address parity error has been detected.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_RUNWAY_ADDR_PARITY_ERR.

A CPU Runway address parity error has been detected.

The data field contains the physical location of the CPU, and therefore also identifies the coherency controller (CC) processor interface, which is also suspect.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Failure in CPU, Coherency controller (CC), or their connections.

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x20000860000063ec
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 62 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000ef
   FRU Source          = 14 (unknown)
   Source Detail       = 15 (unknown)
Event 1226

Severity: MAJORWARNING

Event Summary: A runway control parity error has been detected.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_RUNWAY_CTL_PARITY_ERR.

A CPU runway control parity error has been detected.

The data field contains the physical location of the CPU, and therefore also identifies the coherency controller (CC) processor interface, which is also suspect.

The cell will be halted.

Probable Cause / Recommended Action:

Cause:

Failure in CPU, Coherency controller (CC), or their connections.

Action:

Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x20000860000063fc
   Alert Level             : 6 (Boot possible pending failure - action required
   (e.g. boot disk error rate above threshold, power failure, overtemp
   medium).)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 63 (implementation dependent)
   Activity Status         : 12 (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:   0x00000000000000f0
   FRU Source          = 15 (unknown)
   Source Detail       = 0 (unknown, no source stated)
Event 1227

Severity: MAJORWARNING

Event Summary: The OS_TOC vector is misaligned.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_TOC_BAD_OS_TOC_ADDRESS.

If an OS_TOC vector is registered using PDC_REGISTER_TOC [Register TOC vector], that will be used. Otherwise, the vector stored in page zero will be used. In either case, the vector is checked for 4-byte alignment. The partition will reboot if this test fails.

Probable Cause / Recommended Action:

Cause:

The OS TOC vector is not 4-byte aligned.

Action:

Report this event to the Response Center Partition is rebooted

Event Details:
Chassis Code Encoded Field : 0xb80008100000619c
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 25 (implementation dependent)
   Activity Status         : 12 (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 1228

Severity: MAJORWARNING

Event Summary: Checksum test of OS TOC handler has failed.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_TOC_BAD_OS_TOC_CHECKSUM.

Before PDC_TOC branches to OS_TOC, one of the tests of the OS_TOC handler is a checksum of at least a portion of the OS TOC handler. The length to checksum is taken from the parameter to using PDC_REGISTER_TOC [Register TOC vector], of from page zero storage if this registration has not been done. The partition will reboot if this test fails.

Probable Cause / Recommended Action:

Cause:

The checksum test of the OS TOC handler has failed.

Action:

Report this event to the Response Center Partition is rebooted

Event Details:
Chassis Code Encoded Field : 0xb8000810000061dc
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 29 (implementation dependent)
   Activity Status         : 12 (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 1229

Severity: MAJORWARNING

Event Summary: The OS TOC handler length in not 4-byte aligned.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_TOC_BAD_OS_TOC_CODE.

The OS TOC handler length specifies the range for the checksum test. It must be 4-byte aligned. The partition will reboot if this test fails.

Probable Cause / Recommended Action:

Cause:

The OS TOC handler length supplied by Page zero or PDC_REGISTER_TOC [Register TOC vector] is not correct.

Action:

Report this event to the Response Center Partition is rebooted

Event Details:
Chassis Code Encoded Field : 0xb8000810000061bc
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 27 (implementation dependent)
   Activity Status         : 12 (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 1230

Severity: MAJORWARNING

Event Summary: The first instruction of the OS TOC handler is null.

Event Class: System

Problem Description:
Chassis Code Keyword ERR_TOC_BAD_OS_TOC_CODE_0.

A null has been found as the first instruction of the OS_TOC handler. The partition will reboot.

Probable Cause / Recommended Action:

Cause:

The OS TOC handler supplied by Page zero or PDC_REGISTER_TOC [Register TOC vector] has been corrupted

Action:

Report this event to the Response Center Partition is rebooted

Event Details:
Chassis Code Encoded Field : 0xb8000810000061ac
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 0 (unknown, no source stated)
   Source FRU Detail       : 0 (unknown, no source stated)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (unknown, no source stated)
   Caller Activity         : 6 (machine check)
   Caller Subactivity      : 26 (implementation dependent)
   Activity Status         : 12 (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 1231

Severity: MAJORWARNING

Event Summary: Invalid address passed to TogoWriteVerify().

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_ADDRESS_NOT_IN_SKD_ERR.

An invalid address was passed to TogoWriteVerify().

Data Field:

CSR Address that passed to TogoWriteVerify()

Probable Cause / Recommended Action:

Cause:

PDC Runtime Error Possible memory corruption or misuse of functions

Action:

Report this error to the Response Center Reset the cell Update PDC

Event Details:
Chassis Code Encoded Field : 0x080008c0510027df
   Alert Level             : 12 (Software failure.)
   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      : 125 (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               : 1 (physical address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000f5
Event 1232

Severity: MAJORWARNING

Event Summary: The cabinet number for the cabinet containing the XBC is incorrect.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_CABINET_NUMBER_INCORRECT.

The cabinet number for the cabinet containing the XBC is incorrect.

Data Field:

(Expected external port << 32) | external port determined from CC

Probable Cause / Recommended Action:

Cause:

The cabinet number for the cabinet containing the XBC is incorrect. The cabinet numbering rules are: Left cabinets use even numbers, Right cabinets use odd numbers, and Left / Right cabinet pairs must be numbered sequentially.

Action:

Check all the cabinet numbers Check UGUY for problems (this is where PDC gets the cabinet number from)

Event Details:
Chassis Code Encoded Field : 0x180008f051002f1f
   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      : 241 (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    : 0x00000000000000f6
Event 1233

Severity: MAJORWARNING

Event Summary: The cabinet numbering is non-sequential.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_CABINET_NUMBERS_NONSEQUENTIAL.

The cabinet numbering is non-sequential. Data Field Value (Togo number << 32) | neighbor identification

Probable Cause / Recommended Action:

Cause:

The cabinet numbering is non-sequential. The cabinet numbering rules are:

Left cabinets use even numbers,

Right cabinets use odd numbers, and

Left / Right cabinet pairs must be numbered sequentially.

Action:

Check all the cabinet numbers Check UGUY for problems (this is where PDC gets the cabinet number from)

Event Details:
Chassis Code Encoded Field : 0x180008f051002f2f
   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      : 242 (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    : 0x00000000000000f7
Event 1234
Severity: MAJORWARNING

Event Summary: Fabric topology mismatch with XBCs in complex.

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

There is a fabric topology mismatch with the XBCs in the complex.

Data Field: (Topology of XBC << 32) | Topology of destination XBC
        0x00   Topology not yet determined
        0x30   SD16000
        0x40   SD32000 U-Turn (Left cabinet)
        0x41   SD32000 U-Turn (Right cabinet)
        0x42   SD64000 Cross-Flex
        0x43   SD64000 U-Turn
Probable Cause / Recommended Action:

Cause:

There is a fabric topology mismatch with XBC in complex.

Action:

Reset the cell Check the XBC flex cables Reset the system backplane Contact HP Support personnel to troubleshoot problem
Event Details:
Chassis Code Encoded Field : 0x180008f051002f4f
   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      : 244 (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    : 0x00000000000000f8
Event 1235

Severity: MAJORWARNING

Event Summary: The CC to XBC link is not viable.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_DNA_2_TOGO_ERR.

The CC to XBC link is not viable.

Probable Cause / Recommended Action:

Cause:

The CC to XBC link is not operational.

Action:

Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem

Event Details:
Chassis Code Encoded Field : 0x180008f051002f7f
   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      : 247 (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    : 0x00000000000000f9
Event 1236

Severity: MAJORWARNING

Event Summary: Invalid address passed to one a fabric functions.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_INVALID_ADDRESS_ERR.

An invalid address passed to one of three functions: ReadTogo(), ReadTogoSlice(), or TogoWriteVerify().

Data Field:

XBC #

Probable Cause / Recommended Action:

Cause:

PDC runtime Error Possible memory corruption or misuse of functions

Action:

Report this event to the Response Center Reset the cell Update PDC

Event Details:
Chassis Code Encoded Field : 0x080008c0510027bf
   Alert Level             : 12 (Software failure.)
   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      : 123 (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               : 1 (physical address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000fa
Event 1237

Severity: MAJORWARNING

Event Summary: A loss of lockstep in the fabric has been detected.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_LOSS_OF_LOCKSTEP.

A loss of lockstep in the fabric has been detected. The partition will be halted. ERR_LOL_DETECTED and ERR_LOL_HALT_CELL will also be logged and contain further information regarding this condition.

Probable Cause / Recommended Action:

Cause:

Lockstep between the fabric components has been lost Defective links Defective XBC Defective CC

Action:

Refer to the ERR_LOL_DETECTED and LOL_HALT_CELL chassis codes for more information on this condition. The system backplane must be reset to route the fabric

Event Details:
Chassis Code Encoded Field : 0x080008a05100282f
   Alert Level             : 10 (Boot possible, functionality lost.)
   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      : 130 (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               : 1 (physical address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000fb
Event 1238

Severity: MAJORWARNING

Event Summary: Multi-bit error occurred in fabric function.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_MBE_ERR.

A multi-bit error occurred in ReadTogo(), ReadTogoSlice() or TogoWriteVerify().

Data Field:

XBC #

Probable Cause / Recommended Action:

Cause:

A multi-bit read error occurred

Action:

Check the XBC flex links Reset the CC Reset the system backplane Replace the CC Replace the XBC Replace the cell board Replace the system backplane

Event Details:
Chassis Code Encoded Field : 0x080008a0510027af
   Alert Level             : 10 (Boot possible, functionality lost.)
   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      : 122 (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               : 1 (physical address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x00000000000000fc
Event 1239

Severity: MAJORWARNING

Event Summary: No XBC neighbor was found but was expected.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_NO_TOGO_NEIGHBOR.

No XBC neighbor was found but was expected. The cell will halt.

Data Field:

XBC # that expected a neighbor

Probable Cause / Recommended Action:

Cause:

Failed neighbor or connecting XBC port

Action:

Reset system backplane Reset the neighbor device (XBC or CC) Replace the system backplane

Event Details:
Chassis Code Encoded Field : 0x18000800510022ee
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   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      : 46 (implementation dependent)
   Activity Status         : 14 (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    : 0x00000000000000fd
Event 1240

Severity: MAJORWARNING

Event Summary: No local XBC was present.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_NO_TOGO_PRESENT.

Could not communicate with local XBC. The cell will halt.

Probable Cause / Recommended Action:

Cause:

Defective XBC
Defective CC
Defective connection between cell and system backplane

Action:

Reset the cell
Reset the system backplane
Contact HP Support personnel to troubleshoot

Event Details:
Chassis Code Encoded Field : 0xb80008005100261e
   Alert Level             : 0 (No failure detected, forward progress logs and
   timer requests only.)
   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      : 97 (implementation dependent)
   Activity Status         : 14 (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 1241

Severity: MAJORWARNING

Event Summary: The XBC SBE and LPE errors were not cleared properly.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_PERSISTENT_ERR_SBE_LPE.

The XBC logged a SBE or LPE after they should have been cleared. Either the clear failed, or a new error was logged immediately.

Probable Cause / Recommended Action:

C1:

write to XBC Debug registers failed

A1:

check XBC, check CC to XBC link

C2:

the link generated a new error

A2:

check XBC, check CC to XBC link

Event Details:
Chassis Code Encoded Field : 0x180008a05100283f
   Alert Level             : 10 (Boot possible, functionality lost.)
   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      : 131 (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    : 0x00000000000001bb
Event 1242
Severity: MAJORWARNING

Event Summary: A fabric port was found in error.

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

A fabric port was found in error. Currently the chassis code data field could contain two different formats of data. Use format 2 if bits[31:0] are 0x8-0xf.
Data Field:
Format 1:
           [63:32] = XBC #
            [14:7] = topology
                        0x00: Topology not yet determined
                        0x30: SD16000
                        0x40: SD32000 Left cabinet
                        0x41: SD32000 Right cabinet
                        0x42: SD64000 (crossflex)
                        0x43: SD64000 (unsupported)
             [6:0] = Port route around information
                               -----------------------------------------
                Ext. Port #   |  6  |  5  |  4  |  3  |  2  |  1  |  0  |
                               -----------------------------------------
                Routed Around | n/a | 1/0 | 1/0 | n/a | n/a | 1/0 | 1/0 |
                (1=Yes,0=No)   -----------------------------------------
Format 2:
           [63:32} = XBC #
            [31:0] = Internal Port #
Probable Cause / Recommended Action:

Cause:

Port has errors logged Port has been routed around

Action:

Reset the system backplane Contact HP Support personnel to troubleshoot the problem
Event Details:
Chassis Code Encoded Field : 0x180008815100270f
   Alert Level             : 8 (Boot possible, performance impaired.)
   Source FRU              : 5 (fabric connector)
   Source FRU Detail       : 1 (cross bar)
   Source ID               : 0 (platform dependent)
   Event Detail            : 1 (port in FE mode)
   Caller Activity         : 2 (config)
   Caller Subactivity      : 112 (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    : 0x00000000000000ff
Event 1243

Severity: MAJORWARNING

Event Summary: A routing error has been discovered.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_ROUTING_ERROR.

A routing error was read from a XBC's General Purpose Register 3. The cell will halt.

Data Field:

0x0BADBADBADBADBAD - failed routing opposite corner XBC - must find current XBC being routed from previous chassis codes

0x0000000000000000 - cell's local XBC has been noted having a routing error.

Probable Cause / Recommended Action:

Cause:

Failed link Defective XBC port Found a invalid device on the fabric System backplane error

Action:

Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot the problem

Event Details:
Chassis Code Encoded Field : 0x180008f051002f9f
   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      : 249 (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    : 0x0000000000000100
Event 1244

Severity: MAJORWARNING

Event Summary: Found a illegal device in the fabric.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_SAK_ENCOUNTERED.

A illegal device was found in the fabric. If the system is a SD16000, the cell will halt; otherwise a ROUTING_ERROR is placed in the XBC's General Purpose Register 3.

Data Field:

XBC # that the illegal device is connected to

Probable Cause / Recommended Action:

Cause:

An illegal device was found connected to a XBC

Action:

Remove the illegal device Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot the problem

Event Details:
Chassis Code Encoded Field : 0x180008f051002f6f
   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      : 246 (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    : 0x0000000000000101
Event 1245

Severity: MAJORWARNING

Event Summary: A runtime fabric error occurred.

Event Class: System

Problem Description:
Chassis Code Keyword FABRIC_SW_ERROR.

A runtime fabric error has occurred.

Data Field:

Routing state - Unexpected routing state in RemoteIntraSkdRouting()

Invalid XBC-XBC port - Calculated invalid XBC-XBC port, starting over with built in port #

Invalid Topology - Found invalid topology in a XBC

0x00000000000000CC - Invalid quad calculated, assigning opposite corner XBC with caller's XBC #

0x0000000000000022 - Setting re-route port to callers port XBC # Routing error found in DetermineRoutingState()

Probable Cause / Recommended Action:

Cause:

Unexpected routing state Invalid XBC-XBC port Invalid Topology Invalid quadrant found Invalid reroute Could not determining routing state

Action:

Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot the problem

Event Details:
Chassis Code Encoded Field : 0x080008c05100275f
   Alert Level             : 12 (Software failure.)
   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      : 117 (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               : 1 (physical address)
   Message ID              : 0 (not associated with other log entries) 
Chassis Code Data Field    : 0x0000000000000102
Event 1246

Severity: INFORMATION

Event Summary: GSP Firmware Update.

Event Class: System

Problem Description:
Chassis Code Keyword FIRMWARE_UPDATE_OP.

The firmware on the GSP is being updated.

Probable Cause / Recommended Action:

Cause:

Firmware update utility is being run and loading or updating the firmware on the GSP

Action:

None

Event Details:
Chassis Code Encoded Field : 0x0010081066ff7010
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 6 (service processor)
   Source ID               : 255 (platform dependent)
   Event Detail            : 0 (no problem detail)
   Caller Activity         : 7 (utility)
   Caller Subactivity      : 1 (firmware update)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   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 1247

Severity: INFORMATION

Event Summary: A device on the GSP Bus was attached.

Event Class: System

Problem Description:
Chassis Code Keyword GSP_BUS_DEVICE_ATTACH.

A device has reported its presence to the GSP on the GSP Bus.

Probable Cause / Recommended Action:

Cause:

A device on the GSP Bus reported its presence to the GSP and was acknowledged. The devices on the GSP Bus which cause this code are the CLU, PM3, cell and core IO.

Action:

None

Event Details:
Chassis Code Encoded Field : 0x20100810660050f0
   Alert Level             : 1 (Service processor alert, no failure detected,
   forward progress logs and timer requests only.)
   Source FRU              : 6 (platform entity)
   Source FRU Detail       : 6 (service processor)
   Source ID               : 0 (platform dependent)
   Event Detail            : 0 (no problem detail)
   Caller Activity         : 5 (config and deconfig)
   Caller Subactivity      : 15 (attach to platform internal interconnect)
   Activity Status         : 0 (implementation dependent)
   Reporting Entity Type   : 1 (service processor)
   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:   0x0000000000000104
   FRU Source          = 0 (unknown, no source stated)
   Source Detail       = 4 (unknown)
Event 1248

Severity: INFORMATION

Event Summary: A device on the GSP is no longer communicating with the GSP.

Event Class: System

Problem Description: