AVL AST LicensingUsersGuide

AVL-AST Licensing Users Guide

Version 10.8.5

May 2007

Users Guide FLEXnet Version 10.8.5

AVL LIST GmbH Hans-List-Platz 1, A-8020 Graz, Austria http://www.avl.com AST Local Support Contact: www.avl.com/ast_support

Revision Date Description Document No. A 21-Oct-2001 FLEXnet v7.2 17.0101.0445 B 15-Apr-2002 FLEXnet v8.1 17.0101.0446 C 03-Mar-2003 FLEXnet v8.4 17.0101.0447 D 17-May-2004 FLEXnet 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

Copyright © 2007, 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/


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 1.7. Supported Platforms__________________________________________________________1-3

2. Installing the FLEXnet Distribution _____________________________2-1 2.1. Installation __________________________________________________________________2-1 2.2. Binary Distribution Contents __________________________________________________2-1

3. Running the Application_________________________________________3-1 3.1. Configuring for Local Licenses _________________________________________________3-1 3.2. Configuring for Network Licenses______________________________________________3-3 3.3. Configuring for Local and Network Licenses ____________________________________3-4

4. License Manager Daemon________________________________________4-1 4.1. Starting the License Manager Daemon lmgrd____________________________________4-1 4.2. lmgrd _______________________________________________________________________4-4

5. Software License Utility Programs ______________________________5-1 5.1. The lmstat Utility ____________________________________________________________5-1

6. End-User Administration Tools __________________________________6-1 6.1. lmdown _____________________________________________________________________6-1 6.2. lmhostid_____________________________________________________________________6-1 6.3. lmreread ____________________________________________________________________6-4 6.4. lmremove ___________________________________________________________________6-4 6.5. lmcksum ____________________________________________________________________6-5 6.6. lmdiag ______________________________________________________________________6-6

AST.17.0101.0450 – 31-May-2007 i


1. INTRODUCTION

Note: Detailed information on Globetrotter FLEXnet is available in the manuals delivered with the FLEXnet installation. Refer to Section 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 NT and Unix Network 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 or for manual titles.

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

31-May-2007 1-1

FLEXnet Version 10.8.5 Users Guide

SCREEN-KEYS A SCREEN font is used for the names of windows and keyboard keys, e.g. to indicate that you should type a command and press the ENTER key.

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 FLEXnet 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 lmgrd

• 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)

• lmgrd (Unix), lmgrd.exe (Windows NT)

• avl (Unix), avl.exe (Windows NT)

• The application software

1-2 31-May-2007


1.7. Supported Platforms AVL supports the following platforms and compilers for the AVL Workspace v5.0.1:

Platform Fortran 90 Compiler C++ Compiler

INTEL Architecture (32-bit)

MS Windows XP Pro SP2

Intel Fortran 9.1.024

MS VC++ 2003 Pro

INTEL Architecture (32-bit) Linux RH 9 + RHEL 3 update 6 + SuSE 9.x + SLES 9 +

used for builds: RHEL 3 update 7

Intel Fortran v9.1.032 Intel C++ 9.1.038

LINUX Kernel v2.4 glibc 2.3.x

INTEL EM64T and AMD64 Architecture (64-bit) Linux RHEL 3 + SLES 9 +

used for builds: SLES 9 update 2

PGI Fortran 6.0-8

GCC 3.3.3


INTEL Itanium (64-bit)1)

Linux RHEL 3 SLES 9

Intel Fortran v9.1.032 Intel C++ 9.1.038


HP PA-RISC 2.0 HP-UX 11.11

HP F90 v2.9 HP aC++/C B3910B A.03.60

IBM RS 6000 Power 3 + AIX 5.1 AIX 5.2

XL Fortran Compiler 8.1 VisualAge C++ 6.0 built with vacpp.cmp.core 6.0.0.9 use xlC.aix50.rte 6.0.0.9 or higher

