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.2R3-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.2R3-S5 is now available.

21.2R3-S5 - List of Fixed 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.
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.
1706845Layer 3 forwarding issues for IRB
Product-Group=junos
On EX2300, EX3400, EX4400, EX4100 and EX4300-MP platforms, when master FPC with mac-persistence-timer configured on a virtual chassis switch is halted, it leads to layer 3 (l3) forwarding issues for the integrated routing and bridging (IRB).
PR NumberSynopsisCategory: EX2300/3400 platform
1695057The l2cpd telemetry crash would be observed when the LLDP Netconf notification from external controllers along with Netconf services configuration is present on the device
Product-Group=junos
On all Junos and Junos Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with "system services netconf notification" enabled will trigger the l2cpd crash. This crash causes the CPU to spike.
1706116Alarms were not generated as expected when the Management Interface Link was down
Product-Group=junos
On Junos EX3400 device, whenever the Management Interface Link is Down, the alarm was not getting generated as expected.
PR NumberSynopsisCategory: Accounting Profile
1706085Firewall filter counters are not written to accounting file when interface-specific knob is used
Product-Group=junos
On all Junos platforms, when firewall filters are configured with 'interface-specific' knob to log packet counters on the accounting file using 'accounting-options', firewall filter counters are not written to this file. This causes problem in fetching the filter counters.
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 platforms, devices may display wrong temperature values when executing commands. The temperature value is processed as positive integers but not negative integers. Hence, the negative temperature value is showing the wrong value.
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.
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: MPC Fusion SW
1716766A 10G port on a MPC2E or MPC3E 4x10G MIC can randomly flap constantly every few seconds
Product-Group=junos
On Junos MX platforms, the interface flaps in every few seconds on the 10G port on 4x10G MIC on MPC2E-NG or MPC3E-NG card whatever cause the interface to go down.
PR 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: 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: srx5k service offloading related PR
1702138TCP packet drops are seen when services-offload is enabled
Product-Group=junos
On Junos SRX5400, SRX5600, SRX5800 and SRX4600 Platforms, packet drops may be observed while services-offload is enabled.
PR NumberSynopsisCategory: BBE dynamic profile related issues
1714778PPPoE and DHCP subscriber connection on dynamic VLAN can fail on Junos MX platforms
Product-Group=junos
On Junos MX platforms supporting subscriber services, cleanup of a dynamic VLAN (Virtual Local Area Network) session may fail if SDB (Subscriber Database) becomes briefly unavailable. The dynamic VLANs will stay in an active state, but all PPPoE (Point to Point Over Ethernet) and DHCP (Dynamic Host Configuration Protocol) subscriber connection attempts over this VLAN will fail.
PR 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)
1589765The multi-hop BFD session may flap if the RSI (Request Support Information) collection command is executed
Product-Group=junos
On QFX10002 platforms, the multi-hop BFD session might flap if collecting RSI or some other outputs (such as show interface or configuration). It is caused by the missing BFD packets because the PPMAN thread is not scheduled within the BFD timers which are 300 milliseconds with a multiplier of 3.
PR NumberSynopsisCategory: Border Gateway Protocol
1695062Traffic blackholing is observed when removing the BGP routes take a long time to get removed from RIB
Product-Group=junos
On Junos platforms, if a BGP (Border Gateway Protocol) peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as other work in the routing process utilize the CPU.
1705938The BGP sessions will flap after the RE switchover
Product-Group=junos
On all Junos and Junos OS Evolved platforms with dual RE (Routing Engine) or VC (Virtual Chassis) with NSR enabled scenarios, in some rare BGP scaled scenarios upon RE switchover the new Master RE will send out a route refresh message to all the peers, which is not expected. This will eventually lead to the BGP session flap.
PR NumberSynopsisCategory: Issues related to Common BIOS on x86 based designs
1687790CPU will not reset automatically and will have abnormal behaviour when CAT Error is observed
Product-Group=junosvae
Abnormal behaviour will be seen on the QFX5120-48Y/QFX5120-48T platforms when any CAT (Catastrophic) error (PCIE/ memory driver issue, Defective memory, any PCIe 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.
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".
1710145High CPU utilization is seen on Junos MX series platforms
Product-Group=junos
This issue is seen on Junos MX series platforms that support authd process. when authd traces are enabled in scale setup with 10k+ routing instances, authd will keep generating some logs. These logs consumes CPU cycles and makes authd process to utilize 100% CPU.
1715490IPv4 and IPv6 address allocation will be impacted due to changes in address pool configuration
Product-Group=junos
On Junos platforms supporting address assignment pools, after changing, deleting, adding the IP address pools and moving the prefix ranges among the pools in a single commit would impact the IP address allocation process. This happens because of the overlapping of address prefixes in the pools.
PR NumberSynopsisCategory: Virtual-chassis platform/chassisd infrastructure PRs for MX
1706268FPC offline can be seen on MX-VC during the sequential upgrade
Product-Group=junos
On Junos MX-VC (Virtual Chassis), CCL (Chassis Control Link), and CRC (Cyclic Redundancy Check) errors can be seen after FPC (Flexible PIC Concentrator) detach during the sequential OS (Operating System) upgrade of MX-VC system. The CCL and CRC errors are expected after the FPC detaches and eventually, the FPC is marked offline by the MX-VC and there is an unexpected chassisd process restart. The chassisd restarted because of the connection failure between LCC (Linecard Chassis Control) chassisd and SCC (Switch Chassis Control) chassisd which is triggered by the sequence of messages exchanged between the LCC and SCC after the FPC detach event. There will be a traffic impact as the FPC will be offline, and the system recovers to a working state by itself.
1713502The firmware upgradation will fail for MPC7E line card in MX-VC 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.
PR NumberSynopsisCategory: Class of Service
1699714The AE (Aggregated Ethernet) link flaps on MX platforms with MPC10, MPC11, and LC9600 when high or medium priorities are configured on the queue
Product-Group=junos
The AE link flaps on MX platforms with MPC10, MPC11, and LC9600 when high or medium priorities are configured on the queue. When there is a link flap for a link in the AE bundle with queues having configured high/medium priorities, then it is possible to see a queue drain failure which leads to the queue getting stuck with no traffic moving out.
1702836Control packets would be dropped when CoS configuration under AE wildcard IFLs gets applied to AE control IFLs as well
Product-Group=junos
On MX platforms, when Aggregated Ethernet (AE) working in hierarchical-scheduler or per-unit-scheduler mode and AE class of service (CoS) configuration having wildcard on AE Logical Interface (IFLs) is committed in a single commit with AE interface flap, then the wildcard configuration gets applied to AE control IFL also. Ideally, any wildcard CoS configuration should not get attached to control IFLs. Only explicit configurations should be attached to control IFLs. This can lead to unintentional behavior.
1719028The cosd process crash might be seen on all Junos platforms
Product-Group=junos
On all Junos platforms when the number of supported queues exceeds above 12, the cosd (Class of Service Daemon) process crash will be seen in an extremely rare scenario.
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1617068EVPN-VXLAN : old vtep interface would be remained in the esi output.
Product-Group=junos
On EVPN-vxlan setup, old remote vtep interface would be remained in the list of ESI links.
1712805The generation of the VXLAN table appears to be lost after loading configuration
Product-Group=junos
On all Junos and Juos OS Evolved platforms that have EVPN-VXLAN enabled, the generation of the VXLAN table and the message during the setup of the EVPN/VXLAN connection seems to get lost because of a timing issue between the layer2 address learning daemon(l2ald) and routing protocol daemon( rpd ) connections.
PR NumberSynopsisCategory: Device Configuration Daemon
1650676The dcd core may be seen on the backup RE after GRES is disabled if targeted distributed configuration is used
Product-Group=junos
The device control daemon (dcd) on the backup RE might crash immediately after GRES and NSR are disabled if AE logical interfaces are configured with targeted distribution.
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.
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.
PR NumberSynopsisCategory: ACX IFL, IFF creation
1691004The PFE process crashes on ACX5448
Product-Group=junos
On Junos ACX5448 platforms, the PFE (Packet Forwarding Engine) process will crash after continuous IFD (Interface Device) flaps. As a result, all traffic will be lost until the process recovers on its own.
PR NumberSynopsisCategory: Gnats category for dynamic rendering infrastructure
1681777Invalid XML output in rpc response
Product-Group=junos
If the configured data has special characters in it, then rpc get output will not escape these special characters and display the data as it is. For example, if we have configured qos class as , then ---- > the response should have default as response value
PR NumberSynopsisCategory: EVPN control plane issues
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: EX4100 RE, Platform Infra, Drivers
1656611The show chassis led output does not match the LED behaviour
Product-Group=junos
The output of "show chassis led" does not match the LED behavior. The admin down/up status in ADM mode does not work properly.
PR NumberSynopsisCategory: EX4400 PFE software
1701546The BFD session will remain in init/down state in the Virtual Chassis scenario
Product-Group=junos
On Junos EX and QFX Virtual Chassis platforms configured with Bidirectional Forwarding Detection (BFD) over the Aggregate Ethernet (AE) interface, when the BFD control plane traffic is received on the lag member port which is present as non-anchor FPC of the BFD session, the BFD session will be stuck in the Init/down state. Only single-hop BFD sessions will be impacted.
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: Express PFE CoS Features
1645488Junos ACX/PTX/QFX platforms might silently discard packets after an interface flaps
Product-Group=junos
On certain ACX Series, PTX Series, or QFX Series devices running Junos OS, the device might silently discard packets when the backoff time is set on port or with congestion during link down and up events. There will be a service impact because of the traffic drops. As restoration, the egress Flexible PIC Concentrator (FPC) needs to be rebooted.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1711889Traffic drop is observed in the EVPN-VXLAN scenario with Type-2 ESI Tunnel
Product-Group=junos
On Junos QFX10K platforms, in an Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, if the route is learned over ECMP (Equal-Cost Multi-Path) and each child next hop of the ECMP group is learned over Type-2 Ethernet Segment Identifier (ESI) tunnel, the route doesn't get programmed correctly on the device, causing the complete traffic drop for the affected route.
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 MPLS Features
1712076FPC memory leak will cause FPC crash
Product-Group=junos
On PTX and QFX10K platforms, enabling the collection of LSP (label-switched path) statistics for telemetry data using the CLI command 'set protocols mpls sensor-based-stats' will cause FPC (Flexible Physical Interface Cards (PIC) Concentrators) memory leak and a huge leak may result in FPC crash.
PR NumberSynopsisCategory: SRX1500 platform software
1656738The fxp0 interface might remain 'UP' when the cable is disconnected
Product-Group=junosvae
On specific SRX platforms, the fxp0 interface might remain up even when the cable is disconnected.
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: Interface Information Display
1611623SRX1500: Traffic fail seen on irb interface for network control forwarding class when verifying dscp classification based on single and multiple code-points
Product-Group=junos
Traffic drop might be seen on irb interface on SRX1500 for network control forwarding class when verifying dscp classification based on single and multiple code-points.
1636668Management interface speed is incorrectly reported as 10G instead of 1G
Product-Group=junos
On VM Host platforms, the management interface speed may incorrectly be displayed as 10G instead of 1G - this is a cosmetic issue.
PR NumberSynopsisCategory: MX Inline Jflow
1708195SRR : Unsupported AsIndex logs reported continuously on the device for MPC10/MPC11 linecards
Product-Group=junos
During transitioning window with high BGP scale, when old AS-Path are getting deleted and new getting allocated it can happen that on RPD the as_index count can go more than the max supported value on FPC, thus these errors can be reported. AS-Path are reference counted and during transitioning state where some routes have updated to new as-paths some routes may still be holding reference to old AS-Path index, so increasing the as_index allocation count to exceed max support value on line-card. This issue is -high scale specific and should not happen if the surge is only of ADD operation. This issue should not impact operational traffic and only monitoring services might get impacted.
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.
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.
1698781The kernel crash can be seen in the VPLS scenario
Product-Group=junos
On Junos platforms, Kernel crashes can happen in VPLS (Virtual Private LAN Service) scenario. This issue is seen when the VPLS has IRB (Integrated Routing and Bridging) interface and the next-hop of IRB is RLT (Redundant Logical Tunnel) interface. This issue is triggered when there is an ARP request sent from the IRB interface. There can be a service impact because of this issue as the device can reboot.
PR NumberSynopsisCategory: legacy carrier pic
1701875The cstm4 interface on MIC-3D-8CHOC3-4CHOC12 cannot be partitioned to more than 10 E3 interfaces
Product-Group=junos
On MX platforms with MIC-3D-8CHOC3-4CHOC12, creation of 11th and 12th channelized E3 interfaces will fail on a Channelized STM4 interface.
PR NumberSynopsisCategory: ISIS routing protocol
1696598Wrong SRTE Secondary path weight makes the secondary path active in forwarding table
Product-Group=junos
On all Junos and Junos Evolved platforms, SRTE (Segment Routing Traffic Engineering) Secondary LSP (Label Switched Path) should be only on standby in the forwarding table however it is also active and forwarding traffic due to the wrong metric calculation.
PR NumberSynopsisCategory: jdhcpd daemon
1684521DHCP packets sent to the client have the Option 82 Suboption length set to 0
Product-Group=junos
In all Junos platforms, if a DHCP ( Dynamic Host Configuration Protocol) packet containing an Option 82 Circuit ID or Remote ID made up of Null ASCII values (0x00000005) is received, the system incorrectly sets the length of the option to '0' in responses.
1689005DHCP packets might not be sent to the clients when 'forward-only' is reconfigured under the routing instance
Product-Group=junos
On all Junos platforms, reconfiguring 'forward-only' in any routing instance is leading to deactivate of [default:default] jdhcpd filter. Dynamic Host Configuration Protocol (DHCP) packets might not be sent to the clients.
1713619A jdhcpd process crash is observed on all Junos platforms
Product-Group=junos
On all Junos platforms with DHCP (Dynamic Host Configuration Protocol) relay/server/client configured, a jdhcpd process crash is observed when FPC (Flexible PIC Concentrator) is restarted or rebooted and the DHCP functionality could be impacted.
1714260The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established.
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1688986H.323 traffic failure caused by RAS packet drops when incorrect route lookup performed
Product-Group=junos
On SRX platforms, due to incorrect route lookup performed for default routing-instance instead of ingress routing-instance results in RAS (Registration, Admission, and Status) packet drops for which H.323 traffic failure is observed.
1715315The PPTP connection is not stable and is lost in DS-Lite+ALG scenario
Product-Group=junos
On all Junos MX platforms with MS-MPC/MS-MIC cards in DS-Lite (Dual-stack Lite)+ ALG scenario, the Point-to-Point Tunneling Protocol (PPTP) connection between the client and server is not stable and is lost. The PPTP failure occurred due TCP keepalive mechanism that is always broken due to wrong data in the generated tcp-tickle packet.
1715918SRX5600 | FTPS connection is impacted with ftps-extension config in the device.
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.
PR NumberSynopsisCategory: Flow Module
1683835The non-fragmented packets will get dropped on the SRX5K platforms with SPC3 card
Product-Group=junos
On SRX5K platforms with SPC3 card and IFD enabled, when the fragmented and non-fragmented traffic are processed in a burst on the IPsec tunnel, the non-fragmented packets will get dropped. There will be a very small number of packet drops seen.
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.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
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.
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
1708777Setting the security log profile without a category or stream will lead to srxpfe process crash
Product-Group=junos
On all Junos SRX platforms, when security log profile is added without a category or stream can cause the srxpfe to crash. Due to this there will be complete traffic loss.
1722122ISSU is aborted after one node upgrade and flowd process crash is observed
Product-Group=junos
On SRX1500, SRX4100, SRX4200 and SRX4600 platforms, ISSU (In-Service Software Upgrade) aborts after upgrading one node from 20.4 or lower versions to 21.1 or higher versions and flowd process crash is observed on that node.
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.
1713576The core dump is observed with the security policy updated with changing IP address related to the FQDN
Product-Group=junos
The policy gets updated frequently due to changes in FQDN (Fully Qualified Domain Name) resolution. At the same time, SIP (Session Initiation Protocol) was created with old policy data, thus Parallel security policy updation and sip data packet handling led to the core.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1416334Traffic over IPSec tunnels may be dropped during ISSU
Product-Group=junos
On SRX5400, SRX5600, and SRX5800 devices, during in-service software upgrade (ISSU), the IPsec tunnels flap, causing a disruption of traffic. The IPsec tunnels recover automatically after the ISSU process is completed.
1653704The IPSec tunnel via IPv6 might not establish after rebooting SRX devices
Product-Group=junos
On SRX devices, if IPSec is configured with aggressive mode, the IP type of the peer device might differ from the IP address for the IKE (Internet Key Exchange) external-interface. Thus, the VPN tunnel might not come up after rebooting the device. This issue affects only IPv6 VPN sessions.
1667223VPN traffic loss is seen after HA node reboot while using traffic selectors
Product-Group=junos
On all Platforms, traffic across static VPNs (Virtual Private Network) with traffic selectors might be affected after reboot of one node in the cluster and failover to it.
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).
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: Platform infra to support jvision
1661423Continuous error logs and Telemetry data might not be populated
Product-Group=junos
On all Junos platforms, error logs are observed and telemetry data related to the transceiver does not get correctly populated for PICs (Physical Interface Cards). This is a non-service impacting issue.
1686766MPC10E line card will reboot due to the sensord crash
Product-Group=junos
On MX platforms with MPC10E line card, for sensor installed by health-mon causing sensord crash resulting in the MPC10E line card reboot.
PR NumberSynopsisCategory: Kernel MX virtual-chassis PRs
1645671Pseudo devices connected on ud and ut Interfaces stay down after hosting FPC was restarted
Product-Group=junos
In MX-VC, if FPC enabling tunnel service is restarted, Pseudo devices connected on ud and ut Interfaces on the FPC stay down and never become up.
PR NumberSynopsisCategory: Key Management Daemon
1719216A stale nat-long-route entry is present in the device causing incoming packets to be dropped
Product-Group=junos
On all MX platforms with MS-MPC cards, When there is an active NAT (Network Address Translation) enabled IPSec (IP security) tunnel already present for a particular service-set, any change in the outside logical interface (IFL) becomes a stale entry in the forwarding table causing IKE (Internet Key Exchange) control and data traffic to drop.
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: 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
PR NumberSynopsisCategory: Label Distribution Protocol
1666506LDP session stuck in non-existent state when router has multiple addresses configured on loopback interface
Product-Group=junos
When statically configured LDP neighbour and sessions transport address exists between two routers that is having multiple loopback addresses may cause LDP stuck in non-existent state. Deactivating and activating the LDP neighbour configuration can cause LDP session to remain stuck in the non-existent state.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1686654Subscribers are not able to connect to the device after the device reboot
Product-Group=junos
Due to a rare timing issue all subscribers may fail to connect and get suck in init state after reboot of MX broadband network gateway (BNG).
1708794License expire error will be observed after upgrade
Product-Group=junos
On all Junos and Junos OS Evolved platforms, license expire error will be observed after the upgrade.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1678716'show interfaces diagnostics optics ' shows all 0 on 100/400G port on MPC10E card.
Product-Group=junos
On MPC10E card, the port 4 can operation in either 100G or 400G speed. In certain scenario a stale QSFP56 identifier is left in PFE. It can cause the "show interfaces diagnostics optics " shows all 0 even if 100G QSFP-28 is inserted and the port is up.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1601096Traffic loss from primary to backup path and vice versa
Product-Group=junos
On all Junos and Junos Evolved platforms, Make-Before-Break operation is added for primary path by this PR for the scenario where the LSP secondary path is active and carrying the traffic and the LSP primary path needs to be resignal.
1659340LSPs are getting stuck in a down state after deactivating/activating protocol BGP
Product-Group=junos
On all Junos and Evolved platforms, when deactivating and activating protocol BGP (Border Gateway Protocol) it impacts the dynamic MVPN (Multicast Virtual Private Network) P2MP (point-to-multipoint communication) LSPs to stuck in the down state which leads to MVPN traffic loss.
PR NumberSynopsisCategory: MPLS Openconfig part of RPD.
1667844The RSVP interfaces are not streamed when removing the interface configuration
Product-Group=junos
On all Junos and Junos Evolved platforms, when walking through the bandwidth-reservation leaf in RSVP-TE interface attributes sensor path, there was no check to handle the null case and close that particular streaming and move on to the next interface/sensor path when that particular interface is deleted for which the values are being streamed out. Due to this, stale entries for the RSVP interface paths are streamed out if the interface is deleted. This leads to Open Config Telemetry-related issues.
PR NumberSynopsisCategory: Multicast for L3VPNs
1647149The routing protocol process might stop working when de-activating and activating the same provider tunnel from one to another instance in a single commit
Product-Group=junos
On all platforms when de-activating and activating the same provider tunnel from one to another instance in a single commit, the routing protocol process might stop working.
PR NumberSynopsisCategory: MX Timing software
1631274PTP (Precision Time Protocol) might not lock on MX with MX-MPC2E-3D-P and MPC2E-3D LC
Product-Group=junos
On all MX platforms with MX-MPC2E-3D-P and MPC2E-3D LC linecards, traffic might be flapping between ACQUIRING and HOLDOVER states while PTP with telemetry NPU is enabled.
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.
1704606A transit PTP packet is modified when passing through an MPC5E and MPC6G line card 100G ports part of PTP boundary/ordinary clock configuration
Product-Group=junos
On Junos MX240/MX480/MX960/MX2020/MX2008/MX2020 platforms with MPC5E/MPC6E line-cards at 100G ports, Precision Time Protocol over IPv4/6 (PTPoIPv4/6) and Precision Time Protocol over Ethernet (PTPoE) encapsulations are enabled by default when "phy-timestamping" is configured. Since both of these encapsulation types are enabled on the interface, the transit PTPoIPv4/6 packets passthrough to the through PTP configured interfaces get interpreted and timestamped incorrectly, leading to clock drift at the end of the PTPoIPv4/6 consumer side. In an ideal situation, the transit PTPoIPv4/6 packets should be sent forth as normal packets without being altered.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1681250The traffic loss duration increases during the LSP switchover
Product-Group=junos
On all Junos platforms, the traffic loss duration increases during the LSP switchover. The time consumption for processing indexed NH was more which got reduced due to this fix.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1669072Junos OS: NFX Series: 'set system ports console insecure' allows root password recovery (CVE-2023-28972)
Product-Group=junos
An Improper Link Resolution Before File Access vulnerability in console port access of Juniper Networks Junos OS on NFX Series allows an attacker to bypass console access controls. Please refer to https://supportportal.juniper.net/JSA70596 [juniper.net] for more information.
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.
1717710Unable to take recovery snapshots after USB upgrade is performed on ACX710
Product-Group=junos
On ACX710 platform, the OAM (Operations, Administration and Maintenance) volume seems unpopulated when an upgrade is performed with USB (Universal Serial Bus) drive or zeroize media. This leads to failure in taking recovery snapshots.
PR NumberSynopsisCategory: IPv6/ND/ICMPv6 issues
1703940RE will crash when static route duplicates with an interface IP address
Product-Group=junos
On all Junos platforms, RE (Routing-Engine) will crash when a static route is added that duplicates with an interface IP address. RE crash will lead complete traffic loss.
1704114The next-hop is shown as unicast instead of reject even when the IPv6 neighbor is unreachable
Product-Group=junos
When a neighbor route is unreachable, the IPv6 neighbor state should have been changed back to HOLD, instead, it stays as unicast. This causes impact in the forwarding plane traffic.
PR NumberSynopsisCategory: TCP/UDP transport layer
1694463The vmcore crash observed in low memory conditions
Product-Group=junos
On all Junos platforms, when there are low memory conditions vmcore crash is observed which impacts the traffic.
1700438The TCP sessions for BGP are closed on the backup RE
Product-Group=junos
On all Junos Platforms, if the interface configuration is altered to switch from one routing instance to another it might result in the closing of BGP session on the Backup Routing Engine.
PR NumberSynopsisCategory: OSPF routing protocol
1682506Traffic loss is seen when the router in helper mode deletes the route for the router undergoing graceful restart
Product-Group=junos
On all Junos OS and Junos OS Evolved devices, when "no-strict-lsa-checking" is configured and Graceful Restart (GR) is triggered, the router in helper mode deletes the route for the router undergoing GR and results in the traffic loss.
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: Express Chip L3 software
1658317BFD session session-state is showing DOWN while checking Micro BFD Sessions with Authentication in Non-Distributed Mode
Product-Group=junos
BFD session session-state is showing DOWN when operating in centralized Mode. Packet loss may be seen.
PR NumberSynopsisCategory: Path computation client daemon
1675816In a rare case, 'pccd' will crash when the PCEP connection is down
Product-Group=junos
On all Junos and Junos Evolved platforms, on the intermediate device when connection towards Path Computation Element (PCE) is down, Path Computation Element Protocol (PCEP) session will be down resulting in pccd crash. Routing protocols are not impacted but pccd crashes.
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: PTX10K Routing Engine
1698894The communication between primary and backup Routing Engines breaks in the event of scale network churn
Product-Group=junos
On PTX Series routers and QFX Series switches with dual Routing Engines running Junos OS, high host-bound traffic can cause a memory issue. Because of low memory, the Address Resolution Protocol (ARP) entry add can fail. Due to this, the communication between the primary Routing Engine and backup Routing Engine breaks, causing redundancy failure in high network churn and GRES-enabled scenario.
PR NumberSynopsisCategory: Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1570587JUNOS : QFX5100-96s : Major alarm set, Fan x not spinning for the Fans logs are seen
Product-Group=junos
The error message of "Fan Not spinning at correct speed" encountered when the speed mismatch is seen in the device. We determine the speed match when the fan rpm is greater/lesser than expected RPM that we already have along with tolerance rpm
PR NumberSynopsisCategory: QFX access control list
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 PFE Class of Services
1688455The FPC crash would be observed when the same CoS configuration is applied with wildcard for all the physical interfaces and AE
Product-Group=junos
On all Junos platforms, in a scaled scenario when some of the ge/xe/et interfaces are members of Aggregated Ethernet (AE) and the Class of Service (CoS) forwarding-class-set configuration is applied with a wildcard for all the physical interfaces and AE, it would trigger a Flexible PIC Concentrators (FPC) crash which leads to traffic loss.
PR NumberSynopsisCategory: QFX L2 PFE
1696428Adding more than 256 VLANs as name tags on the same interface results in dcd crash
Product-Group=junos
On all Junos platforms, the dcd (device control daemon) process crash is observed when more than 256 VLANs as name tags are added on the same interface.
1723465PFE crash is seen on Junos when file-logging is disabled
Product-Group=junos
On Junos QFX5K platforms, when file-logging is enabled for ukern_trace handle and the logs are written continuously to the corresponding buffer due to a network issue, disabling file-logging for that handle will cause a PFE crash and will lead to a complete traffic loss.
PR 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.
1713133QFX5120-32C: dcpfe core observed after Restart l2-learning process
Product-Group=junos
The change introduced via PR1496368 has a software defect that is triggered when restarting the l2-learning process. When the process restarts, the l2-learning process may dump its core. There should be no impact to the system operation.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1688323Traffic loss is observed in IP fabric when there is a change in the underlay network
Product-Group=junos
On Junos QFX5K series platforms, configuration-change/protocol flapping/port flapping in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) can cause traffic loss (changes related to the underlay network).
1697244Assigning VNI to VLAN will cause a small number of packets lost on other VLANs on the same interface
Product-Group=junos
On Junos QFX5110 and QFX5120 devices, a small number of packets are lost when assigned VNI (VXLAN Network Identifier) to the VLAN (Virtual Local Area Network). There is a packet loss on incoming packets, but no packet loss on outgoing packets.
1712405VXLAN traffic gets dropped after new L3 VLANs are created
Product-Group=junos
Traffic black-holing in EVPN (Ethernet VPN) fabric when performing configuration of new VLANs, it is found that L3 VLANs are having IPV4 bits disabled.
PR NumberSynopsisCategory: QFX5100 Virtual Chassis
1679919PFE process crash might be observed on QFX5100 platforms
Product-Group=junosvae
On QFX5100 platforms (both stand-alone and VC scenario) running Junos, occasionally during the normal operation of the device, PFE (Packet Forwarding Engine) can crash resulting in total loss of traffic. The PFE reboots itself following the crash.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1696119Traffic drop is observed for the VCP ports when there is traffic congestion in the egress queues
Product-Group=junos
On QFX5110 with Virtual Chassis configured, if any of the egress queues 3 or 4 is congested it causes buffer stuck error messages and traffic drop on the VCP (Virtual Chassis port) ports.
1709938VC members are split when removing and inserting em0 cable
Product-Group=junos
On QFX5120-48YM, QFX5120-48Y-8C, QFX5120-32C and EX4650-48Y platforms, when the management em0 cable is removed and reinserted in the Virtual Chassis (VC) environment, the VC members will split into separate VCs. The VC members will remain in the split state for approximately 5 mins.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1638745EINVAL issue might be observed while installing a route with indirect next-hop (having no-forward type)
Product-Group=junos
On all Junos Evolved platforms when installing a route with indirect next-hop (having no-forward type), EINVAL (kernel is returning error 'EINVAL -- Bad parameter in request) issue might be observed.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1651483The rpd crash would be triggered during the BGP route resolution scenario
Product-Group=junos
On all Junos and Junos Evolved platforms, when Border Gateway Protocol (BGP) is enabled with the combination of both multipath-resolve and preserve-nexthop-hierarchy features, instead of freeing up the node it calls the function of nexthop-fast-reroute (FRR) and freeing up the nexthop node as well that results in recursive free of the same nexthop which triggers the rpd crash.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1687884The traffic drops are seen for the static route after VRRP failover when VRRP VIP is set as next-hop for that static route
Product-Group=junos
On all Junos and Junos OS Evolved platforms, the next-hop for a static route does not refresh at PFE (Packet Forwarding Engine) after VRRP (Virtual Router Redundancy Protocol) failover when VRRP VIP (Virtual-IP) address is used as the next-hop for the static route.
PR NumberSynopsisCategory: Resource Reservation Protocol
1690110Traffic is not load-balanced when one of the next-hop LSP is down
Product-Group=junos
On all Junos and Junos Evolved platforms, in the multi-LSP next-hop load-balance scenario, in case any one of the label-switched path (LSP) is down, the traffic will not be load-balanced to the rest of the LSPs, due to the weight of LSP next hops not being set correctly.
1703424Path Tear message is not forwarded by PLR to merge point which is causing data plane blackholing
Product-Group=junos
On all Junos and Junos OS Evolved platforms, the PLR (point of local repair)is not sending the pathtear message when the merge point supports enhanced FRR while the route reaching the neighbor is using a shortcut route under MVPN (Multicast Virtual Private Network) configured scenario.
PR NumberSynopsisCategory: RPM and TWAMP
1688479From MPC5E line card onwards PPE traps, sync xtxn errors and EDMEM read errors seen when the inline TWAMP is used and accessing the invalid address
Product-Group=junos
On Junos MX, from MPC5E line cards when the inline TWAMP (Two-way Active Measurement Protocol) inline service is used when the 25th bit is set under the virtual memory under PFE, causes PPE traps and sync xtxn errors and EDMEM read errors.
PR NumberSynopsisCategory: Secure Web Proxy functionality on Junos
1719703The flowd process crash is observed when the web proxy packet reinjection fails
Product-Group=junos
On SRX-branch series, SRX4100, SRX4200, and vSRX platforms, packet reinjection fails if the load on the system is high and the web proxy tries to reinject the packet.
PR NumberSynopsisCategory: IPSEC functionality on M/MX/T ser
1680775The dynamic tunnel route gets removed when a new tunnel is brought up for the same selector
Product-Group=junos
On M/MX platforms, a dynamic tunnel route (pointing to the inside interface) gets removed when a new tunnel is brought up for the same selector. When the ARI (Auto Route Insertion) route is added for two or more DEP (Dynamic End Point) tunnels belonging to two different service sets with the same selector (destination address), the ARI route gets overwritten by the tunnel which comes up last in the order, leading to traffic drop.
PR NumberSynopsisCategory: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1713725IPv6 Fragmentation is not working on MS-MPC/MS-MIC in DS-Lite scenario
Product-Group=junos
On all Junos MX platforms with MS-MPC/MS-MIC cards in DS-Lite(Dual-stack Lite) scenario , Address Family Transition Router (AFTR) always failed to fragment newly generated IPV6 packet that has packet size larger than mtu-v6 value. packet will be dropped and will not reach to the softwire initiator (B4)
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1655518SRv6 END.DT46 and END.DT4 configuration might not be Supported
Product-Group=junos
On PTX Junos platforms in Segment Routing IPV6 (SRv6) scenario, when END.DT46 and END.DT4 configured, traffic might be dropped.
1683003The policy-multipath route inherits the attributes of active-route but does not undergo resolution, causing an incorrect metric value
Product-Group=junos
When an active path undergoes resolution with policy-multipath configured, policy-multipath routes are generated which inherit the attributes of active-route and do not undergo route resolution.
1687287The rpd process crash is seen when the BGP SR-TE tunnel is marked for deletion
Product-Group=junos
On all Junos and Junos Evolved platforms, the crash is seen due to a sync failure between the Master and Backup RE when a BGP SR-TE tunnel is marked for deletion.
1720031The rpd process crash will be observed while creating/updating the PCEP tunnel
Product-Group=junos
On Junos and Junos OS Evolved platforms, when SR (Segment Routing) PCEP (Path Computation Element Protocol) provisional tunnel is configured along with the template but the template has delegation configured, then the PCEP update message received for creating/updating tunnels is causing the rpd process crash and tunnel creation/update will fail for PCEP provisional tunnel.
PR NumberSynopsisCategory: SRX branch platforms
1646943No system or chassis alarm will be seen when device booting from backup partition
Product-Group=junos
On Junos SRX branch platforms, when the device boots up from the backup partition, the alert message will not be notified in "show system alarm". This issue has been seen from Junos 19.4R2 release.
PR NumberSynopsisCategory: SRX5XX platform
1634965[SRX] SRX550HM interfaces LED of ge-0/0/6-9 will auto turn off after device bootup some minutes
Product-Group=junos
SRX550HM interfaces LED of ge-0/0/6-9 will auto turn off after device bootup some minutes.
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1636874The interface equipped with a QSA adapter might go down
Product-Group=junos
On all MX platforms with channelized interfaces, disabling laser for channels 1 to 3 of an interface equipped with a QSA module might put the entire optics in low power. As a result, transmit power of channel 0 as well becomes 0 and the link goes down. This happens because only channels 1 to 3 are not supported.
1689644A 1G port on a QSFPP-4x10G transceiver will be down sometimes after the FPC restart
Product-Group=junos
On MX204 device, a QSFPP-4x10G transceiver configured at 1G speed sometimes stays down after a FPC restart. Traffic will not pass through the port.
PR NumberSynopsisCategory: MX10002 Platform SW - Platform s/w defects
1721714BFD session failed when configured on the loopback sub interface
Product-Group=junos
On the MX10003 and MX304 platforms, BFD (Bidirectional Forward Detection) session failed to come up when configured on the loopback sub interface.
PR NumberSynopsisCategory: SRX-1RU platfom chassisd SW defects
1711467SRX4600 doesn't support ae interfaces
Product-Group=junos
On Junos SRX4600 platforms, ae interfaces doesn't come up or not work properly when configured in HA (High Availability) cluster mode.
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: ZT/YT pfe firewall software
1697404FPC crash will be observed when firewall filter is unconfigured and reconfigured with same index
Product-Group=junos
On Junos platforms with MPC10E/MPC11E/LC-9600 cards, Flexible PIC Concentrators (FPC) crash will be seen when frequent ADD/DELETE operations of filter are performed.
1726733Traffic drops with percent policer attached using list
Product-Group=junos
On Junos EX92xx and MX series platforms with MPC10, 11 and LC9600, traffic drops will happen with attachment of filter having percent policer via input-list/output-list.
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1713523When VPLS is enabled on the LT interface, unknown unicast traffic is forwarded rather than discarded
Product-Group=junos
On MX platforms with MPC10/MPC11/LC9600 line cards, when the Logical Tunnel (LT) interface is configured with family Virtual Private LAN Service (VPLS) and VLAN, unknown unicast traffic on this line card forwards the traffic instead of discarding it. Hence the services configured on the LT interface which will use unicast traffic are affected.
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1713958Unexpected load balancing of packets having GRE header
Product-Group=junos
On all Junos and Junos Evolved platforms, incorrect load balancing of packets is observed when the transit packet with GRE (Generic Routing Encapsulation) header having any header fields (checksum, sequence number, etc) other than GRE key is present.
PR NumberSynopsisCategory: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1692256PFE will be disabled whenever XQ_TOE CM error is being detected
Product-Group=junos
On specific line cards or devices with specific line cards MPC2E-3D-NG/MPC3E-3D-NG/MPC5E/MPC6E/EX9200-6QS/SRX5K-MPC3-100G10G/SRX5K-MPC3-40G10G, XQ_TOE CM errors were classified as 'Major' error which triggers disable-pfe action while XQ_TOE errors are classified as Minor error. Once disable-pfe action is triggered, all the interfaces on the impacted PFE will go down and traffic through that PFE will be impacted.
1720591In a rare case FPC crashes and reboots generating a core
Product-Group=junos
On all Junos platforms, in a rare scenario, GRES (Graceful Routing Engine switchover) may result in LACP (Link Aggregation Control Protocol) on the new master being down which may cause an FPC crash.
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1706446No network reachability when enabling the routing-service knob for PPPoE subscribers over AE
Product-Group=junos
On all Junos platforms configured with PPPoE subscribers, when the PPPoE (Point-to-Point Protocol over Ethernet) subscriber is configured on the AE (Aggregated Ethernet) interface while enabling the routing-service knob, the service will not get enabled and the subscriber traffic gets impacted.
PR NumberSynopsisCategory: Trio pfe qos software
1706494Severity reclassification of queuing ASIC XQSS and memory parity error auto recovery
Product-Group=junos
On Junos with MX platform using specific MPC7E/MPC8E/MPC9E/JNP10K-LC2101/JNP10003-LC2103/JNP10K-LC480 line cards in the event of a transient memory hardware issue, parity errors are generated which cannot be rectified by the ASIC. When the Flexible PIC Concentrators(FPC) encounters such an error, it will automatically deactivate the Packet Forwarding Engine(PFE) which leads to traffic impact.
PR NumberSynopsisCategory: Trio pfe stateless firewall software
1614480Filter related service will not work when the filter is deleted/re-added frequently for AE interface
Product-Group=junos
On MX platforms, during reboot, the AE ifls are first added, then deleted and again added, this flapping causes corner case where the filter attachment ipc has older AE ifl index on which the filter bind fails. Filter will not be attached to the interface, so any filter related service will not work.
1666966The MPC hosting an AE member interface with a shared bandwidth policer configured at the AE could crash upon encountering an HMC fatal error
Product-Group=junos
MX MPC7/8/9, MX204 MPC, MX10003 MPC, JNP10K-LC2101, EX9200 MPC hosting an Aggregated Ethernet (AE) member interface with a shared bandwidth policer configured at the AE could crash upon encountering a Hybrid Memory Cube (HMC) fatal error.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1669410Traffic drop is be observed with layer 2 circuit local switching with PS interface
Product-Group=junos
On MX platforms, when VLAN operations are enabled on the ingress interface and ingress and egress processing are done in the same PFE (Packet Forwarding Engine) instance, traffic drop is observed in layer 2 circuit local switching with PS (Pseudowire Subscriber Interface) interface scenario.
PR NumberSynopsisCategory: Junos Fusion Satellite Device Infrastructure
1682680The Junos Fusion Satellite device will be stuck in the SyncWait state
Product-Group=junos
On Junos MX, EX, and QFX platforms, post rebooting the device the Junos Fusion Satellite devices are trying to generate the ssh keys before clearing the old keys. The Satellite devices will not be responsive as they are stuck in the SyncWait state leading to traffic loss.
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
1629672The Create Bearer Request might be dropped on SRX platforms
Product-Group=junos
On SRX platforms, with GTP ALG (General Packet Radio Switching Tunnelling Protocol Application Layer Gateway) enabled, if Create session response is received with cause value among 17 to 19, Control Tunnel (C-Tunnel) might not get created and hence might drop further GTP messages.
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.
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: VSRX platform software
1711440VLAN tagging does not work for vSRX3.0 on HyperV Windows Server 2019 Datacenter
Product-Group=junos
VLAN tagging for vSRX3.0 on HyperV Windows Server 2019 Datacenter is not working.
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.
PR NumberSynopsisCategory: usf nat related issues
1646822NAT session reverse traffic fails due to NAT routes getting deleted from routing instance.
Product-Group=junos
With overlapping NAT pool configured with different NAT rules under different service sets, when service outside interface is moved between different routing instances (EX: from vr1 to default, and from default to vr1), NAT routes corresponding to the service-set in default routing instance are getting deleted, resulting in reverse path traffic failure for NAT sessions.
1718840The PPTP connection itself won't work when trying to establish PPTP connection along with DSLITE
Product-Group=junos
On Junos MX and SRX platforms with SPC3 cards, Point-to-Point Tunneling Protocol (PPTP) connection between client and server always failed along with Dual-Stack Lite (DSLITE) scenario. PPTP failure occurred due to Generic Routing Encapsulation tunnel (GRE) wrong call-id swapping that taken place by Address Family Transition Router (AFTR). Traffic will not pass through the tunnel at all as the tunnel does not establish.
 
 

21.2R3-S5 - List of Known Issues 

See TSB70818 [juniper.net]

Modification History

First Publication 2023-05-05