The hostnamectl tool is provided for administering the three classes of hostnames that can be used on a system controller or license server running RHEL 7.

### **Scope**

***RHEL 7***: The following tips are applicable for RHEL 7. For more information about configuring host names, refer to the Red Hat documentation: [https://access.redhat.com/documentation/en-us/red\_hat\_enterprise\_linux/7/html/networking\_guide/ch-configure\_host\_names](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-configure_host_names).
***RHEL 9***: For information about changing hostnames on RHEL 9 using the **nmcli** or **nmtui** tools, refer to the Red Hat documentation: [https://access.redhat.com/documentation/en-us/red\_hat\_enterprise\_linux/9/html/configuring\_and\_managing\_networking/assembly\_changing-a-hostname\_configuring-and-managing-networking#proc\_changing-a-hostname-using-nmcli\_assembly\_changing-a-hostname](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/assembly_changing-a-hostname_configuring-and-managing-networking#proc_changing-a-hostname-using-nmcli_assembly_changing-a-hostname)

### **View all hostnames** To view all the current hostnames, enter the command: `hostnamectl status ` The `status` option is implied by default if no option is given.

### **Set all hostnames** To set all the hostnames on a system, as root, enter the command: `hostnamectl set-hostname name ` This command changes the pretty, static, and transient hostnames to the name specified in *name*. The static and transient hostnames are simplified forms of the pretty hostname. Spaces are replaced with "-" and special characters are removed.

### **Set a particular hostname** To set a particular hostname, as root, enter the command with the relevant option: `hostnamectl set-hostname name [option...] ` Where option is one or more of: `--pretty`, `--static`, and `--transient`. If either the `--static` or `--transient` options are used with the `--pretty` option, the static and transient hostnames are simplified forms of the pretty hostname. Spaces are replaced with "-" and special characters are removed. If the `--pretty` option is not specivied, no simplification takes place. If the pretty hostname to be set contains spaces or a single quotation mark, use quotation marks around the name entry. For example: `hostnamectl set-hostname "Advantest's SmarTest 8.2 system controller" --pretty`

### **Check a hostname** To check if the hostname is set correctly as a fully qualified domain name, as root, enter the command: `hostname -f` An example of a correct response is: `server123.mycompany.com` Incorrect response example: `localhost.localdomain`

### **Clear a particular hostname** To clear a particular hostname and revert to the default, as root, enter the command with the relevant option: `hostnamectl set-hostname "" [option...] ` Where: `""` is a quoted empty string. option... is one or more of: `--pretty`, `--static`, and `--transient`.

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.

### **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.

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 `

A new license server must be registered with the Advantest FNE Licensing Back-office before it can be used to host licenses.

### About this task Before you can install licenses onto the license server, the license server needs to be registered in the Advantest FNE Licensing Back-office. This is made over an online internet connection or by uploading and downloading files configuration files offline. If your license server has access to the internet, only one **`register-fne-server`** tool command is required to complete the registration. If your license server host system does not have access to the internet, the **`register-fne-server`** tool provides you with a binary request file that you upload using the Advantest License Portal. After registering your license server, activate your licenses using the license portal.

### **Before you begin** Registration is executed by running the **`register-fne-server`** tool with a server activation ID from the Advantest License Portal. The server activation ID is available from the Advantest License Portal as an entitlement. The activation ID takes the following form: ``

Your assigned server activation IDs are listed in the Advantest License Portal.

Note: Your entitlement certificate contains a representation of the registration key. Get the actual registration key from the License Portal.

### **Procedures**

##### **Online Registration** If your license server has access to the internet, run the **`register-fne-server`**tool on the FlexNet Embedded license server for the initial registration of the FNE server at Advantest using the following command: `register-fne-server ` The registration should complete automatically and the following message is displayed: ``` Successfully activated your server to ``` Server registration is complete.

##### **Offline Registration** 1. If you do not have internet access to the Advantest back-office, from the primary server, generate the registration request file using the command: `register-fne-server ` The registration request file is generated and the following message is displayed: ``` No connection to backoffice at license.advantest.com:80 Offline license server activation is successfully written to: /tmp/srv_registration_request_.bin for 127.0.0.1 : 7070 ``` 2. Copy the request file generated in the previous step to a computer with internet access. 3. From the computer with internet access, log on to the Advantest License Portal: [https://license.advantest.com/](https://license.advantest.com/).

Note: If you do not have an account, click the **Register button**, create an account using an entitlement ID belonging to your organization for which the server should be registered. Provide a user name and a password for the account. On successful registration, an account is created and you are automatically logged in.

4. Open the tab License Management and click Register Server. [![5.jpg](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/l2K5-jpg.jpeg)](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/l2K5-jpg.jpeg) The **Register Server** page opens and lists the available registration keys. 5. Click on the registration key corresponding to the activation ID entry to be used to register the license server. The command in the illustration below is adapted and you can use copy and paste to execute the **`register-fne-server `**tool on your FNE license server. [![6.png](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/3Pd6-png.png)](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/3Pd6-png.png) 6. Click **Upload request file** and specify the location of the `srv_registration_request_.bin` file copied from the license server in step 2. The license server is now registered.

### **Results** Your license server is registered.

### **What to do next** [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.")