Core Hardware Monitor (Events)

Event 1

• Severity: Information
• Event Summary: System bus recovered error
• Event Class: System
• Problem Description:
  An error on the system bus occurred, but the system recovered. This does not represent a problem unless an excessive rate of system bus errors occur. If an excessive rate occurs, event #2 with higher severity will be generated.
• Cause / Action:
  A recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details:
Examples:

PBC bus interface chip 2: "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8
 AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

PBC bus interface chip 4:  "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8   
AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

---

Event 2

• Severity: Serious
• Event Summary: Multiple System Bus recovered errors
• Event Class: System
• Problem Description:
  An excessive rate of single bit errors has occurred on the system bus. The operating system has recovered from these errors but the system board should be checked before a catastrophic error occurs.
• Cause / Action:
  The system board has failed. Contact your HP support representative to check the system board.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details:
Examples:

PBC bus interface chip 2: "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8
 AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

PBC bus interface chip 4:  "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8   
AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

---

Event 3

• Severity: Information
• Event Summary: Memory related system bus recovered error
• Event Class: System
• Problem Description:
  An error which was most likely due to a memory problem was seen on the system bus. The system recovered. This does not represent a problem unless an excessive rate of system bus errors occur. If an excessive rate occurs, event #4 with higher severity will be generated.
• Cause / Action:
  A recoverable error occurred. No action is required.
• Automated Recovery: None
• Event Generation Threshold: 2 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 2 occurrences within 24 hours

Event Details:
Examples:

PBC bus interface chip 2: "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8
 AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

PBC bus interface chip 4:  "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8   
AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

---

Event 4

• Severity: Serious
• Event Summary: Multiple memory related system bus recovered errors
• Event Class: System
• Problem Description:
  An excessive rate of recoverable single bit errors, most likely due to memory problems, has occurred on the System Bus.
• Cause / Action:
  The memory system is experiencing problems. Run the logtool utility in the support tool manager (stm(1M)) and examine the memory logs.
• Automated Recovery: None
• Event Generation Threshold: 2 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 2 occurrences within 24 hours

Event Details:
Examples:

PBC bus interface chip 2: "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8
 AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

PBC bus interface chip 4:  "In Order" Correctable error.
 AERR Addr 1 log register: 
  HIT signal (Hit):                         1          
  Response Status Signal's parity (RSP):    1
  Response status signals from Response 
     phase (RS):                            3
  First cycle Request Bus value (ReqA):     0xa
  AddressA:                                 0x56789abcde8
  Hex value of register:                    0x0193456789abcde8   
AERR Addr 2 log register: 
  Second cycle Request Bus value (ReqB):    0x7
  AddressA:                                 0xa9876543210
  Hex value of register:                    0x00007a9876543210

---

Event 5

• Severity: Serious
• Event Summary: Main cabinet fan or blower n failure
• Event Class: System
• Problem Description:
  A main cabinet fan or blower is not functioning. Currently there are sufficient fans to cool the cabinet.
• Cause / Action:
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
  The fan has failed. Contact your HP support representative to check the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 1
     Location of failed fan(s).: Cabinet
     Failed fan number(s).............: 1

---

Event 6

• Severity: Critical
• Event Summary: Main cabinet fan or blower n failure
• Event Class: System
• Problem Description:
  One or more main cabinet fans or blowers are not functioning. There are insufficient fans to cool the cabinet.
• Cause / Action:
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
  The fan has failed. Contact your HP support representative to check the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 2
     Location of failed fan(s).: Cabinet 
     Failed fan number(s).............: 0,1

---

Event 7

• Severity: Critical
• Event Summary: Insufficient main cabinet fans or blowers in x
• Event Class: System
• Problem Description:
  There is an insufficient number of main cabinet fans or blowers installed to cool the unit.
• Cause / Action:
  A fan has failed. Contact your HP support representative to check the fan.
  One or more fans or blowers have been removed from the cabinet. Contact your HP support representative to check the fan(s).
  The electrical connection to a fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 8

• Severity: Information
• Event Summary: Main cabinet fans or blowers are all working in x
• Event Class: System
• Problem Description:
  The currently installed main cabinet fans or blowers are all operating properly.
• Cause / Action:
  A failed fan was removed. Ensure that an operational fan is installed in its place.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 9

• Severity: Information
• Event Summary: Sufficient main cabinet fans or blowers are installed
• Event Class: System
• Problem Description:
  A sufficient number of fans are installed in the cabinet to cool the unit.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 10

• Severity: Serious
• Event Summary: I/O fan n: fan failure
• Event Class: System
• Problem Description:
  An I/O fan is not functioning. Currently there are sufficient fans to cool the unit.
• Cause / Action:
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
  The fan has failed. Contact your HP support representative to check the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 1
     Location of failed fan(s).: I/O Expansion Cabinet 
     Failed fan number(s).............: 1

---

Event 11

• Severity: Critical
• Event Summary: I/O fan n: fan failure
• Event Class: System
• Problem Description:
  One or more I/O fans are not functioning. There are insufficient fans to cool the unit.
• Cause / Action:
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
  The fan has failed. Contact your HP support representative to check the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 2
     Location of failed fan(s).: I/O Expansion Cabinet 
     Failed fan number(s).............: 0,1

---

Event 12

• Severity: Critical
• Event Summary: Insufficient I/O fans in x
• Event Class: System
• Problem Description:
  There are an insufficient number of I/O fans installed to cool the cabinet I/O chassis.
• Cause / Action:
  A fan has failed. Contact your HP support representative to check the fan.
  One or more fans have been removed from the cabinet. Contact your HP support representative to check the fan(s).
  The electrical connection to a fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: I/O Expansion Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 13

• Severity: Information
• Event Summary: I/O fans are all working in x
• Event Class: System
• Problem Description:
  The currently installed I/O fans are all operating properly.
