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

Updated output for show route table—The output for show route table bgp.evpn.0 now displays L2 service TLV type. Previously, the output displayed the L3 service TLV. PR1694780

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 hash will override any other hash options that may be used to determine the source port value.PR1705726

New options for the request system snapshot command (ACX Series, EX Series, MX Series, PTX 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).]PR1663189

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

PTP configuration might not function correctly on an MX10008 Router with JNP10K-LC2101 Line card: - when Hypermode is enabled. Hypermode can be enabled by default when MX10008 Router has Switch Fabric Board 2 (SFB2), or by using the command set forwarding-options hyper mode. Hence, such PTP interfaces (slave, master, stateful) are unsupported. If an aggregated Ethernet (AE) interface is configured and either the primary or secondary links on the AE do not support PTP with Hypermode, then the whole AE is marked as unsupported. PR1698964

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

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.PR1703957

Multicast debug information added in EVPN options to request system information command (MX Series, QFX Series)—The output from CLI command request support information evpn-vxlan now includes additional information to help debug EVPN multicast issues.

[See request support information.]PR1707139

Change the output of the show arp command to display IP addresses and hostnames (MX Series routers)—You can force the show arp command output to display the IP address next to the hostname of each device. To do this, enable the force-show-arp-resolve statement at the [edit system services subscriber-management overrides] hierarchy level. This makes it easier to manage subscriber access if your subscriber configuration relies on the IP addresses of the devices.

[See overrides (Enhanced Subscriber Management) and Configuring Junos OS Enhanced Subscriber Management.]PR1708347

Increased maximum limit for TTP TLVs (MX Series)—The Junos Kernel now accommodates an increased number of TTP TLVs (TNP Tunneling Protocol: type, length, and value messages) to help avoid dropped packets.

[See show system statistics.]PR1709159

Prior to this change the output of a show task replication | display xml validate 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. PR1711008

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-system" root tag and no validation error occurs. PR1711014

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

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

Increased range and maximum range for revert-time—We increased the range for revert-time from 600 to 3600 seconds and the maximum range from 1200 to 7200 seconds.

[See revert-time.]PR1702660

Change in display of affinity constraints to hexadecimal values (MX10004, ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10004, PTX10008, and PTX10016)-Starting in Junos OS release 22.4R1 and Junos Evolved Release 22.4R1, in the output of the show ted spring-te-policy extensive operational command, the affinity constraints will be displayed in hexadecimal format instead of decimal.

[See show ted spring-te-policy extensive]PR1689877

operator login class is restricted from viewing NETCONF trace files that are no-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 the no-world-readable statement (the default), users assigned to the operator 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)—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.]

XML tag in the get-system-yang-packages RPC reply changed (ACX Series, EX Series, MX 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.

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

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, 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.

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

Deprecating options related to certificate enrollment (Junos)—Starting in Junos OS Release 23.2R1, we’re deprecating earlier CLI options related to Public Key Infrastructure (PKI) to enroll and reenroll local certificate through Simple Certificate Enrolment Protocol (SCEP). The table below shows the Junos CLI commands and configuration statements with the options being deprecated. You can find the same CLI options now available under scep option in these commands and statements.

[See auto-re-enrollment (Security), request security pki local-certificate enroll scep, and request security pki node-local local-certificate enroll.]

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].PR1690014

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".PR1712358

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.]PR1719797