cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cjustinek
Level 3

Mixed node-locked and floating license not working

Jump to solution

Hello guys,

I am facing a problem on my license file.  The license file looks almost like the one in the documentation:

 

 

SERVER lulu 17001234 1700
VENDOR sampled C:\flexlm\sampled.exe
FEATURE f1 sampled 1.00 31-dec-2020 2 HOSTID="HOSTNAME=asdf HOSTNAME=fdsa" SIGN=”<...>”
FEATURE f1 sampled 1.00 31-dec-2020 2 SIGN=”<...>

 

 

 

The error in the debug.log says, that hostname "AAAA" was denied for the feature f1 because it is an invalid host (-9.333).

We are using FlexNet licensing v11.18.3.0.

 

Did I understand the documentation wrong? Is it not possible to combine a floating and a node-locked license in a file?

Second question: is there any prioritization? Is client asdf using a floating license even if the host has an own node-locked license?

 

0 Kudos
1 Solution
mrathinam
Revenera Moderator Revenera Moderator
Revenera Moderator

@cjustinek Yes, You are right, I can replicate the issue, its due to the order the license is trying to checkout, so I used sort=1 and Crypted 

--

INCREMENT f1 qavend1 1.00 31-dec-2022 1 HOSTID="HOSTNAME=abcd \
HOSTNAME=BLR-LT-101186_Old" SIGN="0020 2000 AEC8 A374 2826 \
D03A 7E5D 4400 EB48 8252 578A AB91 0377 9283 EBD0"
INCREMENT f1 qavend1 1.00 31-dec-2022 1 sort=first SIGN="00A0 2ED9 1B7E \
C46B 13BE 23F4 4EEE DC00 A9AD 3187 E695 9586 A9EF E945 A5CC"

--

then able to check out the floating license. 

Best Regards,

View solution in original post

7 Replies
mrathinam
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi, @cjustinek to answer your query, can you check the image and check the license file and let me know what is the difference you have in the one which is giving an error?

floating and a node-locked.JPG

For your second query if the license file is like this 
FEATURE f1 qavend1 1.00 31-dec-2022 2 HOSTID="HOSTNAME=BLR-LT-101186 \
HOSTNAME=fdsa" SIGN="00AA 5498 CD8F 5CB5 F22E F248 C4F8 7F00 \
2447 8E6B 3B9A 3A22 4ADE 4215 9665"
FEATURE f1 qavend1 1.00 31-dec-2022 2 SIGN="00CA 4E79 8377 78B7 BCD6 \
DAE3 2AD3 B400 36C7 1791 7FB7 0E75 3F88 7F45 2BE6"

is there any prioritization? Is client HOSTNAME=BLR-LT-101186 using a floating license even if the host has an own node-locked license?

yes, we have Sort Rules 

1. License file. Automatic sorting does not occur across files in a license search path.
2. Feature name.
3. FEATURE before INCREMENT.
4. Uncounted before counted.
5. Version, earlier versions before later versions.
6. Issued date, in reverse order, newest first. The date is taken from ISSUED= or START=.
7. Original order is otherwise maintained.

You can override the automatic ordering by adding the sort attribute for each FEATURE and INCREMENT line. The value defined for the sort attribute identifies the relative position of that feature in the sort order. For example, features with a sort value of 25 will be sorted before those with a sort value of 50. Unless explicitly defined, the sort value for each feature is set to 100. All lines with the same number are sorted as they appear in the file. The value range for the sort attribute is 0 through 255. If you specify a value higher than 255, the encryption process converts it to 255.
Overriding the sort order might be useful to change the order in which licenses are consumed. Consider the following example: A company has multiple pools of licenses with different expiration dates. The company wants their users to first consume the licenses from the pool that expire first. To achieve this, the license administrator can add the sort=1 keyword to the feature line that expires first.

Hope this helps. 

Best Regards,

 

0 Kudos
cjustinek
Level 3

Thanks for the quick reply @mrathinam ,

I'm sorry that I overlooked the sorting in the manual. My bad.

