Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

List of known issues for Junos Software version 21.4R3-S3

Solution

21.4R3-S3 - List of Known issues 

PR NumberSynopsisCategory: EX2300/3400 PFE
1647209DHCP traffic might be dropped when DHCP-security and RTG are enabled
Product-Group=junos		On EX2300, EX2300-48MP, and EX3400 platforms, when DHCP-security and Redundant Trunk Group (RTG) are enabled clients connected over RTG might not get DHCP IP and DHCP traffic might be dropped.

Resolved In: junos:20.2R3-S6 junos:20.4R3-S4 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S2 junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR NumberSynopsisCategory: EX-Series VC Infrastructure
1685067EX4600-VC - Master RE reboot and All-member reboot lead to PFE Manager hogging logs when SFP-T is plugged in
Product-Group=junos		On Junos EX4600 Virtual Chassis (VC), the master RE reboot and all-members reboot lead to the PFE Manager hogging logs when SFP-T pluggable is installed in. The PFE Manager hogging logs has no functionality impact (PR 1641556).

Resolved In: junos:20.2R3-S6 junos:21.4R3-S2
PR NumberSynopsisCategory: NFX Series Platform Software
1583054[NFX250][LACP] : LACP subsystem not started automatically when dc-pfe process is restarted
Product-Group=junos		LACP subsystem not started automatically when dc-pfe process is restarted

Resolved In: 
PR NumberSynopsisCategory: ChassisD changes specific for ACX series
1717105SNMP MIB OID output showing wrong temperature value if device running under negative temperature
Product-Group=junos		On all Junos platform, devices may display wrong temperature values when executing commands. The temperature value is processing as positive integers but not negative integers, so for negative temperature is showing the wrong value. For example: User@Device> show chassis environment routing-engine Routing Engine 0 status: State Online Master Temperature -2 degrees C / 29 degrees F <...> User@Device> show snmp mib get 1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0.0 jnxOperatingTemp.9.1.0.0 = 65534

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: JUNOS kernel/ukernel changes for ACX
1713699The member interface will not be added to the AE bundle if the link-speed of the AE interface doesn't match that of the member
Product-Group=junos		On Junos ACX5048 and ACX5096 platforms, if the link-speed is configured under the aggregated-ether-options hierarchy of the Aggregated Ethernet (AE) interface and the link-speed value does not match with the member link-speed, the member interface will not be added to the AE bundle.

Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.2R1
PR NumberSynopsisCategory: OAM support on ACX
1637615Junos OS: ACX2K Series: Receipt of a high rate of specific traffic will lead to a Denial of Service (DoS) (CVE-2023-22391)
Product-Group=junos		A vulnerability in class-of-service (CoS) queue management in Juniper Networks Junos OS on the ACX2K Series devices allows an unauthenticated network-based attacker to cause a Denial of Service (DoS). Refer to https://kb.juniper.net/JSA70187 [juniper.net] for more information.

Resolved In: junos:19.4R3-S9 junos:20.2R3-S7 junos:20.3R3-S6 junos:20.3X75-D35 junos:20.3X75-D42 junos:20.4R3-S4 junos:21.1R3-S5 junos:21.2R3-S3 junos:21.3R3-S3
PR NumberSynopsisCategory: ACX Interfaces IFD, IFL, vlans, and BRCM init
1692745ACX5448 crashed and booted from secondary disk after restating chassis-control from CLI
Product-Group=junos		An ACX5448 device when subjected to multiple continuous chassis-control restarts will crash the device.

Resolved In: 
PR NumberSynopsisCategory: a20a40 specific issue
1645817Line cards fail to come online state when the device is powered on with multiple cards
Product-Group=junos		On SRX5k and MX240/MX480/MX960 platforms, when device is powered on with multiple line cards, power might not be sufficient and few line cards fail to come into online state.

Resolved In: junos:22.3R1
PR NumberSynopsisCategory: BBE interface related issues
1715410The bbe-smgd process is seen to crash if a large scale PWHT configuration is present
Product-Group=junos		On all MX platforms in a subscriber scenario, the bbe-smgd process is seen to crash immediately after a configuration change is committed and if a large scale PWHT (Pseudowire Headend Termination) configuration is present.

Resolved In: evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S2-J9 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1689904BGP LU Advertisements fail with the message "BGP label allocation failure: Need a gateway"
Product-Group=junos		On all Junos and Junos Evolved platforms BGP-LU (Border Gateway Protocol Labeled-Unicast) Advertisements fail with the message "BGP label allocation failure: Need a gateway" based on timing conditions involving route resolution and installation.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.2R1
1695062Traffic blackholing is observed when removing the BGP routes take a long time to get removed from RIB
Product-Group=junos		On Junos platforms, if a BGP (Border Gateway Protocol) peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as other work in the routing process utilize the CPU.

Resolved In: evo:21.2R3-S5-EVO evo:22.1R3-S2-EVO evo:22.2R3-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D43 junos:21.2R3-S4-J9 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R2-S1-J4 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Virtual-chassis platform/chassisd infrastructure PRs for MX
1686425Interface_check_up verification is not as expected on alisha device
Product-Group=junos		This issue is specific to MXVC only and the issue is not seen during manual execution of the test case. Issue is seen only with the test script that too rarely and hence the exact trigger of the issue is not clear.

Resolved In: 
1706268FPC offline can be seen on MX-VC during the sequential upgrade
Product-Group=junos		On Junos MX-VC (Virtual Chassis), CCL (Chassis Control Link), and CRC (Cyclic Redundancy Check) errors can be seen after FPC (Flexible PIC Concentrator) detach during the sequential OS (Operating System) upgrade of MX-VC system. The CCL and CRC errors are expected after the FPC detaches and eventually, the FPC is marked offline by the MX-VC and there is an unexpected chassisd process restart. The chassisd restarted because of the connection failure between LCC (Linecard Chassis Control) chassisd and SCC (Switch Chassis Control) chassisd which is triggered by the sequence of messages exchanged between the LCC and SCC after the FPC detach event. There will be a traffic impact as the FPC will be offline, and the system recovers to a working state by itself.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Device Configuration Daemon
1682271Node Slicing: In a rare scenario, the FPC/SLC will get stuck in the ready state after a restart
Product-Group=junos		On Junos MX platforms, in a rare scenario, FPC/SLC (Flexible PIC Concentrator/Sub Line Card) may get stuck in the ready state after restarting it and the error message of 'Device busy' will be observed in Syslog.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S2-J19 junos:21.2R3-S4 junos:21.3R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
1692404Incompatible/unsupported configuration is not getting validated correctly during ISSU/normal upgrade causing the traffic loss
Product-Group=junos		On all Junos platforms, while performing the Junos upgrade from the release before 20.4 to a higher version having an incorrect configuration may fail. This issue may lead to traffic loss or network outages.

Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: dns-proxy feature
1704216SRX | DNS-proxy will not forward additional records to the DNS client if the max-cache TTL value is set to 0
Product-Group=junos		SRX acting as DNS-proxy with "max-cache-ttl" value set to 0 will not forward additional records available in the DNS response to the client.

Resolved In: 
PR NumberSynopsisCategory: ACX platform interface issues
1715924[ACX5448]SFP-T(P/N:740-013111) cannot be recognized after detecting I2C error.
Product-Group=junos		After upgrading Junos, SFP-T(P/N:740-013111) may not be recognized on ACX5448. When this issue happens 'show chassis hardware' cannot show the SFP-T information. To restore the issue chassis rebooting is required.

Resolved In: junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Control Plane for Node Virtualization
1695510MPC11E goes offline with "fpc-slice" configured
Product-Group=junos		On MX2020 platforms with MPC11E in the Junos Node Slicing environment, when "fpc-slice" is configured results in MPC11E going offline.

