--- Begin Message ---
We end up backfilling the ASN data in with pmacct - you can hook it up
to a BGP full table, and it'll readd the source/dest ASN based on that.
On 10/21/2020 12:08 PM, Gerald wrote:
Coming from Foundry/Brocade we have still an sFlow monitoring in
production. Our new MX204s do support sFlow but it seems that not all
attributes are present within the exported flows. For instance we do
miss the "BGP (Source|Destination) ASN" value. Is this a general
limitation in the Junos sFlow implementation or is it configurable in
any way?
--
Gerald
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
--- End Message ---
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
