Hi Keith,
Adjusting the size of the flow hash table will reboot the FPC.
In 14.2 and previous, you have everything (15) for IPv4 and only a few entries
for IPv6 and VPLS (0). Each unit is 256K flows (except for 0).
Starting from 15.1R, all flow tables have a default size of "0" (that is, a
mini-minimum of space, 1024 flows), so in 15.1+, fixing the sizing of the
flow-tables is more or less mandatory.
This is the kind of generic config we use here to avoid an FPC reboot, would we
need some unplanned stuff with inline-jflow (that you may adjust according to
your needs, would you have plenty of IPv6 flows...). You have 15 units of 256K
to spend.
groups {
chassis-fpc-netflow {
chassis {
fpc <*> {
sampling-instance sample-1;
inline-services {
flow-table-size {
ipv4-flow-table-size 12;
ipv6-flow-table-size 2;
vpls-flow-table-size 1;
ipv6-extended-attrib;
}
}
}
}
}
}
chassis {
fpc 0 {
apply-groups chassis-fpc-netflow;
}
}
Olivier
> On 3 nov. 2016 at 23:43, Keith <kwo...@citywest.ca> wrote :
>
> One thing about inline that Juniper config docs say is about the flow-table
> size. I had someone
> tell me enabling inline jflow will cause the fpc to reboot, but from what I
> read adjusting the size
> of the flow hash table will cause that.
>
> Any idea what is correct here? I would think that just enabling it would not
> cause an FPC to restart.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
