Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual page 118

Configuring OES 2 Servers to Access the Novell SLP DA
For each of the OES 2 servers installed in your eDirectory tree, you should complete one of the
following procedures as it applies to your situation:

"Configuring for DA Access During the OES 2 Installation" on page 118

"Configuring for DA Access Before or After Installing the OES 2 Server" on page 118
Configuring for DA Access During the OES 2 Installation
As you install OES 2, in the
Guide, do the following:
1 When you reach the SLP section of the installation, select Configure SLP to Use an Existing
Directory Agent.
The first option, Do not configure SLP, causes problems with eDirectory and other services if
this is the fourth or later server installed in the tree. The second option, Use Multicast, requires
that you disable the firewall on the server. Disabling the firewall is always discouraged.
2 In the Service Location Protocol Scopes field, specify one or more appropriate scopes that are
defined on your network.
If you aren't sure about the exact scope names, you can view the SLP configuration of a
NetWare server on the same network segment. Log into Novell Remote Manager on the server
and click Manage Applications > SLP.
You can list multiple scopes, separated by commas (no spaces).
For example, you might type
3 In the Configured SLP Directory Agent field, type the IP address of an appropriate DA server.
You can use Novell Remote Manager on a NetWare server if you aren't sure which address to
use.
You can also list additional DA addresses, separated by commas.
4 Return to the
Configuring for DA Access Before or After Installing the OES 2 Server
Whether you configure DA access before installing OES 2 on a SLES 10 server or after a
simultaneous install of SLES 10 and OES 2, the manual DA configuration process is the same.
1 Open
2 Find the following line:
;net.slp.useScopes = myScope1, myScope2, myScope3
IMPORTANT: The example in the configuration file is misleading because the spaces after
each comma are not ignored as one might expect them to be.
Therefore, the scope names created or configured by the statement after the first comma
actually have leading spaces in them. For example, the first scope name is "myScope1" but the
scope names that follow it all have leading spaces, " myScope2", " myScope3" and so on. This
is a problem, especially if one of the later names becomes the first name in a subsequent SLP
configuration and the leading space is ignored.
If you use the scope names given in the example, remove the spaces between the entries.
118 OES 2 SP3: Planning and Implementation Guide
"Novell eDirectory
Directory
"Novell eDirectory
in a text editor.
/etc/slp.conf
Services" section of the
in the field.
Services" instructions in the
OES 2 SP3: Installation
OES 2 SP3: Installation Guide.