Resolved In: junos:21.2R3-S2-J15 junos:21.2R3-S4 junos:21.3R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EVPN control plane issues
1692249RPD (Routing Protocol Daemon) core is observed due to remote bgp routes being flashed as active routes
Product-Group=junos		On all Junos and Junos Evolved platforms, RPD(Routing Protocol Daemon) core is observed due to remote bgp routes being flashed as active routes if the next hop is not resolved, and when "family evpn signalling no-install" knob under bgp is configured.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1712259The Anycast Gateway stretched across 2 DCs over the seamless MPLS stitching DCI does not have Anycast Gateway MAC information coming from the remote DC when VLAN and VNI ids are different
Product-Group=junos		On all Junos and Junos OS Evolved platforms, the AnyCast Gateway stretched across 2 Data Centres (DC) over the Data Centre Interconnect (DCI) using seamless Multiprotocol Label Switching (MPLS) stitching through Interconnect knob and having different VLAN and Virtual Network Identifier (VNI) ids (e.g., VLAN ID 101 <-- -> VNI 1101), then upon deactivating the Integrated Routing and Bridging (IRB) interface on all the gateways within DC, the AnyCast Gateway MAC information coming from Interconnect-Ethernet Segment Identifier (I-ESI) will not be available in the bridge mac-table and thus, the Inter VLAN/VNI routing will be impacted.

Resolved In: evo:22.1R3-S2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:21.4R3-S2-J11 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: EX4400 platform
1696596EX4400: Port status LED remains "ON" for a few seconds after removing the link connection , the cli o/p shows as down and cli led o/p also shows as off.
Product-Group=junos		Port status LED remains "ON" for a few seconds after removing the link connection

Resolved In: 
PR NumberSynopsisCategory: Sflow on qfx10k/ptx series PRs for defect & enhancement req
1715415QFX10k - sFlow Frame Length Field reporting incorrect data
Product-Group=junos		sFlow might sample traffic in QFX10K platform with a wrong Frame Length. The sampled packets will show a Frame Length of 132 bytes, regardless the real size of these packets.

Resolved In: junos:21.4R3-S2-J7
PR NumberSynopsisCategory: Interface Information Display
1611623SRX1500: Traffic fail seen on irb interface for network control forwarding class when verifying dscp classification based on single and multiple code-points
Product-Group=junos		Traffic drop might be seen on irb interface on SRX1500 for network control forwarding class when verifying dscp classification based on single and multiple code-points.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: MX Inline Jflow
1444849Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.
Product-Group=junos		Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.

Resolved In: 
1708485The Inline Flow Monitoring is not working on Junos MX-VC platforms
Product-Group=junos		In a Virtual-chassis (VC) scenario on Junos MX platforms installed with MPC7E Flexible PIC Concentrators (FPC), if the inline-jflow Sampling is enabled, the Inline Flow Monitoring will not work as data is not getting exported to the collector.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: ISIS routing protocol
1674804Segment-routing may incorrectly set a pop action for paths using a Strict SPF(1) Algorithm
Product-Group=junos		On all Junos and Junos Evolved platforms, segment-routing sets a pop action for paths using a Strict SPF(1) Algorithm incorrectly.

Resolved In: evo:21.4R2-S2-EVO evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:21.4R2-S2 junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR NumberSynopsisCategory: jdhcpd daemon
1694952auto image upgrade is not present when 3400 VC is zeroized and VC is formed
Product-Group=junos		When an EX3400 VC members are zeroized or if it powered on for the first time after halt, "set chassis auto-image-upgrade" config is getting removed during the process of VC formation. Absence of this configuration will not allow user to download configuration and images via ZTP

Resolved In: 
1713619A jdhcpd crash is observed on all Junos platforms
Product-Group=junos		On all Junos platforms, a jdhcpd crash is observed when FPC (Flexible PIC Concentrator) is restarted and the DHCP (Dynamic Host Configuration Protocol) functionality could be impacted.

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-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1688986H.323 traffic failure caused by RAS packet drops when incorrect route lookup performed
Product-Group=junos		On SRX platforms, due to incorrect route lookup performed for default routing-instance instead of ingress routing-instance results in RAS (Registration, Admission, and Status) packet drops for which H.323 traffic failure is observed.

Resolved In: junos:22.1R3-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: all logging related bugs on srx platforms
1708116Log streaming to the security director cloud fails on TLS when DNS re-query is performed
Product-Group=junos		On SRX platforms, log streaming to the security director cloud fails on TLS(Transport Layer Security) when DNS(Domain Name System) re-query is performed.

Resolved In: junos:21.2X32-D20
PR NumberSynopsisCategory: Security platform jweb support
1712454[Jweb] "address-book attach zone" is unexpectedly removed when address-book entry is added or removed by Jweb
Product-Group=junos		On SRX platform series, when address-book entry is added or removed by Jweb, "address-book attach zone" might be unexpectedly removed at configuration commit.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Kernel MX virtual-chassis PRs
1677624Bgp peers status is not as expected
Product-Group=junos		Not fixed in the Current release, the issue was recreated only with IXIA connection. Arp response is not received in the DUT port to store the destination MAC address. unable to determine if the issue is with the MX port or medium or IXIA port.

