Clone Configuration
Table of Contents
10.0 (EoL)
Expand all | Collapse all
-
- Upgrade a Firewall to the Latest PAN-OS Version (API)
- Show and Manage GlobalProtect Users (API)
- Query a Firewall from Panorama (API)
- Upgrade PAN-OS on Multiple HA Firewalls through Panorama (API)
- Automatically Check for and Install Content Updates (API)
- Enforce Policy using External Dynamic Lists and AutoFocus Artifacts (API)
- Configure SAML 2.0 Authentication (API)
- Quarantine Compromised Devices (API)
- Manage Certificates (API)
-
- Asynchronous and Synchronous Requests to the PAN-OS XML API
- Run Operational Mode Commands (API)
- Apply User-ID Mapping and Populate Dynamic Groups (API)
- Get Version Info (API)
-
- PAN-OS REST API
- Access the PAN-OS REST API
- Resource Methods and Query Parameters (REST API)
- PAN-OS REST API Request and Response Structure
- PAN-OS REST API Error Codes
- Work With Objects (REST API)
- Create a Security Policy Rule (REST API)
- Work with Policy Rules on Panorama (REST API)
- Create a Tag (REST API)
- Configure a Security Zone (REST API)
- Configure an SD-WAN Interface (REST API)
- Create an SD-WAN Policy Pre Rule (REST API)
- Configure an Ethernet Interface (REST API)
- Update a Virtual Router (REST API)
- Work With Decryption (APIs)
End-of-Life (EoL)
Clone Configuration
Use action=clone to
clone an existing configuration object. Use the xpath parameter
to specify the location of the object to be cloned. Use the from parameter
to specify the source object, and the newname parameter
to provide a name for the cloned object.
- Use the following API query to clone a security
policy called rule1 to rule2:curl -X GET "https://<firewall>/api/?key=apikey&type=config&action=clone&xpath=/config/devices/entry/vsys/entry[@name='vsys1']/rulebase/security/rules&from=/config/devices/entry/vsys/entry[@name='vsys1']/rulebase/security/rules/entry[@name='rule1']&newname=rule2"
- Confirm that the XML response for the request looks like the following:
<response status="success" name="rule2"/>A corresponding success log is recorded in the Configuration log:1,2014/03/19 19:07:45,0009C100708,CONFIG,0,0,2014/03/19 19:07:45,10.66.18.1,,clone,admin,Web,Succeeded, config devices entry vsys vsys1 rulebase security rules,384,0x8000000000000000 - Confirm that the XML response for the request looks like the following: