Overview of Configuration Changes

To change configuration information, the client application performs the procedures described in the indicated sections:

1. Establishes a connection to the NETCONF server on the C Series Controller, as described in Connecting to the NETCONF Server.
2. Opens a NETCONF session, as described in Starting the NETCONF Session.
3. (Optional) Locks the candidate configuration, as described inLocking the Candidate Configuration. Locking the configuration prevents other users or applications from changing it at the same time.
4. Encloses the <edit-config> and <target> tag elements and the <candidate/> tag in an <rpc> tag element. By including various child tag elements, the application can provide the configuration data either in a file or as a directly loaded tag stream, and can completely replace the existing configuration or specify the manner in which the NETCONF server loads the data into the existing candidate or copy. See Changing the Candidate Configuration.
5. Accepts the tag stream emitted by the NETCONF server in response to each request and extracts its content, as described in Parsing the NETCONF Server Response.
6. (Optional) Verifies the syntactic correctness of a configuration before attempting to commit it, as described in Verifying a Configuration Before Committing It.
7. Commits changes made to the configuration, as described in Committing Configurations.
8. Unlocks the candidate configuration if it is locked, as described in Unlocking the Candidate Configuration. Other users or applications cannot change the configuration while it remains locked.
9. Ends the NETCONF session and closes the connection to the C Series Controller, as described in Ending a NETCONF Session and Closing the Connection.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.