Remote Monitor (Events)

NOTE: As of the December 2000 release, events numbered 100 through 165 have been replaced by events numbered 200 through 265 respectively. (i.e. event 100 was replaced by event 200, event 101 was replaced by event 201, etc.)

Event 100 on the Sept 00 release is replaced by Event 200

Event 100 (New for March 01 release, HP-UX 11.00 & 11.11 and later)

• Severity: Information
• Event Summary: Disk 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 on the Sept 00 release is replaced by Event 201

Event 101 (New for March 01 release, HP-UX 11.00 & 11.11 and later)

• Severity: Critical
• Event Summary: Disk 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 102 on the Sept 00 release is replaced by Event 202

Event 103 on the Sept 00 release is replaced by Event 203

Event 103 (New for Dec 00, HP-UX 11i and later.)

• Severity: Information
• Event Summary: Test event
• Event Class: -
• 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

Event 104 on the Sept 00 release is replaced by Event 204

Event 105 on the Sept 00 release is replaced by Event 205

Event 106 on the Sept 00 release is replaced by Event 206

Event 107 on the Sept 00 release is replaced by Event 207

Event 108 on the Sept 00 release is replaced by Event 208

Event 109 on the Sept 00 release is replaced by Event 209

Event 110 on the Sept 00 release is replaced by Event 210

Event 111 on the Sept 00 release is replaced by Event 211

Event 113 on the Sept 00 release is replaced by Event 213

Event 114 on the Sept 00 release is replaced by Event 214

Event 116 on the Sept 00 release is replaced by Event 216

Event 117 on the Sept 00 release is replaced by Event 217

Event 118 on the Sept 00 release is replaced by Event 218

Event 119 on the Sept 00 release is replaced by Event 219

Event 120 on the Sept 00 release is replaced by Event 220

Event 122 on the Sept 00 release is replaced by Event 222

Event 123 on the Sept 00 release is replaced by Event 223

Event 124 on the Sept 00 release is replaced by Event 224

Event 125 on the Sept 00 release is replaced by Event 225

Event 127 on the Sept 00 release is replaced by Event 227

Event 128 on the Sept 00 release is replaced by Event 228

Event 129 on the Sept 00 release is replaced by Event 229

Event 130 on the Sept 00 release is replaced by Event 230

Event 131 on the Sept 00 release is replaced by Event 231

Event 132 on the Sept 00 release is replaced by Event 232

Event 133 on the Sept 00 release is replaced by Event 233

Event 134 on the Sept 00 release is replaced by Event 234

Event 135 on the Sept 00 release is replaced by Event 235

Event 136 on the Sept 00 release is replaced by Event 236

Event 137 on the Sept 00 release is replaced by Event 237

Event 138 on the Sept 00 release is replaced by Event 238

Event 139 on the Sept 00 release is replaced by Event 239

Event 140 on the Sept 00 release is replaced by Event 240

Event 141 on the Sept 00 release is replaced by Event 241

Event 142 on the Sept 00 release is replaced by Event 242

Event 143 on the Sept 00 release is replaced by Event 243

Event 144 on the Sept 00 release is replaced by Event 244

Event 145 on the Sept 00 release is replaced by Event 245

Event 147 on the Sept 00 release is replaced by Event 247

Event 148 on the Sept 00 release is replaced by Event 248

Event 149 on the Sept 00 release is replaced by Event 249

Event 150 on the Sept 00 release is replaced by Event 250

Event 151 on the Sept 00 release is replaced by Event 251

Event 152 on the Sept 00 release is replaced by Event 252

Event 153 on the Sept 00 release is replaced by Event 253

Event 154 on the Sept 00 release is replaced by Event 254

Event 155 on the Sept 00 release is replaced by Event 255

Event 156 on the Sept 00 release is replaced by Event 256

Event 165 on the Sept 00 release is replaced by Event 265

Event 199

• Severity: Critical
• Event Summary: Lost connection to host.
• Event Description: No longer able to communicate with the host.
• Probable Cause/ Recommended Action: Verify device is properly connected to host.

Event 200

