1 2 3 Previous Next

Licensing and Installation

73 Posts authored by: guy_wettstein

A common question arises when managing a license server. Should I use lmreread to pick up changes in the license file or options file or should use lmdown and then restart the license server?


Over the years, I've found that lmreread generally works well for adding new licenses or for picking up simple changes to the options file such as defining a new LM_PROJECT.


However, for swapping complete license files or for changes to the options file that involve restricting access to licenses (e.g.: RESERVE), you must be careful with lmreread and should probably opt for a restart. In the case of controlling access with keywords, it's one thing to add a new license and define who can check it out with INCLUDE. It's another thing to remove access for a user or host that already has that license checked out. Scheduling a restart can help mitigate problems.


What are your experiences? Please feel free to share your best practices.

Did you know you can drag a path from Windows Explorer to the Windows command line? It's true! Watch:


When you need to run shell commands on Windows as an Administrator, you typically must right-click the cmd.exe and choose "Run as administrator" in order to elevate the privileges in that shell. Well, it's very easy to create a shortcut for cmd that elevates automatically.


1. Create a shortcut to cmd.exe, perhaps on your Desktop. You might want to rename it Admin_cmd or something similar.

2. Right-click the shortcut and select Properties.

3. Select the Shortcut tab and then click Advanced...

4. Check the Run as administrator option and click OK


5. Click OK


Now you can simply double-click this shortcut whenever you need elevated privileges.

There are significant changes in the X-ENTP VX.1 release media and some new options that affect which downloads you should get and how you should install them. We strongly encourage you to carefully read the release documentation available on the download page before you make any selections or begin installing the software. This is especially important if you are considering one of the 64-bit native media sets. The information provided in the release documentation can help you make an informed decision about whether the 32-bit or 64-bit media set is the right one for you.


We also have a TechNote that augments some of the information in the release documentation.

The lmstat command will report the quantity of a particular feature with the -f option. However, if you have multiple versions of a license feature, they're rolled up into a single count by default. For example:


Z:\>lmutil lmstat -c 1717@lic_server -f qhsimvl

lmutil - Copyright (c) 1989-2011 Flexera Software, Inc. All Rights Reserved.

Flexible License Manager status on Fri 10/31/2014 14:09


[Detecting lmgrd processes...]

License server status: 1717@lic_server

    License file(s) on lic_server: C:\MentorGraphics\License_Files\lmstat_test.txt:


lic_server: license server UP (MASTER) v11.11


Vendor daemon status (on lic_server):


     mgcld: UP v11.11

Feature usage info:


Users of qhsimvl:  (Total of 10 licenses issued;  Total of 0 licenses in use)



This might leave you with the impression that you have more features available for the version of the application you're running than you really do.


Note: Every Mentor Graphics application requires a minimum version of a license feature, usually tied to the build or release date of the application.


Fortunately, adding the -i option to your lmstat command will break down the overall count of a feature into separate counts for each version of that feature. For example:


Z:\>lmutil lmstat -c 1717@lic_server -f qhsimvl -i

lmutil - Copyright (c) 1989-2011 Flexera Software, Inc. All Rights Reserved.

Flexible License Manager status on Fri 10/31/2014 14:09


[Detecting lmgrd processes...]

License server status: 1717@lic_server

    License file(s) on lic_server: C:\MentorGraphics\License_Files\lmstat_test.txt:


lic_server: license server UP (MASTER) v11.11


Vendor daemon status (on lic_server):


     mgcld: UP v11.11

Feature usage info:


Users of qhsimvl:  (Total of 10 licenses issued;  Total of 0 licenses in use)



NOTE: lmstat -i does not give information from the server,

      but only reads the license file.  For this reason,

      lmstat -a is recommended instead.


Feature                 Version   # licenses    Expires         Vendor

_______                 _______   __________    _______         ______

qhsimvl                 2014.030              5         10-nov-2014     mgcld

qhsimvl                 2015.100              5         10-nov-2014     mgcld



In this example, I could run up to 10 simultaneous Verilog simulations using a version of Modelsim that requires a qhsimvl with a minimum version of 2014.030 or older (2013.110 for example). However, I could only run 5 simultaneous simulations using a version of Modelsim that requires 2014.040 or newer.


Keep the -i option in mind if you ever suspect you're not able to use the full count of a particular feature.

Sometimes users are running applications that are older than you would like or maybe you're just curious. Either way, you can gain insight into the application versions users are running by looking at the usage status of your license server with lmstat. The lmstat command shows not only the version of the license checked out but the version of the license the application requested. The requested version can be used to find who is running older versions. For example:


$ lmutil lmstat -f msimviewer -c 1717@server

lmstat - Copyright (c) 1989-2013 Flexera Software LLC. All Rights Reserved.

Flexible License Manager status on Fri 9/26/2014 15:26


License server status: 1717@server

    License file(s) on server: /opt/mgls/mgcld.txt:


     server: license server UP (MASTER) v11.11


Vendor daemon status (on server):


     mgcld: UP v11.11

Feature usage info:


Users of msimviewer:  (Total of 25 licenses issued;  Total of 1 license in use)


  "msimviewer" v2015.070, vendor: mgcld

  floating license


    user host (v2011.05) (server/1717 25360), start Fri 9/26 15:26



