# Failover license server installation, upgrades and updates Installation procedure for a failover FlexNet Embedded license server arrangement to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.
### About this task

Note: It is possible to set up an emergency FNE license server, listed at the end of the client.conf file. In an emergency where the normal license servers are inaccessible, install the emergency licenses on the emergency license server. All clients automatically connect to the emergency FNE license server.

Note: If you are upgrading an existing installation, a running license server is automatically stopped as part of the new software installation.

The following procedure is applicable to installation, upgrades and updates. However, associating the servers (step 2), registering the primary server (step 3), and synchronizing the servers (step 4) are only required for initial installation. These steps should be omitted for upgrades and updates.

Note: During updating, the installation script can be called without any options. All installed packages are detected automatically and updated if applicable.

### **Before you begin** A redundant FNE failover setup consists of two servers; the primary production system and the failover standby system. If the primary system stops working, for example, due to a hardware defect, the failover system assumes the production workload and handles all requests. The period of each failover substitution is limited to a maximum of 5 days. During these 5 days, you must repair and recommission the primary server or set up a new server.

Note: If the failover system goes down while the primary system is handling the production workload, there is no mandatory time limit for getting it running again. However, during this period there is no redundancy backup.

For mixed FNE-FNP environments, also refer to [Mixed FlexNet Embedded and FlexNet Publisher licensing](https://lhc.advantest.com/books/licensing-reference/page/mixed-flexnet-embedded-and-flexnet-publisher-licensing "FlexNet Embedded (FNE) and FlexNet Publisher (FNP) license management can be handled from an FNE license server installation, using the FNP to FNE proxy solution, simplifying license management.") and [Set up a three-license-server redundancy configuration](https://lhc.advantest.com/link/84#bkmrk-set-up-a-three-licen-1 "In a redundancy configuration with three license servers, each of the three license servers runs on its own dedicated machine. Two servers are used to serve licenses and their license files must be kept synchronized. The third server is required to build the quorum, participating in monitoring the availability of at least one license server, but does not serve licenses. Licenses do not need to be installed on the third server.") - Make sure that the system hosting the FlexNet Embedded license server host system meets the hardware and operating system prerequisites. For details and check procedures, see [FlexNet Embedded license server setup](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/flexnet-embedded-license-server-setup "FlexNet Embedded license servers are implemented to provide activated licenses to SmarTest system controllers."). - To be able to detect any license server problems early, we strongly recommend that you plan to include the FNE license servers in your availability monitoring setup. SmarTest cannot inform you about the failure of a license server.
### **Procedure** 1. Install the license server software on the primary server, the failover server, and for mixed FNE-FNP environments, on the FNP tertiary server. Follow the instructions described in the appropriate topic linked below:
**FNE-only environments**
[Single FNE License server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/single-fne-license-server-installation-upgrades-and-updates "Installation procedure for a single FlexNet Embedded license server to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")
**Mixed FNE-FNP environments**
[Single FNP License server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/single-fne-license-server-installation-upgrades-and-updates "Installation procedure for a single FlexNet license server to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")
2. **❗ Not for upgrades or updates** : Associate the failover FNE license server with the primary FNE license server, using a user other than root, on the primary server execute the command: `/opt/flexnetls/socbu/fne-failover-setup . ` 3. **❗ Not for upgrades or updates** : Register the primary FNE license server with the Advantest Licensing Back-Office: `register-fne-server ` For details see [Registering the license server](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/registering-the-license-server "A new license server must be registered with the Advantest FNE Licensing Back-office before it can be used to host licenses."). 4. **❗ Not for upgrades or updates** : Synchronize the FNE license servers: For FlexNet Embedded license servers that are connected to the internet, an automatic synchronization should occur immediately. If this is not the case, you can perform a `sync-fne-server` action on the license server. For FlexNet Embedded license servers not connected to the internet, registering the servers from the primary server (uploading the registration-request-file to the Advantest Licensing Back-Office) provides you with a downloadable license container file. Unpack and apply the license container file to the primary AND the failover systems using the following command on each license server: `register-fne-server ` For full details see [Registering the license server](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/registering-the-license-server "A new license server must be registered with the Advantest FNE Licensing Back-office before it can be used to host licenses."). 5. On the primary license server check the status of the failover system: `/opt/flexnetls/socbu/fne-failover-status` The following displays an example of the status output: [![4.png](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/Znx4-png.png)](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/Znx4-png.png) 6. Activate the licenses to the new FNE license server. For details, see [Activating licenses](https://lhc.advantest.com/books/activating-licenses/page/activating-licenses "After the successful license server installation and registration, you need to provide the licenses to the license server that it is to serve. Simple license activation is used to activate an entitlement on a license server.") or [Downloading licenses](https://lhc.advantest.com/books/licensing-reference/page/downloading-licenses "If the FNE license server is not connected to the internet you must manually download the license container from the Advantest License Portal and upload it to the FNE license server.") as appropriate for your environment.
### **Results** The FNE primary and secondary license servers are installed, synchronized and licenses are activated. To check if an FNE license server is running: `/usr/bin/fne-status` or `/usr/local/bin/fne-status ` If the FNE license server is running, the following type of output is displayed: ``` * advantest-fne-server.service - Flex Net Embedded license server adapted for Advantest Active: active (running) since Mon 2019-05-20 11:08:14 CEST; 3 days ago * advantest-fne-server-viewer.service - Advantest Flex Net Embedded License Server Viewer Active: active (running) since Mon 2019-05-20 11:06:48 CEST; 3 days ago * advantest-fne-proxy.service - Advantest FNP2FNE proxy Active: active (running) since Mon 2019-05-20 11:07:36 CEST; 3 days ago ``` To check that the installation is complete, open a browser to view the FNE Server Viewer from the primary FNE license server system: `http://:7077` Click on link **Features**. You should see the licenses activated to your license server. Check the connections of the primary and failover FNE license server systems with: - `http://:7070/api/1.0/health` - `http://:7070/api/1.0/health`

Note To uninstall the FNE License Server and FNE Server Viewer, execute the command: `sudo yum remove advantest-fne-server advantest-fne-server-viewer `