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

Junos Software Service Release version 21.1R3-S5 is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

Solution

Junos Software service Release version 21.1R3-S5 is now available.

21.1R3-S5 - List of Fixed issues 

PR NumberSynopsisCategory: EX4300 PFE
1697685Gratuitous ARP reply will not update the ARP cache
Product-Group=junos
On EX4300 platforms, the ARP (Address Resolution Protocol) cache will not be updated upon receiving the Gratuitous ARP reply even with "gratuitous-arp-reply" configured.
PR NumberSynopsisCategory: EX4300 Platform
1678506The interface on the device will go down when one or more interfaces are connected to the Advantech3260 device at another end
Product-Group=junosvae
On EX4300 platforms with version 19.1R3 and above, the interface on the device will go down when the device is connected to the Advantech3260 device at the other end. It will have a traffic impact.
1680225On EX4300-Virtual Chassis (VC) platforms, the pfex process might crash when PIC 2 is detached
Product-Group=junos
On EX4300-Virtual Chassis (VC) platforms, Packet Forwarding Engine process (pfex) crash will be seen when Physical Interface Card 2(PIC 2) is detached then Physical Interface(IFD) is getting deleted before logical interface (IFL)deletion.
PR NumberSynopsisCategory: EX4300 Filters implementation
1699777TCAM space might be exhausted when learning DHCP snooping entries on a trusted port
Product-Group=junos
On EX, QFX5k, and MX platforms having persistent binding for DHCP (Dynamic Host Configuration Protocol) snooping configured might cause TCAM (Ternary Content Addressable Memory) space exhaustion for DHCP snooping learning on the trusted port after the device reboot.
PR NumberSynopsisCategory: EX4300 Layer 2 implementation
1684072The l2cpd process crash may be observed when disabling RSTP on an interface
Product-Group=junos
On all Junos and Junos Evolved platforms, the l2cpd process may crash and generates the core when disabling RSTP (Rapid Spanning Tree Protocol) on an interface.
PR NumberSynopsisCategory: EX2300/3400 PFE
1695771Traffic loss is seen when a MAC moves from dot1x port to non-dot1x port
Product-Group=junos
On all Junos and Junos OS Evolved platforms is having dot1x enabled interface. When two or more MAC addresses are learnt on a dot1x port, and if one of them is shifted to a non-dot1x port, the MAC address that was moved is still seen as a MAC-based VLAN entry on the Layer2 Address Learning Manager (l2alm). This could lead to network traffic being lost.
PR NumberSynopsisCategory: EX2300/3400 platform
1680408On Ex2300 and EX3400, "set system ports console log-out-on-disconnect" does not allow user to log in via console.
Product-Group=junos
On certain units, with "set system ports console log-out-on-disconnect", when you login to the device via a console, the user will be kicked out to the login prompt and be asked to login again.
PR 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
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.
PR NumberSynopsisCategory: a20a40 specific issue
1698797Fabric monitoring suspension and control link failure may cause HA cluster outage
Product-Group=junos
A series of event happens to trigger this issue: I. HW failure on Node0 which causes a major chassis alarm to suspend fabric link monitoring II. A Critical HW failure happening again on Node0 which also causes control link down. III. Due to above, Node1 is neither able to see Node0 going into disabled state, not fab link down as which was suspended earlier in step I.
PR NumberSynopsisCategory: australia related kernel issue
1714002vmcores can be seen on SRX5k platforms when the fxp0 interface is configured under management-instance
Product-Group=junos
On Junos SRX5K series platforms, when the 'set system management-instance' command is committed on the secondary node, continuous VMcores are observed on the secondary node leading to the kernel crash. The secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until management-instance knob is removed using "delete system management-instance".
PR NumberSynopsisCategory: BBE interface related issues
1687138The PIMv6 is not getting enabled for L2TP subscribers
Product-Group=junos
On MX platforms, the Protocol-Independent Multicast version 6 (PIMv6) might not get enabled when it is configured over the Layer 2 Tunneling Protocol (L2TP) Subscriber Interface using the Dynamic-profiles.
PR NumberSynopsisCategory: Border Gateway Protocol
1648471An RPD crash was observed on all Junos platforms
Product-Group=junos
An rpd crash might be observed on all Junos platforms once the RPKI configuration is activated along with BGP SRv6 at the same time.
1660401RPKI route validation logic is not RFC6907 compliant
Product-Group=junos
Junos OS and Junos OS Evolved have been updated to make RPKI origin-validation RFC6907-compliant.
PR NumberSynopsisCategory: Virtual-chassis platform/chassisd infrastructure PRs for MX
1713502MPC7E firmware upgrade gives tftp timeout error in MXVC scenario
Product-Group=junos
On MX-VC platforms, the MPC7E firmware upgrade cannot be completed due to the TFTP (Trivial File Transfer Protocol) timeout error due to which the firmware image can't be put into FPC and the upgrade will not get succeed. The TFTP is a file transfer protocol that is used to copy or redirect files to or from a remote TFTP server.
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.
1695663The Unicast traffic is dropped on QFX5100/EX46xx-VC platforms
Product-Group=junosvae
On QFX5100/EX46xx Junos platforms configured with Virtual Chassis(VC), if a master member is unplugged or forced to power off, the unicast traffic is dropped due to mac-persistence-timer expiry there is a difference in mac addresses between logical aggregated parent interface and member aggregated ethernet(ae) interface.
PR NumberSynopsisCategory: Control Plane for Node Virtualization
1685453PICs on the GNF failed to come online after the chassisd restart
Product-Group=junos
On MX platforms supporting node-slicing (MX480, MX960, MX2010, MX2020 & MX2008) have an issue that when GNF (Guest Network Function) chassisd restarts, the FPC doesn't restart as expected which causes the PIC (Physical Interface Card) to be offline.
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
1602272Junos OS and Junos OS Evolved: python-cryptography 3.2 is vulnerable to Bleichenbacher timing attacks in the RSA decryption API via timed processing of valid PKCS#1 v1.5 ciphertext (CVE-2020-25659)
Product-Group=junos
A vulnerability in the python cryptographic library as used in Juniper Networks Junos OS and Junos OS Evolved allows an attacker to perform timing oracle attacks against RSA decryption. Please refer to https://kb.juniper.net/JSA11245 [juniper.net] for more information.
PR NumberSynopsisCategory: EVO linux defects & enhancement requests
1602717Ephemeral/dynamic port range has been modified in EVO platforms
Product-Group=junos
On all EVO platforms, near-end port is not within RFC/IANA standards as ephemeral/dynamic port range has been modified.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1662954In EVPN-MPLS Mutihoming scenario DF election will get stuck in the Preference based state
Product-Group=junos
On all Junos and Junos Evolved platforms supporting preference-based DF (Designated Forwarder) election in EVPN-MPLS Multihoming scenario, the DF election will be stuck in the Preference based state if there will be a change in the df-election on the fly.
1702016ARP/ND doesn't resolve when extended-vlan-list is configured for the specific VLAN
Product-Group=junos
On all Junos & Junos Evolved platforms, ARP(Address resolution protocol)/ND(Neighbour discovery) doesn't resolve when extended-vlan-list is configured for the specific VLAN(virtual local area network).
PR NumberSynopsisCategory: Control plane EVPN multicast
1670435EVPN multicast traffic may get impacted because of routes getting stuck in the kernel routing table (krt) queue
Product-Group=junos
On all Junos and Junos Evolved platforms with Ethernet Virtual Private Network(EVPN) enabled, in the presence of certain triggers like rpd restart, rollback of configuration etc., EVPN multicast routes might get stuck in the kernel routing table (krt) queue due to which the corresponding routes in the forwarding table may point to 'fictitious' next hops, resulting in traffic disruption.
PR NumberSynopsisCategory: EX Entry Level Access VC platform
1704457The PXE BIOS recovery fails on EX9204/9208/9214 VC setup
Product-Group=junos
On EX9204/9208/9214 platforms configured in a Virtual Chassis(VC) setup, if the SSD(solid-state drive) local disk is erased or there is a hardware failure for EX9200-40XS FPC, the EX9200-40XS recovery will fail if performed through the PXE(Preboot Execution Environment) and stuck in a boot loop.
PR NumberSynopsisCategory: Express PFE MPLS Features
1712076FPC memory leak will cause FPC crash
Product-Group=junos
On PTX and QFX10K platforms, enabling collection of LSP (label-switched path) statistics for telemetry data will cause FPC (Flexible Physical Interface Cards (PIC) Concentrators) memory leak resulting in FPC crash.
PR NumberSynopsisCategory: GMIC2 platform driver issues
1693211MACsec on logical interfaces fails after port flap
Product-Group=junos
MACsec configured on logical interfaces (IFL) would fail to restore after a flap of the parent physical interface. This will lead to Cyclic Redundancy Check (CRC) errors and failure to pass traffic.
PR NumberSynopsisCategory: idp flow creation, deletion, notification, session mgr intfce
1705491Network outage caused during change in IDP policy
Product-Group=junos
Junos SRX platforms experience traffic outage during change in IDP (Intrusion Detection and Prevention) policy.
PR NumberSynopsisCategory: MX Inline Jflow
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.
PR NumberSynopsisCategory: Fast Ethernet interfaces
1684142Traffic is getting impacted as interface hold-time is not working with wan-phy framing
Product-Group=junos
On all Junos MX series platforms, when hold timer and wan-phy are configured, traffic gets impacted when the link goes down on an interface within the configured hold timer.
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1610540QFX5200 mib OID ifOutDiscards misbehaving and returning value 0 which is not expected
Product-Group=junos
ifOutDiscards(Output Error Drops) returning value 0 for AE interface intermittently. Issue is observed when we receive both SYNC and ASYNC request at the same time for AE member link interface. SYNC request from mib2d(since ASYNC is not supported by QFX for AE) and ASYNC request is from sflowd. Before post-processing completes for the pending SYNC request if ASYNC request is created, ASYNC q_counters is taken for stats calculation and it results in 0.
1649958The user-defined speed does not take effect on the AE interface in certain scenarios on Junos platforms
Product-Group=junos
On Junos platforms supporting GRES (Graceful Routing Engine Switchover), the bandwidth flag on the backup RE (Routing Engine) for the AE interfaces is set unconditionally, hence the bandwidth is struck at a value despite not being set by the user statically. When GRES is performed followed by link delete/add for the AE interface, the interface would get stuck with the bandwidth and gets synced with the backup RE. There can be seen partial service impact in the case of the RSVP (Resource Reservation Protocol) and the restoration to recover from this issue is to configure bandwidth manually and then remove the configuration.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1685406The protocol MTU for the IRB interface is not rolled back when the MTU of the IRB or IFD interfaces is modified or deleted
Product-Group=junos
On all Junos platforms, the maximum transmission unit (MTU) on the Integrated Routing and Bridging (IRB) interface is not getting reset when the MTU configuration on IRB or IFD is removed. When MTU configuration is removed from the IRB interface, the internal data structure for the MTU configuration is not getting reset which might affect traffic and it is a rare case.
PR NumberSynopsisCategory: jdhcpd daemon
1698798A dcd process crash is observed continuously when the dhcp-service is restarted
Product-Group=junos
On MX platforms that support Broadband Edge (BBE) functionality, the dcd crash continuously occurs when the subscribers are logged in using the DHCP dynamic profile and dhcp-service is restarted having the configuration like "set chassis network-services enhanced-ip" enabled.
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1653902Junos OS: SRX Series and MX Series: Memory leak due to receipt of specially crafted SIP calls (CVE-2023-22394)
Product-Group=junos
An Improper Handling of Unexpected Data Type vulnerability in the handling of SIP calls in Juniper Networks Junos OS on SRX Series and MX Series platforms allows an attacker to cause a memory leak leading to Denial of Services (DoS). Please refer to https://kb.juniper.net/JSA70190 [juniper.net] for more information.
PR NumberSynopsisCategory: SRX Firewall Authentication
1685116The user authentication page is not rendering on the client browser
Product-Group=junos
On all Junos SRX platforms due to cross-origin restriction access, the domain page does not load. The issue happened due to a firewall authentication failure.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1678772New secondary node to go into a disabled state after ISSU and failover RG0 because of fabric link failure
Product-Group=junos
On SRX5K platforms with SPC3 card, the primary node will lose the backup node and fabric link failure is observed resulting in the new secondary node going into a disabled state after ISSU (In-Service Software Upgrade) and failover RG0 (redundancy group) in a chassis cluster environment.
1686648Policy configured with condition route-active-on import is not working properly after RG0 failover
Product-Group=junos
In a specific scenario, condition route-active-on import is not working properly after RG0 failover.
1691071Chassis cluster IP monitoring on the secondary node failed after the system reboot on the SRX platforms
Product-Group=junos
On SRX platforms, IP monitoring on the secondary node failed when a Reth (redundant Ethernet) interface consists of two or more than two interfaces on each node. Reth member interface which has a higher port number cannot receive ICMP (Internet Control Message Protocol) packet used for IP monitoring, which will then put the system in an error state.
PR NumberSynopsisCategory: all logging related bugs on srx platforms
1631149SRX5600/5800 - SNMP mib queries may result in occasional response timeouts
Product-Group=junos
SRX5600/5800 - SNMP MIB queries for jnxJsSPUMonitoringMIB objects (1.3.6.1.4.1.2636.3.39.1.12.1.x) may result in occasional response timeouts
PR NumberSynopsisCategory: Firewall Network Address Translation
1655197Syslog mode stream performance limitation for pba-interim-logging
Product-Group=junos
Syslog mode stream performance limitation for pba-interim-logging during syslog messages bursts.
PR NumberSynopsisCategory: Firewall Policy
1698508Security policies go out of sync during ISSU
Product-Group=junos
On all Junos platforms, policies go out of sync between RE (Routing Engine) and PFE (Packet Forwarding Engine) after performing ISSU (In-service software upgrade) leading to the wrong policy lookup.
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.
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.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1684842Licenses on the device might become invalid when the device is upgraded from a legacy licensing-based release to an Agile licensing-based release
Product-Group=junos
This issue is applicable to all Junos. When a device with a valid license is upgraded to a release and this upgrade changes the licensing from Legacy to Agile then the installed license might show as invalid.
PR NumberSynopsisCategory: SW PRs for MPC10E Chassisd
1664448The command "show chassis fpc" shows inaccurate information about heap memory
Product-Group=junos
The command "show chassis fpc" shows inaccurate information about heap memory in output.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1642584MPC10E: Quick 100G link-flaps has still some race conditions which can cause MQSS stream drain failures and xqss_sched_flush_queue failures
Product-Group=junos
On MPC10E cards upon many very quick link down and up events in msec range might not always able to drain all traffic in the queue. This causes lost of traffic going through the interface. Traffic volume and class-of-service configuration does influence the exposure. See also PR1638410.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1694648The rpd crash will be observed during the MPLS label block allocation
Product-Group=junos
On all Junos and Junos Evolved platforms in the Multiprotocol Label Switching (MPLS) scenario, the rpd crash will happen in rare conditions during MPLS label block allocation.
1701800Memory leak issue in TED
Product-Group=junos
On all Junos and Junos Evolved platforms, a memory leak is observed in TED (Traffic Engineering Database) when the inet tables is not cleaned up after routing instance deactivation.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1642287Kernel crash is seen on the device if the device is continuously power cycled
Product-Group=junos
This issue is applicable to EX3400/EX2300/EX4100. There is a possibility of kernel crash when the system will be in the process of coming up after reboot (and observed only with multiple iterations of continuous reboot cycles). This is observed only during the init sequence of the management driver and impact is limited to increased system boot time.
1704032VM process crashes if a file is shared between the host operating system and the guest operating system using virtFS
Product-Group=junos
On Virtual Machines (VM) based platforms running Junos images, files are not shared between the host operating system and guest operating system via Virtual Filesystem (virtFS). When this issue happens, the device will be restarted.
PR NumberSynopsisCategory: Kernel MPLS / Tag / P2MP Infrastructure
1702220LDP flaps will be observed having LT interface with VLAN and LDP running between the logical-system instance and global instance
Product-Group=junos
On Junos platforms, when the LT (Logical Tunnel) interface with VLAN and LDP (Label Distribution Protocol) is configured between the logical-system instance and global instance LDP flaps are observed.
PR NumberSynopsisCategory: TCP/UDP transport layer
1685113BGP session flap with error BGP_IO_ERROR_CLOSE_SESSION
Product-Group=junos
On all Junos platforms, a random BGP (Border Gateway Protocol) session flaps will be observed immediately after committing certain configuration changes with the error "BGP_IO_ERROR_CLOSE_SESSION" along with a TCP connection reset. This issue is generic to any TCP (Transmission Control Protocol) connection that has MD5 (Message-Digest Algorithm) enabled on it, eg targeted LDP Following error is also reported: rpd: bgp_pp_recv: rejecting connection from a.b.c.d (Internal AS xyz), peer in state Established rpd: bgp_pp_recv:5159: NOTIFICATION sent to a.b.c.d+64150 (proto): code 6 (Cease) subcode 5 (Connection Rejected)
PR NumberSynopsisCategory: OSPF routing protocol
1700966OSPF stuck in InitStrictBFD state for the neighbor which doesn't send LLS header
Product-Group=junos
When Strict BFD (Bidirectional Forwarding Detection) for OSPF (Open Shortest Path First) configured on all Junos OS and Junos OS Evolved platforms, and one or more OSPF neighbors don't support Link-Local Signaling ("LLS", RFC5613), the adjacency with these neighbor(s) might stuck in InitStrictBFD state upon adjacency initialization. Neighbor doesn't support LLS, hence it doesn't attach the LLS header, which is a pre-requisite for Strict BFD.
1705975OSPF routes are not getting installed after the interface is flapped
Product-Group=junos
On all Junos and Junos Evolved platforms, the OSPF (Open Shortest Path First) routes are not getting installed when the interface is flapped multiple times. A deadlock is created when the OSPF routers wait for an LSA (Link State Advertisement) with a P2P (Point-to-Point) link to be advertised from its neighbouring router to add it to its router LSA and at the same time the neighbouring router also waits for an LSA with a P2P link to be advertised to add it to its router LSA. Both the OSPF routers advertise their router LSA without a P2P link and as a result, routes are not getting installed.
PR NumberSynopsisCategory: QFX access control list
1695820On QFX5110-VC-VCF platforms, traffic impact is seen when the firewall filter with DSCP action is enabled
Product-Group=junos
On QFX5100-VC-VCF (Virtual-Chassis Fabric) when the firewall filter with action DSCP (Differentiated Services Code Point) is configured and is applied to any interface, the commit check gives a warning on FPC2 (Flexible PIC Concentrators) if the master has member id 0 and traffic drop can be seen.
1710776The message "fpc0 list_get_head, list has bad magic (0x0)" maybe output after the commit operation is complete
Product-Group=junos
When a VACL filter is added or deleted, the message "fpc0 list_get_head, list has bad magic (0x0)" maybe output.
PR NumberSynopsisCategory: QFX L2 PFE
1694076PFE crash is seen on all Junos QFX5K and EX46xx platforms with L2PT configuration
Product-Group=junos
PFE (Packet Forwarding Engine) crashes on all Junos QFX5K and EX46xx platforms when L2PT (Layer 2 Protocol Tunneling) is configured on the interface having flexible-vlan-tagging with encapsulation extended-vlan-bridge. It causes a traffic impact.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1695847Traffic forwarding fails when deleting all L2 related configurations
Product-Group=junos
On QFX and EX series platforms, traffic loss will be observed for deleting all Layer2 related configurations when both L2 and Layer3 configurations are present.
PR NumberSynopsisCategory: QFX MPLS PFE
1687257QFX5120 will drop ingress traffic on an l2circuit configured interface on continuous flapping
Product-Group=junosvae
On QFX5120 platforms, when a flap occurs in a Layer 2 Circuit (L2Circuit) configured interface, l2circuit configuration programming fails on the interface and leads to a traffic drop.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1651827The MAC address from local CE may not be learned due to the VLAN programming issue
Product-Group=junos
On QFX5k series platforms, MAC address from local CE (customer edge) might not get learned when EVPN (Ethernet VPN)/VxLAN (Virtual Extensible LAN) is configured. The traffic drop is expected as MAC learning may not happen.
PR NumberSynopsisCategory: QFX VCCP
1669702FPC1 is getting disconnected after ISSU and before switchover while checking ISSU status
Product-Group=junosvae
On QFX5120-48T platforms with VC setup, FPC1 is getting disconnected after In-Service-Software-Upgrade(ISSU)/Nonstop Software Upgrade (NSSU) and before switchover while checking ISSU status.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Interface
1657534FEC link is down after disabling/enabling interface
Product-Group=junos
On the QFX5200-32C-32Q platform, on disabling and enabling interfaces, the Fast Ethernet channel (FEC) might mismatch. It impacts service as the FEC link might not come up.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1710855The FPC will be offline after upgrading the system
Product-Group=junosvae
On the Junos QFX5100 and QFX5120 platforms, after upgrading the system the PFE (Packet forwarding Engine) will crash continuously and Flexible PIC Concentrators (FPC) will remain down.
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover, 
1701146The 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 NumberSynopsisCategory: Resource Reservation Protocol
1593959ISIS BFD sessions may take a long time to recover when the interface flaps
Product-Group=junos
When RSVP link-protection bypass LSPs active after the primary link goes down and comes back up. The BFD session over the interface stays down until all LSPs using the bypass LSPs come back up. This happens because RSVP installs a /32 route pointing to the bypass tunnel which is required to signal backup LSPs. This route is removed when all LSPs stop using bypass after the link comes back up. This is day 1 RSVP behavior.
PR NumberSynopsisCategory: Cover Logical System Infrastrcuture Development
1694449The process srxpfd/ flowd will crash on SRX devices
Product-Group=junos
On all SRX platforms (except branch SRX series) configured with chassis cluster redundancy group, when numerous logical interfaces or IFLs (> 1K) are deleted and traffic is running for those IFLs, or if the RG failover then the process srxpfed/ flowd will crash.
PR NumberSynopsisCategory: SRX branch platforms
1646943No alarm under booting from backup partition
Product-Group=junos
When SRX device boots up from backup partition, the alert message is not notified in "show system alarm" from junos 19.4R2.
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1701183Traffic loss is seen due to interface flap when changing speed from 10G and 1G
Product-Group=junos
On Junos MX204/MX10003, traffic loss is seen on 4x10G Channelized interfaces when the speed is changed from 10G to 1G on one lane which causes the other 3 lanes to flap and stay down.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1712727Continuous vmcores observed on the secondary node when committing set system management-instance command
Product-Group=junos
On Junos SRX4600 device, when the "set system management-instance" command is synced to the secondary node, continuous VMcores are observed on primary and secondary nodes. The secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until management-instance knob is removed using "delete system management-instance"
PR NumberSynopsisCategory: ZT/YT pfe qos software issues
1704129Traffic is blocked on a queue when enhanced priority mode is configured
Product-Group=junos
On MPC1-9, JNP10K-LC2101, JNP10003-LC2103, JNP10K-LC480 line cards, with scheduler map configuration change in enhanced priority mode, traffic is blocked on a queue.
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1706446No network reachability when enabling the routing service for PPPoE subscriber over AE
Product-Group=junos
On all Junos platforms configured with subscriber management, when the PPPoE (Point-to-Point Protocol over Ethernet) subscriber is configured on the AE (Aggregated Ethernet) interface the subscriber will not have network access and the traffic gets impacted.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1701147FPC restart and core dump generated in MPLS scaled scenario with "always-mark-connection-protection-tlv" configured
Product-Group=junos
FPC restart and core dump generated in MPLS scaled scenario with "always-mark-connection-protection-tlv" configured.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1699245The mgd process might crash during commit synchronize
Product-Group=junos
On all Junos and Junos Evolved platforms with dual Routing Engines, during commit script synchronize, the backup Routing Engine mgd get process crashes once the memory leak reaches 65K. When this happens, commit configurations from the primary Routing Engine fail.
PR NumberSynopsisCategory: PTX/QFX100002/8/16 interface software
1712007The interface does not come up or keeps flapping
Product-Group=junos
On Junos PTX10008/PTX100016 devices with LC1101/LC1102 line cards, any event that causes an interface state change can lead to interface flapping or the interface may not come back at all. This leads to traffic impact on that interface.
PR NumberSynopsisCategory: For GPRS security features on highend SRX series
1704472GTPv2 Message Filtering is not working
Product-Group=junos
GTPv2 Message Filtering not working - resolved
PR NumberSynopsisCategory: Xellent Platform issues
1709817Ports with QSA adapter are down
Product-Group=junos
On Junos PTX1000 and PTX10002-60C/QFX10002-60C platforms, ports which use the QSA (QSFP-to-SFP Adapter) may not come up when running software version containing the fix for PR 1620527.

 


 

