[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

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

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:

[j-nsp] Interface link State Tracking

I have quite a lot of experience with Cisco switches and am starting to also implement Juniper switches. Cisco switches have a feature link state tracking (http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swethchl.html#wp1285238) which I

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

This is why I have 2 gb in 23xx and 4 gb in 4350s android rocks -Original Message- From: Jay Hanke [jha...@myclearwave.net] Received: 7/20/10 4:33 PM To: 'Christopher E. Brown' [chris.br...@acsalaska.net]; juniper-...@punk.nether.net [juniper-...@punk.nether.net] Subject: Re: [j-nsp] J