Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

rfc-compliant (NETCONF)

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
rfc-compliant;

Hierarchy Level

content_copy zoom_out_map
[edit system services netconf]

Description

Require that the NETCONF server enforce certain behaviors that are compliant with RFC 4741, NETCONF Configuration Protocol, during NETCONF sessions.

When you configure the rfc-compliant statement:

  • The NETCONF server explicitly declares the NETCONF namespace in its replies and qualifies all NETCONF tags with the nc prefix.

  • <get> and <get-config> operations that return no configuration data do not include an empty <configuration> element in RPC replies.

  • On devices running Junos OS Release 17.2R1 or later, the NETCONF server sets the default namespace for the <configuration> element to the same namespace as in the corresponding YANG model.

  • On devices running Junos OS Release 17.4R3, 18.2R2, 18.3R2, and 18.4R1 or later, the NETCONF server omits <rpc-error> elements with a severity level of warning in its replies when the operation is successful and returns an <ok/> element.

  • On devices running Junos OS Release 21.2R1 or later, the NETCONF server's response to <commit> operations includes the following changes:

    • If a successful <commit> operation returns a response with one or more warnings, the warnings are redirected to the system log file, in addition to being omitted from the response.

    • The NETCONF server response emits the <source-daemon> element as a child of the <error-info> element instead of the <rpc-error> element.

    • If you also configure the flatten-commit-results statement at the [edit system services netconf] hierarchy level, the NETCONF server suppresses any <commit-results> XML subtree and only emits an <ok/> or <rpc-error> element in its response.

  • On devices running Junos OS Release 23.2R1 or later and on devices running Junos OS Evolved Release 23.4R1 or later, the NETCONF server emits only an <ok/> or <rpc-error> element in response to <validate> operations. In earlier releases, the RPC reply also includes the <commit-results> element.

Default

If you do not include the rfc-compliant statement:

  • The NETCONF server sets the default namespace to the NETCONF namespace in RPC replies.

  • <get> and <get-config> operations that return no configuration data include an empty <configuration> element in RPC replies.

  • The NETCONF server does not set the default namespace for the <configuration> element to the same namespace as in the corresponding YANG model.

  • The NETCONF server might issue an RPC reply that includes both an <rpc-error> element with a severity level of warning and an <ok/> element.

  • The NETCONF server's response to <commit> and <validate> operations might not be RFC compliant.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 15.1.

footer-navigation