Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Resolved Issues: 21.3R1

General Routing

  • In EX2300 and EX3400 platforms, RTC ERROR and SETTIME failed messages are noted. PR1535106

  • The Power over Ethernet (POE) might fail on EX platforms due to a rare timing issue in the Virtual Chassis scenario. PR1539933

  • Cattle-Prod Daemon received unknown trigger (type Semaphore, id 1) error messages seen on the vty when the CLI commands to fetch host route scale are issued.PR1554140

  • The Virtual Chassis Port (VCP) might not come up EX4600 platform. PR1555741

  • FPC with power related faults might come online again after Fabric Healing sets the FPC offline. PR1556558

  • The MAC addresses learned in a Virtual Chassis might fail, aging out in MAC scaling environment. PR1558128

  • Some transmitting packets might get dropped due to the disable-pfe action is not invoked when the fabric self-ping failure is detected. PR1558899

  • The DHCP client might not obtain IP address when dhcp-security is configured .PR1564941

  • On EX platforms, the new primary Routing Engine post switchover might go into DB mode (or crash). PR1565213

  • The rpd crash might be seen at boot time. PR1567043

  • The 40G DAC connection between EX9253 and the peers might not come up. PR1569230

  • On a EX4400 Virtual Chassis, the SNMP MIB object jnRedundencySwitchOverCount will not be reset to 0 when the entire Virtual Chassis is rebooted. PR1570359

  • Packet loss might be observed when sample based action is used in firewall filter. PR1571399

  • Private VLAN configuration might fail in certain scenario. PR1574480

  • Protocol convergence between end nodes might fail when L2PT is enabled on transit switch. PR1576715

  • The device implemented with different service image version might become VC member as unexpected. PR1576774

  • The fxpc process might crash on EX Series platforms. PR1578421

  • The dcpfe crash is observed on Junos EX platforms. PR1578859

  • Random/silent reboot might be seen on EX2300-24MP and EX2300-48MP platforms. PR1579576

  • On the EX Series platforms, a few 40G ports might not be channelized successfully. PR1582105

  • The voice VLAN might not get assigned to the access interface. PR1582115

  • The l2ald crash if a specific naming format is applied between a vlan-range and a single vlan. PR1583092

  • When EX2300-MP in standalone mode is used as a DHCP server, initial set of packets received in the server might get dropped. PR1583983

  • DSCP rewriting might fail to work on EX2300 switches. PR1586341

  • Packet drops during VRRP primary reboot when 40XS linecard is present on some EX9204 platforms. PR1586740

  • The SNMP trap for MAC notifications might not be generated when an interface is added explicitly under switch-options. PR1587610

  • Process dot1xd crash might be seen and re-authentication might be needed on EX9208 platform. PR1587837

  • The rpd crash might be observed on the router running a scaled setup. PR1588439

  • Packet loss could be observed on dynamically assigning VoIP VLAN. PR1589678

  • Traffic loss might be observed for interface configured in subnet PR1590040

  • Inconsistent statistics value seen on performing slaac-snooping. PR1590926

  • The LLDP packet might lose on the EX-4300MP platform if LLDP is configured on the management interface. PR1591387

  • The show pfe filter hw might generate ERROR (dfw): Unknown group id: 21 message. PR1592096

  • The DHCP relay might not work if it connects with the server via type 5 route which with aggregated Ethernet interface as the underlay interface. PR1592133

  • On all Junos platforms, xSTP might not get configured when enabled on an interface with SP style configuration. PR1592264

  • On the EX4300-48MP Virtual Chassis, the backup Routing Engines clear the reporting alarm for a PEM failure intermittently for a missing power source. PR1593795

  • Clients authentication failure might occur due to dot1x daemon memory leak. PR1594224

  • Storm control profile might not be applied on EX2300 platforms. PR1594353

  • On a EX4400 VC, log messages related to fan settings will be observed in chassis traceoptions file. PR1594446

  • The MAC/IP withdraw route might be suppressed by rpd in the EVPN-VxLAN scenario. PR1597391

  • The backup Virtual Chassis member might not learn MAC address on a primary after removing a VLAN unit from the SP style aggregated Ethernet interface which is part of multiple VLAN units. PR1598346

  • On EX4400 Virtual Chassis, linecard member console might fail to redirect to Virtual Chassis primary. PR1599625

  • Unable to disable the management port em1. PR1600905

  • EX4400 PVIDB schema files not updated for the correct count of (lic_ft_cnt) Licensing feature. PR1601449

  • On EX2300 and EX4650, if the system is upgraded from 20.2 or earlier release to 20.3 or later release, either using phone-home feature or when the system is in factory default state, the upgrade will fail with phone-home crash. PR1601722

  • On EX2300 Virtual Chassis platforms ARP might not get resolved. PR1602003

  • On a EX4400 Virtual Chassis, the Cloud LED will display pattern for NO_CLOUD_RESPONSE when there is no IP address present on IRB interface or no DNS is configured on the device. PR1602664

  • On EX4400 dot1x authentication might not work on EVPN/xlan enabled endpoints. PR1603015

  • The NSSU performed with MACsec configuration might result in fxpc core. PR1603602

  • MAC move might be seen between the ICL and MC-LAG interface if adding or removing VLANs on the ICL interface. PR1605234

  • On EX and QFX Series switches, the fxpc process might crash and generate a core dump. PR1607372

  • On EX4300 platform, the dcpfe process might crash and generate core. PR1608306

  • DHCP packets might be received and then returned back to DHCP relay through the same interface on EX2300/EX3400/EX4300 platforms. PR1610253

  • After performing NSSU, timeout waiting for response from fpc0 error message is seen while checking version detail. PR1584457

  • There is a steady increase in storage usage in the backup chassis when the subscriber service is enabled. PR1595238

