Upgrading TufinOS 3.x to 4.30 - In-place VMWare ESXi Machines

Overview

This procedure explains how to upgrade TufinOS 3.x to 4.30 on your existing VMWare ESXi machines.

If you have remote collector clusters, first upgrade the Central Cluster, and then repeat for each remote collector cluster. For more information on Remote Collector clusters, see Remote Collectors.

If you have worker nodes, you will need to upgrade them first.

During the TufinOS upgrade there will be some downtime. Installing TufinOS 4 on the node will erase all data and server configurations.

Prerequisites

NFS

TufinOS 4.x does not support NFS on this TOS release. NFS is supported from R23-2 PHF2.0.0 and later.

To use NFS for external backups:

  1. Install NFS 4 on your backup server

  2. Upgrade TOS

  3. Upgrade TufinOS

Follow the instructions in the relevant knowledge center.

Alternatively, you can switch to local storage or one of the cloud storage options.

General Requirements

  1. This procedure must be performed by an experienced Linux administrator with knowledge of network configuration.

  2. For data nodes only. Make sure you do not have unsupported LVM Volume Groups:

    [<ADMIN> ~]$ sudo vgdisplay --noheadings -C -o vg_name | grep -qs -v "[\t ]*VolGroup0[12]$" && echo "You cannot uppgrade."
    sudo vgdisplay --noheadings -C -o vg_name | grep -qs -v "[\t ]*VolGroup0[12]$" && echo "You cannot uppgrade."

    If the output returns "You cannot upgrade.", do not use the upgrade method in the boot menu to upgrade to TufinOS 4.30. Perform the upgrade on new VMWare ESXi machines.

    If you receive no output, proceed with the next step below.

  3. For data nodes only. Make sure your /var/log partition is large enough:

    [<ADMIN> ~]$ sudo lsblk | grep "MOUNTPOINT\|/var/log$"
    sudo lsblk | grep "MOUNTPOINT\|/var/log$"

    If the output returns a partition size of 400 MB or less, do not perform this upgrade procedure. Perform the upgrade on new VMWare ESXi machines.

  4. If you have any external disks (for example, etcd), disconnect them. These disks should be reconnected after the TufinOS upgrade is complete.

Downloads

  1. Download the TufinOS 4.30 installation package from the Download Center.

    • For a VMWare ESXi machine, download the .iso image file.

  2. Extract the TufinOS image from its archive.

    [<ADMIN> ~]$ sudo tar xzvf <FILENAME>.tgz
    sudo tar xzvf <FILENAME>.tgz

    The run file name includes the release, version, build number, and type of installation.

    TufinOS ISO file example: TufinOS-4.30-4368238-x86_64-Final.iso

  3. Verify the integrity of the TufinOS installation package.

    [<ADMIN> ~]# sha256sum -c TufinOS-X.XX-XXXXXX-x86_64-Final.iso.sha256
    sha256sum -c TufinOS-X.XX-XXXXXX-x86_64-Final.iso.sha256

    The output should return OK

