Junos OS 19.2R1 User manual
Release
Published
2021-04-22
Notes
Junos®OS 19.2R1 Release Notes
SUPPORTED ON
ACX Series, EX Series, Junos Fusion Enterprise, Junos Fusion Provider Edge, MX Series,
•
NFX Series, PTX Series, QFX Series, and SRX Series
HARDWARE HIGHLIGHTS
SRX5K-SPC3 support Avira scan engine on antivirus module (SRX5400, SRX5600, and
•
SRX5800)
SOFTWARE HIGHLIGHTS
Support for BFD, BGP, IS-IS, and OSPF on IRB interfaces in EVPN-MPLS networks (EX
•
Series)
Support for control word in EVPN-VPWS (EX9200 Series and MX Series)
•
Support for QSFP-100GE-DWDM2 transceiver (MX Series)
•
MX2008 routers support in-chassis Junos node slicing (MX Series)
•
Support for Synchronous Ethernet with ESMC on JNP10K-LC2101 (MX10008 and
•
MX10016)
PCE-initiated bypass LSPs (MX Series, PTX Series)
•
Support for unified ISSU on abstracted fabric interfaces (MX Series)
•
Support for fixed wireless access subscribers on BNGs (MX Series)
•
Support for transferring accounting statistics files and router configuration archives using
•
HTTP URL (MX Series)
Packet Forwarding Engine statistics export using gNMI and JTI (MX Series, PTX1000 and
•
PTX10000 routers, and QFX5100 and QFX5200 switches)
Dynamic creation of segment routing LSPs using BGP protocol next hops (MX Series, PTX
•
Series)
gNMI support for Routing Engine statistics for JTI (QFX Series switches)
•
Loopback firewall filter scale optimization (QFX5120)
•
EVPN-VXLAN support (QFX10002-60C switches)
•
Support for 512 ECMP next hops for BGP (QFX10000 switches)
•
Support to configure micro-applications in a unified policy (SRX Series and vSRX)
•
Application-level logging for AppQoE (SRX Series)
•
Anti-Replay Window (SRX Series)
•
Release Notes: Junos®OS Release 19.2R1 for
the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and
Junos Fusion
1
22 April 2021
Contents
Introduction | 11
Junos OS Release Notes for ACX Series | 11
New and Changed Features | 12
New and Changed Features: 19.2R1-S1 | 12
New and Changed Features: 19.2R1 | 12
Changes in Behavior and Syntax | 16
Interfaces and Chassis | 17
Junos OS XML, API, and Scripting | 17
Network Management and Monitoring | 17
VLAN Infrastructure | 18
Known Behavior | 18
General Routing | 19
Known Issues | 20
General Routing | 21
Interfaces and Chassis | 24
Resolved Issues | 24
Resolved Issues: 19.2R1-S1 | 25
Resolved Issues: 19.2R1 | 25
Documentation Updates | 26
Installation and Upgrade Guide | 27
Migration, Upgrade, and Downgrade Instructions | 27
Upgrade and Downgrade Support Policy for Junos OS Releases | 27
Product Compatibility | 28
Hardware Compatibility | 29
Junos OS Release Notes for EX Series Switches | 30
New and Changed Features | 30
New and Changed Features: 19.2R1-S1 | 31
New and Changed Features: 19.2R1 | 31
Changes in Behavior and Syntax | 36
Network Management and Monitoring | 36
VLAN Infrastructure | 37
Known Behavior | 37
2
EVPN | 38
General Routing | 38
Platform and Infrastructure | 38
Known Issues | 38
General Routing | 39
Infrastructure | 40
Junos Fusion Enterprise | 41
Layer 3 Features | 41
Platform and Infrastructure | 41
Spanning Tree Protocols | 41
Resolved Issues | 42
Authentication and Access Control | 43
EVPN | 43
General Routing | 43
Infrastructure | 44
Interfaces and Chassis | 44
Layer 2 Ethernet Services | 45
Junos Fusion Enterprise | 45
Network Management and Monitoring | 45
Platform and Infrastructure | 45
Routing Protocols | 46
Software Installation and Upgrade | 46
Subscriber Access Management | 46
Documentation Updates | 47
Installation and Upgrade | 47
Migration, Upgrade, and Downgrade Instructions | 48
Upgrade and Downgrade Support Policy for Junos OS Releases | 48
Product Compatibility | 49
Hardware Compatibility | 49
Junos OS Release Notes for Junos Fusion Enterprise | 50
New and Changed Features | 50
Changes in Behavior and Syntax | 51
Known Behavior | 52
Known Issues | 52
3
Junos Fusion Enterprise | 52
Resolved Issues | 53
Resolved Issues: 19.2R1 | 53
Documentation Updates | 54
Migration, Upgrade, and Downgrade Instructions | 55
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 55
Upgrading an Aggregation Device with Redundant Routing Engines | 57
Preparing the Switch for Satellite Device Conversion | 57
Converting a Satellite Device to a Standalone Switch | 59
Upgrade and Downgrade Support Policy for Junos OS Releases | 59
Downgrading from Junos OS | 59
Product Compatibility | 60
Hardware and Software Compatibility | 60
Hardware Compatibility Tool | 60
Junos OS Release Notes for Junos Fusion Provider Edge | 61
New and Changed Features | 62
Spanning-Tree Protocols | 62
Changes in Behavior and Syntax | 62
Known Behavior | 63
Known Issues | 63
Junos Fusion Provider Edge | 64
Resolved Issues | 64
Junos Fusion Provider Edge | 65
Junos Fusion Satellite Software | 65
Documentation Updates | 65
Migration, Upgrade, and Downgrade Instructions | 66
Basic Procedure for Upgrading an Aggregation Device | 66
Upgrading an Aggregation Device with Redundant Routing Engines | 69
Preparing the Switch for Satellite Device Conversion | 69
Converting a Satellite Device to a Standalone Device | 71
Upgrading an Aggregation Device | 73
Upgrade and Downgrade Support Policy for Junos OS Releases | 73
Downgrading from Junos OS Release 19.2 | 74
4
Product Compatibility | 74
Hardware Compatibility | 74
Junos OS Release Notes for MX Series 5G Universal Routing Platform | 75
New and Changed Features | 76
New and Changed Features: 19.2R1-S4 | 77
New and Changed Features: 19.2R1-S1 | 77
New and Changed Features: 19.2R1 | 78
Changes in Behavior and Syntax | 96
Interfaces and Chassis | 96
MPLS | 97
Network Management and Monitoring | 97
Routing Policy and Firewall Filters | 98
Services Applications | 98
Software Defined Networking | 98
Subscriber Management and Services | 98
VLAN Infrastructure | 99
Known Behavior | 100
General Routing | 100
Interfaces and Chassis | 101
Routing Protocols | 102
Known Issues | 102
EVPN | 103
Forwarding and Sampling | 103
General Routing | 104
Interfaces and Chassis | 108
Layer 2 Ethernet Services | 109
MPLS | 109
Platform and Infrastructure | 109
Routing Protocols | 110
Resolved Issues | 111
Application Layer Gateways (ALGs) | 112
Authentication and Access Control | 112
Class of Service (CoS) | 113
EVPN | 113
5
Flow-based and Packet-based Processing | 114
Forwarding and Sampling | 114
General Routing | 114
Infrastructure | 121
Interfaces and Chassis | 121
Layer 2 Features | 123
Layer 2 Ethernet Services | 123
MPLS | 123
Network Management and Monitoring | 124
Platform and Infrastructure | 125
Routing Policy and Firewall Filters | 125
Routing Protocols | 126
Services Applications | 127
Software Installation and Upgrade | 128
Subscriber Access Management | 128
User Interface and Configuration | 128
VPNs | 128
Documentation Updates | 129
Migration, Upgrade, and Downgrade Instructions | 130
Basic Procedure for Upgrading to Release 19.2 | 131
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 131
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 133
Upgrade and Downgrade Support Policy for Junos OS Releases | 135
Upgrading a Router with Redundant Routing Engines | 136
Downgrading from Release 19.2 | 136
Product Compatibility | 137
Hardware Compatibility | 137
Junos OS Release Notes for NFX Series | 138
New and Changed Features | 138
Architecture | 139
Application Security | 139
Virtual Network Functions | 139
6
Changes in Behavior and Syntax | 140
Factory-default Configuration | 141
Known Behavior | 141
Interfaces | 141
Platform and Infrastructure | 142
Known Issues | 143
High Availability | 143
Interfaces | 143
Platform and Infrastructure | 144
Routing Protocols | 145
Virtual Network Functions (VNFs) | 145
Resolved Issues | 146
Interfaces | 146
Platform and Infrastructure | 146
Documentation Updates | 147
Migration, Upgrade, and Downgrade Instructions | 147
Upgrade and Downgrade Support Policy for Junos OS Releases | 148
Basic Procedure for Upgrading to Release 19.2 | 148
Product Compatibility | 150
Hardware Compatibility | 150
Junos OS Release Notes for PTX Series Packet Transport Routers | 152
New and Changed Features | 153
New and Changed Features: 19.2R1-S4 | 154
New and Changed Features: 19.2R1-S1 | 154
New and Changed Features: 19.2R1 | 154
Changes in Behavior and Syntax | 160
What’s Changed in Release 19.2R1-S5 | 161
What’s Changed in Release 19.2R1 | 161
Known Behavior | 163
General Routing | 163
Interfaces and Chassis | 164
Known Issues | 164
General Routing | 165
Infrastructure | 166
7
Interfaces and Chassis | 166
Layer 2 Ethernet Services | 166
MPLS | 166
Routing Protocols | 166
Resolved Issues | 167
General Routing | 167
Infrastructure | 169
Interfaces and Chassis | 169
MPLS | 169
Platform and Infrastructure | 169
Routing Protocols | 169
Documentation Updates | 170
Installation and Upgrade Guide | 170
Migration, Upgrade, and Downgrade Instructions | 171
Basic Procedure for Upgrading to Release 19.2 | 171
Upgrade and Downgrade Support Policy for Junos OS Releases | 174
Upgrading a Router with Redundant Routing Engines | 174
Product Compatibility | 175
Hardware Compatibility | 175
Junos OS Release Notes for the QFX Series | 176
New and Changed Features | 177
New and Changed Features: 19.2R1-S1 | 177
New and Changed Features: 19.2R1 | 178
Changes in Behavior and Syntax | 186
Interfaces and Chassis | 186
Network Management and Monitoring | 187
Security | 187
Known Behavior | 188
EVPN | 188
General Routing | 188
Layer 2 Features | 189
Routing Protocols | 189
Known Issues | 190
8
EVPN | 190
General Routing | 191
Layer 2 Ethernet Services | 194
Layer 2 Features | 194
MPLS | 196
Platform and Infrastructure | 196
Routing Protocols | 196
Resolved Issues | 197
Resolved Issues: 19.2R1 | 197
Documentation Updates | 204
Installation and Upgrade guide | 204
Migration, Upgrade, and Downgrade Instructions | 205
Upgrading Software on QFX Series Switches | 205
Installing the Software on QFX10002-60C Switches | 208
Installing the Software on QFX10002 Switches | 208
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 | 209
Installing the Software on QFX10008 and QFX10016 Switches | 211
Performing a Unified ISSU | 215
Preparing the Switch for Software Installation | 216
Upgrading the Software Using Unified ISSU | 216
Upgrade and Downgrade Support Policy for Junos OS Releases | 218
Product Compatibility | 219
Hardware Compatibility | 219
Junos OS Release Notes for SRX Series | 220
New and Changed Features | 221
New and Changed Features: 19.2R1-S1 | 222
New and Changed Features: 19.2R1 | 222
Changes in Behavior and Syntax | 231
Application Security | 232
Ethernet Switching and Bridging | 232
Flow-Based and Packet-Based Processing | 232
Network Management and Monitoring | 232
VPNs | 233
9
Known Behavior | 233
Flow-Based and Packet-Based Processing | 234
J-Web | 234
VPNs | 234
Known Issues | 235
Chassis Clustering | 235
Flow-Based and Packet-Based Processing | 235
J-Web | 236
Platform and Infrastructure | 236
User Firewall | 236
VPNs | 236
Resolved Issues | 237
Application Firewall | 237
Application Identification | 237
Application Layer Gateways (ALGs) | 237
Chassis Clustering | 238
Flow-Based and Packet-Based Processing | 238
Infrastructure | 240
Interfaces and Routing | 240
Intrusion Detection and Prevention (IDP) | 241
Installation and Upgrade | 241
J-Web | 241
Logical Systems and Tenant Systems | 242
Multiprotocol Label Switching (MPLS) | 242
Network Address Translation (NAT) | 242
Network Management and Monitoring | 242
Platform and Infrastructure | 242
Routing Policy and Firewall Filters | 243
Unified Threat Management (UTM) | 243
User Interface and Configuration | 244
VPNs | 244
Documentation Updates | 245
Migration, Upgrade, and Downgrade Instructions | 246
Upgrade and Downgrade Support Policyfor Junos OS Releases and Extended End-Of-Life
Releases | 246
10
Product Compatibility | 247
Hardware Compatibility | 247
Upgrading Using ISSU | 248
Licensing | 248
Compliance Advisor | 248
Finding More Information | 249
Documentation Feedback | 249
Requesting Technical Support | 250
Self-Help Online Tools and Resources | 250
Opening a Case with JTAC | 251
Revision History | 251
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, and Junos Fusion.
These release notes accompany Junos OS Release 19.2R1 for the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and Junos Fusion. They describe new and changed features,
limitations, and known and resolved problems in the hardware and software.
Junos OS Release Notes for ACX Series
IN THIS SECTION
11
New and Changed Features | 12
Changes in Behavior and Syntax | 16
Known Behavior | 18
Known Issues | 20
Resolved Issues | 24
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
These release notes accompany Junos OS Release 19.2R1 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.
New and Changed Features
IN THIS SECTION
New and Changed Features: 19.2R1-S1 | 12
New and Changed Features: 19.2R1 | 12
This section describes the new features and enhancements to existing features in Junos OS Release 19.2R1
for ACX Series Universal Metro Routers.
New and Changed Features: 19.2R1-S1
Routing Protocols
12
Decouple RSVP for IGP-TE (MX Series, PTX Series, ACX Series, QFX Series, SRX Series, and EX
•
Series)—Starting in Junos OS Release 19.2R1-S1, device can advertise selective traffic-engineering
attributes such as admin-color and maximum-bandwidth, without enabling RSVP, for segment routing
and interior gateway protocol (IGP) deployments.
New and Changed Features: 19.2R1
Class of Service (CoS)
Support for class of service (CoS)(ACX6360 routers)—Starting in Junos OS Release 19.2R1, ACX6360
•
routers support class of service (CoS) functionality.
CoS is the assignment of traffic flows to different service levels. Service providers can use router-based
CoS features to define service levels that provide different delay, jitter (delay variation), and packet loss
characteristics to particular applications served by specific traffic flows.
[See CoS on ACX Series Universal Metro Routers Features Overview.]
EVPN
EVPN support of VLAN ID ranges and lists in service provider style interface configurations (EX9200
•
switches, ACX5448 and MX Series routers, and vMX virtual routers)—Starting in Junos OS Release
19.2R1, EX9200 switches, ACX5448 and MX Series routers, and vMX virtual routers support the use
of VLAN ID ranges and lists in a service provider style interface configuration, which must be referenced
in an EVPN routing instance. This configuration is supported with the following EVPN environments,
services, and features:
Environments:
•
EVPN with VXLAN encapsulation
•
EVPN with MPLS encapsulation
•
VLAN bundle service:
•
E-LAN
•
E-Tree
•
E-Line
•
Feature:
•
EVPN multihoming:
•
All-active
•
Single-active
•
Singlehoming
•
[See VLAN ID Ranges and Lists in an EVPN Environment.]
13
Interfaces and Chassis
Support for 100-Mbps and 1-Gbps speeds on Tri-Rate Copper SFP (ACX5448 routers)—Starting in
•
Junos OS Release 19.2R1, ACX5448 routers support 100-Mbps and 1-Gbps speeds on Tri-Rate Copper
SFP optics (part number 740-013111).
NOTE: 100-Mbps speed is supported only on ports xe-0/0/24 through xe-0/0/47.
10-Mbps speed is not supported on Tri-Rate Copper SFP due to hardware limitations.
To set the speed for the optics, issue the set interfaces interface-name speed auto command. [See
•
Speed for more details.]
To enable autonegotiation, issue the set interfaces interface-name gigether-options auto-negotiation
•
command. [See auto-negotiation.]
Junos Telemetry Interface
Support for LSP statistics on JTI (ACX6360)—Starting with Junos OS Release 19.2R1, you can provision
•
the LSP statistics sensor using the resource path /junos/services/label-switched-path/usage/ to monitor
per-MPLS LSP statistics on the ACX6360 router and export telemetry data through Junos telemetry
interface (JTI) to external collectors. You can stream data at configurable intervals through gRPC without
involving polling.
JTI support is only for RSVP LSPs.
Statistics that are streamed are similar to the output displayed by the operational mode command show
mpls lsp bypass statistics.
To provision a sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetry
parameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module.
Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the
Junos OS image by default. Both packages support JTI.
To enable statistics for export from the Junos OS, include the sensor-based-stats statement at the [edit
protocols mpls] hierarchy level.
[See Guidelines for gRPC Sensors (Junos Telemetry Interface) and Understanding OpenConfig and gRPC
on Junos Telemetry Interface.]
•
Specify Routing Instance for JTI (ACX Series, MX Series, PTX Series, and QFX Series)—Starting in Junos
OS Release 19.2R1, you can specify the routing instance to use for remote procedure call (gRPC) services.
Include the routing-instance instance-name at the [edit system services extension-service
request-response grpc] hierarchy level. The routing instance name specified should match the name of
the existing routing instance, such as a name configured under the [routing-instances] hierarchy level
or mgmt_junos if system management-instance is configured (the dedicated management routing
instance).
14
Configuring the routing instance lets you choose the VRF for gRPC services. When the routing instance
is not configured, the default behavior is that all gRPC-related services are available through the
management fxp0/em0) interface.
Layer 3 Features
Support for Layer 3 unicast features (ACX 6360)—Starting in Junos OS Release 19.2R1, ACX routers
•
support the following Layer 3 forwarding features for unicast IPv4 and IPv6 traffic:
Basic IPv6 forwarding
•
Virtual router (VRF-lite) for both IPv4 and IPv6
•
Layer 3 subinterfaces support for both IPv4 and IPv6
•
VRF-lite, subinterfaces, and IPv6 forwarding support on link aggregation groups (LAGs)
•
Statistics support for Layer 3 subinterfaces
•
32-way equal-cost multipath (ECMP)
•
Centralized Bidirectional Forwarding Detection (BFD)
•
IPv4 Layer 3 protocols:
•
OSPF
•
IS-IS
•
BGP
•
IPv6 Layer 3 protocols:
•
OSPFv3
•
RIPng
•
Network Management and Monitoring
Support for displaying valid user input in the CLI for command options and configuration statements
•
in custom YANG data models (ACX Series)—Starting in Junos OS Release 19.2R1, the CLI displays the
set of possible values for a given command option or configuration statement in a custom YANG data
model when you include the action-expand extension statement in the option or statement definition
and reference a script that handles the logic. The action-expand statement must include the script child
statement, which defines the Python action script that is invoked when a user requests context-sensitive
help in the CLI for the value of that option or statement.
[See Displaying Valid Command Option and Configuration Statement Values in the CLI for Custom YANG
Modules.]
Software Installation and Upgrade
Zero Touch Provisioning (ACX5448)—Starting in Junos OS Release 19.2R1, Zero Touch Provisioning
•
(ZTP) automates the provisioning of the device configuration and software image with minimal manual
intervention on management interface em0.
15
When you physically connect a router to the network and boot it with a factory configuration, the router
upgrades the Junos OS software image automatically and automatically installs a configuration file from
the network through the management interface.
[See Zero Touch Provisioning.]
System Management
Support for transferring accounting statistics files and router configuration archives using HTTP URL
•
(ACX Series)—Starting in Junos OS Release 19.2R1, you can transfer accounting statistics files and router
configuration archives to remote servers by using an HTTP URL. In addition to SCP and FTP, the following
HTTP URL will be supported under the archive-sites statement:
http://username@host:url-path password password
To transfer accounting statistics files, configure archive-sites under [edit accounting-options file
•
<filename>] hierarchy.
To transfer router configuration archival, configure archive-sites under edit system archival
•
configuration hierarchy.
To view the statistics of transfer attempted, succeeded, and failed, use the show accounting server
•
statistics archival-transfer command.
To clear the statistics of transfer attempted, succeeded, and failed, use the clear accounting server
•
statistics archival-transfer command.
[See archive-sites, Backing Up Configurations to an Archive Site, show accounting server statistics
archival-transfer, and clear accounting server statistics archival-transfer].
Precision Time Protocol (PTP) Transparent Clock with IPv6 Transport (PTX10001-20C and ACX6360-OR
•
devices)—Starting with Junos OS Release 19.2R1, PTP uses IPv6 transport to synchronize clocks
throughout a packet-switched network. With a transparent clock, the PTP packets are updated with
theresidence time as the packets pass through the switch. There is no master/slaved designation.
End-to-end transparent clocks are supported. With an end-to-end transparent clock, only the residence
time is included. The residence time can be sent in a one-step process, which means that the timestamps
are sent in one packet.
You can configure the transparent clock at the [edit protocols ptp] Junos OS CLI hierarchy.
[See Understanding Transparent Clocks in Precision Time Protocol.]
SEE ALSO
16
What's Changed | 16
Known Limitations | 18
Open Issues | 20
Resolved Issues | 24
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
Changes in Behavior and Syntax
IN THIS SECTION
Interfaces and Chassis | 17
Junos OS XML, API, and Scripting | 17
Network Management and Monitoring | 17
VLAN Infrastructure | 18
This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS
statements and commands in Junos OS Release 19.2R1 for the ACX Series routers.
Interfaces and Chassis
Monitoring information available only in trace log (ACX Series)—In Junos OS Release 19.2R1 and later,
•
the Ethernet link fault management daemon (lfmd) in the peer router stops monitoring the locally occurred
errors until ISSU completes. You can view the monitoring-related details only through the trace log file.
Junos OS XML, API, and Scripting
Mandatory configurations and omission of <database-status-information> tag in platforms supporting
•
Open ROADM standard (ACX6160-T)—Starting in Junos OS Release 19.2R1, it is mandatory to apply
rfc-compliant option at the [edit system services netconf] hierarchy level and unhide option at the [edit
system services netconf unified] hierarchy level. Also, <database-status-information> tag is omitted for
<get> RPC query.
17
[See <get> and netconf.]
Network Management and Monitoring
The show system schema command and <get-yang-schema> RPC require specifying an output directory
•
(ACX Series)—Starting in Junos OS Release 19.2R1, when you issue the show system schema operational
mode command in the CLI or execute the <get-yang-schema> RPC in a remote session to retrieve
schema files, you must specify the directory in which to generate the output files by including the
output-directory command option in the CLI or the <output-directory> element in the RPC. In earlier
releases, you can omit the output-directory argument when requesting a single module to display the
module in standard output.
Custom YANG RPC support for input parameters of type empty (ACX Series)—Starting in Junos OS
•
Release 19.2R1, custom YANG RPCs support input parameters of type empty when executing the RPC’s
command in the Junos OS CLI, and the value passed to the action script is the parameter name. In earlier
releases, input parameters of type empty are only supported when executing the RPC in a NETCONF
or Junos XML protocol session, and the value passed to the action script is the string 'none'.
[See Creating Action Scripts for YANG RPCs on Devices Running Junos OS.]
VLAN Infrastructure
Specifying a descending VLAN ID range ( ACX5448 routers)—In Junos OS releases prior to Junos OS
•
Release 19.2R1, the system accepts a descending range—for example, 102-100, with the vlan-id-range
configuration statement in the [edit interfaces interface-name unit logical-unit-number] hierarchy.
Starting with Junos OS Release 19.2R1, the system considers a descending range specified with
vlan-id-range to be invalid and raises an error if you try to commit this configuration.
SEE ALSO
What's New | 12
Known Limitations | 18
Open Issues | 20
Resolved Issues | 24
18
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
Known Behavior
IN THIS SECTION
General Routing | 19
This section lists known behavior, system maximums, and limitations in hardware and software in Junos
OS Release 19.2R1 for the ACX Series.
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-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
For the et interface, only PRE_FEC_SD defect is raised no OTN alarm is raised. PR1371997
•
static-cak encryption does not work between two ACX-OX transponder nodes. PR1389802
•
For ACX6360 TIC, the beacon port-range needs to be updated to 0-7 instead of 0-15.PR1399335
•
When timing configuration and 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
Snake traffic fails because of the static MAC address assigned for interface. Static MAC address on
•
interface is not supported in ACX Series routers. PR1427132
When an end device (fan tray CPLD) i2c line is grounded or pulled low, the other device fails to write
•
or read. As a workaround, verify the isolation functionality through software simulation when the device
is in the problem state. But in this case where we grounded one of the fan tray CPLD i2c line to verify
the failed test case, then entire circuit will get stalled and it leads to write fail for other devices also such
as the PEM, temp sensors. PR1427222
19
Multicast packets are flooded in a BD if snooping is not enabled. If interfaces x and y belong to a BD,
•
then all multicast packets will be flooded to both x and y interface. If packets are received from interface
x, packets will be flooded to x & y in ingress but discarded in the egress path for interface x because the
packet is received from the same interface. But these packets are also counted in the VOQ and hence
more queue statistics are seen. This is a known hardware limitation. monitor interface xe-0/0/30Input
packets: 177958 (64 pps) [0]Output packets: 357306 (128 pps) [0] monitor interface xe-0/0/12Input
packets: 361161 (128 pps) [642]Output packets: 179878 (63 pps) [320] root@rioxd-p2a-a> show
interfaces queue xe-0/0/30 Queue: 0, Forwarding classes: best-effortQueued:Packets : 544032 192
pps . => Sum of 64 + 128pps root@rioxd-p2a-a> show interfaces queue xe-0/0/12 Queue: 0, Forwarding
classes: best-effortQueued:Packets : 550929 192 pps . => Sum of 64 + 128pps PR1429628
Any packet greater than MTU size will be accounted as oversized packets. Packets exceeding MTU sizes
•
are not considered for Jabber check. PR1429923
Even the system LED glows during halt state. PR1430129
•
Packets dropped because MTU checks in the output interface are not accounted for MTU errors. All
•
packets above MTU size are accounted for oversized packets in the input interface. PR1430446
1G interfaces are shown as 'xe'. Therefore, the cosmetic issue is observed with respect to auto-negotiation
•
parameters though there is no impact on functionality. PR1430835
BCM SDK do not support statistics. The routes get re-installed on a periodic basis and SDK does not
•
support statistics unless Flex mode is moved in KBP. PR1435579
The logical interface statistics in ACX5448 displays the full packet size similar to the behaviour in
•
ACX5000 Series. PR1439124
The time taken to copy DNX file through a WAN interface is more compared to ACX5000. PR1439960
•
The hold timer expiry is common across all platforms. It is not specific to RIO platforms. PR1439980
•
Remote loopback is not supported on RIO-X. PR1443517
•
SEE ALSO
What's New | 12
What's Changed | 16
Open Issues | 20
Resolved Issues | 24
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
20
Known Issues
IN THIS SECTION
General Routing | 21
Interfaces and Chassis | 24
This section lists the known issues in hardware and software in Junos OS Release 19.2R1 for the ACX
Series Universal Metro 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
Forwarding when using non-existing SSM map source address in IGMPv3 instead of pruning. This is a
•
day 1 design issue which needs to be redesigned. The impact is more, But definitely this needs some
soaking time in DCB before it gets ported in previous versions. PR1126699
When ACX 2100 and 2200 routers are used as ingress PE routers for L2circuit connections, and the
•
PE-CE interface (UNI) is an aggregated Ethernet interface, then upon MPLS path switchover, the traffic
might be silently dropped or discarded. PR1194551
The maximum number of logical interfaces (IFLs) on the ACX5000 line of routers has been increased
•
from 1000 to 4000. PR1229492
When Layer 3 packets are classified, DiffServ code points are not preserved but are getting lost at the
•
egress interface because of a chipset limitation. PR1322142
On ACX5000 platforms with Junos OS 16.2 onwards, the fxpc process might use high CPU. This issue
•
can occur after an upgrade in some cases. PR1360452
On ACX1x00/ACX2x00/ACX4x00 running in 15-releases previous to Junos OS Release 15.1R8, when
•
configuring mac-table-size under bridge-domain, an incorrect commit error appears, not allowing the
commit to succeed. PR1364811
21
The switchover time observed is more than 50ms under certain soak test conditions with an increased
•
scale with a multi-protocol multi-router topology. PR1387858
On ACX5000 running Junos OS Release 17.3 and later releases, the Packet Forwarding Engine syslog
•
frequently shows the following error messages: acx_cos_tcp_bind_queues:736 parent acx_cos_tcp_ifd
for ifd:ae0 doesn't exist for ifl:549. In Junos OS Release 17.3R3-S1, the error logs appear only from time
to time, and this can be related with an interface flap. In Junos OS Release 18.1R3, the logs appear
constantly, without any interface flap. This message is related to HCOS checking (even without HCOS
configured). In the software fix, check if the aggregate interface has HCOS configured or not. If not,
return gracefully from this function without throwing this error. This is a harmless message. PR1392088
IGMP packets over Layer 2 Circuit with control word are dropped in ACX5048. PR1394301
•
On ACX1000, ACX2000, ACX4000, ACX5048, and ACX5096 platforms, after a new child logical interface
•
with VLAN and filter is added on an aggregated Ethernet IFD or changing the VLAN ID of a child IFL
with filter, traffic over the aggregated Ethernet physical interface might get filtered with that filter on
the child IFL. For example: ae-0/0/0 is an physical interface and ae-0/0/0.100 is an Ilogical interface.
PR1407855
Clock Class value is wrong in Default Data (show ptp clock) when the slave interface is down in PTP-OC
•
device. PR1416421
On ACX5448 devices, the ZTP process will proceed with the image upgrade even in situations when
•
there is a mismatch in the platform name of the software image stored on FTP/ZTP servers and the
actual platform on which the ZTP process is being run. PR1418313
Hardware-based fragmentation or reassembly is not supported. Software-based fragmentation rates
•
are going to be extremely slow depending CPU load. PR1419371
On ACX5000 platforms, thigh CPU usage on the fxpc process might be seen under rare condition if
•
parity errors are detected in devices. It has no direct service or traffic impact. However, since CPU
utilization is high during this issue, there are some side effects. For example, it could impact time-sensitive
features such as BFD. PR1419761
Packets transmitted in a queue are not as expected when testing IEEE-802.1ad inner classifier at the
•
ingress and IEEE-802.1ad rewrite at the egress with various events. PR1422515
The input packets account for all the frames that are coming in, including the oversized frames. Whereas
•
oversized frame counter only accounts for oversized frames. PR1425748
Because of the BCM sdk design, EEDB hardware entry is not freed for unicast next-hop creation. This
•
leads to resource leakage and is not allowing to higher scale. PR1426734
Error messages can be seen sometimes if the optics is being unplugged in between the eeprom read.
•
This is expected and will not impact any functionality. PR1429016
Multiple hardware i2c failure observed because of intermittent Iayer 2 circuit access failure on main
•
board switches. PR1429047
22
Packet rates are not seen for aggregated Ethernet logical interface. PR1429590
•
Traffic loss is seen if the configuration has /128 prefix routes and it is limited to /128 only. Its due to
•
the known issue tracked in PR 1445231. PR1429833
Any packet greater than the MTU size will be accounted as oversized packets. Packets exceeding the
•
MTU sizes are not considered for jabber check. PR1429923
This is the expected behavior across all ACX platforms. Even the system LED glows during halt state.
•
PR1430129
These are initial transient messages seen and does not have any functional impact. PR1430355
•
Packets dropped due to MTU checks in the output interface are not accounted for MTU errors. All
•
packets above MTU size are accounted for Oversized-packets in the input interface. PR1430446
If L2VPN sessions have OAM control-channel option set to router-alert-label, the no-control-word
•
option in L2VPN should not be used for BFD sessions to come up. PR1432854
Timing on 1G, performance is not in par compared with 10G, 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 (that is, 5-10 percent of the mean latency
introduced by the each phy which is of around 2.5us) without any traffic. PR1437175
These errors can be seen if CFP2 optics are not plugged in. PR1438039
•
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
In a certain test condition, it is observed that L2VPN at a scale of 16000 had issues when all were brought
•
down and up. PR1439471
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
By default mgmt interface speed always shows as 1000Mbps in Junos OS. PR1440675
•
With MACsec feature enabled and introduction of traffic, the peak to peak value varies with the
•
percentage of traffic introduced. PR1441388
Recovery of Junos OS volume is not possible from OAM menu. PR1446512
•
SyncE Jitter tolerance test fails for MACsec ports. For SyncE with MACsec there seems to be additional
•
framing header and footer that would get added by the MACsec protocol. The impact of this on the
jitter test is not obvious and look undefined in the standards and not qualifiable with a single DUT and
Calnex. PR1447296
Drop profile maximum threshold might not be reached to its limit when the packet size is other than
•
1000 bytes. This is due to current design limitation. Making design changes are high risk at this point of
time, Hence, The Junos OS Releases 19.2R1-S1, 19.2R(x), and 19.3(x) will not have fix for this issue.
PR1448418
23
If the client et- interface is up and transportd state is in init state, restart transportd process to get the
•
state updated to normal. This scenario is not seen in normal operation but seen when interfaces are
deleted and re-created and configurations are applied. PR1449937
Red drops seen on the 25G channelized aggregated Ethernet interfaces after some events (deactivate,
•
activate etc) on the PEER box. PR1450674
For the et ports, some output power might be seen even after disabling the interface. This will not have
•
any functional impact as the bcmport is getting disabled on the interface and the link goes down fine.
PR1452323
Incorrect operating state is displayed in SNMP trap message when a FAN tray is removed. PR1455577
•
FAN numbering is not the same in the outputs of the following configuration statements show chassis
•
fan and show snmp mib walk jnxContentsDescr. PR1456589
Interfaces and Chassis
When an unnumbered interface is binding to an interface that has more than one IP address and one of
•
the IP addresses is deleted, the family inet of the unnumbered interface might be deleted. The issue
results in traffic loss for all the services that rely on the family inet of the unnumbered interface. Configure
preferred-source-address on the unnumbered interface to prevent deletion of the IP address, thereby
avoiding the deletion of the family inet of the unnumbered interface. PR1412534
SEE ALSO
What's New | 12
What's Changed | 16
Known Limitations | 18
Resolved Issues | 24
Documentation Updates | 26
24
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
Resolved Issues
IN THIS SECTION
Resolved Issues: 19.2R1-S1 | 25
Resolved Issues: 19.2R1 | 25
This section lists the issues fixed in Junos OS Release 19.2R1 for the ACX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Resolved Issues: 19.2R1-S1
General Routing
Link Fault Signaling (LFS) do not work on ACX5448, ACX5410, ACX5440, and 100-Gigabit Ethernet
•
interfaces. PR1401718
In an ACX5448 platforms, when the Packet Forwarding Engine failed to allocate packet buffer, portion
•
of packet memories might not be free. PR1442901
Resolved Issues: 19.2R1
Class of Service (CoS)
The error message STUCK_BUFF : port_sp not empty for port 35 sp 1 pkts:1 is seen when a lag bundle
•
is configured with 64 lag links.. PR1346452
General Routing
The 1G copper module interface shows "Link-mode: Half-duplex". PR1286709
•
25
On an ACX ring topology, after link between ACX and MX flaps, VPLS RI on PE (MX) has no MAC of CE
•
over l2circuit. PR1360967
ACX5000: fpc0 (acx_rt_ip_uc_lpm_install:LPM route add failed error) Reason : Invalid parameter after
•
configuring lpm-profile. PR1365034
ACX5448: LIBCOS_COS_TVP_FC_INFO_NOT_FOUND: Forwarding-class information not specified"
•
prints while committing on configuration prompt. PR1376665
On ACX5448, channelized ET interface of 25-Gigabit interface will not come up after chassis-control
•
restart. PR1379288
ACX 5448:100 Gigabit link FEC enabled by default on 100G LR4. PR1389518
•
On ACX Series platforms, the forwarding-option dhcp-relay forward-only command stops working and
•
the DHCP packets are dropped. PR1392261
On ACX5048, RPM RFC 2544 benchmarking test failed to start. PR1395730
•
CFM adjacency is not going down with distinct intervals. PR1397883
•
Dynamic tunnels are not supported on ACX Series routers. PR1398729
•
VLAN tagged traffic arriving on VPLS interface might get dropped. PR1402626
•
ot/et interface is not created when invalid speed is configured. PR1403546
•
ACX 5448: TrTCM Policer configuration parameters are as per RFC4115. PR1405798
•
The show services inline stateful-firewall flow or show services inline stateful-firewall flow extensive
•
command might cause a memory leak. PR1408982
ACX Series routers drop DNS responses that contain an underscore. PR1410062
•
VPLS traffic might stop across ACX5000 with the aggregated Ethernet interface. PR1412042
•
Junos PCC might reject PCUpdate/PCCreate message if there is metric type other than type 2. PR1412659
•
Number of inet-arp policers implemented on ACX5000 has been increased from 16 to 64. PR1413807
•
Swap memory is not initialized on boot on ACX5048. PR1415898
•
Commit error while configuring firewall with term having log/syslog and accept actions. PR1417377
•
CoS table error can sometimes cause traffic outages and SNMP timeouts if the optic is plugged out and
•
inserted back. PR1418696
Slow copy image speed to ACX5448. PR1422544
•
SEE ALSO
What's New | 12
What's Changed | 16
26
Known Limitations | 18
Open Issues | 20
Documentation Updates | 26
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
Documentation Updates
IN THIS SECTION
Installation and Upgrade Guide | 27
This section lists the errata and changes in Junos OS Release 19.2R1 for the ACX Series documentation.
Installation and Upgrade Guide
Veriexec explained (ACX Series)—Verified Exec (also known as veriexec) is a file-signing and verification
•
scheme that protects the Junos operating system (OS) against unauthorized software and activity that
might compromise the integrity of your device. Originally developed for the NetBSD OS, veriexec was
adapted for Junos OS and enabled by default from Junos OS Release 7.5 onwards.
[See Veriexec Overview.]
SEE ALSO
What's New | 12
What's Changed | 16
Known Limitations | 18
Open Issues | 20
27
Resolved Issues | 24
Migration, Upgrade, and Downgrade Instructions | 27
Product Compatibility | 28
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 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.
28
SEE ALSO
What's New | 12
What's Changed | 16
Known Limitations | 18
Open Issues | 20
Resolved Issues | 24
Documentation Updates | 26
Product Compatibility | 28
Product Compatibility
IN THIS SECTION
Hardware Compatibility | 29
Loading...