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.


  • 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 because MAC is not learned on the remote PE device, but learned on the A/A local PE device. The non-designated forwarder sends the IM-labeled encapsulated packet to the PE-CE interface after MAC lookup instead of dropping the packet. This creates duplicate packets on the CE side. PR1245316

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

Forwarding and Sampling

  • On all EX9200 and MX Series platforms having MPC10, MPC11 and LC9600 cards, traffic is leaking through a scale filter configuration change. PR1715504

General Routing

  • Compact Forwarding Engine Board (AFEB) crashes with Precision Time Protocol (PTP) thread hog on the device. As a workaround, enable PTP to process the PTP packet when PTP configuration is active. If PTP configuration does not exist, ignore the PTP packet processing even if the field-programmable gate array (FPGA) shows the available PTP packet. This is a rare issue. 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 corrupts, the system boots with the alternate disk that helps the user to 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 VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

  • When you install the MIC-3D-8OC3-2OC12-ATM and configure ATM interface, FPC might crash on MX240 and MX2020 routers. Packet Forwarding Engine might also crash on MX104 routers for the same. PR1453893

  • Error messages "TALUS(number) PCIe(number) DMA RX interrupt received. Queue stuck status 0xeeeeee0" are triggered in system logs due to queue-back pressure or FPGA drop. PR1465888

  • When hardware link errors occur on all 32 links on an FPC11, all FPCs reports destination errors towards FPC11 and FPC11 are taken offline with reason "offlined due to unreachable destinations". PR1483529

  • When secondary Routing Engine stops, CB1 goes offline and comes back online. This reboots the secondary Routing Engine because of the "0x1:power cycle/failure". There is no other functional impact. PR1497592

  • AMS bundle state toggles mometorily from up, down, or up after configuration commit for scaled scenario. PR1521929

  • In MAC-OS platforms when Juniper Secure Connect client connects successfully, the client is not getting minimized to tray icon and needs to be minimized manually.PR1525889

  • In scaled MX2020 router, with VRF localisation enabled, 4 million nexthop scale, 800K route scale. FPCs might go offline on GRES. Post GRES, router continues to report many fabric related CM_ALARMs. FPC might continue to reboot and not come online. Rebooting primary and secondary Routing Engine will help recover and get router back into stable state. PR1539305

  • With IPsec PMI or fat-core enabled, show services sessions utilization CLI do not display 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 occurs from one source to another source. MPCE7 passes 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 adding VLAN or bridge domain, flood tokens and routes are created for both VE and CE mesh-group and flood-group. Ideally, VE mesh-group does not require a CE router where IGMP is enabled on CE interfaces. MX Series based CE boxes have unlimited capacity of tokens, so this might not be a major issue. PR1560588

  • To avoid the additional interface flap, interface hold time needs to be configured . PR1562857

  • This issue is caused by /8 pool with block size as 1, when the configuration is committed the block creation utilizes more memory causing NAT pool memory shortage that is currently being notified to customer with syslog tagged RT_NAT_POOL_MEMORY_SHORTAGE. PR1579627

  • On MX Series routers the Juniper Device Manager (JDM) server is not created in in-chassis mode of Junos node slicing, which results in mgd process crash and affects guest network function (GNF) provisioning. PR1583324

  • When the active secondary interface deactivates, 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 all devices running Junos OS Release 19.1R3-S5-J3, the subscriber logical interface might get stuck after the Extensible Subscriber Services Manager (ESSM) deletion. PR1591603

  • PIM VxLAN is not working on TD3 chipsets enabling VxLAN flexflow after Junos OS Release 21.3R1. Customers Pim VxLAN or data plane VxLAN can use the Junos OS Release 21.3R1. PR1597276

  • MX2010, MX2020: MPC11E: ISSU is not supported for software upgrades from 21.2 to 21.3 and 21.4 releases due to a flag day change PR1597728

  • During Routing Engine switchover, if there is a burst of ICMP, BFD, SSH, FTP, TELNET, and RSVP packets (~18K pps), a new secondary Routing Engine might restart. PR1604299

  • On MX Series Virtual Chassis platforms with MS-MPC or SPC3 service cards and aggregated multi-service (AMS), traffic on the line card in the seconday 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 a traffic loss when interfaces are not properly balanced. PR1605284

  • On all MX Series routers, in a subscriber management environment, new subscribers might not connect if class of service (CoS) classifier rewrite (CR) features are used by the variable based flow (VBF) service. The reference count mismatching between Routing Engine and VBF is caused by VBF flow VAR CHANGE failure. PR1607056

  • When user tries to disable AMS physical interface using configuration statement, the IPsec tunnels are not deleted. Deactivating the services will provide the desired result. PR1613432

  • Percentage physical-interface policer is not working on aggregated Ethernet, after switching between baseline configuration to policer configuration. PR1621998

  • On all Junos OS platforms the MAC address of the 17th aggregated Ethernet interface might be changed after the upgrading from Junos OS Release 18.4 to Junos OS Release 20.4 and later. It will lead to MAC based service interruption. PR1629050

  • For a topology with VSTP and VRRP configured and IPv6 traffic, if VSTP bridge priority is changed a couple of times (to trigger toggling of root bridge), it is possible that V6 traffic drop is seen on some of the streams. PR1629345

  • For ACX5448, MX204 and MX2008 "VM Host-based" platforms, starting with Junos 21.4R1 or later, ssh and root login is required for copying line card image (chspmb.elf for MX2008) from Junos VM to Linux host during installation. The ssh and root login are required during installation. Use "deny-password" instead of "deny" as default root-login option under ssh configuration to allow internal trusted communication. For more information refer to TSB18224. PR1629943

  • On MX Series routers with enhanced subscriber management enabled, when host-prefix-only is configured on the underlying-interface for subscribers, it might not work in FPC. PR1631646

  • 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 or station is slow, the rpd process might crash due to memory pressure. PR1635143

  • Source MAC must not be configured on the underlying static interface on the UP for PPPoE login to work correctly. PR1641495

  • WIth precision time protocol (PTP) over IPv6 on MPC2E 3D EQ, secondary PTP stays in the acquiring state. PR1642890

  • When CFP2-DCO is used, operator need to configure otn-option which is the only supported mode. PR1643815

  • On MX10004, MX10008, and MX10016 routers, oamd process is not started and GRE keepalives adjacency is down. PR1644480

  • Committing configuration changes during the Packet Forwarding Engine reset pause window (when Packet Forwarding Engine is disabled, yet the pfe reset proper has not started) has the potential of causing errors and traffic loss. In particular, the configuration changes that result in re-allocating policers (which are HMC-based) might lead to traffic being entirely policed out (I.e. not flowing). Once the PFE reset procedure has started configuration changes ought to be avoided until the procedure is complete. PR1644661

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

  • In the IPv6 segment routing deployment, packets are sent out with incorrect ethernet type. PR1647622

  • PTP Playback Engine reset error is reported sporadically with PTP FPGA firmware version A4 7 with no functionality impact. PR1652275

  • The core file is generated intermittently where random grpc stack crash is observed. The license service will auto restart and recover. PR1656975

  • DHCPACK is not received at ztp-server after zeroize of the device (client). PR1658287

  • On Junos OS platforms, in the VPLS environment when having routing-options resolution preserve-nexthop-hierarchy configuration 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. For more information efer to JSA70186. PR1661450

  • The version details for certain daemons will appear in the command output after the device has been rebooted after the completion of the USB installation of Junos OS.PR1662691

  • user should not modify the locator attributes, instead locator, SIDs should be deleted and configured back. Otherwise it will lead to coredump.PR1667320

  • For GNMI subscriptions, Packet Forwarding Engine doesn't support filtering in subscription paths. So data is streamed from Packet Forwarding Engine ignoring filtering. PR1668911

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

  • License-check core is being dumped upon reloading the system after applying specific set of configs. Once the system comes up, everything runs fine and no issue is seen.PR1671419

  • In the case of an Active-Active lease query stale-timer config is mandatory. This is required to optimize the sync time, as both peers get the solicit packets at the same time. Knob: set forwarding-options dhcp-relay stale-timer 20 The above knob is required to resolve this issue and it needs documentation. PR1671589

  • On SyncE over LAG interfaces, if the end points have different ESMC QL configured, on one of configured syncE interface, ESMC QL is toggling between PRC and DNU and sync-E does not lock and moves to holdover state. PRC packets are received with MAC address of the upstream master. These packets are not dropped based on the link-local MAC address. Based on PLM recommendation inspired by the customer requirements and MEF 6.1.1 EPL Option 2 service (an excerpt below, taken from here So, by default we are Option #2 compliant, if someone needs Option #1 behavior, a filter can be configured to match and discard. PR1677131

  • 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

  • The IFD remaining stats flag is not set properly in chassid in today's code. It should be set to TRUE only if HCOS is configured on an interface. Else, it should not be SET. Not setting this rightly, results in statistics not being displayed OR the command output not being displayed at all. The impacted command is "run show interfaces extensive intf-name" and the impact is seen in GNF environment with no explicit COS configuration on the interfaces. Not using "extensive" will ensure there is no issue as well. This is specific to MPC11 with sub LC (GNF) setup.PR1678071

  • 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

  • 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

  • PR1683656

  • 100GE interface on JNP-MIC1 TIC module may keep flapping for 1 ~ 45 minutes after a specific 3rd party peer device (NRU02 from Arista/Pluribus) is booting up. PR1686012

  • On Junos MX platforms with MPC1-9E line cards, when PFE (Packet Forwarding Engine) is disabled, scenarios like multicast receiver join/leave that result in allocation and de-allocation of memory in PFE can cause a memory leak issue. This is because memory is allocated on the disabled PFE, but not freed.PR1686068

  • If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch, So, if there are two interfaces between R1 and R2 as below: R1(et-0/0/1 and et-0/0/2)======(et-0/0/1 and et-0/0/2)R2 And one interface is MVRP enabled (say et-0/0/1), and et-0/0/2 is not MVRP enabled. By configuration et-0/0/1 is part of MSTI-1 and et-0/0/2 is part of MSTI-2. MSTI-1 is running on vlan-100 and MSTI-2 is running on Vlan-200. R2 in this case, is advertising only vlan-100. The MVRP enabled interface will become part of all the MSTIs(MSTI-1 and MSTI-2 both) configured on the device and it will take part in the FSM of all the MSTIs. Although et-0/0/1 is not member interface of vlan-200(correspnding to MSTI-2). This potentially can cause a problem where et-0/0/1 although not a vlan-200 member, will go into FWD state and et-0/0/2, genuine member of vlan-200 goes into BLK state for MSTI-2. So, when traffic is received in vlan-200 it will be sent out of et-0/0/1, an it will be dropped.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

  • RPD process crash might be seen when the gRPC stack expects a 8 byte aligned memory but gets a 4 byte aligned memory instead. PR1692738

  • The BUM (Broadcast, Unknown Unicast, and Multicast) packets are getting dropped at egress processing on all MX platforms due to an interoperability issue of MPC1/MPC2/MPC3/MPC4/MPC5/MPC6/MPC7/MPC8/MPC9 with MPC10/MPC11/LC9600 line card. It is observed when equal-cost multipath (ECMP) is enabled for the load-sharing data for an incoming traffic destined to the neighbours. It can be seen with any ECMP traffic distribution configuration.PR1695438

  • FIPS mode is not supported in this release for SRXSME devices.PR1697999

  • On Junos OS Evolved Platforms, any UI (user interface) set (configuration, script, license) changes done post software addition were being lost after the subsequent reboot.PR1699699

  • When packets of size bigger than 1518 Bytes are received/transmitted, pps counter value does not show correct value. PR1700309

  • On MX Series platforms, traffic egressing on the IRB (Integrated Routing and Bridging) interface with the underlying L2 (layer2) access port has VLAN tags imposed incorrectly.PR1700321

  • 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

  • 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, Junos Telemetry interface thread takes more time in streaming of Junos Telemetry interface 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 the MX104 platform, the Wrong threshold-temperature is displayed.PR1713788

  • On all Junos and Junos OS Evolved platforms, due to a bug in route resolution over specific types of next hops, the route can resolve over itself and the nexthop chain keeps expanding. Due to this issue, the depth of recursion gets higher than supported and the KRT (Kernel Routing table) queue returns errors for nexthops. As a result, there will be incorrect route resolution, traffic loss and occasionally, the rpd (routing protocol deamon) crashes. The necessary configurations and conditions that will result in this issue are below 1. BGP (Border Gateway Protocol) Prefix-Independent Convergence (PIC) ("protect core") is configured and BGP receives same prefix from EBGP and IBGP neighbors 2. BGP LU (Labeled Unicast) with "protection" to create backup path to protect the active and BGP receives same prefix from EBGP and IBGP neighbors 3. Mutually recursive Route resolvability situations like Resolving using Default-route (not having proper resolution config)PR1716436

  • When NAT (Network Address Translation) is configured on interfaces along with sampling, the J-flow record will contain NAT'ed IP as opposed to the original IP.PR1716707

  • The fast-lookup-filter is not working on the router's loopback interface with MX10008 line cards in the routers. PR1718893

  • After deactivating an -lt interface with units that have CoS the interface cannot be reactivated. PR1722327

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

  • Service disruptions are seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.PR1727954

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

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


  • Earlier implementation of kvmclock with virtual dynamic shared object (vDSO) 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 launched. Thus, resulting in accurate clock initialization. PR1691036

Interfaces and Chassis

  • Logical interface packet counters are not implemented for AMS interface. It is a new change. Changes are planned for the Junos OS Release 22.4R2 and later. PR1673337

  • Error logs related to invalid anchor next hops are seen when the MPC10 and MPC11 FPCs are restarted with distributed aggregated Ethernet IRB VRRP sessions. The aggregated Ethernet must span multiple FPCs. PR1674069

  • Interface_check_up verification is not as expected on primary member of MX-VC setup. PR1686425

  • On all Junos OS platforms, while performing the Junos upgrade from the release before 20.4 to a higher version having an incorrect configuration may fail. This issue may lead to traffic loss or network outages.PR1692404

  • On Junos OS platforms with MPC line cards, negotiated interfaces will try to come up with the speed already negotiated instead of using the original interfaces speed even if re-negotiation happens like reinserting cable.PR1714267

Junos XML API and Scripting

  • L2TP LAC functionality do not work in this release. PR1642991

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


  • In MVPN Case, if the nexthop index of a group is not same between primary and secondary after a nsr switchover, we may see a packet loss of 250 to 400 ms. PR1561287

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

  • On all Junos OS and Junos OS Evolved platforms, if Circuit Cross-Connect (CCC) is configured to use a label-switched-path such as IGP routed, i.e., no-cspf and no strict explicit route object (ERO) configuration, then restarting egress CCC node or restarting FPC on the egress CCC node containing remote-interface-switch configuration multiple times might cause CCC to remain stuck in remote-if-down state, resulting in loss of traffic. (The configuration statement remote-interface-switch is configured on the egress LER of the Resource Reservation Protocol-Traffic Engineering label-switched-path (RSVP-TE LSP) which binds the LSP terminating on the node to a local interface.)PR1694777

Network Management and Monitoring

  • When you configure maximum-password-length and you try to configure password whose length exceeds the configured maximum-password-length, error is thrown, along with error 'ok' tag. (Ideally 'ok' tag should not be emitted in an error scenario.) The configuration will not get committed.PR1585855

  • In some NAPT44 and NAT64 scenarios, duplicate SESSION_CLOSE syslog is seen. PR1614358

Platform and Infrastructure

  • On all Junos OS and Junos OS Evolved platforms, while using source-address NTP configuration parameter and issue the command set ntp date from the CLI, packets will be sent with the source address of the outgoing interface rather than the manually configured IP address. Typically, the manually configured IP address would be a loopback address. The problem does not apply to automatically generated NTP poll packets. PR1545022

  • When the deactivate services rpm and deactivate routing-options rpm-tracking CLIs are applied together and then committed, some of the rpm tracked added routes are not deleted from the routing table. PR1597190

  • On all Junos OS platforms, if the interface configuration is altered to switch from one routing instance to another, it might result in closing of BGP session on the secondary Routing Engine.PR1700438

  • On Junos OS MX Series 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 OS MX Series and EX9200 devices with specific line cards, VLAN rewrites will not happen for traffic egressing from integrated routing and bridging (IRB) interface over an L2 aggregated Ethernet logical interface, if the L2 aggregated Ethernet is configured to perform VLAN rewrites on the frames. This happens when the IRB is configured as a routing-interface on Ethernet Virtual Private LAN (EVPN) or Virtual Extensible LAN (VXLAN) routing instances and the traffic has to egress on IRB over an L2 aggregated Ethernet logical interface. As a result, the frames are forwarded with incorrect VLAN tag information.PR1720772

  • Irrespective of ingress forwarding class configured and marked, all the TWAMP reflected packets are sent over the Q3(Network control). PR1722232

  • On all MX Series platforms, qualified-bum-pruning-mode completely blackholes VPLS (Virtual Private LAN Service) traffic with network-services configured in enhanced-ip mode.PR1731564

  • Heap memory leak on access MPCs used for subscriber termination may be observed in a subscriber-management environment.PR1732690

Routing Policy and Firewall Filters

  • Delete single prefix from prefix-list will cause all the prefixes to be deleted.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 Series routers, unexpected log message appears if the CLI command show version detail or request support information is executed. user@host> 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

  • On all Junos OS platforms, first time when ESIS is coming up, sometimes the ESIS route might not get installed. PR1559005

  • When l2cpd (in the context of xSTP) clears the entries that it has programmed on ppmd, that is, when you delete xSTP configurations from the box, there can be a possibility of generating ppmd core file. If ppmd is in distributed mode then there will be no service impact, else there can be service impact as packet transmission for various protocols will happen via if ppmd is in centralized mode.PR1660299

  • On all Junos OS and Junos OS Evolved platforms, when the shortest-path-first (SPF) algorithm for IS-IS is triggered frequently, CPU usage might increase and impact the device performance and traffic.PR1667575

  • Any platform with micro BFD configured on member links of the LAG or aggregated Ethernet interface, BFD session state in the Routing Engine remain UP always even if the PEER device is ceased. PR1675921

  • On all Junos OS and Junos OS Evolved platforms, the routing protocol daemon (rpd) can crash when protocol independent multicast (PIM), multicast only fast reroute (MoFRR) configuration is present. Some network churn event such as continuous interface cost changes, resulting in a change of active and backup path for Equal Cost Multi-Path (ECMP) occur. There will be service impact because of the rpd crash but the system self-recovers until the next crash.PR1676154

  • Junos OS Release 22.3 onwards, IS-IS yang is uplifted to 1.0.0 version which has major change in existing OC path that was supported earlier. The OC path change need to be 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 configuration is broken. eventually D27 code will come back to DCB and things will work fine after that. PR1686751

  • OSPF route type extended community cannot be configured as 'rte-type'. PR1687273

  • Secondary path is not found in ASBR6 MPLS table while verifying BGP multipath protection functionality. PR1691131

  • On all Junos OS and Junos OS Evolved platforms, you might see the BGP scheduler slip while deleting a large set of prefixes. PR1696870

  • On all Junos OS and Junos Evolved platforms, when IPv4 prefix advertisement received by an IS-IS/OSPF router in the Extended IP reachability TLV and SR mapping server (SRMS) advertisement for the same prefix received through the segment identifier (SID) label Binding TLV, then SRMS advertised label preferred over IS-IS/OSPF SID label advertised via opaque-AS Extended-Prefix. Traffic will be sent via wrong path due to this issue.PR1702456

  • Show route advertising-protocol bgp reporting next hop self rather than IP in the configured policy-statement for next-hop. Behavior change observed after upgrading Junos OS Release 18.4 to Junos OS Release 20.4. PR1712527

  • On all Junos OS and Junos OS 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

  • On all Junos OS and Junos OS Evolved platforms, if the proxy BGP (Border Gateway Protocol) route reflector is connected to the only peer present in the BGP group then it stops advertising the routes coming from the remote cluster and that leads to proxy route-target routes not getting added which causes traffic disruption.PR1728604

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. PR1660588


  • Tunnel debugging configuration is not synchronized to the backup node. It needs to be configured again after RG0 failover. PR1450393

  • Change here is basically reverting to old enum value used for ATM VPN, and using a new value for BGP multicast address family, and although there is no visible behavior change due to this, there may be impact on ISSU for ATMVPN and BGP multicast address family if enabled.PR1590331

  • 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 are not be received by the group member since the key server might have removed the member from registered members list. PR1608290

  • The rpd crashes when multicast virtual private network (MVPN ) is configured with separate route-targets scenario. PR1700345

  • The pseudowire interfaces are not showing up after performing Routing Engine switchover on all Junos OS and Junos OS Evolved platforms. PR1708572