Table of Contents
This guide provides an overview and best practices for deploying our on-premises license server hardware and network configurations for the nTopology Floating License System. It also contains step-by-step instructions for installing and configuring license server components to get your team up and running on nTopology quickly.
See Revenera’s 'FlexNet Publisher License Administration Guide' for detailed installation and operation instructions.
The nTopology Floating License System is supported on the following platforms:
Microsoft Windows 7
Microsoft Windows 10
Microsoft Windows 11
The nTopology Floating License System must have a license server up and running prior to installation. It’s not recommended that you purchase the nTopology Floating License System for deployment if you do not already have an existing FlexNet Publisher floating license server up and running. Please contact your Account Manager for more information.
We generally recommend not running any additional vendors' license managers or other software from this server as it will reduce performance.
When selecting a license server:
- All files used in conjunction with the license manager software must be located on a disk that is physically local to the server computer(s).
- The license server(s) must have a high-speed, reliable Ethernet connection.
- Computers that experience extremely high levels of network traffic or processing lag due to high CPU and/or I/O usage are poor candidates for license servers.
- Do not use computers that are frequently rebooted.
- The license server machine(s) must have a static IP address
Choose a server model:
- Single Server: 1 license file installed on one server.
- Distributed Servers: Multiple license files installed across multiple servers.
- High-Availability Triad. Licenses are installed on one server, plus two backup servers.
- You must specify a primary server and two redundant servers.
We recommend that you configure multiple single servers instead of a redundant (triad) configuration. If one of the single servers becomes unavailable, then only a portion of your license becomes unavailable, rather than all of them. A redundant-server configuration will add additional network communication overhead, resulting in reduced server performance. When a redundant triad is configured incorrectly, you will lose all of the inherent benefits of redundancy.
If the Triad is your choice for server setup, please consider these specific configurations:
- Choose three machines that are of the same platform type (Windows or Linux).
- All three servers should be on the same subnet in the same physical location.
- Install the license file and entire licensing directory on each of the three license servers.
- Not configuring the servers in this manner defeats the purpose of having redundancy as the server holding these files becomes a single point of failure.
We generally recommend not hosting the nTopology Floating License System with other FlexNet Publisher Vendor Daemons on the same server. However, the system does work on license servers that host other vendors' daemons. For optimal performance with multiple vendor daemons on 1 server please ensure:
- The license server(s) and your network environment have suitable bandwidth appropriate for the total number of product clients served by all vendor daemons.
- We do not support combining the license files from multiple vendor daemons in order to run a single LMGRD.
- Revenera states that multiple machines each running one lmgrd, one vendor daemon, and using one license file is the optimal configuration:
- The license files for each vendor are independent of one another.
- Each server machine can be maintained separately. If one machine goes down, the other machines continue to serve licenses for their vendors.
- Each server has its own debug log.
The primary network settings to configure the nTopology Floating License System are the TCP/IP port settings. 2080, 27000-27009 are the default port(s) for FlexNet Publisher. These settings should only be adjusted in exceptional circumstances, such as to avoid using the same ports as other applications/services on your network.
Our licensing MSI provides local service and network service permissions on installation. Additionally, you should configure any virus scanners, firewalls, and WAN optimization software to allow the various components of the nTopology Floating License System to run & also communicate on the allocated ports. You can edit the license file to use precise port numbers or entirely different port numbers - if necessary.
We do not recommend connecting your license server to your network with a wireless connection as they are simply less stable, less reliable, and transfer speeds are 10X slower than ethernet.
We do not recommend connecting your license server to your network over a VPN due to transfer speeds compared to an ethernet connection.
License File Based Licensing Diagram
Adding Vendor Daemon & License File to Your Licensing Server
Loading License Components To Your Licensing Server
- Download MSI with the following license components from the nTopology Licensing email we sent you.
- nTopology License Manager
- nTopology Vendor Daemon
- nTopology License File
- If you need to produce a host_Id(s) to your Account Manager or Support to set up your license file, open the License Manager folder and run lmutil or lmtools, which will give you the host_id to provide so we can create your license file.
- In lmtools, click System Settings tab, locate Computer/Hostname box
- Locate Ethernet Address box. The 12 character address is the host_id
- Send the host_id to your Account Manager or Support to generate the license file
- Once you have the signed license file, you’ll need to add the server address (and port if running several products from the server) to the file in order to load and run it successfully. See below for how to add these to the file.
- Run your servers on a supported operating system on a stable network and avoid restarts, unless necessary, as they can interfere with continuity of serving floating licenses to your end users.
- Your server(s) should communicate with ports 2080 and 27000-27009. These are the default ports the system uses. Although these ports are configurable, changing them may cause conflicts with other applications. Avoid changing port numbers where possible.
Configuring Your nTopology Licensing Server
- Open LMTOOLS, navigate to Config Settings
- Name the Service, we recommend “nTopLM”
- Browse and load lmgrd.exe
- Browse and load License File
- Click Save Service
Starting Up Your Server
- Navigate to Start/Stop/Reread tab
- Click Start Server
- You will see a success or error message in the bottom left hand corner of the window
Server Status Inquiries
- To check the status of your server, navigate to Server Status tab
- Click Perform Status Inquiry
- Check number of licenses issued for ntop _full
- This number should match the count of licenses purchased.
- Note, if you purchased nTopology CL, you will see a large number of licenses in ntopcl_full, this is simply to enable Organization wide access to nTopology CL so no one is ever denied access
Starting up nTopology & Adding License Server Address (End User)
- Once your license server is up and running with the License Manager (if needed), Vendor Daemon, and nTopology License File, distribute/host the FlexEnabled version of nTopology for your end users to download and install on their machine(s).
- When you start up nTopology for the first time, navigate to the Use Local License button, hold Control button on your keyboard and click Use Local License, which should open the FlexNet License Finder modal.
- Select Specify the License Server System and click Next
- Enter the license server (port if necessary) and address, which your System Administrator should have readily available.
- Click Finish. If a license is available, nTopology will start up.
- If all licenses are checked out, you will receive the following message: