Hi all,
Thanks for supporting.
After the change of flow-table-size we now get to see flows on the GENIEATM
box.
result:
Received Flows/sec: 5126
Flow information
FPC Slot: 0
Flow Packets: 42833914564, Flow Bytes: 37364742189748
Active Flows: 235206, Total Flows: 1015377662
Flow
I recently did this on operational/live MX960's on my 100 gig mpls ring with
no problem. ...no service impact, no card reboots.
set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 4
I run...
agould@960> show system information
Model: mx960
Family: junos
Junos: 17.4R1-S2.2
Hos
Hi,
On 02.01.2019 13:18, sth...@nethelp.no wrote:
From 16.1R1 and up you should also configure the ip flow table sizes
as the default is 1024 entries for v4 if I'm not mistaken. Not sure if
this is your current issue but is something to consider as well. Also
check flex-flow-sizing as an option
Hi,
On 02.01.2019 11:49, Saku Ytti wrote:
Trio does IPFIX in HW, it can inspect each and every packet with no
different cost. So if your flow table can survive it, do 1:1 and get
more visibility.
AFAIK not all Trio Generations and variants are able to do 1:1 at Line Rate.
IIRC MPC5E and newer
> From 16.1R1 and up you should also configure the ip flow table sizes
> as the default is 1024 entries for v4 if I'm not mistaken. Not sure if
> this is your current issue but is something to consider as well. Also
> check flex-flow-sizing as an option.
Note that changing the flow table sizes has
>From 16.1R1 and up you should also configure the ip flow table sizes
as the default is 1024 entries for v4 if I'm not mistaken. Not sure if
this is your current issue but is something to consider as well. Also
check flex-flow-sizing as an option.
Luis
On Wed, Jan 2, 2019 at 7:51 AM A. Camci wro
> see the config:
>
> set services flow-monitoring version-ipfix template ipv4 ipv4-template
> set services flow-monitoring version-ipfix template ipv6 ipv6-template
We have a bit more, e.g.
template ipv4 {
flow-active-timeout 60;
flow-inactive-timeout 15;
On Wed, 2 Jan 2019 at 12:32, Dave Bell wrote:
> Netflow/Jflow/IPFIX does not sample packets. It samples flows. A flow is
> (could be?) made up of many packets.
Everyone probably means the same thing here, but the way you are
saying it, is very confusing to me.
Sampling means we do not look at e
you're right, but that's what I meant.
Op wo 2 jan. 2019 om 11:29 schreef Dave Bell :
> i want samples of a every 128 packets
>>
>
> Netflow/Jflow/IPFIX does not sample packets. It samples flows. A flow is
> (could be?) made up of many packets.
>
>
_
>
> i want samples of a every 128 packets
>
Netflow/Jflow/IPFIX does not sample packets. It samples flows. A flow is
(could be?) made up of many packets.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/ju
This sets a sampling rate of 128:1. Is that intentional?
yes.
i want samples of a every 128 packets
i have also tried with 100 and 512 but still same output.
Op wo 2 jan. 2019 om 11:16 schreef Dave Bell :
> set forwarding-options sampling instance inline input rate 128
>
> This sets a sampling
set forwarding-options sampling instance inline input rate 128
This sets a sampling rate of 128:1. Is that intentional?
Dave
On Wed, 2 Jan 2019 at 10:08, A. Camci wrote:
> Hi Steinar,
>
> see the config:
>
> set services flow-monitoring version-ipfix template ipv4 ipv4-template
> set services
Hi Steinar,
see the config:
set services flow-monitoring version-ipfix template ipv4 ipv4-template
set services flow-monitoring version-ipfix template ipv6 ipv6-template
set forwarding-options sampling instance inline input rate 128
set forwarding-options sampling instance inline family inet ou
> Does anyone have experience with GENIEATM ( 6.3.2 ) and Juniper MX480 MPCE
> Type 2 3D ( 16.1R4-S3.6).
> recently we use the inline-jflow monitoring.
>
> it works but we receive too little sampling.
> expect a 10k of sampling per second instead of 100 samples
We have quite a bit of experience w
Hi all,
Does anyone have experience with GENIEATM ( 6.3.2 ) and Juniper MX480 MPCE
Type 2 3D ( 16.1R4-S3.6).
recently we use the inline-jflow monitoring.
it works but we receive too little sampling.
expect a 10k of sampling per second instead of 100 samples
Border Router:
Flow information
F
15 matches
Mail list logo
