# clresourcegroup status
Make a record for later reference of the online resource groups and on which cluster node each resource group is online.
Do this for each resource group that you identified in Step 1.
# clresource status -g resource-group
Make a record for later reference of the resource names.
# clresourcegroup suspend resource-group
The resource groups remain online but they are prevented from failing the zones over during upgrade. While in this state, the resource groups are also prevented from automatically rebooting the zones when the nodes are rebooted after upgrade. The failover zone will be upgraded together with the node on which it is currently online.
Perform all steps, including booting into the new boot environment, in How to Upgrade the Software (Standard Upgrade) or How to Upgrade the Software (Rolling Upgrade). Then return to this procedure.
# clresource disable sczbt-resource
Disabling this resource ensures that the resource does not time out if the first boot of the upgraded zone takes more time than the resource's Start_timeout allows.
# clresourcegroup online -n node resource-group
The updated failover zones are currently only associated with the global zone boot environment, where they were upgraded, and can only successfully boot there.
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
# zoneadm -z zone-name attach # zoneadm -z zone-name boot
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
# zlogin -C zone-name
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
# zoneadm -z zone-name shutdown # zoneadm -z zone-name detach -F
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
# clresource enable sczbt-resource
If you omit this step, at failover of a solaris brand zone, the last zone boot environment that was booted is first cloned and then activated on the node.
If you perform this step, at failover of a solaris brand zone, the last zone boot environment that was booted is activated on the node without first creating a clone.
phys-schost-1# /opt/SUNWsczone/sczbt/util/ha-solaris-zone-boot-env-id get [-b bename] UUID
Specifies the boot environment from which to retrieve the UUID.
The UUID of the specified boot environment.
The ha-solaris-zone-boot-env-id get command output displays the UUID, similar to the following:
8fe53702-16c3-eb21-ed85-d19af92c6bbd
This UUID will be used in the next steps as the reference UUID for all other upgraded cluster nodes.
phys-schost-N# /opt/SUNWsczone/sczbt/util/ha-solaris-zone-boot-env-id set [-b bename] UUID
Specifies the boot environment in which to define the specified UUID.
The reference UUID that you obtained in Step a.
# clresourcegroup resume resource-group
Next Steps