Difference between revisions of "Deduplication in GigaFlow"
From Observer GigaFlow Support | VIAVI Solutions Inc.
(Created page with "==Overview== GigaFlow can deduplicate flows although it is not recommended by default. Duplicate flows can be used for forensic analysis, e.g. in the situation where an IP pa...") |
(→Overview) |
||
| Line 2: | Line 2: | ||
GigaFlow can deduplicate flows although it is not recommended by default. Duplicate flows can be used for forensic analysis, e.g. in the situation where an IP pair is received by a router on an ingress port, deduplication reduces the information available for trouble-shooting. | GigaFlow can deduplicate flows although it is not recommended by default. Duplicate flows can be used for forensic analysis, e.g. in the situation where an IP pair is received by a router on an ingress port, deduplication reduces the information available for trouble-shooting. | ||
| + | |||
| + | === Changing the Default Settings == | ||
GigaFlow's deduplication behaviour can be modified at '''System > Global > General'''. | GigaFlow's deduplication behaviour can be modified at '''System > Global > General'''. | ||
| − | Setting '''Process Duplicate Flows''' to '''No''': will disable all processing of duplicate flows (no storage, no forensics, no summaries). The only places these will be accounted for are in incrementing the duplicates counter on the device. | + | * Setting '''Process Duplicate Flows''' to '''No''': will disable all processing of duplicate flows (no storage, no forensics, no summaries). The only places these will be accounted for are in incrementing the duplicates counter on the device. |
| − | + | * Setting '''Process Duplicate Flows''' to '''Yes''' and '''Ignore Duplicates on Summaries''' to '''Yes''': will fully process and store the duplicates but the byte/flow/packet count against interfaces will not be affected by the duplicates (important for capacity planning). | |
| − | Setting '''Process Duplicate Flows''' to '''Yes''' and '''Ignore Duplicates on Summaries''' to '''Yes''': will fully process and store the duplicates but the byte/flow/packet count against interfaces will not be affected by the duplicates (important for capacity planning). | + | * Setting '''Process Duplicate Flows''' to '''Yes''' and '''Ignore Duplicates on Summaries''' to '''No''': will fully process and store the duplicates and the byte/flow/packet count against interfaces will be affected by the duplicates (not good for capacity planning). |
| − | + | ||
| − | Setting '''Process Duplicate Flows''' to '''Yes''' and '''Ignore Duplicates on Summaries''' to '''No''': will fully process and store the duplicates and the byte/flow/packet count against interfaces will be affected by the duplicates (not good for capacity planning). | + | |
Revision as of 11:55, 27 September 2019
Overview
GigaFlow can deduplicate flows although it is not recommended by default. Duplicate flows can be used for forensic analysis, e.g. in the situation where an IP pair is received by a router on an ingress port, deduplication reduces the information available for trouble-shooting.
= Changing the Default Settings
GigaFlow's deduplication behaviour can be modified at System > Global > General.
- Setting Process Duplicate Flows to No: will disable all processing of duplicate flows (no storage, no forensics, no summaries). The only places these will be accounted for are in incrementing the duplicates counter on the device.
- Setting Process Duplicate Flows to Yes and Ignore Duplicates on Summaries to Yes: will fully process and store the duplicates but the byte/flow/packet count against interfaces will not be affected by the duplicates (important for capacity planning).
- Setting Process Duplicate Flows to Yes and Ignore Duplicates on Summaries to No: will fully process and store the duplicates and the byte/flow/packet count against interfaces will be affected by the duplicates (not good for capacity planning).
