• ControlUp On-Premises Server Installation - Version 8.5

    This article will guide you through the ControlUp On-Premises (COP) server installation using the on-premises server installation wizard. 

    Before launching the on-premises server installation program, ensure that all COP prerequisites are met.

    To install an on-premises server:

    1. Run the ControlUp On-Premises installation wizard with administrative privileges. From the introductory screen, click Continue to begin the installation process.

      mceclip2.png

    2. We recommend that you read the license agreement documents carefully. Check I agree to the Terms of Use and Privacy Policy and then click Accept.

      Pic1_4.jpg

    3. Select the appropriate license and then click Continue.

      Trial license: This option activates the 21-days trial. It includes all features of the product.
      Paid license: Use this option, if your organization has already signed an agreement to use ControlUp.


      Pic1_3.jpg

    4. From the Configure a License screen, enter your personal information and click Continue.

      Pic1_2.jpg

      Note: The organization name cannot be changed in the future since it is hardcoded. Resetting the organization name will create a new configuration file which means that all settings/modifications will be reset to default settings.

    5. Copy the path or use the Browse button to select the destination folder for the installation. Confirm your input by clicking Continue.

      Pic1_1.jpg

    6. Use the text box or click Browse to select a valid username from your Active Directory (AD) domain. This account will be granted the Log On as a Service privilege. Enter the password for this AD user and click Continue.

      Pic2_1.jpg

    7. The On-Premise installation requires an SQL Server database. Choose your preferred installation type below and click Continue.

      Light Mode: Installs MS SQL Server Express Edition and creates the ControlUp database on the same server that you currently run the installation wizard on.
      Production Mode: Select this option, if you already have an SQL instance with an empty database installed. 

      Pic3.jpg

    8. If Light Mode is selected, the Scripts Action Import window is shown (Step 9). If Production Mode was chosen, provide the database details in the ControlUp Database window:

      SQL Server:  The hostname or IP address of the SQL Server.
      Port: The SQL communication port. By default, 1433.

      Select the authentication for accessing the SQL Server:

      Use Windows Integrated Authentication: A domain user that is granted SQL login permission. This user must be a member of the db_owner database role.  
      Use SQL Authentication: A dedicated SQL user that must be set up in advance. This user must be a member of the db_owner database role. 

      Pic5_2.jpg

    9. In the Scripts Action Import window, browse to the path of the script library file that is provided with the COP installation files, then click Continue.
      If you do not want to import any script actions, you can skip this step and click Continue.

      mceclip1.png

    10. In the VE & AA Import window, browse to the path of the ldif file, which is provided with the COP installation files, then click Continue.
      If you do not want to import any Virtual Expert rules and Automated Actions, you can skip this step and click Continue.

      mceclip0.png

    11. In the Mail Server Settings window, enter

      SMTP Server: The IP address or FQDN of your SMTP Server.
      Sender: The sender’s mail address that is used for sending notification emails. 

      Enter the authentication details for the SMTP Server:
      User: Username for connecting to the SMTP Server.

      Password: The user's password.

      If your SMTP server allows anonymous login, check the Connect Anonymously checkbox.

      You can also skip the configuration of the SMTP Server by clicking the Skip button. 

      Pic6.jpg

    12. Select the AD group, which consists of all authorized ControlUp users. The dialog will automatically populate the field with the current domain name\user group. If you want to change the group, click Browse and select another AD group. To confirm the group, click Continue.

      Pic7.jpg
    13. To configure the Insights On-Premises, enter the following information and click Continue.

      Insights Server: The FQDN or IP address of the Insights server.
      Port: By default 443.
      Activity Files Folder: The location for storing files uploaded from the monitors to IOP.
      Backup Files Location: Used to store the zip files that the monitor creates when archiving the data.

      If you have not installed Insights On-Premises, check the Skip ControlUp Insights On-premises installation radio button and click Continue.

      Note: The selected Activity File Folder path can be a shared location (UNC path) or a local path. If a local path is selected, the monitor, once deployed, will automatically create that folder location on the targeted machine.



      Pic8.jpg
    14. In the SOLVE On-Premise Configuration, enter the FQDN or IP address of your SOLVE Server. You can also skip the configuration of the SOLVE server by checking the Skip ControlUp SOLVE On-Premises installation radio button. Click Continue to confirm your input.

      Pic9.jpg
    15. Review the installation details and click Install to execute the installation.

      Pic10.jpg

       

    16. Once the installation is completed, a confirmation screen appears. Click Close to the installation wizard. 

      Pic13.jpg

       

     

     

  • ControlUp On-Premises Real-Time Console Installation - Version 8.5

    This article will guide you through the ControlUp on-premises Real-Time Console Installation. This installation should be performed after you completed the ControlUp On-Premises Server Installation.

    To install the ControlUp Real-Time Console:

      1. Open the installation file you received from ControlUp to launch the Welcome to the ControlUp Setup Wizard. Click Next.

        Pic2.jpg

      2. View and accept the End-User License Agreement. Click Next.

        Pic3.jpg

      3. In the Select Installation Folder window, click Browse... or enter the path to the folder where ControlUp will be installed. Click Next.

        Pic4.jpg

      4. In the Ready to Install window, click Install to execute the installation. 

        Pic5.jpg

      5. Once the installation is complete, a confirmation screen appears. If you wish to launch ControlUp, check the Launch ControlUp checkbox. Click Finish to complete the installation process.

        Pic6.jpg

      6. If the Launch ControlUp checkbox was selected, the Welcome to ControlUp screen appears. When the Real-Time Console is launched for the first time, the on-premises server name or IP address must be provided. Click Continue.

        Pic7.jpg

        Note: Do not enter localhost or 127.0.0.1 as it will cause issues when a ControlUp monitor is added at a later stage.

      7. If you receive a Server Certificate Error, first click the Don't show this message again checkbox and confirm by clicking Yes.

        mceclip0.png
      8. The ControlUp Real-Time Console opens in the organization that you defined in the on-premises server installation. 

        mceclip1.png

  • Insights On-Premises Linux-Based 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 Linux-based installation of IOP 8.5. If you want to install IOP from an OVA file, refer to the Insights On-Premises Virtual Appliance-Based Installation - Version 8.5 installation guide.

    Prerequisites

    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

    CPU / RAM

    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

    Storage

    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

    Network

    The following ports must be open on your IOP server:

    Machine Type Protocol Port
    Standalone TCP

    443

    8089

    9997

    Master Node TCP

    443

    8089

    Data Node TCP

    9887

    9997

    8089

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

    Recommended Operating Systems

    To install the IOP server, you will need to have one of the following supported Linux variants:

    • Photon OS 3.0
    • CentOS 7 (or above)
    • Ubuntu 16.4 (or above)
    • Red Hat Enterprise Linux 7.6

    Installed Software

    Some of our backend components run Docker containers, so you need to install Docker 18.09.08 or above on your Linux machine. Installation instructions for Docker on Linux can be found here.

    IOP Installation

    For the installation of the IOP server on your Linux machine, you need 2 files that are provided by our Support Team:

    • iopcmd-[version].tgz (for example iopcmd-8.5.733.34.tgz)
    • iop_[version]_images_stable.tgz (for example iop_8_5_images_stable.tgz)

    The installation steps of both environment types, standalone or clustered, are explained below. 

    Installation on a standalone machine

    To install IOP on your standalone machine:

    1. Download the iop_[version]_images_stable.tgz and iopcmd-[version].tgz to your Windows machine. 
    2. Copy both files to the /opt/ directory on your Linux machine. For this, you can use WinSCP or any other software of your choice. 
    3. Login to your Linux machine and move both files to /opt
      sudo mv iop_8.5_images_stable.tgz /opt/
      sudo mv iopcmd-8.5.733.34.tgz /opt/
    4. Extract the iopcmd-8.5.733.34.tgz file to /opt. This will create a new directory "iopcmd" and 2 files, iopcmd and iopcmd.conf. 
      sudo tar zxvf iopcmd-8.5.733.34.tgz
    5. Move the iop_8.5_images_stable.tgz file to /opt/iopcmd/ and rename the file to iop_images.tgz:
      sudo mv iop_8.5_images_stable.tgz /opt/iopcmd/iop_images.tgz
    6. Start the installation script. As this is a standalone installation, use the -t standalone parameter and choose a strong password, in our case P@ssw0rd
      sudo ./iopcmd install local -t standalone -pwd P@ssw0rd -p iop_images.tgz

      After some minutes, the installation is completed:

      InstallationComplete.png

      Note: The password must be at least 8 characters in length. Use a strong password with special characters as this is the admin password for your IOP environment. The password is also necessary for any upgrades, so make sure you don’t lose it.

    Installation of a clustered machine

    If you decide to use a clustered environment, repeat Steps 1-3 on each cluster node. Pay attention to Step 8 which uses a slightly different command for cluster and data node. 

    1. Download both files iop_[version]_images_stable.tgz and iopcmd-[version].tgz to your Windows machine. 
    2. Copy both files to the /opt/ directory on your master node. For this, you can use WinSCP or any other software of your choice. 
    3. Log in to your master node and change to the /opt/ directory.
      cd /opt/
    4. Move the iop_[version]_images_stable.tgz to /opt/iopcmd/iop_images.tgz.
      sudo mv /opt/iop_8_5_images_stable.tgz /opt/iopcmd/iop_images.tgz
    5. Log in to your data node and change to the /opt/ directory.
      cd /opt/
    6. Move the iop_8_5_images_stable.tgz to /opt/iopcmd/iop_images.tgz by running the following command:
      sudo mv /opt/iop_8_5_images_stable.tgz /opt/iopcmd/iop_images.tgz
    7. Make sure that you currently are in the /opt/iopcmd directory. Run the following command on the master node:
      sudo ./iopcmd install local -t master -pwd <Your Password> -p iop_images.tgz
    8. Run the following command on each data node
      sudo ./iopcmd install local -t data -m <DNS name or IP address of the Master Node> -pwd <Your Password> -p iop_images.tgz

    Once the installation is complete, the message “Install Complete!” appears in the installation prompt. 

    Congratulations! You have promoted your Linux server to a new IOP server. To test connectivity with the new server, browse to https://<IPofIOPServer> and wait for the login screen of IOP. 

    mceclip0.png
    Sign in with the admin user and use the password that you defined in the installation script. 

    mceclip1.png

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

    mceclip2.png

  • 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.

    Prerequisites

    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

    CPU / RAM

    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

    Storage

    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

    Network

    The following ports must be open on your IOP server:

    Machine Type Protocol Port
    Standalone TCP

    443

    8089

    9997

    Master Node TCP

    443

    8089

    Data Node TCP

    9887

    9997

    8089

    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...”.

      mceclip0.png


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

      mceclip1.png

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

      mceclip3.png

    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).

      mceclip4.png


    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: 10.10.10.10/24). 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.

        mceclip1.png
      • 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. 

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

    Congratulations! You can now use your new server for Insights On-Premises. To test connectivity with the new server, browse to https://<IPofIOPServer> and wait for the login screen of IOP. 

    mceclip0.png

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

    mceclip1.png

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

    mceclip2.png

     

  • Solve On-Premises Installation - Version 8.5

    Solve is now available for ControlUp On-premises installations. For details about Solve, see Welcome to Solve.

    To use Solve On-Premises (SOP), you must first install the Solve server. For the installation, a pre-configured OVF template needs to be deployed from the vSphere Client. Use this guide to take you through the installation steps for a new SOP server.

    The last section of this article briefly describes the upgrade procedure of an already installed SOP server. Be aware that whether you are installing or upgrading SOP, you need to have a VMware vSphere Client installed in your environment as this is currently the only supported installation option.

    Note: SOP currently does not display historical data. You won't see the history icon.

    This guide includes:

    SOP Prerequisites

    Hardware

    The Solve server requires a machine that meets these minimum hardware specifications:

    • 2 vCPU
    • 4 GB RAM
    • 30 GB disk space

    Network

    Make sure to enable TCP port 443 on the machine where you are installing the SOP server. This is for the communication between the SOP server and the ControlUp Monitors and web browsers. 

    SOP Licensing

    Access to Solve requires a license. 

    To receive a free trial:

    1. Open the ControlUp Real-Time Console and click the Help tab at the top of the screen.
    2. In the top ribbon, click About

      Pic1.jpg
    3. Click Licensing.

      Pic2.jpg
    4. A window opens displaying the details of your ControlUp subscription. Click Start my Free 21-day trial.

      mceclip1.png

       

    Install the SOP server

    It's time to install the SOP server. As mentioned earlier, the installation process requires a pre-configured OVF template (x.ova file) that you can get from our Support Team.

    To install the SOP server:

    1. Download the file to your local machine and open your VMware vSphere client.
    2. Right-click a host and select Deploy OVF Template... The installation wizard opens.
      Pic3.jpg
    3. Click Choose Files and select the OVA file that you downloaded to your local computer. Click NEXT to select a location for the virtual machine. 
      mceclip0.png


    4. Name the SOP virtual machine and select the folder where you want to store it. Click NEXT.

      mceclip3.png

    5. Select a compute resource on your host. Click NEXT to review the configuration.
      Deployment4_Ready.jpg
    6. Review the pre-configured details for SOP. Click NEXT to select a storage location for the virtual hard disk. 
      mceclip4.png
    7. Select the storage location and disk format. The default disk size is 30 GB. Click NEXT to edit the network settings.Deployment6_1_Ready.jpg
    8. Select the network location. This location should be accessible from the ControlUp Monitors and ControlUp On-premises server via TCP port 443. Click NEXT.
      Deployment7_Ready.jpg

    9. Customize the template as follows:
      • Hostname. The virtual appliance's hostname (for example: sib_server).
      • DNS Domain. The virtual appliance’s DNS domain (for example: testdomain.local).

        Note: The DNS domain must be the same as the ControlUp On-premises server's AD domain.

      • IP/Subnet (CIDR). The IP address in CIDR notation for the virtual appliance (for example: 10.10.10.10/24). 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.
      • Appliance Password. A password for your SOP 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.

        mceclip0.png

        Click NEXT to continue with the installation. 
        Deployment9_Ready.jpg
        After the preceding configurations are done, review the summary of the installation and click FINISH to complete the deployment.

        mceclip5.png

    To configuration of the new Solve server details must be saved in the COP configuration. To do so,

    1. Open the Control Panel and select Programs and Features.
    2. Right-Click ControlUp Server.
    3. Select Change. The configuration wizard appears.

      mceclip0.png
    4. Click Solve On-Premises Configuration
      Pic6_1.jpg
    5. Enter the server name or IP address of your new SOLVE server and click Update. 
      Pic7_1.jpg

    Congratulations! You successfully installed your new SOP server. To test connectivity, open your web browser and go to https://hostname.DNSDomain. If you see the login screen below, then you can move on to the configuration of the SOP server. This is further explained in the Solve On-Premises Configuration article.

    mceclip0.png

     

     

     

    Upgrade SOP Server

    If you already have an SOP server and you need to upgrade the version, follow these steps:

    1. Back up the SOP configuration as described in the Configuration Backup and Restore section in the Solve On-Premises Configuration article.
    2. Shut down the old SOP server.
    3. Deploy a new SOP OVA as described in the SOP OVA Deployment section above.
    4. If the new VM is assigned an IP address or an FQDN different from the old VM, reconfigure ControlUp On-Premises as described in this Setup article.
    5. Restore the SOP database as described in the Backup and Restore section above.

     

  • Solve On-Premises Configuration - Version 8.5

    Solve provides two different ways to administer the Solve on-premises (SOP) server. Before you can apply changes to your configuration, make sure that you already have an SOP server installed. If you don't have an SOP server in your environment, install the server first. This is explained in the Solve On-Premises Installation - Version 8.5 guide. Once installed, you can start the configuration of the SOP server. 

    You can choose between the administration from the command-line interface or the graphical user interface (Solve UI), which you can access from your web browser. We explain the administration options from both interfaces in the upcoming sections.

    This guide includes:

    Administration via Command Line

    You can make use of the various administration scripts that help you to manage your SOP server. In this article, we will explain how to use these scripts. In our example, we will use “sib_server” as our SOP server name and cuadmin as the default user that we chose during the OVF deployment.  

    Backup of SOP Database

    Backing up the SOP database is one of the most important administration actions that you should perform regularly. For this purpose, you can use a backup script that lets you back up all configuration and data stored in the Solve database.

    To backup your SOP database:

      1. Open Putty and create an SSH connection to your SOP server.mceclip0.png
      2. Enter the user credentials for the appliance user.mceclip1.png
      3. The command line is ready.
        Linux2.jpg
      4. Change the directory to /opt/scripts and see if there is a backup.sh file.

        Linux3_1.jpg
      5. Make the backup.sh executable by using this command, confirm by entering your password.
        sudo chmod +x backup.sh
        Linux4.jpg
      6. Run the backup.sh script.
        sudo ./backup.sh
        Linux5.jpg
      7. The backup file backup.tar is saved to the /opt directory. Change to this directory.Linux6.jpg
      8. You can now transfer the file via SCP to your local computer.

        Note: When you perform another backup, the old backup.tar will be overwritten. Make sure that you save the files to a different folder.

    Restore of SOP database

    The procedure for restoring a database is as straightforward as the backup process. The restore.sh script is used to restore an existing backup.

    To restore the database:

    1. Copy the backup file that you want to restore into the /opt folder on your SOP server. If your backup file is stored on a Windows machine, the easiest way to copy the file is by using SCP, for example:
      scp backup.tar cuadmin@10.20.55.4:/opt:
    2. Create an SSH connection to the SOP server as described in steps 1-3 from the Backup of SOP database section. Navigate to the /opt folder and check if the backup.tar that you just copied exists.
      Linux8.jpg
    3. Go to the /opt/scripts directory. Here you can find the restore.sh.
      Linux9.jpg
    4. Make the restore.sh executable by using the command below, confirm by entering your password.
      sudo chmod +x restore.sh

      Linux10.jpg

    5. Run the restore.sh script.
      sudo ./restore.sh

    Update a Certificate

    Traffic between the web browser and the SOP server is open and can be intercepted. You can and should use certificates for an encrypted connection to the Solve user interface. SOP provides self-signed certificates that can be found on the SOP server in the /opt/sib_volumes/Solve-proxy/ssl directory.

    To update a certificate:

    1. Copy the server.crt and server.key from your local computer to the /opt/sib_volumes/Solve-proxy/ssl directory.Linux12.jpg
    2. Create an SSH connection to the SOP server as described in steps 1-3 from the Backup of SOP database section. Go to the /opt/scripts directory and check if the user-cert-update.sh script exists.Linux13.jpg
    3. Make the user-cert-update.sh executable by using the command below, confirm by entering your password.
      sudo chmod +x user-cert-update.sh
      Linux14.jpg
    4. Run the user-cert-update.sh script.
      sudo ./user-cert-update.sh
      Linux15.jpg

    Administration via Solve UI

    Besides the command-line scripts, the SOLVE UI that is accessed from the web browser provides additional administration settings. 

    Configuration Actions via GUI

    The SOP GUI allows you to perform a range of actions:

    mceclip0.png

    mceclip2.png

    LDAP Integration

    This option is not available in the on-premises installation. 

    Configuration Backup & Restore

    Backup

    Click Backup to download a backup file (backup.tar) to your local machine. This backup includes the SOP settings and customization settings of your Solve machine. 

    Restore

    1. Click Upload Files and choose the backup file from our local computer. 
    2. Click Apply to save the changes and import the configuration file to the SOP server.

      mceclip3.png


    Logs

    For troubleshooting problems with Solve components or connections, it is often useful to have log files available. Press the Export Log Files button to save and compress log files to your local machine. Send an email with the logs attached to our Support team at support@controlup.com.

    Export and Import Certificates

    Export

    This option allows you to export a previously imported signed certificate so it can be used on a new SOP machine. The exported certificate will only work when the new SOP machine has the same hostname as the one you exported the certificate from. 

    Click Export Certificate to download the currently used certificate files to your local machine.

    mceclip1.png

    Import

    1. To import a certificate, click Upload Certificate to browse the client for the .crt and .key certificate files. 

      mceclip2.png

      Both files are required so you need to mark both files and click Open.

      mceclip7.png

    2. When the files are located, click Apply. You will see the popup as shown below.

      mceclip3.png

      Note: While the certificates are being imported, Solve will not be available.

      SOP_GUI_certificate_import_is_underway.png

    Session Timeout

    Under Session idle timeout, you are able to set the time in minutes after which your Solve session will be disconnected. Hit Apply to save the changes. 

    Stop Ignoring SSL Errors

    SOP comes with a self-signed certificate out of the box that, by default, is not trusted by the ControlUp Monitor. This certificate is used for the communication between the ControlUp Monitor, the web browser, and the SOP server and to access the Solve URL.

    When you update a certificate, the ControlUp Monitors must be configured to use this updated certificate. Follow the instructions below to enforce the updated certificate and to stop ignoring SSL errors.

    To configure the Monitor's SSL behavior:

    1. Open the ControlUp Real-Time Console. Select the Solve tab and click Manage Monitors.
      mceclip1.png
    2. In the Settings screen, click Monitors Settings. This opens the configuration screen for the ControlUp Monitors.
      Certificate2.jpg
    3. From the left menu, click Solve Settings.
      Certificate3.jpg
    4. Uncheck the Ignore SSL Certificate Errors checkbox, and click OK to apply the settings. 
      Certificate4.jpg

    If Solve becomes unavailable after you changed the settings, check any trust issues between the ControlUp Monitors and the new SOP certificate.

     

  • Insights - IOP Forwarder Installation - Version 8.5

    The Insights on-premises (IOP) forwarder is an essential component that forwards activity files from the ControlUp Monitor instance to the IOP server(s), where the log data is indexed. The installation file installs the forwarder and creates configuration files that are used for the log forwarding mechanism. 

     

    Where to Install

    If you run multiple ControlUp Monitors in your environment and you selected a local path for activity files during the on-premises installation, the IOP Forwarder must be installed on each ControlUp Monitor server. If you configured a network share for the activity files, the IOP Forwarder must be installed on the machine, where the network share resides. 

    Prerequisites

    • A machine with the ControlUp Monitor installed.
    • A dedicated Linux machine where the activity files are forwarded to.

    To install the IOP forwarder:

    1. Double-click on the installation file to start the installation wizard. Click Next.

      Pic1.jpg

    2. Select where you want to install the IOP Forwarder. Click Next and the IOP architecture screen appears.

      Pic2.jpg
    3. From the IOP architecture screen, select the type of architecture you want to use. You have the option between Standalone and Cluster

      Pic3.jpg

    4. From the Forwarder Configuration screen, enter the folder for the activity files and the IP or DNS of the Indexer machine (IOP server). Once selected, click Next, and the Ready to Install screen appears. 

      Pic4.jpg
    5. Click Install to confirm and start the installation. 

      Pic5.jpg

    6. Once the installation is complete, the confirmation screen appears. Click Finish to end the installation process. 

      Pic6.jpg