How to Upgrade a solaris Branded Failover Zone - Oracle® Solaris Cluster 4.3 Upgrade Guide

Language:

How to Upgrade a `solaris` Branded Failover Zone

Note - This task does not apply to solaris10 or solaris-kz (kernel) branded failover zones. To manage packages and patches in a solaris10 or solaris-kz branded failover zone, follow normal Oracle Solaris 10 Zone or Oracle Solaris Kernel Zone procedures. See Creating and Using Oracle Solaris 10 Zones or Creating and Using Oracle Solaris Kernel Zones.

Identify which resource groups that manage a failover zone of brand type solaris are online.
```
# clresourcegroup status
```
Make a record for later reference of the online resource groups and on which cluster node each resource group is online.

Identify the resource name for the sczbt components that manage the failover zone.
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.
Suspend each online resource group that manages a failover zone of brand type solaris.
```
# 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 the standard or rolling upgrade on the nodes.
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.
Disable each scbzt resource that you recorded in Step 2.
```
# 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.

For each resource group that you recorded in Step 1. bring the resource group online on the same node where it was online during the upgrade.
```
# 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.
Attach and boot the failover zone.
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
```
Verify the zone console.
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
```
# zlogin -C zone-name
```
Shut down and forcibly detach the failover zone.
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
```
Enable each sczbt resource.
Do this for each zone that is managed by an sczbt resource that you identified in Step 2.
```
# clresource enable sczbt-resource
```
Resume each resource group that you brought online in Step 6.
```
# clresourcegroup resume resource-group
```

Next Steps

Go to Completing the Upgrade.