What's Changed

Flow-label configuration status for EVPN ELAN services]--The output for the show evpn instance extensive command now displays the flow-label and flow-label-static operational status for a device and not for the routing instances. A device with flow-label enabled supports flow-aware transport (FAT) flow labels and advertises its support to its neighbors. A device with flow-label-static enabled supports FAT flow labels but does not advertise its capabilities.PR1690033

New enhancement "udp source port" introduced in Junos OS Release 22.4R1 for overlay ping and traceroute—In Junos OS releases prior to 22.4R1, you could not configure the udp source port in a ping overlay or traceroute overlay operation. You may now configure this value in an EVPN-VXLAN environment using hash. The configuration option hashwill override any other hash-* options that may be used to determine the source port value. PR1705726

The connectivity fault management process (cfmd) runs only when the ethernet connectivity-fault-management protocol is configured.

Prior to this change the output of a show task replication | display xml validate command returned an error of the form ERROR: Duplicate data element <task-protocol-replication-name>. With this change the XML output is properly structured with no validation errors.

Label for the hours unit of time displayed in output—When there are zero minutes in the output for the show system uptime command, the label for the hours unit of time is displayed.

[See show system uptime.]

In the past inet6flow.0 was not allowed to be a primary rib in a rib-group. Starting with Release 22.3 this is now allowed.

Changes to Aggregate Level Policer at FPC (EX9208)—The summation of newly added sub-policers HELLO and UNCLS for DDOS protocols OSPF, OSPFv3, and RSVP result in the correct reporting of counters at the FPC level, for e.g. packet drops. Earlier, you could configure the OSPF, OSPFv3, and RSVP aggregate policer at the FPC level directly.

You can use the following CLI statements to configure the burst and bandwidth values for OSPF, OSPFv3, and RSVP:

• set system ddos-protection protocols ospf ospf-hello burst size bandwidth packets-per-second

• set system ddos-protection protocols ospf ospf-uncls burst 10000 bandwidth 10000

• set system ddos-protection protocols ospfv3v6 ospfv3v6-hello burst 10000 bandwidth 10000

• set system ddos-protection protocols ospfv3v6 ospfv3v6-uncls burst 10000 bandwidth 10000

• set system ddos-protection protocols rsvp rsvp-hello burst 10000 bandwidth 10000

• set system ddos-protection protocols rsvp rsvp-uncls burst 10000 bandwidth 10000

[See Protocols (DDOS).]

The active-user-count is defined as a numeric integer value in ODL request output—The output for the get-system-uptime-information ODL request contains information for the active-user-count. The active-user-count is now defined as a numeric integer value and avoids an invalid value type error.

[See show system uptime.]

The packet rate and byte rate fields for LSP sensors on AFT (with the legacy path) have been renamed as jnx-packet-rate and jnx-byte-rate and is in parity with the UKERN behavior. Previously, these rate fields were named as packetRate and byteRate.

When subscribing to the resource path /junos/system/linecard/environment, the prefix for the streamed path at the collector side was displaying as /junos/linecard/environment. This issue is resolved in Junos OS 23.1R1 and Junos OS Evolved 23.1R1 and the subscription path and the streamed path match to display /junos/system/linecard/environment.PR1690570

Advertise inactive local RIB paths in BMP—We have introduced a new configuration statement bmp-loc-rib-add-path at the [edit routing-options bmp] hierarchy level.

[See bmp-loc-rib-add-path.]PR1697520

The Ethernet link fault management process (lfmd) runs only when the link-fault-management protocol is configured. PR1698132

Previously, if the system failed to install an interface or hierarchical policer, the PFE crashed due to an assert. Now, the system installs a firewall discard and logs a DFW_HALP_ERR_MSG_POLICER_ADD_FAILED error message. This error message provides the name of the affected policer and the corresponding error code. Relevant policers appear under the interface > unit > family > policer input/output (or) interface > unit > family > input-hierarchical-policer stanzas. PR1701676

Before this change the output of a show task replication logical-system all | display xml validate command reported an error. After the change the output is correctly formatted with a logical-systemcodeph> root tag and no validation error occurs. PR1711014

