Oracle ZFS Storage Appliance: Reversing self-replication creates 127.0.0.1 target and can lead to akd hang

Asset ID:	1-72-1961201.1
Update Date:	2016-02-09
Keywords:

Solution Type Problem Resolution Sure

Solution 1961201.1 : Oracle ZFS Storage Appliance: Reversing self-replication creates 127.0.0.1 target and can lead to akd hang

Related Items


Sun ZFS Storage 7320
 Sun Storage 7210 Unified Storage System
 Oracle ZFS Storage ZS3-BA
 Oracle ZFS Storage Appliance Racked System ZS4-4
 Oracle ZFS Storage ZS3-2
 Sun Storage 7410 Unified Storage System
 Oracle ZFS Storage ZS3-4
 Sun ZFS Storage 7420
 Sun Storage 7310 Unified Storage System
 Oracle ZFS Storage ZS4-4
 Sun Storage 7110 Unified Storage System
 Sun ZFS Storage 7120

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-9825821391>

Applies to:

Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

The ZFSSA cluster is configured to use self replication and its reverse replication in production.

But when the self replication is reversed, akd assigns 127.0.0.1 as a target, which we do not want to use, and can lead to akd issues.

Changes

It is not supported to use 127.0.0.1 for replication.

But it is working for customer since he used a singleton IP.

Cause

Replicating to yourself over localhost is not supported.

Currently replication over +cio and 127.0.0.1:216 is forbidden, because these are considered cluster-only addresses.

Solution

So, the concern is how to avoid the loopback IP address which appears as the replication target while reverse replication (of self replication) is being configured.

If the loopback IP address configuration is avoided, no BUI hung happens because there is no loopback replication target.

WORKAROUND: Sever the replication and create an action to replicate back as opposed to doing a replication reversal - worked successfully.

(This has been passed to the Appliance core team to investigate either fixing the target creation or the prohibit reversing a self replication)

References

<BUG:20178223> - REVERSING SELF REPLICATION CREATES 127.0.0.1 TARGET
<BUG:15683126> - SUNBT7002148 REVERSING SELF-REPLICATION PACKAGE CREATES DUPLICATE TARGETS

Attachments

This solution has no attachment