Oracle ZFS Storage Appliance: Selecting a Host Group from the CLI Fails with "An unanticipated system error occurred"

Asset ID:	1-72-1934086.1
Update Date:	2014-11-18
Keywords:

Solution Type Problem Resolution Sure

Solution 1934086.1 : Oracle ZFS Storage Appliance: Selecting a Host Group from the CLI Fails with "An unanticipated system error occurred"

Applies to:

Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

The administrator is selecting an existing initiator group from the CLI of an Oracle ZFS appliance. The tabbing feature of the CLI is being used to construct the command. This correctly locates and appends the initiator group to the end of the line. Upon execution of the command, it fails with the following error.

ZFS-Node1:> configuration san iscsi initiators groups select name=dba_server5_initiator_group
         error: An unanticipated system error occurred: failed to list host group
         properties: libstmf error: <unknown> (code 0x8000)

         This may be due to transient failure, or a software defect. If this problem
         persists, contact your service provider.

Cause

For reasons unknown, the two cluster nodes no longer have an identical configuration of the initiator host groups. One node has the host group defined while the other one does not. Here are the outputs generated from each node in the cluster.

ZFS-Node2:> configuration san iscsi initiators groups select name=dba_server5_initiator_group
ZFS-Node2:> configuration san iscsi initiators group-000> show
            Properties:
             name = dba_server5_initiator_group
             initiators = iqn.1986-03.com.sun:01:0010e02a49aa.53061366

Solution

It is required to manually synchronize the two nodes. In this particular case, the problem was solved by deleting the initiator group on the node which had a definition for it, followed by re-creating it.

ZFS-Node2:> configuration san iscsi initiators groups> destroy name=dba_server5_initiator_group
            This will destroy "group-000". Are you sure? (Y/N)

ZFS-Node2:> configuration san iscsi initiators groups> create
ZFS-Node2:> configuration san iscsi initiators group-000 (uncommitted)> set name=dba_server5_initiator_group
                          name = dba_server5_initiator_group (uncommitted)
ZFS-Node2:> configuration san iscsi initiators group-000 (uncommitted)> set initiators=iqn.1986-03.com.sun:01:0010e02a49aa.53061366
                    initiators = iqn.1986-03.com.sun:01:0010e02a49aa.53061366 (uncommitted)
ZFS-Node2:> configuration san iscsi initiators group-000 (uncommitted)> commit
ZFS-Node2:> configuration san iscsi initiators groups> select group-000
ZFS-Node2:> configuration san iscsi initiators group-000> show
            Properties:
             name = dba_server5_initiator_group
             initiators = iqn.1986-03.com.sun:01:0010e02a49aa.53061366

Now on ZFS-Node1, the command works.

ZFS-Node1:> configuration san iscsi initiators groups select name=dba_server5_initiator_group
ZFS-Node1:> configuration san iscsi initiators group-000> show
            Properties:
             name = dba_server5_initiator_group
             initiators = iqn.1986-03.com.sun:01:0010e02a49aa.53061366

           "Warning : The following command(s)/instruction(s) may result in changes to appliance settings/configuration, and could
                          therefore result in serious damage if not fully understood and implemented correctly. These steps must be
                          carried out only by a highly experienced Oracle TSC or Field Support engineer, trained to work at the Solaris
                          Shell on the ZFS Storage Appliance. If you are at all unsure whether to proceed, please stop and consult your
                          manager or supervisor immediately.".

If the initiator group cannot be deleted from either node, use stmfadm from the shell to remove it.

ZFS-Node2# stmfadm list-hg -v (parsed)
Host Group: dba_server5_initiator_group
Member: iqn.1986-03.com.sun:01:0010e02a49aa.53061366

ZFS-Node2# stmfadm delete-hg dba_server5_initiator_group
ZFS-Node2# stmfadm list-hg -v (the hg is not listed)

ZFS-Node2#

Attachments

This solution has no attachment