• Severity: Critical
• Event Summary: Data unavailable.
• Event Description: The controller cannot retrieve some portion of host data. The most common cause would be the failure or removal of a sufficient number of drives that the data and its redundancy are not available.
• Probable Cause/ Recommended Action: Check the controller log for information.

Event 201

• Severity: Major Warning
• Event Summary: Redundancy Loss.
• Event Description: Some data in the subsystem lacks redundancy and is exposed to becoming unavailable if further drive removals or failures occur.
• Probable Cause/ Recommended Action: Check the controller log data for help in finding the source of this problem. Also, consult the resiliency settings using the armdsp command for more information on the extent of the redundancy loss.

Event 202

• Severity: Major Warning
• Event Summary: NVRAM Battery Depletion in {FRU Location}.
• Event Description: The batteries that backup NVRAM in the array controllers have been depleted to the point where removing power from the controller may cause data loss.
• Probable Cause/ Recommended Action: Do NOT remove power from the controllers. If the array needs to be shut down, perform the proper shutdown sequence. If a battery or batteries have failed (check the controller logs) then the array should be properly shutdown prior to replacing the failed component(s). It could be that the battery is missing. Due to the efforts of automatic battery charging features, this warning may be resolved after a period of time without user intervention.

Event 203

• Severity: Major Warning
• Event Summary: Hot Spare unavailable.
• Event Description: The host indicated that hot spare space reservation was desired but the space left unallocated was insufficient to provide the reservation.
• Probable Cause/ Recommended Action: Most of the time this can be resolved by adding one or more drives to the array. Check the hot spare flag to see if it is enabled using the armdsp command.

Event 204

• Severity: Major Warning
• Event Summary: Disk in slot {FRU Location} has failed.
• Event Description: One or more physical drives have failed. This state indicates that the controller has determined that an included drive is not sufficiently functional to be used.
• Probable Cause/ Recommended Action: Replace the physical drive or drives.

Event 205

• Severity: Minor Warning
• Event Summary: Capacity Depletion.
• Event Description: Unallocated capacity has fallen below the threshold specified by the capacity threshold mode parameter.
• Probable Cause/ Recommended Action: Either add more physical drives or delete a snapshot LUN.

Event 206

• Severity: Major Warning
• Event Summary: Rebuild failed.
• Event Description: A rebuild operation failed.
• Probable Cause/ Recommended Action: The most likely cause is that unallocated space is insufficient to contain the required redundant data. Add more physical drives so that the rebuild can finish. Check the controller logs for more information.

Event 207

• Severity: Major Warning
• Event Summary: NVRAM Failure in {FRU Location}.
• Event Description: One or more NVRAM DIMMs has failed.
• Probable Cause/ Recommended Action: Replace all NVRAM DIMMS in the controller.

Event 208

• Severity: Major Warning
• Event Summary: The controller in slot {FRU Location} has failed.
• Event Description: The controller in slot {FRU Location} has failed.
• Probable Cause/ Recommended Action: Check the controller logs for more information.

Event 209

• Severity: Information
• Event Summary: Degraded JBOD Enclosure Monitoring.
• Event Description: One or more JBOD enclosures in the subsystem are currently running with fewer than two functional enclosure services devices that are monitoring the status of the enclosure. The enclosure (FRU Location) may be at fault.
• Probable Cause/ Recommended Action: Check the output of the armdsp command to determine which JBOD enclosure is running with only one LCC or some other problem that would result in a failure or loss of communication.

Event 210

• Severity: Minor Warning
• Event Summary: Some drives are in the wrong redundancy group.
• Event Description: One or more drives in the subsystem have been placed in slots that are not correct for the redundancy group (RG) they belong to. Drives belonging to RG1 should be in odd numbered slots while RG2 drives belong in the even number slots.
• Probable Cause/ Recommended Action:Move the drive in question back to an appropriate slot.

Event 211

• Severity: Major Warning
• Event Summary: Power supply failed in slot {FRU Location}.
• Event Description: A power supply has failed.
• Probable Cause/ Recommended Action: Replace the power supply.

Event 212

