Sflow billing or usage calculation software

Yang Yu yang.yu.list at gmail.com
Tue Apr 16 10:30:17 UTC 2019


>On Tue, Apr 16, 2019 at 2:14 AM Nick Morrison <nick at nanocat.net> wrote:
>
> Actually the sflow standard is flexible, and there are many fields widely available, including input interface and output interface, vlan/vxlan/mpls headers, etc. The sending device just needs to support the fields.


Vendor support for sFlow extended data types seems to be very limited
and there are quite a few caveats on when the data is
missing/inaccurate.

RFC5472 Section 4.2 Using IPFIX for Billing (Reliability Limitations)
might be applicable to sFlow as well.
https://tools.ietf.org/html/rfc5472#section-4.2


Yang



More information about the NANOG mailing list