Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

20.2R3-S1: Software Release Notification for JUNOS Software Version 20.2R3-S1

0

0

Article ID: TSB18052 TECHNICAL_BULLETINS Last Updated: 15 Jul 2021Version: 4.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX
Alert Description:
Junos Software Service Release version 20.2R3-S1 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:

NOTE: 1. Due to software defects, we do not provide SRX1500 with this release
NOTE: 2. Due to EVPN/VXLAN software defects, Junos 20.2R3-S1 software images for the QFX5000s, the EX4600, and the EX4650 are not recommended for EVPN/VXLAN deployment.

Junos Software service Release version 20.2R3-S1 is now available.

20.2R3-S1 - List of Fixed issues

PR Number Synopsis Category: EX4300 PFE
1576022 DHCP packets with source IP as link-local address are dropped in EX4300
Product-Group=junos
On EX4300 Series switches with Multicast Listener Discovery (MLD) snooping enabled, when DHCP packets with source IP as link-local address are sent across EX4300, they will get dropped.
PR Number Synopsis Category: EX4300 Layer 2 implementation
1578421 The fxpc process might crash on QFX/EX platforms
Product-Group=junos
On QFX/EX series products using Broadcom chip based PFE (i.e., QFX3500/QFX3600/QFX5100/QFX5110/QFX5120/QFX5200/QFX5210/EX4300/EX4600/EX4650), if the VxLAN encapsulated DHCP broadcast packets are received or baseline configuration is loaded on the device, the Packet Forwarding Engine manager(fxpc) crash could be observed. This will impact the traffic.
PR Number Synopsis Category: Marvell based EX PFE L2
1579293 Some MAC addresses might not be aged out on EX4300 platforms
Product-Group=junos
On EX4300 platforms, when the number of MAC addresses learned in the system is close to the MAC limit of 65535, some MAC addresses might not be aged out even if the traffic stops and aging timeout occurs. It is a rare issue and hard to be reproduced.
PR Number Synopsis Category: EX2300/3400 PFE
1548159 Classifier is not programmed in the hardware and error logs may be seen in syslog
Product-Group=junos
On EX platforms except EX4300, when configuring Q-in-Q with vlan-id-list, classifier is not programmed and error logs "Setting vlan id failed" may be seen. All the packet entering this interface will not classify the packets to designated egress queue, but to the default queue. If the default queue is in congestion, traffic with video or voice service may be impacted.
1586341 DSCP Rewriting might fail to work on EX2300
Product-Group=junos
On EX2300-48 platforms with dual tags VLAN used, DSCP Rewriting might not work when QinQ traffic sent across different chip units (in Ex2300 one PFE has 2 chip units).
PR Number Synopsis Category: MX Services URL filter
1584377 Traffic might not get filtered properly when security-intelligence profile is configured on the MX platforms
Product-Group=junos
On MX platforms running Junos, traffic might not get filtered as per whitelist and blacklist. The issue happens while deactivating and activating the security-intelligence profile when web-filtering is configured on the box. During this, the whitelist and blacklist files from PE are not being added to the PFE filter causing the issue.
PR Number Synopsis Category: QFX Access control list
1576168 The QFX5000 line of switches might drop the DHCP packets in the static VXLAN scenario
Product-Group=junos
In the Static VXLAN with the QFX5000 scenario, the QFX5000 acted as the leaf device (also, functions as a VETP). If the DHCP packets are passed over the VXLAN tunnels between the VTEPs, it might be assigned the wrong classid in the VFI (Virtual Forwarding Instance) during the VXLAN tunnel termination operation, then the DHCP packets might be filtered wrongly by PFE and might be dropped after that.
PR Number Synopsis Category: QFX PFE CoS
1581187 The Buffer allocation for VCP ports might not get released in PFE after physically moving the port location
Product-Group=junos
After physical movement of the VCP interface from one port to another port without deleting VCP configuration from CLI, the buffer allocation for VCP ports not getting released in PFE.
1585361 The dscp classifier does not work and all packets are sent to a single queue.
Product-Group=junos
On the QFX5000 line of switches, when a Layer 3 interface with multiple logical interfaces is deleted and re-configured with custom classifier, queue classification will not work and traffic will take best-effort queue.
PR Number Synopsis Category: QFX PFE L2
1574435 On the QFX5000 line of switches, software forwarded VXLAN decapsulated packets contains illegal length.
Product-Group=junos
On the QFX5000 line of switches, software-forwarded VXLAN de-encapsulated packets (such as STP and DHCP) received on a VTEP interface might be forwarded with illegal length. During de-encapsulation, the packet length might not be adjusted to the length on the inner payload. The packet gets forwarded by adding trailer for the remaining length.
1575976 The DF might not forward BUM traffic on QFX5000 series switches
Product-Group=junos
If AE interfaces in SP style are configured with ESI, after deleting a couple of IFLS on the AE interface and then disable the member port of the AE interface on the peer, the DF might not forward BUM traffic from remote VTEP on QFX5000 Series switches.
1582473 MAC addresses learnt from the MC-LAG client device might keep flapping between the ICL interface and MC-AE interface after one child link in the MC-AE interface is disabled.
Product-Group=junos
On QFX/EX series products using Broadcom chip based PFE (i.e., QFX3500/QFX3600/QFX5100/QFX5110/QFX5120/QFX5200/QFX5210/EX4300/EX4600/EX4650), if Multichassis link aggregation group (MC-LAG) is configured, and the interchassis link (ICL) interface is a physical interface instead of an aggregated Ethernet (AE) interface, after one of the child links in Multichassis Aggregated Ethernet (MC-AE) interface on one of MC-LAG peers is disabled, the MAC addresses learnt from MC-LAG client device might keep flapping between the ICL interface and MC-AE interface. It could cause traffic drop when MAC addresses are learnt on ICL interface. This issue is only exposed in Junos release having the code change in PR 1504586 (which is fixed in Junos: 17.3R3-S9 17.4R3-S3 18.1R3-S11 18.2R3-S6 18.3R3-S3 18.4R2-S6 18.4R3-S6 19.1R3-S2 19.2R3 19.3R3 19.4R3 20.1R2 20.2R2 20.3R1 20.3X75-D10 20.4R1) but not having fix of PR 1582473.
1585320 Traffic drop might be seen on the AE interface
Product-Group=junos
On QFX5120 platform with 'aggregated-ether-options dlb' configured on an AE interface, if deactivate/delete the AE interface and then activate/add the AE interface, the traffic on that AE interface might be dropped.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1579736 The dcpfe process might crash when any interface flaps.
Product-Group=junosvae
On QFX5k switches, the dcpfe process might crash in some rare case when there is any interface flap.
PR Number Synopsis Category: Fireall support for ACX
1573956 ARP traffic exceeding the policer limit is not discarded on ACX platforms
Product-Group=junos
ARP is not getting resolved and ARP traffic exceeding the policer limit is not discarded on ACX platforms, when ARP policer is applied on the ingress interface and ARP traffic is sent at a rate higher than the policer limit.
PR Number Synopsis Category: "agentd" software daemon
1580003 Authentication may fail if the password contains special characters
Product-Group=junos
On all Junos platforms with Telemetry enabled, if JSD (JET service process) sends a username or password with any of these 5 special characters < > & ? \ for authentication, the authentication may fail. In this case, the client login via the gRPC channel might fail due to the failed authentication.
PR Number Synopsis Category: a20a40 specific issue
1568183 On SRX5k, the alarm "Power Budget:Insufficient Power" may be raised incorrectly when the second SCB does not contain an RE
Product-Group=junos
On SRX5k the power budget calculation incorrectly assumes that all SCB cards contain a Routing-Engine (RE). Hence the available power budget is incorrectly decreased by 90W for each SCB which does not contain an RE.
PR Number Synopsis Category: BBE interface related issues
1577289 Traffic loss might be seen when subscriber service over AE bundle interface(s)
Product-Group=junos
On MX platforms with subscriber scenario, traffic loss might be seen if configuring dynamic-profile over AE bundle interface(s) (several thousand subscribers upon on the ports). This defect could be seen when changing AE child links while the kernel is busy deleting the old AE link members, and not pseudo ifl (logical interface) with new AE member links.
PR Number Synopsis Category: BBE multicast related issues
1587023 The rpd core may be observed if executing the command "show igmp continuous stats" after GRES
Product-Group=junos
On all Junos platforms, when IGMP is configured, if executing the command "show igmp continuous stats" to fetch the IGMP continuous stats after GRES, rpd core might be seen.
PR Number Synopsis Category: Bi Directional Forwarding Detection (BFD)
1541851 The BFD sessions over IRB interface stuck in Init state with FRR errors incrementing
Product-Group=junos
In the EVPN-VXLAN scenario with QFX5000 as a leaf, if the Inline BFD sessions are configured over the IRB interface of VXLAN, the BFD sessions over the IRB interface stuck in Init state with FRR errors incrementing.
PR Number Synopsis Category: Border Gateway Protocol
1578740 The rpd may crash when two or more routing instances are deleted in one shot
Product-Group=junos
When a device has some routing-instances configured with flow and others with minimum configuration (no protocol, no flow, no other important configuration), the rpd might crash when those routing-instances are deleted in one shot.
1581578 BGP replication might be stuck in rare and timing conditions
Product-Group=junos
On all platforms with dual Routing Engines running Junos OS or Junos OS Evolved, BGP Nonstop-Routing replication might be stuck in a rare and timing case. BGP session(s) on the primary Routing Engine are stuck in "SoWait" state, and BGP session(s) on the backup Routing Engine cannot sync with the primary Routing Engine. From the BGP peer side, the BGP session(s) will break after hold-time expiry (90 seconds by default). This defect could be seen after the following series of events happen. * BGP NSR replication starts while primary Routing Engine (BGP session) is busy reading packets (i.e. protocol data unit). * Primary Routing Engine (BGP session) requests to stop reading at PDU boundary. * While BGP session on primary Routing Engine is waiting to read complete packet (remaining bytes), the TCP sync connection (between primary and backup BGP) flaps (i.e., PDU boundary is NOT read before the flap).
1581794 The rpd might crash in BGP and MPLS scenario
Product-Group=junos
In BGP and MPLS scenario, if a BGP route's forwarding next-hop has no IFA associated (e.g. dynamic tunnel forwarding next-hop etc), the rpd might crash if "ping mpls bgp" is used.
1583630 On rare occasion, RPD core may be observed on backup RE after loading a new image
Product-Group=junos
A BGP core file (or dump file) may be seen after loading a new image on the backup Routing Engine. This is a timing issue. These three events need to happen to generate this core file: 1) an interface flap. 2) a peer over this interface has not been synced with primary Routing Engine. 3) GP triggers multipath calculation before the sync and uses route that has not been marked to be deleted from this peer as a multipath contributor.
1585265 The rpd might crash in BGP multipath scenario if the single hop EBGP peer goes down
Product-Group=junos
On all Junos and Junos Evolved platforms during BGP multipath scenario, if an interface for a single hop EBGP peer goes down, the rpd might crash on the backup RE due to a rare timing issue. When the issue occurs, redundancy might be impacted.
PR Number Synopsis Category: Express Broadway PFE L3
1584042 The packets might be dropped by PFE of PTX5000 after changing the queue of IEEE-802.1ad classifier on FPC-PTX-P1-A or FPC2-PTX-P1A
Product-Group=junos
In the PTX5000 with behavior aggregate (BA) classification scenario, the COS queue-num 3 is applied to TTL packets by default. If the IEEE-802.1ad classifier is configured for the packets which are mapped to the CoS output queue-num 3 (The PFE internal hostbound queue classification code-points=1100), in a very rare case, if some TTL expired packets are passed via the other interfaces which are also mapped to the same hostbound queue (in this case, queue 3), the packets will be dropped by PFE because of some TTL expiry packets in the same queue.
PR Number Synopsis Category: Virtual-chassis platform/chassisd infrastructure PRs for MX
1569556 JDI-RCT:M/Mx: not able to set member-id as RE is in synching mode forever when its having invalid VC data( error: Command aborted. VC configuration synch to backup RE in progress, try after 120 secs. )
Product-Group=junos
New SCB cards may have uninitialized VC Data Blocks, preventing setting the member-id when configuring as a MX-VC for the first time.
1587499 Unable to configure pseudowire interface on an MX10003 in virtual chassis mode
Product-Group=junos
An MX10003 in virtual chassis (VC) mode, configuring a pseudowire interface over a logical tunnel (LT) or a redundant logical tunnel (RLT) results in a commit error that states that the anchor point interface is not configured, even when the LT or RLT interface is operationally up. The issue is not present on MX10003 in non-VC mode.
PR Number Synopsis Category: Class of Service
1568661 FPC crash might be observed after the "show class-of-service" command
Product-Group=junos
When "show class-of-service scheduler-resources fpc" is issued, the FPC might crash and the core-dump is generated.
PR Number Synopsis Category: Enhanced Broadband Edge support for cos
1582356 The bbe-smgd crash might be seen after subscriber log out due to a rare timing issue on MX platforms
Product-Group=junos
On MX platforms with subscribers over the MPLS pseudowire scenario and CoS (Class of Service) configured, the bbe-smgd process might crash on both routing engines due to a rare timing issue after subscriber logout or when FPC reboot is performed on the device.
PR Number Synopsis Category: QFX Access Control related
1589678 Packet loss could be observed on dynamically assigning VoIP vlan
Product-Group=junos
On all Junos platforms, if the received dynamically assigned VoIP vlan is same as the configured static VoIP vlan, packet loss could be observed for the connected IP phone on re-authentication for the VoIP session.
PR Number Synopsis Category: MVRP
1582115 The voice VLAN might not get assigned to the access interface
Product-Group=junos
On all Junos platforms with Multiple VLAN Registration Protocol (MVRP) enabled, when VoIP is configured for the dynamically learned VLANs, the dynamically learned voice VLAN might not get attached to the access interface.
PR Number Synopsis Category: dhcpd daemon
1575740 The DHCP client will be offline for 120 seconds after sending the DHCPINFORM message in the DHCP relay scenario
Product-Group=junos
In a Juniper device acting as DHCP relay scenario, if the DHCP clients are attempting the DHCPINFORM message to DHCP server to obtain an additional configuration state that was not present in their lease binding, an internal temporary client entry will be created in the DHCP relay. If the DHCP relay is not able to properly process the DHCP ACK message from the DHCP server, the subsequent DHCPDISCOVER messages sent from the DHCP client will be dropped by the DHCP relay for 120 seconds.
1578543 The DHCP ALQ is not working as expected
Product-Group=junos
On MX Series platforms, the DHCP active-leasequery(ALQ) feature is not working as expected.
PR Number Synopsis Category: JUNOS Dynamic Profile Configuration Infrastructure
1584457 After performing NSSU, "timeout waiting for response from fpc0 " error message is seen while checking version detail
Product-Group=junos
After NSSU or Image upgrade to 21.1R1, show version details fails with "timeout waiting for response from"
PR Number Synopsis Category: EVPN control plane issues
1562160 The rpd might crash under EVPN-VPWS environment
Product-Group=junos
Within Ethernet VPN-Virtual Private Wire service (EVPN-VPWS) environment, if the interface assigned to VPWS instance is changed from single-homed access to multi-homed access, rpd might crash. Traffic could be self-recovered if rpd restart is success.
1570883 The multicast traffic loss might be seen in EVPN-VXLAN scenario with CRB multicast snooping
Product-Group=junos
On MX and EX92 platforms, if multicast packet replication occurs in IRB egress interface in EVPN-VXLAN scenario with CRB multicast snooping, the ether-type of the inner VXLAN packet is getting changed. It might cause multicast traffic loss and VXLAN traffic flooding.
PR Number Synopsis Category: EX Chassis chassism/chassisd
1556558 FPC with power related faults might get on-lined again once Fabric Healing has off-lined the FPC
Product-Group=junos
In rare cases of power related failures on the FPC, Fabric Healing will detect and try to heal this fault condition by performing an offline/online FPC event. If the same FPC fails again within 10 minute period, fabric auto-healing attempt is considered failing and the FPC will get off-lined to avoid further operational impact. If during the power offline event, the faulty FPC gets disconnected ungracefully due to the hardware power fault, the FPC might attempt an on-lined request again after 5 minutes. There may be traffic impact due to this issue.
PR Number Synopsis Category: EX4400 platform
1573889 EX4400: Mgmt LEDs are not working as per expectations
Product-Group=junos
Below is the status of management LED when speed is set to: 1. 10m - Activity LED is not blinking when ping/traffic is runnig (instead it is remaining steady GREEN) 2. 100m - Activity LED is blinking without any ping/traffic.
PR Number Synopsis Category: Express PFE CoS Features
1588514 There might be higher latency in traffic flow than configured or default value
Product-Group=junos
On PTX5000 and PTX10003 platforms, higher latency than configured or default value might be observed in the traffic passing through the device. This issue is seen as the VOQ (Virtual output queue) size is not correctly set in ASIC.
PR Number Synopsis Category: Enhanced Broadband Edge support for firewall
1580826 More than one subscriber on same vlan fails to apply same FWF Template
Product-Group=junos
On all MX platforms with subscriber management, only one subscriber can login, but when another subscriber logs in and the same services are applied via radius, the service fails due to duplicate service-accounting and UID.
PR Number Synopsis Category: Express ASIC interface
1578511 Traffic loss might be observed on the PTX5000 platform
Product-Group=junos
On PTX5000 with '15x100GE/15x40GE/60x10GE QSFP28' PIC on FPC type 3, when the port is configured in 4x10G mode (using QSFP+) and one of the 10G channels detected a clear of Rx LOS (Loss Of Signal), the traffic might be dropped on all the four 10G channels.
PR Number Synopsis Category: IDP attack detection in the subscriber qmodules
1588450 Application-identification related signatures might not get triggered
Product-Group=junos
On SRX-Series devices, some of the application-identification(appid) related signatures might not get triggered when there is an update of IDP signature package/application-identification version to 3372.
PR Number Synopsis Category: Interface Information Display
1561065 The input errors counter command on the monitor interface command does not work
Product-Group=junos
"Input errors" counter on "monitor interface" CLI not working. After fixing this issue, 'Input errors' shows sum of all input errors. This is a common issue of ge-/xe-/et interfaces.
PR Number Synopsis Category: Internet Group Management Protocol
1586631 The rpd process might crash after committing with the configured static group 224.0.0.0.
Product-Group=junos
On all Junos and EVO platforms, the rpd process crash may occur instead of showing commit configuration failure and generating an error log when an invalid static group 224.0.0.0 is configured under the IGMP protocol.
1588555 The multicast traffic loss could be observed after ISSU is being performed
Product-Group=junos
On all Junos/EVO platforms, in a rare scenario after the ISSU is being performed, the multicast forwarding for the subscribers over the demux interface might get stopped and there won't be any IGMP membership for the affected groups and subscribers.
PR Number Synopsis Category: MX Inline Jflow
1588093 The Aftcore messages might be seen after the MPC10E/MPC11E line card comes up
Product-Group=junos
On MX platforms, the AftCore messages might be seen after the MPC10E/MPC11E line card comes up. These messages will not affect traffic forwarding and Jflow learning/export. But if the 'nexthop-learning' knob is configured, Jflow will not report the correct outgoing interface (OIF)/Gateway (GW) when the flow destination is reachable through multiple paths.
PR Number Synopsis Category: ISIS routing protocol
1571395 There might be 10 seconds delay to upload the LSP on the point-to-point interface if rpd is restarted on its direct neighbor
Product-Group=junos
On platforms running Junos OS or Junos OS Evolved with IS-IS overload timeout configured, when the rpd process is restarted on its direct neighbor, there may be a 10-second delay to upload the LSP on point-to-point interfaces.
PR Number Synopsis Category: jdhcpd daemon
1576417 DHCP relay drops packets during the renewal DHCP process
Product-Group=junos
On all platforms with Windows DHCP scenario, DHCP-ACK for DHCP renew packet might be dropped on DHCP Relay device. Because the Suboptions 1 and Suboptions 11 of DHCP Option 82 are not handled properly in DHCP renew process.
PR Number Synopsis Category: Flow Module
1584299 Unexpected traffic drop happens if both PMI and flexible-vlan-tagging are implemented
Product-Group=junos
On SRX platforms, PowerMode IPsec (PMI) and flexible-vlan-tagging on Aggregated Ethernet (AE) interface could not be implemented at the same time. It could cause IPsec traffic drop if both PMI and flexible-vlan-tagging are enabled.
PR Number Synopsis Category: IPSEC/IKE VPN
1577550 The from-self packet might be dropped when it forwards through an IPsec VPN tunnel
Product-Group=junos
On SRX5000 Series devices with SPU-forwarding enabled, the from-self packet might be dropped when it passes through an IPsec VPN tunnel.
PR Number Synopsis Category: Security platform jweb support
1511853 Junos OS: J-Web allows a locally authenticated attacker to escalate their privileges to root. (CVE-2021-0278)
Product-Group=junos
An Improper Input Validation vulnerability in J-Web of Juniper Networks Junos OS allows a locally authenticated attacker to escalate their privileges to root over the target device. Please refer to https://kb.juniper.net/JSA11182 for more information.
PR Number Synopsis Category: Platform infra to support jvision
1580120 MX-VC: gRPC-based /components/ sensor output is missing lot of data
Product-Group=junos
In an MX Series Virtual Chassis, the /components sensor does not emit complete data due to collateral that is specific to the Virtual Chassis.
PR Number Synopsis Category: Layer 2 Control Module
1583092 The l2ald crash if a specific naming format is applied between a vlan-range and a single vlan
Product-Group=junos
On all L2NG platforms (EX2300/EX3400/EX4300/EX4600/EX9200/QFX3500/QFX3600/QFX5100/QFX10000 etc.) with 'vlan-range' configured, if a single vlan is defined with the format [previously_defined_vlan_range_name]-vlan-[any_string_value]. When an interface already assinged to the vlan-range is trying to be assinged to the single vlan, the layer2 address learning daemon (l2ald) might crash.
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1584874 Bridge domain names information is not displayed properly in "show bridge statistics instance".
Product-Group=junos
Under the conditions of the bridge domains in the virtual-switch type instance having "vlan-id-list", Bridge domain names information is not displayed properly in "show bridge statistics instance".
1584876 After changing configuration, "show bridge statistics" shows extreme larger value.
Product-Group=junos
When the same bridge setting is changed from default-instance to logical-system as it is, "show bridge statistics" may show extreme larger value.
1587610 The SNMP trap for MAC notifications may not be generated when an interface is added explicitly under switch-options
Product-Group=junos
On Junos L2NG EX platforms and QFX platforms, the SNMP trap may not be generated for MAC notifications if "set switch-options interface no-mac-notification" is configured first and an interface is added explicitly without no-mac-notification under switch-options hierarchy at last.
PR Number Synopsis Category: lacp protocol
1551925 AE interface flap might be seen during NSSU
Product-Group=junos
On the EX2300/EX3400/EX4400 platforms, AE (Aggregate Ethernet) interface flap might be seen during NSSU (Nonstop Software Upgrade) for AE with LACP (Link Aggregation Control Protocol) configured. The issue results in traffic outage and flaps in other protocols (e.g. OSPF) running over this AE.
PR Number Synopsis Category: Label Distribution Protocol
1582037 Sub-optimal routing issues might be seen in case LDP route with multiple next-hops
Product-Group=junos
In the case of the LDP route with multiple next-hops, the last NH weight in table mpls.0 is not set properly when the total number of LDP NHs is multiple of 8 + 1, e.g., 9, 17. This might lead to some backup route active as the primary path, which might result in a traffic loop.
PR Number Synopsis Category: lldp sw on MX platform
1591387 The LLDP packet might loss on the EX-4300MP platform if configuring LLDP on the management interface
Product-Group=junosvae
On the EX-4300MP platform, if configuring LLDP on the management interface, the management interface will not transmit any LLDP PDUs to the peer. This issue might cause LLDP packet loss.
PR Number Synopsis Category: MPC11 ULC fabric software related issues.
1565223 On the MX2010 or MX2020 routers, the following error message might be observed after switchover with GRES/NSR: CHASSISD_IPC_FLUSH_ERROR.
Product-Group=junos
On MX2010 and MX2020 routers with the MPC11E line card, the IPC communication between the new primary Routing Engine and MPC11E might break after switchover with GRES/NSR.
PR Number Synopsis Category: Multicast Routing
1577461 Multicast traffic loss might be observed due to logical PIM decapsulation interface is not created as expected
Product-Group=junos
In multicast environment, with tunnel-services enabled on two PICs, the logical PIM decapsulation interface is not created after deleting/deactivating/restarting one of the PIC hosting the PIM decapsulation interface.
PR Number Synopsis Category: For multicast snooping on MX
1583207 With IGMP snooping implemented, there is unexpected jitter issue that could cause traffic loss
Product-Group=junos
On all Junos platforms running 19.4R1 onward, with IGMP snooping implemented, there is unexpected more than 1 second for network convergence. The reason of the issue is that multicast route is not installed into Kernel Routing table (KRT) and synchronized efficiently. This issue could cause jitter problem and initial traffic loss. Please refer to Workaround to avoid this issue.
PR Number Synopsis Category: Multicast for L3VPNs
1579963 The rpd might crash in the NG-MVPN scenario on all Junos/Evo platforms
Product-Group=junos
The routing process (rpd) might crash and generate core-dumps in Next Generation Multicast Virtual Private Network (NG-MVPN) environment configured with 'convert-sa-to-msdp' knob which converts source active from MVPN routes to MSDP SA. The crash might be triggered under rare circumstances when a delete is requested for locally originated MSDP source active (SA) but the SA is already deleted.
PR Number Synopsis Category: OS IPv4/ARP/ICMPv4
1564323 "Last flapped" timestamp for interface fxp0 gets reset every time "monitor traffic interface fxp0" is executed
Product-Group=junos
"Last flapped" timestamp for interface fxp0 gets reset every time "monitor traffic interface fxp0" is executed.
1584115 VRRP device originally taking slave role might cause destination IP unreachable after VRRP mastership switch-over
Product-Group=junos
On all Junos platforms with redundant routing engine (RE), after Virtual Router Redundancy Protocol (VRRP) mastership switch-over, Address Resolution Protocol (ARP) request might not be forwarded by VRRP enabled gateway device originally as VRRP backup. There is packetloss when this issue happens.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1563647 Memory corruption of any binary in /usr/bin/ or /usr/sbin/ may be triggered when a recovery snapshot is being copied to the OAM volume
Product-Group=junos
Memory corruption of a binary from /usr/bin/ or /usr/sbin/ directory can occur if such binary is invoked when a recovery snapshot creation is in progress. The exact symptoms will be different depending on the exact binary and JUNOS version - some programs will show an error, and some programs will crash every time it is executed. Such memory corruption will be persistent until the affected Routing Engine is restarted. Please refer to TSB17954 (https://kb.juniper.net/TSB17954) for further details.
1579331 EX4400: Under some conditions, the FPGA reset reason may be incorrectly shown in console logs as 0.
Product-Group=junos
EX4400: Under some special conditions, such as boot from OAM volume following a graceful/warm reboot, the FPGA reset reason incorrectly shown in console logs as 0.
PR Number Synopsis Category: Kernel Tunnel Interface Infrastructure
1584969 Traffic impact might be seen when tunnel-services bandwidth is configured
Product-Group=junos
On all Junos platforms, when the 'bandwidth' value is modified under the 'tunnel-services' knob, it might take a long time (approximately 35-40 minutes) to bring up IFD (physical interfaces) and result in a traffic impact, particularly multicast traffic.
PR Number Synopsis Category: OSPF routing protocol
1568157 The rpd memory leak may be observed during CLI/ephemeral commits in OSPFv2 scenario
Product-Group=junos
On all Junos/Junos Evolved platforms, rpd memory leak may be observed during CLI/ephemeral commits. It could be seen when the submitted configuration of OSPFv2 can not be successfully parsed. The rpd could crash when running out of memory in Routing Engine, which is an extreme corner case since it needs a massive amount of commits to trigger (e.g. 4000 times).
PR Number Synopsis Category: Protocol Independant Multicast
1568750 The rpd might crash continuously when MoFRR is configured along with TI-LFA
Product-Group=junos
On all Junos platforms, when Multicast-Only Fast Reroute (MoFRR) and Topology Independent Loop-Free Alternate (TI-LFA) are enabled together, the rpd might crash continuously. This might lead to traffic and service impact as the routing protocol daemon doesn't recover.
PR Number Synopsis Category: PTP related issues.
1575055 PTP might be stuck in Phase acquiring state after ISSU upgrade
Product-Group=junos
On MX platforms with MPC7/8/9/LC2101/LC2103 line cards or MX204/MX10003 platforms, PTP might fail and stuck in Phase acquiring state after an ISSU upgrade.
PR Number Synopsis Category: analyzer on QFX 5100,5200, 5110
1576327 Analyzer is not working on all Junos QFX5K platforms
Product-Group=junos
On all Junos QFX5K platforms, when the ECMP(Equal-cost multipath) is enabled, the analyzer is remote switch port and the analyzer's next hop is IRB interfaces, the analyzer function may get failure.
1580473 While mapping analyzers to the channelized port, mirror might not work properly
Product-Group=junosvae
On AS7816-64X/QFX51xx/QFX52xx Series platforms, the analyzer may not work properly when port channelization is done after the analyzer configuration and with these newly created ports new analyzer is created.
1589579 When the deleted aggregated Ethernet interface is not getting deleted (mirror trunk group) in the hardware for the analyzer input aggregated Ethernet interface.
Product-Group=junos
When member interface from AE is deleted and if that AE interface is input to analyzer session, mirroring will continue to happen for the removed member interface also.
PR Number Synopsis Category: QFX L2 PFE
1546572 The dcpfe process might crash on QFX10K platforms
Product-Group=junos
On QFX10K platforms the dcpfe might crash if with traffic bring all SIBs offline and then bring them online, it also might happen during the reboot of FPC.
1580114 The dcpfe process crashes while checking the virtual tunnel-nh packet status.
Product-Group=junos
vty show commands are executed in different context than pfeman. There is a possibility that data might be changed/deleted in pfeman context which might trigger a crash during show command execution.
1580352 DHCP packets might be dropped if dynamic filter 'dyn-dhcpv4_v6_trap' is applied on the interface
Product-Group=junos
DHCP packets might be dropped when dynamic filter 'dyn-dhcpv4_v6_trap' is applied and software-based learning CLI is enabled on the interface.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1587609 Packet DMA memory leak might be seen in EVPN-VXLAN scenario after receiving some packets
Product-Group=junos
On QFX platforms, in EVPN-VXLAN scenario, packet DMA memory leak might be seen after receiving some packets. When the leak is up to 99%, it will cause protocols to stop working.
PR Number Synopsis Category: QFX EVPN / VxLAN
1582017 The traffic may not be load-balanced properly in an EVPN overlay-ecmp setup
Product-Group=junos
On QFX5100/QFX5110/QFX5120/QFX5130 and EX4300/EX4600/EX4650 devices with overlay-ecmp configuration for EVPN-VxLAN, the traffic might not get load-balanced correctly when multi traffic streams with different source address are sent across the fabric.
PR Number Synopsis Category: QFX VC Infrastructure
1559172 The VCF might become not stable
Product-Group=junos
When adding a new leaf to VCF of 12 members without setting its VC mode to 'fabric' on QFX5100 platforms, it might cause the VCF to become not stable.
PR Number Synopsis Category: RPD Next-hop issues including indirect, CNH, and MCNH
1582210 Communication between two CEs might be failed when BGP rib-sharding is enabled
Product-Group=junos
With Border Gateway Protocol (BGP) routing information base (RIB) sharding configured, adjusting route-distinguisher (RD) in provider edge (PE) side might cause routes from customer provider edge (CE) not programmed in forwarding information base (FIB). As a result, unexpected packet loss could happen.
PR Number Synopsis Category: RPD policy options
1565629 The rpd might crash when the deletion of routing table occurs
Product-Group=junos
The rpd might crash when the deletion of routing table occurs.
1583535 bbe-smgd - dymanic-profile NACK due to config error reading address mask prefix-length in policy-options/policy-statement
Product-Group=junos
The bbe-smgd fails when reading the configuration for address mask prefix-length configured in a policy statement. This causes the service profile to fail.
PR Number Synopsis Category: show route table commands, tracing, and syslog facilities
1565425 The KRT log file might continue to grow after removing the KRT log configuration
Product-Group=junos
If kernel routing table (KRT) trace logs are configured and later removed, they will remain active and KRT logs will still be written to the configured files.
PR Number Synopsis Category: SW PRs for SCBE3 related kernel drivers
1564539 MX platforms with MX-SCBE3 may reboot continuously
Product-Group=junos
A recent change in the kernel boot loader causes a system with MX-SCBE3 to experience the Routing Enginne's kernel memory corruption which causes the system to reboot continuously.
PR Number Synopsis Category: IPSEC functionality on M/MX/T ser
1557216 On the EX4300 device, script fails while committing the IPSec authentication configuration as the algorithm statement is missing.
Product-Group=junos
On all Junos platforms except MX/SRX with FIPS mode enabled, the manual IPsec functionality might not be working as no authentication algorithm is configurable for IPsec.
PR Number Synopsis Category: Issues related to Snorkel Interfaces
1573209 CFP unplugged message is not logged in Junos OS Release 17.3 and later.
Product-Group=junos
CFP unplugged message is not logged in Junos OS Release 17.3 and later.
PR Number Synopsis Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1569894 The mspmand process might crash if the packet flow-control issue occurs on MS-MPC/MS-MIC.
Product-Group=junos
In MX platforms with MS-MPC/MS-MIC scenario, the Packet Ordering Engine (POE) recovery operation will control the right packet descriptor of packet flow and detect jbuf (memory) leak. But, if some rare race conditions happen during this time, this kind of flow-control operation might cause the mspmand to crash. Then, MS-MPC/MS-MIC might restart.
PR Number Synopsis Category: SRX Argon module bugs
1587962 Garbage characters might be received in quarantine notification
Product-Group=junos
On SRX-Series devices, enrolled to SKYATP, there might be garbage characters received in quarantine notification from Cloud.
PR Number Synopsis Category: SRX branch platforms
1586426 The l2ald process might crash on issuing ethernet-switching commands
Product-Group=junos
On SRX-Series devices, when global mode is Layer 2 transparent-bridge mode, the l2ald process might crash and generate a core on executing commands: "show ethernet-switching table count" or "show ethernet-switching table vlan-id summary".
PR Number Synopsis Category: SSL Proxy functionality on JUNOS
1587149 On SRX-Series devices, the protocol-version command which controls TLS-versions (1.1, 1.2, 1.3, etc) within SSL-Proxy has been unhidden
Product-Group=junos
On SRX-Series devices, the protocol-version command which controls TLS-versions (1.1, 1.2, 1.3, etc) within SSL-Proxy has been unhidden.
PR Number Synopsis Category: MPC7/8/9 Interface Issues
1574279 QSFP 4x10G interface might not come up after FPC reboot
Product-Group=junos
On EA-based MX platforms with QSFP module, QSFP 4x10G interface fails to come up after FPC reboot.
PR Number Synopsis Category: SRX-1RU platfom related protocol, QoS, filtering features et
1585698 The 1G interfaces might not come up after device reboot
Product-Group=junos
On SRX4600 devices, in some cases 1GbE SFP optical interfaces might not come up and disabling dfe tuning failed is displayed in the logs.
PR Number Synopsis Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1570631 On Trio line cards hosting subscribers error logs might be seen
Product-Group=junos
On all Trio line cards hosting subscribers, when memory allocation in the counter segment fails the error logs may be seen.
PR Number Synopsis Category: Trio pfe qos software
1553961 FPCs may go to "ISSU error" state post performing enhanced ISSU
Product-Group=junos
On the MX series platforms running 20.1R1 onwards, performing enhanced ISSU may cause FPCs (having xq or qx chip like MPC1/MPC2/MPC2E-NG/MPC3E-NG/MPC5E/MPC6E) to run into "ISSU error" state.
PR Number Synopsis Category: Trio pfe stateless firewall software
1586817 FPC might crash in a scaled-firewall configuration.
Product-Group=junos
On MX/PTX/QFX series platforms running Junos, traffic loss might be observed in a scaled firewall filter configuration setup due to FPC crash. When the issue occurs, a core file is generated which could be checked using the CLI command 'show system core-dumps'. host@device> show system core-dumps -rw-r--r-- 1 root wheel 89322187 /var/crash/core-NGMPC0.gz.core.0 ----> Core file
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1571439 On all EX9200 platforms with EVPN-VXLAN configured, the next hop memory leak in MX Series ASIC happens whenever there is a route churn for remote MAC-IP entries learned bound to the IRB interface in EVPN-VXLAN routing instance. When the ASIC's next hop memory partition is exhausted, the FPC might reboot.
Product-Group=junos
On all EX9200 switches and MX Series routers with EVPN-VXLAN configured, the next hop memory leak in Trio ASIC happens whenever there is a route churn for remote MAC-IP entries learned bound to the IRB interface in the EVPN-VXLAN routing-instance. When the ASIC's next hop memory partition is exhausted (free next hop memory is close to 20% or below), the FPC might reboot.
PR Number Synopsis Category: Trio pfe l3 forwarding issues
1560772 Interface not able to send/receive packets after repeated link flaps on MPC10/11E
Product-Group=junos
On all Junos platforms with MPC10E/11E linecards, repeated 100GE interface link flaps may result in complete traffic stall (packets no longer going out the interface).
1568944 Traffic might be dropped when the default route is changed in inet.0 table
Product-Group=junos
Traffic might be dropped on MX/EX92xx trinity platforms when the default route is changed in the inet.0 table. It might take 2-3 seconds to be updated in PFE. This issue can be recovered automatically.
1569829 MPC10 : user.info packetio: [Info] RESOLVER:HOLD: Resolve to hold nh:776 not found in the database
Product-Group=junos
Next-hop type "hold", "resolve" are seen during ARP resolution process. RESOLVER:HOLD: Resolve to hold nh:XXXX not found in the database is an informational message during this process. With the fix of the PR these logs severity is changed to debug level from information.
1577611 When line card is booted on RE1 being Master, Nextgen stats failed to fetch the value of backup mac address correctly
Product-Group=junos
When line card is booted on RE1 being Master, Nextgen stats module failed to fetch the value of RE0 mac address correctly. So subscriber interim stats reporting will be impacted (for the subscriber on the push cards i.e. MPC3 NG, MPC5, MPC7 onwards) when a GRES is performed.
PR Number Synopsis Category: Trio pfe sampling, services plumbing
1575994 Memory partitioning issue might happen on PFE after applying sampling and "flex-flow-sizing" to the Trio based line-cards
Product-Group=junos
If the sampling and flex-flow-sizing (it allows for flexible flow hash table partitioning in the memory) have been applied to the PFE of an FPC, in some particular cases, the memory partitioning errors might happen when the flex-flow table size reaches the MAX. It might cause the PFE to experience invalid operations and reading errors, then the errors might happen on PFE and the inline-services might be impacted.
PR Number Synopsis Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1530106 Ex3400 VC - Console access on backup VC member is not allowed
Product-Group=junos
Console login on a Virtual Chassis backup member might not be permitted if unreachable DNS name-server is configured on the box. DNS name resolution checks if the host is valid for login or not. If the DNS server configured on the box is not reachable, the user is not allowed on the Virtual Chassis while trying to access it from the console of the backup member.
PR Number Synopsis Category: Configuration management, ffp, load action
1577626 Apply-paths might cause validation failures during JUNOS upgrade
Product-Group=junos
On SRX-Series devices with apply-path configuration, during upgrade the validation might fail.
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1559786 It fails if the xml output from command "request vmhost mode test | display xml rpc" is picked and used in netconf
Product-Group=junos
On vmhost platforms, if the xml output from command "request vmhost mode test | display xml rpc" is picked and used in netconf, it will fail. set vmhost mode custom test layer-3-infrastructure cpu count MIN set vmhost mode custom test layer-3-infrastructure memory size MIN set vmhost mode custom test nfv-back-plane cpu count MIN set vmhost mode custom test nfv-back-plane memory size MIN set vmhost mode custom test vnf cpu count MIN
1586229 Fix fast-diff to detect the change when a deactivated delta-list element is deleted
Product-Group=junos
Fix fast-diff to detect the change when a deactivated delta-list element is deleted
PR Number Synopsis Category: PTX/QFX10002/8/16 specific software components
1576521 On MX10016 routers, when the Fan X Failed alarm is cleared in the Fan Tray 1, the Fan/Blower OK SNMP traps are generated for the Fan Tray 0 [Fan 31 - 41] and Fan Tray 1 [Fan 11 - 41].
Product-Group=junos
On MX10016 routers, when "Fan Tray 1 Fan x Failed" alarm is cleared, "Fan/Blower OK" SNMP traps are generated for Fan Tray 0 [Fan 31 - 41] and Fan Tray 1 [Fan 11 - 41].
 

20.2R3-S1 - List of Known issues

PR Number Synopsis Category: EX4300 PFE
1595797 Firewall filter might not get programmed correctly on EX4300 platforms
Product-Group=junos
On EX4300 platforms, the firewall filter might not get programmed correctly, if there is any modification made in the filter which is already attached to an interface and it is the only filter in the group. The traffic through the interface will be impacted.
PR Number Synopsis Category: Control Plane and Infrastructure for the Junos Fusion Enterprise
1188254 Junos Fusion Enterprise: LLDP might stop working if manually deactivated and reactivated
Product-Group=junos
On a Junos Fusion Enterprise, LLDP might stop working if it is reenabled after being manually disabled.
PR Number Synopsis Category: Border Gateway Protocol
1579225 Dynamic tunnels are still up after deactivating the BGP nexthop type UDP policy.
Product-Group=junos
The BGP signaled dynamic tunnels remain in an established state and don't go down after deactivating the BGP export policy which contains next-hop and tunnel community information from the remote end.
1594626 The routing process may crash due to memory corruption while processing BGP multipath route
Product-Group=junos
The rpd process may experience a crash due to memory corruption while processing BGP multipath route. It has a traffic impact.
1594664 The rpd process might crash when executing the SNMP get command to fetch the MPLS L3VPN MIBs
Product-Group=junos
On both Junos and EVO platforms with MPLS (Multiprotocol Label Switching) L3VPN (Layer 3 Virtual Private Network) used, the rpd process might crash when executing the SNMP (Simple Network Management Protocol) get command for specific objects of MPLS L3VPN MIBs (e.g. "show snmp mib get mplsL3VpnVrfRteXCPointer<>"). Traffic loss might be seen during the rpd process crash and restart.
PR Number Synopsis Category: EVPN Layer-2 Forwarding
1586402 The BUM traffic might lose after triggering NSR in EVPN-MPLS or EVPN-ETREE scenario
Product-Group=junos
In EVPN-MPLS or EVPN-ETREE scenario, the EVPN allocates an IM label (Inclusive multicast route labels) per VLAN, and the IM labels including the EVI name and VLAN ID are mirrored to the standby RE (routing engine). If disabling/enabling NSR or switching RE mastership with NSR, the l2ad activated in the new master RE might not create the IM next-hop and locally-learned MAC addresses along with new underlay MPLS next-hop created by rpd for the remote EVPN PE, then the remote EVPN PE might be missed from the flood next-hop group on the EVPN instances, it might cause the BUM traffic to lose between the EVPN PEs.
PR Number Synopsis Category: Express PFE including evpn, vxlan
1590919 [evpn_vxlan] [evpn_instance] QFX10002 :: JUNOS:JDI_REGRESSION:PROTOCOLS:SWITCHING:QFX-EVPN_VXLAN: Traffic loss seen after loading EVPN configuration
Product-Group=junos
Release note needed.
PR Number Synopsis Category: FIPS related issues
1569412 [ipsec] [ipsectag] mx480 :: FIPS :: IPSEC security-associations not established, Observed packet loss
Product-Group=junos
DEV needs provide release note.
PR Number Synopsis Category: Security platform jweb support
1594366 [J-Web] zone info disappears when functional zone is configured
Product-Group=junos
zone info is not listed at configuration menu on J-Web, if functional zone is configured without any option.
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1560588 IGMP joins where there are more than expected value while verifying the IGMP snooping membership in the CE router.
Product-Group=junos
VE & CE mesh groups are default mesh groups created for a given Routing instance. On vlan/bridge-domain add, flood tokens and routes are created for both VE and CE mesh-group/flood-group. Ideally, VE mesh-group doesn't require on a CE router where IGMP is enabled on CE interfaces. Trinity based CE boxes have unlimited capacity of tokens, so this would not be a major issue.
PR Number Synopsis Category: lacp protocol
1461581 The LACP force-up and EVPN core isolation features are not supported together.
Product-Group=junos
In an EVPN multihomed active-active scenario, when LACP is enabled on PE-CE child member links, LACP force-up feature should not be enabled in conjunction with EVPN core isolation feature (enabled by default) because it is currently not supported in this scenario as these two features are contradictory in terms of action they take.
PR Number Synopsis Category: Multicast for L3VPNs
1591228 The ddos-protection reason "packets failed the multicast RPF check" may be seen in NG-MVPN scenario with GRE transport
Product-Group=junos
In Next Generation Multicast VPN scenario where GRE is used as a transport and router receives high amount of traffic via Inclusive PMSI without active multicast subscribers, the ddos-protection may be violated with "packets failed the multicast RPF check" reason.
PR Number Synopsis Category: Issues related to PKI daemon
1549954 PKI CMPv2 client certificate enrolment does not work on SRX when using root-CA.
Product-Group=junos
The PKI CMPv2 (RFC 4210) client certificate enrolment does not properly work on SRX Series devices when using root-CA.
PR Number Synopsis Category: vMX Platform Infrastructure related issue tracking
1575328 On the MX150 routers, the interface might take a long time to power down while rebooting, powering-off, halting, or upgrading.
Product-Group=junos
On MX150 devices, while performing reboot/power-off/halt/software upgrade with/without reboot the interfaces might take a long time to powerdown.
PR Number Synopsis Category: Related to sw defects for K2-RE
1497592 Backup Routing Engine reboots because of power cycle or failure when the offline and online operations are performed on CB1.
Product-Group=junos
After backup Routing Engine halt, CB1 goes offline and comes back online; this leads to the backup Routing Engine booting up, and it shows the reboot reason as "0x1:power cycle/failure." This issue is only for the RE reboot reason, and there is no other functional impact of this.
PR Number Synopsis Category: Resource Reservation Protocol
1576979 With the local reversion on, there is a possibility of the transit router not informing the headend of RSVP disabled link when the link flaps more than once.
Product-Group=junos
With local reversion ON, there is a possibility of transit router not informing headend of RSVP disabled link when link is flapped more than once. Work around is to remove local-reversion configuration.
PR Number Synopsis Category: Secure Web Proxy functionality on Junos
1589957 Pass-through traffic might fail post reboot when Secure Web Proxy is configured
Product-Group=junos
On SRX-Series devices, pass-through traffic on Secure Web Proxy may fail after rebooting the device.
PR Number Synopsis Category: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1593226 The TCP keepalive might not be processed by the private network host
Product-Group=junos
On MX platforms with MS-MPC and MS-MIC when tcp-tickle knob is enabled under services-options in DS-lite (Dual-Stack lite) with NAT scenario, the TCP keepalive might not be processed by the private network host and the purpose of TCP keepalive gets compromised.
PR Number Synopsis Category: ZT/YT pfe l3 forwarding issues
1586057 Unicast traffic over IRB interface may be wrongly routed due to stale PFE programming
Product-Group=junos
Traffic entering or leaving MPC10 may be wrongly routed due to stale PFE programming
PR Number Synopsis Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1573920 cassxr_err_addr(8593): Uninitialized Read Error @ EDMEM[0x7cb601b0]
Product-Group=junos
FPC reports following error log messages cassxr_err_addr(8593): Uninitialized Read Error @ EDMEM[0x7cb601b0]
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1556850 Upgrading the satellite devices might lead to some SDs to go in the SyncWait state.
Product-Group=junos
Upgrading satellite devices may lead to some SDs in SyncWait state. Cascade port flap not causing the issue.
PR Number Synopsis Category: Trio pfe mpls- lsps,rsvp,vpns- ccc, tcc software
1452864 Ferrari: BUD node replicating duplicate packets towards egress PE when we have S-RSVP-TE P2MP with vt interfaces
Product-Group=junos
Ferrari: BUD node replicating duplicate packets towards egress PE when we have S-RSVP-TE P2MP with vt interfaces
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1519367 Commit fails for the backup Routing Engine for the deactivated mpls lsp priority command
Product-Group=junos
When a user tries to deactivate the mpls related config, the commit fails on backup RE. Work-around details are provided in the corresponding section below.
PR Number Synopsis Category: Virtual Router Redundancy Protocol
1534835 IPv6 VRRP sessions are not established when Duplicate Address Detection (DAD) is enabled.
Product-Group=junos
On MX platforms with IPv6 VRRP sessions, the VRRP sessions are not established when Duplicate Address Detection (DAD) is enabled.
PR Number Synopsis Category: usf ams related issues
1596976 CGNAT MX SPC3 AMS warm-standby 1:1 redundancy problem with CLI CPU statistics lost data after PIC failover.
Product-Group=junos
CGNAT MX SPC3 AMS warm-standby 1:1 redundancy problem with CLI CPU statistics lost data after PIC failover. show services service-sets cpu-usage - Does not display service sets show services sessions utilization - Missing session count, the rates and CPU values.
 

 

Modification History:
2021-07-15 Updated missing release note entries
2021-06-12 Update to add a Software RECALL notification QFX5000s, EX4600s, and EX4650 images.
2021-06-10 Modified to include a note that SRX1500 is not part of this release
First publication 2021-05-21
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search