| Parity Group utilization
|
- Root cause:
The usage rate of the Parity Group increases because of the following possible causes:
- Some volumes might be under heavy load.
- Volumes (logical resources) might belong to the same Parity Group (physical resource) which might cause resource contention issues in the shared infrastructure.
- Possible solutions:
- Consider moving some volumes to another Parity Group with a lower usage rate or higher performance.
- Consider increasing the number of drives (by concatenating Parity Groups).
- To manage a Parity Group that is part of a pool, consider adding another Parity Group to the pool.
|
| MPB utilization
|
- Root cause:
The usage rate of the MP Blade (average usage rate of the MP cores in the MP Blade) increases because of an increased load. Too many busy resources such as internal volumes, external volumes, or journal groups accessing the same MP Blade might cause performance degradation.
- Possible solutions:
-
Consider allocating the busy resources (internal volumes, external volumes, or journal groups) to another MP Blade (changing the MP Blade ownership).
-
Limit I/O to the volumes using I/O controls.
-
Increase the size of cache memory allocated to the MP Blade.
|
| Port utilization
|
- Root cause:
The usage rate of the port (amount of data forwarded by the port divided by the amount of data that can be forwarded by the port) increases because of a number of volumes accessing the same port.
- Possible solutions:
Consider allocating some volumes (or host groups) to a different port.
Note: When the connected port is changed, the host might need to be restarted.
|
| Cache utilization
|
|