Resolved In: 
PR NumberSynopsisCategory: Layer 2 VPN related issues
1654516Routes flapping when configuration changes are applied to custom routing instance
Product-Group=junos		Routes flapping when configuration changes are applied to a custom routing instance.

Resolved In: evo:22.2R3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.1R3-S5 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1703200License will be lost due to multiple FPC reboot or switchover on QFX/MX VC scenario
Product-Group=junos		On all Junos QFX/MX platforms with VC (Virtual Chassis) setup, the license for the existing master could be deleted when the master FPC (Flexible PIC Concentrator) is rebooted and services will be impacted if the reboot or switchover happens again.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1693301MACSec session will not come up on the new fallback key during the primary key transition
Product-Group=junos		On all Junos and Evolved platforms, during the primary key transition on the MACSec session, when a new fallback key is updated on the MACSec peers the session will not come up due to the primary key remaining live on the same interface. When this happens, there will be a traffic drop on the MACSec interface. This is a rare issue and only occurs when a certain sequence of steps is performed.

Resolved In: evo:22.2R3-EVO junos:22.2R3
PR NumberSynopsisCategory: Interface related ISSU PRs on Mx-series
1689199The logical interface policer is not working as expected when applied to filter input-list/output-list
Product-Group=junos		The logical interface policer does not work when configured using filter input-list/output-list.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: IPv6/ND/ICMPv6 issues
1703940RE will crash when static route duplicates with an interface IP address
Product-Group=junos		On all Junos platforms, RE (Routing-Engine) will crash when a static route is added that duplicates with an interface IP address. RE crash will lead complete traffic loss.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1588704The dcpfe might crash on QFX5k devices
Product-Group=junos		On QFX5000 line of switches, the Flexible PIC Concentrator (FPC) or dcpfe process might go into a very uncommon state when multiple Broadcom Counter (bcmCNTR) threads are running or spawned in FPC. This state causes the dcpfe process to crash or the FPC to reboot. The purpose of bcmCNTR is to poll statistics from hardware.

Resolved In: junos:18.4R2-S9 junos:20.3X75-D30 junos:20.3X75-D40 junos:22.1R1 junos:22.2R1 junos:22.2R3
1666260Traffic loss might be seen when l2circuit configurations are deactivated and activated on QFX5110
Product-Group=junos		On QFX5110 platforms with more than one l2circuit configured, deactivating and activating the l2circuit configurations successively might cause traffic drop on one or more l2circuits.

Resolved In: 
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1688323Traffic loss is observed when there is a change in EVPN-VXLAN with type 5 tunnel
Product-Group=junos		On Junos QFX5K series platforms, configuration-change/protocol flapping/port flapping in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) with Type 5 tunnel cause traffic loss (Configuration change related to the underlay network).

Resolved In: 
1711783LACP bundle flaps will be observed for tagged packets getting proceeded to the control plane
Product-Group=junos		On QFX5K platforms, LACP (Link Aggregation Control Protocol) flaps will be seen, when LACP BPDUs (Bridge Protocol Data Units) are received, the VLAN tag is not processed causing the system-id mismatch.

Resolved In: 
PR NumberSynopsisCategory: QFX10008/16 QFX10002 Ultimat/Elit platform related issues -
1676740, The traffic doesn't re-route quickly causing traffic blackholing
Product-Group=junos		On all VMHOST based platforms, traffic blackholing happens because the traffic doesn't re-route quickly as chassisd doesn't recognize an FPC failure from a BAD_VOLTAGE notification.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO junos:20.3X75-D50 junos:20.4R3-S5 junos:21.2R3-S4 junos:21.4R2-S2 junos:21.4R3-S2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1660532The port LEDs do not light up when 40G/100G physical interfaces are up.
Product-Group=junos		The port LEDs do not light up when 40G/100G physical interfaces are up. This is a display issue. There is no service impact when this issue occurs.

