Yes, basically switched the definitions. But it makes more sense...dont
need to specify the input family as you already do that by applying the
filter on the interface you want to sample which then carries
v4/v6/whatever.
So its only needed for output as you can then split your flow's to
various c
Bizarre. So you define the family type you want to sample by
specifying it as the family type on the output stanza? (Seems
backwards?)
On Thu, Aug 18, 2011 at 3:51 PM, Jonas Frey (Probe Networks)
wrote:
> Matt,
>
> yes the config changed in JunOS 10.x.
>
> See below:
>
> --- OLD ---
> sampling {
Woops,
forgot something. Input also changed and should be now:
sampling {
input {
rate 100;
}
(no longer using family...)
Am Freitag, den 19.08.2011, 00:51 +0200 schrieb Jonas Frey (Probe
Networks):
> Matt,
>
> yes the config changed in JunOS 10.x.
>
> See below:
>
> --- OLD
Matt,
yes the config changed in JunOS 10.x.
See below:
--- OLD ---
sampling {
input {
family inet {
rate 100;
}
}
output {
flow-server A.B.C.D {
port 2055;
version 5;
}
}
--- NEW ---
sampling {
input {
Thanks to Jeff Richmond and Jonas Frey who were kind enough to provide
guidance both on and off-list.
This is what I ended up with:
[edit interfaces xe-0/0/0 unit 0 family inet filter]
+ input-list [ sample-cflow accept-da accept-bgp accept-icmp
discard-all ];
[edit forwarding-options]
+
Hello Matt,
i am not too familar with peakflow but you should get it working with
the following:
router# show forwarding-options
sampling {
input {
family inet {
rate 100;
}
}
output {
cflowd A.B.C.D {
port 2055;
version 5;
Hello --
I've recently deployed some MX960 (Treo) and now need to get their
flow data in Arbor Peakflow SP. Unfortunately the instructions in the
Arbor manual appear to be very long in the tooth and a bit confusing.
Specifically, the integration directions are for a "JunOS version
5.5B1.3 on a Jun
7 matches
Mail list logo
