Inline NAT can be used on MPC's if you are looking for basic forms of NAT like Source and destination NAT. Inline NAT only supports 1:1 static mapping.
If you want to deploy NAPT then need MS-DPC or MS-PIC Br, Amarjeet > > Message: 1 > Date: Wed, 30 Sep 2015 08:13:36 +0200 > From: Mark Tinka <[email protected]> > To: Josh Hoppes <[email protected]>, Aaron <[email protected]> > Cc: Juniper List <[email protected]> > Subject: Re: [j-nsp] nat / cg nat / vrf aware nat (pe nat) > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > > > On 30/Sep/15 00:17, Josh Hoppes wrote: > > > For CG-NAT you're likely going to be looking at the MS-MIC or MS-MPC > > in an MX and a license for the function. The smaller MX (MX80 and > > MX104) can use the MS-MIC if you're looking for something with a > > smaller footprint. I'm not certain of any limitations as I've not > > deployed it. > > To add, the community has been accustomed to running NAT on Cisco > routers for decades, and so it can come as a surprise when certain > hardware built for a specific purpose from Cisco does not have NAT > supported, as there are fewer and fewer software-based routers targeted > at the service provider market from Cisco nowadays. > > Juniper have always supported their features in hardware from Day One > (until, of course, the J-series routers). So as with the Cisco of today, > you will need an MS-MIC or MS-DPC to run NAT on a Juniper MX platform > (or the equivalent MS-PIC/AS-PIC for the older M- and T-series routers). > > I'm not an SRX user, but I suppose NAT should be inherently supported in > there as well. > > Mark. > > > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