21.1R3-S5 - List of Known issues 

PR NumberSynopsisCategory: EX2300/3400 platform
1704481EX2300 System may Reboot due to Console Port Noise under Rare Circumstances.
Product-Group=junos
EX2300 may hang and reboot due to the Console Port Noise under Rare Circumstances

Resolved In: 
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
1700133One of the Virtual Chassis members on EX4600-VC might be disconnected during VC initialization
Product-Group=junos
On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.

Resolved In: junos:20.2R3-S7
PR 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:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.2R1
PR NumberSynopsisCategory: the SMGD redundancy plugin in SMGD
1718342DHCP ALQ M:N Subscriber Redundancy does not delete-binding-on-renegotiation on backup router.
Product-Group=junos
DHCP ALQ M:N Subscriber Redundancy does not delete-binding-on-renegotiation on backup router.

Resolved In: 
PR NumberSynopsisCategory: Border Gateway Protocol
1679646The AGGREGATOR attribute will not be set correctly when the independent-domain is configured
Product-Group=junos
On all Junos and Junos OS Evolved platforms, in BGP(Border Gateway Protocol) deployments with the "independent-domain" and aggregate routes configured under routing-instance, the AGGREGATOR attribute encapsulated within the ATTR_SET will not be populated correctly. This can result in unintended behavior or service impact because the BGP neighbors receiving this update may discard it as it is not RFC complaint.

Resolved In: evo:21.2R3-S4-EVO evo:21.3R3-S3-EVO evo:21.4R3-S3-EVO evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1676008FPC stuck in present state with log " graceful offline in progress, returning false" flooding
Product-Group=junos
In an over-temperature situation, there will be a 10s timer before the device brings the FPC down. However in some situation due to high temperature, an FPC offline action will be triggered before the 10s timer expires. Then the FPC will stuck in the Present/Announce offline state. Cli offline/online or physical reseat will not be able to recover the issue.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:19.2R3-S5-J2 junos:20.2R3-S3-J9 junos:20.2R3-S5-J5 junos:20.4R3-S5 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Device Configuration Daemon
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:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: EVPN control plane issues
1647734The DF and BDF both may be Up/Forwarding in EVPN Multihoming single-active scenarios
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when EVPN-VXLAN or EVPN-MPLS Multihoming single-active mode through Ethernet Segment Identifier (ESI) is configured and the knob "no-core-isolation" is enabled, then the Circuit Cross-Connect (CCC) might be Up/Forwarding for both Designated Forwarder (DF) and Backup Designated Forwarder (BDF).

Resolved In: evo:21.3R3-EVO evo:21.4R2-EVO evo:21.4R3-EVO evo:22.1R2-EVO evo:22.2R1-EVO evo:22.3R1-EVO junos:21.3R3 junos:21.4R2 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.3R1
PR NumberSynopsisCategory: Express ASIC platform
1683562On PTX5000 platforms when a command is issued to power off an FPC, it gets stuck in the 'Announce Offline' state
Product-Group=junos
When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot ) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to.

