Hi all A flow record is created, when a flow expires. The following are conditions for expiration of a flow:
•Flows which have been idle for a specified time are expired and removed from the cache •Long lived flows are expired and removed from the cache (flows are not allowed to live more than 30 minutes by default, the underlying packet conversation remains undisturbed) •As the cache becomes full a number of heuristics are applied to aggressively age groups of flows simultaneously •TCP connections which have reached the end of byte stream (FIN) or which have been reset (RST) will be expired. Version 9 supports aggregation. The flow record creating in ver 9 is bit different. As per this link, after the expiration of the flow, it is moved to corresponding aggregate cache. Again after timeout in the aggregation cache only, a flow record is created. I don't get it, how can the flow timeout in the aggregation cache which has already been timed out in the main cache. router(config)#ip flow-aggregation cache prefix router(config-flow-cache)#cache timeout ? active Specify the active flow timeout inactive Specify the inactive flow timeout http://www.cisco.com/en/US/products/sw/netmgtsw/ps1964/products_implementation_design_guide09186a00800d6a11.html With regards Kings
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
