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 20.4R3-S5 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 20.4R3-S5 is now available.

20.4R3-S5 - List of Fixed issues

PR Number	Synopsis	Category: EX4300 PFE
1673000	VLAN ID of a VSTP BPDU changes when it transits through the switch Product-Group=junos	On EX4300-24T, EX4300-48P, EX4300-VC, EX430024P, EX430032F and EX430048T platforms, when a VSTP (VLAN Spanning Tree Protocol) BPDU (Bridge Protocol Data Unit) arrives with a VLAN ID that is not configured in the switch, but that matches with an HW Token of any other configured VLAN, the VLAN ID of the BPDU will be changed to the VLAN ID corresponding to the matched HW Token and flooded. This disrupts STP convergence on the configured VLAN because some ports can incorrectly go into blocking state.
PR Number	Synopsis	Category: EX4300 Layer 2 implementation
1655511	The egress traffic is not tagged properly in a L2PT scenario Product-Group=junos	On EX4400/EX4100 and QFX5120 platforms, in a Layer 2 protocol tunneling (L2PT) scenario, the egress traffic from network-to-network interface (NNI) ports on a device, to user-to-network interface (UNI) ports, remains untagged at the UNI end, which will impact the protocols enabled on the interface.
PR Number	Synopsis	Category: EX9200 Platform
1535078	Junos 'et-' interface stuck and remains down between two particular ports Product-Group=junos	In rare instances, when 'et-' interface is stuck and remains down between two particular ports on MPC5E/MPC4E/CXP MIC card on MX SRX/EX92 series. The MAC Chip in the line card goes to a condition where the EDC convergence state (adaptive algorithm state machine error.) in the Firmware remained at 'tracking' while 'et-' interface is stuck and remains down.
PR Number	Synopsis	Category: EX2300/3400 PFE
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: EX-Series VC Infrastructure
1669241	On JUNOS (EX4600, EX4650, QFX5k VC) platforms, line card might be disconnected from VC post master RE reboot Product-Group=junos	On JUNOS EX4600, EX4650, QFX5k VC platforms, when master RE is rebooted, the line card might be disconnected from Virtual Chassis (VC). Packet Forwarding Engine (PFE) planned restart may be seen on the new backup due to which line card leaves and rejoins the VC automatically.
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.
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: "agentd" software daemon
1657886	The 'agentd' and 'eventd' process might cause high CPU utilization and may also affect Telemetry services Product-Group=junos	On all Junos and Junos Evolved platforms, high CPU utilization is observed with the 'agentd' and 'eventd' processes. This is caused by 'rpd' issues.
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 Autoconfigured DVLAN related issues
1680453	The process bbe-smgd on the router would stop processing new PPPoE subscribers session Product-Group=junos	On all Junos platforms configured with subscriber-management, the process bbe-smgd will stop processing new PPPoE (Point-to-Point Protocol over Ethernet) connections due to a memory leak in the control packet pool of the PPPoE plugin.
PR Number	Synopsis	Category: Bi Directional Forwarding Detection (BFD)
1675921	Micro BFD session state in RE remain UP even peer side session is down. Product-Group=junos	Any platforms with Micro BFD configured on member links of the LAG/ae interface, BFD Session state in RE remains as UP always even though PEER device has ceased.
PR Number	Synopsis	Category: Border Gateway Protocol
1635339	BGP multipath computation for the prefix may cause the rpd to crash Product-Group=junos	On all Junos and Junos Evolved platforms, rpd (routing processor daemon) crash can be seen when there is a computation of the BGP (Border Gateway Protocol) multipath prefix. This is a rare timing issue which is observed only when BGP multipath is configured with list-nexthop and there is a peer cleanup and re-establishment. There might be a service impact because of the rpd crash, however, the system recovers to functional state by itself.
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.
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.
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.
PR Number	Synopsis	Category: Express Broadway PFE L3
1680757	BFD sessions will remain down in the EVPN-VxLAN scenario Product-Group=junos	On QFX 10008 and QFX10016 platforms, in a distributed mode Bidirectional Forwarding Detection(BFD) session might remain down if the anchor FPC and the FPC where BFD packets are received over Virtual Tunnel Endpoint (VTEP) are different.
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: 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.
1649510	The cosd process might not be able to send unbinds for rewrites post a certain sequence of operations are performed Product-Group=junos	On All Junos platforms, in certain conditions, a stale rewrite rule entry is left behind in the PFE and the corresponding kernel state is also wrong. The pre-conditions to note this phenomenon include a sequence of AE specific operations along with the presence of COS (class-of-service) configuration. For example, let us say, we have config-1, which defines a set of AE bundles and associates COS rewrite rules under the bundle. Now we perform a sequence of operations to delete AE bundle and then add it back as well. In between, we remove class-of-service and add back class-of-service to the AE bundle as well. Now, when we override this config-1 with a new config-2 that defines the same AE bundle but an updated rewrite rule (with additional forwarding classes and mappings), it is possible to see a previous rewrite rule still being used for AE specific IFLs. At times a stale unused rewrite rule is left behind if config-2 no longer uses the previous rewrite rule that came in from config-1. To recover from this problem, we need to restart cosd twice or do an NSR GRES followed by deactivate/activate of class-of-service.
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: Firewall Filter
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: 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: 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: Gnats category for dynamic rendering infrastructure
1520977	The rpd might be non-responsive after routing restart with Telemetry and scaled configuration Product-Group=junos	With Junos Telemetry Interface monitoring, the rpd process may be non-responsive after a restart in scaled scenarios with an asymmetric number of IPv4 and IPv6 addresses configurations.
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: Ethernet OAM (LFM)
1543641	On the MPC10 line cards, DMRs or SLRs are not received with an EVPN up MEP on the aggregated Ethernet interface with normalization Product-Group=junos	When AE (Aggregate Ethernet) interface with member links located on both MPC10/11 and non-MPC10/11 linecards, if it belongs to EVPN (Ethernet VPN) instance and configured CFM on it, due to difference in handling VLAN information between these two linecards, the CFM PDU (Protocol Data Unit) may be discarded. It will lead to the CFM session Down and the EVPN in Down state either.
PR Number	Synopsis	Category: AAA, auditd issues
1622936	Idle/inactive netconf user sessions not terminated as per the config set under class Product-Group=junos	Session idle time was not supported for netconf session in EVO, as part of the current PR extending this feature support. This might result in dangling sessions.
PR Number	Synopsis	Category: mgd, ddl, odl infra issues
1621892	Junos OS Evolved: The ssh CLI command always runs as root which can lead to privilege escalation (CVE-2022-22239) Product-Group=junos	An Execution with Unnecessary Privileges vulnerability in Junos Management Daemon (mgd) of Juniper Networks Junos OS Evolved allows a locally authenticated attacker with low privileges to escalate their privileges on the device and potentially remote systems. Please refer to https://kb.juniper.net/JSA69895 [juniper.net] for more information.
PR Number	Synopsis	Category: SNMP, mib2d issues
1669510	The snmpd core might be observed with filter-duplicates configuration Product-Group=junos	On all Junos and EVO platforms configured with filter-duplicates, the snmpd core might be observed if the SNMP query is made simultaneously from NMS (Network Management System) as well from the CLI.
PR Number	Synopsis	Category: EVPN control plane issues
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
1609322	Few ARP/ND/MAC entries for Vlans are missing with MAC-VRF configuration Product-Group=junos	In all Junos and Evo platforms, in EVPN-VXLAN scenario, with "proxy-macip-advertisement" knob configured, few ARP/ND/MAC entries may get missing.
1649234	The kernel crash would be observed in an EVPN multi-homed scenario Product-Group=junos	On QFX10002/QFX10008/QFX10016 (only QFX10K) platforms, when Assisted Replication (AR) feature as Replicator role is used in an Ethernet VPN (EVPN) multi-homed scenario, there would be out-of-bound memory access issue observed which could result in the kernel crash leading to the service impact.
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: EX Chassis Interface Handling
1651721	EX9251 :: Reboot reason shows as "0x2000:hypervisor reboot" instead of "0x4000:VJUNOS reboot" when we do Junos reboot Product-Group=junos	Reboot reason may show incorrect starting LTS19 as it requires a change in VM config file. Workaround is provided for releases where fix is not available.
PR Number	Synopsis	Category: Express PFE including evpn, vxlan
1646489	Vxlan Tunnel termination fails due to a change in config Product-Group=junos	Packet drop can be seen when a new VNI (Virtual Network Index)config is applied over the existing VNI config.
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
1627566	QFX10002-60C platform might not respond back to ICMP packets received with TTL or hop limit value of 1 Product-Group=junos	On QFX10002-60C platform when ICMPv4 (Internet Control Message Protocol) packet with TTL (Time To Live) value of 1 or ICMPv6 packet with hop limit value of 1 is received at the IRB (Integrated Routing and Bridging) interface, it might not respond back with the corresponding ICMP error codes [TTL expired or hop limit exceeded] to the source device.
1664656	The DHCP offer packets will not be sent to the clients when the DHCP relay agent is configured over Type-5 EVPN Product-Group=junos	On QFX10002-60c platform, the DHCP (Dynamic Host Configuration Protocol) offer messages from the DHCP server will be dropped when the device acts as a DHCP relay agent over a Type-5 tunnel. Due to this, the IP address will not be assigned to the requesting client from the DHCP server.
PR Number	Synopsis	Category: Express PFE MPLS Features
1683123	L3VPN to VXLAN traffic gets dropped on QFX platforms with QFX10000-60S-6Q and QFX10000-36Q line cards Product-Group=junos	On QFX10008 and QFX10016 platforms with QFX10000-60S-6Q and QFX10000-36Q line cards installed, L3VPN (Layer 3 VPN) to VXLAN (Virtual Extensible LAN) traffic will not flow if the L3VPN tunnel is terminated on the affected cards.
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
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: Signature Database
1623857	IDP security package update is failing during offline method Product-Group=junos	IDPD will not core when wrong package in given for offline download due to missing file in offline downloaded sigpack.
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: Adresses ALG issues found in JSF
1658370	The flowd crash might be observed on SRX5k series platforms where Central Point is present Product-Group=junos	On SRX5k series platforms where Central Point is present if receiving any packet in the ALG (Application Layer Gateway) scenario while the CP card is unavailable (while insertion), the flowd crash might be observed.
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
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: 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: all logging related bugs on srx platforms
1687244	unexpected default event-rate value for event mode logging Product-Group=junos	On SRX platform, when event mode logging is used without event-rate option, the logging rate was unexpectedly set to 100 although the default event rate is 1500
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: Security platform jweb support
1658330	Various page errors have been corrected in JWeb Product-Group=junos	Various page errors have been corrected in JWeb
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1686523	VPLS traffic stop after adding/changing VPLS routing instance Product-Group=junos	VPLS mesh group add is failing because L2ALD is keep trying to add mesh group for a deleted routing instance.
PR Number	Synopsis	Category: Label Distribution Protocol
1670334	Traffic loss will be seen in an LDP->BGP-LU stitching scenario Product-Group=junos	On all QFX platforms, traffic loss can happen when the BGP-LU (Labeled Unicast) routes are exported to LDP (Label Distribution Protocol) to perform LDP->BGP-LU stitching, on a device with directly connected BGP peers.
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.
1676551	LDP egress-policy for default route (0.0.0.0/0) with 'exact' option will make output label for the unrelated routes Product-Group=junos	On all Junos and Junos Evolved platforms, when Label Distribution Protocol (LDP) egress-policy for default route (0.0.0.0/0) with the 'exact' option is configured, it will install the "unrelated route" prefix into inet.3 and will make an output label for an unrelated route (though "set protocols ldp longest-match" is not configured). When this issue happens, next-hop selection may be disturbed and in a rare case, traffic impact will also be seen.
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	This issue is applicable to all Junos. When a device with a valid license is upgraded to a release and this upgrade changes the licensing from Legacy to Agile then the installed license might show as invalid.
PR Number	Synopsis	Category: lldp sw on MX platform
1669677	LLDP neighborship might fail if the chassis-id format of the LLDP packet is xx:xx:xx:XX:XX:xx' Product-Group=junos	On all Junos platforms, Link Layer Discovery Protocol (LLDP) neighborship fails if the chassis-id format of the LLDP packet is xx:xx:xx:XX:XX:xx'
PR Number	Synopsis	Category: MPC11 ULC fabric software related issues.
1658164	Fabric Destination error/Fabric plane in check state Product-Group=junos	Fabric Plane check/error alarm can be seen due to overrun interrupt being set in MS-MPC line cards. Latency difference between the SFB2/SFB3 and the MS-MPC cards potentially causes overruns to increase during the traffic burst.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1616841	Protected LSP goes down with strict hops and link protection configured Product-Group=junos	On all Junos and all EVO platforms, the sub-LSP of a Point-to-Multipoint Label Switched Path(P2MP LSP) with link-protection and having strict hops goes down when a protected link on more than one sub-LSP goes down simultaneously and TED(Traffic Engineering Database) notification or RSVP tunnel local repair message not received before the CSPF(Constrained Shortest Path First) computation. As a result, the sub-LSP fails and traffic drop is seen.
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.
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: MX Timing software
1671262	PTP server state stuck in acquiring state when configured on a port enabled with Ingress Queueing Feature Product-Group=junos	On MX and EX platforms, with Trio-based line cards, configuring ingress queuing on the interface where Precision Time Protocol (PTP) packets are received, Ingress Queueing duration was not accounted for in the PTP fields and results in a delay in processing.
PR Number	Synopsis	Category: MX104 Software - Chassis Daemon
1626486	The chassisd might crash on MX104 Product-Group=junos	On the MX104 platform, when 'Invalid Chassis Model' occurs in the chassisd daemon, the chassisd might crash which might lead to interfaces down and automatic recovery. The fix is to avoid this chassisd core during 'Invalid Chassis Model' scenario.
PR Number	Synopsis	Category: MX10K platform
1674322	SNMP traps "Power Supply failed" and "Power Supply OK" are not generated Product-Group=junos
PR Number	Synopsis	Category: Microkernel for neo mpc
1664602	Line card may crash after offline/online plane Product-Group=junos	On platforms supporting MQ and XM-based line cards, destination error, self-ping error and line cards can be offline after swapping the XM-based uplink cards and toggling the fabric planes. The issue will be seen on other MQ-based line cards in the chassis.
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
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
1645221	Junos OS and Junos OS Evolved: RPD crash upon receipt of specific OSPFv3 LSAs (CVE-2022-22230) Product-Group=junos	An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent unauthenticated attacker to cause DoS (Denial of Service). Please refer to https://kb.juniper.net/JSA69884 [juniper.net] for more information.
1671672	The backup next hop computation might not be as expected for some random prefixes when there is a topology change Product-Group=junos	On all Junos and Junos OS Evolved platforms, when there is a topology change, unexpected flags might be generated which prevents the backup path from being computed accurately. This will lead to functional impact.
PR Number	Synopsis	Category: Used for tracking OVSDB software issues and features
1687847	OVSDB certificate files are not copied from the Master to the Backup Product-Group=junos	On all Junos devices which support OVSDB (Open vSwitch Database) functionality, when a new backup is added on VC (virtual chassis), the master does not copy the certificate files to the backup. This impacts the OVSDB functionality and affects the traffic.
PR Number	Synopsis	Category: Express Paradise PFE Sflow
1672121	Flow sample packet is not sent to the collector when the destination is an ECMP path Product-Group=junos	On QFX10k platforms with sflow configured, flow sample packet is not sent to the collector when a packet is received on an Integrated Routing and bridging (IRB) interface and its destination is an Equal Cost Multi Path (ECMP) path.
PR Number	Synopsis	Category: Path computation client daemon
1675816	In a rare case, 'pccd' will crash when the PCEP connection is down Product-Group=junos	On all Junos and Junos Evolved platforms, on the intermediate device when connection towards Path Computation Element (PCE) is down, Path Computation Element Protocol (PCEP) session will be down resulting in pccd crash. Routing protocols are not impacted but pccd crashes.
PR Number	Synopsis	Category: Protocol Independant Multicast
1500125	Some PIM join or prune packets might not be processed in the first attempt in the scaling scenario where the PIM routers establish neighborship and immediately join the multicast group Product-Group=junos	On all Junos platforms with scaling MVPN scenario, some PIM Join/Prune messages may not be processed for the first attempt. For instance, a dedicated PIM router receives more than 2500 PIM hello packets from the new neighbors, followed by PIM Join packets for the same multicast group in a very short period of time.
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 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
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.
1671449	Packet drops are seen after flapping or changing a passive monitor interface Product-Group=junos	On Junos based specific QFX/PTX platforms (QFX10K8/QFX10K2/PTX1K/PTX5k/PTX10K), packet drops are seen whenever address family of a passive monitored interface is flapped or changed. Packets are treating as forwarding packets due to L2 domain property of a passive monitored interface and getting dropped.
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.
PR Number	Synopsis	Category: QFX10008/16 QFX10002 linecard, serdes and uboot
1688993	On QFX10008/QFX10016 platforms fails to detect flaps even though the remote device connected has observed flaps Product-Group=junos	On QFX10008/QFX10016 platforms, interface faults(Local/Remote) of very short duration (<30msec) can go undetected. The interface does not go down due to these faults leading to unidirectional link and traffic blackholing.
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: QFX10008/16 QFX10002 Ultimat/Elit platform related issues -
1676740	,The traffic doesn't re-route quickly causing traffic blackholing Product-Group=junos	On all VMHOST based platforms, traffic blackholing happens because the traffic doesn't re-route quickly as chassisd doesn't recognize an FPC failure from a BAD_VOLTAGE notification.
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: rosen-6 and rosen-7 mvpn bugs
1592303	The rpd process might crash when deactivating or deleting a routing-instance Product-Group=junos	On all Junos and Junos Evo platforms, rpd core might be seen in the RE (Routing Engine), when deactivating or deleting a routing instance configured with NG-MVPN (Next Generation Multicast VPN), PIM (Protocol Independent Multicast) and having three or more entries of the same MVPN routes inside it [example - receiving 3 or more route entries for 1 MVPN route from different route reflectors].
PR Number	Synopsis	Category: RPD Interfaces related issues
1659102	The rpd memory leak might be seen while processing vlan-ccc configuration Product-Group=junos	On all Junos and Junos Evolved platforms, when deleting/adding the whole interface unit of family vlan-ccc, the rpd will observe a memory leak.
PR Number	Synopsis	Category: KRT Queue issues within RPD
1623170	BGP Flowspec might not show counters Product-Group=junos	On all Junos and Junos Evolved platforms, when installing an IPv6 firewall filter using BGP flowspec, matching traffic counters may show "0" values.
PR Number	Synopsis	Category: Issue related to mcnh routing infrastructure within RPD
1663568	The forwarding plane is not updated properly in scaled MVPN scenario after receiving PIM leave messages Product-Group=junos	On all Junos and Junos Evolved platforms, when IFLs from non-default routing instances are being added with the OIF scaling of more than 2000 there will be a spillover of IFLNHs into different next hops due to this the outgoing interfaces (OIFs) will not be deleted from multicast next-hop.
PR Number	Synopsis	Category: RPD Next-hop issues including indirect, CNH, and MCNH
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.
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
1681403	In the RSVP-TE scenario, with Entropy label capability is enabled during MBB issues handling Resv Messages Product-Group=junos	On all platforms with entropy-label configured, the issue shows up during Make-Before-Break (MBB) at a transit Juniper node when non-Juniper Egress constructs and sends a Resv message with multiple flow-descriptors (includes descriptors for both old and new instances). Juniper transit device has an issue handling such Resv Messages, the RRO object that is part of the flow-descriptor was getting dropped when the LSP_ATTRIBUTES object was also present within the flow-descriptor.
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: SNMP Infrastructure (snmpd, mib2d)
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: Remote Access VPN issues on SRX
1674522	VPN tunnel will not be established in exclusive client scenario Product-Group=junos	On SRX platforms, if NCP(Network Control Protocol) pathfinder client is enabled with tcp-encap mode, VPN(Virtual Private Network) tunnel will not be established.
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
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.
1692063	PCS Errored blocks increments on MX 100GE LR4 link even after the fix of PR1651526 Product-Group=junos	There could be some hardware combinations that PR1651526 couldn't completely stop the PCS error/input framing error on 100GE LR4 link. This PR has added an additional fix that is specific to LR4 optics.
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 Platform SW - Chassisd s/w defects
1574669	The chassisd process might crash on all Junos platforms that support Virtual chassis or Junos fusion Product-Group=junos	On Junos platforms that support virtual chassis or Junos fusion, if virtual FPC is configured with PIC number >=2, the chassisd process might crash and the device might reboot after Junos software upgrading. This might cause traffic impact.
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=junos	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: ZT/YT pfe firewall software
1608723	MPC10/11 - filter matching unknown-unicast does not take effect Product-Group=junos	On MX platforms with MPC10/11 line cards, if firewall filters contain match rules of unknown-unicast, the filter does not work. The filter will be applied in the configuration but no action is taken, e.g., policing action will not take effect.
PR Number	Synopsis	Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1681533	The line card gets crashed during node/interface statistics reporting with resource monitoring Product-Group=junos	On MX platforms with specific line cards, the MPC may crash and generate core dumps in a corner case during node/interface statistics reporting scenario when resource monitoring is used.
PR Number	Synopsis	Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1665234	The rpf-check feature might not be working in a Junos Subscriber management scenario Product-Group=junos	On MX platforms installed with MPC linecard( except MPC10 onwards) and Subscriber management, if the Subscribers are enabled with the routing-services as well as the reverse-path forwarding (RPF) check, the rpf-check feature might not be working.
PR Number	Synopsis	Category: Trio pfe qos software
1571985	AE Interface queues statistics will be exported to jvision server Product-Group=junos	On MPC10, MPC11 and MPC12 line cards, Interface queue statistics(/junos/system/linecard/interface/queue) and extended statistics(/junos/system/linecard/interface/queue/extended-stats) will export for Aggregated interface as well. Aggregation of AE child members will be done on local FPC. If multiple legs of AE is present in different FPC then aggregation has to be done at the collector side.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1669410	Traffic drop is be observed with layer 2 circuit local switching with PS interface Product-Group=junos	On MX platforms, when VLAN operations are enabled on the ingress interface and ingress and egress processing are done in the same PFE (Packet Forwarding Engine) instance, traffic drop is observed in layer 2 circuit local switching with PS (Pseudowire Subscriber Interface) interface scenario.
1670316	Layer 2 packets other than IPv4/IPv6 (e.g. CFM) will get forwarded as out of order via MPC10 and MPC11 in the egress direction Product-Group=junos	On specific MX devices with MPC10 and MPC11 linecards, Layer 2 packets (i.e. other than IPv4/IPv6, e.g. CFM), may get forwarded as out of order in the egress direction. The issue is not seen for IPv4/IPv6/MPLS Encapsulated IPv4/MPLS Encapsulated IPv6 traffic/MPLS Encapsulated Ethernet+IP traffic.
1670923	EX9k and MX platforms do not relay a DHCP offer with a broadcast flag under EVPN-VXLAN scenario Product-Group=junos	In an EVPN-VXLAN configured scenario, EX9k and MX platforms relays a DHCP (Dynamic Host Configuration Protocol) discover with a "Broadcast flag" from a client to a server. However, they do not relay a DHCP offer from a server to a client.
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 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: UI Infrastructure - mgd, DAX API, DDL/ODL
1637552	During the ephemeral configuration database changes, "mgd" core files might be generated Product-Group=junos	On all Junos platforms, "mgd" core files might be generated when the ephemeral configuration database changes.
1669375	commit failure when changing BGP well-known community attributes Product-Group=junos	RCA: After doing multiple testing and trying on various combination it is concluded that issue is happening once we set the community number for a attribute and then try to set community string for the same attribute. Below is the error seen : [edit] root@snagar-re0# set routing-instances L3VPN1 routing-options static route 0.0.0.0/0 community 65535:65281 [edit] root@snagar-re0# set routing-instances L3VPN1 routing-options static route 0.0.0.0/0 community no-export error: could not add object to patricia tree error: statement creation failed: no-export Actually there is a community_map variable in ui code which have the mapping of community names with its corresponding community number. For eg: static const char *community_map[] = { "graceful-shutdown", "65535:0", "Graceful Shutdown", "no-export", "65535:65281", "Do not advertise outside your confederation/AS", ??? ???????? }; On triaging deeper , it is observed that when we try to add community attribute or node we always pass community number as key. However , key size is calculated on passed string. As a result , when community number in the command is passed, key size will be calculated on that and stored. Now when string i.e community name is passed (note that key will still be community number here) , size for the key will calculated on passed string. Now , at this stage even the attribute is same and key passed is also same, child for the node is not found and flow continues to create the object and add that. Later we got the above error as same attribute is already there.
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 all UI tools (mgd-bsd/cli-bsd, XML and DMI
1681656	At start of every hour of the device's uptime, the output of "show system uptime \| display xml" operational command might show incorrect value of the uptime calculated in seconds. Product-Group=junos	At start of every hour of the device's uptime, the output of "show system uptime \| display xml" operational command might show incorrect value of the uptime calculated in seconds.
PR Number	Synopsis	Category: MX10K linecard
1622741	Constant increase of PCS errors may be seen on channelized port Product-Group=junos	On Junos platforms with MPC7E/MPC8E/MPC9E/LC2101/LC2103/EX9200-12QS/EX9200-40XS/MX10003, when 4x10GE-QSFP-LR optics is plugged in, the PCS errors of channelized ports will increase continuously, which might lead to traffic drop.
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.
1628050	MX10008 - Commit fail seen while testing family mpls filter is configured with ip-version match. Product-Group=junos	MX10008 - firewall filter "set firewall family mpls filter term from ip-version ipv4 destination-address ..." does not work on the MX10008 or MX10016. Using such configuration causes a commit error.
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
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.
PR Number	Synopsis	Category: VSRX platform software
1681042	ARP will not get learned if reth interface is configured with VLAN Product-Group=junos	On vSRX 3.0 platforms in High availability (HA) cluster environment, ARP (Address Resolution Protocol) will not get learned if VLAN is configured on the reth (redundant Ethernet) interface.
PR Number	Synopsis	Category: Xellent Platform issues
1678992	Traffic drop will be observed if an IP packet with TTL=1 is routed over VXLAN Tunnel Product-Group=junos	On the QFX10002-60C platform, in EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, an IP packet with TTL=1 to route over to the VXLAN tunnel causes a traffic drop.
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

20.4R3-S5 - List of Known issues

PR Number	Synopsis	Category: EX2300/3400 platform
1660130	EX2300-48MP EX2300-48MP: FXPC Core seen while loading 21.3R3.1 MR build with abort,junos_abort,panic, dcbcm_discover,pic_discover ,cmqfx_pic_sw_init,cmqfx_all_pic_sw_init ,cmqfx_module_init () Product-Group=junos	FXPC Core seen while loading 21.3R3.1 MR build with abort,junos_abort,panic, dcbcm_discover,pic_discover ,cmqfx_pic_sw_init,cmqfx_all_pic_sw_init ,cmqfx_module_init ()
PR Number	Synopsis	Category: QFX PFE CoS
1688455	The FPC crash would be observed when the same CoS configuration is applied with wildcard for all the physical interfaces and AE Product-Group=junos	On all Junos platforms, in a scaled scenario when some of the ge/xe/et interfaces are members of Aggregated Ethernet (AE) and the Class of Service (CoS) forwarding-class-set configuration is applied with a wildcard for all the physical interfaces and AE, it would trigger a Flexible PIC Concentrators (FPC) crash which leads to traffic loss.
PR Number	Synopsis	Category: ACX Interfaces IFD, IFL, vlans, and BRCM init
1217154	The logical interface-level statistics do not get the expected rate PPS values with the traffic flowing. Product-Group=junos	ACX doesn't have rate support (pps/bps) at ifl level. We have a limited statistics of 16 IFLs only due to BCM HW limitation.
PR Number	Synopsis	Category: "agentd" software daemon
1598351	Subscriber management daemons might continuously core and shutdown with RE sensors invalid configured Product-Group=junos	On all platforms support JTI (Junos telemetry interface), when 'set services analytics export-profile xxx format gpb-sdm' and 'set services analytics export-profile xxx transport tcp' are enabled on RE sensors, subscriber management related daemons (like authd, bbe-smgd, bbe-statsd, jdhcpd, smid) might continuously crash and core dumps are observed.
PR Number	Synopsis	Category: a20a40 specific issue
1681701	"%DAEMON-4: Set system alarm failed: Operation not supported by device" message is seen on high end SRX Product-Group=junos	On high end SRX platform, "%DAEMON-4: Set system alarm failed: Operation not supported by device" message is seen when system/chassis alarm is generated
PR Number	Synopsis	Category: Border Gateway Protocol
1669615	RPD crash might be observed due to multiple sequences of flap events Product-Group=junos	On all Junos and Junos Evolved platforms, when BGP update-threading is enabled and executed a certain sequence of flap events like flapping ISIS adjacencies, LDP, iBGP peers, clearing ARP table, interface flap for an hour by turning OFF and ON laser which triggers the rpd crash. It is a rare case.
1675893	The process rpd (route process daemon) crashes with BGP VPN (Border gateway protocol - Virtual Private Network) config, while ebgp (external bgp) routes exported into ibgp (internal bgp) core with vrf (virtual route forward) configured Product-Group=junos	On all Junos devices, rpd crashes with BGP VPN configured with vrf-label and exporting eBGP routes to iBGP.
PR Number	Synopsis	Category: Express BT PFE L3 Features
1651473	The BFD session might flap in some scaled system with churn Product-Group=junos	On all Junos and Junos Evolved AFT (Advanced Forwarding Toolkit) platforms, this is infrastructure enhancement which was done to avoid BFD session flapping during the system churn. Without this infra enhancement, BFD session flap would happen in some scaled system with churn.
1657659	Junos OS Evolved: PTX Series: Multiple FPCs become unreachable due to continuous polling of specific SNMP OID (CVE-2022-22211) Product-Group=junos	A limitless resource allocation vulnerability in FPC resources of Juniper Networks Junos OS Evolved on PTX Series allows an unprivileged attacker to cause Denial of Service (DoS). Please refer to https://kb.juniper.net/JSA69916 [juniper.net] for more information.
PR Number	Synopsis	Category: QFX Control Plane VXLAN
1650202	ARP/NS response to anycast IRB might fail due to missing mac-ip entry Product-Group=junos	On all Junos and EVO platforms, IRB (Integrated routing and bridging) static entry might be missing in the mac-ip-table for mac move allowed for local static IRB entry.
PR Number	Synopsis	Category: Device Configuration Daemon
1658016	when moving few child members from one AE bundle to another AE bundle observed error log "UI_CONFIGURATION_ERROR: Process: dcd, path: , statement: , ae12, Micro BFD local address should be configured on ae12 or lo0" Product-Group=junos	Due to the issue, an error log is printed, and DCD is restarted. But there is no functionality impact for BFD sessions. There may be a slight delay in the new config taking effect as DCD is restarted.
PR Number	Synopsis	Category: Layer 3 forwarding, both v4+v6
1553262	FEB coredump and reset if the core link or protocol flap Product-Group=junos	On ACX710 or ACX5448 platform, if the "chained-composite-next-hop" is configured and there are ECMP paths to remote peer, when one of the core facing interfaces has a protocol flap or interface flap, the FEB will core dump and reset.
PR Number	Synopsis	Category: OAM support on DNX
1592571	[eoam] [eoamtag] ACX5448-D :: EOAM:On delete remote-mep and and auto-discovery on R0, interface not going down on R1 where Action profile attached Product-Group=junos	On deleting remote-mep and auto-discovery in the peer, RDI sent by peer device is not processed in DUT. Hence, action configured for RDI event in the action-profile is not happening as expected.
PR Number	Synopsis	Category: ACX VRRP
1666853	Traffic loss is observed when the VRRP is configured over the AE interface Product-Group=junos	On ACX5448 platforms, the Virtual Router Redundancy Protocol (VRRP) is up from Routing Engine (RE) but the group is not created under the Packet Forwarding Engine (PFE) due to this VRRP virtual IP (VIP) is neither responding to ping nor accept any traffic when the VRRP is configured over Aggregated Ethernet (AE) interface. This results in traffic loss.
PR Number	Synopsis	Category: Control Plane for Node Virtualization
1685453	PICs on the GNF failed to come online after the chassisd restart Product-Group=junos	On MX platforms supporting node-slicing (MX480, MX960, MX2010, MX2020 & MX2008) have an issue that when GNF (Guest Network Function) chassisd restarts, the FPC doesn't restart as expected which causes the PIC (Physical Interface Card) to be offline.
PR Number	Synopsis	Category: EVPN control plane issues
1672749	Traffic drop might be observed in the EVPN-VPWS scenario Product-Group=junos	On Junos and Junos OS Evolved platforms that support Ethernet Virtual Private Lan-Virtual Private Wire service (EVPN-VPWS), traffic drop might be observed in the EVPN-VPWS scenario during a new nexthop addition due to a delay in processing the EVPN route resolution.
PR Number	Synopsis	Category: EX Diagnostics Software
1598805	The interface on SFP-T or SFP-SX might stop forwarding traffic on EX4600 Product-Group=junos	On EX4600, the interfaces on SFP-T or SFP-SX might stop forwarding traffic when MACSec and auto-negotiation is enabled on the ports. The interfaces would still show as up and the transmit and receive counters will increase. However, the transmit counters on the port will not increase.
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.
PR Number	Synopsis	Category: idp flow creation, deletion,notification, session mgr intfce
1686105	IDP unwanted attacks (false positives) detected on the traffic Product-Group=junos	On all Junos SRX platforms with 19.4 and 20.1 releases, IDP (Intrusion Detection and Prevention) false positive attacks can be exempted from the policy for traffic continuity. The impact is that unexpected signatures may trigger in certain conditions and IDP false positive attacks may be detected.
PR Number	Synopsis	Category: MX Inline Jflow
1444849	Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction. Product-Group=junos	Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.
PR Number	Synopsis	Category: Flow Module
1683835	With IFD+POST frag+no np-cache observed packets are dropped as "Drop: IP header error " Product-Group=junos	with IFD enabled, the fragment and non-fragment traffic processed in a burst, the non-fragmented packets might get dropped.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
1691071	Chassis cluster IP monitoring on the secondary node failed after the system reboot on the SRX platforms Product-Group=junos	On SRX platforms, IP monitoring on the secondary node failed when a reth (redundant Ethernet) interface consists of two or more than two interfaces on each node. Reth member interface which has a higher port number cannot receive ICMP (Internet Control Message Protocol) packet used for IP monitoring which will then put the system in an error state.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1626830	The process kmd might crash if the ike gateway is configured with two ip-address Product-Group=junos	The process kmd might crash if the ike gateway is configured with two ip-address and the IPSec vpn tunnel is failed over to another ike gateway address.
PR Number	Synopsis	Category: Platform infra to support jvision
1628807	Interface sensor data may not be decoded on line cards (MPC10E/MPC11/MPC12/LC9600) and Junos Evolved platforms Product-Group=junos	On MX platforms having line cards (MPC10E/MPC11/MPC12/LC9600) and Junos Evolved platforms, the interface sensor data might not be decoded.
PR Number	Synopsis	Category: SW PRs for MPC10E Interfaces
1642584	MPC10E: Quick 100G link-flaps has still some race conditions which can cause MQSS stream drain failures and xqss_sched_flush_queue failures Product-Group=junos	On MPC10E cards upon many very quick link down and up events in msec range might not always able to drain all traffic in the queue. This causes lost of traffic going through the interface. Traffic volume and class-of-service configuration does influence the exposure. See also PR1638410.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1598207	Sometimes MPLS LSP may go down due to a timing issue when a protected link goes down Product-Group=junos	When a protected link goes down, MPLS gets tunnel local repair message from RSVP and trigger CSPF computation. Next, MPLS gets link protection information through RRO notification. If MPLS receives TED notification first before RRO notification, then CSPF computation fails. Since the link protection flag is not set, MPLS thinks it is an unprotected link and brings down the LSP.
PR Number	Synopsis	Category: Multicast issues for VMX
1673489	Automatic Multicast Tunneling (AMT) is not supported on vMX platform Product-Group=junos	Automatic Multicast Tunneling (AMT) is not supported on vMX platform. Please contact your Juniper Account Team for a timeline of support.
PR Number	Synopsis	Category: vMX Data Plane Issues
1669261	vMX crashes due to MBUF leaks Product-Group=junos	vMX platforms (MX150) will crash as a result of the MBUF (Memory Buffer) leak.
PR Number	Synopsis	Category: QFX L2 PFE
1394822	QFX10000 platform drops Veritas CFS heartbeat packets Product-Group=junos	QFX10000 platform drops the Veritas CFS heartbeat , as result the Veritas CFS cannot work.
1549675	LLT may not work properly on the QFX10002-36Q platform Product-Group=junos	On QFX10002-36Q platform, Low Latency Transport protocol (LLT) might not work normally due to the ether-type "0xCAFE" of the LLT is not in the PFE support list.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1588704	The dcpfe might crash on QFX5k devices Product-Group=junos	On QFX5000 line of switches, the Flexible PIC Concentrator (FPC) or dcpfe process might go into a very uncommon state when multiple Broadcom Counter (bcmCNTR) threads are running or spawned in FPC. This state causes the dcpfe process to crash or the FPC to reboot. The purpose of bcmCNTR is to poll statistics from hardware.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1663804	Type-5 traffic drops when the device is configured without IRB in the EVPN-VxLAN scenario Product-Group=junos	On all QFX platforms, Ethernet VPN (EVPN) Type-5 traffic drops are observed when the device is configured only with Type-5 Virtual Routing and Forwarding (VRF) and without an Integrated Routing and Bridging (IRB) interface.
1679684	ARP resolution will fail on QFX5120 VC Product-Group=junos	On QFX5120 Virtual Chassis (VC) with OVSDB (Open vSwitch Database) VxLAN topology, ARP (Address Resolution Protocol) resolution fails if the traffic passes through VCP (Virtual Chassis Port) ports. As a result, ARP packets are dropped.
1681976	When L3 interface configured with vlan-id receives vxlan packet from a remote vtep, it adds extra 4095 tag and forwards to CE ports. Product-Group=junos	When "vlan-id" is configured by Service provider style on the underlay interface which is normally connected to the spine, extra vlan tag 4095 is added and forwarded to CE ports.. This has been fixed by the integration of new SDK (ASIC firmware) rather than a fix on Junos. The new SDK is integrated into Junos 21.4 and later. For example, set interfaces et-0/0/48 unit 3049 vlan-id 3049 set interfaces et-0/0/48 unit 3049 family inet address x.x.x.x/x
1692509	Error message "%PFE-3: fpc0 Failed to get ifl for ifl index = XXX" is generated when receives DHCP packet via remote vtep. Product-Group=junos	You may see the following error message in VXLAN environment. This can happen when the device receives DHCP packet via a remote vtep and L3 interface (IRB) is not assiged on the egress interface. Even though there is no DHCP configuration, the packet injection happens and it fails to get IFL index as there is no IRB interface on the egress interface. Oct 7 16:31:51.137 2022 d16-25 : %PFE-3: fpc0 Failed to get ifl for ifl index = 640
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.
PR Number	Synopsis	Category: Resource Reservation Protocol
1657872	Memory utilization keeps incrementing due to the path error message Product-Group=junos	On all Junos and Junos Evolved platforms, when a no-cspf Label Switched Path (LSP) with strict Explicit Route Object (ERO) is configured and the egress device is disconnected, a high rate of Path Error (PathErr) messages are observed which is leading to high memory utilization and triggering the chassisd crash that causes the device to be out of control, either it can not be accessible via console/ssh or it will not trigger Routing Engine (RE) switchover as well if it is dual-RE. So this would cause an outage.
PR Number	Synopsis	Category: MX10003/MX204 MPC defects tracking
1667298	In MX204 100G Links not coming up after reboot when using QSFP28-100G-CU3M with QFX5110 Product-Group=junos	DAC cable 100G might not come up with peers like QFX
PR Number	Synopsis	Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1648059	Interoperability issue between TRIO line cards and MPC10E and MPC11E AFT cards cause incorrect egress load balancing over Aggregated Ethernet links Product-Group=junos	On MX platforms, due to a software defect seen in interoperability scenarios on newer AFT-based MX cards (MPC10E and MPC11E), packets entering through legacy(non-AFT) card interfaces and exiting through AE interfaces via IRB may get incorrectly load balanced.
PR Number	Synopsis	Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1648473	The FPC crash might be observed during ISSU Product-Group=junos	On all Junos platforms with scaled environment equipped with specific line cards like MPC7E/MPC8E/MPC9E etc., when there are memory errors, the FPC crash might be observed. This happens during ISSU (In-service software upgrade).
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1522896	Egress traffic loss might happen because of PFE MTU feature problem Product-Group=junos	On MX and EX9200 serial platforms, under Ethernet VPN (EVPN) environment, packets routed using IRB interface could not be fragmented due to media maximum transmission unit (MTU) problem.

Modification History

First Publication 2022-11-10