Number Severity Description/Recommended actions
432 Error A replication was aborted due to an error on a secondary volume.
Recommended actions:
• Verify that the secondary volume is valid and that the system where the volume resides is accessible.
433 Info. A replication was skipped.
Recommended actions:
• No action is required.
434 Warning A replication collided with an ongoing replication.
This can be a normal operation, but in some cases this can indicate a problem.
Recommended actions:
• Make sure that there are no network issues.
• Make sure that there is sufficient bandwidth between the primary and secondary systems.
• Make sure that the interval between replications is set to a sufficient amount of time to allow replications
to complete. Having too many replications queued can result in some replications not completing.
435 Warning A replication set could not be initialized. The firmware version of the remote system is not compatible with
the local system.
Recommended actions:
• Update the firmware on one or both systems so they are running the same version.
• Check your network or fabric for abnormally high congestion or connectivity issues.
436 Warning Firmware in the remote system is incompatible with firmware in the local system so they cannot
communicate with each other to perform replication operations.
Recommended actions:
• Update the firmware on one or both systems so they are running the same version.
437 Info. A request by a user to change the primary volume of a replication set was started.
Recommended actions:
• No action is required.
438 Info. A request by a user to change the primary volume of a replication set completed successfully.
Recommended actions:
• No action is required.
439 Error A request to change a primary volume failed.
This can occur for several reasons, such as:
• The volume is not in the replication set.
• Configuration tag or configuration data not found.
• The retry limit has been reached.
Recommended actions:
• Verify that the specified volume is part of the replication set.
• Verify that there are no network issues preventing communication between the local and remote storage
systems.
440 Warning A replication is being retried due to an error in the secondary volume.
This can occur for several reasons, such as:
• The cache request was aborted.
• The cache detected that the source or target volume is offline.
• The cache detected a media error.
• The snap pool is full.
Events and event messages 101