2 node-locked f1 licenses are included as well as one floating (which I would like to use here).

0 Kudos
mrathinam
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi @cjustinek Problem with the HostName in the license file where the license file has s-dop-1 but the actual hostname is s-dop-2, so update the Hostname in the file correctly and then give it a try. There are no issues in checkout as per my test with the HOSTNAME. 

Best Regards,

0 Kudos

But my license file includes an additional f1 floating feature as well. If I would only have the f1 floating (without the f1 floating feature for s-dop-1) the checkout would work.

0 Kudos
mrathinam
Revenera Moderator Revenera Moderator
Revenera Moderator

@cjustinek Yes, You are right, I can replicate the issue, its due to the order the license is trying to checkout, so I used sort=1 and Crypted 

--

INCREMENT f1 qavend1 1.00 31-dec-2022 1 HOSTID="HOSTNAME=abcd \
HOSTNAME=BLR-LT-101186_Old" SIGN="0020 2000 AEC8 A374 2826 \
D03A 7E5D 4400 EB48 8252 578A AB91 0377 9283 EBD0"
INCREMENT f1 qavend1 1.00 31-dec-2022 1 sort=first SIGN="00A0 2ED9 1B7E \
C46B 13BE 23F4 4EEE DC00 A9AD 3187 E695 9586 A9EF E945 A5CC"

--

then able to check out the floating license. 

Best Regards,

I reopen the post here, because the initial issue is still open (and I just realized it).

If I use the following example:

--

INCREMENT f1 qavend1 1.00 31-dec-2022 1 HOSTID="HOSTNAME=abcd \
HOSTNAME=BLR-LT-101186_Old" SIGN="0020 2000 AEC8 A374 2826 \
D03A 7E5D 4400 EB48 8252 578A AB91 0377 9283 EBD0"
INCREMENT f1 qavend1 1.00 31-dec-2022 1 sort=first SIGN="00A0 2ED9 1B7E \
C46B 13BE 23F4 4EEE DC00 A9AD 3187 E695 9586 A9EF E945 A5CC"

--

Host "abcd" will use the floating license (which is set as sort=first) even if it has a dedicated node-locked license.

How do I accomplish, that a node-locked licensed will be used as prio1 and if not suitable, like for host "apppp", the floating licensed will be checked out.

 

Best
Christoph

0 Kudos
mrathinam
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi @cjustinek Thanks for the support case it was resolved now. For other community users, I add more details here. The issue was with the license pool, if you are using both FEATURE lines then it will not create a license pool of two, so change the second Feature line update to INCREMENT as below and now it is working as expected.

FEATURE f1 qavend1 1.00 31-dec-2022 1 HOSTID="HOSTNAME=abcd \
HOSTNAME=BLR-LT-101186" SIGN="0045 30E4 31F7 EFF5 7CA0 \
54C9 792B 9A00 30AB 702E A95C 55F7 2D01 E371 8CFD"
INCREMENT f1 qavend1 1.00 31-dec-2022 1 SIGN="0029 7224 CA2C 8B86 \
6AC7 36BC E510 6900 36D3 C0ED 5A01 FA4A 7945 3C1E 82CF"

Find the lmstat.exe output.

--

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

"f1" v1.00, vendor: qavend1, expiry: 31-dec-2022
nodelocked licenselocked to hostname "abcd"or hostname "BLR-LT-101186"

MRathinam BLR-LT-101186 BLR-LT-101186 (v1.0) (BLR-LT-101186/27000 101), start Mon 8/29 11:50

"f1" v1.00, vendor: qavend1, expiry: 31-dec-2022
floating license

MRathinam BLR-LT-101186 BLR-LT-101186 (v1.0) (BLR-LT-101186/27000 202), start Mon 8/29 11:52

--

First checkout node-locked license if the Hostname is matching or it will go to the second line to check out the floating license. 

Note: I used the same hostname so first it was checked out the Nodelocked then floating. 

Best Regards,

0 Kudos