- Introduction
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow What's New
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for cSRX
- play_arrow Junos OS Release Notes for EX Series
- play_arrow What's New
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for JRR Series
- play_arrow Junos OS Release Notes for MX Series
- play_arrow What's New
- play_arrow What's New in 21.4R3
- What's New in 21.4R2
- play_arrow What's New in 21.4R1
- Hardware
- Architecture
- Chassis
- EVPN
- High Availability
- IP Tunneling
- Junos Telemetry Interface (JTI)
- Layer 2 VPN
- Interfaces
- MPLS
- Multicast
- Network Address Translation (NAT)
- Operation, Administration, and Maintenance (OAM)
- Platform and Infrastructure
- Routing Protocols
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Services Applications
- Software Defined Networking (SDN)
- Software Installation and Upgrade
- Subscriber Management and Services
- VPNs
- Additional Features
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for PTX Series
- play_arrow What's New
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for QFX Series
- play_arrow What's New
- What's New in 21.4R3
- play_arrow What's New in 21.4R2
- play_arrow What's New in 21.4R1
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for SRX Series
- play_arrow Junos OS Release Notes for SRX Series
- play_arrow What's New
- play_arrow What's New in 21.4R1
- Application Identification (AppID)
- Authentication and Access Control
- Chassis
- Chassis Cluster-specific
- Flow-Based and Packet-Based Processing
- Hardware
- J-Web
- Network Address Translation (NAT)
- Platform and Infrastructure
- Software Installation and Upgrade
- Unified Threat Management (UTM)
- Additional Features
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for vMX
- play_arrow What's New
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Upgrade Instructions
- play_arrow Junos OS Release Notes for vRR
- play_arrow Junos OS Release Notes for vSRX
- play_arrow What's New
- play_arrow What's Changed
- Known Limitations
- Open Issues
- play_arrow Resolved Issues
- Documentation Updates
- Migration, Upgrade, and Downgrade Instructions
- Licensing
- Finding More Information
- Requesting Technical Support
- Revision History
ON THIS PAGE
Open Issues
Learn about open issues in Junos OS Release 21.4R3 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 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 theem0
interface of the vRR VNF. PR1648041
High Availability
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
Interfaces
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