Novell Home

Service Location Protocol (SLP) Directory Agent (DA) Setup Instructions

Novell Cool Solutions: Feature

Digg This - Slashdot This

Updated: 15 Mar 2007
 

Contents:

  1. Setup Service Location Protocol Directory Agent (SLPDA)
  2. Verify SLP is active on server
  3. Verify SLP Services are Registering
  4. Configure Workstation SLP settings

1. Setup Service Location Protocol Directory Agent (SLPDA)

Three objects in Novell Directory Service (NDS) are required to configure SLP DA. They are the DA object, the SLP Scope Unit object, and the SLP Scope Unit container object. Novell uses two methods to setup SLPDA; however, because the manual method creates a "Scoped" scope object these instructions cover the manual process.

  1. Unload SLPDA.
    Unload SLPDA on all servers in your environment. Also, make sure that only the DA server(s) has a line in the AUTOEXEC.NCF file that loads SLPDA.NLM. Remove this line from all other servers.

  2. Start "NWAdmin".
    From an Admin equivalent account, open the NW Administrator program.

    Double-clicking on the NWAdmin icon (Figure 1) in the on your desktop.


    Figure 1


    This opens the NWAdmin program (Figure 2).



    Figure 2


  3. Delete SLP Objects.
    Search the directory tree for "SLP Directory Agent" and "SLP Scope Unit." Objects.

    1. Delete SLP Scope Unit Contents.
      Delete the contents of the scope units before deleting the units themselves. If these objects can't be deleted, verify that SLPDA.NLM is not running on any server servicing that scope unit and try again. If they still cannot be deleted, use ConsoleOne instead of NWAdmin for this step.


    2. Delete SLP Objects.
      Delete any that should not exist. This would include the Scope Unit object, the SLPDA object, and the SLP OU (Figure 3). This will clear out any previous attempts at setting up directory agents.


    3. Figure 3


    4. Check Server SLPDA Setting.
      You can verify that all SLPDA settings have been cleared on the servers in you environment by opening the Server Details page and clicking on the "SLP Directory Agent" button (Figure 4). This will show whether the server still has a SLPDA object assigned. If it does, find and delete the SLPDA object and recheck the server.


    5. Figure 4


  4. Create SLP Scope Organizational Unit Container.
    Select the appropriate location for the SLP Scope Unit. Normally, this should be in the same location as the server that will be hosting the "Master SLPDA" (i.e., the first SLPDA to be created).

    • From the NW Administrator window, click on the "New Object" button (Figure 5) to open the "New Object" dialog box (Figure 6).


    Figure 5

    Figure 6

    • Select the "Organizational Unit" (OU) object form the "Class" list and click on the OK button to open the "New Organizational Unit" dialog (Figure 7).


    Figure 7

    Figure 8

    • Enter the name of the new OU and click the Create button. This creates a new OU in the location selected (e.g., SLPHQ - Figure 8).

  5. Create SLP Scope Unit Object.
    The SLP Scope Unit is an NDS container that collects registered "SLP Service" entries. The SLP Scope Unit may also hold an NDS attribute "SLP Scope Name". The SLP Scope Name has no NDS context information associated with it and is only of relevance to SLP SAs and SLP DAs.

    • Select the new Scope Unit container and click on the "Create New Object" button (Figure 5) to open the "New Object" dialog box (Figure 9).



    Figure 9


    • Select the "SLP Scope Unit" object form the "Class of new object:" list and click on the OK button to open the "Create SLP Scope Unit" dialog (Figure 10). Enter the name of the Scope Unit and click the Create button to create the Scope Unit (Figure 11). (Recommendation: Use the name of the server hosting the SLPDA.) No further setup is required on the Scope Unit.


    Figure 10

    Figure 11

    NOTE: Once the whole process has been completed the Scope Unit will display configuration information (Figure 12) about the SLP.


    Figure 12


  6. Create and Configure SLP Directory Agent Object.
  7. The SLPDA object holds the SLP parameters and lists any SLP Scope Units that are defined as being serviced by the SLP DA in an NDS attribute "SLP Scope Unit DN".

    (NOTE: For fault tolerance you can setup more than one SLPDA server. Just use this section to create the additional SLPDA server object.)

    • Select the Scope Unit container and click on the "Create New Object" button (Figure 5) to open the "New Object" dialog box (Figure 13).


    Figure 13

    • Select the "SLP Directory Agent" object form the "Class of new object:" list and click on the OK button to open the "Create SLP Directory Agent" dialog (Figure 14).


    Figure 14

    Figure 15

    • Enter the name of the SLPDA and click the Create button to create the SLPDA object (Figure 15). (Recommendation: Use the name of the server hosting the SLPDA.)


    • Double-Click on the SLPDA object to set its configuration. While on the Configuration page, click on the browser button (Figure 16). This opens a "Select Object" dialog box (Figure 17).


    Figure 16

    Figure 17

    • Search for and select the appropriate sever that will run the SLPDA service.


    • Click the OK button to set the SLPDA server (Figure 18).


    Figure 18


    • Click on the "SLP Scope Unit" button to display the SLP Scope Units page (Figure 19).


    Figure 19


    • Click on the Add button to open the "Select Object" dialog box (Figure 20). Search for and select the appropriate Scope Unit that will service this SLPDA. (In general, there will only be one Scope Unit for the Tree.)


    Figure 20


    • Click the OK button save the selection. The "Serviced scope unit:" will now be displayed (Figure 21).


    Figure 21


  8. Configure DA Server's SLP.CFG File.
    You now need to edit the "SYS:\ETC\SLP.CFG" file on all of the servers. The DA server?s file should be changed as shown below. The blue highlighted section was added to the original file for obvious reasons. However, if there are multiple SLPDA server, you should add a reference on each "DA" server to the other DA servers.
  9. ******************************************************************************
    ;  This is a sample of the slp configuration file.
    ;  Two types of entries can be made: 1) DA entries, 2) SA Register Filters.
    ;
    ;  The DA entry allows static configuration of a known DA.  This would be used
    ;  when the DA was out of multicast range and DHCP was not being used to 
    ;  configure the DA.
    ;  The static DA configuration format is as follows 'DA <addr type>, <addr>'.
    ;  The first word must be "DA".  The addr type is the address type.  Currently, only
    ;  IPV4 has been defined.  IPV6 will be defined in the future.  The addr is 
    ;  the address specified.  
    ;
    ;  The following is an example of a static DA.
    ;  This is the SLP file for ServerName
    ;  Per Novell TID 10059981 - On the DA server, make sure that there is nothing 
    ;  in this file besides comments (A DA NEVER POINTS TO ITSELF, NEVER.)
    ;  However, if you have configured more than one SLPDA server, you can enter
    ;  the IP address of that server here.
    ;  DA IPV4, XXX.XXX.XXX.XX1
    DA IPV4, XXX.XXX.XXX.XX2
    ;  The SA Register Filter would be used when the administrator wanted all services
    ;  of a specific service type being mapped to a single scope.  For example, 
    ;  the administrator wanted all "lpr" printers being registered to scope "printer".
    ;  The format is as follows: 'REGISTER TYPE "<type name>" to SCOPE "<scope name>"'.
    ;  The parser will look for REGISTER, TYPE, and SCOPE as keywords followed by quote on
    ;  a single line.  Example:
    ;
    ;  REGISTER TYPE "lpr" to SCOPE "eng"
    ;
    ;  The last line must contain a line feed and char return.  A semi-colon specifies a 
    ;  comment.
    ******************************************************************************
  10. Configure Other Server's SLP.CFG File.
    The other server?s file should be changed as shown below [where "XX.XX.XX.XX" is the IP address of the DA server(s)]. If you are using multiple "DA" servers, you should add a line for each DA server. Make sure that there are no other lines in this file except for the comments. It might be convenient to edit this file on one server and then copy it to the others.
  11. ******************************************************************************
    ;  This is a sample of the slp configuration file.
    
    ;  Two types of entries can be made: 1) DA entries, 2) SA Register Filters.
    ;
    ;  The DA entry allows static configuration of a known DA.  This would be used
    ;  when the DA was out of multicast range and DHCP was not being used to 
    ;  configure the DA.
    ;  The static DA configuration format is as follows 'DA <addr type>, <addr>'.
    ;  The first word must be "DA".  The addr type is the address type.  Currently, only
    ;  IPV4 has been defined.  IPV6 will be defined in the future.  The addr is 
    ;  the address specified.  
    ;
    ;  The following is an example of a static DA.
    ;  Per Novell TID 10059981 - On the DA server, make sure that there is nothing 
    ;  in this file besides comments (A DA NEVER POINTS TO ITSELF, NEVER.)
    ;  However, if you have configured more than one SLPDA server, you can enter
    ;  the IP address of that server here.
    DA IPV4, XXX.XXX.XXX.XX1
    DA IPV4, XXX.XXX.XXX.XX2
    ;
    ;  The SA Register Filter would be used when the administrator wanted all services
    ;  of a specific service type being mapped to a single scope.  For example, 
    ;  the administrator wanted all "lpr" printers being registered to scope "printer".
    ;  The format is as follows: 'REGISTER TYPE "<type name>" to SCOPE "<scope name>"'.
    ;  The parser will look for REGISTER, TYPE, and SCOPE as keywords followed by quote on
    ;  a single line.  Example:
    ;
    ;  REGISTER TYPE "lpr" to SCOPE "eng"
    ;
    ;  The last line must contain a line feed and char return.  A semi-colon specifies a 
    ;  comment.
    ******************************************************************************
  12. Edit all Server's Service Location Protocol Setting.
    You must now configure all the servers "Service Location Protocol" settings. (NOTE: When entering the scope name use only the common name and not the fully qualified domain name (FQDN). For example if the scope is named FRED then just type FRED in the scope list.) To do this,
    1. Load the MONITOR.NLM on the server.
    2. Enter the "Server Parameters – Service Location Protocol" submenu.
    3. Enter the scope name in the "SLP Scope List" field (Figure 22).


    Figure 22


    This table shows the Setting Name and Setting of SLP configurable settings. Each of the settings should be reviewed for your environment and needs.

    SettingName Setting SettingName Setting
    SLP Agent IP Address FIRST SLP Maximum WTD Queue 15000
    SLP API Handicap 50 SLP MCA Timeout 16
    SLP Broadcast OFF SLP MTU Size 1450
    SLP Cache Timeout 1800 SLP Multicast Radius 255
    SLP Close Idle TCP Connections Time 300 SLP nwserver NLM names ON
    SLP DA Discovery Options 4 SLP Rediscover Inactive Directory Agents 60
    SLP DA Event Timeout 15 SLP Register nwserver ON
    SLP DA Heart Beat Time 10800 SLP Reset OFF
    SLP Debug 0 SLP Retry Count 3
    SLP Enable UA Multicast ON SLP SA Default Lifetime 3600
    SLP Exclude IP Addresses NONE SLP Scope List MEDBD06_SCOPE_UNIT
    SLP Include IP Addresses ALL SLP Static Scope List ON
    SLP Maximum Memory Percent 15 SLP TCP ON
    SLP Maximum WTD 32 SLP Version Mode 0

    The SLP SCOPE LIST change requires restarting the server before it will take effect. If the server can't be restarted right away then don't load MONITOR.NLM again until the restart or the change may be lost. If this step is not completed for every server in the tree the servers will not register their IP services with the DA and they will not communicate properly over IP with one another. Also, clients will have problems getting services from any server not registered with the DA using the proper scope. If your SCOPE name was already set in Monitor, you MAY not have to reboot the server, but if this particular server's services do not register to the DA, then that means that the scope name is NOT in memory, and you HAVE to reboot.

