Linux G-vTAP Agent Installation
Refer to the following sections for the Linux agent installation:
Single NIC Configuration
A single NIC/vNIC acts both as the source and the destination interface. A G-vTAP Agent with a single NIC/vNIC configuration lets you monitor the ingress or egress traffic from the NIC/vNIC. The monitored traffic is sent out using the same NIC/vNIC.
For example, assume that there is only one interface eth0 in the monitoring VM. In the G-vTAP configuration, you can configure eth0 as the source and the destination interface, and specify both egress and ingress traffic to be selected for monitoring purpose. The egress and ingress traffic from eth0 is mirrored and sent out using the same interface.
Note: Using a single NIC/vNIC as the source and the destination interface may cause increased latency in sending the traffic out from the VM.
Example of the G-vTAP config file for a single NIC/vNIC configuration:
Grant permission to monitor ingress and egress traffic at iface
# eth0 mirror-src-ingress mirror-src-egress mirror-dst
Dual NIC Configuration
A G-vTAP Agent lets you configure two NICs/vNICs. One NIC/vNIC can be configured as the source interface and another NIC/vNIC can be configured as the destination interface.
For example, assume that there is eth0 and eth1 in the monitoring VM. In the G-vTAP Agent configuration, eth0 can be configured as the source interface and egress traffic can be selected for monitoring purpose. The eth1 interface can be configured as the destination interface. So, the mirrored traffic from eth0 is sent to eth1. From eth1, the traffic is sent to the GigaVUE V Series node.
Example of the G-vTAP config file for a dual NIC/vNIC configuration:
Grant permission to monitor ingress and egress traffic at iface
# 'eth0' to monitor and 'eth1' to transmit the mirrored packets.# eth0 mirror-src-ingress mirror-src-egress # eth1 mirror-dst
