Open Issues

On QFX5100 platforms, traffic might not get classified based on a fixed classifier in MPLS as well as the VXLAN scenario. PR1650051

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. PR1688455

When you add VLAN as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

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

5M DAC connected between QFX10002-60C switches does not link up. But with 1M and 3M DAC this interop works as expected. Also it is to be noted QFX10002-60C and ACX or Traffic generator the same 5M DAC works seamlessly. There seems to be certain SI or link level configuration on both QFX10002-60C and MX2010 which needs to be debugged with the help from HW and SI teams and resolved. PR1555955

To avoid the additional interface flap, interface hold time needs to be configured. PR1562857

On QFX5100 devices, media type for SFP+-10G-CU1M and SFP-T cables are shown as Fiber. This is only a display issue and no functionality impact is observed. PR1570555

On QFX5110 VC, FPC might gets disconnected with 24,000 DHCPv6 relay scaling, after the traffic is stopped. "pfe_listener_disconnect" error messages may be seen. PR1594748

Pim VXLAN does not work on TD3 chipsets enabling VXLAN flexflow after Junos OS Release 21.3R1. Customers Pim VXLAN or data plane VXLAN can use the version prior to Junos OS Release 21.3R1. PR1597276

On QFX5100, optical power is seen after detached and attached QSFP on disable interface. PR1606003

On QFX5120-48Y devices, when scaled configuration and baseline configs are loaded multiple times one after other without much wait time in between then traffic or protocols on pure Layer 3 interfaces might behave in undefined/unexpected manner. PR1612973

On PTX10002-60C and QFX10002-60C switches after the system is rebooted, the FPC 0 Major Errors alarm might be seen due to a rare timing issue. The issue could cause the host path traffic to get dropped. It is a rare issue and does not always happen during reboot. Please try to perform "request vmhost reboot" for recovery. PR1613229

On QFX5110-32Q devices, traffic loss occurs after renumbering primary in Virtual Chassis. PR1632565

Backup FPC lose their connection to the master when new members are added to the VCF (Virtual Chassis Fabric). PR1634533

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 may not establish a VCP connection and Cyclic Redundancy Check (CRC) errors are also observed.PR1646561

On QFX platform, IPv6 ifl status 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 QFX5100-24Q devices VC (Virtual-chassis) is in unstable state for 3-7 minutes causing traffic loss. PR1661349

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 QFX5200 devices after NSSU upgrade for a 4 member VC , FPC might toggle resulting in interfaces goes offline. PR1673116

Each locally learned ARP/ND Nexthop requires unique fabric token from Kernel. This unique token maps to physical address in HW and this address points to EDF memory for the ARP/ND nexthops. Token pool in kernel is also used by different features like flood nexthops, arp/ndp nexthops. Token usage has increased as tokens are now used by IRB interfaces and default mesh groups also. 96,000 ARP/ND scale might not be achievable always. It is recommended to scale upto 95,000 ARP/ND. PR1673626

On QFX10008 devices, statistics for multicast packets is not as expected as the packets has L2 header stripped during replication in PFE because of which it is not forwarded to the next hop.PR1678723

On QFX5100 devices (both stand-alone and VC scenario) running Junos, occasionally during the normal operation of the device, Packet Forwarding Engine can crash resulting in total loss of traffic. The PFE reboots itself following the crash. PR1679919

On QFX5100 switches configured with Virtual Chassis(VC), if a primary member is unplugged or forced to power off, the unicast traffic is dropped due to mac-persistence-timer expiry there is a difference in mac addresses between logical aggregated parent interface and member aggregated ethernet(ae) interface. PR1695663

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

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 config from sandbox does not have.PR1601504

On all Junos OS platforms, while using source-address NTP configuration parameter and issue the command "set ntp date" from the CLI, packets will be sent with the source address of the outgoing interface rather than the manually configured IP address. Typically, the manually configured IP address would be a loopback address. The problem does not apply to automatically generated NTP poll packets. PR1545022