• Cause / Action:
  A failed fan was removed. Ensure that an operational fan is installed in its place.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 14

• Severity: Information
• Event Summary: Sufficient I/O fans are installed
• Event Class: System
• Problem Description:
  A sufficient number of I/O fans are installed in the cabinet to cool the unit.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 15

• Severity: Serious
• Event Summary: Cabinet power supply n: power supply failure
• Event Class: System
• Problem Description:
  A cabinet power supply has failed. Currently there are sufficient power supplies operating to power the unit.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the plug is connected to the power supply, and to a working power source.
  The power supply is disabled. Verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 1
     Location of failed power supplies.: Cabinet 
     Failed power supply number(s).....: 2

---

Event 16

• Severity: Critical
• Event Summary: Cabinet power supply n: power supply failure
• Event Class: System
• Problem Description:
  One or more cabinet power supplies have failed. Currently there are insufficient power supplies operating to power the unit.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the plug is connected to the power supply, and to a working power source.
  The power supply is disabled. Verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 2
     Location of failed power supplies.: Cabinet 
     Failed power supply number(s).....: 0,1

---

Event 17

• Severity: Critical
• Event Summary: Insufficient cabinet (bulk) power supplies in x
• Event Class: System
• Problem Description:
  There are an insufficient number of working cabinet (or bulk) power supplies installed to power the unit.
• Cause / Action:
  A power supply has been removed from the cabinet. Contact your HP support representative to check the power supply.
  A power supply is disabled. If present, verify that the switch on the front of each power supply is in the "On" position.
  A power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of power supplies present.........: 1
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 2
     Missing or failed power supply number(s).: 1

---

Event 18

• Severity: Information
• Event Summary: Cabinet (bulk) power supplies are all working in x
• Event Class: System
• Problem Description:
  The currently installed cabinet (or bulk) power supplies are all operating properly.
• Cause / Action:
  A failed power supply was removed. Ensure that an operational power supply is installed in its place.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

---

Event 19

• Severity: Information
• Event Summary: Sufficient cabinet power supplies are installed
• Event Class: System
• Problem Description:
  A sufficient number of power supplies are installed in the cabinet to power the unit.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 20

• Severity: Serious
• Event Summary: I/O power supply n: power supply failure
• Event Class: System
• Problem Description:
  An I/O power supply has failed. Currently there are sufficient power supplies operating to power the unit.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the plug is connected to the power supply, and to a working power source.
  The power supply is disabled. Verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 1
     Location of failed power supplies.: I/O Expansion Cabinet
     Failed power supply number(s).....: 2

---

Event 21

• Severity: Critical
• Event Summary: I/O power supply n: power supply failure
• Event Class: System
• Problem Description:
  One or more I/O power supplies have failed. Currently there are insufficient power supplies operating to power the unit.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the plug is connected to the power supply, and to a working power source.
  The power supply is disabled. Verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 2
     Location of failed power supplies.: I/O Expansion Cabinet
     Failed power supply number(s).....: 2,3

---

Event 22

• Severity: Critical
• Event Summary: Insufficient I/O power supplies in x
• Event Class: System
• Problem Description:
  There are an insufficient number of I/O power supplies installed in the cabinet to power the I/O chassis.
• Cause / Action:
  One or more power supplies have been removed from the cabinet. Contact your HP support representative to check the power supply or supplies.
  A power supply is not connected to a working AC power source. Verify that the power supply is connected properly.
  A power supply is disabled. If present, verify that the switch on the front of the power supply is in the "On" position.
  A power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of power supplies present.........: 2
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 0,1
     Missing or failed power supply number(s).: 2

---

Event 23

• Severity: Information
• Event Summary: I/O power supplies are all working in x
• Event Class: System
• Problem Description:
  The currently installed I/O power supplies are all operating properly.
• Cause / Action:
  A failed power supply was removed. Ensure that an operational power supply is installed in its place.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 24

• Severity: Information
• Event Summary: Sufficient I/O power supplies are installed
• Event Class: System
• Problem Description:
  A sufficient number of I/O power supplies are installed in the cabinet to cool the unit.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 25

• Severity: Serious
• Event Summary: Chassis code logging failure
• Event Class: System
• Problem Description:
  An attempt by the operating system to log a chassis code failed.
• Cause / Action:
  Communications between the processor dependent code (PDC) and the service processor has failed. Verify service processor operation. Enter chassis log manually with service processor commands.
• Automated RecoveryAutomated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

An attempt by the operating system (OS) to do a chassis log write function
failed.
The chassis code that the OS was trying to write was:
   Encoded chassis code: 0x123456789abcdef0
   Data field:           0x1122334455667788
The processor dependent code returned the status -1.  Possible status values:
   -1 = Unimplemented procedure.
   -2 = Nonexistent Option.
   -3 = Call completed with error.
  -10 = Invalid argument.

---

Event 26

• Severity: Major Warning
• Event Summary: Processor dependent hardware battery low
• Event Class: System
• Problem Description:
  The processor dependent hardware (PDH) battery is low.
• Cause / Action:
  For N-Class, rp7400, L-Class, rp5400, rp5430, rp5450, rp5470, rp4440, rp3440 and c3000 systems:
  The processor dependent hardware (PDH) battery, which is a non-replaceable part of the system board, is discharged. Contact your HP support representative to check the the system board.
  For SuperDome, rp8420, rp7420 and sdl6A32A64A systems:
  The battery on the cell board is discharged. Contact your HP support representative to check the battery on the cell board, using the procedure defined in the Electronic Performance Support System (EPSS). Following this procedure is important because removing the battery will cause the non-volatile RAM (and the memory page de-allocation table) to be cleared.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the processor dependent hardware (PDH)
battery is low.

---

Event 27

• Severity: Information
• Event Summary: Processor dependent hardware microprocessor timeout
• Event Class: System
• Problem Description:
  The processor dependent hardware (PDH) microprocessor has timed out waiting for bus arbitration. An individual occurrence of this event does not necessarily reflect a problem with the hardware. If multiple occurrences of this event are seen, event #28 with higher severity will be generated.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that there has been a timeout waiting for
microcontroller arbitration.

---

Event 28

• Severity: Serious
• Event Summary: Processor dependent hardware microprocessor timeout
• Event Class: System
• Problem Description:
  The processor dependent hardware (PDH) microprocessor has timed out waiting for bus arbitration.
• Cause / Action:
  For N-Class, rp7400, L-Class, rp5400, rp5430, rp5450, rp5470, rp4440, rp3440 and c3000 systems:
  There is a problem with the internal support bus. Prioritized list of possible field replaceable units (FRUs):
  1) System board.
  2) Core I/O board.
  3) Power monitor.
  For SuperDome, rp8420, rp7420 and sdl6A32A64A systems:
  There is a problem with the internal support bus. Prioritized list of possible field replaceable units (FRUs):
  1) Cell board.
  2) Service processor.
• Automated Recovery: None
• Event Generation Threshold: 3 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 3 occurrences within 24 hours

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that there has been a timeout waiting for
microcontroller arbitration.

---

Event 29

• Severity: Information
• Event Summary: Support bus controller reset
• Event Class: System
• Problem Description:
  The support bus controller chip has been reset. An individual occurrence of this event does not necessarily reflect a problem with the hardware. If multiple occurrences of this event are seen, event #30 with higher severity will be generated.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details
Examples:

The PDC_PAT_EVENTS function reports that the I2C bus interface chip has been
reset.

---

Event 30

• Severity: Serious
• Event Summary: Support bus controller reset
• Event Class: System
• Problem Description:
  The support bus controller chip has been reset.
• Cause / Action:
  For N-Class, rp7400, L-Class, rp5400, rp5430, rp5450, rp5470, rp4440, rp3440, and c3000 systems:
  The support bus controller is defective. Contact your HP support representative to check the system board.
  For SuperDome, rp8420, rp7420 and sld6A32A64A systems:
  The support bus controller is defective. Contact your HP support representative to check the cell board.
• Automated Recovery: None
• Event Generation Threshold: 3 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 3 occurrences within 24 hours

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the I2C bus interface chip has been
reset.

---

Event 31

• Severity: Serious
• Event Summary: Power monitor not responding
• Event Class: System
• Problem Description:
  The power monitor is not functioning.
• Cause / Action:
  For N-Class and rp7400 systems:
  The support bus which connects the system processors, the service processor and the Power Monitor may have become hung. (The support bus can be tested by issuing the service processor command "XD", and selecting the I2C access test). To reset the bus, issue the service processor command "XD" and then select "R", use the HP-UX command `stty +resetGSP %lt/dev/GSPdiag1', or press the service processor reset button. If this solves the problem (if the I2C access test now works) and the system is an N-Class or rp7400, check the service processor command "HE". If the service processor firmware is less than A.01.09, schedule an update of the service processor firmware to version A.01.09 or to a more recent version to prevent a reoccurrence of this problem.
  
  There could be a problem with the power monitor. Issue the service processor "PS" command. If this command fails, contact your HP support representative to check the power monitor.
  There could be a problem with the system board. Contact your HP support representative to check the system board.
  For SuperDome systems:
  The power monitor is not functioning properly. Contact your HP support representative to check the UGUY board.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the power monitor is not functioning.

---

Event 32

• Severity: Serious
• Event Summary: Service processor not responding
• Event Class: System
• Problem Description:
  The operating system is unable to communicate with the service processor.
• Cause / Action:
  For N-Class, rp7400, L-Class, rp5400, rp5430, rp5450 and rp5470 systems:
  The support bus which connects the system processors, the service processor and the Power Monitor or Platform Monitor may have become hung. (The support bus can be tested by issuing the service processor command "XD", and selecting the I2C access test). To reset the bus, issue the service processor command "XD" and then select "R", use the HP-UX command `stty +resetGSP </dev/GSPdiag1', or press the service processor reset button. If this solves the problem (if the I2C access test now works) and the system is an N-Class, rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the service processor firmware revision using the service processor command "HE". If the service processor firmware version is less than A.01.09, schedule and update of the service processor firmware to version A.01.09 or a more recent version to prevent a reoccurrence of this problem.
  There could be a problem with the service processor. Verify that the service processor appears to be operating normally. This can be done by typing a CTRLB at the console and verifying that the service processor responds to commands. If the service processor has failed, contact your HP support representative to check the core I/O board.
  There could be a problem with the system board. Contact your HP support representative to check the system board if necessary.
  For SuperDome systems:
  There could be a problem with the service processor. Verify service processor operation. If the service processor has failed, Contact your HP support representative to check the service processor.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the service processor is not 
functioning.

---

Event 33

• Severity: Critical
• Event Summary: Processor cabinet intake temperature is too hot
• Event Class: Overtemp
• Problem Description:
  The system intake temperature is too high.
• Cause / Action:
  Something is blocking the cooling intakes in the system processing unit (SPU). Check for obstructions.
  The room containing the SPU is too hot. Check for problems with the room air conditioning.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 34

• Severity: Critical
• Event Summary: Processor cabinet intake temperature is critically hot
• Event Class: Overtemp
• Problem Description:
  The system intake temperature is extremely high.
• Cause / Action:
  Shut down the system immediately to prevent damage.
  Something is blocking the cooling intakes in the System Processing Unit (SPU). Check for obstructions.
  The room containing the SPU is too hot. Check for problems with the room air conditioning.
  Note: The standard configuration for the environmental daemon envd is to shut the system down when this condition occurs. The shutdown may happen before this event can be generated. In this case, this event may be generated immediately after a reboot. If this is the case, the system will not automatically shutdown again unless the temperature problem reoccurs.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 35

