Caligare NetFlow - Knowledgebase
Search:     Advanced search
Browse by category:
Glossary | Contact Us

What is diference between normal, fast and long mls aging?

Add comment
Views: 1564
Votes: 0
Comments: 0

The MLS aging time (default 300 seconds) applies to all NetFlow table entries. You can configure the normal aging time in the range of 32 to 4092 seconds. Flows can age as much as 4 seconds sooner or later than the configured interval. On average, flows age within 2 seconds of the configured value.

Other events might cause MLS entries to be purged, such as routing changes or a change in link state.

If the number of MLS entries exceeds the recommended utilization (see the results of the command: show mls netflow table-contention detailed), only adjacency statistics might be available for some flows.

To keep the NetFlow table size below the recommended utilization, enable the following parameters when using the mls aging command:

  • normal aging - Configures an inactivity timer. If no packets are received on a flow within the duration of the timer, the flow entry is deleted from the table.
  • fast aging - Configures an efficient process to age out entries created for flows that only switch a few packets, and then are never used again. The fast aging parameter uses the time keyword value to check if at least the threshold keyword value of packets have been switched for each flow. If a flow has not switched the threshold number of packets during the time interval, then the entry is aged out.
  • long aging - Configures entries for deletion that have been active for the specified value even if the entry is still in use. Long aging is used to prevent counter wraparound, which can cause inaccurate statistics.

A typical table entry that is removed by fast aging is the entry for flows to and from a Domain Name Server (DNS) or TFTP server.

If you need to enable MLS fast aging time, initially set the value to 128 seconds. If the size of the NetFlow table continues to grow over the recommended utilization, decrease the setting until the table size stays below the recommended utilization. If the table continues to grow over the recommended utilization, decrease the normal MLS aging time.

Command references:

Router(config)# mls aging {fast [threshold {1-128} | time {1-128}] | long 64-1920 | normal 32-4092}
Router# show mls netflow aging
Also read
document What are the optimal netflow aging values?

Others in this Category
document When I run show ip flow top-talkers I see null destination interface. What does null interface mean?
document How can I enable netflow on Cisco 3550 or Cisco 3750 devices?
document I would like to get NetFlow information from individual layer 2 switch ports.
document What is difference between "ip flow ingress" and "ip route-cache flow"?
document "Unable to change flowmask" error message on Cisco 6500
document EARL NetFlow error messages
document What are the optimal netflow aging values?
document I configured NetFlow on Cat6500, but application shows only a few MBytes, whereas it should have been several GBytes.
document On which Cisco device is netflow supported?
document Is NetFlow version 9 supported on 3620? Where can I find the document to see the supported devices?
document What means "TCAM Utilization" and "ICAM Utilization"?
document What means "flow mask" in the mls configuration?
document Can I use a bridged IP traffic NetFlow on PFC3A?
document NetFlow on a Cisco 4500 series. Do I need a NetFlow services card?
document I have interface Vlan2 with record ip route-cache flow, but I have never seen traffic of this interface, although, other VLAN interfaces present in statistics.
» More articles



RSS