{"id":948,"date":"2010-05-09T09:57:40","date_gmt":"2010-05-09T08:57:40","guid":{"rendered":"http:\/\/mccltd.net\/blog\/?p=948"},"modified":"2010-06-09T10:01:18","modified_gmt":"2010-06-09T09:01:18","slug":"netflow-export","status":"publish","type":"post","link":"http:\/\/darenmatthews.com\/blog\/?p=948","title":{"rendered":"NetFlow Export"},"content":{"rendered":"<p>NetFlow Export Version Formats<\/p>\n<p>For all export versions, the NetFlow export datagram consists of a header and a sequence of flow records. The header contains information such as sequence number, record count, and system uptime. <!--more--><\/p>\n<p>The flow record contains flow information, for example IP addresses, ports, and routing information. NetFlow version 9 export format is the newest NetFlow export format. The distinguishing feature of the NetFlow version 9 export format is that it is template based. Templates make the record format extensible. This feature allows future enhancements to NetFlow without requiring concurrent changes to the basic flow-record format.<\/p>\n<p>The use of templates with the NetFlow version 9 export format provides several other key benefits:<\/p>\n<ul>\n<li>You can export almost any information from a router or switch including Layer 2 through 7 information, routing information, IP version 6 (IPv6), IP version 4 (IPv4), multicast, and Multiprotocol Label Switching (MPLS) information. This new information allows new applications for export data and new views of network behavior.<\/li>\n<li>Third-party business partners who produce applications that provide collector or display services for NetFlow are not required to recompile their applications each time a new NetFlow export field is added. Instead, they might be able to use an external data file that documents the known template formats.<\/li>\n<li>New features can be added to NetFlow more quickly, without breaking current implementations.<\/li>\n<li> NetFlow is &#8220;future-proofed&#8221; against new or developing protocols, because the version 9 export format can be adapted to provide support for them and for other non-NetFlow-based approaches to data collection.<\/li>\n<\/ul>\n<p>The work of the Internet Engineering Task Force (IETF) IP Information Export (IPFIX) Working Group (WG) and the IETF Pack Sampling (PSAMP) WG are based on the NetFlow version 9 export format.<\/p>\n<p>The version 1 export format was the original format supported in the initial Cisco IOS software releases containing NetFlow functionality and is rarely used today. The version 5 export format is a later enhancement that adds Border Gateway Protocol (BGP) autonomous system information and flow sequence numbers. The version 7 export format is an enhancement that adds NetFlow support for Cisco Catalyst series switches that use hybrid or native mode. Versions 2 through 4 and version 6 export formats were either not released or are not supported. Version 8 export format is the NetFlow export format to use when you enable router-based NetFlow aggregation on Cisco IOS router platforms.<\/p>\n<p>Configuring NetFlow Export (example):<\/p>\n<blockquote><p>ip flow-export source fastethernet0\/0<br \/>\nip flow-export version 5<br \/>\nip flow-export destination 1.1.1.1 2055<br \/>\ninterface fastethernet0\/0<br \/>\nip flow ingress<br \/>\nip flow egress<br \/>\nip route-cache flow<br \/>\nexit<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>NetFlow Export Version Formats For all export versions, the NetFlow export datagram consists of a header and a sequence of flow records. The header contains information such as sequence number, record count, and system uptime.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[83,10],"tags":[45],"_links":{"self":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/948"}],"collection":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=948"}],"version-history":[{"count":2,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/948\/revisions"}],"predecessor-version":[{"id":950,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/948\/revisions\/950"}],"wp:attachment":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=948"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=948"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}