In R77 we had "save policy as", which was useful in order to have multiple copies of a policy. What is the equivalent for that in R80?
April 2017 update: An standalone open-source tool exists for exporting and importing policies and objects by using the R80 or R80.10 Management API: Python tool for exporting/importing a policy package or parts of it
This tool exports a policy package as a list of csv files that can later by imported into a different management setup.
In R80 you can export a policy, but not import.
Export can be done:
Importing a layer, a policy, or an entire policy package, is planned as an API command for the next releases.
Please note that for some of the use cases, SmartConsole has alternative tools.
Please reply to this thread with your input - are these tools sufficient, or do you find other cases where need the import option? For example:
As we discussed I would like to add the answer you gave me on why we would actually export a policy file if import is not an option.
In addition I would like to record here that export options for Permission profiles and Administrators currently don't exist and a Request for Change is submitted.
What could an export give me:
Moving policies and their associated clusters would be helpful, certainly we have had need to reorganize domain cluster groupings as the organization changes over time.
I also agree with Peter - we need to be able to export permission profiles- if fact to be able to configure perm profiles via API would also be good.
We are also looking to be able to publish all changes carried out within a session to an external source for audit trail purposes - configurable per administrator
What is the best way to export a very large access layer rulebase? There seem to be a limit on the number of rules that can be exported at once? Guess I can script it and cycle through the rulebase using the offset but why the limitation or have I missed something?
Would be helpful to have some API calls to query policy stats e.g number of active\inactive access rules\rules without logging\number of NAT rules\number of policy packages etc. Most can be gather from existing API call but might be helpful just to be able to do some stats directly
Hi, the instructions for exporting a very large rulebase are the same. These commands query the rulebase multiple times by pages of 50 or 100 rules (depending the specific command), and then aggregate the results to the output file or JSON structure. Therefore, there is no limit on the number of rules that can be exported at the same time.
In the case of the API command, you can also change the page size if you find that it makes the response faster on your side. This depends on the specific Internet speed on your side and the number of objects that are selected in your rulebase. You can also specify offsets and limits. Please refer to the API documentation for more details.
Thank you for the suggestions regarding "rulebase statistics". We will add this to our roadmap plans.
Please have a look at Python tool for exporting/importing a policy package or parts of it
This tool exports a policy package as a list of csv files that can later by imported into a different management setup
Retrieving data ...