Starting in Junos Space Security Director Release 16.2, you can migrate firewall and NAT policies from Network and Security Manager (NSM) to Security Director for a set of devices. All objects supported by Security Director (addresses, services, address groups, service groups, and schedulers) can be imported with the policy, with the exception of polymorphic objects. Rules referring to unsupported objects are disabled after the migration. For example, if a firewall policy rule is configured with the VPN tunnel or if a NAT pool is configured with a routing instance, such rules are disabled after the migration.
At any time, only a single migration from the NSM workflow can be triggered on Security Director. Figure 149 shows the device import workflow.
Figure 149: High-Level Device Import Workflow
You can migrate policies from the NSM database (for the NSM Release 2010.3 to Release 2012.2) into Security Director.
The following NSM features are supported during the migration:
Note: NSM to Security Director migration is not supported for ScreenOS devices.
Before You Begin
Migrating policies from NSM requires the NSM database to be exported in .xdiff format. You must copy this file to your local machine and provide its path to migrate policies from NSM to Security Director.
To import policies from NSM:
The Migration From NSM page appears.
The NSM Migration page appears.
The Devices page appears showing the name of the available devices, the IP address of each device, the Junos OS version of each device, the platform, the device family, and the domain.
The Managed Services summary page appears. This page provides the following information.
The Conflict Resolution page appears showing a list of conflicts, if any. An object conflict occurs when the name of the object to be imported matches an existing object, but the definition of the object does not match.
Conflicting objects can be IP addresses, services, or NAT pool objects. You can take the following actions for the conflicting objects:
Once the initial naming conflict has been resolved, the object conflict resolution checks for further conflicts with the new name and definition until resolution is complete.
Note: If Security Director finds further conflicts, the Conflict Resolution page is refreshed to display the new conflicts.
After the import is complete, a comprehensive report for each policy imported is available. You can download the summary report from your browser to your local machine. The summary report is saved as SummaryReport.zip.
Note:
© 2018 Juniper Networks, Inc. All rights reserved