Known Limitations

Learn about known limitations in this release for MX Series routers.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Note:

The Junos OS 23.2R2 Release offer limited or no support for the subscriber-management user-plane mode feature category.

General Routing

When a P or PE router is configured with inline active flow monitoring and MPLS template with tunnel-observation ipv4/ipv6 is used, there is a chance that some EoMPLS packets may be exported using mpls-ipv4 or mpls-ipv6 template instead of mpls template.PR1713728
On linecards and platforms using AFT, (that is, MPC10, MX304, LC9600), the final accounting stop stats for filters with accurate accounting enabled for the subscriber would be zero.PR1734608
On Junos OS MX304 and MX Series platforms with LC9600 linecards, with the current error handling mechanism upon receiving fatal error on Flexible pic concentrators(FPC), leads to disable both the Packet Forwarding Engine on a Physical Interface Cards (PIC) card and seen traffic impact.PR1765394
EBGP sessions established over IPSEC tunnels might flap, if multihop configuration statement is not configured. PR1791196

When upgrading from releases before Junos OS Release 21.2 to Release 21.2 and onward, validation and upgrade might fail. The upgrade requires using the 'no-validate' option to complete successfully. TSB18251 PR1568757

Traceroute in MPLS OAM may fail with unreachable in ECMP case when topology has multiple ecmp paths in each transit router. This is because destination address is not available. Destination address is computed using base address + bitmap index(available for that leg).Junos currently supports 64 bitvector size.Each transit ecmp legs consumes available bitmap indexes in the echo request packet. When all the bitmap indexes are consumed by the previous transit routers/ecmp legs, then for other ecmp legs bitmap indexes are not available hence multipath information tlv bitmap will be zero leading to unreachable issue as no destination address is available. Even RFC 8029 section 4.1 says full coverage is not possible as below, If several transit LSRs have ECMP, the ingress may attempt to compose these to exercise all possible paths. However, full coverage may not be possible. Hence this is an expected behavior.PR1699685