Alert Type
PSN - Product Support Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX EX MX NFX PTX QFX SRX vSRX excluding QFX5K EX4100 EX4400 EX4650
Alert Description
Junos Software Service Release version 22.4R3-S2 is now available for download from the Junos software download site.
This posting excludes images for the QFX5K, EX4100, EX4400, and EX4650 platforms
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 22.4R3-S2 is now available.
22.4R3-S2 - List of Fixed issues
PR Number
Synopsis
Category: EX4300 Layer 2 implementation
1797422
DHCP IP assignment will fail on VoIP phone connected to a VXLAN access port
Product-Group=junos
On EX4300-48MP platform, in Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, Dynamic Host Configuration Protocol (DHCP) IP assignment for a Voice over IP (VoIP) phone connected to a VXLAN enabled access port will not work.
PR Number
Synopsis
Category: EX2300/3400 platform
1772477
Turning port beacon LED on or OFF may not change the LED status
Product-Group=junos
On EX2300, turning port beacon LED on or OFF may not change the LED status. There is no service impact due to this.
1781317
Error is shown on system when pvidb variable is accessed
Product-Group=junos
On Junos EX platforms, when pvidb variable which is unkown is tried to access from a device, pvidb error messages will be seen, There is no impact on service due to this.
1789272
Watchdog SPI transaction is causing the interface flap in the system
Product-Group=junos
On EX2300-MP platforms, when the SPI (Serial Peripheral Interface) bus is accessed by multiple processes simultaneously results in watchdog reset due to the lack of lock-unlock operations. Consequently, this can lead to interface flaps affecting the traffic flow.
PR Number
Synopsis
Category: NFX Layer 3 Features Software
1776216
IPsec Tunnel behind NAT stops passing traffic when the NAT port Number or IP address changes
Product-Group=junos
On Junos SRX and NFX series platforms, when the peer device located behind a Network address translation (NAT) device, experiences a change in the NAT port number or Internet Protocol (IP) address, the next Dead Peer Detection (DPD) or rekey process fails to update the port number in the existing tunnel NAT Traversal (NAT-T) flow session if the DPD "always-send" is being configured. This leads to communication failure over the Internet Protocol Security (IPsec) tunnel.
PR Number
Synopsis
Category: SPC3 HW and SW Issues
1780282
Unexpected failover will be seen when there is communication loss between CP and SPU on SRX platforms with web-authentication or web-redirect is configured
Product-Group=junos
On all SRX series firewall with web-authentication or web-redirect configured, with continuous traffic from different IPs for which authentication needs to be done in such scenarios firewall authentication entries are out of sync between Central Point (CP) and Services Processing Units (SPU) modules caused attempt to delete same firewall authentication entry twice, that causes invalid memory access resulting into the core-dump followed by failover. Traffic impact will be seen during the fail over.
PR Number
Synopsis
Category: "agentd" software daemon
1772435
"/components/component/power-supply/" sensor leaves and values are not streamed in gNMI and the data is streamed via gRPC in latest master 24.1 builds
Product-Group=junos
On all evo platforms, power-supply data is not getting streamed via gnmi. Issue shall be resolved in D41
PR Number
Synopsis
Category: MPC10/11/LC9600 Chassis Category
1715831
MX reports continuous PLL Access Failures for LC9600
Product-Group=junos
For platforms which are designed with Junos and EVO there could be the repetition of PLL Access Failure logs which are cleared after 5 seconds
PR Number
Synopsis
Category: MPC Fusion SW
1746643
FPC process crash will be observed after performing the ISSU
Product-Group=junos
On Junos MX platforms with MPC2E-3D-NG, MPC3E-3D-NG and MPC2E NG HQoS line cards with MIC -> 10x 1GE(LAN) -E SFP, the Flexible PIC Concentrators (FPCs) process crash will be observed after performing the In-Service Software Upgrade (ISSU).
1777534
On MX and EX platform replacing the line-cards may trigger FPC to be offlined due to unreachable destinations
Product-Group=junos
On Junos MX and EX9200 platforms when replacing MPC2E-NG and EX9200-40XS with MPC3E-NG, SCBE3 and EX9200-MPC cards, inserting the new MPC may cause new and other line cards to go offline due to unreachable destinations. This happens due to some registers on the fabric card is not properly updated once the fabric channel bonding has changed and impacts the traffic.
PR Number
Synopsis
Category: Application Quality of Experience
1790782
The srxpfe or flowd process will crash while trying to update the path probe statistics
Product-Group=junos
On Junos SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX4100, SRX4200, SRX4600, vSRX2, vSRX3, and NFX platforms, while trying to update the path probe statistics the flowd/srxpfe process will crash when APPQOE best path changes to no path selected state. The process crash will restart the PFE affecting the traffic.
PR Number
Synopsis
Category: a20a40 specific issue
1663839
Syslog message CHASSISD_IPC_WRITE_ERR_NULL_ARGS are observed at commit
Product-Group=junos
Syslog message CHASSISD_IPC_WRITE_ERR_NULL_ARGS is observed at commit on SRX5K platforms. This is caused by unsupported chassis component connection on SRX5K platforms during commit checks. This syslog message is informational only for SRX5K, and was removed.
1761928
E2E packet capture will be corrupted
Product-Group=junos
On SRX platforms, when services-offload is enabled, End-to-end (E2E) packet capture will be corrupted.
1784775
The chassis cluster failover is seen post ISSU
Product-Group=junos
On SRX5K platforms with SPC3, chassis cluster failover is seen post ISSU. The SPC3 connects to the wrong Routing Engine which impacts all the PICs affecting the complete traffic.
1787219
Insufficient power alarm observed in SRX5K platforms
Product-Group=junos
On Junos SRX5600 and SRX5800 platforms, FPC (Flexible PIC Concentrator) will not come online due to insufficient power, leading to service disruption.
1793262
FPC reboot seen on SRX platforms with SPC3 card post RG failover
Product-Group=junos
On SRX5K platforms with SPC3 card, the FPC (Flexible PIC Concentrator) card reboots when a RG0 failover (in chassis cluster scenario) is performed. Due to this, traffic impact can be seen.
PR Number
Synopsis
Category: common or misc area for SRX product
1779749
Traffic loss due to PPM not offloading LACP
Product-Group=junos
On SRX5K platforms, the LACP (Link Aggregation Control Protocol) packets are reaching the RE (Routing Engine) instead of ppm (Periodic packet management) which is causing extra strain on RE leading to dcpfe core dumps and causing LACP connections to go down or flap.
PR Number
Synopsis
Category: BBE Layer-2 Bitstream Access
1796125
The broadband subscriber (L2BSA subscribers) on the core interface logging out with interface state changes
Product-Group=junos
On all Junos platforms, any configuration changes that involve interface down/up sequence, result in logging-out L2BSA (Layer 2 Broadband Subscriber Access) subscribers associated with that core interface.
PR Number
Synopsis
Category: BBE routing
1781938
Access route may get stuck in the routing table after trying to change the prefix length using CoA message
Product-Group=junos
On Junos MX platforms with subscribers management enabled, the access route may get stuck in the routing table failing to update or be removed as expected. This occurs when a user attempts to modify the prefix length associated with this route using a Change of Authorization (CoA) message. This may lead to traffic loss, and if a subscriber goes down following the CoA change, there is a failure to bring that specific subscriber back up.
PR Number
Synopsis
Category: Border Gateway Protocol
1785227
Applying aggregate-bandwidth for BGP paths removes all other communities from the advertised routes
Product-Group=junos
On all Junos and Junos Evolved platforms, when load-balancing on BGP is configured with multipath and along with that aggregate-bandwidth knob is enabled, communities are dropped from the routes that are going out. The community attributes are not propagated.
PR Number
Synopsis
Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1796530
High CPU utilization due to BMP to be running with the longest and highest run count
Product-Group=junos
In a rare situation, BMP might falls into a loop processing rib-in RM update messages but none of message being sent out. It can hog CPU for long time until the BMP station state is bounced. Since BMP task has low priority, it will yield CPU if there are other tasks jump in. So BMP will only hog CPU when system is idle and won't block other important tasks.
PR Number
Synopsis
Category: Track PRs in BGP Flow Spec area & is part of BGP inside RPD.
1740257
The inetflow6 routes are not installed on firewall filter table using BGP FlowSpec
Product-Group=junos
On all Junos and Junos OS Evolved platforms configured with BGP FlowSpec, ipv6 routes are installed in flow route table but not in firewall filter table. FlowSpec routes are blocked and dropped leading to traffic disruption. This is especially seen when BGP UPDATE Message does not include "Filter: Packet Length filter" within "FLOW_SPEC_NLRI" from BGP flowspec server thereby inetflow6 routes do not have "Action(s)"
PR Number
Synopsis
Category: BBE Remote Access Server
1740912
Subscribers sessions are logged out after performing GRES
Product-Group=junos
On MX platforms with subscriber management scenario, subscribers sessions are logged out in the backup Routing Engine (RE) after performing Graceful Routing Engine Switchover (GRES) .
PR Number
Synopsis
Category: PFE COS features on BT based platforms
1797592
More than 8 forwarding-classes cannot be configured with CBF
Product-Group=junos
On PTX10001-36MR, error will be displayed when we commit more than 8 forwarding-classes (FCs) which are configured with Class Based Forwarding (CBF) even though the product supports upto 16 forwarding-classes configured with CBF.
PR Number
Synopsis
Category: MX304 Chassis specific platform
1731237
MX304 Major Alarm " Host 0 detected AER correctable error" after RE switchover.
Product-Group=junos
MX304 Major Alarm " Host 0 detected AER correctable error" after RE switchover.
1799431
JDI-REGRESSION:MX304: cty core seen during usb upgrade from 23.1R1.8 to 23.2R2.18
Product-Group=junos
cty is a log collecter daemon process Which might get crashed during bootup It does not make any impact on the performance as its an independent process to collect logs only
PR Number
Synopsis
Category: PTX Chassis Manager
1776993
Over temperature on the linecards can cause chassis shutdown on PTX platforms
Product-Group=junosvae
On PTX10K8 and PTX10K16 Junos platforms, the temperature sensors generates alarms reporting over-temp condition when the temperature crossed the over-temp threshold value defined for that FRU ( Field-replaceable units ). This can cause the whole chassis to shutdown if the over-temp condition on the FRU stays for more than 240 sec and lead to a system wide outage.
PR Number
Synopsis
Category: Class of Service
1795898
COS output-traffic-control-profile is not getting attached to ps transport IFLs on a specific MX platforms that support HCOS
Product-Group=junos
COS output-traffic-control-profile does not get attached to ps (pseudowire service) transport IFLs when ps interfaces are configured over lt/rlt (logical tunnel/redundant logical tunnel) and both - ps transport IFL and ps service IFLs have COS output-traffic-control-profile configured, TCPs have different SMAPs (scheduler-maps) configured and these COS configuration on both these types of IFLs are committed in a single commit. This can impact COS scheduling on ps transport IFL.
PR Number
Synopsis
Category: QFX Access Control related
1794778
Dot1x process crash will be seen in the system with "server-timeout" & "server-fail use-cache" configuration
Product-Group=junos
On all Junos platforms having 802.1x with "server-timeout" & "server-fail use-cache" configuration, 802.1x process crash will be seen. In initial authentication client receives multiple egress-VLANs from radius server and during re-authentication if radius server is unreachable, then clients gets authenticated in server-fail use-cache scenario and the egress VLAN list is deleted. When 802.1x process attempts to access the same egress VLAN list which is deleted then the 802.1x process crash is seen and clients will face traffic drop.
PR Number
Synopsis
Category: QFX Control Plane VXLAN
1777635
Traffic loss for few seconds will be observed after restarting l2-learning process on L3 VxLAN gateway
Product-Group=junos
On all Junos and Junos Evolved platforms, in the EVPN-VXLAN( Ethernet Virtual Private Network- Virtual Extensible Local Area Network) scenario, traffic loss for few seconds would be observed when a user restart l2-learning process on a Layer-3 VXLAN gateway. This happens because of timing issues in the kernel, which mistakenly delete MAC routes of its associated devices instead of updating them in the table. The traffic from devices with those MAC addresses won't flow until the system is back on track and syncing properly.
PR Number
Synopsis
Category: Platform PR for 1G/10G LC
1758764
The remote end of the link goes down on JNP10K-LC480 Line Card after ISSU
Product-Group=junos
On MX10008 and MX10016 platforms with JNP10K-LC480 Line Card installed, the remote end of the Ethernet link of the JNP10K-LC480 Line Card goes down when an ISSU (Unified In-Service Software Upgrade) is performed from Junos OS 22.2R3 (or earlier) to Junos OS 22.3R1 (or higher). This causes traffic disruption.
PR Number
Synopsis
Category: CoS support on DNX
1770491
Traffic convergence is longer than usual after the CoS rewrite
Product-Group=junos
On ACX5448 and ACX710 platforms, traffic convergence takes more time than the expected 50ms i.e. traffic loss is more than expected observed for CoS (Class-of-service) rewrite change after a link failover in the MPLS (Multiprotocol Label Switching) scenario with FRR (Fast Reroute) and LSP (Label-Switched Path) link-protection configured.
PR Number
Synopsis
Category: JUNOS Dynamic Profile Configuration Infrastructure
1797305
The KRT queue stuck resulting in subscriber traffic loss
Product-Group=junos
On Junos MX platforms with subscriber dynamic profile versioning, following a commit configuration command, the krt ( Kernel routing table) queue becomes stuck on the master Routing Engine (RE), causing loss of subscriber traffic and subsequent client restarts. This occurs due to a large number of queued entries, resulting in blockage of the KRT queue.
PR Number
Synopsis
Category: JDHCP daemon for EVO platform to handle DHCP protocol
1775275
EVO(EVPN Fabric): DHCP packets are getting relayed even after deleting the dhcp relay configuration from the leaf
Product-Group=junos
TBA
PR Number
Synopsis
Category: EVO MACSEC Platform Independent Implementation
1762141
The dot1xd process crash will be observed due to an assert condition
Product-Group=junos
On the Junos OS Evolved platforms configured with MACsec (Media Access Control Security ) bounded-delay, the incorrect MACsec bounded delay stats timer ref count will result in an assert condition leading to the dot1xd process crash. The dot1xd process crash will flap the MACsec sessions.
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1783888
[Junos OS Evolved] Traceoptions log sometimes shows UTC timestamp, although non UTC time-zone is configured
Product-Group=junos
On all Junos OS Evolved platforms, traceoptions log sometimes shows UTC timestamp, although non UTC time-zone is configured.
PR Number
Synopsis
Category: EVPN control plane issues
1792566
Traffic drop in between EVPN hosts might be seen when "vlan-id none" is configured and any commit changes done under "protocols mpls"
Product-Group=junos
On all Junos Evolved ACX and PTX platforms, Traffic drop in between EVPN hosts might be seen when "vlan-id none" is configured and any commit changes done under "protocols mpls". The intermittent drops are due to MAC label refresh post commit change.
PR Number
Synopsis
Category: EX4100 RE, Platform Infra, Drivers
1775479
Peer device ports connected to Gigabit Physical ports of EX4100 transition to up state momentarily during reboot of EX4100
Product-Group=junos
When Junos EX4100 undergoes reboot or power cycle, peer device ports connected to GPHY (Gigabit Physical) ports of EX4100 transition to up state momentarily and can impact traffic on the peer device.
1797727
Intermittent alarms related to fan overspeed value can be observed on EX4100 platform
Product-Group=junos
On Junos EX4100 platform, intermittent alarms can occur regarding fan overspeed on the FPCs if they exceed the predefined fan speed threshold. These alarms are regularly activated and deactivated whenever the fan speed crosses the threshold and subsequently falls back below it. There is no service impact due to this.
PR Number
Synopsis
Category: EX4400 PFE software
1790316
The access port is dropping a VLAN-tagged packet of which the interface is a VLAN-member
Product-Group=junos
On all Junos EX and QFX5K platforms supporting Virtual Extensible LAN protocol (VXLAN), the access ports drop Virtual Local Area Network (VLAN) tagged traffic of the same VLAN for which the interface is configured. Though ideally, the access port should be accepting only untagged traffic, because of customer requests the access ports were made to accept tagged packets of which the interface is a VLAN member along with untagged traffic.
1791053
Warning message 'Too many VLAN-IDs on untagged interface' is seen when more than 1025 vlans on the same LAG interface are configured
Product-Group=junos
On EX platforms, when more than 1025 vlans on the same LAG interface are configured, a warning message 'Too many VLAN-IDs on untagged interface' at commit operation will be seen.
1795545
On all Junos EX platforms rewrite rules does not work properly when multiple interfaces are configured
Product-Group=junos
On all EX Junos platforms enabled with CoS, if there is rewrite-rule applied to the multiple interfaces, the rewrite-rule which is present for only one of the logical interfaces might work as expected due to this issue.
1795807
Cos rewrite rules does not work properly when input/output-vlan-map swap are configured
Product-Group=junos
On Junos EX4400 platforms enabled with CoS rewrite, if there is rewrite-rule applied to the input/output-vlan-map swap interface, the rewrite-rule of the logical interfaces does not work properly since the priority value for the queue is not updating. There is no traffic impact due to this, only CoS rewrite value is not updating.
PR Number
Synopsis
Category: EX4400 platform
1758042
EX-hardening: EX4400: set chassis config-button no-clear is not working
Product-Group=junos
EX-hardening: EX4400: set chassis config-button no-clear is not working
PR Number
Synopsis
Category: PFE EVPN / VxLAN related issues on EX platforms
1788573
Traffic loss after PIC restart if the packet has a VLAN tag of 4095
Product-Group=junos
On EX4400, EX4100, EX4650, and QFX5120 platforms in the EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) IPv6 (Internet Protocol Version 6) underlay environment, after the PIC (Physical Interface Card) restart few AE (Aggregated Ethernet) member interfaces go down and comes back up traffic loss is observed if the packet has a VLAN tag of 4095. The issue happens because PFE (Packet Forwarding Engine) will not receive any new next-hop addition to PFE as the AE interface is already present in PFE as next-hop.
PR Number
Synopsis
Category: Express PFE CoS Features
1789302
Traffic loss observed with line rate jumbo frames
Product-Group=junos
On Junos QFX10K platforms, during throughput/latency test, 30% traffic loss is observed when loading a line rate traffic with jumbo frames.
PR Number
Synopsis
Category: Express PFE including evpn, vxlan
1779890
On QFX10002-60c platforms, during system reboot and fpc reboot time, some non functional error logs are displayed.
Product-Group=junos
On QFX10002-60c express based Junos platform the error logs are seen during boot time. These errors are not impacting any functionality. The table is getting programmed correctly. These are seen during system reboot and fpc reboot time. We will be emitting the logs for non default routing instances and not for default routing instance.
PR Number
Synopsis
Category: Express PFE L2 fwding Features
1772126
Firewall filters will not work if IRB interface and layer 2 filter attached to BD is configured in SP style on QFX10K platforms
Product-Group=junos
On Junos based QFX10002/10008/10016 platforms running 22.3R1 and higher releases with policers configured in firewall filter and Interface Routing and Bridging (IRB) interface and Layer 2 filters attached to Broadcast Domain (BD) has Service Provider (SP) style Interface logical (IFL) configuration, firewall filter fails to filter traffic.
1779527
At the interface level, only half of the traffic is policed when applying a policer
Product-Group=junos
On QFX10002-36q, QFX10002-72Q, QFX10008 and QFX10016 platforms, when applying a policer at the interface level only half of the traffic is policed.
PR Number
Synopsis
Category: Port Mirroring feature on express PFE
1508627
Serviceability:Good to have CLI validation for remote port mirroring with TOS/DSCP setting
Product-Group=junos
Show forwarding-options port-mirroring shows correct NH ip and destination (NULL) to NA in qfx10K remote port-mirroring
PR Number
Synopsis
Category: SRX4100/SRX4200 platform software
1739559
SRX4100/4200 accepts the datapath-debug configuration although it does not support it
Product-Group=junos
It is possible to set and commit the datapath-debug configuration on platforms SRX4100/SRX4200 although datapath debugging is not supported on those platforms. because of this unsupported configuration being accepted the RE (Routing Engine) load can go high and cause traffic outage. The workaround is to remove the datapath-debug configuration and perform a commit.
1761668
False SNMP traps for power supply unit failure generated on SRX4100 and SRX4200 platforms
Product-Group=junosvae
On SRX4100/SRX4200 platforms, false SNMP traps for power supply unit failure generated as instability with the transmission in the hardware.
PR Number
Synopsis
Category: IDP policy
1786822
The flowd process crash is observed when the device is rebooted
Product-Group=junos
On all Junos SRX platforms, flowd crash is seen when the device is rebooted and a CLI request for Intrusion Detection and Prevention (IDP) counters reaches the Packet Forwarding Engine (PFE) before the IDP memory module is initialized (even if IDP is not configured). The flowd process restarts affecting the traffic.
PR Number
Synopsis
Category: Interface Information Display
1786555
The ifinfo process crash is seen on Junos platforms
Product-Group=junos
On all Junos platforms, the ifinfo process crash will be seen post executing `show interface extensive`.
PR Number
Synopsis
Category: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1787707
The KRT queue will be stuck on Junos ACX710 platform
Product-Group=junos
On Junos ACX710 platform with BGP (Border Gateway Protocol) configuration, the response message will be lost and it will lead to element being stuck in the KRT (Kernel Routing Table) queue.
PR Number
Synopsis
Category: ISIS routing protocol
1781138
The rpd process keeps on restarting on all Junos and Junos OS Evolved platforms due to memory exhaustion
Product-Group=junos
On all Junos and Junos OS Evolved platforms with Topology-Independent Loop-Free Alternate (TILFA) enabled and in a grid topology interconnect involving several nodes and links (more specifically this is seen with a 30x30 grid topology), the routing protocol daemon (rpd) process keeps on restarting due to high memory exhaustion.
1782887
Traffic blackhole due to Flex-algo not removing stale entries from ISIS database
Product-Group=junos
On all Junos and Junos Evolved platforms, in an ISIS scenario using Flex-algo , the system does not remove the stale (outdated) entries from the ISIS database causes traffic blackholing. This issue could lead to some traffic loss, as the routing information stored in the ISIS database does not get properly updated.
PR Number
Synopsis
Category: jdhcpd daemon
1763331
DHCP-OFFER gets dropped leading to subscribers not completing the DORA process in the ALQ EVPN-VPWS without the topology-discover scenario
Product-Group=junos
On MX platforms in the DHCP4 (Dynamic Host Configuration Protocol) and DHCPv6 subscribers in ALQ (Active Leasequery) EVPN-VPWS (Ethernet VPN - Virtual Private Wire Service) without topology-discover scenario, due to incorrect GIADDR (Gateway IP address) DHCP-OFFER gets dropped leading to subscribers not completing the DORA (Discover, Offer, Request, Acknowledge) process. The issue seen for static PS (Pseudowire Service) VLAN interfaces where DHCP subscribers are landing.
1763336
The backup BNG device has an incorrect IPv6 neighbor link-layer address when OLT is using a virtual MAC-address
Product-Group=junos
On MX platforms in the ALQ (Active Leasequery) EVPN-VPWS (Ethernet VPN - Virtual Private Wire Service) without topology-discover scenario, traffic impact will be observed for subscribers due to DHCPv6 binding with the incorrect MAC-address at the time of fail-over from Master BNG (Broadband Network Gateway) to Backup BNG device. This issue results in the backup BNG device having an incorrect IPv6 (Internet Protocol Version 6) neighbor link-layer address when OLT (Optical Line Termination) is using a virtual MAC-address. The issue happens when an OLT device with virtual MAC is configured in the transit path to DHCPv6 (Dynamic Host Configuration Protocol version 6) Relay/Server ALQ Master.
1775108
DHCP ALQ subscribers may not logged out after TCP connection is removed on all Junos platforms
Product-Group=junos
On all Junos platforms with ALQ (Active-Lease Query) enabled with DHCP(Dynamic Host Configuration Protocol ) relay agent configuration, with inflight subscribers login & logout and TCP connection reset, the DHCP subscribers may not properly release their IP address leases from a backup DHCP Relay, leading to inaccurate IP address management and allocation for the subscribers. This can lead to traffic impact for subscribers who are not released.
PR Number
Synopsis
Category: Flow Module
1755181
Traffic loss is observed for the existing session if there is an update for the next-hop MAC address
Product-Group=junos
On SRX5000 series and SRX4600, for flow sessions that are using Express Path (a.k.a. Service Offload), the next-hop MAC address is not updated for existing sessions, when the Address Resolution Protocol (ARP) table entry for the next-hop IP address changes, as a result, traffic is stalled for those existing sessions. This may for example occur on Virtual Router Redundancy Protocol (VRRP) failovers of directly connected routers if they do not use a virtual MAC address or server load balancers failing over the VIP to a new device with a different MAC address. Note that from Junos 21.2 onwards, Express Path is enabled by default.
1756972
CPU utilization calculation is inaccurate on vSRX platform
Product-Group=junos
On vSRX platform, when PowerMode IPsec (PMI) is enabled, the CPU displays less utilization compared to the actual utilization value.
1762568
Unable to download a file completely from SaaS server to LAN
Product-Group=junos
TCP sessions are not refreshed when enabled the "set security flow gre-perf-acceleration" is configured.
1776480
The nsd process goes high on primary device when the Tenant System is configured
Product-Group=junos
On SRX 1500, SRX4K , SRX5K series platforms and vSRX, the nsd process will remain high on primary device after the reboot of the device or power outage or RG0 failover (in chassis cluster scenario) if Tenant Systems are configured. This can lead to traffic loss and outages in the network.
1777565
Packet drops will be observed in GRE scenarios on SRX and vSRX platforms
Product-Group=junos
On SRX and vSRX platforms, when Generic Routing Encapsulation (GRE) tunnels are configured, packet drops will be observed when packets enter to a tunnel.
1779260
ISSU upgrade to 21.4+ on SRX5k or SRX4600 may lead to a flowd coredump
Product-Group=junos
On SRX5000 series and SRX4600, performing ISSU (In-Service Software Upgrade) to Junos version 21.4 and higher from earlier Junos versions can lead to a flowd coredump occurring during the ISSU process. The coredump would occur on the already upgraded node while the sessions are getting synchronized from the node which is not upgraded yet.
1783101
The srxpfe process crash when SkyATP turned on
Product-Group=junos
On all SRX series devices, when SkyATP feature is used, the srxpfe process may unexpectedly crash causing the device to reboot automatically
1783595
PMI sends packets to the wrong destination
Product-Group=junos
On SRX platform, when the next-hop changes, the PowerMode Ipsec (PMI) induces the packets to be sent to the wrong destination, causing packet drops.
PR Number
Synopsis
Category: l2 flow module
1780182
SRX with transparent mode may fail to create a new flow session for multicast traffic when vlan has l3-interface
Product-Group=junos
On all SRX platforms, when transparent mode is used, flow session does not create for the first few multicast packets due to which traffic drop occurs when l3-interface is used. The issue only happen in flow session creation process for Multicast traffic and the unicast traffic is unaffected. Once the flow session is created, multicast traffic will not be dropped.
PR Number
Synopsis
Category: Firewall Policy
1783249
Security policies may go out of sync during ISSU
Product-Group=junos
On all SRX platforms, performing ISSU (In-Service Software Upgrade) to or from an affected release can lead to policies going out of sync between control plane and forwarding plane. Affected releases are 19.4R3-S13, 20.4R3-S8/9/10, 21.2R3-S6/7; 21.4R3-S5/6; 22.2R3-S2; 22.4R3; 22.4R3-S1; 23.4R1. To recover, use the CLI command "request security policies resync".
PR Number
Synopsis
Category: IPSEC/IKE VPN
1759738
ADVPN connection-limit shortcut limitation not working as expected
Product-Group=junos
On all SRX series platforms, the number of shortcut VPN tunnels exceeds the connection-limit configured for an ADVPN partner in the IKE gateway configuration
1777531
In the MNHA scenario traffic drops are observed after failover
Product-Group=junos
On all SRX platforms, traffic drops will be observed when failover happens and if the traffic matches an old tunnel-id traffic selector in the Multi-Node High Availability (MNHA) scenario. The issue happens when peers-synchronize is not configured and a new Internet Protocol Security (IPsec) tunnel configuration is done on the active node first and later on the backup node, there will be duplicate traffic-selector entries on the backup node.
1780468
The ikemd process crashes when IKE traceoptions is configured
Product-Group=junos
On all SRX platforms and MX platforms with SPC3 card, which run ikemd (Internet Key Exchange Protocol Management daemon) process either by default or by installing junos-ike package, ikemd process crashes when user tries to configure the IKE traceoptions. However, the services automatically restore themselves following the crash.
1783738
The kmd/iked process crashes under rare circumstances
Product-Group=junos
On Junos SRX/MX platforms, VPNs (Virtual Private Network) that employ the use of KMD (ipsec-key-management) or IKED (ike-key-management) may inadvertently crash while generating the random number used by IPSec services which can cause the device to become very busy.
1784752
High RE CPU observed on both nodes in chassis cluster due to jsrpd
Product-Group=junosvae
High RE (Routing Engine) CPU caused is caused by jsrpd (Junos stateful redundancy protocol daemon) on both the nodes in a chassis cluster configured with control link Encryption (Internal SA) after upgrading the cluster.
1793207
Tunnel IKE and IPSec fails to come up on Junos SRX platforms with L2HA and FIPS after switchover
Product-Group=junos
On Junos SRX5K platforms in cluster with Layer2 High Availability (L2HA) and Federal Information Processing Standards (FIPS) enabled together won't go through a successful switchover. The backup node will not be able to move to active mode successfully leading to service impact.
PR Number
Synopsis
Category: Security platform jweb support
1788364
J-Web default session limits has been aligned with CLI default values
Product-Group=junos
If session limit not configured in cli, default value of session limit will be 7 for Seige models and 1024 for other models
1789466
Jweb does not display address book entries properly after certain operations.
Product-Group=junos
On SRX platform, Jweb does not display address book entries properly after certain operations.
PR Number
Synopsis
Category: Layer 2 Circuit issues
1699493
The AE interface will be down when l2circuit-control-passthrough is configured
Product-Group=junos
On Junos PTX platforms configured with "l2circuit-control-passthrough", if the IFL between Customer Edge (CE) and Provider Edge (PE) device is encapsulated with vlan-ccc, then the layer 2 control protocols like LACP and LLDP will be impacted and Aggregate Ethernet (AE) Interface will be down leading to traffic loss.
PR Number
Synopsis
Category: Layer 2 Control Module
1770053
xSTP configured interface will remains in discarding state
Product-Group=junos
On all Junos and Junos OS Evolved Platforms, when an interface is added inside RSTP (Rapid Spanning Tree Protocol), VSTP (VLAN Spanning Tree Protocol), MSTP (Multiple Spanning Tree Protocol) or STP (Spanning Tree Protocol), because of STP port creation fail from l2cpd (Layer 2 control protocol daemon), port will remains in discarding state. This leads to traffic impact.
1787892
Interface configured with BPDU-disable goes down during VC mastership switchover
Product-Group=junos
On Junos EX3400/EX4300/EX2300 platforms configured with VC (Virtual Chassis) and NSB (Nonstop-Bridging) enabled, when VC mastership switchover is triggered, the configuration under 'set protocols layer2-control bpdu-block interface ' will not take effect due to which the interface will go down and will impact the traffic. The configuration 'set protocols layer2-control bpdu-block interface all' will not have any impact.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1772424
Connectivity between static and LDP signaled pseudowires broken in VPLS after upgrade and results in VPLS traffic drop
Product-Group=junos
On all Junos and Junos OS Evovled platforms, when there is a upgrade and also when one mesh group of routing instance is substring of other, the connection between static and LDP (Label Distribution Protocol) signaled psuedowires is broken will lead to traffic drop.
1776782
Host device cannot resolve target IP's ARP when client uses virtual mac address
Product-Group=junos
On Junos or Junos OS Evolved platforms which supports EVPN-MPLS/EVPN-VXLAN, device will not reply for ARP (Address Resolution Protocol) requests when source MAC (Media Access Control) of ethernet header and ARP source MAC are different and ARP target address are exists in mac-ip-table. Traffic drop will be seen.
1776913
ARP resolution fails when EVPN configured with preserve-nexthop-hierarchy
Product-Group=junos
On all Junos and Junos Evolved MX platforms, it is observed that when EVPN-MPLS and Preserve-nexthop-hierarchy are configured, then ARP (Address-resolution Protocol) resolution fails and impacts the MPLS (Multi Protocol Label System) header packets that are sent to the MPLS core.
1790064
The l2ald process will crash, with rapid configuration changes followed by rpd and l2ald restart process
Product-Group=junos
On all Junos and Junos OS Evolved platforms with EVPN -VXLAN and high scaling configuration, rapid configuration changes followed by restart of rpd and l2ald will result in l2ald process crash and traffic drop will be observed.
PR Number
Synopsis
Category: lacp protocol
1783793
All AEs bundles configured in Active-Standby mode for EVPN-MPLS routing-instances will flap on the first commit post a fresh system reboot
Product-Group=junos
On all Junos MX and EX platforms with MPC family of line cards, all the Aggregated-Ethernet (AEs) bundles configured in Active-Standby mode for Ethernet Virtual Private Network-Multiprotocol Label Switching (EVPN-MPLS) routing-instances on the system will flap on the first commit after a fresh system reboot.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1721757
Uncleared alarm observed when any capacity license is used and installed multiple times
Product-Group=junos
On Junos EX and MX platforms, when any capacity license is used and installed multiple times, causes uncleared alarm.
PR Number
Synopsis
Category: PTX1000 platform
1770739
Reboot on PTX1k with image 22.3x60 causes fpc to reboot with "Fatal ASIC initialization error, Offlining FPC" Error message
Product-Group=junosvae
Reboot on PTX1k with image 22.3x60 causes fpc to reboot with "Fatal ASIC initialization error, Offlining FPC" Error message times
PR Number
Synopsis
Category: Port-based link layer security services and protocols that a
1792507
With any config change or interface up/down with MACsec protocol configured with or without Dot1x, dot1xd process core is observed in the device
Product-Group=junos
On all Junos and Junos Evolved platforms, dot1xd process core is observed because in MACsec (MAC Security) code where memory associated with an interface is prematurely freed while a timer(stats timer) linked to that interface is still running. This would lead to a use-after-free scenario, causing instability or crashes in the dot1xd process.
PR Number
Synopsis
Category: SW PRs for MPC10E Chassisd
1775368
An error will be observed while configuring HCOS resulting in COS not being applied to subscribers leading to traffic shaping not working
Product-Group=junos
On MX platforms with MPC10E, MPC11E, LC9600, and MX304-LMIC16 in the Subscriber-Management scenario, COS (Class-of-Service) will not be applied to subscribers leading to traffic shaping not working i.e. may result in slowness and packet drops due to the saturation of the link. The issue happens when configuring "set chassis fpc 3 pic 2 tunnel-services bandwidth 250g" and "hierarchical-scheduler" on the LT (Logical Trunnel) interface in separate commits.
PR Number
Synopsis
Category: For multicast snooping on MX
1710565
In a scaled setup mcsnoopd is taking high CPU causing traffic drop
Product-Group=junos
On all Junos and Junos Evolved platforms, whenever a commit is done, that involves mcsnoopd daemon config parsing such as (VLAN creation/deletion, interface add/delete to VLAN, interface enable/disable, IGMP (Internet Group Management Protocol) snooping/MLD (Multicast Listener Discovery) snooping related config commands) mcsnoopd will consume CPU. In less scaled setup (few IGMP snooping enabled VLANs and few hundred IGMP snooping memberships), the CPU time taken is less. In a more scaled setup (many IGMP snooping-enabled VLANs and a few thousand IGMP snooping memberships), the CPU may reach >90%. Since mcsnoopd is taking high CPU, it may affect other daemons like rpd. It may affect all the protocols if the CPU is not available to the protocols/daemons. This can impact route entries expiring and cause traffic drop.
PR Number
Synopsis
Category: MX Timing software
1750885
MPC10E: Support of G.8275.1 PTP Hybrid mode with speed 25G and 400G
Product-Group=junos
In 21.2R3S6 release, MPC10E line-card does not support of G.8275.1 PTP Hybrid mode with speed 25G and 400G
1781161
After a GRES the MX external clock is stuck in a Holdover State
Product-Group=junos
After a GRES the MX external clock is stuck in a Holdover State
PR Number
Synopsis
Category: Odin Timing software
1745604
[TWM Clocking Solution] - chassis clock status should not move to "holdover" while switching between PTP path alone
Product-Group=junos
[TWM Clocking Solution] - chassis clock status should not move to "holdover" while switching between PTP path alone
PR Number
Synopsis
Category: FreeBSD Kernel Infrastructure
1691036
NTP time drift
Product-Group=junos
NTP time drift on the affected Junos releases. Earlier implementation of kvmclock with vDSO (virtual Dynamic Shared Object) which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate.
PR Number
Synopsis
Category: Kernel Tunnel Interface Infrastructure
1753191
ARP resolution failure for lt interfaces is observed after cluster failover on Junos SRX platforms
Product-Group=junos
On Junos SRX platforms in cluster, Address Resolution Protocol (ARP) resolution fails for logical tunnel interfaces when the logical tunnel interfaces are toggled and the cluster switchovers.
PR Number
Synopsis
Category: OSPF routing protocol
1774715
OSPF route flap might be observed
Product-Group=junos
On all Junos and Junos OS Evolved platforms OSPF (Open Shortest Path First) route flaps can be observed which will cause a traffic drop. This is a rare timing issue happening after an OSPF adjacency flap.
PR Number
Synopsis
Category: Express Paradise PFE Sflow
1729316
Sflow sampling will not work on Junos based QFX10K platforms
Product-Group=junos
On all Junos based QFX10K platforms with ingress Sflow enabled on bridged Aggregated Ethernet (AE)/ L3 trunk(tagged) interfaces, packet coming on an IRB interface with its destination on Equal Cost Multi-path (ECMP) will lead to dropping of sampled data and Sflow records will not be generated.
PR Number
Synopsis
Category: Protocol Independant Multicast
1792886
The rpd crash is observed when PIM SSM mode with RPF-Vector and MoFRR is configured
Product-Group=junos
On Junos and Junos Evolved platforms , when PIM SSM (PIM Source-Specific Multicast) with RPF (Reverse Path Forwarding)-Vector and MoFRR (Multicast-only fast reroute) is configured , rpd crash if the device receives PIM Prune message for (S, G) state with RPF vector TLV. interface is freed for the (S, G) from the outgoing interface list i.e. RPF-Vector TLV (Type, Length, and Value) having (S, G) is getting freed but that same (S, G) is still used by MoFRR. The issue happens when MoFRR Backup upstream interface is also listed at the outgoing interface list for the (S, G)
PR Number
Synopsis
Category: vMX Platform Infrastructure related issue tracking
1729152
The FPC crash or flap in protocols will be seen as soon as port-mirroring or firewall filters with syslog action is enabled
Product-Group=junos
On MX150 platform, when port-mirroring or firewall with syslog configuration is enabled, there will be a memory leak which will cause depletion of buffer memory which will lead to flap in the protocols or the (Flexible PIC Concentrators) FPC crash. This will impact the traffic.
PR Number
Synopsis
Category: QFX access control list
1754929
[QFX5120]Egress filter does not work properly on vlan pop configuration
Product-Group=junos
On QFX5120 platform if it sets egress filter on vlan pop configuration, filter does not work properly
PR Number
Synopsis
Category: for all ipv6 related issues
1775394
EX/QFX: fails to ping ipv6 link local address in routing instance if there is a default route in the same instance.
Product-Group=junos
On QFX5K, EX4300-MP, EX4400 or EX4100 series switch with VXLAN, ping to ipv6 link local address in routing instance would be failed. This issue affects only to the traffic which is sent to Link Local IPV6 Interfaces when the interface is an IRB along with VXLAN configuration.
PR Number
Synopsis
Category: QFX L2 PFE
1739048
Q-in-Q for access port to access port through VxLAN bridge-domain does not work on all Junos QFX5K platforms
Product-Group=junos
Q-in-Q for access port to access port is not working on all Junos QFX5K platforms when it is configured with VxLAN local switching (bridge-domain). The traffic is working in only one direction and the packet is getting dropped in reverse direction because the packet is coming in as single tagged VLAN.
1781955
A few AE interfaces will drop traffic when a large number of AE interfaces are deleted and added back
Product-Group=junos
On EX4100, EX4100 Multigigabit, EX4100-F, EX4400, EX4400 Multigigabit, EX4650-48Y, QFX5120-48Y, QFX5120-32C, QFX5120-48T, QFX5110 and QFX5120-48YM platforms with Ethernet VPN-Virtual Extensible LAN (EVPN-VxLAN) configured, a few AE interfaces will drop traffic when a large number of Aggregated Ethernet (AE) interfaces are deleted and added back. When this issue happens AE interfaces will be UP but traffic would be dropped.
1797516
DCPFE process crash occurs in EVPN-VXLAN scenario
Product-Group=junos
When a vport, which is a memory pointer, is a member of an itable list, the entry in the itable should be removed before freeing the vport. For some corner case, the vport is not removed from the itable when freeing the vport. The freed memory or the reused memory corrupts the itable list and it crashes when performing some operation on the corrupted list.
PR Number
Synopsis
Category: QFX L3 data-plane/forwarding
1771630
Family ethernet-switching policer per-sub-unit interface breaks after dcpfe/device restarts
Product-Group=junos
On all Junos QFX and EX platforms, on dcpfe/device reboot, the firewall filters will not be processed affecting the filters applied on subunits of the LAG interfaces.
1782762
MTU Adjustment on Junos QFX5K platforms with GRE Causes FPC and Link Partner FPC Reboots
Product-Group=junos
On Junos QFX platforms with Generic Routing Encapsulation (GRE) tunnels enabled, when attempting to adjust the MTU (Maximum Transmission Unit) configuration of a physical interface, a reboot of the FPC is triggered which would leads to crash and impacts the traffic.
PR Number
Synopsis
Category: QFX analyzer, sflow
1777265
The fxpc process crash is seen on a specific Junos QFX and EX platforms except EX4300 due to memory leak after VTEP IFLs configuration and un-configuration
Product-Group=junos
VTEP (VXLAN Tunnel Endpoint) IFLs (Logical Interfaces) configuration and un-configuration causes a memory leaks and it leads to the fxpx process crash on a specific Junos QFX and EX platforms except EX4300.
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1773676
The tagged traffic drop will be seen with vlan-id-list and native-vlan-id configured on one IFL.
Product-Group=junos
On QFX5120, EX4650, and EX4400 platforms, when vlan-id-list and native-vlan-id are configured on one IFL, the packets will drop and will impact the tagged traffic.
1774366
The dcpfe process crash due to stale memory
Product-Group=junos
On Junos QFX platforms, stale memory references are causing dcpfe crashes triggering PFE (Packet Forwarding Engine) to restart resulting in traffic disruptions.
1775672
The untagged packets get dropped in transparent EVPN-VXLAN on the ingress PE-CE port of SP style on certain Junos EX/QFX platforms
Product-Group=junos
On Junos QFX5k/EX4650/4400/4100 platforms with SP (Service Provider)-style configuration and in the EVPN (Ethernet Virtual Private Network)-VXLAN (virtual Extensible Local Area Network) scenario at the ingress port of the CE (Customer Edge) host, untagged packets are getting dropped when native VLAN (Virtual Local Area Network) is configured. These packets should be flooded into the VLAN (Virtual Local Area Network) including intra-VLAN ports and remote VTEP (Virtual Tunnel Endpoint).
1778725
Traffic drop is observed when VIPs become unreachable due to GARP sent on VLANs to which the VIP does not belong
Product-Group=junos
Under a rare scenario, on all Junos and Junos Evolved platforms configured with EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible Local Area Network) type 5 routes, Bridge-Domain, IRB (Integrated Routing and Bridging) and having L4 (Layer 4 device like an application load balancer) devices as single-homed with each border leaf and when VIP (Virtual Internet Protocol) entries are learnt on a leaf and L4 failover happens, it is observed that the VIPs announced by GARP (Gratuitous Address Resolution Protocol) is sent on VLANs that the VIP does not belong to and the incorrect GARP is not handled as per the expectation.
1783397
The fxpc process crash and the device reboots after deleting Aggregated Ethernet (AE) Interface along with its associated physical interface and then applying new interface configuration on the associated physical interface in an EVPN-VXLAN scenario
Product-Group=junos
On an Ethernet Virtual Private Network (EVPN) / Virtual eXtensible Local-Area Network (VXLAN) scenario, after removing an Aggregated Ethernet (AE) Interface along with its associated physical interface on a QFX5k series device and then applying any configuration to the physical interface, the fxpc process crashes and the device undergoes an automatic reboot.
1796210
In the EVPN-VxLAN scenario traffic blackholes on spine reboot
Product-Group=junos
On all Junos QFX5K and some specific EX4K in EVPN-VxLAN (Ethernet VPN-Virtual extensible LAN) environment with underlay connections using Virtual Chassis Port Link Aggregation with AE (Aggregated Ethernet) interface and during one of the spine reboot, traffic will not be immediately switched to another spine and traffic blackholes.
1802958
ECMP programming issue on Junos QFX5K/EX4K in EVPN-VXLAN
Product-Group=junos
In rare scenarios on Junos QFX5K/EX4K platforms that are part of Ethernet VPN - Virtual extensible LANs (EVPN-VXLAN) Fabric topology and employing ECMP (Equal Cost Multi-path) routing on the underlay interfaces between the Leaf and Spine, if one or more of these physical underlay interfaces flaps or their associated underlay protocol adjacency flaps and this time aligns precisely with the associated unicast next-hop deletion process, a race condition may occur, resulting in the potential failure to program the associated ECMP interface next-hop entry correctly in the hardware table.
PR Number
Synopsis
Category: QFX5200/5110/5120/5210 Platfom issues
1779624
On the QFX5110-48S platform the virtual chassis port goes down when the VC is upgraded or the VC ports are deleted and added back
Product-Group=junos
One of the virtual chassis ports in a VC of QFX5110-48S goes down either by deleting or adding the port or by upgrading the virtual chassis thereby causing a loss of redundancy for the virtual chassis ports. The ways to recover are by re-creating the VC or by doing soft removal and insertion of the port (please contact JTAC for the same).
PR Number
Synopsis
Category: RPD Interfaces related issues
1709629
RPD CPU utilization is 100% when configured with virtual router-advertisement for AE interface
Product-Group=junos
On all Junos and Junos OS Evolved platforms rpd ( Routing protocol daemon) CPU utilisation reaches 100% when configured with virtual router-advertisement for AE interface due to which AE member link flaps.
1798801
MPLS/RSVP LSP self-ping behaviour differs from expected behaviour causing self-ping time out
Product-Group=junos
On Junos OS Platforms, configured with Multiprotocol Label Switching (MPLS)/Resource Reservation Protocol(RSVP) Label Switched Path(LSP) and firewall filter applied on the loopback with prefix list that does not include the interface address of local router, self-ping time out is observed.
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1785884
The rpd crash is observed due to segment fault
Product-Group=junos
On Junos OS Evolved platforms, when no acknowledgment is received from PFE (Packet Forwarding Engine) within timeout results in the rpd (Routing Process Daemon) crash. This issue happens when routes requesting acknowledgment do not receive acknowledgment leading to segment fault.
PR Number
Synopsis
Category: RPD policy options
1714163
The static routes are installed in the routing table even though interface routes are not present
Product-Group=junos
On all Junos and Junos OS Evolved platforms, the static routes are installed in the routing table even though the corresponding interface routes are not present.
PR Number
Synopsis
Category: Resource Reservation Protocol
1785214
RSVP incorrectly determines the outgoing interface resulting in the rpd crash
Product-Group=junos
On Junos platforms, the rpd (Routing Protocol Process Daemon) crash is observed when LSP (Label-Switched-Path) terminates on the incorrect outgoing interface. The issue happens because RSVP (Resource Reservation Protocol) incorrectly determines the outgoing interface that the ResvTear applies to.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1766097
PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
Product-Group=junos
PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
PR Number
Synopsis
Category: Issues related to control plane security
1781732
Junos OS and Junos OS Evolved: Impact of Terrapin SSH Attack (CVE-2023-48795)
Product-Group=junos
An Improper Validation of Integrity Check Value vulnerability in OpenSSH before 9.6 of Juniper Networks Junos OS and Junos OS Evolved allows a remote attacker to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka the Terrapin Attack. Please refer to https://supportportal.juniper.net/
JSA76462
[juniper.net]
for more information.
PR Number
Synopsis
Category: Remote Access VPN issues on SRX
1766594
After the device reboot JSC stops accepting user connections
Product-Group=junos
On all SRX platforms, when Juniper Secure Connect (JSC) configuration is done on Point-to-Point Protocol over Ethernet (PPPoE) interface then after the device reboot, JSC clients couldn't connect.
PR Number
Synopsis
Category: SRX branch platforms
1714620
High latency will be observed while pinging to peer device
Product-Group=junos
On Branch SRX Platforms, The delay will be observed while pinging to peer device due to high latency when VLAN(Virtual Local Area Network) tagged DHCP(Dynamic Host Configuration Protocol) packets arrive at IRB (Integrated Routing and Bridging) interface.
1770303
Inter and intra VLAN traffic drop can be seen on the SRX branch series
Product-Group=junos
On all Junos SRX branch series devices, intra and inter-VLAN (Virtual Local Area Network) traffic drop will be seen when the devices are running in ethernet-switching mode and STP(Spanning Tree Protocol) is configured on the respective interface for the VLANs.
1776400
The Wifi MPIM card will be down upon upgrading the device
Product-Group=junos
Upon upgrading the Junos SRX platform which is acting as a WAP (wireless access point) or WLAN (wireless LAN) installed with a Wi-Fi MPIM (Mini Physical Interface Module) card, the card is not working. This will tear down the Wi-Fi client sessions, impacting the services.
1776656
Interfaces stay down when 1G SFP fiber transceiver connected to SRX380 platform
Product-Group=junos
Ports are staying down on SRX380 platform with 1G SFP fiber transceiver while trying to connect to a device that doesn't support auto-negotiation and/or having hard-coded speed and duplex setting
1780326
IP Monitoring fail to install route after SRX cluster reboot
Product-Group=junos
On Junos SRX branch series platforms in cluster, the IP Monitoring fails to install route after the SRX cluster reboots.
PR Number
Synopsis
Category: SSL Proxy functionality on JUNOS
1788673
The flowd crash will be observed when the TLS 1.3 session ticket is received on SSL-I
Product-Group=junos
On SRX platforms with SSL (Secure Sockets Layer) Proxy configured, due to timing synchronization issues, while doing multiple session tickets check on SSL_I [initiator on the server side], and SSL_T [terminator on the client side] updating the session cache and releasing the session cache resources resulting in proxy session info cleared & causing the flowd crash at SSL_I. The issue happens when the SSL_I (Server) is using TLS1.3 and SSL_T (Client) using TLS1.2.
PR Number
Synopsis
Category: Stout card (MPC7) fabric issues
1768592
The SFB3 will go offline during during SFB3 < -> ADC < -> MPC7E link initialization
Product-Group=junos
On MX2020 and MX2010 platforms with Switch Fabric Boards (SFB) 3 and Modular Port Concentrators (MPCs) MPC7E-10G or MPC7E-MRATE inserted via Adapter Card (ADC) MX2000-LC, SFB3 will go offline during SFB3 < -> ADC < -> MPC7E link initialization with a fatal error. This is a timing issue and will not be seen with every SFB3 < -> ADC < -> MPC7E link initialization. It happens because of a race condition between certain events occurring during MPC initialization.
1769983
At MX2020 with SFB3 and MPC7+ADC in FPC slot 11, link errors in fabric planes 1, 4, 7, 10 will be seen upon MPC7/ADC restart in FPC slot 11
Product-Group=junos
On the Junos MX2020 with SFB3 and MPC7+ADC in FPC slot 11, link errors in fabric planes 1, 4, 7, and 10 will be seen upon MPC7/ADC restart in FPC slot 11. The link errors will come along with the 'failed word alignment' syslog message logged by hsl2_channel_train_hsl2_rx().
PR Number
Synopsis
Category: SRX-1RU infrastructure SW defects
1784983
Chassis alarm not present for if /var partition usage exceeds 100%
Product-Group=junos
When /var partition disk space is greater than 100%, "RE 0 /var partition usage is high" chassis alarm gets cleared
PR Number
Synopsis
Category: SRX-1RU platfom datapath SW defects
1775083
Traffic drop observed right after boot up on Junos SRX 4600 platforms
Product-Group=junosvae
On SRX 4600 platforms running the Field Programmable Gate Array (FPGA) firmware versions 163, 165, 171, 175 the Packet Forwarding Engine (PFE) may experience a 25% drop in performance after bootup.
PR Number
Synopsis
Category: Issues related to broadband edge apps (PPP, DHCP) on ZT/YT
1784914
The backup routing-engine mac address is not resolved on Junos MX platforms with subscriber management configuration
Product-Group=junos
On Junos MX platforms with MPC 3NG, MPC5, MPC7 line cards with subscriber management configuration, when upgrade is performed to Junos 18.4 release or higher, the backup routing-engine (REs) mac address does not get resolved during Flexible PIC Concentrators (FPCs) bootup when the backup RE and the FPC reboot at the same time.
PR Number
Synopsis
Category: ZT/YT pfe firewall software
1733724
Inline Services MAP-E is failing on MPC10 after configuration modification
Product-Group=junos
On MX platform with MPC10 line card, when there is a modification in configured inline-services under Mapping of Address and port Encapsulation (MAP-E) which results inline MAP-E feature will not work and it causes traffic loss.
1758935
The shared-bandwidth-policer may be loaded into irrelevant PFE depending on the choice of member port of aggregated Ethernet
Product-Group=junos
When one of member port of aggregated Ethernet (AE) is taken from PIC port 2 and 3, and when shared-bandwidth-policer is configured on the AE, shared-bandwidth-policer may be loaded to irelevant PFE which does not host AE member port.
1790331
Traffic drop will be seen when two firewalls actions are referring to same Routing Instance name
Product-Group=junos
On Junos MX platforms with MPC10E/11E line cards, when two firewalls are referring to the same routing instance, then the traffic black holing and translations failings are seen.
PR Number
Synopsis
Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1783821
L2VPN: On AFT-based cards, Using Core facing IRB, l2vpn datapath broken.
Product-Group=junos
L2VPN: Using Core facing IRB, l2vpn datapath broken. As part of this code changes PushLabels Feature is added to IRB NH egress feature list. All the AFT-based cards, are impacted by this.
PR Number
Synopsis
Category: ZT/YT pfe l3 forwarding issues
1776783
BGP session on MPLSoUDP tunnel will not be established
Product-Group=junos
On MX platforms with MPC1-MPC9/LC2103/LC2101/LC480 line cards and EX9200 platforms, Border Gateway Protocol (BGP) session on Multiprotocol Label Switching over User Datagram Protocol (MPLSoUDP) tunnel will not be established as the packet going to control plane doesn't carry IIF information.
PR Number
Synopsis
Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1773148
The demux0 interfaces won't show any data traffic (measured in packets per second) after the FPC restarts
Product-Group=junos
On MX platform, If the line card restarts while subscribers are still connected, there might be a delay in adding the AE (Aggregated Ethernet) member interface back online. This delay can cause inaccurate updates to the demux interface information, resulting in the demux0 interface showing zero data traffic (measured in pps) even though there might actually be traffic flowing.
PR Number
Synopsis
Category: Trio pfe stateless firewall software
1738672
FPC crashes due to back-to-back GRES
Product-Group=junos
On line cards such as MPC5E/MPC7E/LC480/MPC10E/11E/LC9600 and MX304 platforms, when multiple times Graceful Routing Engine Switchover (GRES) is performed, all the FPCs crashed.
PR Number
Synopsis
Category: Trio pfe bridging, learning, stp, oam, irb software
1766080
Traffic drop is observed with "preserve-nexthop-hierarchy" at global level on Junos MX/EX92k platforms with MPC10 and above line cards (including MPC10, MPC11, LC9600 line cards and EX9204, EX9208, EX9214, EX9251, EX9253, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, MX304 platforms)
Product-Group=junos
On Junos MX/EX92k platforms with MPC10 and above line cards (including MPC10, MPC11, LC9600 line cards and EX9204, EX9208, EX9214, EX9251, EX9253, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, MX304 platforms) having EVPN (Ethernet Virtual Private Network) and IRB (Integrated Routing and Bridging), configuring "preserve-nexthop-hierarchy" at global level causing traffic from core to drop on PE (Provider Edge) in CRB (Centrally-Routed Bridging) mode.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1718063
After deleting commit scripts with transient changes, the changes do not take effect
Product-Group=junos
On Junos OS Evolved ACX7100-32C / ACX7100-48L / ACX7509 / PTX10001-36MR / PTX10003 / PTX10004 / PTX10008 / PTX10016 platforms, when a commit script with transient configurations is deleted, daemon does not see the change after commit.
1799277
mgd core seen on MX960 during upgrade to aggregated satellite switches
Product-Group=junos
The satellite package is not conforming to the expected junos version format leading to the problem reported. The code which parses this version string has been modified to handle such format incompatibility gracefully.
PR Number
Synopsis
Category: PRs related to PICd and associated lib WAN side PI code.
1793763
IFDs are not created when back to back port configuration is committed without much delay
Product-Group=junos
On MX platforms with MPC11/LC9600 line cards and MX304 platforms, if on the same PIC of FPC, back to back port configuration is committed without much delay (< 10 secs) physical interfaces (IFD) will not be created as per the latest commit.
PR Number
Synopsis
Category: web filterig issues
1772232
[SRX] Flowd core is generated by UTM web-filtering
Product-Group=junos
On SRX platform, flowd core might be generated when when TCP flow session for HTTP traffic is in error state due to some reason and UTM WF trying to apply fallback action.
PR Number
Synopsis
Category: Junos Fusion Aggregation Device Infra
1787147
The sdp process crashes when trying to add a new satellite device to the network
Product-Group=junos
In the Junos Fusion setup, the sdp (Satellite Discovery and Provisioning Daemon) process crashes repeatedly when trying to add a new satellite device to the network. This issue happens when the MD5 encrypted data is read as a string, in which the string validation code throws errors when the first byte of MD5 encrypted data is 0.
PR Number
Synopsis
Category: MX10K linecard
1785182
On Junos MX and SRX platforms silent FPC reboot is observed with no generation of crash files
Product-Group=junos
On Junos MX platforms with Modular Port Concentrators (MPCs) 7/8/9 line cards, MX10008/MX10016 platforms using LC1201 or LC480 line cards, SRX5K platforms with Services Processing Card (SPC3) cards, due to memory issue causing hardware issue, the Flexible PIC Concentrators (FPC) reboots silently without generating any crash files.
PR Number
Synopsis
Category: For GPRS security features on highend SRX series
1736985
Cores are observed on both the nodes of SRX HA cluster setup when it's upgraded to 21.2 and above
Product-Group=junos
On Junos SRX high-end platforms configured with GTP (GPRS Tunneling Protocol), during the upgrade of an SRX High Availability (HA) cluster, a crash occurs on the nodes when processing GTP packet traffic. This persistent crashing prevents the system from restarting and impacts service availability.
PR Number
Synopsis
Category: Track Windriver Linux issues
1631579
A few line cards will be stuck in the 'Present' state and later go 'Offline'
Product-Group=junos
A system equipped with specific line cards, the line cards will be stuck in the 'Present' state and later go 'Offline' after the line card or router is rebooted. Ideally, the Line Card should go 'Online' instead it goes 'Offline'.
PR Number
Synopsis
Category: usf ipsec related issues
1781768
Pre-fragmentation IPsec traffic is getting dropped when PMI is enabled
Product-Group=junos
On all SRX and MX platforms with SPC3 and when PMI (power-mode-ipsec) is enabled, the fragmented traffic will be dropped when the configured MTU (Maximum transmission unit) of the tunnel is less than the size of the packet.
PR Number
Synopsis
Category: usf nat related issues
1776355
Internet traffic destined for the NAT pool address (Network Address Translation) will loop after configuration changes
Product-Group=junos
On Junos MX platforms, with MS-MPC and SPC3 service cards, Change in "interim-logging-interval" configuration can lead to UDP traffic get looped and it will impacting CPU utilisation and traffic drop can be seen.
22.4R3-S2 - List of Known issues
PR Number
Synopsis
1779410
The pfex process crash is observed when PIC is removed
Product-Group=junos
PR Number
Synopsis
1767706
EX2300 VC: Dot1x authentication flapping in multiple supplicant mode with 100 user scale
Product-Group=junos
PR Number
Synopsis
1580560
On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.
Product-Group=junos
PR Number
Synopsis
1640307
QFX5120-32C might reboot randomly with the last reboot reason:- "0x2000:hypervisor reboot"
Product-Group=junos
PR Number
Synopsis
1789694
ACX1100 PTP(enterprise profile) is stuck at freerun state
Product-Group=junos
PR Number
Synopsis
1758348
Traffic loss will be observed during the ungraceful removal of a switch fabric board
Product-Group=junos
PR Number
Synopsis
1734761
JUNOS_REG:BNG_CUPS:MX480:DHCP dual stack relay /PPPoE subscriber bring-up failed on BNG-CUPS
Product-Group=junos
PR Number
Synopsis
1769800
The traffic shaping rate gets impacted in a subscriber scenario on Junos MX BBE platforms
Product-Group=junos
PR Number
Synopsis
1754547
On a L3 interface default classifier is ipprec-compatibility, but after reboot another default classifier is taking effect - ieee8021p-default
Product-Group=junos
PR Number
Synopsis
1764966
After restart chassis-control syslog is error out " Err] ACX_ASIC_PROGRAMMING_ERROR: pfe_dnx_translation_set: Error, bcm_vlan_port_translation_set rv:Entry not found ".
Product-Group=junos
PR Number
Synopsis
1690598
VMX :: Incorrect data encoding format is used for the parameter ISIS extended reachability TLV - max link bandwidth when passed to Influx DB server via GNMI
Product-Group=junos
PR Number
Synopsis
1801072
JDI - PDT:ENT:CnB:Multi - Tier Campus:ENTCnB - AccessAggregation-XSTP : LACP flap seen in the lagavulin device with PDT PROFILE CONFIGS
Product-Group=junos
PR Number
Synopsis
1689990
Minor alarm "FPC Inefficient Port Mapping" won't be cleared
Product-Group=junos
PR Number
Synopsis
1751260
Directly connected neighbour via AE becomes unreachable if the member interfaces of AE are swapped and if one AE has VLAN and the other doesn't
Product-Group=junos
1762490
JDI-RCT-MPC10E: Ksyncd crash on backup RE after fpc reboot
Product-Group=junos
PR Number
Synopsis
1675919
NFX350 :: JDI_REGRESSION:PLATFORM:SWITCHING:JDM:: Core "localhost.libvirtMib_suba.15909.1656455866.core.tgz" is seen on NFX-350 boxes
Product-Group=junos
1769048
On NFX350, for SRIOV traffic, NFV Backplane can be disabled to get a higher throughput
Product-Group=junos
PR Number
Synopsis
1732210
23.1R2:ISSU:USERFW-CP: Clearpass Auth entry's are getting deleted post successful ISSU
Product-Group=junos
PR Number
Synopsis
1716776
Security log missing space between timestamp and hostname
Product-Group=junos
PR Number
Synopsis
1722057
Scaled IPsec gateway configuration not pushed to database
Product-Group=junos
1722689
IKED cores are generated in node1, while doing ISSU upgrade from any release before Junos 22.4R1 to Junos 22.4R1 or later.
Product-Group=junos
PR Number
Synopsis
1725519
LDP sync not complete with NSR ( stuck at Inprogress forever) when "protocols ldp strict-targeted-hellos" is enabled when LDP signalled VPLS is configured
Product-Group=junos
PR Number
Synopsis
1737035
BGP sessions flap due to license updates
Product-Group=junos
PR Number
Synopsis
1753374
MPC11E suddenly goes offline due to power failure causing multitude fabric stream drain failures on all other MPC11
Product-Group=junos
PR Number
Synopsis
1746230
ISSU feature doesn't work
Product-Group=junos
PR Number
Synopsis
1777865
Telefonica:Higher revert-time for MVPN Hot-root-standby
Product-Group=junos
PR Number
Synopsis
1740873
ARP resolution will not work properly if the L3 interfaces are configured with native vlan-id
Product-Group=junos
PR Number
Synopsis
1797453
QFX-10002-36q||SFP+-10G-CU3M SFP are not coming up post upgrade from 18.2X75-D12.6 to 20.4R3-S7.2
Product-Group=junos
PR Number
Synopsis
1703229
JDI_REG:: QFX5200:: After ISSU upgrade, device is hanged and not able to perform any operations until USB recovery done on device
Product-Group=junos
PR Number
Synopsis
1562387
The session status gets stuck in the Invalid state after the core-facing link fails in the primary PE devices.
Product-Group=junos
PR Number
Synopsis
1796119
SNMPv3 re-configuration procedure
Product-Group=junos
PR Number
Synopsis
1696234
JWEB: While creating source nat we are not able to select the source ingress
Product-Group=junos
PR Number
Synopsis
1750521
Packet drop will be observed if different Native-VLANs are configured on the SRX platform
Product-Group=junos
PR Number
Synopsis
1775083
Traffic drop observed right after boot up on Junos SRX 4600 platforms
Product-Group=junos
PR Number
Synopsis
1766694
802.1p priority is preserved when traffic is sent from AFT with irb
Product-Group=junos
PR Number
Synopsis
1683289
VPLS IRB traffic dropped as sw error in IRB enhanced-convergence + vt tunnel services combination
Product-Group=junos
PR Number
Synopsis
1729970
L2-Trans: pm_soam_frame_rx count is not incrementing as expected
Product-Group=junos
1775966
TEF: [CST] - NGMPC1 core in pfeman_watchdog -> process_periodic_list after dcd restart
Product-Group=junos
PR Number
Synopsis
1801136
TEF: [CST] - Config in primary and backup RE are out of sync when graceful-switchover is turned on and there is no commit sync failure
Product-Group=junos
Modification History
First publication 2024-05-16
22.4R3-S2: Software Release Notification for JUNOS Software