[j-nsp] J-Flow problem

[Stefan Fouant]

Make sure you have a proper NTP source. It's not documented but
somewhere in JUNOS 9.x they started requiring NTP to be setup in order
to make sure your flows had accurate timestamps.


On 4/18/09, Stephen Fulton <sf at lists.esoteric.ca> wrote:
> Greetings,
>
> I recently upgraded a J-series 6350 from 8.4 to 9.2, and it appears that it
> is
> no longer exporting, or properly exporting, version 5 flows.  I'm at a loss,
> since the documentation on Juniper's site is simply wrong for the J-series
> --
> ie. commands listed do not exist.  Here's a redacted snippet of the
> appropriate
> sections:
>
> sf at router> show configuration forwarding-options
> sampling {
>      input {
>          family inet {
>              rate 50;
>              run-length 0;
>              max-packets-per-second 1000;
>          }
>      }
>      output {
>          cflowd 10.52.135.6 {
>              port 2055;
>              source-address 10.51.100.2;
>              version 5;
>              no-local-dump;
>              autonomous-system-type origin;
>          }
>      }
> }
>
> sf at router> show configuration interfaces ge-0/0/3 unit 5
> bandwidth 1g;
> vlan-id 5;
> family inet {
>      sampling {
>          input;
>          output;
>      }
>      address xxx.xxx.xxx.xxx/xx
> }
>
> Thoughts?
>
> -- Stephen
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>

-- 
Sent from Gmail for mobile | mobile.google.com

Stefan Fouant

Stay the patient course.
Of little worth is your ire.
The network is down.