1) can be executed also on SGI Aetix Pro Pack 3 and 4 RH – Red Hat RHEL – Red Hat Enterprise Linux SLES – SuSE Linux Enterprise Server

31-May-2007 1-3


2. INSTALLING THE FLEXNET DISTRIBUTION

2.1. Installation UNIX

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.

Windows NT

The FLEXnet is automatically installed. The files will be transferred to the <InstallationPath> described in Binary Distribution Contents.

2.2. Binary Distribution Contents UNIX

The FLEXnet distribution sub-tree contains:

FLEXNET/bin General FLEXnet startup scripts FLEXNET/<FLEXNET_VERSION>/bin Version-dependent FLEXnet scripts FLEXNET/<FLEXNET_VERSION>/man FLEXnet PDF manuals FLEXNET/<FLEXNET_VERSION>/ bin.<PLATFORM>

Binary executables

Windows NT

The FLEXnet distribution sub-tree contains:

FLEXNET\<FLEXNET_VERSION>\bin Binary executables FLEXNET\<FLEXNET_VERSION>\ manuals

FLEXnet PDF manuals

31-May-2007 2-1


3. RUNNING THE APPLICATION

3.1. Configuring for Local Licenses UNIX

A local license restricts the use of the application to a specified number of users on a single computer (node locked license). For local licensing, no server is required.

Requirements:

• The application binary

• The license file

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 LM_LICENSE_FILE to the file name including the path.

csh: setenv LM_LICENSE_FILE <path>/<filename>

sh: LM_LICENSE_FILE=<path>/<filename>

export LM_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 LM_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>:...

31-May-2007 3-1


Windows NT

A default location for the license file does not exist. Start an application requiring a license and the FLEXnet License Finder (as shown in the following figure) will specify the license location. The following options are available:

1. Specify a license server and then in the following figure enter the server name on which the license manager daemon is running.

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

Figure 3-1: License Finder Window

The license files location can be specified manually by setting the environment variable LM_LICENSE_FILE to the directory which contains the file.

Execute the following

$ set LM_LICENSE_FILE=<path>\<filename>



The license file settings can be specified using the LMTOOLS program. This program is delivered with the FLEXnet installation and is located beneath the binary executable directory. Alternatively select START -> Programs -> AVL -> License and then select the License Utilities link.

After the program has started, select the Service/License File tab. Select Configuration using license File and enter the license file location or find the location using Browse.

3-2 31-May-2007


Figure 3-2: LMTOOLS – Service/License File Window

To define multiple local licenses, extend the environment variable or the list in the described dialog boxes by a semi-colon separated list of locations:

<path1>/<filename1>;<path2>/<filename2>;...

3.2. Configuring for Network Licenses UNIX

A network license restricts the use of the application to a specified number of users in a network (floating license) or to a specific computer in the network (node locked license). Network licensing requires a running server.

Requirements:

• The application binary

• The license file

• A running license server daemon

• The vendor daemon

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.

31-May-2007 3-3


Set the environment variable LM_LICENSE_FILE to the correct location:

$ setenv LM_LICENSE_FILE <path>/<filename>

$ setenv LM_LICENSE_FILE <port>@<server>



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

setenv LM_LICENSE_FILE

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

Windows NT

This is the same as described in Local Licenses.

In the Service/License File window (refer to Figure 3-2), the correct syntax for a license server named test would be @test.

3.3. Configuring for Local and Network Licenses To provide local and network licensing on your host, local and network licensing must be configured. In this case, extend the LM_LICENSE_FILE environment variable by specifying a colon separated list of license files or a port@server statement (skip the port for using the default value) on UNIX systems or use the license utilities on windows machines.

UNIX

Example:

Locate the license files for the application:

$ setenv LM_CONFIG_FILE

<path1>/<filename1>:1774@licserv1:@licserv2:<path2>/<filename2>

:...



Windows NT

