Flows and Flow RecordsДЄ net flow, or flow, consists of packets that share these attributes: To configure NetFlow on the collector, see our Integration Guides or the documentation provided by your NetFlow collector service. To configure NetFlow on the Firebox, see Configure NetFlow. Physical, VLAN, bridge, wireless, and link aggregation interfaces are supported in all zones (Trusted, External, Optional, and Custom).ДЇor more information about the NetFlow protocol, see RFC 3954. In Fireware v12.5 or higher, you can also select to monitor traffic destined for the Firebox itself. You can select to monitor Firebox-generated (self-generated) traffic, which is outbound traffic generated by the Firebox itself. In Fireware v12.5 or higher, you can also select to monitor egress traffic, which is traffic that exits an interface.

For pass-through traffic, the Firebox monitors bi-directional traffic if you select to monitor both inbound and outbound interfaces. On the Firebox, you can select to monitor ingress traffic, which is traffic that arrives on an interface. The Firebox itself does not display or analyze flow records. Many third-party applications support the NetFlow protocol. The collector runs a third-party application that uses the NetFlow protocol to record and analyze network traffic. The Firebox monitors the selected interfaces and sends streams of data known as net flow records to the collector for analysis. You also specify the IP address of a server known as a collector. When you configure NetFlow on your Firebox, you specify which interfaces to monitor. NetFlow is a protocol that is used to collect and analyze IP network traffic. For example, you can use NetFlow data to troubleshoot network performance issues or investigate security concerns. In Fireware v12.3 or higher, you can configure the Firebox as a NetFlow exporter to gain more insights into your network traffic.

Active timer on netflow