jspωiki
Limber

Limber#

Limber EDirectory Background Processes is responsible with maintaining NDS Tree connectivity and periodically, each NcpServer in the NDS tree checks and verifies that it still knows the correct tree name.

Limber is the process that performs Agent Configuration Synchronization. Limber (may also be referred to as Connectivity Check) may trigger other processes to refresh their configuration (i.e. LDAP, etc.)

Limber is scheduled to run every 4 hours by default, which is configurable in NDS Imonitor. Limber will also run when requested or when a change is noticed that needs to be synchronized.

Limber check is executed when the NcpServer boots, when the NDS processes are restarted and when the server receives a specific Limber request from another NcpServer.

Limber process typically runs when a tree name changes or with IP or IPX address changes. A NcpServer holding the Master NDS Partition needs to send out the request. Additionally, the Limber process will run when the Master NDS Partition of a server receives change information from another NcpServer/partition on the NDS tree.

After questioning several sources, it is still unclear to me why this process is named Limber, so that will remain a mystery for now. However, naming issues aside, Limber is an EDirectory Background Processes that is responsible for

Limber can be monitored indirectly through

  • Ndsrepair using the Check External Reference, Report Synchronization Status, and Replica Ring repair options.
  • Ndstrace (LMBR Flag) also provides the ability to monitor Limber directly.

More Information#

There might be more information for this subject on one of the following: