FlexLM License file format

General

FlexLM license files are in effect an agreement between the license vendor and the end user; They elaborate the number of available licenses, the check – out policy for each license, validity and expiration date of each license etc. The FlexLM License Manager Daemon (lmgrd) interprets the license file to dispatch license requests to different license vendor daemons.

This document is a short account of the format and syntax of the license file, and its effect on licensed applications’ utilization.

SERVER line

License files usually begin with a single SERVER line, or three SERVER lines for Server triad configurations. The SERVER line specifies the license server’s

  • Hostname

  • Hostid (MAC address) of the and

  • TCP/IP port number of the license manager daemon (lmgrd). If no port is specified then the first available port in the range 27000 to 27009 will be used.

Syntax

Server line syntax is as follows:

SERVER <server name> <host id> <lmgrd port>

Example

SERVER my_server 001122334455 27000

USE_SERVER

VENDOR line

The VENDOR line specifies the

  • Vendor daemon name and path. lmgrd uses this line to start the vendor daemon.

  • Options file path

  • Vendor daemon TCP/IP port number (default 2080).

Syntax

VENDOR vendor [vendor_daemon_path][[options=]options_file_path] [[port=]port]

Example

VENDOR adskflex adskflex.opt port=2080

FEATURE / INCREMENT line

FEATURE / INCREMENT lines describe specific licenses. A single FEATURE (or INCREMENT) line may be followed by several INCREMENT lines, creating separate license pools.

Syntax

{FEATURE|INCREMENT} feature vendor feat_version exp_date num_lic SIGN=sign [optional_attributes]

Example

FEATURE MayaUnltdf sgiawd 7.000 17-aug-2005 2 001122334455

PACKAGE Lines

PACKAGE lines provide an outline to licensing product SUITEs, and facilitate distribution of features which largely share the same FEATURE line arguments. PACKAGE lines are ineffective on their own account; they require FEATURE / INCREMENT lines to effectively activate these licenses.

Syntax

PACKAGE package vendor COMPONENTS=pkg_list SIGN=pkg_sign

Example

PACKAGE suite_example vendor_name version SIGN=12345 COMPONENTS=”feature_1:version_1:3 feature_2:version_2:4″

FEATURE suite_example vendor_name version issue_date 2 SIGN=54321 SN=123

In this case, checking out either feature_1 or feature_2 will also check out the suite_example suite. The total number of available licenses is 3×2=6 for feature_1, and 4×2=8 for feature_2.

Please visit www.openlm.com for more information about software license management.

Please follow and like us:

What is the difference between the FlexLM lmgrd and lmadmin license server managers

license server components

The vendor daemon and the license server manager jointly comprise the FlexLM (Flexnet) license server. The license server manager contacts a FlexEnabled application, and dispatches the handling of that application to the appropriate vendor daemon. It also serves as an interface between the Vendor daemon and the Application, for checking out licenses.

License server manager types

There are two versions of the license server manager:
• lmgrd – the original license server manager with a command-line interface.
• lmadmin – a newer web-based license server manager.

Conceptual differences

The following table summarizes the conceptual differences between the two license server manager types:

Item lmgrd lmadmin
Interface Command-line interface Web-based license server manager
Configuration Options Configuration information is acquired  from the command-line options used when the program is started No configuration options are required upon program start.
Persistence of change Changes need to be done in the license file Settings are maintained after relaunching the tool, and they override the license file.
License file import A single license file set by the configuration options upon running lmgrd Import (multiple) license files.
Number of running instances One instance of lmgrd is run for each vendor daemon. Supports multiple vendor daemons with one lmadmin process.

More changes between lmgrd & lmadmin

On top of these conceptual changes, there have been some changes in commands:

  • Some commands are no longer supported or have been replaced in lmadmin (e.g. lmremove, lmdown)
  • Some have changed in behavior (e.g. lmreread)
  • Other commands have been added into the lmadmin to integrate the functionality previously provided by the LMTOOLS (Stop server)
Please follow and like us:

FlexNet vulnerability: lmgrd Remote Code Execution

Zero Day has reported that a security vulnerability has been discovered in FlexNet License Server Manager installations. This vulnerability enables attackers to execute arbitrary code on remote FlexNet License Server managers. Authentication is not required to exploit this vulnerability. The flaw was reported by Luigi Auriemma and Alexander Gavrun.

