action.skip

Installing on a Linux KVM hypervisor

Use the procedures on this page to install the Zenoss Cloud Collector virtual appliance as a guest system on a Linux Kernel-based Virtual Machine (KVM) hypervisor. The procedures have been tested on RHEL/CentOS hypervisor hosts.

Prerequisites

To perform these procedures, you need:

  • A KVM hypervisor host with Virtual Machine Manager (virt-manager) installed and a bridge network adapter configured.

    For more information about configuring a bridge network adapter, refer to KVM documentation.

  • Permission to download files from delivery.zenoss.io.

    Customers can obtain permission by filing a ticket at the Zenoss Support site.

  • Optionally, a VNC client and server, to enable GUI access to the hypervisor host.

Procedures

Follow these steps to install on a KVM hypervisor host:

  1. Download QCOW file

  2. Install the virtual machine

  3. Configure collector networking

  4. Optional: Add multiple interfaces

Downloading the QCOW file

Follow these steps:

  1. In a web browser, navigate to delivery.zenoss.io, and then log in.

  2. Display the Zenoss Cloud files.

  3. Download the Zenoss Cloud Collector QCOW distribution file.

    In the preceding example, the filename is zenoss-collector-363.qcow2.tgz. (The version number may be greater than 363.)

    Make sure you have the latest distribution

    Always use the latest QCOW2 distribution file. For example, if you downloaded a QCOW2 file for a previous installation, please verify that its file name is identical to the latest file available on delivery.zenoss.io before proceeding. New collectors should always be installed with the latest QCOW2 distribution file.

  4. Copy the QCOW distribution file to the hypervisor host.

    For example, to copy the file to the /tmp directory, enter the following command. Substitute the hostname or IP address of the KVM hypervisor host for KVM_HOST:

    scp zenoss-collector-*.tgz root@KVM_HOST:/tmp
    

Installing the virtual machine

Follow these steps:

  1. Log in to the KVM hypervisor host as root, or as a user with superuser privileges.

  2. Extract the QCOW image from the distribution file.

    For example, if the file is located in /tmp, enter the following commands:

    cd /tmp; tar --checkpoint=250000 -xzf zenoss-collector-*.tgz
    

    The tar command displays progress information similar to the following:

    tar: Read checkpoint 250000
    tar: Read checkpoint 500000
    tar: Read checkpoint 750000
    tar: Read checkpoint 1000000
    tar: Read checkpoint 1250000
    tar: Read checkpoint 1500000
    tar: Read checkpoint 1750000
    tar: Read checkpoint 2000000
    tar: Read checkpoint 2250000
    tar: Read checkpoint 2500000
    

    On success, a new file is created. The new file's name is identical to the distribution file's name, less the .tgz extension.

    File name extension required in OpenStack environments

    If you are installing in an OpenStack environment, add the .img extension to the QCOW file name. For example:

    mv zenoss-collector-10.qcow2 zenoss-collector-10.qcow2.img
    
  3. In Virtual Machine Manager, select File > New Virtual Machine.

  4. At Step 1 in the New VM dialog box, select Import existing disk image, and then click Forward.

  5. At Step 2 in the New VM dialog box, specify the disk image and operating system.

    1. In the Provide the existing storage path field, enter the path of the QCOW file, or use the Browse button to locate the file.

      For OpenStack environments, append the .img file extension first (step 2).

    2. From the OS type list, select Linux.

    3. From the Version list, select Ubuntu 20.04.

    4. Click Forward.

  6. At Step 3 in the New VM dialog box, specify the CPU and RAM resources for the virtual machine.

    For more information about collector virtual appliance requirements, see Resource requirements.

  7. At Step 4 in the New VM dialog box, specify the name of the virtual machine and a bridge adapter.

    1. In the Name field, edit the default name, if desired.

      The virtual machine name does not affect collector functionality.

    2. From the Network selection option, select the bridge adapter that maps to an interface that is on the LAN to monitor.

    3. Click Finish.

Configuring collector networking

The default configuration of a Zenoss Cloud Collector virtual machine uses DHCP to obtain IPv4 and IPv6 addresses. Use this procedure to configure static addressing, specify DNS servers in your environment, and specify search domains. The latter two are commonly required to resolve the names of devices in your network environment.

Warning

Please do not change the virtual machine hostname.

  1. Gain access to the console interface of the virtual machine through your hypervisor or through a remote shell utility such as PuTTY.

  2. Log in to the system as user ccuser, password zenoss.

  3. Enter a new, secure password when prompted and keep a secure record of the chosen password.

  4. In the appliance menu, select Configure Network, and then press Enter.

  5. In the NetworkManager TUI, use the arrow key to select Edit a connection, and then press Enter.

    Make sure you edit the Wired connection interface. Currently, a few known issues can cause other, incorrect interface names to appear—for example, ensplan. Please ignore those.

  6. From the Ethernet interfaces, select Wired connection 1, and then use the right and down arrow keys to select <Edit...>. Press Enter.

  7. In the Edit Connection area, use the TAB key to select the <Show> command next to IPv4 CONFIGURATION or IPv6 CONFIGURATION, and then press Enter.

  8. Change <Automatic> to <Manual>, and then enter a static address in CIDR notation.

    If no prefix size is specified, the default (/32) is used.

  9. In the DNS servers field, enter the IP address of one or more DNS servers in your environment.

  10. In the Search domains field, enter one or more domain names used in your environment.

  11. Use the TAB key to select OK, and then press Enter.

  12. Use the down arrow key to select <Quit>, and then press Enter.

  13. In the appliance menu, select Reboot Appliance, and the press Enter.

Optional: Adding multiple interfaces

In some situations, monitoring a small number of isolated network segments through a single collector is preferred. This procedure describes how to configure multiple network interfaces for a single on-premise collector appliance.

Please note the following constraints:

  • The collector appliance must be based on a vSphere (OVA) or Linux KVM (QCOW2) image.
  • The default route interface must be used to reach the Collection Zone outboard host.
  • Syslog and SNMP collectors can only accept messages on the primary interface used for the default route.
  • VLAN tagged interfaces (802.1Q) are not supported.

Note

Start the virtual machine with only the interface intended for the default route.

Configure default route interface

  1. Connect to the collector through SSH or a virtual machine console.

  2. From the main menu, select Configure network.

  3. Select Edit a connection.

  4. Select Wired connection 1, and then click Edit.

  5. In the Device field, enter the MAC address of the network adapter.

  6. To save the configuration, click OK.

  7. Power off the collector and add additional interfaces to the virtual machine.

Configure additional interfaces

  1. From the main menu, select Configure network.

  2. Select Edit a connection.

  3. Click Add.

  4. In the New Connection dialog, select Ethernet, and then select Create.

  5. Set Profile name to Wired Connection 2.

  6. In the Device field, enter the MAC address of the network adapter.

  7. Under IPv4 Configuration, click Show, and then set the following options:

    • Never use this network for default route
    • Ignore automatically obtained routes
    • Ignore automatically obtained DNS parameters

  8. To save the configuration, click OK.

  9. Reboot the collector appliance.

Next step

Connect to a Collection Zone (Initializing a collector appliance).