Actions
Feature #16855
open
Add option to skip Nexus registration data from config.xml export.
Status:
New
Priority:
Normal
Assignee:
-
Category:
Multi-Instance Management
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Release Notes:
Default
Description
We've seen a couple tickets where importing a config into another firewall will cause it to be unable to register to a Nexus controller if both exported and imported config firewalls are trying to communicate since the Nexus data identifiers are stored in the config file.
We should put a warning on this checkbox also to use the option if using Nexus and planning to import the config into a separate firewall.
No data to display
Actions