Preliminary Preparations

    1. Check your current TufinOS version:

      cat /etc/tufinos-release

      Your TufinOS release appears in the output. If the command is not recognized, you have a non-TufinOS operating system and cannot upgrade using this procedure.

    2. If there is a supported upgrade path for your TufinOS release, continue with the upgrade. Otherwise, upgrade first to a supported release.

    1. On the primary data node, check the following status.

      [<ADMIN> ~]$ sudo systemctl status k3s
      sudo systemctl status k3s

      2. In the output under the line k3s.service - Aurora Kubernetes, two lines should appear - Loaded... and Active... similar to the example below. If they appear, continue with the next step, otherwise contact Tufin Support for assistance.

      Example output:

      [<ADMIN> ~]$ sudo systemctl status k3s
 [root@TufinOS ~]# systemctl status k3s
 Redirecting to /bin/systemctl status k3s.service
 ● k3s.service - Aurora Kubernetes
    Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: disabled)
    Active: active (running) since Tue 2021-08-24 17:14:38 IDT; 1 day 18h ago
      Docs: https://k3s.io
   Process: 1241 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
   Process: 1226 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
  Main PID: 1250 (k3s-server)
     Tasks: 1042
    Memory: 2.3G

    2. On the same node or nodes, check the TOS status.

      [<ADMIN> ~]$ sudo tos status
      sudo tos status

      3. In the output, if the System Status is Ok and all the items listed under Components appear as ok, continue with the next steps. Otherwise contact Tufin Support for assistance.

      Example output:

      [<ADMIN> ~]$ sudo tos status
 Tufin Orchestration Suite 2.0
  
 System Status: Ok
 System Mode:   Multi Node
  
 Nodes:
   1 Master, 1 Worker. Total 2 nodes. Nodes are healthy.
  
 Components:
   Node:            Ok
   Cassandra:       Ok
   Mongodb:         Ok
   Mongodb_sc:      Ok
   Nats:            Ok
   Neo4j:           Ok
   Postgres:        Ok
   Postgres_sc:     Ok

  3. If you are going to perform this procedure over multiple maintenance periods, create a new backup each time.

    1. Create the backup using tos backup create: 

      2. [<ADMIN> ~]$ sudo tos backup create
      sudo tos backup create

      Example output:

      [%=Local.admin-prompt% sudo tos backup create
[Aug 23 16:18:42]  INFO Running backup
Backup status can be monitored with "tos backup status"

    2. You can check the backup creation status using tos backup status, which shows the status of backups in progress. Wait until completion before continuing.

      3. [<ADMIN> ~]$ sudo tos backup status
      sudo tos backup status

      Example output:

      [<ADMIN> ~]$ sudo tos backup status
 Found active backup "23-august-2021-16-18"

    3. Run the following command to display the list of backups saved on the node:

      [<ADMIN> ~]$ sudo tos backup list
      sudo tos backup list

      4. Example output:

      [<ADMIN> ~]$ sudo tos backup list
 ["23-august-2021-16-18"]
   Started: "2021-08-23 13:18:43 +0000 UTC"
   Completed: "N/A"
   Modules: "ST, SC"
   HA mode: "false"
   TOS release: "21.2 (PGA.0.0) Final"
   TOS build: "21.2.2100-210722164631509"
   Expiration Date: "2021-09-22 13:18:43 +0000 UTC"
   Status: "Completed"

    4. Check that your backup file appears in the list, and that the status is "Completed".

    5. Run the following command to export the backup to a file: 

      [<ADMIN> ~]$ sudo tos backup export
      sudo tos backup export

      6. The command creates a single backup file.

      [<ADMIN> ~]$ sudo tos backup export
 [Aug 23 16:33:42]  INFO Preparing target dir /opt/tufin/backups
 [Aug 23 16:33:42]  INFO Compressing...
 [Aug 23 16:33:48]  INFO Backup exported file: /opt/tufin/backups/backup-21-2-pga.0.0-final-20210823163342.tar.gzip 
 [Aug 23 16:33:48]  INFO Backup export has completed

    6. If your backup files are saved locally:

      1. Run sudo tos backup export to save your backup file from a TOS backup directory as a single .gzip file. If there are other backups present, they will be included as well.

      2. Transfer the exported .gzip file to a safe, remote location.

        Make sure you have the location of your backups safely documented and accessible, including credentials needed to access them, for recovery when needed.

      After the backup is exported, we recommend verifying that the file contents can be viewed by running the following command:

      [Target location]$ tar tzvf <filename>
      tar tzvf <file name>

  4. On the Central cluster primary data node run:

    [<ADMIN> ~]$ sudo tos cluster list
    sudo tos cluster list

    The output shows all connected clusters.

    Example output:

    $ sudo tos cluster list
    NAME    ID    IP                TYPE

    Central    1                    master
    RC1        2    192.168.75.156    data_collector

  5. If you are running a multi-node cluster, get a list of your nodes.

    [<ADMIN> ~]$ sudo tos cluster node list
    sudo tos cluster node list

  6. The upgrade to TufinOS 4 keeps the TOS Aurora data in the /opt partition. The upgrade to TufinOS 4 is like a regular TufinOS installation with one enhancement that keeps the untouched /opt partition, thus all the TOS Aurora data remains available after this upgrade.

    This is not the case with TufinOS configuration data. The upgrade erases all existing TufinOS configurations. The TOS backup does not include your TufinOS configurations. Therefore, before you start create a list of the data you want to keep and save it outside the machine you are upgrading.

    After the upgrade completion, re-configure all your backed-up data before restoring the TOS Aurora snapshot.

    After the upgrade completion, re-configure all your backed-up data before restoring TOS Aurora.

    After the upgrade completion, re-configure all your backed-up data.

    For more information on what to information to save, see Saving TufinOS Configuration:

    If you have any questions about the upgrade, contact the Tufin support team. Do not attempt the upgrade if you are unsure about any part of it.

Upgrade Worker Nodes

Repeat these steps for each worker node.

    1. Identify the node you want to remove and its status by running sudo tos cluster node list on the primary data node.

    2. Run sudo tos cluster node list.

      • If the node is in a healthy state:

        1. On the primary data node, run:

          [<ADMIN> ~]$ sudo tos cluster node remove <node>
          sudo tos cluster node remove <node>

          Parameters

          Parameter

          Description

          Required/Optional

          <node>

          Hostname address of the node to remove.

          Required

          On completion, a new command string is displayed, which you will need to run on the node you want to remove within 30 minutes. If the allocated time expires, you will need to repeat the current step.

        2. Log in to the CLI of the node to be removed.

        3. On the node to be removed, run the command string displayed on completion of the command above. On completion, all TOS-related directories and data will be deleted from the node, therefore make sure you run it on the correct node. Running the command on the wrong node will destroy the cluster.

        All TOS-related directories will be deleted from the node.

      • If the node you want to remove is not in a healthy state:

        1. On the primary data node, run:

          [<ADMIN> ~]$ sudo tos cluster node remove <node> --force
          sudo tos cluster node remove <node> --force

          Parameters

          Parameter

          Description

          Required/Optional

          <node>

          Hostname address of the node to remove.

          Required
    3. Verify that the node has been removed by again running sudo tos cluster node list.

    1. Place the TufinOS ISO image file on the datastore of vSphere. For local installation on a VMware machine, locate the extracted ISO image file.

    2. Confirm that in your virtual machine settings, Boot Options is configured to use BIOS. If you are using EFI, the procedure will not work.

    3. Disconnect all disks that were added to increase partition space. Increase the primary disk size to accommodate the required size.

      4. If a separate disk for Etcd was added, disconnect the disk, and add the disk back after the TufinOS installation is complete.

    4. Edit the properties of the virtual CD/DVD drive, and do one of the following:

      Using vSphere:

      • As Device Type select Datastore ISO file, and browse to the TufinOS ISO image.

      • Under Device Status, select Connect at power on.

      Using a workstation:

      • Under Device Status, select Connect at power on.

      • Under Connection, select Use ISO image file, and browse to the TufinOS ISO image.

    5. Set the VM to boot to BIOS configuration

      1. Navigate to VM settings > VM options.
      2. Check: During the next boot, force entry into the BIOS setup screen.

    6. Power on the VM.

    7. In BIOS > Boot, select CD-ROM Drive.

    8. In BIOS > Exit, select Exit Saving Changes. Click Yes.

    9. Save the settings.

    10. Restart the VM. TufinOS installation begins.

      1. Shut down TOS.

        [<ADMIN> ~]# tos stop
        tos stop

      2. Restart the virtual machine. TufinOS installation begins.

    12. Select TufinOS 4.30 Installation for TOS Aurora.

    13. Select Install TufinOS 4.30 for Worker Node.

    14. When prompted, confirm and choose Yes.

    15. When the installation is complete, reboot the virtual machine.

    16. When BIOS launches, change the Boot option to Hard Drive.

    17. In BIOS > Exit, select Exit Saving Changes. Click Yes.

    18. Log in using the default admin user credentials:

      username: tufin-admin

      password: admin (you will be prompted to change this on first log in)

      IP address: assigned by DHCP

    1. Restore the TufinOS configuration data that you saved before beginning the upgrade procedure (see Save Your TufinOS Configuration). In general we recommend that the new server configurations be similar to the old configurations.

    2. If you want to reset the host name or IP of the machine, do so now. Once TOS Aurora has been installed, changing the host name or IP address will require reinstalling - see Changing IP Address/Host Names. To change the host name, use the command below, replacing <mynode> with your preferred name:

      [<ADMIN> ~]$ sudo hostnamectl set-hostname <mynode>
      sudo hostnamectl set-hostname <mynode>

    3. Configure the server timezone:

      [<ADMIN> ~]$ sudo timedatectl set-timezone <timezone>
      sudo timedatectl set-timezone <timezone>

      where <timezone> is in the format Area/Location. Examples: America/Jamaica, Hongkong, GMT, Europe/Prague.

      To view a list of the time-zone formats that can be used, run:

      [<ADMIN> ~]$ sudo timedatectl list-timezones
      sudo timedatectl list-timezones

    4. Synchronize your machine time with a trusted NTP server. Follow the steps in Configuring NTP Using Chrony. In an HA deployment, all servers need to be synchronized to the same time.

    5. Configure the IP address and DNS, where <Interface Name> is the name of the interface you are using (for example, ens32):

      Use one of these two configuration methods:

      • Method 1: (Recommended) Run this command: 

        [<ADMIN> ~]$ sudo nmtui edit <Interface Name>
        sudo nmtui edit <Interface Name>

        and set the following parameters in the window:

        • Set IPv4 CONFIGURATION to Manual
        • Set Addresses for the physical IP, together with the chosen subnet
        • Set Gateway and DNS Servers to the IPs used by your organization

      • Method 2: Edit the configuration files directly:

        1. Edit file /etc/sysconfig/network-scripts/ifcfg-<Interface Name>: For example:

          sudo vi /etc/sysconfig/network-scripts/ifcfg-ens32

        2. Change line BOOTPROTO=dhcp to BOOTPROTO=static

        3. Add entries at the end of the file:

          IPADDR=<NEWIP>
          NETMASK=<MyNetmask>
          GATEWAY=<MyGateway>
          DNS1=<DNS_IP1>
          DNS2=<DNS_IP2>
          IPADDR=<NEWIP> NETMASK=<MyNetmask> GATEWAY=<MyGateway> DNS1=<DNS_IP1> DNS2=<DNS_IP2>

          where

          <NEWIP> is the physical machine IP

          <MyNetmask> , <MyGateway>, <DNS_IP1>, and <DNS_IP2> are the appropriate values for your network

      Restart the network service.

      [<ADMIN> ~]# systemctl restart network
      systemctl restart network

    6. Run:

      [<ADMIN> ~]$ sudo nslookup <DNS SERVER IP>
      sudo nslookup <DNS SERVER IP>

      If the name of the server is displayed, the DNS server can resolve its own address using a reverse lookup.

      Example Output

      [<ADMIN> ~]$ sudo nslookup  1.2.3.4
4.3.2.1.in-addr.arpa	name=EXAMPLE.company.com

      If the name of the server is not displayed, set it using a reverse lookup entry at /etc/hosts.

      Example Output where 1.2.3.4 4.3.2.1.in-addr-arpa was added.

      [<ADMIN> ~]$ sudo cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost6 localhost6.localdomain6
1.2.3.4 admin.company.com admin
2.3.4.5 5.4.3.2.in-addr-arpa

       

    1. On the primary data node run:

      [<ADMIN> ~]$ sudo tos cluster node add --role=<TYPE>
      sudo tos cluster node add --role=<TYPE>

      where <TYPE> is worker or data, depending on the type of node you want to add.

      On completion, a new command string is displayed, which you will need to run on the new node within one hour. If the allocated time expires, you will need to repeat the current step.

    2. Log in to the CLI of the server to be added as a new node in the cluster.

    3. On the new node, run the command string displayed previously on the primary data node in step 2 above. If the allocated time has expired, you will need to start from the beginning.
    4. Verify that the node was added by running sudo tos cluster node list on the primary data node.

    1. On the primary data nodes, check the TOS status.

      [<ADMIN> ~]$ sudo tos status
      sudo tos status

    2. In the output, check if the System Status is Ok and all the items listed under Components appear as ok. If this is not the case, contact Tufin Support.

      3. Example output:

      [<ADMIN> ~]$ sudo tos status
 Tufin Orchestration Suite 2.0

 System Status: Ok
 System Mode:   Multi Node

 Nodes:
   1 Master, 1 Worker. Total 2 nodes. Nodes are healthy.

 Components:
   Node:            Ok
   Cassandra:       Ok
   Mongodb:         Ok
   Mongodb_sc:      Ok
   Nats:            Ok
   Neo4j:           Ok
   Postgres:        Ok
   Postgres_sc:     Ok

Upgrade the Data Node

  1. If you are going to perform this procedure over multiple maintenance periods, create a new backup each time.

    1. Create the backup using tos backup create: 

      2. [<ADMIN> ~]$ sudo tos backup create
      sudo tos backup create

      Example output:

      [%=Local.admin-prompt% sudo tos backup create
[Aug 23 16:18:42]  INFO Running backup
Backup status can be monitored with "tos backup status"

    2. You can check the backup creation status using tos backup status, which shows the status of backups in progress. Wait until completion before continuing.

      3. [<ADMIN> ~]$ sudo tos backup status
      sudo tos backup status

      Example output:

      [<ADMIN> ~]$ sudo tos backup status
 Found active backup "23-august-2021-16-18"

    3. Run the following command to display the list of backups saved on the node:

      [<ADMIN> ~]$ sudo tos backup list
      sudo tos backup list

      4. Example output:

      [<ADMIN> ~]$ sudo tos backup list
 ["23-august-2021-16-18"]
   Started: "2021-08-23 13:18:43 +0000 UTC"
   Completed: "N/A"
   Modules: "ST, SC"
   HA mode: "false"
   TOS release: "21.2 (PGA.0.0) Final"
   TOS build: "21.2.2100-210722164631509"
   Expiration Date: "2021-09-22 13:18:43 +0000 UTC"
   Status: "Completed"

    4. Check that your backup file appears in the list, and that the status is "Completed".

    5. Run the following command to export the backup to a file: 

      [<ADMIN> ~]$ sudo tos backup export
      sudo tos backup export

      6. The command creates a single backup file.

      [<ADMIN> ~]$ sudo tos backup export
 [Aug 23 16:33:42]  INFO Preparing target dir /opt/tufin/backups
 [Aug 23 16:33:42]  INFO Compressing...
 [Aug 23 16:33:48]  INFO Backup exported file: /opt/tufin/backups/backup-21-2-pga.0.0-final-20210823163342.tar.gzip 
 [Aug 23 16:33:48]  INFO Backup export has completed

    6. If your backup files are saved locally:

      1. Run sudo tos backup export to save your backup file from a TOS backup directory as a single .gzip file. If there are other backups present, they will be included as well.

      2. Transfer the exported .gzip file to a safe, remote location.

        Make sure you have the location of your backups safely documented and accessible, including credentials needed to access them, for recovery when needed.

      After the backup is exported, we recommend verifying that the file contents can be viewed by running the following command:

      [Target location]$ tar tzvf <filename>
      tar tzvf <file name>

    1. Place the TufinOS ISO image file on the datastore of vSphere. For local installation on a VMware machine, locate the extracted ISO image file.

    2. Confirm that in your virtual machine settings, Boot Options is configured to use BIOS. If you are using EFI, the procedure will not work.

    3. Disconnect all disks that were added to increase partition space. Increase the primary disk size to accommodate the required size.

      4. If a separate disk for Etcd was added, disconnect the disk, and add the disk back after the TufinOS installation is complete.

    4. Edit the properties of the virtual CD/DVD drive, and do one of the following:

      Using vSphere:

      • As Device Type select Datastore ISO file, and browse to the TufinOS ISO image.

      • Under Device Status, select Connect at power on.

      Using a workstation:

      • Under Device Status, select Connect at power on.

      • Under Connection, select Use ISO image file, and browse to the TufinOS ISO image.

    5. Set the VM to boot to BIOS configuration

      1. Navigate to VM settings > VM options.
      2. Check: During the next boot, force entry into the BIOS setup screen.

    6. Power on the VM.

    7. In BIOS > Boot, select CD-ROM Drive.

    8. In BIOS > Exit, select Exit Saving Changes. Click Yes.

    9. Save the settings.

    10. Restart the VM. TufinOS installation begins.

    11. Select TufinOS 3 upgrade for TOS Aurora.

    12. Select Upgrade from TufinOS 3 to TufinOS 4.30.

    13. When prompted, confirm and choose Yes.

    14. When the installation is complete, reboot the virtual machine.

    15. When BIOS launches, change the Boot option to Hard Drive.

    16. In BIOS > Exit, select Exit Saving Changes. Click Yes.

    17. Log in using the default admin user credentials:

      username: tufin-admin

      password: admin (you will be prompted to change this on first log in)

      IP address: assigned by DHCP

    1. Restore the TufinOS configuration data that you saved before beginning the upgrade procedure (see Save Your TufinOS Configuration). In general we recommend that the new server configurations be similar to the old configurations.

    2. If you want to reset the host name or IP of the machine, do so now. Once TOS Aurora has been installed, changing the host name or IP address will require reinstalling - see Changing IP Address/Host Names. To change the host name, use the command below, replacing <mynode> with your preferred name:

      [<ADMIN> ~]$ sudo hostnamectl set-hostname <mynode>
      sudo hostnamectl set-hostname <mynode>

    3. Configure the server timezone:

      [<ADMIN> ~]$ sudo timedatectl set-timezone <timezone>
      sudo timedatectl set-timezone <timezone>

      where <timezone> is in the format Area/Location. Examples: America/Jamaica, Hongkong, GMT, Europe/Prague.

      To view a list of the time-zone formats that can be used, run:

      [<ADMIN> ~]$ sudo timedatectl list-timezones
      sudo timedatectl list-timezones

    4. Synchronize your machine time with a trusted NTP server. Follow the steps in Configuring NTP Using Chrony. In an HA deployment, all servers need to be synchronized to the same time.

    5. Configure the IP address and DNS, where <Interface Name> is the name of the interface you are using (for example, ens32):

      Use one of these two configuration methods:

      • Method 1: (Recommended) Run this command: 

        [<ADMIN> ~]$ sudo nmtui edit <Interface Name>
        sudo nmtui edit <Interface Name>

        and set the following parameters in the window:

        • Set IPv4 CONFIGURATION to Manual
        • Set Addresses for the physical IP, together with the chosen subnet
        • Set Gateway and DNS Servers to the IPs used by your organization

      • Method 2: Edit the configuration files directly:

        1. Edit file /etc/sysconfig/network-scripts/ifcfg-<Interface Name>: For example:

          sudo vi /etc/sysconfig/network-scripts/ifcfg-ens32

        2. Change line BOOTPROTO=dhcp to BOOTPROTO=static

        3. Add entries at the end of the file:

          IPADDR=<NEWIP>
          NETMASK=<MyNetmask>
          GATEWAY=<MyGateway>
          DNS1=<DNS_IP1>
          DNS2=<DNS_IP2>
          IPADDR=<NEWIP> NETMASK=<MyNetmask> GATEWAY=<MyGateway> DNS1=<DNS_IP1> DNS2=<DNS_IP2>

          where

          <NEWIP> is the physical machine IP

          <MyNetmask> , <MyGateway>, <DNS_IP1>, and <DNS_IP2> are the appropriate values for your network

      Restart the network service.

      [<ADMIN> ~]# systemctl restart network
      systemctl restart network

    6. Run:

      [<ADMIN> ~]$ sudo nslookup <DNS SERVER IP>
      sudo nslookup <DNS SERVER IP>

      If the name of the server is displayed, the DNS server can resolve its own address using a reverse lookup.

      Example Output

      [<ADMIN> ~]$ sudo nslookup  1.2.3.4
4.3.2.1.in-addr.arpa	name=EXAMPLE.company.com

      If the name of the server is not displayed, set it using a reverse lookup entry at /etc/hosts.

      Example Output where 1.2.3.4 4.3.2.1.in-addr-arpa was added.

      [<ADMIN> ~]$ sudo cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost6 localhost6.localdomain6
1.2.3.4 admin.company.com admin
2.3.4.5 5.4.3.2.in-addr-arpa

       

  4. If you had the etcd database on a separate disk which you disconnected before the upgrade, remount it now.

    1. Reinstate the etcd disk.

    2. Log into the data node as the root user.

    3. Verify that the new disk is recognized by TufinOS.

      [<ADMIN> ~]# lsblk
      lsblk
      [<ADMIN> ~]# ls -l /dev/sd*
      ls -l /dev/sd*

      Compare the output with the name of the disk you saved in the preliminary preparations, and verify that the disk name it returned ends with the next letter in the alphabet. For example, if the name you saved was sdb the output should return sdc. This indicates that TufinOS recognizes the new disk.

    4. Create a variable with the block device path of the new disk.

      [<ADMIN> ~]# BLOCK_DEV="/dev/sd<>"
      BLOCK_DEV="/dev/sd<>"

      where <> represents the letter of the new disk.

    5. Generate a UUID for the block device of the new disk.

      [<ADMIN> ~]# BLOCK_UUID="$(uuidgen)"
      BLOCK_UUID="$(uuidgen)"

    6. Create a primary partition on the new disk.

      [<ADMIN> ~]# parted -s -a optimal ${BLOCK_DEV} mklabel msdos -- mkpart primary ext4 1MiB 100%
      parted -s -a optimal ${BLOCK_DEV} mklabel msdos -- mkpart primary ext4 1MiB 100%

    7. Verify that the partition was created.

      [<ADMIN> ~]# parted -s ${BLOCK_DEV} print
      parted -s ${BLOCK_DEV} print

    8. Format the partition as ext4.

      [<ADMIN> ~]# mkfs.ext4 -L ETCD -U ${BLOCK_UUID} ${BLOCK_DEV}1
      mkfs.ext4 -L ETCD -U ${BLOCK_UUID} ${BLOCK_DEV}1

    9. Verify that the partition has been formatted with the UUID and the etcd label (output should return the partition with UUID and an ETCD label).

      [<ADMIN> ~]# blkid | grep "$BLOCK_UUID"
      blkid | grep "$BLOCK_UUID"

    10. Create the mount point of the etcd database.

      [<ADMIN> ~]# mkdir -p /var/lib/rancher/k3s/server/db
      mkdir -p /var/lib/rancher/k3s/server/db

    11. Set the partition to mount upon operating system startup.

      [<ADMIN> ~]# echo "UUID=${BLOCK_UUID} /var/lib/rancher/k3s/server/db ext4 defaults 0 0" >> /etc/fstab
      echo "UUID=${BLOCK_UUID} /var/lib/rancher/k3s/server/db ext4 defaults 0 0" >> /etc/fstab

    12. Load the changes to the filesystem.

      [<ADMIN> ~]# systemctl daemon-reload
      systemctl daemon-reload

    13. Mount the partition that was added to /etc/fstab.

      [<ADMIN> ~]# mount /var/lib/rancher/k3s/server/db
      mount /var/lib/rancher/k3s/server/db

      If the output is not empty, stop the procedure. The etcd disk cannot be mounted. Review what was missed in the previous steps.

    14. Verify the partition has been mounted (the output should return the block device and mount point).

      [<ADMIN> ~]# mount | grep "/var/lib/rancher/k3s/server/db"
      mount | grep "/var/lib/rancher/k3s/server/db"

      If the output is empty, stop the procedure. The etcd disk is not mounted. Review what was missed in the previous steps.

    1. Run the screen command:

      [<ADMIN> ~]$ screen -S TOS-Install
      screen -S TOS-Install

    2. On the target machine, create the directory /opt/misc/, if it does not exist already.

    3. Transfer the run file (already downloaded) to the /opt/misc/ directory.

    4. Go to /opt/misc/

    5. Verify the integrity of the TOS installation packages by entering the following commands and comparing the output with the checksum information.

      6. [<ADMIN> ~]$ sha256sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz
      sha256sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz
      [<ADMIN> ~]$ sha1sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz
      sha1sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

    6. Extract the TOS run file from its archive.

      [<ADMIN> ~]$ tar -xvzf tos-xxxx-xxxxxxxx-final-xxxx.run.tgz
      tar -xvzf tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

      7. The run file name includes the release, version, and build number.

      TOS file example: R22-2-pga0.0-final-4577.run

    7. Run the TOS Aurora run file.

      [<ADMIN> ~]$ cd /opt/misc/
      cd /opt/misc/
      [<ADMIN> ~]$ sudo sh <runfile>
      sudo sh <runfile>

    8. Run the install command, replacing the parameters:

      • <PRIMARY> - The VIP you will use to access TOS Aurora as described in Prerequisites

      • <SERVICE-CIDR> - The CIDR you want to use for the Kubernetes service network, as described in Prerequisites

      • <PODS-CIDR> Optional. The CIDR you want to use for the Kubernetes pods network, as described in Prerequisites. The default pods network is 10.244.0.0/16

      • <MODULE-TYPE> - One of the following values:

        • ST for SecureTrack only
        • ST, SC for both SecureTrack and SecureChange/SecureApp
        • RC for a remote collector
      • <LOAD> - small, medium, large or extra-large, as provided by your account team, based on your sizing calculation.

      There is also an option to do a dry run, to verify the procedure in advance by going through all the stages without installing anything. To do a dry run, add the parameter --dry-run to the install command.

      [<ADMIN> ~]$ sudo tos install --modules=<MODULE-TYPE> --primary-vip=<PRIMARY> --services-network=<SERVICE-CIDR> --pod-network=<PODS-CIDR> --load-model=<LOAD>
      sudo tos install --modules=<MODULE-TYPE> --primary-vip=<PRIMARY> --services-network=<SERVICE-CIDR> --pod-network=<PODS-CIDR> --load-model=<LOAD>

      Examples:

      $ sudo tos install --modules=ST,SC --primary-vip=192.168.1.2 --services-network=10.10.10.0/24 --load-model=medium

      $ sudo tos install --modules=RC --primary-vip=162.148.10.0 --services-network=10.10.10.0/24 --load-model=large

    9. The EULA is displayed. After reading, enter q to exit the document. If you accept the EULA, enter y and wait until the command completes.

    1. You can now safely exit the CLI screen session:

      [<ADMIN> ~]# exit
      exit

    2. If the installation was for a central (main) cluster, log into TOS Aurora at https://<VIP> in your browser with user=admin, password=admin. If a warning message is shown regarding the site security certificate, 'accept the risk' and continue to the site. You will be prompted to set a new password.

      If the installation was for a remote collector, connect it to the central cluster.

  6. If you are restoring from external storage:

    1. Connect to the external backup storage using sudo tos backup storage set. with the <LOCATION> as external.

    2. Run sudo tos backup list to list all the backups and identify the one that you want to restore.

    3. Run sudo tos restore specifying the desired backup. We recommend that you select the most recent backup. On completion, your data will have been restored.

    If you are restoring from a backup that was saved locally and transferred to a safe, external location:

    1. Copy the export file (gzip format) from the remote location to your primary data node.

    2. Run sudo tos backup import, specifying the full path of the export file, to extract all the backups from the export file to the TOS backup directory.

    3. Run sudo tos backup list to list all the backups and identify the one that you want to restore.

    4. Run sudo tos restore specifying the desired backup. We recommend that you select the most recent backup. On completion, your data will have been restored.

    1. On the primary data nodes, check the TOS status.

      [<ADMIN> ~]$ sudo tos status
      sudo tos status

    2. In the output, check if the System Status is Ok and all the items listed under Components appear as ok. If this is not the case, contact Tufin Support.

      3. Example output:

      [<ADMIN> ~]$ sudo tos status
 Tufin Orchestration Suite 2.0

 System Status: Ok
 System Mode:   Multi Node

 Nodes:
   1 Master, 1 Worker. Total 2 nodes. Nodes are healthy.

 Components:
   Node:            Ok
   Cassandra:       Ok
   Mongodb:         Ok
   Mongodb_sc:      Ok
   Nats:            Ok
   Neo4j:           Ok
   Postgres:        Ok
   Postgres_sc:     Ok