For OES 11 SP1 (with the latest patches) and later, when you modify the load, unload, and monitor scripts for a resource and click Apply or OK, the updated resource scripts can take effect in any of the following ways:
When an administrator takes the resource offline and then brings it online on the same node.
When the resource fails over to another node, if both the source and destination nodes have received the updated scripts from eDirectory.
When an administrator uses the cluster migrate command to load the resource on another node, if both the source and destination nodes have received the updated scripts from eDirectory.
In earlier releases, script changes do not take effect until the resource is taken offline and then brought online.
The ability of the scripts to be applied on fail-over or migration to a different node depends on the synchronization of the updated scripts from the master node to eDirectory, and from eDirectory to the nodes in the cluster. The destination node will not run the updated scripts unless the updated scripts are visible on both the source node (where the resource is currently running) and the destination node.
To verify that the updated scripts can take effect on the destination node:
In a text editor, verify that both the source node and destination node have the updated scripts (resource_name.load, resource_name.unload and resource_name.monitor) under the /var/opt/novell/ncs/ directory.
If the scripts are the same on both nodes, the updated scripts are applied on failover or migration between those nodes.
If the scripts are not the same on both nodes, pull the scripts down to the nodes from eDirectory:
Ensure that eDirectory is fully synchronized.
On the source node, pull down the scripts from eDirectory. Log on as the root user, open a terminal, then enter
/opt/novell/ncs/bin/ncs-configd.py –init
Repeat Step 2.b for the destination node.
Repeat Step 1 to verify that both the source node and destination node have the updated scripts.