/
5-1 Group Control

5-1 Group Control

Group control is affected by group state. Following are the commands and attributes related to control a group.


Table of Contents

Group Online/Offline

It issues an online/offline command for all resources in the group.
This means that bring online all the resources added in a group on a node. 
For more details, please refer to "Chapter 5. 3 Dependency Management" of this document
If there is an online node in a failover group, online command will not work. However this will be work for partial online state.

Offline command enables a node which is online for partial online a group. It is used when take offline all the online resources or deletes some of the resources or safely turn 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 given to enabled nodes.

[Figure] Group Online


[Figure] Group Offline


 

Switch

This is manual switch over the group from a node to another node. It is useful when you need do maintenance for node 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.
From the group management view of MCCS console, select the group and right click as shown in the picture below, then select ‘Switch’, the node of the group will be enabled which can be applied.

This command can only be given to enabled nodes.

[Figure] Manual Group Failover View


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 standby 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 not allowed. 
But command for Add/Delete/Probe/Clear Fault for resource are allowed.
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 impossible re-failover or manual switch to original node without clear this.
From the group management view of MCCS console, select the group or the resource and right click as shown in the picture below, then select ‘Clear Fault’, the node of the group will be enabled which can be applied. 

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