Outgoing counter with length N x 8 bits for the number of bytes associated with an IP Flow.

Incoming counter with length N x 8 bits for the number of bytes associated with an IP Flow.

TCP/UDP destination port number i.e.: FTP, Telnet, or equivalent.

TCP/UDP source port number i.e.: FTP, Telnet, or equivalent.

Data fields that an MX or Z-Series will export via NetFlow are: In NetFlow v9 the NetFlow exporter sends a schema outlining the fields that will be be included in subsequent NetFlow flow updates.

One of the new NetFlow version 9 features is the use of templates. In this use case, Dashboard networks across a wide number of different Dashboard organizations can export NetFlow data to a common server for centralized traffic analysis and monitoring within a network operations center. In some cases, customers may have a very large number of managed networks, also distributed across many distinct Dashboard organizations.

Traffic analysis across a large number of Dashboard networks and organizations - The Cisco Meraki Dashboard provides a large suite of traffic analysis information and summary reports across multiple networks or for an entire Dashboard organization.NetFlow can subsequently be used to aggregate traffic data for both Cisco IOS and Meraki MX/Z-Series devices at a given location. Mixed Meraki & Cisco Deployments - NetFlow is supported within Cisco IOS on a large number of Cisco products.Services and applications that serve as NetFlow collectors are designed to receive the NetFlow data sent from exporters, aggregate the information, and provide data visualization and exploration toolsets.Įxporting NetFlow data about traffic on an MX or Z-Series network can be useful in a variety of scenarios, including the following: NetFlow data is sent from a flow exporter to a flow collector. NetFlow is a protocol for exporting metrics for IP traffic flows.

Netflow traffic