Changes in Behavior and Syntax
This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands from Junos OS Release 17.2R2 for the EX Series.
Support for deletion of static routes when the BFD session goes down (EX Series)—Starting with Junos OS 17.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session down message.
Deprecated no-path-mtu-discovery configuration option for ipip6 tunnels—Starting in Junos OS Release 17.2R1, the no-path-mtu-discovery configuration statement in the [edit interfaces ip-fpc/pic/port unit logical-unit-number tunnel] and [edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel] hierarchies is no longer available for ipip6 tunnels.
Changes to the rfc-compliant configuration statement (EX Series)—Starting in Junos OS Release 17.2R1, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. If you configure the
rfc-compliantstatement at the [edit system services netconf] hierarchy level and request configuration data in a NETCONF session on a device running Junos OS Release 17.2R1 or later, the NETCONF server sets the default namespace for the
<configuration>element in the RPC reply to the same namespace as in the corresponding YANG model.
Junos OS YANG module namespace and prefix changes (EX Series)—Starting in Junos OS Release 17.2R1, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each
juniper-commandmodule uses its own unique module name as the module’s prefix. In earlier releases, Junos OS YANG modules used only a unique identifier to differentiate the namespace for each module, and the prefix for all
Device families include
junos-qfx. The Junos OS YANG extension modules,
junos-extension-odl, use the
junosdevice family identifier in the namespace, but the modules are common to all device families.