Junos OS Release Notes for JRR Series
These release notes accompany Junos OS Release 20.3R3 for the JRR Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.
Learn about new features introduced in Junos OS Release main and maintenance releases for JRR Series Route Reflectors.
What's New in Release 20.3R3
There are no new features or enhancements to existing features for JRR Series in Junos OS Release 20.3R3.
What's New in Release 20.3R2
There are no new features or enhancements to existing features for JRR Series in Junos OS Release 20.3R2.
What's New in Release 20.3R1
Support for Implicit filter for default EBGP route propagation behavior without policies (ACX Series, JRR200, MX204, vRR and PTX5000)—Starting in Junos OS Release 20.3R1, we’ve introduced a new configuration hierarchy, defaults ebgp no-policy at the existing [edit protocols bgp] hierarchy level. The configuration option separates the default policy for receive and advertise, into separate clauses (accept, reject, or reject-always) to allow the route propagation behavior of EBGP speakers to vary independently from its default behavior.
In earlier releases, the default behavior of BGP was to receive and advertise all routes. With the introduction of this feature, the default behavior still remains to “accept” all routes for both receive and advertise, but you also have an option to reject routes by default.
With the reject configuration, you can reject routes of type inet unicast and inet6 unicast in instance types master, vrf, virtual-router, and non-forwarding. With the reject-always configuration, you can reject all routes from being received or getting advertised, irrespective of address family or instance type. By using this feature, you can control traffic in leaf autonomous systems (AS) and thereby, prevent them from having to accidentally function as transit autonomous systems.
The introduction of this implicit filter does not affect the existing deployments that rely on the default behavior.
There are no changes in behavior and syntax in Junos OS Release 20.3R3 for JRR Series Route Reflectors.
There are no known limitations JRR Series in Junos OS Release 20.3R3 for JRR Series Route Reflectors.
There are no open issues in Junos OS 20.3R3 Release for JRR Series Route Reflectors.
Learn about resolved issues for JRR Series in Junos OS 20.3R3 Release.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
Resolved Issues: 20.3R3
Alarm is generated when the enhanced-ip statement is configured. PR1554292
Option-60 (Vendor-Class-Identifier) is not sent during ZTP. PR1582038
Resolved Issues: 20.3R2
JRR200:firewall filter with non-zero TTL value can cause commit error. PR1531034
The tcp_timer_keep logs flooding on JRR200. PR1533168
On JRR200 devices, four out of eight fans might not work. PR1534706
On SRX4100 and SRX4200 devices, four out of eight fans might not work. PR1534706
The request system power-off and the request system halt commands are not working as expected on JRR200. PR1534795
Resolved Issues: 20.3R1
There are no fixed issues in Junos OS Release 20.3R1 for JRR Series Route Reflectors.
There are no errata or changes in Junos OS Release 20.3R3 documentation for JRR Series Route Reflectors.
Migration, Upgrade, and Downgrade Instructions
This section contains the upgrade and downgrade support policy for Junos OS for the JRR Series Route Reflector. Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration of the network.
Upgrade and Downgrade Support Policy for Junos OS Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.
You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 19.2, 19.3, and 19.4 are EEOL releases. You can upgrade from Junos OS Release 19.2 to Release 19.3 or from Junos OS Release 19.2 to Release 19.4.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.