Class of Service (CoS)

  • The buffer allocation for VCP ports might not get released in Packet Forwarding Engine after physically moving the port location. PR1581187


  • Traffic loss might be seen under EVPN-VxLAN scenario when MAC-IP moves from one CE interface to another. PR1591264

  • The label field for the EVPN Type 1 route is set to 1. PR1594981

  • Traffic loss might be seen if aggregated Ethernet bundle interface with ESI is disabled on primary Routing Engine followed by a Routing Engine switchover. PR1597300


  • While loading the kernel displays the following error message: GEOM: mmcsd0s.enh: corrupt or invalid GPT detected. PR1549754

  • The vme/me0 management interface cannot process any incoming packets. PR1552952

  • Some MAC addresses might not be aged out on EX4300 platforms. PR1579293

  • In EX4400 platforms, under some conditions, the FPGA reset reason might be incorrectly shown in console logs as 0. PR1579331

  • The fxpc process might crash and generate core. PR1611480

Interfaces and Chassis

  • The aggregated Ethernet interface might flap. PR1576533

  • ARP resolution failure might occur during VRRP failover. PR1578126

  • VRRP incorrect advertisement threshold values are seen on vrrp groups when VRRP is configured on EX2300 boxes. PR1584499

Junos Fusion Enterprise

  • Reverting mastership from RE1 to RE0 might lead to l2ald daemon crash and cause an outage. PR1601817

Layer 2 Features

  • 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. PR1582473

Layer 2 Ethernet Services

  • The DHCP client will be offline for 120 seconds after sending the DHCPINFORM message in the DHCP relay scenario. PR1575740

  • The DHCP client might be offline for about 120 seconds after sending the DHCPINFORM message. PR1587982

Platform and Infrastructure

  • On Ex3400 VC, console access on backup VC member is not allowed. PR1530106

  • Junos OS: Upon receipt of specific sequences of genuine packets destined to the device the kernel will crash and restart (vmcore) (CVE-2021-0283, CVE-2021-0284). PR1557881

  • 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. PR1571439

  • FPC crashes might be seen on EX92 platforms. PR1579182

  • The pfex might crash during PIC 4x 1G/10G SFP/SFP+ offline/online. PR1582457

  • Firewall filter is not programmed correctly and traffic would be dropped unexpectedly. PR1586433

  • The Egress RACL Firewall filter might not get programmed correctly on EX4300 platforms. PR1595797

  • Broadcast traffic might be discarded when a firewall filter is applied to the loopback interface. PR1597548

  • VLAN tagged traffic might be dropped with service provider style configuration. PR1598251

  • The VRRP packets might not be forwarded when mac-move-limit configuration statement is configured. PR1601005

  • Adding aggregated Ethernet configuration without child member might cause MAC or ARP learning issues. PR1602399

  • ZTP does not work when downgrade from 21.1R2.2 image to 21.1R2.1 image. PR1603227

  • Slaac-Snooping global address entry learnt over vtep interface does not RENEW sometimes after lease timer expiry. PR1603269

Routing Protocols

  • BGP session carrying VPNv4 prefix with IPv6 next-hop might be dropped. PR1580578

  • The rpd might crash in scaled routing instances scenario. PR1590638

Virtual Chassis

  • EX4300 VCP might not come up after upgrade when QSFP+-40G-SR4/QSFP+-40G-LR4/QSFP+40GE-LX4 is used. PR1579430