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.

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.

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.

Modified show ancp subscriber details output fields (MX Series)—As the access loop encapsulation is transport independent it can be either passive optical network (PON) or DSL TLV. Hence, the show ancp subscriber details output field should not tag the details as a DSL TLV. Therefore, we've modified the existing DSL Line Data Link, DSL Line Encapsulation, and DSL Line Encapsulation Payload output fields to the following respectively:

• Access Loop Encapsulation Data Link
• Access Loop Encapsulation Encapsulation1
• Access Loop Encapsulation Encapsulation2

[See show ancp subscriber.]

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

For Access Gateway Function (AGF) statistics, consistency changes are implemented for specific leaf values in telemetry data to match field values in Junos CLI operational mode commands. AGF NG Application Protocol (NGAP) data streamed to a collector and viewable from the Junos CLI now displays "ngap-amf-stats-init-ctx-setup-failure" and Access and Mobility Function (AMF) overload state now displays "On, Off".

Router advertisement module status on backup Routing Engine (MX Series)–The router advertisement module does not function in the backup Routing Engine as the Routing Engine does not send an acknowledgment message after receiving the packets. Starting in this Junos OS Release, you can view the router advertisement module information using the show ipv6 router-advertisement operational command.

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 <codeph>set routing-options?<codeph>. 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.

Support for DDoS (MX10008)–We've enabled the DDoS protocol support at the [edit system ddos-protection] hierarchy level for MX10008 devices. In earlier releases, the MX10008 devices did not support these DDoS protocol statements.

• Filter-action

• Virtual-chassis

• Ttl

• Redirect

• Re-services

• Re-services-v6

• Rejectv6

• L2pt

• Syslog

• Vxlan

[See protocols (DDoS).]

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 is changed to VMHost RE 0 Disk 1 Size usage breached threshold.

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.

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.

The traffic rate could display incorrect values in the "show services inline ip-reassembly statistics fpc x pfe-slot y" output.

CSPF LSP resignaling uses new instance ID (MX480)–A Constrained Shortest Path First (CSPF) LSP uses a new instance ID when attempting to resignal an LSP that is down. In earlier releases, the CSPF LSPs that went down were stuck in CSPF path computation stage. You had to manually clear the affected LSPs and recompute the paths for the LSPs to be up again.

[See LSP Computation.]

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

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

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 https://github.com/Juniper/yang 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

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 <codeph>set cli timestamp</codeph> 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 <variable>class name</variable> permissions <variable>permissions</variable> set system login class <variable>class name</variable> cli timestamp set system login user username class <variable>class name</variable> authentication plain-text-password Note: The default timestamp format is %b %d %T. You can modify the format per your requirements. For example, you can configure the following statement:set system login class <variable>class name</variable> cli timestamp format "%T %b %d To enable timestamp for a particular user with default class permissions and format, configure the following statements:set system login user username class <variable>class name</variable> authentication plain-text-password set system login user <variable>username</variable> cli timestamp