Application Note 1030: OpenLM license usage monitoring according to projects – v1.8.

General

OpenLM is able to record information about the usage of various licenses and allocate them to different company projects. This ability facilitates license allocation according to organizational projects, and can also serve as a mean to effectively charge-back license usage expenses according to these projects.

This ability complements OpenLM’s license monitoring capabilities; integrating license usage optimization with Active directory synchronization, Project assignment, and monitoring a variety of  license managers such as FlexLM (Flexnet), Sentinel HASP, Sentinel RMS, RLM, DSLS, LM-X, IBM LUM, and MathLM.

Scope

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some modifications have been made:

  • The configuration of Project monitoring was shifted from the OpenLM Server configuration tool to the EasyAdmin web application.

  • Administrative capabilities have been added, such as Enabling / Disabling a project, assigning it a priority and expected duration, and marking the project’s completeness percentage.

  • Projects can now be assigned to user groups (not just to individual users), and

  • Projects can be introduced by end-users via the OpenLM Agent module.

This Application Note describes the feature as implemented in the 1.8 version.

Project usage reporting

The Project usage reporting is available on the EasyAdmin web interface. Click OpenLM Start → Resports → Project usage in order to see the report. Set the filtering options on the left-hand side of the screen, and click the ‘Apply’ button in order to run the usage query. It is also possible to view the report in a chart format, or extract the information to a CSV file (green arrow icon at the bottom) and manipulate it on a spreadsheet software.

However, before having any information to report – it is necessary to set up the projects. Please follow the section below in order to do so.

Projects Settings

The “Projects Settings” screen defines the policy of the Project usage monitoring capability. In order to open it, click the OpenLM ‘Start’ button → ‘Administration’ → ‘Projects’ icon.

Notes:

1. Projects’ information logging requires the installation of the OpenLM Agent (Either Active Agent or Utilizer Agent) on the end-users’ workstations.

2. When the OpenLM server is configured to employ user permissions, access to this window requires administrative privileges.

The ‘Projects’ window appears:

Note:

