Junos SRX380 Release Notes
Release
Published
2021-04-20
Notes
Junos®OS 20.1R1 Release Notes
SUPPORTED ON
ACX Series, EX Series, JRR Series, Junos Fusion Enterprise, Junos Fusion Provider Edge,
•
MX Series, NFX Series, PTX Series, QFX Series, and SRX Series
HARDWARE HIGHLIGHTS
SRX380 Services Gateway and Software support for SRX380
•
SOFTWARE HIGHLIGHTS
Sequential upgrade for Virtual Chassis (MX240, MX480, MX960, MX2010, MX2020, and
•
MX10003)
Delegation of IPv4 segment routing LSPs to a PCE (MX Series)
•
gRPC Dial-Out support on JTI (ACX Series, MX Series, PTX Series, QFX Series)
•
Unified ISSU with enhanced mode (MX240, MX480, MX960, MX2008, MX2010, MX2020)
•
AppQoE support for granular APBR rules (SRX Series)
•
Support for security policy reports (SRX Series)
•
Support for UPN as User Identity (SRX Series)
•
Trusted Platform Module (TPM) to bind secrets (SRX5400, SRX5600, and SRX5800)
•
IN FOCUS GUIDE
Use this new guide to quickly learn about the most important Junos OS features and how
•
you can deploy them in your network.
Release Notes: Junos®OS Release 20.1R1 for
the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, JRR
Series, and Junos Fusion
1
22 April 2021
Contents
Introduction | 13
Junos OS Release Notes for ACX Series | 13
What's New | 14
Interfaces and Chassis | 14
Junos OS XML API and Scripting | 15
Junos Telemetry Interface | 15
MPLS | 16
Routing Protocols | 17
System Management | 17
What's Changed | 18
Known Limitations | 18
General Routing | 18
Open Issues | 19
General Routing | 19
Resolved Issues | 20
General Routing | 21
Interfaces and Chassis | 22
Layer 2 Ethernet Services | 22
Routing Protocols | 22
Documentation Updates | 23
Dynamic Host Configuration Protocol (DHCP) | 23
Migration, Upgrade, and Downgrade Instructions | 23
Upgrade and Downgrade Support Policy for Junos OS Releases | 24
Junos OS Release Notes for EX Series Switches | 25
What's New | 25
EVPN | 27
Interfaces and Chassis | 27
Junos OS XML, API, and Scripting | 27
Junos Telemetry Interface | 27
Layer 2 Features | 28
Multicast | 28
Routing Policy and Firewall Filters | 29
Storage and Fibre Channel | 29
2
System Management | 29
Virtual Chassis | 30
What's Changed | 31
Class of Service (CoS) | 32
Interfaces and Chassis | 32
Multicast | 32
Known Limitations | 33
Infrastructure | 33
Platform and Infrastructure | 33
Open Issues | 34
General Routing | 34
Infrastructure | 36
Junos Fusion Provider Edge | 36
Junos Fusion Satellite Software | 36
Layer 2 Ethernet Services | 36
Multiprotocol Label Switching (MPLS) | 36
Platform and Infrastructure | 36
Routing Protocols | 37
Resolved Issues | 37
Authentication and Access Control | 38
Class of Service (CoS) | 38
EVPN | 38
Forwarding and Sampling | 38
General Routing | 38
Infrastructure | 40
Interfaces and Chassis | 40
Junos Fusion Enterprise | 41
Junos Fusion Satellite Software | 41
Layer 2 Features | 41
Layer 2 Ethernet Services | 41
Platform and Infrastructure | 41
Routing Protocols | 42
3
User Interface and Configuration | 42
Documentation Updates | 42
Dynamic Host Configuration Protocol (DHCP) | 43
Migration, Upgrade, and Downgrade Instructions | 43
Upgrade and Downgrade Support Policy for Junos OS Releases | 43
Junos OS Release Notes for JRR Series | 44
What's New | 45
What's Changed | 45
Known Limitations | 46
Open Issues | 46
Resolved Issues | 47
General Routing | 47
Documentation Updates | 47
Migration, Upgrade, and Downgrade Instructions | 48
Upgrade and Downgrade Support Policy for Junos OS Releases | 48
Junos OS Release Notes for Junos Fusion Enterprise | 49
What’s New | 50
What's Changed | 50
Known Limitations | 51
Open Issues | 51
Junos Fusion for Enterprise | 51
Resolved Issues | 52
Resolved Issues: 20.1R1 | 52
Documentation Updates | 53
Migration, Upgrade, and Downgrade Instructions | 53
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 54
Upgrading an Aggregation Device with Redundant Routing Engines | 56
Preparing the Switch for Satellite Device Conversion | 56
Converting a Satellite Device to a Standalone Switch | 57
Upgrade and Downgrade Support Policy for Junos OS Releases | 58
Downgrading from Junos OS | 58
Junos OS Release Notes for Junos Fusion Provider Edge | 59
What's New | 59
4
Hardware | 60
What's Changed | 60
Known Limitations | 61
Open Issues | 61
Junos Fusion Provider Edge | 62
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 63
Basic Procedure for Upgrading an Aggregation Device | 64
Upgrading an Aggregation Device with Redundant Routing Engines | 66
Preparing the Switch for Satellite Device Conversion | 67
Converting a Satellite Device to a Standalone Device | 68
Upgrading an Aggregation Device | 70
Upgrade and Downgrade Support Policy for Junos OS Releases | 71
Downgrading from Junos OS Release 20.1 | 71
Junos OS Release Notes for MX Series 5G Universal Routing Platform | 72
What's New | 72
Hardware | 73
Class Of Service | 74
EVPN | 76
Forwarding and Sampling | 76
General Routing | 76
High Availability and Resiliency | 76
Interfaces and Chassis | 78
Junos OS, XML, API, and Scripting | 83
Junos Telemetry Interface | 83
Layer 2 Features | 88
Layer 3 Features | 90
Management | 91
MPLS | 91
Multicast | 93
Network Management and Monitoring | 94
Next Gen Services | 94
OAM | 95
5
Port Security | 96
Routing Policy and Firewall Filters | 96
Routing Protocols | 97
Services Applications | 98
Software Defined Networking | 102
Subscriber Management and Services | 102
System Management | 103
User Interface and Configuration | 104
What's Changed | 104
Interfaces and Chassis | 105
Network Management and Monitoring | 105
Services Applications | 106
Subscriber Management and Services | 106
Known Limitations | 106
General Routing | 107
Infrastructure | 108
Platform and Infrastructure | 108
Services Applications | 108
Subscriber Management and Services | 108
VPNs | 109
Open Issues | 109
EVPN | 110
Forwarding and Sampling | 110
General Routing | 110
Infrastructure | 113
Interfaces and Chassis | 113
Junos Fusion Provider Edge | 114
Layer 2 Ethernet Services | 114
MPLS | 114
Platform and Infrastructure | 114
Routing Protocols | 115
Subscriber Access Management | 116
VPNs | 116
Resolved Issues | 116
6
Application Layer Gateways | 117
Authentication and Access Control | 117
Class of Service (CoS) | 117
EVPN | 118
Forwarding and Sampling | 118
General Routing | 119
Infrastructure | 127
Interfaces and Chassis | 128
Junos Fusion Enterprise | 129
Layer 2 Ethernet Services | 129
MPLS | 129
Network Management and Monitoring | 130
Platform and Infrastructure | 130
Routing Policy and Firewall Filters | 131
Routing Protocols | 131
Services Applications | 133
Subscriber Access Management | 133
User Interface and Configuration | 133
VPNs | 133
Documentation Updates | 134
Dynamic Host Configuration Protocol (DHCP) | 134
Migration, Upgrade, and Downgrade Instructions | 135
Basic Procedure for Upgrading to Release 20.1R1 | 136
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 136
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 139
Upgrade and Downgrade Support Policy for Junos OS Releases | 140
Upgrading a Router with Redundant Routing Engines | 141
Downgrading from Release 20.1R1 | 141
Junos OS Release Notes for NFX Series | 142
What’s New | 142
Application Security | 143
Interfaces | 144
Virtualized Network Functions (VNFs) | 144
7
What's Changed | 144
Known Limitations | 145
Open Issues | 145
Interfaces | 146
Platform and Infrastructure | 146
Resolved Issues | 147
High Availability | 147
Interfaces | 147
Mapping of Address and Port with Encapsulation (MAP-E) | 148
Platform and Infrastructure | 148
Routing Protocols | 148
Virtualized Network Functions (VNFs) | 148
Documentation Updates | 149
Migration, Upgrade, and Downgrade Instructions | 149
Upgrade and Downgrade Support Policy for Junos OS Releases | 150
Basic Procedure for Upgrading to Release 20.1 | 150
Junos OS Release Notes for PTX Series Packet Transport Routers | 152
What's New | 152
Interfaces and Chassis | 153
Junos OS XML API and Scripting | 153
Junos Telemetry Interface | 153
Routing Protocols | 157
MPLS | 157
Network Management and Monitoring | 158
System Management | 159
What's Changed | 159
Known Limitations | 160
General Routing | 160
Open Issues | 161
General Routing | 161
Infrastructure | 163
MPLS | 163
Routing Protocols | 163
Resolved Issues | 163
8
Forwarding and Sampling | 164
General Routing | 164
Infrastructure | 165
Interfaces and Chassis | 166
Layer 2 Ethernet Services | 166
MPLS | 166
Routing Protocols | 166
Documentation Updates | 167
Dynamic Host Configuration Protocol (DHCP) | 167
Migration, Upgrade, and Downgrade Instructions | 167
Basic Procedure for Upgrading to Release 20.1 | 168
Upgrade and Downgrade Support Policy for Junos OS Releases | 170
Upgrading a Router with Redundant Routing Engines | 171
Junos OS Release Notes for the QFX Series | 172
What's New | 172
EVPN | 174
High Availability (HA) and Resiliency | 174
Interfaces and Chassis | 174
Junos OS XML, API, and Scripting | 175
Junos Telemetry Interface | 175
Multicast | 176
Routing Policy and Firewall Filters | 177
Routing Protocols | 177
Software Defined Networking | 177
Storage and Fibre Channel | 177
System Management | 178
What's Changed | 179
Class of Service (CoS) | 179
Interfaces and Chassis | 179
Multicast | 180
Network Management and Monitoring | 180
Routing Protocols | 180
Known Limitations | 181
Class of Service (CoS) | 181
9
General Routing | 181
Infrastructure | 182
Layer 2 Ethernet Services | 182
Open Issues | 182
Class of Service (CoS) | 183
EVPN | 183
General Routing | 183
Interfaces and Chassis | 185
Layer 2 Features | 185
Layer 2 Ethernet Services | 186
Multiprotocol Label Switching (MPLS) | 186
Routing Protocols | 186
Resolved Issues | 187
Class of Service (CoS) | 187
EVPN | 188
Forwarding and Sampling | 188
General Routing | 188
High Availability (HA) and Resiliency | 192
Interfaces and Chassis | 192
Junos Fusion Enterprise | 192
Junos Fusion Satellite Software | 192
Layer 2 Features | 192
Layer 2 Ethernet Services | 193
Multiprotocol Label Switching (MPLS) | 193
Platform and Infrastructure | 193
Routing Protocols | 193
Documentation Updates | 194
Dynamic Host Configuration Protocol (DHCP) | 195
Migration, Upgrade, and Downgrade Instructions | 195
Upgrading Software on QFX Series Switches | 196
Installing the Software on QFX10002-60C Switches | 198
Installing the Software on QFX10002 Switches | 198
Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release
15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and
QFX10016 Switches | 199
10
Installing the Software on QFX10008 and QFX10016 Switches | 201
Performing a Unified ISSU | 205
Preparing the Switch for Software Installation | 206
Upgrading the Software Using Unified ISSU | 206
Upgrade and Downgrade Support Policy for Junos OS Releases | 208
Junos OS Release Notes for SRX Series | 209
What’s New | 210
Application Security | 211
Authentication and Access Control | 211
Flow-Based and Packet-Based Processing | 212
GPRS | 212
Hardware | 213
Interfaces and Chassis | 213
Intrusion Detection and Prevention | 213
Juniper Sky ATP | 214
Junos OS XML API and Scripting | 214
J-Web | 214
Network Management and Monitoring | 215
Port Security | 216
Security | 216
System Management | 216
Tenant Systems and Logical Systems | 216
VPNs | 217
What's Changed | 218
ALG | 218
Application Security | 218
Ethernet Switching and Bridging | 220
J-Web | 220
Unified Threat Management (UTM) | 220
VPNs | 220
Known Limitations | 221
J-Web | 222
Platform and Infrastructure | 222
VPNs | 222
11
Open Issues | 223
Flow-Based and Packet-Based Processing | 223
Platform and Infrastructure | 223
Routing Policy and Firewall Filters | 223
VPNs | 224
Resolved Issues | 224
Application Layer Gateways (ALGs) | 224
Authentication and Access Control | 225
Chassis Clustering | 225
Flow-Based and Packet-Based Processing | 225
Interfaces and Chassis | 226
Intrusion Detection and Prevention (IDP) | 227
J-Web | 227
Layer 2 Ethernet Services | 227
Network Address Translation (NAT) | 227
Network Management and Monitoring | 227
Platform and Infrastructure | 227
Routing Policy and Firewall Filters | 228
Routing Protocols | 228
Unified Threat Management (UTM) | 229
VLAN Infrastructure | 229
VPNs | 229
Documentation Updates | 230
Dynamic Host Configuration Protocol (DHCP) | 231
Migration, Upgrade, and Downgrade Instructions | 231
Upgrade and Downgrade Support Policy for Junos OS Releases and Extended End-Of-Life
Releases | 231
Upgrading Using ISSU | 232
Licensing | 233
Compliance Advisor | 233
Finding More Information | 233
Documentation Feedback | 234
Requesting Technical Support | 235
Self-Help Online Tools and Resources | 235
12
Creating a Service Request with JTAC | 236
Revision History | 236
Introduction
Junos OS runs on the following Juniper Networks®hardware: ACX Series, EX Series, M Series, MX Series,
NFX Series, PTX Series, QFabric systems, QFX Series, SRX Series, T Series, JRR Series, and Junos Fusion.
These release notes accompany Junos OS Release 20.1R1 for the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, JRR Series, and Junos Fusion. They describe new and changed
features, limitations, and known and resolved problems in the hardware and software.
In Focus guide—We have a document called In Focus that provides details on the most important features
•
for the release in one place. We hope this document will quickly get you to the latest information about
Junos OS features. Let us know if you find this information useful by sending an e-mail to
techpubs-comments@juniper.net.
Important Information:
•
Upgrading Using ISSU on page 232
•
13
Licensing on page 233
•
Compliance Advisor on page 233
•
Finding More Information on page 233
•
Documentation Feedback on page 234
•
Requesting Technical Support on page 235
•
Junos OS Release Notes for ACX Series
IN THIS SECTION
What's New | 14
What's Changed | 18
Known Limitations | 18
Open Issues | 19
Resolved Issues | 20
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
These release notes accompany Junos OS Release 20.1R1 for the ACX 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.
What's New
IN THIS SECTION
Interfaces and Chassis | 14
Junos OS XML API and Scripting | 15
Junos Telemetry Interface | 15
MPLS | 16
14
Routing Protocols | 17
System Management | 17
Learn about new features introduced in the Junos OS main and maintenance releases for ACX Series
routers.
Interfaces and Chassis
Support for new show | display set CLI commands (ACX Series, MX Series, PTX Series, QFX Series, and
•
SRX Series)—Starting in Junos OS Release 20.1R1, the following new show commands have been
introduced:
show | display set explicit—Display explicitly, as a series of commands, all the configurations that the
•
system internally creates when you configure certain statements from the top level of the hierarchy.
show | display set relative explicit—Display explicitly, as a series of commands, all the configurations
•
that the system internally creates when you configure certain statements from the current hierarchy
level.
[See show | display set and show | display set relative.]
Junos OS XML API and Scripting
The jcs:load-configuration template supports loading the rescue configuration (ACX Series, EX Series,
•
MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 20.1R1, the
jcs:load-configuration template supports the rescue parameter to load and commit the rescue
configuration on a device. SLAX and XSLT scripts can call the jcs:load-configuration template with the
rescue parameter set to "rescue" to replace the active configuration with the rescue configuration.
[See Changing the Configuration Using SLAX and XSLT Scripts and jcs:load-configuration Template.]
Junos Telemetry Interface
•
gRPC Dial-Out support on JTI (ACX Series, MX Series, PTX Series, and QFX Series)—Junos OS Release
20.1R1 provides remote procedure call (gRPC) dial-out support for telemetry. In this method, the target
device (server) initiates a gRPC session with the collector (client) and, when the session is established,
streams the telemetry data that is specified by the sensor-group subscription to the collector. This is in
contrast to the gRPC network management interface (gNMI) dial-in method, in which the collector
initiates a connection to the target device.
15
gRPC dial-out provides several benefits as compared to gRPC dial-in, including simplifying access to the
target advice and reducing the exposure of target devices to threats outside of their topology.
To enable export of statistics, include the export-profile and sensor statements at the [edit services
analytics] hierarchy level. The export profile must include the reporting rate, the transport service (for
example, gRPC), and the format (for example, gbp-gnmi). The sensor configuration should include the
name of the collector (the server’s name), the name of the export profile, and the resource path. An
example of a resource path is /interfaces/interface[name='fxp0'.
[See Using gRPC Dial-Out for Secure Telemetry Collection.]
•
gRPC version v1.18.0 with JTI (ACX Series, MX Series, PTX Series, and QFX Series)—Junos OS Release
20.1R1 includes support for remote procedure call (gRPC) services version v1.18.0 with Junos telemetry
interface (JTI). This version includes important enhancements for gRPC. In earlier releases, JTI is supported
with gRPC version v1.3.0.
Use gRPC in combination with JTI to stream statistics at configurable intervals from a device to an outside
collector.
[See gRPC Services for Junos Telemetry Interface.]
MPLS
CoS-based forwarding and policy-based routing to steer selective traffic over an SR-TE path (ACX
•
Series, MX Series, and PTX Series)—Starting in Junos OS Release 20.1R1, you can use CoS-based
forwarding (CBF) and policy-based routing (PBR, also known as filter-based forwarding or FBF) to steer
service traffic using a particular segment routing-traffic-engineered (SR-TE) path. This feature is supported
only on uncolored segment routing LSPs that have the next hop configured as a first hop label or an IP
address.
With CBF and PBR, you can :
Choose an SR-TE path on the basis of service.
•
Choose the supporting services to resolve over the selected SR-TE path.
•
16
[See Example: Configuring CoS-Based Forwarding and Policy-Based Routing For SR-TE LSPs.]
Routing Protocols
Support for topology-independent loop-free alternate (TI-LFA) in IS-IS for IPv6-only networks (ACX
•
Series, MX Series, and PTX Series)— Starting with Junos OS Release 20.1R1, you can configure TI-LFA
with segment routing in an IPv6-only network for the IS-IS protocol. TI-LFA provides MPLS fast reroute
(FRR) backup paths corresponding to the post-convergence path for a given failure. TI-LFA provides
protection against link failure, and node failure.
You can enable TI-LFA for IS-IS by configuring the use-post-convergence-lfa statement at the [edit
protocols isis backup-spf-options] hierarchy level. You can enable the creation of post-convergence
backup paths for a given IPv6 interface by configuring the post-convergence-lfa statement at the [edit
protocols isis interface interface-name level level] hierarchy level. The post-convergence-lfa statement
enables link-protection mode.
You can enable node-protection mode for a given interface at the [edit protocols isis interface
interface-name level level post-convergence-lfa] hierarchy level. However, you cannot configure
fate-sharing protection for IPv6-only networks.
17
[See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS.]
System Management
Restrict option under NTP configuration is now visible (ACX Series, QFX Series, MX Series, PTX Series,
•
and SRX Series)—Starting in Junos OS Release 20.1R1, the noquery command under the restrict hierarchy
is now available and can be configured with a mask address. The noquery command is used to restrict
ntpq and ntpdc queries coming from hosts and subnets.
[See Configuring NTP Access Restrictions for a Specific Address.]
SEE ALSO
What's Changed | 18
Known Limitations | 18
Open Issues | 19
Resolved Issues | 20
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
What's Changed
There are no changes in behavior and syntax for ACX Series in Junos OS Release 20.1R1.
SEE ALSO
What's New | 14
Known Limitations | 18
Open Issues | 19
Resolved Issues | 20
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
18
Known Limitations
IN THIS SECTION
General Routing | 18
Learn about known limitations in this release for ACX Series routers.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
General Routing
ACX6360 Junos telemetry interface or telemetry infrastructure does not support the interface-filtering
•
capability. Therefore, after you enable a particular sensor for telemetry, it is turned on for all the interfaces.
PR1371996
ACX Series routers support only 900 joins of IGMPv3 users per second. PR1448146
•
SEE ALSO
What's New | 14
What's Changed | 18
Open Issues | 19
Resolved Issues | 20
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
Open Issues
IN THIS SECTION
General Routing | 19
19
Learn about open issues in this release for ACX Series routers.
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 ACX Series routers, which are acting as PE routers for Layer 2 VPN, Layer 2 circuit, VPLS, and Layer
•
3 VPN services, traffic forwarding over the MPLS paths used by these services can be stopped. you
experience the traffic forwarding issue when the LSP flaps between the primary and the backup paths
in a particular sequence. PR1204714
The link fault signaling (LFS) feature is not supported on ACX5448 10-Gigabit, 40-Gigabit, and 100-Gigabit
•
Ethernet interfaces. PR1401718
When timing configuration and corresponding interface configurations are flapped for multiple times in
•
iteration, PTP is stuck in INITIALIZE state where the ARP for the neighbor is not resolved. In the issue
state, BCM hardware block gets into inconsistency state, where the lookup fails. PR1410746
CoS table error might sometimes cause traffic outages and SNMP timeouts, if the optic module is plugged
•
out and inserted back. PR1418696
On ACX5000 platform, the high CPU usage by the fxpc process might be seen under a rare condition if
•
parity errors are detected in devices. It has no direct service/traffic impact. However, because CPU
utilization is high when this issue occurs, there are some side effects. For example, the issue could impact
time-sensitive features such as BFD. PR1419761
The configuration of em2 interface causes the FPC to crash during initialization and the FPC does not
•
come online. To recover the FPC, first delete the em2 configuration, commit the configuration then
restart the router. PR1429212
Memory leaks are expected in Junos OS Release 20.1R1. PR1438358
•
Recovery of Junos OS volume is not possible from the OAM menu. PR1446512
•
On ACX500 and ACX4000, FFeb core could happen when heavy traffic of kernel trapped packets is
•
received due to recent SDK upgrade for ACX devices. PR1465802
- Issue seen during unified ISSU to Junos OS Releases 20.1- Unified ISSU will be completed, but the
•
Packet Forwarding Engine will not function. - Impact will be forwarding will be affected. PR1483959
SEE ALSO
What's New | 14
What's Changed | 18
20
Known Limitations | 18
Resolved Issues | 20
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
Resolved Issues
IN THIS SECTION
General Routing | 21
Interfaces and Chassis | 22
Layer 2 Ethernet Services | 22
Routing Protocols | 22
Learn which issues were resolved in the Junos OS main and maintenance releases for ACX Series routers.
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 ACX5000 routers, the internal error MacDrainTimeOut and bcm_port_update failed is seen.
•
PR1284590
High CPU utilization is seen for fxpc processes with CoS changes on the aggregated Ethernet interfaces.
•
PR1407098
The optics module comes with Tx enabled by default. As the port is administratively disabled, the port
•
is stopped but as the port has not been started, it does not disable Tx. PR1411015
The l2cpd process might crash and generate a core file when interfaces flap. PR1431355
•
ACX5448:DHCP packets are not transparent over Layer 2 circuit. PR1439518
•
On the ACX5448, the flexible VLAN tagging encapsulation is not supported with MPLS family, need to
•
provide commit ERROR. PR1445046
Fans on an ACX5448-M might not be running at the correct speed. PR1448884
•
The operating state for et- interfaces does not transit from init to normal. PR1449937
•
21
ACX5448-D interfaces support: After the 100-Gigabit and 40-Gigabit Ethernet interface are disabled,
•
the laser output power in the output of the show interfaces diagnostics optics command shows some
values. PR1452323
ACX5048 SNMP polling stops after the link is flapped or the SFP transceiver is replaced and
•
ACX_COS_HALP(acx_cos_gport_sched_set_strict_priority:987): Failed to detach logs will be seen.
PR1455722
ACX5448-D and ACX5448-M devices do not display airflow information and temperature sensors as
•
expected. PR1456593
ACX5448 Layer 2 VPN with the encapsulation-type ethernet configuration, stops passing traffic after
•
a random port is added with VLAN configuration. PR1456624
The rpd might crash if a BGP route is resolved over the same prefix protocol next hop in the inet.3 table
•
that has both RSVP and LDP routes. PR1458595
Route resolution is not happening when the packet size is 10,000. PR1458744
•
The traffic might be discarded silently during link recovery in an open ethernet access ring with ERPS
•
configured. PR1459446
ACX5000: SNMP MIB walk for jnxOperatingTemp is not returning anything for an FPC in new versions.
•
PR1460391
ACX5448-M interfaces and optics support: When you enable local loopback, the 10-Gigabit Ethernet
•
interface goes down. PR1460715
ACX5448-D interfaces and optics support: Sometimes when you bring up the aggregated Ethernet
•
interface, there are ARP resolution issues. PR1461485
On ACX Series platform, the LLDP neighbor is not up on the LAG after software upgrade to Junos OS
•
Release 18.2R3-S1. PR1461831
Not able to add more than 16 links in a LAG. PR1463253
•
Memory leak on l2cpd process might lead to l2cpd crash. PR1469635
•
RED drops are seen on interfaces even without any congestion. PR1470619
•
The dcpfe core is seen when disabling or enabling MACsec through ACX6360-OR scripts. PR1479710
•
ACX5448 Layer 2 VPN with interface ethernet-ccc input-vlan-map/output-vlan-map can cause trafficto
•
be discarded silently. PR1485444
Interfaces and Chassis
MC-AE interface might show unknown status if you add the subinterface as part of the VLAN on the
•
peer MC-AE node. PR1479012
22
Layer 2 Ethernet Services
Member links state might be asychronized on a connection between the PE and CE devices in an EVPN
•
A/A scenario. PR1463791
Routing Protocols
The rpd might crash continuously because of memory corruption in the IS-IS setup. PR1455432
•
SEE ALSO
What's New | 14
What's Changed | 18
Known Limitations | 18
Open Issues | 19
Documentation Updates | 23
Migration, Upgrade, and Downgrade Instructions | 23
Documentation Updates
IN THIS SECTION
Dynamic Host Configuration Protocol (DHCP) | 23
This section lists the errata and changes in Junos OS Release 20.1R1 for the ACX Series documentation
Dynamic Host Configuration Protocol (DHCP)
Introducing DHCP User Guide—Starting in Junos OS Release 20.1R1, we are introducing the DHCP
•
User Guide for Junos OS routing, switching, and security platforms. This guide provides basic configuration
details for your Junos OS device as DHCP Server, DHCP client, and DHCP relay agent.
23
[See DHCP User Guide.]
SEE ALSO
What's New | 14
What's Changed | 18
Known Limitations | 18
Open Issues | 19
Resolved Issues | 20
Migration, Upgrade, and Downgrade Instructions | 23
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Upgrade and Downgrade Support Policy for Junos OS Releases | 24
This section contains the upgrade and downgrade support policy for Junos OS for the ACX Series Router.
Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration
of the network.
For information about software installation and upgrade, see the Installation and Upgrade Guide.
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 17.1,
17.2, and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from
Junos OS Release 17.1 to Release 17.3.
24
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.
For information about software installation and upgrade, see the Installation and Upgrade Guide.
SEE ALSO
What's New | 14
What's Changed | 18
Known Limitations | 18
Open Issues | 19
Resolved Issues | 20
Migration, Upgrade, and Downgrade Instructions | 23
Junos OS Release Notes for EX Series Switches
IN THIS SECTION
What's New | 25
What's Changed | 31
Known Limitations | 33
Open Issues | 34
Resolved Issues | 37
Documentation Updates | 42
Migration, Upgrade, and Downgrade Instructions | 43
25
These release notes accompany Junos OS Release 20.1R1 for the EX 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.
What's New
IN THIS SECTION
EVPN | 27
Interfaces and Chassis | 27
Junos OS XML, API, and Scripting | 27
Junos Telemetry Interface | 27
Layer 2 Features | 28
Multicast | 28
Routing Policy and Firewall Filters | 29
Storage and Fibre Channel | 29
System Management | 29
Virtual Chassis | 30
Learn about new features introduced in the Junos OS main and maintenance releases for EX Series switches.
NOTE: The following EX Series switches are supported in Release 20.1R1: EX2300, EX2300-C,
EX3400, EX4300, EX4600-40F, EX4650, EX9200, EX9204, EX9208, EX9214, EX9251, and
EX9253.
26
EVPN
Routing traffic between a VXLAN and a Layer 3 logical interface (EX4650 and QFX5120)—Starting in
•
Junos OS Release 20.1R1, EX4650 and QFX5120 switches support the routing of traffic between a
Virtual Extensible LAN (VXLAN) and a Layer 3 logical interface. (You can configure the Layer 3 logical
interface using the set interfaces interface-name unit logical-unit-number family inet address
ip-address/prefix-length or the set interfaces interface-name unit logical-unit-number family inet6 address
ipv6-address/prefix-length command.) This feature is enabled by default, so you do not need to take any
action to enable it.
NOTE: By default, this feature is disabled on QFX5110 switches. To enable the feature on
QFX5110 switches, you must perform the configuration described in Understanding How to
Configure VXLANs and Layer 3 Logical Interfaces to Interoperate.
27
Interfaces and Chassis
Support for static link protection on aggregated interfaces (EX4650, QFX5120-32C, and
•
QFX5120-48Y)—Starting in Junos OS Release 20.1R1, you can enable link protection on aggregated
interfaces for a specified static label-switched path (LSP). You can designate a primary and a backup
physical link to support link protection. Egress traffic passes only through the designated primary link.
This traffic includes transit traffic and locally generated traffic on the router. When the primary link fails,
traffic is routed through the backup link.
[See link-protection.]
Junos OS XML, API, and Scripting
The jcs:load-configuration template supports loading the rescue configuration (ACX Series, EX Series,
•
MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 20.1R1, the
jcs:load-configuration template supports the rescue parameter to load and commit the rescue
configuration on a device. SLAX and XSLT scripts can call the jcs:load-configuration template with the
rescue parameter set to "rescue" to replace the active configuration with the rescue configuration.
[See Changing the Configuration Using SLAX and XSLT Scripts and jcs:load-configuration Template.]
Junos Telemetry Interface
•
MPLS and local routing sensor streaming support on JTI (EX2300, EX3400, EX4300, EX4600, and
EX9200)—Junos OS Release 20.1R1 provides MPLS constrained-path Label Switched Paths (LSPs),
RSVP-Traffic Engineering (RSVP-TE) and local routing statistics using Junos telemetry interface (JTI) and
remote procedure call (gRPC) services. Streaming statistics are sent to an outside collector at configurable
intervals.
The following resource paths are supported:
Local routing (resource path /local-routes/)
•
MPLS constrained-path LSPs and RSVP-TE (resource path /network-instances/network-instance/
•
mpls/)
To provision the sensor to export data through gRPC services, use the telemetrySubscribe RPC.
Streaming telemetry data through gRPC or gNMI also requires the OpenConfig for Junos OS module.
[See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]
•
JTI infrastructure support for (EX2300, EX2300-MP, and EX3400)—Junos OS Release 20.1R1 provides
Junos telemetry interface (JTI) infrastructure support for EX2300, EX2300-MP, and EX3400 switches.
Layer 2 Features
28
Q-in-Q support on redundant trunk links using LAGs with link protection (EX4300-MP switches and
•
Virtual Chassis)—Starting in Junos OS Release 20.1R1, Q-in-Q is supported on redundant trunk links
(also called “RTGs”) using LAGs with link protection. Redundant trunk links provide a simple solution for
network recovery when a trunk port on a switch goes down. In that case, traffic is routed to another
trunk port, keeping network convergence time to a minimum.
Q-in-Q support on redundant trunk links on a LAG with link protection also includes support for the
following items:
Configuration of flexible VLAN tagging on the same LAG that supports the redundant links
•
configurations
Multiple redundant links configurations on one physical interface
•
Multicast convergence
•
[See Q-in-Q Support on Redundant Trunk Links Using LAGs with Link Protection.]
Multicast
PIM with IPv6 multicast traffic (EX4650 and QFX5120-48Y)—Starting in Junos OS Release 20.1R1,
•
EX4650 and QFX5120-48Y switches support Protocol Independent Multicast (PIM) with IPv6 multicast
traffic as follows:
PIM sparse mode (PIM-SM), PIM dense mode (PIM-DM), and PIM sparse-dense mode (PIM-SDM)
•
PIM any-source multicast (PIM-ASM) and PIM source-specific multicast (PIM-SSM)
•
Static, embedded, and anycast rendezvous points (RPs)
•
[See PIM Overview.]
Routing Policy and Firewall Filters
Support for flexible-match-mask match condition (EX4650 and QFX-Series)—Starting with Junos OS
•
Release 20.1R1, for EX4650, QFX5120-32C, and QFX5120-48Y switches, the flexible-match-mask
match condition in firewall filters is supported for the inet, inet6, and ethernet-switching families. With
this feature, you can configure a filter by specifying the length of the match (4 bytes maximum) starting
from a Layer 2 or Layer 3 packet offset.
[See Firewall Filter Flexible Match Conditions.]
Storage and Fibre Channel
FIP snooping (EX4650-48Y and QFX5120-48Y)—Starting in Junos OS Release 20.1R1, EX4650-48Y
•
and QFX5120-48Y switches support Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP)
snooping. With FIP snooping enabled on these switches, you prevent unauthorized access and data
transmission to a Fibre Channel (FC) network by permitting only those servers that have logged in to
the FC network to access the network. You enable FIP snooping on FCoE VLANs when the switch is
being used as an FCoE transit switch that connects FC initiators (servers) on the Ethernet network to
FCoE forwarders at the FC storage area network (SAN) edge.
29
[See Understanding FCoE Transit Switch Functionality and Understanding VN_Port to VN_Port FIP
Snooping on an FCoE Transit Switch.]
System Management
Change status LED for network port to chassis beacon light (EX4300-48MP switch and EX4300-48MP
•
Virtual Chassis)—By default, when a network port and its associated link are active, the status LED for
that port blinks green 8 times per second. Starting in Junos OS Release 20.1R1, you can use the request
chassis beacon command to slow down the current blinking rate to 2 blinks per second. The
slower-blinking and steadier green light acts as a beacon that leads you to an EX4300-48MP switch or
a particular port in a busy lab.
Using options with the request chassis beacon command, you can do the following for one or all network
port status LEDs on a specified FPC:
Turn on the beacon light for:
•
5 minutes (default)
•
A specified number of minutes (1 through 120)
•
Turn off the beacon light:
•
Immediately
•
Loading...