Distributed De-duplication

The distributed de-duplication is more efficient than the existing de-duplication.

Suppose a particular traffic is tapped at multiple tapping points and sent to different GigaVUE V Series Nodes. In that case, the deduplication application cannot identify the duplicate packets, as they run in different GigaVUE V Series Nodes.

In distributed de-duplication, when you set up a monitoring session with a de-duplication app,

  1. The traffic is first sent to a component.

  2. The component distributes the traffic based on a consistent mechanism to ensure packets from a particular traffic go to the same de-duplication instance.

  3. The packets are shared across the GigaVUE V Series Nodes.

From version 6.5, distributed de-duplication is supported on Azure, AWS, GCP, VMware NSX-T, VMware ESXi, and OpenStack. An enhanced configuration profile for the load balancer is set by default with no option for modification. The default profile uses source and destination IP addresses, source and destination ports as the configuration for calculating the hash value for traffic distribution.

Important:

  1. False traffic health alarms could be raised due to distribution of traffic across GigaVUE V Series Nodes.

  2. Statistics are displayed for all the applications. Distributed De-duplication requires additional entities which will be listed in the statistics page.