Managing Service Location Protocol Services in Oracle^® Solaris 11.3

How to Configure the Random-Wait Bound

Use the following procedure to change the net.slp.RandomWaitBound property in the slp.conf file.

1. Become an administrator.

   For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

2. Stop slpd and all SLP activity on the host.

   # svcadm disable network/slp

3. Back up the default /etc/inet/slp.conf file before you change the configuration settings.
4. Change the net.slp.RandomWaitBound property in the slpd.conf file:

   net.slp.RandomWaitBound=value

   value

   The upper bound for calculating the random-wait time before attempting to contact a DA

   Default Value=1000 milliseconds (1 second)

   Range of Values=1000 to 3000 milliseconds

   For example, you can lengthen the maximum wait to 2000 milliseconds (2 seconds).

   net.slp.randomWaitBound=2000

   When you lengthen the random-wait bound, a longer delay in registration occurs. SAs can complete registrations with newly discovered DAs more slowly to avoid collisions and timeouts.

5. If necessary, change the net.slp.datagramTimeouts property in the slpd.conf file:

   net.slp.datgramTimeouts=value

   value

   A list of 32–bit integers that specify timeouts, in milliseconds, to implement unicast datagram transmission to DAs

   Default=3000,3000,3000

   For example, you can increase the datagram timeout to 20000 milliseconds to avoid frequent timeouts.

   net.slp.datagramTimeouts=2000,5000,6000,7000

   In high-performance networks, you can reduce the time-out bound for multicast and unicast UDP datagram transmission. This setting reduces the amount of latency in satisfying SLP requests.

6. Save your changes and close the file.
7. Restart slpd to activate your changes.

   # svcadm enable network/slp