UCT-V

UCT-V (earlier known as G-vTAP Agent) is a module installed in the VM instance. It provides packet-level visibility from inside the workload VMs without informing the cloud provider or requiring any assistance from the cloud provider. You can install UCT-V on both Linux and Windows environments. The installed UCT-V mirrors packets from workload virtual interfaces and sends to GigaVUE V Series nodes for filtering, mapping, and transformation.

How UCT-V Works

  • UCT-V mirrors the selected traffic from a source interface to a destination mirror interface.

  • The mirrored traffic is encapsulated using GRE or VXLAN tunneling.

  • Then, sent to the GigaVUE® V Series Node.

A UCT-V can consist of multiple source interfaces and a single destination interface. It mirrors network packets collected from the source interface to destination interface. From the destination interface, packets traverse via L2GRE, VXLAN tunnel, or Secure Tunnels to the GigaVUE V Series Node.

Single Network Interface Configuration

You can configure a single network interface card (NIC to act as both the source and the destination. This setup allows you to monitor ingress and egress traffic using the same interface.

Example scenario:

If the VM has only one interface (For example, eth0), UCT-V configuration, can mirror ingress and egress traffic through eth0.

Note:  Using a single network interface card as the source and the destination interface can introduce higher latency.

Linux Configuration Example for a single NIC configuration:

Grant permission to monitor ingress and egress traffic at iface 

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

Multiple Network Interface Configuration

UCT-V supports lusing two separate interfaces, one for capturing traffic and other for sending mirrored packets.

Example scenario:

  • Use eth0 as the source to monitor traffic

  • Use eth1 as the destination to send mirrored packets

So, the mirrored traffic from eth0 is sent to eth1. From eth1, the traffic is sent to the GigaVUE V Series Node.

Linux UCT-V configuration Example for a dual NIC 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

Loopback Network Interface Configuration

Note:  Windows environment does not support the Loop Back Interface configuration.

UCT-V supports the ability to tap and mirror the loopback interface. You can tap the loopback interfaces on the workload that carries application-level traffic inside the Virtual Machine. The loopback interface is always configured as bidirectional traffic, regardless of the configurations provided in the configuration file.

The UCT-V is offered as a Debian (.deb), Redhat Package Manager (.rpm) package for Linux workloads and a ZIP or MSI for Windows Server workloads. For more information on installing UCT-V on your virtual machines, refer to Configure UCT-V.