Network Address Translation (NAT)

Inline NAT support (MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 23.1R1, you need a license to use the inline NAT feature on the listed devices. The inline NAT feature is part of the Premium tier of licenses.

[See Flex Software License for MX Series Routers and MPC Service Cards.]

Source NAT port overload (MX240, MX480, and MX960 devices with MX-SPC3)—Starting in Junos OS Release 23.1R1, we support port overloading with and without enhanced port overloading hash algorithm. MX-SPC3 with port-overloading supports:

• Maximum number of IP Address = 2048 per NPU.

• Maximum port-overloading factor value = 32.

We’ve updated the hash algorithm to determine the port-overloading index for a destination address. The hash algorithm uses the reverse traffic from the server, matches the existing sessions, and reuses the same Network Address Translation (NAT) resources. To configure enhanced algorithm, it is mandatory to have port-loading.

You can configure the updated hash algorithm using the enhanced-port-overloading-algorithm statement at the [services nat source pool pool-name port] hierarchy level. Enhanced port overloading algorithm provides better utilization of port overloading.

[See pool (Source NAT Next Gen Services).]

CGNAT services on MX-SPC3 (MX240, MX480, and MX960 with MPC10)—Starting with Junos OS Release 23.1R1 CGNAT services support is added in MPC10 for access side subscribers.

[See Junos OS Enhanced Subscriber Management Overview.]

AMS support for load balancing on MX-SPC3 (MX240, MX480, and MX960 with MPC10 )—Starting in Junos OS Release 23.1R1, we support load balancing using the new CLI option modulo-key in the set interfaces ams0 unit 1 load-balancing-options command.

[See Configuring Load Balancing on AMS Infrastructure.]