Configuring SLP Revisited
Articles and Tips: qna
01 Apr 2003
Q.
I noticed, in the January 2003 AppNotes, Net Management Tips & Tricks section, regarding SLP configuration.The dual Directory Agent (DA) configuration is the very similar to the SLP design that I have pieced together for my network. There is one notable problem with this design which was omitted in the article. This is object collision. For example, you could have two DAs registering objects into the same named scope. This eventually becomes a stuck obituary problem. Would it be possible to set up a redundant SLP design without the object collisions?
Stan the Stuck
A.
Dear Stan: Jeff Fischer on our AppNotes Team offers the following tip: "Probably the quickest and maybe the most efficient solution to this is to make one of the replicas on one of the DA servers a read-only replica instead of a read/write. This way, you only have one server that is writing to the Directory and thus avoiding object collisions.This essentially creates a "primary" DA server and a "secondary" server that will provide SLP services on the network, which is probably all that is needed, but only one server that writes to the Directory.
Secondly, have the "backup" DA server configured, but not loaded. SLPDA is not loaded on that server so you only have one DA on the network that is writing to the Directory. If the "primary" DA server goes down, you load SLPDA on the "backup" DA server and you still have SLP services on the network. You lose the automatic fail-over for SLP services with this method because you have to manually load the DA when the primary DA goes down, but you avoid object collisions.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.