• Severity: Critical
• Event Summary: Excessive missing drives.
• Event Description: The subsystem has experienced a loss of multiple drives, which it assumes is the result of the loss of power to an external JBOD enclosure. It will continue to process data requests in a manner that will allow it to resume normal operation once the drives have been made available to the system again. At some point, I/Os being processed by the subsystem will be suspended internally waiting for the drives to return and may incur a host timeout as a result.
• Probable Cause/ Recommended Action: Check the logs. Check all cables (power and data) to any external JBOD connected to the array.

Event 213

• Severity: Minor Warning
• Event Summary: Missing Drive {FRU Location}.
• Event Description: One or more member drives are missing.
• Probable Cause/ Recommended Action: Re-install the missing member drive or drives.

Event 214

• Severity: Major Warning
• Event Summary: Memory Configuration Mismatch.
• Event Description: A DIMM has been detected that the controller is unable to use. The DIMM configuration for all controllers in the subsystem must be the same.
• Probable Cause/ Recommended Action: This situation can arise as the result of improper installation of memory components or as the result of a failure of one or more memory components. Check the output of the armdsp command for DIMM configuration.

Event 215

• Severity: Critical
• Event Summary: JBOD Port Speed Mismatch.
• Event Description: One or more controllers in the subsystem detects that there is a conflict between the operating speed of the external JBOD loop pairs and the requested operating speed of the controllers' JBOD fibre channel ports.
• Probable Cause/ Recommended Action: Ensure the setting for the controller enclosure JBOD data rate matches the speed selection switches on the external JBOD enclosures. Once the settings are synchronized, power cycle the array.

Event 216

• Severity: Major Warning
• Event Summary: RAM not mirrored.
• Event Description: The mirroring hardware was unable to keep the two NVRAM images synchronized across the two controllers.
• Probable Cause/ Recommended Action: Check both the controller logs and the output of armdsp command for more information.

Event 217

• Severity: Minor Warning
• Event Summary: State Changing.
• Event Description: A hot plug event has occurred that the controller is still processing.
• Probable Cause/ Recommended Action: Do not remove another FRU until the controller has finished processing the recent event.

Event 218

• Severity: Critical
• Event Summary: Code Mismatch.
• Event Description: The controllers installed in the subsystem do not have the same revision of firmware installed.
• Probable Cause/ Recommended Action: Shutdown the system and install controllers with the same revision of firmware. Check the controller logs and the output of armdsp for more information.

Event 219

• Severity: Critical
• Event Summary: Controller Mismatch.
• Event Description: The controllers installed in the subsystem were designed for different AutoRAID products and cannot operate together.
• Probable Cause/ Recommended Action: Shutdown the system and install the correct controllers.

Event 220

• Severity: Critical
• Event Summary: Recovery Failed.
• Event Description: A recover operation has failed or was interrupted by powerfail or reset. In this condition some data may be available, but the controller has evidence that some data may have been corrupted due to multiple failures.
• Probable Cause/ Recommended Action: If the recovery was interrupted, it should be retried. If not, the data may be lost and the only way to recover is restoring from back up media.

Event 221

• Severity: Critical
• Event Summary: Battery Charger Microcode Download Interrupted.
• Event Description: The initialization process found that a Battery Charger microcode download was in progress when the most recent reset occurred. As a result, the Battery Charger processor cannot perform its job.
• Probable Cause/ Recommended Action: This can be resolved by successfully retrying the download operation.

Event 222

• Severity: Minor Warning
• Event Summary: Single Controller.
• Event Description: The array has a single controller present. Because of this, subsystem metadata is not stored redundantly exposing it to a single failure.
• Probable Cause/ Recommended Action: Follow the instructions for installing a second controller.

Event 223

• Severity: Minor Warning
• Event Summary: Secure Mode.
• Event Description: The array is operating in a secure mode with respect to NVRAM. A failure has occurred in such a manner that NVRAM is no longer reliable. Therefore, array firmware has entered a mode where operations that require non-volatility of the RAM are performed in a secure, lower performance manner.
• Probable Cause/ Recommended Action: Check the controller logs for more information.

Event 224

• Severity: Major Warning
• Event Summary: Battery Failure in {FRU Location}.
• Event Description: One or more of the batteries that maintain the controller NVRAM hardware is missing or has failed.
• Probable Cause/ Recommended Action: Using proper procedures, replace or install the battery in the controller.

Event 225

• Severity: Major Warning
• Event Summary: GBIC problem in {FRU Location}.
• Event Description: A GigaBit Interface Converter (GBIC) has a problem.
• Probable Cause/ Recommended Action: Check the controller logs for more information.

Event 226

• Severity: Major Warning
• Event Summary: Real Time Clock Battery Failure in {FRU Location}.
• Event Description: The battery that maintains the Real Time Clock and NVSRAM is reporting that it is low.
• Probable Cause/ Recommended Action:Using proper procedures, replace the controller.

Event 227

• Severity: Major Warning
• Event Summary: ID Module Problem.
• Event Description: The ID module has failed or is not installed. This module is necessary to provide subsystem identification information.
• Probable Cause/ Recommended Action: Replace or install the ID module.

Event 228

• Severity: Major Warning
• Event Summary: BBU Failure in {FRU Location}.
• Event Description: One or more of the subsystem Battery Backup Units (BBUs) has failed or is not installed. In this state, the subsystem may not be able to tolerate an unexpected power loss without some or all data becoming unavailable.
• Probable Cause/ Recommended Action: Replace or install a BBU.

Event 229

• Severity: Minor Warning
• Event Summary: BBU Discharged.
• Event Description: One or more of the subsystem Battery Backup Units (BBUs) is in a discharged state such that it could not perform its duties in the event of a power failure.
• Probable Cause/ Recommended Action: Due to the efforts of automatic battery charging features, this warning may be resolved, after a period of time without user intervention.

Event 230

• Severity: Major Warning
• Event Summary: IO Module Problem in {FRU Location}.
• Event Description: One or more of the IO Modules has failed or is missing.
• Probable Cause/ Recommended Action: Replace or install the ID module.

Event 231

• Severity: Major Warning
• Event Summary: LCC Problem in {FRU Location}.
• Event Description: One or more JBOD LCCs has a problem.
• Probable Cause/ Recommended Action: Replace the JBOD LCC.

Event 232

• Severity: Major Warning
• Event Summary: Link Down in {FRU Location}.
• Event Description: One or more of the active fibre channel links connecting the subsystem to hosts or connecting disks to the subsystem is in the down state.
• Probable Cause/ Recommended Action: This could be due to the failure of Gigabit Interface Converters GBICs, inadvertent disconnection of FC link cables, or the failure of other components in the array controllers.

Event 233

• Severity: Minor Warning
• Event Summary: Too Many Drives.
• Event Description: There are more drives, attached to the array controller enclosure, than can be used by the subsystem.
• Probable Cause/ Recommended Action: Consult the armdsp command for the limit on the maximum number of attached drives. Drives that are removed need to be one at a time to insure proper redundancy. Each time a drive is removed, check the state of the array. If the array is rebuilding, wait for the rebuild to complete before removing another drive.

Event 234

• Severity: Minor Warning
• Event Summary: Too Many Drives per Loop Pair.
• Event Description: There are more drives, connected to a loop pair, than the subsystem can manage.
• Probable Cause/ Recommended Action: If possible, the execc drives should be moved to another loop pair. Consult the armdsp command for the limit on the maximum number of attached drives. Drives that are removed need to be removed one at a time to insure proper redundancy. Each time a drive is removed, check the state of the array. If the array is rebuilding, wait for the rebuild to complete before removing another drive.

Event 235

• Severity: Minor Warning
• Event Summary: Too Many JBOD Enclosures.
• Event Description: There are more JBOD enclosures, attached to the array controller enclosure, than can be used by the subsystem.
• Probable Cause/ Recommended Action: Consult the armdsp command for the limit on the maximum number of attached JBOD enclosures.

Event 236

• Severity: Minor Warning
• Event Summary: Too Many JBOD Enclosures per Loop Pair.
• Event Description: There are more JBOD enclosures, connected to a loop pair, than can be used by the subsystem.
• Probable Cause/ Recommended Action: If possible, the exess enclosures should be moved to another loop pair. Consult the armdsp command for the limit on the maximum number of attached JBOD enclosures.

Event 237

