Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 141 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 8
NETCONF XML Elements
<get-config> 129
<bad-attribute>message-id</bad-attribute>
<bad-element>rpc</bad-element>
</error-info>
</rpc-error>
</rpc-reply>
]]>]]>
Section 8.9
<get-config>
Description: Requests all or part of a specified configuration.
Parameters: <source> : the configuration to query: candidate or running.
<filter> : identifies the configuration segments to retrieve. The filter element contains elements describing the
configuration segment to return. For more information, see Filtering.
Response: If the NETCONF device can complete the request, it sends an <rpc-reply> document containing the <data>
element and results of the query.
If the NETCONF device cannot complete the request, it sends an <rpc-reply> document containing the <rpc-error>
element.
Example: To return configuration data from the chassis namespace:
<rpc message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter type="subtree">
<chassis xmlns="http://ruggedcom.com/ns/rmf_chassis"></chassis>
</filter>
</get-config>
</rpc>]]>]]>
Section 8.10
<hello>
Description: Lists the capabilities of the NETCONF server and client. When connecting to the device, the device sends a <hello>
message containing its NETCONF capabilities and a session-id. The client connecting to the device must also send
a <hello> message, listing at least the base NETCONF capability. The client's <hello> message must not contain a
session-id.
Parameters: <capabilities> : contains one or more <capability> elements.
<capability> : contains the uniform resource identifier (URI) for a single NETCONF capability. Standard NETCONF
capabilities appear with a universal resource name (URN). Vendor-defined NETCONF capabilities appear with
either a URN or universal resource locator (URL).
<session-id> : a session identifier returned by the NETCONF server. A NETCONF client must not return a <session-
id> element in its hello message. If the client returns a <session-id> element, the server terminates the session.
Example: A <hello> message returned from a device:
<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:capability:writable-running:1.0</capability>