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

Planning and implementation guide
Hide thumbs Also See for OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010:
Table of Contents

Advertisement

IMPORTANT: If you need to set up OpenSLP for the reasons above, it is most convenient if you do
it before you install the fourth server in your tree or partition. That way you can point to the SLP
service during the installation. Setting up SLP services on every OES 2 server is recommended.
Setting Up an OpenSLP DA Server
If you need OpenSLP and you don't already have an OpenSLP Directory Agent (DA) set up on your
network, for simplicity's sake we recommend that you set up the first OES 2 server in your tree as
an OpenSLP DA. Although SLP services can be managed without having a Directory Agent, that
approach is far less robust, requires multicasting, and involves disabling the firewall.
After creating the DA, you can then configure all subsequently installed servers to either point to
that DA or to other DAs you create later.
1 On the OES 2 server that will become the DA, open the
2 In
slp.conf
;net.slp.isDA = true
so that it reads
net.slp.isDA = true
3 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, remove the spaces between the entries.
4 Modify the line by removing the semicolon and typing the name of the scope you want this DA
to use to provide service information on the network. For example, you might change the line
as follows:
net.slp.useScopes = Directory
IMPORTANT: Although SLP provides a default scope if no scope is specified, it is always
good practice to define one or more scopes by configuring the net.slp.useScopes parameter in
slp.conf
Scopes group and organize the services on your network into logical categories. For example,
the services that the Accounting group needs might be grouped into an Accounting scope.
More information about scope planning is available in
8.8 Administration Guide
When no scope is specified, all services are registered in a scope named Default.
5 Configure the firewall on the DA server to allow SLP daemon traffic:
5a In the YaST Control Center, click Security and Users > Firewall.
114 OES 2 SP3: Planning and Implementation Guide
, remove the semicolon [;]) from the beginning of the following line:
.
and on the
/etc/slp.conf
"SLP Scopes
OpenSLP Web site
(http://www.openslp.org/).
file in a text editor.
" in the
Novell eDirectory

Advertisement

Table of Contents
loading

This manual is also suitable for:

Open enterprise server 2 sp3

Table of Contents