I am not able to get my HA zone to come up, it stays in offline state
and a clresource enable <ha zone resource> does not help, this is the
message I get:
cluster status
,snip>
Resource Name Node Name State Status Message
------------- --------- ----- --------------
hazone-zone CCC Offline Offline
BBB Starting Unknown - Starting
This is what I did:
clresourcetype register SUNW.HAStoragePlus
clresourcegroup create hazone-rg
clresource create -t SUNW.HAStoragePlus -g hazone-rg -p
Zpools=hazonepool -p AffinityOn=True hazone-zpool
clreslogicalhostname create -g hazone-rg -h hazone-lh hazone-lh
clresourcegroup online -M hazone-rg
On one node: zonecfg -z hazone
set zonepath=/hazonepool/zones/hazone
then
clresourcegroup switch -n node2 hazone-rg
mv /hazonepool/zones/hazone/root /hazonepool/zones/hazone/root.old
zonecfg -z hazone
set zonepath=/hazonepool/zones/hazone
clresourcetype register SUNW.gds
vi /etc/zones/sczbt_config
# The resource group that contains the resources the zones depend on
RG=hazone-rg
# The name of the zone resource to create
RS=hazone-zone
# The directory where this configuration file is stored
PARAMETERDIR=/etc/zones
SC_NETWORK=true
# Name of the logical hostname resource
SC_LH=hazone-lh
# Name of the zone you passed to zonecfg -z
Zonename=hazone
Zonebrand=native
Zonebootopt=”"
Milestone=”multi-user-server”
FAILOVER=true
# ZFS pool that contains the zone
HAS_RS=hazone-zpool
cd /opt/SUNWsczone/sczbt/util
./sczbt_register -f /etc/zones/sczbt_config
The resource hazone-zone shows up offline..............
Did you remember to do console login on the zone for the first boot
initial setup?
Sami
yes
And still if you import the pool manually and star the zone manually
you are able to start the zone with no problems?
Sami
Thanks for following up. I appreciate it. Yes the zones start on both
nodes no problem.
Without cluster hooks - The zones start on either node without issue -
my issue is that when I put in the zone resource by using the /opt/
SUNWsczone/sczbt/util/sczbt_register script the zone stays on OFFLINE
state on both nodes, clresource enable <resource name> brings it
online - after a while. The zone then comes online but does not
failover.