MX Series,
NFX Series, PTX Series, QFX Series, and SRX Series
HARDWARE HIGHLIGHTS
Wi-Fi Mini-Physical Interface Module (SRX320, SRX340, SRX345, and SRX550M)
•
SOFTWARE HIGHLIGHTS
Support for EVPN routing policies (ACX5448)
•
Inline monitoring services (MX Series with MPCs excluding MPC10E linecards)
•
Support for BGP PIC Edge with BGP labeled unicast (MX Series and PTX Series)
•
Integrating RIFT protocol into Junos OS (MX Series and VMX virtual routers)
•
Support for flexible algorithm in IS-IS for segment routing–traffic engineering (MX Series
•
and PTX Series)
Junos Multi-Access User Plane (MX240, MX480, MX960)
•
Support for Lawful Intercept on Junos Multi-Access User Plane (MX240, MX480, MX960)
•
Precision Time Protocol (PTP) transparent clock (QFX5120 and QFX5210)
•
Additional support for Bidirectional Forwarding Detection (QFX5110, QFX5120, QFX5200,
•
and QFX5210)
Selectively disable midstream APBR (SRX Series and vSRX)
•
Improved query performance in on-box reporting (SRX300, SRX320, SRX340, SRX345,
•
SRX550M, SRX1500, SRX4100, SRX4200, SRX4600, and vSRX)
UTM Support for Active/Active Chassis Cluster (SRX Series)
•
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 19.4R1 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 | 14
Junos OS Release Notes for ACX Series | 14
What's New | 15
EVPN | 15
Junos OS XML API and Scripting | 16
MPLS | 18
OAM | 18
Routing Protocols | 18
System Logging | 19
Software Defined Networking (SDN) | 19
What's Changed | 20
General Routing | 20
Routing Protocols | 20
Known Limitations | 21
General Routing | 21
Open Issues | 22
General Routing | 22
Resolved Issues | 23
General Routing | 24
Layer 2 Ethernet Services | 26
Platform and Infrastructure | 26
Routing Protocols | 26
Documentation Updates | 26
Feature Guides Are Renamed As User Guides | 27
Migration, Upgrade, and Downgrade Instructions | 27
Upgrade and Downgrade Support Policy for Junos OS Releases | 27
Junos OS Release Notes for EX Series Switches | 28
What's New | 29
Authentication, Authorization, and Accounting | 30
Class of Service | 30
EVPN | 30
2
Junos OS XML, API, and Scripting | 32
Junos Telemetry Interface | 33
Layer 2 Features | 34
MPLS | 36
Multicast | 36
Operation, Administration, and Maintenance (OAM) | 36
Port Security | 37
Routing Policy and Firewall Filters | 38
System Logging | 38
System Management | 38
User Interface and Configuration | 39
What's Changed | 39
What’s Changed in Release 19.4R1-S3 | 40
What's Changed in Release 19.4R1 | 40
Known Limitations | 41
Open Issues | 42
Authentication and Access Control | 43
Class of Service (CoS) | 43
EVPN | 43
General Routing | 43
Infrastructure | 45
Interfaces and Chassis | 45
Junos Fusion Enterprise | 45
Junos Fusion Satellite Software | 45
Layer 2 Ethernet Services | 45
Layer 2 Features | 46
Platform and Infrastructure | 46
Routing Protocols | 46
User Interface and Configuration | 47
Resolved Issues | 47
Authentication and Access Control | 48
EVPN | 48
General Routing | 48
Infrastructure | 50
3
Interfaces and Chassis | 51
Junos Fusion Enterprise | 51
Junos Fusion Satellite Software | 51
J-Web | 51
Layer 2 Ethernet Services | 51
Layer 2 Features | 51
Platform and Infrastructure | 52
Routing Protocols | 52
User Interface and Configuration | 53
Virtual Chassis | 53
Documentation Updates | 53
Feature Guides Are Renamed As User Guides | 54
Migration, Upgrade, and Downgrade Instructions | 54
Upgrade and Downgrade Support Policy for Junos OS Releases | 54
Junos OS Release Notes for JRR Series | 55
What's New | 56
Hardware | 56
What's Changed | 57
Known Limitations | 57
Open Issues | 58
General Routing | 58
Resolved Issues | 58
Documentation Updates | 59
Feature Guides Are Renamed As User Guides | 59
Migration, Upgrade, and Downgrade Instructions | 60
Upgrade and Downgrade Support Policy for Junos OS Releases | 60
Junos OS Release Notes for Junos Fusion Enterprise | 61
What’s New | 61
What’s Changed | 62
Known Limitations | 62
Open Issues | 63
Junos Fusion for Enterprise | 63
Resolved Issues | 64
4
Documentation Updates | 64
Feature Guides Are Renamed As User Guides | 65
Migration, Upgrade, and Downgrade Instructions | 65
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 66
Upgrading an Aggregation Device with Redundant Routing Engines | 67
Preparing the Switch for Satellite Device Conversion | 68
Converting a Satellite Device to a Standalone Switch | 69
Upgrade and Downgrade Support Policy for Junos OS Releases | 69
Downgrading from Junos OS | 70
Junos OS Release Notes for Junos Fusion Provider Edge | 71
What's New | 71
What's Changed | 72
Known Limitations | 72
Open Issues | 73
Junos Fusion for Provider Edge | 73
Resolved Issues | 73
Documentation Updates | 74
Feature Guides Are Renamed As User Guides | 74
Migration, Upgrade, and Downgrade Instructions | 75
Basic Procedure for Upgrading an Aggregation Device | 75
Upgrading an Aggregation Device with Redundant Routing Engines | 78
Preparing the Switch for Satellite Device Conversion | 78
Converting a Satellite Device to a Standalone Device | 80
Upgrading an Aggregation Device | 82
Upgrade and Downgrade Support Policy for Junos OS Releases | 82
Downgrading from Junos OS Release 19.4 | 83
Junos OS Release Notes for MX Series 5G Universal Routing Platform | 83
What's New | 84
Hardware | 85
Class of Service | 88
EVPN | 88
Forwarding and Sampling | 89
5
General Routing | 90
High Availability (HA) and Resiliency | 90
Interfaces and Chassis | 90
Junos OS, XML, API, and Scripting | 93
Junos Telemetry Interface | 94
Layer 2 Features | 96
Layer 2 VPN | 96
MPLS | 96
Multicast | 97
Network Management and Monitoring | 98
OAM | 98
Routing Policy and Firewall Filters | 98
Routing Protocols | 99
Services Applications | 102
Software-Defined Networking | 102
Software Licensing | 103
Subscriber Management and Services | 103
System Logging | 104
What's Changed | 105
General Routing | 105
Interfaces and Chassis | 106
MPLS | 107
Network Management and Monitoring | 107
Routing Protocols | 107
Services Applications | 107
Software-Defined Networking | 107
Subscriber Management and Services | 108
Known Limitations | 109
General Routing | 109
Interfaces and Chassis | 110
MPLS | 111
6
Platform and Infrastructure | 111
Routing Protocols | 111
Open Issues | 112
Application Layer Gateways | 113
Class of Service | 113
EVPN | 113
Forwarding and Sampling | 113
General Routing | 114
Infrastructure | 122
Interfaces and Chassis | 122
Layer 2 Features | 123
Layer 2 Ethernet Services | 123
MPLS | 124
Network Management and Monitoring | 124
Next Gen Services MX-SPC3 Services Card | 124
Platform and Infrastructure | 125
Routing Protocols | 126
Services Applications | 127
Subscriber Access Management | 128
VPNs | 128
Resolved Issues | 129
Resolved Issues: 19.4R1 | 129
Documentation Updates | 150
Feature Guides Are Renamed As User Guides | 150
Migration, Upgrade, and Downgrade Instructions | 151
Basic Procedure for Upgrading to Release 19.4 | 152
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 152
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 155
Upgrade and Downgrade Support Policy for Junos OS Releases | 156
Upgrading a Router with Redundant Routing Engines | 157
Downgrading from Release 19.4 | 157
Junos OS Release Notes for NFX Series | 158
What’s New | 158
General routing | 159
7
Hardware | 159
Architecture | 159
What's Changed | 160
Known Limitations | 161
Interfaces | 161
Platform and Infrastructure | 161
Open Issues | 162
Mapping of Address and Port with Encapsulation (MAP-E) | 162
Interfaces | 162
Platform and Infrastructure | 163
Virtual Network Functions (VNFs) | 164
Resolved Issues | 164
Class of Service | 165
High Availability | 165
Interfaces | 165
Layer 2 Ethernet Services | 166
Platform and Infrastructure | 166
Routing Protocols | 167
SNMP | 167
Virtual Network Functions (VNFs) | 167
Documentation Updates | 168
Feature Guides Are Renamed As User Guides | 168
Migration, Upgrade, and Downgrade Instructions | 169
Upgrade and Downgrade Support Policy for Junos OS Releases | 169
Basic Procedure for Upgrading to Release 19.4 | 169
Junos OS Release Notes for PTX Series Packet Transport Routers | 171
What's New | 172
General Routing | 173
Hardware | 173
High Availability (HA) and Resiliency | 173
Junos OS, XML, API, and Scripting | 173
Junos Telemetry Interface | 174
MPLS | 176
Routing Protocols | 177
8
Services Applications | 178
Software Defined Networking | 179
System Logging | 179
What's Changed | 180
General Routing | 180
Interfaces and Chassis | 180
Routing Protocols | 181
Software-Defined Networking | 181
Known Limitations | 181
General Routing | 182
Open Issues | 183
General Routing | 183
Infrastructure | 185
Layer 2 Ethernet Services | 185
MPLS | 185
Routing Protocols | 185
Resolved Issues | 186
Forwarding and Sampling | 186
General Routing | 186
Infrastructure | 188
Interfaces and Chassis | 188
Layer 2 Ethernet Services | 188
MPLS | 188
Platform and Infrastructure | 188
Routing Protocols | 188
VPNs | 189
Documentation Updates | 189
Feature Guides Are Renamed as User Guides | 190
Migration, Upgrade, and Downgrade Instructions | 190
Basic Procedure for Upgrading to Release 19.4 | 190
Upgrade and Downgrade Support Policy for Junos OS Releases | 193
Upgrading a Router with Redundant Routing Engines | 194
Junos OS Release Notes for the QFX Series | 195
What's New | 195
9
EVPN | 196
General Routing | 200
Interfaces and Chassis | 200
Junos OS XML API and Scripting | 201
Junos Telemetry Interface | 202
Layer 2 Features | 202
MPLS | 203
Routing Protocols | 203
Software Defined Networking (SDN) | 203
System Logging | 204
System Management | 205
VLAN Infrastructure | 206
What's Changed | 206
General Routing | 208
Interfaces and Chassis | 208
Management | 208
Routing Protocols | 208
Software Defined Networking (SDN) | 208
Known Limitations | 209
Layer 2 Ethernet Services | 210
Layer 2 Features | 210
Network Management and Monitoring | 210
Platform and Infrastructure | 210
Routing Protocols | 211
Open Issues | 211
Class of Service (CoS) | 212
EVPN | 212
High Availability (HA) and Resiliency | 213
Interfaces and Chassis | 213
Junos Fusion for Provider Edge | 213
Layer 2 Features | 213
Layer 2 Ethernet Services | 214
10
MPLS | 214
Platform and Infrastructure | 214
Routing Protocols | 217
Resolved Issues | 218
Class of Service (CoS) | 218
EVPN | 219
Forwarding and Sampling | 219
Interfaces and Chassis | 219
Layer 2 Features | 219
MPLS | 220
Platform and Infrastructure | 220
Routing Protocols | 224
User Interface and Configuration | 225
Documentation Updates | 226
Feature Guides Are Renamed As User Guides | 226
Migration, Upgrade, and Downgrade Instructions | 226
Upgrading Software on QFX Series Switches | 227
Installing the Software on QFX10002-60C Switches | 229
Installing the Software on QFX10002 Switches | 229
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 | 230
Installing the Software on QFX10008 and QFX10016 Switches | 232
Performing a Unified ISSU | 236
Preparing the Switch for Software Installation | 237
Upgrading the Software Using Unified ISSU | 237
Upgrade and Downgrade Support Policy for Junos OS Releases | 239
Junos OS Release Notes for SRX Series | 240
What’s New | 241
Application Security | 241
Chassis Clustering | 242
Flow-Based and Packet-Based Processing | 242
General Packet Radio Switching (GPRS) | 243
11
Hardware | 243
Interfaces and Chassis | 244
Intrusion Detection and Prevention (IDP) | 244
Junos OS XML API and Scripting | 245
J-Web | 246
Logical Systems and Tenant Systems | 246
Network Management and Monitoring | 247
System Logging | 248
Unified Threat Management (UTM) | 248
VPNs | 248
What's Changed | 249
Application Security | 250
Authentication and Access Control | 253
General Routing | 253
J-Web | 253
Network Management and Monitoring | 253
Port Security | 254
Routing Protocols | 254
VPNs | 254
Known Limitations | 255
Application Layer Gateways (ALGs) | 255
Ethernet Switching | 255
Flow-Based and Packet-Based Processing | 255
J-Web | 255
Open Issues | 256
ALG | 257
Flow-Based and Packet-Based Processing | 257
IDP | 257
J-Web | 257
Platform and Infrastructure | 257
Routing Policy and Firewall Filters | 257
VPNs | 258
Resolved Issues | 259
12
Application Layer Gateways | 259
Application Security | 259
Authentication and Access Control | 259
Chassis Clustering | 259
Class of Service | 260
Flow-Based and Packet-Based Processing | 260
Interfaces and Chassis | 262
Intrusion Detection and Prevention (IDP) | 262
J-Web | 262
Layer 2 Ethernet Services | 263
Network Address Translation | 263
Network Management and Monitoring | 263
Platform and Infrastructure | 263
Routing Policy and Firewall Filters | 264
Services Applications | 264
Unified Threat Management | 264
VLAN Infrastructure | 265
VPNs | 265
Documentation Updates | 266
Feature Guides Are Renamed As User Guides | 267
Migration, Upgrade, and Downgrade Instructions | 267
Upgrade and Downgrade Support Policy for Junos OS Releases and Extended End-Of-Life
Releases | 267
Upgrading Using ISSU | 268
Licensing | 269
Compliance Advisor | 269
Finding More Information | 269
Documentation Feedback | 270
Requesting Technical Support | 271
Self-Help Online Tools and Resources | 271
Creating a Service Request with JTAC | 272
Revision History | 272
13
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 19.4R1 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.
Feature Guides Are Renamed As User Guides—Starting with Junos OS 19.4R1, we renamed our Feature
•
Guides to User Guides to better reflect the purpose of the guides. For example, the BGP Feature Guide
is now the BGP User Guide. We didn’t change the URLs of the guides, so any existing bookmarks you
have will continue to work. To keep the terminology consistent on our documentation product pages,
we renamed the Feature Guides section to User Guides. To find documentation for your specific product,
check out this link.
New In Focus Guide—Starting on Junos Release 19.4R1, we are introducing a new 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 features. Let us know if you find
this information useful by sending email to techpubs-comments@juniper.net.
14
Important Information:
•
Upgrading Using ISSU on page 268
•
Licensing on page 269
•
Compliance Advisor on page 269
•
Finding More Information on page 269
•
Documentation Feedback on page 270
•
Requesting Technical Support on page 271
•
Junos OS Release Notes for ACX Series
IN THIS SECTION
What's New | 15
What's Changed | 20
Known Limitations | 21
Open Issues | 22
Resolved Issues | 23
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
These release notes accompany Junos OS Release 19.4R1 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
15
IN THIS SECTION
EVPN | 15
Junos OS XML API and Scripting | 16
MPLS | 18
OAM | 18
Routing Protocols | 18
System Logging | 19
Software Defined Networking (SDN) | 19
Learn about new features introduced in the Junos OS main and maintenance releases for ACX Series
routers.
EVPN
SPRING support for EVPN (ACX5448)—Starting in Junos OS Release 19.4R1, you can use Source Packet
•
Routing in Networking (SPRING) as the underlay transport in EVPN on ACX5448 routers. SPRING tunnels
enable routers to steer a packet through a specific set of nodes and links in the network.
To configure SPRING, use the source-packet-routing statement at the [edit protocols isis] hierarchy
level.
[See Understanding Source Packet Routing in Networking (SPRING).]
Support for EVPN features on new hardware (ACX5448)—Starting with Release 19.4R1, Junos OS
•
supports the following EVPN features:
EVPN E-TREE. [See EVPN E-TREE Overview.]
•
ARP/NDP proxy and suppression with proxy MAC responses. [See EVPN Proxy ARP and ARP
•
Suppression, and Proxy NDP and NDP Suppression.]
EVPN with segment routing (SPRING). [See Understanding Source Packet Routing in Networking
•
(SPRING).]
EVPN E-LAN services over MPLS, including support for VLAN-based and VLAN-bundles services. [See
•
EVPN Overview and Overview of VLAN Services for EVPN.]
Support for EVPN routing policies (ACX5448, EX4600, EX4650, EX9200, MX Series, QFX Series, and
•
vMX)—Starting in Junos OS Release 19.4R1, Junos OS has expanded routing policy support to include
the creation and application of policy filters specific to EVPN routes. You can create policies and apply
policy filters to import and export EVPN routes at the routing-instance level or at the BGP level. Junos
OS supports the following matching criteria for EVPN routes:
16
Route distinguisher ID
•
NLRI route type
•
EVPN Ethernet tag
•
BGP path attributes
•
Ethernet Segment Identifier
•
MAC Address on EVPN route type 2 routes
•
IP address on EVPN route type 2 and EVPN route type 5 routes
•
Extended community
•
[See Routing policies for EVPN.]
Junos OS XML API and Scripting
Automation script library upgrades (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX
•
Series)—Starting in Junos OS Release 19.4R1, devices running Junos OS that support the Python
extensions package include upgraded Python modules. Python scripts can leverage the upgraded versions
of the following modules:
idna (2.8)
•
jinja2 (2.10.1)
•
jnpr.junos (Junos PyEZ) (2.2.0)
•
lxml (4.3.3)
•
markupsafe (1.1.1)
•
ncclient (0.6.4)
•
packaging (19.0)
•
paho.mqtt (1.4.0)
•
pyasn1 (0.4.5)
•
yaml (PyYAML package) (5.1)
•
[See Overview of Python Modules Available on Devices Running Junos OS.]
Python 3 support for commit, event, op, and SNMP scripts (ACX Series, EX Series, MX Series, PTX
•
Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, you can use Python 3 to
execute commit, event, op, and SNMP scripts on devices running Junos OS. To use Python 3, configure
the language python3 statement at the [edit system scripts] hierarchy level. When you configure the
language python3 statement, the device uses Python 3 to execute scripts that support this Python
version and uses Python 2.7 to execute scripts that do not support Python 3 in the given release.
17
The Python 2.7 end-of-support date is January 1, 2020, and Python 2.7 will be EOL in 2020. The official
upgrade path for Python 2.7 is to Python 3. As support for Python 3 is added to devices running Junos
OS for the different types of onbox scripts, we recommend that you migrate supported script types from
Python 2 to Python 3, because support for Python 2.7 might be removed from devices running Junos
OS in the future.
[See Understanding Python Automation Scripts for Devices Running Junos OS.]
MPLS
Support for Topology Independent Loop-Free Alternate, advertising MPLS labels, and configuring SRGB
•
for SPRING for ISIS and OSPF (ACX5448-D and ACX5448-M)—Starting with Junos OS Release 19.4R1,
ACX5448-D and ACX5448-M router supports topology independent (TI)-loop-free alternate (LFA),
advertise MPLS labels (ISIS, OSPF), and segment routing global block (SRGB) for SPRING (ISIS, OSPF).
[See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS,
Understanding Source Packet Routing in Networking (SPRING).]
OAM
Support for Ethernet OAM and Metro Ethernet services over segment routing (ACX5448-D, ACX5448-M,
•
MX Series)—Starting with Junos OS Release 19.4R1, ACX5448-D, ACX5448-M and MX Series routers
support Ethernet OAM and Metro Ethernet services over segment routing.
[See Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING for
IS-IS Protocol, Understanding Topology-Independent Loop-Free Alternate with Segment Routing for
IS-IS, Ethernet OAM Connectivity Fault Management .]
18
Routing Protocols
Support for configurable SRGB used by SPRING in OSPF protocols (ACX5448)— Starting in Junos OS
•
Release 19.4R1, you can configure the segment routing global block (SRGB) range label used by segment
routing. Labels from this range are used for segment routing functionality in OSPF domain.
The SRGB is a range of the label values used in the segment routing. Prior to Junos OS Release 19.4R1,
you could not configure the range for the SRGB block.
Locally you can configure srgb start-label <label-range> index-range <index-range> command under
[edit protocols ospf source-packet-routing] hierarchy or globally under [edit protocols mpls label-range]
hierarchy.
Following are the SRGB precedences for OSPF protocol:
Local SRGB
•
Global SRGB
•
Node-segment implementation of 256 label block
•
Unnumbered interface support for IS-IS and OSPFv2 with topology-independent loop-free alternate
•
(ACX Series, MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, you can enable IPv4
processing on a point-to-point interface without assigning it an explicit IPv4 address. The router borrows
the IPv4 address of another Ethernet or loopback interface already configured on the router and assigns
it to the unnumbered interface to conserve IPv4 addresses.
To enable IPv4 processing for unnumbered interfaces include unnumbered-address source at the [editinterfaces [name] unit [name] family inet] hierarchy level.
[See Configuring an Unnumbered Interface.]
System Logging
Improved intermodule communication between FFP and MGD (ACX Series, EX Series, MX Series, PTX
•
Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, intermodule communication
is improved to enhance software debugging. To enhance error messages with more context, the exit
conditions from libraries have been updated as follows:
Additional information is now logged for MGD-FFP intermodule communication.
•
Commit errors that previously were only shown onscreen are now logged.
•
We provide a new operational command, request debug information, to speed up the initial
information-gathering phase of debugging.
19
[See request debug information.]
Software Defined Networking (SDN)
Tunnel templates for PCE-initiated segment routing LSPs (ACX Series)—Starting in Junos OS Release
•
19.4R1, you can configure a tunnel template for Path Computation Element (PCE)-initiated segment
routing LSPs and apply it through policy configuration. These templates enable dynamic creation of
segment routing tunnels with two additional parameters – Bidirectional forwarding detection (BFD) and
LDP tunneling.
With the support for tunnel configuration, the LSPs that you would configure statically can now be
automatically created from the PCE, thereby providing the benefit of reduced configuration on the
device.
[See Understanding Static Segment Routing LSP in MPLS Networks.]
SEE ALSO
What's Changed | 20
Known Limitations | 21
Open Issues | 22
Resolved Issues | 23
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
What's Changed
IN THIS SECTION
General Routing | 20
Routing Protocols | 20
Learn about what changed in Junos OS main and maintenance releases for ACX Series.
General Routing
Support for full inheritance paths of configuration groups to be built into the database by default (ACX
•
Series, MX Series, PTX Series, and SRX Series)—Starting with Junos OS Release 19.4R1, the
persist-groups-inheritance option at the [edit system commit] hierarchy level is enabled by default. Todisable this option, use no-persist-groups-inheritance.
20
[See commit (System).]
Support for gigether-options statement (ACX5048, ACX5096)—Junos OS supports the gigether-options
•
statement at the edit interfaces interface-name hierarchy on the ACX5048 and ACX5096 routers.
Previously, support for the gigether-statement was deprecated. See gigether-options and
Routing Protocols
XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX
•
Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release
19.4R1, we have included an XML RPC equivalent for the show bgp output-scheduler | display xml rpc
CLI command. In Junos OS releases before Release 19.4R1, the show bgp output-scheduler | displayxml rpc CLI command does not have an XML RPC equivalent.
[See show bgp output-scheduler.]
SEE ALSO
What's New | 15
Known Limitations | 21
Open Issues | 22
Resolved Issues | 23
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Known Limitations
IN THIS SECTION
General Routing | 21
Learn about known limitations in Junos OS Release 19.4R1 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.
21
General Routing
ACX6360-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
When the timing configuration and the corresponding interface configuration is flapped for multiple
•
times in iteration, PTP is stuck in initialize state where the ARP for the neighbor is not resolved. In issue
state, BCM hardware block get into inconsistency state, where the lookup is failing. PR1410746
The port LEDs and the system LED glow during system or vmhost halt state on all ACX Series devices.
•
PR1430129
With an asymmetric network connection (for example, 10G MACsec port connected to 10G channelized
•
port), high and asymmetric T1 and T4 time errors are seen, which introduces a high 2 way time error.
This introduces different CF updates in forward and reverse paths. PR1440140
With MACsec feature enabled and introduction of traffic, the peak-to-peak value varies with the
•
percentage of traffic introduced. PR1441388
You cannot directly associate a policer in an IFL on ACX Series devices. It has to be achieved using
•
"filters" only. In this case, "family any" filter can be configured. Also, ACX5448 hardware ASIC does not
support "egress policing". Egress shaping (H-QoS at the IFL level) can be used instead. PR1446376
ACX Series routers support rate of join of IGMPv3 users only around 900 joins per second. Same is
•
updated to PDD. PR1448146
SEE ALSO
What's New | 15
What's Changed | 20
Open Issues | 22
Resolved Issues | 23
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Open Issues
IN THIS SECTION
22
General Routing | 22
Learn about open issues in Junos OS Release 19.4R1 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
High CPU usage for fxpc processes with class-of-service changes on aggregated Ethernet interfaces.
•
PR1407098
On ACX1000, ACX2000, ACX4000, ACX5048, and ACX5096 devices, after a new child logical interface
•
with VLAN and filter is added on an aggregated Ethernet physical interface or after changing the VLAN
ID of a child logical interface with filter, traffic over the aggregated Ethernet physical interface might
get filtered with that filter on the child logical interface. For example, ae-0/0/0 is a physical interface
and ae-0/0/0.100 is a logical interface. PR1407855
Layer 2 rewrites happens on regular Bridge domain and VLAN interfaces. Though there are some service
•
dependencies, VPLS in this case, in which the Egress interface map table is not updated properly with
the Layer 2 rewrite map id that causes rewrite to stop working. PR1414414
CoS table error can sometimes cause traffic outages and SNMP timeouts if the optic is removed and
•
inserted back. PR1418696
On the ACX5000 line of devices, high CPU usage might be seen for the fxpc process. PR1419761
•
The request system reboot command on the ACX5448 and ACX5448-D box triggers a reboot on the
•
host (Linux) instead of being limited to Junos OS. PR1426486
DHCP clients are not able to scale to 96000. PR1432849
•
The time consumed for 1-Gigabit performance is not equal to the time for 10-Gigabit performance.
•
Compensation is done to bring the mean value under class A, but the peak-to-peak variations are high
and can go beyond 100ns. It has a latency variation with peak-to-peak variations of around 125ns-250ns
without any traffic (for example, 5-10% of the mean latency introduced by each phy, which is around
2.5us). PR1437175
Memory leaks are expected. PR1438358
•
ACX can support rate of join of IGMPv3 users only around 900 joins per second. Same will be updated
•
to PDD. PR1448146
Drop profile maximum threshold might not reach its limit when the packet size is other than 1000 bytes.
•
This is due to the current design limitation. PR1448418
Not possible to form 125000 IGMP groups with ACX5448 receiving 125000 IGMP v2 Reports per
•
second. This is a product limitation from BCM and CPU host path queuing model. PR1454465
23
SEE ALSO
What's New | 15
What's Changed | 20
Known Limitations | 21
Resolved Issues | 23
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Resolved Issues
IN THIS SECTION
General Routing | 24
Layer 2 Ethernet Services | 26
Platform and Infrastructure | 26
Routing Protocols | 26
Learn which issues were resolved in Junos OS Release 19.4R1 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 MacDrainTimeOut and bcm_port_update failed: Internal error error is seen. PR1284590
•
bcmDPC task is high even though Interuppt START_BY_START flag is set to 0. PR1329656
•
The AE interface with LACP stays down after the router reboots if link-speed is configured. PR1357012
•
On ACX Series devices, the LED on the GE interface goes down when speed 10M is added. PR1385855
•
Link Fault Signaling (LFS) doesn not work on ACX5448 10-, 40-, and 100-Gigabit Ethernet interfaces.
•
PR1401718
The optic comes with Tx enabled by default. Because the port is administratively disabled, the port is
•
stopped. However, because the port has not been started, it does not disable Tx. PR1411015
The ACX5448:40G FEC on ACX5448, which is FEC enabled by default, must be aligned with the MX
•
and QFX platforms, where FEC is NONE. PR1414649
24
On the ACX5448-X:SKU and ACX5448-D, 96000 ARPs get populated. However, only 47000 NH entries
•
are present. Around 50 percent of packet drop is observed. PR1426734
Chassisd might crash with unsupported hcos configuration when an MX104 is used as a fusion aggregation
•
device. PR1430076
The l2cpd process might crash and generate a core file when interfaces flaps. PR1431355
•
Deviation in traffic rate in the queue is around 8 % to 10% percent in some cases. PR1436297
•
1PPS performance metrics (class A) of G.8273.2 are not met for 1G interfaces because of the variable
•
latency added by the Vittesse PHY. PR1439231
The interface on ACX1100 devices remains down when using SFP-1FE-FX (740-021487). PR1439384
•
Transit DHCP packets are not punted to CPU and are transparently passthrough. PR1439518
•
When the interface is flapped between channelized configurations, 25-Gigabit Ethernet to 100-Gigabit
•
the aggregated Ethernet interface configuration is not cleaned up properly. PR1441374
In an ACX5448 platforms, when the PFE failed to allocate packet buffer, portion of packet memories
•
may not be freed. PR1442901
RED drops might be seen after link flaps or CoS configuration changes. PR1443466
•
ACX5448/18.3R1-S4.1 is not performing proper dot1p CoS rewrite on interfaces configured with
•
l2circuit/local-switching/family ccc. PR1445979
On ACX Series, the auto exported route between VRFs might not respond for icmp echo requests.
•
PR1446043
l2circuit with a backup-neighbor (hot-standby) configured might stop forwarding traffic after failovers.
•
PR1449681
oper-state for et interface does not transition from 'init' to 'Normal'. PR1449937
•
RMPC core files are found after configuration changes done on the network for PTP/Clock
•
Synchronization. PR1451950
After disabling 100G and 40G interface Laser output power in show interfaces diagnostics optics shows
•
some values. PR1452323
ACX5448 FPC crashed due to segmentation fault. PR1453766
•
Incorrect operating state is displayed in snmp trap for fan removal. PR1455577
•
Enable gigether option to configure Ethernet FEC on client ports. PR1456293
•
ACX5448-D and ACX5448-M Devices does not display airflow information and temperature sensors
•
as expected. PR1456593
ACX5448 Layer2 VPN with encapsulation-type ethernet stops passing traffic after a random port is
•
added with vlan configuration. PR1456624
25
The rpd crash might be seen if BGP route is resolved over same prefix protocol next-hop in inet.3 table
•
which has both RSVP and LDP routes. PR1458595
Route resolve resolution is not happening when the packet size is 10000. PR1458744
•
The traffic might be blackholed during link recovery in an open ethernet access ring with ERPS configured.
•
PR1459446
ACX5000: SNMP mib walk for jnxOperatingTemp not returning anything for FPC in new versions.
•
PR1460391
ACX5448-M Interfaces and Optics support: on enabling local loopback 10G interface is going down.
•
PR1460715
ACX5448-D Interfaces and Optics support: sometimes during the bring up of AE interface there are
•
ARP resolution issues. PR1461485
ACX Series routers LLDP neighbor not up on lag after software upgrade to Junos OS Release 18.2R3-S1.
•
PR1461831
RED drop on interface, no congestion. PR1470619
•
Layer 2 Ethernet Services
DHCP request might get dropped in DHCP relay scenario. PR1435039
•
Platform and Infrastructure
REST API process will get non-responsive when a number of request coming with a high rate. PR1449987
•
Routing Protocols
Loopback address are exported into other VRF instance might not work on EX/QFX/ACX platforms.
•
PR1449410
MPLS LDP might still use stale MAC of the neighbor even the LDP neighbor's MAC changes. PR1451217
•
The rpd might crash continuously due to memory corruption in an IS-IS setup. PR1455432
•
26
SEE ALSO
What's New | 15
What's Changed | 20
Known Limitations | 21
Open Issues | 22
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Documentation Updates
IN THIS SECTION
Feature Guides Are Renamed As User Guides | 27
This section lists the errata and changes in Junos OS Release 19.4R1 for the ACX Series documentation.
Feature Guides Are Renamed As User Guides
Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the
•
purpose of the guides. For example, the BGP Feature Guide is now the BGP User Guide. We didn’t change
the URLs of the guides, so any existing bookmarks you have will continue to work. To keep the terminology
consistent on our documentation product pages, we renamed the Feature Guides section to User Guides.
To find documentation for your specific product, check out this link.
SEE ALSO
What's New | 15
What's Changed | 20
Known Limitations | 21
Open Issues | 22
Resolved Issues | 23
27
Migration, Upgrade, and Downgrade Instructions | 27
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Upgrade and Downgrade Support Policy for Junos OS Releases | 27
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.
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 information about software installation and upgrade, see the Installation and Upgrade Guide.
For more information about EEOL releases and to review a list of EEOL releases, see