What’s Changed in Release 21.4R3

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

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.

[See show ipv6 router-advertisement].

For PTX Series devices running Junos OS Evolved, software priority "medium-low" maps to hardware priority "medium" for normal scheduling mode and "low" for strict priority scheduling mode.

New ARP and NDP packet classification (QFX10002, QFX10008, and QFX10016)—We've introduced two CP classes for ARP and NDP packets received over VTEP interface. When your device identifies a packet as ARP or NDP, it performs an ingress port check which verifies whether the VTEP interface receives these packets. If VTEP interface receives the packet, datapath re-writes the CP class to the newly defined values. Based on this new CP class, the system performs the remaining packet processing and forwards the packets toward the host path. The system adds a separate DDoS policer to this ARP traffic, which ensures that the ARP traffic is not triggering underlay ARP DDoS violation.

Starting with Junos OS 16.1 the MPLS EXP bits transmitted in self ping messages are set based on the DSCP/ToS setting of the corresponding IP packet.

When defining a constrained path LSP using more than one strict hop belonging to the egress node, the first strict hop must be set to match the IP address assigned to the egress node on the interface that receives the RSVP Path message. If the incoming RSVP Path message arrives on an interface with a different IP address the LSP is rejected.

Starting with Junos OS release 21.4R3 CLI support for the set protocols express-segments configuration statement, and the show express-segments and clear express-segments operational mode commands are removed from the EX4300-24P, EX4300-24T, EX4300-48P, EX4300-48T, EX4300-48T-DC, EX4300-32F, EX4300-48T-BF, EX4300-48T-DC-BF, MX5-T, MX10-T MX40-T, MX80, MX80-T, MX80-48T, MX80-P, MX104, and the MX-TSR80 platforms.

Starting with Junos OS and Junos Evolved release 21.4R3 a CSPF LSP uses a new instance ID when attempting to re-signal a down LSP.

Changes to the NETCONF <edit-config> RPC response (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When the <edit-config> operation returns an error, the NETCONF server does not emit a <load-error-count> element in the RPC response. In earlier releases, the <edit-config> RPC response includes the <load-error-count> element when the operation fails.

A new field rollback pending is added to the output of show system commit that identifies whether commit confirmed is issued. It is removed once commit or commit check is issued or commit confirmed is rolled back after rollback timeout.