Linux G-vTAP Agent Installation
Refer to the following sections for Linux agent installation:
Single vNIC Configuration
A single NIC/vNIC acts both as the source leader in a bidirectional clock relationship (formerly master) 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
Multiple vNICs Configuration
A G-vTAP Agent lets you configure multiple vNICs. One or many vNICs can be configured as the source interface. The monitored traffic can be sent out using any one of the vNICs or using a separate, non-monitored vNIC.
For example, assume that there is eth0 and eth1 in the monitoring instance. 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.
