AST Licensing Guide

Edition 01/2013

© AVL List Gmbh 2009. All right reserved

LICENSING GUIDE VERSION 2013

Licensing Guide AST v2013

AVL LIST GmbH Hans-List-Platz 1, A-8020 Graz, Austria http://www.avl.com AST Local Support Contact: www.avl.com/ast-worldwide Revision Date Description Document No. A 21-Oct-2001 FLEXlm v7.2 17.0101.0445 B 15-Apr-2002 FLEXlm v8.1 17.0101.0446 C 03-Mar-2003 FLEXlm v8.4 17.0101.0447 D 17-May-2004 FLEXlm v8.4 17.0101.0448 E 29-Jul-2005 FLEXnet v10.1 17.0101.0449 F 31-May-2007 FLEXnet v10.8.5 17.0101.0450 G 26-Mar-2008 FLEXnet v10.8.5 17.0101.0451 H 17-Apr-2008 FLEXnet v10.8.5 17.0101.0452 I 16-Jun-2008 FLEXnet v10.8.5 17.0101.0453 J 09-Feb-2009 FLEXnet v10.8.5 17.0101.0454 K 30-Apr-2009 FLEXnet v11.6 17.0101.0455 L 30-Mar-2010 FLEXnet v11.6 17.0101.0456 M 30-Nov-2010 FlexNnet v11.6 17.0101.0457 N 28-Feb-2013 AST v2013 - FlexNnet v11.6 17.0101.0458 O 25-Jan-2013 AST v2013 - FlexNnet v11.10 17.0101.0459

Copyright © 2013, AVL

All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language, or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written consent of AVL.

This document describes how to install, maintain and administer the Globetrotter FlexNet software on your computer.

This software and document are distributed solely on an "as is" basis. The entire risk as to their quality and performance is with the user. Should either the software or this document prove defective, the user (and not AVL or its distributors) assumes the entire cost of all necessary servicing, repair, or correction. AVL and its distributors will not be liable for direct, indirect, incidental, or consequential damages resulting from any defect in the software or this document, even if they have been advised of the possibility of such damage.

http://www.avl.com/

http://www.avl.com/ast-worldwide


AST.17.0101.0458 – 25-Jan-2013 i

Table of Contents

1. Introduction _____________________________________________________ 1-1 1.1. Scope _______________________________________________________________________ 1-1 1.2. User Qualification ____________________________________________________________ 1-1 1.3. Symbols _____________________________________________________________________ 1-1 1.4. FlexNet Terms and Definitions ________________________________________________ 1-2 1.5. Software Components _________________________________________________________ 1-2 1.6. Configurations _______________________________________________________________ 1-2

2. General Information _____________________________________________ 2-1 2.1. Types of Licenses _____________________________________________________________ 2-1 2.2. Identify your License _________________________________________________________ 2-1 2.3. Workflows ___________________________________________________________________ 2-1 2.4. Requesting a License Key _____________________________________________________ 2-2

3. Installing the FlexNet Distribution ______________________________ 3-1 3.1. Installation __________________________________________________________________ 3-1 3.2. Binary Distribution Contents __________________________________________________ 3-1

4. Modify The License File _________________________________________ 4-1

5. License Server Setup ____________________________________________ 5-1 5.1. General _____________________________________________________________________ 5-1 5.2. Server Setup _________________________________________________________________ 5-1

6. First Application Start up – License Set up ______________________ 6-1 6.1. Windows ____________________________________________________________________ 6-1

6.1.1. Using the AVL License Definition Utility ____________________________________ 6-1 6.1.2. FlexNet License Finder ____________________________________________________ 6-2

6.2. Linux _______________________________________________________________________ 6-3 6.2.1. Configuring for Local Uncounted Licenses ___________________________________ 6-3 6.2.2. Configuring for Network Licenses __________________________________________ 6-3

7. Updating a License File __________________________________________ 7-1 7.1. Windows ____________________________________________________________________ 7-1

7.1.1. New Local Uncounted License ______________________________________________ 7-1 7.1.2. New License Server _______________________________________________________ 7-1 7.1.3. New Local Floating and Network License ____________________________________ 7-1

7.2. Linux _______________________________________________________________________ 7-3 7.2.1. New Local Uncounted License ______________________________________________ 7-3 7.2.2. New License Server _______________________________________________________ 7-3 7.2.3. New Local Floating and Network License ____________________________________ 7-3

8. Additional License File __________________________________________ 8-1 8.1. Merging License Files _________________________________________________________ 8-1 8.2. Windows ____________________________________________________________________ 8-2

AST v2013 Licensing Guide

ii AST. 17.0101.0458 – 25-Jan-2013

8.2.1. Additional Local Uncounted License File ____________________________________ 8-2 8.2.2. Additional Local Floating or Network License File ____________________________ 8-2

8.3. Linux _______________________________________________________________________ 8-2 8.3.1. Additional Local Uncounted License File ____________________________________ 8-2 8.3.2. Additional Local Floating or Network License File ____________________________ 8-3

9. Software License Utility Programs ______________________________ 9-1 9.1. lmadmin Usage ______________________________________________________________ 9-1 9.2. lmgrd Usage _________________________________________________________________ 9-1 9.3. The lmstat Utility ____________________________________________________________ 9-2

10. End-User Administration Tools _______________________________ 10-1 10.1. lmdown ___________________________________________________________________ 10-1 10.2. lmhostid___________________________________________________________________ 10-1 10.3. lmreread __________________________________________________________________ 10-2 10.4. lmremove _________________________________________________________________ 10-3 10.5. lmcksum __________________________________________________________________ 10-3 10.6. lmdiag ____________________________________________________________________ 10-4


AST.17.0101.0458 – 25-Jan-2013 iii

List of Figures Figure 2-1: License Request Window ................................................................................................ 2-2 Figure 4-1: Example of a License File ............................................................................................... 4-1 Figure 5-1: AST Launcher ................................................................................................................. 5-2 Figure 5-2: Product Licensing ........................................................................................................... 5-2 Figure 5-3: lmadmin Dashboard ........................................................................................................ 5-3 Figure 5-4: lmadmin Firewall Confirmation ..................................................................................... 5-3 Figure 5-5: Vendor Daemon Configuration ....................................................................................... 5-4 Figure 5-6: Import License................................................................................................................. 5-5 Figure 5-7: avl Firewall Confirmation ............................................................................................... 5-5 Figure 5-8: Import Information ......................................................................................................... 5-6 Figure 5-9: Vendor Daemon Status ................................................................................................... 5-7 Figure 5-10: Vendor Daemon Administration ................................................................................... 5-8 Figure 6-1: License Path Window ...................................................................................................... 6-1 Figure 6-2: License Path Window ...................................................................................................... 6-2 Figure 7-1: Vendor Daemon Administration ..................................................................................... 7-2 Figure 8-1: License File Structure ..................................................................................................... 8-1


25-Jan-2013 1-1

1. INTRODUCTION

Note: Detailed information on Globetrotter FlexNet is available in the manuals delivered with the FlexNet installation. Refer to Section 3.2.2 for their location.

FlexNet allows software licenses to be available (or float) anywhere on a network, instead of being tied to specific machines. Floating licensing benefits both users and license administrators. Users can make more efficient use of fewer licenses by sharing them on the network. License administrators can control the usage of the licensed application and the node(s) where the licenses will be available.

1.1. Scope This manual describes how to install and configure FlexNet to run applications using FlexNet. Information is provided about FlexNet with which the user can install software packages for different licenses for a specified number of users on a single computer or a specified number of users in a network.

This guide is for administrators and the end-user of AVL-AST software applications.

1.2. User Qualification Users of this manual must be experienced in Windows and/or LinuxNetwork basics.

1.3. Symbols The following symbols are used throughout this manual. Safety warnings must be strictly observed during operation and service of the system or its components.

Caution: Cautions describe conditions, practices or procedures which could result in damage to, or destruction of data if not strictly observed or remedied.

Note: Notes provide important supplementary information.

Convention Meaning

Italics For emphasis, to introduce a new term.

monospace To indicate a command, a program or a file name, messages, input / output on a screen, file contents or object names.


1-2 25-Jan-2013

MenuOpt A MenuOpt font is used for the names of menu options, submenus and screen buttons.

1.4. FlexNet Terms and Definitions The following terms are used to describe FlexNet components:

License Manager Daemon

The license manager daemon (lmgrd) handles the initial contact with the client application programs, passing the connection onto the appropriate vendor daemon. It also starts and restarts the vendor daemons.

Vendor Daemon In FlexNet, licenses are granted by running processes (unless they are node-locked, uncounted licenses, in which case they only need read the license file to run). There is one process for each vendor who has a FlexNet-licensed product on the network. This process is called the vendor daemon.

