ClusterUpdate
From pressy's brainbackup
Cluster Update
let's update our cluster running a flying zone:
On both nodes:
# scinstall -u update -b 11.3.26.0.5.0 -L accept
[...]
disable the zone-resource
# clrs disable name-zone-res
reboot second cluster node where the RG is not running into the new BE after coming back, switch the RG to the updated node
clrg switch -n <node> name-zone-rg
Now set the BE UUID from the first node to the second
first# /opt/SUNWsczone/sczbt/util/ha-solaris-zone-boot-env-id get second# /opt/SUNWsczone/sczbt/util/ha-solaris-zone-boot-env-id set <uuid>
Having the storage-res/RG on the second node and the right UUID you can attach the zone:
# zoneadm -z <name> attach -x destroy-orphan-zbes
Check if the zone comes up with a normal state (boot and svcs -xv). If ok, shutdown the zone again.
Now we can give the control back to the cluster
# clrs enable name-zone-res # clrg resume name-zone-rg
Now you can try to switch back...
Now you could also upgrade your resource type version