SLP Directory Agent always deactivates and activates.

  • 3157466
  • 13-Jan-2007
  • 27-Apr-2012

Environment

SLPDA

Situation

SLP Directory Agent always deactivates and activates.
ERROR: "SLP directory agent x.x.x.x de-activated"

Resolution

There are several reasons why the DA may appear to be deactivated and then reactivated on another servers console.

One popular reason is that SLP uses UDP and if a UDP packet is dropped it will not be responded to causing the error. The next time the UDP query is sent if it gets a response the DA will show as active again.

Another reason might be that the DA configuration will only allow it to respond to SLP v1 queries. If the server that sees the deactivate / re-activate messages sends a v2 query first followed by a v1 query, it will not get a response to the v2 query causing the deactivate message then when it sends the v1 query and gets a response the DA will then be activated.

In the early days of SLP, version 1 would only respond from the primary interface. If the server running the SLPDA.NLM had more than one IP address bound (Multiple NIC's or Secondary IP addresses on a single NIC) and a request came in on an IP addresses other than the servers primary IP address (first one bound) then the ERROR: "SLP directory agent x.x.x.x de-activated" message would occur. This was resolved in SLP Version 2.

NetWare 6.0 and later servers by default will respond to both version 1 and version 2 queries. They may also be configured to only respond to v1 or v2.

Additional Information


Formerly known as TID# 10061336

Feedback service temporarily unavailable. For content questions or problems, please contact Support.