HP-UX Reference (11i v2 04/09) - 4 File Formats (vol 8)

s
slp.conf(4) slp.conf(4)
UA Configuration
The following sections of configuration properties are specified in RFC2614 and are supported for the
above categories.
DA configuration
The configuration properties for DAs are explained in this section.
net.slp.isDA
A boolean indicating if the SLP server is to act as a DA. If false, slpd runs as SA server. Default is
false.
net.slp.DAHeartBeat
A 32 bit integer giving the number of seconds for the DA heartbeat. The default is 3 hours (10800
seconds). This value is ignored if isDA is false.
net.slp.DAAttributes
A comma-separated list of parenthesized attribute/value list pairs that the DA must advertise in
DAAdverts. The property must be in the SLP attribute list wire format, including escapes for
reserved characters. This property is currently ignored.
Static Scope Configuration
These properties allow various aspects of scope handling to be configured.
net.slp.useScopes
A value-list of strings indicating the scopes that a UA or SA is allowed to use while making requests
or registrations, or the scopes that a DA must support. In the absence of a DA and SA or no scope
information is available from DHCP, the default scope "DEFAULT" is used. If this parameter is not
specified in the UA or no scope information is available from DHCP, then the user scoping model
will be used. The UA can give available information on all the scopes to be used through active or
passive DA or SA discovery. If this information cannot be discovered here, then the scope
"DEFAULT" is used. Unlike the other properties, this property is "read-only". Hence, any attempts
to change this setting after the configuration file has been read are ignored.
net.slp.DAAddresses
A value-list of IP addresses or DNS resolvable host names of SLPv2 DAs that has to be used by stat-
ically configured UAs and SAs for sending queries and registrations. This value-list is ignored by
DAs (unless the DA is also an SA server). Default is none. Unlike the other properties, this property
is "read-only". Hence, any attempts to change it after the configuration file has been read are
ignored.
The following grammar describes the property:
addr-list = addr / addr "," addr-list
addr = fqdn / hostnumber
fqdn = ALPHA / ALPHA *[ anum / "-" ] anum
anum = ALPHA / DIGIT
hostnumber = 1*3DIGIT 3("." 1*3DIGIT)
An example is:
sawah,mandi,sambal
IP addresses can be used instead of host names in networks where DNS is not deployed, but net-
work administrators are reminded that using IP addresses will complicate machine renumbering,
since the SLP configuration property files in statically configured networks will have to be changed.
Similarly, if host names are used, implementors must be careful that a name service is available
before SLP starts. In other words, SLP cannot be used to find the name service.
Tracing and Logging
This section describes tracing and logging information to be printed by the various agents.
net.slp.traceDATraffic
A boolean controlling printing of messages about traffic with DAs. Default is false.
net.slp.traceMsg
A boolean controlling printing of details on SLP messages. The fields in all incoming messages and
outgoing replies are printed. Default is false.
Section 4−−300 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: September 2004