Resolved In: junos:19.2R3-S5-J2 junos:20.4R3-S2-J17 junos:20.4R3-S5-J3 junos:20.4R3-S6 junos:21.4R3-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1626562A major alarm DPDK (data plane development kit) Tx stuck issue of SRX4100/4200
Product-Group=junosvae
On the SRX4100 and SRX4200 platforms, it can detect DPDK (data plane development kit) Tx stuck issue and trigger a major chassis alarm goes which might trigger RG1 failover to the healthy node. A DPDK reset will be triggered only to the stuck port and if the reset resolves the tx stuck issue, the major chassis alarm will go off.

Resolved In: junos:19.4R3-S8 junos:19.4R3-S9 junos:20.2R3-S7 junos:20.4R3-S4 junos:21.2R3-S1 junos:21.2R3-S3 junos:21.4R3-S3 junos:22.2R1 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1671135RE reboot can be seen when PPPoE subscribers login
Product-Group=junos
On all Junos platforms supporting PPPoE (Point-to-Point Protocol over Ethernet) the RE (Routing Engine) can reboot with a 'vmcore' generated during the PPPoE subscriber login. This issue can be triggered when the system has demux (demultiplexing) interface configuration and static VXLAN (Virtual Extensible Local Area Network) is configured at BD (Bridge-Domain). There will be a traffic impact because of the RE reboot but the system reverts to a functioning state without manual intervention.

