Q100141: Can you float Foundry RLM licenses from another RLM server?
SUMMARYThis article describes what you will need to do if you want to float RLM licences from the Foundry using a 3rd party RLM license server.
MORE INFORMATIONThe Foundry Licensing Tools (FLT) includes everything that you should need to float our licences on your network. However, it is also possible to use a generic 3rd party RLM server if you wish to, for example if you want to float licenses from multiple vendors from a single server.
NOTE: This is not a tested or supported way of floating our licenses so if you run into any problems with this then we may only be able to provide limited help. This article is just to provide guidance.
You would need to do the following.
- Have another RLM server running RLM 9.4bl4 or above.
- Extract the 'foundry.set' file from the /bin/RLM directory of the Foundry Licensing Tools (FLT) install. This file is required for the RLM server to validate the licenses. The file can be found in the following locations after you install FLT:
Windows: C:\Program Files\The Foundry\LicensingTools7.1\bin\RLM
- Put the "foundry.set" file in the same directory as your 3rd party RLM server binary.
You can then uninstall FLT by following this guide: Q100133: How to Uninstall the Foundry Licensing Tools
- Manually install the Foundry RLM license file into the same directory as your 3rd party RLM license directory. You will need to edit the HOST line to put your server's hostname or IP address in place of "<server_name>" and change port 4101 to your chosen port (or remove it altogether to use the default port 5053).
- Restart the 3rd party RLM server. It should then float the Foundry licenses.
If you encounter any problems with your licenses then please follow the instructions in Q100013: Diagnosing License Problems. This explains how to generate a License Diagnostic file and create a Support Ticket. Please note that if the problem is happening whilst using a 3rd party RLM server then we may suggest using the Foundry Licensing Tools instead as these are the supported tools for our licenses.
We're sorry to hear that!Please tell us why.