(12.01-en) Adding Further Servers to the HA Network

Introduction

Further HA servers – with UMS Server, UMS Load Balancer, or both – can be installed in the same way as the first one. However, you do not need to create a new IGEL network token. Instead, you must select the network token created previously during the installation of the first server in an HA network.

In addition, a connection with the same database that is used by the first server must be established. The UMS HA network only works if all servers are connected to the same database.

Prerequisites

A High Availability (HA) installation with a configured database, see (12.01-en) Installing the First Server in an HA Network.

The database connection should be defined during the installation of the first UMS Server in an HA network. In this case, all relevant configuration information is automatically copied to the additional UMS Servers.
The IGEL network token created during the installation of the first server in the HA network, see (12.01-en) Installing the First Server in an HA Network#HA_1Server_Start_Installation.
A server with the operating system supported by the UMS; see the "Supported Environment" section of the release notes.
All installation requirements described under (12.01-en) HA: Installation Requirements are fulfilled.
The same version of the UMS as for the first HA server is downloaded from the IGEL Download Server.

Instructions

To add a new server to the UMS HA installation, follow the instructions in the order given:

Preparing the Server
Preparing the IGEL Network Token
Starting the Installation
Checking the Installation

Preparing the Server

Verify that the server can "see" the other servers via the network.
- High Availability with IGEL UMS Load Balancers: All UMS Servers and UMS Load Balancers must reside on the same VLAN.
- For High Availability (UMS HA) with IGEL UMS Load Balancers, network traffic must be allowed over UDP broadcast port 6155, and TCP traffic and UDP broadcast traffic over port 61616. For further port configuration, see (12.01-en) IGEL UMS Communication Ports.
- The network configuration on Windows Servers must have the TCP/IPv6 option enabled for UMS 12.
- IGEL UMS HA installation with IGEL UMS Load Balancers is not supported in cloud environments like Azure / AWS as they do not allow broadcast traffic within their networks. The HA installation without IGEL UMS Load Balancers (as well as the Distributed UMS) is, however, supported in cloud environments as of UMS version 6.10.
Verify that the time on all servers is synchronized.

To avoid problems with your HA installation, make sure that the time on the servers of the HA network does not differ by more than one minute. After each manual time reset, the HA services on the relevant server must be restarted.
For Linux systems, make the directory /root writable for the user root.

Preparing the IGEL Network Token

If you have not yet done so, save the IGEL network token created during the installation of the first HA server, e.g. on a portable storage medium.

If the path has not been changed, the file IGEL-Network.token can be found by default in the home directory of the administrator user on a UMS Server host.

If you have a fully functional UMS HA network already in use and simply want to enlarge it with one more HA server, make sure you use for the additional HA server installation the current IGEL network token. If you have not saved it:

Restart the IGEL RMGUIServer service (for the instruction, see (12.01-en) IGEL UMS HA Services and Processes) and use in this case the network token created upon the UMS Server startup from the directory:Windows: C:\Windows\System32\config\systemprofile\IGEL-Network.tokenLinux: /root/IGEL-Network.token

Starting the Installation

Launch the UMS installer.

You need administration rights to install the IGEL UMS HA.
Read and confirm the License Agreement.
Read the Information regarding the installation process.
Select a path for the installation.
Select the components to be installed depending on your desired HA network configuration. See also (12.01-en) Configuration Options.
Confirm the system requirements dialog if your system fulfills them.
Select the UMS data directory, in which Universal Firmware Updates and files are to be saved.
Disable the option for creating an IGEL network token.
Select the IGEL network token to be used.
If the internal Windows firewall is active on your host: Review the settings under Windows firewall settings and change them where necessary. Each port that is activated here will be set as rule in the Windows firewall.
UMS 12 Communication Ports
If you are going to make network changes, consider the following ports and paths:
- For IGEL OS 12 devices, TCP 8443 /device-connector/* is required.
  SSL can be terminated at the reverse proxy / external load balancer (see IGEL UMS Configuration for the External Load Balancer or Reverse Proxy: Example for NGINX with SSL Offloading) or at the UMS Server.
- For importing IGEL OS 12 Apps to the UMS from the IGEL App Portal, the URL https://app.igel.com/ (TCP 443) is required.
- For the UMS Web App, TCP 8443 /webapp/* and /wums-app/* are required.
- For the UMS Console, the root is required, i.e. TCP 8443 /*
- For IGEL OS 11 devices, TCP 30001 and TCP/UDP 30005 are required.
For more information on UMS ports, see (12.01-en) IGEL UMS Communication Ports.
Specify a folder name for the shortcut.
Read the summary and start the installation process.
Close the UMS installer once the installation is complete.

If you have included a UMS Server in the installation, the UMS installer creates entries in the Windows software directory and the start menu. The UMS Console and UMS Administrator applications are installed, and a shortcut for the UMS Console is placed on the desktop.

If you have installed an individual load balancer, only the option for uninstalling the UMS will be set up in the Windows start menu. No configuration on the load balancer is necessary. It connects automatically to the HA network during booting.

If SQL Server AD Native is used, you must also set the correct startup type and logon settings for the "IGEL RMGUIServer" service and restart the service. This must be done on ALL UMS Server hosts. For details, see "Configuring the UMS Server Windows Service" under "Setting Up the UMS for SQL Server AD Native".

Checking the Installation

Check if all processes are running. For the list of UMS HA processes, see (12.01-en) IGEL UMS HA Services and Processes.
If you have included a UMS Server in the installation, open UMS Administrator > Datasource and verify that the database connection has been successfully transferred from the already running UMS Server.

Default path to the UMS Administrator:
Linux: /opt/IGEL/RemoteManager/RMAdmin.shWindows: C:\Program Files\IGEL\RemoteManager\rmadmin\RMAdmin.exe
The IGEL UMS Administrator application can only be started on the UMS Server.
If the database connection has not been defined automatically, enter under UMS Administrator > Datasource > Add exactly the same database parameters you used during the installation of the first HA server and click Activate.
In the UMS Console, go to UMS Administration > UMS Network and check the items Server and/or Load Balancer.

Additionally, you can use the feature for checking the HA installation, see (12.01-en) UMS HA Health Check - Analyse Your IGEL UMS High Availability and Distributed UMS Systems.

For the management of IGEL OS 12 devices, it is necessary to register your UMS after the installation, see (12.01-en) Registering the IGEL UMS.

For the future, you may also find it useful to read: (12.01-en) Creating a Backup of the IGEL UMS and (12.01-en) Which Files Are Automatically Synchronized between the IGEL UMS Servers?.