2. Verify SLP is active on server

To verify that SLP is working, type "DISPLAY SLPDA" at the consoles of any server. A line that starts with "XX.XX.XX.XX : ACTIVE :" (where XX.XX.XX.XX is the IP address of the DA server) followed by the scope name should be displayed.


Figure 23


3. Verify SLP Services are Registering

To verify/view all the services registered by the SLPDA server, type "DISPLAY SLP SERVICES" at any server console. Various addresses for every configured NetWare server should be displayed. This will show which servers are registering with the DA. If all the servers show up then the servers are all communicating via SLP.

4. Configure Workstation SLP settings

Configure all workstations, either manually (Novell client properties on the "Service Location" tab) or using NetWare DHCP (option 78), with the IP address of the DA (NOTE: Option 79 is SLP Scope List, this parameter does NOT need to be configured on your workstations, SCOPES are for registering services, your client has no services to register, a BLANK or NULL scope list will allow your client to see ALL services with any DAs that it contacts).

  • If setting the SLPDA address through DHCP, set 'mandatory' if the desired effect is to have DHCP override any local settings. Unload DHCPSRVR and load it again for the DHCP Server to hand out this information.


  • For manual configuration, right click on the N in the system tray and select "Novell Client Properties". Click on the "Service Location" tab. Enter the name of your "Scope Name" in the "Scope List" field, check the Static option and click Add. Enter the IP address of your "Directory Agent" server in the "Directory Agent List" field, check the static option, and click Add.

The workstations may not be able to communicate with the servers without restarting.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell