Owners Manual
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
This event is the result of a hardware problem that has caused the controller to run slower than
expected. The system works, but I/O performance is degraded.
Recommended actions:
● Restart the controller that logged the event. If the problem persists, replace the controller
module.
566 Info. One of the DDR ports has been busy for at least 5 minutes.
This event is the result of a speed compensation while handling short data blocks. The system is
operational but I/O performance is degraded.
Recommended actions:
● No action is required.
568 Info. A disk group has mixed physical sector size disks (for example 512n and 512e disks in the same
disk group).
This event is the result of the user selecting disks with sector formats that do not match or a
global spare replacement with a different sector format than the disk group. This could result in
degraded performance for some workloads.
Recommended actions:
● No action is required.
569 Warning A SAS host cable mismatch has been detected for port. The indicated alternate PHYs have been
disabled.
For example, a fan-out cable is connected to a controller module host port but the port is
configured to use standard SAS cables, or vice versa.
Recommended actions:
● To use the connected cable, use the CLI 'set host-parameters' command to configure ports
to use the proper cable type.
● Otherwise, replace the cable with the type of cable that the port is configured to use.
● When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Resolved A previously detected SAS host cable mismatch has been resolved for port.
The proper cable type has been connected.
Recommended actions:
● No action is required.
571 Error Allocated snapshot space exceeded the configured percentage limit of the virtual pool.
If the snapshot space limit policy is set to delete snapshots, the system will begin to delete
snapshots according to the snapshot retention priority setting until the snapshot space usage
drops below the configured limit. Otherwise, the system will begin to use general pool space for
snapshots until snapshots are manually deleted. If the storage usage drops below a threshold,
event 572 is logged.
Recommended actions:
● If the snapshot space limit policy is set to notify only, you should immediately take steps to
reduce snapshot space usage or add storage capacity.
● If the snapshot space policy is set to delete, the system will reduce snapshot space
automatically, or log event 573 if no snapshots can be deleted.
Warning Allocated snapshot space exceeded the high snapshot space threshold.
The high threshold setting indicates that the pool is nearly out of snapshot space. The threshold
settings are intended to indicate that the pool is using a significant portion of configured
140 Events and event messages