Use the LMTOOLS program delivered with the FLEXnet installation, which is located beneath the binary executable directory to extend the list of FLEXnet license files. Alternatively select START -> Programs -> AVL -> License and then select the License Utilities link.

After the program has started, select the Service/License File tab, select Configuration using license File and enter the license file locations as a semi-colon separated list of license files and license servers. The correct syntax for a license server named test would be @test.

3-4 31-May-2007


Example 1:

In the text box of the license utility enter for example following:

@test;E:\Programme\AVL\license\license.dat

Example 2:

Another possibility is to set up the environment variable LM_LICENSE_FILE. Specify all desired license file locations and license servers:

Locate the license files and license servers for the application:

$ set

LM_CONFIG_FILE=<path1>\<filename1>;<path2>\<filename2>;@test1;@test2;

...

Start your application.


31-May-2007 3-5


4. LICENSE MANAGER DAEMON

4.1. Starting the License Manager Daemon lmgrd Once the license file and the daemon are in place, the daemon can be started. It can be started manually (refer to examples 1 - 3) or it can be conveniently started in /etc/rc.boot, /etc/rc, /sbin/rc2.d or /etc/rc2.d, depending on the operating system.

Note: FLEXnet does not require root privileges, therefore any user can start the FLEXnet daemon lmgrd.

Start the daemon from the command line as follows:

Example 1:

The LM_LICENSE_FILE environment variable is set up correctly

$ lmgrd

Example 2:

UNIX:

$ setenv LM_LICENSE_FILE <path>/<license_file>

Windows NT:

$ set LM_LICENSE_FILE=<path>\<filename>

$ lmgrd

Example 3:

$ lmgrd -c <path>/<license_file>

If the FLEXnet license daemon, lmgrd, is started in this way and the computer is rebooted, the started service will be stopped and will not be restarted. So these examples are good for testing FLEXnet’s functionality but not for normal use.

UNIX

To ensure the license manager is running, after a reboot, a startup script should be provided which is sourced every time the system is booted to start the lmgrd service and is also executed when the computer is shut down to stop the running license manager service.

31-May-2007 4-1


An example script is:

#!/bin/sh

avl_licdir=<ENTER_INSTALLATION_DIRECTORY_HERE>

avl_licfile_dir=<ENTER_LICENSEFILE_DIRECTORY_HERE>

case "$1" in

'start')

$avl_licdir/lmgrd -c $avl_licfile_dir/license.dat -l $avl_licfile_dir/license.log

;;

'stop')

$avl_licdir/lmdown -q -c $avl_licfile_dir/license.dat -vendor avl

;;

*)

echo "usage: $0 {start|stop}"

;;

esac

This script should be modified to let the license manager know where the license files and the FLEXnet executables can be found. Therefore replace <ENTER_INSTALLATION_DIRECTORY_HERE> with the installation directory specified at installation time and replace <ENTER_LICENSEFILE_DIRECTORY_HERE> with the path to the directory where the license is placed. This should be a directory which resides locally on the license server and not on an NFS-mounted file-system. A commonly used choice is /opt/FLEXnet.

The license file must be modified as follows:

The second line in the license file should begin with VENDOR avl followed by a path specifying the location of the FLEXnet vendor daemon. Modify this path so that it specifies the path containing the vendor daemon. The default location for this file depends on the selected installation directory and the platform on which the license manager should run.

The vendor daemon can be found in: <InstallationPath>/FLEXNET/<FLEXNET_VERSION>/bin.<PLATFORM>

To automatically run this script during the boot and shut down sequence, copy the file to a special location for startup scripts and create a symbolic link.

These steps depend on the operating system architecture, an example is:

Create the script /sbin/init.d/avlFLEXnet or /sbin/init.d/avlFLEXnet and insert the lines shown above.

Create a link to locate the script for the operating system at boot-time: $ ln -s /etc/init.d/avlFLEXnet /etc/rc2.d/S99avlFLEXnet

