nanog mailing list archives
Re: Sflow billing or usage calculation software
From: Yang Yu <yang.yu.list () gmail com>
Date: Tue, 16 Apr 2019 03:30:17 -0700
On Tue, Apr 16, 2019 at 2:14 AM Nick Morrison <nick () 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
Current thread:
- Sflow billing or usage calculation software Tony C (Apr 13)
- RE: Sflow billing or usage calculation software Ryan Hamel (Apr 13)
- Re: Sflow billing or usage calculation software Peter Phaal (Apr 13)
- Re: Sflow billing or usage calculation software Tom Beecher (Apr 13)
- RE: Sflow billing or usage calculation software Tony C (Apr 14)
- Re: Sflow billing or usage calculation software Nick Morrison (Apr 14)
- RE: Sflow billing or usage calculation software Deepak Jain (Apr 15)
- Re: Sflow billing or usage calculation software Nick Morrison (Apr 16)
- Re: Sflow billing or usage calculation software Yang Yu (Apr 16)
- Re: Sflow billing or usage calculation software Deepak Jain (Apr 16)
- Re: Sflow billing or usage calculation software Peter Phaal (Apr 17)
- Re: Sflow billing or usage calculation software Tom Beecher (Apr 13)