Isolating Remote Snap replication faults 51
Can you replicate a volume?
IMPORTANT: Remote Snap must be licensed on all systems configured for replication, and the controller module
firmware must be compatible on all systems licensed for replication.
Has a replication run successfully?
No Communication link is down. Review event logs for indicators of a specific fault in a host or replication data
path component.
1
After ensuring valid licensing, valid cabling connections, and network availability, create the replication set using the Replications topic; select
Action > Create Replication Set.
Answer Possible reasons Actions
Table 19 Diagnostics for replication setup: Creating a replication set (continued)
Answer Possible reasons Actions
Yes System functioning properly. No action required.
No Remote Snap is not licensed on each
controller enclosure used for replication.
See actions described in “Can you successfully use the Remote Snap feature?”
(page 50).
No Nonexistent replication set. • Determine existence of primary or secondary volumes.
• If a replication set has not been successfully created, use the Replications
topic: select Action > Create Replication Set to create one.
• Review event logs (in the footer, click the events panel and select Show
Event List) for indicators of a specific fault in a replication data path
component. Follow any recommended actions.
No Network error occurred during
in-progress replication.
• Review event logs for indicators of a specific fault in a replication data
path component. Follow any recommended actions.
• Click in the Volumes topic, then click on a volume name in the volumes
list. Click the Replication Sets tab to display replications and associated
metadata.
• Replications that enter the suspended state can be resumed manually
(see the SMU Reference Guide for additional information).
No Communication link is down. Review event logs for indicators of a specific fault in a host or replication data
path component.
Table 20 Diagnostics for replication setup: Replicating a volume
Answer Possible reasons Actions
Yes System functioning properly. No action required.
No Last Successful Run shows N/A. • In the Volumes topic, click on the volume that is a member of the
replication set.
Select the Replication Sets table.
Check the Last Successful Run information.
• If a replication has not run successfully, use the SMU to replicate as
described in the section about working in the Replications topic within the
SMU Reference Guide.
No Communication link is down. Review event logs for indicators of a specific fault in a host or replication data
path component.
Table 21 Diagnostics for replication setup: Checking for a successful replication