Jan 2024

Since using Alma Linus and cRPM installations for Encoding Live and Single Server applications, changing the management IP Address has become a little more tricky than just changing the IP Address in the ifcfg-xxxx files.

This document assumes you are fairly familiar with the installation of Controller/Encoding Live and some of the other server settings. Please seek advice if you are not familiar with these things.

NOTE — This process only works if Controller was initally installed using the loopback address of 127.0.0.1.

If the unit was installed using a physical address for Controller then you either have the choice of:

Create a second IP Address on the unit - See: Multiple IP Addresses on Single Interface
Complete re-install of all software.

When installing the Encoding Live or Single Server we must perform a few pre-requisite steps, and these are:

Install the Alma Linux Security updates for your version of software.

tar -xvf mediakind-almalinux-updates-x.x-x.tar.gz
cd mediakind-almalinux-updates-x.x-x
./install --update

Edit the /etc/hosts file and add the loopback (if not already set) and local IP Address and host name.

vi /etc/hosts
10.32.13.100  server1 (where 10.32.13.100 is the management IP Address and server1 will be hostname of the server)

Example Hosts File

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.32.13.200   server1

Set the hostname of the server using the following:

hostnamectl set-hostname server1

Enable ChronyD for time synchronisation (requires internet access and DNS running)
systemctl enable chronyd

You can check timesync by using the following:

timedatectl

Example output:

               Local time: Tue 2024-02-06 19:41:00 UTC
           Universal time: Tue 2024-02-06 19:41:00 UTC
                 RTC time: Tue 2024-02-06 19:41:00
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Until the server is rebooted, any IP Address or HostName changes will not take effect.

sudo reboot

If the software is already installed then of course you can skip this section, the important part here is for Controller.

You must use the Loopback IP address of 127.0.0.1 when installing the Controller component.

Use the following Commands:

tar -xvf installer-controller-el8-v.x.y-z.tgz
./installer-controller-el8-*.sh host --configure --autoremove true
./installer-controller-el8-*.sh host-apps --configure
./installer-controller-el8-*.sh controller --configure --controllerIP1 127.0.0.1 --serverID server1

This means that Controller and Mongo will communicate on the loopback address of 127.0.0.1, so changing the Management IP Address will not break this connection.

Only the Controller Install uses the 127.0.0.1 Loopback Address.

In the Controller UI, you will still see the actual server IP Address listed (10.32.13.100 for example).

(For an IP Address change, only the EL will need to be changed, RT/Mux/Controller require no changes).

./installer-encoding-live-el8-*.sh standalone --configure --controllerIP 10.32.13.100 --licenseServerIP 10.32.13.100

Where the –controllerIP and –licenseServerIP is the management IP Address of the server. (This is for Standalone and Single Server installs only).

After EL install, unit will automatically reboot.

If this is an Encoding Live only Server, your software installation is complete, please check the section Changing the Server Management IP address at the end of this article.

You do not need to specify an IP Address to install RT

tar -xvf installer-reliable-transport-el8-*.tar.gz
./installer-reliable-transport-el8-*.sh standalone --configure --serverID server1

where the serverID used is the same as teh serverID used during the previous Controller installation.