The license version (aka Exact Access Date or EAD), made bold for the example, usually corresponds to the release date of the application but you can check the application's release notes on SupportNet for confirmation. Better yet, find the user running the application and confirm the version they're running. You may want to point them to the latest release.

One thing that's always been lacking in Windows is a good interface for creating or editing your environment variables, especially when it comes to PATH:




Se what I mean?


Fortunately, there's a great free utility called Rapid Environment Editor that not only makes it easier to edit variables, it will also tell you where you have bad values. Check it out:




It highlighted my Path in red to tell me there was a problem and when I expand Path, it shows the problematic entries. Brilliant!


I can delete these and save my environment with a cleaner PATH variable.


Feel free to give REE a try - http://www.rapidee.com



With the release of PADS VX.0, the Aladdin USB (9-) hardware key is now the only supported dongle. We began dongle discontinuations a few years ago and they have trickled out release by release. The PADS VX.0 is a major release and customers using older dongles who wish to run the latest version will need to request a replacement key.


Please see our Hardware Key (Dongle) Discontinuations and Replacement FAQ for more information.


Customers running older releases can continue to run with the older dongles provided they are on a supported platform.

With the MSL v2014_1 release, we now have a 100% 64-bit MGLS for Linux x64. This means that for your Mentor license server, you no longer have to load 32-bit OS compatibility libraries to run MGLS.


You can download the latest MGLS for Linux x64 from SupportNet.

I believe keyboard shortcuts improve my efficiency. The also make you look like a pro. Here are some of my favorites, which all work on Windows 7:


(Windows + E) - Opens a explorer window to get to your drives, folders and files.


(Windows + M) - Minimizes all open windows to the Task Bar


(Windows + Home) - Minimizes all open windows to the Task Bar, except the active window


(Windows + Arrow Up and Windows + Arrow Down) - Maximizes your active window and restores it to the previous size, respectively.


(Windows + Left Arrow and Windows + Right Arrow) - Windows + Left Arrow makes your active window fill half the screen. Windows + Left Arrow repeatedly will move it to the other side of your monitor or the other monitor and eventually restore it's original size. Windows + Arrow Right will simply restore it to it's previous position or size. This shortcut is handy for moving a window to your second monitor.


(Windows + + and Windows + -) - Activate the magnifier and zoom in or zoom out.


(CTRL + + and CTRL + -) - Zooms in or out on the text in page or doc.



I admit to really needing the last two. ;-)



Try these out. They may take a little practice and change of habit to work into your routine but they can save you time. Feel free to share your favorite keyboard shortcuts.

I stumbled on an interesting little browser trick this week. You can make your browser take notes.


Paste the following into the address bar and press Enter:




You can then use your browser to type in text as notes or just something you want to paste elsewhere. You'll have to Ctrl-A and paste them somewhere to save them but this is a good way to type out some text that you can then use however you want.



Personally, I've never cared for the layout of the Control Panel in Windows 7. As an "admin type", I like to see everything. The default layout of the Control Panel is intended for the average user and perhaps it serves that group well. Nevertheless, I want full control of my Control Panel. I also love shortcuts.


Here's a way to create a "shortcut" to the Control Panel and have it display everything possible:


     1. Create a folder (perhaps on your Desktop) named "Everything.{ED7BA470-8E54-465E-825C-99712043E01C}


         You can actually replace the "Everything" part with whatever name you wish. The extension ".{ED7BA470-8E54-465E-825C-99712043E01C}" must be typed in exactly as is, including the dot and the curly braces.


     2. Double-click the folder you just created and everything that is possible to display in the Control Panel will be displayed.



Last week, Ken Foster showed us how to use psping on for measuring network latency on Windows - Tip of the Week: Measuring Network Latency. On Linux you can use ping with specific options to achieve similar results.


For example:


     ping -U -q -c 300 -s 1200




The options are as follows:


-U display full user-to-user latency, not just network round trip time.


-q Print only the first line and the summary


-c The number requests to send at one second intervals (300 = 5 minutes worth)


-s The number of bytes sent for each ping


rtt is ‘round trip time’. The values that follow are the minimum, average, and maximum latency values in milliseconds.



Please see previous blog posts on latency:


Tip of the Week: Troubleshooting Networking on Windows with pathping.

Tip of the Week: Measuring Network Latency

Whether it's defining a path in an environment variable, a .ini file or in an application, typing a long path can be frustrating and is prone to typos that can cause problems for you to troubleshoot. Here is an easy of getting an accurate path to a folder into your paste buffer.


When you navigate with Windows Explorer to the folder for which you need the path, click in the field that shows the hierachy of folder names and it will become a path to that folder that you can copy and paste.



We've previously discussed how to get fairly detailed debug information with the MGLS_DEBUG_LOG_DIR variable - Tip of the Week: Check requested license feature with debug. But sometimes a quick confirmation of the license checkout can be nice to see in the transcript. And, if anything fails, an error message will be right there.


The FLEXLM_DIAGNOSTICS variable is a simple way to show some debug information. Simply set FLEXLM_DIAGNOSTICS=3 in your environment and you should see something like the following in the shell where you invoked the application:


Checkout succeeded: msimhdlsim/9E204CB2CC009FD365DE

        License file: 1717@licserver

        License Server: 1717@licserver

License granted through "msimhdlsim".



I hope you find this useful. Be sure to share your own tips!



Filter Blog

By date:
By tag: