01-11-2015 10:37 AM
Hi
I have a service group named redsg running which is online on node1 and and offline on node 2.
I froze resg and ran hastop -all -force ,and started it back again on both nodes
the service group state is online now on node1 and offline on node2 as earlier
But when i reboot the node the service group goes to offline on both nodes.
Any idea what makes this difference.
Thanks
dilip
Solved! Go to Solution.
01-11-2015 08:15 PM
As for the action taken before, hastop -all -force brings down only the cluster process (HAD) and leaves the clustered application in the exisiting state. Therefore when you restarted HAD with hastart, it found the application as you left it, online.
01-12-2015 05:44 AM
A few points:
Hence when you reboot a node where the group is online and frozen, the frozen state prevents the group switching to other node when server goes down and prevents the group being started when the server comes back up.
Mike
01-11-2015 08:11 PM
Hello,
This would depend on what command you used to freeze the group .. If you have used "persistent" flag in the "hagrp -freeze" command, the group will remain frozen & won't change the status once node is rebooted. So if a node is rebooted, as soon VCS is started, VCS will read the persistent frozen flag & will not take any action on group & hence it is offline.
Refer admin guide for more details
https://sort.symantec.com/public/documents/sfha/6.1/solaris/productguides/html/vcs_admin/ch06s12s07.htm
G
01-11-2015 08:15 PM
As for the action taken before, hastop -all -force brings down only the cluster process (HAD) and leaves the clustered application in the exisiting state. Therefore when you restarted HAD with hastart, it found the application as you left it, online.
01-12-2015 05:44 AM
A few points:
Hence when you reboot a node where the group is online and frozen, the frozen state prevents the group switching to other node when server goes down and prevents the group being started when the server comes back up.
Mike