[Flexlm Licence Crack
Hanne Rylaarsdam
I'm having an issue that is causing us headaches when compilingusing the MDK-ARM Standard version. We have a FlexLM license setupand it works - we can compile. However, it takes us roughly 7 minutesto compile (our development is in the USA and the license server isin Europe) our project.
When we check out a license, it takes roughly 20 seconds tocompile. We have been able to check out licenses in the past buttoday, when we go to License Management, the Check Out button isdisabled (grayed out).
Ok, but it's hard to deduce the topology of your network, or ifyou have firewall, NAT or VPN issues. I presume you don't have theserver directly on the public internet. Last time I did this withRealView and FlexLM, my European colleagues would VPN/VNC into amachine on the same subnet as the licence server in the USA.
I have the same issue, and have worked in detail with KeilSupport, but we got nowhere.
Even with a sub 1 ms latency network (PC->1Gbe Switch->10GbeSwitch->Server), you can be hit with large delays in checkout offlex token.
It usefully states that NI VLM can be installed on a machine that is not the VLM however it insists on an agreement file valid on the computer I'm running it on before I can go any further (v3,2). I need to get at the "Create Volume License Installer" part.
The only option is to use a custom type of license file that is written specifically for FlexLM. You can get custom license files for FlexLM by contacting Agree...@ni.com as stated in step 1 in Getting Started with FlexNet Publisher Configuration.
I've set up a license server using the FlexLM daemons and with a flexlm formatted license file. That works. Whilst configuring the services using lmtools another NILM service sneaks in. I deleted that but I need to know why this appears. The link from KnowedgeBase 489FTAXT: Why Does "NILM License Manager" Show Up in LMTOOLS? doesn't work.
Anyway, in order to use the VLM I had an agreement file created on the PC that I'm going to run it on (i.e. the 'technicians' PC) but when creating the Volume License Installer, I get it to point to the server running the NI FlexLM. I don't start the volume license server on the technicians PC.
The license file is unmanaged concurrent. We don't want to use groups, so I deselected the installer to request permission to join groups. It all starts up without asking the user difficult questions. Jobs jobbed!
Using FLEXlm License Management UtilitiesFLEXlm provides license management utilities that you can use to monitor the license manager. These utilities are available at the command line or through a graphical user interface.
Using the lmutil CommandThe lmutil command, available in the $MATLAB\flexlm folder, provides access to all the FLEXlm license management utilities. To view a list of all the capabilities of the lmutil.exe utility, open a Command Prompt window, go to the $MATLAB\flexlm folder and type
The following table lists the names of the most useful tools available through lmutil. For more detailed information, see the FLEXlm End User Manual, included in PDF format in your MATLAB installation ($MATLAB\flexlm\enduser.pdf).
Utility
Description
lmdiag
Diagnose license checkout problems.
lmdown
Shut down all license daemons (both lmgrd and all vendor daemons) on the license server node.
lmhostid
Report the host ID of a system.
lmreread
Make the license manager daemon reread the License File and start any new vendor daemons.
lmstat
Display the status of all network licensing activities.
lmswitchr
Switch the report log file.
lmver
Determine the FLEXlm version of a library or binary file.
For example, to view the current status of the license manager, open a DOS command prompt window and enter the lmutil command, specifying the name of the lmstat utility. The example uses the -a option to get a verbose listing of available licenses and the -c option to specify the location of the License File to use. You must specify the -c option with every tool invoked through lmutil.exe.
Using the FLEXlm Utilities Graphical User InterfaceFLEXlm provides a graphical user interface (GUI), called LMTOOLS, to its license management utilities. The GUI provides access to the same set of tools as the lmutil command and displays the results returned in an integrated display window.
FLEXnet packages all their license management utilities in a singleexecutable called lmutil.exe. The MathWorks Installer includesthis utility in every server installation in the matlabroot\flexlm folder.To view a list of all the capabilities of the lmutil utility,open a Command Prompt window, go to the matlabroot\flexlm folderand type
The following table lists the names of the most useful tools availablethrough lmutil. For more detailed information, see the FLEXnetLicensing End User Manual, included in PDF format in your MATLABinstallation (matlabroot\flexlm\enduser.pdf).For information about accessing these tools through a graphical user interface,see Using the FLEXnet Utilities Graphical User Interface (LMTOOLS).
Make the license manager daemon reread the License File and start anynew vendor daemons.
Note: When you use lmreread toreprocess a License File for a user-based license, changes to INCLUDE statementsin the associated FLEXnet options file take affect after a 15 minute delay.
The example uses the -a option to get a verbose listingof available licenses and the -c option to specify thelocation of the License File to use. You must specify the -c optionwith every tool invoked through lmutil.exe. If your installationpathname contains spaces, enclose the pathname in quotes.
We have purchased a floating license for CodeWarrior Development Suite for Networked Applications. For the license we want to use our existing FlexLM server application running on a CentOS 5.11 linux machine.
After installation the generated license.dat file on the server machine, flexlm service was restarted but was not able to integrate the license.dat file for the CodeWarrior suite. Obviously the appropriate vendor daemon is missing on the linux host.
FlexNet Publisher (formerly FLEXlm) is a software-based licensing system which does not need any hardware device such as a dongle. Instead, licenses are stored on either your machine or on a server to which you have network access, in a protected area of storage known as trusted storage. FlexNet licensing is available for OrcaFlex from version 11.0 onwards.
Once activated, the licenses are tied to the machine or machines where they have been activated. Licenses can be moved between machines. This is done by deactivating, using OrcaLicense, and then reactivating on another machine, again using OrcaLicense. Note that licenses should not be moved with excessive frequency.
These licenses in trusted storage are in essence what you have purchased or leased from us, and should be treated with due care and security. We cannot replace lost active licenses. In particular, if you wish to decommission a server, or relocate a VM or replace hardware etc, you must deactivate your licenses first and then reactivate them after making the changes when you are again ready to use them.
FlexNet licenses come in two different sorts: floating (on a network) and local (commonly known as node-locked). You cannot switch your license type yourself: you will be asked which type you require before we set up your license(s). If you later wish to change it you must contact us to arrange to exchange it for the other type.
Floating licenses should be installed on a central server which is always available. Access to the licenses is managed by a license manager service. Any computer on the same network which can access the license server, is able to use a license. Because floating licenses require a central server with a license manager service, your company IT service will normally be required to help install the licensing system.
Floating licenses can be borrowed from the server in order to have a license available on a specific machine without network access. This facility is not intended for routine use. Borrowing is used when the user does not have access to your office network, for example an offshore trip.
As mentioned above, licenses can be moved between machines, although this should not be done with excessive frequency. Local licences are much simpler to install than floating licenses, because no license manager server is required.
I checked the server and says it is running. I have restarted it, rebooted, reread the license file, checked the firewall settings. It was working last week. I've also deleted the concurrent_state.xml and activation_state.xml files (read here that might work).
Not sure what to try next. I did see one odd thing, and that was the MAC address in the licence file does not match the MAC address being used under License Server Name: localhost MAC Address. I checked our other instrument and PC and it shows the same thing (and is working).
The MAC addresses haven't changed. The licence file was generated using the MAC address of the motherboard. The instrument is connected to an extra network card. I tried swapping the network connection to the extra card and connecting the instrument to the motherboard card but that didn't help.
I think I have it figured out. The AgilentOpenABCDSChemStation feature is missing from the license file. Will have to request a new license file that includes it (where the old one went I have no idea!)
I installed pgi as root and may want to use it as root as well as when logged in as a user so generated flexlm licenses. I think (but am far from sure) that I put things in the correct places to start the flexlm manager at boot time. Lack of confidence is related to redhat directions being mapped onto SuSE.
Hi Steve,
To use lmgrd through a firewall, you first need to fix the port which lmgrd listens on and then fix which port pgroupd uses. (See the PGI Installl FAQ page). Note that Macrovision has recently changed their recommended lmgrd port to 27000 (See Here)