Article Detail

Alert Type

SRN - Software Release 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.3R3-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.3R3-S3 is now available.

21.3R3-S3 - List of Fixed issues

PR Number	Synopsis	Category: Daily JUNOS build failures - automated builder use only
1691209	Use latest os-package when upgrading Product-Group=junos	Upgrade to 22.3R1 while using os-package published between July 2022 and November 2022 may incorrectly link os-libs package
PR Number	Synopsis	Category: EX4300 Platform
1678506	The interface on the device will go down when one or more interfaces are connected to the Advantech3260 device at another end Product-Group=junosvae	On EX4300 platforms with version 19.1R3 and above, the interface on the device will go down when the device is connected to the Advantech3260 device at the other end. It will have a traffic impact.
1680225	On EX4300-Virtual Chassis (VC) platforms, the pfex process might crash when PIC 2 is detached Product-Group=junos	On EX4300-Virtual Chassis (VC) platforms, Packet Forwarding Engine process (pfex) crash will be seen when Physical Interface Card 2(PIC 2) is detached then Physical Interface(IFD) is getting deleted before logical interface (IFL)deletion.
PR Number	Synopsis	Category: EX4300 Layer 2 implementation
1684072	The l2cpd process crash may be observed when disabling RSTP on an interface Product-Group=junos	On all Junos and Junos Evolved platforms, the l2cpd process may crash and generates the core when disabling RSTP (Rapid Spanning Tree Protocol) on an interface.
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: EX2300/3400 platform
1680408	On Ex2300 and EX3400, "set system ports console log-out-on-disconnect" does not allow user to log in via console. Product-Group=junos	On certain units, with "set system ports console log-out-on-disconnect", when you login to the device via a console, the user will be kicked out to the login prompt and be asked to login again.
PR Number	Synopsis	Category: SRX-1RU System Hardware defects
1658148	SRX4600 platforms in split brain scenario post ISSU Product-Group=junos	Junos SRX4600 platforms might go into spit brain mode after ISSU (In-Service Software Upgrade) is performed in presence of heavy traffic or huge volume of configuration. This issue causes one of the nodes to go into ineligible state, the control port is brought up late causing the split brain issue. Once the issue happens, there is traffic outage after ISSU as RG0 (Redundancy Group 0) split-brain happens, and one node may stuck in FPC (Flexible PIC Concentrator) present state.
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: SPC3 HW and SW Issues
1692611	SRX cluster may fail in a rare scenario when node status changes to disabled state without going through the ineligible state Product-Group=junos	On SRX platforms with chassis cluster configured, the RE(Routing-Engine) & PFE (Packet Forwarding Engine) connection may break, and the cluster may fail when the node status changes from primary/secondary state to disabled state without going through the ineligible state.
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
1698797	Fabric monitoring suspension and control link failure may cause HA cluster outage Product-Group=junos	In HA cluster, a local node failure which causes control link to go down may not guarantee the other node to take over primary if the fabric link monitoring suspension was triggered earlier before (e.g. - caused by a minor hardware failure), as the fabric link down event would be ignored when the other node was in RG0 ineligible state. This is a corner case to https://www.juniper.net/documentation/us/en/software/junos/chassis-cluster-security-devices/topics/topic-map/security-chassis-cluster-failover-parameters.html#id-understanding-chassis-cluster-control-link-heartbeats-failure-and-recovery__d27575e82. And PR1698797 fixed this defect.
PR Number	Synopsis	Category: chassisd related issues for high-end SRX platforms
1657958	Archived files created by non-root users may not include some files Product-Group=junos	On certain SRX platforms (1500,4100,4200 and 4600), the file archive command under a non-root user account may not archive all files under /var/log. This is a non-service impacting issue and the workaround is to either use the root user for file archiving under /var/log path or change the file permissions.
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: BBE interface related issues
1687138	The PIMv6 is not getting enabled for L2TP subscribers Product-Group=junos	On MX platforms, the Protocol-Independent Multicast version 6 (PIMv6) might not get enabled when it is configured over the Layer 2 Tunneling Protocol (L2TP) Subscriber Interface using the Dynamic-profiles.
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.
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.
1679646	The AGGREGATOR attribute will not be set correctly when the independent-domain is configured Product-Group=junos	On all Junos and Junos OS Evolved platforms, in BGP(Border Gateway Protocol) deployments with the "independent-domain" and aggregate routes configured under routing-instance, the AGGREGATOR attribute encapsulated within the ATTR_SET will not be populated correctly. This can result in unintended behavior or service impact because the BGP neighbors receiving this update may discard it as it is not RFC complaint.
PR Number	Synopsis	Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1695320	BMP EOR is sent with wrong peer address causing BMP failure Product-Group=junos	On all Junos and Junos Evolved platforms, on removing and re-applying BMP (BGP Monitoring Protocol) configuration, the EOR (End-of-RIB) message sent by the router has the wrong peer address updated causing BMP collector failure. There is no traffic impact due to this issue.
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.
1697827	Traffic drop is observed after deleting or deactivating the logical interface Product-Group=junos	On Junos QFX10K platforms configured with multiple logical interfaces (IFLs) on the same physical interface (IFD), if any one of the logical interfaces (IFL) is deleted or deactivated, it will cause a complete traffic drop on the other IFLs of the same IFD.
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: Virtual-chassis platform/chassisd infrastructure PRs for MX
1670345	The PFE I/O chip setup failed for some interfaces and causes those interfaces missing in PFE after backup chassis upgraded via Sequential Upgrade Product-Group=junos	When the MX virtual-chassis was upgraded by using the Sequential Upgrade method, there is the possibility that PFE provisioning may start before link training completes and all PICs are online. In such scenario, the ifd provisioning is preserved and if the preserved state is applied to the PFE before fabric training has completed and all the PICs have been powered on, ifd missing errors will be seen.
1697630	MX-VC: The backup VC router could become master after the system reboot Product-Group=junos	On Junos MX platforms when VC (Virtual Chassis) configuration is done and after the VC membership election, when routers are rebooted, the previously elected primary router will become the backup router and the backup router will come up as the primary router.
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
1693977	The oid tree jnxCosQstatEntry returns nothing for some interfaces after restarting class-of-service Product-Group=junos	The oid tree jnxCosQstatEntry returns nothing for some interfaces after restarting class-of-service.
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: CFM
1536417	FPC might core if CFM flap trap monitor feature in use Product-Group=junos	FPC generates core file when flap-trap-monitor is used and performance monitoring flap occurs.
PR Number	Synopsis	Category: QFX Access Control related
1693640	The dot1x reauthentication will not work for a port with VoIP VLAN Product-Group=junos	On Junos EX platforms, the dot1x clients will remain in connecting state after the 'clear dot1x interface' is done due to which the interface would not get authenticated to become a member of the configured access VLAN. When this happens, VLAN membership will not be formed.
1696906	The dot1x authentication will not be enabled on interfaces with specific configuration combination Product-Group=junos	On QFX and EX platforms running Junos, the dot1x authentication will not get enabled on the interfaces when both "set protocols dot1x authenticator interface server-fail-voip vlan-name " and "set switch-options voip interface vlan " are configured. As a result, the dot1x authentication will not work on the interfaces.
PR Number	Synopsis	Category: Device Configuration Daemon
1658016	Observed error log "UI_CONFIGURATION_ERROR Product-Group=junos	Due to the issue, an error log is printed, and the 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: Firewall Filter
1697959	Deactivating and activating the GRES causes churn in dfwd filter addition/deletion Product-Group=junos	On all Junos dual-RE platforms, when performing activate/deactivate Graceful Routing Engine Switchover (GRES) multiple times synchronization issues are observed between the master and backup dfwd process.
PR Number	Synopsis	Category: ACX BFD specific issues
1670684	New BFD sessions will not come up on ACX5448/ACX710 due to continuous flaps Product-Group=junos	On ACX710/ACX5448 platforms, if the Bidirectional Forwarding Detection(BFD) endpoint ID in chipset level reaches ~8K (for ACX710) or ~16k (for ACX5448),the following BFD session can't be created properly and be stuck at Init state. Once the issue is hit, disable BFD configuration and restart the bfdd process to make the endpoint ID roll over from 16.
PR Number	Synopsis	Category: CoS support on DNX
1603622	RED-dropped packets might be observed if hierarchical-scheduler is configured on ACX5448 platforms Product-Group=junos	On ACX5448 platforms, if hierarchical-scheduler is configured for an interface, during interface flaps or configuration changes, some of PFE buffers might become out of sync, which might cause packets drops even without congestion.
PR Number	Synopsis	Category: EVPN ELAN/E-TREE
1681980	Memory leak is seen on ACX710/5448 when the core link flaps Product-Group=junos	On Junos ACX5448 and ACX710 platforms, memory leak occurs in MPLS-EVPN (MultiProtocol Label Switching - Ethernet Virtual Private Network) environment when core-facing paths merge to one path caused by interface or protocol flaps. The memory leak causes complete traffic loss once the resource is exhausted.
1683321	The traffic drop would be observed with inter-vlan configuration when deactivating and activating the EVPN routing instance Product-Group=junos	On Junos ACX5448/ACX5448-M/ACX5448-D platforms, after deactivating and activating the Ethernet Virtual Private Network (EVPN) routing-instance, inter-vlan ping is not working on the same routing-instance and the duplicate packets were noticed between sites because of which data path and traffic will get impacted.
1690590	Packet forwarding fails on specific ACX Junos platforms due to flapping of core interface member link in the MPLS-EVPN environment Product-Group=junos	On specific ACX Junos platforms (ACX5448/ACX710), forwarding traffic is getting impacted the MPLS-EVPN environment as kernel memory is exhausted with continuous core link flaps.
PR Number	Synopsis	Category: ACX IRB specific issues
1683770	On Junos ACX the IP packets with VLAN tags do not get an ICMP response when sent out on the IRB interface Product-Group=junos	On ACX710, when locally generated VLAN(Virtual Local Area Network)-based IP packets (e.g. ping packet) are sourced from IRB (Integrated Routing and Bridging) interface, the Priority and DEI (Drop Eligibility Indicator) bits for the 802.1Q may be changed in PFE (Packet Forwarding Engine) and hence there will be no response to such packets from remote end causing service impact.
PR Number	Synopsis	Category: DNX L2 related features
1662686	PFE will crash after activating EVPN-ETREE service on ACX5448 platform 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 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: Manageability for Node Virtualization
1583324	JDM server creation might fail on junos node slicing setup in in-chassis mode Product-Group=junos	On MX platforms the JDM (Juniper Device Manager) server could not be created in in-chassis mode of junos node slicing, which results in mgd process crash and affects GNF's (Guest Network Function) provisioning.
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. (See Also https://kb.juniper.net/TSB69942 [juniper.net]).
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
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.
PR Number	Synopsis	Category: Control plane EVPN multicast
1670435	EVPN multicast traffic may get impacted because of routes getting stuck in the kernel routing table (krt) queue Product-Group=junos	On all Junos and Junos Evolved platforms with Ethernet Virtual Private Network(EVPN) enabled, in the presence of certain triggers like rpd restart, rollback of configuration etc., EVPN multicast routes might get stuck in the kernel routing table (krt) queue due to which the corresponding routes in the forwarding table may point to 'fictitious' next hops, resulting in traffic disruption.
PR Number	Synopsis	Category: EX4400 PFE software
1694800	On a PVLAN with DAI ARP packets will be forwarded between isolated ports Product-Group=junos	On Junos based EX platforms, when Dynamic ARP (Address Resolution Protocol) Inspection (DAI) is configured on PVLAN (Private Virtual Local Area Network), ARP packets coming from the LAG (Link Aggregation Group) are forwarded to other isolated access ports.
PR Number	Synopsis	Category: EX4400 platform
1690674	On EX4100 and EX4400 platform, alarm 'PEM is not supported' might be seen. Product-Group=junos	On EX4100 and EX4400 platform, system alarm 'PEM is not supported' might be seen with a specific trigger and it keeps remain even after supplied power.
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.
1693424	Traffic loss is observed when the ECMP path is IRB over AE (IPv4->MPLS) Product-Group=junos	On QFX10002 platforms, when the ECMP (Equal-cost multi-path) path is IRB (Integrated routing and bridging) over AE (Aggregated Ethernet) {IPv4->MPLS (Multiprotocol Label Switching)} results in packets getting discarded for which traffic loss is observed.
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: 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: GMIC2 platform driver issues
1693211	MACsec on logical interfaces fails after port flap Product-Group=junos	MACsec configured on logical interfaces (IFL) would fail to restore after a flap of the parent physical interface. This will lead to Cyclic Redundancy Check (CRC) errors and failure to pass traffic.
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: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1663050	The rpd core may be seen when there is a synchronization issue Product-Group=junos	On Junos ACX710 device, the rpd core may be seen. The rpd keeps running and there is no functional impact.
PR Number	Synopsis	Category: Fast Ethernet interfaces
1684142	Traffic is getting impacted as interface hold-time is not working with wan-phy framing Product-Group=junos	On all Junos MX series platforms, when hold timer and wan-phy are configured, traffic gets impacted when the link goes down on an interface within the configured hold timer.
PR Number	Synopsis	Category: ISIS routing protocol
1677567	Label traffic will be dropped at the one-hop LSP stitching node if the packet has more than one label Product-Group=junos	On all Junos and Junos Evolved platforms supporting the Segment Routing (SR) feature, when segment routing and Label Distribution Protocol (LDP) stitching are configured, the label traffic drop is observed at the one-hop Label Switched Path (LSP) stitching node when the labeled packet is received with more than one label.
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: JFlow bug tracker for SRX platforms
1688627	The system may crash when Jflow inactive timeout is configured to be less than 'previous flow-inactive-timeout + 180' seconds Product-Group=junos	On SRX platforms, when Jflow inactive timeout is configured to be less than 'previous flow-inactive-timeout + 180' seconds result in a system crash and core files are generated.
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 Express Path is enabled Product-Group=junos	On SRX5K series devices with IOC2 line-cards installed, when running JUNOS 21.2R1 or later where Express Path is enabled by default, sessions traversing the IOC2 card would time out early, leading to a traffic loss and unpredictable flow behavior.
1692100	SOF was incorrectly offloading short-lived flows leading to early exhaustion of NP memory, reducing overall device performance Product-Group=junos	On SRX5K and SRX4600 series platforms, Automated Express Path (SOF) was incorrectly offloading short-lived flows. This consumed additional resources on the Network Processor (NP) which could lead to an early exhaustion of its memory, reducing overall device performance. By default, Automated Express Path (SOF) is designed to offload flows which are high bandwidth/throughput in nature.
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.
1685116	The user authentication page is not rendering on the client browser Product-Group=junos	On all Junos SRX platforms due to cross-origin restriction access, the domain page does not load. The issue happened due to a firewall authentication failure.
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: 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: IPSEC/IKE VPN
1648249	Vmcore is seen on Junos platforms when data plane IPSec is configured Product-Group=junos	On Junos platforms, when data plane IPsec (IP Security) is configured, the IP layer passes bad mbuf information to the IPsec layer causing the core which is triggered by data plane ESP (Encapsulating Security Payload) packets coming to RE (Routing Engine).
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
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: Port-based link layer security services and protocols that a
1693730	Traffic loss will be seen when MACSEC is configured Product-Group=junos	On all Junos platforms where MACSEC(Media Access Control Security) is configured with 60s SAK (secure association key) rollover, traffic loss will be observed during RE (Routing Engine) switchover.
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: Multiprotocol Label Switching
1690458	On a controller based MPLS setup with container LSPs, rpd daemon crashes after LSP deletion occurs Product-Group=junos	On all Junos-based platforms, in a scenario where an external controller is provisioned, rpd crashes when an externally controlled container LSP (Label Switched Path) is deleted and the software tries to update its status.
1697982	[MX]L2VPN ping is failing when UHP rsvp LSP is used Product-Group=junos	MPLS L2VPN ping is getting failed when MX is egress. In egress, RE verifies whether received label is VC label or not. For most of the platforms, tunnel label will be removed in PFE before punting the echo request packet to RE. But in this platform, tunnel label is not removed hence RE verifies this tunnel label and it is returning no-mapping.
1701800	Memory leak issue in TED Product-Group=junos	On all Junos and Junos Evolved platforms, a memory leak is observed in TED (Traffic Engineering Database) when the inet tables is not cleaned up after routing instance deactivation.
PR Number	Synopsis	Category: Category for tracking Olympus-MX issues
1670507	Fabric Destination error and Fabric plane going in check state after changing the fabric redundancy mode Product-Group=junos	On MX240/480/960 platforms, Fabric drops are observed when changing the fabric redundancy mode.
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: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1697643	NTP threshold reject action does not work on all Junos platforms Product-Group=junos	When CLI command "set system ntp threshold action reject" is set on all Junos platforms, the nodes are still getting NTP updates although the NTP time is above the configured threshold.
PR Number	Synopsis	Category: PFE Peer Infra
1547903	Tnplock independent implementation from the jlock Product-Group=junos	software interrupts: tnplock and jlock will work independently to prevent jlock hog.
1608038	Improvements for internal control traffic handling Product-Group=junos	Improvements for internal control traffic handling are introduced for intra-chassis components communication.
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: OSPF routing protocol
1700966	OSPF stuck in InitStrictBFD state for the neighbor which doesn't send LLS header Product-Group=junos	When Strict BFD (Bidirectional Forwarding Detection) for OSPF (Open Shortest Path First) configured on all Junos OS and Junos OS Evolved platforms, and one or more OSPF neighbors don't support Link-Local Signaling ("LLS", RFC5613), the adjacency with these neighbor(s) might stuck in InitStrictBFD state upon adjacency initialization. Neighbor doesn't support LLS, hence it doesn't attach the LLS header, which is a pre-requisite for Strict BFD.
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: 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.
PR Number	Synopsis	Category: JRR - VRR running on SRX4200
1691694	A 802.1Q tagged Ethernet traffic with an expected VLAN ID and with a non-zero 802.1P value ingressing a JRR200 VLAN enabled interface is dropped. Product-Group=junos	A 802.1Q tagged Ethernet traffic with an expected VLAN ID and with a non-zero 802.1P value ingressing a JRR200 VLAN enabled interface is dropped. This problem could happen at a JRR200 system running a 21.1+ JUNOS release.
PR Number	Synopsis	Category: vMX Platform Infrastructure related issue tracking
1671347	MX150 platform reports error for bandwidth license Product-Group=junos	MX150 reporting error for bandwidth license restricting bandwidth after upgrade.
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
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.
1683771	Traffic loss is seen when MAC flaps between the MC-AE interface and the ICL interface. Product-Group=junos	On QFX5K/EX46XX platforms, post zeroizing, traffic loss is seen when the optics of the child interface of an Inter Chassis Link (ICL) Aggregated Ethernet(AE) interface is unplugged or Multi Chassis-Aggregated Ethernet(MC-AE) ICL configuration is deleted(Using delete chassis aggregated-devices ethernet device-count).
1694076	PFE crash is seen on all Junos QFX5K and EX46xx platforms with L2PT configuration Product-Group=junos	PFE (Packet Forwarding Engine) crashes on all Junos QFX5K and EX46xx platforms when L2PT (Layer 2 Protocol Tunneling) is configured on the interface having flexible-vlan-tagging with encapsulation extended-vlan-bridge. It causes a traffic impact.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1695943	JUNOS_REG::QFX5110-32Q:VC:::After loading "20.4R3-S5.3" dcpfe core is observed and device is unstable Product-Group=junos	On QFX5K VCF platform, the PFE core will be seen due to invalid usage of snprintf (PR 1688206).
PR Number	Synopsis	Category: QFX MPLS PFE
1687257	QFX5120 will drop ingress traffic on an l2circuit configured interface on continuous flapping Product-Group=junosvae	On QFX5120 platforms, when a flap occurs in a Layer 2 Circuit (L2Circuit) configured interface, l2circuit configuration programming fails on the interface and leads to a traffic drop.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1651827	The MAC address from local CE may not be learned due to the VLAN programming issue Product-Group=junos	On QFX5k series platforms, MAC address from local CE (customer edge) might not get learned when EVPN (Ethernet VPN)/VxLAN (Virtual Extensible LAN) is configured. The traffic drop is expected as MAC learning may not happen.
1687565	VxLAN configured on access port breaks L2 connectivity with "vxlan encapsulate-inner-vlan" knob Product-Group=junos	On all Junos QFX5k platforms, L2 connectivity fails when "vxlan encapsulate-inner-vlan" knob is configured on an access port. It impacts a forwarding plane and causes a traffic impact.
1691417	When a new VLAN is added on trunk interfaces, the newly added VLAN member drops the traffic Product-Group=junos	On QFX5K platforms with Virtual Extensible VLAN (VXLAN) configuration, when a new Virtual Local Area Network (VLAN) is added to the trunk, it is not getting added and traffic loss will be seen on the newly VLAN added port.
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 -
1670240	The dcpfe process might generate core-dumps and FPC might crash after line card reboot or switchover Product-Group=junos	On QFX10K, PTX10K, PTX5K, PTX3K, and PTX1K platforms, the dcpfe process might generate core-dumps and FPC might crash after line card boot or switchover. The BIST (Built-in Self Test) might report an error in the HMC (Hybrid Memory Cube) and restart the dcpfe process causing FPC crash.
PR Number	Synopsis	Category: QFX5100 Interface related issues
1688023	The LLDP output packets are not transmitting on the em0 interface of Junos and Junos OS Evolved platforms Product-Group=junos	On Junos and Junos OS Evolved platforms, if a management Ethernet interface(em0) has an inet or inet6 family configured and "delete interfaces em0" is issued, the Link Layer Discovery Protocol (LLDP) output packets will stop transmitting, causing the LLDP neighborship to remain down in peer router.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1667397	Some 10G ports are missing from FPCs after rebooting the device with 1G Ports enabled on one FPC Product-Group=junosvae	On Junos EX4650 virtual chassis (VC) setup and QFX5120-48y platforms, after enabling 1G ports on one FPC and rebooting the entire VC, some 10G ports which have already been up and running on other FPCs may miss from CLI output of "show interfaces terse". Production traffic will be impacted by this issue. The cause of issue is that configuration change on one FPC is propagated to other members of VC. Configuration files should be removed on FPCs on which the 10G ports are present. After that, upgrade/re-image the VC to fixed versions and issue will not be observed any longer.
PR Number	Synopsis	Category: Resource Reservation Protocol
1625438	Unexpected traffic loss on LSP headend might be observed when downstream IGP metric changes Product-Group=junos	On all Junos and all EVO platforms, when Resource Reservation Protocol (RSVP) metric changes due to change in Interior Gateway Protocol (IGP) metric or static metric, traffic loss might be observed for less than one second. This happens because the old route is deleted before addition of new route with new metric by RSVP.
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.
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.
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.
1685182	RSVP path tear is not encapsulated by the MPLS header when bypass is configured Product-Group=junos	On all Junos and Junos Evolved platforms, RSVP(Resource Reservation Protocol) path tear is not encapsulated by the MPLS(Multiprotocol Label Switching ) header, when "no-enhanced-frr-bypass" is configured on the routers that undertake FRR(fast re-route) procedures after the failure.
PR Number	Synopsis	Category: Cover Logical System Infrastrcuture Development
1694449	The process srxpfd/ flowd will crash on SRX devices Product-Group=junos	On all SRX platforms (except branch SRX series) configured with chassis cluster redundancy group, when numerous logical interfaces or IFLs (> 1K) are deleted and traffic is running for those IFLs, or if the RG failover then the process srxpfed/ flowd will crash.
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
1594014	During reboot, "warning: requires 'idp-sig' license" can be seen on the screen even when the device has valid license Product-Group=junos	If a device is rebooted manually or reboots for any other reason, The following messages can be seen on the boot up screen even when the device has valid license and proper configuration to use the features like IDP/UTM
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.
1682962	Auto-negotiation is not getting reflected on the MPC7E-10GE line card Product-Group=junos	On all MX platforms with MPC7E-10GE line card, auto-negotiation will not be set properly when changing the port speed from 10GE to 1G on a port with auto-negotiation configured. The port remains down until the commit is done separately for changing the port speed.
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: SRX-1RU platfom related protocol, QoS, filtering features et
1689705	SNMP MIB walk for jnxBoxDescr OID returns incorrect value Product-Group=junosvae	On SRX4600 platforms running Junos, SNMP MIB walk for jnxBoxDescr OID returns the incorrect chassis name and model. This is only a display issue with no service 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=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: ZT/YT pfe qos software issues
1688416	The COS queue burst size computation was incorrect when the explicit queue shaping rate was not configured, causing initial packet drops Product-Group=junos	On specific linecards MPC10/11/LC9600 and MX304 device, there was an issue with the COS (Class of Service) queue burst size calculation when the explicit queue shaping-rate was not configured, resulting in an initial packet drop and the COS queue burst size computation was incorrect which causes packets to drop initially.
1696089	FPC crash is observed in GNF scenario with CoS configuration Product-Group=junos	On Junos and Junos Evolved platforms, in GNF (Guest Network Function) setup when CoS (Class of Service) configuration is attached on an IFL (Interface Logical) stacked over another IFL and the CoS configuration message is received on an FPC (Flexible PIC Concentrators) which does not host the IFLs IFD (Interface Device), then the FPC can crash because the FPC does not have any information about the IFLs or underlying IFDs.
PR Number	Synopsis	Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1669609	The error will be observed if eTree is used with EVPN-MPLS and the routing-instance is changed Product-Group=junos	On all MX platforms, when eTree is used with EVPN (Ethernet VPN) over MPLS (Multiprotocol Label Switching) and the routing-instance is changed, the syslog errors will be reported. This happens when the leaf label is not properly updated in the table. There is no service impact other than error message.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1631217	The core interface goes down Product-Group=junos	Using static LSP(labeled switched path) configuration, the child node is not removed from the flood composite when the core interface goes down.
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
1701147	FPC restart and core dump generated in MPLS scaled scenario with always-mark-connection-protection-tlv" configured. Product-Group=junos	FPC restart and core dump generated in MPLS scaled scenario with always-mark-connection-protection-tlv" configured.
PR Number	Synopsis	Category: Issues related to all UI tools (mgd-bsd/cli-bsd, XML and DMI
1681656	System uptime display is shown in minutes instead of seconds Product-Group=junos	On all Junos and Junos Evolved platforms, after the device reboot, show system uptime command is showing time in minutes instead of seconds for 24 hours.
PR Number	Synopsis	Category: VMHOST platforms software
1646339	The alarm might not be generated for EDAC errors until the FPC is rebooted Product-Group=junos	On all MX and PTX platforms, EDAC errors are triggered but alarms are not observed until the FPC gets rebooted due to the data corruption in hardware.
PR Number	Synopsis	Category: VSRX platform software
1680874	vSRX instance in GCP gets stuck in halt state randomly when trying to reboot multiple times Product-Group=junos	vSRX instance in GCP (Google Cloud Platform) freezes during restart and does not shutdown. This issue is very difficult to hit in production as it is seen very rarely after several reboots.
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: 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
1692525	ALG child session will not be transported through the DS-Lite tunnel which might lead to traffic failures in absence of a direct route to the host Product-Group=junos	On Junos MX240/MX480/MX960 platform with MX-SPC3, a tunnel ID of the control session is not updated properly on the gate created for Session Initiation Protocol (SIP) Application Layer Gateway (ALG), which is leading to the gate hit session not mapping back to the Dual-Stack Lite (DS-Lite) tunnel. This might result in traffic failure if the client does not have a direct route to the host.
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

21.3R3-S3 - List of Known issues

PR Number	Synopsis	Category: EX4300 Platform implementation
1668414	On EX4300-48MP, NSSU abort is seen with "error: rebooting VC". VC instability and dc-pfe core is observed after reboot. Product-Group=junos	On EX4300-48MP, NSSU abort is seen with "error: rebooting VC". VC instability and dc-pfe core is observed after reboot. Resolved In:
PR Number	Synopsis	Category: EX-Series VC Infrastructure
1685067	EX4600-VC - Master RE reboot and All-member reboot lead to PFE Manager hogging logs when SFP-T is plugged in Product-Group=junos	On Junos EX4600 Virtual Chassis (VC), the master RE reboot and all-members reboot lead to the PFE Manager hogging logs when SFP-T pluggable is installed in. The PFE Manager hogging logs has no functionality impact (PR 1641556). Resolved In: junos:20.2R3-S6 junos:21.4R3-S2
1700133	One of the Virtual Chassis members on EX4600-VC might be disconnected during VC initialization Product-Group=junos	On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected. Resolved In: junos:20.2R3-S7
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. Resolved In: junos:20.2R3-S6 junos:21.4R3-S1 junos:23.1R1
PR Number	Synopsis	Category: CoS support on ACX
1689604	EVPN Packets may go to incorrect queues due to the wrong classification and may lead to packets drop during congestion Product-Group=junos	On Junos ACX5448 and ACX710 devices, in EVPN (Ethernet Virtual private network) with a multihoming scenario, if one link fails traffic will switch over to another link. When FPC is restarted and the dot1p classifier is changed, restore the failed link. Packets may not go to the correct queue due to the wrong classification when traffic switches back to the original link, and traffic drops may happen during congestion. Resolved In: junos:21.2R3-S4 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Border Gateway Protocol
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. Resolved In: evo:20.4R3-S5-EVO evo:21.2R3-S3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:20.2R3-S2-J20 junos:20.2R3-S6 junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR Number	Synopsis	Category: Express BT PFE L3 Features
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. Resolved In: evo:20.4R3-S4-EVO evo:20.4X6-EVO evo:21.3R3-EVO evo:21.4R2-EVO evo:21.4R3-EVO evo:21.4X1-EVO evo:22.1R2-EVO evo:22.2R1-EVO evo:22.3R1-EVO junos:22.2R1 junos:22.3R1
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. Resolved In: evo:21.2R3-EVO evo:21.4R2-EVO evo:21.4R3-EVO evo:22.2R1-EVO junos:20.2R3-S7 junos:20.4R3-S5 junos:21.2R3 junos:21.3R3 junos:21.4R2 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.3R1
PR Number	Synopsis	Category: SRX1500 platform software
1690621	SRX1500 chassis cluster port ge-0/0/1 does not work in switching mode Product-Group=junos	SRX1500 chassis cluster port ge-0/0/1 on a node is not working in switching mode when this interface is configured in L2 (layer2) mode. Resolved In: junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Express ASIC platform
1683562	On PTX5000 platforms when a command is issued to power off an FPC, it gets stuck in the 'Announce Offline' state Product-Group=junos	When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot ) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to. Resolved In: junos:19.2R3-S5-J2 junos:20.4R3-S2-J17 junos:20.4R3-S6 junos:21.4R3-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
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. Resolved In: junos:19.4R3-S10 junos:20.2R3-S6 junos:20.3R3-S6 junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR Number	Synopsis	Category: Integrated Routing & Bridging (IRB) module
1685406	The protocol MTU for the IRB interface is not rolled back when the MTU of the IRB or IFD interfaces is modified or deleted Product-Group=junos	On all Junos platforms, the maximum transmission unit (MTU) on the Integrated Routing and Bridging (IRB) interface is not getting reset when the MTU configuration on IRB or IFD is removed. When MTU configuration is removed from the IRB interface, the internal data structure for the MTU configuration is not getting reset which might affect traffic and it is a rare case. Resolved In: junos:20.2R3-S6 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:23.1R1
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1686523	VPLS traffic loss might be seen when deleting and adding a routing-instance Product-Group=junos	VPLS (Virtual Private LAN Service) traffic stops on all Junos and Junos Evolved platforms after adding/changing interfaces in the routing instance. Restarting l2ald daemon may restore the VPLS services. Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.4R3-S5 junos:21.4R3-S2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: Multiprotocol Label Switching
1694648	The rpd crash will be observed during the MPLS label block allocation Product-Group=junos	On all Junos and Junos Evolved platforms in the Multiprotocol Label Switching (MPLS) scenario, the rpd crash will happen in rare conditions during MPLS label block allocation. Resolved In: evo:20.4R3-S6-EVO evo:21.2R3-S4-EVO evo:22.1R3-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.2R3-S7 junos:20.4R3-S6 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Microkernel for neo mpc
1670137	Multibit ECC error causes the whole MX platform chassis to go down Product-Group=junos	Faulty FPC (Flexible PIC Concentrator) on the MX platform chassis exhibiting multibit ECC (Error Checking and Correction) error (L2 cache error) will trigger this issue. The whole chassis goes down until the faulty FPC is removed from the chassis. Resolved In: junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR Number	Synopsis	Category: TCP/UDP transport layer
1685113	Random BGP session flap with error "BGP_IO_ERROR_CLOSE_SESSION" Product-Group=junos	On all Junos and Junos Evolved platforms, a random BGP (Border Gateway Protocol) session flaps will be observed immediately after committing unrelated configuration changes with the error "BGP_IO_ERROR_CLOSE_SESSION" along with a connection reset. This issue is generic to any TCP (Transmission Control Protocol) connection that has MD5 (Message-Digest Algorithm) enabled on it. Resolved In: junos:20.4R3-S6 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R2-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Express Chip L3 software
1660606	MVPN traffic is getting dropped on PTX/QFX series platforms Product-Group=junos	On all Junos PTX and QFX10k series platforms, MVPN (Multicast Virtual Private Network) traffic is getting dropped with a discarded error. This is because, the way LSI (Label Switched Interface) interface data is carried from ASIC (Application-Specific Integrated Circuit) to PFE (Packet Forwarding Engine) is changed, causing MVPN to break. Resolved In: junos:19.3R3-S7 junos:19.4R3-S9 junos:20.3X75-D35 junos:20.3X75-D41 junos:20.3X75-D42 junos:20.3X75-D43 junos:20.4R3-S4 junos:21.1R3-S3 junos:21.2R3-S1 junos:21.2R3-S2 junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.2R2 junos:22.3R1
PR Number	Synopsis	Category: Resource Reservation Protocol
1694777	Restarting FPC or router reboot might causes some CCC interfaces to go down due to a 'Remote CCC down' Product-Group=junos	On all Junos and Junos OS Evolved platforms, if CCC (Circuit Cross-Connect) is configured to use a label-switched-path such as IGP routed, i.e., no-cspf and no strict ERO (Explicit Route Object) configuration, then restarting egress CCC node or restarting FPC on the egress CCC node containing remote-interface-switch configuration multiple times may cause CCC to remain stuck in remote-if-down state, resulting in loss of traffic. (The knob 'remote-interface-switch' is configured on the egress LER of the RSVP-TE LSP (Resource Reservation Protocol-Traffic Engineering label-switched-path) which binds the LSP terminating on the node to a local interface). Resolved In: evo:22.4R2-EVO evo:23.1R1-EVO junos:20.4R3-J8 junos:22.4R2 junos:23.1R1
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. Resolved In: junos:21.1R3-S4 junos:21.2R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1
1646661	21.3R2:SRX_RIAD:srx1500,srx4200:SKYATP:IMAP/IMAPS Email permitted counter is not incremented in AAMW email statistics while testing whole email block. Product-Group=junos	The SKYATP:IMAP/IMAPS Email permitted counter may have incorrect value under certain conditions. Resolved In: junos:22.3R2 junos:23.1R1
PR Number	Synopsis	Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1700321	VLAN tags are imposed incorrectly when traffic is routed over IRB going out of the access interface Product-Group=junos	On MX platforms, traffic egressing on the IRB (Integrated Routing and Bridging) interface with the underlying L2 (layer2) access port has VLAN tags imposed incorrectly. Resolved In: evo:23.1R1-EVO junos:21.2R3-S4 junos:23.1R1
PR Number	Synopsis	Category: Xellent Platform issues
1610745	"output-mac-control-frames" and "output-mac-pause-frames" counters are not incrementing on QFX10002-60C Product-Group=junos	In QFX10002-60C under mac statistics "output-mac-control-frames" & "output-mac-pause-frames" does not increment. Resolved In:

Modification History

First publication 2023-01-04