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 22.1R3-S3 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 22.1R3-S3 is now available.

22.1R3-S3 - List of Fixed issues 

PR NumberSynopsisCategory: EX4300 Platform
1720335On EX4300-48MP I/O accesses to disk will fail
Product-Group=junosvae
On EX4300-48MP due to a disk cache mode that is less resilient, in rare conditions, all the I/O (Input Output) accesses to the disk will fail including any configuration commands. The device might also go into an inaccessible state.
PR NumberSynopsisCategory: EX4300 Platform implementation
1712785EX4300-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 NumberSynopsisCategory: SRX DNS DGA and tunneling related
1727122Nstraced process is running high on the primary node after the Junos upgrade
Product-Group=junos
On all Junos SRX/vSRX platforms, nstraced process spikes to 100% usage after upgrading to Junos version 21.4R3-S2 or any later releases without having any traces/debugs explicitly configured in the RE (Routing Engine) or PFE (Packet forwarding Engine) of the device.
PR NumberSynopsisCategory: Accounting Profile
1692411MPC11e: repeated pfed: PFED_NOTIF_GLOBAL_STAT_UNKNOWN: xxxx in syslog
Product-Group=junos
pfed: PFED_NOTIF_GLOBAL_STAT_UNKNOWN: xxxx in syslog The above log messages will be seen when we are using SNMP and if its trying to poll "show pfe statistics notification" through MIB OID - 1.3.6.1.4.1.2636.3.44.1.1.2.1.2
PR NumberSynopsisCategory: AFT l2lam
1721704Sending GARP reply packet on a VTEP interface causes flooding in network on QFX5130 and QFX5700 platforms
Product-Group=junos
On Junos OS Evolved QFX5130 and QFX5700 platforms, Gratuitous Address Resolution Protocol (GARP) flooding occurs in the network when it receives a GARP reply packet on a Virtual Tunnel End Point (VTEP) interface.
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.
PR NumberSynopsisCategory: BBE packet trigger access model issues
1726136PTSP 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 NumberSynopsisCategory: the SMGD redundancy plugin in SMGD
1718342In a DHCP ALQ subscriber scenario delete-binding-on-renegotiation knob does not work as expected due to a synchronization error between the primary and the backup routers
Product-Group=junos
On Junos platforms, active lease query (ALQ) synchronization between peers is not happening properly. Traffic forwarding impact would be observed if there was a switchover from the Primary to the Backup. The primary router will correctly delete-binding-on-renegotiation and create a new session, but the backup router keeps the old session and old MAC address. (DHCP overrides have delete-binding-on-renegotiation configured and work as expected on the primary router whereas no notification is sent to the backup to delete the session)
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1725971Multiple flaps of the interface will cause the BFD session to be down
Product-Group=junos
On all Junos and Junos Evolved platforms, the IPv4 static route BFD (Bidirectional Forwarding Detection) session may stay down if the corresponding interface flaps multiple times.
PR NumberSynopsisCategory: Border Gateway Protocol
1728455The rpd process crashes when BGP is cleaned up
Product-Group=junos
On Junos and Junos OS Evolved platforms, if static default RT-C (Route Target -Constrain) is configured when BGP is cleaned up, the routing process might crash.
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1713444The rpd process will crash when BMP is configured
Product-Group=junos
On all Junos and Junos Evolved platforms, the rpd process will crash when BGP Monitoring Protocol (BMP) is configured. This will cause rpd to restart and affect routing protocols.
PR NumberSynopsisCategory: Issues related to Common BIOS on x86 based designs
1715258On EX4400 and EX4400-24X platforms, BIOS upgrade is not getting successful via CLI
Product-Group=junos
On EX4400 and EX4400-24X platforms, BIOS upgrade is not getting successful via CLI when the system is booted with a secondary partition.
PR NumberSynopsisCategory: BBE Remote Access Server
1709574The subscriber sessions will be logged out when assigned IP addresses from Radius or AAA via framed-IP
Product-Group=junos
On the MX platforms, when the subscriber sessions are not assigned addresses from locally configured pools and the knob "address-protection" is not enabled under the access profile configuration, then those subscriber sessions will be logged out after GRES with termination code: "aaa shutdown-administrative-reset".
1723183Subscriber sessions will fail to login post GRES and scaled subscriber scenario
Product-Group=junos
On MX platforms in a scaled subscriber scenario (8K subscribers) and post GRES (Graceful Routing Engine Switchover), the session database and IP pool database can get out of sync on the backup RE if there is a subscriber churn. After the RE switchover, this condition will lead to the immediate termination of new subscriber sessions if the assigned IP address is still in use by an existing subscriber.
PR NumberSynopsisCategory: Class of Service
1722939Cos Scheduling hierarchy on PS interface is destroyed when the TCP is modified
Product-Group=junos
When a TCP attached on a service IFL is modified, cosd is supposed to destroy the hierarchy and send gencfg messages with new TCP information. LT IFD :: level1 PS transport IFL :: level2 - -> TCP attached here is modified. PS service IFL :: level3 After destroying the hierarchy of level2 and level3 mentioned above, instead of sending the add message which will rebuild the hierarchy, it sends a change message, thus the new hierarchy is not built up while old hierarchy is destroyed. As the PS interface hierachy is destroyed because of the events mentioned above, eventhough TCP is present for the service/transport IFL, LT IFD queues would be used for sending the PS traffic.
1734013QOS scheduler map incorrect when using wildcard interface configuration: " interface <> unit * " starting with Junos 21
Product-Group=junos
Class of service scheduler map incorrectly attached to interface when configuration is using a wildcard expression for interfaces or sub-interfaces in class-of-service interface definition. Example: set class-of-service interfaces unit * classifiers.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for cos
1713968Subscribers 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 NumberSynopsisCategory: L2NG Access Security feature
1724933On 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 NumberSynopsisCategory: L2NG RTG feature
1715518Traffic loss is seen on RTG bound interface
Product-Group=junos
On all Junos and Junos OS Evolved platforms, configuring mac-move with action shutdown can disable the RTG (Redundant Trunk Groups) interface leading to traffic loss bound to that interface.
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1723968Traffic loss is seen as Type 2 routes are not pushed even after withdrawing Type 5 routes
Product-Group=junos
On all Junos and Junos Evolved platforms with the EVPN (Ethernet VPN) Type 2 and Type 5 Coexistence and when the host route changes from EVPN Type 5 route to non EVPN route in the rpd, traffic loss is observed as Type 2 routes are not getting pushed even after withdrawing Type 5 routes.
PR NumberSynopsisCategory: Device Configuration Daemon
1712800On Junos platforms the dcd will flap the IFLs which are part of EVPN routing-instance
Product-Group=junos
On Junos platform that support VPLS and/or EVPN, on configuring IGMP-Snooping or VPLS, over Bridge-domain (BD), the data-carrier-detect (dcd) will flap the Logical Interface (IFLs) which are part of this EVPN routing-instance.
1714267The 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.
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1723624Traffic is getting discarded in PFE when forwarding-table is changed
Product-Group=junos
On Junos ACX series platforms, traffic will be discarded and PFE (Packet Forwarding Engine) has error logs when EVPN-VPWS (Ethernet VPN Virtual Private Wire Service) over unilist towards NNI (network-to-network) side is configured and PFE is restarted. It is a timing issue and is dependent on the order of events received from the control plane.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1695292Traffic loss is more than expected with OSPF TI-LFA enabled and the primary path is down
Product-Group=junos
On ACX710 and ACX5448 platforms, with OSPF TI-LFA (Topology-Independent Loop-Free Alternate) Node protection L3VPN traffic loss will be more than the expected convergence time when the primary path goes down along with the 4 MPLS labels to be programmed in the secondary path.
PR NumberSynopsisCategory: Firewall related development
1720389Commit error will not be seen after deactivating routing-instance applied under firewall filter
Product-Group=junos
On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic.
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1712554The MACsec on the channelized IFD impacts the MACsec traffic on other channelized IFL interfaces within the same port and vice versa
Product-Group=junos
If both MACsec(media access control security) IFL(interface logical) and MACsec IFD(physical interface device) coexist on the channelized interface, enabling MACsec on the channelized IFD impacts the MACsec traffic on other channelized IFL interfaces within the same port and vice versa. This issue is applicable to MPC10E and MPC11E platforms.
PR NumberSynopsisCategory: EVPN control plane issues
1713508A high CPU consumption of mcsnoopd process is seen under IGMP-snooping configured scenario leading to its crash
Product-Group=junos
On all Junos and Junos OS Evolved platforms with IGMP-snooping (Internet Group Management Protocol) enabled under instance type EVPN (Ethernet Virtual Private Network) with vlan-id=none or unspecified vlan-id there will be a spike in the mcsnoopd process CPU utilization. This will lead to the mcsnoopd process crash and there will be disruptions in the traffic.
1723832The 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 NumberSynopsisCategory: EX4400 PFE software
1710219Commit convergence gets delayed with a scaled VLAN setup on EX platforms
Product-Group=junos
On EX platforms, commit convergence, i.e. the time taken for the new configuration to get processed is delayed as the number of VLANs increases. Since the traffic forwarding cannot start till the convergence is completed, it will have a traffic impact.
1718286DHCP 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.
1731522The 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.
1731548The fxpc process crashes when the next hop information is not properly maintained in the PFE table
Product-Group=junos
On Junos EX series deployed as a virtual chassis, post switchover/GRES (Graceful Routing Engine Switchover), next hop information for Type 5 route fluctuates which leads to invalid entries in the PFE (Packet Forward Engine) table and causes the fxpc (Packet Forwarding Engine Manager) process to crash.
PR NumberSynopsisCategory: EX4400 platform
168095240G VC ports might not come up after changing VC mode from HGoE to HiGig on EX4400 VC
Product-Group=junos
On Junos EX4400 VC (Virtual Chassis) platforms the 40G VCP (Virtual Chassis Port) ports do not come up after changing the VC PHY (Physical Layer) mode from HGoE (Higig over Ethernet) to HiGig. This is a rare issue that will be difficult to encounter, there will impact on traffic because the ports do not come up. To recover from the issue, the mode needs to be changed back to HGoE and a reboot needs to be performed.
1687848EX4400 SNMP : FRU removal/insertion trap may not be generated when Fan try or PIC is removed and inserted
Product-Group=junos
On EX4400, FRU removal/insertion trap may not be generated when Fan try or PIC is removed and inserted.
1696444Transceiver not detected after it's unplugged and plugged in again
Product-Group=junos
On EX4400 and EX4300MP platforms, after JOJI (jack out/jack in), transceiver is not detected in "show chassis hardware".
1707762BFD flaps will be seen on EX4400 platforms
Product-Group=junos
On EX4400 platforms, BFD (Bidirectional Forwarding Detection) will flap randomly.
1715680The interface phy of PIC 0 comes up causing traffic loss while the device boots/reboots
Product-Group=junos
On EX4400-48P/T and EX4400-24P/T platforms, traffic loss is observed when the interface phy comes up of PIC 0 for which the remote end link powers up while the device boots/reboots.
1718825[EX4400]Alarm PEM is not supported/powered might be seen
Product-Group=junos
On EX4400 platform, system alarm 'PEM is not supported/powered' might be seen after removing a power cable from PEM.
1719509There is a missing default config of RSTP which is missing when zeroriez is done
Product-Group=junos
On Junos EX4400 device running will not have a Rapid Spanning Tree (RSTP) enabled for uplink ports in the factory default config. This could impact the Zero Touch Provisioning (ZTP) of the device over uplink ports due to a risk of encountering Mac-learning race conditions or loops. If multiple such devices (that are zeroized) are in a VLAN, that could cause unpredictable results for traffic being forwarded.
1724188EX4400: Flow control shows as disabled at pfe, even after enabling it
Product-Group=junos
Flow control state does not show updated value in pfe cli when flow-control for a port is enabled or disabled. This is a display issue with PFE level flow control status, with no functional impact. Need to hard reboot the device or the dcpfe process restart to show correctly updated value
1726532EX4400: FPC temperature value is exported incorrectly as 0 in Telemtery server
Product-Group=junos
When data is streamed through telemetry with subscription to path /components/component, there is no data present for FPC temperature hence exporting as value 0. There is no functionality impact due to this issue. There is no a workaround for this issue.
1728725EX4400 VC: During upgrade/reboot , fxpc core may be seen in a very rare race condition
Product-Group=junos
issues aren't always seen. test cases are pre-provisioned and pfe planned restart conditions are randomly seen due to race conditions. System will auto recover after dcpfe core.
PR NumberSynopsisCategory: MPC10 platform specific issues on EX92xx platform
1692365A self-ping blackhole is seen along with fmpc process crash in a rare scenario causing traffic loss
Product-Group=junos
On MX platforms with MPC10, MPC11, and LC9600, traffic impact is seen on the fabric links due to self-ping blackhole and fmpc process crash under the scaled config scenario.
PR NumberSynopsisCategory: PFE EVPN / VxLAN related issues on EX platforms
1727112Programming of native-vlan-id on the interface fails and mac is not learnt
Product-Group=junos
On all EX4400 and EX4100 devices in virtual-chassis (VC) deployed, in EVPN-VXLAN scenario, with native-vlan-id configured on the interface, MAC address is not learnt.
PR NumberSynopsisCategory: EX POE
1713545The LLDP negotiation response is not sent back to PD when perpetual Power over Ethernet (PoE) is enabled on EX4400
Product-Group=junos
On the EX4400 platform, perpetual Power over Ethernet (PoE) is enabled, and when a device is connected to more than 10 Link Layer Discovery Protocol (LLDP) Power Devices (PD) and PD restarted while perpetual PoE is enabled, the LLDP negotiation response is not sent back to PD.
PR NumberSynopsisCategory: Express PFE CoS Features
1719956Convergence delay is seen when FPC is offlined under heavy traffic and scaled scenario
Product-Group=junos
On certain Junos PTX platforms (PTX3000/PTX5000/PTX10008/PTX10016) when the FPC (Flexible PIC Concentrators) is offlined with scale configuration and heavy traffic, a delay in convergence (into tens of minutes) is seen on all the live FPCs in the chassis other than the offlined one, leading to traffic impact.
PR NumberSynopsisCategory: Express PFE FW Features
1727067FPC 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), when prefixes above 65K are configured in a single firewall filter, FPC (Flexible PIC Concentrator) crash would be observed.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1701636Aggregated 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.
1718528Traffic egressing over the EVPN-VXLAN tunnel will drop which has AE interface as underlay
Product-Group=junos
On all QFX10K platforms with EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) configured with AE (aggregate-ethernet) as underlay, complete packet drop is observed in certain scenarios like chassis/FPC reboot or BGP (Border Gateway Protocol) flap which causes the tunnel to be rebuilt along with AE churn.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1723545ECMP traffic is not being forwarded on all QFX10002 platforms after software upgrade
Product-Group=junos
ECMP traffic is not being forwarded to L3 interface on all QFX10002 platforms after upgrading to any release where enhanced convergence is enabled when ECMP (Equal-cost multipath) is configured with L3 interface and VTEP (Virtual Tunnel End Point) interface.
PR NumberSynopsisCategory: Express ASIC interface
1712920When a 4x10GE channelized interface is set to disable from config, the channel 0 also goes down
Product-Group=junos
With a software changed introduced via PR1630006, when a 40G Ethernet interface is configure to be channelized interface as 4x10G interface, if an interface is disabled, or detecting an error, the interface channel 0 will also go down.
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.
PR NumberSynopsisCategory: ISIS routing protocol
1718734Unexpected behavior of bandwidth based metric for IS-IS protocol
Product-Group=junos
On all Junos and Junos OS Evolved platforms unexpected behavior of bandwidth based metric in IS-IS is seen since actual bandwidth is falling back to 0 bps when one of the member interface of AE (Aggregated Ethernet) bundle (interface-group) goes down.
PR NumberSynopsisCategory: JFlow bug tracker for SRX platforms
1716707J-flow sends wrong IP in sampling records when NAT is configured for traffic along with input sampling
Product-Group=junos
When NAT (Network Address Translation) is configured on interfaces along with sampling, the J-flow record will contain NAT'ed IP as opposed to the original IP.
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1715918The first FTPS session will not work on SRX5K platforms leading to a traffic drop
Product-Group=junos
FTPS connection to the server will not be successful until the first attempt is aborted and a new connection to the server is made.
1722877Device crashed while processing H323 traffic in SRX
Product-Group=junos
The SRX Device crashes due to a timing issue, while processing H323 traffic.
1728638SIP ALG not working and traffic is dropped
Product-Group=junos
On all MX and SRX platforms, SIP ALG not working as SIP packets with MIME header causes traffic to be dropped
PR NumberSynopsisCategory: Flow Module
1692885Packet loss is observed for IPSec sessions when PMI is enabled
Product-Group=junos
On SRX4k series, and vSRX platforms with PMI (Power-mode) enabled, when using IPSec tunnels, IPSec packets sent out by SRX which contain a small IP packet (less than 64 bytes) may be dropped by a non-Juniper IPSec VPN peer. Power-mode is enabled by default in Junos 21.3R1 and higher.
1708876The IPv6 source-level fragmented SCTP packets passing through an IPSec tunnel will be dropped
Product-Group=junos
On all SRX platforms, the IPv6 source-level fragmented Stream Control Transmission Protocol (SCTP) packets will be dropped when pass through an IPSec (Internet Protocol Security) tunnel.
1720570The IPv6 Neighbor Discovery fails on VLAN tagged reth interfaces
Product-Group=junos
On SRX5k and SRX4600 platforms, the IPv6 Neighbor Discovery(ND) fails if the IPv6 address is configured on two or more Virtual local area network(VLAN) tagged redundant Ethernet(reth) interfaces. This will impact the IPv6 connectivity on affected interfaces.
1733819The inet6 packet mode drops traffic significantly compared to the flow mode
Product-Group=junos
On the SRX branch series, inet6 packet mode (packet-based) throughput drops significantly when compared to flow-based. Traffic will be fine until the CPU reaches 100% and random traffic will be dropped.
PR NumberSynopsisCategory: Firewall Network Address Translation
1712738Some 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 NumberSynopsisCategory: Firewall Policy
1724048Traffic loss will be observed after committing faulty or incorrect configuration
Product-Group=junos
On all Junos SRX, vSRX and NFX series platforms, commit after faulty or warning-induced configuration will trigger warning on the console which invoke unstable or unexpected behavior with the system. It can even invoke iked/kmd process to flap VPN resulting in traffic outage.
1724777The nsd process crash is seen when ISSU is performed on the cluster
Product-Group=junos
The nsd (Network Security Daemon) process crash is observed when ISSU (In Service Software Upgrade) is performed on HA (High Availability) clusters using Destination NAT (Network Address Translator).
1725567Traffic impact is observed when the security policy is configured with a huge number of addresses and on addition/deletion of these policies
Product-Group=junos
On SRX platforms configured with security policies, having a huge number (approx. 15K) of addresses and performing addition/deletion of such policies in short intervals of time might result in srxpfe process crash and hence, data path traffic gets impacted.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1690921IKE cookies didn't change in rekey lifetime expire cases after manual failover
Product-Group=junos
On all Junos platform Sometimes after manual failover, IKE-SA rekey does not succeed.
1718199The iked process will crash due to a memory leak
Product-Group=junos
On SRX devices that run ike-package, iked process will crash due to a memory leak. Memory leaks over a period of time will cause the memory to be exhausted and the iked process will restart. As a result, memory allocations will fail and can cause failures for tunnel bring-up.
PR NumberSynopsisCategory: Security platform jweb support
1735314[Jweb] "Exclude selected" is unexpectedly enabled in security policy configuration
Product-Group=junos
On SRX platform, when you cancel editing source/destination address in security policy using Jweb, "Exclude selected" is unexpectedly enabled
PR NumberSynopsisCategory: Layer 2 Control Module
1717267Traffic loop is seen due to incorrect root bridge ID
Product-Group=junos
On all Junos and Junos Evolved platforms, in VSTP (Virtual Spanning-Tree Protocol) topology, whenever a new vlan is added in between previously configured vlan group followed by configuring the system-identifier, the bridge priority will change for existing vlans which might give incorrect system ID or bridge ID creating a traffic loop.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1716270mac-move-limit : MMAS flag not getting reset after interface recovers due to l2-learning restart
Product-Group=junos
MMAS Flag will not be displayed for interface after it recovers due to l2-learning process restart
1727954On all Junos and Junos Evolved platforms, the l2ald process memory usage is seen to increase over time
Product-Group=junos
Service disruptions are seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1726264JSU installation fails when MACsec is configured
Product-Group=junos
On Junos and Junos Evolved platforms with PPC based image (Example MX104), JSU (Junos Selective Update) package might not pass configuration validation when the MACsec (Media Access Control Security) configuration is present.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1698889The rpd process will crash when rpd is restarted
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information.
PR NumberSynopsisCategory: Multicast for L3VPNs
1710323MVPN tunnel is not synced to backup router
Product-Group=junos
On all Junos and Junos Evolved platforms, when OSPF inter-area is configured with segmented provider-tunnel and master undergoes MBB(make-before-break), the multicast route entry on backup router will not have the tunnel name synced with master.
PR NumberSynopsisCategory: MX Timing software
1724254On 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 NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1690892After the VC are upgraded with NSSU and rebooted again, the VCPs constantly flap.
Product-Group=junos
Upgraded using NSSU, and then after power cycling the VC, the VC gets unstable and the CPU usage of new master might get too high.
1712855ICMP packets are received on the management interface even though the destination MAC is not local
Product-Group=junos
On all platforms supporting em driver for their ethernet interface, promiscuous mode is enabled by default and hence traffic storm is noticed on the management interface.
PR NumberSynopsisCategory: Kernel MPLS / Tag / P2MP Infrastructure
1723145Routing engine initiated PING failed over MPLS interface
Product-Group=junos
The packets that have MTU size greater than the inet MTU size get dropped.
PR NumberSynopsisCategory: Express Chip L3 software
1713279Next-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 NumberSynopsisCategory: Protocol Independant Multicast
1720708Slow convergence of PIM joins causes temporary traffic loss with scaled downstream interfaces
Product-Group=junos
On all Junos and Junos Evolved platforms with PIM (Protocol Independent Multicast), MVPN (Multicast Virtual Private Network) configured and when the number of downstream interfaces is more than three thousand, slow convergence of PIM joins is seen to take up more of the time and CPU, causing traffic loss for some time.
PR NumberSynopsisCategory: PPPoE functional plugin for bbe-smgd
1701739Some PPPoE subscriber connection lost during RE switchover
Product-Group=junos
On all Junos platforms, when rpd is busy on standby RE in deleting routes from previous subscriber termination, and followed by new subscriber login in master RE and switchover performed. Some PPPoE subscriber won't come up on new master RE.
PR NumberSynopsisCategory: QFX PFE Class of Services
1641572Traffic failure with error message 'Buffers are stuck on queue' after removing and attaching 100G QSFP
Product-Group=junos
On QFX5110, traffic failure may be observed after removing and attaching 100G QSFP.
PR NumberSynopsisCategory: QFX5K hostpath
1721318Error 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
PR NumberSynopsisCategory: QFX L2 PFE
1705853Tracking PR to add the null check for list_get_head if magic is NULL.
Product-Group=junos
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.
1715477Untagged packets get dropped while adding a layer 3 logical unit to an interface with native vlan configured
Product-Group=junos
On all Junos platforms, adding a logical layer3 unit to an interface with native vlan configured causes the untagged packets to get dropped.
1725916On QFX5K platforms, the status of 'ECMP Resilient Hashing' will not be displayed in output of CLI command 'show forwarding-options enhanced-hash-key'
Product-Group=junos
On Junos QFX5K platforms, the output of CLI command 'show forwarding-options enhanced-hash-key' does not indicate weather the 'ECMP Resilient Hashing' is enabled or disabled. This is just a display issue with no functional impact.
1731460FPC will core dump when run out of memory
Product-Group=junos
On Junos and Junos OS Evolved platforms, access side hosts were connected through a switch where there was misconfiguration which resulted in duplicate IPv4 ARP/IPv6 ND getting flooded to the Leaf's and memory leak was observed.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1686539The dcpfe process crashes on QFX5k and certain EX 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.
1713133The dcpfe crashes after restarting l2-learning process on QFX and EX series Junos platforms
Product-Group=junos
The dcpfe process crash is observed on EX and QFX Junos platforms after restarting the l2-learning process when flex-hash is configured. It will be recovered automatically after the dcpfe restart
1714701Traffic blackhole after reboot
Product-Group=junos
On all Junos platforms, traffic drops observed when RH (Resilient-Hashing) is configured on a LAG (Link Aggregation Group) interface.
1724675Traffic 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 which include PR 1519244 fix, 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.
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
1712175The dcpfe process crash is seen on QFX5k platforms due to stale vtep entry
Product-Group=junos
On all QFX5000 platforms, with VXLAN (Virtual Extensible LAN) configured and due to a stale next hop entry of vtep (vxlan tunnel end point) interface, dcpfe (Dense Concentrator Packet Forwarding Engine) process crash was observed.
1716996The 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.
1730771Traffic is impacted due to high CPU and dcpfe/fxpc crash (in some cases) in EVPN-VXLAN scenario
Product-Group=junos
On Junos QFX5k and EX platforms, a high CPU and dcpfe/fxpc crash (in some cases) is seen in the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1710952No 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.
1725116The 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 NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1655052Momentary traffic drop observed for 2 to 3sec while RE switchover
Product-Group=junos
RE switchover may result in a momentary traffic drop for about 2 to 3 sec, In EVPN-VXLAN setup with EVPN type 5 traffic and NSR configuration.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1716153Multipath route is not getting compute and skip the multipath eligibility check
Product-Group=junos
On all Junos platforms, multipath route will not be formed correctly when a BGP route is received from RR (Route Reflector) and preference decided based on cluster list length.
PR NumberSynopsisCategory: Stout cards (MPC7, MPC8, MPC9) microkernel issues
1727427FPC 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 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 NumberSynopsisCategory: MX10003/MX204 Linux issues (including driver issues)
1660446SSH non-default port configuration causes FPC offline after an upgrade to 21.4
Product-Group=junos
On all VMHost platforms, if a non-default ssh port is configured for system login, after the upgrade to 21.4 release, the FPC is stuck in offline state. To avoid this issue please use the default SSH port and use protect RE filter to only allow access from the trusted source.
PR NumberSynopsisCategory: MX10002 Platform SW - Platform s/w defects
1721714BFD session failed when configured on the loopback sub interface
Product-Group=junosvae
On the MX10003 and MX304 platforms, BFD (Bidirectional Forward Detection) session failed to come up when configured on the loopback sub interface.
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
1712167Ping drop is observed between directly connected devices in SRX4600
Product-Group=junosvae
On Junos SRX4600 platform may encounter upto 25% packet packet loss after upgrade to Junos image using FPGA v1.63.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1729284L2 channel error counter increases when unknown family packets received by interfaces
Product-Group=junos
On SRX4600 and SRX5K platforms, the L2 channel error counter will increase when some unknown family packets received by interfaces.
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1726733Traffic drops with percent policer attached using list
Product-Group=junos
On Junos EX92xx, MX304 and MX series platforms with MPC10, MPC11 and LC9600, traffic drop will happen with the attachment of family filter configured with percent policer (bandwidth-percent) via input-list/output-list.
PR NumberSynopsisCategory: Trio pfe qos software
1714429The DEI bit will not be copied in the inner VLAN tag although the incoming traffic has the DEI bit set
Product-Group=junos
On all Junos platforms, there might be a service impact if the DEI (Drop eligible indicator) bit is used to decide if the packet needs to be dropped or not as the DEI bit will not be copied in the inner VLAN tag although the incoming traffic has the DEI bit set. The issue will happen when the dot1p (IEEE 802.1p) rewrite is bound to the egress interface with inner and outer tag options in the P2P (Point-to-Point) L2VPN (Layer 2 Virtual Private Network) environment.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1636758JDI-RCT:M/Mx: FPC core @ jnh_call_read_index , trinity_nh_ucast_uninstall_hw
Product-Group=junos
With given multi dimensional scale, if configuration is removed and restored continuously for more than 24 times, MX Trio based FPC may crash and restart. During the reboot, there can be traffic impact if backup paths are not configured.
1696106Packets received from type-5 tunnel are not sent out to local CE in EVPN-VxLAN scenario
Product-Group=junos
IIn EVPN-VxLAN scenario, traffic drop can be seen for some local CEs which are multihomed to at least one MX Router as the packets
1727049Multiple CFM sessions are not coming up when CFM configured on AE interfaces
Product-Group=junos
On all Junos platforms, the pfe instance of the child ifl is getting wrongly updated due to this multiple CFM sessions are not getting established.
PR NumberSynopsisCategory: Junos Automation, Commit/Op/Event and SLAX
1642991BNG Controller: L2TP LAC functionality is not working in this release
Product-Group=junos
L2TP LAC functionality is not working in this release
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.
PR NumberSynopsisCategory: Issues related to NETCONF
1709056Unable to upgrade Junos using NetConf or Junos script
Product-Group=junos
On all Junos and Junos 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.
PR NumberSynopsisCategory: web filterig issues
1715260utmd 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 NumberSynopsisCategory: VMHOST platforms software
1686825The pre-installed optional packages and JSUs will be lost after a VMHost rollback
Product-Group=junos
On VMHost based platforms, the pre-installed optional packages and Junos Selective Update (JSU) packages will be lost when a VMHost reboot is performed after VMHost rollback.
1726775Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support
Product-Group=junosvae
Steps for Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support is described in https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/task/vmhost-nvm-upgrade.html i40e NVM version 6.01 is the prerequisite to install a LTS19 based image, else image installation will fail. This prerequisite is not needed now.
PR NumberSynopsisCategory: Virtual Private LAN Services
1729052The rpd process crash will be observed during VPLS to EVPN migration
Product-Group=junos
On all Junos platforms during VPLS (Virtual Private LAN Service) to EVPN (Ethernet Virtual Private Network) migration, when the EVPN and VPLS are configured under the same routing instance and "instance-type evpn" is enabled, then upon deactivate/delete "protocols vpls" and changing the IFL configuration associated with VPLS will lead to rpd process crash.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1720943Issue 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 NumberSynopsisCategory: usf nat related issues
1729801Traffic drop might be observed on MX Platform configured with PCP mapping 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 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.
PR NumberSynopsisCategory: usf service set related issues
1728510SNMP walk timeout for NMS
Product-Group=junos
On Junos MX platform with SPC3 card, NMS (Network Management System) times out when polling any data from jnxSpSvcSetIfTable OID.
 
 

22.1R3-S3 - List of Known issues 

PR NumberSynopsisCategory: JUNOS bugs found in UAC integration
1692398Connection fails are observed on Junos despite a valid auth entry
Product-Group=junos
On Junos platforms, authentication failures and connection drops are observed for a few users when UAC (Unified Access Control) modules fail to look up the roles.

Resolved In: junos:20.2R3-S8 junos:20.4R3-S7 junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Daily JUNOS build failures - automated builder use only
1691209Use latest os-package when upgrading
Product-Group=junos
Upgrade to 22.3R1 while using os-package published between July 2022 and November 2022 may incorrectly link os-libs package

Resolved In: junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S2 junos:22.1R3-S1 junos:22.2R2-S1 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR NumberSynopsisCategory: EX4300 PFE
1720219PFE process crash is observed on Junos EX4300 platforms
Product-Group=junos
In a rare scenario, due to timing issues, the Packet Forwarding Engine (PFE) crash is observed on Junos EX4300 platforms. This causes traffic loss until the PFE comes up.

Resolved In: junos:21.4R3-S4
PR NumberSynopsisCategory: EX4300 Layer 2 implementation
1697995Dot1x authentication failure for EVPN VXLAN enabled port
Product-Group=junos
On Junos EX4300-48MP platforms, dot1x authentication fails with EVPN-VXLAN (Ethernet VPN-Virtual extensible LANs) end to end configuration on a user port.

Resolved In: junos:21.4R3-S3 junos:21.4R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EX-Series VC Infrastructure
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 junos:21.4R3-S4
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:21.4R3-S4 junos:22.1R3-S2 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.2R1 junos:23.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:21.4R3-S4 junos:22.1R3-S2 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: 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:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Border Gateway Protocol
1690213BMP 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
PR NumberSynopsisCategory: Issues related to Common BIOS on x86 based designs
1687790CPU will not reset automatically and will not work as expected when CAT Error is observed
Product-Group=junosvae
Unexpected behavior will be seen on the QFX5120-48Y/QFX5120-48T platforms when any CAT (Catastrophic) error (PCIE/ memory driver issue, defective memory, any PCIE (Peripheral Component Interconnect Express) events like malfunctioning PCIE devices etc) is seen. The switch can also go in the hung state as the CPU is unable to execute the instructions.

Resolved In: junos:20.4R3-S6 junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: BBE Remote Access Server
1687998The authd process crashes during GRES recovery phase
Product-Group=junos
On MX platforms, during recovery phase of Graceful Routing Engine Switchover (GRES), authd process crashes.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: Device Configuration Daemon
1679952After changing the settings related interface, a particular interface does not flap but a LAG interface may flap on all Junos platforms except MX
Product-Group=junos
The LAG (Link Aggregation Group) member links may flap on all Junos platforms except MX when the configuration of any interface is changed/modified. The flap is not seen always.

Resolved In: junos:21.4R3 junos:21.4R3-S4 junos:22.1R3 junos:22.1R3-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
1702615Leaf to leaf traffic flow is observed on Junos ACX5448 platform with EVPN E-Tree configuration
Product-Group=junos
ACX5448 Ingress PE is pushing label 0 instead of leaf label, hence traffic received on other PE is sending traffic out of leaf IFL (Logical Interface).

Resolved In: junos:21.4R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1683900The traffic drop is observed in the l2circuit scenario with control-word configuration
Product-Group=junos
On Junos ACX5448/ACX710 platforms in the layer2 circuit (l2circuit) scenario, if the control-word configuration is enabled/disabled, the complete traffic drop is observed for the affected l2circuit.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S1 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1712564Transit traffic drop is observed for the BGP-LU route prefixes with ECMP forwarding path on Junos ACX5448/ACX710 platforms
Product-Group=junos
On Junos ACX5448/ACX710 platforms, if the BGP-LU route prefixes points towards the ECMP forwarding path, the transit traffic drop is observed for the BGP-LU routes, due to the incorrect programming for the routes.

Resolved In: junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Gnats category for dynamic rendering infrastructure
1698192EVO jkey path changed under protocol/isis. "isis/levels" is missing
Product-Group=junos
When using the proprietary subscribe RPC for telemetry, the "isis/levels" keyword is missing from the jkey output for leaf lists.

Resolved In: evo:22.1R3-S2-EVO evo:22.2R3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.1R3-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Firewall related development
1720389Commit error will not be seen after deactivating routing-instance applied under firewall filter
Product-Group=junos
On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic.

Resolved In: evo:21.4R3-S4-EVO evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: jdhcpd daemon refactored for evo
1707690[dhcp] [DHCP_RELAY] ACX7100-48L :: Getting commit error for the dhcp config commit and then it is coring with the bt jtimer_start_oneshot
Product-Group=junos
During commit of configuration related to active-leasquery requires initialization of timers. However, in Junos Evolved system, the timers were not initialized correctly. This caused commit check error.

Resolved In: evo:22.1R3-S2-EVO evo:22.2R3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1709605Traffic drop is observed with "vxlan encapsulate-inner-vlan" knob on Junos QFX10K platforms
Product-Group=junos
On Junos QFX10K platforms, in an EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, if the "vxlan encapsulate-inner-vlan" knob is enabled, the Address Resolution Protocol (ARP) unicast packets are dropped if it egresses out of the VXLAN tunnel. This will cause a complete traffic drop.

Resolved In: junos:21.4R3-S3 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R2
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1630981BGP down due to BFD expired; failover restored services
Product-Group=junosvae
All VPN traffic may internally drop during encryption / decryption processing in HW engine requiring PFE plane reset.

Resolved In: junos:20.4R3-S7 junos:21.4R3-S3 junos:23.2R1
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.

Resolved In: junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:21.4R3-S4 junos:22.1R3-S1 junos:22.1R3-S2 junos:22.2R3 junos:22.2R3-S1 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1696102IPsec VPNs will disconnect after ISSU
Product-Group=junos
On SRX platforms except SRX5K, & vSRX2.0/vSRX3.0, traffic will not pass over IPsec (Internet Protocol Security) VPN tunnels after ISSU (In-service software upgrade).

Resolved In: junos:21.2R3-S5 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: For multicast snooping on MX
1699784The mcscnoopd process will be stuck in resync state after snooping configuration is deleted and added again immediately
Product-Group=junos
On all Junos platforms, when the multicast snooping configuration is deleted and added again immediately, the mcscnoopd (multicast-snooping process daemon) process will be stuck in the resync state, impacting the multicast traffic.

Resolved In: evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.3R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Multicast for L3VPNs
1700345The rpd crash happens when Multicast VPN (Virtual Private Network) is configured with separate route-targets scenario
Product-Group=junos
This happens only when MVPN protocol has separate route targets configured and then both the address families are disabled. rpd (Routing process daemon) infra parsing does not check if MVPN protocol is disabled and hence will create the auto policies for route-targets if configured. So if those policies are not marked as active in MVPN configuration flow, it does not get resolved and thereby the policy object may not be valid thus leading to the core.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1
1708572The pseudowire interface is not showing after performing the switchover
Product-Group=junos
On all Junos and Junos Evolved platforms, after performing RE(Routing Engine) switchover the pseudowire interface is not showing and traffic will be blackhole.

Resolved In: evo:23.2R1-EVO junos:23.2R1
PR NumberSynopsisCategory: MX Timing software
1704644Software improvement for PTP nbr-update || lcinfo_bmc || utc_arrival_time || lcinfo_msg || utc_arrival_time
Product-Group=junos
Enhancement needed on PTP nbr-update to improve user experiences.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.4R3-S6 junos:21.2R3-S6 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: MX10K platform
1684728An interface configured as 1G may flap on a port with the mixed speeds of 1G and 10G after a PIC restart
Product-Group=junos
On MX10008, MX10004, and MX10016 platforms with LC2101, when the channelized interfaces of a port are configured with mixed port speeds of 1G and 10G, after a Physical Interface Card (PIC) reboot the 1G channelized interface will keep flapping. Or, it may also remain down. This will impact all the services running through the 1G channelized interface.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1671649Traffic loss may be seen due to SPC3's packets getting stuck
Product-Group=junos
On Junos MX960, MX480 and SRX5000 series platforms with SPC3 card, Flowd restart or PIC (Physical Interface Card) going offline/online may cause SPC3's sending of packets to get stuck.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R2-S1 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1681783On Ex4400 upgrade failure happens when upgrading through a USB drive.
Product-Group=junos
On EX4400 upgrade failure happens when upgrading through a USB drive.

Resolved In: junos:19.1R3-S10 junos:19.2R3-S7 junos:19.4R3-S10 junos:20.3R3-S6 junos:20.3X75-D43 junos:20.3X75-D46 junos:20.4R3-S5 junos:21.2R3-S3 junos:21.2R3-S4 junos:21.3R3-S2 junos:21.3R3-S3 junos:21.4R3-S1 junos:21.4R3-S4 junos:22.1R2-S1 junos:22.1R2-S2 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R2-S1 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Path computation client daemon
1678970The pccd process might crash during MBB for an externally controlled LSP
Product-Group=junos
On MX and PTX platforms the pccd (Path Computation Client Process) might crash when MBB (Make before break) update is received from rpd.

Resolved In: evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: QFX L2 PFE
1730076Packets received on a port that is in "LACP Detached" state is getting forwarded
Product-Group=junos
On all Junos EX46xx/QFX5k (except QFX5100) platforms, child links that are in LACP (Link Aggregation Control Protocol) detached state are up and accepting incoming traffic, expecting it to drop.

Resolved In: junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1666260Traffic loss might be seen when l2circuit configurations are deactivated and activated on QFX5110
Product-Group=junosvae
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: junos:20.2R3-S8 junos:20.4R3-S8 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
1690239MPLS traffic will be dropped due to the wrong programming of the L3VPN ID
Product-Group=junos
On certain QFX/PTX platforms, when a new Virtual Routing and Forwarding (VRF) is created or FPC reboot/restart or Router upgrade is performed MultiProtocol label switching (MPLS) traffic will be dropped due to the wrong programming of the L3VPN ID.

Resolved In: junos:21.4R3-S1 junos:22.1R3 junos:22.2R3 junos:22.2R3-S1 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1 junos:23.1R2
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1625285Traffic loss might be observed after configuring VXLAN over IRB interface
Product-Group=junos
On QFX5100/QFX5110/QFX5200/QFX5210/EX4300-48MP/EX4600/EX4650-48Y platforms, with IRB interface as underlay for VXLAN, data plane VXLAN traffic loss might be observed.

Resolved In: junos:21.2R2-S1 junos:21.2R3 junos:21.3R2 junos:21.4R1 junos:21.4R2 junos:22.1R1
1697614Local multicast traffic forwarding issue can be seen on QFX5K in EVPN-VXLAN OISM setup
Product-Group=junos
On Junos QFX5K devices in OISM (Optimised Inter Subnet Multicast) scenario, there can be issues with local multicast traffic forwarding between VLANs (Virtual Local Area network). This issue will be seen when there are similar VLAN and VLANRW (Virtual Local Area Network Rewrite) configurations on AE (Aggregated Ethernet) interfaces and VLAN from the AE interface is deleted. This issue is a rare timing issue and the recovery method is to add a new VLAN on the interface before deleting the existing VLAN config.

Resolved In: junos:21.4R3-S4 junos:22.2R2-S1 junos:22.2R3 junos:22.2R3-S1 junos:22.3R2 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover, 
1681394The rpd process will crash due to rpd memory leak
Product-Group=junos
On all Junos and Junos Evolved platforms with 21.4 above version, when continuous BGP flapped is seen, a memory leak in the rpd process may be observed. The continuous flapping of BGP will acquire more memory eventually the system will run out of memory, causing the rpd crash when new memory is requested.

Resolved In: evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R1-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.3R3-S2 junos:21.4R3 junos:22.1R3 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: KRT Queue issues within RPD
1721032Local route is not added in the secondary FIB and KRT queue is stuck
Product-Group=junos
On all Junos SRX platforms when ST (Secure-Tunnel) interface with P2MP (Point-to-Multipoint) is configured and interface routes are leaked via RIB(Routing Information Base)-group, local route of the ST interface will not be leaked into forwarding-table of the secondary-RIB and it will be stuck in the KRT (Kernel Routing Table) queue.

Resolved In: evo:21.2R3-S6-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1677749High CPU is seen on the platforms running IPv6
Product-Group=junos
On all Junos platforms, high CPU is seen due to ipv6 router-advertisement.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:22.1R3 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1685182RSVP path tear is not encapsulated by the MPLS header when bypass is configured
Product-Group=junos
On all Junos and Junos Evolved platforms, RSVP(Resource Reservation Protocol) path tear is not encapsulated by the MPLS(Multiprotocol Label Switching ) header, when "no-enhanced-frr-bypass" is configured on the routers that undertake FRR(fast re-route) procedures after the failure.

Resolved In: evo:21.2R3-S3-EVO evo:21.3R3-S3-EVO evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: SW PRs for SCBE3 fabric
1724007Complete traffic blackhole from one PFE to another on fabric links after injecting/reporting CRC errors on fabric links of MX10008
Product-Group=junos
On the MX10008 platform, the low-priority stream might be marked as a destination error and as a result, the low-priority stream is stuck and all traffic might get dropped. Complete traffic blackhole is observed from one PFE to another.

Resolved In: junos:21.4R3-S4 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: SRX branch platforms
1680405Dial-on-demand mode on the dialer interface is not working as expected
Product-Group=junos
On SRX branch series platforms with a dialer interface, the dial-on-demand mode on the dialer interface is not working as expected.

Resolved In: junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
1715247Interface speed stays 100Mbps when removing speed and duplex command separately
Product-Group=junos
On SRX platforms, Interface speed stays 100Mbps when removing speed and duplex command separately

Resolved In: junos:20.4R3-S8
PR NumberSynopsisCategory: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1648473The FPC crash might be observed during ISSU
Product-Group=junos
On all Junos platforms with scaled environment equipped with specific line cards like MPC7E/MPC8E/MPC9E etc., when there are memory errors, the FPC crash might be observed. This happens during ISSU (In-service software upgrade).

Resolved In: evo:21.3R3-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:20.2R3-S5 junos:20.4R3-S5 junos:21.1R3-S5 junos:21.2R3 junos:21.3R2-S1 junos:21.3R3 junos:21.4R2 junos:22.1R1 junos:22.1R2 junos:22.2R1
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1720772VLAN rewrite will not work for traffic egressing on IRB over L2 AE IFL
Product-Group=junos
On Junos MX and EX92XX with specific line cards, VLAN rewrites will not happen for traffic egressing from IRB(Integrated Routing and Bridging) interface over an L2 AE (Aggregated Ethernet) IFL (Interface Logical), if the L2 AE IFL is configured to perform VLAN rewrites on the frames. This happens when the IRB is configured as a routing-interface on EVPN (Ethernet Virtual Private LAN) or VXLAN (Virtual Extensible LAN) routing instances and the traffic has to egress on IRB over an L2 AE IFL. As a result, the frames are forwarded with incorrect VLAN tag information.

Resolved In: evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.2R3-S6 junos:22.2R3-J4 junos:22.2R3-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1708321MX960 :: CST:RE goes to amnesiac state, when rebooting the DUT -mgd: error: translation script failure
Product-Group=junos
When a toggle attribute with variable is committed under dynamic-profiles hierarchy, upon reboot system will go to amnesiac mode

Resolved In: evo:21.4R3-S3-EVO evo:22.2R2-J4-EVO evo:22.2R2-J6-EVO evo:22.2R2-S2-J1-EVO evo:22.2R2-S2-J2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-S2-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:20.4R3-S7 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R2-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
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.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 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

Modification History

First publication 2023-06-09