Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Open Issues

Learn about open issues in this release for QFX Series switches.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Interfaces and Chassis

  • The following two error messages gets generated brcm_rt_ip_mc_ipmc_install:2455 Failed (Invalid parameter:-4) This message is due to IPMC Group being used is not created, when RE tried to add this check indicates there is a parameter mis-match. brcm_rt_ip_mc_ipmc_install:2455 Failed (Internal error:-1) This message is due to Failure to read IPMC Table or any memory/register. PR1461339

Layer 2 Features

  • In case of the access-side interfaces used as SP-style interfaces, when a new logical interface is added and if there is already a logical interface on the physical interface, there is 20--50 ms traffic drop on the existing logical interface. PR1367488

Layer 2 Ethernet Services

  • On QFX5100 and QFX5110 devices, vendor-id format maybe incorrect for network ports. This does not impact the ZTP functionality or service. The DHCP client config is coming from two places, i.e AIU script and vsdk sandbox. The DHCP client config coming from AIU script has the serial Id in vendor id where as the default configuration from sandbox does not have. PR1601504

Platform and Infrastructure

  • On the QFX5100 line of switches, inserting or removing optics on a port might cause a Packet Forwarding Engine Manager CPU spike and an eventual microcode failure. PR1372041

  • VXLAN VNI (multicast learning) scaling on QFX5110 traffic issue is seen from VXLAN tunnel to Layer 2 interface. PR1462548

  • In the platform using INH (indirect next hop, such as Unilist) as route next hop type for multiple paths scenario (such as BGP PIC or ECMP), the session fast-reroute might be enabled in Packet Forwarding Engines (PFEs). When the version-id of session-id of INH is above 256, the PFE might not respond to session update, which might cause the session-id permanently to be stuck with the weight of 65535 in PFE. It might lead PFE to have a different view of Unilist against load-balance selectors. Then either the BGP PIC or the ECMP-FRR might not work properly and traffic might be dropped or silently discarded. PR1501817

  • When launching a guest Virtual Machine (VM) to run a third party application on Junos OS 15.1R1 and above, the guest VM might be shown as "UNAVAILABLE" even after successfully installing the third party application. This is due to duplicated device ID assigned to different disks. PR1529596

  • On QFX5110 Virtual Chassis, FPC may gets disconnected with 24000 DHCPv6 relay scaling, after the traffic is stopped. "pfe_listener_disconnect" error messages may be seen. PR1594748

  • Pim Vxlan not working on TD3 chipsets enabling VxLAN flexflow after release 21.3R1. Customers Pim Vxlan or data plane VXLAN can use the version 21.3R1. PR1597276

  • On all devices running Junos OS or Junos OS Evolved, where this is a high BGP scale with flapping route and the BGP Monitoring Protocol (BMP) collector/station is very slow, the rpd process might crash due to memory pressure. PR1635143

  • When MACSEC and VRRP are enabled on QFX5120 VC, MACSEC sessions are flapping at random times. Without VRRP this issue is not seen. PR1640031

  • On all QFX5100 Virtual Chassis platforms, after the reboot, Virtual Chassis port (VCP) ports might not establish a VCP connection and Cyclic Redundancy Check (CRC) errors are also observed. PR1646561

  • On QFX platform, v6 ifl stats are being derived from the underlying ifd stats unlike on PTX where they are hardware assisted. Hence, they are not very reliable. PR1653671

  • When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted may go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission. PR1665800

  • On QFX5110 platforms with more than one l2circuit configured, deactivating and activating the l2circuit configurations successively might cause traffic drop on one or more Layer 2 circuits. PR1666260

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

  • On QFX5000 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). PR1688323

  • On QFX5100 Virtual Chassis (VC) and Virtual Chassis Fabric (VCF) platforms on upgrading Virtual Chassis Fabric (VCF) and toggling the interface, when FPC (Flexible PIC Concentrators) is disabled and rebooted, the member fails to join the virtual chassis and the interface remains disabled even after been enabled. PR1689499

  • The show chassis hardware command indicates duplicate entries for PSU and FAN tray after USB clean install or zeroize. PR1704106

  • as list_get_head function is called in multiple places in pfe we needed previous 3 functions on the stack which had called list_get_head so we could debug why 'list_get_head list has bad magic ' this error has occured. PR1705853

  • On QFX10000 devices, traffic going over unilist is dropped when unilist member goes from next-hop hold state to unicast or aggregate state. PR1713279

  • On QFX5000 devices, the output of the show forwarding-options enhanced-hash-key command does not indicate weather the ECMP Resilient Hashing is enabled or disabled. PR1725916

Routing Protocols

  • On all QFX platforms unexpected behavior of bandwidth based metric in IS-IS is seen since actual bandwidth is falling back to 0 bps when one of the member interface of AE (Aggregated Ethernet) bundle (interface-group) goes down. PR1718734

Virtual Chassis

  • On QFX5100 platforms running QFX-5e images in Virtual Chassis setup, when Virtual Chassis Port (VCP) links are connected between PHY and PHYLESS ports, CRC alignment errors will be seen. As a result, there can be traffic loss on these links. PR1692102