ON THIS PAGE
Open Issues
Learn about open issues in this release for QFX Series switches.
For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.
General Routing
-
On QFX5230-64CD platform, 400G DAC cable of 2.5m length and 4X100G DAC BO might not link up with some peer devices. This issue is not seen with all peer devices. If this happens, please replace the 2.5m cable with a 1m DAC cable or use supported 400G Optics instead. PR1747315
-
On QFX5130-48C, when image upgrade is done using CLI, the log messages will have kernel trace reported. There is no functionality impact due to the messages.PR1755406
-
QFX5230-64CD: FPC 0 idtRC38612 PLL LOCK Failure major alarm is seen after the system comes up post a device reboot. This alarm is cleared after a few minutes once the system reaches steady state. No user action is required.PR1766984
-
Whenever a QFX5130-48C device is reset using rear panel reset button by pressing the button for short or long duration, the port LEDs on ports 56/57 might glow in amber for a few seconds during boot up. The port LEDs amber status turn off and reflect correct port state once device is up.PR1792619
-
The recommended procedure for FPC card removal is to do a graceful OIR by following the documented steps. However, if the FPC card is ungracefully jacked out or plugged in several times in a short interval, the software might show the FPC status as "FAULT". Following are the steps to recover from the fault state: PR1799333
Jack out the FPC.
Wait for 1 minute for FPC state to become Fault in
show chassis fpc pic-status
command.Jack In FPC.
Wait for 1 minute for FPC state shows as present in
show chassis fpc pic-status
command.Run CLI command
request chassis fpc online slot
to bring FPC in online state.Wait for 3 minutes for all interfaces to come up.
-
QFX5130E-32CD supports class A performance with default FEC applicable for the particular interface.PR1800144
-
On a QFX5700 chassis with QFX5700E-FEB, during FEB offline or online operation, a power fault message is reported on the console. Following is an example of the message printed on to the console. pcieport 0000:41:09.0: pciehp: Slot(9): Power fault. PR1802959
-
When a VXLAN encapsulated IP packet, or an IP packet with UDP port matching the VXLAN UDP port, is received on a vlan-tagging enabled interface, the switch drops the frame. This issue is not seen if the incoming port is an untagged interface, or if the interface is actually doing VXLAN encap/decap operations. In such cases, the device forwards the frame correctly. PR1805922
-
When the QFX5700 is power cycled, in some cases, during the reboot of the system, the evoaft-jvisiond-brcm process might not start automatically. The operating system stops the service and generates a major alarm. This does not impact other forwarding or chassis functionality. Restarting the process through the CLI login shell clears the alarm and the process functionality is restored. PR1807624
-
IPv4/IPv6 reserved multicast and L2 multicast traffic received over VXLAN access port is flooded out of all ports of the VXLAN except vtep. PR1811158
-
On the QFX5220, QFX5130, QFX5700, QFX5230, or QFX5240 platforms, after clearing queue counters for the aggregated Ethernet interface from CLI, if one of the aggregated Ethernet member interfaces is immediately removed from aggregated Ethernet bundle, it displays invalid queue counters for the aggregated Ethernet interface. Clearing the queue counters from CLI again helps to resolve the issue.PR1811575
-
No support for Layer 3 vlan-tagged sub-interfaces on VXLAN NNI side in Junos OS Evolved 23.4R2 on QFX5230. Only layer 3 interfaces or IRB can be configured on VXLAN NNI side. PR1813069
-
When a QFX5700E chassis is powered off, there might be CPU kernel trace messages printed onto the console during power off. These messages have no impact to functionality.PR1813256
-
QFX130E-32CD: Sometimes system fails to boot up during power cycle when there is insufficient time gap between power-off and power-on. The recommendation is to give a 120 seconds gap between power-off and power-on. PR1813294
-
QFX5230-64CD, QFX5130-48C, : Help string for MTU settings on management interface are not correct. The range is showed as 256-9408 instead of 256-9216.PR1813591
-
In rare cases, FPC 0 Volt Sensor Fail" or "FPC 0 Voltage Threshold Crossed alarm is seen after bootup on QFX5130-48C or QFX5130-48CM. PR1816064
-
QFX5700 MacSec: Minor packet drops (< 0.0000001%) observed when MacSec is enabled. PR1816407
-
USB disks with Junos OS Evolved images from Junos OS Evolved 23.4R2 onwards might not be detectable by Windows. They still have valid images, and can be used for Junos OS Evolved installs. The only issue is that new images cannot be installed on these USB disks because Windows no longer recognizes these USB drives. PR1819846
-
On QFX5220, QFX5230, QFX5240, QFX5130, or QFX5700 platforms, for lossless queues packet admission control is based on ingress priority group thresholds only. Once lossless packet is accepted by ingress, there is no any further admission control checks based on egress queue thresholds. So dynamic threshold (alpha) setting configured at egress queue level, does not make any impact for lossless queues. For lossless queue, peak shared buffer utilisation is always based on the ingress priority group dynamic threshold. Do not configure per queue alpha through buffer-dynamic-threshold for lossless queues. On QFX5220, QFX5230, QFX5240, QFX5130, or QFX5700 platforms, ECN threshold is static. However PFC thresholds are dynamic. For effective DCQCN behaviour, make sure ECN threshold is always lower than the PFC XOFF threshold. Specifically when multiple ingress and egress ports involved in lossless queue congestion, there is high chance for PFC XOFF threshold hitting before ECN threshold. Proper ECN marking thresholds can be arrived by monitoring the peak buffer utilisation of congested lossless queues and fine tuning the ECN thresholds accordingly. PR1820266
-
QFX5130-48CM: MacSec: Packet drops are seen when MKA session switches from primary to fallback In case the primary pre-shared-key (PSK) fails to establish a connection, the fallback PSK is used. Traffic loss is observed during switch from primary to the fallback session. No traffic drop is observed if the primary PSK is kept active without switching to the fallback PSK. Thus, as long as the primary PSK is active, the MACSec sessions pass traffic properly without any drop. PR1820549
Interfaces and Chassis
-
Unified ISSU from Junos OS Evolved 23.2R2 to newer releases generates core files. Object data structure is extended for a fix and during the extension, the extensions between the releases should match. However, there is a mismatch with respect to such extensions between the releases, which causes the issue. PR1803068