clstrlib.conf really saved my day, adding a node to an OES cluster. The
password for the LDAP user had been changed, and I had no clue where it was
stored on the old nodes. The TID linked here was just what I needed, but I
just couldn't find it from the KB, since it had a different problem as



>>> On Thu, Jul 5, 2007 at 4:25 PM, in message

Robert<> wrote:
> As almost totally undocumented (afaik), NCS communicates with eDirectory
> in a strange way: it caches some of the relevant eDirectory information
> (cluster nodes, cluster resources etc.) into the local filesystem e.g.
> - /etc/opt/novell/ncs/*.load
> - /etc/opt/novell/ncs/*.unload
> - /etc/opt/novell/ncs/resources.xml
> - /etc/opt/novell/ncs/clstrlib.conf
> (

> en-enterprise-server.clustering#5592
> -- many thanks Don!)
> This "data synchronization" seems to be LDAP based. The LDAP DN (like
> cn=Admin,o=mycompany) and the password of the Admin user seems to be
> wired
> (in an encrypted way) into some of the "cached files" (like
> /etc/opt/novell/ncs/clstrlib.conf).
> Concerning this, I some fundamental these questions (afaik unanswered
> both
> in the Novell documentation/knowledgebase and this newsgroup):
> - does iManager read eDirectory or the "cached files"?
> - does iManager write eDirectory or the "cached files"?
> - which application/process/daemon does perform the "data
> synchronization"
> between eDirectory and the "cached files"?
> - which events do trigger this "data synchronization" process?
> - is there a way to force this "data synchronization" manually?
> - can this "data synchronization" events be logged?
> - what should be done (beyond TID-3753894) after changing the Admin
> password so that the LDAP-based "data synchronization" should work again?
> And the most important question is this:
> - is this whole stuff documented/described somewhere?