Depending on your cluster application or resource, you can add an unload script to specify how the application or resource should terminate. An unload script is not required by all resources, but is required for cluster-enabled Linux partitions. Consult your application vendor or documentation to determine if you should add commands to unload the resource.
Example unload scripts are available in the following sections:
If you are creating a new cluster resource, the unload script page should already be displayed. You can start with Step 5.
In the left column of the main iManager page, locate , then click the link.
Browse to locate and select the Cluster object of the cluster you want to manage.
Select the check box next to the resource whose unload script you want to edit, then click the link.
Click the tab, then click the link.
Edit or add the necessary commands to the script to unload the resource on the server.
You can add any lines to the unload script that are required to unload services that are loaded by this cluster resource.
You also need to personalize the script by replacing variables with actual values for your specific configuration, such as the mount point, IP address, container name, file system type, and device.
Specify the value, 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 when migrating to another node. 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 , then continue with Section 10.6.2, Configuring Resource Monitoring.
Click to save your changes.
Changes for a resource’s properties are not applied while the resource is loaded or running on a server. You must offline, then online the resource to activate the changes for the resource.