Viewing and Synchronizing Out-of-Band NAT Policy Changes Manually
Starting in Junos Space Security Director Release 20.1R1, when there is an out-of-band NAT policy change in the device, you can see an icon next to the corresponding policy in device-specific and group NAT policies in Security Director. You can manually synchronize the out-of-band changes for a device-specific policy, only when the automatic synchronization is disabled.
When you hover over the icon next to the policy, the tooltip indicates the out-of-band changes.
When a device is discovered in Security Director, the Managed Status is displayed as Managed in the Security Devices page. For manual synchronization of out-of-band policy changes, the managed status of the device must be SD Changed, Device Changed, or In Sync. You must update the device atleast once from Security Director. In case of logical system (LSYS) or tenant system (TSYS), root device may show the status as Device Changed if a policy is assigned to it. Update the root device so that the status is In Sync.
After you synchronize the policy changes, the policy shows that you’ll need to republish the policy. A dummy publish and update has to be performed in order to set the managed status as In sync.
The custom rule group in a policy is not supported. If the policy has a custom rule group, then the custom rule group is deleted after synchronizing the policy and all the rules are grouped inside device-specific or predefined rule groups.
Out-of-band changes are not supported if more than one policy is assigned to a device or if rules are configured in All Devices Policy Pre/Post policies.
The out-of-band changes does not support synchronization of duplicate rule-sets in a NAT policy.
Viewing Out-of-Band NAT Policy Changes
To view out-of-band NAT policy changes:
Importing Out-of-Band NAT Policy Changes Manually
To import out-of-band NAT policy changes: