Installing UFM Server Software

The default UFM® installation directory is /opt/ufm.

UFM Server installation options are:

• Standalone

• High Availability (HA) - Delivered in a separate package as of UFM v6.10.0.

• Docker Container

The following processes might be interrupted during the installation process:

• httpd (apachi2 in Ubuntu)

• dhcpd

After installation:

1. Activate the software license

2. Perform initial configuration

Verify that a supported version of Linux is installed on your machine. For details, see UFM System Requirements.

The following table lists the packages that must be installed on your machine (according to system OS) before you install the UFM server software.

In addition, ensure the following before you begin installation:

• The computer hostname is not defined as 127.0.0.1 and localhost is defined as 127.0.0.1.

• The hostname must NOT appear on the loopback address line. An example of the loopback address is: 127.0.0.1 localhost.localdomain localhost.

• Disable the firewall service (/etc/init.d/iptables stop), or ensure that the required ports are open (see the prerequisite script).

• SELinux is disabled.

• If more than one fabric is managed by different UFM instances, set up different management network spaces for each fabric (not the same LAN).

• Uninstall any previously installed Subnet Manager from the UFM server machine.

• MLNX_OFED 5.x version is installed prior to installing UFM.

• As of UFM v.6.12.0, it is NOT mandatory to configure the IPoIB fabric interface with an IP address.
  In cases where the IP is configured, it is mandatory that the IP is permanently configured and that it starts automatically upon server reboot (the IPoIB fabric interface should be active even if the network is down).

  Warning

  The user can set a persistent IP address using Netplan (mainly for Ubuntu systems) or modifying the interface network script (RedHat systems).

• The default MLNX_OFED installation includes opensm. Remove the MLNX_OFED opensm before UFM installation like the following examples:

  RedHat:

  Copy

  Copied!

              
  
              
  rpm -e opensm-3.3.9.MLNX_20111006_e52d5fc-0.1
          

  Ubuntu:

  Copy

  Copied!

              
  
              
  apt purge opensm
          

  By default, ib0 and eth0 are configured as primary access points for the UFM management. If different management and/or InfiniBand interfaces (including bond interfaces) are used as the primary access points, you should modify the configuration file by running the script /opt/ufm/scripts/change_fabric_config.sh as described in the section Configuring General Settings in gv.cfg.

  Change the UFM Agent interface to the Ethernet and/or IPoIB interfaces used for communication with UFM Agent:

  Copy

  Copied!

              
  
              
  ufma_interfaces = ib0,eth0
          

• Reliable and high-capacity out-of-band IP connectivity between the UFM Primary and Secondary servers (1 Gb Ethernet is recommended). This connectivity is used for DRBD synchronization.

• Format two identical servers with dedicated disk partitions for UFM replication. Since the UFM configuration file is replicated to the standby server, both master and standby servers must have the same interfaces.

• Allocate exactly the same size partition on both servers (master and slave) for the replicated data. See UFM Server Requirements for the recommended partition size.
  Partitions should not be mounted and must be zeroed (the file system should not be installed on the partitions). For disk partitioning, see the Linux user manual (man fdisk).

• We recommend establishing a passwordless SSH (via /root/.ssh/authorized_keys file) between the two servers before the installation.

• In fabrics consisting of multiple tiers of switches, it is recommended that the management ports (ib0) of the primary and secondary UFM server be connected to different fabric switches on the same tier (the outermost edge in CLOS 5 designs).

  This is because by default, UFM manages the IB fabric via ib0, port 1 of the HCA. Failure or disconnect of ib0, the IB management port, causes a failure condition in UFM resulting in HA failover.
  When the management ports (ib0) of the primary and secondary UFM server are connected to the same switch, a failure of this switch will result in a disconnect of both UFMs from the fabric, and therefore UFM will not be able to manage the fabric.

To install the UFM server software as a standalone for InfiniBand:

1. Create a temporary directory (for example /tmp/ufm).

2. Open the UFM software zip file that you downloaded. The zip file contains the following installation files:

   • RedHat 7/CentOS 7/OEL 7: ufm-6.9-XXX.el7.x86_64.tgz

   • RedHat 8/Centos 8: ufm-X.X-XXX.el8.x86_64.tgz

   • Ubuntu 18.04: ufm-X.X-XXX.Ubuntu18.x86_64.tgz

   • Ubuntu 20.04: ufm-X.X-XXX.Ubuntu20.x86_64.tgz

3. Extract the installation file for your system's OS to the temporary directory that you created.

4. From within the temporary directory, run the following command as root:

   Copy

   Copied!

               
   
               
   ./install.sh
           

   Warning

   Running with the option "-o ib" is no longer required. For automatic installation, use the -q flag.

   For “quiet” installation -q flag can be added (automatically answer yes for each question the installer asks).

The UFM software is installed. You can now remove the temporary directory.

UFM can be installed in HA mode using an additional package for HA called UFM-HA.

1. On both servers, Install UFM Enterprise in Stand Alone (SA) mode.

   Warning

   Do not start UFM service.

2. Install the latest pcs and drbd-utils drivers on both servers.

   For Ubuntu:

   Copy

   Copied!

               
   
               
   apt install pcs pacemaker drbd-utils
           

   For CentOS/Red Hat:

   Copy

   Copied!

               
   
               
   yum install pcs pacemaker drbd84-utils kmod-drbd84
           

   OR

   Copy

   Copied!

               
   
               
   yum install pcs pacemaker drbd90-utils kmod-drbd90
           

3. Download UFM-HA latest package from this link.

4. Extract the downloaded UFM-HA package on both servers under /tmp/.

5. Go to the directory you extracted /tmp/ufm_ha_XXX and run the installation script. For example:

   Copy

   Copied!

               
   
               
   ./install.sh -l /opt/ufm/files/ -d /dev/sda5 -p enterprise
           

   Option	Description
   -l	DRBD Files Location. Must be always /opt/ufm/files/
   -d	DIsk name for DRBD. For example /dev/sda5
   -p	Product Name. Must use “enterprise” to UFM Enterprise

6. On the master server only, configure the HA nodes. To do so, from /tmp, run the configure_ha_nodes.sh command as shown in the below example:

   Copy

   Copied!

               
   
               
   configure_ha_nodes.sh --cluster-password 12345678 --master-ip 192.168.10.1 --standby-ip 192.168.10.2 --virtual-ip 192.168.10.5 
           

   Warning

   The configure_ha_nodes.sh script is located under /usr/local/bin/, therefore, by default, you do not need to use the full path to run it.

7. Configure HA from the main server using the following command:

   Copy

   Copied!

               
   
               
   configure_ha_nodes.sh --cluster-password 12345678 --master-ip 192.168.10.1 --standby-ip 192.168.10.2 --virtual-ip 192.168.10.5
           

   Warning

   The --cluster-password must be at least 8 characters long.

   Warning

   When using back-to-back ports with local IP addresses for HA sync interfaces, ensure that you add your IP addresses and hostnames to the /etc/hosts file. This is needed to allow the HA configuration to resolve hostnames correctly based on the used IP addresses.

   Warning

   configure_ha_nodes.sh will require SSH connection to the standby server. If SSH is not configured then you will be prompted to enter the password during configuration runtime.

   Option	Description
   --cluster-password	UFM HA cluster password for authentication by pacemaker.
   --master-ip	Master (main) server IP address
   --standby-ip	Standby server IP address
   --virtual-ip OR --no-vip	UFM HA cluster Virtual IP or configure HA without virtual IP

8. You must wait until after configuration for DRBD sync to finish depending on the size of your partition.

9. To start UFM HA cluster:

   Copy

   Copied!

               
   
               
    ufm_ha_cluster start
           

10. To check UFM HA cluster status:

    Copy

    Copied!

                
    
                
    ufm_ha_cluster status
            

To stop UFM HA cluster:

            

            
 ufm_ha_cluster stop
        

To uninstall UFM HA, first, stop the cluster and then run the ufm_ha uninstallation script as follows:

            

            
/opt/ufm/ufm_ha/uninstall_ha.sh
        

To replace the standby server with a new one, run:

            

            
./replace_ha_nodes --cluster-password 123456 --master-ip  192.168.10.1  --standby-ip 192.168.10.2  –virtual-ip 192.168.10.3
        

UFM can be deployed as a docker container. For further information, please refer to the UFM Enterprise Docker Installation .