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.

General Routing

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

  • 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

  • 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

  • Configuring em0/em1 interface on a Virtual chassis will cause instability in a Virtual Chassis, causing the VC members to split. VME interface should be used instead of em0/em1PR1636050

  • 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 and are at best, guesstimate.PR1653671

  • On all QFX platforms, Ethernet VPN (EVPN) Type-5 traffic drops are observed when the device is configured only with Type-5 Virtual Routing and Forwarding (VRF) and without an Integrated Routing and Bridging (IRB) interface. PR1663804

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

  • Applying ERSPAN configuration along with the ERSPAN output/egress INET interface configuration sometimes leads to the analyzer not getting created in the HW.PR1682610

  • On Junos OS QFX5000 Series platforms, configuration changes in Ethernet Virtual Private Network (EVPN) Virtual Extensible LAN (VXLAN) with Type 5 tunnel cause port and protocol flaps which cause traffic loss (Configuration change related to the underlay network).PR1688323

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

  • root show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis XXXXXXXXXXXX Virtual Chassis Pseudo CB 0 Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine FPC 0 REV 16 650-064380 XXXXXXXXXXXX QFX5100-48S-6Q CPU BUILTIN BUILTIN FPC CPU PIC 0 BUILTIN BUILTIN 48x10G-6x40G Xcvr 0 REV 01 740-031980 XXXXXXXXXXX SFP+-10G-SR Power Supply 0 REV 04 740-041741 1GA27194620 JPSU-650W-AC-AFO Power Supply 1 REV 04 740-041741 1GA27194616 JPSU-650W-AC-AFO Fan Tray 0 QFX5100 Fan Tray 0, Front to Back Airflow - AFO Fan Tray 1 QFX5100 Fan Tray 1, Front to Back Airflow - AFO Fan Tray 2 QFX5100 Fan Tray 2, Front to Back Airflow - AFO Fan Tray 3 QFX5100 Fan Tray 3, Front to Back Airflow - AFO Fan Tray 4 QFX5100 Fan Tray 4, Front to Back Airflow - AFO Power Supply 0 REV 04 740-041741 1GA27194620 JPSU-650W-AC-AFO <<<<<<<<<<< Dup!! Power Supply 1 REV 04 740-041741 1GA27194616 JPSU-650W-AC-AFO <<<<<<<<<<< Dup!! Fan Tray 0 QFX5100 Fan Tray 0, Front to Back Airflow - AFO <<<<<<<<<<< Dup!! Fan Tray 1 QFX5100 Fan Tray 1, Front to Back Airflow - AFO <<<<<<<<<<< Dup!! Fan Tray 2 QFX5100 Fan Tray 2, Front to Back Airflow - AFO <<<<<<<<<<< Dup!! Fan Tray 3 QFX5100 Fan Tray 3, Front to Back Airflow - AFO <<<<<<<<<<< Dup!! Fan Tray 4 QFX5100 Fan Tray 4, Front to Back Airflow - AFO <<<<<<<<<<< Dup!! {master:0} root>. PR1704106

  • 1. VC members can split when em0 cable is removed and reinserted. 2. VC will automatically converge after the split(after point 1). PR1709938

  • In QFX5000 devices, LACP flaps will be seen, when LACP BPDUs are received, VLAN tag is not processed causing system-id mismatch. PR1711783

  • Whenever a new VLAN is added in between previously configured VLANs, existing context ID which is already assigned to existing VLAN context, will be assigned for that new VLAN. Due to this we might see incorrect system ID or bridge ID and this might create an issue.PR1717267