What's Changed

Change in options and generated configuration for the EZ-LAG configuration IRB subnet-address statement—With the EZ-LAG subnet-address inet or subnet-address inet6 options at the edit services evpn evpn-vxlan irb irb-instance hierarchy, you can now specify multiple IRB subnet addresses in a single statement using the list syntax addr1 addr2 ?. Also, in the generated configuration for IRB interfaces, the commit script now includes default router-advertisement statements at the edit protocols hierarchy level for that IRB interface.

[See subnet-address (Easy EVPN LAG Configuration).]

EVPN-VXLAN tracing configuration— The set services trace evpn-vxlan configuration invokes a built-in commit script to generate tracing configurations for troubleshooting EVPN-VXLAN in multiple modules and hierarchies.

[See trace (EVPN-VXLAN).]

New commit check for MAC-VRF routing instances with the encapsulate-inner-vlan statement configured —We introduced a new commit check that prevents you from configuring an IRB interface and the encapsulate-inner-vlan statement together in a MAC-VRF routing instance. Please correct or remove these configurations prior to upgrading to 23.2R2 or newer to avoid a configuration validation failure during the upgrade.

[See encapsulate-inner-vlan.]

Option to disable path MTU discovery—Path MTU discovery is enabled by default. To disable it for IPv4 traffic, you can configure the no-path-mtu-discovery statement at the edit system internet-options hierarchy level. To reenable it, use the path-mtu-discovery statement.

[See Path MTU Discovery.]

Starting in Junos OS release 23.2R1 and Junos OS Evolved release 23.2R1-EVO, the output of show chassis power command displays the state of the power supply in PTX10003 and QFX10003 platforms.

[See show chassis power

While running request system snapshot recovery command on all VMHost based Routing Engines, disable or stop reporting any warning message.

Enhanced DDoS status operational command (PTX Series)—We've enhanced the aggregate DDoS status output field to display the aggregate count of all sub packet types.

Earlier to this release, the aggregate DDoS status output displayed only the packet type level output information.

[See show ddos-protection protocols.]

On PTX10004, PTX10008, and PTX10016 routers, after executing the request node offline command, you must wait at least 180 seconds to execute the request chassis cb offline command.

Enhanced DDoS statistics operational command (PTX Series)—We've enhanced the aggregate DDoS statistics output field to display the aggregate statistics for BFD and DHCP protocols. The enhanced DHCP statistics output displays the collective DHCPv4 and DHCPv6 statistics for DDoS.

Earlier to this release, the aggregate DDoS statistics output displayed 0 for aggregate BFD and the aggregate DHCPv4v6.

[ See show ddos-protection protocols

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 /var/db/scripts/jet file path.

[See file (JET).]

Changes to the RPC response for <validate> operations in RFC-compliant NETCONF sessions (ACX Series, PTX Series, and QFX Series)—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.

NETCONF <copy-config> operations support a file:// URI for copy to file operations (ACX Series, PTX Series, and QFX Series)—The NETCONF <copy-config> operation supports using a file:// URI when <url> is the target and specifies the absolute path of a local file.

[See <copy-config>.]

gNOI OS RPCs use the software version string instead of the package filename (PTX Series)—The version field in the gnoi.os.OS Activate(), Install(), and Verify() RPCs uses the software version string (as displayed in /system/state/software-version) instead of the package name.

Previously, shaping of Layer 2 pseudowires did not work on logical tunnel interfaces. This has been fixed for all platforms except QX chip-based MICs and MPCs.

In Junos OS Evolved platforms, show route snooping and show route forwarding-table does not show /56 routes in the VPLS address family table.

Starting in Junos OS Evolved 23.4R1, we have enabled the process-non-null-as-null-register configuration statement under edit protocols pim rp local by default. For earlier releases, you must configure this statement explicitly.

Before this change most list were ordered by the sequence in which the user configured the list items, for example a series of static routes. After this change the list order is determined by the system with items displayed in numerical sequence rather than by the order in which the items were configured. There is no functional impact to this change.

Optimized mesh group routes (ACX Series, QFX5130, QFX5700 and ACX Series)— show route snooping for inet.1/inet6.1 table and show route snooping table inet.1/inet6.1 will display only CE mesh group routes for platforms that support EVPN-MPLS or EVPN-VxLAN multicast. In earlier releases, other mesh groups like the VE mesh group were also displayed.

Viewing files with the file compare files command requires users to have maintenance permission — The file compare files command in Junos OS and Junos OS Evolved requires a user to have a login class with maintenance permission.

[See Login Classes Overview.]

Increase in revert-delay timer range— The revert-delay timer range is increased to 600 seconds from 20 seconds.

[See min-rate.]

Configure min-rate for IPMSI traffic explicitly— In a source-based MoFRR scenario, you can set a min-rate threshold for IPMSI traffic explicitly by configuring ipmsi-min-rate under set routing-instances protocols mvpn hot-root-standby min-rate. If not configured, the existing min-rate will be applicable to both IPMSI and SPMSI traffic.

[See min-rate.]