[j-nsp] Inline jflow AS Lookup Failures

[david.roy at orange.com]

Hi

12.3 runs on several mx960 with mpc4e cards since several months without any issue.

Note. We don't use NSR and we use a service release that includes some fix of bugs found during our qualification tests in lab.

For me 12.3 is a good release, but in our config.

Envoyé depuis mon Samsung Galaxy Ace d'Orange



Gabriel Blanchard <gabe at teksavvy.ca> a écrit :


Just an FYI though, we run 12.3 on MX80s and that's been fine. Anything with dual RE seems to be the problem.

On 2013-07-01, at 10:24 AM, Drew Weaver <drew.weaver at thenap.com<mailto:drew.weaver at thenap.com>>
 wrote:

Has anyone else been brave enough to try 12.3 yet to see what the damage is? =)

From: Richard Hesse [mailto:richard.hesse at weebly.com<http://weebly.com>]
Sent: Friday, June 28, 2013 5:52 PM
To: Gabriel Blanchard
Cc: Drew Weaver; juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
Subject: Re: [j-nsp] Inline jflow AS Lookup Failures

Did you report the crash to Juniper? What was it related to?

-richard

On Fri, Jun 28, 2013 at 7:02 PM, Gabriel Blanchard <gabe at teksavvy.ca<mailto:gabe at teksavvy.ca>> wrote:
I tried 12.3. Crashed within 24h

On 2013-06-28, at 2:59 PM, Drew Weaver <drew.weaver at thenap.com<mailto:drew.weaver at thenap.com>>
 wrote:

> How much of a disaster (vs 11.4) are we guessing that 12.3R3 is going to be?
>
> From: Richard Hesse [mailto:richard.hesse at weebly.com<mailto:richard.hesse at weebly.com>]
> Sent: Friday, June 28, 2013 2:58 PM
> To: Drew Weaver
> Cc: juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] Inline jflow AS Lookup Failures
>
> It's fixed in JunOS 12.3R3 and 13.2R1. It's in PR#820988, but that isn't ready for the public yet.
>
> -richard
>
> On Fri, Jun 28, 2013 at 5:08 PM, Richard Hesse <richard.hesse at weebly.com<mailto:richard.hesse at weebly.com><mailto:richard.hesse at weebly.com<mailto:richard.hesse at weebly.com>>> wrote:
> It's totally useless right now. I have a support case open with Juniper on this. I'll post back to the list if we make any headway.
>
> -richard
>
> On Fri, Jun 28, 2013 at 9:51 AM, Drew Weaver <drew.weaver at thenap.com<mailto:drew.weaver at thenap.com><mailto:drew.weaver at thenap.com<mailto:drew.weaver at thenap.com>>> wrote:
> Howdy,
>
> I am wondering if anyone has figured out any way to get inline jflow to send proper dstas/srcas on routers with full tables?
>
> I'm seeing a lot of these incrementing (snipped output):
>
> show services accounting errors inline-jflow
>    Route Record Lookup Failures: 5415, AS Lookup Failures: 15775477
> show services accounting errors inline-jflow
>    Route Record Lookup Failures: 5415, AS Lookup Failures: 15776293
> What this ends up doing in practice is sending ff ff ff ff (or 4294967295) for the ASN..
>
> Which ends up looking like:
>
> [root at d6 etc]# /usr/local/bin/nfdump -r /var/netflow/nc/nfcapd.current -s dstas/bytes 'router ip 192.168.25.7 and out if 555' -qN
> 2013-06-27 22:23:02.827 52026.907 any          4294967295      996(20.3)     2201(14.9)   420620(17.1)        0       64   191
>
> In other words, totally useless.
>
> Any tips?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net><mailto:juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>>
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/juniper-nsp


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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.