From f2a77846208cbbb5b6afe43f15312b2ef64b17f8 Mon Sep 17 00:00:00 2001 From: Nataliia Solomko Date: Tue, 13 Oct 2026 13:49:55 +0300 Subject: vpp: T9312: sFlow is supported on physical interfaces only --- docs/vpp/configuration/sflow.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/vpp/configuration/sflow.md b/docs/vpp/configuration/sflow.md index 042cf8a8..b5ba40dd 100644 --- a/docs/vpp/configuration/sflow.md +++ b/docs/vpp/configuration/sflow.md @@ -30,6 +30,18 @@ monitor. This is done using the following commands: This will enable sFlow on the specified interface. You can repeat this command for each interface you want to monitor. +:::{note} +sFlow can only be enabled on physical interfaces that are bound to +VPP with `set vpp settings interface `. VPP samples traffic on +the physical port, so logical interfaces, such as bonding, loopback +and tunnels (GRE, VXLAN, IPIP), are not supported and produce no +samples. + +To monitor traffic on a bonding interface, enable sFlow on its +physical member interfaces instead. A physical interface can be a +bonding member and an sFlow target at the same time. +::: + :::{note} sFlow collects statistics only for traffic *received* on the interface. If you want to monitor traffic *sent* on the interface, -- cgit v1.2.3