How to review your network installation set up

Information

 
QuestionHow to review your network installation set up
Answer
Step 1: Verify service and daemon version on the license server

We ship and install lmgrd as the license manager/service. As this is the most common, I'll refer to this below. If you are running lmadin (aka FlexNet Publisher) as your license manager, the procedure will be different, but the results will be the same.

1. Using lmtools.exe (Windows only, the default path is C:\Program Files (x86)\AGI\STK License Server\lmtools.exe), or lmutil (command line utility included with the license service install for all OS's), check the version of the license manager (lmgrd) and the daemon (STKD) as shown here:

 
check version
The version required will be dependent on the version of the STK licenses to be served.
 
FlexNet v11.14.1.2 or higher is required if you have STKv11.3 licenses
FlexNet v11.13 or higher is required if you have STKv11 licenses
FlexNet v11.9 or higher is required if you have STKv10 licenses 
 
Step 2: Verify the SERVER set-up

1. On Windows, you can use lmtools.exe to verify the configuration. Open lmtools, and  go to the “Config Services” tab. Verify that you are browsed correctly to the server (not client) license file, and that the lmgrd.exe path is the default path for the STK lmgrd (C:\Program Files (x86)\AGI\STK License Server\lmgrd.exe).  If you need to make changes, be sure to click “Save Service.” 
 
User-added image

On all other OS's, these paths are specified when starting the license service - lmgrd - via command line options:
 
usage: lmgrd [-l [+]debug_log_path] [-2 -p] [-z] [-c license_file_list]
             [-v] [-local]
             [-x lmdown|lmremove] [-help]
Use -l option before other options to log all debugging information to debug_log_path.

* NOTE: Specify a debug log file path. This is useful to have in solving any issues that may arise.

2. In lmtools.exe, from the “Server Status” tab, click “Perform Status Enquiry” to make sure the server is seeing the correct license count and available license seats.  If the server does not appear to be started, go to the “Start/Stop/Reread” tab, STOP the server, then START the server.  Then, do a 'Perform Status Enquiry' again.
 
Perform Status Enquiry
Using lmutil with the the 'lmstat' option, the same results can be check.
 
lmutil lmstat

Step 3: Check the license file

1. Check the server license file. The SERVER line identifies the HostName or IPAdddress and the HostID (aka Ethernet address) of the SERVER. Verify that these are correct using lmtools.exe or lmutil.
 
System Settings
If other manual edits were made to the server license file, such as changing the HostName or IPAddress, or adding TCP/IP ports, a path to the daemon, or a path to an options file, verify that these edits were correctly made.
 
Step 4: Verify the CLIENT set-up only after the server is confirmed started
Utility:  STK License Manager on the user workstation
 
1. Use the “Manage Licenses” tab of the “STK License Manager” (Windows "Start," => All Programs => STK Support Tools => License Manager) to review your client workstations.  The client workstations should have the client file, not the server file, installed. 

2. Highlight that client license, which should appear in the middle window of that Manage Licenses tab.

3. Click the green check mark for the status.

 
User-added image

4. If the client licenses do not return a status that is green and happy, then be sure that the license manager and daemon (lmgrd and STKD, or the user defined TCP/IP ports) are both allowed thru any server firewalls. 
  • If the STKD.exe and lmgrd.exe are allowed thru any firewalls and the client machines still cannot connect, but they can ping the server, then you may need to add specific port references to both the server and the client license files. 
  • By default, STK uses ports 27000-27009, but sometimes those are not the most optimal ports for your particular installation.  Users have the ability to add specific port references to the server/client license files to force STK traffic down whatever path suits your specific setup best. 
  • If you do add specific port references, be sure you make the exact same change to both the server and the client license files or the connection between the two will break. 



 
Resource File 1 
Resource File 2