What’s Changed in Release 21.4R3
General Routing
-
Stateful port configuration for PTP over Ethernet and default profile is supported only on boundary clock mode and not on ordinary clock mode.
-
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. -
Change in in unnumbered-address support for GRE tunnel—Starting in Junos OS Release 24.4R1, there is a behavioural change in unnumbered-address support for GRE tunnel with IPV6 family and display donor interface for both IPV4 and IPV6 families of GRE tunnel. You can view interface donor details under show interfaces hierarchy level.
[See show interfaces.]
-
sFlow configuration— sFlow configuration is allowed only on et, xe, and ge interfaces in Junos OS Evolved-based platforms. All other interfaces are blocked for configuring sFlow on Junos OS Evolved-based platforms. A CLI error will be thrown if sFlow is configured on any other interface other than et, xe or ge interface.
Interfaces and Chassis
-
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].
MPLS
-
Starting with Junos Evolved Release 21.4R3 a CSPF LSP uses a new instance ID when attempting to re-signal a down LSP.
-
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.
Network Management and Monitoring
-
Changes to the NETCONF
<edit-config>
RPC response (ACX Series, PTX Series, and QFX Series)—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.
OpenConfig
-
OpenConfig container names for point-to-multipoint per interface ingress and egress sensors are modified for consistency from "signalling" to "signaling".
MPLS
-
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.
Routing Protocols
-
When the
krt-nexthop-ack
statement is configured, the RPD waits 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 ignore this statement.
Network Management and Monitoring
Changes to the NETCONF <edit-config>
RPC response (ACX Series, PTX
Series, and QFX Series)—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.
User Interface and Configuration
-
A new field
rollback pending
is added to the output ofshow system commit
that identifies whethercommit confirmed
is issued. It is removed oncecommit
orcommit check
is issued orcommit confirmed
is rolled back after rollback timeout.