Learning Forum

[RCC Operator]

Hello Community,

We have an Ansys License Server running with a license file for Lumerical configured with the license manager daemon on port 27011 and the vendor daemon (ansyslmd) on port 27012. This license file has a set of features/increments that belong to an internal group in our organization. We have another internal group in our organization who purchased a separate Ansys license file for the same product and we would like to add this same license file to our existing license server. The problem is that we would like to keep this second license server and its features in a separate port in order to avoid that one group uses license seats from the other. Is this possible? We tried to change the vendor port in one of the license files and add it to the license server, but this did not work.

If not, what would be the recommendation to have two independent Ansys license files in a single license server? We also tried to install a separate Ansys license server from scratch in the same machine, but there were conflicts because Tomcat was already running for the first installation.

 

Thank you for any recommendations.

 

Kind regards,

Gustavo Garcia Rondina, PhD

Research Computing Center

University of Chicago

[Mrunali Barde]

Hello team RCC, 

Yes, you can have 2 license files on the same server. 
I do not believe that 2 license managers can be present on the same server. 

I'd suggest using an options file to separate licenses as per user or group. 
References: 

https://optics.ansys.com/hc/en-us/articles/4403333893267-Controlling-access-to-the-license-using-the-options-file

I hope this helps, 
Mrunali. 

[RCC Operator]

 

 

 

Hi Mrunali,

Thank you for your reply! Could you please point me out to a resource indicating how to have 2 license files on the same server? We attempted doing it in two ways, below I focus on a single feature, but the beahavior is the same for more features. License details were redacted from the files for privacy reasons.

1) Two separate license files

In this case we have two files:

 

 

 

# ansyslmd1.lic
SERVER licenses.rcc.local aabbccddeeff 27011
VENDOR ansyslmd port=27012
USE_SERVER

INCREMENT optislang_level3 ansyslmd 9999.9999 04-aug-2025 2 \
AABBCCDD123 VENDOR STRING="customer:111111 tp:a" SUPERSEDE \
ISSUER=SIEBEL ISSUED=09-aug-2022 START=05-aug-2022 SIGN2="XXXX \
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \
XXXX XXXX"

 

 

And:

 

 

# Second file: ansyslm21.lic
SERVER licenses.rcc.local aabbccddeeff 27011
VENDOR ansyslmd port=27022
USE_SERVER

INCREMENT optislang_level3 ansyslmd 9999.9999 08-sep-2024 1 \
EEFFGGHHJJ123 VENDOR_STRING="eval customer:222222 tp:a" \
SUPERSEDE ISSUER=SIEBEL ISSUED=19-aug-2024 START=09-aug-2024 \
SIGN="YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \
YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \
YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY"

 

 

As you can see, both files have the same feature “optislang_level3”, but the first has 2 seats, and the second has 1 seat. Both are related to different customers, and have different issuance/expiration dates. Restarting the license server with these two files in the license_files directory makes only the second one to be active, e.g., running lmutil lmstat yields:

 

 

 

License server status: 27011@licenses.rcc.local
    License file(s) on licenses.rcc.local: /srv/ansys_inc/shared_files/licensing/license_files/ansyslmd1.lic:/srv/ansys_inc/shared_files/licensing/license_files/ansyslmd2.lic:
licenses.rcc.local: license server UP (MASTER) v11.19.0

Vendor daemon status (on licenses.rcc.local):
  ansyslmd: UP v11.19.0

Feature usage info:

Users of optislang_level3:  (Total of 1 license issued;  Total of 0 licenses in use)

 

 

 

 

2) Merging into a single license file

We have also attempting creating a single license file:

 

 

 

# ansyslmd.lic
SERVER licenses.rcc.local aabbccddeeff 27011
VENDOR ansyslmd port=27012
USE_SERVER

INCREMENT optislang_level3 ansyslmd 9999.9999 04-aug-2025 2 \
AABBCCDD123 VENDOR STRING="customer:111111 tp:a" SUPERSEDE \
ISSUER=SIEBEL ISSUED=09-aug-2022 START=05-aug-2022 SIGN2="XXXX \
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \
XXXX XXXX"

INCREMENT optislang_level3 ansyslmd 9999.9999 08-sep-2024 1 \
EEFFGGHHJJ123 VENDOR_STRING="eval customer:222222 tp:a" \
SUPERSEDE ISSUER=SIEBEL ISSUED=19-aug-2024 START=09-aug-2024 \
SIGN="YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \
YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \
YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY"

 

 

 

But in this case the same happens, only the feature with 1 seat is shown.

If we start the server only with the  AABBCCDD123 license, then it correctly shows the two seats:

 

 

Users of optislang_level3:  (Total of 2 licenses issued;  Total of 0 licenses in use)

 

 

But then if we append the second license (EEFFGGHHJJ123) and re-read the file and restart the server, what we see in the log is:

 

 

9:41:46 (ansyslmd) Feature optislang_level3 superseded by optislang_level3
9:41:46 (ansyslmd) optislang_level3
9:41:46 (ansyslmd) Rereading options file...
9:41:46 (ansyslmd) =====================================================================================
9:41:46 (ansyslmd) ==== Reread : Feature List and Client Validation Initiated ===
9:41:46 (ansyslmd) =====================================================================================
9:41:46 (ansyslmd) === ls_client_removal_on_reread is disabled ===
9:41:46 (ansyslmd) Support removed for feature optislang_level3(AABBCCDD123) [FEATURE_REMOVED]
9:41:46 (ansyslmd) =====================================================================================

 

 

 

And then only the second license is shown. Is the SUPERSEDE option at play here? Can we just remove that?

Looking forward to any recommendations.

Thank you,
Gustavo

 

 

 

 

[Mrunali Barde]

Hello Gustavo, 

The licenses are getting superseded. Can you please regenerate both licenses and make sure the issue date of both license file is same. 
We cannot directly remove supersede, we can create both files with same issue date to eliminate the issue. 

Once done, make sure to add both the licenses (one file at a time) in Ansys license manager. 

Wishes, 
Mrunali.