Event 1
Event Details:
- Severity: Information
- Event Summary: Soft SCSI error
- Event Class: I/O
- Problem Description:
This code indicates that an abnormal SCSI bus or disk drive event was detected. A retry of the operation cleared the condition. (SP Event Code 0x801)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 25 occurrences/day/FRU
- Fault Notifier Event Generation Threshold: 25 occurrences/day/FRU
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:14 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:14 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 1 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Soft SCSI error Description of Error: This code indicates that an abnormal SCSI bus or disk drive event was detected. A retry of the operation cleared the condition. (SP Event Code 0x801) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef27200000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef27100000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#1 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 01 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 01 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08010000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0801 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x801 This code indicates that an abnormal SCSI bus or disk drive event was detected. A retry of the operation cleared the condition. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 2
Event Details:
- Severity: Information
- Event Summary: Illegal SCSI Bus interrupt
- Event Class: I/O
- Problem Description:
An inconsistent interrupt situation has been detected on the SP (storage-control processor). (SP Event Code 0x802)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 10 occurrences/month/FRU
- Fault Notifier Event Generation Threshold: 10 occurrences/month/FRU
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:17 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:17 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 2 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Illegal SCSI Bus interrupt Description of Error: An inconsistent interrupt situation has been detected on the SP (storage-control processor). (SP Event Code 0x802) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef27500000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef27400000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#2 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 02 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 02 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08020000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0802 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x802 An inconsistent interrupt situation has been detected on the SP (storage-control processor). SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 3
Event Details:
- Severity: Major Warning
- Event Summary: Recommend Disk Replacement
- Event Class: I/O
- Problem Description:
This disk CRU has sent status to the SP (storage-control processor) indicating that it believes it may be susceptible to a fault in the near future. (SP Event Code 0x803)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:20 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:15:20 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 3 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Recommend Disk Replacement Description of Error: This disk CRU has sent status to the SP (storage-control processor) indicating that it believes it may be susceptible to a fault in the near future. (SP Event Code 0x803) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef27800000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef27700000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#3 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 03 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 03 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08030000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0803 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x803 This disk CRU has sent status to the SP (storage-control processor) indicating that it believes it may be susceptible to a fault in the near future. We recommend replacing the drive. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 4
Event Details:
- Severity: Information
- Event Summary: Single Bit Error
- Event Class: I/O
- Problem Description:
The SP's tolerance level for single bit errors in the write cache has been exceeded. (SP Event Code 0x804)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:23 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:23 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 4 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Single Bit Error Description of Error: The SP's tolerance level for single bit errors in the write cache has been exceeded. (SP Event Code 0x804) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef27b00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef27b00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#4 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 04 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 04 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08040000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0804 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x804 This SP (storage-control processor) has experienced excessive single bit errors in the write cache. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 5
Event Details:
- Severity: Information
- Event Summary: Single Bit Error
- Event Class: I/O
- Problem Description:
The SP's tolerance level for single bit errors in the read cache has been exceeded. (SP Event Code 0x805)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:26 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:26 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 5 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Single Bit Error Description of Error: The SP's tolerance level for single bit errors in the read cache has been exceeded. (SP Event Code 0x805) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef27e00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef27e00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#5 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 05 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 05 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08050000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0805 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x805 This SP (storage-control processor) has experienced excessive single bit errors in the read cache. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 6
Event Details:
- Severity: Information
- Event Summary: Soft Media Error
- Event Class: I/O
- Problem Description:
This disk CRU has reported a media defect which was successfully cleared by the SP (storage-control processor). (SP Event Code 0x820)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 3 occurrences/month/FRU
- Fault Notifier Event Generation Threshold: 3 occurrences/month/FRU
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:29 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:29 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 6 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Soft Media Error Description of Error: This disk CRU has reported a media defect which was successfully cleared by the SP (storage-control processor). (SP Event Code 0x820) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef28100000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef28100000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#6 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 20 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 20 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08200000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0820 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x820 This disk CRU has reported a media defect which was successfully cleared by the SP (storage-control processor). SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 7
Event Details:
- Severity: Information
- Event Summary: Disk Sector Invalidated
- Event Class: I/O
- Problem Description:
The LUN that owns this disk CRU encountered a condition which required the firmware to invalidate a sector on the unit. The firmware did this to ensure that incorrect data is not returned to the host in the future. (SP Event Code 0x840)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:32 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:32 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 7 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Disk Sector Invalidated Description of Error: The LUN that owns this disk CRU encountered a condition which required the firmware to invalidate a sector on the unit. The firmware did this to ensure that incorrect data is not returned to the host in the future. (SP Event Code 0x840) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef28400000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef28400000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#7 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 40 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 40 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08400000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0840 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x840 The LUN that owns this disk CRU encountered a condition which required the firmware to invalidate a sector on the unit. The firmware did this to ensure that incorrect data is not returned to the host in the future. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 8
Event Details:
- Severity: Information
- Event Summary: Enclosure State Change
- Event Class: I/O
- Problem Description:
The SP detected that the DPE enclosure changed state. (SP Event Code 0x850)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:35 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:35 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 8 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Enclosure State Change Description of Error: The SP detected that the DPE enclosure changed state. (SP Event Code 0x850) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef28700000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef28700000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#8 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 50 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 50 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08500000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0850 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x850 This SP (storage-control processor) has detected a state change in a DPE enclosure. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 9
Event Details:
- Severity: Information
- Event Summary: Enclosure Address Error
- Event Class: I/O
- Problem Description:
The SP detected that a DPE enclosure has an invalid address. Enclosure chain shunted prior to failing enclosure. (SP Event Code 0x851)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:38 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:38 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 9 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Enclosure Address Error Description of Error: The SP detected that a DPE enclosure has an invalid address. Enclosure chain shunted prior to failing enclosure. (SP Event Code 0x851) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef28a00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef28a00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#9 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 51 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 51 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08510000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0851 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x851 This SP (storage-control processor) has detected an invalid address in a DPE enclosure. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 10
Event Details:
- Severity: Information
- Event Summary: Enclosure Duplicate Address Error
- Event Class: I/O
- Problem Description:
The SP detected that two or more DPE enclosures have the same address. Enclosure chain shunted prior to failing enclosure. (SP Event Code 0x852)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:42 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:15:41 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 10 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Enclosure Duplicate Address Error Description of Error: The SP detected that two or more DPE enclosures have the same address. Enclosure chain shunted prior to failing enclosure. (SP Event Code 0x852) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef28d00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef28d00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#10 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 08 52 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 08 52 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x08520000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0852 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x852 This SP (storage-control processor) has detected an addressconflict between two or more DPE enclosures. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 20
Event Details:
- Severity: Major Warning
- Event Summary: Hard SCSI error
- Event Class: I/O
- Problem Description:
An abnormal SCSI bus or disk drive event was detected and could not be cleared through retry operations. (SP Event Code 0x901)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:45 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:15:44 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 20 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Hard SCSI error Description of Error: An abnormal SCSI bus or disk drive event was detected and could not be cleared through retry operations. (SP Event Code 0x901) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef29000000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef29000000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#20 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 01 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 01 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09010000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0901 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x901 An abnormal SCSI bus or disk drive event was detected and could not be cleared through retry operations. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 21
Event Details:
- Severity: Serious
- Event Summary: Fan Removed
- Event Class: I/O
- Problem Description:
A fan module has been shutdown or removed from the system. (SP Event Code 0x903)- Probable Cause / Recommended Action:
Fan pack has been opened for longer than 2 minutes, or fan pack has failed and shudown due to multiple fan failures. Check to insure fan pack is fully closed. Check "REPLACE LED", if lit replace the fan module.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:15:48 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:15:47 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 21 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Fan Removed Description of Error: A fan module has been shutdown or removed from the system. (SP Event Code 0x903) Probable Cause / Recommended Action: Fan pack has been opened for longer than 2 minutes, or fan pack has failed and shudown due to multiple fan failures. Check to insure fan pack is fully closed. Check "REPLACE LED", if lit replace the fan module. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef29300000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef29300000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#21 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 03 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 03 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09030000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0903 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x903 A fan module has been shutdown or removed from the system. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 22
Event Details:
- Severity: Serious
- Event Summary: VSC Removed
- Event Class: I/O
- Problem Description:
A VSC module has been shutdown or removed from the system. (SP Event Code 0x904)- Probable Cause / Recommended Action:
A power supply unit (voltage semi-regulated converter (VSC)) has failed or has been removed for replacement. Open fan pack and check VSC Service LED's. Replace the VSC with the "REPLACE LED" indicator on.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:03 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:16:03 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 22 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : VSC Removed Description of Error: A VSC module has been shutdown or removed from the system. (SP Event Code 0x904) Probable Cause / Recommended Action: A power supply unit (voltage semi-regulated converter (VSC)) has failed or has been removed for replacement. Open fan pack and check VSC Service LED's. Replace the VSC with the "REPLACE LED" indicator on. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2a300000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef29600000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#22 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 04 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 04 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09040000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0904 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x904 A VSC module has been shutdown or removed from the system. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 23
Event Details:
- Severity: Information
- Event Summary: Chassis Overtemperature
- Event Class: I/O
- Problem Description:
A chassis overtemperature condition has been detected, the SP (storage-control processor) will attempt corrective action. (SP Event Code 0x905)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:19 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:19 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 23 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Chassis Overtemperature Description of Error: A chassis overtemperature condition has been detected, the SP (storage-control processor) will attempt corrective action. (SP Event Code 0x905) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b300000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef29900000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#23 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 05 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 05 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09050000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0905 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x905 A chassis overtemperature condition has been detected, the SP (storage-control processor) will attempt corrective action. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 24
Event Details:
- Severity: Information
- Event Summary: Unit Shutdown
- Event Class: I/O
- Problem Description:
The Unit, which this drive is a member of, has been shutdown and can no longer be accessed by the host. (SP Event Code 0x906)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:19 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:19 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 24 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Unit Shutdown Description of Error: The Unit, which this drive is a member of, has been shutdown and can no longer be accessed by the host. (SP Event Code 0x906) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b300000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef29c00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#24 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 06 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 06 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09060000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0906 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x906 The Unit, which this drive is a member of, has been shutdown and can no longer be accessed by the host. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 25
Event Details:
- Severity: Information
- Event Summary: Controller Firmware Panic
- Event Class: I/O
- Problem Description:
This SP (storage-control processor)'s firmware encountered a situation from which there was no reliable execution other than to reload itself from from disk and restart. This message is logged once the restarted session completes its initialization. (SP Event Code 0x907)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:20 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:20 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 25 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Controller Firmware Panic Description of Error: This SP (storage-control processor)'s firmware encountered a situation from which there was no reliable execution other than to reload itself from from disk and restart. This message is logged once the restarted session completes its initialization. (SP Event Code 0x907) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b400000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2a000000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#25 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 07 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 07 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09070000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0907 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x907 This SP (storage-control processor)'s firmware encountered a situation from which there was no reliable execution other than to reload itself from disk and restart. This message is logged once the restarted session completes its initialization. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 26
Event Details:
- Severity: Information
- Event Summary: Hardware fault - Cache disabling
- Event Class: I/O
- Problem Description:
Some hardware condition has caused the SP (storage-control processor) to disable the cache. (SP Event Code 0x908)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:20 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:20 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 26 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Hardware fault - Cache disabling Description of Error: Some hardware condition has caused the SP (storage-control processor) to disable the cache. (SP Event Code 0x908) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b400000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2a300000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#26 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 08 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 08 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09080000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0908 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x908 Some hardware condition has caused the SP (storage-control processor) to disable the cache. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 27
Event Details:
- Severity: Major Warning
- Event Summary: Cache dump failed
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) cannot safely dump the cache to disk. This will usually be caused by one or more of the cache dump disks being missing or failed. (SP Event Code 0x909)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:21 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:21 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 27 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Cache dump failed Description of Error: The SP (storage-control processor) cannot safely dump the cache to disk. This will usually be caused by one or more of the cache dump disks being missing or failed. (SP Event Code 0x909) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b500000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2a600000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#27 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 09 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 09 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09090000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0909 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x909 The SP (storage-control processor) cannot safely dump the cache to disk. This will usually be caused by one or more of the cache dump disks being missing or failed. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 28
Event Details:
- Severity: Major Warning
- Event Summary: Assign fails - Cache dirty unit
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) cannot assign this unit, because it is marked as having cached data outstanding, and the SP has no access to the data. (SP Event Code 0x90A)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:22 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:21 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 28 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Assign fails - Cache dirty unit Description of Error: The SP (storage-control processor) cannot assign this unit, because it is marked as having cached data outstanding, and the SP has no access to the data. (SP Event Code 0x90A) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b500000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2a900000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#28 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0A 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0A 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090A0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090A CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90A The SP (storage-control processor) cannot assign this unit, because it is marked as having cached data outstanding, and the SP has no access to the data. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 29
Event Details:
- Severity: Major Warning
- Event Summary: Controller cannot initialize cache
- Event Class: I/O
- Problem Description:
There was some hardware or software failure which occured when the SP (storage-control processor) attempted to initialize a new cache image. (SP Event Code 0x90B)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:22 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:22 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 29 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Controller cannot initialize cache Description of Error: There was some hardware or software failure which occured when the SP (storage-control processor) attempted to initialize a new cache image. (SP Event Code 0x90B) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b600000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2ac00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#29 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0B 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0B 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090B0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090B CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90B There was some hardware or software failure which occured when the SP (storage-control processor) attempted to initialize a new cache image. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 30
Event Details:
- Severity: Major Warning
- Event Summary: Cache image exceeds memory size
- Event Class: I/O
- Problem Description:
This SP (storage-control processor) is incapable of loading the saved cache data image due to insufficient cache memory size. (SP Event Code 0x90C)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:23 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:22 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 30 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Cache image exceeds memory size Description of Error: This SP (storage-control processor) is incapable of loading the saved cache data image due to insufficient cache memory size. (SP Event Code 0x90C) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b600000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2af00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#30 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0C 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0C 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090C0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090C CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90C This SP (storage-control processor) is incapable of loading the saved cache data image due to insufficient cache memory size. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 31
Event Details:
- Severity: Serious
- Event Summary: BBU Removed
- Event Class: I/O
- Problem Description:
The BBU in this system has failed or been removed. (SP Event Code 0x90D)- Probable Cause / Recommended Action:
The Battery Backup Unit (BBU) has been removed or has failed. Check for presence of BBU. If present replace if "REPLACE LED" indicator is on.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:23 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:16:23 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 31 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : BBU Removed Description of Error: The BBU in this system has failed or been removed. (SP Event Code 0x90D) Probable Cause / Recommended Action: The Battery Backup Unit (BBU) has been removed or has failed. Check for presence of BBU. If present replace if "REPLACE LED" indicator is on. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2b700000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2b200000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#31 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0D 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0D 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090D0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090D CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90D The BBU in this system has failed or been removed. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 32
Event Details:
- Severity: Serious
- Event Summary: BBU Failed
- Event Class: I/O
- Problem Description:
The BBU in this system has failed its internal selftest. (SP Event Code 0x90E)- Probable Cause / Recommended Action:
The Battery Backup Unit (BBU) has failed its internal self-test. Replace BBU with device power on.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:39 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:16:38 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 32 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : BBU Failed Description of Error: The BBU in this system has failed its internal selftest. (SP Event Code 0x90E) Probable Cause / Recommended Action: The Battery Backup Unit (BBU) has failed its internal self-test. Replace BBU with device power on. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2c600000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2b500000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#32 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0E 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0E 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090E0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090E CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90E The BBU in this system has failed its internal selftest. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 33
Event Details:
- Severity: Information
- Event Summary: Cache Recovered with Errors
- Event Class: I/O
- Problem Description:
The attempted cache recovery on this SP (storage-control processor) recovered the dirty cache pages for some, but not all, of its dirty units. (SP Event Code 0x90F)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:54 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:54 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 33 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Cache Recovered with Errors Description of Error: The attempted cache recovery on this SP (storage-control processor) recovered the dirty cache pages for some, but not all, of its dirty units. (SP Event Code 0x90F) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d600000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2b800000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#33 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 0F 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 0F 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x090F0000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x090F CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x90F The attempted cache recovery on this SP (storage-control processor) recovered the dirty cache pages for some, but not all, of its dirty units. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 34
Event Details:
- Severity: Information
- Event Summary: Cache Recovery Failed
- Event Class: I/O
- Problem Description:
The attempted cache recovery on this SP (storage-control processor) failed to recover the pages for any of its cache dirty units. (SP Event Code 0x910)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:55 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:54 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 34 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Cache Recovery Failed Description of Error: The attempted cache recovery on this SP (storage-control processor) failed to recover the pages for any of its cache dirty units. (SP Event Code 0x910) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d600000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2bb00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#34 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 10 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 10 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09100000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0910 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x910 The attempted cache recovery on this SP (storage-control processor) failed to recover the pages for any of its cache dirty units. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 35
Event Details:
- Severity: Major Warning
- Event Summary: Hard Media Error
- Event Class: I/O
- Problem Description:
This disk CRU has reported a media defect which could not be successfully cleared by the SP (storage-control processor). This is a hard media error. (SP Event Code 0x920)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:55 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:55 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 35 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Hard Media Error Description of Error: This disk CRU has reported a media defect which could not be successfully cleared by the SP (storage-control processor). This is a hard media error. (SP Event Code 0x920) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d700000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2be00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#35 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 20 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 20 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09200000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0920 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x920 This disk CRU has reported a media defect which could not be successfully cleared by the SP (storage-control processor). This is a hard media error. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 36
Event Details:
- Severity: Major Warning
- Event Summary: Host vault load failed
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) encountered multiple errors while attempting to load the cache image from disk. This message may indicate multiple drive failures. (SP Event Code 0x921)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:56 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:56 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 36 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Host vault load failed Description of Error: The SP (storage-control processor) encountered multiple errors while attempting to load the cache image from disk. This message may indicate multiple drive failures. (SP Event Code 0x921) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d800000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2c100000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#36 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 21 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 21 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09210000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0921 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x921 The SP (storage-control processor) encountered multiple errors while attempting to load the cache image from disk. This message may indicate multiple drive failures. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 37
Event Details:
- Severity: Major Warning
- Event Summary: Host vault load inconsistent
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) found the cache image on disk to have inconsistent data. This may indicate a failure or abort of the cache dump. (SP Event Code 0x922)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:57 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:56 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 37 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Host vault load inconsistent Description of Error: The SP (storage-control processor) found the cache image on disk to have inconsistent data. This may indicate a failure or abort of the cache dump. (SP Event Code 0x922) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d800000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2c500000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#37 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 22 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 22 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09220000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0922 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x922 The SP (storage-control processor) found the cache image on disk to have inconsistent data. This may indicate a failure or abort of the cache dump. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 38
Event Details:
- Severity: Major Warning
- Event Summary: Host vault load failed bitmap ok
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) successfully read the control portion of the cache image on disk, but found the data portion to be incomplete. This means that a failure or abort occurred during the cache dump. (SP Event Code 0x923)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:57 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:57 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 38 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Host vault load failed bitmap ok Description of Error: The SP (storage-control processor) successfully read the control portion of the cache image on disk, but found the data portion to be incomplete. This means that a failure or abort occurred during the cache dump. (SP Event Code 0x923) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2d900000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2c800000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#38 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 23 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 23 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09230000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0923 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x923 The SP (storage-control processor) successfully read the control portion of the cache image on disk, but found the data portion to be incomplete. This means that a failure or abort occurred during the cache dump. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 39
Event Details:
- Severity: Major Warning
- Event Summary: Host vault disks scrambled
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) found the vault drives containing the cache image to be in different order than when the cache image was dumped to disk. The drives must be restored to their original order before the SP can load the cache image. (SP Event Code 0x924)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:58 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:16:57 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 39 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Host vault disks scrambled Description of Error: The SP (storage-control processor) found the vault drives containing the cache image to be in different order than when the cache image was dumped to disk. The drives must be restored to their original order before the SP can load the cache image. (SP Event Code 0x924) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2da00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2cb00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#39 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 24 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 24 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09240000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0924 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x924 The SP (storage-control processor) found the vault drives containing the cache image to be in different order than when the cache image was dumped to disk. The drives must be restored to their original order before the SP can load the cache image. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 40
Event Details:
- Severity: Information
- Event Summary: Single Board Cache - need PROM update
- Event Class: I/O
- Problem Description:
This SP (storage-control processor), which is operating in non-mirrored caching mode, has too low a PROM revision level. Write Caching cannot be enabled. (SP Event Code 0x925)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:58 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:58 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 40 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Single Board Cache - need PROM update Description of Error: This SP (storage-control processor), which is operating in non-mirrored caching mode, has too low a PROM revision level. Write Caching cannot be enabled. (SP Event Code 0x925) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2da00000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2ce00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#40 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 25 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 25 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09250000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0925 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x925 This SP (storage-control processor), which is operating in non-mirrored caching mode, has too low a PROM revision level. Write Caching cannot be enabled. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 41
Event Details:
- Severity: Information
- Event Summary: RAID-3 Unit, Cannot Assign - No Memory
- Event Class: I/O
- Problem Description:
A RAID-3 LUN cannot be enabled because memory allocated for RAID-3 processing is not available (that is, the memory has been removed or reconfigured). (SP Event Code 0x926)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:16:59 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:59 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 41 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : RAID-3 Unit, Cannot Assign - No Memory Description of Error: A RAID-3 LUN cannot be enabled because memory allocated for RAID-3 processing is not available (that is, the memory has been removed or reconfigured). (SP Event Code 0x926) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2db00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2d100000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#41 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 26 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 26 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09260000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0926 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x926 A RAID-3 LUN cannot be enabled because memory allocated for RAID-3 processing is not available (that is, the memory has been removed or reconfigured). SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 42
Event Details:
- Severity: Information
- Event Summary: Old RAID-3, Can't Assign
- Event Class: I/O
- Problem Description:
The revision of LIC you are running does not support "old" (pre-Revision 9.X) RAID-3 LUNs. To use the new RAID-3, you must use the current revision of LIC to unbind the LUN and rebind it as a RAID-3 LUN with RAID-3 memory. (SP Event Code 0x927)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:00 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:16:59 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 42 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Old RAID-3, Can't Assign Description of Error: The revision of LIC you are running does not support "old" (pre-Revision 9.X) RAID-3 LUNs. To use the new RAID-3, you must use the current revision of LIC to unbind the LUN and rebind it as a RAID-3 LUN with RAID-3 memory. (SP Event Code 0x927) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2db00000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2d400000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#42 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 27 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 27 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09270000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0927 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x927 This LUN is bound at an unsupported RAID-3 revision level. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 43
Event Details:
- Severity: Information
- Event Summary: RAID-3 Initialization Failure - No memory
- Event Class: I/O
- Problem Description:
No RAID-3 LUNs can be enabled because memory allocated for RAID-3 processing is not abailable, (that is, the memory has been removed or reconfigured). (SP Event Code 0x928)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:00 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:17:00 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 43 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : RAID-3 Initialization Failure - No memory Description of Error: No RAID-3 LUNs can be enabled because memory allocated for RAID-3 processing is not abailable, (that is, the memory has been removed or reconfigured). (SP Event Code 0x928) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2dc00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2d700000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#43 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 28 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 28 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09280000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0928 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x928 No RAID-3 LUNs can be enabled because memory allocated for RAID-3 processing is not abailable, (that is, the memory has been removed or reconfigured). SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 44
Event Details:
- Severity: Major Warning
- Event Summary: Front End Fibre Link Down
- Event Class: I/O
- Problem Description:
The front end fibre link is down. (SP Event Code 0x929)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:01 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:01 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 44 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Front End Fibre Link Down Description of Error: The front end fibre link is down. (SP Event Code 0x929) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2dd00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2da00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#44 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 29 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 29 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09290000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0929 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x929 The front end fibre link is down. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 45
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card Write Protected While Active
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card is write protected. (SP Event Code 0x930)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:02 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:02 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 45 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card Write Protected While Active Description of Error: The PCMCIA (write-cache memory) card is write protected. (SP Event Code 0x930) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2de00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2dd00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#45 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 30 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 30 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09300000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0930 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x930 The PCMCIA (write-cache memory) card is write protected. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 46
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card Battery Failed
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card's battery failed.- Probable Cause / Recommended Action:
Replace the battery.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:05 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:05 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 46 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card Battery Failed Description of Error: The PCMCIA (write-cache memory) card's battery failed. Probable Cause / Recommended Action: Replace the battery. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2e100000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2e000000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#46 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 31 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 31 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09310000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0931 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x931 The PCMCIA (write-cache memory) card's battery failed. You must replace the battery. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 47
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card Absent or Inserted Incorrectly
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card is not present or was inserted incorrectly. (SP Event Code 0x932)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:08 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:08 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 47 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card Absent or Inserted Incorrectly Description of Error: The PCMCIA (write-cache memory) card is not present or was inserted incorrectly. (SP Event Code 0x932) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2e400000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2e300000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#47 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 32 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 32 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09320000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0932 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x932 The PCMCIA (write-cache memory) card is not present or was inserted incorrectly. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 48
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card POST Test Failed
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card failed its power up (POST) test. The SP (storage-control processor) disabled storage-system write caching Power down the storage system, replace the card, and power up the storage system. (SP Event Code 0x933)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:11 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:11 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 48 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card POST Test Failed Description of Error: The PCMCIA (write-cache memory) card failed its power up (POST) test. The SP (storage-control processor) disabled storage-system write caching Power down the storage system, replace the card, and power up the storage system. (SP Event Code 0x933) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2e700000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2e700000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#48 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 33 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 33 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09330000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0933 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x933 The PCMCIA (write-cache memory) card failed its power up (POST) test. The SP (storage-control processor) disabled storage-system write caching. Power down the storage system, replace the card, and power up the storage system. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 49
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card Doesn't Match Subsystem, Cache Date Locked
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card was used in a different storage system. The SP (storage-control processor) has locked the card to prevent cache data from being overwritten. You must either remove the card and install it in the correct storage system or clear the card. (SP Event Code 0x934)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:14 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:14 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 49 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card Doesn't Match Subsystem, Cache Date Locked Description of Error: The PCMCIA (write-cache memory) card was used in a different storage system. The SP (storage-control processor) has locked the card to prevent cache data from being overwritten. You must either remove the card and install it in the correct storage system or clear the card. (SP Event Code 0x934) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2ea00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2ea00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#49 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 34 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 34 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09340000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0934 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x934 The PCMCIA (write-cache memory) card was used in a different storage system. The SP (storage-control processor) has locked the card to prevent cache data from being overwritten. You must either remove the card and install it in the correct storage system or clear the card. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 50
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card too small for currently configured write cache
- Event Class: I/O
- Problem Description:
The PCMCIA (write-cache memory) card's capacity is smaller than the specified size of the SP (storage-control processor)'s write cache. The SP disabled storage-system write caching. You must either respecify the write cache size to equal the card's capacity or install a card with a capacity that equals the specified size. (SP Event Code 0x935)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:17 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:17 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 50 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card too small for currently configured write cache Description of Error: The PCMCIA (write-cache memory) card's capacity is smaller than the specified size of the SP (storage-control processor)'s write cache. The SP disabled storage-system write caching. You must either respecify the write cache size to equal the card's capacity or install a card with a capacity that equals the specified size. (SP Event Code 0x935) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2ed00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2ed00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#50 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 35 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 35 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09350000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0935 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x935 The PCMCIA (write-cache memory) card's capacity is smaller than the specified size of the SP (storage-control processor)'s write cache. The SP disabled storage-system write caching. You must either respecify the write cache size to equal the card's capacity or install a card with a capacity that equals the specified size. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 51
Event Details:
- Severity: Major Warning
- Event Summary: PCMCIA Card Hardware Failure
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) encountered a hardware failure while trying to write to the SP. The SP has disabled write caching. (SP Event Code 0x936)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:20 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:20 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 51 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : PCMCIA Card Hardware Failure Description of Error: The SP (storage-control processor) encountered a hardware failure while trying to write to the SP. The SP has disabled write caching. (SP Event Code 0x936) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2f000000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2f000000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#51 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 36 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 36 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09360000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0936 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x936 The SP (storage-control processor) encountered a hardware failure while trying to write to the SP. The SP has disabled write caching. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 52
Event Details:
- Severity: Information
- Event Summary: Command Failed
- Event Class: I/O
- Problem Description:
A command failed for the reason explained in the extended status word. (SP Event Code 0x937)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:23 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:17:23 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 52 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Command Failed Description of Error: A command failed for the reason explained in the extended status word. (SP Event Code 0x937) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2f300000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2f300000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#52 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 09 37 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 09 37 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x09370000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0937 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0x937 A command failed for the reason explained in the extended status word. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 60
Event Details:
- Severity: Major Warning
- Event Summary: Failed SCSI bus
- Event Class: I/O
- Problem Description:
A SCSI channel has failed; all drives on that bus are now inaccessable by the SP (storage-control processor). (SP Event Code 0xA02)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:26 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:17:26 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 60 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Failed SCSI bus Description of Error: A SCSI channel has failed; all drives on that bus are now inaccessable by the SP (storage-control processor). (SP Event Code 0xA02) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2f600000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2f600000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#60 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 02 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 02 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A020000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A02 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA02 A SCSI channel has failed; all drives on that bus are now inaccessible by the SP (storage-control processor). SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 61
Event Details:
- Severity: Information
- Event Summary: NOVRAM Unititialized
- Event Class: I/O
- Problem Description:
The non-volatile memory on this SP (storage-control processor) was found to be uninitialized. The SP has reinitialized the memory to its default state, and the SP will be functional after a reboot. (SP Event Code 0xA05)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:30 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:17:29 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 61 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : NOVRAM Unititialized Description of Error: The non-volatile memory on this SP (storage-control processor) was found to be uninitialized. The SP has reinitialized the memory to its default state, and the SP will be functional after a reboot. (SP Event Code 0xA05) Probable Cause / Recommended Action: Not available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2f900000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2f900000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#61 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 05 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 05 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A050000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A05 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA05 The non-volatile memory on this SP (storage-control processor) was found to be uninitialized. The SP has reinitialized the memory to its default state, and the SP will be functional after a reboot. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 62
Event Details:
- Severity: Critical
- Event Summary: Chassis Shutdown
- Event Class: I/O
- Problem Description:
An overtemperature situation could not be corrected. All drives in the the chassis will be shut down. (SP Event Code 0xA06)- Probable Cause / Recommended Action:
The fan pack door has been opened for longer than 2 minutes or multiple fans have failed in the fan pack. Insure the fan pack is closed. If the "REPLACE LED" indicator is on, replace the fan pack.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:33 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Jul 26 07:17:32 2000 Severity............: CRITICAL Monitor.............: ha_disk_array Event #.............: 62 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Chassis Shutdown Description of Error: An overtemperature situation could not be corrected. All drives in the the chassis will be shut down. (SP Event Code 0xA06) Probable Cause / Recommended Action: The fan pack door has been opened for longer than 2 minutes or multiple fans have failed in the fan pack. Insure the fan pack is closed. If the "REPLACE LED" indicator is on, replace the fan pack. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef2fc00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2fc00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#62 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 06 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 06 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A060000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A06 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA06 An overtemperature situation could not be corrected. All drives in the chassis will be shut down. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 63
Event Details:
- Severity: Critical
- Event Summary: Drive Failure
- Event Class: I/O
- Problem Description:
Disk drive has failed and can no longer be accessed. (SP Event Code 0xA07)- Probable Cause / Recommended Action:
Replace the disk module.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:17:48 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Jul 26 07:17:48 2000 Severity............: CRITICAL Monitor.............: ha_disk_array Event #.............: 63 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Drive Failure Description of Error: Disk drive has failed and can no longer be accessed. (SP Event Code 0xA07) Probable Cause / Recommended Action: Replace the disk module. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef30c00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef2ff00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#63 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 07 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 07 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A070000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A07 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA07 The disk drive has failed and can no longer be accessed. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 64
Event Details:
- Severity: Major Warning
- Event Summary: Data Base Sync Error
- Event Class: I/O
- Problem Description:
The SP (storage-control processor) cannot determine the correct logical configuration of all units in this system. Some units may be unusable. (SP Event Code 0xA08)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:04 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:18:03 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 64 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Data Base Sync Error Description of Error: The SP (storage-control processor) cannot determine the correct logical configuration of all units in this system. Some units may be unusable. (SP Event Code 0xA08) Probable Cause / Recommended Action: Not Available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef31b00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef30200000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#64 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 08 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 08 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A080000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A08 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA08 The SP (storage-control processor) cannot determine the correct logical configuration of all units in this system. Some units may be unusable. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 65
Event Details:
- Severity: Information
- Event Summary: Drive Too Small
- Event Class: I/O
- Problem Description:
A replacement drive has been inserted and does not have adequate capacity for a rebuild operation to begin. (SP Event Code 0xA09)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:04 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:18:04 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 65 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Drive Too Small Description of Error: A replacement drive has been inserted and does not have adequate capacity for a rebuild operation to begin. (SP Event Code 0xA09) Probable Cause / Recommended Action: Not Available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef31c00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef30500000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#65 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 09 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 09 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A090000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A09 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA09 A replacement drive has been inserted and does not have adaquate capacity for a rebuild operation to begin. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 66
Event Details:
- Severity: Critical
- Event Summary: Peer Controller Removed
- Event Class: I/O
- Problem Description:
This SP (storage-control processor)'s peer is no longer responding to queries from this SP following a period of time where the peer was known present. (SP Event Code 0xA11)- Probable Cause / Recommended Action:
The peer Storage-control Processor (SP) has been removed or has failed. Replace the SP with the "Service LED" indicator on.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:05 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Jul 26 07:18:04 2000 Severity............: CRITICAL Monitor.............: ha_disk_array Event #.............: 66 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Peer Controller Removed Description of Error: This SP (storage-control processor)'s peer is no longer responding to queries from this SP following a period of time where the peer was known present. (SP Event Code 0xA11) Probable Cause / Recommended Action: The peer Storage-control Processor (SP) has been removed or has failed. Replace the SP with the "Service LED" indicator on. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef31c00000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef30900000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#66 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 11 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 11 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A110000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A11 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA11 This SP (storage-control processor)'s peer is no longer responding to queries from this SP following a period of time where the peer was known present. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 67
Event Details:
- Severity: Major Warning
- Event Summary: Cache Memory Hard Error
- Event Class: I/O
- Problem Description:
This SP (storage-control processor), which is operating in non-mirrored caching mode, has detected a nonrecoverable memory fault in the cache memory area. (SP Event Code 0xA12)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:20 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:18:20 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 67 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Cache Memory Hard Error Description of Error: This SP (storage-control processor), which is operating in non-mirrored caching mode, has detected a nonrecoverable memory fault in the cache memory area. (SP Event Code 0xA12) Probable Cause / Recommended Action: Not Available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef32c00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef30c00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#67 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 12 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 12 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A120000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A12 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA12 This SP (storage-control processor), which is operating in non-mirrored caching mode, has detected a nonrecoverable memory fault in the cache memory area. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 68
Event Details:
- Severity: Information
- Event Summary: CRU Type Unsupported
- Event Class: I/O
- Problem Description:
This type of disk CRU is not supported by the current SP (storage-control processor) software. The disk cannot be bound or used for for host I/O. (SP Event Code 0xA13)- Probable Cause / Recommended Action:
Default- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:21 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Jul 26 07:18:21 2000 Severity............: INFORMATION Monitor.............: ha_disk_array Event #.............: 68 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : CRU Type Unsupported Description of Error: This type of disk CRU is not supported by the current SP (storage-control processor) software. The disk cannot be bound or used for for host I/O. (SP Event Code 0xA13) Probable Cause / Recommended Action: Not Available Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef32d00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef30f00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#68 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 01 0A 13 00 00 00 00 00 00 00 0x0010: 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 01 0A 13 00 00 00 00 00 00 00 5D 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x01 Information Field Valid : FALSE Information Field : 0x0A130000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x5D Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x01, RECOVERED ERROR, indicates that the last command completed successfully with some recovery action performed by the device. The additional sense code and qualifier indicate that: The Storage Processor is returning unsolicited sense data to the host, using the "Recovered Error Reporting" option for the disk array. The actual condition being reported may not be a "Recovered Error" (the "Recovered Error" sense key has been used for compatibility reasons). The "Event Code" (contained in the Information field of the sense data) reports the actual condition. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0A13 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 Event Code: 0xA13 This type of disk CRU is not supported by the current SP (storage-control processor) software. The disk cannot be bound or used for host I/O. SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
NOTE: Event numbers 80-110 have been renumbered consecutively to 110 - 140 in the December 2000 Release. Event numbers 100, 101 and 103 below are NEW events for December 2000 and after.
Event 100 (as of Dec. 2000)
- Severity: Information
- Event Summary: XXXX at hardware path x/x.x.x : Device added to monitoring
- Event Class: I/O
- Problem Description:
The device has been added to the set of devices being monitored by this monitor.- Probable Cause / Recommended Action
The device was added to the system, has started responding to the system.
The /var/stm/data/os_decode_xref file was modified to add information indicating this device is now supported by this monitor.
If the device is in the DOWN state and this monitor does not control setting the state of the device to UP (check by running the "/etc/opt/resmon/lbin/set_fix ed -L" command), use the "/etc/opt/resmon/lbin/set_fixed -n <RESOURCE_NAME>" command to set the state of the device to UP.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence <RESOURCE_NAME>
Event 101 (as of Dec. 2000)
- Severity: Critical
- Event Summary: XXXX at hardware path x/xx/x.x.x : Device removed from monitoring
- Event Class: I/O
- Problem Description:
The device has been removed from the list of devices being monitored by this monitor.- Probable Cause / Recommended Action
The device was removed from the system, has stopped responding to the system or it has been replaced with a device that is not supported by this monitor.
Run ioscan to determine the state and type of the device.
Check the /var/stm/data/os_decode_xref for the information indicating which devices are supported by this monitor.
Check other monitors to determine if they are now monitoring the device by running /etc/opt/resmon/lbin/monconfig and using the "Check monitoring" command.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 103 (as of Dec. 2000)
- Severity: Information
- Event Summary: Test event
- Event Class: I/O
- Problem Description:
This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.- Probable Cause / Recommended Action
No action required.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
NOTE: Event numbers 80-110 have been renumbered consecutively to 110 - 140.
Event 110
- Severity: INFORMATION
- Event Summary: No Sense
- Event Class:
- Problem Description:
There is no sense information to return at this time for this LUN. (Sense 00/00/00)- Probable Cause / Recommended Action:
No action necessary- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 111
- Severity: INFORMATION
- Event Summary: Not Ready
- Event Class: I/O
- Problem Description:
The LUN is reporting that it is not ready. (Sense 02/04/00)- Probable Cause / Recommended Action:
.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 112
- Severity: INFORMATION
- Event Summary: Not Ready
- Event Class: I/O
- Problem Description:
The LUN is reporting that it is becoming ready (performing an Assign). (Sense 02/04/01)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 113
- Severity: INFORMATION
- Event Summary: Not Ready
- Event Class: I/O
- Problem Description:
The LUN is reporting that it is not ready. Initializing comand required. (Sense 02/04/02)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 114
- Severity: INFORMATION
- Event Summary: Not Ready
- Event Class: I/O
- Problem Description:
The LUN reporting this sense data is indicating that it cannot be assigned to this SP for reasons other than the peer SP owning it. (Sense 02/04/03)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 115
- Severity: INFORMATION
- Event Summary: Media Error
- Event Class: I/O
- Problem Description:
Data cannot be returned for a read operaton because of an unrecoverable media error on the LUN in question. (Sense 03/11/04)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 116
- Severity: INFORMATION
- Event Summary: Media Error
- Event Class: I/O
- Problem Description:
A Verify operation has failed because of an unrecoverable media error \ on the LUN in question. (Sense 03/11/0B)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 117
- Severity: INFORMATION
- Event Summary: Hardware Error
- Event Class: I/O
- Problem Description:
The command could not be completed by the SP because of an unrecoverable \ error. (Sense 04/00/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 118
- Severity: INFORMATION
- Event Summary: Hardware Error
- Event Class: I/O
- Problem Description:
The command could not be completed by the SP because of an unrecoverable \ error. (Sense (04/05/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 119
Event Details:
- Severity: Serious
- Event Summary: Hardware Error
- Event Class: I/O
- Problem Description:
A SP microcode update was attempted, but fewer than two database (microcode-storing) disks were in the cabinet at the time. Two disks are required so that the new micrcode does not overwrite all copies of the current version, in case the new microcode does not load correctly. If the new code does not load correctly, the SP will reload the old microcode. (Sense 04/3A/00)- Probable Cause / Recommended Action:
Refer to Service Manual to determine the Database Drives. Insure at least two Data Base drives exist and retry the operation.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:18:56 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:18:56 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 119 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Hardware Error Description of Error: A SP microcode update was attempted, but fewer than two database (microcode-storing) disks were in the cabinet at the time. Two disks are required so that the new micrcode does not overwrite all copies of the current version, in case the new microcode does not load correctly. If the new code does not load correctly, the SP will reload the old microcode. (Sense 04/3A/00) Probable Cause / Recommended Action: Refer to Service Manual to determine the Database Drives. Insure at least two Data Base drives exist and retry the operation. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef35000000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef34f00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/scsi.htm#119 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 04 00 00 00 00 00 00 00 00 00 0x0010: 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 04 00 00 00 00 00 00 00 00 00 3A 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x04 Information Field Valid : FALSE Information Field : 0x00000000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x3A Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x04, HARDWARE ERROR, indicates that the device detected a nonrecoverable hardware failure (for example, controller failure, device failure, parity error, etc.) while performing the command or during a self test. The combination of Additional Sense Code and Sense Qualifier (0x3A00) indicates: Medium not present. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0000 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 120
- Severity: INFORMATION
- Event Summary: Hardware Error
- Event Class: I/O
- Problem Description:
A drive firmware update failed on one of the internal disk drives. (Sense 04/44/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 121
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The LUN specified in the identify message accompanying the command descriptor block (CDB) is not assigned to this SP. The initiator (host) can assume that the Auto-Assign attempt failed. (Sense 05/04/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 122
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The device was unsuccessful in processing the current I/O request because the parameter list for the request had the wrong length. The request was not processed. (Sense 05/1A/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 123
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The device was unsuccessful in processing the current request message because the message contained an invalid command operation code. The request was not processed. (Sense 05/20/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 124
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The Logical Block Address specified in the CDB is out of range. The request was not processed. (Sense 05/21/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 125
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The device was unsuccessful in processing the current request message because the message contained an invalid field in the command data block. The request was not processed. (Sense 05/24/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 126
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The device was unsuccessful in processing the current I/O request because the request contained a logical unit number, which is not supported by this device. The request was not processed. (Sense 05/25/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 127
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
This LUN is a global hot spare. This LUN cannot be accessed for data operations from the host. (Sense 05/25/01)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 128
- Severity: INFORMATION
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The device was unsuccessful in processing the current I/O request because a parameter in the request had an invalid value. The request was not processed. (Sense 05/26/02)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 129
Event Details:
- Severity: Serious
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The initiator (host) is attempting to download drive firmware without disabling the peer SP. (Sense 05/27/00)- Probable Cause / Recommended Action:
An operational peer SP exists in the array. The array requires that the peer SP be disabled during drive firmware download operations. Disable the peer SP then retry the download operation. WARINING: do NOT enable peer SP while drive firmware download operations are in progress. Doing so can interrupt the process, possibly causing drive failure and loss of data.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:21:16 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is SERIOUS(4). Event data from monitor: Event Time..........: Wed Jul 26 07:21:16 2000 Severity............: SERIOUS Monitor.............: ha_disk_array Event #.............: 129 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Illegal Request Description of Error: The initiator (host) is attempting to download drive firmware without disabling the peer SP. (Sense 05/27/00) Probable Cause / Recommended Action: An operational peer SP exists in the array. The array requires that the peer SP be disabled during drive firmware download operations. Disable the peer SP then retry the download operation. WARINING: do NOT enable peer SP while drive firmware download operations are in progress. Doing so can interrupt the process, possibly causing drive failure and loss of data. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef3dc00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef36e00000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#129 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 05 00 00 00 00 00 00 00 00 00 0x0010: 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 05 00 00 00 00 00 00 00 00 00 27 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x05 Information Field Valid : FALSE Information Field : 0x00000000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x27 Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal parameter in the command data block or in the additional parameters supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.). This sense key may also indicate that an invalid IDENTIFY message was received. The combination of Additional Sense Code and Sense Qualifier (0x2700) indicates: Write protected. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0000 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 130
Event Details:
- Severity: Major Warning
- Event Summary: Illegal Request
- Event Class: I/O
- Problem Description:
The initiator (host) is performing a microcode download operation, but there are no disk drives to which the SP can appropriately install the microcode. (Sense 05/3A/00)- Probable Cause / Recommended Action:
The array contains no operational disk drives which are compatible with the firmware/microcode being downloaded. The firmware does NOT need to be downloaded. No further action is necessary.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Jul 26 07:21:31 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/8_12.8.0.255.0.1 is >= 1. Its current value is MAJORWARNING(3). Event data from monitor: Event Time..........: Wed Jul 26 07:21:31 2000 Severity............: MAJORWARNING Monitor.............: ha_disk_array Event #.............: 130 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 8/12.8.0.255.0.1.0 : Illegal Request Description of Error: The initiator (host) is performing a microcode download operation, but there are no disk drives to which the SP can appropriately install the microcode. (Sense 05/3A/00) Probable Cause / Recommended Action: The array contains no operational disk drives which are compatible with the firmware/microcode being downloaded. The firmware does NOT need to be downloaded. No further action is necessary. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x397ef3eb00000000 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): 0x397ef37100000000 Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#130 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: Physical Device Path.......: 8/12.8.0.255.0.1 Inquiry Vendor ID..........: DGC Inquiry Product ID.........: C3400WDR5 Serial Number..............: hajj1 Firmware Version...........: HP03 Device Class...............: 13 Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: C3400 Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x00 SCSI LUN..........: 0x00 I/O Log Event Data: Driver Status Code..................: 0x00000000 Length of Logged Hardware Status....: 76 bytes. Offset to Logged Manager Information: 76 bytes. Length of Logged Manager Information: 34 bytes. Hardware Status: Raw H/W Status: 0x0000: 00 00 00 02 70 00 05 00 00 00 00 00 00 00 00 00 0x0010: 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 SCSI Status...: CHECK CONDITION (0x02) Indicates that a contingent allegiance condition has occurred. Any error, exception, or abnormal condition that causes sense data to be set will produce the CHECK CONDITION status. SCSI Sense Data: Undecoded Sense Data: 0x0000: 70 00 05 00 00 00 00 00 00 00 00 00 3A 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 SCSI Sense Data Fields: Error Code : 0x70 Segment Number : 0x00 Bit Fields: Filemark : 0 End-of-Medium : 0 Incorrect Length Indicator : 0 Sense Key : 0x05 Information Field Valid : FALSE Information Field : 0x00000000 Additional Sense Length : 0 Command Specific : 0x00000000 Additional Sense Code : 0x3A Additional Sense Qualifier : 0x00 Field Replaceable Unit : 0x00 Sense Key Specific Data Valid : FALSE Sense Key Specific Data : 0x00 0x00 0x00 Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal parameter in the command data block or in the additional parameters supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.). This sense key may also indicate that an invalid IDENTIFY message was received. The combination of Additional Sense Code and Sense Qualifier (0x3A00) indicates: Medium not present. Detailed Disk Array SCSI Sense Data Fields: Event Code................: 0x0000 CRU ......................: A0 LUN.......................: 0x00 Type of FRU...............: Disk Module Host SCSI ID..............: 0x00 Backend SCSI ID...........: 0x00 Extended Status ( 8-bits).: 0x00 Extended Status (32-bits).: 0x00000000 SCSI Command Data Block: (not present in log record) Manager-Specific Information: Raw Manager Data: 0x0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0020: 00 00 Manager Specific Data Fields: Data Residue...........: 0x00000000 Sense Status...........: 0x00000000 Request ID.............: 0x00000000 Additional I/O Status..: 0x00000000 BUSP Struct Pointer....: 0x00000000 Target Struct Pointer..: 0x00000000 LUN Struct Pointer.....: 0x00000000 Target ID..............: 0x00 LUN ID.................: 0x00 Sense Data Length......: 0x00 Tag....................: 0x00 Retry Count............: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Event 131
- Severity: INFORMATION
- Event Summary: Unit Attention
- Event Class: I/O
- Problem Description:
The LUN has been reset. This is reported after a power-up sequence completes or when a LUN is reset due to a SCSI Bus Reset, Bus Device Reset message, or Trespass operation. (Sense 06/29/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 132
- Severity: INFORMATION
- Event Summary: Unit Attention
- Event Class: I/O
- Problem Description:
A SCSI Clear Queue message has been received by this LUN from another initiator (host). This status indicates that all of the initiator's requests to this LUN have been aborted by the Clear Queue message. (Sense (06/2F/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 133
- Severity: INFORMATION
- Event Summary: Unit Attention
- Event Class: I/O
- Problem Description:
The SCSI Reservation for this LUN has been changed by a Force Reserve operaton. This sense key is reported to all initiators (hosts) other than the one that issued the Force Reserve command. (Sense 06/80/01)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 134
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The SP has aborted a command due to a condition in which the initiator (host) is encouraged to retry the command at a later time. (Sense 0B/00/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 135
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The SP has aborted a command due to an unrecoverable error (includes retries exhausted) on the SCSI Bus. (Sense 0B/00/06)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 136
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The initiator (host) has issued a nontagged CDB during a Contingent Allegiance that was not a Request Sense while TAGGED I/O's were present on the board for the I_T_L nexus. The SP considers this to be an invalid sequence of commands. The initiator is encouraged to reissue the command with a valid tag. (Sense 0B/2C/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 137
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The SP has aborted the command because a SCSI message the SP needed to complete the command was rejected by the initiator (host). (Sense 0B/43/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 138
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The SP has aborted the command due to Parity errors exhausting their retry count. (Sense 0B/47/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 139
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The SP has received a SCSI Initiator Detected Error message. (Sense 0B/48/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 140
- Severity: INFORMATION
- Event Summary: Aborted Command
- Event Class: I/O
- Problem Description:
The LUN has encountered an "Incorrect Initiator Connection". Examples include receiving two CDB's for the same I_T_L_Q nexus, or the mixing of tagged and untagged CDB's for a given I_T_L_Q nexus (with no outstanding Contingent Allegiance). Per the SCSI-2 specification, the SP will abort all outstanding CDB's for the I_T_L nexus. (Sense 0B/4E/00)- Probable Cause / Recommended Action:
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Event 200
Event Details:
- Severity: Critical
- Event Summary: Device Failure
- Event Class: I/O
- Problem Description:
The device is not responding to I/O.- Probable Cause / Recommended Action:
The device may have been powered off. Power it back on.
Alternatively, one or both of the terminators on the SCSI bus may be missing. Install the terminators in their proper locations at the ends of the SCSI bus.
Alternatively, the SCSI cable may have become detached from the device. Re-attach the cable.
Alternatively, the SCSI cable may have failed. Replace it.
Alternatively, the device may be in a state where it could not process this, or any, request. Cycle power to the device.
Alternatively, there could be more than one device having the same address on the SCSI bus. Make all the addresses on the SCSI bus unique.
Alternatively, the total length of all cable segments on the SCSI bus exceeds 25 meters. Replace one or more cable segments until the total length is less than this value.
Alternatively, if all of the above fail to correct the problem, the device has experienced a hardware failure. Repair or replace it, as necessary.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
- Fault Notifier Event Generation Threshold: 1 occurrence
Example:>------------ Event Monitoring Service Event Notification ------------< Notification Time: Tue Sep 5 14:21:58 2000 hprdstl6 sent Event Monitor notification information: /storage/events/disk_arrays/High_Availability/10_12.8.0.255.0.1 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Tue Sep 5 14:21:58 2000 Severity............: CRITICAL Monitor.............: ha_disk_array Event #.............: 200 System..............: hprdstl6.rose.hp.com Summary: Storage array controller at hardware path 10/12.8.0.255.0.1.0 : Device Failure Description of Error: The device is not responding to I/O. Probable Cause / Recommended Action: The device may have been powered off. Power it back on. Alternatively, one or both of the terminators on the SCSI bus may be missing. Install the terminators in their proper locations at the ends of the SCSI bus. Alternatively, the SCSI cable may have become detached from the device. Re-attach the cable. Alternatively, the SCSI cable may have failed. Replace it. Alternatively, the device may be in a state where it could not process this, or any, request. Cycle power to the device. Alternatively, there could be more than one device having the same address on the SCSI bus. Make all the addresses on the SCSI bus unique. Alternatively, the total length of all cable segments on the SCSI bus exceeds 25 meters. Replace one or more cable segments until the total length is less than this value. Alternatively, if all of the above fail to correct the problem, the device has experienced a hardware failure. Repair or replace it, as necessary. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x39b563f600000002 Monitor Version.....: B.01.00 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_ha_disk_array.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 OS Version......................: B.11.00 System Serial Number............: unavailable System Software ID..............: 2012993918 EMS Version.....................: A.03.10 STM Version.....................: A.23.00 Latest information on this event: http://docs.hp.com/hpux/onlinedocs/diag/ems/ha_disk_array.htm#200 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Product/Device Identification Information: Logger ID.........: sdisk Product Identifier: High Availability Disk Array Product Qualifier.: DGCC3400WDR5 SCSI Target ID....: 0x01 SCSI LUN..........: 0x00 >---------- End Event Monitoring Service Event Notification ----------<
Events 100000-1nnnnn
Events 100000-1nnnnn are default SCSI Events. All are asynchronous. For a list of these events, see:
- New List of SCSI Events (June 2000 and later versions of diagnostics)
- Old List of SCSI Events (Feb 1999 - March 2000 versions of diagnostics)
Top of Page / Diagnostics HOME