SGI Techpubs Library

IRIX 6.2  »  Books  »  Administrative  »  
 Network License System Administration Guide
(document number: 007-2115-002 / published: 1993-09-07)    table of contents  |  additional info  |  download
find in page

Chapter 7. Global Location Broker and Network License Server Administration Tasks
Prev   Next

Chapter 7. Global Location Broker and Network License Server Administration Tasks

This chapter explains how to perform various administrative tasks on Global Location Brokers and Network License Servers. The first two sections describe tasks that should be done on a regular basis; the remainder should be done as needed. The sections are:

Backing Up Databases

GLB databases, Concurrent License databases, and the nodelock license file should be saved onto backup media periodically as part of regular backups. The files to back up are:

  • /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) on systems running node-locked applications

  • /var/ncs/* (/usr/etc/ncs/* on IRIX Release 5.0 and earlier) on all systems that are Global Location Brokers

  • /var/netls/* (/usr/netls/* on IRIX Release 5.0 and earlier) on all systems that are Network License Servers

If a GLB database is restored from a backup, it could have obsolete information that is inconsistent with other Global Location Brokers. “Routine Maintenance of Global Location Brokers” and “Cleaning GLB Databases” in this chapter describe some recommended restoration procedures.

Routine Maintenance of Global Location Brokers

Replicated Global Location Brokers require some maintenance to ensure consistency among the Global Location Brokers. Global Location Broker consistency problems are minimized if:

  • All Global Location Brokers are kept running and available.

  • The clocks on systems running Global Location Brokers are closely synchronized. Problems are likely to occur if clocks become skewed by more than a few minutes or if some Global Location Brokers are stopped (for example, due to hardware failure) or unavailable (for example, due to network failure) for several days. Running timed(1M) on each Global Location Broker enables these systems to synchronize their clocks automatically.

The procedure below should be done every week or so to perform routine maintenance on the Global Location Brokers even if there are no apparent discrepancies in the GLB databases. In the example output below, thomas, henry, and percy are example host names.

  1. Use drm_admin(1M) to check for clock skew:

    /usr/etc/drm_admin 
drm_admin: set -o glb -h ip:thomas
    Default object: glb  default host: ip:thomas  state: in service

    Checking clocks of glb replicas
    ip:thomas.island.sodor.com   1993/05/13.11:47        
    ip:henry.island.sodor.com    1993/05/13.15:13     *** clock skew warning ***
    ip:percy.island.sodor.com    1993/05/12.59:26     *** clock skewed ***
drm_admin:

    You can choose any Global Location Broker on the network when you give the set subcommand. If drm_admin finds that the clock of another Global Location Broker is more than two minutes different from the specified one, it prints one of these two messages:

    • *** clock skew warning ***

      This message indicates that the clock disagrees with the clock of the system named in the set subcommand by more than two minutes and less than 10 minutes. You can continue to run these Global Location Brokers (at increased risk of database inconsistencies), but you should reset a clock to eliminate the difference as soon as possible.

    • *** clock skewed ***

      This message indicates that a clock disagrees with the clock of the system specified in the set subcommand by more than 10 minutes. If the clocks at two systems are skewed by more than 10 minutes, the Global Location Brokers at those systems don't propagate updates to each other and do not perform drm_admin merge operations. You should reset the clocks immediately.

  2. Set clocks as necessary using the date(1) command.

  3. Use the merge_all subcommand of drm_admin to reconcile copies of the database:

    drm_admin: merge_all
    Merge from ip:henry.island.sodor.com done
    Merge from ip:percy.island.sodor.com done
    Merge to ip:henry.island.sodor.com done
    Merge to ip:percy.island.sodor.com done
    Merge_all successfully completed
drm_admin: quit

Verifying That llbd Is Running

To verify that llbd(1M) is running properly, give these commands on the system that is running llbd (shown with example output):

/usr/etc/lb_admin 
lb_admin: lookup 
------------
      object = glb/object
        type = glb/type
   interface = 33599c670000.0d.00.00.24.34.00.00.00
"rdrm" @ ip:edward.island.sodor.com[4350] 
------------
      object = glb/object
        type = glb/type
   interface = 3e188a057000.0d.00.00.be.8a.00.00.00
"rdrm_debug" @ ip:edward.island.sodor.com[4350] 
------------
      object = glb/object
        type = glb/type
   interface = 339a6e4fe000.0d.00.00.87.84.00.00.00
"rdrm_applic" @ ip:edward.island.sodor.com[4350] 
------------
      object = glb/object
        type = glb/type
   interface = glb/interface
"/usr/etc/glbd" @ ip:edward.island.sodor.com[4350] 
------------
lb_admin: quit 
bye.

If you get the message “No entries match”, then the llbd database is empty.

Checking Global Location Brokers

The procedure below explains first how to get the name of a Global Location Broker, if there is one, in the network. The remainder of the procedure explains how to get the names of other Global Location Brokers, if any, and verify that each Global Location Broker is running.

  1. Give the lb_admin(1M) command and two subcommands to determine if there is a Global Location Broker in the network, for example:

    /usr/etc/lb_admin 
lb_admin: use global
lb_admin: lookup

    Data from GLB replica: ip:thomas.island.sodor.com

------------
      object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00
        type = nls
   interface = nls
"NLS @ ip:gordon.island.sodor.com" @ ip:gordon.island.sodor.com[4467] global
------------
...

    This lookup subcommand was successful. The first line of output contains the name of a Global Location Broker. In this example, it is thomas.

    If the lookup subcommand can't find a Global Location Broker, you get this error message:

    ?(lb_admin) communications failure (network computing system/RPC runtime)
No entries match.

    lb_admin doesn't always succeed on the first try, so if you get this error message, try again:

    lb_admin: lookup

    If you receive an error message after you issue the lookup subcommand a second time, you can assume that there are no Global Location Brokers in the network.

  2. Exit lb_admin with this subcommand:

    lb_admin: quit
bye.

  3. To get the names of additional Global Location Brokers and to verify that all Global Location Brokers are running, give these commands:

    /usr/etc/drm_admin 
drm_admin: set -o glb -h ip:hostname
    Default object: glb default host: ip:thomas state: in service

    Checking clocks of glb replicas
    ip:thomas.island.sodor.com    1993/04/06.11:00        
    ip:gordon.island.sodor.com    1993/04/06.11:00        
drm_admin: quit

    hostname is the name of a Global Location Broker (probably the one from the first line of the output from the lb_admin lookup command; it is thomas in this example).

    The output lists the names of Global Location Brokers in the network. In this example, both of the Global Location Brokers, thomas and gordon, are running.

    When Global Location Brokers have been set up but aren't currently running, you see these messages:

    • If the Global Location Broker that is not running is the one you specified in the set subcommand, this is the error message:

          Default object: glb  default host: ip:thomas  status: not communicating communications failure (network computing system/RPC runtime)

    • If other Global Location Brokers aren't running, you see an error message like this:

          ip:james.island.sodor.com  *** clock unavailable ***

Checking Network License Servers

The lb_admin, ls_tv(1M), ls_stat(1M), and ls_admin(1M) commands provide information about Network License Servers in the network. Each command performs slightly different functions, which are explained in the next sections.

Checking Network License Servers Using ls_admin

ls_admin quickly and graphically lists Network License Servers but does not automatically verify that the Network License Servers are running. To use ls_admin, give this command as superuser:

/usr/etc/ls_admin

Network License Servers are listed in the Servers area. To check to see if a particular server is running, select it. Messages are printed in the scrolling area at the bottom. This message indicates that server bertie is running:

Consulting server
Connected to server: bertie.island.sodor.com

This message indicates that the Network License Server harold is not running:

Consulting server
?(ls_admin) communications failure (network computing system/RPC runtime)
Connected to server: harold.island.sodor.com

Checking Network License Servers Using lb_admin

lb_admin quickly lists Network License Servers (and the vendors on each Network License Server), but does not verify that the Network License Servers are running. To use lb_admin for this purpose, give these commands:

/usr/etc/lb_admin 
lb_admin: use global
lb_admin: lookup

    Data from GLB replica: ip:thomas.island.sodor.com

------------
      object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00
        type = nls
   interface = nls
"NLS @ ip:bertie.island.sodor.com" @ ip:bertie.island.sodor.com[4467] global
------------
      object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00
        type = 3bd624ea7000.0d.00.00.80.9c.00.00.00
   interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00
"NLS[2.0] @ ip:bertie.island.sodor.com" @ ip:bertie.island.sodor.com[4467] global
------------
      object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00
        type = 4ca0fd5cf000.0d.00.02.1a.9a.00.00.00
   interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00
"NLS[2.0]: Hewlett-Packard NetLS Test" @ ip:bertie.island.sodor.com[4467] global
------------
      object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00
        type = 5806f403b277.02.82.f8.d0.17.00.00.00
   interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00
"NLS[2.0]: Adobe Systems" @ ip:bertie.island.sodor.com[4467] global
------------
...
lb_admin: quit
bye.

Each block of lines between rows of dashes is for a vendor on a Network License Server. Look at the last line of each block to see the Network License Server name.

Checking Network License Servers Using ls_tv

ls_tv lists all Network License Servers and verifies that they are running (a dummy test product, Hewlett Packard NetLS Test, which is always installed by default, must be present on each Network License Server; see ls_tv(1M) for more information). This command can take some time as it communicates with each Network License Server. Give this command:

/usr/etc/ls_tv 
LS_TV Version 2.01 BL04 -- NetLS Test and Verification Tool
(c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved
Completed license transaction on node  690217e7 running NetLS  2.01 BL04
Active NetLS Servers:
    bertie.island.sodor.com (Irix) running NetLS 2.01 BL04
    harold.island.sodor.com (Irix) running NetLS 2.01 BL04
    donald.island.sodor.com (Irix) running NetLS 2.01 BL04
    douglas.island.sodor.com (Irix) running NetLS 2.01 BL04
    #192.82.171.202 (Irix) running NetLS 2.01 BL04
    trevor.island.sodor.com (Irix) running NetLS 2.01 BL04

See the ls_tv(1M) manual page for more information and explanations of the error messages displayed by ls_tv.

Checking Network License Servers Using ls_stat

ls_stat lists all running Network License Servers and their licenses. To run the graphical version of ls_stat, give this command:

/usr/etc/ls_stat

The Network License Servers are listed in the center area under the All Servers (Update) button when it first comes up. It can take a while for ls_stat to come up, because it is checking Network License Servers.

To use the command-line interface version of ls_stat, give this command:

/usr/etc/ls_stat -i 
LS_STAT Version 2.01 BL04
(c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved
Installed Licenses

Hewlett-Packard NetLS Test

 NetLS Test Product [1.0]

  On server: donald.island.sodor.com 
  Wait queue length: 0
              Licenses        Type  In Use  Start Date   Expiration Date
                 10000  concurrent       0  Jan  1 1970  Jan 20 2038
  Total active   10000                   0

  On server: douglas.island.sodor.com 
  Wait queue length: 0
              Licenses        Type  In Use  Start Date   Expiration Date
                 10000  concurrent       0  Jan  1 1970  Jan 20 2038
  Total active   10000                   0

  On server: trevor.island.sodor.com 
  Wait queue length: 0
              Licenses        Type  In Use  Start Date   Expiration Date
                 10000  concurrent       0  Jan  1 1970  Jan 20 2038
  Total active   10000                   0

  On server: harold.island.sodor.com 
  Wait queue length: 0
              Licenses        Type  In Use  Start Date   Expiration Date
                 10000  concurrent       0  Jan  1 1970  Jan 20 2038
  Total active   10000                   0

The “On server” lines list Network License Servers.

Stopping Daemons

To stop daemons on a Global Location Broker (glbd(1M) and llbd), give this command as superuser:

/etc/init.d/nck stop

To stop daemons on a Network License Server (netlsd(1M) and llbd), give these commands as superuser:

/etc/init.d/netls stop 
/etc/init.d/nck stop

Restarting Daemons

The following sections describe how to restart daemons. Choose the section that is appropriate for your situation. Remember that to operate correctly, daemons must be started in a particular order on a single system and in a particular order on a network (see “Required Software, Configuration Flags, and Daemons” in Chapter 1 for more information).

Restarting Daemons for a Global Location Broker

To restart the daemons (llbd and glbd) for a Global Location Broker, give these commands:

  1. Become superuser:

    /bin/su - 
Password:

  2. Set the glb and llb chkconfig(1M) flags to “on” in case they aren't set correctly:

    /etc/chkconfig glb on 
/etc/chkconfig llb on

  3. Start llbd and glbd:

    /etc/init.d/nck start

Restarting Daemons for a Network License Server

Follow these steps to restart the daemons for a Network License Server (llbd and netlsd):

  1. Become superuser:

    /bin/su - 
Password:

  2. Set the llb and netls chkconfig(1M) flags to “on” in case they aren't set correctly:

    /etc/chkconfig llb on 
/etc/chkconfig netls on

  3. If this system is not a Global Location Broker, set the glb chkconfig(1M) flag “off” in case it isn't set correctly:

    chkconfig glb off

  4. Start llbd:

    /etc/init.d/nck start

  5. Start netlsd:

    /etc/init.d/netls start

Restarting All Daemons on a Network

This procedure restarts all the daemons on a network in a way that ensures that they all “know about each other” and share the same GLB database.

  1. On each Global Location Broker, become superuser and remove its GLB database and Global Location Broker list. On IRIX 5.0.1 or later, give these commands:

    /bin/su - 
Password: 
rm /var/ncs/glb.*

    On IRIX 5.0 or earlier, give these commands:

    /bin/su - 
Password: 
rm /usr/etc/ncs/glb.*

  2. On one Global Location Broker, set the llb and glb chkconfig flags to “on” in case they aren't set correctly and restart the llbd and glbd daemons by giving these commands:

    /bin/su - 
Password: 
/etc/chkconfig glb on 
/etc/chkconfig llb on 
/etc/init.d/nck start

  3. On each of the remaining Global Location Brokers, set the chkconfig flags and restart the daemons by giving these commands:

    /bin/su - 
Password: 
/etc/chkconfig glb on 
/etc/chkconfig llb on 
/usr/etc/llbd 
/usr/etc/glbd -create -from ip:other_GLB_hostname &

    other_GLB_hostname is the host name of the Global Location Broker in step 2.

  4. On each Network License Server that is also a Global Location Broker, set the netls chkconfig flag and restart the netlsd daemon by giving these commands:

    /bin/su - 
Password: 
/etc/chkconfig netls on 
/etc/init.d/netls start

  5. On each Network License Server that is not a Global Location Broker, set the llb, glb, and netls chkconfig flags and restart the daemons (llbd and netlsd) by giving these commands:

    /bin/su - 
Password: 
chkconfig glb off 
chkconfig llb on 
chkconfig netls on 
/etc/init.d/nck start 
/etc/init.d/netls start

Creating a New License Group

To turn one or more Network License Servers and one or more Global Location Brokers into a license group, follow these steps:

  1. Become superuser on one of the Network License Servers or Global Location Brokers:

    /bin/su - 
Password:

  2. Start ls_admin to get a list of all Network License Servers:

    /usr/etc/ls_admin

  3. Write down the names of the Network License Servers that appear in the Servers area.

  4. Exit ls_admin.

  5. On each of the Network License Servers you wrote down in step 3, become superuser and stop the netlsd daemon:

    /bin/su - 
Password: 
killall netlsd

  6. On one of the Network License Servers or Global Location Brokers, get the names of all Global Location Brokers by giving these commands:

    /usr/etc/drm_admin 
drm_admin: set -o glb -h ip:hostname
    Default object: glb default host: ip:thomas state: in service

    Checking clocks of glb replicas
    ip:thomas.island.sodor.com    1993/04/06.11:00        
    ip:gordon.island.sodor.com    1993/04/06.11:00        
drm_admin: quit

    hostname is the name of any Global Location Broker you want to include in the license group. The names of the rest of the Global Location Brokers appear after Checking clocks ....

  7. On each of the Global Location Brokers in step 6, become superuser and stop the llbd and glbd daemons:

    /bin/su - 
Password: 
/etc/init.d/nck.stop

  8. On one of the Network License Servers or Global Location Brokers, create a glb_obj.txt file:

    /usr/etc/uuid_gen > /usr/tmp/glb_obj.txt

  9. On each system that is to be part of the license group and is running IRIX 5.0.1 or later, give these commands to create the directory /var/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step 8:

    /bin/su - 
Password: 
mkdir /var/ncs 
rcp guest@hostname:/usr/tmp/glb_obj.txt /var/ncs/glb_obj.txt

    hostname is the name of the system where you performed step 8.

  10. On each system that is to be part of the license group and is running IRIX 5.0 or earlier, give these commands to create the directory /usr/etc/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step 8:

    /bin/su - 
Password: 
mkdir /usr/etc/ncs 
rcp guest@hostname:/usr/tmp/glb_obj.txt \
/usr/etc/ncs/glb_obj.txt

    hostname is the name of the system where you performed step 8.

  11. Restart all of the daemons on all of the Network License Servers and Global Location Brokers on the network by following the procedure in “Restarting All Daemons on a Network” in this chapter.

Adding a System to a License Group

The following sections describe how to add a system to an existing license group. Use the section that is appropriate for the system you want to add.

System Is Not a Network License Server or a Global Location Broker

Copy the glb_obj.txt file from a system that is already in the license group when you want to add a system that is not a Network License Server or a Global Location Broker to a license group. Give these commands on the system that you want to add:

/bin/su - 
Password: 
mkdir todir 
rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt

hostname is the name of the system that you are getting glb_obj.txt from. If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.

System Is a Network License Server and a Global Location Broker

Follow these steps when you want to add a system that is already a Global Location Broker and a Network License Server to a license group:

  1. Stop the netlsd daemon on the system that you want to add:

    /bin/su - 
Password: 
/etc/init.d/netls stop

  2. Follow the instructions in “Using drm_admin delrep” in the chapter to delete the Global Location Broker from the system that you want to add to the license group.

  3. Copy the glb_obj.txt file from a Global Location Broker in the license group to the system you want to add:

    mkdir todir 
rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt

    hostname is the name of a Global Location Broker in the license group. (If you do not know which system is a Global Location Broker, see “Checking Global Location Brokers” in this chapter.) If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.

  4. On the system you want to add, restart the Network License Server and Global Location Broker by giving these commands:

    llbd 
glbd -create -from hostname 
/etc/init.d/netls start

    hostname is the name of the Global Location Broker from step 3.

System Is a Network License Server

To add a system that is a Network License Server to a license group, follow these steps:

  1. Become superuser on the system that you want to add:

    /bin/su - 
Password:

  2. Stop the netlsd daemon:

    /etc/init.d/netls stop

  3. Copy the glb_obj.txt file from a Global Location Broker in the license group to the system you want to add:

    mkdir todir 
rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt

    hostname is the name of a Global Location Broker in the license group. (If you do not know which system is a Global Location Broker, see “Checking Global Location Brokers” in this chapter.) If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.

  4. Restart the netlsd daemon:

    /etc/init.d/netls start

Reducing the Size of Network License Server Logs

You can use ls_rpt(1M) to reduce the size of the netlsd log file, /var/netls/log_file (/usr/netls/log_file on IRIX Release 5.0 and earlier). Give the command:

/usr/etc/ls_rpt -x yy/mm/dd

yy/mm/dd is a date. Log messages from this date or earlier are deleted.

Cleaning GLB Databases

Over time, GLB databases can accumulate entries for Network License Servers that no longer exist, possibly because of network reconfigurations or because they were set up only temporarily. You can use the lb_admin command to detect and delete these obsolete entries. It is a good idea to do this periodically or if license retrieval is slow.

On a system that is a Global Location Broker, give these commands:

/usr/etc/lb_admin 
lb_admin: clean 
lb_admin: use global 
lb_admin: clean

When lb_admin encounters an obsolete entry or an entry for a Network License Server that doesn't respond to an attempt to contact it, it asks you if you want to delete it. Enter y or yes to delete it and n or no to leave it in the database.

You should delete entries (Network License Servers) that you know are obsolete. In some cases, you may be prompted about a Network License Server that you know is not obsolete. This can happen because the Network License Server is not responding due to a network failure or because the Network License Server system is down temporarily. When you know the Network License Server is not obsolete, follow these steps:

  1. Respond to the lb_admin prompt with yes to delete the entry for this Network License Server.

  2. Stop the Network License Server daemons on the Network License Server by giving these commands on that system:

    /bin/su - 
Password: 
/etc/init.d/netls stop 
/etc/init.d/nck stop

  3. Restart the Network License Server daemons on the Network License Server by giving these commands on that system:

    /bin/su - 
Password: 
/etc/init.d/nck start 
/etc/init.d/netls start

    When the Network License Server daemons are restarted, the Network License Server reregisters itself with the Global Location Broker.

See the lb_admin(1M) manual page for additional information about how lb_admin determines obsolete entries and the possible responses when it finds an obsolete entry.

Using glb_site.txt Files

glb_site.txt files contain a list of the network addresses of systems that are Global Location Brokers. These files are useful when:

  • The usual broadcast mechanism can't be used to find Global Location Brokers.

  • You don't want to use the usual broadcast mechanism when Global Location Brokers attempt to communicate with each other, possibly because of the volume of network traffic this generates.

To create glb_site.txt files, follow this procedure on each system that will be running applications that request licenses:

  1. Become superuser:

    /bin/su - 
Password:

  2. If you are running IRIX Release 5.0.1 or later and the directory /var/ncs doesn't exist, create it:

    mkdir /var/ncs

  3. If you are running IRIX Release 5.0 or earlier and the directory /usr/etc/ncs doesn't exist, create it:

    mkdir /usr/etc/ncs

  4. Using a text editor, open a file called /var/ncs/glb_site.txt (/usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier).

  5. Make a list in the file of each Global Location Broker system that you want this system to communicate with. You can use either the network address or host name for each Global Location Broker system. Each address or name must be preceded with “ip:”, and IP addresses must be preceded with “#”. For example, to specify that Global Location Brokers are present on the system named toby and on the system with IP address 192.9.8.7, put these two lines into the file:

    ip:toby 
ip:#192.9.8.7

For more information on the glb_site.txt file, see the glb_site(4) manual page.

Deleting a Network License Server

If a system is a Network License Server and you don't want it to be a Network License Server anymore, you must stop the daemons, prevent them from being restarted automatically, and remove the Concurrent License database.

If you are running IRIX Release 5.0.1 or later, give these commands on the system with the Network License Server you want to remove:

/bin/su - 
Password: 
/etc/init.d/netls stop 
chkconfig netls off 
rm -f /var/netls/*db*

If you are running IRIX Release 5.0 or earlier, give these commands on the system with the Network License Server you want to remove:

/bin/su - 
Password: 
/etc/init.d/netls stop 
chkconfig netls off 
rm -f /usr/netls/*db*

Deleting a Global Location Broker

There are two different ways to delete Global Location Brokers. Normally, you use the drm_admin(1M) command and its delrep subcommand described in “Using drm_admin delrep” in this chapter. In extreme cases, when no other method works or when you require all Global Location Brokers to be deleted immediately, use the drm_admin reset command described in “Using drm_admin reset” in this chapter.

Using drm_admin delrep

The delrep subcommand of the drm_admin command can be used to delete Global Location Brokers. The delrep subcommand puts the deleted glbd into the “deleted state” in which it does not accept client updates or queries.

A Global Location Broker in the deleted state delivers all updates on its propagation queue to other Global Location Brokers. The Global Location Broker in the deleted state then delivers to the other Global Location Brokers a request to delete itself from their Global Location Broker lists. Finally, it deletes its own database and stops running. It can take a while for delrep to complete the deletion of a Global Location Broker.

Follow these steps to use delrep:

  1. Invoke drm_admin:

    /usr/etc/drm_admin
drm_admin:

  2. Specify a Global Location Broker that you are not planning to delete:

    drm_admin: set -o glb -h ip:hostname

  3. Give the delrep subcommand once for each Global Location Broker you want to delete: 

    drm_admin:  delrep ip:delhost1
drm_admin:  delrep ip:delhost2

    Although the drm_admin prompt is returned immediately, the deletion process may take a while.

  4. To verify that a deletion has finished, give the ps(1) command to see whether glbd is still running on the system from which it was deleted. If the deletion takes too long to finish, use the reset subcommand of drm_admin as described in the next section.

Using drm_admin reset

The reset procedure, which should be run only in extreme cases, uses the drm_admin reset command to delete Global Location Brokers. To delete most Global Location Brokers, use the delrep subcommand described in the previous section. The reset subcommand tells the Global Location Broker at the named system to delete its glbd, but does not propagate a request to delete the Global Location Broker from the Global Location Broker lists of other Global Location Brokers. Because it processes this way, you must run a successful merge_all subcommand before the reset subcommand and use the purgerep subcommand to delete the Global Location Broker from other systems' Global Location Broker lists after the reset.

The reset procedure is given below. It uses example systems with host names thomas, henry, percy, and james. percy and james have the Global Location Brokers to be deleted.

  1. Invoke drm_admin and set the default system to a system other than the one to be deleted:

    /usr/etc/drm_admin
drm_admin:  set -o glb -h ip:thomas
Default object: glb default host: ip:thomas state: in service
    Checking clocks of glb replicas
    ip:thomas.island.sodor.com     1993/04/09.17:09
    ip:henry.island.sodor.com      1993/04/09.17:09
    ip:percy.island.sodor.com      1993/04/09.17:10
    ip:james.island.sodor.com      1993/04/09.17:09

  2. Run the merge_all subcommand to ensure that all Global Location Brokers are in a consistent state before the reset subcommand: 

    drm_admin: merge_all
    Merge from ip:henry.island.sodor.com done
    Merge from ip:percy.island.sodor.com done
    Merge from ip:james.island.sodor.com done
    Merge to ip:henry.island.sodor.com done
    Merge to ip:percy.island.sodor.com done
    Merge to ip:james.island.sodor.com done
    Merge_all successfully completed

    If the merge_all does not process the Global Location Brokers to be deleted, you must run merge_all again after step 4. In the example above, the Global Location Brokers to be deleted were processed.

  3. Give the reset subcommand to delete the glbds:

    drm_admin: reset ip:percy
drm_admin: reset ip:james

  4. Run the purgerep subcommand to purge the Global Location Broker from the Global Location Broker lists:

    drm_admin: purgerep ip:percy
drm_admin: purgerep ip:james

  5. If the merge_all in step 2 did not process the Global Location Brokers to be deleted, run merge_all again now.

  6. To verify that a deletion has finished, give the ps command to see if glbd is still running on the system from which it was deleted:

    ps -e | grep glbd

Adjusting to Network Reconfigurations

Reconfigurations of a network can result in changes to its systems' network addresses. When a system is a Global Location Broker, you may have to perform some administrative adjustments. Among the reconfigurations that can change a system's network address are:

  • Moving a system from one network to another

  • Combining two networks to form a larger network

  • Connecting two networks to form a multi-segment network

  • Partitioning a network to form a multi-segment network or two separate networks

  • Changing a network number

If the network address of a Global Location Broker changes, glbd learns its new address automatically the next time it starts, and it propagates its change of address to all other Global Location Brokers. If only one system changes its address, no administrative work should be required. However, if more than one Global Location Broker changes its address, some Global Location Brokers may not be able to contact one another, and you have to edit their Global Location Broker lists manually, as described below.

The procedure below corrects the Global Location Broker lists at two Global Location Brokers, henry and percy, that have new network numbers. A third Global Location Broker, thomas, has not changed.

  1. At all Global Location Brokers whose network addresses have changed, ensure that a glbd has been started since the address change. Stop and restart daemons where necessary (see “Stopping Daemons” and “Restarting Daemons” in this chapter).

  2. Invoke drm_admin and set the default system to one of the changed sites:

    /usr/etc/drm_admin 
drm_admin: set -o glb -h ip:henry
    Default object: glb default host: ip:henry state: in service

    Checking clocks of glb replicas
    ip:henry.island.sodor.com     1993/04/06.11:00        
    ip:#192.26.52.9                *** clock unavailable ***
    ip:thomas.island.sodor.com    1993/04/06.11:00

    The Global Location Broker at henry knows its own new network address but knows only the old network address of percy and hence cannot communicate with the Global Location Broker there.

  3. Use the drm_admin chrep command to replace the network address for percy, then use the lrep -na subcommand to verify the change:

    drm_admin: chrep -from ip:192.26.52.9 -to ip:percy
drm_admin: lrep -na
    ip:henry.island.sodor.com      ip:#192.26.77.80
    ip:percy.island.sodor.com      ip:#192.26.77.3
    ip:thomas.island.sodor.com     ip:#192.26.77.17

  4. For each other Global Location Broker whose network address changed, set it to the default system, check its Global Location Broker list, replace obsolete network addresses in its Global Location Broker list, and confirm the change:

    drm_admin: set -o glb -h ip:percy
    Default object: glb default host: ip:percy state: in service
    ...
drm_admin: lrep -na
    ip:percy.island.sodor.com      ip:#192.26.77.3
    ip:#192.26.52.5                ip:#192.26.77.5
    ip:thomas.island.sodor.com     ip:#192.26.77.17
drm_admin: chrep -from ip:192.26.52.5 -to ip:henry
drm_admin: lrep -na
    ip:percy.island.sodor.com      ip:#192.26.77.3
    ip:henry.island.sodor.com      ip:#192.26.77.80
    ip:thomas.island.sodor.com     ip:#192.26.77.17

Prev Table of Contents Next
Chapter 6. License Administration Tasks  Chapter 8. Error Messages 

Network License System Administration Guide
(document number: 007-2115-002 / published: 1993-09-07)    table of contents  |  additional info  |  download

    Front Matter
    About This Guide
    Chapter 1. NetLS Concepts
    Chapter 2. The Licensing Process
    Chapter 3. Installing Node-locked Licenses
    Chapter 4. Setting Up Global Location Brokers and Network License Servers
    Chapter 5. Installing Concurrent Licenses
    Chapter 6. License Administration Tasks
    Chapter 7. Global Location Broker and Network License Server Administration Tasks
    Chapter 8. Error Messages
    Chapter 9. Troubleshooting
    Appendix A. NetLS Files
    Glossary
    Index


home/search | what's new | help