Skip to content

Optional: Assigning a virtual IP address to a resource pool

The zentrap and zensyslog services are designed to receive data from devices in your environment at a specific IP address. Typically, the address is assigned to a specific host. However, if the host fails, then no data is received. To avoid this issue, you can assign a virtual IP (VIP) address to a resource pool, and then Control Center can create a VIP interface on any host in the pool. Zenoss recommends using a VIP with resource pools that include Resource Manager collection services as a best practice.

VIP address management relies on gratuitous ARP to announce new hardware, so your network must support this method using the VIP.

AWS networking does not support gratuitous ARP, and VIPs will therefore not work on AWS-hosted collector pools. There are two possible workarounds for this:

  • Host a pool outside of AWS for trap/syslog collection.
  • Send traps to both of the individual collector IP addresses.

To perform this procedure, you need an unused IPv4 address in the same subnet as the other hosts in the resource pool to modify. To avoid conflicts, ask your networking specialist to assign or reserve the address. In addition, all of the hosts in the resource pool to modify must have the same network interface names. Note: For additional information about network interface names, contact Zenoss Support.

  1. Log in to the Control Center browser interface.
  2. At the top of the page, click Resource Pools.
  3. In the Resource Pool column of the Resource Pools table, click the name of the resource pool to modify.
  4. At the right side of the Virtual IPs table, click Add Virtual IP.

  5. In the Add Virtual IP dialog, specify the virtual IP.

    1. In the IP field, enter an IPv4 address.

      The address must be in the same subnet as the other hosts in the current resource pool.

    2. In the Netmask field, enter an IPv4 subnet mask.

      The mask must match the range of addresses in the current resource pool. The following table associates commonly-used subnet masks with the number of addresses they include.

      Subnet mask Addresses in subnet
      255.255.255.192 64
      255.255.255.224 32
      255.255.255.240 16
      255.255.255.248 8

    3. In the Interface field, enter the name of the network interface that is used on all hosts in the resource pool.

    4. At the bottom of the Add Virtual IP dialog, click Add Virtual IP.

When you configure devices to send syslog or SNMP trap messages, use the virtual IP address assigned to a resource pool.