Install G-vTAP Agents

You must have sudo/root access to edit the G-vTAP agent configuration file.

For dual or multiple ENI configuration, you may need to modify the network configuration files to make sure that the extra NIC/ENI will initialize at boot time.

Note:  Before installing G-vTAP agent .deb or .rpm packages on your Linux VMs, you must install packages like Python3 and Python modules (netifaces, urllib3, and requests). Package iproute-tc is also required on RHEL and CentOS VMs.

You can install the G-vTAP agents either from Debian or RPM packages.

Refer to the following topics for details:

To install from a Debian package:

  1. Download the G-vTAP Agent 1.8-5 Debian (.deb) package from the Gigamon Customer Portal. For assistance contact Contact Technical Support.
  2. Copy this package to your instance. Install the package with root privileges, for example:

    $ ls gvtap-agent_1.8-5_amd64.deb

    $ sudo dpkg -i gvtap-agent_1.8-5_amd64.deb

  3. Once the G-vTAP package is installed, modify the file /etc/gvtap-agent/gvtap-agent.conf to configure and register the source and destination interfaces. The following examples registers eth0 as the mirror source for both ingress and egress traffic and eth1 as the destination for this traffic:

    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.

    Example 1—Configuration example to monitor ingress and egress traffic at interface eth0 and use the same interface to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress mirror-dst

    Example 2—Configuration example to monitor ingress and egress traffic at interface eth0 and use the interface eth1 to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress
    # eth1   mirror-dst

    Example 3—Configuration example to monitor ingress and egress traffic at interface eth0 and eth 1; use the interface eth1 to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress
    # eth1   mirror-src-ingress mirror-src-egress mirror-dst

  4. Save the file.

  5. To enable the third-party orchestration, a configuration file /etc/gigamon-cloud.conf needs to be created with the following contents:

    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <controller list IP addresses separated by comma>
    	remotePort: 8891
  6. Reboot the instance.

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

$ sudo /etc/init.d/gvtap-agent status

G-vTAP Agent is running

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

  1. Download the G-vTAP Agent 1.8-5 RPM (.rpm) package from the Gigamon Customer Portal. For assistance contact Contact Technical Support.
  2. Copy this package to your instance. Install the package with root privileges, for example:

    $ ls gvtap-agent_1.8-5_x86_64.rpm

    $ sudo rpm -i gvtap-agent_1.8-5_x86_64.rpm

  3. Modify the /etc/gvtap-agent/gvtap-agent.conf file to configure and register the source and destination interfaces.The following example registers the eth0 as the mirror source for both ingress and egress traffic and registers eth1 as the destination for this traffic as follows:

    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.

    Example 1—Configuration example to monitor ingress and egress traffic at interface eth0 and use the same interface to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress mirror-dst

    Example 2—Configuration example to monitor ingress and egress traffic at interface eth0 and use the interface eth1 to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress# eth1   mirror-dst

    Example 3—Configuration example to monitor ingress and egress traffic at interface eth0 and eth 1; use the interface eth1 to send out the mirrored packets

    # eth0   mirror-src-ingress mirror-src-egress# eth1   mirror-src-ingress mirror-src-egress mirror-dst

  4. Save the file.

  5. To enable the third-party orchestration, a configuration file /etc/gigamon-cloud.conf needs to be created with the following contents:

    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <controller list IP addresses separated by comma>
    	remotePort: 8891
  6. Reboot the instance.

Check the status with the following command:

$ sudo service gvtap-agent status

G-vTAP Agent is running

  1. Launch the RHEL/CentOS agent AMI image.
  2. Download the following packages from the Gigamon Customer Portal. For assistance contact Contact Technical Support.
    • strongSwan TAR files
    • gvtap-agent_1.8-5_x86_64.rpm
    • gvtap.te files (type enforcement files)
  3. Copy the downloaded G-vTAP package files and strongSwan TAR file to G-vTAP Agent.
  4. Checkmodule -M -m -o gvtap.mod gvtap.te
    semodule_package -o gvtap.pp -m gvtap.mod
    sudo semodule -i gvtap.pp
  5. Install G-vTAP Agent package:
    sudo rpm -ivh gvtap-agent_1.8-5_x86_64.rpm
  6. Edit gvtap-agent.conf file to configure the required interface as source/destination for mirror:

    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.

    # eth0 mirror-src-ingress mirror-src-egress mirror-dst
    # sudo /etc/init.d/gvtap-agent restart
  7. Install strongSwan: 
    tar -xvf strongswan-5.7.1-1.el7.x86_64.tar.gz
    cd strongswan-5.7.1-1.el7.x86_64
    sudo sh ./swan-install.sh

  8. Reboot the instance.