Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Understanding the Client Application’s Role in a NETCONF Session

 

To create a session and communicate with the NETCONF server, a client application performs the following procedures, which are described in the indicated sections:

  1. Satisfies the prerequisites for an SSH connection, as described in Establishing an SSH Connection for a NETCONF Session.

  2. Establishes a connection to the NETCONF server on the routing, switching, or security platform, as described in Connecting to the NETCONF Server.

  3. Opens a NETCONF session, as described in Starting the NETCONF Session.

  4. Optionally locks the candidate configuration or opens an instance of the ephemeral configuration database.

    Locking the configuration prevents other users or applications from changing it at the same time. For more information, see Locking and Unlocking the Candidate Configuration Using NETCONF.

    For information about the ephemeral configuration database, see Understanding the Ephemeral Configuration Database and Enabling and Configuring Instances of the Ephemeral Configuration Database.

  5. Requests operational or configuration information, or changes configuration information, as described in Requesting Operational Information Using NETCONF, Requesting Configuration Data Using NETCONF, and Editing the Configuration Using NETCONF.

  6. (Optional) Verifies the syntactic correctness of the candidate configuration before attempting to commit it, as described in Verifying the Candidate Configuration Syntax Using NETCONF.

  7. Commits changes made to the candidate configuration, as described in Committing the Candidate Configuration Using NETCONF and Committing the Candidate Configuration Only After Confirmation Using NETCONF, or commits changes made to an open instance of the ephemeral configuration database, as described in Committing an Instance of the Ephemeral Configuration Database Using the NETCONF or Junos XML Protocol.

  8. Unlocks the candidate configuration if it is locked or closes an open instance of the ephemeral configuration database.

    Other users and applications cannot change the candidate configuration while it remains locked. For more information, see Locking and Unlocking the Candidate Configuration Using NETCONF.

  9. Ends the NETCONF session and closes the connection to the device, as described in Ending a NETCONF Session and Closing the Connection.