Skip to main content

FlowIntfs

Counts traffic per router interface from NetFlow, IPFIX and sFlow records, keyed by exporter IP plus SNMP ifIndex.

PropertyValue
GUID{C0B04CA7-95FA-44EF-8475-3835F3314761}
LayerFlow Record
InputFlows
Key typeExporter IPv4 address + ifIndex
ImplementationNative C++ — CPICGNetflowIntf (trisul_probe/sysplugs/flowhandlers/PICGNetflowIntf.cpp); updated by CPINetflowMeter and CPISFlowMeter; meters 4–6 by Lua flow-interface-util.lua (same directory)
Bucket / Topper60 s / 300 s
Enabled by defaultYes

What it measures​

  • Each flow record updates two keys: the input interface (INPUT_SNMP, field 10) gets Recv, and the output interface (OUTPUT_SNMP, field 14) gets Xmit. Both keys get Total and Flows. NetFlow v5 uses the input/output ifIndex in the record. sFlow uses inputPort/outputPort and the sFlow agent address.
  • Recv is traffic that enters the router on that interface. Xmit is traffic that leaves the router on that interface.
  • Byte counts are sampling-adjusted. Records removed by the interface, host or ASN filters are not counted.
  • MeterNetflowInterfaces (default TRUE) in the NetFlow config turns this group on or off. IPDR mode turns it off.
  • At each flush, flow-interface-util.lua computes the utilization meters. It reads the interface speed from the snmp.ifspeed key attribute, or from snmp.ifspeed_rx and snmp.ifspeed_tx, in bits/s, on this group's keys. The SNMP integration stores these attributes (see Using SNMP). Without a speed, meters 4 and 5 stay empty.

Keys​

The key is <exporter IP as dotted hex>_<ifIndex as 8 hex digits>, all uppercase, 20 characters. The UI shows the readable form router_ifIndex, and you can type that form in search.

KeyMeaning
C0.A8.01.01_00000003Router 192.168.1.1, ifIndex 3 (readable 192.168.1.1_3)
CB.00.71.01_0000022CRouter 203.0.113.1, ifIndex 556
0A.00.00.FE_0000F4DCRouter 10.0.0.254, ifIndex 62684

The label is the interface name. It comes from IPFIX IF_NAME/IF_DESC (fields 82/83) in options records, from SNMP name resolution, or from a label you assign.

Special keys​

KeyMeaning
SYS:GROUP_TOTALSSum of every update made to this group in the interval. Each flow updates an input key and an output key, so Total here is about 2× the flow traffic.
<router>_00000000ifIndex 0. The exporter did not send INPUT_SNMP/OUTPUT_SNMP, or sent 0 (for example, locally originated or dropped traffic).

Meter list​

IDNameTypeUnitsTopBottomDescription
0TotalVT_RATE_COUNTERBps10000Bytes of every flow where this interface is the input or the output interface.
1RecvVT_RATE_COUNTERBps10000Bytes of flows whose input interface is this ifIndex.
2XmitVT_RATE_COUNTERBps10000Bytes of flows whose output interface is this ifIndex.
3FlowsVT_COUNTERFlw10000Flow records that touched this interface (input or output).
4Recv-UtilVT_GAUGEPct10000Recv × 8 × 100 / receive ifSpeed. Set at flush only when an ifSpeed attribute exists.
5Xmit-UtilVT_GAUGEPct10000Xmit × 8 × 100 / transmit ifSpeed. Set at flush only when an ifSpeed attribute exists.
6Recv-Xmit-RatioVT_GAUGEPct10000Recv × 100 / (Recv + Xmit). 100 means receive-only, 0 means transmit-only.
7Unused Cardinality counterVT_GAUGEUniques2020Reserved cardinality slot. Not populated.
8Unused Cardinality counterVT_GAUGEUniques2020Reserved cardinality slot. Not populated.
  • FlowGens: totals per exporter.
  • SNMP-Interface: the same interface keys, measured by SNMP polling.
  • Flow-Link-ASN: AS numbers per interface.
  • Interface Tracking creates filtered Hosts, Apps and NetworkLayerStats groups for one FlowIntfs key.
  • You can create crosskey groups with FlowIntfs, such as Flow-ASN × Interface, Country × Interface, or FlowIntfs × Hosts, Apps, Flow-ASN or NetworkLayerStats. The interface drilldown shows these as tabs.