[Contents] [Prev] [Next] [Index] [Report an Error]

# Committing a Configuration

To commit the candidate configuration, a client application includes the <commit/> tag in an <rpc> tag element:

`

    <rpc>
        <commit/>
    </rpc>
    ]]>]]>

`

The NETCONF server confirms that it committed the candidate configuration by returning the <ok/> tag in the <rpc-reply> tag element:

`

    <rpc-reply xmlns="URN "xmlns:sdx="URL">
        <ok/>
    </rpc-reply>
    ]]>]]>

`

If the NETCONF server cannot commit the candidate, the <rpc-reply> tag element instead encloses an <rpc-error> tag element explaining the reason for the failure. The most common causes are semantic or syntactic errors in the candidate configuration.

To avoid inadvertently committing changes made by other users or applications, a client application locks the candidate configuration before changing it and emits the <commit/> tag while the configuration is still locked. (For instructions on locking and changing the candidate configuration, see Locking the Candidate Configuration and Changing Configuration Information.) After committing the configuration, the application unlocks the candidate as described in Unlocking the Candidate Configuration.

[Contents] [Prev] [Next] [Index] [Report an Error]