547
edits
Ingress filter: Difference between revisions
→Packet deduplication
| Line 64: | Line 64: | ||
It is also possible to capture packets which have been detected as duplicates but since these packets are excluded from further processing as well as the packet ring buffer it is only possible to create a live capture. Also, since only hash values are stored, the first packet of a series of duplicates will not be part of the duplicate capture, but it can be captured with the regular capture feature as it is part of the packet processing. | It is also possible to capture packets which have been detected as duplicates but since these packets are excluded from further processing as well as the packet ring buffer it is only possible to create a live capture. Also, since only hash values are stored, the first packet of a series of duplicates will not be part of the duplicate capture, but it can be captured with the regular capture feature as it is part of the packet processing. | ||
Packet deduplication works on a per [[Virtual Link Group functionality|Virtual Link Group]] basis. Duplicates are detected within each VLG so duplicates from one link groups do not interfere with packets having the same hash in other link groups. | |||
To utilize the packet deduplication feature, follow the following steps: | |||
# Configure and enable the packet deduplication engine in the Ingress filter configuration section as described below. | |||
# [[Virtual Link Group Configuration Guide|Configure]] each VLG to enable or disable packet deduplication for that group. | |||
==== Statistics ==== | ==== Statistics ==== | ||