It is classified resources according the types 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

There are two systems connected to external shared storage and MCCS monitor the health status of I/O path to the file system.

Mirror Disk

When clustered nodes does not use shared storage, the data will be stored in each of local disk or direct attache storage.
In this environment, the mirroring component is needed through TCP/IP connection between nodes to synchronize the changed data.

Service

The service manages the process sets managed by the linux daemon.

SCSI Reservation

SCSI reservation agents manage LUN based locking using the SCSI3-PR (Persistent Reservation) protocols that shared storages support such as SAN.
This function can prevent data losses when no nodes in a cluster know the status of other nodes.

Oracle database

This resource controls the Oracle database.
It detects the Oracle database installed on the system, controls the service and monitors the status.

Oracle Listener

This resource controls the listener process of the Oracle DB.

When you add a resource, this will be classified under the type as tree view structure.
For an example, when you add two NIC resource, these will be classified under the NIC type as shown below.
If you edit an attribute of resource type, this will affect all of the resources classified this type.

[Figure] Classifying of resources under the type

As shown in the figure, eth0 and eth1 are the resources included in the NIC resource type.
If you edit an attribute of resource type, this will affect all of the resources classified this type.
For an example, if the value of MonitorInterval of NIC resource type is edited to 30 sec, this will be applied to all of NIC resource.

Resource Type Attribute

Resource type has specified attributes for each type.
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.

[Figure] Resource Type Attribute View

Attribute	Description	Type	Default	Edit	Note

Attribute	Description	Type	Default	Edit
Actions	Define the resource operation type. OnOff value is the command resource. None is the resource command only for monitoring.	STRING		X
ArgList	It represents the necessary arguments for each type of resource. Based on these arguments, you can create variables in an agent and characterize the types. You can check it in the type.json file but the value cannot be modified by a user.	STRING		X
CleanTimeout	It represents the time out until execution of CleanProgram is finished. When the limit is exceeded, it will be forcefully terminated.	INTEGER	60 sec	O
FaultOnMonitorTimeouts	If the timeout specified by this value occurs, it is regarded as trouble. If it is '0', it is not regarded as trouble.	INTEGER	4 times	O
MonitorInterval	It represents the time interval until the next monitoring of online resource. If the value is too small, it could mistakenly start monitoring before receiving the proper monitoring results. If the value is too big, then it will take too long until it detects the status changes.	INTEGER	10 sec	O
MonitorTimeout	It represents the time elapsed until monitoring is finished or terminated.	INTEGER	10 sec	O
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	60 sec	O
OfflineTimeout	It represents the max time until the final decision is made on the success/failure of resource going offline.	INTEGER	300 sec	O
OnlineRetryLimit	Set the number of retries if the resource fails to restart.	INTEGER	0 time	O
OnlineTimeout	It represents the max time until the final decision is made on the success/failure of resource going online.	INTEGER	300 sec	O
OnlineTrustTime	It is the time to reset the restart number of resource. Initialize the number of retries if the normal condition is maintained for the duration specified after the resource is started	INTEGER	600 sec	O
OnlineWaitLimit	If the time our occurs while determining whether the resource goes online properly, it will retry as many times as designated. It is the time interval of retry is defined in 'MonitorInterval'.	NTEGER	2 times	O
* ToleranceLimit	When the monitoring results cannot be trusted , monitoring will be retried as many times as designated. For instance, if the network condition is not good, and you cannot trust the ping test results, then you need to perform monitoring several more times until you get a good result.	INTEGER	0 time	O

6- Resource Type