Export Panorama by hand
Upload Panorama's own configuration as a management model.
On this page
Export the configuration
In the web interface: Panorama > Setup > Operations > Export named Panorama configuration snapshot, and choose running-config.xml. From the CLI:
set cli pager off
set cli config-output-format xml
show config runningSave the CLI output as one .txt file, with the show config running line directly above the XML and only plain text around it.
Add the serial with show system info
After the upload is parsed, paste the output of this command in Verify Panorama identity (optional). The hostname must match the file.
show system infoWhat the upload is read for
- Device groups and their hierarchy, shared objects and policy, pre-rulebase and post-rulebase.
- Templates, template stacks in their member order, and variables.
- The firewall serials Panorama lists under its managed devices.
- From the pasted
show system info: serial, model and the full software version.
A Panorama export is a management-model analysis. It is not the effective configuration of a managed firewall: export that firewall with the PAN-OS guide.
Through the Relay
| Reading | Command |
|---|---|
| Serial, model and version | show system info |
| Licenses | request license info |
Upload
Open New analysis
Choose File upload and select the file, or choose Paste, paste the output and select Upload and parse.
It is sent at once
One file per upload. ConfigProof reads the vendor and export type from the content, not the file name, then asks the client, project and name. If your role is limited to certain clients, choose the client first.
Answer the picker if asked
A file that holds several VDOMs, contexts, virtual systems or gateways opens a picker. Each one you choose is its own analysis.
Operational CLI commands
The Panorama configuration contains NAT and security rules. Collect active routes, neighbors and VPN state on the managed firewall.
show system info
show devices all
show devicegroups
show templatesReport evidence and rule hit counts
Panorama. Available sources across collection methods
Hit counters without a supported source: security, nat, decryption, pbf, qos, dos, tunnel inspection, application override, authentication, sdwan, network packet broker.
- Supported checks
- VPN and NAT, Remote access, Lifecycle dates, Recommended release, Rule dependencies
- Checks not yet supported
- HA state, Change attribution, Pending changes, Configuration history
- Outside this device’s role
- Active routes, Route decisions, CDP / LLDP, Tunnel, BGP and interface state, Reachability