What's Changed
Learn about what changed in this release for EX Series switches.
Network Management and Monitoring
-
operator
login class is restricted from viewing NETCONF trace files that areno-world-readable
(ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—When you configure NETCONF tracing options at the[edit system services netconf traceoptions]
hierarchy level and you restrict file access to the file owner by setting or omitting theno-world-readable
statement (the default), users assigned to theoperator
login class do not have permissions to view the trace file. -
Support for the
junos:cli-feature
YANG extension (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Thecli-feature
YANG extension identifies certain CLI properties associated with some command options and configuration statements. The Junos YANG modules that define the configuration or RPCs include thecli-feature
extension statement, where appropriate, in schemas emitted with extensions. This extension is beneficial when a client consumes YANG data models, but for certain workflows, the client needs to generate CLI-based tools. -
XML tag in the
get-system-yang-packages
RPC reply changed (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Theget-system-yang-packages
RPC reply replaces thexmlproxy-yang-modules
tag with theproxy-xml-yang-modules
tag in the XML output. -
Changes to the NETCONF server's
<rpc-error>
element when theoperation="delete"
operation deletes a nonexistent configuration object (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—We've changed the<rpc-error>
response that the NETCONF server returns when the<edit-config>
or<load-configuration>
operation usesoperation="delete"
to delete a configuration element that is absent in the target configuration. The error severity is error instead of warning, and the<rpc-error>
element includes the<error-tag>data-missing</error-tag>
and<error-type>application</error-type>
elements.