The following reference provides more information about events with a critical priority, shown with this icon in the Event Log.
Critical Event Type and Sense Key/ASC/ASCQ |
Description/Action |
Event 1001 - Channel failed Sense key/ASC/ASCQ: 6/3F/C3 |
Description: The controller failed a channel, and will not access drives on this channel any more. The FRU Group Qualifier (byte 26) in the sense data will indicate the 1-relative channel number of the failed channel. This condition is typically caused by a drive ignoring SCSI protocol on one of the controller's destination channels. The controller typically fails a channel if it issued a reset on a channel, and it continued to see drives ignore the SCSI Bus Reset on this channel. Action: Select the Recovery Guru to obtain the "Failed Drive SCSI Channel" recovery procedure. Contact technical support to complete this procedure. |
Event 1010 - Impending drive failure (PFA) detected Sense key/ASC/ASCQ: 6/5D/80 |
Description: A drive has reported that a failure prediction threshold has been exceeded. This indicates that the drive may fail within 24 hours. Action: Select the Recovery Guru to obtain the "Impending Drive Failure" recovery procedure. |
Event 1015 - Incorrect mode parameters set on drive Sense key/ASC/ASCQ: 6/3F/BD |
Description: The controller was unable to query the drive for its current critical mode page settings or was unable to change these to the correct setting. This indicates the Qerr bit is set incorrectly on the drive specified in the FRU field of the Request Sense data. Action: The controller has not failed yet. Contact technical support for instructions on recovering from this failure. |
Event 1207 - Fibre Channel link errors - threshold exceeded Sense key/ASC/ASCQ: None |
Description: Invalid characters have been detected in the Fibre Channel signal. Possible causes for the error are a degraded laser in a Gigabit Interface Converter (GBIC), Small Form-factor Pluggable (SFP) transceiver, or Media Interface Adapter (MIA); damaged or faulty Fibre channel cables; or poor cable connections between components on the loop. Action: In the main Subsystem Management Window, select the Help >> Recovery Procedures pull-down menu option. Select "Fibre Channel Link Errors - Threshold Exceeded" for more information about recovering from this failure. |
Event 150E - Controller loopback diagnostics failed Sense key/ASC/ASCQ: None |
Description: The controller cannot initialize the drive-side Fibre Channel loops. Diagnostics have been run identifying a controller problem, and the controller has been placed offline. This event will only occur on certain controller models. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 150F - Channel miswire Sense key/ASC/ASCQ: None |
Description: Two or more drive channels are connected to the same Fibre Channel loop. This can cause the storage subsystem to behave unpredictably. Action: Select the Recovery Guru to obtain the "Channel Miswire" recovery procedure. |
Event 1510 - ESM canister miswire Sense key/ASC/ASCQ: None |
Description: Two ESM canisters in the same drive enclosure are connected to the same Fibre Channel loop. A level of redundancy has been lost, and the I/O performance for this drive enclosure is reduced. Action: Select the Recovery Guru to obtain the "ESM Canister Miswire" recovery procedure. |
Event 200A - Data/parity mismatch detected on logical drive Sense key/ASC/ASCQ: None |
Description: A media scan operation has detected inconsistencies between a portion of the logical drive's data blocks and associated parity blocks. User data in this portion of the logical drive may have been lost. Action: Select an application-specific tool (if available) to verify the correctness of the logical drive's data. If no such tool is available, or if problems with the user data are reported, the entire logical drive contents should be restored from the most recent backup, if it is critical data. |
Event 202E - Read drive error during interrupted write Sense key/ASC/ASCQ: 3/11/8A |
Description: A media error has occurred on a read operation during interrupted write processing. Action: Select the Recovery Guru to obtain the "Unrecovered Interrupted Write" recovery procedure. Contact technical support to complete this procedure. |
Event 2109 - Controller cache not enabled - cache sizes do not match Sense key/ASC/ASCQ: 6/A1/00 |
Description: The controller will not allow mirroring to be enabled if the alternate controller's cache size is different. Action: Ensure that both controllers have the same cache size. Contact technical support for instructions on recovering from this failure. |
Event 210C - Controller cache battery failed Sense key/ASC/ASCQ: 6/0C/80 |
Description: The controller has detected that the battery is either not physically present, or is fully discharged, or has reached its expiration date. Action: Select the Recovery Guru to obtain the "Failed Battery Canister" recovery procedure. |
Event 210E - Controller cache memory recovery failed after power cycle or reset Sense key/ASC/ASCQ: 6/0C/81 |
Description: Recovery from a Data Cache error was unsuccessful. User data may have been lost. Action: Contact technical support for instructions on recovering from this failure. |
Event 2110 - Controller cache memory initialization failed Sense key/ASC/ASCQ: 6/40/81 |
Description: The controller has detected the failure of an internal controller component (RAID Buffer). This failure may have been detected during operation as well as during an on-board diagnostic routine. Action: Contact technical support for instructions on recovering from this failure. |
Event 2113 - Controller cache battery nearing expiration Sense key/ASC/ASCQ: 6/3F/D9 |
Description: The cache battery is within the specified number of weeks before failing. Action: Select the Recovery Guru to obtain the "Battery Nearing Expiration" recovery procedure. |
Event 2229 - Drive failed by controller Sense key/ASC/ASCQ: None |
Description: The controller has failed a drive because of a problem with the drive. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 222D - Drive manually failed Sense key/ASC/ASCQ: 6/3F/87 |
Description: The drive was manually failed by a user. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 2247 - Data lost on logical drive during unrecovered interrupted write Sense key/ASC/ASCQ: 6/3F/EB |
Description: An error has occurred during interrupted write processing during the start-of-day routine causing the logical drive to transition to the Failed state. Action: Select the Recovery Guru to obtain the "Unrecovered Interrupted Write" recovery procedure. Contact technical support to complete this procedure. |
Event 2248 - Drive failed - write failure Sense key/ASC/ASCQ: 6/3F/80 |
Description: The drive failed a write command to it. The drive will be marked failed. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 2249 - Drive capacity less than minimum Sense key/ASC/ASCQ: 6/3F/8B |
Description: During drive replacement, the capacity of the drive is not large enough to support all the logical drives that must be reconstructed on it. Action: Replace the drive with a larger capacity drive. |
Event 224A - Drive has wrong block size Sense key/ASC/ASCQ: 6/3F/8C |
Description: The drive's block size does not match that of the other drives in the logical drive. The drive will be marked failed. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 224B - Drive failed - initialization failure Sense key/ASC/ASCQ: 6/3F/86 |
Description: The drive failed either a Format Unit command or a Write operation (issued when a logical drive was initialized). The drive will be marked failed. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 224D - Drive failed - no response at start of day Sense key/ASC/ASCQ: 6/3F/85 |
Description: The drive failed a Read Capacity or Read command during the start-of-day routine. The controller was unable to read the configuration information stored on it. The drive will be marked failed. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 224E - Drive failed - initialization/reconstruction failure Sense key/ASC/ASCQ: 6/3F/82 |
Description: The previously-failed drive was marked failed because either the drive failed a Format Unit command issued to it, or the reconstruction on the drive failed due to the controller being unable to restore it; for example: an error occurring on another drive required for reconstruction. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 2250 - Logical Drive failure (3F E0) Sense key/ASC/ASCQ: 6/3F/E0 |
Description: The controller has marked the logical drive failed. User data and/or redundancy (parity) can no longer be maintained to ensure availability. The most likely cause is the failure of a single drive in non-redundant configurations or a second drive in a configuration protected by one drive. Action: Select the Recovery Guru to obtain the "Failed Logical Drive - Drive Failure" recovery procedure. |
Event 2251 - Drive failed - reconstruction failure Sense key/ASC/ASCQ: 6/3F/8E |
Description: A drive failed due to a reconstruction failure during the start-of-day routine. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 2252 - Drive marked offline during interrupted write Sense key/ASC/ASCQ: 6/3F/98 |
Description: An error has occurred during interrupted write processing causing the logical drive to be marked failed. Drives in the array that did not experience the read error will transition to the Offline state and log this error. Action: Select the Recovery Guru to obtain the "Unrecovered Interrupted Write" recovery procedure. Contact technical support to complete this procedure. |
Event 2254 - Redundancy (parity) and data mismatch was detected Sense key/ASC/ASCQ: 6/8E/01 |
Description: The controller detected inconsistent redundancy (parity)/data during a parity verification. Action: Contact technical support for instructions on recovering from this failure. |
Event 2255 - Logical Drive definition incompatible with ALT mode - ALT disabled Sense key/ASC/ASCQ: 6/91/3B |
Description: Auto-LUN Transfer (ALT) works with arrays that have only one logical drive defined. There are currently arrays on the storage subsystem that have more than one logical drive defined; therefore, ALT mode has been disabled. The controller will operate in normal redundant controller mode and if there is a problem, will transfer all logical drives on an array instead of transferring individual logical drives. Action: Contact technical support for instructions on recovering from this failure. |
Event 2602 - Automatic controller firmware synchronization failed Sense key/ASC/ASCQ: 02/04/81 |
Description: The versions of firmware on the redundant controllers are not the same because the automatic controller firmware synchronization failed. Controllers with an incompatible version of firmware may cause unexpected results. Action: Try the firmware download again. If the problem persists, contact technical support. |
Event 2801 - Storage Subsystem running on UPS battery Sense key/ASC/ASCQ: 6/3F/C8 |
Description: The Uninterruptible Power Source (UPS) has indicated that AC power is no longer present and the UPS has switched to standby power. While there is no immediate cause for concern, you should save your data frequently, in case the battery is suddenly depleted. Action: Select the Recovery Guru to obtain the "Lost AC Power" recovery procedure. |
Event 2803 - UPS battery - two minutes to failure Sense key/ASC/ASCQ: 6/3F/C9 |
Description: The Uninterruptible Power Source (UPS) has indicated that its standby power source is nearing depletion. Action: You should take actions to stop I/O activity to the controller. Normally, the controller will change from a write-back caching mode to a write-through mode. |
Event 2804 - UPS battery failed Sense key/ASC/ASCQ: None |
Description: The UPS battery has failed. Action: Contact technical support for instructions on recovering from this failure. |
Event 2807 - ESM canister failed Sense key/ASC/ASCQ: None |
Description: An ESM canister has failed. Action: Select the Recovery Guru to obtain the "Failed ESM Canister" recovery procedure. |
Event 2808 - Enclosure ID not unique Sense key/ASC/ASCQ: 6/98/01 |
Description: The controller has determined that there are multiple drive enclosures with the same ID selected. Ensure that each drive enclosure has a unique ID setting. Action: Select the Recovery Guru to obtain the "Enclosure ID Conflict" recovery procedure. |
Event 280A - Controller enclosure component missing Sense key/ASC/ASCQ: 6/3F/C7 |
Description: A component other than a controller is missing in the controller enclosure (for example, fan, Gigabit Interface Converter (GBIC) or Small Form-factor Pluggable (SFP) transceiver, power supply, or battery). The FRU codes indicate the faulty component. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 280B - Controller enclosure component failed Sense key/ASC/ASCQ: 6/3F/C7 |
Description: A component other than a controller has failed in the controller enclosure (for example, fan, Gigabit Interface Converter (GBIC) or Small Form-factor Pluggable (SFP) transceiver, power supply, or battery), or an over-temperature condition has occurred. The FRU codes indicate the faulty component. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 280D - Drive enclosure component failed Sense key/ASC/ASCQ: 6/3F/C7 |
Description: A component other than a drive has failed in the drive enclosure (for example, controller, Gigabit Interface Converter (GBIC), ESM, fan, power supply, battery), or an over-temperature condition has occurred. The FRU codes indicate the faulty component. Action: Select the Recovery Guru to obtain the recovery procedure and follow the instructions to correct the failure. |
Event 280E - Standby power source not fully charged Sense key/ASC/ASCQ: 6/3F/CA |
Description: The Uninterruptible Power Source (UPS) has indicated that its standby power source is not at full capacity. |
Event 280F - ESM canister - loss of communication Sense key/ASC/ASCQ: 6/E0/20 |
Description: Communication has been lost to one of the dual ESM canisters in a drive enclosure. The drive enclosure has only one I/O path available. Action: Select the Recovery Guru to obtain the "ESM Canister - Loss of Communication" recovery procedure. |
Event 2813 - Minihub canister failed Sense key/ASC/ASCQ: 6/3F/C7 |
Description: Communications with the minihub canister has been lost. This may be the result of a minihub canister failure, a controller failure, or a failure in an internal backplane communications board. If there is only one minihub failure, the storage subsystem is still operational but a second minihub failure could result in the failure of the affected enclosures. Action: Select the Recovery Guru to obtain the "Failed Minihub Canister" recovery procedure. |
Event 2815 - GBIC/SFP failed Sense key/ASC/ASCQ: None |
Description: A Gigabit Interface Converter (GBIC) or Small Form-factor Pluggable (SFP) transceiver on either the controller enclosure or the drive enclosure has failed. If there is only one GBIC or SFP failure, the storage subsystem is still operational but a second GBIC or SFP failure could result in the failure of the affected enclosures. Action: Select the Recovery Guru to obtain the "Failed GBIC/SFP" recovery procedure. |
Event 2816 - Enclosure ID conflict - duplicate ID's across drive enclosures Sense key/ASC/ASCQ: 6/98/01 |
Description: Two or more drive enclosures are using the same enclosure identification number. Action: Select the Recovery Guru to obtain the "Enclosure ID Conflict" recovery procedure. |
Event 2818 - Enclosure ID mismatch - duplicate ID's in the same drive enclosure Sense key/ASC/ASCQ: 6/98/02 |
Description: A drive enclosure in the storage subsystem contains ESM canisters with different enclosure identification numbers. Action: Select the Recovery Guru to obtain the "Enclosure ID Mismatch" recovery procedure. |
Event 281B - Nominal temperature exceeded Sense key/ASC/ASCQ: 6/98/03 |
Description: The nominal temperature of the enclosure has been exceeded. Either a fan has failed or the temperature of the room is too high. If the temperature of the enclosure continues to rise, the affected enclosure may automatically shut down. Fix the problem immediately, before it becomes more serious. The automatic shutdown conditions depend on the model of the enclosure. Action: Select the Recovery Guru to obtain the "Nominal Temperature Exceeded" recovery procedure. |
Event 281C- Maximum temperature exceeded Sense key/ASC/ASCQ: 6/3F/C6 |
Description: The maximum temperature of the enclosure has been exceeded. Either a fan has failed or the temperature of the room is too high. This condition is critical and may cause the enclosure to shut down if you do not fix the problem immediately. The automatic shutdown conditions depend on the model of the enclosure. Action: Select the Recovery Guru to obtain the "Maximum Temperature Exceeded" recovery procedure. |
Event 281D - Temperature sensor removed Sense key/ASC/ASCQ: 6/98/03 |
Description: A fan canister containing a temperature sensor has been removed from the storage subsystem. Action: Replace the canister as soon as possible. Select the Recovery Guru to obtain the "Failed or Removed Fan Canister" recovery procedure. |
Event 281E - ESM canister firmware mismatch Sense key/ASC/ASCQ: 6/98/03 |
Description: A drive enclosure in the storage subsystem contains ESM canisters with different versions of firmware. ESM canisters in the same drive enclosure must have the same version firmware. Action: Select the Recovery Guru to obtain the "ESM Canister Firmware Version Mismatch" recovery procedure. If you do not have a replacement canister, call technical support to perform the firmware download. |
Event 2821 - Incompatible minihub Sense key/ASC/ASCQ: None |
Description: An incompatible minihub canister has been detected in the controller enclosure. Action: Select the Recovery Guru to obtain the "Incompatible Minihub Canister" recovery procedure. |
Event 3019 - Logical Drive ownership changed due to failover Sense key/ASC/ASCQ: None |
Description: The multi-path driver software has changed ownership of the logical drives to the other controller because it could not access the logical drives on the particular path. Action: Select the Recovery Guru to obtain the "Logical Drive Not on Preferred Path" recovery procedure. |
Event 502F - Missing logical drive deleted Sense key/ASC/ASCQ: None |
Description: The storage subsystem has detected that the drives associated with a logical drive are no longer accessible. This can be the result of removing all drives associated with an array or a loss of power to one or more drive enclosures. Action: Select the Recovery Guru to obtain the "Missing Logical Drive" recovery procedure. |
Event 5005 - Place controller offline Sense key/ASC/ASCQ: None |
Description: The controller was placed offline. This could be caused by the controller failing a diagnostic test. (The diagnostics are initiated internally by the controller or by using the Controller >> Run Diagnostics pull-down menu option.) Or the controller was manually placed Offline using the Controller >> Place Offline pull-down menu option. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 5602 - This controller's alternate failed - timeout waiting for results Sense key/ASC/ASCQ: None |
Description: This controller initiated diagnostics on the alternate controller but did not receive a reply indicating that the diagnostics completed. The alternate controller in this pair has been placed offline. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 560B - ctlrDiag task cannot obtain Mode Select lock Sense key/ASC/ASCQ: None |
Description: This controller was attempting to run diagnostics and could not secure the test area from other storage subsystem operations. The diagnostics were canceled. Action: Contact technical support for instructions on recovering from this failure. |
Event 560C - ctlrDiag task on controller's alternate cannot obtain Mode Select lock Sense key/ASC/ASCQ: None |
Description: The alternate controller in this pair was attempting to run diagnostics and could not secure the test area from other storage subsystem operations. The diagnostics were canceled. Action: Contact technical support for instructions on recovering from this failure. |
Event 560D - Diagnostics read test failed on controller Sense key/ASC/ASCQ: None |
Description: While running diagnostics, the controller has detected that the information received does not match the expected return for the test. This could indicate that I/O is not completing or that there is a mismatch in the data being read. The controller was placed offline as result of this failure. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 560E - This controller's alternate failed diagnostics read test Sense key/ASC/ASCQ: None |
Description: While running diagnostics, this controller's alternate detected that the information received does not match the expected return for the test. This could indicate that I/O is not completing or that there is a mismatch in the data being read. The alternate controller in this pair was placed offline as result of this failure. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 560F - Diagnostics write test failed on controller Sense key/ASC/ASCQ: None |
Description: While running diagnostics, the controller was unable to write data to the test area. This could indicate that I/O is not completing or that there is a mismatch in the data being written. The controller was placed offline as result of this failure. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 5610 - This controller's alternate failed diagnostics write test Sense key/ASC/ASCQ: None |
Description: While running diagnostics, this controller's alternate was unable to write data to the test area. This could indicate that I/O is not completing or that there is a mismatch in the data being written. The alternate controller in this pair was placed offline as result of this failure. Action: Select the Recovery Guru to obtain the "Offline Controller" recovery procedure. Use this procedure to replace the controller. |
Event 5616 - Diagnostics rejected - configuration error on controller Sense key/ASC/ASCQ: None |
Description: This controller was attempting to run diagnostics and could not create the test area necessary for the completion of the tests. The diagnostics were canceled. Action: Contact technical support for instructions on recovering from this failure. |
Event 5617 - Diagnostics rejected - configuration error on controller's alternate Sense key/ASC/ASCQ: None |
Description: This controller's alternate was attempting to run diagnostics and could not create the test area necessary for the completion of the tests. The diagnostics were canceled. Action: Contact technical support for instructions on recovering from this failure. |
Event 6101 - Internal configuration database full Sense key/ASC/ASCQ: None |
Description: Because the amount of data required to store certain configuration data for the maximum number of logical drives has been underestimated, two types of data may have caused the internal configuration database to become full:
Action: Recovery options include deleting one or more FlashCopy logical drives from your storage subsystem, and/or removing one or more mirror relationships. |
Event 6200 - FlashCopy repository logical drive threshold exceeded Sense key/ASC/ASCQ: None |
Description: The FlashCopy's FlashCopy repository logical drive capacity has exceeded a warning threshold level. If the FlashCopy repository logical drive's capacity becomes full, its associated FlashCopy logical drive can fail. If you do not resolve this problem, this is the last warning you will receive before the FlashCopy's FlashCopy repository logical drive becomes full. Action: Select the Recovery Guru to obtain the "FlashCopy Repository Logical Drive Threshold Exceeded" recovery procedure and follow the instructions to recover from this failure. |
Event 6201 - FlashCopy repository logical drive full Sense key/ASC/ASCQ: None |
Description: All of the FlashCopy repository logical drive's available capacity has been used. The FlashCopy repository logical drive's failure policy determines what happens when the FlashCopy's FlashCopy repository logical drive becomes full. The failure policy can be set to either fail the FlashCopy logical drive (default setting) or fail incoming I/Os to the FlashCopy's base logical drive. Action: Select the Recovery Guru to obtain the "FlashCopy Repository Logical Drive Capacity - Full" recovery procedure and follow the instructions to recover from this failure. |
Event 6202 - Failed FlashCopy logical drive Sense key/ASC/ASCQ: None |
Description: Either the FlashCopy logical drive's associated FlashCopy repository logical drive is full or its associated base or FlashCopy repository logical drives were failed due to one or more drive failures on their respective arrays. Action: Select the Recovery Guru to obtain the "Failed FlashCopy Logical Drive" recovery procedure and follow the instructions to recover from this failure. |
Event 6400 - Dual primary logical drive Sense key/ASC/ASCQ: None |
Description: Both logical drives have been promoted to Primary after a forced role reversal. This could be reported at controller reset, or when a cable from an array to a Fibre Channel switch is reinserted after having been removed, and the other logical drive has been promoted to Primary. Action: Select the Recovery Guru to obtain the "Dual Primary Logical Drive Conflict" recovery procedure, and follow the instructions to recover from this failure. |
Event 6401 - Dual secondary logical drive Sense key/ASC/ASCQ: None |
Description: Both logical drives in the Remote Mirror have been demoted to Secondary after a forced role reversal. This could be reported at controller reset, or when a cable from an array to a Fibre Channel switch is reinserted after having been removed, and the other logical drive has been demoted to Secondary. Action: Select the Recovery Guru to obtain the "Dual Secondary Logical Drive Conflict" recovery procedure, and follow the instructions to recover from this failure. |
Event 6402 - Mirror data unsynchronized Sense key/ASC/ASCQ: Not recorded with event |
Description: This may occur because of I/O errors, but there should be other events associated with it. One of them would be the root cause, that would contain the sense data. A Needs Attention icon will appear on both the primary and secondary storage subsystems of the Remote Mirror. Actions: Select the Recovery Guru to obtain the "Mirror Data Unsynchronized" recovery procedure, and follow the instructions to recover from this failure. |
Event 6503 - Remote logical drive link down Sense key/ASC/ASCQ: None |
Description: This event is triggered when either a cable between one array and its peer has been disconnected, the Fibre Channel switch has failed, or the peer array has reset. This error could result in the Mirror Data Unsynchronized event. The affected remote logical drive will show an Unresponsive icon, and this state will be selected in the logical drive's tooltip. Action: Select the Recovery Guru to obtain the "Mirror Communication Error - Unable to Contact Logical Drive" recovery procedure, and follow the instructions to recover from this failure. |
Event 6505 - WWN change failed Sense key/ASC/ASCQ: None |
Description: Mirroring causes a WWN change to be communicated between arrays. Failure of a WWN change is caused by non-I/O communication errors between one array, on which the WWN has changed, and a peer array. (The array WWN is the unique name used to locate an array on a fibre network. When both controllers in an array are replaced, the array WWN changes). The affected remote logical drive will show an Unresponsive icon, and this state will be selected in the logical drive's tooltip. Action: Select the Recovery Guru to obtain the "Unable to Update Remote Mirror" recovery procedure, and follow the instructions to recover from this failure. The only solution to this problem is to delete the Remote Mirror and then to establish another one. |