License Restriction issue

[ImIronMan]

Hello,

We have created 2 licenses for SQL , one is for Clusters and another one is for Non-Clusters and we have scoped the "cluster" to a particular location "randburg" and ensured all the devices are tagged to this "randburg" location.

However, we have noticed that few of the devices (with location randburg) are being consumed by "Non-Cluster" license ignoring the above restriction.

As a first check, I've checked the applications which are linked to those 2 licenses, which seems to be okay and the "license priority" has been set to use "Cluster" license first, but still, these few devices are consuming Non-Cluster license of sql.

Can you please help, how to fix this issue

@ChrisG @mpeters 

[mfranz]

Hi,

Does the "Cluster" license have enough entitlements? A restriction does not keep FNMS from using other licenses which do also apply.

You could test if allocations do work. And/or you could try to restrict the "Non-Cluster" license to anything but "Randburg".

Best regards,

Markward

[Nico_Erasmus · Accepted solution]

Hi Rajesh.

If you read the help docs on restrictions, you will see that restrictions do not force priority - they simply prevent device from outside the restriction consuming the restricted license.

If you set theory will allow, that is "Randburg" only has clusters and "JHB CBD" only has non clustered installs, then place a restriction on your second SQL license too.  Additionally, you can use group assignments to prioritise the consumption of the expected license.

Just be aware of devices that do not meet either restriction as they will fall into unlicensed installation if you have no unrestricted option.