Dell Unity: Replication Connection Fails with Error 0x6500128

One or more of the following symptoms may be observed:

Scenario 1: Replication Connection Creation Fails

During Replication Connection creation, the task fails with messages similar to:

Failed: The remote system is registered but local interconnects validate has failed.
The time skew between the local and remote systems may be more than 10 minutes.
Fix the time skew and run verify operation on the remote system.
(Error Code: 0x6500128)

The task may also roll back with:

Rollback Result: Task was rolled back and marked as failed.
(Error Code: 0x100a)

Scenario 2: Replication Connection Cannot Be Verified

A replication connection configured with Connection Mode = Both may:

• Show a degraded health status.
• Fail verification.
• Display no remote interface information.

Alerts may indicate:

The remote system connection failed to validate the replication interface connectivity between the two systems.

One or more replication interface pairs are experiencing network connectivity issues between the local and remote systems.

Error 0x6500128 can occur for any of the following reasons:

Cause 1: Required Replication Interfaces Are Missing or Incorrectly Configured

Replication interfaces must exist and be correctly configured on both the local and remote Unity systems before a Replication Connection can be successfully established.

Verify the configuration under:

Unisphere > Data Protection > Replication > Interfaces

Confirm that:

• Required replication interfaces exist on both systems.
• Interfaces are in a Healthy/OK state.
• Valid IP addresses are assigned.
• Interfaces are associated with the correct Storage Processor (SP) and network port.
• Replication network connectivity exists between source and destination interfaces.

Cause 2: Connection Mode "Both" Selected Without Required Interfaces

When Connection Mode = Both (Synchronous and Asynchronous replication), both of the following must be configured on the source and destination systems:

• Synchronous replication interfaces (Replication Management Ports)
• Asynchronous replication interfaces (Ethernet replication ports)

If either interface type is missing, connection validation fails.

Cause 3: Synchronous Replication Requirements Not Met

Synchronous replication requires Fibre Channel connectivity between the source and destination Unity systems.

If Fibre Channel replication ports are not configured or available, a replication connection configured for Both modes may fail verification or show degraded status.

Step 1: Remove Any Failed Replication Connection

Important: If the Replication Connection creation failed, remove the failed connection before creating or modifying replication interfaces. Failure to do so can cause subsequent replication session creation to fail.

Step 2: Verify or Create Required Replication Interfaces

In Unisphere:

Data Protection > Replication > Interfaces

Verify or create the required replication interfaces on both source and destination systems.

For asynchronous replication, create Ethernet replication interfaces for both SPA and SPB.

For synchronous replication, ensure the required synchronous replication interfaces are configured.

Step 3: Validate Connectivity Requirements

For Connection Mode:

If Fibre Channel connectivity is not available, configure the replication connection for Asynchronous mode only.

Step 4: Recreate the Replication Connection

After interfaces have been verified or created:

1. Create a new Replication Connection.
2. Verify the connection completes successfully.
3. Create the required replication sessions (NAS Server, LUN, Consistency Group, and so on).