Skip to main content

FNX proxy setup questions

Installation questions

If option fnx is used, why is also v93000-fne-client installed?

The fne-client is part of the license software (The client needs to correctly configure the configuration file /etc/fne/client.conf before establishing the connection to the server.).

How to check if proxy related packages are installed or not?

The fne-status command gives you a list of installed packages (requires advantest-fne-server package to be installed).


Are the hostnames for command fne-proxy-setup case-sensitive?

Yes. For example if the hostnames of the second license server is HostX2 and for the third license server is HostY3 then you need to enter the following command for setting up the proxy connection on the primary server.

/opt/flexlm/bin/fne-proxy-setup HostX2 HostY3

The hostnames are case-sensitive here. So you need to take care to use the correct upper and lower letters.


Option file usage information with FNX

With FNX environemnt, FNP clients can use an option file as for FNP. There are two important differences:

  1. The option file is only valid for FNP-clients.
  2. Please put the option file to folder /opt/flexlm/bin. Ideally you use the default option file name socbu.opt. If you do not use the default name, you need to define the name in license file proxy.lic in folder /opt/flexlm/bin as known for FNP.

If the FNE proxy already runs and you installed a new option file or changed an option file you need to restart the proxy with 

sudo systemctl restart advantest-fne-proxy 

to make the new / changed option file effective.


Problem with using MAX 0 in option file - Message "FATAL ... internal error" in the license server log file

Do not use MAX 0 in the option file but use the EXCLUDE keyword.

Reason: if you use MAX 0 in the option file you will get a "FATAL ... internal error" error message in the log file with trying to checkout this license with the user / host which shall not be able to do it. In this case the search algorithm tries to check out -1 licenses and fails and therefore the "FATAL ... internal error" is written to the log file. 

Positive is that the license cannot be checked out as defined with the option file. Therefore, the functionality is working, but there are unnecessary and incomprehensible error messages in the log file.

The use of EXCLUDE instead prevents these error messages.

Back to top