• Severity: Information
• Event Summary: Processor cabinet temperature normal
• Event Class: Overtemp
• Problem Description:
  The system temperature has returned to the normal range.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:

---

Event 36

• Severity: Serious
• Event Summary: Platform monitor not responding
• Event Class: System
• Problem Description:
  The platform monitor is not functioning.
• Cause / Action:
  The support bus which connects the system processors, the service processor, and the Platform Monitor may have become hung. (The support bus can be tested by issuing the service processor command "XD", and then selecting the I2C access test.) To reset the bus, issue the service processor command "XD" and then select "R", use the HP-UX command 'stty +resetGSP </dev/GSPdiag1', or press the service processor reset button.
  
  If this solves the problem (if the I2C access test now works) and the system is an L-Class, rp5400, rp5430, rp5450, or rp5470, check the service processor firmware revision using the service processor command "HE". If the service processor firmware version is less than A.01.09, schedule an update of the service processor firmware to version A.01.09 or a more recent version to prevent a reoccurrence of this problem.
  
  There could be a problem with the platform monitor. Issue the service processor "PS" command. If this command fails, contact your HP support representative to check the platform monitor.
  
  There could be a problem with the system board. Contact your HP support representative.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the platform monitor is not functioning.

---

Event 37

• Severity: Information
• Event Summary: I/O Link Interface recovered error
• Event Class: System
• Problem Description:
  Unknown to the protection domain, an error occurred on the outbound I/O link interface that was recovered by hardware logic. This does not represent a problem unless the rate of I/O link interface errors is excessive. If an excessive rate occurs, event #38 with higher severity will be generated.
• Cause / Action:
  A hardware recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

FRU Physical Location:   0x000003ffff00ff82
   FRU Source          = 8 (I/O device)
   Source Detail       = 2 (system bus adapter)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 3
   I/O Slot Number     = 0
Error log time stamp: Century 20, Year 00, Month 07, Day 24 18:54:44
Error Status Register: 0x0000000000171800
   Estat.: 23:
           Bus parity error.
           - The error occurred on data.
           - The error was correctable.


Responder.................: 0xfffffff848000000
Cell number...............: 2
System Bus Adapter........: 0
Rope......................: 0
Link interface error logs:
   li_pri_err_log.........: 0x0000000020000001
   li_sec_err_log.........: 000000000000000000
   li_fe_err_en...........: 0x0000000000fff4f6
   li_unc_err_en..........: 0x0000000000000308
   li_cor_err_en..........: 0x0000000000000001
   link_data_a_syn........: 000000000000000000
   link_data_b_sys........: 000000000000000000
   link_data_c_syn........: 000000000000000000
   link_inb_cmd_stat......: 000000000000000000
   link_inb_perr_stat.....: 000000000000000000
   link_inb_illcmd_stat...: 000000000000000000
   link_syn_sw_err........: 0x0204c40000000000
   link_syn_poison........: 000000000000000000
   link_syn_improp........: 000000000000000000
   link_syn_mw_err........: 000000000000000000
   link_syn_unrec.........: 000000000000000000

---

Event 38

• Severity: Serious
• Event Summary: I/O Link Interface recovered errors
• Event Class: System
• Problem Description:
  Unknown to the protection domain, an excessive number of (hardware recoverable) errors occurred on the outbound I/O link interface.
• Cause / Action:
  Several hardware recoverable errors occurred. Contact your HP support representative to check the following FRUs (in order of priority): the outbound I/O Link cable, the I/O back plane FRU, the companion cell FRU.
• Automated Recovery: None
• Event Generation Threshold: 3rd occurrence within 8 hours
• Fault Notifier Event Generation Threshold: 3rd occurrence within 8 hours

Event Details:
Examples:

FRU Physical Location:   0x000003ffff00ff82
   FRU Source          = 8 (I/O device)
   Source Detail       = 2 (system bus adapter)
   Cabinet Location    = 0
   Card Cage Location  = 0
   Backplane Location  = 3
   I/O Slot Number     = 0
Error log time stamp: Century 20, Year 00, Month 07, Day 24 18:54:44
Error Status Register: 0x0000000000171800
   Estat.: 23:
           Bus parity error.
           - The error occurred on data.
           - The error was correctable.


Responder.................: 0xfffffff848000000
Cell number...............: 2
System Bus Adapter........: 0
Rope......................: 0
Link interface error logs:
   li_pri_err_log.........: 0x0000000020000001
   li_sec_err_log.........: 000000000000000000
   li_fe_err_en...........: 0x0000000000fff4f6
   li_unc_err_en..........: 0x0000000000000308
   li_cor_err_en..........: 0x0000000000000001
   link_data_a_syn........: 000000000000000000
   link_data_b_sys........: 000000000000000000
   link_data_c_syn........: 000000000000000000
   link_inb_cmd_stat......: 000000000000000000
   link_inb_perr_stat.....: 000000000000000000
   link_inb_illcmd_stat...: 000000000000000000
   link_syn_sw_err........: 0x0204c40000000000
   link_syn_poison........: 000000000000000000
   link_syn_improp........: 000000000000000000
   link_syn_mw_err........: 000000000000000000
   link_syn_unrec.........: 000000000000000000

Event 39

• Severity: Serious
• Event Summary: Main cabinet fan or blower n failure in x
• Event Class: System
• Problem Description:
  A main cabinet fan or blower is not functioning.
• Cause / Action:
  The fan has failed. Contact your HP support representative to check the fan.
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 1
     Location of failed fan(s).: Cabinet
     Failed fan number(s).............: 1