License File Licensing data is stored in a text file called the license file. The license file is created by the software vendor, edited and installed by the license administrator.

Application Program

The application program using FlexNnet is linked with the program module (the FlexNet client library) that provides the communication with the license server. During execution, the application program communicates with the vendor daemon to request a license.

1.5. Software Components The components in FlexNet are:

• The License Manager Daemon lmadmin

• The Vendor Daemon avl

• The End-user license administration tools (lmutil, lmhostid, lmstat, lmdiag, lmcksum, lmdown, lminstall).

1.6. Configurations The typical configuration of FlexNet consists of:

• The license file (default <AST_INSTALLATION_DIR>/license/license.dat)

• lmadmin (Linux), lmadmin.exe (Windows)

• avl (Linux), avl.exe (Windows)

• The application software


25-Jan-2013 2-1

2. GENERAL INFORMATION The supported platforms are described in the Installation Guide. If you have any license related questions or problems, please send an email to [email protected].

2.1. Types of Licenses 1. Local Uncounted License

This is uncounted and does not require a server (usually demo keys).

2. Local Floating License This is counted and usage is limited to one machine.

3. Network License This is counted and uses a server.

2.2. Identify your License Open the license file and check if the SERVER & DAEMON lines (Figure 4-1) exist.

YES NO

Check if the system ID appears more than once in the license file. If YES it’s a Local Floating License. If NO it’s a Network License.

It’s a Local Uncounted License.

2.3. Workflows Local Uncounted License Local Floating & Network License

Installing a New License File

License Request Before running the software for the first time, a license key is required (see section 2.4).

First Application Start up – License Set up Windows / Linux (see section 6).

License Request Before running the software for the first time, a license key is required (see section 2.4).

Modify License File Change host name, installation directory and platform to fit to your installation. Also change server and daemon lines (see section 4).

License Server Setup Windows / Linux (see section 5).

First Application Start up – License Set up Windows / Linux (see section 6).

Updating a License File

After receiving an updated license file, replace the existing file. The license file does not need to be modified. Alternatively adjust the Vendor path (see section 7).

After receiving an updated license file, replace the existing file and refer to the steps in section 7.

mailto:[email protected]


2-2 25-Jan-2013

Additional License File

If AWS, CRUISE, FIRE or CONCERTO software need to be installed on the same machine/server, the existing license file needs to be merged with the additional file (see section 8).

2.4. Requesting a License Key If you have not received a license key, request one from your local representative or from AVL Graz - [email protected]. Please include the following information:

• Software Product

• Name

• Telephone, Fax, E-Mail address

• Company

• System ID

Local installation: on every computer where the AVL software should be used

Network installation: on the license server computer

• Installation Type (Node locked, Network)

The above information can be obtained in the License Definition utility. In the AST launcher select AST | Product Licensing, then select the License Request tab which contains the necessary information. Please complete the template text and send it to AVL.

Figure 2-1: License Request Window

mailto:[email protected]


25-Jan-2013 3-1

3. INSTALLING THE FLEXNET DISTRIBUTION

3.1. Installation The AST Installer automatically installs the FlexNet. The FlexNet component must be selected in the installers component view. The license manager program files are then transferred to the selected <InstallationPath> and placed beneath this directory as described in Binary Distribution Contents.

3.2. Binary Distribution Contents The FlexNet distribution sub-tree contains:

FLEXLM/<FLEXNET_VERSION>/manuals FlexNet PDF manuals FLEXLM/<FLEXNET_VERSION>/bin/bin.<PLATFORM> Binary executables FLEXLM/<FLEXNET_VERSION>/bin/bin.<PLATFORM>/lmadmin lmadmin binaries FLEXLM/<FLEXNET_VERSION>/bin/bin.<PLATFORM>/lmadmin/licenses/avl AVL license folder


25-Jan-2013 4-1

4. MODIFY THE LICENSE FILE The following figure is an example of a license file:

Figure 4-1: Example of a License File

If necessary, i.e. if the license you have received contains placeholders for the hostname of the license server or for the path to the vendor daemon, modify your license file according to the description below:

Modify the SERVER line by entering your local computer name for the hostname_of_flexlm_server.

Modify the DAEMON line by setting the path to the avl vendor daemon. Default paths are:

Windows <install>\FLEXLM\vx.x\bin\bin.<platform>\avl.exe Linux <install>/FLEXLM/vx.x/bin/bin.<platform>/avl

