[mailto:ctr...@es.net]
Sent: Thursday, July 15, 2010 7:55 PM
To: bit gossip
Cc: Peter Krupl; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] MS-DPC and netflow.
Peter, Luca,
I believe you need to be running 9.6 or later in order to use the config that
Luca provided below.
Prior to 9.6, you will only
: Chris Tracy [mailto:ctr...@es.net]
Sent: Thursday, July 15, 2010 7:55 PM
To: bit gossip
Cc: Peter Krupl; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] MS-DPC and netflow.
Peter, Luca,
I believe you need to be running 9.6 or later in order to use the config that
Luca provided below
Hi Peter,
On Fri, Jul 16, 2010 at 08:01:34AM +0200, Peter Krupl wrote:
2.
As my box is running as PE, I think the mpls-ipv4 template is the one to use,
am I correct ?
It depends what you are trying to do with the NetFlow export; if
you are a SP and are sampling public internet traffic
Hi guys,
Im at a complete loss regarding this issue. And the documentation at J is
a bad mess of RE based flow sampling, and M series stuff mixed with
MX/MS-DPC stuff.
1 .Do I need to prep the MS-DPC more than ? :
aggregated-devices {
ethernet {
device-count 1;
}
}
fpc 1 {
Hi Peter,
this should be working
Thanks,
Luca.
forwarding-options {
sampling {
input {
rate 1;
run-length 0;
}
family inet {
output {
flow-server 1.1.1.66 {
port ;
Peter, Luca,
I believe you need to be running 9.6 or later in order to use the config that
Luca provided below.
Prior to 9.6, you will only find 'input', 'output' and 'traceoptions' under
forwarding-options { sampling { ... } }. After 9.6, you will find 'family
inet' and 'family inet6' under
6 matches
Mail list logo
