Hi,
Extreme also supports it, and we use it for conducting statistics against
dst_as/dst_peer_as to perform "traffic engineering" specifically for the
transit paths. dst_as_path can also identify possible future peering situations
or undesirable paths.
BR
Jörg
On 4 Apr 2023, at 16:48, Peter P
On 4 Apr 2023, at 21:48, Peter Phaal
mailto:peter.ph...@gmail.com>> wrote:
Export of destination AS-Path is supported in the sFlow extended_gateway
structure.
As a consumer of sFlow, [as well as NetFlow, IPFIX, etc.] I haven’t run into
the use of this option in production, FWIW.
In addition
Export of destination AS-Path is supported in the sFlow extended_gateway
structure.
/* Extended Gateway Data */
/* opaque = flow_data; enterprise = 0; format = 1003 */
struct extended_gateway {
next_hop nexthop; /* Address of the border router that should
* na...@ics-il.net (Mike Hammett) [Tue 04 Apr 2023, 15:06 CEST]:
1) How common is it to have the additional extensions to include
that data for analysis?
pmacct is a commonly used tool to enrich flow data with such
information.
-- Niels.
On 4 Apr 2023, at 20:04, Mike Hammett
mailto:na...@ics-il.net>> wrote:
2) I have seen flow tools that show the entire AS path. Are they just cherry
picking which platforms they showcase for the best marketing, or are they
enriching the data they receive from "lesser" platforms from an outside
One of the reasons to analyze flow data is to make purchase\peering decisions.
The sFlow standard seems to only include source and destination AS, though I
know some route platforms have extensions to provide additional data.
1) How common is it to have the additional extensions to include tha
6 matches
Mail list logo