Note: If the directory name contains a blank you must use quotation marks, e.g.: DAEMON avl "C:\Program Files\AVL\license\avl.exe"

Note: Do not use the directory C:\flexlm\avl or C:\flexlm to store the files. This results in errors from FLEXlm. Generally no file or sub directory with the name avl should exist in C:\flexlm.


25-Jan-2013 5-1

5. LICENSE SERVER SETUP 5.1. General

Starting with FLEXNet Version 11.10 a new license manager daemon, lmadmin, has been introduced enhancing the previous manager, lmgrd.

Although lmgrd is still available as command line tool, lmadmin offers the same command line interface but also a web interface allowing to configure license servers remotely and platform independently.

Note: See the lmadmin Migration document (fnp_lmadmin_migration_FAQ.pdf) in the manuals folder of the FLEXNet installation for the most common migration questions.

5.2. Server Setup To setup the FLEXnet license server you should either use your preferred web browser to connect to the license server website (in case it is already running), or you can use the AVL license definition utility to start a local instance of the lmadmin.

Note: You must have write privileges on the installation folder (or at least the FLEXLM folder) to ensure the license manager can store its configuration and log data!

After the received license file has been modified (see section 4) proceed with the following steps:

1. Copy the vendor daemon in the lmadmin binary folder (see section 3.2) of the FlexNet installation if not already automatically done during the installation.

2. Start the license definition utility by opening the AST Launcher and select the Product Licensing menu entry within the common AST section.


5-2 25-Jan-2013

Figure 5-1: AST Launcher

3. The License Administration button on the bottom of the Product Licensing window starts a lmadmin process and opens the default web browser displaying its web site.

Figure 5-2: Product Licensing


25-Jan-2013 5-3

Figure 5-3: lmadmin Dashboard

If starting lmadmin the first time, on MS Windows, it might be necessary to allow the corresponding process to pass the Windows Firewall.

A confirmation dialog as shown below asks for the permission to communicate through the Windows Firewall.

Figure 5-4: lmadmin Firewall Confirmation


5-4 25-Jan-2013

Select whether you only want to allow that within private networks (suggested) or also in public networks by checking the corresponding check boxes and click the Allow access button.

4. Switch from the Dashboard into the Administration mode by clicking Administration in the upper right corner of the web site.

When asked for login credentials you should be able log in with the default administration user admin with its password admin.

Note: The first time you are logging in you will have to specify a new password.

5. Open the vendor daemon configuration by clicking the bottom horizontal tab on the left side.

Figure 5-5: Vendor Daemon Configuration

6. You can add a new license by clicking the Import License button and either enter the fully qualified path to the license file or use the Browse functionality to select the license file you want to add.


25-Jan-2013 5-5

Please make sure you check the Overwrite License File on License Server checkbox to ensure the selected license is used!

Figure 5-6: Import License

Confirm and apply your selection by clicking the Import License button.

On MS Windows an additional confirmation dialog, as shown below, might ask for the permission to let the AVL vendor daemon communicate through the Windows Firewall.

Figure 5-7: avl Firewall Confirmation


5-6 25-Jan-2013

7. An information site should be loaded reporting the status of the license import.

Figure 5-8: Import Information

If the license import was successful the license server and the vendor daemon should already be running and after confirming the Import Information by clicking the OK button you should see it in the list of vendor daemons.


25-Jan-2013 5-7

Figure 5-9: Vendor Daemon Status

You can manage the vendor daemon by clicking the Administer link in the vendor daemon line where you e.g. can stop and start the vendor daemon.


5-8 25-Jan-2013

Figure 5-10: Vendor Daemon Administration

To register the lmadmin License Server Manager as on operating system service please consult the License Admintration Guide (fnp_LicAdmin.pdf) provided by FlexNet located in the FLEXNet manuals folder.

In this document you can also find detailed explanations on the available command line options allowing to do all described configuration steps also from the command line.


25-Jan-2013 6-1

6. FIRST APPLICATION START UP – LICENSE SET UP If a License Failure message appears instead of Figure 6-1, then an AVL license file exists - refer to chapter 8.

6.1. Windows The license file to be used can be defined during the installation process, via the AVL License Definition Utility or via the FlexNet License Finder. All three possibilities operate on the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\AVL_LICENSE_FILE

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FLEXlm License Manager\AVL_LICENSE_FILE (relevant for 32 bit executables on 64 bit machines)

6.1.1. Using the AVL License Definition Utility To edit the license configuration start the AST launcher and then select AST | Product Licensing.

