Mailing List Archive

MX204 sFlow and BGP attributes
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
Re: MX204 sFlow and BGP attributes [ In reply to ]
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: MX204 sFlow and BGP attributes [ In reply to ]
Am 21.10.20 um 20:12 schrieb Brian Rak:
> 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.

Thank you for the confirmation Brian, that means the MX itself is really
limited in that way.

--
Gerald
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: MX204 sFlow and BGP attributes [ In reply to ]
On 22 Oct 2020, at 10:19 EAT, Gerald wrote:

> Am 21.10.20 um 20:12 schrieb Brian Rak:
>> 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.
>
> Thank you for the confirmation Brian, that means the MX itself is
> really limited in that way.

Any reason you’re not using j-flow instead? It should be supported
inline and include source/dest ASN (if the router has BGP sessions).

https://www.juniper.net/documentation/en_US/junos/topics/concept/inline-sampling-overview.html


--
patrick
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: MX204 sFlow and BGP attributes [ In reply to ]
Am 22.10.20 um 11:14 schrieb Patrick Okui:
> Any reason you’re not using j-flow instead? It should be supported
> inline and include source/dest ASN (if the router has BGP sessions).
>
> https://www.juniper.net/documentation/en_US/junos/topics/concept/inline-sampling-overview.html

Because currently we are still using sFlow-only monitoring software. We
will probably went to other flow tools in the future but I had the
little hope that we could enable sFlow BGP attributes on the MX in any
way without changing our flow monitoring in advance.

--
Gerald
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: MX204 sFlow and BGP attributes [ In reply to ]
On 22 Oct 2020, at 12:35 EAT, Gerald wrote:

> Am 22.10.20 um 11:14 schrieb Patrick Okui:
>> Any reason you’re not using j-flow instead? It should be supported
>> inline and include source/dest ASN (if the router has BGP sessions).
>>
>> https://www.juniper.net/documentation/en_US/junos/topics/concept/inline-sampling-overview.html
>
> Because currently we are still using sFlow-only monitoring software.
> We will probably went to other flow tools in the future but I had the
> little hope that we could enable sFlow BGP attributes on the MX in any
> way without changing our flow monitoring in advance.

ACK.

I’ve always felt Juniper’s implementation of sFLOW was targeted
towards bridging so you mostly get attributes a switch would be
interested in.


--
patrick
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp