Skip to main content

NI VLM

To monitor NI Volume License Manager (NI VLM) in OpenLM Platform, including the licenses that NI VLM disconnects for computers that are isolated from your network, configure OpenLM Broker with the NIVLM license manager type. NI VLM runs a FlexNet license server, so OpenLM Broker queries it with lmutil, as it does a FLEXlm license server. With the NIVLM license manager type, Broker also runs nivlmcmd.exe, the command-line tool of NI VLM, to export the disconnected licenses, and reports each one as a borrowed license.

Note

Broker can also monitor NI VLM with the FLEXlm type, as described in Flexera FlexNet (FLEXlm). That type does not report the disconnected licenses as borrowed licenses. Known limitations lists what the NIVLM type does differently.

Before you begin​

Confirm these prerequisites:

  • OpenLM Platform.
  • OpenLM Broker v26.7.8.1247 or higher, installed on the NI VLM server machine. Earlier Broker releases do not list NIVLM as a license manager type. Broker must run on that machine, because it runs nivlmcmd.exe locally.
  • The Broker approved in Broker Hub. OpenLM Platform accepts license manager data only from approved Brokers, so the NI VLM entry does not reach Pending Servers until the Broker itself is approved.
  • NI Volume License Manager 2025 Q4 or higher. NI added the disconnected-usage export to nivlmcmd.exe in that version.
  • nivlmcmd.exe in the NI VLM installation folder, by default C:\Program Files (x86)\National Instruments\Volume License Manager\nivlmcmd.exe.
  • A Broker service that runs with administrator rights on the NI VLM server. nivlmcmd.exe does not run without them.
  • The Main Licensing Port of NI VLM. The default is 27000. To check it, open NI VLM and select Tools, then Preferences, then General.

What you can monitor​

With the NIVLM type, Broker sends OpenLM Platform the same lmstat report of the license server as the FLEXlm type, with two changes:

  • Disconnected licenses: Broker adds each license from the nivlmcmd.exe export to its feature, as a borrowed license. It raises both the issued total and the in-use count of the feature by the number of disconnected licenses that it adds.
  • Reservations: Broker removes every reservation line from the report, and subtracts the reserved licenses from the licenses in use. In the lmstat report of NI VLM, disconnected licenses appear among the reservations for host groups, and the report does not show which reservations are disconnected.

For each disconnected license, Broker reports:

  • Feature name: the PackageName value of the export, for example LabVIEW_Pro_PKG.
  • Username and Workstation: the computer name in ClientName. From NI VLM 2026 Q3, NI disconnects only computer-based licenses.
  • Start time: the CreationDateTimeUTC value, when NI VLM created the disconnected license.
  • Linger time: the time from CreationDateTimeUTC to ExpirationDateTimeUTC, the expiration of the disconnected license.

How OpenLM Platform interfaces with NI VLM​

The following diagram shows how OpenLM Broker collects NI VLM license usage and sends it to OpenLM Platform.

Diagram of OpenLM Broker on the NI VLM server machine running lmutil and nivlmcmd.exe, and sending license data to OpenLM Platform over HTTPS on port 443 How OpenLM Platform collects NI VLM license usage

Broker runs on the NI VLM server machine and sends the license data to OpenLM Platform over HTTPS, on outbound port 443. For NI VLM, it runs two command-line tools and reads no log file. The following points describe how it collects NI VLM data:

  • Commands: The Data Inquiry command holds two commands, separated by a semicolon, and runs every 55 seconds by default:

    "<Executable path>lmutil" lmstat -a -c <port>@<Host> -i;"<Executable path>nivlmcmd.exe" disconnected-usage {$destination_path}

    Broker runs lmutil first and nivlmcmd.exe second, on every run. A failure of one does not stop the other.

  • Export: nivlmcmd.exe writes the licenses that are disconnected at that moment to a CSV file named after the date and time, such as nivlm-disconnected-usage-2026-10-23_09-15-42.csv. Broker replaces {$destination_path} with the nivlm folder of the Broker installation, reads the newest file there, and deletes all but the two newest files. A file has one row per disconnected license:

    LicenseName,PackageName,ClientName,IsUser,HostIdLockedTo,CreationDateTimeUTC,ExpirationDateTimeUTC,ReconnectDateTimeUTC,ReconnectReason
    LabVIEW Professional Development System,LabVIEW_Pro_PKG,WS-1001,False,0A1B2C3D4E5F,2026-10-01 08:30:00,2027-01-31 22:59:59,,

    Broker reads PackageName, ClientName, CreationDateTimeUTC, and ExpirationDateTimeUTC, and ignores the other columns.

  • Report: Broker adds each row to the Users of <PackageName>: block of the lmstat output, in the form of a borrowed license, with the linger time in seconds:

    WS-1001 WS-1001 WS-1001 (nivlm01.example.com/27000 1), start Thu 10/1 08:30 (linger: 10592999)

    Broker adds a row only when the lmstat output has a block for its PackageName, and drops the other rows.

  • Sessions: Each data inquiry reports the licenses that are disconnected at the time of the data inquiry. When the NI VLM administrator reconnects a computer, its licenses leave the export, so the next report no longer holds them.

  • Log files: None. The NIVLM type defines no log file type of its own, and the Log Files tab offers only Other.

Test the NI VLM export​

Broker reports only what nivlmcmd.exe exports, so run the export by hand on the NI VLM server first.

  1. Close NI Volume License Manager in every session on the server, including disconnected Remote Desktop sessions of other users.

    nivlmcmd.exe does not run while the NI VLM user interface is open.

  2. Open Command Prompt as administrator.

  3. Run the export to a folder that exists, for example C:\Temp:

    "C:\Program Files (x86)\National Instruments\Volume License Manager\nivlmcmd.exe" disconnected-usage C:\Temp

    The tool answers Report exported successfully to, followed by the path of the new CSV file.

  4. Open the CSV file and confirm that it lists the disconnected licenses that you expect, with one row per license.

Configure OpenLM Broker​

To configure OpenLM Broker for NI VLM:

  1. Open the Broker UI for the Broker on the NI VLM server machine.

    • On the NI VLM server machine: open http://localhost:5090/. Local access needs no credentials.
    • From any other machine: open Broker Hub in OpenLM Platform and select the Broker UI icon of that Broker. This opens the interface with the remote access token handled for you.
  2. On the License Managers page, set Host to the host name of the NI VLM server machine.

  3. Select the save icon next to the field.

    Set Host before you add the license manager, because Broker writes the host name into the lmutil command when you add it.

  4. If Broker already monitors this NI VLM server as FLEXlm, copy the settings of that license manager, such as the license file path.

  5. If Broker already monitors this NI VLM server as FLEXlm, delete that license manager from the License Managers list.

    Broker refuses a port that another license manager on this Broker already uses, even one that is turned off, and the NIVLM type queries the same port.

  6. Select License Managers, then Add License Manager.

  7. From LM Type, select NIVLM, not FLEXlm.

  8. In Port, enter the Main Licensing Port of NI VLM, for example 27000.

  9. Select Add.

    The Add License Manager dialog with LM Type set to NIVLM and port 27000 Add NI VLM as a license manager

  10. On the Commands tab, select Data Inquiry.

  11. Change the path of nivlmcmd.exe in the command.

    Broker fills in both commands with the Executable path, the tools64 folder of the Broker installation. lmutil runs from that folder, but nivlmcmd.exe is in the NI VLM installation folder. Replace the path in front of nivlmcmd.exe with that folder, and leave the rest of the command as it is:

    "C:\Program Files\OpenLM\OpenLM Broker\tools64\lmutil" lmstat -a -c 27000@nivlm01.example.com -i;"C:\Program Files (x86)\National Instruments\Volume License Manager\nivlmcmd.exe" disconnected-usage {$destination_path}

    Keep {$destination_path}. Broker reads the export only from the nivlm folder of the Broker installation, and replaces {$destination_path} with that folder when the command runs. Broker runs the command every 55 seconds (Watch interval (sec)).

    The Commands tab with Data Inquiry selected and the Data Inquiry command for port 27000, with the full path of nivlmcmd.exe in the NI VLM installation folder Point the Data Inquiry command at nivlmcmd.exe

    If you change Executable path later, or select Restore Default, Broker puts back the default command. Change the path of nivlmcmd.exe again afterwards.

  12. Leave the Vendors and Log Files tabs as they are.

  13. Select Save.

    The Vendors tab lists a vendor named NIVLM, which Broker adds for this type.

  14. Wait a few minutes.

    Broker runs the Data Inquiry command and reports NI VLM to OpenLM Platform. The license server then reaches Pending Servers.

Approve NI VLM in OpenLM Platform​

Broker reports NI VLM with the license manager type NIVLM and names the license server after the Host that you set in the Broker UI. The pending entry is listed by that host name and the port, with License Manager Type shown as NIVLM.

