Differences

This shows you the differences between two versions of the page.

--- tips:ingress-egress-netflow [2020/11/27 14:04] – [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 44: / Line 44: @@
 The following diagram shows a valid use case.
-{{:tips:egressnetflowdup_-_page_2.png?600|}}
+[{{:tips:egressnetflowdup_-_page_2.png?600|when ingress and egress enabled only on upstream interfaces no duplicates are seen. this configuration works}}]
 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.//
+===== Configuration options in Trisul =====
+The following are relevant [[https://www.trisul.org/docs/ref/netflow-config.html|Netflow configuration parameters]] in Trisul Network Analytics.
+  * ''IgnoreV9EgressFromDevices'' : A list of device IP addresses. Egress direction netflows will be ignored from these devices
+  * ''IgnoreAllEgress'' : Ignore egress netflow from all devices.
+Trisul automatically detects duplicate flow records  which arrive within a time window and removes them.