Kill-Session; Lock; Section 8.11, "<Kill-Session; Section 8.12, "<Lock - Siemens RX1400 Reference Manual

RUGGEDCOM NETCONF
Reference Guide
Section 8.11
<kill-session>
Description: Terminates a specified NETCONF session, cancelling any operations in progress and releasing all locks, resources,
Parameters: <session-id> : the unique identifier for a session.
Response: If the NETCONF device can complete the request, it sends an <rpc-reply> document containing the <ok> element.
Example: To kill a session:
Section 8.12
<lock>
Description: Locks the specified configuration, preventing other NETCONF sessions and other services, such as the web
Parameters: <target> : the configuration to lock: <candidate/> or <running/>
Response: If the NETCONF device can complete the request, it sends an <rpc-reply> document containing the <ok> element.
Example: To lock the running configuration:
<kill-session>
and connections for the session.
<kill-session> does not roll back the configuration or state changes made by the configuration being terminated.
If the session being terminated is performing a confirmed commit when the <kill-session> is issued, the NETCONF
server restores the configuration to its state before the confirmed commit was issued.
To kill a session, you need to know its <session-id>. To find a session's <session-id>, attempt to <lock> or <unlock>
the session. The <session-id> is reported in the <rpc-error> message received from the unsuccessful <lock> or
<unlock> attempt.
If the NETCONF device cannot complete the request, it sends an <rpc-reply> document containing the <rpc-error>
element.
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<kill-session>
<session-id>4</session-id>
</kill-session>
</rpc>
interface and command line interface, from editing the session. Other sessions may read a locked session, but
cannot edit it.
The <lock> operation fails if the configuration is already locked by the current or another session, or if the
configuration has been modified by the current session but not yet committed.
Only the session performing the <lock> operation can unlock the configuration with the <unlock> operation. If the
session is terminated before the <unlock> operation is performed, the configuration is automatically unlocked.
If the NETCONF device cannot complete the request, it sends an <rpc-reply> document containing the <rpc-error>
element.
<rpc message-id="104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lock>
<target>
<running/>
</target>
</lock>
</rpc>
]]>]]>
Chapter 8
NETCONF XML Elements
131