Ben, Nobody is forcing the jseries to become firewalls. They did alter the default behavior of the packet handling to be flow mode..but you can configure that.
To enable "packet mode" junos. Just issue the following commands. delete security set security forwarding-options family mpls mode packet-based set security forwarding-options family iso mode packet-based set security forwarding-options family inet6 mode packet-based This works on an SRX to turn it into a packet based device just the same as it does for a jseries. In regards to the flash size, I honestly can't speak to that. Maybe buy a couple of larger flash disks in bulk? Otherwise clean up the file system, load the code from sftp/ftp/tftp and upgrade with no-copy. That way you don't have to transfer it locally. Hope this helps, -Tim Eberhard On Mon, Nov 7, 2011 at 8:18 AM, R. Benjamin Kessler <ben.kess...@zenetra.com> wrote: > Hello All - > > We have a client with a lot of J-Series routers running 9.3 code or earlier. > We really like the features and functionality of JUNOS as a router and are > more than a little annoyed that Juniper seems to be forcing us to turn these > routers into firewalls. > > What are others doing to deal with the "flow" issues associated with more > recent versions of code? > > Also, many of these routers have "small" CF cards (e.g. 256MB or 512MB) which > will also cause issues with more modern versions of code. > > I'm interested in knowing how others have tackled these challenges for > customers with hundreds of these in the field. > > Thanks, > > Ben > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp