[j-nsp] J series users bitten by the massive memory use increase with flow mode add, please file jtac cases.

[Heath Jones]

Chris - Is the current situation: that Juniper have said there is no
workaround / configuration change that can be made to stop the allocation of
memory for the flow forwarding information?



On 20 July 2010 23:14, Christopher E. Brown <chris.brown at acsalaska.net>wrote:

>
>
> I know alot of us here have been bitten by this, and the fact that
> disabling flow mode and
> reverting to packet does not free up any of the ~ 460MB or so being eaten
> by fwdd/flowd is
> insane.
>
>
> I am currently having the "This is a design feature, the pre-alloc is
> planned" argument
> with a SE.
>
>
> I have no issue with flow features being added, looks great for branch
> office use.
>
>
> What is killing be is that flow is not wanted, needed or usable in a
> small-infra use with
> multipath and MPLS services, but even disabled flowd is eating half the box
> memory.
>
>
> 52% memory usable at bootup (bare config) is not sane, and a 1GB 6350 used
> to be able to
> handle a few thousand igp routed plus a full table with easy and lots of
> headroom, now it
> is at 92%....
>
>
>
>
> I am pushing this w/ account team and support case, please do the same.  If
> enough people
> complain about the insane resource consumption they might actually fix it.
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>