5.1 Group Control.
- Copy Page Tree
Group control is affected by group state. Following are the commands and attributes related to control a group.
Table of Contents
Enable All Resources / Disable All Resources
Through these menus(Enable All Resources and Disable All Resources), it is available to choose whether use all resources in a group or not. All resources in new group will have been activated basically because the Enable All Resources function is applied automatically as soon as adding a group.
But, if needed, it is available to de-activate all resources in a group temporarily by using the Disable All Resources function, for instance, in case of maintenances.
Then, all resources would have been de-activated so it is not available to start or stop a group, or to do others. Choose the Enable All Resources menu if the resources in the group have to be started again after temporary working such as maintenances. Then, functions such as start/stop a group will be available to operate again because all of the resources in the group has been re-activated.
Group Online/Offline
It initiates an online/offline command for all resources in the group.
This means that MCCS bring online all the resources by order of dependency among those in a group on a node.
For more details about dependency, please refer to "5.4 Dependency Management" of this document.
If there is an onlined group on a node in a failover group, online command will not work. However this will be work if the group state is partial online.
Offline command enables a node which group state is online or partial online. It is used when take offline all the onlined resources or deletes some of the resources or safely power off/reboot a node.
From the group management view of MCCS console, select the group and right click as shown in the picture below, then select ‘Online’ or ‘Offline’, the nodes of the group will be enabled which can be applied.
These commands can only be initiated to enabled nodes.
[Figure] Group Online
[Figure] Group Offline
Switch
This is manual switch over the group from a node to opposite node. It is useful when you need to keep online a service during unplanned downtime like O.S update, patch, job related server rebooting and etc.
Or when you completed cluster configuration, you can group failover test using this without node shutdown.
This command can be changed by selecting the node on service. It can test if the failover works properly or testing if there is any problem after failover and so on.
This is called 'Switch over' and 'Switch' command. A group should be online or partial online to enable this and standby node should not be in a failure status.
This command can only be given to enabled nodes.
[Figure] Manual Group Failover View
Release Auto Deactivation
Sometimes MCCS on an original primary server does not work well although both of two servers installed MCCS have been booted well and the OS of both sides operate normally, and in the case, all resources will be deactivated automatically, so the followings will be getting needed: checking and then activating the resources deactivated automatically. In details, if the current operated MCCS cannot communicate with another MCCS on another server, resources status or information will not be detected and then all resources are forced to be deactivated automatically. To check these deactivated resources and to run the relevant service on the MCCS of the current operating server, use this function. In summary, it is the function enables to check the resources which have not been checked by error. MCCS, and then to make the resources online on another server which the current MCCS is operated well.
Group Lock
Group lock is useful when you need to maintain like test, update and patch the resources. MCCS monitor the status of resources, but do not online, offline and failover for ‘lock’ state group.
For an example, when you patch your own developed ‘a.exe’ which is managed by MCCS, you may need ‘a.exe’ process down for maintenance.When you get planned downtime for this, MCCS will detect this as failure and is trying to restart that or failover the group to secondary node which you do not want to be.
When group lock is set, command for Online/Offline/Switch for group and Online/Offline/Offline Prop/Enable for resources are disabled.
But command for Add/Delete/Probe/Clear Fault for resource are enabled.
There are ‘Temporary Lock’ and ‘Lock’ and it’s attribute can be checked on Group Attributes view. When MCCS service is stop, ‘Temporary Lock’ will be unlocked even after this is brought up again.
But ‘Lock’ remains the same after do this. From the group management view of MCCS console, select the group and right click as shown in the picture below, then select ‘Lock’, You can choose Temporary Lock or Lock from this.
[Figure] Lock Group View
Temporary Lock
Unlocks when both nodes of MCCS service is stop and restarted.
Permanent Lock
Group is lock permanently even after MCCS service is stop and restarted. This will be unlock when you set ‘Unlock’ command from management console.
Clear Fault
When a failure is occurred on a resource and MCCS decide this is failed, this will be marked failed resource with icon on its resource and group icon.
This mark is needed to be clear after you fix the problem of the resource. It is not allowed re-failover or manual switch to original node without clear this.
This command can only be given to enabled nodes.
[Figure] Clear Fault
Flush
This is used when commands like Online/Offline/Switch for a group is pending for some reasons (e.g. hang up) and this is needed to be initialized.
All the commands will be cancelled by using 'Flush'.From the group management view of MCCS console, select the group and right click as shown in the picture below, then select ‘Flush’, the node of the group will be enabled which can be applied.
This command can only be given to enabled nodes.
[Figure] Group Flush View