Figure 6-1: License Path Window

For adding or removing license sources click the “+” or “-“ toolbar icon and specify the required information in the following dialog.


6-2 25-Jan-2013

Figure 6-2: License Path Window

6.1.2. FlexNet License Finder The FlexNet License Finder (Figure 6-1) will appear if an application is started for which no valid license file definition exists.

Figure 6-3: License Finder – Specify Window

The following options are available:

1. Select Specify the License Server System and then in the following figure enter the server name on which the license manager daemon is running.

2. Select Specify the License File and then in the following figure enter the location of the license file or find the location using Browse.

Figure 6-4: License Finder Window


25-Jan-2013 6-3

6.2. Linux

6.2.1. Configuring for Local Uncounted Licenses When the application is started, the license file is searched for a valid local license entry, which allows the application to start.

The license file default is <InstallationPath>/license/license.dat. This default can be overwritten by the end-user setting the environment variable AVL_LICENSE_FILE to the file name including the path.

(t)csh: setenv AVL_LICENSE_FILE <path>/<filename> (ba)sh: AVL_LICENSE_FILE=<path>/<filename>

export AVL_LICENSE_FILE

Example 1:

$ cp <license_file> <AST_INSTALLATION_DIR>/license/license.dat

$ start_your_application

Example 2:

If the default path is not used for the license file, the following line will locate the license file for the application:

$ setenv AVL_LICENSE_FILE <path>/<filename>

Start the application:


To define multiple local licenses, extend the environment variable by a colon separated list of locations:

setenv LM_LICENSE_FILE <path1>/<filename1>:<path2>/<filename2>:...

6.2.2. Configuring for Network Licenses When the application is started, the license file is parsed for the server entry, containing the server host name and the server hostid, and for the vendor entry specifying name and location of the vendor daemon. The application connects to the server specified in the license file, to retrieve a network license, which allows the application to start.

Specify the location of the license file OR a port@server statement, which contains the network license, so that the application can find it.

Set the environment variable AVL_LICENSE_FILE to the correct location:

$ setenv AVL_LICENSE_FILE <path>/<filename>

$ setenv AVL_LICENSE_FILE <port>@<server>


6-4 25-Jan-2013

Start the application:


To define multiple license locations, extend the environment variable by a colon separated list of locations:

setenv LM_LICENSE_FILE <path1>/<filename1>:<path2>/<filename2>:...

Note: The environment variable can hold license settings for local and network licenses. Therefore a license setup for local and network license can look like this:

setenv LM_LICENSE_FILE <path1>/<filename1>:<port1>@<server1>:...


25-Jan-2013 7-1

7. UPDATING A LICENSE FILE

7.1. Windows

7.1.1. New Local Uncounted License After receiving an updated license file, replace the existing file. The license file does not need to be modified.

If you do not want to replace the existing file, then use the Product Licensing tool to update your license sources (see section 6.1.1).

7.1.2. New License Server If you have a new license server, use the Product Licensing tool to update your license sources (see section 6.1.1).

The correct syntax for a license server named test would be @test and has to be specified in the path textbox.

7.1.3. New Local Floating and Network License After receiving an updated license file, replace the existing file

1. Modify the license file (see section 4).

2. Open the lmadmin web interface and switch to the detailed vendor daemon settings, e.g. by browsing to http://localhost:8090/vendor:

http://localhost:8090/vendor


7-2 25-Jan-2013

Figure 7-1: Vendor Daemon Administration

3. Click the Reread License File button to retrieve the new license file information

If you do not want to replace the license file:

1. Modify the new license file (see section 4).

2. Open the lmadmin web interface and switch to the detailed vendor daemon settings, e.g. by browsing to http://localhost:8090/vendor (see Figure 7-1)

3. Specify the license file path in the License File or Directory textbox

4. Click the Save button to apply the changed settings.


For changing the vendor daemon location you can do the same thing by providing the vendor daemon location in the Vendor Daemon Location texbox.



25-Jan-2013 7-3

7.2. Linux

7.2.1. New Local Uncounted License After receiving an updated license file, replace the existing file. The license file does not need to be modified.

If you do not want to replace the existing file, update the Vendor name and path.

The license file default is <InstallationPath>/license/license.dat. This default can be overwritten by the end-user setting the environment variable AVL_LICENSE_FILE to the file name including the path.

(t)csh: setenv AVL_LICENSE_FILE <path>/<filename> (ba)sh: AVL_LICENSE_FILE=<path>/<filename>


