Distributed 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 will not be able to identify the duplicate packets, as they are running in different GigaVUE V Series Nodes. When you enable traffic distribution in a monitoring session that is configured with a deduplication application, traffic is first sent to a component that distributes the traffic across GigaVUE V Series Nodes in that monitoring session based on a consistent mechanism to ensure that packets from an identical flow are sent to the same GigaVUE V Series Node, so that the packets are processed by same deduplication application and deduplicated properly.

The deduplication, along with traffic distribution enabled, is more accurate. It can deduplicate identical traffic tapped at different tapping points and sent to multiple GigaVUE V Series Nodes.

From version 6.5, distributed de-duplication is supported on Azure, AWS and, GCP. An enhanced configuration profile for the load balancer will be set by default with no option for modification. The default profile will use 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 statistics page.