Resolved In: evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:20.4R3-S7 junos:21.4R3 junos:22.1R2 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
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: Layer 2 Control Module
1717267On QFX10K Incorrect root ID or bridge ID seen after adding new VLANs on a Root Bridge.
Product-Group=junos
Whenever a new vlan is added "in between" previously configured vlans, existing context id which already assigned to existing vlan context, will be assigned for that new vlan. Due to this we might see incorrect system ID or bridge ID and this may create an issue.

Resolved In: evo:21.2R3-S5-EVO evo:21.3R3-S4-EVO 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:20.4R3-S7 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1545175Intermittent license-check.core observed
Product-Group=junos
Intermittent license-check.core observed during the device initialization. License daemon will restart and start providing the required support. There is no service impact.

Resolved In: 
1658913Valid software licenses might not be in sync between members in the Virtual chassis.
Product-Group=junos
Software licenses will now be synced to all members of Virtual chassis. - Warnings and alarm to be seen only on global master member in VC. - show system license. command will be executed only on global master member. - Issue is specific to all MX VC setup for all Junos. For all other members it will display the following message: root@> show system license error: This command can only be used on the master routing engine.

Resolved In: evo:21.2R3-S1-EVO evo:21.4R3-EVO evo:22.1R2-EVO evo:22.1R3-EVO evo:22.2R1-EVO evo:22.2R2-EVO evo:22.3R1-EVO junos:21.2R3-S2 junos:21.4R3 junos:22.1R2 junos:22.1R3 junos:22.2R1 junos:22.2R2 junos:22.3R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1655031The rpd core is seen due to IGP database and BGP LS database out of sync
Product-Group=junos
On all Junos and Junos OS Evolved platforms, rpd core is hit when the events for deleting prefixes, sids, links and nodes come in out of order which occasionally leads to IGP database and BGP LS database out of sync.

Resolved In: evo:20.4R3-S5-EVO evo:21.4R3-S2-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.3X75-D36 junos:20.4R3-S5 junos:21.2R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: MX Timing software
1696957In the rare scenario, huge PTP Time errors are introduced and propagated to the downstream devices after the chassis reboot
Product-Group=junos
On MX240, MX480, MX960, MX2010, and MX2020 platforms, the remote PTP (Precision Time Protocol) clock will recover the PTP clock with Time errors after a chassis reboot on the device running as Boundary Clock.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.4R3-S6 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Microkernel for neo mpc
1670137Multibit ECC error causes the whole MX platform chassis to go down
Product-Group=junos
Faulty FPC (Flexible PIC Concentrator) on the MX platform chassis exhibiting multibit ECC (Error Checking and Correction) error (L2 cache error) will trigger this issue. The whole chassis goes down until the faulty FPC is removed from the chassis.

Resolved In: junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR NumberSynopsisCategory: OSPF routing protocol
1563350The rpd might crash on the backup Routing Engine after rpd restart is triggered on the primary Routing Engine.
Product-Group=junos
On all Evo platforms, if the rpd restart is triggered on Master RE (using the following command : restart routing immediately) then rpd might crash on Backup RE.

Resolved In: evo:20.4R1-S1-EVO evo:20.4R2-EVO evo:21.1R1-EVO evo:21.2R1-EVO junos:20.4R2 junos:21.1R1 junos:21.2R1
PR NumberSynopsisCategory: vMX Data Plane Issues
1669261vMX crashes due to MBUF leaks
Product-Group=junos
vMX platforms (MX150) will crash as a result of the MBUF (Memory Buffer) leak.

Resolved In: junos:20.3X75-D43 junos:20.4R3-S5 junos:21.4R3 junos:22.1R3 junos:22.3R1 junos:22.3R2 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1688323EVPN VXLAN with Type 5 tunnel configuration changes cause port and protocol flaps
Product-Group=junos
On Junos QFX5K series platforms, configuration changes in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) with Type 5 tunnel cause port and protocol flaps which cause traffic loss (Configuration change related to the underlay network).

Resolved In: 
1712405[EVPN-VXAN] L3 VLANs created with IPv4 bits disabled
Product-Group=junos
Traffic blackholing in EVPN fabric when performing configuration of new VLANs, it is found that L3 VLANs are having IPV4 bits disabled.

Resolved In: junos:20.4R3-S7 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R2-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: KRT Queue issues within RPD
1640813The rpd crash might be triggered due to memory corruption
Product-Group=junos
The rpd crash might be triggered due to memory corruption with the cos-next-hop-map policy configuration.

Resolved In: evo:21.3R3-EVO evo:21.4R3-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1694777Restarting FPC or router reboot might causes some CCC interfaces to go down due to a 'Remote CCC down'
Product-Group=junos
On all Junos and Junos OS Evolved platforms, if CCC (Circuit Cross-Connect) is configured to use a label-switched-path such as IGP routed, i.e., no-cspf and no strict ERO (Explicit Route Object) configuration, then restarting egress CCC node or restarting FPC on the egress CCC node containing remote-interface-switch configuration multiple times may cause CCC to remain stuck in remote-if-down state, resulting in loss of traffic. (The knob 'remote-interface-switch' is configured on the egress LER of the RSVP-TE LSP (Resource Reservation Protocol-Traffic Engineering label-switched-path) which binds the LSP terminating on the node to a local interface).

Resolved In: evo:22.4R2-EVO evo:23.1R1-EVO junos:20.4R3-J8 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: SRX branch platforms
1713759Continuous 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".

Resolved In: junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1620773SRX4600 - Packet drop or srxpfe coredump might be observed
Product-Group=junos
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: Trio pfe bridging, learning, stp, oam, irb software
1522896Egress traffic loss might happen because of PFE MTU feature problem
Product-Group=junos
On MX and EX9200 serial platforms, under Ethernet VPN (EVPN) environment, packets routed using IRB interface could not be fragmented due to media maximum transmission unit (MTU) problem.

Resolved In: junos:18.4R2-S5-J1 junos:20.4R3-S4-J3 junos:21.2R3-S3 junos:21.2R3-S4 junos:21.3R3-S2 junos:21.4R3-S2 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1618391A device which is configured IP interface(ip-x/x/x) cannot sent out encapsulated IPv4-over-IPv6 packets to a remote device in case of transit packets
Product-Group=junos
Transit IPv4-over-IPv6 encapsulated packets cannot pass through using IP over IP interface(ip-x/x/x). This behavior has been seen in'transit' packets only.

Resolved In: evo:21.2R3-EVO evo:21.3R3-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO evo:22.3R1-EVO junos:20.4R3-S3 junos:21.2R3 junos:21.3R2 junos:21.3R3 junos:21.4R2 junos:22.1R2 junos:22.2R1 junos:22.3R1



 

Modification History

First publication 2023-03-15