SmarTest Client Information

What is multi-dimensional locking, which FNE supports

With FNP licenses can only be locked to a HOSTID or a system serial number. The locking to the HOSTID is not used anymore.

With FNE it is also possible to lock the licenses e.g. to the upstream of a device, to device categories, the downstream company, … This is meant with multi-dimensional locking.

So it is possible to limit a license to a specific device with FNE.

What are the connection times between client and license server for FNE and FNP?

An FNE client connects to the FNE license server every 20 minutes. And if the connection fails another FNE license server can be connected (if defined in /etc/fne/client.conf) to get the same license.

An FNP client tries to connect to the FNP license server every 2 minutes. When this connection fails SmarTest starts the grace period and shuts down at the end of the grace period, if a reconnection to the same FNP license server is not possible.

How does SmarTest read the client.conf configuration file?

Explanation on FNE license check-out behavior / order for FNE servers defined in the client.conf file

Q1:  If two servers are defined in the client.conf file, is there any order where the licenses got checked out?

The sequence is down top down, so first entry gets queried first and if the license is not available, the next entry in line will be queried.

Q2: Or are both servers always queried?

If the response from the first entry is positive and the license is checked out, there is no additional query to other servers.

Q3: Is there any technical reason why ELF lics seems to be checked out preferentially?

They are preferred due to the FULL_CAPABILITY license. If any FULL_CAPABILITY licenses is found, this lic will get checked out with priority, even if it's from the second server