...
Resource attribute is a reference value used when the resource takes some actions or determines the status.
Resource attribute can be identified from Resource Attributes view of MCCS web console.
From the group management view of MCCS web console, select the resource, then select ‘Resource Attributes’ tab located on the top of detailed information panel.
The values of gray colored are read only. They just contain and show the information of resource state.
The values of white colored are configurable by user definition. Below is description of some of them.
※ '리소스 고유 속성' 에 대한 설명은 각 리소스 페이지에 설명되어 있습니다.
※ '리소스 일반 속성' 은 리소스 타입에도 있습니다.
...
| Info |
|---|
Detail on the "Specified Attribute" is also described on each page related to every resource in this manual. |
| Info |
|---|
Detail on the Resource Attribute is also described on the Resource Type in this manual. |
[Figure] Resource Attribute View
| Info |
|---|
| MCCS 에서 구성할 수 있는 리소스의 최대 갯수는 500개이며, 그룹의 최대 갯수는 32개 입니다 Maximum numbers of resources available to be configured in MCCS is 500 pieces, and those of groups is 32 pieces. |
| Info |
|---|
| *이 표시된 속성의 경우, 온라인/오프라인 명령이 불가능한 네트워크 카드 리소스에서는 사용되지 않습니다 Among the attributes listed on the following tables, those with the * marks do not work on the network card resources that is unable to use the online/offline command. |
| Attribute | Description | Type | Default | Minimum Value/ Maximum Value | Edit | Note | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Key Attribute | Critical | When a failure occurs in the resource it indicated whether to failover the group. | BOOLEAN | X | ||||||||
| Enabled | It is used when deciding whether to manage the resource. | BOOLEAN | X | |||||||||
| General Attribute | AgentState | It indicates the agent state of the resource. | STRING | X | ||||||||
*BatchAfterOffline | This is a batch command to be executed after a resource is taken offline. | FILE | 8 to 254 characters of text | O | ||||||||
*BatchAfterOnline | This is a batch command to be executed after a resource is brought online. | FILE | 8 to 254 characters of text | O | ||||||||
| *BatchBeforeOffline | This is a batch command to be executed before a resource is brought online. | FILE | 8 to 254 characters of text | O | ||||||||
| *BatchBeforeOnline | This is a batch command to be executed before a resource is taken offline. | FILE | 8 to 254 characters of text | O | ||||||||
| *BatchTimeout | It is the waiting time until execution of batch command completes. If execution result is over this time, it is considered as a failure. | INTEGER | 300sec | 100 to 1500 seconds | O | |||||||
| CleanProgram | This program is executed to initialize related resources and state when a failure occurs to a resource. This program must be written separately. | FILE | 8 to 254 characters of text | O | ||||||||
| CleanTimeout | It represents the time out until execution of CleanProgram is completed. When the limit is exceeded, it will be forcefully stoped. | INTEGER | 60 sec | 0 to 300 will be forcefully stoped. | INTEGER | 60 sec | 0 to 300 seconds | O | ||||
| EnableTimeout | It is the waiting time until the execution of Enable completes. If the execution result is over this time, it is considered as a failure. (unit = second) | INTEGER | INFINITY | 1 to INFINITY seconds | O | |||||||
| *Failoverable | It indicates whether the resource is in the state to be failover. | BOOLEAN | X | |||||||||
| FaultOnMonitorTimeouts | If the monitoring timeout take place as much as this value, it is regarded as fault. If it is '0', it is not regarded as fault. | INTEGER | 4 times | 0 to 12 times | O | |||||||
| Group | It is the name of the group which the resource belongs. | STRING | 4 to 50 characters of text | X | ||||||||
| *LastOnline | It is name of the node on which state of the resource is online lastly. | STRING | X | |||||||||
| Monitored | Depending on the 'MonitorTimeout', attribute values for the resource types, it record periodically whether each node's monitoring is completed. | BOOLEAN | X | |||||||||
| MonitorInterval | It indicates the interval to the next monitoring when online resources are monitored. If the value is too small, it may result in malfunction. If the value is too big, then it will take too long until it detects the status changes. | INTEGER | 10 sec | 1 to 300 seconds | O | |||||||
| MonitorTimeout | It represents the time elapsed until monitoring is completed or terminated. | INTEGER | 60 sec | 1 to 300 seconds | O | |||||||
| NoAction | It represents the action attribute of the resource. | BOOLEAN | X | |||||||||
| OfflineMonitorInterval | It is the time interval until the next monitoring of offline resource. If the time interval is '0', the offline resources will not be monitored. | INTEGER | 10 sec | 0 to 300 seconds | O | |||||||
| *OfflineTimeout | It indicates the maximum time until resources is taken offline successfully, stop or final judgment is made. | INTEGER | 300 sec | 1 to 1500 seconds | O | |||||||
| *OnlineRetryLimit | It indicate the number of retry count if it fails to start resource. | INTEGER | 0 time | 0 to 10 times | O | |||||||
| *OnlineTimeout | It indicates the maximum time until resources is brought online successfully, stop or final judgment is made. | INTEGER | 300 sec | 1 to 1500 seconds | O | |||||||
| *OnlineTrustTime | It is the time to reset the retry count of resource. If resources remain normal for a specified amount of time after starting, the retry count will be initialized. | INTEGER | 600 sec | 60 to 3000 seconds | O | |||||||
| *OnlineWaitLimit | If the timeout occurs while determining whether the resource goes online properly, it will retry as many times as defined. It is the time interval of retry is defined in 'MonitorInterval'. | INTEGER | 2 times | 0 to 30 times | O | |||||||
| Persist | It is used when deciding whether to manage the resource. Persist Resource just has two resource state Online and fault. | BOOLEAN | X | |||||||||
| ResName | It is the name of the resource. | NAME | 4 to 50 characters of text | X | ||||||||
| *Restartlimit | It shows the retry count before failover when the resource is determined as a failure. | INTEGER | 0 | 0 to 100 times | Shared Disk DR X | |||||||
| State | It is the resource state of each node. | STRING | X | |||||||||
| ToleranceLimit | When the monitoring results cannot be trusted , monitoring will be retried during the defined time. For instance, if the result of the ICMP ping test with a network interface card cannot be trusted, it must be retried as many times as defined. | INTEGER | 0 time | 0 to 100 times | O | |||||||
| Type | It is the name of the agent type of the resource. | STRING | X | |||||||||
| EnableTimeoutWaitMonitorInterval | It is indicates the waiting time until the execution of Enable completes. If the execution result is over this time, it is considered as a failure. (unit = second) | INTEGER | INFINITY | 1 to INFINITY seconds | O | WaitMonitorInterval | 온라인, 오프라인 대기중 리소스를 모니터링 할 때, 다음 모니터링까지의 시간 간격을 나타냅니다time interval until starting the next monitoring when monitoring resources which are waiting for online or offline. | INTEGER | 1 sec | 1 to 300 seconds | O | |
| Info |
|---|
MCCS 는 사용자의 입력필드에 대한 입력값 제한 기능이 존재하며, 사용자가 잘못 입력한 데이터에 대해 자동 점검기능을 제공합니다 has function to limit input values against user's input field, and it provides function detects automatically data which is input wrong by user's mistake. |
Critical
This attribute shows to failover (true) or not (false) when failure has occured.
Default is set as true, and most of the resources are set as a true value. For resources that is not as important or resources that cannot be failover are set as false.
Critical values affects failover group only, does not affect parallel group. Critical attribute can be set onto each resource, but there are many things to be considered if it has linked dependency among resources. If at least one of the resources has true value of it's critical attribute in a group, all of the resources will be failover to provide proper service.
...
Resource is not being monitored since it is not enabled.
Resource Control
[Figure] Resource control
A resource can be managed easily through MCCS console. From the group management view of MCCS console, select the resource and right click , then control menu will be pop up.
...
You can delete a resource by using this.
Copy and Paste Resource
It is an annoyance if attribute value is entered whenever a new resource is added.
When you add a new resource same as type of resource which is already exist, you can use this function.
Copied resource maintain same values as original one and can be pasted on any group.
After paste the resource, you can edit the values.
| Warning |
|---|
Attribute values that is copied resource are basically same as original resource. |
Copy and Paste resource
- Right click on the resource to be copy and select "Copy Resource".
- Right click on the group to be paste and select "Paste Resource".
| Info |
|---|
Copied resource name is defined which '"_number'" is added from original name by default and this can be editable.ex) Original name is 'UserProgram', copied name will be 'UserProgram_1'. When you copy this resource again, second copied name will be 'UserProgram_2'. Depending on the resource type, you need to enter extra information if necessary. |
[Figure] Paste Networkcard Resource View
CLI Use (mcres command)
It sends the commands related to MCCS resource. Resource related commands such as add, delete, online, offline and etc can be done.
...
mcres [-u userid -pw password] [-ip node_ip_address] [-p port] -command [ resource ] [ -g group ] [ -n node]mcres [-u userid -pw password] [-ip node_ip_address] [-p port] -add [ resource ] [ -t resource_type ] [ -g group ]mcres [-u userid -pw password] [-ip node_ip_address] [-p port] -monitor [ group_name ] [ -t interval(seconds)]mcres [-u userid -pw password] [-ip node_ip_address] [-p port] -modify [ resource ] [-a attribute attribute_value] [ -g group ] [ -n node] |
Options
| Option | Description |
-h | Display help menu. |
| -u | Enter the user account. |
| -pw | Enter the password. |
-ip | It defines the node to access to execute command. If omitted, it will access to execute command for local node. |
-p | It defines the port to access to execute command. If omitted, it will access to the default value which is 4321, and when you define specific port number as heartbeat, enter this followed by --p. |
-resourcecommand | It defines resource command. (add, delete, enable, disable, monitor, modify, link, unlink, local, Global, Online, Offline, Offlineprop, Probe, clear, list) |
resource | It enters resource name. |
-a | [list] It defines the attribute value that should be listed if it is command. |
-t | It defines resource type when it is [-add] command. It specifies time interval when it is [-monitor] command. |
-g | It defines group name to be managed. |
-n | It defines node name to be managed. |
...