Versions Compared

Old Version 1

changes.mady.by.user Harald Saller

Saved on

compared with

New Version Current

changes.mady.by.user Harald Saller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Scroll Documents: Update page title prefix

This article describes possible installation options for the IGEL Universal Management Suite (UMS) and it provides general installation recommendations and instructions. For further guidelines about the UMS environment, see (12.04.120-en_orig) Installation and Sizing Guidelines for IGEL UMS.

...

A UMS installation can consist of a single UMS Server instance or multiple UMS Servers.

...

Info

Alternatively, you can use a reverse proxy / external load balancer for load distribution as of UMS 12; the FQDN and port of the external load balancer / reverse proxy must be specified as a Cluster Address, see (12.04.120-en_orig) Server Network Settings in the IGEL UMS.

Note the following:


  • UMS High Availability (HA) Extension
    The UMS HA provides all features from the Distributed UMS but comes with the possibility to install UMS Load Balancers. Communication between the components of the UMS HA installation, i.e. UMS Servers, UMS Load Balancers, is possible due to the use of the same IGEL network token. 
    As of UMS version 6.10 (no matter if it is an HA installation with UMS Load Balancers or without), messages between the UMS Servers use the database bridge, and not ActiveMQ like on earlier UMS versions. Nevertheless, ActiveMQ messaging still remains active: on HA installations without Load Balancers, it is active only in the background; on HA installations with UMS Load Balancers, ActiveMQ messaging is, however, further used for the message exchange with Load Balancers, and exactly this poses restrictions on the cross-subnet communication and possibility to install UMS HA with Load Balancers in cloud environments. For further information on messaging, see (12.04.120-en_orig) UMS HA Health Check - Analyse Your IGEL UMS High Availability and Distributed UMS Systems.

    Expand
    titleMore on message exchange...


    A UMS HA installation has the following requirements:

Characteristic features of HA installations with IGEL UMS Load Balancers: All UMS Servers and UMS Load Balancers must reside on the same VLAN; there is no support for cloud environments like Azure / AWS.

Info

Cross-subnet Communication for UMS HA Installations without UMS Load Balancers

Existing UMS HA installations without UMS Load Balancers can be further used – there is no need to reinstall them as Distributed UMS. UMS Server communication over subnets will automatically be possible when you update to UMS 6.10 or higher.

There is no need for reinstallation also because a UMS HA without Load Balancers operates essentially as the Distributed UMS - both are identical in terms of the synchronization of files, firmware, certificates, licenses, and jobs; both use the database bridge for the message exchange.

How to Choose between the Standard UMS, Distributed UMS, and UMS High Availability

Tip

General Installation Recommendations

For small installations, a single UMS Server instance (standard UMS) with an embedded database is usually sufficient. If required, a single-instance installation can be easily extended anytime to a Distributed UMS installation by installing additional servers (and in the case of an embedded database, by switching preliminarily to an external data source).

Large installations should use either the UMS High Availability or the Distributed UMS (preferable for new installations, e.g. because you do not have to configure additional firewall exclusions). For large installations, it is also recommended to use DNS-Round-Robin load balancing or IGEL Cloud Gateway.

See also (12.04.120-en_orig) Installation and Sizing Guidelines for IGEL UMS.

  • You are an existing customer and have a single-instance UMS installation but want to run additional UMS Servers...
    => Install UMS 12.01 or higher ("standard UMS" in the UMS installer) on the first server and enable the Distributed UMS feature. After that, you can install additional servers (as Distributed UMS) and connect them to the same database (NOT embedded database).

...

  • You are a new customer and want the UMS with multiple servers in the cloud...
    => Install UMS 12.01 or higher  ("Distributed UMS" in the UMS installer) on the first server. After that, you can install the other servers, also as Distributed UMS, and connect them to the same database (NOT embedded database).

How to Install the IGEL UMS


Info
  • For the management of the UMS installation, you require the UMS Console. In multi-instance installations, the UMS Console does not necessarily have to be installed on every UMS Server.
    Note: For security, performance, or other reasons, the UMS Console is often additionally installed on a separate host.  
  • You cannot manage IGEL OS 12 devices without the UMS Web App. Thus, the UMS Web App must be selected during the installation of the UMS. In multi-instance installations, the UMS Web App does not necessarily have to be installed on every UMS Server, see (12.04.120-en_orig) Important Information for the IGEL UMS Web App. 
  • The UMS Administrator application, which is necessary for the management of the UMS installation, will be automatically installed during the installation of the UMS Server.

For information on the UMS components, see (12.04.120-en_orig) Overview of the IGEL UMS.


Standard UMS

If you decided on a single-instance UMS installation, see the following articles. They describe the complete procedure for installing the standard UMS with an embedded database. If your required installation differs, you can select individual components, e.g. for an individual console installation.

Distributed UMS

If you want to install the Distributed UMS or extend your existing standard UMS installation to the Distributed UMS, see (12.04.120-en_orig) Installing the Distributed IGEL UMS.

UMS High Availability

If you want to install the UMS HA Extension, see (12.04.120-en_orig) HA Installation.