Isolating Remote Snap replication faults
55
Can you successfully use the Remote Snap feature?
Can you create a replication set?
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.
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
Remote Snap is not licensed on each
controller enclosure used for replication.
Verify licensing of the optional feature per system:
•
In the
Home
topic in the SMU, select
Action > Install License
.
•
The License Settings panel opens and displays information about each
licensed feature.
•
If the Replication feature is not enabled, obtain and install a valid license
for Remote Snap.
•
For more information on licensing, see the “Installing a license” chapter in
the SMU Reference Guide.
No
Compatible firmware revision
supporting Remote Snap is not running
on each system used for replication.
Perform the following actions on each system used for replication:
•
In the
System
topic, select
Action > Update Firmware
.
The Update Firmware panel opens. The Update Controller Modules tab
shows firmware versions installed in each controller.
•
If necessary, update the controller module firmware to ensure
compatibility with other systems.
•
For more information on compatible firmware, see the “Updating
firmware” chapter in the SMU Reference Guide.
No
Invalid cabling connection.
(If multiple controller enclosures are
used, check the cabling for each system)
Verify controller enclosure cabling.
•
Verify use of proper cables.
•
Verify proper cabling paths for host connections.
•
Verify cabling paths between replication ports and switches are visible to
one another.
•
Verify that cable connections are securely fastened.
•
Inspect cables for damage and replace if necessary.
No
A system does not have a pool configured. Configure each system to have a storage pool.
Table 17
Diagnostics for replication setup: Using Remote Snap feature
Answer
Possible reasons
Actions
Yes
System functioning properly.
No action required.
No
On controller enclosures with iSCSI host
interface ports, replication set creation
fails due to use of CHAP.
If using CHAP (Challenge-Handshake Authentication Protocol), see the topics
about configuring CHAP and working in replications within the SMU Reference
Guide.
No
Unable to create the secondary volume
(the destination volume on the pool to
which you will replicate data from the
primary volume)?
1
•
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.
•
Verify valid specification of the secondary volume according to either of
the following criteria:
A conflicting volume does not already exist
Available free space in the pool
Table 18
Diagnostics for replication setup: Creating a replication set