---

Event 40

• Severity: Serious
• Event Summary: Main cabinet fans or blowers are not redundant in x
• Event Class: System
• Problem Description:
  The number of fans required to cool the cabinet has gone from N+1 (redundant) to N (non-redundant).
• Cause / Action:
  A fan has failed. Contact your HP support representative to check the fan.
  Something is blocking a fan's rotation. Unblock the fan.
  A fan has been removed from the cabinet. Contact your HP support representative to check the fan.
  The electrical connection to a fan has become disconnected. Reconnect the fan.
  If redundancy is not not required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 0.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 41

• Severity: Information
• Event Summary: Main cabinet fans or blowers are not redundant in x
• Event Class: System
• Problem Description:
  The number of fans required to cool the cabinet has gone from N+1 (redundant) to N (non-redundant).
• Cause / Action:
  No action is required.
  If redundancy is required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 1.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 42

• Severity: Information
• Event Summary: Redundant main cabinet fans or blowers are installed in x
• Event Class: System
• Problem Description:
  A sufficient number of main cabinet fans or blowers are installed to cool the unit, even if one should fail.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 43

• Severity: Serious
• Event Summary: I/O fan n failure in x
• Event Class: System
• Problem Description:
  An I/O fan is not functioning.
• Cause / Action:
  The fan has failed. Contact your HP support representative to check the fan.
  The electrical connection to the fan has become disconnected. Reconnect the fan.
  Something is blocking the fan's rotation. Unblock the fan.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed fans.....: 1
     Location of failed fan(s).: I/O Expansion Cabinet 
     Failed fan number(s).............: 1

---

Event 44

• Severity: Serious
• Event Summary: I/O fans are not redundant in x
• Event Class: System
• Problem Description:
  The number of fans required to cool the cabinet has gone from N+1 (redundant) to N (non-redundant).
• Cause / Action:
  An I/O fan has failed. Contact your HP support representative to check the fan.
  Something is blocking a fan's rotation. Unblock the fan.
  An I/O fan has been removed from the cabinet. Contact your HP support representative to check the fan.
  The electrical connection to a fan has become disconnected. Reconnect the fan.
  If redundancy is not not required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 0.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: I/O Expansion Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 45

• Severity: Information
• Event Summary: I/O fans are not redundant in x
• Event Class: System
• Problem Description:
  The number of fans required to cool the cabinet has gone from N+1 (redundant) to N (non-redundant).
• Cause / Action:
  No action is required.
  If redundancy is required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 1.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of fans present..........: 6
     Location of fan(s)..............: I/O Expansion Cabinet
     Present fan number(s)...........: 2,3,4,5,6,7
     Missing or failed fan number(s).: 1

---

Event 46

• Severity: Information
• Event Summary: Redundant I/O fans are installed in x
• Event Class: System
• Problem Description:
  A sufficient number of I/O fans are installed to cool the I/O chassis, even if one should fail.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 47

• Severity: Serious
• Event Summary: Cabinet (bulk) power supply n failure in x
• Event Class: System
• Problem Description:
  A cabinet (or bulk) power supply has failed.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the plug is connected to the power supply, and to a working power source.
  The power supply is disabled. If present, verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 1
     Location of failed power supplies.: Cabinet 
     Failed power supply number(s).....: 2

---

Event 48

• Severity: Serious
• Event Summary: Cabinet (bulk) power supplies are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of cabinet (or bulk) power supplies required to power the unit is currently installed and operating. There are no redundant cabinet (bulk) power supplies available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is set to 1, this is considered to be a problem.
• Cause / Action:
  A power supply has been removed from the cabinet. Contact your HP support representative to check the power supply.
  A power supply is disabled. If present, verify that the switch on the front of each power supply is in the "On" position.
  A power supply has failed. Contact your HP support representative to check the power supply.
  If redundancy is not not required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 0.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power supplies present.........: 1
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 2
     Missing or failed power supply number(s).: 1

---

Event 49

• Severity: Information
• Event Summary: Cabinet (bulk) power supplies are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of cabinet (or bulk) power supplies required to power the unit is currently installed and operating. There are no redundant cabinet (bulk) power supplies available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is not set to 1, this is not considered to be a problem.
• Cause / Action:
  No action is required.
  If redundancy is required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 1.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power supplies present.........: 1
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 2
     Missing or failed power supply number(s).: 1

---

Event 50

• Severity: Information
• Event Summary: Redundant cabinet (bulk) power supplies are installed in x
• Event Class: System
• Problem Description:
  A sufficient number of cabinet (or bulk) power supplies are installed to power the unit, even if one should fail.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 51

• Severity: Serious
• Event Summary: I/O power supply n failure in x
• Event Class: System
• Problem Description:
  An I/O power supply has failed.
• Cause / Action:
  The power supply is not connected to a working AC power source. Verify that the power supply is connected properly.
  The power supply is disabled. If present, verify that the switch on the front of the power supply is in the "On" position.
  The power supply has failed. Contact your HP support representative to check the power supply.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power supplies...: 2
     Location of failed power supplies.: Cabinet 
     Failed power supply number(s).....: 2,3

---

Event 52

• Severity: Serious
• Event Summary: I/O power supplies are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of I/O power supplies required to power the unit is currently installed and operating. There are no redundant I/O power supplies available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is set to 1, this is considered to be a problem.
• Cause / Action:
  A power supply has been removed from the cabinet. Contact your HP support representative to check the power supply.
  A power supply is disabled. If present, verify that the switch on the front of each power supply is in the "On" position.
  A power supply has failed. Contact your HP support representative to check the power supply.
  If redundancy is not not required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 0.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power supplies present.........: 2
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 0,1
     Missing or failed power supply number(s).: 2

---

Event 53

• Severity: Information
• Event Summary: I/O power supplies are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of I/O power supplies required to power the I/O chassis is currently installed and operating. There are no redundant I/O power supplies available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is not set to 1, this is not considered to be a problem.
• Cause / Action:
  No action is required.
  If redundancy is required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 1.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power supplies present.........: 2
     Location of power supplies...............: Cabinet
     Present power supply number(s)...........: 0,1
     Missing or failed power supply number(s).: 2

---

Event 54

• Severity: Information
• Event Summary: Redundant I/O power supplies are installed in x
• Event Class: System
• Problem Description:
  A sufficient number of I/O power supplies are installed to power the I/O chassis, even if one should fail.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 55

• Severity: Serious
• Event Summary: Backplane power board n failure in x
• Event Class: System
• Problem Description:
  An Backplane power board has failed.
• Cause / Action:
  The power board is not connected to a working AC power source. Verify that the power board is connected properly.
  The power board has failed. Contact your HP support representative to check the power board.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of failed power boards...: 1
     Location of failed power boards.: Cabinet 
     Failed power boards number(s)...: 2

---

Event 56

• Severity: Serious
• Event Summary: Backplane power boards are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of backplane power boards required to power the unit is currently installed and operating. There are no redundant backplane power boards available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is set to 1, this is considered to be a problem.
• Cause / Action:
  A power board has been removed from the cabinet. Contact your HP support representative to check the power board.
  A power board has failed. Contact your HP support representative to check the power board.
  If redundancy is not not required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 0.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power boards present..........: 2
     Location of power boards................: Cabinet
     Present power board number(s)...........: 0,1
     Missing or failed power board number(s).: 2

---

Event 57

• Severity: Information
• Event Summary: Backplane power boards are not redundant in x
• Event Class: System
• Problem Description:
  The minimum number of backplane power boards required to power the backplane is currently installed and operating. There are no redundant backplane power boards available in case of failure. Because the REQUIRE_REDUNDANCY parameter in the monitor's configuration file /var/stm/config/tools/monitor/dm_core_hw.cfg is not set to 1, this is not considered to be a problem.
• Cause / Action:
  No action is required.
  If redundancy is required, change the REQUIRE_REDUNDANCY parameter setting in dm_core_hw.cfg to 1.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

Device identification information:

     Number of power boards present..........: 2
     Location of power boards................: Cabinet
     Present power board number(s)...........: 0,1
     Missing or failed power board number(s).: 2

---

Event 58

• Severity: Information
• Event Summary: Redundant backplane power boards are installed in x
• Event Class: System
• Problem Description:
  A sufficient number of Backplane power boards are installed to power the backplane, even if one should fail.
• Cause / Action:
  No action is required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 59

• Severity: Information
• Event Summary: Backplane power boards are all working in x
• Event Class: System
• Problem Description:
  The currently installed backplane power boards are all operating properly.
• Cause / Action:
  A failed power board was removed. Ensure that an operational power board is installed in its place.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details: None

---

Event 60

• Severity: Critical
• Event Summary: Insufficient backplane power boards in x
• Event Class: System
• Problem Description:
  There are an insufficient number of backplane power boards installed in the cabinet to power the backplane.
• Cause / Action:
  One or more power boards have been removed from the cabinet. Contact your HP support representative to check the power board or boards.
  A power board is not connected to a working AC power source. Verify that the power board is connected properly.
  A power board has failed. Contact your HP support representative to check the power board.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

Device identification information:

     Number of power boards present..........: 2
     Location of power boards................: Cabinet
     Present power board number(s)...........: 0,1
     Missing or failed power board number(s).: 2

---

Event 61

• Severity: Information
• Event Summary: Chassis code input queue is full
• Event Class: System
• Problem Description:
  The queue used to pass chassis codes from the service processor to the OS has filled.
• Cause / Action:
  Chassis codes may be getting generated faster than the system can process them. This does not represent a problem, but is just an informational event. This condition will typically be the case for Superdome systems with multiple cells. This event is disabled on all but the initial release.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

The PDC_PAT_EVENTS function reports that the Platform circular log queue 
threshold was reached (CCI queue full).

---

Event 62

• Severity: Serious
• Event Summary: AC power not present on line x in y
• Event Class: System
• Problem Description:
  AC power is not present on the specified line. The system is configured to expect AC power on this line.
• Cause / Action:
  The power could be disconnected. Reconnect the power cord.
  A power failure may have occurred on the power grid. Investigate and fix the power failure, or wait for the failure to be corrected.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

     Power line..............................: 1
     AC Grid.................................: A

---

Event 63

• Severity: Information
• Event Summary: Cell controller to crossbar controller link error
• Event Class: System
• Problem Description:
  A recoverable error was detected by the a crossbar integrated circuit chip (XBC) on a port connected to a cell controller integrated circuit chip. This does not represent a problem unless the rate of errors is excessive. If an excessive rate of errors is detected, events with higher severity will be generated.
• Cause / Action:
  A hardware recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 6
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000006

---

Event 64

• Severity: Major Warning
• Event Summary: Multiple cell controller to crossbar controller link errors in short duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to a cell controller integrated circuit chip during a short time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 10 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 3 occurrences within 24

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 6Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000006

---

Event 65

• Severity: Serious
• Event Summary: Excessive cell controller to crossbar controller link errors in short duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to a cell controller integrated circuit chip during a short time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 10 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 3 occurrences within 24

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 6
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000006

---

Event 66

• Severity: Major Warning
• Event Summary: Multiple cell controller to crossbar controller link errors in long duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to a cell controller integrated circuit chip during a long time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 60 occurrences within 1 week
• Fault Notifier Event Generation Threshold: 60 occurrences within 1 week

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 6
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000006

---

Event 67

