Known Limitations

In Junos OS Release 23.2, Juniper BNG User Planes are not supported by Juniper BNG CUPS.

When you configure a P or PE router with inline active flow monitoring and MPLS template with tunnel-observation IPv4 or IPv6 is used, there is a chance that some EoMPLS packets might be exported using mpls-ipv4 or mpls-ipv6 template instead of mpls template. PR1713728

When upgrading from releases before Junos OS Release 21.2 to Release 21.2 and later validation and upgrade might fail. The upgrade requires using the 'no-validate' option to complete successfully. https://kb.juniper.net/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