Skip to main content

Flow-BGP-NextHop

Counts traffic per BGP next-hop router, using the BGP next-hop address in each NetFlow v9/IPFIX record.

PropertyValue
GUID{FC61EC07-BED0-4734-C64C-F5932FD8B943}
LayerFlow Record
InputFlows
Key typeIPv4 address
ImplementationLua — nf-bgp-next-hop.lua (trisul_probe/sysplugs/flowhandlers); updated by CPINetflowMeter (PINetflowMeter.cpp)
Bucket / Topper60 s / 300 s
Enabled by defaultYes

What it measures​

  • Each NetFlow v9 or IPFIX record adds its byte count to the key for BGP_IPV4_NEXT_HOP (field 18). One record updates one key.
  • NetFlow v1/v5 and sFlow do not update this group.
  • IPv6 BGP next hop (field 63) is not decoded. IPv6 flows, and v9/IPFIX templates without field 18, count against 00.00.00.00.
  • MeterBGPNextHop (default TRUE) in the NetFlow config turns it on or off. IPDR mode turns it off.

Keys​

The key is the next-hop IPv4 address in dotted uppercase hex. The group's ResolverCounterGUID is Hosts, so the UI shows the same name (DNS or user label) that Hosts has for that IP.

KeyMeaning
CB.00.71.01Next hop 203.0.113.1
C6.33.64.07Next hop 198.51.100.7
00.00.00.00No BGP next hop in the record

Special keys​

KeyMeaning
SYS:GROUP_TOTALSSum of every update made to this group in the interval. One key per record, so this equals total v9/IPFIX flow traffic.
00.00.00.00Template lacks field 18, the flow is IPv6, or the router has no BGP route (locally connected or IGP-only destination).

Meter list​

IDNameTypeUnitsTopBottomDescription
0TotalVT_RATE_COUNTERBps100Sampling-adjusted bytes of v9/IPFIX records with this BGP next hop.
1Unused Cardinality counterVT_GAUGEUniques2020Reserved cardinality slot. Not populated.
2Unused Cardinality counterVT_GAUGEUniques2020Reserved cardinality slot. Not populated.