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

[Jay Hanke]

Ditto, I was writing basically the same email when I saw your post come
through. I got a set of 2350's out of the box running 60% memory
utilization, I added a l3 vpn (with 3 routes) and the nice green bar in the
web interface changed colors on me.

Thanks,

Jay

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Christopher E.
Brown
Sent: Tuesday, July 20, 2010 5:15 PM
To: juniper-nsp at punk.nether.net
Subject: [j-nsp] J series users bitten by the massive memory use increase
with flow mode add, please file jtac cases.



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