Known Limitations

Junos OS can hang trying to acquire the SMP IPI lock while rebooting when it is running as a VM on Linux and QEMU hypervisor. Device can be recovered using power-cycle of the device. PR1385970

This issue occurs due to PECHIP limitation when underlay is tagged. After de-encapsulation when inner packet is recirculated it still retains the VLAN tag property from the outer header since outer header was tagged. Thus 4 bytes of inner tag got overwritten in inner packet and packet got corrupted which will result in EGP chksum trap seen in PECHIP. Fixing PECHIP limitation in software has high risk. It will be accommodated in a future release. Workaround is provided to enable encapsulate-inner-vlan configuration statement. PR1435864

This warning will pop up at reboot or power off time. This notification is part of unmount routine which is harmless with no functional impact. This might get fixed in coming RPCL/WRL release. PR1527581

In case of fan failure, show chassis environment and show chassis fan will show failed and check status respectively. This is expected and no discrepancy in terms of real status. PR1527628

On QFX10002 switches in a dynamic IP-IP tunnel transit scenario, when sFlow egress sampling is enabled on an aggregated Ethernet interface in an ECMP case, the sFlow export data does not include the nextHop field. PR1533307

When an image with the third party SDK upgrade (6.5.x) is installed, the CPU utilization might go up by around 5 percent. PR1534234

ECMP over GRE does not work for BGP routes. Traffic is polarized to just one egress interface but not distributed to multiple egress interfaces. PR1537924

In QFX5100 and EX4300 non-TVP platforms, the sample rate is limited by the IPC between the Packet Forwarding Engine and the sFlow process, so the supported limit is around 700 samples per second in these platforms. This is applicable to any sampled packets in these platforms and not specific to IPnIP. PR1539815

ISSU is not supported from releases below 20.4 to releases 20.4 and above. There is a major SDK upgrade from 6.3.2 to 6.5.16, due to which the warm boot feature needed for ISSU is not supported by our vendor. PR1554915

On QFX5200 and QFX5100 switches with the IPIP tunnel feature, show dynamic-tunnels database statistics command output shows extra packet counts (i.e. sampled packets when sFlow is enabled). PR1555922

Software versions 21.1 and lower are running FreeBSD version 11 whereas from version 21.2 onward, the FreeBSD version is 12. Software upgrade to 21.2 (or later) from 21.1 (or earlier) will mandatorily need cli configuration statement no-validate to be used during software image upgrade process. (For EX4400 platforms, this is applicable from version 21.3 onward. Hence, for EX4400 platforms, software upgrade to 21.3 (or later) from 21.2 (or earlier) will mandatorily need cli configuration statement no-validate to be used during software image upgrade process.) PR1586481

On QFX-5210 platforms, when two Flex Hash rules are configured, on deactivating first one, second one is not programmed in hardware. Commit works though. 1. Two flex hash profiles with same traffic type and different hash-parameters cannot be configured. For example: * Profile 1: Below profile applies flex hash rule for traffic with mpls 2 -label and pick the offsets configured set forwarding-options enhanced-hash-key flex-hashing FH-MPLS-2-V4-TCP-UDP ethtype mpls num-labels 2 set forwarding-options enhanced-hash-key flex-hashing FH-MPLS-2-V4-TCP-UDP ethtype mpls conditional-match CM-MPLS-2-V4-TCP set forwarding-options enhanced-hash-key flex-hashing FH-MPLS-2-V4-TCP-UDP ethtype mpls hash-offset offset1 base-offset1 start-of-L3-OuterHeader set forwarding-options enhanced-hash-key flex-hashing FH-MPLS-2-V4-TCP-UDP ethtype mpls hash-offset offset1 offset1-value 28 set forwarding-options enhanced-hash-key flex-hashing FH-MPLS-2-V4-TCP-UDP ethtype mpls hash-offset offset1 offset1-mask ffff * Profile 2: Below profile applies flex hash rule for traffic with mpls 2-label which is same as profile 1. Since already there is a profile1 configured to match mpls label-2 traffic this profile will not be installed and doesn't have any impact . set forwarding-options enhanced-hash-key flex-hashing FH1-MPLS-2-V4 ethtype mpls num-labels 2 set forwarding-options enhanced-hash-key flex-hashing FH1-MPLS-2-V4 ethtype mpls hash-offset offset1 base-offset1 start-of-L3-OuterHeader set forwarding-options enhanced-hash-key flex-hashing FH1-MPLS-2-V4 ethtype mpls hash-offset offset1 offset1-value 0 set forwarding-options enhanced-hash-key flex-hashing FH1-MPLS-2-V4 ethtype mpls hash-offset offset1 offset1-mask ffff 2. Two flex hash profiles with same traffic types can be configured only when below conditions are met : 1. All the flex-hash parameters like base-offset, offset-value, offset-mask are same for both profiles. 2. Both profiles should have different conditional profiles attached. 3. The conditional parameters like base-offset and offset-value have to be same for both profiles. 4. Combination of match-data & match-mask has to be different for both profiles . PR1521306