Chapter 8
NETCONF XML Elements
RUGGEDCOM NETCONF
Reference Guide
126
<close-session/>
Section 8.2
<close-session/>
Description:
Requests the graceful termination of a NETCONF session.
When a NETCONF server receives a <close-session> request, it does the following:
• gracefully closes the session
• releases any locks and resources associated with the session
• gracefully closes any associated connections
• ignores any NETCONF requests received after the <close-session> request
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:
Using <close-session/> to close a NETCONF session:
<rpc>
<close-session/>
</rpc>
]]>]]>
Section 8.3
<commit>
Description:
Commits the changes made to the candidate configuration, applying the changes to the device's currently running
configuration.
Commits can be immediate, or can require confirmation:
• To commit the changes immediately, issue an empty <commit/> tag: the changes immediately apply to the
currently running configuration.
• To require confirmation of the changes, issue the <confirmed/> tag within the <commit/> tag: the changes
appear in the currently running configuration, but are rolled back if they are not confirmed within a timeout
period. The default timeout period is 10 minutes. To specify a different timeout period, use the <confirm-
timeout> tag within the <commit/> tag. To confirm the commit before the timeout period expires, issue an
empty <commit/> tag.
Parameters:
<confirmed/> : requires the commit to be confirmed within a configurable timeout period. If a timeout period is
not specified with the optional <confirm-timeout> tag, the default period is 10 minutes. To confirm the commit
within the timeout period, issue an empty <commit/> tag.
<confirm-timeout> : specifies the timeout period, in minutes, during which you can confirm a commit. If
the commit is not confirmed within the timeout period, the configuration rolls back to the previously active
configuration.
Example:
To commit changes immediately:
<rpc>
<commit/>
</rpc>
]]>]]>
To commit changes and require a commit confirmation with the default timeout period:
<rpc>
<commit/><confirmed/></commit>
</rpc>
]]>]]>
To commit changes and require a commit confirmation within a 30 minute timeout period:
Summary of Contents for RUGGEDCOM MX5000RE
Page 8: ...Table of Contents RUGGEDCOM NETCONF Reference Guide viii ...
Page 12: ...Preface RUGGEDCOM NETCONF Reference Guide xii Customer Support ...
Page 26: ...Chapter 1 Introduction RUGGEDCOM NETCONF Reference Guide 14 Sample Session Editing Data ...
Page 40: ...Chapter 3 NETCONF Sessions RUGGEDCOM NETCONF Reference Guide 28 Killing a Session ...
Page 64: ...Chapter 5 Changing Configuration Data RUGGEDCOM NETCONF Reference Guide 52 Committing Changes ...
Page 148: ...Chapter 8 NETCONF XML Elements RUGGEDCOM NETCONF Reference Guide 136 validate ...
