cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ohe_2995
Level 2

How to read a host id node feature license first if the license file contains also a not node locked feature

Hi FlexNet Publisher support team,

 

We have following license file installed on our license server to find out following bug described in this case.

License File:

SERVER this_host VMW_UUID=6D4D3542-523A-7CB0-2605-93454BE6E552 27005

VENDOR AUCOTEC PORT=10001 OPTIONS=AUCOTEC.opt

USE_SERVER

FEATURE 1080 AUCOTEC 1.0 permanent 1 VENDOR_STRING=AUCOTEC BORROW=672 \

         NOTICE="Engineering Base Instrumentation Pro" SIGN="1236 80A8 \

         3D0B A785 F8F5 3728 20B4 8418 A709 9380 91C7 024C 84C4 D69F \

         7093 0667 6ECE CBF2 D4A2 391D 280C 78BC D40B 57C7 179F DB10 \

         5E6A 9E24 F075 0BE1"

INCREMENT 1080 AUCOTEC 1.0 permanent 1 VENDOR_STRING=AUCOTEC \

         HOSTID=HOSTNAME=ohe-pc BORROW=672 NOTICE="Engineering Base \

         Instrumentation Pro node" SIGN="1E28 1943 E3FA F1F8 B31D 6BB1 \

         35B3 7AA3 ADC4 3F02 73A1 099B 38ED E313 9451 1B85 CB1D 225C \

         438C EEC4 D5C5 FCD2 9518 BC83 016D EF8E D756 EFD3 1DC7 7639"

 

Our Bug togeter with FNP:

  1. The INCREMENT line is noded locked to host id “ohe-pc
  2. We have two client computers
    1. ohe-pc
    2. ssi-dev-1
  3. When I first start our application from ssi-dev-1, feature 1080 from “feature line” will be used – ok
    1. Starting out application from ohe-pc will use the noded locked increment line
    2. Both applications are running properly
  4. When I first start our application from ohe-pc, feature 1080 from “feature line” will be used – failed-> increment line should be used
    1. Starting our application from ssi-dev-1 does not get any licence because the feature line is used and the increment line is node locked to another host

Question:

How can I configure FNP that an existing node locked line with valid host is used instead of the not node locked one?

0 Kudos
(2) Replies
aparashar1
Flexera Alumni

@ohe_2995 , conventionally an INCREMENT line can be used in place of a FEATURE line, as well as to incrementally add licenses to a prior FEATURE or
INCREMENT line in the license file. Only the first FEATURE line for a given feature is processed by the vendor daemon.

If you want to have additional copies of the same feature (for example, to have multiple node-locked, counted features), use multiple INCREMENT lines.


To cause multiple FEATURE lines for the same feature to be recognized and processed as INCREMENT lines, set ls_use_all_feature_lines (in lsvendor.c) to a non-zero value.

Hope this helps.

(If my response assists with your questions , then please click "ACCEPT AS SOLUTION" or 'Kudos' so that it help others.)
0 Kudos

@ohe_2995, I think what you need to do is add an EXCLUDE line in your options file.

You can prevent the machine ohe-pc from ever using that floating key.

Use something like:

EXCLUDE 1080:keyword=value HOST ohe-pc

You'll have to choose a keyword and value so that this exclude line only applies to the FEATURE line and not the INCREMENT line.  You can use SIGN but that will change every time you get a new license.   A better option might be to add your own data using asset_info or one of the other unencrypted fields.  This will still require you to edit the license every time you get a new one, but it is a smaller and more readable change. 

Read the FNP "License Administration Guide" for details on how to do this.

0 Kudos