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

In large networks, divided in different localities, with large size eDirectory, with many objects, with multiple WAN links and with centralized management, the creation of cluster resource scripts or any modification can become a task with a lot of patience.

Sometimes, after you have made a modification to anyone in the scripts of resources is necessary to wait for the replication of changes in the eDirectory and that the scripts are updated in the folders var/opt/novell/NCS/of each node.

In certain cases, to ensure that the scripts are updated in all nodes is necessary to use the command /opt/novell/NCS/bin/NCS-configd.py -init .

Administrators of the clusters should expect that the synchronization process and update of the scripts are complete.

A signal, flag or status message in the iManager indicating the synchronization status of scripts of the resources can be of great utility.

In the same way, a console command of cluster also can be very useful.

Example: cluster scripts status < Resource Name> --> Scripts Updated, Scripts Outdated, Scripts Insync, etc.

by: Carlos R. | over a year ago | Cluster Services (NCS)