Set Up a VM With TufinOS

Proceed only if...

You have completed all the checks on your current TOS Classic system and the results indicate you are ready to set up your target machine.
Your target platform meets all general and platform-specific prerequisites.
You have available all IP, DNS and other information needed to set up the server and TOS Aurora. We recommended putting this information in your worksheet and sharing with relevant administrators.

Otherwise, go back.

In this step you will:

Install TufinOS
Configure TufinOS

Overview

This procedure is for the setting up of a supported VM platform, ready to create a TOS Aurora cluster on it or to add it as a node to an existing TOS Aurora cluster.

Complete the steps below in sequence.

Install TufinOS

Place the TufinOS ISO image file on the datastore of vSphere. For local installation on a VMware workstation, locate the extracted ISO image file.
Confirm that in your virtual machine settings, Boot Options is configured to use BIOS. If you are using EFI, the procedure will not work.
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.
Set the VM to boot to BIOS configuration
Example using vSphere
1. Navigate to VM settings > VM options.
2. Check: During the next boot, force entry into the BIOS setup screen.
Power on the VM.
In BIOS > Boot, select CD-ROM Drive.
In BIOS > Exit, select Exit Saving Changes. Click Yes.
Save the settings.
Power on the virtual machine. TufinOS installation begins.
When prompted, select either Install TufinOS 4.30 for Data Node or Install TufinOS 4.30 for Worker Node.
In the virtual machine console, follow the installation prompts. When asked to enter the required configuration, select TufinOS 4.30 installation for TOS Aurora TufinOS 3 upgrade for TOS Aurora. When prompted, confirm and choose Yes.

Do not select TufinOS 4.30 installation for TOS Aurora! Selecting this option will delete all your data from the node and cause the upgrade to fail.
When the installation is complete, reboot the virtual machine.
When BIOS launches, change the Boot option to Hard Drive.
In BIOS > Exit, select Exit Saving Changes. Click Yes.
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
A new command string in the format curl http://xx.xx.xx.xx:8080/xxxxxxxx | sudo sh will be generated. When prompted, copy/paste this string and run it on the new node.

Configure TufinOS

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.
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>
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
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.
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
Verify that the DNS server can resolve its own address using a reverse lookup
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
```

Can I Proceed?

Continue to the next step only if...

You have completed the setup described above.