


{"id":379851,"date":"2024-08-22T15:49:20","date_gmt":"2024-08-22T15:49:20","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/379851\/"},"modified":"2024-08-22T15:59:44","modified_gmt":"2024-08-22T15:59:44","slug":"379851","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/379851\/","title":{"rendered":"Reply To: Multiple License Files in the Same License Server"},"content":{"rendered":"<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;Hi Mrunali,&lt;\/p&gt;&lt;p&gt;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.&lt;\/p&gt;&lt;p&gt;<strong>1) Two separate license files<\/strong>&lt;\/p&gt;&lt;p&gt;In this case we have two files:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;span style=\"font-size: 12pt;\"&gt;# ansyslmd1.lic&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SERVER licenses.rcc.local aabbccddeeff 27011&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;VENDOR ansyslmd port=27012&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;USE_SERVER&lt;br&gt;&lt;br&gt;&lt;\/span&gt;&lt;span style=\"font-size: 12pt;\"&gt;INCREMENT optislang_level3 ansyslmd 9999.9999 04-aug-2025 2 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;AABBCCDD123 VENDOR STRING=\"customer:111111 tp:a\" SUPERSEDE \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;ISSUER=SIEBEL ISSUED=09-aug-2022 START=05-aug-2022 SIGN2=\"XXXX \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;XXXX XXXX\"&lt;br&gt;&lt;\/span&gt;&lt;br&gt;&lt;br&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;And:&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;span style=\"font-size: 12pt;\"&gt;# Second file: ansyslm21.lic&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SERVER licenses.rcc.local aabbccddeeff 27011&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;VENDOR ansyslmd port=27022&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;USE_SERVER&lt;\/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;INCREMENT optislang_level3 ansyslmd 9999.9999 08-sep-2024 1 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;EEFFGGHHJJ123 VENDOR_STRING=\"eval customer:222222 tp:a\" \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SUPERSEDE ISSUER=SIEBEL ISSUED=19-aug-2024 START=09-aug-2024 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SIGN=\"YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY\"&lt;\/span&gt;&lt;br&gt;&lt;br&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;As you can see, both files have the same feature &ldquo;optislang_level3&rdquo;, 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 <em>license_files <\/em>directory makes only the second one to be active, e.g., running <em>lmutil lmstat<\/em> yields:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;span style=\"font-size: 12pt;\"&gt;License server status: 27011@licenses.rcc.local&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;  &nbsp; 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:&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;licenses.rcc.local: license server UP (MASTER) v11.19.0&lt;\/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;Vendor daemon status (on licenses.rcc.local):&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;  ansyslmd: UP v11.19.0&lt;\/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;Feature usage info:&lt;\/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;Users of optislang_level3:&nbsp; (<strong>Total of 1 license issued<\/strong>;&nbsp; Total of 0 licenses in use)&lt;\/span&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;<strong>2) Merging into a single license file<\/strong>&lt;\/p&gt;&lt;p&gt;We have also attempting creating a single license file:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;span style=\"font-size: 12pt;\"&gt;# ansyslmd.lic&lt;br&gt;&lt;\/span&gt;&lt;span style=\"font-size: 12pt;\"&gt;SERVER licenses.rcc.local aabbccddeeff 27011&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;VENDOR ansyslmd port=27012&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;USE_SERVER&lt;br&gt;&lt;br&gt;&lt;\/span&gt;&lt;span style=\"font-size: 12pt;\"&gt;INCREMENT optislang_level3 ansyslmd 9999.9999 04-aug-2025 2 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;AABBCCDD123 VENDOR STRING=\"customer:111111 tp:a\" SUPERSEDE \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;ISSUER=SIEBEL ISSUED=09-aug-2022 START=05-aug-2022 SIGN2=\"XXXX \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;XXXX XXXX\"&lt;br&gt;&lt;br&gt;&lt;\/span&gt;&lt;span style=\"font-size: 12pt;\"&gt;INCREMENT optislang_level3 ansyslmd 9999.9999 08-sep-2024 1 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;EEFFGGHHJJ123 VENDOR_STRING=\"eval customer:222222 tp:a\" \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SUPERSEDE ISSUER=SIEBEL ISSUED=19-aug-2024 START=09-aug-2024 \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;SIGN=\"YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY \\&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;YYYY YYYY YYYY YYYY YYYY YYYY YYYY YYYY\"&lt;\/span&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;But in this case the same happens, only the feature with 1 seat is shown.&lt;\/p&gt;&lt;p&gt;If we start the server only with the &nbsp;AABBCCDD123 license, then it correctly shows the two seats:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;Users of optislang_level3: &nbsp;(<strong>Total of 2 licenses issued<\/strong>; &nbsp;Total of 0 licenses in use)&lt;br&gt;&lt;\/span&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&lt;br&gt;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:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n<pre>&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) <strong>Feature optislang_level3 superseded by optislang_level3<\/strong>&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) optislang_level3&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) Rereading options file...&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) =====================================================================================&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) ==== Reread : Feature List and Client Validation Initiated ===&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) =====================================================================================&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) === ls_client_removal_on_reread is disabled ===&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) <strong>Support removed for feature optislang_level3(AABBCCDD123) [FEATURE_REMOVED]<\/strong>&lt;\/span&gt;&lt;br&gt;&lt;span style=\"font-size: 12pt;\"&gt;9:41:46 (ansyslmd) =====================================================================================&lt;\/span&gt;&lt;br&gt;&lt;br&gt;<\/pre>\n<p>&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;And then only the second license is shown. Is the <em>SUPERSEDE <\/em>option at play here? Can we just remove that?&lt;\/p&gt;&lt;p&gt;Looking forward to any recommendations.&lt;\/p&gt;&lt;p&gt;Thank you,&lt;br&gt;Gustavo&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;<\/p>\n","protected":false},"template":"","class_list":["post-379851","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"acf":[],"_links":{"self":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/379851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies"}],"about":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/types\/reply"}],"version-history":[{"count":3,"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/379851\/revisions"}],"predecessor-version":[{"id":379856,"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/379851\/revisions\/379856"}],"wp:attachment":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/media?parent=379851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}