7.2.2. New License Server Set the environment variable AVL_LICENSE_FILE to the correct location:

$ setenv AVL_LICENSE_FILE <port>@<server>

7.2.3. New Local Floating and Network License After receiving an updated license file, replace the existing file

4. Modify the license file (see section 4).



If you do not want to replace the license file:

6. Modify the new license file (see section 4).


8. Specify the license file path in the License File or Directory textbox

9. Click the Save button to apply the changed settings.


For changing the vendor daemon location you can do the same thing by providing the vendor daemon location in the Vendor Daemon Location texbox.




25-Jan-2013 8-1

8. ADDITIONAL LICENSE FILE After receiving an additional AVL license file there are two options for the required setup:

• To add an additional local license file it is necessary to adjust the relevant variables and settings as described in section 8.2.1 for Windows and section 8.3.1 for Linux.

• Alternatively and for local floating and network licenses it is necessary to merge the new license file into the existing one, resulting in one common AVL license file (see section 8.2.2 for Windows and section 8.3.2 for Linux).

8.1. Merging License Files Generally local floating and network licenses consist of two parts (as shown in Figure 8-1). The header part (H) contains the SERVER and DAEMON line, specifying the license server and the vendor daemon. This part is unique and must only exist once in a license file. The rest of the license file, the body (B), contains the different license keys. Its length depends on the amount of license products covered in the body.

Figure 8-1: License File Structure

Merging two license files is the process of combining two different license files of the same type (local floating or network license) in such a way that the resulting license file consists of one common header, preferably taken from the first, already existing license file, plus the body part of one license file in succession to the body of the other license file.


8-2 25-Jan-2013

Figure 8-2: License Merge

8.2. Windows

8.2.1. Additional Local Uncounted License File Use the Product Licensing tool to update your license sources (see section 6.1.1).

8.2.2. Additional Local Floating or Network License File After the license files have been merged (see section 8.1) update the server’s license file as described in section 7.1.3.

8.3. Linux

8.3.1. Additional Local Uncounted License File To add an additional local uncounted license file for Linux the environment variable AVL_LICENSE_FILE has to be modified.

(t)csh: setenv AVL_LICENSE_FILE <path>/<filename>

or (in case AVL_LICENSE_FILE is already set)

setenv AVL_LICENSE_FILE <path>/<filename>:$AVL_LICENSE_FILE

(ba)sh: AVL_LICENSE_FILE=<path>/<filename>



25-Jan-2013 8-3

or (in case AVL_LICENSE_FILE is already set)

AVL_LICENSE_FILE=<path>/<filename>:$ AVL_LICENSE_FILE


8.3.2. Additional Local Floating or Network License File After the license files have been merged (see section 8.1) update the server’s license file as described in section 7.2.3.


25-Jan-2013 9-1

9. SOFTWARE LICENSE UTILITY PROGRAMS

9.1. lmadmin Usage For a detailed listing of all available lmadmin command line arguments and available lmadmin command line use case, such as “Adding a Vendor Daemon to lmadmin” or “Installing lmadmin License Server Manager as an Operating System Service” please consult the License Admintration Guide (fnp_LicAdmin.pdf) provided by FlexNet located in the FLEXNet manuals folder.

9.2. lmgrd Usage Name lmgrd - FLEX license manager daemon.

Synopsis

lmgrd [-c license_file_list] [-l debug_log_path] [-2 –p] [-nfs_log] [-x lmdwon] [-x lmremove] [-z] [-v]

Description lmgrd is the main daemon program for FlexNet. When lmgrd is invoked, it looks for a license file which contains information about vendors and features. On Linux systems, it is strongly recommended that lmgrd be run as a non-privileged user (not root).

Options

-c license_file_list Uses the specified license file(s).

-l debug_log_path Writes debugging information to file debug_log. This option uses the letter l, not the numeral 1.

-2 -p

Restricts usage of lmdown, lmreread, and lmremove to a FlexNet administrator who is root by default. If there is a Linux group called lmadmin, then use is restricted to 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. If -2 -p is used when starting lmgrd, no user on Windows can shut down the license server with lmdown.

-nfs_log

We do not recommend writing a debug log to an NFS-mounted or PC network-mounted disk. If you choose to write to a mounted disk and the speed of the license server is too slow, use this flag to cache debug info before it is written out (when approximately 1kb of data is reached).

