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.

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

OpenConfig container names for Point-to-Multipoint per interface ingress and egress sensors are modified for consistency from "signalling" to "signaling".PR1653962

Junos IPv6 flowspec implements certain constraints from RFC8956—The Junos IPv6 flowspec implementation now follows certain constraints present in the more recent RFC8956. This change updates the IPv6 flowspec implementation to enforce additional match conditions for ICMPv6 type and ICMPv6 code components. Also, ensures that packets are correctly matched and counted only if the upper-layer protocol value is 58 (ICMPv6) and that the system can locate the transport header. Earlier, when installing an IPv6 firewall filter using BGP flowspec, the matching traffic counters display zero values because the traffic isn't counted correctly.PR1656342

Prior to this change when route sharding is configured the output of CLI show route commands included information about sharding. After the change the use must add the "rib-sharding all" argument to CLI show route commands to display sharding information.

Instance type change is not permitted from default to L3VRF in open configuration (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—DEFAULT_INSTANCE is the primary instance that runs when there is no specific instance type configured in the route set routing-options ?. Any instance you explicitly configure is translated into set routing-instance r1 routing-options ?. The issue appears in translation, when you change instance type DEFAULT_INSTANCE (any instance to DEFAULT_INSTANCE) to L3VRF or L3VRF to DEFAULT_INSTANCE. As a result, such changes are not permitted. Additionally, DEFAULT_INSTANCE can only be named DEFAULT, and DEFAULT is reserved for DEFAULT_INSTANCE, therefore allowing no such changes.

In order to monitor vmhost storage usage, a new minor alarm, VMHost RE 0 Disk 1 inode usage breached threshold is introduced. The existing minor alarm, VMHost RE 0 Disk 1 Usage is above threshold and is changed to VMHost RE 0 Disk 1 size usage breached threshold.PR1680682

sFlow configuration—sFlow configuration is allowed only on et, xe, and ge interfaces in EVO-based platforms. All other interfaces are blocked for configuring sFlow on EVO platforms. A cli error will be thrown if sFlow is configured on any other interface other than et, xe or ge interface.PR1681044

Qualification check for "ordered-by-user"—Review to check and confirm if hierarchies qualify for "ordered-by-user" list type. Once show policy-options prefix-list is initiated by the user, the hierarchies appear in the order updated by the user. This enhancement organizes the hierarchies in ascending order. PR1685527

Incorrect Metric Value for Policy Multipath Routes—Junos OS and Junos OS Evolved correctly report metric 2 values for BGP routes configured with policy-multipath. When the active prefix for the route is SR TE and undergoing resolution, the system accurately reflects the metric 2 value in the route metrics. This modification ensures that routing decisions are based on accurate metrics, improving overall network performance and reliability.

[See policy-multipath.]PR1686297

Prior to this change when route sharding is configured the output of CLI show route commands included information about sharding. After the change the use must add the rib-sharding all argument to CLI show route command to display sharding information.PR1687038

Removed "and-quit" CLI option from "commit prepare" for configure exclusive and configure private modes (All-Junos, All Evo)—Starting in Junos OS Release 22.3R1, we have removed and-quit CLI option from commit prepare for configure exclusive and configure private modes. By removing the and-quit option, users will now be prevented from losing any changes made in these two configuration modes after exiting. To commit changes after a commit prepare, apply commit activate.PR1689995

Local Address Configuration Enhancement—If you configure the local-address option under bfd-liveness-detection is now ignored for single-hop BFD sessions, the configuration is ignored and a syslog warning is generated. The local-address option is intended only for multi-hop BFD sessions.

[See bfd-liveness-detection (Routing Options Static Route).]PR1858398

Operational Script Pagination Handling—The default behavior for handling operational output has been modified to prevent pagination. All output from operational scripts will now display continuous lines without being interrupted by pagination according to the CLI screen-length settings. This ensures that user prompts and outputs are visible in sequence, enhancing user experience.PR1648417

The file copy command supports only text-formatted output in the CLI (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The file copy command does not emit output when the operation is successful and supports only text-formatted output when an error occurs. The file copy command does not support using the | display xml filter or the | display json filter to display command output in XML or JSON format in any release. We've removed these options from the CLI.PR1698820

Display flexible algorithm information for SRv6 locators in TED database-Use the show ted database extensive command to view the metric, flags, and flexible algorithm information associated with a SRv6 locator. Prior to this release, this information was not included in the TED database.

[See show ted database.]

Enhancement to the jnxRmonAlarmState (ACX Series, EX Series, MX Series, NFX Series, PTX Series, QFX Series, SRX Series)—You can now view the following additional values for the jnxRmonAlarmState when you use the show snmp mib walk jnxRmonAlarmTable: fallingThreshold (6) - If the value is less than or equal to falling-threshold risingThreshold (5) - If the value is greater than or equal to rising-threshold getFailure (7)- If the value is any value other than noError for the current internal 'get' request In earlier releases, you could view only the following status for the jnxRmonAlarmState: unknown (1), underCreation (2), or active (3).

Junos YANG modules for RPCs include the junos:command extension statement (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The Junos YANG modules that define RPCs for operational mode commands include the junos:command extension statement in schemas emitted with extensions. The statement defines the CLI command for the corresponding RPC. The Juniper yang GitHub repository stores the RPC schemas with extensions in the rpc-with-extensions directory for the given release and device family. Additionally, when you configure the emit-extensions statement at the [edit system services netconf yang-modules] hierarchy level and generate the YANG schemas on the local device, the YANG modules for RPCs include the junos:command extension statement.

Enhanced bandwidth and burst policer value (MX Series and EX9200 Series)--We've updated the default bandwidth value from 20000 to 100 pps and burst policer value from 20000 to 100 packets. This enhancement avoids the CPU usage of eventd and snmpd reaching more than 100 percent. Earlier to this release, when the system receives a violated traffic for SNMP along with other protocols traffic, the CPU usage of eventd and snmpd was reaching more than 100 percent with an error.

[See show ddos-protection protocols parameters.]

Starting Junos Evolved release 22.3R1, support is provided to limit Network Time Protocol (NTP) configuration to one address family (inet vs inet6). You can configure one source-address per inet and inet6 family for each routing-instance in NTP. For example, the following configuration is valid: set system ntp source-address 2620:149:1d06:100::1set system ntp source-address 10.10.10.100

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 {https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/family-edit-protocols-bgp-route-target-vp.html} family route-target].PR1690014

Changes to the JSON encoding of configuration data for YANG leaf nodes of type identityref (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—If a YANG leaf node is type identityref, Junos devices emit the namespace-qualified form of the identity in the JSON encoding of that node. In addition, Junos devices accept both the simple (no namespace) and the namespace-qualified form of an identity in JSON configuration data. In earlier releases, Junos devices only emit and accept the simple form of an identity. Emitting and accepting the namespace-qualified identity ensures that the device can properly resolve the value in the event that the YANG data model defines an identity and a leaf node containing the identifyref value in different modules.

The file copy command supports only text-formatted output in the CLI (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The file copy command does not emit output when the operation is successful and supports only text-formatted output when an error occurs. The file copy command does not support using the | display xml filter or the | display json filter to display command output in XML or JSON format in any release. We've removed these options from the CLI.

Persistent CLI timestamps—To have a persistent CLI timestamp for the user currently logged in, enable the set cli timestamp operational command. This ensures the timestamp shows persistently for each new line of each SSH session for the user or class until the configuration is removed.

To enable timestamp for a particular class with permissions and format for different users, configure the following statements: set system login class class name permissions permissions, set system login class class name cli timestamp , and set system login user username class class name authentication plain-text-password.

To enable timestamp for a particular user with default class permissions and format, configure the following statements: set system login user username class class name authentication plain-text-password and set system login user username cli timestamp. PR1748113

Restoration of ATM VPN NLRI and BGP NLRI update—We have restored the ATM VPN NLRI to its original enum value and introduced a new NLRI value for the BGP Multicast address family. This change may impact In-Service software upgrades (ISSU) if both ATM VPN and BGP Multicast address families are configured.

[See Restore ATMVPN address family NLRI and use a new NLRI value for BGP Multicast NLRI.]PR1674843