Label for the hours unit of time displayed in output—When there are zero minutes in the output for the show system uptime command, the label for the hours unit of time is displayed.

[See show system uptime.]PR1715255

The shared-tunnels statement is not supported on EX9204, EX9208, EX9214, EX9251, EX9253, MX304, MX10001, MX10002, MX960, MX480, MX240, MX2020, MX2010, MX2008, and vMX devices.PR1716955

Two new alarms are added and can be seen with MPC11E when 400G-ZR optics are used. High Power Optics Too Warm: warning of the increase in chassis ambient temperature with no functional action taken on the optics Temperature too high for optics power on: New inserted optics when the chassis ambient temperature is elevated beyond the threshold will not be powered on and would need to be reinserted when the ambient temperature is within the acceptable range. PR1719569

You can specify the minimum and maximum value for the hold-time down and hold-time up interval between 0 through 3600000 milliseconds at the [edit protocols network-isolation group group-name detection] hierarchy level. PR1726039

Support for podman-based JDM deployment--Starting in Junos OS Release 23.2R1, the external server-based Junos node slicing supports deployment of Juniper Device Manager (JDM) using the Pod Manager tool (podman). This change is applicable to servers running Red Hat Enterprise Linux (RHEL) 9. In Junos releases prior to 23.2R1, Junos node slicing supported RHEL 7.3 that provided libvirts lxc driver (libvirt-lxc) to deploy JDMs. PR1737550

An optics configuration mismatch alarm may be triggered when there is a discrepancy between the configured speed of an interface and the supported speed of the optic. This alarm indicates that the optic installed in the specified FPC is incompatible with the speed configured on the interface.

Ability to commit extension-service file configuration when application file is unavailable—When you set the optional option at the [edit system extension extension-service application file file-name] hierarchy level, the operating system can commit the configuration even if the file is not available at the <filepath>/var/db/scripts/jet</filepath> file path.

[See file (JET).]

Ability to restart restart daemonized applications—Use the request extension-service restart-daemonize-app application-name command to restart a daemonized application running on a Junos device. Restarting the application can assist you with debugging and troubleshooting.

[See request extension-service restart-daemonize-app.]

