Oracle ZFS Storage Appliance: Creation of replication action fails with "The selected target does not have storage configured"

Asset ID:	1-72-2039682.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2039682.1 : Oracle ZFS Storage Appliance: Creation of replication action fails with "The selected target does not have storage configured"

Applies to:

Sun ZFS Storage 7420 - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

Creating a replication action fails with:

"The selected target does not have storage configured. Please select another target"

or in the CLI

"error: target appliance has no storage configured"

Cause

The target IP is not associated with any valid storage pool.

If you have verified that a storage pool exists on the Appliance node where the target IP address is configured and reachable, the issue could be :

Source and target appliance software versions are not compatible for remote replication, at least not from this source version to this target version.
See Doc ID 1958039.1 - Oracle ZFS Storage Appliance : Remote Replication Compatibility.
In the case where the target is a clustered Appliance, a private IP address (one that does not failover between nodes) was given as the target IP address.
In the case where the target is a clustered Appliance, the cluster node which owns the target IP address does not own any suitable storage pool.
In order for the target IP to be associated with a storage pool, they must have the same owner, i.e. the node where a resource is active when the cluster is in CLUSTERED state, as opposed to OWNER/STRIPPED state.

In the example below, both the network interface net/aggr1 and the storage pool zfs/POOL01 are currently active on node 1, but they have a different owner. Therefore a request to create a replication action to target IP 10.10.10.10 fails with "The selected target does not have storage configured. Please select another target". This can happen when the cluster is in OWNER/STRIPPED state.

node1:> configuration cluster resources show
Resources:

RESOURCE    OWNER   TYPE      LABEL      CHANGES DETAILS
net/aggr1   node2   singleton bond0      no    10.10.10.10 <== the target IP is owned by node2
net/igb0    node1   private    node1-mgt no       10.10.10.11
zfs/POOL01 node1   singleton             no       15.3T    <== the Pool is owned by node1

node1:> configuration cluster show
Properties:
  state = AKCS_OWNER
  description = Active (takeover completed)
  peer_asn = 8c738c7b-3bda-6548-8ecd-ca8a25ae89b9
  peer_hostname = node2
  peer_state = AKCS_STRIPPED
  peer_description = Ready (waiting for failback)

Solution

Verify replication compatibility between the source and target ZFS Appliance.
If setting up replication to a cluster, make sure to provide a singleton and not a private resource as the IP name or address of the replication target.
Verify that the target IP resource and the pool resource have the same owner in a cluster.

In the above example, issuing a failback would put the clustered IP resource on node2 and leave the storage pool on node1, causing loss of network access to the data. This is a misconfiguration in the cluster.

To correct this, change the ownership of the IP resource to match that of the storage pool.

node1:configuration cluster resources> select net-a/aggr1
node1:configuration cluster resources net/aggr1> show
Properties:
  owner = node2
  type = singleton
  user_label = bond0
  details = 10.10.10.10

node1:configuration cluster resources net/aggr1> set owner=node1
owner = node1 (uncommitted)
node1:configuration cluster resources net/aggr1> commit
Warning: In order to commit these changes fully, it is necessary to commit the parent "resources" node.
node1:configuration cluster resources> commit
The changes have been committed. Would you also like to fail back? (Y/N) N
The changes have been committed.

node1:configuration cluster resources> show
Resources:

RESOURCE    OWNER   TYPE    LABEL      CHANGES DETAILS
net/aggr1 node1 singleton bond0      no    10.10.10.10
net/igb0    node1   private    node1-mgt no       10.10.10.11
zfs/POOL01 node1   singleton             no       15.3T

Attachments

This solution has no attachment