Alert Type
SRN - Software Release 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
Alert Description
Junos Software Service Release version 20.4R3-S8 is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 20.4R3-S8 is now available.
20.4R3-S8 - List of Fixed issues
PR Number
Synopsis
Category: EX4300 PFE
1722284
Native VLAN traffic is getting dropped in the Q-in-Q scenario on EX4300
Product-Group=junos
On Junos EX4300-24T/24P when the native CVLAN (Customer Virtual Local Area Network) ID is configured for Q-in-Q setup, the traffic for that particular VLAN gets dropped even if the knob "input-native-vlan-push" is configured. This issue is encountered when the when inner-tag matches 'native-vlan-id' irrespective of the outer tag.
1729636
Traffic loss is seen after configuration changes related to VSTP are committed
Product-Group=junos
On EX4300 platforms, when RSTP (Rapid Spanning Tree Protocol) and VSTP(VLAN Spanning Tree Protocol) are configured on two different interfaces which are part of the same VLAN (Virtual LAN), the RSTP-enabled interface will drop traffic after doing a configuration change in VSTP for the specified VLAN.
PR Number
Synopsis
Category: EX4300 Platform
1733339
On EX4300-VC, the PFE might crash if a QSFP is inserted or removed when the CPU is stressed
Product-Group=junos
On EX4300-VC, the Online Insertion and Removal (OIR) of Quad Small Form-factor Pluggable (QSFP) may result in a PFE crash under near-zero idle CPU conditions.
PR Number
Synopsis
Category: EX4300 Platform implementation
1712785
EX4300-48MP CPLD firmware fails to upgrade from 2.2 to 2.5 with 22.4R1.10 image
Product-Group=junosvae
EX4300-48MP CPLD firmware fails to upgrade from 2.2 to 2.5 with 22.4R1.10 image
PR Number
Synopsis
Category: SRX DNS DGA and tunneling related
1717503
The srxpfe core has been seen on secondary SRX during ISSU
Product-Group=junos
On all Junos SRX platforms, when in-service software upgrade (ISSU) is in progress and if any traffic received by DNSF plugin leads to the srxpfe core.
PR Number
Synopsis
Category: ACX L2 related features
1720141
Devices stop passing VPLS traffic following a link flap causing LSP switchover
Product-Group=junosvae
On ACX5048 and ACX5096 acting as PE (Provider End) routers, when the VPLS (Virtual Private LAN Service) gets switched multiple times between the primary path and backup path after some time programming fails and the software starts throwing errors. It will impact VPLS services.
PR Number
Synopsis
Category: ACX MPLS
1726711
[ACX5048] L2circuit might drop forwarding traffic after flaps although it's in UP state; acx_rt_ccc_eth_vpws_vpn_uni_port_add:UNI VPWS port_add failed AC-IFL: <> VPN: <> (-15:Invalid configuration)
Product-Group=junos
- Upon multiple operations of deactive/active of the interface, pfe related mpls uni port stale entry might be created with invalid match vid due to which tagged traffic start dropping. - If the system is in the issued state, then the problematic l2circuit might be identified with the error logs seen below upon l2circuit flaps. fpc0 acx_bcm_mpls_uni_port_delete: VPWS port_del failed VPN: 12443 (-7:Entry not found) fpc0 acx_bcm_mpls_uni_port_add: NNI VPWS port_add failed (-15:Invalid configuration) fpc0 acx_rt_ccc_eth_vpws_vpn_uni_port_add:UNI VPWS port_add failed AC-IFL: 715 VPN: 12443 (-15:Invalid configuration) - Upon the l2circuit hits the issue, even if it's up and running after the flap, it might drop all traffic forwarded.
PR Number
Synopsis
Category: ACX Services feature
1612212
On Junos platforms, cfmd core dumps might be seen in the logs if CCM configuration is changed from AE IFL to the physical IFL in a single commit
Product-Group=junos
On Junos platforms, when CCM configuration is changed from the AE IFL to the physical IFL which is a part of the AE bundle, cfmd core dumps might be seen in the logs.
PR Number
Synopsis
Category: MPC Fusion SW
1716766
A 10G port on a MPC2E or MPC3E 4x10G MIC can randomly flap constantly every few seconds
Product-Group=junos
On Junos MX platforms, the interface flaps in every few seconds on the 10G port on 4x10G MIC on MPC2E-NG or MPC3E-NG card whatever cause the interface to go down.
PR Number
Synopsis
Category: BBE dynamic profile related issues
1714778
PPPoE and DHCP subscriber connection on dynamic VLAN can fail on Junos MX platforms
Product-Group=junos
On Junos MX platforms supporting subscriber services, cleanup of a dynamic VLAN (Virtual Local Area Network) session may fail if SDB (Subscriber Database) becomes briefly unavailable. The dynamic VLANs will stay in an active state, but all PPPoE (Point to Point Over Ethernet) and DHCP (Dynamic Host Configuration Protocol) subscriber connection attempts over this VLAN will fail.
PR Number
Synopsis
Category: BBE packet trigger access model issues
1726136
PTSP subscribers are stuck in 'configured' state
Product-Group=junos
On MX platforms supporting packet-triggered subscribers and policy control (PTSP) feature, a high percentage of packet triggered subscribers are getting stuck in 'Configured' state due to an authentication failure.
PR Number
Synopsis
Category: Border Gateway Protocol
1651211
Delay in BGP session establishment due to longer time for the listening task to be ready on all platforms running "rpd"
Product-Group=junos
On all platforms running rpd, the longer time for the listening task to be ready might have the longest time for the active task to be created, resulting in BGP session delay establishment.
1670715
The rpd process crash is observed when running BGP-LS EPE configuration with RIB sharding enabled
Product-Group=junos
The rpd process crash is observed when running BGP-LS (Border Gateway Protocol - Link-State) EPE (Egress Peer Traffic Engineering) configuration with RIB sharding enabled since the label allocation is only allowed in the main thread. But the shards thread was trying to allocate the label during EPE configuration parsing.
1732833
RPD core dumps may be seen when BGP Rib Sharding is used
Product-Group=junos
RPD core dumps may be seen when BGP Rib Sharding is used
1739919
Junos OS and Junos OS Evolved: A BGP session will flap upon receipt of a specific, optional transitive attribute (CVE-2023-0026)
Product-Group=junos
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA71542
[juniper.net]
for more details.
PR Number
Synopsis
Category: BBE Remote Access Server
1697392
A few subscriber sessions will not be up post RE switchover
Product-Group=junos
On MX platforms, in a high scale subscriber scenario with close to 100% address pool utilization, when the session table and the IP pool database are out of sync and a switchover is performed, authd assigns an in-used IP address to the new subscriber session. This issue doesn't have an impact on existing subscribers but is not able to keep the new sessions up.
PR Number
Synopsis
Category: MX Platform SW - FRU Management
1707976
Upon ISSU upgrade or system reboot or FPC restart the DAC 100G speed configured port might not come up
Product-Group=junos
If the ISSU upgrade, FPC restart, or system reboots, then the 100G DAC cable port link goes down intermittently. The issue is seen due to hardware failing to lock onto data stream and RX CDR clock not locked.
PR Number
Synopsis
Category: Enhanced Broadband Edge support for cos
1713968
Subscribers connectivity is lost due to multiple MIC restart on all Junos MX platforms with MPC5E and BBE configuration
Product-Group=junos
On all Junos MX platforms with MPC5E and BBE (Broadband Edge) configuration, subscribers connectivity will be lost due to multiple MIC (Modular Interface Card) restart.
PR Number
Synopsis
Category: L2NG Access Security feature
1724933
On certain Junos EX and QFX platforms the static ARP entries for DHCP-security are not present
Product-Group=junos
On certain Junos EX series switches, the static MAC (Media Access Control) bindings are not present in certain conditions. This issue will be seen when the static DHCP (Dynamic Host Configuration Protocol)-security ARP(Address Resolution Protocol) bindings are moved from an interface having a higher interface number to an interface with a lower interface number. Due to the binding not happening, there will be impact on the traffic. The workaround when such a binding change is done is to restart the DHCP services after the configuration is committed.
PR Number
Synopsis
Category: Device Configuration Daemon
1714267
The interface speed gets set to a lower speed when the interface is disabled and enabled because renegotiation of the interfaces happens at the previously negotiated speed
Product-Group=junos
On Junos platforms with MPC line cards, negotiated interfaces will try to come up with the speed already negotiated instead of using the original interfaces speed even if re-negotiation happens like reinserting cable.
1731190
The lt/vt/ut interfaces may not recover from the disable-pfe (admin down) state if the GRES switchover is done before restarting FPC
Product-Group=junos
On all Junos Platforms when a PFE (Packet Forwarding Engine) gets disabled to a CM (Chassis Manager) error disable-pfe action or any other reason and a GRES (Graceful Routing Engine Switchover) happens, the lt/vt/ut (Logical Tunnel/Virtual Tunnel/Uplink Tunnel) interfaces will not recover after the FPC (Flexible PIC Concentrator) restart even though the error condition is recovered resulting in traffic loss.
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: BGP MPLS VPN specific issues
1719507
L3VPN traffic loss and PFE errors can be seen after an LSP Flap
Product-Group=junos
On ACX2200 platforms, when L3VPN (Layer 3 Virtual Private Network) and MPLS-LSP (Multiprotocol Label Switching - Label-Switched Paths) is configured, L3VPN traffic loss and PFE (Packet Forwarding Engine) errors can be seen after an LSP flap.
PR Number
Synopsis
Category: DNX VPLS
1722919
Intermittent MAC move is observed in VPLS environment when ACX5448 or ACX710 is acting as a PE device
Product-Group=junos
On Junos ACX5448 and ACX710 platforms acting as a PE (Provider Edge) device in a VPLS (Virtual Private LAN Services) environment and multiple CE (Customer Edge) interfaces are bound to a single routing instance, intermittent MAC move is observed. This is a corner case scenario and the MAC move can be triggered due to various reasons and not limiting to mac address time out, L2 loop on the extended network or a congested backbone link connecting the PE devices. The split horizon rule in VPLS fails and the traffic received from VPLS LSI (Label-Switched Interface) is forwarded back towards the MPLS core through the LSI.
PR Number
Synopsis
Category: EVPN control plane issues
1723832
The rpd core is seen in the long-running devices with EVPN enabled
Product-Group=junos
On Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) community object reference count is not handled properly during the process of remote BGP peer routes update event. The community reference count is increasing during the increment function. However, decrement functions are not called in one of the places after processing the routes update. This will lead to a disturbance of the continuity reference count, which will cause an rpd crash.
PR Number
Synopsis
Category: EX4400 PFE software
1716902
IGMP/MLD queries may get dropped if received on a port on the backup VC member when IGMP/MLD snooping is enabled
Product-Group=junos
On Junos QFX and EX in the VC (Virtual Chassis) scenario, when the switch is acting as pure L2 (Layer 2), and forwarding IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery) query as transit traffic, if IGMP/MLD snooping is enabled then IGMP/MLD queries may get dropped if received on a port on the backup VC member resulting in IGMP/MLD groups to expire.
1718286
DHCP services are impacted as DHCP binding will not work as expected
Product-Group=junos
On all Junos and Junos Evolved platforms, all the DHCP (Dynamic Host Configuration Protocol) security services will be impacted as the DHCP-security binding will not work if the DHCP server-facing interface is a VTEP (VXLAN tunnel endpoint) interface.
PR Number
Synopsis
Category: Express PFE FW Features
1727067
FPC crashes when the firewall filter is configured with above 65k prefixes in a single filter
Product-Group=junos
On the below PTX platforms ( PTX1000, PTX3000 (NextGen), PTX5000, PTX10008, PTX10016 and QFX10002), when prefixes above 65K are configured in a single firewall filter, FPC (Flexible PIC Concentrator) crash would be observed.
PR Number
Synopsis
Category: Express PFE including evpn, vxlan
1701636
Aggregated Ethernet interface member with vlan-id-list configured not forwarding traffic
Product-Group=junos
On Junos QFX10002, QFX10008 and QFX10016 platforms, AE(aggregated-ethernet) interface member with vlan-id-list configured does not forward traffic thus leading to traffic loss.
1720527
L2 Multicast traffic drops when PIM is configured without IGMP Snooping enabled
Product-Group=junos
On Junos QFX10002 and QFX10008 platforms, L2 (Layer 2) Multicast traffic drop is observed when PIM (Protocol Independent Multicast) is configured without IGMP (Internet Group Management Protocol) Snooping enabled in the EVPN-VXLAN scenario.
PR Number
Synopsis
Category: MX 100GE MPC
1719746
Packets are not sent or received properly with '3D 20x 1GE(LAN)-E, SFP' after 100Mbps auto-negotiation
Product-Group=junos
On MX platforms with MIC-3D-20GE-SFP-E + SFP-T combination, setting 100Mbps speed on the opposite interface results in packet loss with FrameCheckSequenceErrors.
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.
1725686
Unnecessary SPF calculation is causing high CPU utilization
Product-Group=junos
On all Junos and Junos Evolved platforms, very frequent SPF (Shortest Path First) calculation, being caused by leaking multiple prefixes across the IS-IS areas, is causing high CPU utilization.
PR Number
Synopsis
Category: jdhcpd daemon
1731784
Dhcp security bindings may not happen when DHCP security is enabled on multiple vlans along with dhcp stateless relay
Product-Group=junos
When DHCP security is enabled on multiple vlans along with dhcp stateless relay enabled at that time, dhcp security bindings may not happen.
1742696
Address allocation for DHCP client will fail if 'force-discover' configuration is enabled on client
Product-Group=junos
Junos based platforms operating as DHCP-client with 'force-discover' knob enabled, will get stuck in requesting state when DHCP-Server is not responding. Client will face login failure and thus traffic would be impacted.
PR Number
Synopsis
Category: Adresses ALG issues found in JSF
1722877
Device crashed while processing H323 traffic in SRX and MX
Product-Group=junos
The SRX Device and MX with MS-MPC and MX-SPC3 service cards, crashes due to a timing issue, while processing H323 traffic.
PR Number
Synopsis
Category: Flow Module
1683334
Packet loss on GRE Tunnel due to improper route look-up for tunnel destination
Product-Group=junos
On SRX platforms, due to improper route look-up for the tunnel destination if the GRE tunnel is configured in a virtual routing-instance for which packet loss is observed.
PR Number
Synopsis
Category: Firewall Network Address Translation
1712738
Some sessions will not be deleted when the NAT rule is deleted from the system
Product-Group=junos
On all SRX platforms with NAT (Network Address Translation) configured, upon deleting a NAT rule the session associated with deleted rule continues to exist in the system, until the connection close initiated by the session. This is a rare timing issue.
PR Number
Synopsis
Category: User Firewall related issues
1683420
SRX Branch models are unable to connect to domain controller on installing Microsoft KB update
Product-Group=junos
On SRX300 series and SRX550M, when the User Identification feature is used with Active Directory, after the Domain Controller server installs updates related to Microsoft's KB article
KB5004442
[juniper.net]
, SRX is no longer able to connect to it. The PR1637548 did not fix this issue for these specific SRX platforms.
1701990
The user-id entries will not be synced with secondary node
Product-Group=junos
On Junos platforms, user-id process doesn't work properly (user-id ?process also sync users primary and second node). As a result, active directory user-ip-mapping entries were not synced to the secondary node and due to that user connection will drop. When the issue happens, storage space eventually go full and the user may notice the issue at that time.
PR Number
Synopsis
Category: Security platform jweb support
1735314
Editing security policy configuration via J-web is enabling "Exclude Selected" unexpectedly
Product-Group=junos
On Junos platforms, when you cancel editing source/destination address in security policy using J-web, "Exclude selected" is unexpectedly enabled.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1706364
With MAC limit and persistent MAC learning configuration l2ald process will crash when MAC is learned through remote peers
Product-Group=junos
On all Junos and Junos Evolved platforms, l2ald (Layer 2 Address Learning Daemon) will crash if the MAC (Media Access Control) limit is configured with persistent MAC learning and MAC is learned from remote peers through ICCP (Interchassis Control Protocol).
1723400
Unable to commit configs interface-mac-limit on sub-interfaces with vlan-tagging / flexible-vlan-tagging
Product-Group=junos
On QFX10K platforms unable to configure interface-mac-limit on sub-interfaces with vlan-tagging / flexible-vlan-tagging.
PR Number
Synopsis
Category: lacp protocol
1609618
LACP Member interfaces might get stuck in out of sync state
Product-Group=junos
When sync-reset feature is enabled on the device then few member interfaces might stay in out of sync state even when number of available child interfaces is greater than minimum-links configured for the Lag interface. This will affect the overall capacity of the lag interface.
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: MX Timing software
1652275
PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7
Product-Group=junos
PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7 No functionality impact.
1664569
Switch Fabric Board information for supporting PTP on MX10k8 with MX10K-LC2101 LC(s)
Product-Group=junos
MX10k8 with MX10K-LC2101 Linecard(s) supports *PTP* only with JNP10008-SF Switch Fabric Board(s), *PTP* currently doesn't work with JNP10008-SF2 Switch Fabric Board(s).
1704633
Interface flaps are seen after PTP GM changes to a different FPC slot
Product-Group=junos
On MX platforms, when PTP (Precision Time Protocol) is configured, the interfaces will flap after the PTP GM (Grand Master) is changed to a different FPC (Flexible PIC Concentrators) slot. The flaps can last for several seconds. Chassis-SyncE clock is also influenced by PTP phase change.
1724254
On certain Junos MX platforms with SCB3 SyncE fails after enabling PTP
Product-Group=junos
On Junos MX platforms having SCB3 (Switch Control Board), the SyncE (Synchronous Ethernet) can be stuck in "Clock_Aborted" state. This issue is seen in release 20.4R3 onwards when PTP (Precision Time Protocol) is operated in hybrid mode, the SyncE failure will hinder the operation of applications like G.8275.1 deployment will fail. There is a fix in 20.4R3-S4 with JSU (Juniper Selective Upgrade) J10.2. Below are the important notes to consider regarding the verification of the fix. - -> JSU upgrade can be performed to replace the clksyncd with fix to address this issue. - -> However, if the system is already in a problem state before the JSU upgrade, a one-time deactivate and activate of "protocols PTP" and "chassis synchronization" configuration is needed to recover from the current problem state after the JSU upgrade of clksyncd is performed.
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.
PR Number
Synopsis
Category: Express Chip L3 software
1713279
Next-hop programming issue at PFE on Junos PTX and QFX10k platforms when the member of unilist is in hold state
Product-Group=junos
On PTX Series routers and the QFX10000 line of switches, traffic going over unilist is dropped when unilist member goes from next-hop hold state to unicast/aggregate state.
PR Number
Synopsis
Category: Periodic Packet Management Daemon
1619886
BFD sessions flaps are observed on scaled setups if PFE restarts
Product-Group=junos
BFD sessions flap can be seen on a scaled setup when a PFE is restarted. The issue state can be confirmed if the peer IPs are observed more than once on the ppm entries, each IP should appear only once per routing instance.
PR Number
Synopsis
Category: PPPoE functional plugin for bbe-smgd
1696221
The smgd (Enhanced Subscriber Management) crash is seen during creation/deletion of Interface-set in Subscriber management scenario
Product-Group=junos
bbe-smgd process might crash with generating a coredump if any interface-set used for subscriber management has the length more than 12 characters.
PR Number
Synopsis
Category: QFX platform fabric mgmt for Express ASIC chip
1734735
Packet drop is observed due to SIB ASIC issue on fabric
Product-Group=junos
On all inserted FPCs of Junos based QFX10K8/QFX10K16 platforms, due to SIB (Switch Interface Board) ASIC (Application-Specific Integrated Circuit) issue on fabric, packets are getting dropped and major errors "PECHIP_CMERROR_EPW_MISC_INT_EVENTS_CRC_ERR (0x2101aa)" are reported. These errors are not auto-cleared on a couple of FPCs.
PR Number
Synopsis
Category: QFX PFE Class of Services
1641572
Traffic drop would be observed along with the error message 'Buffers are stuck on queue' when performing the OIR in the 100G QSFP interface
Product-Group=junos
On QFX5110-32Q platforms, the traffic drop along with the error message "Buffers are stuck on queue" will be seen when the Online Insertion and Removal (OIR) is performed with 100G QSFPs on continuous ports 28, 29, 30, 31 at the same time.
1726124
The class of service subsystem crashed after the device is restarted or the switchover is performed
Product-Group=junos
On Junos QFX5100 and QFX5110 platforms in virtual chassis, the cosd crash is observed when the GRES (Graceful Routing Engine Switchover) is performed or the device is restarted, due to which the Class of Service (CoS) functionality will not work. It is a rare issue.
PR Number
Synopsis
Category: QFX5K hostpath
1721318
Error message "%PFE-3: fpc0 Failed to get ifl for ifl index = XXX" is generated when receives DHCP packet via remote vtep.
Product-Group=junos
You may see the following error message in VXLAN environment. This can happen when the device receives DHCP packet via a remote vtep and L3 interface (IRB) is not assiged on the egress interface. Even though there is no DHCP configuration, the packet injection happens and it fails to get IFL index as there is no IRB interface on the egress interface. Oct 7 16:31:51.137 2022 d16-25 : %PFE-3: fpc0 Failed to get ifl for ifl index = 640
1723465
PFE crash is seen on Junos when file-logging is disabled
Product-Group=junos
On Junos QFX5K platforms, when file-logging is enabled for ukern_trace handle and the logs are written continuously to the corresponding buffer due to a network issue, disabling file-logging for that handle will cause a PFE crash and will lead to a complete traffic loss.
PR Number
Synopsis
Category: QFX L2 PFE
1705853
Tracking PR to add the null check for list_get_head if magic is NULL.
Product-Group=junos
On all Junos platforms, as list_get_head function is called in multiple places in pfe we needed previous 3 functions on the stack which had called list_get_head, so we could debug why 'list_get_head list has bad magic' this error has occured.
PR Number
Synopsis
Category: QFX L3 data-plane/forwarding
1666260
Traffic is not restored when l2circuit configurations are deleted and added back on QFX5K
Product-Group=junosvae
On Junos QFX5K platforms, flapping the Layer 2 circuit ports or removing and re-adding the configuration on the l2circuit ports, the re-configuration of the access side port fails and traffic ingressing or egressing out of that port gets dropped.
1704489
High CPU utilization causes a latency/slowness issue on QFX platforms
Product-Group=junos
On QFX5110 and QFX5120 platforms, latency or slowness issue is observed when the traffic is passing through a layer 3 interface configured with just family inet/family inet6 due to unwarranted MAC lookup. This could lead to traffic loss on that interface.
1724675
Traffic loss will be observed with vlan tagging and/or vlan normalisation in a specific design (using a looped cable)
Product-Group=junos
Upon upgrade to Junos versions (junos:20.3R2, 20.3R3, 20.3X75-D20, 20.4R2, 21.1R1, 21.2R1), network connectivity is lost for traffic requiring vlan normalization and having DMAC one of the switch's MAC addresses. For example, incoming traffic has two vlans (S-vlan, C-vlan) ingressing on an interface and switch uses a looped link to provide routing via an IRB. --- (S-vlan|C-vlan) -- -> SW_X --- C-vlan -- -> SW_X_irb ARP and L2 learning occurs as expected but upon receiving the frame with DMAC of a local interface, switch takes a route lookup action instead of bridging and vlan normalization due to the frame having DMAC as the MAC of one of its interfaces. Hence, the traffic is not sent via looped cable to the L3 interface.
1725375
DCPFE process crash can be seen on all Junos EX and QFX5K platforms with MACSEC enabled
Product-Group=junos
On all Junos platforms supporting MACSEC (Media Access Layer Security), the DCPFE (Dense Concentrator Packet Forwarding Engine) process might crash in a rare scenario when the configuration of MACSEC is deleted from the interface and the PFE is trying to access the memory location of the interface. The DCPFE process crash will lead to the FPC (Flexible PIC Concentrator) reboot but the system will self-recover.
1732708
SNMP polling Timeout due to OID 1.3.6.1.2.1.31.1.1.1.10.514 ( ifInOctets.514 )
Product-Group=junos
When trying to poll information via SNMP, the device stops reponding causing a SNMP timeout, the issue is due to sxe-0/0/0 private interface that is marked as public interfaces which causes it to query kernel for statistics.
PR Number
Synopsis
Category: QFX MPLS PFE
1742364
Traffic dropped is observed in the MPLS LDP scenario when the peer device MAC address is changing
Product-Group=junos
On Junos QFX5100 and EX4600 platforms when there is MAC (Media Access Control) change for the LDP (Label Distribution Protocol) neighbor and IP remains the same, the ARP (Address Resolution Protocol) update is proper but MPLS LDP may still use the stale MAC address of the neighbor. If there is any application/service such as MP-BGP using LDP as next-hop, all transit traffic pointing to the stale MAC address will be dropped.
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1686539
The dcpfe process crashes on QFX5k and EX4k platforms
Product-Group=junos
On QFX5k, EX4100, EX4300, EX4400, and EX4650 platforms, the dcpfe process crash will be seen when EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) is configured.
1716996
The dcpfe process crashes on QFX5K devices
Product-Group=junos
On Junos QFX5K platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process will crash occasionally in EVPN-VXLAN (Ethernet Virtual Private LAN - Virtual Extensible LAN) scenarios. As a result, the FPC (Flexible PIC Concentrators) will restart causing traffic loss and recover on its own.
1738276
High convergence time in the EVPN-VxLAN uplink failover scenario
Product-Group=junos
On Junos QFX5K platforms in the EVPN-VxLAN scenario, due to high convergence time, traffic loss is more than expected when the uplink to the spine disabled (CLI initiated uplink failover).
PR Number
Synopsis
Category: QFX5200/5110/5120/5210 Platfom issues
1710952
No alarm is raised when PSU is inserted with different airflow directions
Product-Group=junosvae
On QFX5100/QFX5110/QFX5120/QFX5200 platforms, no alarm would be raised even though inserted PSU module which has a different airflow.
1720884
Interface with QSFP+-40G-CU50CM will be down
Product-Group=junosvae
The interface will be down on EX and QFX platforms with QSFP+-40G-CU50CM (740-044512) resulting in traffic loss. In the VCP (Virtual Chassis port) scenario if connected with QSFP+-40G-CU50CM it does not come up and break the VC (Virtual Chassis) environment when upgrading or rebooting the device.
1725116
The 100G interface will remain down post rebooting the device
Product-Group=junosvae
On the Junos QFX5200 platform, sometimes upon restarting the device the 100G link will not come up and will remain down, impacting the traffic flowing through it.
PR Number
Synopsis
Category: RPD infrastructure issues related to NSR, GRES, switchover,
1701146
The rpd crash will be observed when any commit is performed
Product-Group=junos
On all Junos and Evolved platforms with RSVP auto-mesh dynamic tunnel configuration, whenever a commit is done the rpd (Routing Process Daemon) crash will be seen. This happens due to null pointer access in the memory.
PR Number
Synopsis
Category: RPD route tables, resolver, routing instances, static routes
1742147
Memory leak observed when reconfiguring the flow routes
Product-Group=junos
On all Junos and Junos OS Evolved platforms, if the nexthop of a flow route is the same as it was before when reconfiguring flow routes, memory leak occurs. High memory use of routing process daemon(rpd) is seen as a result of this leak. A kernel out of memory message is observed which results BGP flap.
PR Number
Synopsis
Category: IPSEC functionality on M/MX/T ser
1635882
IPsec tunnel may not establish after a flap
Product-Group=junos
IPsec tunnel may not establish after a flap if the remote end is aggressively retrying and sending many IKE requests.
PR Number
Synopsis
Category: SNMP Infrastructure (snmpd, mib2d)
1691986
Consistent high CPU usage is seen on the device post reboot
Product-Group=junos
On all Junos and Junos Evolved platforms consistent high CPU usage in snmpd immediately after reboot.
PR Number
Synopsis
Category: Remote Access VPN issues on SRX
1715297
The nsd process may report an error msg
Product-Group=junos
On SRX platforms, nsd process may report harmless an error msg during the commit.
PR Number
Synopsis
Category: SRX branch platforms
1713759
Continuous vmcores observed on the secondary node when committing the "set system management-instance" command
Product-Group=junos
On Junos SRX3xx series platforms, when the "set system management-instance" command is committed on the secondary node, continuous vmcores are observed on primary and secondary nodes. No recovery action is needed for the primary node and the secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until the management-instance knob is removed using the "delete system management-instance".
1715247
Interface speed stays 100Mbps when removing speed and duplex command separately
Product-Group=junos
On SRX branch series, when the interface speed is set to 100Mbps and the link-mode is set to full-duplex, the interface speed remains at 100Mbps even the speed and duplex commands are removed separately.
1719108
OAM not working with flexible-vlan-tagging
Product-Group=junos
OAM is not working when flexible-vlan-tagging is enabled
1738271
"Minor Autorecovery information needs to be saved" alarm is not displayed after zeroize
Product-Group=junos
On SRX Branch platform, "Minor Autorecovery information needs to be saved" alarm is not displayed after running zeroize command
PR Number
Synopsis
Category: Stout cards (MPC7, MPC8, MPC9) microkernel issues
1727427
FPC crash observed when the ASIC usage is high
Product-Group=junos
On platforms with MS-MPC/MPC1/2/3/4/5/6/7/8/9/JNP10K-LC2101/JNP10003-LC2103/JNP10K-LC480 line cards and EX9200/EX9204/EX9208/EX9214/EX9251/EX9253 series devices, route churn (add or deletes) when the ASIC usage crosses a threshold (ASIC usage is high) which leads to a FPC crash.
PR Number
Synopsis
Category: ZT/YT pfe infra issues
1697215
Stoppage of statistics update on MPC10E
Product-Group=junos
We have seen the stoppage of statistics update on MPC10E cards running older releases. Please note that this issue affects only the statistics update with no impact on forwarding or connectivity. This issue is seen very rarely, and we don't know the exact trigger yet. A couple of occurrences seem to point at link flaps as trigger but not conclusive. We think this may be due to a data race condition and the changes in this PR address a potential issue.
PR Number
Synopsis
Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1718595
Subscribers disruption is seen on the AE interface after the "disable-pfe" action
Product-Group=junos
On all MX platforms with MPC7/8/9/LC2101/LC2103 line cards, when a "disable-pfe" action is executed for major cmerrors, there will be improper flagging of timeouts and incorrect logging out for all subscribers in scenarios where an AE(Aggregated Ethernet) interface is present on the disabled PFE(Packet Forwarding Engine).
PR Number
Synopsis
Category: Trio pfe bridging, learning, stp, oam, irb software
1731564
VPLS traffic gets blackholed by qualified-bum-pruning mode
Product-Group=junos
On all MX and EX9K platforms, qualified-bum-pruning-mode completely blackholes VPLS (Virtual Private LAN Service) traffic with network-services configured in enhanced-ip mode.
PR Number
Synopsis
Category: Trio pfe l3 forwarding issues
1700203
DHCP offer requests are dropped while routed towards different VRFs of transit router
Product-Group=junos
On all Junos platforms with route leaking and no-snoop configuration, DHCP (Dynamic Host Configuration Protocol) offer requests could be dropped while traversed to different VRFs (Virtual Routing and Forwarding) from default RI (Routing Instance).
1714656
Incorrect Destination MAC and Source MAC addresses while processing transit packets over LT IFL
Product-Group=junos
On MX platforms with MPC10, MPC11, LC9600, and MX304-LMIC16, while processing transit packets over LT IFL (logical interface) incorrect Destination MAC and Source MAC addresses are observed when the Ethernet encapsulation type is configured on the LT interface.
1739854
Major alarms will be observed on the FPC when ALB is enabled under AE interface
Product-Group=junos
On Junos MX platforms with MPC2-MPC9 line cards configured with ALB (Adaptive Load Balancing) under AE (Aggregate Ethernet) interface and Network-Services IP mode, when the AE interface comes up initially or activating AE after deactivating, the error logs of "Bad JNH Write to unilist-selector" and "LUCHIP Uncorrectable ECC" would be observed. These errors will lead to major alarms on the FPC (Flexible PIC Concentrators) causing traffic impact.
PR Number
Synopsis
Category: Junos Automation, Commit/Op/Event and SLAX
1717425
Junos platform device unable to commit configuration in recovery mode
Product-Group=junos
On all Junos platforms where snapshot is supported, when a device is rebooted from recovery mode it fails to commit configuration due to problems with slax import and device might go into amnesiac mode due commit fail.
PR Number
Synopsis
Category: Configuration mgmt, ffp, load-action, commit processing
1659783
The configuration might roll back after performing "commit confirmed" and then reboot
Product-Group=junos
On all Junos OS and Junos OS Evolved platforms, the configuration might roll back after performing "commit confirmed" and then a reboot.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1638847
The mustd process crash might be observed with persist-group-inheritance
Product-Group=junos
On all Junos and Junos Evolved platforms configured with persist-group-inheritance, which is enabled by default from 19.4R3 onwards, might lead to mustd process crash in highly scaled configuration.
PR Number
Synopsis
Category: web filterig issues
1715260
utmd core has seen at commit when *.* or *.*.* is configured at url-pattern
Product-Group=junos
When url-pattern contains '*.*' or '*.*.*', utmd core is generated and commit fails .
PR Number
Synopsis
Category: PTX/QFX10002/8/16 specific software components
1734703
Speed configuration mismatch causes the ukern core on Junos PTX10008 and PTX10016 platforms
Product-Group=junos
On Junos PTX10008 and PTX10016 platforms, when the speed configuration on the interface is not matching with the speed of the optics present in the port, it causes memory corruption because of this FPC will crash and restart. Traffic loss till the FPC restarts after the ukern core.
PR Number
Synopsis
Category: VMHOST platforms software
PR Number
Synopsis
Category: Virtual Router Redundancy Protocol
1720943
Issue in VRRP inline adjacency whenever a master router uplink goes down on MX platforms
Product-Group=junos
On all Junos MX platforms, when "set protocols vrrp delegate-processing" knob is enabled in Virtual Router Redundancy Protocol (VRRP) protocol and VRRP track is also enabled for uplink interfaces in that scenario if the master router uplink fails and the master priority remains higher than the backup router even after the master router uplink failure, this results in an issue with VRRP inline adjacency.
PR Number
Synopsis
Category: usf nat related issues
1598382
The TCP keepalive does not reach host on the private Network
Product-Group=junos
On all MX platforms with SPC3 cards where tcp-tickle knob is enabled under services-options in DS-lite (Dual-Stack lite) with NAT scenario , TCP keepalive sent by AFTR (Address Family Transition Router) will not be properly encapsulated by IPv6 addresses.
1729801
Traffic drops are observed on MX Platform configured with PCP mapping along with NAT
Product-Group=junos
On all MX platforms with SPC3 cards and PCP (Port Control Protocol) with NAT (Network Address Translation) configured, the PCP client should renew the mapping before its expiry time to keep the PCP mapping always active. The sessions are not refreshed with the received PCP mapping refresh. The issue is seen if the traffic from outside the network (public network) toward B4 (softwire initiator) was suspended for sometime. When traffic started again toward B4 from outside the network, it will be dropped and service will be impacted.
20.4R3-S8 - List of Known issues
PR Number
Synopsis
Category: "agentd" software daemon
1665516
Na-grpcd process core observed in telemetry services
Product-Group=junos
On all Junos and Junos OS Evolved platforms, due to race condition happening at the time of AFT streaming and simultaneous multiple attempts to subscribe and unsubscribe AFT sensors, followed by modifying firewall filter configurations, na-grpcd can core on rare occasions. This will cause a temporary outage of streaming telemetry services. The service will self-recover upon restart of the process.
Resolved In:
evo:20.4R3-S7-EVO evo:21.4R2-S1-EVO evo:21.4R3-EVO evo:21.4X1-EVO evo:22.1R3-EVO evo:22.3X50-EVO evo:22.3X80-D36-EVO evo:22.3X80-D37-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:21.4R3 junos:22.1R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: dynamic vlan creation and associated processing
1743903
If more than 32 vlan ranges are configured under the dynamic-profile then login issue and traffic impact can be seen with subscribers of random VLANs
Product-Group=junos
On all Junos platforms that support subscriber services, when more than 32 VLAN ranges are configured, random VLAN (Virtual Local Area Network) traffic is impacted and subscribers are unable to login.
Resolved In:
junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: BBE OS Infrastructure library
1732216
'max-db-size' configuration is optional in routers having DRAM greater than or equals to 32GB
Product-Group=junos
On Junos MX platforms, to enable Enhanced Subscriber Management feature without 'max-db-size' configuration on router >=32GB DRAM(Dynamic Random Access Memory), router needs to be rebooted only once instead of rebooting twice.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.2R3-S4-J9 junos:21.2R3-S5-J3 junos:21.2R3-S6 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: Border Gateway Protocol
1690213
BMP will not send EOR message
Product-Group=junos
On all Junos and Junos Evolved platforms, BMP(BGP Monitoring Protocol) will not send EOR(End of RIB) message for some releases. This will impact some data collections.
Resolved In:
evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R2 junos:23.1R1 junos:23.2R1 junos:23.3R1
1742416
RPD scheduler slip is observed when the BGP session flaps and subsequent configuration changes for the same peer
Product-Group=junos
On all Junos and Junos Evolved platforms, high CPU (RPD scheduler slips) leads to session timeouts/flaps for other protocols running in the system.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
1745073
RPD using 100% CPU after adding duplicate community in config
Product-Group=junos
When intermediate routers don't support certain large/extended communities, receiving router will mark partial bits on the communities. However, when a community is added using policy for the received route, where some of the policy added community members are duplicates (already present on route), policy evaluation is leading to creation of one community per evaluation (as the partial bits are no copied and hence the existing entries are not matching). This is leading to RPD CPU staying high at 100%, for a time which increase with scale, as every policy evaluation (community add) is leading to comparison to the entries present. Fix is to ensure that community re-size preserves partial bits intact, as in current process with non-duplicated community config. Flags and other fields are reset anyway.
Resolved In:
evo:22.2R3-S2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: EX4400 PFE software
1731522
The traffic drop will be observed after changing the VSTP VLAN configuration
Product-Group=junos
On Junos EX4400, EX4100, EX2300, EX3400, and QFX5K platforms, traffic drop would happen on RSTP (Rapid Spanning Tree Protocol) enabled port attached to a VLAN (Virtual Local Area Network) when the same VLAN has VSTP (VLAN Spanning Tree Protocol) enabled on a different port and there is a configuration change done on VSTP for that VLAN.
Resolved In:
junos:21.2R3-S6 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.1R3-S4 junos:22.2R3-S1 junos:22.2R3-S2 junos:22.3R3 junos:22.3R3-S1 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1733365
Error logs are seen with a non-vxlan dot1x enabled port
Product-Group=junos
In a heaviliy loaded system in a specific scenario (Dot1x in multiple supplicant mode & dynamic vlan from radius server & non vxlan access port) following log message may be captured in the syslog - {brcm_as_dot1x_vxlan_set_mac_learning_mode:1168 dot1x bd_get failed for bd index 0}. This log is not impacting any funtionality.
Resolved In:
junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S1 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: Security platform jweb support
1698386
Junos OS: J-Web: Multiple Vulnerabilities in PHP software
Product-Group=junos
PHP software included with Junos OS J-Web has been updated from 7.4.30 to 8.2.0 to resolve multiple vulnerabilities. Please refer to https://supportportal.juniper.net/
JSA71653
[juniper.net]
for more information.
Resolved In:
evo:23.2R1-EVO evo:23.3R1-EVO junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Layer 2 Control Module
1739975
Layer 2 traffic will be dropped on VSTP disabled interface
Product-Group=junos
On Junos platforms, Whenever an interface is disabled under VSTP (VLAN Spanning Tre Protocol) configuration, the issue will be seen in the following cases. 1. When interface, IFBD (Interface Family Bridge Domain) and VSTP, configured via single commit. (In case of new configuration) 2. When VSTP configurations are present and chassisd restarts/device reboots, then issue will be seen. (During ifd delete and add, issue will be seen)
Resolved In:
evo:21.2R3-S6-EVO evo:21.3R3-S5-EVO evo:21.4R3-S5-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1727954
On all Junos and Junos Evolved platforms the l2ald process memory usage is seen to increase over time
Product-Group=junos
On all Junos and Junos Evolved platforms service impact is seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.
Resolved In:
evo:21.2R3-S6-EVO evo:21.4R3-S4-EVO evo:22.1R3-S4-EVO evo:22.2R3-S2-EVO evo:22.3R3-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1733543
Traffic loss is seen when "lacp force-up" knob is configured
Product-Group=junos
On all Junos and Junos OS Evolved platforms, traffic destined to the core is getting dropped when "lacp force-up" knob is configured on ae interface under EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR Number
Synopsis
Category: Multiprotocol Label Switching
1738774
Traffic blackhole due to an additional label when CCNH is toggled
Product-Group=junos
On all Junos and Junos Evolved platforms, with scaled Border Gateway Protocol (BGP) routes, when Chained Composite Next Hops (CCNH) is toggled, a few next-hops end up creating additional labels causing a traffic blackhole.
Resolved In:
evo:21.4R3-S5-EVO evo:22.3X50-EVO evo:22.3X80-D36-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: MX10K platform
1719915
SNMP TRAP for "Power Supply Removed" will not generate after removing a PEM which doesn't have power feed
Product-Group=junos
If a PEM (Display Power Entry Module) doesn't have power feed by doing power switch OFF, SNMP (Simple Network Management Protocol) TRAP "Power Supply Removed" will not generate by removing the PEM physically.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:20.3X75-D36 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: QFX L2 PFE
1696428
Adding more than 256 VLANs as name tags on the same interface results in dcd crash
Product-Group=junos
On all Junos platforms, the dcd (device control daemon) process crash is observed when more than 256 VLANs as name tags are added on the same interface.
Resolved In:
junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: QFX MPLS PFE
1731291
Traffic for VLAN-id 2 gets dropped in Ethernet-CCC L2 Circuit on QFX5k/EX4650 platforms
Product-Group=junos
On Junos QFX5k and EX4650 platforms traffic drop for VLAN (Virtual Local Area Network) having id 2 will be seen in the Ethernet-CCC (Circuit Cross Connect) L2 circuit. This happens because the VLAN-id is getting stripped at the egress PE (Provider Edge Router) hence causing a traffic drop at the CE (Customer Edge) Router.
Resolved In:
junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1698491
On QFX5K switch, VGA is not working when SP style config is mixed with EP style configuration
Product-Group=junos
On QFX5K switch running Junos, VGA (virtual gateway address) is not working when sharing the same VLAN (Virtual Local Area Network) between EP (Enterprise) style and SP (Service Provider)style configuration.
Resolved In:
junos:21.4R3-S4 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: RPD policy options
1744449
Policy change to a rib-group import-policy configured with global routing-options interface-routes causes the rpd issue on all platforms with EVPN-VXLAN configuration
Product-Group=junos
When a user configures "set routing-options interface-routes rib-group " along with an import policy for that particular rib-group, it will result in an unexpected behavior. It could disrupt the rpd or result in the rpd running at 100%. This issue is only related the "interface-routes" being configured in the global routing-options hierarchy with EVPN-VXLAN configuration. This issue won't be seen when routing-options configurations can have "interface-routes" enabled under specific routing instance.
Resolved In:
evo:21.2R3-S6-EVO evo:22.1R3-S4-EVO evo:22.2R3-S2-EVO evo:22.3R3-S1-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: SRX branch platforms
1591951
syslog messages: dot1xd[]: JTASK_IO_CONNECT_FAILED: ESP CLIENT:33010.143.144.0.1+33010: Connecting to 143.144.0.1+33010 failed: No route to host
Product-Group=junos
Misleading syslog message is generated for SRX branch chassis cluster setup with Junos 19.4. dot1xd[]: JTASK_IO_CONNECT_FAILED: ESP CLIENT:33010.143.144.0.1+33010: Connecting to 143.144.0.1+33010 failed: No route to host The syslog message is cosmetic, with no impact. This syslog message can be filtered from the syslog file. Layer 2 communication infrastructure between chassis cluster nodes improvements were added in 19.4R3-S9 resolving this problem.
Resolved In:
PR Number
Synopsis
Category: MX10003/MX204 Platform SW - Chassisd s/w defects
1426480
SNMP MIB jnxAlarms is not available on MX10003 and MX204 platforms.
Product-Group=junos
These MIBs are handled by craftd process, which does not run on MX10003/MX204 due to HW limitation.
Resolved In:
PR Number
Synopsis
Category: MX10002 Platform SW - Platform s/w defects
1721714
BFD session failed when configured on the loopback sub interface
Product-Group=junos
On the MX10003 and MX304 platforms, BFD (Bidirectional Forward Detection) session failed to come up when configured on the loopback sub interface.
Resolved In:
evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.2R3-S5 junos:21.3R3-S5 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: ZT/YT pfe infra issues
1596039
AFT: Implementing stats push model, including SCU/DCU statistics implementation changed model.
Product-Group=junos
After this PR, stats implementation has made huge changes, starting to use a push model. This change involves the SCU/DCU statistics reading.
Resolved In:
evo:21.2R2-EVO evo:21.2R3-EVO evo:21.3R2-EVO evo:21.4R1-EVO junos:21.1R3 junos:21.2R2 junos:21.2R3 junos:21.3R1 junos:21.3R2 junos:21.4R1
PR Number
Synopsis
Category: ZT/YT pfe qos software issues
1715149
DSCP field in IPv4 header is incorrectly re-written
Product-Group=junos
On Junos platforms that support MPC10/MPC11/LC9600 line cards, whenever there is a rewrite rule configured to rewrite the DSCP bits on transit router in core network, packet loss are observed in the destination due to incorrectly re-written DSCP field in IPv4 header.
Resolved In:
evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D46 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S2-J6 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: ZT/YT pfe l3 forwarding issues
1642851
Traffic drop due to incorrect memory allocation for the default route on MPC10E and MPC11E line cards
Product-Group=junos
On MPC10E & MPC11E line cards default route information might be overwritten/lost due to incorrect memory allocation.
Resolved In:
evo:21.3R3-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:20.2R3-S6 junos:20.3X75-D46 junos:20.4R3-S4 junos:21.2R3 junos:21.3R3 junos:21.4R2 junos:22.1R1 junos:22.1R2 junos:22.2R1
PR Number
Synopsis
Category: Trio pfe l3 forwarding issues
1623271
MX Fusion extended port doesn't perform my-mac validation.
Product-Group=junos
The destination MAC (my mac) validation is not performed on MX Fusion extended port. So MX may still do L3 forwarding on a packet which is not destinated to local MAC. This is a product limiation for Fusion extended port.
Resolved In:
Modification History
First publication 2023-08-03
20.4R3-S8: Software Release Notification for JUNOS Software