The xmlns:junos attribute includes the complete software version string (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—The xmlns:junos namespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by the show version command. In earlier releases, the xmlns:junos string includes only partial software version information.

Changes to the show system yang package (get-system-yang-packages RPC) XML output (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—The show system yang package command and <get-system-yang-packages> RPC include the following changes to the XML output:

• The root element is yang-package-information instead of yang-pkgs-info.

• A yang-package element encloses each set of package files.

• The yang-pkg-id tag is renamed to package-id.

• If the package does not contain translation scripts, the Translation Script(s) (trans-scripts) value is none.

NETCONF server's <rpc-error> response changed when <load-configuration> uses operation="delete" to delete a nonexistent configuration object (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—In an earlier release, we changed the NETCONF server's <rpc-error> response for when an <edit-config> or <load-configuration> operation uses operation="delete" to delete a configuration element that is absent in the target configuration. We've reverted the changes to the <load-configuration> response.

Changes to the RPC response for <validate> operations in RFC-compliant NETCONF sessions (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—When you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level, 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.

XML tag in the get-system-yang-packages RPC reply changed (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The get-system-yang-packages RPC reply replaces the xmlproxy-yang-modules tag with the proxy-xml-yang-modules tag in the XML output.PR1701858

operator login class is restricted from viewing NETCONF trace files that are no-world-readable (ACX Series, EX Series, MX Series, PTX 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 the no-world-readable statement (the default), users assigned to the operator login class do not have permissions to view the trace file.PR1707820

Support for the junos:cli-feature YANG extension (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The cli-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 the cli-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.

[See Understanding the Junos DDL Extensions YANG Module.]PR1713424

Event Data Model Enhancement for Syslog Priority--The event data model has been enhanced to include the priority parameter in the syslog event logs. This update corrects the calculation and representation of syslog priority. Previously, the syslog priority was incorrectly calculated leading to errors in syslog message handling.

Changes to the NETCONF server's <rpc-error> element when the operation="delete" operation deletes a nonexistent configuration object (ACX Series, EX Series, MX Series, PTX 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 uses operation="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.

NETCONF server's <rpc-error> response changed when <load-configuration> uses operation="delete" to delete a nonexistent configuration object (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)--In an earlier release, we changed the NETCONF server's <rpc-error> response for when an <edit-config> or <load-configuration> operation uses operation="delete" to delete a configuration element that is absent in the target configuration. We've reverted the changes to the <load-configuration> response.

The ping host | display xml validate command validates XML without error (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, and vMX)—In Junos OS and Junos OS Evolved releases prior to 22.4R2, the ping host | display xml validate command results in CRITICAL ERROR: Root tag name mismatch. Expected 'ping-results', got 'run-command'. The command now validates the XML successfully without error.

[See ping.]PR1694765

Prior to this change, devices by default responded only to ARP requests originating from the same subnet. Configure the new CLI option, "respond-out-of-subnet" at the [edit system arp] hierarchy level to allow ARP reply to a request that originates from a different subnet. PR1710699

Addition of nexthop-resolution no-resolution option for Route Target constrains (RTC) family--The nexthop-resolution no-resolution configuration option has been added to the family route-target in BGP configurations. This addition allows users to disable nexthop-resolution for RTC family (AFI 1, SAFI 132) routes, and consider them usable for filtering of VPN-routes without depending on the RTC route's nexthop reachability.

[See family route-target.]

Prior to this change the output of the show isis statistics interface interface_name | display xml command used the XML tag "interface-name", which generated an error. With the change the XML output uses the tag "isis-interface-name".

TI-LFA and Legacy LFA Configuration Commit Validation Update (Junos OS and Junos OS Evolved)-You can now enable TI-LFA and legacy FRR (node-link-protection) in separate OSPF instances. The system generates a commit error only if you enable both TI-LFA and legacy FRR under the same OSPF instance. In that case, the commit fails and triggers the following message: error: commit failed: (statements constraint check failed).

[See Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS and OSPF..]

BGP Multipath route calculation--When configuring multipath in the routing-instance, BGP routes that are inactive due to cluster-list length are also considered as eligible for multipath calculations. This enhances route selection by including more potential paths in your multipath configuration.

[See Understanding BGP Path Selection.]

New options for the request system snapshot command (ACX Series, EX Series, MX Series, QFX Series, and SRX Series)—The request system snapshot command includes new options for non-recovery snapshots. You can include the name option to specify a user-defined name for the snapshot, and you can include the configuration or no-configuration option to include or exclude configuration files in the snapshot. By default, the snapshot saves the configuration files, which include the contents of the /config and /var directories and certain SSH files.

[See request system snapshot (Junos OS with Upgraded FreeBSD).]

The xmlns:junos attribute includes the complete software version string (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX and vSRX)—The xmlns:junos namespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by the show version command. In earlier releases, the xmlns:junos string includes only partial software version information.PR1696560

Port Mirroring Configuration Update—Interface ranges are no longer supported as part of configuration groups for creating analysers. If you attempt to use an interface-range in a config group, you will encounter an error indicating an invalid interface type. Additionally, interface ranges or interface lists cannot be configured under this setting. This change ensures precise and error-free configuration by requiring the specification of individual interfaces rather than ranges, thus improving the accuracy and reliability of port mirroring setups.PR1728883

Enhancement to MVPN Sender Site Configuration—MVPN (Multicast Virtual Private Network) sender sites configured with an IR (Ingress Replication) tunnel send Type 1 routes with label 0. This means that remote PEs do not add the Type 1 route as a leaf of the tunnel but will still add the sender site PE as MVPN neighbor. This ensures that traffic from the sender site PE is not dropped by the remote PEs due to unknown MVPN neighbor. But since the sender site PE sends the label as 0, remote PEs will not add the sender site PE as a leaf and traffic from the remote PE will not be replicated to this PE ensuring sender site functionality.PR1711769