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.
Programs should be unloaded in the reverse order of how they were loaded. This ensures that supporting programs are not unloaded before programs that rely on them in order to function properly.
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 6.
In iManager, select Clusters > My Clusters.
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 8.2, Setting Up a Personalized List of Clusters to Manage.
Select the Cluster Options tab.
Select the cluster resource to view its Properties page.
You can also select the check box next to the resource, then click Details.
On the Properties page, click the Scripts tab, then click the Unload Script 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, volume group name, file system type, and mount device.
Specify the Unload Script Timeout value, then click Apply to save the script or, if you are creating a new cluster resource, click Next.
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 Next, then continue with Section 10.7.2, Configuring Resource Monitoring.
Click Apply to 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 10.8, Applying Updated Resource Scripts by Offline/Offline, Failover, and Migration.