Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Open Issues

Learn about open issues 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.

Class of Service (CoS)

  • While Traffic control profile is with only scheduler map associated with it and if its attached to IFL , commit error to be thrown. PR1688790


  • 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

  • On all platforms, MAC-IP route deletion and addition are triggered when re-ARP (Address Resolution Protocol) on MH (Multihoming) device fails in the EVPN-MPLS multihoming scenario resulting in traffic drop. PR1691132

Forwarding and Sampling

  • On MX series routers which support MPCs (Modular Port Concentrators), the ingress-queue-filter was not programmed correctly causing the traffic loss. The issue is seen only on non zero PFE (Packet Forwarding Engine) interface. PR1751494

General Routing

  • AFEB crashing with PTP thread hog on the device. PR1068306

  • If a vmhost snapshot is taken on an alternate disk and there is no further vmhost software image upgrade, the expectation is that if the current vmhost image gets corrupted, the system boots with the alternate disk so the user can recover the primary disk to restore the state. However, the host root file system and the node boots with the previous vmhost software instead of the alternate disk. PR1281554

  • When there is an input failure on one of the AC PEMs (low or high) it's wrongly categorized as a "Mix of AC PEMs". Thus, instead of "PEM input failure" an alarm "Mix of AC PEMs" might be raised.PR1315577

  • On WRL8 based VMHost platforms (i.e., ACX6360/PTX10001/MX150/NFX150/NFX250/NFX350), there is no log rotation for resild log and temperature sensor info is incorrectly written into resild log which could result in continuous logs in resild log file. The disk usage might keep increasing due to this issue. The disk usage could be eventually full which could cause system to hang and reboot. PR1480217

  • When there are HW link errors occurred on all 32 links on an FPC 11. Because of these link errors, all FPCs reported destination errors towards FPC 11 and FPC 11 was taken offline with reason "offlined due to unreachable destinations". PR1483529

  • After backup Routing Engine halt, CB1 goes offline and comes back online; this leads to the backup Routing Engine booting up, and it shows the reboot reason as "0x1:power cycle/failure." This issue is only for the RE reboot reason, and there is no other functional impact of this. PR1497592

  • In the platform using INH (indirect next hop, such as Unilist) as route next hop type for multiple paths scenario (such as BGP PIC or ECMP), the session fast-reroute might be enabled in Packet Forwarding Engines (PFEs). When the version-id of session-id of INH is above 256, the PFE might not respond to session update, which might cause the session-id permanently to be stuck with the weight of 65535 in PFE. It might lead PFE to have a different view of Unilist against load-balance selectors. Then either the BGP PIC or the ECMP-FRR might not work properly and traffic might be dropped or silently discarded. PR1501817

  • PR1463859 introduces a software defect that causes a 10GE interface to flap continuously when configuring with the WAN-PHY framing with the default "hold-down" timer (0). Once upgrading a router to an affected software release, the interface may flap continuously. This is not applicable to an interface with the default framing - LAN-PHY. PR1508794

  • When launching a guest Virtual Machine (VM) to run a third party application on Junos OS 15.1R1 and above, the guest VM might be shown as "UNAVAILABLE" even after successfully installing the third party application. This is due to duplicated device ID assigned to different disks. PR1529596

  • Due to BRCM KBP issue route lookup might fail. Need to upgrade KBP to address this issue, Due to high risk KBP SDK upgrade planned for 21.1. PR1533513

  • USF-SPC3 : With ipsec PMI/fat-core enabled, "show services sessions utilization" cli not displaying right CPU utilization. PR1557751

  • The Sync-E to PTP transient simulated by Calnex Paragon Test equipment is not real network scenario. In real network deployment model typically there will be two Sync-E sources (Primary and Secondary) and switchover happens from one source to another source. MPCE7 would pass real network SyncE switchover and associated transient mask. PR1557999

  • VE and CE mesh groups are default mesh groups created for a given Routing instance. On vlan/bridge-domain add, flood tokens and routes are created for both VE and CE mesh-group/flood-group. Ideally, VE mesh-group doesn't require on a CE router where IGMP is enabled on CE interfaces. Trinity based CE boxes have unlimited capacity of tokens, so this would not be a major issue. PR1560588

  • Service MIC does not work on ACX500 running Junos 20.4 or higher. PR1569103

  • 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

  • Service MIC does not work on ACX500 running Junos 20.4 or higher. PR1569103

  • 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

  • On QFX5110 VC, FPC may gets disconnected with 24K DHCPv6 relay scaling, after the traffic is stopped. "pfe_listener_disconnect" error messages may be seen.PR1594748

  • Pim Vxlan not working on TD3 chipsets enabling VxLAN flexflow after release 21.3R1. Customers Pim Vxlan or data plane VxLAN can use the version lower than 21.3R1. PR1597276

  • During RE switchover, if there is a burst of ICMP/BFD/SSH/FTP/TELNET/RSVP packets (~18K pps) you might see new backup RE restarting. PR1604299

  • On MX-VC (Virtual Chassis) platforms with MS-MPC or SPC3 service cards and AMS(Aggregated Multi-Service), traffic on the line card in the backup chassis may not be load-balanced properly due to timing conditions. This works well on the line card in the master chassis. There might be traffic loss when interfaces are not properly balanced.PR1605284

  • output of show network agent command should be null, which shows statistic per component after GRES. PR1610325

  • When user tries to disable AMS ifd using config knob, the ipsec tunnels are not deleted. Deactivating the services will provide the desired result. PR1613432

  • On all Junos platforms the MAC address of the 17th ae interface might be changed after the upgrade from 18.4+ to 20.4+ releases. It will lead to mac based service interruption.PR1629050

  • The fabric statistics counters are not displayed in the output of "show snmp mib walk ascii jnxFabricMib". PR1634372

  • On all devices running Junos OS or Junos OS Evolved, where this is a high BGP scale with flapping route and the BGP Monitoring Protocol (BMP) collector/station is very slow, the rpd process might crash due to memory pressure. PR1635143

  • The mspmand daemon running on MS-MPC/MS-MIC cards can occasionally crash when the service card (fpc/pic) is turned offline and then online at regular intervals when the number of service-set configured is moderately high and when extensive hardware crypto operations are being performed. Exact issue is yet to be isolated.PR1641107

  • vMX: "input fifo errors" drops reported under pfe shell "show ifd" but not seen in "show interface extensive" output. PR1642426

  • The broadband device has to be manually enabled in the configuration for DHCP and PPP access models for BNG CUPS. Configuration to enable the bb device is as follows: #set system subscriber-management mode force-broadband-device. PR1645075

  • On Junos platform, PTP does not lock when port speed is not configured under PIC hierarchy or port speed for some additional random ports are configured under the PIC hierarchy or perform PIC deactivate/activate.PR1645562

  • Core dump reported intermittently where random grpc stack crash is observed. The license service will auto restart and recover.PR1656975

  • On Junos platforms, in the VPLS environment when having "routing-options resolution preserve-nexthop-hierarchy" configured results in the packet dropped at egress PE for multiple MPLS stack labels.PR1658406

  • The OpenSSL project has published security advisories for multiple vulnerabilities resolved in OpenSSL. Please Refer to for more information.PR1661450

  • With following configuration changes subscribers are coming up. Config changes: ============= set forwarding-options dhcp-relay overrides allow-snooped-clients set forwarding-options dhcp-relay group DHCP-FO overrides allow-snooped-clients set forwarding-options dhcp-relay group DHCP-FO overrides user-defined-option-82 deactivate forwarding-options dhcp-relay group DHCP-FO interface ae31.0 overrides. PR1665499

  • On all Junos and Junos Evolved platforms, the user should not modify the locator attributes, instead, locator, SIDs should be deleted and configured back. Otherwise, it will lead to core file.PR1667320

  • On MX platforms with MIC-MACSEC-20GE, FEB(Forwarding Engine Board) may go down while activating/deactivating GRES (Graceful Routing Engine Switchover) configuration.PR1668983

  • These are expected error logs, and doesn't cause any functional impact. "jsr_iha_pri_unrepl_msg_func: Error: Invalid primary handle in msg 0x10006c600000621, error=2" These logs might be seen if the following conditions are met: * On all Junos OS platforms * Non stop routing is enabled. * with scaled setup The possible triggers would be restart chassisd, ksyncd, switchover, re reboot... which causes nsr unreplication/replication.PR1675057

  • Sometimes cores are reported on backup RE during init after a reboot etc. When the backup RE initialization is being done and system is busy, some commands executed in context of spmbpfe are taking more time to complete due to the initial heavy lifting by the kernel, In this stage, if in case the commands from spmbpfe process do not complete for >2.5 seconds, then there are chances of spmbpfe cores. This is a temporary issue seen on backup RE during init time only. This may not be impacting because if in case spmbpfe process crashes due to this, it would restart by itself and continue to init and run once the initial high cpu condition has passed. It should not cause any functionality or performance impact; especially since it is reported only on backup RE.PR1675268

  • On LC480 MX line-card with 1G interface 1PPS time error does not meet class B requirement (maximum absolute time error is 70 ns).PR1677471

  • A new command has been introduced that will display the differences between the destroute entries learned within l2ald and present in the kernel. PR1677996

  • 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

  • On QFX5100 platforms (both stand-alone and VC scenario) running Junos, occasionally during the normal operation of the device, PFE (Packet Forwarding Engine) can crash resulting in total loss of traffic. The PFE reboots itself following the crash.PR1679919

  • Changing a filter from interface-specific to physical-interface-filter (or visa versa) while also restarting the firewall process may result in issues with LACP. To avoid this, deactivate the filter before changing the mode.PR1679965

  • The issue here is that we see ?MQSS(0): DRD: Error: WAN reorder ID timeout error? once per PFE during bootup of FPC. This happens because during the FPC bootup some control packet from vmhost comes before the PFE init is fully complete. Because of this the EA Asic is not able to process the packet and throwing the error. The fix involves complex changes in the bootup sequence of ASICS and will result in other major issues. The original issue has no functionality impact. It is just one error per PFE seen during the FPC reload case only. At that time the traffic is not started yet and once the system is up no other impact is seen due to the Error. Hence the issue will not be fixed. Any "WAN reorder ID timeout error" during the bootup of FPC can be safely ignored.PR1681763

  • With this the maintenance-domain (MD) configuration and maintenance-association (MA configuration) under the connectivity-fault-management stanza will be ordered by the system and not as per the configuration order. PR1682939

  • When the hostname configuration is changed, the change is not reflected in the RIFT output. Also when changes are made to the REDIS configuration, they are not applied until rift is restarted via "restart rift-proxyd". PR1686233

  • On all Junos and Junos Evolved platforms if MVRP (Multiple VLAN Registration Protocol) is configured on an MSTP (Multiple Spanning Tree Protocol) enabled interface, the interface will be made part of all the existing MSTI (Multiple Spanning Tree Instance) on the switch and it will take part in the FSM (Finite State Machine) of all the MSTIs. If this interface will go into the forwarding state for the MSTI, of which it is not a part actually, will result in dropping in traffic of that particular VLAN.PR1686596

  • For leaves of data type ieeefloat32, the value will be encoded in bytes while being streamed to collector. The value contained in such leaves may not be completely accurate.PR1690598

  • With Sharding enabled, BGP flags like the following are not displayed on Active route in "show route extensive" output:"Accepted Multipath MultipathContrib MultiNexthop" Per shard view, using "show route extensive prefix rib-sharding shard-name" will show these flags.PR1693207

  • Issue is seen when multiple line cards exports telemetry data for sensor-path "/junos/system/linecard/fabric/" and one of the line card exporting data reboots. After rebooting, the same card or one/more cards may stop streaming of data or streaming of data will be too slow to detect. Removing one or more line card from telemetry streaming of this data resolves the issue.PR1693394

  • It is recommended to use IGP shortcut with strict SPF SIDs in SRTE path. if Strict SPF SIDs are used then this issue would not occur. This issue will occur only if regular ISIS SIDs are used in SRTE path and IGP shortcut is enabled. with this, if customer perform multiple times deactivate/activate for SRTE telemetry. PR1697880

  • During BGP MP route re-resolution window, a corner case was hit, such that rpd will assert and restart. This error case is observed during Multi-Feature-Test with BGP-MP, L3VPN/L2VPN, over RSVP/LDP transport, as well as colored SRTE, and SRv6 tunnel transport along with BGP CT. This issue will get resolved in next 22.4R1 services releases.PR1699773

  • Once the device is loaded with the new image, PIC tries to boot up. mspmand is one of the processes inside PIC, crashes sometimesPR1700462

  • The optic configuration mismatch alarm was always enabled, but was not reported by the RE during 'show chassis alarms'. This alarm will now be correctly reported by the FPC and displayed in the RE. There is no behavior change other than the alarm being reported correctly now.PR1700606

  • On Junos platforms, even though there are no active subscribers, a foreign file propagation (ffp) commit error is seen for the class-of-service traffic-control-profile.PR1700993

  • When subscribing to sensor paths "/junos/system/linecard/packet/usage/", "/junos/services/label-switched-path/usage/" or other line card (PFE) sensor paths in gNMI subscription mode, packet drops may be seen in the CLI command "show network-agent statistics gnmi detail" output. The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc.PR1703418

  • In Chassisd, Jvision thread takes more time in streaming of jvision packets because of volume of data and number of sensors involved with this daemon. Jvision thread engaged for more time to process streaming events caused Chassisd master thread to lose receive/send keepalive messages to/from other RE, which eventually was causing automatic RE switchover in most of the cases. To avoid this, fix done for exporting small payload jvision packets (formation of which takes less time) and deferring jvision thread more in an interval, to allow chassisd master thread to process high-priority hello/keep-alive messages. This means now, more number of packets is sent in one reporting interval and with larger spread (earlier same amount of data was sent with 2 or 3 packets of higher payload size, and 100ms of deferring time for jvision thread. This behaviour is increasing KPI-2 but lowering KPI-1 (payload size).It is not possible to back out changes done to solve keep-alive message loss issue. Hence we will have to keep Chassisd as an exception, when we measure/report KPI-2 values. Jvision in Chassisd has to give more priority/time to process keep-alive messages than sending of jvision packets. Hence delay between jvision packets are more.PR1706300

  • On Junos and Junos OS Evolved platforms, the dcpfe(Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces will flap.PR1711860

  • On the MX104 platform, the Wrong threshold-temperature is displayed.PR1713788

  • On Junos MX10008 platform, the FPC (Flexible PIC Concentrator) crash will be observed when connected to non-Juniper SFP (Small Form-factor Pluggable) and it will lead to traffic loss.PR1722823

  • On all Junos and Junos Evolved platforms BGP traceoptions configuration will have an impact on the CPU, threads will be busy and will take time to recede in spite of disabling it. It is important we enable a specific trace flag and disable it when the CPU goes high. It is also important not to perform switchover and other triggers which can add load to the CPU during traces are enabled. Traces must be enabled discretely. PR1724986

  • MX304 Major Alarm " Host 0 detected AER correctable error" after RE switchover.PR1731237

  • gNOI "Rotate" and "Install" gRPC message should be handled as part of a single RPC stream instead of individual RPC message. Currently, each message in rotate and install RPCs are handled as separate stream. If the same stream is used to send multiple RPC messages, the rotate gRPC will fail.PR1732601

  • Xmlproxyd crash could be seen if there are multiple collectors subscribing for Xmlproxyd sensors and some or all of the collectors are flapping frequently at the rate of 90 seconds or so. The occurrence of this issue is rare. The telemetry streaming of Xmlproxyd sensors will be absent during the time Xmlproxyd crashes and restarts on its own. This time could be within 30 seconds or so. Once Xmlproxyd comes up, the telemetry streaming of Xmlproxyd sensors will be resumed automatically.PR1732763

  • 400g option is visible under "set chassis fpc 0 pic 0 port port_num speed" command. For example: # set chassis fpc 0 pic 0 port 20 speed ? Possible completions:100g Sets the interface mode to 100Gbps10g Sets the interface mode to 10Gbps200g Sets the interface mode to 200 Gbps25g Sets the interface mode to 25Gbps400g Sets the interface mode to 400Gbps40g Sets the interface mode to 40Gbps50g Sets the interface mode to 50GbpsPR1734654

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

  • On all Junos and Junos Evolved platforms, in a rare scenario, the FPC will go down due to core.PR1739595

  • When running DHCPv6 Relay in CUPS model, on UP GRES DHCPv6 traffic loss is observed.PR1743087

  • The switch-options settings on logical-system will be not reflected after Routing Engine rebooting or Routing Engine switchover. This will happen logical-system only. In default instance, this behavior cannot be seen. PR1743737

  • RPD core is sometimes seen if there are many unilist nexthop with identical key values but different metric in Evo, esp when ACK is requested for those nexthops.PR1745509

  • On all Junos platforms with dual RE, error message: 'Minor potential slow peers are: X' will be seen. Due to some reason the PFE/PIC will be slow and services will face latency issue. the peerbuf list gets full, peer proxy could not enqueue further IPCs (ifstate chain/peer update to backup gets stalled ) causing pfe/pics to be a slow consumer, this impacts service on the device. 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 (PFE) which causes VRRP traffic to get dropped even though other active member links in the AE 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

  • Memory in VMhost level is still in cache and not properly freed after take VMhost snapshot. PR1755585

High Availability (HA) and Resiliency

  • When GRES is performed with the interface em0 (or fxp0) disabled on the primary Routing Engine, then enable the interface on the new backup Routing Engine, it isn't able to access network.PR1372087


  • A Use After Free vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Refer to for more information. PR1636063

  • NTP time drift on the affected Junos releases. Earlier implementation of kvmclock with vDSO (virtual Dynamic Shared Object) which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate.PR1691036

Interfaces and Chassis

  • MediaType value in SNMP/Jvision is not correct for DOWN interfaces after the switch comes up following a reboot. PR1671706

  • IFL packet counters are not implemented for AMS interface. It is a new change. PR1673337

  • This issue is specific to MXVC only and the issue is not seen during manual execution of the test case. Issue is seen only with the test script that too rarely and hence the exact trigger of the issue is not clear. PR1686425

  • On all Junos platforms, if a speed mismatch happens in the LAG (Link Aggregation) and member interface then a traffic drop will be seen.PR1725168


  • PHP software included with Junos OS J-Web has been updated from 7.4.30 to 8.2.0 to resolve multiple vulnerabilities. Please refer to for more information. PR1698386

Layer 2 Features

  • In case of the access-side interfaces used as SP-style interfaces, when a new logical interface is added and if there is already a logical interface on the physical interface, there is 20--50 ms traffic drop on the existing logical interface. PR1367488

  • On all Junos Evolved and Junos MX platforms, when a new logical interface(LSI) is created, but the configuration was deleted as the kernel failed to add the interface will lead to rpd crash.PR1680687

  • in a H-VPLS network with VPLS hot-standby and the knob 'routing-options forwarding-table vpls-hotstandby-convergence' enabled on spokes, if the active hub is rebooted, 20-25 seconds loss for inter-zone traffic stream is seen. This is due to hubs in other zones connected by full-mesh ldp, starting global repair before spokes starting local repair.PR1699645

Layer 2 Ethernet Services

  • If a client sends a DHCP request packet, and option 55 includes PAD option (0), a DHCP ACK will not be sent back to the client. PR1201413

  • In the CBNG (XDA CUPS) environment, DHCPv6 subscribers fail to login over PPP over L2tp Tunneled. This setup has XDA CP and UP for both LAC and LNS. DHCPv6 subscriber is stacked over PPP from the Client side. While the PPP(v4 and v6) session gets established successfully, DHCPv6 subscriber traffic is being dropped at the LNS UP. Though this is the Release notes for 22.4R1 Release, issue is not seen in 23.1 based Dev Common Branch. Adding the release notes for 22.4R1 scope only. PR1683955

  • DHCP ALQ no-advertise-routes-on-backup functionality does not work in VRF for Framed-Route. PR1740822


  • ingress will retry after lsp stay down for extended period of time or customer can clear lsp to speed up the retry. PR1631774

Network Management and Monitoring

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

Platform and Infrastructure

  • PVSTP protocol packets is getting duplicated when it tunnelled through Layer2 tunnelling protocol. Other protocol data units PDUs( STP,VTP,CDP ) are not impacted. PR1686331

  • On Junos MX platforms, when Virtual Router Redundancy Protocol (VRRP) packets come from the LAG interface with delegate-processing enabled, it should be processed on anchor PFE. If it comes from non-anchor PFE - it goes to anchor PFE through the fabric. In that case, TTL is decremented. If a FW filter on the loopback interface is applied for VRRP with a ttl=255 condition, the VRRP won't work - there will be a service impact.PR1701874

  • On Junos MX and EX92XX with specific line cards, VLAN rewrites will not happen for traffic egressing from IRB(Integrated Routing and Bridging) interface over an L2 AE (Aggregated Ethernet) IFL (Interface Logical), if the L2 AE IFL is configured to perform VLAN rewrites on the frames. This happens when the IRB is configured as a routing-interface on EVPN (Ethernet Virtual Private LAN) or VXLAN (Virtual Extensible LAN) routing instances and the traffic has to egress on IRB over an L2 AE IFL. As a result, the frames are forwarded with incorrect VLAN tag information.PR1720772

  • On Junos MX platforms, in Ethernet Virtual Private Networks-Layer 2 Virtual Private Networks-Circuit Cross-Connect (EVPN-L2VPN-CCC) setup, the integrated routing and bridging (IRB) interface over access logical tunnel (LT) interface is configured, it is sending vlan tagged packet on the access port and not removing it causing the host communication to break.PR1740606

Routing Policy and Firewall Filters

  • On all Junos and Junos OS Evolved platforms where Openconfig routing policies are configured, deleting a single prefix from prefix-list deletes all the prefixes.PR1691218

Routing Protocols

  • 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

  • LDP OSPF are in synchronization state because the IGP interface is down with ldp-synchronization enabled for OSPF. user@host> show ospf interface ae100.0 extensive Interface State Area DR ID BDR ID Nbrs ae100.0 PtToPt 1 Type: P2P, Address:, Mask:, MTU: 9100, Cost: 1050 Adj count: 1 Hello: 10, Dead: 40, ReXmit: 2, Not Stub Auth type: MD5, Active key ID: 1, Start time: 1970 Jan 1 00:00:00 UTC Protection type: None Topology default (ID 0) -> Cost: 1050 LDP sync state: in sync, for: 00:04:03, reason: IGP interface down config holdtime: infinity. As per the current analysis, the IGP interface goes down because although LDP notified OSPF that LDP synchronization was achieved, OSPF is not able to take note of the LDP synchronization notification, because the OSPF neighbor is not up yet. PR1256434

  • On MX platforms, unexpected log message will appear if the CLI command 'show version detail' or 'request support information' is executed: test@test> show version detail *** messages *** Oct 12 12:11:48.406 re0 mcsnoopd: INFO: krt mode is 1 Oct 12 12:11:48.406 re0 mcsnoopd: JUNOS SYNC private vectors set. PR1315429

  • Errors might be seen on ephemeral commit during ISSU.PR1679645

  • BGP LU statistics does not report correct statistics when sharding is enabled. This is not specific to BGP CT feature of this RLI. This will be fixed via RLI 53922 [Umbrella RLI to fix small Topgun Sharding Gap]. PR1684238

  • 22.3 onwards, isis yang is uplifted to 1.0.0 version which has major change in existing OC path that was supported earlier. Since OC path has change, same need to reflected in translation script which is not done. As part of D27 release for cloud, translation script will be modified with newer OC path. Till then supported older OC config is broken. eventually D27 code will come back to DCB and things will work fine after that. PR1686751

  • The issue is not addressed for 22.1R3 and will be addressed in future releases. PR1687273

  • This issue is seen with only evo and not seen Junos. Its seen in a combination of Rsvp and ISIS. Stats is getting incremented. PR1700063

  • On all Junos and Junos OS Evolved platforms with dual-RE, after back to back Graceful Routing Engine switchover (GRES) is performed, the periodic packet management process (ppmd) crash will be seen. PR1702687

  • On all Junos and Junos Evolved platforms with TI-LFA (Topology-Independent Loop-Free Alternate) feature enabled, when IP address is removed from one interface and is assigned to another interface in the same commit, the rpd process crashes affecting routing control plane. PR1723172

Services Applications

  • When a configured tunnel interface is changed to another one, flow-tap-lite functionality stops working i.e, packets don't get mirrored to content destination. But, this problem isn't consistently seen. PR1660588

User Interface and Configuration

  • On all Junos OS Evolved platforms, when archiving configuration files to a remote IPv6 host using Secure Copy Protocol(SCP), file transfer fails.PR1720525


  • When using Group VPN, in certain cases, the PUSH ACK message from the group member to the group key server may be lost. The group member can still send rekey requests for the TEK SAs before the hard lifetime expiry. Only if the key server sends any new PUSH messages to the group members, those updates would not be received by the group member since the key server would have removed the member from registered members list.PR1608290