TIP
Measures taken to prevent the HyperImage fault:
l Before creating a HyperImage, check the effective capacity of the resource pool, so that the
resource pool space is enough.
l When an alarm is generated because the effective capacity of the resource pool reaches the
threshold value, add resource LUNs to the resource pool in time.
l Do not arrange the resource LUNs in the same resource pool to the same expander enclosure.
l Stop the snapshots that are not used to release the resource pool space.
----End
5.19 HyperCopy Fault
This section describes how to handle the HyperCopy fault.
Symptom
On the ISM interface, the HyperCopy is in the Fault status and the status cannot be normal for
a long time.
Possible Causes
One of the following causes may arouse the HyperCopy fault:
l The disk enclosure where the source LUN or the target LUN is located is powered off
abnormally.
l The link between devices are disconnected.
l The RAID group that owns the source LUN or the target LUN is invalid.
l The HyperImage is automatically terminated (applies to the incremental HyperCopy).
Fault Diagnosis
You can determine the cause for the fault through the following procedure:
l Cause 1: The disk enclosure where the source LUN or the target LUN is located is powered
off abnormally.
1. Check whether the power indicator on the disk enclosure where the source LUN or
the target LUN is located is normal.
2. If the power indicator on the disk enclosure is off, you can determine that the disk
enclosure where the HyperCopy is located is powered off abnormally.
l Cause 2: The link between devices is disconnected.
1. Log in to the ISM to check whether the corresponding expander port or the host port
is normally connected, or observe whether the link indicator of the corresponding
expander port or the host port is normal.
2. If the corresponding expander port or the host port is not connected or the link indicator
is off, you can determine that the link between devices is disconnected.
l Cause 3: The RAID group that owns the source LUN or the target LUN is invalid.
1. Log in to the ISM to check whether the RAID group that owns the source LUN or the
target LUN is normal.
5 Troubleshooting of Common Faults
OceanStor S2600 Storage System
Troubleshooting
5-24 Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
Issue 03 (2010-01-28)
To Next Page
Loading...
Need help?
General