To approve NI VLM in OpenLM Platform:

  1. Sign in to OpenLM Platform with the URL your administrator gave you.

  2. Select Navigation (the grid icon in the OpenLM Platform header), then Licenses and Features, then License Servers.

  3. Select Pending Servers.

  4. Find the row whose Host Name and Port match the host name and the port that you configured in Broker.

    Its License Manager Type is NIVLM.

  5. Select that row, then Approve And Merge.

  6. On the Approve License Server page, check the settings.

    License Manager Type shows NIVLM, and you cannot change it.

  7. Select Approve.

Verify the integration​

To verify the integration:

  1. In OpenLM Platform, select License Servers, then under Operational, select Live Servers Statistics.

  2. Find the row for the license server and its port, and confirm that Status is Up.

    Confirm that RSQT (Recent Successful Query Time), the last time OpenLM Platform received data from the license server, is recent.

  3. Open Licenses (Navigation, then Licenses and Features, then Licenses) and select Live Statistics.

    Check that the features of NI VLM appear with the totals and the licenses in use that lmstat reports.

  4. Select a feature's Used count to confirm that sessions arrived.

    The count opens the Usage app on Currently Consumed Licenses. Check that each disconnected license of the feature appears with Borrowed, and with the computer name as User Name and Workstation. To see when it expires, add the Linger Due column from the grid menu (⋮, then Columns).

Troubleshooting​

The following entries cover NI VLM that does not reach Pending Servers, a Data error status, Broker log messages, and disconnected licenses that are missing from OpenLM Platform.

Why does NI VLM never reach Pending Servers?​

Open Broker Hub and confirm that this Broker appears under Brokers with status Up, and not under Pending Brokers. OpenLM Platform accepts license manager data only from approved Brokers.

Why does Live Servers Statistics show the Data error status?​

If Live Servers Statistics shows the Status Data error, hover over the status to see the reason. When the reason is Parsing failed. Data format is wrong. Can't convert xml., OpenLM Platform cannot read the report of the license manager. Open a ticket from the Customer Portal, and attach the Broker log of the license manager.

Which Broker log messages explain the problem?​

Broker writes the messages of this license manager to port-<port>-NIVLM.log, for example port-27000-NIVLM.log, in the logs folder of the Broker installation. The messages in this list are ERROR messages, so they appear at the default log level. Compare the log with these cases:

  • NiVLM nivlmcmd sub-command failed: followed by the reason, this message means Broker cannot run nivlmcmd.exe. Check the path of nivlmcmd.exe in the Data Inquiry command, as described in Configure OpenLM Broker.
  • NiVLM nivlmcmd produced no CSV content in: followed by the folder, this message means the nivlm folder holds no export. Run the export by hand, as described in Test the NI VLM export. If the tool answers Error 17001: NI Volume License Manager is already running., the NI VLM user interface is open in a session on the server. Close it in every session. If the export works by hand but not from Broker, check that the Broker service runs with administrator rights. Without them, nivlmcmd.exe answers Please run the application as an administrator.
  • NiVLM lmutil sub-command produced no output: Broker cannot query the license server. Check the port and Host of the license manager.

Why is a disconnected license in the export but not in OpenLM Platform?​

Compare its PackageName with the features of the license server. Broker adds a row only to a feature that the lmstat output lists with the same name, and drops the other rows without an ERROR message.

Known limitations​

These limits apply to NI VLM monitoring with the NIVLM type:

  • Broker exports only the licenses that are disconnected at the time of the data inquiry. OpenLM Platform gets no history of the licenses that NI VLM disconnected before you configured the license manager.
  • Broker removes every reservation line from the lmstat report, including reservations that are not disconnected licenses. OpenLM Platform shows no reservations for this license server.
  • Each disconnected license arrives with the computer name as both the username and the workstation.
  • A disconnected license that never expires, Permanent in the export, has no linger time. Broker adds it without one, so it is not marked as borrowed.
  • If nivlmcmd.exe fails, Broker reads the newest export that is already in the nivlm folder. OpenLM Platform then keeps showing the disconnected licenses of that export until an export succeeds.
  • The NIVLM type has no FlexLM Debug Log File log type, the log from which the FLEXlm type reads denials.
  • The default Data Inquiry command looks for nivlmcmd.exe in the Broker tools folder. Change its path by hand, as described in Configure OpenLM Broker.
  • Detect on the License Managers page does not add NIVLM license managers. Add the license manager by hand.

The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.