• Severity: Serious
• Event Summary: Excessive cell controller to crossbar controller link errors in long duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to a cell controller integrated circuit chip during a long time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 600 occurrences within 1 week
• Fault Notifier Event Generation Threshold: 600 occurrences within 1 week

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 6
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000006

---

Event 68

• Severity: Information
• Event Summary: Crossbar controller to crossbar controller link error
• Event Class: System
• Problem Description:
  A recoverable error was detected by a crossbar integrated circuit chip (XBC) on a port connected to another crossbar integrated circuit chip. This does not represent a problem unless the rate of errors is excessive. If an excessive rate of errors is detected, events with higher severity will be generated.
• Cause / Action:
  A hardware recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 1
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000001

---

Event 69

• Severity: Major Warning
• Event Summary: Multiple crossbar controller to crossbar controller link errors in short duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to another crossbar integrated circuit chip during a short time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 10 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 10 occurrences within 24

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 1
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000001

---

Event 70

• Severity: Serious
• Event Summary: Excessive crossbar controller to crossbar controller link errors in short duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to another crossbar integrated circuit chip during a short time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 100 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 100 occurrences within 24

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 1
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000001

---

Event 71

• Severity: Major Warning
• Event Summary: Multiple crossbar controller to crossbar controller link errors in long duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to another crossbar integrated circuit chip during a long time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 60 occurrences within 1 week
• Fault Notifier Event Generation Threshold: 600 occurrences within 1 week

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 1
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000001

---

Event 72

• Severity: Serious
• Event Summary: Excessive crossbar controller to crossbar controller link errors in long duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on a port connected to another crossbar integrated circuit chip during a long time duration.
• Cause / Action:
  There could be a problem with the cell controller chip. Contact your HP support representative to check the cell board.
  There could be a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 600 occurrences within 1 week
• Fault Notifier Event Generation Threshold: 600 occurrences within 1 week

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff04ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:02:04
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 4
Receiving XBC chip port.................: 1
Connected XBC chip id...................: 0
Additional error log registers:
   port error status....................: 0x0000610100006d00
   port sbe running count...............: 0x0000000000000001
   port lbe running count...............: 0x0000000000000001
   port sbe log header 0 0..............: 0x0000000000000003
   port sbe log header0 1...............: 0x00000000000001c0
   port sbe log header0 2...............: 000000000000000000
   port sbe log header1 0...............: 000000000000000000
   port sbe log header1 1...............: 000000000000000000
   port sbe log header1 2...............: 000000000000000000
   port lpe log header0 0...............: 0x0000000000000003
   port lpe log header0 1...............: 0x00000000000001c0
   port lpe log header0 2...............: 000000000000000000
   port lpe log header1 0...............: 000000000000000000
   port lpe log header1 1...............: 000000000000000000
   port lpe log header1 2...............: 000000000000000000
   port number..........................: 0x0000000000000001

---

Event 73

• Severity: Information
• Event Summary: Crossbar controller control status register error
• Event Class: System
• Problem Description:
  A recoverable error was detected by a crossbar integrated circuit chip (XBC) on its control status register (CSR) port. This does not represent a problem unless the rate of errors is excessive. If an excessive rate of errors is detected, events with higher severity will be generated.
• Cause / Action:
  A hardware recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff00ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:58:00
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 0
Receiving XBC chip port.................: 8
Additional error log registers:
   csr error status.....................: 0x0000000000000020
   csr low severity error count.........: 0x0000000000000088
   csr high severity error count........: 000000000000000000
   csr low severity error log sym0 1....: 0x0000000000005004
   csr low severity error log sym0 1....: 0x0000000000000042
   csr low severity error log sym0 1....: 0x0000000000006425
   csr low severity error log sym0 1....: 0x0000000000002004
   csr low severity error log sym0 1....: 0x0000000000000026
   csr low severity error log sym2 3....: 0x0000000000007801
   csr low severity error log sym2 3....: 0x0000000000004029
   csr low severity error log sym2 3....: 0x000000000000003f
   csr low severity error log sym2 3....: 000000000000000000
   csr low severity error log sym2 3....: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr port number log..................: 0x0000000100000000

---

Event 74

• Severity: Major Warning
• Event Summary: Multiple crossbar controller control status register errors in short duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on its control status register (CSR) port within a short time duration.
• Cause / Action:
  There is a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 10 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 10 occurrences within 24 hours

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff00ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:58:00
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 0
Receiving XBC chip port.................: 8
Additional error log registers:
   csr error status.....................: 0x0000000000000020
   csr low severity error count.........: 0x0000000000000088
   csr high severity error count........: 000000000000000000
   csr low severity error log sym0 1....: 0x0000000000005004
   csr low severity error log sym0 1....: 0x0000000000000042
   csr low severity error log sym0 1....: 0x0000000000006425
   csr low severity error log sym0 1....: 0x0000000000002004
   csr low severity error log sym0 1....: 0x0000000000000026
   csr low severity error log sym2 3....: 0x0000000000007801
   csr low severity error log sym2 3....: 0x0000000000004029
   csr low severity error log sym2 3....: 0x000000000000003f
   csr low severity error log sym2 3....: 000000000000000000
   csr low severity error log sym2 3....: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr port number log..................: 0x0000000100000000

---

Event 75

• Severity: Serious
• Event Summary: Excessive crossbar controller control status register errors in short duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on its control status register (CSR) port within a short time duration.
• Cause / Action:
  There is a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 100 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 100 occurrences within 24 hours

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff00ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:58:00
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 0
Receiving XBC chip port.................: 8
Additional error log registers:
   csr error status.....................: 0x0000000000000020
   csr low severity error count.........: 0x0000000000000088
   csr high severity error count........: 000000000000000000
   csr low severity error log sym0 1....: 0x0000000000005004
   csr low severity error log sym0 1....: 0x0000000000000042
   csr low severity error log sym0 1....: 0x0000000000006425
   csr low severity error log sym0 1....: 0x0000000000002004
   csr low severity error log sym0 1....: 0x0000000000000026
   csr low severity error log sym2 3....: 0x0000000000007801
   csr low severity error log sym2 3....: 0x0000000000004029
   csr low severity error log sym2 3....: 0x000000000000003f
   csr low severity error log sym2 3....: 000000000000000000
   csr low severity error log sym2 3....: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr port number log..................: 0x0000000100000000

---

Event 76

• Severity: Major Warning
• Event Summary: Multiple crossbar controller control status register errors in long duration
• Event Class: System
• Problem Description:
  Multiple recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on its control status register (CSR) port within a long time duration.
• Cause / Action:
  There is a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 60 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 60 occurrences within 24 hours

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff00ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:58:00
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 0
Receiving XBC chip port.................: 8
Additional error log registers:
   csr error status.....................: 0x0000000000000020
   csr low severity error count.........: 0x0000000000000088
   csr high severity error count........: 000000000000000000
   csr low severity error log sym0 1....: 0x0000000000005004
   csr low severity error log sym0 1....: 0x0000000000000042
   csr low severity error log sym0 1....: 0x0000000000006425
   csr low severity error log sym0 1....: 0x0000000000002004
   csr low severity error log sym0 1....: 0x0000000000000026
   csr low severity error log sym2 3....: 0x0000000000007801
   csr low severity error log sym2 3....: 0x0000000000004029
   csr low severity error log sym2 3....: 0x000000000000003f
   csr low severity error log sym2 3....: 000000000000000000
   csr low severity error log sym2 3....: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr port number log..................: 0x0000000100000000

---

Event 77

• Severity: Serious
• Event Summary: Excessive crossbar controller control status register errors in long duration
• Event Class: System
• Problem Description:
  An excessive number of recoverable errors have been detected by a crossbar integrated circuit chip (XBC) on its control status register (CSR) port within a long time duration.
• Cause / Action:
  There is a problem with the crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 600 occurrences within 1 week
• Fault Notifier Event Generation Threshold: 600 occurrences within 1 week

Event Details:
Examples:

FRU Physical Location:   0x00ffffffff00ff51
   FRU Source          = 5 (fabric connector)
   Source Detail       = 1 (cross bar)
   Cabinet Location    = 0
Error log time stamp: Century 20, Year 00, Month 12, Day 27 19:58:00
Error Status Register: 0x0000000000170000
   Estat.: 23:
           Bus parity error.


Receiving XBC chip id...................: 0
Receiving XBC chip port.................: 8
Additional error log registers:
   csr error status.....................: 0x0000000000000020
   csr low severity error count.........: 0x0000000000000088
   csr high severity error count........: 000000000000000000
   csr low severity error log sym0 1....: 0x0000000000005004
   csr low severity error log sym0 1....: 0x0000000000000042
   csr low severity error log sym0 1....: 0x0000000000006425
   csr low severity error log sym0 1....: 0x0000000000002004
   csr low severity error log sym0 1....: 0x0000000000000026
   csr low severity error log sym2 3....: 0x0000000000007801
   csr low severity error log sym2 3....: 0x0000000000004029
   csr low severity error log sym2 3....: 0x000000000000003f
   csr low severity error log sym2 3....: 000000000000000000
   csr low severity error log sym2 3....: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym0 1...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr high severity error log sym2 3...: 000000000000000000
   csr port number log..................: 0x0000000100000000

---

Event 78

• Severity: Serious
• Event Summary: Crossbar controller status error
• Event Class: System
• Problem Description:
  System firmware has detected a crossbar chip (XBC) error, and has marked it as being unavailable.
• Cause / Action:
  There could be a problem with the hardware which connects to this XBC port. The system firmware has found an error which prevents it from discovering the identy of the hardware connected to this port. It could be either another XBC or a cell controller. Look for other events which indicate another XBC having problems to identify the connected hardware.
  There could be a problem with this crossbar chip. Contact your HP support representative to check the backplane.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

     Receiving XBC chip id...................: 4
     Receiving XBC chip port.................: 1

---

Event 79

• Severity: Information
• Event Summary: [Crossbar controller (XBC) | Cell controller] to cell controller link error
• Event Class: System
• Problem Description:
  The cell controller (CC) chip has detected and corrected an error in data transferred to it from the [crossbar controller (XBC) | cell controller] chip to which it is connected. This does not represent a problem unless the rate of errors is excessive. If an excessive rate of errors is detected, events with higher severity will be generated.
• Cause / Action:
  A hardware recoverable error occurred. No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 detection
• Fault Notifier Event Generation Threshold: 1 detection

Event Details:
Examples:

FRU Physical Location:   0x00ffff04ffffff93
   FRU Source          = 9 (cell)
   Source Detail       = 3 (coherency controller)
   Cabinet Location    = 0
   Cell Location       = 4

XIN_PRI_MODE..............: 0x6000000000000000
   Link parity error on early 72 bits of data.  The link identified in this
   event had detected an error, but may not be the cause of it.
   Single bit parity error on duplicated bits.  The link identified in this
   event is responsible for this error.

XIN_COR_LOG_HI...........: 000000000000000000
XIN_COR_LOG_LO...........: 0x0300030003000700
XIN_COR_LOG_ECCPAR.......: 000000000000000000

---

Event 80

• Severity: Major Warning
• Event Summary: Multiple [crossbar controller (XBC) | cell controller] to cell controller link errors in short duration
• Event Class: System
• Problem Description:
  The cell controller (CC) chip has detected and corrected multiple errors in data transferred to it from the [crossbar controller (XBC) | cell controller] chip to which it is connected during a short time duration.
• Cause / Action:
  There may be a problem with the [crossbar controller (XBC) | cell c