Junos OS Release 19.3R3 User Manual
Release Notes: Junos®OS Release 19.3R3 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 | 10
Junos OS Release Notes for ACX Series | 10
What's New | 11
What's New in Release 19.3R3 | 11
What's New in Release 19.3R2 | 11
What’s New in Release 19.3R1-S1 | 11
What's New in Release 19.3R1 | 12
What's Changed | 19
What’s Changed in Release 19.3R3-S1 | 20
What's Changed in Release 19.3R3 | 20
What's Changed in Release 19.3R2-S6 | 20
What's Changed in Release 19.3R2 | 21
What's Changed in Release 19.3R1 | 21
Known Limitations | 23
General Routing | 23
Open Issues | 25
General Routing | 25
Platform and Infrastructure | 27
Virtual Chassis | 27
Resolved Issues | 27
Resolved Issues: 19.3R3 | 28
Resolved Issues: 19.3R2 | 30
Resolved Issues: 19.3R1 | 31
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
Upgrade and Downgrade Support Policy for Junos OS Releases | 35
Junos OS Release Notes for EX Series Switches | 37
What's New | 37
What's New in 19.3R3 | 38
What's New in 19.3R2 | 38
What's New in 19.3R1 | 39
What's Changed | 47
What's Changed in 19.3R3 | 48
2
What's Changed in Release 19.3R2-S6 | 49
What's Changed in 19.3R2 | 50
What's Changed in 19.3R1 | 50
Known Limitations | 52
EVPN | 52
Infrastructure | 52
Platform and Infrastructure | 52
Open Issues | 53
Authentication and Access Control | 54
Infrastructure | 54
Interfaces and Chassis | 54
Layer 2 Features | 54
Network Management and Monitoring | 54
Platform and Infrastructure | 54
Virtual Chassis | 56
Resolved Issues | 56
Resolved Issues: 19.3R3 | 57
Resolved Issues: 19.3R2 | 62
Resolved Issues: 19.3R1 | 64
Layer 2 Ethernet Services | 64
Network Management and Monitoring | 65
Platform and Infrastructure | 65
Routing Protocols | 68
Subscriber Access Management | 69
User Interface and Configuration | 69
Virtual Chassis | 69
VPNs | 69
Documentation Updates | 69
Migration, Upgrade, and Downgrade Instructions | 70
Upgrade and Downgrade Support Policy for Junos OS Releases | 70
Junos OS Release Notes for Junos Fusion Enterprise | 71
What’s New | 72
What's New in Release 19.3R3 | 72
What's New in Release 19.3R2 | 72
3
What's New in Release 19.3R1 | 72
What’s Changed | 73
Known Limitations | 73
Open Issues | 74
Junos Fusion for Enterprise | 74
Resolved Issues | 75
Resolved Issues: 19.3R3 | 75
Resolved Issues: 19.3R2 | 75
Resolved Issues: 19.3R1 | 75
Documentation Updates | 76
Migration, Upgrade, and Downgrade Instructions | 76
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 77
Upgrading an Aggregation Device with Redundant Routing Engines | 78
Preparing the Switch for Satellite Device Conversion | 79
Converting a Satellite Device to a Standalone Switch | 80
Upgrade and Downgrade Support Policy for Junos OS Releases | 80
Downgrading from Junos OS | 81
Junos OS Release Notes for Junos Fusion Provider Edge | 82
What's New | 82
What's New in Release 19.3R3 | 83
What's New in Release 19.3R2 | 83
What's New in Release 19.3R1 | 83
What's Changed | 83
Known Limitations | 84
Junos Fusion Provider Edge | 84
Open Issues | 85
Junos Fusion Provider Edge | 85
Resolved Issues | 86
Resolved Issues: 19.3R3 | 86
Resolved Issues: 19.3R2 | 86
Resolved Issues: 19.3R1 | 86
4
Documentation Updates | 87
Migration, Upgrade, and Downgrade Instructions | 87
Basic Procedure for Upgrading an Aggregation Device | 88
Upgrading an Aggregation Device with Redundant Routing Engines | 90
Preparing the Switch for Satellite Device Conversion | 91
Converting a Satellite Device to a Standalone Device | 92
Upgrading an Aggregation Device | 95
Upgrade and Downgrade Support Policy for Junos OS Releases | 95
Downgrading from Junos OS Release 19.3 | 95
Junos OS Release Notes for MX Series 5G Universal Routing Platform | 96
What's New | 97
What’s New in Release 19.3R3 | 97
What’s New in Release 19.3R2 | 97
What’s New in Release 19.3R1 | 116
What's Changed | 135
What’s Changed in Release 19.3R3-S1 | 136
What’s Changed in Release 19.3R3 | 136
What's Changed in Release 19.3R2-S6 | 139
What’s Changed in Release 19.3R2-S5 | 140
What’s Changed in Release 19.3R2 | 140
What’s Changed in Release 19.3R1 | 142
Known Limitations | 146
General Routing | 146
Infrastructure | 149
Interfaces and Chassis | 149
MPLS | 150
Platform and Infrastructure | 150
Routing Protocols | 151
Open Issues | 151
EVPN | 152
Forwarding and Sampling | 153
General Routing | 153
Infrastructure | 161
Interfaces and Chassis | 161
5
Layer 2 Ethernet Services | 162
MPLS | 162
Platform and Infrastructure | 163
Routing Protocols | 164
Services Applications | 166
Subscriber Access Management | 166
User Interface and Configuration | 166
VPNs | 166
Resolved Issues | 167
Resolved Issues: 19.3R3 | 167
Resolved Issues: 19.3R2 | 186
Resolved Issues: 19.3R1 | 195
Documentation Updates | 214
Migration, Upgrade, and Downgrade Instructions | 215
Basic Procedure for Upgrading to Release 19.3 | 216
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 216
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 219
Upgrade and Downgrade Support Policy for Junos OS Releases | 220
Upgrading a Router with Redundant Routing Engines | 221
Downgrading from Release 19.3 | 221
Junos OS Release Notes for NFX Series | 222
What’s New | 222
Release 19.3R3 New and Changed Features | 223
Release 19.3R2 New and Changed Features | 223
Release 19.3R1 New and Changed Features | 223
What's Changed | 224
What's Changed in Release 19.3R2-S6 | 224
Known Limitations | 225
Interfaces | 225
Platform and Infrastructure | 225
Virtual Network Functions (VNFs) | 226
Open Issues | 226
Interfaces | 226
High Availability (HA) | 227
6
Platform and Infrastructure | 227
Virtual Network Functions (VNFs) | 227
Resolved Issues | 228
Resolved Issues: 19.3R3 | 228
Resolved Issues: 19.3R2 | 229
Resolved Issues: 19.3R1 | 230
Documentation Updates | 232
Migration, Upgrade, and Downgrade Instructions | 232
Upgrade and Downgrade Support Policy for Junos OS Releases | 232
Basic Procedure for Upgrading to Release 19.3 | 233
Junos OS Release Notes for PTX Series Packet Transport Routers | 234
What's New | 235
What's New in Release 19.3R3 | 235
What's New in Release 19.3R2 | 235
What's New in Release 19.3R1 | 236
What's Changed | 243
What’s Changed in Release 19.3R3-S1 | 244
What's Changed in Release 19.3R3 | 244
Juniper Extension Toolkit (JET) | 245
What's Changed in Release 19.3R2-S6 | 245
What's Changed in Release 19.3R2 | 246
What's Changed in Release 19.3R1 | 246
Known Limitations | 248
General Routing | 248
Interfaces and Chassis | 249
Open Issues | 249
General Routing | 249
Routing Protocols | 250
Resolved Issues | 251
Resolved Issues: Release 19.3R3 | 251
Resolved Issues: Release 19.3R2 | 254
Resolved Issues: Release 19.3R1 | 255
Documentation Updates | 257
Migration, Upgrade, and Downgrade Instructions | 258
7
Basic Procedure for Upgrading to Release 19.3 | 258
Upgrade and Downgrade Support Policy for Junos OS Releases | 261
Upgrading a Router with Redundant Routing Engines | 262
Junos OS Release Notes for the QFX Series | 263
What's New | 263
What’s New in Release 19.3R3 | 264
What’s New in Release 19.3R2 | 264
What’s New in Release 19.3R1 | 264
What's Changed | 272
What’s Changed in Release 19.3R3-S1 | 273
What's Changed in Release 19.3R3 | 273
What's Changed in Release 19.3R2-S6 | 275
What's Changed in Release 19.3R2 | 276
What's Changed in Release 19.3R1 | 276
Known Limitations | 278
Class of Service (CoS) | 279
EVPN | 279
Platform and Infrastructure | 279
Infrastructure | 280
Layer 2 Features | 280
Routing Protocols | 281
Open Issues | 281
EVPN | 282
High Availability (HA) and Resiliency | 282
Infrastructure | 282
Interfaces and Chassis | 282
Junos Fusion Provider Edge | 283
Layer 2 Features | 283
Platform and Infrastructure | 283
Routing Protocols | 285
Virtual Chassis | 286
Resolved Issues | 286
Resolved Issues: Release 19.3R3 | 287
Resolved Issues: Release 19.3R2 | 295
8
Resolved Issues: Release 19.3R1 | 299
Documentation Updates | 306
Migration, Upgrade, and Downgrade Instructions | 307
Upgrading Software on QFX Series Switches | 307
Installing the Software on QFX10002-60C Switches | 310
Installing the Software on QFX10002 Switches | 310
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 | 311
Installing the Software on QFX10008 and QFX10016 Switches | 313
Performing a Unified ISSU | 317
Preparing the Switch for Software Installation | 318
Upgrading the Software Using Unified ISSU | 318
Upgrade and Downgrade Support Policy for Junos OS Releases | 320
Junos OS Release Notes for SRX Series | 321
What’s New | 322
What’s New in Release 19.3R3 | 322
What’s New in Release 19.3R2 | 322
What’s New in Release 19.3R1 | 322
What's Changed | 330
What's Changed in Release 19.3R3 | 331
What's Changed in Release 19.3R2-S6 | 332
What's Changed in Release 19.3R2 | 333
What's Changed in Release 19.3R1 | 333
Known Limitations | 335
Authentication and Access Control | 336
J-Web | 336
Logical Systems and Tenant Systems | 337
Platform and Infrastructure | 337
VPNs | 337
Open Issues | 338
Flow-Based and Packet-Based Processing | 338
9
Intrusion Detection and Prevention (IDP) | 338
J-Web | 339
Routing Policy and Firewall Filters | 339
VPNs | 339
Resolved Issues | 340
Resolved Issues: Release 19.3R3 | 340
Resolved Issues: Release 19.3R2 | 346
Resolved Issues: Release 19.3R1 | 349
Documentation Updates | 357
Migration, Upgrade, and Downgrade Instructions | 357
Upgrade and DowngradeSupport Policy for Junos OS Releases and Extended End-Of-Life
Releases | 358
Upgrading Using ISSU | 359
Licensing | 359
Finding More Information | 360
Documentation Feedback | 360
Requesting Technical Support | 361
Self-Help Online Tools and Resources | 361
Opening a Case with JTAC | 362
Revision History | 362
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.3R3 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
10
What's New | 11
What's Changed | 19
Known Limitations | 23
Open Issues | 25
Resolved Issues | 27
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
These release notes accompany Junos OS Release 19.3R3 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
What's New in Release 19.3R3 | 11
What's New in Release 19.3R2 | 11
What’s New in Release 19.3R1-S1 | 11
What's New in Release 19.3R1 | 12
Learn about new features introduced in the Junos OS main and maintenance releases for ACX Series
routers.
11
What's New in Release 19.3R3
There are no new features or enhancements to existing features for ACX Series Universal Metro Routers
in Junos OS Release 19.3R3.
What's New in Release 19.3R2
There are no new features or enhancements to existing features for ACX Series Universal Metro Routers
in Junos OS Release 19.3R2.
What’s New in Release 19.3R1-S1
Hardware
New ACX5448-M Universal Metro Routers—In Junos OS Release 19.3R1-S1, we introduce the
•
ACX5448-M, a top-of-rack router with support for advanced security capabilities such as Media Access
Control Security (MACsec). A compact 1 U model, the ACX5448-M provides a system throughput of up
to 800 Gbps through the following port configuration:
Forty-four 10-Gigabit Ethernet SFP+ or 1-Gigabit Ethernet SFP ports (0 through 43). The ACX5448-M
•
supports MACsec only on these ports.
Six 100-Gigabit Ethernet QSFP28 or 40-Gigabit Ethernet QSFP+ ports (44 through 49). You can
•
channelize each QSFP28 port into four 25-Gbps interfaces and each QSFP+ port into 10-Gbps interfaces
using breakout cables (and the channelization configuration).
The ACX5448-M routers have redundant fan modules and redundant AC or DC power supply modules.
New ACX5448-D Universal Metro Routers—In Junos OS Release 19.3R1-S1, we introduce the
•
ACX5448-D, a top-of-rack router for aggregation environments. Designed for packet-optical convergence,
this compact 1 U router provides wire-speed packet performance, very low latency, and a rich set of
Layer 2 and Layer 3 features.
The ACX5448-D provides a system throughput of up to 800 Gbps through the following port
configuration:
Thirty-six 10-Gigabit Ethernet SFP+ or 1-Gigabit Ethernet SFP ports (0 through 35).
•
Two 100-Gigabit Ethernet QSFP28 or 40-Gigabit Ethernet QSFP+ ports (36 and 37). You can channelize
•
each QSFP28 port into four 25-Gbps interfaces and each QSFP+ port into four 10-Gbps interfaces
using breakout cables (and the channelization configuration).
Two 200-Gigabit Ethernet CFP2-DCO ports (38 and 39).
•
The ACX5448-D routers have redundant fan modules and redundant AC or DC power supply modules.
What's New in Release 19.3R1
12
Class of Service
Class of Service (CoS) parity support for ACX5000 routers—Starting in Junos OS 19.3R1, the
•
Class-of-Service feature set is supported on ACX5000 devices to enable users to configure classification,
rewrite, shaping, queueing, and scheduling parameters for traffic flow.
For more information regarding CoS, see Understanding Class of Service.
Support for Class-of-Service (CoS) for ACX5448 devices—Starting in Junos OS 19.3R1, support is
•
provided for Class-of-Service (COS) on ACX5448 devices to include firewall filter families (ANY, VPLS,
ethernet-switching, CCC, IPv6, IPv4, Lo0-IPv6, Lo0-IPv4, and MPLS), and CoS (classification, policing,
forwarding policy, forwarding class to queue map, WRED and Tail drop profiles, fabric queue and
scheduling configuration, scheduler, deep buffers, and remarking).
For more information regarding CoS, see Understanding Class of Service.
High Availability (HA) and Resiliency
VRRP support (ACX5448)—Starting in Junos OS Release 19.3R1, the ACX5448 router supports the
•
Virtual Router Redundancy Protocol (VRRP) over aggregated Ethernet and integrated routing and bridging
(IRB) interfaces. The VRRP queue size is limited, so it doesn’t disturb other protocols such as Bidirectional
Forwarding Detection (BFD) and connectivity fault management (CFM). The ACX5448 supports 16
VRRP groups.
[See Understanding VRRP. ]
•
Software Support (ACX5448-D and ACX5448-M)—Starting in Junos OS Release 19.3R1, ACX5448-D
and ACX5448-M routers support:
Chassis management software—Manages the onboard FRUs
•
Upgradable common BIOS software—Initializes all the devices on the hardware
•
FPC and PIC management
•
Interfaces and Chassis
Hardware resiliency support (ACX5448-D and ACX5448-M)—Starting in Junos OS Release 19.3R1,
•
ACX5448-D and ACX5448-M routers support the resiliency feature, which includes handling of hardware
failure and faults. Resiliency on an ACX5448-D enhances its debugging capability in the case of hardware
failure of its components such as Routing Engine, solid-state drive (SSD), and PCI Express. For example,
the resiliency feature enables the router to recover from inter-integrated circuit (I2C) failure, and improves
its voltage monitoring, temperature monitoring, and PCI Express error handling and reporting. The
resiliency feature also provides DRAM single-bit and multibit error checking and correction (ECC)
capabilities.
[See show chassis fpc errors.]
Interface speed, channelization, and MACsec support (ACX5448-M)—In Junos OS Release 19.3R1, we
•
introduce the ACX5448-M Universal Metro Router with support for advanced security capabilities such
as Media Access Control Security (MACsec). The ACX5448-M has the following port types:
13
Forty-four 10-Gigabit Ethernet or 1-Gigabit Ethernet SFP+ ports (0 through 43). Based on the optics
•
plugged in, the ports come up either as 1-Gbps or 10-Gbps.
Six 100-Gigabit Ethernet QSFP28 ports (44 through 49). These ports support 100-Gbps (the default)
•
and 40-Gbps speeds. You can channelize these ports into four 25-Gbps or four 10-Gbps interfaces.
The 44 SFP+ ports on the ACX5448-M support MACsec; however, the six QSFP28 ports do not support
MACsec.
[See Channelize Interfaces on ACX5448-D and ACX5448-M Routers.]
Layer 2 Features
Support for Layer 2 Features (ACX5448-D and ACX5448-M)—Starting in Junos OS Release 19.3R1,
•
Junos OS supports Layer 2 bridging, Q-in-Q tunneling, no-local switching, Layer 2 protocol tunneling,
Spanning Tree Protocols (RSTP,MSTP), Bridge Protocol Data Unit (guard, root and loop protect), Ethernet
OAM, VPLS, BGP, LDP, pseudowire ping, and Bidirectional Forwarding Detection (BFD) support for
virtual circuit connectivity verification (VCCV) on ACX5448-D and ACX5448-M routers.
Support for Layer 2 switching cross-connects (ACX5440)—Starting in Junos OS Release 19.3R1, you
•
can leverage the hardware support available for cross-connects on the ACX5448 device with the Layer
2 local switching functionality using certain models. With this support, you can provide the EVP and
Ethernet Virtual Private Line (EVPL) services.
[See Configuring Layer 2 Switching Cross-Connects Using CCC.]
Layer 3 Features
Support for Layer 3 features (ACX5448-D and ACX5448-M)—Starting in Junos OS Release 19.3R1,
•
Junos OS supports Layer 3 protocols, multicast, and MPLS as the transport mechanism on ACX5448-D
and ACX5448-M routers.
Management
OpenConfig AAA data model support (ACX1100, ACX2100, ACX5448, ACX6360, EX4300, MX240,
•
MX480, MX960, MX10003, PTX10008, PTX10016, QFX5110, and QFX10002)—Junos OS Release
19.3R1 supports the configuration leaves specified in the OpenConfig AAA data model. Mapping the
OpenConfig AAA configuration to the Junos AAA configuration using the following YANG files in the
data model makes this support possible:
openconfig-aaa.yang
•
openconfig-aaa-types.yang
•
openconfig-aaa-tacacs.yang
•
openconfig-aaa-radius.yang
•
14
The configuration model supporting the OpenConfig data model includes:
A translation script (.py / .slax) that maps each configuration leaf in the OpenConfig schema to one
•
or more configuration leafs in the JUNOS OS schema.
A deviation file (.yang) that specifies how much the implementation deviates from the vendor-neutral
•
model.
[See Mapping OpenConfig AAA Commands to Junos Configuration.]
Network Management and Monitoring
Support for adding custom YANG data models to the Junos OS schema (ACX5448-D and
•
ACX5448-M)—Starting in Junos OS Release 19.3R1, ACX5448-D and ACX5448-M routers support
loading custom YANG data models on the device, which enables you to add RPCs or configuration
hierarchies that are customized for your operations. The ability to add data models to a device is beneficial
when you want to create device-agnostic RPCs and configuration models that can be used on different
devices from one or more vendors.
[See Understanding the Management of Non-Native YANG Modules on Devices Running Junos OS.]
Port Security
Media Access Control Security (MACsec) support (ACX5448)—Starting with Junos OS Release 19.3R1,
•
ACX5448 routers support MACsec on 1-Gigabit Ethernet SFP and 10-Gigabit Ethernet SFP+ ports.
MACsec is an industry-standard security technology that provides secure communication for all traffic
on point-to-point Ethernet links. MACsec is standardized in IEEE 802.1AE.
15
[See Understanding Media Access Control Security (MACsec).]
Routing Policy and Firewall Filters
Match condition support for IPv6 firewall filters (ACX6360)—Starting in Junos OS Release 19.3R1, the
•
ACX6360 router supports the following firewall filter match conditions for IPv6 traffic: address,
destination-address, destination-port, destination-port-except, destination-prefix-list, port, port-except,
icmp-code, icmp-code-except, icmp-type, icmp-type-except, next-header, next-header-except, prefix-list,
source-address, source-port, source-port-except, and source-prefix-list.
[See Firewall Filter Match Conditions for IPv6 Traffic on ACX Series Routers and ACX6360
Documentation. ]
Routing Protocols
Clocking and Synchronous Ethernet support (ACX5448)—Starting in Junos OS Release 19.3R1, ACX5448
•
routers support frequency synchronization using the Synchronous Ethernet and Ethernet Synchronization
Message Channel (ESMC) protocols. The routers also support phase and time synchronization through
Precision Time Protocol (PTP).
[See Synchronous Ethernet Overview.]
Transparent clock over IPv6 support (ACX5448)—Starting with Junos OS Release 19.3R1, ACX5448
•
routers support transparent clock functionality for PTP over IPv6. To configure the transparent clock
functionality, you must include the e2e-transparent statement at the [edit protocol ptp] hierarchy level.
Use the show ptp global-information command to check the status of the transparent clock functionality
configured on the router.
[See Understanding Transparent Clocks in Precision Time Protocol.]
Support for RIPv2 (ACX5448)—Starting in Junos OS Release 19.3R1, Junos OS supports RIP version 2
•
(RIPv2) for both IPv4 and IPv6 packets.
Services Applications
•
Support for Two-Way Active Measurement Protocol or TWAMP (ACX5448-D and ACX5448-M)—Starting
in Junos OS Release 19.3R1, you can configure TWAMP on your ACX5448-D and ACX5448-M routers.
TWAMP enables you measure the IP performance between two devices in a network. The ACX5448-D
and ACX5448-M routers support only the reflector side of TWAMP.
[See Two-Way Active Measurement Protocol on ACX Series.]
•
Support for virtualization (ACX5448-D and ACX5448-M)—Starting in Junos OS Release 19.3R1, the
Routing Engines on the ACX5448-D routers and ACX5448-M routers support virtualization.
On Routing Engines of ACX5448-D routers and ACX5448-M routers, one instance of Junos OS, which
runs as a guest operating system, is launched by default. The user needs to log in to this instance for
operations and management.
With virtualization of the Routing Engine, Junos OS supports new request and show commands associated
with host and hypervisor processes. The commands are related to:
16
Reboot, halt, and power management for the host
•
Software upgrade for the host
•
Disk snapshot for the host
•
[See What Are VM Hosts?.]
Port mirroring support for the IPv6 address family (ACX6360)—Starting in Release 19.3R1, you can
•
configure port mirroring on the ACX6360 router for the inet6 family. Port mirroring copies packets
entering or exiting a port and sends the copies to a local interface for local monitoring. You can use port
mirroring to send traffic to applications that analyze traffic for purposes such as monitoring compliance,
enforcing policies, detecting intrusions, monitoring and predicting traffic patterns, and correlating events.
[See Configuring Port Mirroring.]
Software Installation and Upgrade
Migration of Linux kernel version—Starting in Junos OS Release 19.3R1, the following devices support
•
the Wind River Linux 9 (WRL9) kernel version:
Routing Engine SupportedPlatforms
RE-ACX-5448ACX5448-D
RE-S-X6-64GMX240, MX480, and MX960
REMX2K-X8-64GMX2020 and MX2010
17
Routing Engine SupportedPlatforms
RE-S-1600x8MX204
RE-S-1600x8MX10003
RE-MX2008-X8-64GMX2008
RE X10MX10016
RE X10MX10008
RE-PTX-X8-64GPTX5000
RCBPTXPTX3000
RE-PTX-2X00x4/RE X10PTX10016
RE-PTX-2X00x4/RE X10PTX10008
RE-PTX1000PTX1000
RE-PTX10002-60CPTX10002-XX
RE-S-EX9200-2X00x6EX9208
EX9251-REEX9251
EX9253-REEX9253
RE-S-EX9200-2X00x6EX9204
RE-S-EX9200-2X00x6EX9214
RE-QFX10002-60CQFX10002
RE-QFX10008QFX10008
RE-QFX10016QFX10016
Starting in Junos OS Release 19.3R1, in order to install a VM host image based on Wind River Linux 9,
you must upgrade the i40e NVM firmware on the following routers:
MX Series—MX240, MX480, MX960, MX2010, MX2020, MX2008, MX10016, and MX10008
•
PTX Series—PTX3000, PTX5000, PTX10016, PTX10008, and PTX10002-XX
•
If you perform a software upgrade on a router with i40e NVM version earlier than 6.01, the upgrade
fails and the following error message is displayed:
ERROR: i40e NVM firmware is not compatible ,please upgrade i40e NVM before installing this package
ERROR: Aborting the installation
ERROR: Upgrade failed
[See https://kb.juniper.net/TSB17603.]
System Management
Transparent clock functionality support on (ACX5448)—Starting in Junos OS Release 19.3R1, transparent
•
clock functionality and a global configuration for enabling it are supported on the ACX5448 router.
Transparent clock functionality works for PTP over both IPv4 and Ethernet packets. To check the status
of transparent clock, use the show ptp global-information command.
[See Understanding Transparent Clocks in Precision Time Protocol. ]
18
Synchronous Ethernet and PTP support (ACX 5448)—Starting in Junos OS Release 19.3R1, the ACX5448
•
router supports the following features:
Frequency synchronization using Synchronous Ethernet
•
Ethernet Synchronization Message Channel (ESMC)
•
Phase and time synchronization using Precision Timing Protocol (PTP)
•
[See Synchronous Ethernet Overview. ]
SEE ALSO
What's Changed | 19
Known Limitations | 23
Open Issues | 25
Resolved Issues | 27
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
What's Changed
IN THIS SECTION
What’s Changed in Release 19.3R3-S1 | 20
What's Changed in Release 19.3R3 | 20
What's Changed in Release 19.3R2-S6 | 20
What's Changed in Release 19.3R2 | 21
What's Changed in Release 19.3R1 | 21
See what changed in the Junos OS main and maintenance release for ACX Series routers.
19
What’s Changed in Release 19.3R3-S1
Routing Protocols
Advertising /32 secondary loopback addresses to traffic engineering database as prefixes (ACX Series,
•
EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We've made changes to export multiple
loopback addresses to the lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of
advertising secondary loopback addresses as router IDs instead of prefixes. In earlier releases, multiple
secondary loopback addresses in the traffic engineering database were added to the lsdist.0 and lsdist.1
routing tables as part of node characteristics and advertised them as the router ID.
What's Changed in Release 19.3R3
General Routing
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.
20
[See gigether-options.]
Juniper Extension Toolkit (JET)
Set the trace log to only show error messages (ACX Series, EX Series, MX Series, PTX Series, QFX
•
Series, SRX Series)— You can set the verbosity of the trace log to only show error messages using the
error option at the edit system services extension-service traceoptions level hierarchy.
See traceoptions (Services).
What's Changed in Release 19.3R2-S6
Network Management and Monitoring
Support for disconnecting unresponsive NETCONF-over-SSH clients (ACX Series, EX Series, MX Series,
•
NFX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—You can enable devices to automatically
disconnect unresponsive NETCONF-over-SSH clients by configuring the client-alive-interval and
client-alive-count-max statements at the [edit system services netconf ssh] hierarchy level. The
client-alive-interval statement specifies the timeout interval in seconds, after which, if no data has been
received from the client, the device requests a response, and the client-alive-count-max statement
specifies the threshold of missed client-alive responses that triggers the device to disconnect the client,
thereby terminating the NETCONF session.
See ssh (NETCONF).
Changes to commit RPC responses in RFC-compliant NETCONF sessions (ACX Series, EX Series, MX
•
Series, PTX Series, QFX Series, and SRX Series)—When you configure the rfc-compliant statement at
the edit system services netconf hierarchy level, the NETCONF server's response for commit operations
includes the following changes:
If a successful commit operation returns a response with one or more warnings, the warnings are
•
redirected to the system log file, in addition to being omitted from the response.
The NETCONF server response emits the <source-daemon> element as a child of the <error-info>
•
element instead of the <rpc-error> element.
If you also configure the flatten-commit-results statement at the edit system services netconf hierarchy
•
level, the NETCONF server suppresses any <commit-results> XML subtree in the response and only
emits an <ok> or <rpc-error> element.
See Configuring RFC-Compliant NETCONF Sessions.
What's Changed in Release 19.3R2
There are no changes in behavior and syntax for ACX Series in Junos OS Release 19.3R2.
What's Changed in Release 19.3R1
21
Interfaces and Chassis
Support for creating Layer 2 logical interfaces independently (ACX Series, EX Series, MX Series, PTX
•
Series, and QFX Series)—In Junos OS Release 19.3R1 and later, ACX Series routers support creating
Layer 2 logical interfaces independent of the Layer 2 routing-instance type. That is, you can configure
and commit the Layer 2 logical interfaces separately and add the interfaces to the bridge domain or
Ethernet VPN (EVPN) routing instance separately. Note that the Layer 2 logical interfaces work fine only
when they are added to the bridge domain or EVPN routing instance.
In earlier Junos OS releases, when you use a Layer 2 logical interface configuration (units with
encapsulation vlan-bridge configuration), then you must add the logical interface as part of a bridge
domain or EVPN routing instance for the commit to succeed.
Monitoring information available only in trace log (ACX Series)—In Junos OS Release 19.3R1 and later,
•
the Ethernet link fault management daemon (lfmd process) in the peer router stops monitoring the locally
occurred errors until unified ISSU completes. You can view the monitoring-related details only through
the trace log file.
Junos OS XML API and Scripting
Range defined for confirm-timeout value in NETCONF and Junos XML protocol sessions (ACX Series,
•
EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.3R1,
the value for the <confirm-timeout> element in the Junos XML protocol <commit-configuration>
operation must be in the range 1 through 65,535 minutes, and the value for the <confirm-timeout>
element in the NETCONF <commit> operation must be in the range 1 through 4,294,967,295 seconds.
In earlier releases, the range is determined by the minimum and maximum value of its unsigned integer
data type.
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.3R1, 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.3R1, the show bgp output-scheduler | display
xml rpc CLI command does not have an XML RPC equivalent.
[See show bgp output-scheduler.]
System Logging
Preventing system instability during core file generation (ACX Series)—Starting with Release 19.3R1
•
onward, Junos OS checks for available storage space on the Routing Engine before generating core files
either on request or because of an assertion condition. This check ensures that your device does not
become unstable because of shortage of storage space on the Routing Engine. If the available space is
not sufficient, core files are not generated. Instead, Junos OS either displays the Insufficient Disk space
!!! Core generation skipped message as an output or issues the syslog message core generation is skipped
due to disk full.
Operation, Administration, and Maintenance (OAM)
22
Performance monitoring history data is lost when a change in number of supported history records is
•
detected (ACX Series and MX Series)—In Junos OS Release 19.3R1, when Ethernet connectivity fault
management starts, it detects the number of history records supported by the existing performance
monitoring history database and if there is any change from the number of history records supported
(that is, 12) in Release 19.3R1, then the existing performance monitoring history database is cleared and
all performance monitoring sessions are restarted with mi-index 1.
SEE ALSO
What's New | 11
Known Limitations | 23
Open Issues | 25
Resolved Issues | 27
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
Known Limitations
IN THIS SECTION
General Routing | 23
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
PTP IP packets queued to the best -effort queue instead of to the network control queue by default.
•
PR1361315
23
Filter for sensors (Optical and OTN) does not work. PR1371996
•
For the et interface, the FEC and FRR alarms are not raised. PR1371997
•
The clock class to QL level mapping must be changed through CLI on the ACX2100 router with network
•
option-1. PR1384968
The clock class must be changed to quality level mapping on the ACX2100 router with network option-2.
•
PR1386916
The PTP slave gets stuck in the Initialize state intermittently due to the ARP resolution issue when PTP
•
and interfaces flaps continuously. PR1410746
For the ACX6360-OR routers, use the PTX10001 router documentation and not the ACX Series router
•
documentation. PR1417258
Hardware-based fragmentation or reassembly is not supported. Software-based fragmentation rates
•
goes extremely slow depending on CPU load. PR1419371
Oversized frames are accounted twice (input packet and oversized frames) in the extensive command.
•
PR1425748
Error messages might be observed if the optics is unplugged during the EEPROM read. This is expected
•
and does not impact any functionality. PR1429016
On the ACX5448-D interfaces, the pps and bps for the aggregated Ethernet logical interfaces do not
•
get displayed during traffic flow. PR1429590
Incorrect queue statistics are observed for PTPOE multicast packets. PR1429628
•
On the ACX5448-D interfaces, the Jabber frames counter does not increment correctly. PR1429923
•
On the ACX5448-D interfaces, the input bytes value displayed in the show interfaces extensive command
•
output is not at par with that of the older ACX Series devices. PR1430108
On the ACX5448-D interfaces, the interface LEDs glow after the system halts. PR1430129
•
On the ACX5448-D interfaces, the following error message is observed:
•
rio_mic_cfp2_ifd_ot_eth_media_conf port command handler failed. PR1430355
On the ACX5448-D interfaces, the MTU error count in the output interface does not increment when
•
frames are dropped due to less MTU output. PR1430446
The 1-Gigabit interfaces are displayed as xe. This issue is observed with respect to auto-negotiation
•
parameters even though there is no functional impact. PR1430835
The l2cpd process generates the core file continuously after loading the 19.3 DCB image. PR1431866
•
On the ACX5448-D interface, when configured over Layer 2 VPN with control-channel set, BFD gets
•
to the Down state. PR1432854
Incase of Dot1P, CFI rewrite based on TC or DP classification is not possible on the ACX5448, ACX-710,
•
and ACX-R6675 Series routers. PR1435966
24
The new rate 1.8 MB/s that takes 16 to 17 minutes to copy an ACX5448 image size of 1.9-Gigabit, the
•
ACX5448 router takes lesser time. Since, the rate limiter is in bps and does not support pps based, which
is a hardware limitation from DNX, the average size is 512. PR1439960
The hold timer expiry is common across all platforms. It is not specific to the ACX5448 Series of routers.
•
PR1439980
With an asymmetric network connection (for example, a 10GbE MACsec port connected to a 10GbE
•
channelized port), high and asymmetric T1 and T4 time errors lead to a high two-way time error.
PR1440140
By default, the management interface speed is always displayed as 1000 Mbps in Junos OS command
•
output. PR1440675
TC performance with 1-Gigabit Ethernet enables MACsec. PR1441388
•
On the ACX5448-M interface, the Jitter tolerance test fails over MACsec ports. PR1447296
•
IGMPv3 rate of join supported in the ACX5448 routers or an ACX5448-D interface is around 900 joins
•
per second. PR1448146
The aggregated Ethernet interface speed is displayed incorrectly when 1-Gigabit Ethernet member links
•
are a part of the aggregated Ethernet interface. PR1449887
Input packet rejects counter when the MAC address is not supported. PR1463981
•
SEE ALSO
What's New | 11
What's Changed | 19
Open Issues | 25
Resolved Issues | 27
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
Open Issues
IN THIS SECTION
General Routing | 25
Platform and Infrastructure | 27
Virtual Chassis | 27
25
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
Loopback status is not displayed for ot interfaces on CLI, which is available from vty only. PR1358017
•
The show class-of-service interface command does not show the classifier information. PR1522941
•
The Layer 2 VPN might flap and the CE device facing interface cannot restore the TX optical laser power
•
even if the Layer 2 VPN is in the Up status under the asynchronous-notification. PR1486181
The routes update might fail upon the HMC memory issue and traffic impact might be seen. PR1515092
•
The SD threshold is set above the SF threshold. PR1376869
•
On the ACX6360-OR router, enhancement is needed for the FRR BER threshold SNMP support.
•
PR1383303
Tx power cannot be configured using the + sign. PR1383980
•
Traffic gets lost for more than 50 minutes under certain conditions. PR1387858
•
The circuit cross-connect logs are not compressed after rotation. PR1398511
•
The jnxIfOtnOperState trap notification is sent for all ot interfaces. PR1406758
•
The Layer 2 rewrite does not occur on the UNI side for the packet arriving from the MPLS core.
•
PR1414414
Clock class value is incorrect in the default data when the slave interface is down in the PTP-OC device.
•
PR1416421
On the ACX5448 router, ZTP proceeds to load the image even when there is a platform string mismatch
•
with the platform and software image names on the ZTP server. PR1418313
On the ACX5448 router, the firewall filter works in a different way if it is untagged traffic. PR1423214
•
The fpc process might crash with em2 configuration during initialization. PR1429212
•
DHCP clients are not able to scale to 96000. PR1432849
•
Logical interfaces or protocols take time to come up. PR1433426
•
Forwarding occurs when using non-existing SSM map source address in IGMPv3 instead of pruning.
•
PR1435648
The time consumed on 1-Gigabit performance is not equal to as compared to 10-Gigabit. 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 percent of the mean latency introduced by the each phy which is of around 2.5us).
PR1437175
26
On the ACX5448-D interfaces, the following error message is observed when an interface is brought
•
up: fpc0 otnpic_otn_frr_set pic='et-0/2/0' link=0 IFD=et-0/2/0 error=7. PR1438039
Memory leakage is observed while running the longevity check. PR1438358
•
On the ACX5448-D interfaces, the logical interface statistics are not displayed correctly. PR1439124
•
Using an unnumbered interface for ECMP results in a few next hop being nonresponsive in the KRT
•
queue. PR1442622
Recovery of Junos OS volume from OAM becomes nonresponsive indefinitely. PR1446512
•
On the ACX5448-X or ACX5448-M interfaces, the drop profile maximum threshold might not reach to
•
its limit when the packet size is other than 1000 bytes. PR1448418
oper-state for the et interface does not transition from the Init state to the Normal state. PR1449937
•
While checking the BFD functionality over a Layer 2 VPN client, the BFD session does not come up.
•
PR1483014
On the ACX5048 routers, traffic loss is observed during the unified ISSU upgrade. PR1483959
•
The CLI command configures announce-interval to -3 so that the announce messages rate is set to 8
•
pps. PR1507782
On the ACX5048 or ACX5096 line of routers, the LACP control packets might get dropped due to high
•
CPU utilization. PR1493518
Platform and Infrastructure
On the ACX5448-M interface, the CFM remote MEP does not come up after configuration. PR1460555
•
Virtual Chassis
On the ACX5000 router, the following false positive parity error message is observed:
•
_soc_mem_array_sbusdma_read. PR1276970
SEE ALSO
What's New | 11
What's Changed | 19
Known Limitations | 23
27
Resolved Issues | 27
Documentation Updates | 34
Migration, Upgrade, and Downgrade Instructions | 35
Resolved Issues
IN THIS SECTION
Resolved Issues: 19.3R3 | 28
Resolved Issues: 19.3R2 | 30
Resolved Issues: 19.3R1 | 31
Learn which issues were resolved 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.
Resolved Issues: 19.3R3
General Routing
On the ACX5000 router, the following error message is observed: MacDrainTimeOut and
•
bcm_port_update failed: Internal error. PR1284590
The gigether-options command are enabled again under the interface hierarchy. PR1430009
•
On the ACX5448-D interface, while performing repeated power-off or power-on of the device, SMBUS
•
transaction timeout is observed. PR1463745
High CPU utilization of the fxpc process might be observed with the class-of-service changes on
•
interfaces. PR1407098
Policer discarded count is displayed incorrectly to the enq count of the interface queue. But the traffic
•
behavior is as expected. PR1414887
On the ACX2200 routers, the drift messages, which is a PTP hybrid (PTP + Synchronous Ethernet), are
•
observed. PR1426910
The input bytes value displayed in the show interfaces extensive command output is not at par with
•
that of the older ACX Series routers. PR1430108
28
The l2cpd process might crash and generate a core file when interfaces flap. PR1431355
•
On the ACX5448 routers, the encapsulation flexible-vlan-tagging is not supported with the MPLS family.
•
PR1445046
On the ACX5448-M routers, fans might not run at the correct speed. PR1448884
•
On the ACX5048 routers, the SNMP polling is stalled after the link is flapped or the SFP transceiver is
•
replaced. The following error message is observed:
ACX_COS_HALP(acx_cos_gport_sched_set_strict_priority:987): Failed to detach logs. PR1455722
The rpd process might crash if a BGP route is resolved over the same prefix protocol next hop in an
•
inet.3 table that has both RSVP and LDP routes. PR1458595
On enabling the local loopback, the 10-Gigabit Ethernet interface goes down. PR1460715
•
The ARP resolution issue might be observed while bringing up the aggregated Ethernet interface after
•
reboot. PR1461485
Memory leakage on the l2cpd process might lead to l2cpd crash. PR1469635
•
RED drop might be seen on an interface even when there is no congestion. PR1470619
•
On the ACX5048 routers, the egress queue statistics are not applicable to the aggregated Ethernet
•
interfaces. PR1472467
FPC might continuously crash after deactivating or activating the loopback filter or rebooting the system
•
after configuring the loopback filter. PR1477740
The dcpfe process might crash when disabling or enabling MACsec. PR1479710
•
Links might not come up when the 100-Gigabit Ethernet interface is channelized into 4x25-Gigabit
•
Ethernet interfaces. PR1479733
RPD memory chunk size is optimized for the ACX Series routers to reduce the memory foot print.
•
PR1481151
On the ACX5448 routers, the following logs are reported: dnx_nh_mpls_tunnel_install. PR1482529
•
On the ACX5448 router, the fpc process might crash. PR1485315
•
On the ACX5448 routers, the Layer 2 VPN with the ethernet-ccc input-vlan-map/output-vlan-map
•
interface silently discard the traffic. PR1485444
The queue statistics are not as expected after configuring the IFD and logical interface shaping with the
•
transmit rate and scheduler-map. PR1488935
During speed mismatch, the QSFP28 or QSFP+ optics or cables might not work. PR1494600
•
Outbound SSH connection flap or memory leakage issue might be observed while pushing the
•
configuration to the ephemeral database with a high rate. PR1497575
On the ACX500 router, the SFW sessions might not get updated on the MS interfaces. PR1505089
•
29
The PIC slot might get shut down in less than 240 seconds due to the over-temperature start time being
•
handled incorrectly. PR1506938
BFD flaps with the following error message after a random time interval: ACX_OAM_CFG_FAILED: ACX
•
Error (oam):dnx_bfd_l3_egress_create : Unable to create egress object. PR1513644
The l2ald process crashes during the stability test with traffic on a scaled setup. PR1517074
•
On the ACX5448 Chassis, the MAC-address and label MAC-address might not match. PR1489034
•
Interfaces and Chassis
The MC-AE interface displays status as Unknown if the subinterface is added as part of the VLAN on
•
the peer MC-AE node. PR1479012
Layer 2 Ethernet Services
Member links states might be asynchronized on a connection between the PE and CE devices in the
•
EVPN active/active scenario. PR1463791
MPLS
The BGP session might flap between two directly connected BGP peers because of the wrong TCP MSS
•
(maximum segment size) in use. PR1493431
Routing Protocols
The BGP route target family might prevent the route reflector from reflecting the Layer 2 VPN and Layer
•
3 VPN routes. PR1492743
VPNs
30
The Layer 2 circuit neighbor might get stuck in the RD state at one end of the MG-LAG peer. PR1498040
•
Resolved Issues: 19.3R2
General Routing
The AE interface with LACP stays down after the router reboots if the link-speed is configured.
•
PR1357012
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
On the ACX5448-X:SKU and ACX5448-D, 96000 ARPs gets populated however, only 47000 NH entries
•
are present. Around 50 percentage of packet drop is observed. PR1426734
The deviation in traffic rate in the queue is around 8 to 10 percentage in some cases. PR1436297
•
The interface on ACX1100 remains down while using SFP-1FE-FX (740-021487). PR1439384
•
In an ACX Series, the auto exported route between VRFs might not respond for icmp echo requests.
•
PR1446043
The ACX5048 l2circuit with backup neighbor configuration stops passing traffic after the link flaps and
•
move back from backup neighbor to primary. PR1449681
On the ACX5448-X NPI platforms, after disabling 100-Gigabit and 40-Gigabit interface laser output
•
power, the ACX5448-D interface diagnostics optics display some values. PR1452323
Loading...