Trisul Network Analytics
Developer Zone

User Tools

Site Tools

You are here: Home » netflow » Sample Netflow configuration for Juniper MX routers
Trace:
netflow:junipermx

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
netflow:junipermx [2023/06/21 16:49] – [Flow table size] veeranetflow:junipermx [2023/06/21 16:49] – [Flow table size] veera
Line 65: Line 65:
  
  
-===== Flow table size =====+===== Default Flow table size =====
  
 By default MX has a very small flow table size of 1K, this can be observed by Trisul as a very slow netflow records / second rate. Go to "Netflow > Flow Sources"  then see the Flow records /sec.  This happens usually when you are configuring JFlow on a Juniper MX for the first time and are using the default 1K flow table size. Juniper recommends configuring the ipv4-flow-table-size to 4 that means 1M for most cases ((https://www.juniper.net/documentation/us/en/software/junos/flow-monitoring/topics/ref/statement/ipv4-flow-table-size.html))  By default MX has a very small flow table size of 1K, this can be observed by Trisul as a very slow netflow records / second rate. Go to "Netflow > Flow Sources"  then see the Flow records /sec.  This happens usually when you are configuring JFlow on a Juniper MX for the first time and are using the default 1K flow table size. Juniper recommends configuring the ipv4-flow-table-size to 4 that means 1M for most cases ((https://www.juniper.net/documentation/us/en/software/junos/flow-monitoring/topics/ref/statement/ipv4-flow-table-size.html)) 
netflow/junipermx.txt · Last modified: 2023/06/21 16:50 by veera