Installing SL1 on Hardware Appliances and Virtual Appliances

Download this manual as a PDF file

This section describes how to install SL1 on hardware Appliances or on virtual machines.

Use the following menu options to navigate the SL1 user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Prerequisites

To perform the steps in this section:

  • You must have already performed the prerequisites for all the ScienceLogic Hardware Appliances in your SL1 stack or for all the Virtual Appliances in your SL1 stack.
  • You must have a valid customer account that allows you to download the SL1 ISO. For details, contact your Customer Success Manager.
  • You must download the SL1 ISO.
  • Mount the SL1 ISO on each virtual appliance.
  • You must have access to the files for your SSL certificate.
  • You must have a valid customer account that allows you to access the Artifactory page on the ScienceLogic Support Site. For details, contact your Customer Success Manager.

ScienceLogic does not support vmotion or VMware Snapshots for backups of data. For backup purposes, ScienceLogic supports only SL1 backups to remote storage. vmotion andVMware Snapshots can cause SL1 outages. For details on SL1 backups, see the section on Backup Management.

Upgrading

For detailed upgrade instructions, see the section on Upgrading SL1.

Installing the Database Server

The Database Server should be the first node or appliance you install. To do so:

  1. Boot the appliance from the SL1 ISO. The Installation window appears.

    If you are using Hyper-V, check that the ScienceLogic installation ISO mounted correctly and that the Virtual Machine displays the install screen. To do this, right-click the Virtual Machine in inventory and select Connect or View and then Connect via Console.

  2. Select Install EM7. The Model Type window appears.
  3. Select Database. Select Continue.
  4. The Military Unique Deployment window appears. Do not select [Enable] if you are not using a Military Unique Deployment.
  5. Select Continue. The Database window appears.
  6. In the Database window, select Local Database and select Continue.
  7. After the installer for the selected appliance type is loaded, the Network Configuration window appears.
  1. Enter the following information:
  • IP Address. Type the primary IP address of the node or appliance.
  • Netmask. Type the netmask for the primary IP address of the node or appliance.
  • Gateway. Type the IP address for the network gateway.
  • DNS Server. Type the IP address for the primary Nameserver.
  • Hostname. Type the hostname for the node or appliance.
  1. Select Continue.
  2. The System Password window appears.
  1. Type the password for the em7admin user on the operating system and select Continue.
  2. Type the password for the em7admin user again and select Continue.
  3. The appliance installer runs, and the virtual machine reboots automatically, and you are returned to a login prompt.
  4. If you are using a VMware instance, after the appliance reboots, follow the instructions to install VMware tools.
  5. If the Database Server is running a version of SL1 before 11.2.0, follow the instructions to license the appliance.
  6. Repeat these steps for the remaining nodes or appliances: the Administration Portal, the Data Collectors, and the Message Collectors (if applicable).

Installing the Administration Portal, Data Collector and/or Message Collector

 Starting with SL1 version 11.2.0, the installation process for SL1 Collectors was updated. For detailed procedures for installing a collector, see Installing and Configuring an SL1 Collector.

After installing the Database Server, you can next install:

  1. The Administration Portal (if applicable)
  2. The Data Collectors
  3. The Message Collectors (if applicable)

You can use the following instructions to build the Administration Portal, and one or more Data Collectors and Message Collectors.

  1. Boot the appliance from the SL1 ISO.
  2. Select Install EM7. The Model Type window appears.

The Model Type window

  1. Select the appropriate appliance type. Select Continue.
  2. The Military Unique Deployment window appears. Do not select if you are not using a Military Unique Deployment.

The Military Unique Deployment window

  1. After the installer for the selected appliance type is loaded, the Network Configuration window appears.

The Network Config window

  1. Enter the following information:
  • IP Address. Type the primary IP address of the appliance.
  • Netmask. Type the netmask for the primary IP address of the appliance.
  • Gateway. Type the IP address for the network gateway.
  • DNS Server. Type the IP address for the primary Nameserver.
  • Hostname. Type the hostname for the appliance.

  1. Select Continue.
  2. The System Password window appears:

The System Password window

  1. Type the password for the em7admin user on the operating system and select Continue.
  2. Type the password for the em7admin user again and select Continue.
  3. If you are using a VMware instance, after the appliance reboots, follow the instructions to install VMware tools.
  4. Follow the instructions to configure the appliance in the Web Configuration Tool.

Licensing the SL1 Appliances

For details on licensing the SL1 Appliances, see the section Licensing and Configuring an Appliance.

Additional Steps for SL1 10.1

SL1 10.1.x included an upgrade to MariaDB. The upgrade did not include a tool, jemalloc, that helps manage memory usage.

This section applies only to the following releases:

  • 10.1.0
  • 10.1.1
  • 10.1.2
  • 10.1.3
  • 10.1.4
  • 10.1.4.1
  • 10.1.4.2
  • 10.1.5
  • 10.1.5.1

For SL1 versions later than 10.1.5.1, jemalloc is included with the platform. For SL1 versions prior to 10.1.0, jemalloc is included with the platform.

To avoid problems with memory usage on Database Servers, perform the following steps after upgrading MariaDB for 10.1.x.

Perform these steps first on the active Database Server and then on each additional Database Server in your SL1 System.

  1. Open an SSH session to the Database Server.

  2. To verify that the Database Server is not currently running jemalloc, enter the following command at the shell prompt:

    silo_mysql -e 'show global variables like "version_malloc_library"'

    3. If the Database Server is not currently running jemalloc, the shell will display the following:

    Variable Name Value
    version_malloc_library system

  3. Search for the file /usr/lib64/libjemalloc.so.1.

    If the file does not exist, contact ScienceLogic Customer Support to request the file jemalloc-3.6.0-1.el7.x86_64.rpm.

    To install the RPM, use a file-transfer utility, copy the file to a directory on the SL1 appliance. Then enter the following commands at the shell prompt:

    cd /usr/lib64
sudo yum install jemalloc-3.6.0-1.el7.x86_64.rpm

  4. Create the file /etc/systemd/system/mariadb.service.d/jemalloc.conf, as follows:

    vi /etc/systemd/system/mariadb.service.d/jemalloc.conf

  5. Add the following lines to the file:

    [Service]
Environment="LD_PRELOAD=/usr/lib64/libjemalloc.so.1"
  6. Save and close the file.

  7. Reload the systemd config files with the following command:

    sudo systemctl daemon-reload

  8. Restart the Database Server:

    To restart the standalone Database Server or the primary Database Server in a cluster, enter the following:

    sudo systemctl restart mariadb

    To restart each secondary Database Server in a cluster:

    1. Open an SSH session to the secondary Database Server. At the shell prompt, enter:

      coro_config
    2. Select 1.
    3. When prompted to put the Database Server into maintenance, select y.

    4. Open an SSH session to the primary Database Server. To pause SL1, enter the following command at the shell prompt:

      sudo touch /etc/.proc_mgr_pause

    5. In the SSH session for the secondary Database Server, restart MariaDB:

      crm resource restart mysql

    6. After MariaDB has restarted successfully on the secondary Database Server, return to the SSH session on the primary Database Server. Remove the pause file for SL1 using the following command:

      sudo rm /etc/.proc_mgr_pause

    7. In the SSH session on the secondary Database Server, take the Database Server out of maintenance. At the shell prompt, enter:

      coro_config
    8. Select 1.
    9. When prompted to take the Database Server out of maintenance, select y.

  9. To verify that jemalloc is running on the Database Server, enter the following command at the shell prompt:

    silo_mysql -e 'show global variables like "version_malloc_library"'

    10. If the Database Server is currently running jemalloc, the shell will display something like the following:

    Variable Name Value
    version_malloc_library jemalloc 3.6.0-0-g46c0af68bd248b04df75e4f92d5fb804c3d75340
  10. Perform these steps on each Database Server in your SL1 system.