Skip to content

Migrating PCoIP Management Console to a Newer Release Using firewalld

Teradici recommends using firewalld and thus has provisioned scripts and instructions to enable and configure firewalld. The instructions contained in this topic are for administrators who would like to use firewalld with Management Console and are making changes to an existing deployment.

Backup Your Database

Always ensure you have a working backup of your Management Console data when performing a Management Console removal, upgrade, or installation. Considerations should include:

  • having a current snapshot of your virtual machine
  • having a complete backup or clone of your Linux PC
  • having a current backup of your Management Console database.

This topic is separated into different scenarios that differ slightly from one another based on the initial version of Management Console in use. Management Console 20.04 and newer has moved to using firewalld as it's firewall. RPM upgrades to versions 20.04 or newer do not administer any firewall configurations thus leaving the administrator in complete control of the installation. In Management Console releases 19.05 through 20.01, RPM upgrades disabled firewalld, enabled iptables and created rules that allowed Management Console to work as expected.

Upgrades in IPv4 Environments

To Upgrade from Management Console 20.01 or older to 20.07 or newer in an IPv4 environment perform the following steps:

The following instructions provide the steps to remove the iptables configuration applied by Management Console and steps to add firewalld rules required by Management Console to operate properly. Additional rules required to comply to your corporate security policy must be added by the administrator.

  1. Login to the Management Console host operating system console.

  2. Configure your firewall. See Firewall changes after a RPM Upgrade from Management Console 20.01 or older using IPv4

  3. Upgrade existing Management Console to 20.07 or newer.

    sudo yum install teradicimc-<version>.rpm

  4. Access Management Console Web UI with IPv4 address.

To upgrade from Management Console 20.04 to 20.07 or newer in an IPv4 environment perform the following steps:

Upgrades from an existing Management Console 20.04 deployment should not require additional firewall configurations as new installs use firewalld.

  1. Login to the Management Console host operating system console.

  2. Upgrade the existing Management Console to new version using RPM in IPv4 environment.

    sudo yum install teradicimc-<version>.rpm

  3. Access Management Console Web UI with IPv4 address.

Upgrades in IPv6 Environments

Loss of Data

When migrating between IPv4 and IPv6, the older unrelated data will be permanently deleted. See Deleted Datafor further details.

To upgrade from Management Console 20.01 or older to 20.07 or newer in an IPv6 environment perform the following steps:

  1. Login to the Management Console host operating system console.

  2. Upgrade existing 20.01 or later Management Console to 20.07 or newer.

    sudo yum install teradicimc-<version>.rpm

  3. After RPM upgrade, perform the steps Moving between IPv4 and IPv6 for switching between IPv4 and IPv6.

    Error Message

    The error message connecting to INET family : ipv4 socket. Error No: 101, Reason: Network is unreachable is expected behaviour when upgrading to IPv6. It is OK to ignore this message.

    Verify your using the new rpm

    Verify your using the new rpm with this command.

    sudo rpm -qa | grep teradici

    Current RPM

  4. Access Management Console Web UI with IPv6 address. Depending on your network configuration, this can be either a manual, DHCP, or SLAAC provided IPv6 address.

To upgrade from Management Console 20.04 to 20.07 or newer in an IPv6 environment perform the following steps:

Deleted data when moving between IP versions

When Management Console migrates between IPv4 to IPv6 using RPM, only the common data between IPv4 and IPv6 will be restored. The rest of the data will be deleted. For further details see Deleted Data When Migrating between IP Protocols

  1. Login to the Management Console host operating system console.

  2. Upgrade existing 20.04 Management Console to 20.07 or newer. (See tip above)

    sudo yum install teradicimc-<version>.rpm

    Error Message

    The error message connecting to INET family : ipv4 socket. Error No: 101, Reason: Network is unreachable is expected behaviour when upgrading to IPv6. It is OK to ignore this message.

  3. After RPM upgrade, perform the steps Moving between IPv4 and IPv6 for switching between IPv4 and IPv6.

  4. Access Management Console Web UI with a configured IPv6 address. Depending on your network configuration, this can be either a manual, DHCP, or SLAAC provided IPv6 address.

To Migrate Management Console 20.07 or newer between IPv4 and IPv6 Networks using a static IP address perform the following steps:

These steps must be performed in order for Management Console to operate successfully in a pure IPv6 environment when moving from an IPv4 environment.

  1. Login to the Management Console host operating system console.

  2. Stop mcconsole and mcdaemon services

    sudo systemctl stop mcconsole
    sudo systemctl stop mcdaemon
    
  3. Change IP address from IPv4 to IPv6 using nmtui.

  4. Reboot Management Console host operating system.

    sudo init 6

  5. Configure your firewall for IPv6

  6. Run scripts to delete unrelated data.

    cd  /opt/teradici/database
    sudo python mc_env_db.py
    

    Error Message when migrating from IPv4 to IPv6

    The error message connecting to INET family : ipv4 socket. Error No: 101, Reason: Network is unreachable is expected behaviour when migrating from IPv4 to IPv6. It is OK to ignore this message.

  7. Start mcconsole and mcdaemon services.

    sudo systemctl start mcconsole
    sudo systemctl start mcdaemon
    

Data deleted

When migrating from IPv4 to IPv6, the data from IPv4 will be deleted during the migration and vice versa.

Deleted data information can be found here

  1. Access Management Console Web UI with the address you configured for IPv6 in step 3.