I am considering the SRX series and perhaps for J series for a quite large MPLS deployment and this flow stuff is a pet peeve of mine. From what I can see, all it means is that a box that used to do rather well is now limited by the number of flows it can handle and the ludicrous memory requirements of something that is not used.
I'll be mentioning this in our requirements report for any equipment we order for this project. -- Leigh Porter -----Original Message----- From: Shane Short [mailto:[email protected]] Sent: 21 July 2010 08:32 To: Leigh Porter Cc: Jay Hanke; Christopher E. Brown; [email protected] Subject: Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases. I don't suppose this trick works on the SRX as well? *grin* -Shane On 21/07/2010, at 2:54 PM, Leigh Porter wrote: > > I thought that as soon as you turn MPLS on the flow mode was diabled and you were back to good old packet mode? > > -- > Leigh > > > -----Original Message----- > From: [email protected] on behalf of Jay Hanke > Sent: Tue 7/20/2010 11:26 PM > To: 'Christopher E. Brown'; [email protected] > Subject: Re: [j-nsp] J series users bitten by the massive memory useincrease 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: [email protected] > [mailto:[email protected]] On Behalf Of Christopher E. > Brown > Sent: Tuesday, July 20, 2010 5:15 PM > To: [email protected] > 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 [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
