Environment
Novell eDirectory 8.8 for All Platforms
Novell eDirectory 8.7.3 SP10 for All Platforms
Novell eDirectory 8.7.3 SP10 for All Platforms
Situation
When ndstrace is run on the OpenSLP DA server using the service advertizing flag it can be seen that the server is re-regestering its services every 10 minutes.
Resolution
This is not a problem nor can the timing of eDirectory reregistration be changed.
Using the default parameters in a typical environment the following process gives a summary of what can be considered expected behavior of an eDirectory server using OpenSLP.
1. A server is configured as an OpenSLP DA.
(More information can be found at https://www.novell.com/documentation/edir873/index.html in the Novell eDirectory 8.7.3 Administration Guide under the section entitled Configuring OpenSLP for eDirectory.)
2. When the OpenSLP DA service is started it does not read eDirectory as with Novell's SLP product but rather starts with an empty cache. It therefore knows of no services starting out.
2. When the OpenSLP daemon comes up it broadcasts on the local subnet that it is available.
3. All SA's on that net that are configured to register with this DA do so.
From that moment on, unlike NetWare, the SLP client application is responsible for not only re-registering with its local SA and from there to the DA but also sets its slp lifetime.
4. The DA takes the registration information it receives and places it into its registration cache.
5. However, eDirectory has been hard coded to re-register its services to the DA every 10 minutes. This cannot be changed nor can its default lifespan of 3600 seconds.
Normally the re-registration of eDirectory services on a server takes place in under a second. As this occurs every 600 seconds there is minimal overhead in doing so.
Using the default parameters in a typical environment the following process gives a summary of what can be considered expected behavior of an eDirectory server using OpenSLP.
1. A server is configured as an OpenSLP DA.
(More information can be found at https://www.novell.com/documentation/edir873/index.html in the Novell eDirectory 8.7.3 Administration Guide under the section entitled Configuring OpenSLP for eDirectory.)
2. When the OpenSLP DA service is started it does not read eDirectory as with Novell's SLP product but rather starts with an empty cache. It therefore knows of no services starting out.
2. When the OpenSLP daemon comes up it broadcasts on the local subnet that it is available.
3. All SA's on that net that are configured to register with this DA do so.
From that moment on, unlike NetWare, the SLP client application is responsible for not only re-registering with its local SA and from there to the DA but also sets its slp lifetime.
4. The DA takes the registration information it receives and places it into its registration cache.
5. However, eDirectory has been hard coded to re-register its services to the DA every 10 minutes. This cannot be changed nor can its default lifespan of 3600 seconds.
Normally the re-registration of eDirectory services on a server takes place in under a second. As this occurs every 600 seconds there is minimal overhead in doing so.