tips:ingress-egress-netflow
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
tips:ingress-egress-netflow [2020/11/27 14:03] – [Example : Ingress and Egress enabled on both downstream and upstream interfaces] veera | tips:ingress-egress-netflow [2020/11/27 15:18] – [Configuration options in Trisul] veera | ||
---|---|---|---|
Line 27: | Line 27: | ||
- If used with a sampler can cause inconsistent data | - If used with a sampler can cause inconsistent data | ||
- | [{{: | + | [{{: |
Line 44: | Line 44: | ||
The following diagram shows a valid use case. | The following diagram shows a valid use case. | ||
- | {{: | + | [{{: |
In this example the red and blue flows are measured for Netflow at the upstream interfaces only. Hence there will be no duplicate or inconsistent data. | In this example the red and blue flows are measured for Netflow at the upstream interfaces only. Hence there will be no duplicate or inconsistent data. | ||
Line 55: | Line 55: | ||
//Egress NetFlow accounting might adversely affect network performance because of the additional accounting-related computation that occurs in the traffic-forwarding path of the router.// | //Egress NetFlow accounting might adversely affect network performance because of the additional accounting-related computation that occurs in the traffic-forwarding path of the router.// | ||
+ | |||
+ | ===== Configuration options in Trisul ===== | ||
+ | |||
+ | |||
+ | The following are relevant [[https:// | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | Trisul automatically detects duplicate flow records |
tips/ingress-egress-netflow.txt · Last modified: 2020/11/27 16:05 by veera