netflow介绍.ppt

* NetFlow Deployment Managerial Advice Current economic environment drives the need to justify the cost of premium service(s) accounting IT and management need to agree on which fields to track Where in the network (access, distribution, or core)? Crucial to set appropriate expectations for management with regards to frequency of NetFlow reports Cisco recommends a trial deployment in one department/area before network-wide implementation NetFlow Deployment Technical Advice IT and management need to agree on which fields to track Currently and in the future Do not export Versions 5,7, 9 simultaneously with Version 8 Plan NetFlow deployment in the network topology to avoid a design that creates duplicate flows for billing Use a dedicated interface / VLAN for data export Monitor lost packet counter in NFC Check the export link bandwidth Estimated export of 3% to 5% of the interface throughput NetFlow Performance Paper Tests NetFlow performance on software platforms depends on number of flows in the cache. NetFlow Performance paper covers data on the topic Paper at /go/netflow under “Technical Documents” 0, 1, and 2 NetFlow data export destinations Initial performance after enabling V8 Aggregation vs. v5, V9 performance “Full” NetFlow vs. 1:100 sampled NetFlow Hardware: Cisco 2600, 3600, 7200 NPE-400 and NSE-1, 7500 RSP8 VIP4-80 with CEF and dCEF, 12000 Engine 1 Linecard dCEF Updated Performances document available for Flexible NetFlow + new platforms Cisco1800, Cisco2800, Cisco3800, Cisco 7200 NPE-G2 Performance Testing Conclusions NetFlow data export (single/dual) No significant impact NetFlow v5 versus v8: little or no impact Number of Active Flows Additional CPU Utilization 10,000 4% 45,000 12% 65,000 16% Average additional CPU utilization across all platforms tested * * * * * * * * * * * * * * * * /en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7f9.html * /en/US/products/sw/iosswrel/ps1835/products_configuration_guid