Traffic Acquisition Method using VPC Mirroring

If you select the VPC Traffic Mirroring option, the mirrored traffic from your workloads is directed directly to the GigaVUE V Series nodes, and you need not configure the UCT-Vs and UCT-V Controller.

VPC Peering is required to send mirrored traffic from other VPCs into a centralized GigaVUE V Series deployment.


You can choose to use the AWS Network load balancer for a VPC Traffic Mirroring destination. Select Yes to use load balancer. Refer to Configure an External Load Balancer for detailed information.

To acquire traffic using VPC mirroring, perform the following steps:

  1. Install GigaVUE-FM on AWS.

  2. Create a Monitoring Domain.

    1. Select VPC Mirroring as the Traffic Acquisition Method.

      You can configure a prefilter and determine the VPC endpoint traffic that is mirrored. For more information on prefiltering, see Configure a Traffic Pre-filter.

    • UCT-V Controller configuration is not applicable for VPC Traffic Mirroring.
    • VPC mirroring does not support cross-account solutions without a load balancer.
    • For VPC Traffic Mirroring option, additional permissions are required. Refer to the Permissions topic for details.
    • After deploying the Monitoring Session, a traffic mirror session is created in your AWS VPC consisting of a session, a filter, sources, and targets. For more details, refer to Traffic Mirroring in AWS Documentation.

  3. Configure GigaVUE Fabric Components in GigaVUE-FM

  4. Create and configure a Monitoring Session

Refer to the following Gigamon Validated Design for more detailed information on how to use Application Filtering Intelligence and Slicing with VPC MIrroring: