Owners Manual
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
During the Failback Restore operation, the replication direction for a replication set was
reversed.
Recommended actions:
● No action is required.
584 Info. A peer connection was modified.
Recommended actions:
● No action is required.
585 Info. A replication set was modified.
Recommended actions:
● No action is required.
586 Error Resuming the replication was unsuccessful due to the condition specified within the event.
Reasons for replication failure include but are not limited to shutdown of the secondary system,
a loss of communication across the peer connection (which may be due to CHAP configuration
changes), or a pool out-of-space condition.
Recommended actions:
● Resolve the issue specified by the error message included with this event.
Info. A replication was resumed.
Recommended actions:
● No action is required.
587 Info. A pending replication was removed from the queue.
Recommended actions:
● No action is required.
588 Info. A replication set was failed over.
During the Failback Restore operation, a replication set was failed over
Recommended actions:
● No action is required.
589 Info. A replication set completed the Failback No Restore operation or failed to complete the
Failback No Restore operation.
Recommended actions:
● No action is required.
590 Error A disk group has been quarantined.
This condition resulted from a controller flush/restore failure.
Recommended actions:
● To restore the disk group, use the CLI dequarantine command to dequarantine the disk
group. If more than one disk group is quarantined you must individually dequarantine each
disk group, whether it is fault tolerant or not. When dequarantine is complete, the disk group
will return to the state it was in before being quarantined. For example, if the disk group was
reconstructing before being quarantined, the disk group will resume reconstructing where it
stopped
● For a linear disk group, if you want to find where parity is incorrect, use the CLI scrub
vdisk command with the fix parameter disabled. This step is optional and not required to
fix data integrity issues
Events and event messages 143