-x lmdown Disables the lmdown command (no user can run lmdown). If lmdown is disabled, stop lmgrd via kill pid (Linux) or


9-2 25-Jan-2013

stop the lmgrd and vendor daemon processes through the Task Manager or NT Service (Windows). On Linux, ensure the kill command does not have a -9 argument. (v4+ lmgrd)

-x lmremove Disables the lmremove command (no user can run lmremove). (v4+ lmgrd)

-z

Runs in foreground. The default behavior is to run in the background. Windows: pre-v7, lmgrd always runs in the foreground. In v7+, lmgrd runs in the background by default. If -l debug_log_path is present, then no windows are used, but if no -l argument specified, separate windows are used for lmgrd and each vendor daemon.

-v Prints lmgrd version number and copyright and then exits.

9.3. The lmstat Utility Name lmstat - utility to show which licenses are already located in the license file. lmstat can be executed either by calling a lmstat executable directly, if existing, or by starting it in the form lmutil lmstat

Synopsis lmstat [-a] [-A] [-c license_file_list] [-f feature] [-s [vendor]]

Description The lmstat utility helps to monitor the status of all network licensing activities, including:

• Daemons that are running • Users of individual features • Users of features served by a specific vendor daemon

lmstat prints information that it receives from the license server, therefore it will not return any information about users of node-locked uncounted or DEMO licenses.

-a Displays information about used and available licenses.

-A Lists all active licenses.


-f [feature] Lists users of feature.

-S [vendor] Lists all users of vendor's features.


25-Jan-2013 9-3

The output of lmstat -a looks similar to: License server status: 27000@myhost1 License file(s) on myhost: /FlexNet/v8.4/sun4_u5/license.dat: myhost: license server UP (MASTER) v8.4 Vendor daemon status (on myhost1): demo: UP v8.4 Feature usage info: Users of f1: (Total of 4 licenses available) "f1" v1.0, vendor: demo floating license daniel myhost2 19.16.18.26 (v1.0) (myhost1/27000 102), start Fri 5/3 7:29

where:

daniel user User name.

Myhost2 user_host Host where user is running.

19.16.18.26 display Display where user is running.

v1.0 version Version of feature.

Myhost1 server_host Host where license server is running.

27000 port 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.


25-Jan-2013 10-1

10. END-USER ADMINISTRATION TOOLS The End-User Administration Tools provide information about license usage on your host or network and check in/check out licenses of applications, which are no longer running.

All license server utilities are packaged as a single executable called lmutil. The lmutil is either installed as individual commands (either by creating links to the individual command names, or making copies of lmutil as the individual command names), or as a wrapper that runs the individual command as lmutil command. For example, lmutil lmstat or lmutil lmdown.

On Windows systems, the lmutil <command> form of the commands are available.

10.1. lmdown Name lmdown - shutdown license daemons

Synopsis lmdown [-c license_file_list] [-vendor vendor] [-q] [-all]

Description The lmdown utility allows the shutdown of all license daemons (both lmgrd and all vendor daemons) on all nodes.

Option -c license_file_list Uses the specified license file(s).

-vendor vendor

Shuts down this vendor daemon only. lmgrd will always continue running if this option is specified. Requires v6.0 lmdown and lmgrd (the vendor daemon can be any version).

-q Does not prompt or print a header. Otherwise lmdown asks "Are you sure? [y/n]: ."

-all If multiple servers are specified, automatically shuts down all of them. Otherwise, only one is shutdown. -q is implied with -all. (v7+)

10.2. lmhostid Name lmhostid - displays the host ID of the system.


10-2 25-Jan-2013

Synopsis lmhostid [-n] [type] where type is one of: [-internet] (optional on all platforms) [-ether] (optional on HP)

Description The lmhostid utility reports the hostid of any machine whose platform is supported by FlexNet. The default hostid type is displayed for a platform, unless an optional hostid type is specified and supported by that platform.

Options

-n No header is printed, only the hostid is printed.

-internet IP address in ###.###.###.### format.

-vsn Volume Serial Number of the Windows C:\ drive.

The output of this command is as follows:

lmhostid - Copyright (c) 1989, 1997 Globetrotter Software, Inc. The FlexNet hostid of this machine is "69021c89"

10.3. lmreread Name lmreread - rereads the license file and starts any new vendor daemons that have been added.

Synopsis lmreread [-c license_file_list] [-vendor vendor] [-all]

Description The lmreread utility causes the license daemon to reread the license file and start any new vendor daemons that have been added. In addition, all running daemons will be signaled to reread the license file for changes in feature licensing information. If the optional vendor daemon name is specified, only the named daemon will reread the license file (in this case, lmgrd will not reread the license file).

Options


-vendor vendor

Only this one vendor daemon should reread the license file. lmgrd will restart the vendor daemon if necessary. Requires v6+ lmreread and lmgrd (the vendor daemon can be any version).

-all If more than one lmgrd is specified, instructs all lmgrds to reread. (v7+)


25-Jan-2013 10-3

10.4. lmremove Name lmremove – allows a single user’s license to be removed for a specified feature.

Synopsis lmremove [-c license_file_list] [-h] feature user user_host display

Description The lmremove utility allows a single user’s license to be removed for a specified feature.. This is only needed when a client node crashes, since that's the only condition where a license is not automatically freed. If the application is active, it will re-checkout the license after it is freed by lmremove.

Option

-c license_file_list Specifies license file(s).

Feature Name of the feature checked out by the user.

user Name of the user whose license is being removed, as reported by lmstat -a.

user_host Name of the host the user is logged into, as reported by lmstat -a.

Display Name of the display where the user is working, as reported by lmstat -a.

Server_host Name of the host on which the license server is running.

port Port number where the license server is running, as reported by lmstat -a.

Handle License handle, as reported by lmstat -a.

The user, user_host, display, server_host, port, and handle information must be obtained from the output of lmstat -a.

10.5. lmcksum Name lmcksum – perform a checksum of a license file

Synopsis lmcksum [-k] [-c license_file_path]


10-4 25-Jan-2013

where -c license_file_path designates the license file to checksum. By default, lmcksum uses license.dat in the current directory (unlike other lmutil commands). Specify -c license_file_path to checksum another license file.

Description The lmcksum program (FlexNet v2.4 or later) will perform a checksum of a license file. This is useful to verify data entry errors at your location. lmcksum will print a line-by-line checksum for the file as well as an overall file checksum. lmcksum takes the -k switch to force the encryption key checksum to be case-sensitive.

lmcksum will ignore all fields that do not enter into the encryption key computation; thus the server node name and port number, the vendor daemon and options file paths, and lowercase keyword=value pairs on FEATURE/INCREMENT lines are not checksummed. In addition, lmcksum will treat non-case-sensitive fields correctly (in general, lmcksum is not case sensitive).

Example output is:

lmcksum--Copyright (C) 1989, 1997 GLOBEtrotter Software, Inc. lmcksum: using license file "/a/b/xyzd/licenses/license.dat189: SERVER speedy 08002b32b161 2837 189: SERVER speedy 08002b32b161 2837 166: DAEMON xyzd C:\FlexNet\xyzd.exe 8: INCREMENT f1 xyzd 1.000 01-jan-2005 0 3B2BC333A0BF OK: 231: INCREMENT f2 xyzd 1.0 01-jan-0 1 8B1C3001535E \ DUP_GROUP=HD ck=231 109: (overall file checksum)

10.6. lmdiag Name lmdiag – diagnoses problems when a license cannot be checked out.

Synopsis lmdiag [-c license_file_list] [-n] [feature[:keyword=value]]

Description If no feature is specified, lmdiag will operate on all features in the license file(s) in your list. lmdiag will first print information about the license, then attempt to check out each license. If the checkout succeeds, lmdiag will indicate this. If the checkout fails, lmdiag will give the reason for the failure. If the checkout fails because lmdiag cannot connect to the license server, then there is the option of running "extended connection diagnostics".

These extended diagnostics attempt to connect to each port on the license server node, and can detect if the port number in the license file is incorrect. lmdiag will indicate each port number that is listening, and if it is an lmgrd process, lmdiag will indicate this as well. If lmdiag finds the vendor daemon for the feature being tested, then it will indicate the correct port number for the license file to correct the problem.


25-Jan-2013 10-5

Option -c license_file_list Diagnoses the specified file(s).

-n Runs in non-interactive mode; lmdiag will not prompt for any input in this mode. In this mode, extended connection diagnostics are not available.

Feature Diagnoses this feature only.

Keyword=value

If a license file contains multiple lines for a particular feature, select a particular line for lmdiag to report on. For example: lmdiag f1:HOSTID=12345678 will attempt a checkout on the line with the hostid "12345678." keyword can be one of the following: VERSION, HOSTID, EXPDATE, KEY, VENDOR_STRING, ISSUER

Documents

AST Licensing Guide