Option A

Set the same UUIDs, for the BE, on all of the Veritas Cluster Server (VCS) nodes where the zone is configured for failover.

All of the commands below are executed in the global zone.

1. Note the UUID of the Boot Environment on the first VCS host: 

vcshost1# beadm list -H| grep NR

solaris-1; 5090a0a0-6cda-43b4-afa3-d9bd0ad2905f ;NR;/;24001328640;static;1455921334

In the above output,  "5090a0a0-6cda-43b4-afa3-d9bd0ad2905f" is the Boot Environment UUID in the global zone of the first VCS host

2.  List the UUID of the active BE on the other cluster nodes:

vcshost2# beadm list -H | grep NR

solaris-1; 1c76992e-a8b9-4f7e-922f-dbdb1f6c4fe3 ;NR;/;40804133888;static;1455924098

In the above output,  "1c76992e-a8b9-4f7e-922f-dbdb1f6c4fe3" is the Boot Environment UUID in the global zone of the second VCS host.

3. Update the UUID of the BE on the VCS nodes, where the zone is configured for failover. Set the UUID of the BE to be same as the node where the zone is in a running state:

vcshost2# zfs set org.opensolaris.libbe:uuid=5090a0a0-6cda-43b4-afa3-d9bd0ad2905f rpool/ROOT/solaris-1 

The UUID is set on the data set of the active BE (rpool/ROOT/solaris-1).
 
To find the data set for the active BE, use the command: “df -b /”

vcshost2# df -b / Filesystem avail rpool/ROOT/solaris-1 77666058 

Option B

Install the patch for the VCS Zone agent, which supports the newer zone attach options in Solaris 11.3.  [e3874627]

 
In this case, the zone is attached using the following options:

attach -x attach-last-booted-zbe -x deny-zbe-clone
 
With Option B, it is unnecessary to set the same BE UUIDs across the VCS nodes.

Contact Infoscale Technical Support for obtaining the fix mentioned in Option B.

For a zone failover to work seamlessly in Solaris 11.3, the following two options are available:
 

For Solaris 11.3, when a zone is migrated from one global zone to another, the active Boot Environment (BE) in the zone is different from the one that was active before the zone failed over.

The "pre-failover" zone BE is listed as "orphan," and any configuration changes made on the "pre-failover" zone BE are not immediately available.

ETrack: 3874627