Install G-vTAP OVS Agent for OVS Mirroring

This is applicable only if you are using G-vTAP OVS agent as the source of acquiring traffic. You must have sudo/root access to edit the G-vTAP OVS agent configuration file. Before installing the G-vTAP OVS agents, you must have launched the GigaVUE‑FM instance.

Note:  After rebooting your Ubuntu, you must redeploy the respective monitoring sessions to restore the mirror traffic on the respective Ubuntu VM interfaces.

You can install the G-vTAP OVS agents either from Debian or RPM packages as follows:

Install the G-vTAP OVS Agent from Ubuntu/Debian Package

To install from a Debian package:

  1. Download the latest version of G-vTAP OVS Agent Debian (.deb) package from the Gigamon Customer Portal.
  2. Copy this package to OpenStack compute nodes. Install the package with root privileges, for example:

    $ ls gvtap-ovs-agent_1.8-2_amd64.deb

    $ sudo dpkg -i gvtap-ovs-agent_1.8-2_amd64.deb

  3. Once the G-vTAP OVS agent package is installed, modify the file /etc/gvtap-agent/gvtap-agent.conf to configure and grant permission to monitor ingress and egress traffic and to transmit the mirrored packets.

    Note:  Any changes to the G-vTAP Agent config file made after the initial setup require an agent restart and an inventory refresh or sync from GigaVUE-FM to pick up the new changes and re-initiate the traffic mirroring. When you have an active, successful monitoring session deployed, modifying the G-vTAP config file results in traffic loss until GigaVUE-FM does a periodic sync on its own every 15 minutes.


    br-int mirror-dst

     

    # Changes for OVS Mirroring

    # This Value will be used as local Ip in OVS Mirror Config

    tunnel-src 172.20.20.11

    # This Value will be used as Next Hop for Tunneled Packets

    tunnel-gw 172.20.20.1

    # OVS Agent Mode, Values: auto|standard|dpdk|hw-offload

    ovs-agent-mode auto

    # VLAN Tag value (valid: 0-4094)

    ovs-vlan-tag 2020

    # Egress Interface for OVS Mirrored Traffic

    ovs-egress-if vlan2020

  4. After modifying the G-vTAP OVS config file, start the agent service.

    $ sudo service gvtap-agent start

  5. The G-vTAP OVS agent status will be displayed as running. Check the status using the following command:

    $ sudo service gvtap-agent status

    G-vTAP Agent is running

Install the G-vTAP OVS Agent from RPM package

To install from an RPM (.rpm) package on a Redhat, CentOS, or other RPM-based system:

  1. Download the G-vTAP OVS Agent RPM (.rpm) package from the Gigamon Customer Portal.
  2. Copy this package to OpenStack compute nodes. Install the package with root privileges, for example:

    $ ls gvtap-ovs-agent_1.8-2_x86_64.rpm

    $ sudo rpm -ivh gvtap-ovs-agent_1.8-2_x86_64.rpm

  3. Once the G-vTAP OVS agent package is installed, modify the file /etc/gvtap-agent/gvtap-agent.conf to configure and grant permission to monitor ingress and egress traffic and transmit the mirrored packets.

    Note:  Any changes to the GvTAP agent config file made after the initial setup require an agent restart and an inventory refresh or sync from GigaVUE-FM to pick up the new changes and re-initiate the traffic mirroring. When you have an active, successful monitoring session deployed, modifying the GvTAP config file results in traffic loss until GigaVUE-FM does a periodic sync on its own every 15 minutes.


    # br-int mirror-dst

     

    # Changes for OVS Mirroring

    # This Value will be used as local Ip in OVS Mirror Config

    tunnel-src 172.20.20.11

    # This Value will be used as Next Hop for Tunneled Packets

    tunnel-gw 172.20.20.1

    # OVS Agent Mode, Values: auto|standard|dpdk|hw-offload

    ovs-agent-mode auto

    # VLAN Tag value (valid: 0-4094)

    ovs-vlan-tag 2020

    # Egress Interface for OVS Mirrored Traffic

    ovs-egress-if vlan2020

  4. After modifying the G-vTAP OVS config file, start the agent service and verify its status.

    $ systemctl start gvtap-agent.service

    $ sudo service gvtap-agent status

    G-vTAP Agent is running

When you are installing a self-signed RPM package, you must execute the following command to import the signing key into the RPM db.

sudo rpm --import /path/to/YOUR-RPM-GPG-KEY

To upgrade G-vTAP OVS agent:

  • You must backup the /etc/gvtap-agent/gvtap-agent.conf configuration file before upgrading the G-vTAP OVS Agent and uninstall the old OVS agents.
  • Follow the same installation procedure to upgrade the G-vTAP OVS agents.
  • After upgrading the G-vTAP OVS Agent, copy and modify the gvtap-agent.conf file, stop the agent, and start the agent. Redeploy the Monitoring Session if required.
    service gvtap-agent stop
    service gvtap-agent start