The project configuration window was moved in OpenLM version 1.8 to EasyAdmin (under the Administration menu. Following is an account of its different configuration objects:

Log Projects Information

Check the Log projects information checkbox to start recording license usage information according to projects’ allocation.

Minimal Usage Duration for Project

This setting defines the shortest duration for logging purposes. Shorter periods would be merged together to form significant usage periods. For example, if the minimal duration is set to 5 minutes, and a user has opened the application for only 3 minutes, this usage period will not be accumulated to the current session, but rather merged with the following session.

Agent’s Behavior Settings

These settings define what the end-users will see on their workstations if they work on more than one project for their organization. If the workers are only allocated to one project in EasyAdmin then OpenLM will log their license usage without the need to take any action when the software is started. If the users work on more than one project then a dialog box will appear on their screen prompting them to select the current project.

Hide projects option from menu

Deny users the ability to determine the name of the project on which they’re working.

Projects window fades away after

OpenLM enables users to ignore the project dialog box by having it fade away after a predefined number of seconds. The Projects window fades away after setting defines the number of seconds after which it becomes invisible.

Allow creation of projects in Agent

This option has been introduced in the OpenLM 1.8 version.

The OpenLM project management module facilitates project creation via the OpenLM Agent. Check this box to enable this option, thus adding the “Create New Project” menu item in the OpenLM Agent interface (see image below).

When an end-user selects this option, the “Create new Project” window opens. The user then could create new projects and associate themselves to them.

Modification of these projects will be possible in EasyAdmin only. The origin of creation of the project will be apparent in the EasyAdmin Projects list window.

Show unassigned projects

By default, users can only see projects they are assigned to in the Agent → Set Active Project menu option. Checking this box will produce a list that contains all enabled projects in the system and the user will be able to select any project from this list. This option has been introduced in the OpenLM 1.8 version.

Support Environment Variable

The LM_PROJECT env. variable support is a backward-compatibility option, that supports this variable for registering projects. The variable is defined separately for each workstation, so there is no option of overriding its value between users.

The environment variable option is disabled by default. It is recommended to use the OpenLM supplied solution, unless backward support of the environment variable option is required.

The “Add unknown project” option presents an administrative filter for project names that are unknown to the OpenLM server:

  • Checked: The unknown project will be set and added to the list of projects.

  • Unchecked (default): The unknown project will not be set.

Selecting the active project

When logging of project information is enabled (see above), work hours need to be assigned to a specific project. When there is only one project – that project will automatically be assigned all the working hours. When there are more than one project – it is up to the end users to report on what project they are currently working.

1. One option for the end user to set the Active project is to right-click the Agent icon, and select the “Set Active Project” option.

2. Another option for setting the Active project is by a pop-up window. The appearance of this pop-up is configurable by options in the ‘Projects’ window, which was mentioned above.

Display at license retrieval

The default option is to prompt the worker to select the project when retrieving a license. This is a very useful way to ensure accurate logging of the project information, therefore the recommended setting is to leave the checkbox turned on.

Display periodically every

Users may start to work on one project, and then switch to a different one, without changing the Active Project setting. If this checkbox is ticked, a dialog box will pop up in a predefined time interval, according to the number of minutes set by the user.

Project creation in EasyAdmin

In the previous section, we have seen the mathod for creating project via the Agent. Projects can also be created via the EasyAdmin “Add project” window.  

In the “Project details” tab, the Administrator can set up the following characteristics:

  • Project name

  • Start and End time for the project

  • Number of working hours allocated to this project

  • The project’s priority, and

  • The project’s completeness percentage.

Users and user groups may be assigned to the project upon its creation, via the ‘Users’ and ‘Groups’ tabs. After configuring these items, click the ‘Save’ button.

Editing existing projects

The new project would be apparent in the Projects list window. In order to access this window, Click the EasyAdmin Start button → Users and Permissions → Project List.

This window presents options to create new projects, as well as to delete or edit existing ones. It is split to two panes:

  • The left pane serves as a filter for projects to be shown on the list on the right pane.

    • The Priority drop-down list presents Low / Medium / High priority levels.

    • “Created in” marks whether the project was created by the Agent or via the EasyAdmin window: Admin / Agent

  • The right pane consists of a list of the existing projects, and an action bar at the top.  Click the top bar icons to add a new project, delete a selected project, Edit a selected project’s properties, Enable or Disable a selected project.

Attaching users and user groups to the project

After creating a project, it is time to bind users or user groups to the different projects, according to organizational preferences. In order to do so, select the target project, and select the Users or Groups tab in the ‘Add project’ window. Then select the User or Group that would be attached to the project, and click the ‘Add’ button.

Appendix A: Projects information logging in v1.7

This application note relates to the OpenLM 1.8 version. As stated in the scope of this document, most Projects information logging capabilities are already existent in the 1.7 version. The main change of interface is due to the shift of the configuration from the OpenLM Server configuration tool to the EasyAdmin web application. Below is a screenshot of the 1.7 Projects setting tab on the OpenLM Server configuration tool for comparison.

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:

Multiple Server license management constellations

Flexera’s FlexLM (Flexnet)Three Server Redundancy (Triad)

IBM’s High Availability Licensing (HAL)

Dassault Systemes DSLS cluster for “Failover” mode

Scope:

License management tools such as IBM and Flexera both a method of employing multiple license servers in a cluster as part of their attempt to assure a fault-free license management solution. This article summarizes the operative measures required for implementing each of these solutions, and attempts to compare them in terms of pros and cons.

The OpenLM Utilizer license monitoring tool supports both configurations. OpenLM is designed to extract license statistics from multiple servers over WAN. It has been tried and confirmed for Flexera’s Triad configuration. At the time of writing this revision (Rev 1.0), It has not yet been verified with the IBM LUM HAL.

Flexera’s Three Server Redundancy constellation

General:

The Flexnet constellation is consisted of Three license servers, all inter-connected by TCP/IP. These machines are adequately named “Primary”, “Secondary” & “Tertiary”. Any one of the two first machines (Primary or Secondary) may be defined as the “Master”; which is counter intuitive, as it gets to do all the work while the other two basically sit on their hands. All licenses are served by this Master machine, and the Report & Debug logs are also accumulated by it.

Upon system start-up, the three FlexLM license servers are started up separately according to their order, and the Master role is set according to this order or according to a designated flag: “PRIMARY_IS_MASTER”.

The  FlexLM license Servers inter-communicate by a “Heartbeat” messages over TCP/IP, using the same port number. A machine which fails to receive a response to its sent Heartbeats turns down the vendor daemon and can not serve licenses. When the Master server (Primary or Secondary) fails, the Master role is passed to the other (Secondary or Primary) server. The new Master assumes the license management role for all the FlexEnabled applications, and accumulates new Debug and Report logs.

Configuration of a Three Server Redundancy constellation:

  • First, a set of three stable machines needs to be identified, and reliable communication needs to be set between them.
  • The software vendor must receive the HostID and Host name of the machines that consist the Triad. In return, they should provide system – specific license server files. Some changes may need to be done in the license file according to this new information, such as the PRIMARY_IS_MASTER value, the communication port number and the HEARTBEAT_INTERVAL which is effectively the timeout for license servers to be knocked out of the triad.
  • The license server package needs to be copied to each of the three participating servers.

Limitations:

  • There should always be at least two machines up and running. If any two machines halt – then the Triad is stopped as a whole, and no “FlexEnabled” applications are served. This is quite an odd limitation, as the system basically employs a single machine at a time anyway.
  • The “Tertiary” machine never gets to play “Master”. I find this an odd planning, because this in effect renders this machine useless.
  • This configuration puts a strain on one machine at a time. It does not share the work, and is prone for errors especially in busy environments.


IBM’s High Availability Licensing (HAL)

General

The IBM HAL is based on the “License server Cluster” concept. A cluster is a group of 3 to 12 license servers, that jointly manage licensed applications. The management activity load is dynamically and equally shared among most of the servers, while one or two other servers remain on-hold, waiting to pitch in in case an active server becomes unavailable.
Network license servers that participate in a cluster can simultaneously serve server-bound licensed applications,  as well as cluster bound applications.

Configuring HAL

  • Select a set of interconnected license servers as cluster members. These members need to be stable machines, that stay on permanently. Network stability is also crucial in order to assure faultless system activity. It is recommended to maintain the machines in the same geographical vicinity, and that they all run the same operation system type.
  • Instal LUM on each of the license servers.
  • Create the cluster from one of the servers in the cluster. This may be done using the i4blt -H command or the GUI. In the following example, cluster ThisCluster was created, and it contains 3 servers: Server1, Server2 & Server3.
    • i4blt -H c -N ThisCluster -T 3 -n “Server1 Server2 Server3”
  • Activate each member of the cluster. The 1st member is already enabled by default following the cluster definition. This example enables Server2:
    • i4blt -H a -N ThisCluster -n Server2

In order to Deactivate a Server2, use

  • i4blt -H a -N ThisCluster -n Server2
  • Get a HAL Enrollment Certification File (ECF) from the license vendor. In order to do so, You must send him the “Cluster ID”. This ID can be obtained by typing in the status cmmad:
    • i4blt -H s -N ThisCluster.
  • Enroll the HAL ECF just like as for regular license servers, using the GUI or the i4blt command line. for example:
    • i4blt -a -n ThisCluster -f <ECF> -T <NumberOfLicenses>
  • Configure all clients to recognize all the cluster members.

Dassault Systemes DSLS

The DSLS license manager also implements a cluster structure, for “Failover mode”. Its characteristics are a mix of the two types mentioned above;

  • A server may not perform as part of a cluster AND as a stand alone server at the same time.
  • The number of license servers that participate in the cluster are exactly 3.
  • The OS on each server may be either Unix or Windows.
  • At least two machines should be up and running, and interconnected  in order to serve licensed applications.
  • There is no ‘Master’ here: all machines have the same role of license management.
  • The three machines each log the license activity independently. They update each other when usage conditions change.


Summary

It seems that the IBM LUM solution for multiple server constellations is more comprehensive than that of Flexera’s. Its main ‘Pro’ characteristics include:

  • Equal sharing of the workload.
  • Dynamic redistribution of license management as a function of server availability
  • Configurable amount of servers; a maximal 12 server constellation, in comparison to 3 (effectively 2) Flexera servers.

The main ‘con’ on the IBM LUM list is its lack of popularity in comparison to Flexnet (FlexLM). This has manifested in a trend of licensed application vendor’s migration from LUM to various other license management tools, e.g. FlexLM and DSLS.

 

Further Reading:

http://www-01.ibm.com/software/awdtools/lum/hal.html

http://kb.flexerasoftware.com/doc/DocumentRepository/Licensing/FLEXnet_Publisher/FLEXnet_Publisher_11.6/03_ISV/Product%20Manual/LicenseAdministration.pdf

http://communities.mentor.com/mgcx/servlet/JiveServlet/previewBody/2877-102-1-5407/licensing_bp_wp-10.8.pdf

http://pdir.technodat.cz/r21/install_v5doc/doc21/online/basil_C2/pdf/DSLS.pdf

Please follow and like us:

Application Note 1001_b: Configuring OpenLM to interface the Sentinel RMS license manager

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Sentinel RMS License Manager, and obtain reliable license reports and usage statistics.

Enabling the OpenLM server to work with RMS

In order to configure OpenLM to work with  Sentinel RMS, please follow this procedure:
1. Download lsmon.exe and lsapiw32.dll . These files aren’t included in the OpenLM installation package. For information on how to obtain these files, please contact OpenLM on support@openlm.com.
2. Copy these files to “C:\Program Files\OpenLM\OpenLM Server\LM”
3. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RMS.
4. Type in the full path of the executable file, i.e.:  “C:\Program Files\OpenLM\OpenLM Server\LM\lsmon.exe” in the “RMS executable file” text box.

See the following image for further clarification:

Introducing a new Sentinel RMS server

After configuring the OpenLM configuration tool to work with Sentinel RMS as elaborated above, the user may introduce an new  Sentinel RMS server under the License Servers tab:
1. Select the “License Servers” tab.
2. Select the RMS type from the “Type” dropdown list.
3. Type in a meaningful description in the “Description” text box.
4. Type in the appropriate “Hostname” and “Port” numbers. The Sentinel RMS default port is 5093.
5. Check the “Enabled” check box.
6. Click the “Apply” button. The  Sentinel RMS server is now ready to interface the OpenLM.

OpenLM Broker configuration for RMS

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the RMS license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RMS license manager type from the ‘Type’ dropdown list.
In the port’s Commands list make sure the ‘status’ command is
lsmon <License Server Name>

Document Revision Table

Version Author Date Changes
0.1 Orik May1, 2012 Preliminary
1.0 Orik Jun3, 2012 Revised.
1.1 Orik Jun6, 2012 Added Broker

 

Please follow and like us:

AutoDesk FlexNet feature codes, March 2012

Feature codes

FlexNet (FlexLM) uses a predefined set of codes in order to manage multiple licensed Features. Each of these features is given a unique code, by which FlexNet grants license requests, and keeps track of the license pool.

OpenLM Also makes use of these feature codes during FlexLM reporting in order to monitor and optimize Autodesk license usage. As versions progress and features are added, the code tables need constant updating. The following is a complete list of AutoDesk codes, updated to March 2012. It was taken from Autodesk’s official site.

Autodesk code table

AutoCAD 2013 85871ACD_2013_0F
AutoCAD Architecture 2013 85883ARCHDESK_2013_0F
AutoCAD Civil 3D 2013 85976CIV3D_2013_0F
AutoCAD Design Suite Premium 2013 85969DSPRM_2013_0F
AutoCAD Design Suite Standard 2013 85970DSSTD_2013_0F
AutoCAD Design Suite Ultimate 2013 85971DSADV_2013_0F
AutoCAD ecscad 2013 85889ECSCAD_2013_0F
AutoCAD Electrical 2013 85890ACAD_E_2013_0F
AutoCAD for Mac 2013 85989ACDMAC_2013_0F
AutoCAD Inventor LT Suite 2013 85958INVLTS_2013_0F
AutoCAD LT 2013 85872ACDLT_2013_0F
AutoCAD LT Civil Suite 2013 85991ACDLTC_2013_0F
AutoCAD LT for Mac 2013  86021ACDLTM_2013_0F
AutoCAD Map 3D 2013 85981MAP_2013_0F
AutoCAD Map 3D Enterprise 2013 85982MAP3DE_2013_0F
AutoCAD Mechanical 2013 85885AMECH_PP_2013_0F
AutoCAD MEP 2013 85887BLDSYS_2013_0F
AutoCAD P&ID 2013 85977PNID_2013_0F
AutoCAD Plant 3D 2013 85978PLNT3D_2013_0F
AutoCAD Raster Design 2013 85952ARDES_2013_0F
AutoCAD Revit Architecture Suite 2013 85954REVITS_2013_0F
AutoCAD Revit MEP Suite 2013 85955REVSYP_2013_0F
AutoCAD Revit Structure Suite 2013 85957REVSU_2013_0F
AutoCAD Structural Detailing 2013 85943STRDET_2013_0F
AutoCAD Utility Design 2013 86027UTLDESN_2013_0F
Autodesk 360 Vault Collaboration 2013 85983VLTC_2013_0F
Autodesk 360 Vault Collaboration AEC 2013 85984VTCAEC_2013_0F
Autodesk 360 Vault Office 2013 85986PCOFFI_2013_0F
Autodesk 360 Vault Professional 2013 85987VLTM_2013_0F
Autodesk 360 Vault Workgroup 2013 85988VLTWG_2013_0F
Autodesk 3ds Max 2013 858923DSMAX_2013_0F
Autodesk 3ds Max Design 2013 85893MAXDES_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Premium 2013 85918MXECSP_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Standard 2013 85920MXECS_2013_0F
Autodesk Alias Automotive 2013 85881AUTOST_2013_0F
Autodesk Alias Design 2013 85896DESNST_2013_0F
Autodesk Alias Surface 2013 85895SURFST_2013_0F
Autodesk Animation Academy 2013 85922AAA_2013_0F
Autodesk Building Design Suite Premium 2013 85946BDSPRM_2013_0F
Autodesk Building Design Suite Standard 2013 85947BDSS_2013_0F
Autodesk Building Design Suite Ultimate 2013 85948BDSADV_2013_0F
Autodesk Entertainment Creation Suite Premium 2013 Exclusives 86043ECSPE_2013_0F
Autodesk Entertainment Creation Suite Standard 2013 Exclusives 86044ECSSE_2013_0F
Autodesk Entertainment Creation Suite Ultimate 2013 85926ENCSU_2013_0F
Autodesk Factory Design Suite Premium 2013 85965FDSPRM_2013_0F
Autodesk Factory Design Suite Standard 2013 85966FDSS_2013_0F
Autodesk Factory Design Suite Ultimate 2013 85967FDSADV_2013_0F
Autodesk Infrastructure Design Suite for Education 2013 85974ESCSE_2013_0F
Autodesk Infrastructure Design Suite Premium 2013 85992IDSP_2013_0F
Autodesk Infrastructure Design Suite Standard 2013 85993IDSS_2013_0F
Autodesk Infrastructure Design Suite Ultimate 2013 85994IDSU_2013_0F
Autodesk Infrastructure Map Server 2013 86014IMS_2013_0F
Autodesk Infrastructure Modeler 2013 86013INFMDR_2013_0F
Autodesk Inventor 2013 85998INVNTOR_2013_0F
Autodesk Inventor Factory Premium 2013 85999INVFPR_2013_0F
Autodesk Inventor Factory Ultimate 2013 86000INVFAD_2013_0F
Autodesk Inventor LT 2013 86004INVLT_2013_0F
Autodesk Inventor OEM 2013 86002INVOEM_2013_0F
Autodesk Inventor Professional 2013 86001INVPROSA_2013_0F
Autodesk Inventor Publisher 2013 85979INVPUB_2013_0F
Autodesk Maya 2013 85857MAYA_2013_0F
Autodesk Maya Entertainment Creation Suite Premium 2013 85928MYECSP_2013_0F
Autodesk Maya Entertainment Creation Suite Standard 2013 85930MYECS_2013_0F
Autodesk MotionBuilder 2013 85936MOBPRO_2013_0F
Autodesk Mudbox 2013 85869MBXPRO_2013_0F
Autodesk Navisworks Manage 2013 86022NAVMAN_2013_0F
Autodesk Navisworks Simulate 2013 86023NAVSIM_2013_0F
Autodesk Plant Design Suite Premium 2013 85995PDSPRM_2013_0F
Autodesk Plant Design Suite Standard 2013 85996PLTDSS_2013_0F
Autodesk Plant Design Suite Ultimate 2013 85997PDSADV_2013_0F
Autodesk Product Design Suite for Education 2013 85961ESME_2013_0F
Autodesk Product Design Suite Premium 2013 85962PDSP_2013_0F
Autodesk Product Design Suite Standard 2013 85964PDSS_2013_0F
Autodesk Product Design Suite Ultimate 2013 85963PDSU_2013_0F
Autodesk Quantity Takeoff 2013 86024AQTO_2013_0F
Autodesk Revit 2013 85950RVT_2013_0F
Autodesk Revit Architecture 2013 85862REVIT_2013_0F
Autodesk Revit Structure 2013 85866REVITST_2013_0F
Autodesk Robot Structural Analysis 2013 86005RSA_2013_0F
Autodesk Robot Structural Analysis Professional 2013 85975RSAPRO_2013_0F
Autodesk Showcase 2013 85956SHOWCASE_2013_0F
Autodesk Showcase Professional 2013 85949SHOWPRO_2013_0F
Autodesk Simulation CFD 2013 86025SCFD_2013_0F
Autodesk Simulation CFD 2013 Advanced 86028SCFDA_2013_0F
Autodesk Simulation CFD 2013 Connection for ACIS 86045SCACIS_2013_0F
Autodesk Simulation CFD 2013 Connection for NX 86030SCFDNX_2013_0F
Autodesk Simulation CFD 2013 Connection for Parasolid 86047SCFDP_2013_0F
Autodesk Simulation CFD 2013 Connection for Pro/E 86032SCPROE_2013_0F
Autodesk Simulation CFD 2013 Design Study Environment 86034SCDSE_2013_0F
Autodesk Simulation CFD 2013 Motion 86036SCFDM_2013_0F
Autodesk Simulation DFM 2013 86056SIMDFM_2013_0F
Autodesk Simulation Mechanical 2013 85940ASMES_2013_0F
Autodesk Simulation Moldflow Adviser Premium 2013 86006MFAM_2013_0F
Autodesk Simulation Moldflow Adviser Standard 2013 86008MFAD_2013_0F
Autodesk Simulation Moldflow Adviser Ultimate 2013 86007MFAA_2013_0F
Autodesk Simulation Moldflow CAD Doctor 2013 86009MFCD_2013_0F
Autodesk Simulation Moldflow Design Link 2013 86010MFDL_2013_0F
Autodesk Simulation Moldflow Insight Premium 2013 86038MFIP_2013_0F
Autodesk Simulation Moldflow Insight Standard 2013 86042MFIB_2013_0F
Autodesk Simulation Moldflow Insight Ultimate 2013 86040MFIA_2013_0F
Autodesk Simulation Moldflow Synergy 2013 86012MFS_2013_0F
Autodesk Simulation Multiphysics 2013 85942ASPRO_2013_0F
Autodesk SketchBook Designer 2013 85990ALSK_2013_0F
Autodesk Softimage 2013 85934SFTIM_2013_0F
Autodesk Softimage Entertainment Creation Suite Standard 2013 85932SIECS_2013_0F
mental ray Standalone 2013 86019MRSTND_2013_0F

Please follow and like us:

Application Note 1026: Basic OpenLM Server configuration for FlexLM

General

OpenLM supports the monitoring of a wide, and ever growing variety of license servers. Among those are Flexera FlexLM (Flexnet) , Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This is an description of the basic procedure for configuring the Openlm server to interface a FlexLM license manager, to monitor Flexnet reporting.

Procedure

Please first refer to this Application Note. It gives a general description of the OpenLM system; what should be installed where, and who needs to communicate with whom.

Install the latest version of the OpenLM server. It is found on the OpenLM site.

  1. Configure the OpenLM server so that it would communicate with the License server:
  • Open the “OpenLM server configuration window, On the “License Servers” tab (see image below).

  • Click the ‘Add’ button, and type in the license server parameters (Type, Host name (or IP), port & time zone). In order to find the Server name and port, please refer to this post.
  • You can type in a descriptive name to make recognizing the sever easier
  • In the image above, these parameters are: FLEXlm, olm-lm-arcgis10, 27000, UTC+08, “ArcGIS 10 Head Office”.
  • Click the ‘Apply’ button. Select ‘Restart now’. That’s it: the OpenLM server is
  1. Check the connection of the OpenLM server to the license server; click the ‘Check’ button. A text would follow. This text is a query of the License server. It indicates whether a connection to that server is established.
  1. Now open the EasyAdmin web application. Click start -> Management -> License servers. The “License servers” window appears. Verify that the configured license managers appear on the list. Circle nodes indicate a connection to a license server. Square nodes indicate a connection to a Broker which is installed on the License server machine.


Please follow and like us:

Setting FlexLM port numbers statically

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

Please follow and like us:

How do I know the FlexLM license manager port number ?

OpenLM employs the Flexnet / FlexLM reporting mechanism to monitor and optimize concurrent license usage, and obtain license statistics. The FlexLM license manager interfaces licensed applications via predefined ports. You can verify that a port number is set correctly by:

1. Using Flexera’s LMTOOL utility: Select the “Server Status” tab, and click the “Perform Status inquiry” button. the port number would appear on the line that begins with “License server status:” e.g.:

License server status: 27000@My_server

2. You can also find the server name and port number (If defined as static) directly in the license file, in the SERVER line e.g.:

SERVER <ServerName> <hostId> <PortNumber>

USE SERVER

The path and name of the license file is set in the LMTOOLS, under the “Config Services” tab.

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:

Automatically Release “Orphan” ArcGIS and Autodesk licenses

Users of network licensed ESRI ArcGIS and Autodesk (AutoCAD) applications report cases in which licensed application were closed, but the licenses remained “hanging”, and were not returned to the license pool.

This condition may be caused by broken communication between the FlexLM license server and the workstation on which the application is running, or any other “glitch” for that matter. The answer given by the vendors to this condition is that the system administrator should manually release the checked-out license via the license administrator tool or Flexera’s LMTOOLS UI.

But this is wrong.

This problem does not manifest in any apparent error message or visible notification, so this condition may persist indefinitely. Because of that:

  • There is no way for manually and routinely tracking down and fixing this condition. This condition is only captured when there is an obvious “leak” in the amount of available licenses.
  • On top of not being able to utilize the full extent of the acquired software licenses, this condition may also cause exaggerated billing for users.

An automatic solution for the identifying and fixing this condition is therefore required, and is supplied by OpenLM. On the OpenLM EasyAdmin web application, there is a check box which is configured to do just that. It configures the OpenLM system to track down ArcGIS and Autodesk applications’ licenses which are checked out but not used, and retrieve them.

This option is set active by default. The configuration check box is found as follows:

  • Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.
  • Select the “Active Agent” icon. The “Active Agent” window opens.
  • Select the “Extension dedicated” tab, and check the “Solve license manager errors” box.

That’s it. You wouldn’t have to worry about hanging “Orphaned” licenses for ArcGIS and Autodesk applications any more.

 

Please follow and like us: