| Where Can I Use This? | What Do I Need? |
|---|
| NGFW (Managed by PAN-OS or Panorama) |
|
Any change in the Palo Alto Networks device configuration is first written to the
candidate configuration. The change only takes effect on the device when you commit
it. Committing a configuration applies the change to the running configuration,
which is the configuration that the device actively uses. Upon commit, the device
performs both a syntactic validation (of configuration syntax) and a semantic
validation (whether the configuration is complete and makes sense). As a best
practice, validate configuration changes prior to committing
so that you can fix any errors that will cause a commit failure, thereby ensuring
that the commit will succeed. This is particularly useful in environments with a
strict change window.
The firewall and Panorama queue commit operations so that you can initiate a new
commit while a previous commit is in progress. The firewall and Panorama perform
commits in the order you and other administrators initiate them but prioritize
automatic commits such as content database installations and FQDN refreshes. If the
queue already has the maximum number of administrator-initiated commits (this varies
by appliance model), the firewall or Panorama must begin processing a commit (remove
it from the queue) before you can initiate a new commit.
To see details (such as queue positions or Job-IDs) about commits that are
pending, in progress, completed, or failed, run the operational command
show jobs all. To see the messages and description
for a particular commit, run show jobs id
<job-id>.
