What’s Changed in Release 21.4R3

Stateful port configuration for PTP over Ethernet and default profile is supported only on boundary clock mode and not on ordinary clock mode.

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

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.

Display the donor details of the IPv6 borrower interface—The output for the show interfaces command now displays the donor details of the IPv6 borrower interface.

[See show interfaces].

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.

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

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.

When the krt-nexthop-ack statement is configured, the RPD will wait for the next hop to get acknowledged by PFE before using it for a route. Currently, only BGP-labeled routes and RSVP routes support this statement. All other routes will ignore this statement.

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.