Rpc-Reply - Siemens RX1400 Reference Manual

RUGGEDCOM NETCONF
Reference Guide
Example: An <rpc-error> in response to an <rpc> request:
Section 8.16
<rpc-reply>
Description: Contains the results of an <rpc> request. The <rpc-reply> may contain returned data, the <ok/> element indicating
Examples: An <rpc-reply> message containing data from the NETCONF server:
<rpc-reply>
<error-message> : shows a human-readable error message describing the error condition. This element does not
appear if no error message is available for the error condition.
<error-info> : shows protocol or data-model error content. This element does not appear if no error content is
available for the error condition.
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="103">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-path xmlns:rmf_admin="http://ruggedcom.com/ns/rmf_admin">
/rmf_admin:admin/rmf_admin:authentication
</error-path>
<error-message xml:lang="en">/admin/authentication: admin/timezone must be
set</error-message>
<error-info>
<bad-element>authentication</bad-element>
</error-info>
</rpc-error>
</rpc-reply>
]]>]]>
the successful completion of an operation request, or error information.
The user-id attribute contains the user-id string sent with the <rpc> request. The user-id attribute helps to
map the <rpc-reply> to the original <rpc> message.
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interface xmlns="http://ruggedcom.com/ns/rmf_if">
<modem>
<slot>lm2</slot>
<port>1</port>
</modem>
<wan>
<slot>lm5</slot>
<port>1</port>
</wan>
<eth>
<slot>lm3</slot>
<port>1</port>
</eth>
</interface>
</data>
</rpc-reply>]]>]]>
An <rpc-reply> message indicating the successful completion of a request:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="103">
<ok/>
</rpc-reply>]]>]]>
An <rpc-reply> message containing error information:
Chapter 8
NETCONF XML Elements
133