Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.

How to configure the destination and source NAT via NSM for Junos.

The use of NSM address objects in a NAT policy can be confusing. The proper field to provide the address objects within the NAT policy varies, depending on how address objects are used on the devices.

In Junos devices, address objects can be associated with a security zone (zone based) or they can be global. When zone based address objects are defined in Junos, global address objects cannot be used or defined. When global address objects are defined in Junos, zone based address objects cannot be used or defined.

So, when applying an address object to a NAT Policy, you must be careful to apply it in the proper field. Note, in the following image, the highlighted Src fields:



If the Junos device uses zone based addressing, then the addresses that are to be used in the NAT policies must be provided in the Src Address field. If the Junos device uses global addressing, then the addresses to be used in NAT policies must be provided in the Src Address Name field.

2020-10-20: Tagged article for EOL/EOE.