NetFlow Analyzer is based on Cisco NetFlow protocol versions 5 and 9, but it also supports IPFIX, NSEL and sFlow v5. The system is capable of recognizing protocol formats from other vendors, which are compatible with NetFlow 5 and 9 such as Juniper J-Flow and Huawei NetStream.

The following table offers a comparison between different protocols NetVizura supports.

It can help you decide which protocol to use according to your needs, if your device supports more than one, and provide understanding of limitations brought by each protocol.

sFlow requires extensive sampling to be applied and to completely understand its advantages and disadvantages you should read article Full vs. Sampled Export.

DatasetNetFlow v5NetFlow v9IPFIXNSELsFlow v5 (info)Comment

Flows(tick)(tick)(tick)(tick)(error)For sFlow, due to NetVizura licensing, number of flows is shown as the same as the number of packets.
Metrics (L2-7)

Interface (in/out)(tick)(tick)(tick)(tick)(tick)
VLAN (in/out)(tick)(tick)(tick)(tick)(tick)
Next hop(tick)(tick)(tick)(tick)(tick)
QoS (prioritity)(tick)(tick)(tick)(tick)(tick)
Protocol (UDP/TCP/ICMP...)(tick)(tick)(tick)(tick)(tick)
TCP flags(tick)(tick)(tick)(tick)(tick)
Port (service)(tick)(tick)(tick)(tick)(tick)Provided only by TCP and UDP protocols.
IPv4 address (src/dst)(tick)(tick)(tick)(tick)(tick)
IPv6 address (src/dst)(error)(tick)(tick)(tick)(error)In general, End User traffic from IPv6 addresses is not supported
AS (src/dst)(plus)(plus)(plus)(error)(error)To provide AS data, exporter device must have a full BGP table configured.
Delivery schemes

Export options

Ingress(tick)(tick)(tick)(error)(tick)For NSEL, because export is configured on exporter, not its interfaces, ingress and egress options are not possible.

NetVizura supports both compact and expanded sFlow formats.


(tick) Provides by default
(plus) Requires additional configuration
(error) Cannot provide

Here you may find information about which protocols are supported on your devices Supported Devices List.

  • No labels