Open Issues

Learn about open issues in Junos OS Release 21.4R2 for NFX Series devices.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

On the NFX350, if you change the device operational mode to custom mode, ovs-vswitchd cores might be seen on the device. PR1634245
At times, L3 interfaces on the NFX150 device do not receive traffic when the SRIOV mapping changes from L2 interface to L3 interface. PR1612643
On an NFX250 NextGen device, if you delete a vRR VNF and then add it back, the show virtual-network-functions command might show the vRR liveliness state as down.

Workaround: Configure dhcp force-discover on the em0 interface of the vRR VNF. PR1648041

On an NFX350 chassis cluster, when FPC0 (when node0 is primary) or FPC7 (when node1 is primary) is restarted by either using the request chassis fpc slot slot restart node local command or due to dcpfe core files on the primary, it restarts FPC1 or FPC8. This might break the preexisting TCP sessions and fail to restart the TCP sessions. The TCP sessions might require a manual restart. PR1557607

(Applies to an NFX350 device with MACsec on the layer 2 interfaces) After you reboot an NFX350 device or restart the Packet Forwarding Engines on the device, the MACsec connectivity is not established on some of the links.
Workaround—Delete the layer 2 interface configuration for the affected links and then reconfigure it. PR1640451
On the NFX250, the LACP subsystem does not start automatically when the dc-pfe process is restarted.

Workaround—Deactivate and then activate the aggregated Ethernet interface. PR1583054