FLEXNET LICENSING END USER GUIDE Version 10.
Legal Notices Copyright Notice Copyright © 1996-2004 Macrovision Corporation. All Rights Reserved. The information contained herein contains confidential information and proprietary trade secrets and is the property of Macrovision Corporation. Any use, copy, publication, distribution, display, modification, or transmission of the information in whole or in part in any form or by any means without the prior express written permission of Macrovision Corporation is strictly prohibited.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Versions of FLEXnet Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documents from Macrovision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One Machine with Multiple License Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Machine with One License Server and Multiple License Files . . . . . . . . . . . . . . . . . . . . . . . Managing Multiple License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIMEOUTALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the Vendor Daemon Uses the Options File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules of Precedence in Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8 Mobile Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Node-Locked to a Laptop Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node-locked to a FLEXid (Windows Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node-Locked to a FLEXid with FLOAT_OK (Windows Only) . . . . . . . . . . . . . . . . . . . . . . . . . Initiating FLEXid with FLOAT_OK . . . .
Appendix E FLEXnet Licensing Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Error Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Format 1 (short): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Format 2 (long—version 6.0+): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii FLEXnet Licensing End User Guide
Preface Welcome to FLEXnet Licensing, the de facto standard network license manager used by over 2000 leading software vendors to control the use of their software products. FLEXnet Licensing is a part of FLEXnet Publisher. If you are a system administrator or end user, chances are one or more of the products currently on your network is FLEXenabled.
Typographic Conventions Typographic Conventions The following typographic conventions are used in this manual: • The first time a new term is used it is presented in italics. • Commands and path, file, and environment variable names are presented in a fixed_font. • Other variable names are in an italic_fixed_font. • API function calls are in a sans-serif font.
Introduction and Overview 1 This chapter explains the basics of floating (network) licensing and gives a quick overview of the FLEXnet Licensing components. It explains where license administrators have control and where end users have control. “Getting Started Checklist” tells both license administrators and end users how to start managing FLEXnet Licensing. Introduction to FLEXnet Licensing FLEXnet Licensing is a member of the FLEXnet Publisher family of products.
Chapter 1 - Introduction and Overview How to Use This Manual Chapter: Explains: Chapter 2, “License File Basics” License file basics; setting the path at start-up; different types of licensing policies. Chapter 3, “Managing Licenses from Multiple Vendors” Using license files from multiple software vendors. Chapter 4, “Selecting Server Machines” Resources required by the servers; multiple servers; quorums; redundant license servers.
Chapter 1 - Introduction and Overview FLEXnet Licensing Components FLEXnet Licensing Components FLEXnet Licensing components are organized based on the license model used by your software vendor. License models are classified according to their requirement for a license server: • Licenses are served by a license server. This is commonly referred to as a served license model.
Chapter 1 - Introduction and Overview FLEXnet Licensing Components Figure 1-1 shows the relationship these FLEXnet Licensing components have to one another. See “Component Overview” for a description of each component.
Chapter 1 - Introduction and Overview FLEXnet Licensing Components Figure 1-2 shows this model. See “Component Overview” for a description of each component. Your Application Code FLEXnet Licensing Client Library FLEXenabled Application License File(s) Figure 1-2: FLEXnet Unserved License Component Model The FLEXenabled application and license certificate reside on the same machine.
Chapter 1 - Introduction and Overview FLEXnet Licensing Components If the vendor daemon terminates for any reason, all users lose their licenses (though this does not mean the applications suddenly stop running). Users normally regain their license automatically when lmgrd restarts the vendor daemon, though they may exit if the vendor daemon remains unavailable. This behavior is defined by the vendor in the FLEXenabled application.
Chapter 1 - Introduction and Overview FLEXnet Licensing Components End-User Administration Options File The end-user administration options file allows the end-user license administrator to control various operating parameters of FLEXnet Licensing that remain within the license rights granted to them by the vendor.
Chapter 1 - Introduction and Overview The License Request Process Table 1-1: FLEXnet Licensing Components for End-User Distribution Component Description lmtools.exe Optional component. Graphical user interface for FLEXnet Licensing utilities, lmutil.exe. Also available from www.macrovision.com. lmgr10.dll Required if the FLEXenabled application is dynamically linked.This library provides the standard FLEXnet Licensing client library routines. flexid.exe or flexidsilent.
Chapter 1 - Introduction and Overview Configuring FLEXnet Licensing Configuring FLEXnet Licensing Most of the parameters of FLEXnet Licensing are configurable by the license administrator.
Chapter 1 - Introduction and Overview Getting Started Checklist 6. Start lmgrd (the license manager daemon) manually; you may also want to set it up to start automatically at boot time. See Chapter 6, “The License Manager Daemon.” These steps are discussed briefly below. License Server Machine and Hostids Before running any FLEXenabled application using floating licenses, you first need to set up your license server machine (or machines).
Chapter 1 - Introduction and Overview Getting Started Checklist How to Specify a License File Location The license file determines what features are available to a FLEXenabled application. It also contains information telling the application how to connect to the license server. For information about the standard way of specifying the location of a license file for an application, see Chapter 2, “License File Basics.
Chapter 1 - Introduction and Overview Getting Started Checklist 22 FLEXnet Licensing End User Guide
License File Basics 2 The license file contains information required by FLEXnet Licensing to manage licenses for a FLEXenabled application. This information includes: • License server names and hostids • Vendor names and paths to vendor daemon executables • Feature information In general, the license file, or a copy of it, must be accessible to every machine that runs a FLEXenabled application, and to each machine designated as a license server.
Chapter 2 - License File Basics Specifying Location of the License File @host. Table 2-1 shows some examples of LM_LICENSE_FILE and VENDOR_LICENSE_FILE environment variable settings.
Chapter 2 - License File Basics License File Format Overview • a port@host setting, where port and host are the TCP/IP port number and host name from the SERVER line in the license file. Alternatively, use the shortcut specification, @host, if the license file SERVER line uses a default TCP/IP port or specifies a port in the default port range (27000-27009). Applications accept an environment variable (or Windows Registry) named VENDOR_LICENSE_FILE, where VENDOR is the vendor daemon name, e.g.
Chapter 2 - License File Basics Types of License Files • Values in keyword=value pairs on FEATURE lines, if keyword is specified in lowercase See Also • “Redundant License Servers” • “Counted vs. Uncounted Licenses” • Appendix B, “License File Format,” for details on each one of these components. FLEXNET LICENSING VERSION NOTES • USE_SERVER introduced in the v5.0 client library. • VENDOR lines are known as DAEMON lines in the pre-v6.0 lmgrd and vendor daemon.
Chapter 2 - License File Basics Types of License Files If the number of licenses is set to 0 (or uncounted), then the license is uncounted and unlimited use is permitted on the specified machine. This configuration does not require an lmgrd or a vendor daemon because it is not going to count the concurrent usage of the features. The following license file allows unlimited usage of feature “f1” on the machines with hostids of “17007ea8” and “1700ab12”: FEATURE f1 sampled 1.
Chapter 2 - License File Basics Types of License Files 28 FLEXnet Licensing End User Guide
Managing Licenses from Multiple Vendors 3 Since more than 2500 vendors have chosen FLEXnet Licensing as their license manager, chances are good that you have to administer FLEXnet Licensing licenses from more than one vendor. Overview of Multiple License Management Strategies When you are running FLEXenabled products from multiple vendors, you may need to take steps to prevent licensing conflicts during installation.
Chapter 3 - Managing Licenses from Multiple Vendors Multiple Machines Multiple Machines Vendor ABC’s License File(s) Vendor DEF Daemon Vendor DEF’s License File(s) Server Machine1 Server Machine2... lmgrd Vendor XYZ Daemon License Server Vendor ABC Daemon lmgrd License Server lmgrd License Server In this scenario, each distinct vendor daemon and its associated license file or files is located on a separate server machine.
Chapter 3 - Managing Licenses from Multiple Vendors One Machine with Multiple License Servers One Machine with Multiple License Servers Vendor DEF’s License Files Vendor XYZ Daemon Vendor XYZ’s License Files Single Server Machine Vendor ABC’s License Files Vendor DEF Daemon lmgrd License Server 3 Vendor ABC Daemon lmgrd License Server 2 lmgrd License Server 1 In this model, each vendor daemon and its associated license file or files is served by its own lmgrd process, and everything is conta
Chapter 3 - Managing Licenses from Multiple Vendors One Machine with One License Server and Multiple License Files • Licensing load is concentrated to one machine. Starting the License Server Invoke each license server: • For Server 1: lmgrd -c vendor_ABC_license_dir_list • For Server 2: lmgrd -c vendor_DEF_license_dir_list • For Server 3: lmgrd -c vendor_XYZ_license_dir_list Where vendor_nnn_license_list is a license-file list as described in “Managing Multiple License Files.
Chapter 3 - Managing Licenses from Multiple Vendors Managing Multiple License Files • Output from all vendor daemons goes into one common debug log unless separate debug logs are specified with DEBUGLOG in each vendor’s options file. Having one common debug log makes it harder to debug a single vendor daemon’s problem. • Maximizes licensing load to one machine and one lmgrd process. Starting the License Server Invoke the license manager daemon once on the server machine.
Chapter 3 - Managing Licenses from Multiple Vendors Additional Considerations lmgrd builds up an internal license-file list when it starts up by parsing each license-file list component in the order listed. Some scenarios where a license-file list is used include those described in “Multiple Machines” “One Machine with Multiple License Servers” or “One Machine with One License Server and Multiple License Files.
Chapter 3 - Managing Licenses from Multiple Vendors Additional Considerations Disadvantage • Careful planning must be given in combining license lines from multiple vendors into one file, initially and over time. Starting the License Server Invoke the license manager daemon once on the server machine. lmgrd -c combined_license_file Criteria for Combining License Files Your product’s license file(s) define the license server(s) by host name and hostid in the SERVER line(s) in the license file.
Chapter 3 - Managing Licenses from Multiple Vendors Additional Considerations How to Combine License Files If your license files are compatible, use any text editor to combine them. To combine license files, read all of the compatible license files into one file, then edit out the extra SERVER lines so that only one set of SERVER lines remains. Save the resulting data, and you have your combined license file. Figure 3-5 shows an example of combining license files.
Chapter 3 - Managing Licenses from Multiple Vendors Additional Considerations Version Component Compatibility When one lmgrd process manages multiple vendor daemons, it may be the case that those vendor daemons do not use the same version of FLEXnet Licensing. By observing the FLEXnet Licensing version compatibility rules described in “Version Compatibility with FLEXnet Licensing Components” you are assured that all of your FLEXnet Licensing components are compatible.
Chapter 3 - Managing Licenses from Multiple Vendors Additional Considerations 38 FLEXnet Licensing End User Guide
Selecting Server Machines 4 This chapter helps you decide which machines to use as license server machines. Resources Used by the Server This section discusses the resources used by the license server. When you select a server machine, you may need to take into account the system limits on these resources. For small numbers of licenses (under about 100), most of these system limits are not a problem on any workstation.
Chapter 4 - Selecting Server Machines Remote Mounted Disks Disk Space The only output files created by the license servers are the debug and report log files. The report log files are used to generate accurate usage reports by SAMreport. If you have a lot of license activity, these log files grow very large. You need to consider where to put these files and how often to rotate and archive them. The license administrator has the option to suppress log file output if disk space is at a premium.
Chapter 4 - Selecting Server Machines Redundant License Servers mounted disk, you double the points of failure which could lead to a temporary loss of all of your licenses. When all files are mounted locally, the licenses are available as long as the server machine is up; but when the files are on a different machine, then the loss of either the license server machine or the file server machine causes the licenses to be unavailable.
Chapter 4 - Selecting Server Machines Redundant License Servers The user in Chicago could set LM_LICENSE_FILE to: 1700@chicago:1700@tokyo The user in Tokyo could set LM_LICENSE_FILE to: 1700@tokyo:1700@chicago Remember to separate the license file names with a colon (“ : ”) on UNIX and with a semicolon (“ ; ”) on Windows. The application attempts the first server in the list, and if that fails for any reason, the second server is tried.
Chapter 4 - Selecting Server Machines Counted vs. Uncounted Licenses • License-file list is not limited to three servers (any number work). • Clients do not require reliable networking to a single machine with license-file list, so this is recommended where networking itself requires redundancy. Counted vs. Uncounted Licenses The license file determines whether a license server is needed.
Chapter 4 - Selecting Server Machines Counted vs.
The Options File 5 The options file allows the license administrator to control various operating parameters of FLEXnet Licensing. Users are identified by their user name, host name, display, IP address, or PROJECT (which is set with the LM_PROJECT environment variable).
Chapter 5 - The Options File Options File Syntax 3. Add the path to the options file in the license file as the fourth field on the VENDOR line for the application’s vendor daemon. For example: VENDOR sampled /etc/sampled \ [options=]/sample_app/sampled/licenses/sampled.opt enables the sampled vendor daemon to look at the specified options file. If the path is omitted, the vendor daemon automatically looks for a file according to the following criteria: • the name of the file is vendor.
Chapter 5 - The Options File Options File Syntax Table 5-1: Option Keywords (cont.) Option Keyword Description GROUPCASEINSENSITI VE Sets case sensitivity for user and host lists specified in GROUP and HOST_GROUP keywords. HOST_GROUP Define a group of hosts for use with any options (v4.0+). INCLUDE Allow a user to use a feature. INCLUDE_BORROW Allow a user to borrow BORROW licenses. INCLUDEALL Allow a user to use all features served by this vendor daemon.
Chapter 5 - The Options File Options File Syntax Comments Include comments in your options file by starting each comment line with a pound sign “#.” Feature Specification The feature name can be modified with an optional keyword-value pair to fully qualify it. This notation is used for distinguishing a particular group of licenses when there are multiple FEATURE lines for a single feature. The following syntax is used: feature:keyword=value For example: f1:VERSION=2.0 specifies the version 2.
Chapter 5 - The Options File Options File Syntax Type Specification The following option keywords restrict who may use licenses or where licenses may be used: EXCLUDE, EXCLUDEALL, EXCLUDE_BORROW, INCLUDE, INCLUDEALL, INCLUDE_BORROW, MAX, and RESERVE. These options take a type argument, which specifies whether the restriction is based on USER, HOST, DISPLAY, INTERNET, or PROJECT: • USER— user name of the user executing the FLEXenabled application. User names are case sensitive.
Chapter 5 - The Options File Options File Syntax BORROW_LOWWATER BORROW_LOWWATER feature[:keyword=value] n Sets the number of licenses for a BORROW feature that cannot be borrowed. feature Name of feature being affected. keyword=value Feature name modifier to denote a group of licenses. See “Feature Specification” for details. n Number of licenses that cannot be borrowed via license borrowing.
Chapter 5 - The Options File Options File Syntax EXCLUDE EXCLUDE feature[:keyword=value] type {name | group_name} Excludes a user or pre-defined group of users, etc., from the list of who is allowed to use the feature. EXCLUDE supersedes INCLUDE; conflicts between the EXCLUDE list and the INCLUDE list are resolved by the EXCLUDE taking precedence. feature Name of the feature being affected. keyword=value Feature name modifier to denote a group of licenses. See “Feature Specification” for details.
Chapter 5 - The Options File Options File Syntax group_name Name of the group to exclude from borrowing. To exclude the user “fred” from the list of users able to borrow feature “f1” assuming the feature has the BORROW attribute: EXCLUDE_BORROW f1 USER fred EXCLUDEALL EXCLUDEALL type {name | group_name} Excludes a user or pre-defined group of users, etc., from the list of who is allowed to use all features served by this vendor daemon.
Chapter 5 - The Options File Options File Syntax Only the last FQDN_MATCHING keyword in the the options file has effect; all others are ignored. Table 5-2 shows the outcome of matching attempts between HOST type-specifiers in the options file and host names sent by the application. Table 5-2: Host Name Matching Matrix Options File FQDN_MATCHING exact FQDN_MATCHING lenient Application configured for FQDN — sends. myhost.abc.
Chapter 5 - The Options File Options File Syntax The example below is even more lenient: INCLUDE f2 HOST myhost FQDN_MATCHING lenient This includes the host name, myhost, on the list of hosts for feature “f3.” Since lenient matching is specified, host names such as myhost, myhost.abc.com, and myhost.xyz.com match. Whereas, yourhost or yourhost.abc.com do not match. See Also • “Type Specification” FLEXNET LICENSING VERSION NOTES • FQDN_MATCHING introduced in v9.3 client library and vendor daemon.
Chapter 5 - The Options File Options File Syntax HOST_GROUP HOST_GROUP group_name host_list Defines a group of hosts for use in INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, and RESERVE option lines. Multiple HOST_GROUP lines add all the specified hosts into the group. group_name Name of the group being defined. Host group names are case sensitive. host_list List of host names in that group. Names are case sensitive. Set the GROUPCASEINSENSITIVE options file keyword to turn on case insensitivity.
Chapter 5 - The Options File Options File Syntax Note INCLUDE is required for USER_BASED or HOST_BASED features. The system administrator specifies which users are allowed to use the product, via INCLUDE, and the license limits the number of users that are INCLUDEd. INCLUDE_BORROW INCLUDE_BORROW feature[:keyword=value] type {name | group_name} Includes a user or pre-defined group of users, etc., in the list of who is allowed to borrow the BORROW feature.
Chapter 5 - The Options File Options File Syntax name Name of an item of type type for which license usage is included. group_name Name of the group to include. To allow the user “jane” to use all features served by this vendor daemon: INCLUDEALL USER jane LINGER LINGER feature[:keyword=value] seconds A lingering license stays checked out for a specified period of time beyond its checkin or FLEXenabled application exit, whichever comes first.
Chapter 5 - The Options File Options File Syntax feature Feature this limit applies to. keyword=value Feature name modifier to denote a group of licenses. See “Feature Specification” for details. type One of USER, HOST, DISPLAY, INTERNET, PROJECT, GROUP, or HOST_GROUP. See “Type Specification” for details. name Name of an item of type type for which usage is limited. group_name Name of the group to limit.
Chapter 5 - The Options File Options File Syntax keyword=value Feature name modifier to denote a group of licenses. See “Feature Specification” for details. num_lic Usage limit for this user or group. NOLOG NOLOG { IN | OUT | DENIED | QUEUED } Suppresses logging the selected type of event in the debug log file.
Chapter 5 - The Options File Options File Syntax See Also • “Configuring the License Manager as a Windows Service” • Appendix D, “FLEXnet Licensing Environment Variables” • Appendix F, “The Report Log File” RESERVE RESERVE num_lic feature[:keyword=value] type {name | group_name} Reserves licenses for a specific user. num_lic Number of license to reserve for this user or group. feature Feature or package this reservation applies to. keyword=value Feature name modifier to denote a group of licenses.
Chapter 5 - The Options File How the Vendor Daemon Uses the Options File TIMEOUT TIMEOUT feature[:keyword=value] seconds Sets the time after which an inactive license is freed and reclaimed by the vendor daemon. Note The vendor must have enabled this feature in the FLEXenabled application for it to work. Contact your software vendor to find out if this feature is implemented. feature Name of the feature. keyword=value Feature name modifier to denote a group of licenses.
Chapter 5 - The Options File Rules of Precedence in Options Files FLEXNET LICENSING VERSION NOTES • The lmreread utility enhanced in v8.0 vendor daemon so that it causes the vendor daemon to reread the options file. If you are using earlier versions, the vendor daemon must be stopped and restarted in order for the options file to be reread.
Chapter 5 - The Options File Options File Examples • Prevents the user “lori” from using the “compile” feature on any machine on the network. • Causes QUEUED messages to be omitted from the debug log file. The sum total of the licenses reserved must be less than or equal to the number of licenses specified in the FEATURE line. In the example above, there must be a minimum of four licenses on the “compile” FEATURE line.
Chapter 5 - The Options File Options File Examples EXCLUDE Example #First Define the group "painters" GROUP painters picasso mondrian klee EXCLUDE spell GROUP painters EXCLUDE spell USER bob EXCLUDE spell INTERNET 123.123.123.* This options file: • Prevents the users “picasso,” “mondrian,” and “klee” from using the feature “spell” on any machine on the network. • Prevents the user “bob” from using the feature “spell” on any machine on the network.
The License Manager Daemon 6 The license manager daemon, lmgrd, is one of two FLEXnet Licensing components which comprise the license server (the other being the vendor daemon). It handles the initial contact with FLEXenabled applications, passing the connection on to the appropriate vendor daemon. The purpose of the license manager daemon, lmgrd, is to: • Start and maintain all the vendor daemons listed in the VENDOR lines of the license file.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on UNIX Platforms -2 -p Restricts usage of lmdown, lmreread, and lmremove to a FLEXnet Licensing administrator who is by default root. If there a UNIX group called “lmadmin,” then use is restricted to only members of that group. If root is not a member of this group, then root does not have permission to use any of the above utilities.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on UNIX Platforms license file (as well as the lmgrd and the vendor daemons binaries) on each server node. If you do not do this, you lose all the advantages of having redundant servers, since the file server holding these files becomes a single point of failure.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on Windows /bin/su daniel -c '/home/flexlm/v5.12/hp700_u9/lmdiag -n -c\ /home/flexlm/v5.12/hp700_u9/license.dat >> \ /home/flexlm/v5.12/hp700_u9/boot.log' /bin/su daniel -c 'echo exiting >>\ /home/flexlm/v5.12/hp700_u9/boot.log' Please note the following about how this script was written: • All paths are specified in full, because no paths are assumed at boot time.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on Windows Configuring the License Manager as a Windows Service To configure a license server as a service, you must have Administrator privileges: 1. Run LMTOOLS. 2. Click the Configuration using Services radio button, then click the Config Services tab. 3. In the Service Name, type the name of the service that you want to define, for example, Myvendor License Manager. 4. In the Path to the lmgrd.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on Windows In order to control the operation of lmgrd from the LMTOOLS user interface, you first must configure it as a license manager service. Follow the procedure in “Configuring the License Manager as a Windows Service” before proceeding. Once the license manager service is configured, lmgrd is started by starting the service from the LMTOOLS interface: 1. Start LMTOOLS. LMTOOLS appears with the Service/License File tab open.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on Windows 4. Click the Start/Stop/Reread tab. 5. Start Myvendor License Manager by clicking the Start Server button. Myvendor License Manager license server starts and writes its debug log output to c:\flexlm\lmgrd.dl. Automatically at System Start Up In order for lmgrd, and hence the license server, to start up automatically at system start up time, you first must configure it as a license manager service.
Chapter 6 - The License Manager Daemon Starting the License Manager Daemon on Windows 1. With LMTOOLS started and the desired service name selected, click the Config Services tab. Step 3 Step 2 2. Make this license manager a Windows service: check the Use Services check box (otherwise, it becomes a FLEXnet Licensing service). 3. Configure it to start at system startup time by checking the Start Server at Power Up check box.
License Administration Tools 7 FLEXnet Licensing provides utilities for the license administrator to help manage the licensing activities on the network. Always use the newest version of the utilities as possible; they are available for download from www.macrovision.com. Table 7-1 lists these utilities. Table 7-1: License Administration Utilities Utility Description lmborrow Supports license borrowing. lmdiag Diagnoses license checkout problems.
Chapter 7 - License Administration Tools Running Administration Tools Table 7-1: License Administration Utilities (cont.) Utility Description lmver Reports the FLEXnet Licensing version of a library or binary file. FLEXNET LICENSING VERSION NOTES • • • • The lmpath utility introduced in the v7.0 utilities. The lmborrow utility introduced in the v8.0 utilities. The lmswitch utility introduced in v8.0 vendor daemon. The lmswitchr utility introduced in v8.0 vendor daemon.
Chapter 7 - License Administration Tools lmborrow -help Displays usage information and exits. -v Displays the FLEXnet Licensing version of the utility and exits. -verbose Displays longer description for all errors found. FLEXNET LICENSING VERSION NOTES • VENDOR_LICENSE_FILE environment variable honored in utilities starting with v7.0 utilities. • -verbose option introduced in v6.0 of the utilities. lmborrow lmborrow supports borrowing of licenses that contain the BORROW attribute.
Chapter 7 - License Administration Tools lmborrow For example: lmborrow sampled 20-aug-2001 13:00 This has the effect of setting LM_BORROW with the borrow period in either the registry (Windows) or in $HOME/.flexlmrc (UNIX). To borrow licenses for the desired vendor, on the same day and the same machine that the user runs lmborrow, run the application(s) to check out the license(s). If you run the application(s) more than once that day, no duplicate licenses are borrowed.
Chapter 7 - License Administration Tools lmborrow where: -fqdn Directs lmborrow to access the borrowing system using its fully qualified host name. Use this option if the license was borrowed based on the fully qualified host name, rather than the relative distinguished name. Use lmstat to determine the format of the host name used when the license was borrowed. -c license_file_list Use the specified license file(s).
Chapter 7 - License Administration Tools lmdiag lmdiag lmdiag allows you to diagnose problems when you cannot check out a license. Usage is: lmdiag [-c license_file_list] [-n] [feature[:keyword=value]] where: -c license_file_list Diagnose the specified file(s). -n Run in non-interactive mode; lmdiag does not prompt for any input in this mode. In this mode, extended connection diagnostics are not available. feature Diagnose this feature only.
Chapter 7 - License Administration Tools lmdown lmdown The lmdown utility allows for the graceful shutdown of selected license daemons (both lmgrd and selected vendor daemons) on all machines. Usage is: lmdown -c license_file_list [-vendor vendor_daemon] [-q] [-all] [-force] where: -c Use the specified license file(s). Note that specifying -c license_file_list license_file_list is always recommended with lmdown -vendor Shut down only this vendor daemon. lmgrd continues running. Requires v6.
Chapter 7 - License Administration Tools lmhostid See Also • “lmgrd Command-Line Syntax” for details about securing access to lmdown • “lmreread.” FLEXNET LICENSING VERSION NOTES • -all option introduced in the v7.0 lmdown utility. • -force option introduced in the v8.0 lmdown utility. lmhostid The lmhostid utility returns the FLEXnet Licensing hostid of the current platform. Invoked without any arguments, lmhostid displays the default hostid type for current platform.
Chapter 7 - License Administration Tools lminstall -flexid Parallel or USB FLEXid dongle identification. (Windows platforms only) -long 32-bit hostid. Platform Independent Hostids -user Current user name. -display Current display name. On Windows, it is the system name or, in the case of a terminal server environment, the terminal server client name. On UNIX, it is in the form /dev/ttyxx or the X-Display name. -hostname Current host name.
Chapter 7 - License Administration Tools lmnewlog When an input file is specified with no output file specified, output goes to stdout; if neither input nor output file is specified, lminstall assumes that input comes from stdin and prompts the user for an output file name. lminstall is also used to convert licenses from readable to decimal format, and between different versions of FLEXnet license formats.
Chapter 7 - License Administration Tools lmpath lmpath The lmpath utility allows direct control over FLEXnet license path settings. It is used to add to, override, or get the current license path settings. Usage is: lmpath {-add | -override} {vendor | all} license_file_list where: Note -add Prepends license_file_list to the current license-file list or creates the license-file list, if it doesn’t exist, initializing it to license_file_list. Duplicates are discarded.
Chapter 7 - License Administration Tools lmremove Other Vendors: ______________ /usr/local/flexlm/licenses/license.lic Note that where the path is set to a directory, all the *.lic files are listed separately. lmremove The lmremove utility allows you to remove a single user’s license for a specified feature. If the application is active, it re-checks out the license shortly after it is freed by lmremove.
Chapter 7 - License Administration Tools lmreread The -h variation uses the server_host, port, and license handle, as reported by lmstat -a. Consider this example lmstat -a output: joe nirvana /dev/ttyp5 (v1.000) (cloud9/7654 102), start Fri 10/29 18:40 In this example, the user is “joe,” the user host is “nirvana,” the display is “/dev/typp5,” the server host is “cloud9,” the TCP/IP port is “7654,” and the license handle is “102.
Chapter 7 - License Administration Tools lmstat -all Note If more than one lmgrd is specified, instructs all lmgrds to reread. If you use the -c license_file_list option, the license file(s) specified are read by lmreread, not by lmgrd; lmgrd rereads the file it read originally. You can protect the unauthorized execution of lmreread when you start up the license manager daemon, lmgrd.
Chapter 7 - License Administration Tools lmstat -c license_file_list Uses the specified license file(s). -f [feature] Displays users of feature. If feature is not specified, usage information for all features is displayed. -i [feature] Displays information from the FEATURE/INCREMENT line for the specified feature, or all features if feature is not specified.
Chapter 7 - License Administration Tools lmswitch 27000 port TCP/IP port on server_host where license server is running. 102 handle License handle. start Fri 5/3 7:29 checkout_time Time that this license was checked out. The user, user_host, display, server_host, port, and handle information is used when removing licenses with lmremove. Note lmstat -a is a potentially expensive command. With many active users, this command generates a lot of network activity.
Chapter 7 - License Administration Tools lmswitchr If debug log output is not already directed to a separate file for this vendor daemon, lmswitch tells the vendor daemon to start writing its debug log output to a file, new_debug_log. If this vendor daemon is already writing to its own debug log, lmswitch tells the vendor daemon to close its current debug log file and start writing its debug log output to new_debug_log.
Chapter 7 - License Administration Tools lmver Note The effect of lmswitchr continues only until the vendor daemon is shut down or its options file is reread via lmreread. When the vendor daemon is restarted or its options file is reread, it looks for a REPORTLOG line in the options file to determine whether or not to write report log output to a file and, if so, what file to write.
Chapter 7 - License Administration Tools License Administration Tools—LMTOOLS for Windows Configuration Using License File Operations are performed on a particular license file. The file can be either local or remote. In this mode, you cannot start the lmgrd process, but you can do everything else. To configure this mode, perform the following: 1. Invoke LMTOOLS. 2. Click the Configuration using License File radio button. 3. Enter one or more the license file names or port@host specifications.
Chapter 7 - License Administration Tools License Administration Tools—LMTOOLS for Windows 92 FLEXnet Licensing End User Guide
Mobile Licensing 8 End users often want to use applications on computers that do not have a continuous connection to a FLEXnet license server.
Chapter 8 - Mobile Licensing Node-Locked to a FLEXid with FLOAT_OK (Windows Only) Node-Locked to a FLEXid with FLOAT_OK (Windows Only) This method of license mobility has an advantage over simply using a license node-locked to a FLEXid, because the FLEXid is attached to a license server machine and its license floats on the network. Licenses with a FLOAT_OK keyword that are node-locked to a FLEXid are supported only where both the FLEXenabled application and the license server are running on Windows.
Chapter 8 - Mobile Licensing Node-Locked to a FLEXid with FLOAT_OK (Windows Only) Returning a FLEXid with FLOAT_OK License To return the license to the license server machine so it floats on the network again, the end user: 1. Removes the FLEXid from the client machine and replaces it on the license server machine. 2. Rereads the license file for the license server that serves the floating version of the license by running lmreread.
Chapter 8 - Mobile Licensing License Borrowing with BORROW License Borrowing with BORROW If a license is to be used on a computer that is intermittently connected to a license server, that license can be issued as a floating license with the BORROW keyword. A BORROW license can be borrowed from a license server via a special checkout and used later to run an application on a computer that is no longer connected to the license server.
Chapter 8 - Mobile Licensing License Borrowing with BORROW Setting the LM_BORROW Environment Variable Directly The lmborrow utility is a user interface to set LM_BORROW in either the registry (Windows) or in $HOME/.flexlmrc (UNIX). LM_BORROW can also be set directly as an environment variable: today:{vendor|all}:enddate[:time] where: today Today’s date in dd-mmm-yyyy format. Any checkouts done on this date create local borrow information.
Chapter 8 - Mobile Licensing License Borrowing with BORROW out stays checked out from the license server until the borrow period expires—that license now is used on your disconnected machine until the borrow period expires. Once checked out, it remains checked out for the full borrow period. The borrow period cannot be renewed until the period has expired.
Chapter 8 - Mobile Licensing Node-locked to a User Name FLEXNET LICENSING VERSION NOTES • BORROW keyword introduced in v8.0 client library, license manager daemon, and vendor daemon. All components must be v8.0+ in order to use BORROW. Node-locked to a User Name If a license is to be used exclusively by one user on different machines, that license can be nodelocked to the user’s user name.
Chapter 8 - Mobile Licensing Fulfilled from a Prepaid License Pool 100 FLEXnet Licensing End User Guide
Hostids for FLEXnet Licensing-Supported Platforms A FLEXnet Licensing uses different machine identifications for different machine architectures. For example, all Sun Microsystems machines have a unique hostid, whereas all DEC machines do not. For this reason, the ethernet address is used on some machine architectures as the hostid. An ethernet address is a 6-byte quantity, with each byte specified as two hexadecimal digits. Specify all twelve hex digits when using an ethernet address as a hostid.
Appendix A - Hostids for FLEXnet Licensing-Supported Platforms Expected FLEXnet Licensing Hostids Hardware Platform Hostid Type this command on the license server: Example DEC Alpha ethernet address netstat -i 080020005532 HP (32-bit and 64-bit platforms, nonItanium) 32-bit hostid uname -i and convert to hex, HP (64-bit Itanium getconf \ machine identification CS_PARTITION_ IDENT then prefix with “ID_STRING=” Mac OS X ethernet address or prepend with # 778DA450 or #2005771344 ID_STRING=9c76
Appendix A - Hostids for FLEXnet Licensing-Supported Platforms Special FLEXnet Licensing Hostids Special FLEXnet Licensing Hostids FLEXnet Licensing contains a number of special hostid types which apply to all platforms. These hostid types are valid to use in both SERVER lines and FEATURE lines, wherever a hostid is required. These are: ANY Locks the software to any machine (i.e., does not lock anything). DEMO Similar to ANY, but only for use with uncounted FEATURE lines.
Appendix A - Hostids for FLEXnet Licensing-Supported Platforms Special FLEXnet Licensing Hostids INTERNET= ###.###.###.### USER=user Locks the software to an Internet IP address, or group of IP addresses. Wildcards are allowed. For example, 198.156.*.* means any host with a matching internet IP address. The main use is to limit usage access by subnet, implying geographic area. For this purpose, it is used on the FEATURE/INCREMENT line as a hostid lock. Locks the software to user name user.
License File Format B License files usually begin with a SERVER line (or three lines for three-server redundant servers) followed by one or more VENDOR lines, followed by one or more FEATURE or INCREMENT lines. In some cases the license file requires no SERVER line and no VENDOR line.
Appendix B - License File Format License File Syntax License File Syntax Sample License File This is an example of a license file for a single vendor with two features. SERVER my_server 17007ea8 1700 VENDOR sampled FEATURE f1 sampled 1.000 01-jan-2005 10 SIGN=9BFAC0316462 FEATURE f2 sampled 1.000 01-jan-2005 10 SIGN=1B9A308CC0F7 The license file above allows the license server “my_server” with the hostid “17007ea8” to serve ten floating licenses for each feature, “f1” and “f2,” to any user on the network.
Appendix B - License File Format License File Syntax See Also • “FEATURE/INCREMENT Lines” for more information about uncounted features. • Chapter 4, “Selecting Server Machines,” for more information about redundant servers. FLEXNET LICENSING VERSION NOTES • IP address specification for host introduced in v5.0 lmgrd, vendor daemon, and client library. • port specification is required with a pre-v6.0 lmgrd, vendor daemon, and client library.
Appendix B - License File Format License File Syntax Field Description options_file_ path Full path to the end-user options file for this daemon. FLEXnet Licensing does not require an options file. If omitted, the vendor daemon, by default, looks for a file called vendor.opt (where vendor is the vendor daemon name) located in the same directory as the license file. port Vendor daemon TCP/IP port number. The default, if port is not specified, is chosen by the operating system at run-time.
Appendix B - License File Format License File Syntax FEATURE/INCREMENT Lines A FEATURE line describes the license required to use a product. An INCREMENT line can be used in place of a FEATURE line, as well as to incrementally add licenses to a prior FEATURE or INCREMENT line in the license file. Only the first FEATURE line for a given feature is processed by the vendor daemon.
Appendix B - License File Format License File Syntax Table B-1: FEATURE/INCREMENT Line Required Fields (cont.) Field Description exp_date Expiration date of license in the format dd-mmm-yyyy, e.g., 07-may-2005. Note: If exp_date is the string “permanent” or the year is 0 (or 00, 000, 0000) then the license never expires. num_lic Number of concurrent licenses for this feature.
Appendix B - License File Format License File Syntax Table B-2: Vendor Supplied Attributes (cont.) Attribute Description DUP_GROUP=... The syntax is: DUP_GROUP=NONE|SITE|[UHDV] U H D V = = = = DUP_USER DUP_HOST DUP_DISPLAY DUP_VENDOR_DEF Any combination of UHDV is allowed, and the DUP_MASK is the OR of the combination.
Appendix B - License File Format License File Syntax Table B-2: Vendor Supplied Attributes (cont.) 112 Attribute Description LINGER=n The vendor-defined lingering interval for this license. Use LINGER in the options file to extend this time. See “LINGER” for more information. NOTICE="..." A field for intellectual property notices.
Appendix B - License File Format License File Syntax The following attributes listed in Table B-3 are optional and are under control of the end user. These attributes have a keyword=value syntax where keyword is in lowercase. Table B-3: End-User Attributes Attribute Description asset_info="..." Additional information provided by the license administrator for asset management. dist_info="..." Additional information provided by the software distributor.
Appendix B - License File Format License File Syntax To turn off automatic ordering add sort=nnn to the FEATURE/INCREMENT line, where nnn is the same on all lines; nnn specifies the relative sort order. The default sort order value is 100. Lines with a sort order value of less than 100 are sorted before all lines without this attribute, and lines with a sort order value greater than 100 appear after all unmarked lines. All lines with the same number are sorted as they appear in the file.
Appendix B - License File Format License File Syntax Example: PACKAGE package vendor [pkg_version] COMPONENTS=pkg_list \ [OPTIONS=SUITE] [SUPERSEDE[="p1 p2 ..."] ISSUED=date] SIGN=pkg_sign Table B-4 lists the PACKAGE line fields. They must appear in the order listed. Table B-4: PACKAGE Line Fields Field Description package Name of the package. The corresponding FEATURE/INCREMENT line must have the same name. vendor Name of the vendor daemon that supports this package.
Appendix B - License File Format License File Syntax Table B-4: PACKAGE Line Fields (cont.) Field Description SUPERSEDE [="p1 p2 ..."] Optional field. Used in conjunction with ISSUED date. Replaces all PACKAGE lines for the same package name with ISSUED dates previous to dd-mmm-yyyy. ISSUED= dd-mmm-yyyy Optional field. Used in conjunction with SUPERSEDE. Replaces all PACKAGE lines for the same package name with ISSUED dates previous to dd-mmm-yyyy. SIGN=\ License key or SIGN= signature.
Appendix B - License File Format Decimal Format UPGRADE Lines UPGRADE feature vendor from_feat_version to_feat_version \ exp_date num_lic [options ... ] SIGN=sign All the data is the same as for a FEATURE or INCREMENT line, with the addition of the from_feat_version field. An UPGRADE line removes up to the number of licenses specified from any old version (>= from_feat_version) and creates a new version with that same number of licenses. For example, the two lines: INCREMENT f1 sampled 1.
Appendix B - License File Format License File Order License File Order The order of the lines in a license file is not critical. They are sorted when they are processed so that in most cases the optimal result is achieved. However, pre-v7.0 versions of FLEXenabled applications and license servers implicitly impose an ordering to license file lines. Note the following suggestions for ordering lines in the license file: • Place FEATURE lines before INCREMENT lines for the same feature.
Troubleshooting Guide C This appendix documents areas of FLEXnet Licensing that have given customers difficulty in the past. General Troubleshooting Hints The following are tips for debugging: • When you start the license server (lmgrd) be sure that you direct the output into a local log file where you can examine it. The log file often contains useful information. Examine it when you have a problem, and be prepared to answer questions about it when you talk to a support person.
Appendix C - Troubleshooting Guide FLEXLM_DIAGNOSTICS - Did the server start correctly? Look for a message such as: server xyz started for: feature1 feature2.
Appendix C - Troubleshooting Guide FLEXLM_DIAGNOSTICS • It was unable to find the other license file, which is what produces the message “No such file or directory” Following is a description of the arguments to lm_checkout() lm_checkout(feature, version, num_lic, queue_flag, ..., dupgroup_mask) where: feature The requested feature. version The requested version. The license file must contain a version >= the requested version. num_lic Number of licenses requested. Usually 1.
Appendix C - Troubleshooting Guide FLEXLM_DIAGNOSTICS 122 FLEXnet Licensing End User Guide
FLEXnet Licensing Environment Variables D Environment variables are not required in order to use FLEXenabled applications. Environment variables are normally used for debugging or for changing license default location. How to Set Environment Variables FLEXnet Licensing environment variables are set in two different ways: • In the process’ environment • In the registry (Windows v6.0+) or in $HOME/.flexlmrc (UNIX v7.0+), which functions like the registry for FLEXnet Licensing on UNIX.
Appendix D - FLEXnet Licensing Environment Variables Environment Variables FLEXLM_DIAGNOSTICS Used for debugging where applications don’t print FLEXnet Licensing error message text. Set to 1, 2, or 3, depending on the amount of diagnostic information desired. See “FLEXLM_DIAGNOSTICS.” (Version 5.0+ clients) FLEXLM_TIMEOUT Windows only: Sets the timeout value a FLEXenabled application uses when attempting to connect to a license server port in the range 27000-27009.
FLEXnet Licensing Error Codes E Error Message Format FLEXnet Licensing error messages presented by applications have the following components: • FLEXnet Licensing Error Number—a negative number starting at -1. • FLEXnet Licensing Error Text—short sentence (< 80 characters) summarizing problem. • FLEXnet Licensing Error Explanation (optional)—short paragraph (3-5 lines) explaining problem and possible solutions or workarounds. • FLEXnet Licensing Minor Error Number—a positive number starting at 1.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Format 2 (long—version 6.0+): FLEXlm error text FLEXlm error explanation [Optional Supporting information] FLEXlm error: -lm_errno, minor_num. [System Error: sys_errno] [“system_error_text”] Example: Cannot connect to license server The server (lmgrd) has not been started yet, or the wrong port@host or license file is being used, or the port or hostname in the license file has been changed.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) Error Code Description -11 Invalid date format in license file. -12 Invalid returned data from license server. -13 No SERVER lines in license file. -14 Cannot find SERVER host name in network database. The lookup for the host name on the SERVER line in the license file failed. This often happens when NIS or DNS or the hosts file is incorrect. Workaround: Use IP address (e.g., 123.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) 128 Error Code Description -34 Clock difference too large between client and server. -35 In the queue for this feature. -36 Feature database corrupted in daemon. -37 Duplicate selection mismatch for this feature. Obsolete with v8.0+ vendor daemon. -38 User/host on EXCLUDE list for feature. -39 User/host not on INCLUDE list for feature. -40 Cannot locate dynamic memory.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) Error Code Description -68 License BORROW support not enabled. -69 FLOAT_OK can’t run standalone on SERVER. -71 Invalid TZ environment variable. -73 Local checkout filter rejected request. -74 Attempt to read beyond end of license file path. -751 SYS$SETIMR call failed (VMS). -76 Internal FLEXnet Licensing error—please report to Macrovision.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) 130 Error Code Description -95 Network connect to this_host failed. Change this_host on the SERVER line in the license file to the actual host name. -96 Server machine is down or not responding. See the system administrator about starting the server, or make sure that you’re referring to the right host (see LM_LICENSE_FILE environment variable). -97 The desired vendor daemon is down.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) Error Code Description -115 Error in Public Key package. -116 TRL not supported for this platform. -117 BORROW failed. -118 BORROW period has expired. -119 lmdown and lmreread must be run on license server machine. -120 Cannot lmdown the server when licenses are borrowed. -121 FLOAT_OK license must have exactly one FLEXid hostid. -122 Unable to delete local borrow info.
Appendix E - FLEXnet Licensing Error Codes Error Code Descriptions Table E-1: FLEXnet Licensing Error Codes (cont.) Error Code Description -506 Internal FLEXnet Licensing error. -507 Bad date format in license file. -508 Bad SERVER line. -509 Bad license string. -510 Server's feature doesn't authenticate on client side. -511 No license checked out. -512 License already checked out. -513 Error list returned. -514 No certicom module available. -515 Wrong or incomplete certicom module.
The Report Log File F The license server produces both report log files and debug log files. The focus of this appendix is report log files. For information on debug log files see Appendix G, “The Debug Log File.” The report log file contains feature usage information and is generated by the vendor daemon. However, a vendor daemon does not write report log output by default. Report log output is not human readable and is only used by the SAMreport and FLEXbill products.
Appendix F - The Report Log File Redirecting Report Log Output for a Vendor Daemon Redirecting Report Log Output for a Vendor Daemon The report log output for a particular vendor daemon can be moved into separate files, each file representing activity over a different period of time. There are three ways in which to do this whether the vendor daemon is running or not: • Change the REPORTLOG line in the vendor daemon’s options file and reread its options file by invoking lmreread (v8.
The Debug Log File G The license server produces both debug log files and report log files. The focus of this appendix is debug log files. For information on report log files see Appendix F, “The Report Log File.” A debug log file contains status and error messages useful for debugging the license server. A license server always generates debug log output. Some of the debug log output describes events specific to lmgrd and some of the debug log output describes events specific to each vendor daemon.
Appendix G - The Debug Log File Debug Log Messages Redirecting Debug Log Output for a Running Vendor Daemon It is possible to redirect the debug log output for a particular vendor daemon to a different file. There are two ways to do this: • Change the DEBUGLOG line to the options file for the vendor daemon and reread its options file by invoking lmreread. See “DEBUGLOG” for more details. • Invoke lmswitch on the vendor daemon. See “lmswitch” for more details.
Appendix G - The Debug Log File Debug Log Messages Informational Messages Message Description Connected to host This daemon is connected to its peer on host. CONNECTED, master is host The license daemons log this message when a quorum is up and everyone has selected a master. DENIED: num_lic feature to user user was denied access to num_lic licenses of feature. EXITING DUE TO SIGNAL nnn EXITING with code nnn All daemons list the reason that the daemon has exited.
Appendix G - The Debug Log File Debug Log Messages Message Description Retrying socket bind (address in use) The license servers try to bind their sockets for approximately six minutes if they detect “address in use” errors. Selected (EXISTING) master host. This license daemon has selected an existing master host as the master. SERVER shutdown requested. A daemon was requested to shut down via a usergenerated kill command.
Appendix G - The Debug Log File Debug Log Messages Configuration Problem Messages Message Description host: Not a valid server host, exiting This daemon was run on an invalid host name. host: Wrong hostid, exiting The hostid is wrong for host. BAD CODE for feature The specified feature name has a bad license key or signature. It was probably typed in wrong, or modified by the end user. CANNOT OPEN options file file The options file specified in the license file could not be opened.
Appendix G - The Debug Log File Debug Log Messages Message Description Unknown host: host The host name specified on a SERVER line in the license file does not exist in the network database (probably /etc/hosts). Daemon Software Error Messages Message Description accept: message An error was detected in the “accept” system call. Can’t allocate server table space A malloc error. Check swap space. Connection to host TIMED OUT The daemon could not connect to host.
FLEXnet Licensing Versions H Version Compatibility with FLEXnet Licensing Components In general, always use the latest lmgrd and lmutil/LMTOOLS, which are available from www.macrovision.com, and you’ll automatically enjoy many of the enhancements available in the most recent versions of FLEXnet Licensing. However, some enhancements require a vendor daemon built with a newer version of FLEXnet Licensing, and yet others require a FLEXenabled application built with a newer version of FLEXnet Licensing.
Appendix H - FLEXnet Licensing Versions Version Summary >= Version 5 SUPERSEDE, ISSUED, USER_BASED, HOST_BASED, or SN appear. >= Version 6 START appears. >= Version 7.1 SIGN= keyword appears. >= Version 8 BORROW, FLOAT_OK, and TS_OK appear. Version Summary v1.0—1988 First FLEXlm Release, containing all the basic FLEXlm features v1.5—February 1990 First widely used version including DEMO v2.1—March 1991 • Improved TIMEOUT support • Improved ethernet hostid support v2.
Appendix H - FLEXnet Licensing Versions Version Summary • Added multiple jobs for enhanced support of LM_LICENSE_FILE environment variable as a license-file list • New, optional license file format with keyword=value syntax for optional new features, including: asset_info, ISSUER, and NOTICE, “ \ ” license file continuation character, 2048 character limit per feature v4.
Appendix H - FLEXnet Licensing Versions Version Summary • • • • • • • • • • • • • • • FLEXlm license directory support: *.
Appendix H - FLEXnet Licensing Versions Version Summary • SIGN= keyword in license • lmnewlog utility (v7.1+ vendor daemon) v7.2—December 2000 • Performance enhancements v8.0—October 2001 • lmborrow (v8.0+ components), lmpath (v8.0+ vendor daemon), lmswitch (v8.0+ vendor daemon) utilities • lmreread rereads end-user options file and SERVER host name • License borrowing with BORROW keyword v8.1—January 2002 • CRO Security enhancements v8.2—August 2002 • Support added for Windows XP compliancy v8.
Appendix H - FLEXnet Licensing Versions Version Summary 146 FLEXnet Licensing End User Guide
Index A about this manual ix ANY hostid 103 asset_info 113 B BORROW_LOWWATER 50 borrowing 96 C commands x COMPOSITE hostid 103 concurrent license 26 configuring FLEXnet licensing files 19 conventions x converting license formats 81 creating options file 45 D DAEMON line 108 debugging license server 119 DEBUGLOG 50 decimal format licenses 81 DEMO hostid 103 deployed FLEXnet Licensing files FLEXid drivers 18 lmgr10.dll 18 lmgrd 17 lmtools.
FEATURE line 109 asset_info 113 dist_info 113 DUP_GROUP 111 expiration date 110 feature version 109 FLOAT_OK 111 HOST_BASED 111 HOSTID 111 ISSUED 111 ISSUER 111 license count 110 NOTICE 112 order of precedence 113 OVERDRAFT 112 PLATFORMS 112 serial number 112 SIGN 110 signature 110 SN 112 sort 113 sorting order 113 START 112 SUPERSEDE 112 syntax 114 TS_OK 112 USER_BASED 112 user_info 113 vendor daemon name 109 vendor_info 113 VENDOR_STRING 112 Feature line SUITE_DUP_GROUP 112 FLEXid with FLOAT_OK 94 flexid.
ISSUED 111 ISSUER 111 L license borrowing 96 concurrent 26 floating 26 mixed 27 mobile 93 network license 26 node-locked 26 license count 110 license directory 67, 68 license file compatibility between different versions 36 DAEMON line 108 decimal format 117 expected location 16 FEATURE line 109 format 25 how to combine 35 INCREMENT line 109 LM_LICENSE_FILE 16 lminstall 81 order of lines 27, 118 overview 16 PACKAGE line 114 rereading after an update 85 SERVER lines 36 specifying location 23 types 26 UPGRAD
lmreread restricting access 66 syntax 85 lmstat output for lmreread 86 syntax 86 lmswitch, syntax 88 lmswitchr, syntax 89 LMTOOLS 18, 90 lmutil lmdiag 78 lmdown 79 lmhostid 80 lminstall 81 lmnewlog 82 lmremove 84 lmreread 85 lmstat 86 lmswitch 88 lmswitchr 89 lmver 90 lmver, syntax 90 M MAX 57 MAX_BORROW_HOURS 58 MAX_OVERDRAFT 58 memory usage, daemons 40 mixed licenses 27 mobile licensing borrowing 96 FLEXid with FLOAT_OK 94 node-locked to FLEXid 93 node-locked to laptop 93 node-locked to user name 99 prep
P PACKAGE line 114 OPTIONS=SUITE 115 OPTIONS=SUITE_RESERVED 115 syntax 115 package suite 115 PLATFORMS 112 port number server default range 106 SERVER line 106 VENDOR line 108 precedence or FEATURE lines 113 preface ix PROJECT type 49 R redundant servers selecting server nodes 41 separate license files 66 SERVER lines 106 three-server redundancy 42 via license-file list 41 rehosting, license 93 remote disks, guidelines for using 40 report log file 40 reporting on project 59 REPORTLOG 59 RESERVE 60 restrict
V vendor daemon and redundant servers 67 debug log file 136 lmnewlog 82 lmreread 85 lmswitchr 89 memory usage 40 options file 46 overview 15 uncounted licenses 43 VENDOR_LICENSE_FILE 124 version compatibility 65 vendor daemon name FEATURE line 109 VENDOR line 107 vendor daemon path 107 VENDOR line 107 options file path 108 port number 108 vendor daemon name 107 vendor daemon path 107 vendor.
