Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Руководство по внедрению, Страница: 117 / 288

Network Services 117
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
For all other 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 117
Š
“Configuring for DA Access Before or After Installing the OES 2 Server” on page 117
Configuring for DA Access During the OES 2 Installation
As you install OES 2 by using the instructions in the “ Novell eDirectory Services ” section of the
OES 2 SP2: Installation 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 the scope you defined in Step 4 on
page 116 . You can also list additional scopes, separated by commas (no spaces).
For example, you might type
Directory
in the field if that is the scope name you assigned to
the DA you created.
3 In the Configured SLP Directory Agent field, type the IP address of the DA server you defined
in “Setting Up an OpenSLP DA Server” on page 115 . You can also list additional DA
addresses, separated by commas.
4 Return to the “ Novell eDirectory Services ” instructions in the OES 2 SP2: Installation Guide .
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
/etc/slp.conf
in a text editor.
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 scopes given in the example for some reason, remove the spaces between the
entries.
3
Modify the line by removing the semicolon and typing the name or names of the scopes you
want this server to have access to. Be sure to include the scope you defined in
Step 4 on
page 116 .
For example, you might change the line as follows:
net.slp.useScopes = Directory