Insights On-Premises Virtual Appliance Installation - Version 8.5

The Insights on-premises (IOP) component captures, indexes, and correlates real-time data in a searchable repository from which you can view a variety of dashboards, graphs, reports, alerts, etc.

IOP is a Linux-based application that can be installed in two different ways:

  • Virtual Appliance: This option includes the deployment of an OVA file that runs the Photon OS distribution. This installation option is currently available for VMware only. 
  • Linux OS installation: This option allows you to install IOP on a separate Linux machine. It means, you install one of the supported Linux distributions and we provide you the necessary installation files.

This installation guide assumes that you want to use the Virtual Appliance-based installation of IOP 8.5. If you want to install IOP on a separate Linux machine, refer to the Insights On-Premises Linux-Based Installation - Version 8.5 installation guide.


Session-based Installations

  • Single (Standalone): The recommended server installation for environments with 5000 or fewer sessions. In this case, you only need 1 Linux server. 
  • Cluster: This option is recommended for environments with 5000 or more sessions. As this is a clustered environment, at least 2 Linux servers must be used, one for the master node, the other for the data node(s). Each data node should serve up to 5000 sessions. It means that for every 5000 sessions, you need to set up a new machine for the data node. 

Sizing examples

Number of sessions Number of Master Nodes Number of Data Nodes
6 000 1 2
9 000 1 2
11 000 1 3


Minimum requirements for CPU and memory

Installation Mode CPU Cores RAM
Single (Standalone) 12 Cores 32 GB
Cluster Master Node 12 Cores 32 GB
Cluster Data Node 8 Cores 16 GB


Installation Mode OS Volume Data Volume Notes
Single (Standalone) SSD 100 GB 500 GB (disk with at least 800 IOPs)

50 GB (/var partition) **

The data must be mounted under /opt/iop_volumes

If ext3 or ext4 are chosen for the data volume, the “Reserved block percentage” should be set to 1%, using the following command (as root): tune2fs -m 1 <FILESYSTEM-PATH>. For example: tune2fs -m 1 /dev/sdb1

Cluster Master Node SSD 100 GB (at least 800 IOPs) 1 TB (disk with at least 800 IOPs)

50 GB (/var partition) **

The recommended file systems for the data volume are ext3, ext4 or xfs


Cluster Data Node SSD 100 GB (at least 800 IOPs)  

50 GB (/var partition) **


The data must be mounted under /opt/iop_volumes


If ext3 or ext4 are chosen for the data volume, the “Reserved block percentage” should be set to 1%, using the following command (as root): tune2fs -m 1 <FILESYSTEM-PATH>. For example: tune2fs -m 1 /dev/sdb1


** if mounted on a different file system than OS partition


The following ports must be open on your IOP server:

Machine Type Protocol Port
Standalone TCP




Master Node TCP



Data Node TCP




For more information on general port requirements, see the Communication Ports Used by ControlUp: On-Premises Mode article.

IOP Installation

The IOP installation must be performed through the VMware vSphere Client. This requires an OVA file that is provided by our Support Team. 

To install IOP from the OVA file: 

  1. Download the OVA file to your local computer. 
  2. Open your vSphere Client with an account that has administrative permissions on the hosts. 
  3. Right-click on a host and select “Deploy OVF template...”.


  4. Choose Local File and then browse to find the downloaded OVA file.


  5. Assign a unique name as well as a location where the virtual machine will be deployed. 


  6. Select a resource.

  7. Select the Virtual Disk format and the virtual machine storage policy (for better performance and flexibility reasons, both “thick” formats are recommended).


  8. On the Customize Template page, provide additional information about your virtual machine.

    • Hostname. The virtual appliance's hostname (for example: iop_server).
    • DNS Domain. The virtual appliance’s DNS domain (for example: testdomain.local).
    • IP/Subnet (CIDR). The IP address in CIDR notation for the virtual appliance (for example: Leave blank if DHCP should be used to retrieve IP information automatically.
    • Default Gateway. The default gateway address for this virtual appliance. Leave blank if DHCP should be used to automatically assign Gateway information.
    • DNS. The domain name servers for this VM (comma separated). Leave blank if DHCP should be used.

    • Root Password. The root password for the CLI admin user. 

      Note: Use a strong password, with a minimum of 8 characters. It should contain a combination of the following character types: uppercase, lowercase, special characters, and numbers. Spaces are not allowed.

    • Machine Type. Choose the type of appliance. This can be either standalone, master, or data. 
    • Master IP/DNS. Only relevant when using the machine type data. In this case, provide the IP or DNS name of the master node. 

  9. Review the selected settings and click Finish to complete the installation of the IOP server. 

Post Installation Configuration

We recommend to increase the disk volume of the IOP data partition, which by default is 50 GB.

To increase disk capacity for standalone/data machines:

  1. Right-click your virtual machine and select Edit Settings.
  2. Increase the capacity of Hard disk 2 from 50 GB to a higher value like 500 GB.

Once you completed the post installation, you can now use your new server for Insights On-Premises. To test connectivity to the new server, browse to https://<IPofIOPServer> and wait for the login screen of IOP. 


Sign in with the admin user and use the password that you defined during the OVF deployment. 


After you successfully logged in, you should see the home screen of Insights:



1-on-1 Demo
Schedule now
Price Quote
Get it now
Need a Script?
Get it here
Powered by Zendesk