Report detail: CM XX in the high load state was detected. The monitoring states of other presumably related targets are as follows: <Monitoring state of each CM> <- (1) [CM0x00] High load state detected [CM0x01] Not detected [CM0x10] Not detected [CM0x11] Not detected Related graph: Refer to the CM utilization graph. Refer to the IOPS graph of each LogicalVolume. <- (2) Guidelines for corrective measure: 1. I/O may be concentrated on the RAIDGroups under control of the same CM <- (2) By referring to the monitoring state of each CM, distribute I/O to RAIDGroups under control of a CM with a low load. 2. If the monitoring state of every CM is "Monitoring" or "High load state detected," the number of CMs is probably too small to meet every I/O request. Consider adding or upgrading hardware.
Indicates the states of other CMs during the same time zone as the relevant CM detected a high load state.
High load state detected | An alarm log indicating a load error in the relevant CM is generated during the same time zone. |
Monitoring | The CM is monitoring for alarm detection because the threshold has been exceeded several times although no events have been detected as an alarm. |
Not detected | The relevant CM did not cause a bottleneck during the same time zone. |
If only the relevant CM detected a high load state, I/O access is unevenly concentrated on the CM.
Refer to the IOPS graphs of RAIDGroups and LogicalVolumes and take measures such as distributing I/O loads of each CM.
Point
CM is put in high load state when a transaction is in contention with advanced copy.
In this case, review the operation mode so that advanced copy is executed in a time slot in which a transaction load is relatively small. Alternatively, if the same CM controls both the copy source and target volumes (RAIDGroups), use separate CMs to control the source and target volumes.
