Q100211: How to check which licenses are available from an RLM server

Follow

SUMMARY

This article explains how you can use check the status of your RLM server and see what licenses are available.  You can do this using the rlmutil program that is installed with the license server. You can also view what licences are installed on your server machine via the FLU 8 and above.

 

USING THE TERMINAL OR COMMAND PROMPT

The RLM server software included in the Foundry Licensing Tools (FLT) also includes a command line utility a program called for querying and managing the server called "rlmutil".  This is installed in the following location on the server machine:

  • Linux: /usr/local/foundry/LicensingTools<version>/bin/RLM/rlmutil
  • OSX: /Applications/TheFoundry/LicensingTools<version>/bin/RLM/rlmutil
  • Windows: C:\Program Files\The Foundry\LicensingTools<version>\bin\RLM\rlmutil.exe
 
To get check that the server is up, get a list of all the available licenses and see who is using them by running rlmutil with either of the following commands
 
rlmutil rlmstat -c /path/to/foundry_float.lic -a
 
rlmutil rlmstat -c 4101@serverName -a
 
where /path/to/ is the RLM license directory on the server and "serverName" is the hostname or IP address of your license server.
 
If you want to be able to check the server from another machine on your network then you can copy the "rlmutil" executable to a central location and run it with the second command above.
More information on the rlmutil and how to use this can be found here:Q100659: What are the RLM utilities (rlmutil) and how can I use it?
 

USING THE FLU 8 OR ABOVE

One of the features included in the Foundry Licensing Utility (FLU) 8 and above is the ability to view a summary of the licenses installed on your machine. 
More information on this can be found here: Q100522: How to view the licenses installed on your machine using the Foundry Licensing Utility (FLU)

 

FURTHER READING

For more information on the RLM web server please visit the RLM Enduser Guide

    We're sorry to hear that

    Please tell us why