Novell is now a part of Micro Focus

Working with Scopes in SLP

Articles and Tips: qna

01 Jan 2001


Q.

Dear Ab-end: I'm having trouble getting SLP (Service Location Protocol) to work within a scope. When I used UNSCOPED_SCOPE, everything works great. I can log in to the tree and I can also see the servers and NDS trees in the Network Neighborhood.

But when I use a specific scope, such as SERVERS, I can still log in to the server/tree, but I can't see anything. I can't find any information in the Network Neighborhood either. I'm running NetWare 5 with Support Pack 5. The SLPDA (SLP Directory Agent) that services the scopes is one router hop away. The routers are configured with multi-casting disabled. So, now what do I do?

No Scope, No Hope in Phoenix

A.

Dear No Scope: Just as the Phoenix arose alive, you do have hope. Follow this general list to ensure that everything is configured correctly to run SLP with no multi-casting:

Make sure all servers with the scope have the "SLP Scope List" defined to match the named scope.

Make sure the client has the IP addresses of the DAs and has the scope list defined. You may want "Static" checked on these options so it will not discover via multicast any local SLP resources if the listed services are not available.

Make sure the servers that are not DAs have the SYS:ETC\SLP.CFG configured for the DAs to register the services.

These other client and server parameters disable responses to multicasts and otherwise "optimize" SLP communications in an non-multicasted environment:

SLP Multicast Radius (0 on server, 1 on client)
SLP Active Discovery (off)
SLP Enable UA Multicast (off)
SLP DA Discovery Options (4 if SLP.CFG is configured)

Obviously, these settings decrease the fault tolerance "failover" for SLP, but with proper design and planning, you can negate these risks. (Answer supplied by Sterling Smith of Novell)

* 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.

© Copyright Micro Focus or one of its affiliates