• Severity: Minor Warning
• Event Summary: Loop Pairs Unbalanced.
• Event Description: There is significant imbalance in the distribution of JBOD enclosures amongst the loop pairs of the subsystem.
• Probable Cause/ Recommended Action: Consult the output from armdsp to observe the current configuration. The enclosures should be configured so that there are an equal or nearly equal number on each loop pair.

Event 238

• Severity: Minor Warning
• Event Summary: Non redundant disk access.
• Event Description: The configuration of the subsystem is such that one or more drives has only a single path of access to it. In the event of failure of that access path, that drive would become inaccessible to the subsystem.
• Probable Cause/ Recommended Action: This condition can arise from specific drive failures as well as incorrect configuration of the loop pairs. The output from the armdsp command should show the cause of the lack of redundancy.

Event 239

• Severity: Major Warning
• Event Summary: Target addressing conflict in {FRU Location}.
• Event Description: One or more of the target devices (attached to the JBOD ports) were unable to obtain their hard address during the fibre channel address acquisition process.
• Probable Cause/ Recommended Action: This is usually the result of incorrect configuration of the enclosure ID switches on the JBOD LCCs.

Event 240

• Severity: Critical
• Event Summary: Over-temperature out of range in {FRU Location}.
• Event Description: Temperature sensors in one or more of the subsystem enclosures are reporting temperature(s) that exceed the maximum recommended value for reliable operation of the subsystem.
• Probable Cause/ Recommended Action: The source of excessive temperature can be determined using the armdsp command directed to the individual enclosures that comprise the subsystem. If this persists, the array will automatically shutdown.

Event 241

• Severity: Critical
• Event Summary: FRU Monitor failure.
• Event Description: An internal FRU monitoring resource has become inoperative. The FRUs that it monitors are likely to be functional and continue to operate properly. However, the array controller(s) cannot report their failures when and if they occur. The subsystem cannot accurately determine the location of the fault that causes this failure.
• Probable Cause/ Recommended Action: This can be either a mid plane or a controller problem.

Event 242

• Severity: Major Warning
• Event Summary: JBOD LCC firmware mismatch in {FRU Location}.
• Event Description: One or more of the JBOD enclosures in the subsystem contain LCC components that have mismatched firmware.
• Probable Cause/ Recommended Action: Consult the output of the armdsp command for information on the firmware revisions for the LCC components.

Event 243

NO LONGER GENERATED.

Event 244

• Severity: Critical
• Event Summary: JBOD Port Addressing Conflict.
• Event Description: One or more of the JBOD fibre channel ports in the subsystem were unable to obtain their desired hard address during the most recent Loop Initialization Process.
• Probable Cause/ Recommended Action: This is most likely due to an addressing conflict with other ports on the loop.

Event 245

• Severity: Critical
• Event Summary: Host Fibre Channel Offline.
• Event Description: One or more of the host fibre channel ports in the subsystem did not go online after the most recent reset. This is due to the fact that the mode parameter that specifies the loop ID for the port has specified that the port not go online.
• Probable Cause/ Recommended Action: This situation can be remedied by selecting a valid loop ID for the host port(s) using the virtual front panel.

Event 249

• Severity: Major Warning
• Event Summary: Map disk redundancy loss.
• Event Description: Some or all of the subsystem metadata stored on map disks lacks redundancy.
• Probable Cause/ Recommended Action: Check the controller logs for more information.

Event 250

• Severity: Major Warning
• Event Summary: One or more JBODs have unsupported enclosure ids.
• Event Description: One or more JBOD enclosures in the subsystem have enclosure IDs that are not supported by the subsystem. This conflict usually arises from addressing conflicts between drives in the controller enclosure and drives in the external JBOD enclosures.
• Probable Cause/ Recommended Action: Determine which JBOD has an incorrect enclosure setting, set the enclosure setting switch to a valid setting; then reset the JBOD in question.

Event 251

• Severity: Major Warning
• Event Summary: Insufficient map disks.
• Event Description: There are not enough functional map disks installed in the subsystem to redundantly store metadata.
• Probable Cause/ Recommended Action: Additional map disks should be installed or failed map disks should be replaced.

Event 252

• Severity: Critical
• Event Summary: No map disks.
• Event Description: The subsystem can identify no disks suitable for use in storing subsystem metadata.
• Probable Cause/ Recommended Action: Either no disks are installed, the installed disks have failed, or the disks that are installed are unsuitable for use as map disks.

