Versions Compared

Old Version 1

changes.mady.by.user Christina Loher

Saved on

compared with

New Version 2

changes.mady.by.user Emese Pogany

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

    Note

    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 Installing the First Server in an HA Network#HA_1Server_Start_InstallationNetwork.

  • A server with the operating system supported by the UMS; see the "Supported Environment" section of the release notes.
  • All installation requirements described under HA: Installation Requirements are fulfilled.
  • The same version of the UMS as for the first HA server is downloaded from the IGEL Download Server.

...

  1. Verify that the server can "see" the other servers via the network.
    Include Page
    ENLITEUMSP:_UMS HA: No NAT or Proxies
    ENLITEUMSP:_UMS HA: No NAT or Proxies


  2. Verify that the time on all servers is synchronized.
    Include Page
    ENLITEUMSP:_UMS HA: No Time Difference Warning
    ENLITEUMSP:_UMS HA: No Time Difference Warning


  3. For Linux systems, make the directory /root writable for the user root.

Anchor
HA_FurtherServers_PrepareToken
HA_FurtherServers_PrepareToken
Preparing the IGEL Network Token

Include Page
ENLITEUMSP:_Icon_handlungsaufforderung.png
ENLITEUMSP:_Icon_handlungsaufforderung.png
 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.

...

Note

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:

Include Page
ENLITEUMSP:_Icon_handlungsaufforderung.png
ENLITEUMSP:_Icon_handlungsaufforderung.png
Restart the IGEL RMGUIServer service (for the instruction, see 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.token
Linux: /root/IGEL-Network.token

...

  1. Launch the UMS installer.

    Info

    You need administration rights to install the IGEL UMS HA.



  2. Read and confirm the License Agreement.

  3. Read the Information regarding the installation process.

  4. Select a path for the installation.

  5. Select the components to be installed depending on your desired HA network configuration. See also IGEL UMS HA Configuration Options.


  6. Confirm the system requirements dialog if your system fulfills them.

  7. Select the UMS data directory, in which Universal Firmware Updates and files are to be saved.

  8. Disable the option for creating an IGEL network token.


  9. Select the IGEL network token to be used.



  10. 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. 

    Info

    Include Page
    ENLITEUMSP:_SvIncludePlusContent-_UMS 12 Communication Ports
    ENLITEUMSP:_SvIncludePlusContent-_UMS 12 Communication Ports

    For more information on UMS ports, see IGEL UMS Communication Ports.



  11. Under Select Start Menu Folder, specify a folder name for the shortcut.

  12. Under Select Additional Tasks, specify whether you would like to create shortcuts for the UMS Console and UMS Administrator on the desktop.

  13. Read the summary and start the installation process.

  14. Close the UMS installer once the installation is complete.

...

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.

Info

If SQL If SQL Server AD Native is 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 detailsmore information, see "Configuring the UMS Server Windows Service" under "Setting Up the UMS for SQL Server AD Native".  Microsoft SQL Server/Cluster with Native Active Directory (AD) Authentication.

Anchor
HA_FurtherServers_CheckInstallation
HA_FurtherServers_CheckInstallation
Checking the Installation

  1. Check if all processes are running. For the list of UMS HA processes, see IGEL UMS HA Services and Processes.

  2. 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.
    Include Page
    ENLITEUMSP:_Path for the UMS Administrator
    ENLITEUMSP:_Path for the UMS Administrator

    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.


  3. 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 UMS HA Health Check - Analyse Your IGEL UMS High Availability and Distributed UMS Systems.


Include Page
ENLITEUMSP:_Register the UMS
ENLITEUMSP:_Register the UMS


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