On Mon, Mar 5, 2012 at 3:28 PM, TCIS List Acct <[email protected]>wrote:
> Over the past few years the general feeling I've gotten reading j-nsp and > elsewhere was to stay away from the SRX line until the code matured. We've > got an upcoming project that I'm considering using a SRX 240 for. > > Has the code matured to the point that it can be considered a stable > platform for security (just basic firewall, 1:1 NATs, maybe a few VPNs), > high availability, and some very basic layer 3 routing services? > > TIA. > > --Mike > ______________________________**_________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp> > I have many SRXs, from 100's, to 1400's, and things in between. There are still some gotchas, but I would say they are very mature. On my branch units, I run 10.4R6.5, and on the highend units I run 11.1R3.5 Have not have any stability issues, they are quick, a pleasure to configure, and reliable. I wouldn't go back to ASAs ever at this point either -- Brent Jones [email protected] _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
