Open Issues

Earlier implementation of kvmclock with vDSO (virtual Dynamic Shared Object) which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate. PR1691036

Following two Failure messages seen 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

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

In MVPN Case, if the nexthop index of a group is not same between master and backup after a nsr switchover, we may see a packet loss of 250 to 400 ms. PR1561287

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

When VLAN is added 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 and MX2010 doesn't 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, the 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 may gets disconnected with 24K DHCPv6 relay scaling, after the traffic is stopped. The pfe_listener_disconnect error messages gets generated. 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 QFX5100, optical power is seen after detached and attached QSFP on disable interface. PR1606003

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

On PTX10002-60C/QFX10002-60C, 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

In QFX5110-32Q, a part of the traffic is lost after renumbering master in VC. Issue was seen in all the releases before 22.4 and not seen from 22.4 release when sdk is upgraded to 6.5.26. The workaround provided here is to either flap the Higig port or flap the ingress interface. 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 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 QFX5100 platforms, traffic may not get classified based on a fixed classifier in MPLS as well as the VXLAN scenario. PR1650051

On QFX devices, IPv6 ifl status gets 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, Virtual-chassis is in unstable state for 3 to 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 the EX4600 device with SFP-LX10/SFP-SX, after a power cycle/software reboot, all ports are initialized and links are up with auto-negotiation enabled. Few ports are up and traffic flows whereas few ports are up but no traffic flow through them. PR1672583

On QFX5200 devices after NSSU upgrade for a 4 member VC , FPC might toggle resulting in interfaces going 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. 96k ARP/ND scale might not be achievable always. It is recommended to scale upto 95K ARP/ND. PR1673626

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

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

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 all EX and QFX platforms, BFD (Bidirectional Forwarding Detection) sessions are flapped with VLAN configuration change on LAG interface. PR1709664

Service disruptions are seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage. PR1727954

On all Junos EX46xx/QFX5k (except QFX5100) platforms, child links that are in LACP (Link Aggregation Control Protocol) detached state are up and accepting incoming traffic, expecting it to drop. PR1730076

QFX5120 will reboot without causing a dcpfe crash upon the deletion of EP style(trunk) interface with multiple IFLs and native vlan configured. PR1733022

On all Junos and Junos Evolved platforms, when the shortest-path-first (SPF) algorithm for IS-IS is triggered frequently, CPU usage might increase and impact the device performance and traffic. PR1667575

On QFX5100 devices 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