Skip to content

Installing on VMware vSphere hypervisors

Use this procedure to install the Zenoss Cloud Collector virtual appliance as a guest system on a VMware vSphere hypervisor. The virtual appliance has been tested on vSphere versions 6.0, 6.5, 6.7, and 7.0.


The minimum supported version of vSphere is 6.0. Earlier versions do not work with the current virtual appliance.


To perform this task, you need:


Follow these steps to install on a vSphere hypervisor host:

  1. Download OVA file

  2. Install the virtual machine

  3. Configure collector networking

  4. Optional: Add multiple interfaces

Downloading the OVA image

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

  2. Display the Zenoss Cloud files.

  3. Download the Zenoss Cloud Collector OVA file.

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

Installing the virtual machine

This procedure is based on vSphere Web Client 6.5. The steps might be different with other versions of the vSphere Client.

  1. Use the vSphere Client to log in to vCenter as root, or as a user with superuser privileges, and then display the Home view.

  2. In the top navigation bar, choose Actions > Deploy OVF Template.

    1. Use panels in the Deploy OVF Template wizard to select the OVF package.

      To choose the package from a drive on your workstation or network share, browse to the location and choose the OVA file.

      Click Next.

    2. Select name and location: Specify a name for the OVF, select a datacenter or folder as the deployment location, and then click Next.

    3. Select a resource: Select the host, cluster, or other resource on which to run the deployed template, and then click Next.


      On releases of vSphere 6.5 before update 1d, the import may fail at this step due to a known bug. To work around this issue, see Workaround for vSphere bug

    4. Review details: Verify the template details, and then click Next.

    5. Select storage: In Select virtual disk format, choose Thick Provision, accept defaults for other fields, and then click Next.

    6. Select networks: Accept defaults and click Next.

    7. Ready to Complete: Verify the deployment settings, and then click Finish.

  3. On the new virtual machine's Getting Started tab, click Power on virtual machine.

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.


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.


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.

Workaround for vSphere bug

Releases of vSphere 6.5 before update 1d are unable to import OVA packages that include a compressed manifest file due to a known bug.

Follow these steps to work around the problem and import the virtual appliance:

  1. On your workstation, extract the files in the virtual appliance package into a folder, with a utility such as WinRAR or 7zip.

  2. In the folder, delete the manifest file (with the .mf extension).

  3. Repeat step 5a of the procedure in the preceding section. Instead of selecting the OVA file, select both of the remaining files in the folder (with .ovf and .vmdk extensions).

    Both files must be selected for import at the same time.

  4. Continue with the remaining steps of the install procedure.


    You may need different permissions to adminstrate a VM that is not imported from an entire OVA package.

Next step

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