or $ ln -s /etc/init.d/avlFLEXnet /etc/init.d/rc2.d/S99avlFLEXnet

or $ ln -s /sbin/init.d/avlFLEXnet /sbin/rc2.d/S99avlFLEXnet

4-2 31-May-2007


After these operations the FLEXnet license manager should start automatically after the next reboot.

Windows NT

A startup script is not required to start or stop the FLEXnet license manager. The license tools collected in lmtools can be used to specify the lmgrd service.

Select START -> Programs -> AVL -> License and then select the License Utilities link.

As shown in Figure 3-2, select the Service/License File tab and then select Configuration using Services to activate the Configure Services tab. Select the Configure Services tab and enter the relevant data as shown in the following figure.

Figure 4-1: LMTOOLS – Configure Services Window

Select Use Service and Start Server at Power Up.

Click Save Service to save the settings and confirm with Yes.

The license manager daemon should be set up and ready for use.

31-May-2007 4-3


4.2. lmgrd 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 UNIX systems, it is strongly recommended that lmgrd be run as a non-privileged user (not root).

Options

{PRIVATE}-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 UNIX 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 NT 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 (UNIX) or stop the lmgrd and vendor daemon processes through the Task Manager or NT Service (Windows). On UNIX, 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)

4-4 31-May-2007


-z

Runs in foreground. The default behavior is to run in the background. Windows NT: 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.

31-May-2007 4-5


5. SOFTWARE LICENSE UTILITY PROGRAMS

5.1. The lmstat Utility Name lmstat - utility to show which licenses are already located in the license file.

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.

{PRIVATE}-a Displays information about used and available licenses.

-A Lists all active licenses.

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

-f [feature] Lists users of feature.

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

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

31-May-2007 5-1


where:

{PRIVATE} 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.

5-2 31-May-2007


6. 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.

6.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 {PRIVATE} -c license_file_list


-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+)

6.2. lmhostid Name almhostid - displays the host ID of the system.

Synopsis lmhostid [-n] [type]

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

31-May-2007 6-1


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

{PRIVATE}-n No header is printed, only the hostid is printed.

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

-vsn Volume Serial Number of the Windows NT 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"

Expected FLEXnet Hostids

The program lmhostid will print the exact hostid that FLEXnet expects to use on any given machine. The following table lists alternate methods to obtain the required hostid for each machine architecture. FLEXnet also supports a group of special hostids and vendor-defined hostids.

6-2 31-May-2007


Hardware Platform Hostid Type this command on the license

server: Example

AIX (RS/6000, PPC)

32-bit hostid

uname -m (returns 000276513100), then remove last two digits and use remaining last eight digits

02765131

DEC Alpha ethernet address

netstat -i 080020005532

32-bit hostid

uname -i and convert to hex, or prepend with #

778DA450 or #2005771344

HP ethernet address

lanscan (station address without leading "0x") 0000F0050185

Linux Composite Hostid

$AVLAST_HOME/bin/lmcomposite COMPOSITE= C25C48BF77F9

SCO Hostid String

uname -x (Serial is SCO00354), then prefix with "ID_STRING="

ID_STRING= SCO00354

SGI 32-bit hostid

/etc/sysinfo -s, convert to hex, or prefix #

69064C3C or #1762020412

SUN 32-bit hostid

hostid 170a3472

Composite Hostid

FLEXLM/v10.1/bin/lmcomposite.exe COMPOSITE= 88F360B80245

Windows Dongle-- parallel port hardware key

lmhostid -flexid FLEXID=7-b28520b9

31-May-2007 6-3


6.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+)

6.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.

6-4 31-May-2007


Option


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.

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

Synopsis lmcksum [-k] [-c license_file_path]

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:

31-May-2007 6-5


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)

6.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.

Option {PRIVATE}-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

6-6 31-May-2007

AVL AST LicensingUsersGuide

Documents

Transcript of AVL AST LicensingUsersGuide