Article Detail

Alert Type

PSN - Product Support Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

Junos Software Service Release version 21.2R3-S3 is now available for download from the Junos software download site

Download Junos Software Service Release:

Go to Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts

Solution

Junos Software service Release version 21.2R3-S3 is now available.

21.2R3-S3 - List of Fixed issues

PR Number	Synopsis	Category: Software build tools (packaging, makefiles, et. al.)
1641712	Enhanced subscriber management might not work when Junos is installed using USB image Product-Group=junos	On all Junos platforms, USB installation fails to bring up subscriber daemons while installing Junos via USB. Subscriber daemons keep crashing and never bring up subscribers. It impacts enhanced subscriber management services.
PR Number	Synopsis	Category: EX2300/3400 PFE
1647209	DHCP traffic might be dropped when DHCP-security and RTG are enabled Product-Group=junos	On EX2300, EX2300-48MP, and EX3400 platforms, when DHCP-security and Redundant Trunk Group (RTG) are enabled clients connected over RTG might not get DHCP IP and DHCP traffic might be dropped.
1678430	AE interface will receive unknown unicast traffic on FPC3 reboot of a VC Product-Group=junos	On VC (Virtual Chassis) supporting EX and QFX platforms, having VC of 4 or more nodes, with an AE (Aggregated Ethernet) interface connected to other VC members, if FPC3 (Flexible PIC Concentrator) of VC is rebooted, unknown unicast traffic will be received on the AE interface.
1679094	DHCP binding will fail for the clients (Clients connected on an AE interface with 2 or more VLANs) on a VLAN where DHCP security is not configured Product-Group=junos	On Junos EX2300, EX3400, and EX4300-MP, DHCP (Dynamic Host Configuration Protocol) binding will fail for clients on a VLAN where DHCP security is not configured. This is seen when an Aggregated Ethernet (AE) interface has two or more VLANs, and DHCP security is configured on only one interface DHCP security is not configured on the other VLAN.
1685938	MAC address learning might not happen on specific EX/QFX platforms Product-Group=junos	On specific EX/QFX platforms (EX2300/EX3400/EX4300-MP/EX4100/EX4400/QFX5K), MAC learning is not happening in any of the interfaces of the particular VLAN (contains both LAG (Link Aggregation Group) and non-LAG interfaces) when VSTP (VLAN Spanning Tree Protocol) is enabled on LAG interface with no child interface and VSTP is disabled for non-LAG interfaces. It causes a traffic impact as mac address learning does not happen for all interfaces on the VLAN.
PR Number	Synopsis	Category: EX2300/3400 platform
1667564	High numbers of PDs connected may result in high CPU utilization Product-Group=junos	On EX2300 and EX3400 platforms, high CPU utilization may be observed when more PoE devices (more than 25 PDs) are connected to the switch.
PR Number	Synopsis	Category: NFX Series Platform Software
1674872	VNF's Getting DHCP Address from virbr0 with Default Route Product-Group=junosvae	VNF with DHCP configured on virbr0 is getting a default route and it should not
PR Number	Synopsis	Category: QFX Multichassis Link Aggregrate
1579016	VRRP flaps between MC-LAG peers Product-Group=junos	On all Junos platforms, On deletion/addition of MC-AE (Multi Chassis Aggregated Ethernet ) IFD (Interface Device), VRRP (Virtual Router Redundancy Protocol) flaps between the MC-LAG peers.
1648271	Incorrect configuration and rollback might cause issues with ARP learning between ICL interface and local MC-AE interfaces Product-Group=junos	On all Junos platforms, there might be an issue with ARP learning between ICL interface and local MC-AE interfaces when an MC-AE device is misconfigured and the configuration is rolledback using "rollback" command. This issue could result in packet drop.
PR Number	Synopsis	Category: SPC3 HW and SW Issues
1641793	Traffic might be dropped due to the RX queue being full Product-Group=junos	Incoming packets might be sent to RX queues of core0 or core14 mistakenly, might result in the queue buffer full and the packets getting dropped.
PR Number	Synopsis	Category: ChassisD changes specific for ACX series
1643989	The copper ports on ACX5448 might go down if loaded with copper SFP Product-Group=junos	On ACX5448 platforms, if the device is loaded with copper SFPs (1G-SFP-T), in certain situations copper ports might be down without any notice. If this issue is hit, traffic through that interface would be blackholed.
PR Number	Synopsis	Category: ACX MPLS
1665178	ACX5048 after upgrade to 20.4R3-S3 VPLS multihoming is not working Product-Group=junos	In VPLS MH cases, the standby UNI ifl in backup router will be programmed in disable state, by adding the UNI interface to invalid vpn id in HW. During switch over the UNI ifl will be deleted and will be added under the VPLS instance VPN id. In issue case, UNI interface added under invalid VPN id in backup router is tried to deleted by passing the VPLS instance vpn id, causing the issue. This issue is applicable only for ACX5k series.
PR Number	Synopsis	Category: MX YT-ZF Linecards Interface Software Category
1670685	On MX platforms, back to back modification of the Interface profile results in ports not coming up Product-Group=junos	On MX platforms with line cards MPC11E, MX10K-LC9600 configured, the physical interface-related object remains unpublished and thus channel remains stuck in a chan_deleting state.
PR Number	Synopsis	Category: Category for tracking AMR related issues.
1643570	AMR first session traffic is not copying over multiple paths for v6 traffic over v6 ipsec tunnel mode Product-Group=junos	AMR when it is enabled in non-cso v6 over v6 mode with IPSEC tunnels, the first session after reboot or forward restart, will not have multipath treatment, post that the feature works fine.
PR Number	Synopsis	Category: a20a40 specific issue
1642138	Missing boot parameters on Junos SRX5K platforms will result in fabric plane CRC link errors Product-Group=junos	Fabric plane link CRC errors are detected on Junos SRX5K platforms which can cause an HA switchover and in worst case scenario, throughput issues for user traffic. The hardware error message "Minor CB (Control Board) Fabric Chip Not Online" is displayed and is caused by fabric plane CRC error like "FPC plane CRC link error". The issue happens in HA (High Availability) scenario with SCB4 (Switch Control Board) and IOC3 (Input Output, I/O) cards in use.
PR Number	Synopsis	Category: BBE Advanced Services related issues
1657027	The mspmand will crash when service-set is configured with syslog and SSL Product-Group=junos	On all Junos platforms, when service-set is configured with syslog and SSL (secure Syslog), multiservices PIC manager daemon (mspmand) will crash and might cause traffic disruption.
PR Number	Synopsis	Category: BBE database related issues
1648565	MX960 :: bbe-statsd core observed at vlogging,smid_reregister, sdb_db_check,Juniper: :SmidInterface:: isReady in bbe-smgd daemon restart test Product-Group=junos	During bbe-smgd daemon restart there is a small window during which requests for subscriber statistics results in bbe-statsd daemon core. There is no functional impact as the system returns to normal after both daemons finally restart.
PR Number	Synopsis	Category: BBE interface related issues
1663689	Subscribers will be stuck in the initializing or terminating state Product-Group=junos	On all MX platforms with Enhanced subscriber-management configured, subscribers can get stuck in the initializing and terminating state during the stress test( Graceful switchover(GRES)/FPC Restart/Daemons restart).
PR Number	Synopsis	Category: BBE Statistics daemon & libraries
1676049	Minor memory leak in 'bbe-statsd' daemon may be seen when subscriber-management is enabled on MX platforms Product-Group=junos	On MX platforms, a minor memory leak may be seen over time for transient subscriber sessions which last for around 30 seconds or less. The issue is reproducible consistently and may result in 'bbe-statsd' daemon crash over time.
PR Number	Synopsis	Category: Border Gateway Protocol
1648471	An RPD crash was observed on all Junos platforms Product-Group=junos	An rpd crash might be observed on all Junos platforms once the RPKI configuration is activated along with BGP SRv6 at the same time.
1659441	Routing Process Daemon (rpd) crashes and restarts when a specific timing condition is hit with BGP configuration Product-Group=junos	On all Junos platforms and all Junos Evolved platforms, Routing Process Daemon (rpd) crashes and restarts when BGP (Border Gateway Protocol) is configured and a specific timing condition is hit for secondary route. This issue might cause a traffic impact.
1665610	BGP labeled-unicast inactive routes might not be advertised when add-path is configured Product-Group=junos	On all Junos and Junos Evolved platforms, by default, inactive routes from inet.3 are advertised in BGP. When add-path is configured, inactive routes from inet.3 are no longer advertised, this behavior is unexpected.
1669716	The rpd crash is observed while making configurational changes Product-Group=junos	On all Junos and Junos Evolved platforms, which supports protocol BGP (Border Gateway Protocol), RPD (Routing Protocol daemon) crash is seen when a eBGP peering interface is moved to a "no-forwarding" instance and resetting the BGP peer.
1669930	BGP inactive routes may not be advertised to peers in BGP-LU scenario Product-Group=junos	If BGP-LU(labeled-unicast) is configured using "rib inet.3/inet6.3" address family, BGP inactive routes are not re-distributed to BGP-LU peers, leading to improper traffic patterns.
1677935	Inter-domain forwarding connectivity will be broken between different lo0s in the option-C network causing problems for the MPLS transit-route Product-Group=junos	On all Junos and Evolved platforms, having BGP Labeled-Unicast (BGP-LU) and non-BGP route for same prefix/lo0 (loopback interface) and readvertising non-BGP active route for this prefix in BGP-LU, cause problems for MPLS transit-route.
1680360	InboundConvergencePending flag is set after RE switchover Product-Group=junos	When the BGP EOR update is received, the BGP flag "InboundConvergencePending" should be cleared on both master and backup RE. However, after performing RE switchover, the flag "InboundConvergencePending" might be re-set on master or backup RE, which is unexpected. The potential impact may be seen ONLY when BGP multipath is used. The multipath calculation may not start or stop as expected.
PR Number	Synopsis	Category: BBE Remote Access Server
1669284	Errors are seen when the accounting server source address is IPv6 Product-Group=junos	On all Junos platforms having a profile assigned to the RI (Routing Instance) and using a source IPv6 (Internet Protocol version6) address for the radius server, errors might be observed and the accounting services might not work in an expected manner.
1687998	The authd process crashes during GRES recovery phase Product-Group=junos	On MX platforms, during recovery phase of Graceful Routing Engine Switchover (GRES), authd process crashes.
PR Number	Synopsis	Category: Express BT PFE L3 Features
1658839	The packetio may core when router reboot or FPC reboot is triggered Product-Group=junos	In case the main thread of packetio terminates, but AppService thread is still running, it may try to access global objects that might have been freed on termination of the main thread might result in packetio PFE process core.
PR Number	Synopsis	Category: MX Platform SW - FRU Management
1676008	MPC stuck in present state with log " graceful offline in progress, returning false" flooding Product-Group=junos	In over temperature situation, there will be a 10s timer before device bring the FPC down . However in some situation due to high temperature, a FPC offline action will be triggered before the 10s timer expires. Then the FPC will stuck in Present/Announce offline state. Cli offline/online it or physical reseat will not be able to recover the issue. When the issue happening, you may observe log message " graceful offline in progress, returning false" flooding: <<< fpc_ok_to_start_generic: [FPC 0] gracefull offline in progress, returning false fpc_ok_to_start_generic: [FPC 0] gracefull offline in progress, returning false <<< Below MPCs are affected by this issue: MPC7/8/9 MPC10 MPC11 LC480 LC2101 LC9600 LC304 LC4800 FPC-P2, FPC-P3
PR Number	Synopsis	Category: PRs related to DS3/E3 mics
1688315	A kernel crash can be seen with MIC-3D-8DS3-E3 installed Product-Group=junos	On Junos MX platforms which support MIC (Modular Interface Card)-3D-8DS3-E3 a kernel crash can be seen when the configuration 'interface-type t3 and framing type e3' is present on the device. There will be an impact on data services when this issue is encountered and to avoid the issue the framing type configuration should be changed to t3.
PR Number	Synopsis	Category: Class of Service
1604943	IEEE 802.1 rewrite rule might not work on MPC10 linecard Product-Group=junos	On MX platforms with MPC10/MPC11 linecard, if Class-of-Service (CoS) ieee-802.1 rewrite rule is applied on Aggregated Ethernet (AE) interface with vlan-ccc encapsulation, the rewrite rule might not work as expected due to this issue.
1675781	QoS may not work as expected on AE interfaces with explicit-null label Product-Group=junos	On all Junos platforms having explicit-null label along with other labels, the QoS (Quality of Service) may not work in an expected manner for AE(Aggregated Ethernet) interfaces. This is because AE interfaces do not consider the explicit-null label which carries the exp bits and thus the exp bits carried are not considered for classification by PHP (Penultimate Hop Popping) router.
PR Number	Synopsis	Category: Enhanced Broadband Edge support for cos
1684019	Traffic would hit wrong queue post ISSU Product-Group=junos	On all MX platforms configured with Class-of-Service scheduler maps, after In-Service Software Upgrade (ISSU) the scheduler map does not have the right queue mapping and the traffic would be mapped to the wrong queue leading to traffic loss.
PR Number	Synopsis	Category: QFX Control Plane VXLAN
1648368	The spine might have stale vtep entry for the ESI even though the host mac is not advertised by the leaf Product-Group=junos	On all Junos and Junos OS Evolved platforms configured with EVPN-VXLAN, if an Ethernet Segment Identifier (ESI) link towards a multihomed CE experiences a quick down->up->down transition on a leaf, a remote Ethernet VPN (EVPN) peer might continue to install the Virtual Extensible LAN (VXLAN) tunnel (vtep) towards the affected leaf or the failed device in its ESI next-hop, resulting in traffic drops on the leaf.
PR Number	Synopsis	Category: Firewall Filter
1647669	mib2d core hitting @mib2d_fwstats_async_handler_cb rtslib_async_process_msg during GRES testing with page pooling enabled Product-Group=junos	mib2d core hitting @mib2d_fwstats_async_handler_cb rtslib_async_process_msg during GRES testing with page pooling enabled
1662955	The MPC/FPC crash is seen on specific LC's running BGP Flowspec Product-Group=junos	On Junos platforms with specific MPC/FPC model, crash may happen in certain scenario with BGP flowspec. With the BGP flowspec filter, the scaled prefix-list spread across the terms with a total prefix-list-scale. While processing the BGP flowspec filter with scale, it takes almost 6 minutes to consume the filter into ASIC during convergence. Since the PFE has a time max limit which is lesser than 6 scaled convergence time, PFE crash happens during the threshold handler. This causes the services or traffic impact running through the FPC until the FPC comes online and configurations are converged again.
1670622	Traffic loss may be observed when changing firewall configuration Product-Group=junos	On MX platforms supporting MPC7/8/9 line cards, traffic loss may be observed if the firewall configuration changes are made when PFE 0 (Packet Forwarding Engine) is in a disabled state. It is a rare occurrence.
PR Number	Synopsis	Category: EVPN ELAN/E-TREE
1638421	The ARP request packets might be sent out from ACX router without VLAN header Product-Group=junos	On ACX5448 and ACX710 platforms, the ARP request packets might be sent out from ACX router without vlan header when an EVPN instance is configured with vlan-id none. Since the targeted ARP request packet generated in ACX doesn't have VLAN header, this ARP request packet gets dropped in peer node. This continues to happen till the ARP entry ages out. Once ARP entry ages out, the entry gets deleted from ARP table.
PR Number	Synopsis	Category: ACX IRB specific issues
1683770	On the ACX710 router, the IEEE 802.1p priority and DEI values in the locally generated VLAN-based IP packets might be changed when sourced from the IRB interface. Product-Group=junos	On ACX710, when locally generated VLAN-based IP packets (e.g. ping packet) are sourced from IRB interface, the Priority and DEI bits may be changed in PFE.
PR Number	Synopsis	Category: DNX L2 related features
1662686	After activating EVPN-ETREE service on ACX5448 pfe may crash Product-Group=junos	On ACX5448 platform after add some EVPN-ETREE services/interfaces the riofeb (pfe) process may crash and 'dnx_rt_vpls_rebake_flood_route' and 'dnx_nh_composite_handle_flood_nh_change' logs will be seen. "show vmhost crash" will show riofeb coredumps.
PR Number	Synopsis	Category: ACX IFL, IFF creation
1638581	L3 interface creation may fail on the ACX5448 and ACX710 platforms Product-Group=junos	On the ACX5448 and ACX710 platforms, Layer 3 interface creation may fail due to a base MAC address programmed on the PFE. As a result, the simplest symptom is ping failure.
PR Number	Synopsis	Category: ACX VxLAN Issue
1665828	MAC-IP bindings for IPv4 (ARP) and IPv6 (ND) may not be processed for IRB interfaces in an EVPN scenario Product-Group=junos	On all Junos and Junos Evolved platforms, when EVPN (Ethernet Virtual Private Network) related configuration is introduced from baseline, due to a rare timing issue between the IRB (Integrated Routing and Bridging) interfaces coming up and an attempt is made by the 'l2ald' (l2 address learning) daemon to process the corresponding MAC-IP entries, this issue may occur. This may also occur when IRB logical units are activated and deactivated.
PR Number	Synopsis	Category: Covers Application classification workflows apart from custo
1632205	Signature package update may fail and the appid process may crash on SRX devices Product-Group=junos	On SRX platforms, with a sig-pack update if any application is moved to DEPRICATED and if that application was part of any custom group, signature upgrade may fail. Due to this sometimes the appid process may crash.
PR Number	Synopsis	Category: EA chip ( MQSS SW issues )
1612201	Reclassify MQSS_CMERROR_CELL_MEM_PROTECT_FSET_REG_DETECTED_FBM_MEM from Major to Minor Product-Group=junos	Some error events did not have persistent packet forwarding impact and had been reclassified from Major to Minor. All Major events per default trigger a disable-pfe action.
PR Number	Synopsis	Category: FIB telemetry, fibtd, libocaft repositories
1662999	network-instance name for streaming telemetry to be changed from default to DEFAULT to align with CONFIG stanza Product-Group=junos	for ONDATRA test case which tested this with different network-instance names - DEFAULT. test is failing. for TEST to pass ,use network-instance names - default.
PR Number	Synopsis	Category: Distributor related issues
1658426	Routes in RIB and FIB table may go out of sync on all Junos Evolved platforms and causes a traffic impact Product-Group=junos	On all Junos evolved platforms, routes in RIB (Routing Information Base) and FIB (Forwarding Information Base) are not in sync when it is running over long period of the time (200+ days) with a constant route churn. It causes a traffic impact due to stale entries.
PR Number	Synopsis	Category: EVPN control plane issues
1659786	The process rpd might crash when protocol EVPN is deactivated Product-Group=junos	On all Junos and Junos OS Evolved platforms, with multiple activating/deactivating Ethernet Virtual Private Network (EVPN) or deactivating the Virtual Routing and Forwarding (VRF) instance with protocols EVPN for type 5 route, the process rpd might crash.
1680421	EVPN MPLS traffic drop can be observed in a multi-vendor PE CE setup with single-active LAG Product-Group=junos	On all Junos platforms running EVPN (Ethernet Virtual Private Network) MPLS (Multi-Protocol Labeled Switching) and a single active LAG (Link Aggregation), the traffic can get forwarded to the NDF (Non-Designed Forwarder) router which can lead to a traffic drop. This issue is seen in multi-vendor PE (Provider Edge) CE (Customer Edge) setup when there is a DF switchover i.e DF (Designated Forwarder) role changes and the backup router starts advertising the EVPN type 2 route, now there is another switchover and the old DF again becomes the DF and advertises EVPN type 1 route but the NDF does not withdraw its route consequently the traffic gets forwarded to the NDF.
PR Number	Synopsis	Category: EVPN Layer-2 Forwarding
1677521	The ARP/ND entries are not relearnt as expected on the spine with EVPN-VxLAN Product-Group=junos	On the spine node of the EVPN-VxLAN scenario, after the initial learning of an ARP(Address Resolution Protocol) or ND (Neighbor Discovery) entry has timed out, the node may not learn that entry again.
PR Number	Synopsis	Category: EX4400 platform
1662288	LEDs on ports 0-35 are always lit on EX4400-48MP platforms Product-Group=junos	On EX4400-48MP platforms running Junos, Link LEDs on ports 0-35 are always lit, even if there are no cables connected.
PR Number	Synopsis	Category: Express PFE FW Features
1651546	Transit traffic might get dropped and protocols might be down when firewall filters are modified Product-Group=junos	On all PTX and QFX platforms except QFX5k, a change operation in firewall filters might lead to drops observed in transit packets. When the issue hits, we might face connectivity issues and protocols going down. This is a timing issue and hard to reproduce.
PR Number	Synopsis	Category: Express PFE including evpn, vxlan
1674116	The BFD packets will drop in an EVPN-VxLAN scenario due to incorrect layer3 offset being set in the host path Product-Group=junos	On all QFX10000-60C platforms with Ethernet VPN-Virtual Extensible LAN (EVPN-VxLAN) scenario, the Bidirectional Forwarding Detection (BFD) packets are getting classified as packets of different protocols like Virtual Router Redundancy Protocol (VRRP), depending on the value at an incorrect offset which leads to BFD packet drop.
PR Number	Synopsis	Category: Express PFE L2 fwding Features
1659732	On QFX10K Junos platforms configuration of IGMP group range might result in traffic loss Product-Group=junos	On QFX10K Junos platforms, the configuration of the IGMP group range might result in a specific multicast route getting programmed and this might cause traffic loss.
PR Number	Synopsis	Category: Express PFE MPLS Features
1590387	ISIS adjacency is not coming up through TCC l2circuit Product-Group=junos	On ACX/PTX/QFX platforms(PTX10002/10003/10008/10016/QFX10002/10003/10008/10016/ACX6360) if protocols l2circuit and channel tcc is enabled for providing layer 2 transaction, ISIS connection through the layer 2 domain might get failed and traffic loss might be seen.
1618019	Junos OS: QFX10000 Series: In IP/MPLS PHP node scenarios upon receipt of certain crafted packets multiple interfaces in LAG configurations may detach. (CVE-2022-22223) Product-Group=junos	On QFX10000 Series devices using Juniper Networks Junos OS when configured as transit IP/MPLS penultimate hop popping (PHP) nodes with link aggregation group (LAG) interfaces, an Improper Validation of Specified Index, Position, or Offset in Input weakness allows an attacker sending certain IP packets to cause multiple interfaces in the LAG to detach causing a Denial of Service (DoS) condition. Please refer to https://kb.juniper.net/JSA69873 [juniper.net] for more information.
1651703	The traffic with ether type 0X88FC might get corrupted Product-Group=junos	On all Junos platforms, with the L2 circuit configuration when the ether type in the incoming packet is 0x88FC is not added to the known ether type list in ASIC for which traffic might get corrupted.
PR Number	Synopsis	Category: Express ASIC interface
1669267	PCS errored blocks count increments on PTX3000/PTX5000 after Junos software upgrade Product-Group=junos	On PTX platforms, packets drop is seen because of increment in PCS and framing errors on some of the 100GE ports on PIC or its peer devices after firmware migration.
PR Number	Synopsis	Category: SRX4100/SRX4200 platform software
1626562	A major alarm DPDK (data plane development kit) Tx stuck issue of SRX4100/4200 Product-Group=junos	On the SRX4100 and SRX4200 platforms, it can detect DPDK (data plane development kit) Tx stuck issue and trigger a major chassis alarm goes which might trigger RG1 failover to the healthy node. A DPDK reset will be triggered only to the stuck port and if the reset resolves the tx stuck issue, the major chassis alarm will go off.
1650112	Packet loss might be seen on SRX4100 and SRX4200 devices from 20.2R2 Product-Group=junosvae	Packet loss might be seen on SRX4100 and SRX4200 devices from 20.2R2
PR Number	Synopsis	Category: BSDX Software installation issues
1665411	JDI-RCT:M/Mx: errors spew on junos upgrade @ rm: //opt/sdk/service-packages/...: is a directory Product-Group=junos	A harmless error from activation of jservices packages
PR Number	Synopsis	Category: Integrated Routing & Bridging (IRB) module
1660208	After changing the MTU on an aggregated interface along with IRB the kernel crash might be observed Product-Group=junos	The kernel crash might be observed after changing the MTU on an aggregated interface along with integrated routing and bridging (IRB) on all Junos platforms.
PR Number	Synopsis	Category: ISIS routing protocol
1682778	The rpd process will crash and generate core post graceful restart Product-Group=junos	The rpd process crash is seen when a graceful rpd restart is initiated and ISIS auto-bandwidth is not configured in the system.
PR Number	Synopsis	Category: jdhcpd daemon
1676573	The DHCP unicast acknowledge packet might be dropped Product-Group=junos	On all Junos platforms configured with forward-only and server-id override under DHCP Relay, the DHCP unicast acknowledge packet from the server will be dropped for the DHCP Request from the client for renewing lease or reconnection.
PR Number	Synopsis	Category: jl2tpd daemon
1667950	VMcore or RE crash might be triggered due to the memory corruption when the FPC is restarted for LNS subscribers Product-Group=junos	On all MX platforms, when Flexible PIC Concentrators (FPCs) restart for L2TP network server (LNS) subscribers stacked over aggregated service interface (asi) and LNS subscribers belong to more than one routing instance causes the VMcore or Routing Engine (RE) crash and brings down all the traffic.
PR Number	Synopsis	Category: Adresses ALG issues found in JSF
1677554	SIP 200 OK(INVITE) response packets are dropped leading to SIP Call failure Product-Group=junos	On SRX and MX platforms with SIP (Session Initiation Protocol) ALG (Application Layer Gateway) configured, SIP call failure is observed due to SIP 200 OK(INVITE) response packets being dropped.
1686613	SIP calls are getting dropped due to NAT failure and SIP ALG is enabled Product-Group=junos	On all MX and SRX platforms which support the SIP ALG (Session Initiation Protocol Application Layer Gateway) feature, SIP calls are getting dropped due to NAT (Network Address Translation) failure and failure to allocate XLATE context. The issue happens when there are multiple SIP INVITEs with different media IPs that arrive on the same SIP call. The drop is seen from the 4th SIP INVITE packet onwards.
PR Number	Synopsis	Category: Flow Module
1629216	The hardware acceleration flag was not properly updated on RT_FLOW_SESSION_CLOSE logs. Additionally, the values for "Services-offload-sessions" for customers using SPC2's in their SRX5000-Series devices was incorrect. Product-Group=junos	The hardware acceleration flag was not properly updated on RT_FLOW_SESSION_CLOSE logs. Additionally, the values for "Services-offload-sessions" for customers using SPC2's in their SRX5000-Series devices was incorrect.
1688658	The flow sessions traversing the IOC2 card would time out early when Automated Express Path is enabled Product-Group=junos	On SRX5K series devices with IOC2 line-cards installed, when running JUNOS 21.2R1 or later where Automated Express Path is enabled by default, sessions traversing the IOC2 card would time out early, leading to a traffic loss and unpredictable flow behavior.
PR Number	Synopsis	Category: SRX Firewall Authentication
1672378	The Forwarding plane crashes during HA failover Product-Group=junos	On SRX platforms with firewall authentication feature enabled, the forwarding plane could crash during HA (High Availability) failover.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
1632466	The BFD session might fail and not come up when it is modified with the expiry timer of more than 10 seconds Product-Group=junos	On a few SRX series platforms, when an existing BFD (Bidirectional Forwarding Detection) session is modified with the expiry timer set to greater than 10 seconds, the modification of the BFD timer may fail and the BFD session would stay down. There will be traffic disruption when the issue happens.
1651501	A hardware issue is detected on the RG-0 primary node's CP Product-Group=junos	On all SRX 5K products, when the chassis cluster is configured and there's a hardware issue with the CP (Central Point), failover might not happen correctly.
PR Number	Synopsis	Category: l2 flow module
1599891	OSPF neighbor won't establish under Transparent mode when neighborship across different zone Product-Group=junos	Some of the OSPF neighborship might not able to establish after system bootup when the neigborship connect to SRX via different zone under transparent mode
PR Number	Synopsis	Category: Firewall Policy
1669386	Security policy state may be invalid on SRX platforms Product-Group=junos	On SRX platforms, when dynamic-application-group and all the internal applications in that group are configured separately on the security policy, that security policy state may become invalid.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1673391	High Control Plane CPU utilisation while the kmd process is stuck after the core file Product-Group=junos	On all SRX platforms, during key management (kmd) core file, with VPN/Internet Key Exchange (IKE) implemented and a high number of file descriptors open, the kmd process will reach above 80% CPU utilisation and stay for a long period of time if the kmd process is stuck after the core file is generated.
PR Number	Synopsis	Category: Security platform jweb support
1681549	All the security policies on Junos SRX platforms can get deleted while trying to delete any particular policy via J-Web Product-Group=junos	On Junos SRX platforms, all the security policies under the 'security' hierarchy can get deleted while trying to delete a specific policy by applying a search filter via the J-Web interface. This issue is seen in Junos release 20.3R1 and above and results in traffic loss due to the deletion of policies.
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1664955	MAC addresses learned on the RTG interface are not aging out Product-Group=junos	On Junos EX/NFX/QFX platforms, stale MAC addresses entry not getting removed for RTG (Redundant trunk groups) interfaces.
1667310	H-VPLS traffic blackhole when mesh group local-switching is disabled Product-Group=junos	On all Junos and Evolved platforms, disabling the mesh group local-switching will lead H-VPLS (Hierarchical Virtual Private LAN Service) traffic drop.
1675861	Traffic flow will be affected as interfaces will be removed from VLAN Product-Group=junos	On all Junos and Junos-Evolved platforms, when both vlan name (vlan name having vlan-id-list under "edit vlans" hierarchy) and vlan-id-list having overlapping vlan IDs are added to the interface, traffic will be affected when the vlan name is deleted from the interface.
PR Number	Synopsis	Category: Label Distribution Protocol
1671187	LDP Traffic will be blackholed when the L-ISIS/L-OSPF route changes due to interface level configuration Product-Group=junos	On all Junos and Junos Evolved platforms running Segment Routing (SR), with "set protocols ldp sr-mapping-client" configured, and when interface level configuration changes are done leading to Labeled-ISIS /Labeled-OSPF route change, Labeled Distribution Protocol (LDP) traffic will be blackholed.
1680574	In an LDP -> BGP LU stitching scenario, Multiple LSPs will not be installed in the forwarding table, even if BGP Multipath and ECMP are enabled Product-Group=junos	On all Junos and Junos OS Evolved Platforms, when BGP LU (Labeled Unicast) routes are exported to LDP (Label Distribution Protocol) to perform LDP->BGP-LU stitching, LDP installs only one NH(Next Hop) in the forwarding table instead of multiple NHs, even when BGP Multipath and ECMP are enabled. This issue will be seen for both EBGP (External Border Gateway Protocol) and IBGP (Internal Border Gateway Protocol) multipaths on PTX platforms and for only iBGP multipaths on all other platforms.
PR Number	Synopsis	Category: Issues related to Junos licensing infrastructure
1684842	Licenses on the device might become invalid when the device is upgraded from a legacy licensing-based release to an Agile licensing-based release Product-Group=junos
PR Number	Synopsis	Category: Platform issues specific to MS-MPC (XLP)
1681624	Fabric Plane check/error alarm would be seen due to the burst traffic in MS-MPC line cards Product-Group=junos	On MX2008 platforms, when the overrun interrupt is set in Multiservices Modular PIC Concentrator (MS-MPC) line cards Fabric Plane check/error alarm would be observed. Latency difference between the SFB2/SFB3 and the MS-MPC cards with burst traffic potentially causes overruns as a result the fabric planes get stuck into the check state. It is a timing issue.
PR Number	Synopsis	Category: SW PRs for MPC10E Fabric
1676777	Traffic drop can be seen on MX platforms with MPC10E-10C line card Product-Group=junos	On MX platforms with MPC10E-10C line card, with line rate traffic, continuous traffic drop can be seen when fabric mode is changed from increased bandwidth to redundant.
PR Number	Synopsis	Category: MPC11 ULC interface software related issues.
1669333	UDP: optics sensor data missing snmp_if_index under Optics_diag Product-Group=junos	snmp_index for an interface on ULC based line cards (such as MPC11, LC9600 & MX304) will not be exported over the telemetry.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1655031	The rpd core is seen due to ted-export and ted database out of sync Product-Group=junos	On all Junos and Junos OS Evolved platforms, rpd core is hit when the events for deleting prefixes, sids, links and nodes come in out of order which occasionally leads to ted-export and ted database out of sync.
1672804	The rpd crash might be observed with Container LSPs Product-Group=junos	On all Junos/EVO platforms, the rpd process might get crash if the Container LSP (Label Switch Path) is associated with an external-controller.
1673348	CPU utilization of rpd process may reach 100% while reporting LSP states to pccd if the IS-IS update churn is high Product-Group=junos	On all Junos and Junos Evolved platforms where PCEP (Path Computation Element Protocol) is provisioned, after IS-IS (Intermediate System-Intermediate System) PDU (Protocol Data Unit) flooding, rpd (routing protocol daemon) re-computes LSPs (Label Switched Path) and sends those to the pccd (path computation client daemon) which in turn reports those to PCE (Path Computation Element) for processing. If the update churn is high, this may cause the rpd to reach or get stuck at 100% CPU utilization.
PR Number	Synopsis	Category: For multicast snooping on MX
1636261	Message 'Initialize libjtask-license first! for mcsnoopd' is seen after committing configuration Product-Group=junos	On all Junos platforms, a harmless message is observed on the terminal output after committing the multicast snooping configuration.
1637090	An IGMPv2 snooping proxy will originate IGMPv3 membership for a new group join request towards a multicast router Product-Group=junos	On all MX platforms, in an IGMPv2-only (Internet Group Management Protocol) environment with two queriers (multicast router or switch), the IGMP snooping proxy device will originate an IGMPv3 membership request to join a new group towards a router, upon receiving the IGMPv2 query. The default IGMP query interval is 125 seconds. However, in the presence of two queriers, the IGMP proxy calculates the query interval based on the difference between queries received from the two queriers. This would cause issues in join/leave requests.
1672488	MCSNOOPD will be restarted and will again learn the states after core Product-Group=junos	On all JUNOS and EVO platforms, with IGMP/MLD with EVPN configured.
PR Number	Synopsis	Category: Multicast for L3VPNs
1652481	MVPN Inter-AS option B shows updated PMSI attribute tunnel id when advertising type-3 routes to Intra-AS PE Product-Group=junos	PMSI attribute should be changed when sending Multicast VPN auto-discovery(AD) route from one region to other (here region referred to BGP groups in Multicast VPN) or in case it is sent to External Border Gateway Protocol (EBGP) peer or from EBGP to Internal Border Gateway Protocol (IBGP) peer. For IBGP to IBGP in case of RR (Route Reflector), ideally it should just reflect the route and not change PMSI attribute. Hence change in PMSI may result into traffic drop for internal RR clients.
1675099	The multicast receiver receives no traffic in an extranet scenario having an SPT tree already established Product-Group=junos	On Junos and Junos Evolved MX/PTX platforms, if the SPT (Shortest-Path Tree) tree is already established on PE (Provider Edge) it sends (s,g,rpt) prune which will lead to no traffic to the multicast receiver in an extranet scenario.
PR Number	Synopsis	Category: MX Timing software
1632632	SyncE clock might get stuck in holdover state Product-Group=junos	On MX platforms with PTP (Precision Time Protocol) hybrid mode configured on AE (Aggregate Ethernet) interfaces, if clock mode is reconfigured from PTP hybrid to plain SyncE (Synchronous Ethernet), SyncE clock might get stuck at holdover state and thus affects clock functionality.
PR Number	Synopsis	Category: MX10K platform
1655089	The 1G port always stays down while changing of 10G interface lane speed to 1G Product-Group=junos	Due to an incorrect hardware setting, the 1G port stays down while changing of 10G interface lane speed to 1G and vice versa on LC2101.
PR Number	Synopsis	Category: Category for tracking Olympus-MX issues
1671649	Traffic loss seen due to SPC3's packets getting stuck Product-Group=junos	On Junos MX960, MX480 platforms, Flowd restart or PIC offline/online( Physical Interface Cards) causes SPC3's sending of packets to get stuck.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1668090	Junos upgrade might fail due to file system corruption Product-Group=junos	On all Junos platforms, file system corruption can result in a corrupted package/db which might lead to an upgrade failure.
1681783	On Ex4400 upgrade failure happens when upgrading through a USB drive. Product-Group=junos	On EX4400 upgrade failure happens when upgrading through a USB drive.
PR Number	Synopsis	Category: Kernel MPLS / Tag / P2MP Infrastructure
1681892	The RE crashes when MPLS next-hop is created and deleted frequently Product-Group=junos	On all Junos platforms, when the system is up for a very long time, tag stats counters increase and cross the 32-bit capacity when MPLS next-hop is created/deleted frequently, resulting in RE (routing engine) crash.
PR Number	Synopsis	Category: PFE Peer Infra
1667674	The FPC might fail to initialize on Junos platforms Product-Group=junos	On all Junos platforms, in a very corner case, the FPC (Flexible PIC Concentrators) might fail to initialize and remains in a stuck state when an FPC is installed or rebooted.
PR Number	Synopsis	Category: Kernel Tunnel Interface Infrastructure
1676912	IS-IS packet drop observed for packets having GRE over FTI-VXLAN header Product-Group=junos	All Junos platforms face the issue of IS-IS (Intermediate System-to-Intermediate System) packet drop where the packet headers are GRE (Generic routing encapsulation) over FTI-VXLAN (Flexible Tunnel Interface-Virtual Extensible LAN). Such packets are dropped at sender side kernel in the egress direction due to incorrect handling.
PR Number	Synopsis	Category: OSPF routing protocol
1634162	OSPF adjacency may take longer to converge when the neighbor restarts non-gracefully Product-Group=junos	On possibly a different vendor device or a Junos device running Junos OS Release 15.1 or later, when an OSPF neighbor is restarted non-gracefully, there might be a delay in convergence. An eventual traffic loss might appear as the Junos device marks the immediately originated LSA from the restarting neighbor as stale and waits for the next Type-1 LSA to arrive.
PR Number	Synopsis	Category: Express Chip L3 software
1650217	IRP memory parity issue might result in traffic loss on PTX and QFX10k Junos platforms Product-Group=junos	On PTX and QFX10k Junos platforms, parity issues might be observed related to Ingress Result Processor (IRP) memory might result in traffic loss.
PR Number	Synopsis	Category: Path computation client daemon
1678874	The rpd process crashes when a delegated LSP with IPv6 install prefix is configured Product-Group=junos	On all Junos and Junos Evolved platforms, when a LSP (Label Switched Path) is configured with IPv6 install prefix and the management of the LSP is delegated to a PCE (Path Computational Element) controller, rpd process crashes.
1678970	The pccd process might crash during MBB for an externally controlled LSP Product-Group=junos	On MX and PTX platforms the pccd (Path Computation Client Process) might crash when MBB (Make before break) update is received from rpd.
PR Number	Synopsis	Category: Protocol Independant Multicast
1676154	The rpd crash can be seen in MoFRR scenario Product-Group=junos	On all Junos and Junos Evolved platforms, the rpd ( routing protocol daemon) can crash when PIM (Protocol Independent Multicast), MoFRR (Multicast only Fast Reroute) configuration is present and some network churn event such as continuous interface cost changes, resulting in a change of active and backup paths for ECMP (Equal Cost Multi-Path) happens. There will be service impact because of the rpd crash but the system self-recovers until the next crash.
PR Number	Synopsis	Category: Issues related to PKI daemon
1655904	OCSP verification will return a failure when the OCSP server URL contains a domain name Product-Group=junos	On Junos SRX, MX, and Junos Evolved PTX platforms, when the connection to the OCSP (Online Certificate Status Protocol) server is not attempted e.g. when the OCSP server URL (Uniform Resource Locator) contains a domain name but the DNS (domain name system) server cannot resolve this domain name, the OCSP verification will return failure.
PR Number	Synopsis	Category: vMX Platform Infrastructure related issue tracking
1662524	In the EVPN-VXLAN scenario, the DHCP packets will get dropped when the DHCP relay agent is configured Product-Group=junos	On EX92XX series and MX platforms with the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, the DHCP (Dynamic Host Configuration Protocol) packets from the client get dropped while tunneling to the EVPN-VXLAN. When this happens, the packets will not reach the DHCP server and the host could not get the IP address.
PR Number	Synopsis	Category: PPPoE functional plugin for bbe-smgd
1685070	Multiple bbe-smgd cores might be observed resulting in subscribers being lost or failing to login in the Enhanced subscriber scenario Product-Group=junos	On MX platforms, multiple bbe-smgd cores might be observed due to out-of-bound memory access in the Enhanced subscriber scenario when bringing up PPPoE (Point-to-Point Protocol over Ethernet) subscribers and ACI (agent circuit identifier)/ARI (agent remote identifier) are part of the payload.
PR Number	Synopsis	Category: QFX access control list
1663790	Verification of stats for BFD session is "UP" while checking BFD session Product-Group=junos	On QFX5120 platforms with the firewall filter configured and inline BFD enabled hardware assist BFD support i.e. RLI 42378, the BFD filter is installed with an action Mirror. Due to this, IRALC cannot drop the packets in hardware and is eventually going to RE. The BFD session stays up. The issue causes no traffic/service disruption.
PR Number	Synopsis	Category: QFX L2 PFE
1667069	PVLAN IGMP packet is forwarded between Isolated ports and also duplicated to primary vlan port (Promiscous). Product-Group=junos	When Isolated port receives IGMP packet, it should not be forwarded to other Isolated ports but was forwarded and also duplicated to primary vlan port (Promiscous).
1676772	VLAN translation mapping gets deleted when one of the member interface removed from LAG Product-Group=junos	On all QFX5k, EX4650 and EX4600 platforms, if port has VLAN translation configuration and LAG interfaces connected on same FPC then incoming traffic can drop if one member of LAG interface is deleted/removed.
1681614	LLDP neighborship fails to come up with a Private VLAN configuration Product-Group=junos	On the Junos platforms, In a Virtual Chassis (VC) scenario if the interface is configured with Private VLAN (PVLAN) and connected through the Flexible PIC Concentrator (FPC) of the non-master switch, the LLDP (Link Layer Discovery Protocol) neighborship fails to come up and traffic through the interface will be impacted.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1650335	Traffic Loss will be observed with Virtual-Router Product-Group=junos	In EX4K and QFX5K platforms, traffic loss will be observed with virtual-router function.
1667751	Multihop BFD sessions might remain down in inline mode Product-Group=junos	On all QFX10002 platforms, multihop Bidirectional Forwarding Detection (BFD) over routing instance with inline mode configuration keeps the BFD sessions down.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1659533	Traffic loss might be seen when a VxLAN port is recovering from a failure Product-Group=junos	On all Junos platforms, the Virtual Extensible LAN (VxLAN) port goes to Spanning Tree Protocol (STP) BLK state when the port is down and takes a while to go back to the FWD state when the link is up. Traffic loss is seen in this case.
1665306	On QFX5K series platforms, duplicate packets might be seen in the multihomed scenario in an EVPN-VxLAN fabric when unicast ARP packets are received Product-Group=junos	On QFX5K series platforms, when unicast ARP (Address Resolution Protocol) is received for a MAC address that is already learned in an EVPN-VxLAN (Ethernet VPN-Virtual Extensible LAN) environment, the ARP request is flooded and duplicate packets might be seen on leaf devices. We might see some service impact where split-horizon might not work or continuous mac-move might be seen. This issue is rare and very unlikely to occur in a production environment due to presence of intermediate switches which might resolve the unicast ARP query.
PR Number	Synopsis	Category: QFX VCCP
1646561	VCP neighborship might not be formed on the LX4 40G VCP port Product-Group=junos	On all QFX5100 Virtual Chassis platforms, after the reboot, Virtual Chassis port (VCP) ports may not establish a VCP connection and Cyclic Redundancy Check (CRC) errors are also observed.
1669702	FPC1 is getting disconnected after ISSU and before switchover while checking ISSU status Product-Group=junosvae	On QFX5120-48T platforms with VC setup, FPC1 is getting disconnected after In-Service-Software-Upgrade(ISSU)/Nonstop Software Upgrade (NSSU) and before switchover while checking ISSU status.
PR Number	Synopsis	Category: QFX10008/16 QFX10002 optics related issues.
1677325	Interfaces with QFX-10000-30C and QFX10000-30C-M Line Cards will not work properly Product-Group=junos	On QFX10K platforms, interfaces with QFX-10000-30C and QFX10000-30C-M Line Cards will not work properly with FEC (Forward Error Configuration) and links connected to them will remain down.
PR Number	Synopsis	Category: QFX5100 Interface related issues
1665800	Ports with SFP-T 1G plugged in may go to hung state on QFX5100 platforms Product-Group=junos	When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted may go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission.
1669436	On specific QFX5k platforms, member links may reduce their configured speed when the other side doesn't have auto-negotiation disabled Product-Group=junos	On QFX5110, QFX5120, QFX5200-32C and QFX5100 Junos platforms, the member link reduces its speed if there is an optics/cable issue, which effectively reduces the overall AE (Aggregate Ethernet) link speed. This is an undesired behavior since the matching speed is one of the mandatory criteria for a member link to join an AE.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Interface
1629637	The interface on the peer device might remain up even after disabling the 10G interface on the Juniper device Product-Group=junos	On QFX5120-48T and QFX5120-48Y platforms, after disabling the 10G interface on the device the interface on the peer device might remain up.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1677376	The ge interface of QFX5110-48s-4c stay down post connected ACX device reboot Product-Group=junos	On Junos QFX5110-48s-4c platform, when ge port of QFX5110-48s-4c is connected to em0 of ACX, it is observed that the ge interface of QFX5110-48-4c stay down post ACX device reboot. Due to this, all the traffic running on particular interface will be impacted.
PR Number	Synopsis	Category: RPD Interfaces related issues
1639134	The dynamic tunnel might flap every 15 mins with a non-forwarding route Product-Group=junos	On all Junos and Junos Evolved platforms, the dynamic tunnel might flap every 15 mins when a non-forwarding route is resolving over the dynamic tunnel. The non-forward route resolution on a dynamic tunnel route might not be successful. As the route resolution is having impact, traffic drop might be seen in peer nodes.
PR Number	Synopsis	Category: KRT Queue issues within RPD
1639252	High CPU utilization for rpd process might be seen Product-Group=junos	On all Junos OS and Junos OS Evolved devices, the rpd process might utilize a large amount of the CPU during commit. This might only be seen in a scaled static route setup with virtual routing and forwarding (VRF) and Bidirectional Forwarding Detection (BFD) configured. The reason for the CPU spike is that kernel routing table (KRT) might get stuck and keep running for a long time. The high CPU might hamper the rpd process functionality in rare cases. However, the system recovers by itself when it encounters this issue.
1664527	The routing process on the device might crash when the IP address of local interface is changed to the IP address of BGP peer Product-Group=junos	On all Junos and Junos Evolved platforms, the rpd process might crash when the IP address of local interfaces is changed to BGP peer's IP address. When the IP address is changed, Router NH is created. When this route is leaked to another routing instance, flag is set on the same Router NH instead of creating a new one. This leads to rpd crash. Core files are generated and some traffic impact might be seen.
PR Number	Synopsis	Category: RPD Next-hop issues including indirect, CNH, and MCNH
1652387	The rpd process might generate core files with back-to-back rpd process restarts Product-Group=junos	On all Junos platforms, after back-to-back rpd process restarts, the rpd process might generate core files (or dump files) before the rpd process comes up.
1659255	The multipath route might be missing when multipath is configured Product-Group=junos	On all Junos and Evolved platforms, when multipath is configured multipath computation is missed for the routes resulting in missing multipath routes.
1668481	The BGP multipath might not install some of the available next-hops Product-Group=junos	On all Junos and Junos OS Evolved platforms configured with BGP multipath, if the number of BGP paths available for multipath is greater than the maximum-ecmp configured (default 16), multipath might not install some of the next-hops. This might lead to an undesired ECMP load-balancing of traffic.
PR Number	Synopsis	Category: RPD policy options
1670998	The rpd process crashes whenever it is getting shut down with router reboot, rpd restart, RE switchover, software upgrade Product-Group=junos	The routing process daemon crashes whenever the rpd process is getting shutting down with router reboot, rpd restart, RE switchover, and software upgrade with Border Gateway Protocol configured on the device.
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1632468	Due to timing issues the rpd process may get stuck after rpd restart or post commit configuration Product-Group=junos	On all Junos and Evolved platforms, the routing subsystem might not respond to the management requests due to the rpd process getting stuck after the restart or post-commit configuration. When this happens, the rpd may not come up on its own and the functionality of the router is impacted.
1665094	Route leaking might happen with auto-export configuration Product-Group=junos	On all Junos and Junos evolved platforms, if auto-export is configured under VRF, unexpected leaking of the routes could be observed.
PR Number	Synopsis	Category: Resource Reservation Protocol
1661954	A LSP might get stuck in the CSPF path computation stage Product-Group=junos	A label-switched path (LSP) might get stuck in the Constrained Shortest Path First (CSPF) computation and might not finish the session setup. The LSP retry continues to fail when no error feedback is received from downstream routers.
1667708	Transit LSR might stop sending RESV msg if there is no RRO in the LSP's PATH message Product-Group=junos	On all Junos and Junos Evolved platforms, if the ingress router is from a different vendor and the PATH message doesn't have RRO (RECORD_ROUTE object), the Junos devices will not process such packets, and the tunnel remains down.
1685182	PTX10008 EVO : When Bypass is used, RSVP PathTear is not encapsulated by MPLS header Product-Group=junos	When the bypass host route was deprecated through PR 1593959, bypass label info is not correctly set when sending backup PathTear messages if long refresh interval is disabled between the Point of Local Repair (PLR) and the Merge Point (MP).
PR Number	Synopsis	Category: RPM and TWAMP
1667716	The line cards MPC10/MPC11/LC-9600 might crash on Junos and EVO platforms Product-Group=junos	On Junos platforms with MPC10/MPC11/LC-9600 linecard and all EVO platforms configured with TWAMP, the MPC10/MPC11 linecard might crash when the TWAMP client tries to create a session with the TWAMP server.
PR Number	Synopsis	Category: IPSEC functionality on M/MX/T ser
1661815	Traffic loss might be seen in certain IPsec VPN and Group-VPN scenario Product-Group=junos	Group-vpn (gkmd daemon) and IPsec-vpn (kmd daemon) configured at the same time on a device and when SAs are present for both the type of configurations, leads to traffic loss.
1674585	The 'kmd' process may crash due to SA re-negotiation failure during IKE phase-1 Product-Group=junos	On platforms running Junos 16.2 onwards releases, if for some reason IKE (Internet Key Exchange) phase-1 SA (Security Association) re-keying fails, 'kmd' process may crash and the IPSec (Internet Protocol Security) tunnels may also get torn down. Most of the time, the reason is that the initiator changes its offerings after the initial successful key exchange.
PR Number	Synopsis	Category: SNMP Infrastructure (snmpd, mib2d)
1651774	VTEP might report a high speed on the sub-interface, causing SNMP alarms Product-Group=junos	When used on the VTEP sub-interface, the ifspeed OID may show a maximum value that is not zero.
1666548	The "snmpd" process might crash if SNMP timeout happens Product-Group=junos	On all Junos and EVO platforms, the "snmpd" process might crash, if there is no response for the SNMP requests and a timeout happens.
PR Number	Synopsis	Category: Bug and Review Tracking for Segment routing traffic eng
1665943	In the SRTE scenario, sensors are wrongly populated for colored tunnel BSID routes when uncolored tunnels are enabled Product-Group=junos	On all Junos platforms, incorrect sensor base telemetry data are collected when multiple SR-TE tunnels are configured with at least one uncolored, sharing the same single hop segment list.
PR Number	Synopsis	Category: SRX Argon module
1629972	SMS Channel Down alarm on primary node of HA pair after upgrade Product-Group=junos	After upgrading an SRX HA pair, a chassis alarm for "SMS Channel Down" is triggered and remains present though no cloud connectivity issues detected.
1666420	SRX alarming "SMS control channel down" without SMS feature configured Product-Group=junos	At times an AAMW connection issue can trigger an SMS Control channel down alarm even when the SMS feature is not configured on the device. It is safe to ignore the SMS alarm if the feature is not in use.
PR Number	Synopsis	Category: SRX branch platforms
1675853	Netbios traffic (IRB broadcast) is getting dropped post upgrade on the SRX platform Product-Group=junos	On SRX platforms, NetBIOS (Network Basic Input/Output System) broadcast packets originating from the client do not reach the SRX routing engine, which is required in case "set forwarding-options helpers port 137" is configured to forward NetBIOS to a server.
PR Number	Synopsis	Category: MPC7/8/9 Interface Issues
1651526	PCS Errored blocks count will increment after Junos software upgrade to 20.2R1 or above releases Product-Group=junos	After a Junos upgrade to 20.2R1 or above releases with 100G-LR4 optics, Physical Coding Sublayer (PCS) Errored blocks and framing errors on 100G-LR4 interfaces are seen, which impacts traffic.
1660154	Some of ports on MX platforms with MPC7E-10G do not come up with 1G speed Product-Group=junos	On MX platforms with MPC7E-10G, random interfaces with 1G speed fail to come up after PIC or FPC restart.
PR Number	Synopsis	Category: Stout PF fabric (SFB2)
1674309	During the smooth upgrade from SFB1 to SFB2, SFB2 gets detected as "Unknown Fabric Board" Product-Group=junos	On MX2010 and MX2020 platforms, SFB2 gets detected as "Unknown Fabric Board" during the smooth upgrade from SFB1 to SFB2 causing fabric issues.
PR Number	Synopsis	Category: MX10003/MX204 MPC defects tracking
1659087	Speed change from 10G to 1G on MX causes all other lanes to flap Product-Group=junos	LC2101 on MX10k8 and LC2103 on MX10003 do not support mixed optical and copper mode on line side of PHY, due to which when 1G mode is configured, 10G lanes go down.
PR Number	Synopsis	Category: SRX-1RU HA SW defects
1684756	The cluster fabric link will be down post reboot of node or power cycle Product-Group=junos	On SRX4600 platform, when using a cluster-id of 16 or higher post cluster node reboot, the fabric link will stay monitored down.
PR Number	Synopsis	Category: MX10003/MX204 Timing/Sync-E issues tracking
1663065	The offset value might be high on the downstream node while switching between line cards which impacts 5G services Product-Group=junosvae	On Junos MX10003 platform, the offset value might be high on a downstream node which impacts 5G services. While switching the SyncE(Synchronous Ethernet) and slave PTP (Precision Time Protocol) interface between line cards, SyncE will be in a holdover state for a long time and the clock will not get locked. SyncE clock status can be monitored using the following command "show chassis synchronization extensive"
PR Number	Synopsis	Category: Issues related to broadband edge apps (PPP, DHCP) on ZT/YT
1686761	DHCP operations fail when MPC10/11 cards are configured as relays towards uplink DHCP servers Product-Group=junos	When a DHCP (Dynamic Host Control Protocol) IP address request goes through MX platforms with MPC10/11 cards configured as DHCP relays, the requesting client will fail to acquire the lease as it will not receive the DHCPOFFER packet sent from the responding server.
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1649499	The MPC might crash or the traffic may be silently dropped/discarded Product-Group=junos	The firewall filter might be incorrectly updated in the Packet Forwarding Engine (PFE) when large-scale filters, applied on any of the supported bind points, undergo repeated load and unload. It can result in a core and FPC will be restarted. It's a timing issue
PR Number	Synopsis	Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1575722	VPLS traffic with control-word may fail to be forwarded Product-Group=junos	In MX platforms with MPC10E line card installed running release lower than 21.3 and VPLS (BGP signaling/LDP signaling) setup, traffic between CEs may fail to be forwarded if "control-word" knob is enabled.
1663725	Trinity-based line cards with VPLS and CFM configuration may crash when the indirect NH associated with LSI IFL is deleted Product-Group=junos	On MX platforms, the trinity-based line cards with VPLS (Virtual Private LAN Service ) and CFM (connectivity-fault-management) configuration might get crash when the indirect NH is associated with LSI (label-switched interface) IFL is deleted. When this happens, FPC may crash. However, it will come up again and the services will be restored.
1688629	All VPLS/Ethernet L2 traffic destined to VMAC will be flooded across the VPLS instance Product-Group=junos	An MPC10E/MPC11E at a VPLS (Virtual Private LAN Services) PE (provider edge) with a VPLS routing-instance configured with 'routing-interface irb.x' (Integrated Routing and Bridging) could get a group specific VRRP (Virtual Router Redundancy Protocol) VMAC (Virtual MAC) missed in its hardware MAC forwarding table if irb.x is a VRRP master for the respective VRRP group and it was a VRRP backup earlier with a VRRP master reachable through a VPLS pseudowire bound to some LSI (label-switched interface) IFL. Once that LSI IFL goes down because the pseudowire goes down, the MPC10E/MPC11E at a VRRP master will get a group-specific VRRP VMAC entry missed in its hardware MAC forwarding table.
PR Number	Synopsis	Category: ZT/YT pfe, vpls, mesh group software
1669765	Interoperability issue between legacy line cards and MPC10E/11E causes L2 packet drop Product-Group=junos	Due to a software defect seen in interoperability scenarios on newer AFT (Advanced Forwarding Toolkit) based MX cards (MPC10E and MPC11E), packets entering through legacy (non-AFT) card interfaces and exiting through AE (Aggregated Ethernet) interfaces via IRB (Integrated routing and bridging) will get dropped.
1678927	On linecards MPC10E,MPC11E and LC9600, no user configured mac address on IRB IFL is used as source mac in the transit path Product-Group=junos	On MPC10E,MPC11E and LC9600 linecards packet will not carry user defined IRB (Integrated Routing and Bridging) IFL as source mac, instead will carry IRB IFD mac.
PR Number	Synopsis	Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1580500	TTL expired reply might be received with a different source address Product-Group=junos	On MX series platforms with "allow-l3vpn-traceroute-src-select" knob enabled, when traceroute runs over L3VPN, TTL expired reply gives incorrect source address, which might mislead the troubleshooting engineer. allow-l3vpn-traceroute-src-select" knob
PR Number	Synopsis	Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1637304	FPC crash might be seen on all MX platforms with BBE subscriber Product-Group=junos	FPC might crash on all MX platforms with Broadband Edge (BBE) subscribers and the traffic flowing through the impacted FPC will get affected.
PR Number	Synopsis	Category: Trio pfe stateless firewall software
1579182	FPC crashes might be seen on MX Series devices and the EX9200 line of switches Product-Group=junos	On MX Series devices and the EX9200 line of switches, the FPC gets restarted and thereby disrupts traffic when there is an out-of-order filter state and terms. This issue might be seen only in back-to-back GRES in more than 40 to 50 iterations.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1677631	DHCP bindings will fail for the client connected on an LT interface when DHCP snooping is enabled Product-Group=junos	On all Junos and Junos Evolved platforms, Dynamic Host Configuration Protocol (DHCP) bindings will fail for the clients connected on an LT(Logical Tunnel) interface when DHCP snooping is enabled. This issue is not seen when DHCP snooping is disabled or when clients and server are on other interfaces.
PR Number	Synopsis	Category: Trio pfe l3 forwarding issues
1662950	TCP MSS value might not get reflected to packets Product-Group=junos	On MX platforms with TCP MSS (TCP maximum segment size)configured, mss value might not get stamped/configured to TCP packets when transiting through the device.
PR Number	Synopsis	Category: Trio pfe multicast software
1655363	Multicast packet drop causes pixelization Product-Group=junos	On all MPC1/MPC2NG/MPC3NG/MPC7/MPC8/MPC9/MPC10/MPC11/LC9600/MX304 line cards, the multicast traffic drop could be observed. Only a few mcast packets get dropped, hence pixelization is seen on the receiver. The packet for the static receiver on the router passes through the policer on the loopback filter. Only those packets that pass through are looked into by the firewall loopback filter.
PR Number	Synopsis	Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1662172	The CPU utilization might increase when a user login and logout to the device continuously Product-Group=junos	When multiple users log in and log out using SSH public-private key authentication to the device every few seconds, then the CPU utilization might increase on all Junos and Junos OS Evolved platforms.
PR Number	Synopsis	Category: Junos Automation, Commit/Op/Event and SLAX
1656436	A large configuration might not get committed at boot Product-Group=junos	On all Junos and Junos Evolved, the mgd process might fail to commit a scaled configuration (~350K set statement) during boot due to insufficient memory.
1657595	Commit failure may be observed with Terminate API used Product-Group=junos	On all Junos platforms, if the Slax script is configured with API ";", commit may fail. This SLAX script uses library APIs to consume and execute, and any upgrade to these libraries may change the behaviour of the parsing script.
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1659783	The configuration might roll back after performing "commit confirmed" and then reboot Product-Group=junos	On all Junos OS and Junos OS Evolved platforms, the configuration might roll back after performing "commit confirmed" and then a reboot.
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1643209	Commit fails with message "statement does not match patch" due to TOD mismatches between Primary RE and Backup RE Product-Group=junos	When time-zone for the router is set as EST5EDT and if the TOD (Time-Of-Day) values under "event-options generate-events" are modified in different time zones, that is TOD configurations created on EST time zones are getting modified in EDT time zone, then it can cause commit failures. When such commits happens at different time-zones, internally, it generates a patch file and tries to load the patch at both RE. But due to different time zone, it is not getting excepted by backup RE.
1673176	"gethostbyname: Host name lookup failure" is displayed during commit Product-Group=junos	On all SRX Series devices with J-Web enabled, "gethostbyname: Host name lookup failure" is displayed during commit. This issue is a display issue and doesn't have any service impact.
PR Number	Synopsis	Category: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1661323	High logging rate may cause 'eventd' to increase RE CPU utilization Product-Group=junos	On Junos and Junos Evolved platforms, if a process creates an unusually high number of logs, 'eventd' may end up consuming more resources which may result in RE (Routing-Engine) CPU (Central Processing Unit) spike. This may happen when Telemetry is not configured but due to the bug, the logs are processed by 'eventd' and 'drend'(Dynamic Rendering Daemon).
PR Number	Synopsis	Category: MX10K platform
1605255	[MX10008/16] Kernel error logs(tcp_timer_keep) is seen on backup RE when 'set system internet-options no-tcp-reset drop-all-tcp' option is enabled. Product-Group=junos	When 'set system internet-options no-tcp-reset drop-all-tcp' option is configured, kernel error logs(tcp_timer_keep) is repeated about every 80 sec on backup RE. Backup RE is trying to initiate TCP connection to synchronize the same daemon on master RE. However, the connection status will be stuck SYN_SENT and repeating connection initiation and drop.
PR Number	Synopsis	Category: For GPRS security features on highend SRX series
1673879	GTP control packets might be incorrectly dropped/passed if there is more than one APN IMSI filter configured Product-Group=junos	On SRX platforms, during General Packet Radio Services (GPRS) Tunneling Protocol (GTP) inspection if there is more than one APN IMSI (Access Point Name or International Mobile Subscriber Identification) filter configured in the GTP profile, the filter may incorrectly drop/pass CrPdpRequest and CrSessRequest GTP Control packets.
PR Number	Synopsis	Category: Virtual Private LAN Services
1655858	The Pseudo Wires might go down in VPLS scenario Product-Group=junos	On all Junos/Junos Evolved platforms with VPLS (virtual private LAN service) deployed, deactivating and activating the neighbour under the default mesh-group might lead Pseudo Wires(PW) to go down. This happens when there is a change in default mesh-group and that might not be updating the PW status. This can be recovered by deactivating and activating the complete routing instance under the mesh-group.
PR Number	Synopsis	Category: Virtual Private Networks - rpd
1661542	Traffic drop may be seen when Inter-AS option-B label spoofing is configured along with vrf-table-label Product-Group=junos	On all Junos and Junos OS Evolved platforms, when the router is configured as both Autonomous System Border Router and Provider Edge (ASBR and PE), and virtual-router/mpls-forwarding as "forwarding-context" is in use along with "vrf-tabel-label" for the Local Layer 3 Virtual Private Network - Virtual Routing and Forwarding (L3VPN VRF) traffic drop may be seen.
PR Number	Synopsis	Category: Virtual Router Redundancy Protocol
1650873	Authenitcation key can not be configured more than 15 character Product-Group=junos	Dual masters are seen in VRRP when the devices are running two different Junos versions.
1652549	VRRP failover over 2 seconds may be observed Product-Group=junos	In all Junos and Junos Evolved platforms, VRRP failover over 2 seconds may be observed in case of "fast-interval" configured less than 1 second and "failover-delay" is not configured.
1666519	The hold time of EVPN DF election takes time and it brings BUM traffic loss Product-Group=junos	On Junos platform, it takes time to elect EVPN DF when LAG interface as a part of EVPN multihoming comes up. As a result, BUM traffic could be lost for a while.
1683871	If vrrp authentication key is more than 16 characters instead of commit error it is ignoring remaining characters Product-Group=junos	A new commit check is added for the "vrrp authentication-key" stanza to validate its length. An Error will be returned if the authentication key exceeds 8 characters for simple and 16 for md5.
PR Number	Synopsis	Category: Xellent Platform issues
1620527	QSFP in slot et-0/0/0 might not come up after plug-in Product-Group=junos	On PTX Series routers and QFX Series switches using QSFP and optic toolkit, QSFP in slot et-0/0/0 might not come up after plug-in. When this happens, one or a few ports might start showing i2c errors and eventually not come up. When this happens, the link does not come up in that particular port.
PR Number	Synopsis	Category: usf logging and reporting function related issues
1668941	Commit configuration check-out failed while configuring syslog stream host IP in specific range Product-Group=junos	On Junos MX platform with SPC3 cards, while configuring services [service-set name syslog stream stream-name host] within some specific IP range (the last octet is >223 or =127 or the IP is X.0.0.192) is committed, will get "error: Host IP Address is not valid" and "error: configuration check-out failed".
PR Number	Synopsis	Category: usf nat related issues
1632278	DSLite might not work on MX platforms installed with MPC7E line card and SPC3 service PIC Product-Group=junos	DSLite (Dual-Stack Lite) may not work on MX platforms when MPC7E line card and SPC3 service PIC (Physical Interface Card) are installed and subsequently NAPT44 (Network Address Port Translation) will not work.
PR Number	Synopsis	Category: usf service set related issues
1672819	Traffic impact might be seen due to an unexpected reboot of SPC3 card Product-Group=junos	On all MX platforms with SPC3 service card installed, when endpoint independent filtering is configured along with DS-LITE (Dual Stack Lite) then PIC might reboot along with a core dump.
PR Number	Synopsis	Category: Unified Services Framework
1664517	SPC3: Receive [Rx] queue of direct memory access might be stuck which may cause issues in packet processing Product-Group=junos	SPC3:Receive [Rx] queue of direct memory access might be stuck which may cause issues in packet processing
1674381	The "nsd" may crash post NAT rule configuration change Product-Group=junos	On Junos platforms with MX-SPC3 services card, this issue is seen due to an error condition for a memory allocation, while changing the NAT (Network Address Translation) rule configuration might crash "nsd" (Network Security Daemon) and unable to allocate memory due to large config and that results in memory allocation failure.

Modification History

First publication 2022-11-04