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

Locking the Configuration

The client application then prepares to incorporate a change into the candidate configuration by emitting the <lock> tag to prevent any other users or applications from altering the candidate configuration at the same time. To confirm that the candidate configuration is locked, the NETCONF server returns an <ok/> tag in an <rpc-reply> tag element. For more information about locking the configuration, see Locking the Candidate Configuration.

Client Application	NETCONF Server
<rpc> <lock> <target> <candidate/> </target> </lock> </rpc> ]]>]]>
	<rpc-reply xmlns=”URN” xmlns:sdx=”URL” > <ok/> </rpc-reply> ]]>]]>

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