The specific flaw exists within lmgrd license server manager. lmgrd listens by default on TCP port 27000. A specially crafted packet sent to the server will cause a stack overflow allowing for remote code execution under the context of the server.

Flexera Software has issued an update to correct this vulnerability and also provided license administrators best practices for mitigating risk exposure.

More details can be found at:

http://www.flexerasoftware.com/pl/13057.htm

Please follow and like us:

FAQ: Flexera lmgrd log file is very big


The lmgrd log file collects all license check out / check in activity. This log would continue to increase in size and as long as the licensed service is running.

The log is cleared when the licensed service is restarted.
This can be done via Flexera’s LMTOOLS UI.

On The “Services/License File” tab choose the licensed service. e.g.: Autocad.

On the “Config Services” tab – you can view the log (e.g: Autocad.log) and its path.

On the “Start/Stop/Reread” tab, use the marked buttons. This would clear the service log file (Autocad.log) and restart logging.

One of the advantages of the OpenLM system is that the accumulation of large amounts of data in this log file is made redundant. The OpenLM Broker is a component in OpenLM’s system which reads the licensed log file, and reports its content to the OpenLM server. There this information is processed and exhibited in a clear and negotiable manner.

 

 

Please follow and like us:

IBM Rational – FlexNet Token based licensing

IBM Rational license management using FLEXnet

The IBM Rational License Server uses FLEXnet (FlexLM) for licensing IBM Rational products.

FLEXnet main components

The four main components of FLEXnet are:

  • The License Manager Daemon, lmgrd

  • The Vendor Daemon, telelogic

  • The client application program, in this case any IBM Rational application

  • The license file, license.dat

Mode of employment

  • When an IBM Rational product is started, the program uses the TELELOGIC_LICENSE_FILE system variable to find out the name of the computer that’s running the FLEXnet license server and the port that it’s using.

  • The program contacts the license manager on the FLEXnet license server, using the specified port. It requests a floating license and makes the request for the Telelogic vendor daemon.

  • On the FLEXnet license server, the license manager sends the request to the Telelogic vendor daemon. The Telelogic vendor daemon checks to see if any licenses are available.

  • If there are free licenses, the Telelogic vendor daemon grants a license and the program runs. If there aren’t any licenses available, the Telelogic vendor daemon refuses the request, and the program fails to start and displays a license denial message.


Token-based licensing

Token licenses are in fact a form of floating license, only that instead of having a pool of licenses – it has a pool of tokens. When a feature is checked-out, a certain amount of tokens are consumed. The number of consumed tokens is specific to each feature, and is apparent in the feature/Increment line in the license file. When the application is closed, the tokens are returned to the pool for other end users to use.

Advantages of Token licensing

Having the ability to apply the acquired licenses to multiple products is an appealing concept:

  • Customers are not always aware of the full array of features they may acquire. having a token based license scheme ensures customer satisfaction from the license acquisition.

  • As development stages progress, customer needs change. They may require different licensed features, and eliminate the charge of “unused” software.

  • The entire license purchasing method is simplified. Customer can add/try new software during project, without new PO or evaluation process

Rational tools’ token-based licensing

IBM Rational license types

IBM Rational includes the following license types:

DOORS, Synergy, Change, Tau, System Architect, Focal Point, Rhapsody, Publishing Engine, Logiscope and Team Webtop

IBM Rational token license file examples

  • The Increment / Change line marks the number of tokens to be consumed:

INCREMENT Change telelogic 2015.04302 30-apr-2015 1 …

VENDOR_STRING=T10-999999:t,TLSTOK,1.0,Change,5  … // 5 Tokens worth.

  • This is an INCREMENT line indicating the total number of Tokens in the license

file. In this case, it is 200:

INCREMENT TLSTOK ibmratl 2.0 30-apr-2015 200 ISSUER=IBM

Rational License Server 8.1.1

Rational License Server 8.1.1 incorporates all vendor daemons (telelogic, rational, and ibmratl) into one. This change has also been incorporated into multiple Rational products such as ClearCase and ClearQuest.


References

http://publib.boulder.ibm.com/infocenter/rational/v0r0m0/index.jsp?topic=/com.ibm.rational.license.doc/topics/r_lic_log_file.html


http://www-01.ibm.com/support/docview.wss?uid=swg27023414&aid=1

Please follow and like us: