Linux NLRM Installation Guide
This guide describes installation of Network License and Reporting Manager (NLRM) on a license server. Before installing NLRM, any previously installed Autodesk Network Licensing Solutions (such as NLM and NLRS) should be uninstalled.
In addition, refer to the NLRM Installation Planning Checklist and Linux Preinstallation Guide before proceeding with installation of NLRM to ensure that your license server meets the requirements.
Note: Do not install NLRM on a directory shared over the network
Installation Overview
The Linux installation process includes these five steps:
- Install NLRM
- Configure NLRM
- Test your connection
- Start NLRM
- Verify that the license server is running successfully
Detailed instructions for each of these steps follows.
Install NLRM
This step involves two tasks: Configure license server and NLRM setup.
If you are already using NLRS with start/stop scripts and installing NLRM for the first time, modify the start/stop scripts and change the lmgrd path. The new path of NLRM binaries will be:
- lmgrd:
/opt/Autodesk/NLRM/lmgrd
- lmutil:
/opt/Autodesk/NLRM/lmutil
- Skip this task if you upgraded from a previous version of NLRM.
Note: You no longer need to add the append mode (+) to the start of the selected debug log file.
NLRM setup must be run if:
- This is the first time NLRM is being installed,
OR
- Setup was not run with the earlier version of NLRM installation.
The setup workflow will help you perform following tasks as required:
- Installing the NLRM authorization certificate
- Configuring Personally Identifiable Information (PII) masking
- Configuring customer email address
- Testing your connection
To start this workflow:
Note:
- PII masking flag must be set and should be the same value as used in previous NLRS/NLRM installation.
- If the connection fails please check the proxy and firewall settings
For Token Flex license servers which cannot connect to Autodesk directly, following additional setup is required.
When the transmit-mode is set to manual, you may configure offline duration allowance (1 to 30 days) which is otherwise defaulted to 30 days. The usage data must be exported and transmitted to Autodesk servers, before the configured offline duration allowance is elapsed since the last time usage was collected from the license server.
To set offline duration allowance, use the following command:
sudo ./nlrm_config set offline-duration-allowance-days <number within range 1 to 30>
For data transmission to Autodesk servers, please refer to the instructions here:
If you have configured NLRM previously and wish to perform specific operations only, follow Re-configure NLRM Settings. These commands should be executed in consultation with your Autodesk support contact.
Start NLRM
Note:
- If you have custom stop/start scripts which are using NLRM flexnet binaries, then you can use them to start the license server.
When trying to start the lmgrd on the license server, if the program aborts and print the following error:
lmgrd: No such file or directory
A possible reason is the missing Linux Standard Base (LSB) components which are required by the lmgrd. Run the following command to solve the issue:
For RHEL 9 or Rocky 9
32-bit Linux:
sudo bash -c "if [ ! -e /lib/ld-lsb.so.3 ]; then ln -s ld-linux.so.2 /lib/ldlsb.so.3; fi"
64-bit Linux:
sudo bash -c "if [ ! -e /lib64/ld-lsb-x86-64.so.3 ]; then ln -s ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3; fi"
For all other supported Linux versions
yum -y install redhat-lsb
Verify that your license server is running successfully
Online Server
When the license server starts, it automatically sends a license server start event message back to Autodesk. You can verify that your server is running by following these steps to inspect the application logs:
In a text editor, open: /var/opt/Autodesk/NLRM/4.15/logs/collection_dispatcher_car-park.log
Note: This file is created almost immediately after the license server is started.
A complete segment of the log file should look similar to the following example. If it does, your license server has started and is running correctly.
Starting Autodesk Collection Dispatcher v4.15 ...
Autodesk Server Url => https://car2.autodesk.com
Source => /var/opt/Autodesk/NLRM/car.park
Re-dispatch Target => /var/opt/Autodesk/NLRM/re
Log File => /var/opt/Autodesk/NLRM/4.15/logs/collection_dispatcher_car-park.log
Initializing transmitter ...
Check for messages older than 2022-03-10 04:29:35.842564994 UTC , completed in 33.563µs
Starting to transmit data ...
Sending data: 1
[POST] https://car2.autodesk.com/api/v1/event
request => {"event_origin":{"application_info":{"name":"NLRM","version":"4.15"},...
response_code => 200
response => {"message":"Request has been successfully processed","time_to_next_request_ms":100}
collection_dispatcher::event_processor::web_transmit Message processed successfully.
collection_dispatcher::event_processor::web_transmit Message queue completed processing.
Offline Server
When the license server starts, it automatically creates a license server start event. You can verify that your server is running by following these steps to inspect the application logs:
In a text editor, open: /var/opt/Autodesk/NLRM/4.15/logs/collection_dispatcher_car-park.log
Note: This file is created almost immediately after the license server has started.
A complete segment of the log file should look similar to the following example. If it does, your offline license server has started, and is collecting usage data locally.
Starting Autodesk Collection Dispatcher v4.15 ...
Autodesk Server Url => https://car2.autodesk.com
Source => /var/opt/Autodesk/NLRM/car.park
Re-dispatch Target => /var/opt/Autodesk/NLRM/re
Transmit Mode => manual
Log File => /var/opt/Autodesk/NLRM/4.15/logs/collection_dispatcher_car-park.log
Check for messages older than 2022-03-10 05:46:40.811245673 UTC , completed in 21.52µs
collection_dispatcher::event_processor::manual_transmit Message queue completed processing.
Parent page: About Network License and Reporting Manager (NLRM)
|