Committing A Configuration; Verifying A Configuration Before Committing It; Chapter 6 Committing A Configuration - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

CHAPTER 6

Committing a Configuration

Verifying a Configuration Before Committing It

Copyright © 2010, Juniper Networks, Inc.
This chapter explains how to commit a configuration so that it becomes the active
configuration on the routing, switching, or security platform. For more detailed information
about commit operations, including a discussion of the interaction among different
variants of the operation, see the Junos CLI User Guide.
Verifying a Configuration Before Committing It on page 133
Committing the Candidate Configuration on page 134
Committing a Private Copy of the Configuration on page 135
Committing a Configuration at a Specified Time on page 136
Committing the Candidate Configuration Only After Confirmation on page 137
Committing and Synchronizing a Configuration on Redundant Control Planes on page 140
Logging a Message About a Commit Operation on page 145
During the process of committing the candidate configuration or a private copy, the Junos
XML protocol server confirms that it is syntactically correct. If the syntax check fails, the
server does not commit the candidate. To avoid the potential complications of such a
failure, it often makes sense to confirm the candidate's correctness before actually
committing it. The client application encloses the empty
<commit-configuration> and
<rpc>
<commit-configuration>
<check/>
</commit-configuration>
</rpc>
The Junos XML protocol server encloses its response in
and tag elements. If the syntax check succeeds, the
<routing-engine>
tag element encloses the
which reports the name of the Routing Engine on which the check succeeded (
routing platforms that use a single Routing Engine, and either
platforms that can have two Routing Engines):
<rpc-reply xmlns:junos="URL">
<commit-results>
<routing-engine>
<name>(re0 | re1)</name>
<rpc> tag elements:
<commit-check-success/>
tag in
<check/>
<rpc-reply> , <commit-results>
<routing-engine>
tag and the tag element,
<name>
re0
or on routing
re0 re1
,
on
133