Open Issues

A few duplicate packets might be seen in an A/A EVPN scenario when the remote PE device sends a packet with an IM label due to MAC not learned on the remote PE device, but learned on the A/A local PE device. The nondesignated forwarder sends the IM-labeled encapsulated packet to the PE-CE interface after MAC lookup instead of dropping the packet, which causes duplicate packets to be seen on the CE side. PR1245316

After GRES, VPWS switchover occurs only after NSR phantom timer expires. The NSR phantom timer is configurable. This can result in packet loss for that duration. PR1765052

The subscription path for flow sensor shall be changed from /junos/security/spu/flow/usage to /junos/security/spu/flow/statistics. This change is done to maintain uniform format for subscription path in request and response data.PR1738832

fpc3 cannot scan phys_mem_size.out syslog error occurs at /var/log/*.out (0;0xdd3f6ea0;-1). PR1548677

Because of a race condition, the show multicast route extensive instance instance-name output can display the session status as invalid. Such an output is a cosmetic defect and not indicative of a functional issue. PR1562387

When the active slave interface is deactivated, the PTP lock status is set to 'INITIALIZING' state in show ptp lock-status output for few seconds before BMCA chooses the next best slave interface. This is the day-1 behavior and there is no functional impact. PR1585529

Output of the show network agent command shows null indicating the statistic per component after GRES. PR1610325

There will be drop of syslog packets seen for RT_FLOW: RT_FLOW_SESSION_CREATE_USF logs until this is fixed. This will not impact the functionality. PR1678453

Current stack and display is correctly set to 128 ports that is qualified on all MX10K8 linecardsPR1706376

When LAG is configured with mixed speed interfaces switching to a secondary interface of different port speed, results in a few packet drops for a very short duration. PTP remains lock and there is no further functional impact. PR1707944

Next Hop counts are not as expected. PR1710274

The commit notification from 'edit private' mode won't produce correct patch.PR1713447

rpd might generate core file when running slow related gribi toby scripts in fusion system. Running same scripts in manually deployed testbed will not trigger rpd core file.PR1715599

Segmentation fault on grpc timer thread (might be related to keepalive) #32085 grpc issue https://github.com/grpc/grpc/issues/32085 grpc stack needs to be upgraded to 1.53 or later.PR1722414

With a two-color policer configured on aggregated Ethernet interfaces, the "queue-counters-trans-bytes-rate" counter might display an incorrect value. PR1735087

On all Junos OS devices, the time needed to commit increases when a Trusted Platform Module (TPM) is configured. PR1738193

There must be at least 1 minute spacing between consecutive key rollovers. This includes key rollovers triggered by key chain, sak_key_interval, primary/fallback, packet count rollovers.PR1739933

Given that JNP10K-PWR-AC3 has four inputs, it will be useful to provide the operating state information of the feed in Snmp. This is planned as an enhancement in future releases. PR1742996

On MX Series platforms with MS-MPC/MS-DPC, when the system is busy in the creation/deletion of sessions results in the picd process crashes for executing the CLI command show service sessions/flows or clear service sessions/flows aggressively (executing CLI command in 5-10 secs iteration). PR1743031

On MX10004 and MX10008 platforms, the DIP Switch - 15A or 20A does not get displayed in the CLI output. This is in line with the existing 5.5KW power supplies. The actual DIP switch has to be checked physically. PR1744396

[TIMING BITS] - LOS alarm not generating when BITS is in LOS state. PR1744419

Session synchronization is not working on standby even after replication-threshold timer (150 seconds) is complete with SRD configuration.PR1744420

On MX10004, MX10008, and MX10016 routers, some enhanced fans is not working after hot-insertion of Fan Tray. PR1745299

On all Junos OS platforms, due to timing issues the Packet Forwarding Engine and the Physical Interface Card (PIC) will be slow and services will face slowness issue and error message: 'Minor potential slow peers are: X' will be seen. This is rare timing issue.PR1747077

On Junos using afeb/tfeb way of communication to PFE that is MX80/MX104 platforms with Virtual Router Redundancy Protocol (VRRP) configured, deleting a member link from the aggregated Ethernet (AE) bundle removes the VRRP filter entry in the Packet Forwarding Engine which causes VRRP traffic to get dropped even though other active member links in the aggregated Ethernet bundle exists.PR1747289

On MX104 platform with MACSEC MIC, the per-unit-scheduler configuration on the MACSEC MIC interface results in the PFE crash leading to traffic impact.PR1747532

On MX10000 platforms, when fan trays are removed, the chassisd log messages displays normal and when fans are running, it displays full speed. These log messages are incorrect and there is no functionality impact. PR1753787

When you remove fantray, the SNMP logs message displays Fan Tray 0 Fan 0 in jnxContentsDescr instead of Fan Tray 0. However, the chassisd log message displays Fan TRAY 0 is absent, which is correct. SNMP code by design doess not consider Fans Tray as a separate entity and is associated with the Fans. There is no separate OID for Fan Tray. Logs and SNMP Traps mislead the Fan Tray issues. PR1753801

MX304 core-spmbpfe-bugatti-pvl-b1-node seen in re1. PR1758480

SRv6 TE with logical-systems is not qualified in any release. PR1760727

For certain releases, performing unified ISSU on MPC10 or MPC11 can generate an FPC core file. PR1766307

Ability to track partially upgraded PSM is not available under the show system firmware command. This is due to current limitation of the show system firmware command.

Removing PEM FRU from the chassis during its firmware upgrade is currenlty not allowed due to firmware upgrade limitations, leading to undefined software behaviour in such situations.PR1773895

When UPs are not connected, the user cannot delete a configured SGRP.PR1774717

You can configure the routing platform to track IPv6-specific packets and bytes passing through the router. To enable IPv6 accounting, include the route-accounting statement at the [edit forwarding-options family inet6] hierarchy level: [edit forwarding-options family inet6] route-accounting; By default, IPv6 accounting is disabled. If IPv6 accounting is enabled, it remains enabled after a reboot of the router. To view IPv6 statistics, issue the show interface statistics operational mode command. Can be found here: http://www.juniper.net/techpubs/en_US/junos10.4/topics/usage-guidelines/policy-configuring-ipv6-accounting.html PR717316

The link aggregation group (LAG) member links may flap on all Junos OS platforms except MX Series when the configuration of any interface is changed or modified. The flap is not seen always. PR1679952

The default behavior of local reversion has changed from Junos OS Release 16.1 and that impacts the LSPs for which the ingress does not perform make-before-break. Junos OS does not perform make-before-break for no-cspf LSPs. PR1401800

Observed vgldfpc core @__kernel_vsyscall,__GI___open_catalog.PR1740390

In some NAPT44 and NAT64 scenarios, duplicate SESSION_CLOSE Syslog will be seen. PR1614358

L2-Trans: pm_soam_frame_rx count is not incrementing as expected.PR1729970

MVPN RVT MX EA cards: RVT interface traffic statistics are not properPR1755516

In EVPN Multi-Home AA scenario, random drops will be observed on the non-designated-forwarder for ARP-REPLY generated in response to ARP-REQ received for Virtual-Gateway-Address defined on IRB interface.PR1772733

Certain BGP traceoption flags (for example, "open", "update", and "keepalive") might result in (trace) logging of debugging messages that do not fall within the specified traceoption category, which results in some unwanted BGP debug messages being logged to the BGP traceoption file. PR1252294

On all Junos OS platforms and Junos OS Evolved with scaled BFD sessions, FPC reload/restart results in few BFD session flap.PR1698373

BFD sessions bounce during unified ISSU if authentication is used. PR1723992

openconfig-local-routing.yang from "1.0.0" to "2.0.0" in which this module is deprecated now. As we upgraded yang model for local-routes, it deprecated few xpaths that were previously supported: /local-routes/static-routes/static/ /local-routes/local-aggregates/aggregate/ PR1735926

The set routing-instance ri_name protocols igmp-snooping for non-MX Series platforms like QFX series, EX series, ACX5K and all EVO platforms supporting snooping need to mandtorily pass vlan option for set routing-instance ri_name protocols igmp-snooping. The instance level snooping for these is supported using set routing-instance ri_name protocols igmp-snooping vlan all.PR1736608

rpd core is generated in master Routing Engine @ block_id_free_unique_blk, block_id_free_unique_blk, rt_instance_delete_master_lsi_ifl_data. PR1742915

There are streaming discrepancies for /adjacency-sids/adjacency-sid in /network-instances/network-instance/protocols/protocol/isis between Junos OS Releases 22.3R2-S1 and 20.X75-D51. There is a OC YANG version difference between the two releases and the OC YANG versions are not backwards compatible. The YANG version is tightly coupled with the release. PR1750314

On Junos OS MX80, MX240, MX480, MX960 platforms, in an issue where an old dynamic security association_configuration (sa_cfg) with a different instance is present and trying to establish new sets of IPSec Security Association (IPSec SAs) using a new Internet Key Exchange security associations (IKE SA) established for the same remote device but with different instance. This can happen, if for some reason old sa_cfg is not cleaned (failed in clean-up). On crash, the Key Management Daemon (kmd) restarts but fails because of kernel instance mismatch present in the kernel database (DB). So all the IPsec tunnels will be impacted.PR1771009