A load script is required for each resource, service, disk, or pool in your cluster. The load script specifies the commands to start the resource or service on a server.
Example load scripts are available in the following sections:
If you are creating a new cluster resource, the load script page should already be displayed. You can start with Step 6.
In iManager, select> .
Select the cluster that you want to manage.
If the cluster does not appear in your list, add the cluster to your list as described in Section 9.2, Setting Up a Personalized List of Clusters to Manage.
Select the cluster resource to view its Properties page.
You can also select the check box next to the cluster resource, then click.
On the Properties page, click thetab, then click the link.
Edit or add the necessary commands to the script to load the resource on a server.
You can then add any lines to the load script that are required to load needed services like web servers, and so on.
You also need to personalize the script by replacing variables with actual values for your specific configuration, such as the mount point, IP address, volume group name, file system type, and mount device.
IMPORTANT:Do not comment out commands that are automatically generated for parameters that define the cluster resource, such as the mount point, IP address, volume group name, file system type, and device.
Specify thevalue, then click to save the script or, if you are creating a new cluster resource, click .
The timeout value determines how much time the script is given to complete. If the script does not complete within the specified time, the resource becomes comatose. Cluster Services marks the process as failed right after the defined timeout expires, but it must wait for the process to conclude before it can start other resource operations.
The timeout value is applied only when the resource is migrated to another node. It is not used during resource online/offline procedures.
Do one of the following:
If you are configuring a new resource, click Section 11.6, Configuring an Unload Script for a Cluster Resource., then continue with
Clickto save your changes.
Changes for a resource’s properties are not applied while the resource is loaded or running on a server. Apply the updated script by taking the resource offline and then bringing it online on the same node. Alternatively, after the updated scripts have been synchronized from eDirectory to the source and destination nodes, the updated scripts are used automatically on system failover or cluster migration. For more information, see Section 11.8, Applying Updated Resource Scripts by Offline/Offline, Failover, and Migration.