Drive Enclosure Miswire ? ESM Interface Type Conflict
What Caused the Problem?
One or more drive channels are connected to one or more ESMs that are
incompatible with each other.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Possible loss of data accessibility.
It is very important that you resolve this miswire problem along with
any other miswire problem that is reported in the Summary area before
attempting to resolve any other problem that is being reported in the
Summary area. Resolving non-miswire problems with miswire problems
still present can lead to a loss of data accessibility.
Important Notes
- This problem typically occurs when the internal architecture of
the ESMs is different such that the ESMs are not able to communicate
with each other properly.
- All the drive enclosures can still be used
in the storage subsystem, but the similar ESMs must be cabled together
in separate drive channels.
- The following events will occur until this problem is corrected:
- This storage subsystem will remain in a Needs Attention state
- A critical event will be logged once every 24 hours
- Alert notifications will be sent, if configured
- You will NOT be able to:
- Create new configuration objects (Automatically or
Manually) - such as logical drives, flashcopies, mirror
relationships, logical drive copy pairs, and storage partitions
- Assign hot spares
- Change the segment size of a logical drive
- Change the RAID level of an array
- Expand the capacity of an array or logical drive
Recovery Steps
1 |
Refer to the Details area to determine:
- Which drive channels are affected by the miswire AND
- Which ESMs are connected to each drive channel
|
2 |
Using the cabling documentation to ensure proper redundancy,
re-cable the storage subsystem so that every ESM on any given
drive channel is:
- The same interface speed AND
- The same interface type (switch or hub)
|
3 |
Click the Recheck button to rerun the Recovery Guru.
The failure should no longer appear in the Summary area. If
the failure appears again, contact your technical support
representative. |