6- Resource Type
Resource type is classified resources according the characteristics and has different attributes for each type.
Table of Contents
Resource Type
[Figure] Resource Types in the MCCS for Linux
Network Interface card(NIC)
MCCS monitor the TCP/IP based network connectivity. It detects the network unplug, ethernet adapter failure, or cable failure.
IP Address
MCCS manages virtual IP address and subnet mask which will be assigned on a NIC and switchable node to node in case it reacts in the same manner as the node's real IP address.
A real IP address which is static must be set in the NIC to add on a virtual IP address.
Process
Process is used when register single execution file. MCCS detects the failures by checking if the process name exists in the process table of operating system.
Application
It is similar to process. But this is more complicated. Application works with several application or scripts such as tomcat.
MCCS does only detect on execution file, but it also brings online/ take offline/monitor the process by using pre-defined script.
Shared Disk
MCCS monitors the status of I/O path for a node connected to the external shared storage.
Mirror Disk
When there is no shared disk in a cluster, data is saved in local or the direct-connected storage.
In such an environment, TCP/IP based mirror components are used to copy the changed data.
Service
The service manages the process sets managed by the linux daemon.
Shared disk DR
It is the mirror set of shared disk in a cluster to an off-site DR node through WAN, so that mission critical service will be always-on from disasters.
Mirror disk DR
It is the 2nd mirror disk set of mirror disk in a cluster to an off-site DR node through WAN, so that mission critical service will be always-on from disasters.
Oracle database
This resource controls the Oracle database.
It detects the Oracle database installed on the system, controls thee service and monitors the status.
Oracle Listener
This resource controls the listener process of the Oracle DB.
Postgres Plus Advanced Server
This resource controls the PPAS and detects whether PPAS is installed on a system or not, also controls relevant services and monitors their status.
Resource Type Attribute
Each resource type has a specific attribute value.
For an example, when compare to NIC and mirror disk, each service has different characteristics and has specific monitor interval, online/offline timeout and managed policies
In addition, even in the environment where high availability clusters are configured, if the network condition is not good, you need to adjust the monitoring timeout.
Depending on the requests, you can change the attribute of each type.
Resource type attribute can be checked in the resource type attribute menu of the MCCS web console.
Detail on the "Specified Attribute" is also described on each page related to every resource in this manual.
Detail on the "Resource Attribute" is also described on the "Resource" in this manual.
[Figure] Resource Type Attribute View
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/ | Edit | Note | |
---|---|---|---|---|---|---|---|
ResourceType Attribute | Actions | Define the resource operation type. | STRING | X | |||
Resource General Attribute | *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. | 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 | ||
FaultOnMonitorTimeouts | If the monitoring timeout take place as much as this value, it is regarded as fault. | INTEGER | 4 times | 0 to 12 times | O | ||
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. | 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 | ||
OfflineMonitorInterval | It is the time interval until the next monitoring of offline resource. | 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. | 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. | INTEGER | 2 times | 0 to 30 times | O | ||
*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 Mirror Disk DR X Other Resources O | ||
ToleranceLimit | When the monitoring results cannot be trusted , monitoring will be retried during the defined time. | INTEGER | 0 time | 0 to 100 times | O | ||
WaitMonitorInterval | It indicates the time interval until starting the next monitoring when monitoring resources which are waiting for online or offline. | INTEGER | 1sec | 1 to 300 seconds | O |
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.
CLI Use (mctype command)
Sends command related the resource type. You can command to inquire about the attribute or change the attribute values.
When you install MCCS, the initial user account is set to 'admin' and the password is set to 'password'.
When you run the CLI command, you need to enter the account and the password. Otherwise, the above initial account and password will be used.
Thus, when you change the account and password, you must enter the account/password in the CLI command as options.
Syntax
mctype [-u userid -pw password] -t resoruceType -a attribute |
Options
Option | Description |
---|---|
-h | Display Help. |
-u | Enter the user account. |
-pw | Enter the password. |
-r | Designate the name of resource type to be modified. |
-a | Designate the attribute names for the resource type to be modified. |
-list | Display the list of resource types. |
Example
modify
Modify the MonitorInterval attribute values for MirrorDisk.
mctype -modify -t resoruceType -a attribute attribute_value |
list
Display the attribute values for all the resource types.
(If you enter -t resourceType, the attribute values for the designated resource type will be displayed.)
mctype -list [-t resourceType] |