1.8 Setting Up the Server as an SLP Directory Agent

For OES 2 services to work, the OES 2 server must have one of the following:

For the lab setup, you don’t actually need SLP services set up because each of the two lab servers (this server and the NetWare® VM) has an eDirectory replica. However, it’s important to understand the basics of setting up SLP on OES 2. For more information, see SLP in the OES 2 SP2: Planning and Implementation Guide.

  1. Log in to the server as root.

  2. Click Computer > Home Folder.

  3. In the left panel, double-click File System, then double-click the etc directory.

  4. Scroll down to the slp.conf file, right-click the file, and select Open with gedit.

  5. In slp.conf, find the following line:

    ;net.slp.useScopes = myScope1, myScope2, myScope3

  6. Remove the semicolon (;) and change the line as follows:

    net.slp.useScopes = Directory

  7. Find:

    ;net.slp.isDA = true

  8. Remove the semicolon (;) so that it reads:

    net.slp.isDA = true

  9. Save and close the file and the file browser.

  10. Configure the firewall on the DA server to allow SLP daemon traffic:

    1. Click Computer > YaST Administrator Settings, then click Security and Users > Firewall.

    2. In the left navigation frame, click Allowed Services.

    3. Click the Services to Allow drop-down list and select SLP Daemon.

    4. Click Add > Next.

    5. Click Accept.

  11. Click Computer > Gnome Terminal.

  12. At the command prompt, enter the following command to restart the SLP daemon with the changed configuration:

    rcslpd restart

  13. Restart eDirectory by entering the following command:

    rcndsd restart

    This registers eDirectory as an SLP service.

  14. After eDirectory restarts, enter the following command:

    slptool findsrvs service:ndap.novell

    After a moment or two, the system should respond with a line that indicates EXAMPLE_TREE is being advertised as a service in SLP.

  15. Close the terminal by entering the following command:

    exit

  16. Continue with Accessing iManager.