AppNeta makes a v35 Virtual Monitoring Point that can run on the Linux KVM hypervisor. A qcow2 image is available for download to create the v35 on the KVM host.

Prerequisites

The following are the minimum requirements for the KVM host:

  • Running CentOS/RHEL 7.0 (or higher) or Ubuntu 14.04 LTS (or higher).
  • These virtualization management packages installed: virtinst, libvirt, and libvirt-python.
  • Capable of running a guest with the v35 requirements.
  • Open vSwitch (OVS) software installed if you want to configure VLAN interfaces or set up Usage monitoring.
  • Bridge setup for Delivery and Experience monitoring:
    • A Linux bridge if you want to bind the v35 LAN interface to a physical interface on the host.
    • Alternatively, an OVS bridge if you want to configure VLAN interfaces on a v35.
  • Bridge setup for Usage monitoring:
    • An OVS bridge to mirror traffic from a second physical interface on the host.
  • Installation scripts downloaded on the KVM host:
    • vk35tool.py: Script to create a v35 and configure its interfaces
    • vk35hook.sh: Script to automatically connect a mirror port to an OVS bridge

Set up a v35 on KVM

Make sure that all prerequesites are met before starting this section. Open a support ticket for any assistance in installing OVS software or setting up virtual networks based on the OVS bridge configuration.

Download Software

  1. Download the base image (.qcow2) plus a config image (.iso) from AppNeta at > manage monitoring points > + Add Monitoring Point > Virtual Monitoring Point.
  2. On the host, place the images you downloaded in /var/lib/libvirt/images/.

Below is the list of parameters you should have defined based on the setup done so far:

Parameter Description
BRIDGE_NAME Linux bridge
OVS_NET_LAN Virtual netwok based on the OVS bridge configured to forward VLAN traffic
VLAN_PORTGROUP Port group that defines a set of tagged and untagged VLANs the traffic is received from
OVS_NET_SPAN Virtual network based on the OVS bridge configured for mirroring traffic
BASE_IMAGE qcow2 base image
ISO_IMAGE Config ISO image containing initial monitoring point configuration

Substitute these parameters with the appropriate values in the commands in the next section.

Create v35

You will use vk35tool.py to create a v35. It is recommended that the name of the v35 you create is same as the name supplied in the config ISO image. Substitute this name for V35_NAME in the commands below.

Depending on whether you have a simple setup with a Linux bridge, more complex setup with an OVS bridge, or you are setting up Usage monitoring, select one of the following options:

A. v35 with Linux bridge and no support for Usage monitoring

#./vk35tool.py install V35_NAME --image /var/lib/libvirt/images/BASE_IMAGE.qcow2 --config /var/lib/libvirt/images/CONFIG_IMAGE.iso --network type=bridge,source=BRIDGE_NAME

B. v35 with Linux bridge and support for Usage monitoring

#./vk35tool.py install V35_NAME --image /var/lib/libvirt/images/BASE_IMAGE.qcow2 --config /var/lib/libvirt/images/CONFIG_IMAGE.iso --network type=bridge,source=BRIDGE_NAME type=network,source=OVS_NET_SPAN

C. v35 with virtual network for VLAN traffic and no support for Usage monitoring

#./vk35tool.py install V35_NAME --image /var/lib/libvirt/images/BASE_IMAGE.qcow2 --config /var/lib/libvirt/images/CONFIG_IMAGE.iso --network type=network,source=OVS_NET_LAN,portgroup=VLAN_PORTGROUP

D. v35 with virtual networks for VLAN traffic and for Usage monitoring

#./vk35tool.py install V35_NAME --image /var/lib/libvirt/images/BASE_IMAGE.qcow2 --config /var/lib/libvirt/images/CONFIG_IMAGE.iso --network type=network,source=OVS_NET_LAN,portgroup=VLAN_PORTGROUP type=network,source=OVS_NET_SPAN

The v35 has two interfaces: eth0 and eth1. They are pre-configured as LAN and mirror ports, respectively. In the above commands, the first network option defines a connection to the eth0 and the second network option defines a connection to the eth1. If the second network option is omittted (as seen in the first two commands), the eth1 is still initialized and connected to eth0’s bridge/network. In order to update the network connection to eth0 or eth1 after the v35 is created, you need to shut down the virtual machine first, update interfaces using vk35tool.py and then start the virtual machine. For example, you may create a v35 using option A or C and later set up a virtual network for Usage monitoring. The v35 network options are updated with these commands:

#virsh shutdown V35_NAME
#./vk35tool.py update V35_NAME --network type=<type>,source=<source>[,portgroup=<portgroup>] type=network,source=OVS_NET_SPAN
#virsh start V35_NAME

Note that the update option requires both interfaces to be specified in the command line.

Your v35 monitoring point is ready.

Complete v35 setup

Go back to the AppNeta tab in your browser from where you downloaded the images and follow the on-screen instructions to complete setup. Continue setting up Usage monitoring if your monitoring point is configured for it.