Indicate that the NETCONF server has experienced an error while processing the client application’s request. If the server has already emitted the response tag element for the current request, the information enclosed in that response tag element might be incomplete. The client application must include code that discards or retains the information, as appropriate. The child tag elements described in the Contents section detail the nature of the error. The NETCONF server does not necessarily emit all child tag elements; it omits tag elements that are not relevant to the current request.
Starting in Junos OS Release 17.4R3, 18.2R2, 18.3R2, and
18.4R1, when you configure the rfc-compliant statement
at the [edit system services netconf] hierarchy level to
enforce certain behaviors by the NETCONF server, the NETCONF server
cannot return an RPC reply that includes both an
<rpc-error> element and an
<ok/> element. If the
operation is successful, but the server reply would include one or
<rpc-error> elements with a severity
level of warning in addition to the
<ok/> element, then the warnings are omitted.
<error-message>—Describes the error or warning in a natural-language text string.
<error-path>—Specifies the path to the Junos OS configuration hierarchy level at which the error or warning occurred, in the form of the CLI configuration mode banner.
<error-severity>—Indicates the severity of the event that caused the NETCONF server to return the
<rpc-error>tag element. The two possible values are
tag element is described separately.