|
|
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 6. License Administration TasksThis chapter explains how to perform various license administration tasks for both node-locked licenses and concurrent licenses. The tasks covered are:
Verifying That a License Was Installed ProperlyTo verify that a license was installed properly, try using one of the product's applications that is license protected. The release notes for each product list the licensed applications.
If the application works, the license is installed and accessible. If you get a message that no license can be found, see “License or Server Not Found” in Chapter 8.
Deleting a Node-locked LicenseTo delete a node-locked license, simply remove the line containing the license and any comments that go with it from the /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) file. Instead of deleting the license line, you can leave the license in the file as a comment by putting a # (comment character) at the beginning of the license line.
If you do not know which license line in the file is the one you need to delete because there are no comments, see “Identifying Licenses in a Nodelock File” in Chapter 6.
On IRIX 5.0.1 or later, do not delete the file /var/netls/nodelock even if you have deleted the last license in the file, because there is a symbolic link from /usr/netls/nodelock to this file. Breaking this link may prevent applications from running properly in the future.
Deleting a Concurrent LicenseTo delete a concurrent license, follow one of the procedures below. The first procedure can be used on a graphics terminal only; the second procedure doesn't require graphics.
Remember that when you delete a concurrent license, the software product is no longer available to users. Deleting a license cannot be undone; you must reinstall the license.
Follow these steps to use the graphical version of ls_admin(1M) to delete a concurrent license:
Become superuser:
Give this command to start ls_admin:
A window border appears. After you position the window border and click the left mouse button, the ls_admin window appears.
Select the system where you installed the temporary license from the list in the Servers area.
Click the Vendor button. The Servers area becomes the Vendors area with a list of vendors.
Select the vendor of the product.
Click the Product button. The Vendors area becomes the Products area and a list of products appears.
Select the product whose license you want to delete from the list of products.
Click the License button. The Products area becomes a Licenses area and a list of one or more licenses appears.
Select the license you want to delete from the list of licenses.
Click the Delete... button. A dialog box appears requesting confirmation.
Click the Delete button in the dialog box.
Follow this procedure to delete a concurrent license using the ls_admin command-line interface.
Become superuser:
Get the timestamp of the license you want to delete:
ls_admin -s -p v_name
LS_ADMIN Version 2.01 BL04
(c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved
Server: ip:clarabelle.island.sodor.com
socket address family ip
socket address 192.132.142.4
socket port 1457
target type Irix
target id 69068635
Vendor: Silicon Graphics
vendor id 546fb4684914.02.c0.1a.3d.52.00.00.00
Product: CASEVision/Workshop [2.0]
id 1
Licenses:
1 Concurrent Access from 1993/05/21 to 1994/05/21, timestamp 737998264
|
v_name is the vendor name of the product. Be sure to surround it with double quotes if it contains spaces. Identify the license you want to delete and look for its timestamp. The timestamp for CASEVision/Workshop in this example is 737998264.
Give this command to delete the license:
ls_admin -d -p v_name p_name timestamp
LS_ADMIN Version 2.01 BL04
(c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved
|
v_name is the vendor name, p_name is the product name (double-quoted if it contains spaces), and timestamp is the timestamp from step 2.
To confirm that the license has been deleted, give this command:
ls_admin -s -p v_name
LS_ADMIN Version 2.01 BL04
(c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved
Server: ip:pele.wpd.sgi.com
socket address family ip
socket address 192.132.142.4
socket port 1457
target type Irix
target id 69068635
Vendor: Silicon Graphics
vendor id 546fb4684914.02.c0.1a.3d.52.00.00.00
|
The CASEVision/Workshop license has been deleted because it is no longer listed.
A Network License Server user file, /var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier), can be used to prohibit some users from using certain products or give different users of a product different access priorities. If you want all users to have access to all products with the same priority, you don't need a user file. User files are used for products licensed with concurrent licenses only.
Example 6-1 shows a sample user file. In this example, the keywords are uppercase; they may be uppercase or lowercase, but mixed-case keywords are not allowed. Comments are preceded by a percent sign (%).
Example 6-1. Sample User File
% NetLS User File for Shining Clock Shop, Inc.
CRAWL 10
% **********************************************
VENDOR "Silicon Graphics" CASEVision/Workshop
ALLOW tanya -p 2 harry -p 1 stacy -p 1 matt
% **********************************************
VENDOR "Mr. Conductor, Inc." ALL
DISALLOW ringo george
% **********************************************
VENDOR "Silicon Graphics" CASEVision/Tracker
DISALLOW schemer
VENDOR "Silicon Graphics" "IRIS Volume Manager"
DISALLOW schemer
VENDOR "Silicon Graphics" "IRIS Networker"
DISALLOW schemer
|
The meanings of the lines in the file in Example 6-1 are explained below.
This causes all users listed in the file to move up one level in priority after the product polls the queues of users waiting for licenses a specified number of times (in this case, 10 times). Using CRAWL makes sense only when different users have different priorities. The CRAWL keyword and user priorities apply only to products that use wait queues.
VENDOR "Silicon Graphics" CASEVision/Workshop
ALLOW tanya -p 2 harry -p 1 stacy -p 1 matt
|
Here, the user file declares the vendor Silicon Graphics and its only installed product, CASEVision/Workshop. The vendor name contains spaces, so it is delimited by double quotes. The product name is not quoted because it contains no spaces. Four users may use CASEVision/Workshop: Tanya is a priority 2 user; Harry and Stacy are priority 1 users (the highest), and Matt's unspecified priority defaults to priority 3 (the lowest).
When a high-priority user requests a license for which low-priority users are already waiting, the high-priority user moves ahead of the lower-priority users in the queue. In this case, if Matt and Tanya are unsuccessful in obtaining a license and are willing to wait, CRAWL eventually changes their priority to 1. At that time, the declared priority 1 users (Harry and Stacy) can no longer displace Matt and Tanya in the user queue.
VENDOR "Mr. Conductor, Inc." ALL
DISALLOW ringo george
|
The keyword ALL means that all licensed products of this vendor (whatever those products may be) have the same user authorizations. In this case, everyone except Ringo and George may use all Mr. Conductor software products.
VENDOR "Silicon Graphics" CASEVision/Tracker
DISALLOW schemer
VENDOR "Silicon Graphics" "IRIS Volume Manager"
DISALLOW schemer
VENDOR "Silicon Graphics" "IRIS Networker"
DISALLOW schemer
|
These lines specify three products of Silicon Graphics: CASEVision/Tracker, IRIS Volume Manager™, and IRIS Networker™. There is one VENDOR line for each product. The keyword DISALLOW excludes only Schemer from using the three products of Silicon Graphics. All other users are priority 3 by default.
Since this user file specifies the products of Silicon Graphics individually, Silicon Graphics probably has other installed products that anyone, including Schemer, may use. If CASEVision/Tracker, IRIS Volume Manager, and IRIS Networker were the only installed products of Silicon Graphics (and Schemer was prohibited from using them), you would use the keyword ALL in the user file, as shown below, instead of specifying each product individually.
VENDOR "Silicon Graphics" ALL
DISALLOW schemer
|
Example 6-2 shows the format of the file /var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier). Square brackets, [], indicate optional items and vertical bars, |, indicate either the item on the left or the item on the right can be used.
Example 6-2. User File Syntax
% comment
[CRAWL n]
VENDOR 1st_vendor_name 1st_product_name|ALL
ALLOW|DISALLOW
1st_user_id [-P 1|2]
nth_user_id [-P 1|2]
VENDOR nth_vendor_name nth_product_name|ALL
ALLOW|DISALLOW
1st_user_id [-P 1|2]
nth_user_id [-P 1|2]
|
You may specify any number of vendors with associated products and user authorizations, and any number of user names (or none) may follow the ALLOW or DISALLOW keywords. Keywords may be uppercase or lowercase, but mixed-case keywords are not allowed. Single or double quotes must delimit vendor or product names that contain spaces. Comments can be used anywhere.
These keywords can be included in a user file:
| CRAWL | | Causes the priority of users to be changed to the next higher priority after the application has polled the queue n times. CRAWL may be specified only once in a user file. This keyword applies only to products that use queuing.
| | VENDOR | | Specifies the vendor of a licensed product(s). Either ALL or the name of a single product must follow the declaration of a VENDOR.
| | ALL | | Specifies that all of the vendor's products have the same user authorizations. The keyword ALL and the name of a single product are mutually exclusive.
| | ALLOW | | Specifies that the user names following this keyword are allowed to use the product(s). If no user names follow this keyword, it means no users are allowed to use the product(s). ALLOW and DISALLOW are mutually exclusive.
| | DISALLOW | | Specifies that the user names following this keyword are not allowed to use the product(s). If no user names follow this keyword, it means all users are allowed to use the product(s). ALLOW and DISALLOW are mutually exclusive.
| | –P 1 | | Specifies a priority-1 user (highest priority). Priority-1 users may displace lower-priority users already waiting in a queue. Default if omitted: priority-3 (lowest priority). This keyword applies only to products that use queuing.
| | –P 2 | | Specifies a priority-2 user. Priority-2 users may displace priority-3 users already waiting in a queue. Default if omitted: priority 3. This keyword applies only to products that use queuing.
|
Writing and Integrating User FilesIf you decide to have a user file, you can use any text editor to create it. Put one copy on each Network License Server in the file /var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier). You can write different user files for different Network License Servers, or put user files on some servers and not on others. However, such a policy might cause user access to a product to vary depending upon which server is granting the license. You should put the same user file on all servers in the interests of a consistent user authorization policy.
You can use the ls_admin command to check that the format of a user file is correct. See the ls_admin(1M) manual page for more information.
When you add a new product or wish to change user priorities for existing products, remember to update the user files at all Network License Server systems accordingly. The rdist(1C) command can be used to update these files automatically. See the rdist(1C) manual page for more information.
ls_stat(1M) provides users and administrators with status information including:
The names of Network License Servers on the network
The licensed products at all servers or at selected servers
The current users of licensed products and their user ID, host name, group, number of licenses held, and the times they started using the products
The licenses installed at each Network License Server, the number of active licenses, and their start and expiration dates
The use of products: the number of licenses in use, the total number of licenses, and the licenses available
ls_stat has both a graphical interface and a command-line interface. The steps below demonstrate how to get information from ls_stat using its graphical interface:
Give this ls_stat command:
The ls_stat window appears with a list of Network License Servers and a list of products.
Select a server and the product you are interested in.
Click the Installed button to get the number of licenses for the selected product that are installed at the selected server.
Click the Usage button to get the number of users of the selected product at the selected server.
Click the All Users button to get the user IDs and host names of all of the users of the selected product at the selected server.
Click the User button to bring up a User Name window. Enter the user ID of a user in which you are interested, then click the OK button. Information about usage of the selected product at the selected server by that user is displayed.
Select “All” as the server and/or product to obtain information about all servers and products at once.
Click the All Servers (Update) button to poll the network and update the server list. A check mark appears to indicate that all existing Network License Servers are displayed, and the vendors and products listed exist at the currently selected server.
Click the All Products (Update) button to poll the network and update the product list. A check mark appears to indicate that all existing vendors and products are displayed, and the listed servers hold licenses for the product or vendor currently selected.
The ls_stat(1M) manual page provides additional reference information on the graphical interface and on the alternative command-line interface.
Generating Reports on License ActivityThe ls_rpt(1M) command generates reports on all kinds of Network License Server activities that are based on the log of license activity kept by netlsd(1M). To use ls_rpt, give the command:
A report is printed to the screen.
With command-line arguments, you can specify different kinds of events to be reported (as well as all events) and use dates, software vendors, products, and users as information filters. Besides helping you monitor Network License Server activities, Network License Server reports can help you track demand for software products. This kind of information is useful in planning purchases of licenses for those products.
For complete information on ls_rpt, see the ls_rpt(1M) manual page.
Identifying Licenses in a Nodelock FileIf you need to locate a specific license in a /var/netls/nodelock or /usr/netls/nodelock file, possibly because it is a temporary license you want to delete, or if you want to find out what products have node-locked licenses on a particular system, use these techniques:
Look for comments that give the product name for each license. The recommended convention is to put a comment line (comment lines start with #) that includes the product name before each license line.
If you are looking for the license for a particular product, comment out all licenses except one. Try running a licensed application (see the release notes for the product for a list of licensed commands) to see if its license is the uncommented one. Test each license until you find the one you want.
To figure out what products the licenses might be for, give the versions(1M) command to list the installed products. Use the release notes for the products, if necessary, to identify which products require licenses. For each product, use the technique in the previous bullet to figure out if the license file contains a valid license for the product.
Installing Replacement LicensesAny time you install a license because a previous license for the same product is obsolete, you are installing a replacement license. The old and new licenses need not be of the same type: a concurrent license can replace a node-locked license or vice versa. Replacement licenses are sometimes needed when:
The original license is a temporary license
System or network reconfiguration results in a node-locked licensed application running on a system with a different system identification number
System or network reconfiguration results in a change in the system identification number of a Network License Server
You upgrade to a new version of a licensed product (see the release notes for the product to determine if a new license is required)
Follow these steps to install a replacement license:
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
|
|
|