Event 253

• Severity: Critical
• Event Summary: Enclosure ID switch mismatch in {FRU Location}.
• Event Description: One or more JBOD enclosures in the subsystem contain enclosure controllers (LCCs) that have enclosure ID switch settings that do not match.
• Probable Cause/ Recommended Action:
  Having these switches set to the same value is a prerequisite for correct operation of the array.

Event 254

NO LONGER GENERATED.

Event 255

• Severity: Critical
• Event Summary: Memory Image Mismatch.
• Event Description: A controller was hot installed into a subsystem that already contained a functional controller. The memory image on the new controller is not compatible with the existing controller and, as a result, the new controller must operate in an independent degraded mode.
• Probable Cause/ Recommended Action:
  Remove the hot plugged controller and install one that is compatible with the existing controller.

Event 256

• Severity: Critical
• Event Summary: Identity Crisis.
• Event Description: Nonvolatile storage for the subsystem worldwide names and serial numbers has failed. In some products, this may be due simply to the absence of the ID module. In other products, this warning represents the failure of the midplane component. In either case, the subsystem will continue to operate properly until the next reset operation occurs. After this, positive identification of the subsystem identity is not possible and no host communication will be possible.
• Probable Cause/ Recommended Action:
  An orderly shutdown of the subsystem and repair of the NV storage should be performed as soon as possible.

Event 257

• Severity: Minor Warning
• Event Summary: Power Switch Sensor Mismatch.
• Event Description: The circuitry that senses the state of the power switch is composed of two redundant sensors. This failure occurs as a result of the two sensors returning conflicting data regarding the state (position) of the power switch. As a result, the subsystem cannot verify that a valid power down request has been made and will continue to operate with this warning asserted. .
• Probable Cause/ Recommended Action:
  An orderly shutdown of the subsystem and repair of the defect power switch sensor should be performed as soon as possible.

Event 258

• Severity: Critical
• Event Summary: Midplane Failure.
• Event Description: The subsystem has detected a failure of some sort in the midplane component of the array controller enclosure.
• Probable Cause/ Recommended Action:
  Replacement of this FRU (midplane) is required to correct this warning.

Event 265

• Severity: Minor Warning
• Event Summary: Disk in slot {FRU Location} belongs to a different disk set.
• Event Description: One or more physical drives have been previously used. This state indicates that the drive contains information that indicates it was previously being used by another array controller. A user removed the drive from another subsystem and inserted it into this subsystem.
• Probable Cause/ Recommended Action:
  Either put the drive back into the original array or include it. Inclusion of a physical drive can be accomplished in two ways: 1. Enable the Auto Include flag using the armmgr command. 2. Include the drive using the armcfg command.

Event 303

• Severity: Critical
• Event Summary: No Quorum.
• Event Description: This state indicates that the part field in the Subsystem Parameters mode page is clear and that not enough volume set member drives are available to continue without partitioning the volume set.
• Probable Cause/ Recommended Action:
  Either add more volume set member drives or format the array.

Event 304

• Severity: Critical
• Event Summary: No Map.
• Event Description: This state indicates that the subsystem lacks internal metadata that is critical to continued operation. The data structures necessary to perform host data storage commands have been lost or have not been created.
• Probable Cause/ Recommended Action:
  When the subsystem reaches this state, the possibility of recovery of lost data is remote (ignoring the case where drives and/or controllers were simply removed and are reinserted). Recovery of extremely important data can be attempted using the recovery command (arm-recover). The other recommendation is to format the array, re-configure LUNs, and restore data from back up media.

Event 308

• Severity: Major Warning
• Event Summary: No Code: Controller {FRU Location}.
• Event Description:
  This state indicates that the controller has lost microcode. This state is entered when the FLASH ROM is erased in preparation for firmware update and persists until the subsystem is reset following a successful update of firmware. NOTE: Field exchange and replacement controllers are originally placed in a no code state. When one of these controllers are installed in an array with another controller that has code, it will automatically get the same code as its mate during one of the initialization steps. This is a normal operation. Getting this NO CODE error indicates a problem with the controller.
• Probable Cause/ Recommended Action:
  Replace the controller indicated.

Event 312

• Severity: Critical
• Event Summary: Mismatched Code.
• Event Description:
  This state indicates that the two controllers have different firmware revisions. In this state, the two controllers operate independently.
• Probable Cause/ Recommended Action:
  This error can be fixed by downloading code (copying) through the primary controller (which will cause the download to both controllers).

Event 313

• Severity: Critical
• Event Summary: Controller Mismatch.
• Event Description:
  This state indicates that the secondary controller is a different revision than the primary controller. The primary controller will operate in another state independently from the secondary controller which reports this state.
• Probable Cause/ Recommended Action:
  This error can only be fixed by replacing one of the controllers with a controller revision that matches the other controller.

Event 314

• Severity: Minor Warning
• Event Summary: Disk Format Mismatch.
• Event Description:
  One or more disks installed contain a disk format that indicates the drive was previously used by an HP AutoRAID Disk Array with a disk format that is incompatible with the expectations of this subsystem.
• Probable Cause/ Recommended Action:
  Either format the subsystem to erase the previous disk format (erasing ALL user data) or remove the disks with the incompatible format.

Event 315

• Severity: Critical
• Event Summary: Memory Configuration Mismatch.
• Event Description:
  There is not a consistent configuration of usable (functional) memory installed in all controllers in the subsystem. This could be due to differences in installed components or due to failures of existing components. The controllers will continue to operate independently until the mismatch has been identified and repaired.
• Probable Cause/ Recommended Action:
  Successful recovery from this state involves a successful shutdown of the subsystem, correction of the problem, and a subsequent power on reset.

Event 316

• Severity: Critical
• Event Summary: Memory Image Mismatch.
• Event Description:
  All controllers in the subsystem appear to have valid contents in their NVRAM's but the contents of these memories do not match despite the fact that they all appear to belong with the current enclosure. As a result, controller firmware cannot choose one of the images and synchronize all controllers to it.
• Probable Cause/ Recommended Action:
  Proper recovery from this state involves choosing a controller with the proper image and invalidating the images on all other controllers.

Event 317

• Severity: Critical
• Event Summary: Midplane auto-repair failure.
• Event Description:
  The power-on process discovered a replacement midplane assembly. However, none of the controllers present in the subsystem contain a valid NVRAM image which is required for proper initialization of the replacement midplane.
• Probable Cause/ Recommended Action:
  Recovery from this state can only be accomplished by installation of a controller with a valid NVRAM image.

Event 318

• Severity: Critical
• Event Summary: Image repair needed.
• Event Description:
  The preferred NVRAM image has uncorrectable memory errors. The other controller does not have a "matching" image that firmware can use for repair. It could be an older NVRAM image, an invalid image, or an image that does not belong with the enclosure.
• Probable Cause/ Recommended Action:
  Remove the controller with the non-matching image and reinstall the controller that was previously paired with the controller that has memory errors. Check the controller logs for information that may help with this selection. NOTE: If a controller with a "matching" image is not available, map loss will occur.

Event 319

• Severity: Critical
• Event Summary: NVRAM Identity storage failure.
• Event Description:
  During a reset operation, an identity storage failure was detected. As a result, the subsystem identity cannot positively be determined. As a result, none of the host ports will be brought online.
• Probable Cause/ Recommended Action:
  Repair of the identity storage device is required to resolve this problem.

Event 320

• Severity: Critical
• Event Summary: Dual controller communication failure.
• Event Description:
  The controllers are not able to communicate over the TWSI so the NWAY communication channel cannot be enabled. Consequently, a NVRAM image selection can not be made. One or the other of the controllers must have a hardware failure of some sort.
• Probable Cause/ Recommended Action:
  Replace the failed controller. Search the controller logs for a history of problems that may relate to one of the controllers. This will help identify the failed controller.

Event 400

• Severity:<log-severity>
• Event Summary:Event generated by Array Logs and detail not available. Refer to the description for more information.
• Event Description:
  <log-code>:<log-description>
• Probable Cause/ Recommended Action:
  Correlate the description and take appropriate action.

  Where <log-severity> is the array log severity level, <log-code> is the array log code number, and <log-description> is the text description for the array log event.