Resolved In: junos:20.3X75-D43 junos:21.1R3-S4 junos:21.2R3-S4 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1696119Traffic drop is observed for the VCP ports when there is traffic congestion in the egress queues
Product-Group=junos		On QFX5110 with Virtual Chassis configured, if any of the egress queues 3 or 4 is congested it causes buffer stuck error messages and traffic drop on the VCP (Virtual Chassis port) ports.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1652387The rpd process might crash with back-to-back rpd restarts
Product-Group=junos		On all Junos and Junos Evolved platforms, the rpd process might crash if the rpd process restarts back-to-back before the rpd process comes up.

Resolved In: evo:21.4R3-S3-EVO evo:22.3R1-EVO junos:20.3X75-D42 junos:20.3X75-D50 junos:21.2R3-S3 junos:22.3R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1713392PathErr with RoutingProblem error code generated unexpectedly during dual failure local repair
Product-Group=junos		When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: All Asgard Platform Related Issues
1335526The ppmd process might crash after an upgrade on SRX platforms
Product-Group=junos		On SRX platforms with Bidirectional Forwarding Detection (BFD) enabled for multiple protocols (such as OSPF, ISIS, BGP, PIM), the ppmd process might crash after an upgrade.

Resolved In: junos:12.3X48-D66 junos:12.3X48-D70 junos:15.1X49-D126 junos:15.1X49-D140 junos:21.1R3 junos:21.2R3 junos:21.3R3-S4 junos:21.4R1 junos:21.4R2 junos:22.1R1
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1705461MX204/MX10003/EX9251 : Interfaces gigether-options "speed 1g" should be configured with "auto-negotiation" option when using 1GE SFP optics, otherwise we see traffic blackhole in case of 1 Rx cable cut
Product-Group=junos		On 1G speed ethernet, auto-negotiation is responsible for exchaning Remote-fault and additional capability options (Pause etc) between link partners. So any link failure (Rx LOS) will not be reported to the peer link via Remote-fault if it configures without auto-negotiation / speed 1g. In such situation, the link on local side goes down, but the link on far end keeps Up, which will cause traffic blackhole. Configuring auto-negotiation explicitly under gigether-options is recommended to avoid traffic blackhole.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.2R1
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1620773SRX4600 - Packet drop or srxpfe coredump might be observed
Product-Group=junosvae		Packet drop or srxpfe coredump might be observed on SRX 4600 during periods of high traffic

Resolved In: junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1700321VLAN tags are imposed incorrectly when traffic is routed over IRB going out of the access interface
Product-Group=junos		On MX platforms, traffic egressing on the IRB (Integrated Routing and Bridging) interface with the underlying L2 (layer2) access port has VLAN tags imposed incorrectly.

Resolved In: evo:23.1R1-EVO junos:21.2R3-S4 junos:23.1R1
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1714656Incorrect 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.

Resolved In: evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1638847The 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.

Resolved In: evo:23.2R1-EVO junos:23.2R1
PR NumberSynopsisCategory: Issues related to NETCONF
1709056Unable to update Junos using NetConf/Junos script
Product-Group=junos		On all Junos and Juos OS Evolved platforms, if rpc get-configuration is invoked before rpc request-package-add in the same session of the netconf or junos script, rpc request-package-add will not work.

Resolved In: evo:23.3R1-EVO
PR NumberSynopsisCategory: MX10K linecard
1688651JUNOS_REG:MX10008:Carrier transition count is more than expected at DUT(mx10008) after flapping the interface at peer non-DUT end.
Product-Group=junos		When laser off and on happens on the remote end, within an interval of less than 500 ms, the local interface undergoes additional flap, before the link comes up. There is no impact of the additional flap, as the link does come up eventually.

Resolved In: 
PR NumberSynopsisCategory: usf nat related issues
1718840The PPTP connection itself won't work when trying to establish PPTP connection along with DSLITE
Product-Group=junos		On Junos MX and SRX platforms with SPC3 cards, Point-to-Point Tunneling Protocol (PPTP) connection between client and server always failed along with Dual-Stack Lite (DSLITE) scenario. PPTP failure occurred due to Generic Routing Encapsulation tunnel (GRE) wrong call-id swapping that taken place by Address Family Transition Router (AFTR). Traffic will not pass through the tunnel at all as the tunnel does not establish.

Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1