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

Unlocking the Candidate Configuration

As long as a client application holds a lock on the candidate configuration, other applications and users cannot change the candidate. To unlock the candidate configuration, the client application includes the <unlock> and <target> tag elements and the <candidate/> tag in an <rpc> tag element:



<rpc>
    
<unlock> 

        
<target> 

            
<candidate/> 

        
</target> 

    
</unlock> 

</rpc>
]]>]]>

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



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

If the NETCONF server cannot unlock the configuration, the <rpc-reply> tag element instead encloses an <rpc-error> tag element explaining the reason for the failure.

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