Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 146 / 148

Chapter 8
NETCONF XML Elements
RUGGEDCOM NETCONF
Reference Guide
134 <target>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="104"><rpc-
error>
<error-type>protocol</error-type>
<error-tag>lock-denied</error-tag>
<error-severity>error</error-severity>
<error-info>
<session-id>3216</session-id>
</error-info>
</rpc-error>
</rpc-reply>
]]>]]>
Section 8.17
<target>
Description: Specifies the configuration on which to perform on operation. <target> is used in the <copy-config>, <delete-
config>, <edit-config>, <lock>, and <unlock> operations.
Parameters: <candidate/> : specifies the candidate configuration.
<running/> : specifies the candidate configuration.
Response: If the NETCONF device can complete the request, it sends an <rpc-reply> document containing the <ok> element.
If the NETCONF device cannot complete the request, it sends an <rpc-reply> document containing the <rpc-error>
element.
Example: To lock the candidate configuration:
<rpc>
<lock>
<target>
<candidate/>
</target>
</lock>
</rpc>
]]>]]>
Section 8.18
<unlock>
Description: Releases the configuration lock placed by an earlier <lock> operation in the same NETCONF session. The specified
configuration must already be locked, and only the session that performed the <lock> operation can unlock the
configuration.
Parameters: <target> : the configuration to unlock: <candidate/> or <running/>
Response: If the NETCONF device can complete the request, it sends an <rpc-reply> document containing the <ok> element.
If the NETCONF device cannot complete the request, it sends an <rpc-reply> document containing the <rpc-error>
element.
Example: To unlock the running configuration:
<rpc message-id="105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>