Junos OS Release Notes for JRR Series
These release notes accompany Junos OS Release 20.4R3 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 the Junos OS main and maintenance releases for JRR Series Route Reflectors.
What's New in Release 20.4R3
There are no new features or enhancements to existing features for JRR Series in Junos OS Release 20.4R3.
What's New in Release 20.4R2
There are no new features or enhancements to existing features for JRR Series in Junos OS Release 20.4R2.
What's New in Release 20.4R1
Support for BGP Sharding (JRR200)—Starting in Junos OS Release 20.4R1, we support BGP sharding. BGP sharding splits a BGP RIB into several sub RIBs and each sub RIB handles a subset of BGP routes. Each sub RIB is served by a separate RPD thread to achieve parallel processing. This results in reduced convergence time and faster performance. BGP sharding is disabled by default.
To enable BGP sharding, configure rib-sharding at the [edit system processes routing bgp] hierarchy level. Sharding is dependent on the update I/O thread feature. Therefore, you need to enable update I/O thread when you configure sharding. To enable update I/O, configure update-threading at the [edit system processes routing bgp] hierarchy level for rib-sharding configuration to pass commit check.
If you configure rib-sharding on a routing engine, RPD will create sharding threads. By default the number of sharding and update threads created is same as the number of CPU cores on the routing engine. Optionally, you can specify the number-of-shards and number-of-threads you want to create.
BGP sharding is supported for IPv4, IPv6, L3VPN and BGP-LU. All the other RIBs are processed without sharding.
There are no changes in behavior and syntax in Junos OS Release 20.4R3 for JRR Series Route Reflectors.
Learn about known limitations in this release for JRR200 Route Reflectors.
These features are not supported in Junos OS 20.4R1 release for BGP Sharding:
routing-options validations with rib sharding
inet4/6 unicast rib-group along with rib sharding
outbound route-filter with bgp sharding.
There are no open issues in this release for JRR Series Route Reflectors.
This section lists the issues fixed in Junos OS Release 20.4R3 for JRR Series routers.
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.4R3
JRR200: Option-60 (Vendor-Class-Identifier) is not sent during ZTP. PR1582038
Resolved Issues: 20.4R2
There are no fixed issues in the Junos OS Release 20.4R2 for JRR Series routers.
Resolved Issues: 20.4R1
On the JRR200 routers, the firewall filter with non-zero TTL value might cause a commit error. PR1531034
tcp_timer_keep logs flood on JRR200. PR1533168
Optics info of physical interfaces is not available for JRR200 on Junos OS. PR1537261
The CLI "request system power-off" and "request system halt" commands do not work as expected on JRR200. PR1534795
There are no errata or changes in Junos OS Release 20.4R3 documentation for JRR200 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
We have two types of releases, EOL and EEOL:
End of Life (EOL) releases have engineering support for twenty four months after the first general availability date and customer support for an additional six more months.
• Extended End of Life (EEOL) releases have engineering support for thirty six months after the first general availability date and customer support for an additional six more months.
For both EOL and EEOL releases, you can upgrade to the next three subsequent releases or downgrade to the previous three releases. For example, you can upgrade from 19.2 to the next three releases – 19.3, 19.4 and 20.1 or downgrade to the previous three releases – 19.1, 18.4 and 18.3.
For EEOL releases only, you have an additional option - you can upgrade directly from one EEOL release to the next two subsequent EEOL releases, even if the target release is beyond the next three releases. Likewise, you can downgrade directly from one EEOL release to the previous two EEOL releases, even if the target release is beyond the previous three releases. For example, 19.2 is an EEOL release. Hence, you can upgrade from 19.2 to the next two EEOL releases – 19.3 and 19.4 or downgrade to the previous two EEOL releases – 19.1 and 18.4.4.
End of Engineering (EOE)
End of Support (EOS)
Upgrade and Downgrade to subsequent 3 releases
Upgrade and Downgrade to subsequent 2 EEOL releases
End of Life (EOL)
End of Engineering + 6 months
Extended End of Life (EEOL)
End of Engineering + 6 months
For more information about EOL and EEOL releases, see https://www.juniper.net/support/eol/junos.html.
For information about software installation and upgrade, see the Installation and Upgrade Guide.