Event 2001

• Severity: Serious
• Event Summary: Temperature element has failed.
• Event Description: One or more temperature elements have failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2002

• Severity: Serious
• Event Summary: Temperature is in an over temperature failure condition.
• Event Description:
  One or more temperature elements indicate a failure condition.
• Probable Cause/ Recommended Action:
  Verify the air flow and/or replace the FRU (Field Replaceable Unit).

Event 2003

• Severity: Serious
• Event Summary: Temperature is in an under temperature failure condition.
• Event Description: One or more temperature elements indicate a failure condition.
• Probable Cause/ Recommended Action: Verify the air flow and/or replace the FRU (Field Replaceable Unit).

Event 2004

• Severity: Minor Warning
• Event Summary: Temperature is in an over temperature warning condition.
• Event Description: One or more temperature elements indicate a warning condition.
• Probable Cause/ Recommended Action: Verify the air flow and/or replace the FRU (Field Replaceable Unit).

Event 2005

• Severity: Minor Warning
• Event Summary: Temperature is in an under temperature warning condition.
• Event Description: One or more temperature elements indicate a warning condition.
• Probable Cause/ Recommended Action: Verify the air flow and/or replace the FRU (Field Replaceable Unit).

Event 2006

• Severity: Serious
• Event Summary: Voltage element has failed.
• Event Description: One or more voltage elements have failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2007

• Severity: Serious
• Event Summary: Voltage is in an over voltage failure condition.
• Event Description: One or more voltage elements indicate a failed condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2008

• Severity: Serious
• Event Summary: Voltage is in an under voltage failure condition.
• Event Description: One or more voltage elements indicate a failed condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2009

• Severity: Minor Warning
• Event Summary: Voltage is in an over voltage warning condition.
• Event Description: One or more voltage elements indicate a warning condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2010

• Severity: Minor Warning
• Event Summary: Voltage is in an under voltage warning condition.
• Event Description: One or more voltage elements indicate a warning condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2011

• Severity: Serious
• Event Summary: Port has failed.
• Event Description: One or more ports have failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2012

• Severity: Serious
• Event Summary: Port is in a loss of link condition.
• Event Description: One or more ports indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2013

• Severity: Serious
• Event Summary: Port is in a transmit failure condition.
• Event Description: One or more ports indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2014

• Severity: Serious
• Event Summary: Disk has failed.
• Event Description: One or more disk slots have failed.
• Probable Cause/ Recommended Action: Replace the enclosure.

Event 2015

• Severity: Serious
• Event Summary: Disk is in a drive fault sensed condition.
• Event Description: One or more disk slots indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the enclosure.

Event 2016

• Severity: Serious
• Event Summary: Fan has failed.
• Event Description: One or more fans have failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2017

• Severity: Serious
• Event Summary: Fan is in an off condition.
• Event Description: One or more fans indicate an off state.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2018

• Severity: Serious
• Event Summary: Power supply has failed.
• Event Description: One or more power supplies have failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2019

• Severity: Serious
• Event Summary: Power supply is in an off condition.
• Event Description: One or more power supplies indicate an off state.
• Probable Cause/ Recommended Action: Verify the AC source and/or replace the FRU (Field Replaceable Unit).

Event 2020

• Severity: Serious
• Event Summary: Power supply is in an DC over voltage condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2021

• Severity: Serious
• Event Summary: Power supply is in an DC under voltage condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2022

• Severity: Serious
• Event Summary: Power supply is in an DC over current condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2023

• Severity: Serious
• Event Summary: Power supply is in an over temperature failure condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2024

• Severity: Serious
• Event Summary: Power supply is in an AC failure condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Verify the AC source and/or replace the FRU (Field Replaceable Unit).

Event 2025

• Severity: Serious
• Event Summary: Power supply is in an DC failure condition.
• Event Description: One or more power supplies indicate a failure condition.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).

Event 2026

• Severity: Serious
• Event Summary: Enclosure Controller Failed.
• Event Description: The enclosure controller has failed.
• Probable Cause/ Recommended Action: Replace the FRU (Field Replaceable Unit).