Owners Manual
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
Recommended actions:
● Resolve the issue specified by the error message included with this event.
Info. A replication was started.
Recommended actions:
● No action is required.
579 Warning A replication completed with failure.
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 completed successfully.
Recommended actions:
● No action is required.
580 Info. A replication was aborted.
Recommended actions:
● No action is required.
581 Warning A replication was suspended internally by the system.
The system will suspend the replication internally if it detects an error condition in the replication
set and replications cannot continue for any reason. This includes but is 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:
● The replication will automatically resume once the condition described in this event is
cleared.
Info. A replication was suspended by the user.
Recommended actions:
● No action is required.
582 Info. A replication has queued behind the active replication.
Recommended actions:
● No action is required.
583 Error The replication set was not reversed due to a failure.
During the Failback Restore operation, the replication direction for a replication set was not
reversed due to a failure.
Recommended actions:
● If an issue with the peer connection was reported, check that appropriate interface cables
are connected to the host ports defined in the peer connection.
● If the appropriate cables are connected, check the cables and any network switches for
problems.
● Otherwise, check the peer connection for invalid configuration.
Info. The replication direction for a replication set was reversed. Secondary is now primary. Primary is
now secondary.
142 Events and event messages