Junos OS 19.3R1 User Manual
Release
Published
2021-04-22
Notes
Junos®OS 19.3R1 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
Support for two 100-Gigabit Ethernet QSFP28 transceivers on the 2-port QSFP+/QSFP28
•
uplink module
(EX4300-48MP, EX4300-48MP-S switches)
SOFTWARE HIGHLIGHTS
Adding custom YANG data models to the Junos OS schema (ACX5448-D and ACX5448-M)
•
Match condition for IPv6 firewall filters (ACX6360)
•
IGMP snooping for EVPN-VXLAN (EX9200 switches, MX Series, vMX)
•
Power over Ethernet IEEE 802.3bt (EX4300-48MP switches)
•
Configuring Q-in-Q tagging behavior for the native VLAN (EX4300 and EX4300-MP
•
switches and Virtual Chassis)
IPv6 filter-based forwarding (EX4650 and QFX5120 switches)
•
Input traffic control profile assignment to dynamic logical interface sets (MX Series)
•
Multiple routing instance for ping overlay and traceroute overlay on VXLAN (MX Series
•
routers and vMX virtual routers)
Seamless BFD inline mode for static segment routing LSPs (MX Series)
•
Program management interface in a nondefault routing instance in op scripts and JET
•
applications (MX Series)
IPv6 support in Python automation scripts (MX Series, PTX Series, and QFX Series)
•
Juniper AAA Model streaming telemetry support for subscriber services for JTI (MX Series)
•
OSPF TI-LFA back paths for Segment Routing (MX Series)
•
Dual virtual function (NFX150)
•
UDP tunnels using FTI interfaces (PTX Series)
•
VLAN tag manipulation: pop, push, and swap (PTX Series)
•
DSCP in APBR rule (SRX Series and vSRX)
•
Express Path (SRX4600)
•
Application quality of services for logical systems and tenant systems (SRX Series)
•
New SCB, IOC, and Routing Engine improve performance and scalability (SRX5400,
•
SRX5600, and SRX5800)
Diameter S6a authentication (SRX Series)
•
Release Notes: Junos®OS Release 19.3R1 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 | 13
Junos OS Release Notes for ACX Series | 13
What's New | 14
What’s New in 19.3R1-S1 | 14
What’s New in 19.3R1 | 15
What's Changed | 21
General Routing | 22
Junos OS XML API and Scripting | 22
Interfaces and Chassis | 22
System Logging | 23
Operation, Administration, and Maintenance (OAM) | 23
Known Limitations | 23
General Routing | 24
Open Issues | 25
General Routing | 26
Resolved Issues | 28
Resolved Issues: 19.3R1 | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
Upgrade and Downgrade Support Policy for Junos OS Releases | 32
Junos OS Release Notes for EX Series Switches | 33
What's New | 33
Hardware | 35
Authentication, Authorization and Accounting (AAA) (RADIUS) | 35
EVPN | 35
Forwarding and Sampling | 36
Interfaces and Chassis | 37
Junos Telemetry Interface | 37
Layer 2 Features | 39
Management | 39
Multicast | 40
Routing Policy and Firewall Filters | 40
2
Routing Protocols | 40
Services Applications | 40
Software Installation and Upgrade | 41
Virtual Chassis | 42
What's Changed | 44
General Routing | 44
Interfaces and Chassis | 45
Junos OS XML API and Scripting | 45
Layer 2 Features | 45
System Logging | 45
Known Limitations | 46
EVPN | 47
Infrastructure | 47
Platform and Infrastructure | 47
Open Issues | 48
Authentication and Access Control | 48
Infrastructure | 48
Interfaces and Chassis | 49
J-Web | 49
Network Management and Monitoring | 49
Platform and Infrastructure | 49
Routing Protocols | 50
Resolved Issues | 51
EVPN | 51
Forwarding and Sampling | 52
Infrastructure | 52
Interfaces and Chassis | 52
Layer 2 Ethernet Services | 52
Network Management and Monitoring | 52
Platform and Infrastructure | 52
Routing Protocols | 56
Subscriber Access Management | 56
User Interface and Configuration | 56
Virtual Chassis | 56
3
VPNs | 56
Documentation Updates | 57
Migration, Upgrade, and Downgrade Instructions | 57
Upgrade and Downgrade Support Policy for Junos OS Releases | 58
Junos OS Release Notes for Junos Fusion Enterprise | 58
What’s New | 59
What’s Changed | 60
Known Limitations | 60
Open Issues | 61
Junos Fusion for Enterprise | 61
Resolved Issues | 62
Resolved Issues: 19.3R1 | 62
Documentation Updates | 62
Migration, Upgrade, and Downgrade Instructions | 63
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 63
Upgrading an Aggregation Device with Redundant Routing Engines | 65
Preparing the Switch for Satellite Device Conversion | 66
Converting a Satellite Device to a Standalone Switch | 67
Upgrade and Downgrade Support Policy for Junos OS Releases | 67
Downgrading from Junos OS | 68
Junos OS Release Notes for Junos Fusion Provider Edge | 69
What's New | 69
What's Changed | 70
Known Limitations | 70
Open Issues | 71
Junos Fusion Provider Edge | 71
Resolved Issues | 72
Junos Fusion for Provider Edge | 72
Documentation Updates | 73
Migration, Upgrade, and Downgrade Instructions | 73
Basic Procedure for Upgrading an Aggregation Device | 74
Upgrading an Aggregation Device with Redundant Routing Engines | 76
Preparing the Switch for Satellite Device Conversion | 77
Converting a Satellite Device to a Standalone Device | 78
4
Upgrading an Aggregation Device | 80
Upgrade and Downgrade Support Policy for Junos OS Releases | 81
Downgrading from Junos OS Release 19.3 | 81
Junos OS Release Notes for MX Series 5G Universal Routing Platform | 82
What's New | 82
Hardware | 83
Authentication and Access Control | 83
Class of Service (CoS) | 84
EVPN | 85
General Routing | 86
Interfaces and Chassis | 87
Junos OS XML API and Scripting | 88
Junos Telemetry Interface | 88
Layer 2 Features | 92
Management | 93
MPLS | 93
Operation, Administration, and Maintenance (OAM) | 94
Port Security | 94
Routing Protocols | 95
Services Applications | 96
Software-Defined Networking (SDN) | 98
Software Installation and Upgrade | 98
Subscriber Management and Services | 100
What's Changed | 102
EVPN | 102
General Routing | 102
Interfaces and Chassis | 103
Junos OS XML API and Scripting | 103
MPLS | 103
Operation, Administration, and Maintenance (OAM) | 104
Routing Protocols | 104
Services Applications | 104
Software Defined Networking (SDN) | 105
Subscriber Management and Services | 105
5
System Logging | 105
Known Limitations | 106
General Routing | 106
Infrastructure | 107
Interfaces and Chassis | 107
MPLS | 108
Platform and Infrastructure | 108
Routing Protocols | 108
Open Issues | 109
EVPN | 109
Forwarding and Sampling | 110
General Routing | 110
Infrastructure | 116
Interfaces and Chassis | 117
J-Web | 118
Layer 2 Ethernet Services | 118
MPLS | 118
Platform and Infrastructure | 118
Routing Policy and Firewall Filters | 120
Routing Protocols | 120
Services Applications | 121
User Interface and Configuration | 121
VPN | 121
Resolved Issues | 122
Class of Service (CoS) | 123
EVPN | 123
Forwarding and Sampling | 124
General Routing | 124
Infrastructure | 133
Interfaces and Chassis | 134
Layer 2 Features | 135
Layer 2 Ethernet Services | 135
MPLS | 136
Network Address Translation (NAT) | 137
6
Network Management and Monitoring | 137
Platform and Infrastructure | 137
Routing Policy and Firewall Filters | 138
Routing Protocols | 138
Services Applications | 140
Software Installation and Upgrade | 141
Subscriber Access Management | 141
User Interface and Configuration | 141
VPNs | 141
Documentation Updates | 142
Migration, Upgrade, and Downgrade Instructions | 143
Basic Procedure for Upgrading to Release 19.3 | 144
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 144
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 147
Upgrade and Downgrade Support Policy for Junos OS Releases | 148
Upgrading a Router with Redundant Routing Engines | 149
Downgrading from Release 19.3 | 149
Junos OS Release Notes for NFX Series | 150
What’s New | 150
Application Security | 151
Interfaces | 151
What's Changed | 151
Factory-Default Configuration | 152
Known Limitations | 152
Interfaces | 153
Platform and Infrastructure | 153
Open Issues | 153
High Availability | 154
Interfaces | 154
Platform and Infrastructure | 154
Virtual Network Functions (VNFs) | 155
7
Resolved Issues | 155
Class-of-Service (CoS) | 156
Interfaces | 156
Platform and Infrastructure | 157
Protocols | 157
Virtual Network Functions (VNFs) | 157
Documentation Updates | 158
Migration, Upgrade, and Downgrade Instructions | 158
Upgrade and Downgrade Support Policy for Junos OS Releases | 159
Basic Procedure for Upgrading to Release 19.3 | 159
Junos OS Release Notes for PTX Series Packet Transport Routers | 160
What's New | 161
Class of Service | 162
Interfaces and Chassis | 162
Junos OS XML, API, and Scripting | 162
Junos Telemetry Interface | 163
Management | 165
MPLS | 165
Network Management and Monitoring | 165
Routing Policy and Firewall filters | 166
Routing Protocols | 166
Security | 167
Software Installation and Upgrade | 167
What's Changed | 169
General Routing | 170
Interfaces and Chassis | 170
Junos OS XML, API, and Scripting | 171
Software Defined Networking | 171
System Logging | 171
Known Limitations | 172
General Routing | 172
Interfaces and Chassis | 173
Open Issues | 174
General Routing | 174
8
Infrastructure | 176
Interfaces and Chassis | 176
Routing Protocols | 176
Resolved Issues | 176
General Routing | 177
Infrastructure | 178
Interfaces and Chassis | 179
Layer 2 Ethernet Services | 179
MPLS | 179
Routing Protocols | 179
VPNs | 179
Documentation Updates | 180
Migration, Upgrade, and Downgrade Instructions | 180
Basic Procedure for Upgrading to Release 19.3 | 181
Upgrade and Downgrade Support Policy for Junos OS Releases | 183
Upgrading a Router with Redundant Routing Engines | 184
Junos OS Release Notes for the QFX Series | 185
What's New | 185
Hardware | 186
EVPN | 186
Forwarding and Sampling | 187
Interfaces and Chassis | 188
Junos OS XML, API, and Scripting | 189
Junos Telemetry Interface | 190
Management | 190
Multicast | 191
Routing Protocols | 191
Routing Protocols and Firewall Filters | 192
Services Applications | 192
Software Installation and Upgrade | 192
Virtual Chassis | 194
What's Changed | 195
Interfaces and Chassis | 195
Junos OS XML, API, and Scripting | 197
9
Layer 2 Features | 197
Software Defined Networking | 197
System Logging | 197
Known Limitations | 198
Class of Service (CoS) | 199
EVPN | 199
General Routing | 199
Infrastructure | 200
Layer 2 Features | 200
Routing Protocols | 200
Open Issues | 201
General Routing | 201
High Availability (HA) and Resiliency | 204
Infrastructure | 204
Interfaces and Chassis | 204
Layer 2 Features | 204
MPLS | 205
Platform and Infrastructure | 205
Routing Protocols | 205
Resolved Issues | 206
Class of Service (CoS) | 206
EVPN | 206
General Routing | 207
Interfaces and Chassis | 212
Layer 2 Ethernet Services | 212
Layer 2 Features | 212
MPLS | 212
Routing Protocols | 213
User Interface and Configuration | 214
Documentation Updates | 214
Migration, Upgrade, and Downgrade Instructions | 214
Upgrading Software on QFX Series Switches | 215
Installing the Software on QFX10002-60C Switches | 217
10
Installing the Software on QFX10002 Switches | 217
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 | 218
Installing the Software on QFX10008 and QFX10016 Switches | 220
Performing a Unified ISSU | 224
Preparing the Switch for Software Installation | 225
Upgrading the Software Using Unified ISSU | 225
Upgrade and Downgrade Support Policy for Junos OS Releases | 227
Junos OS Release Notes for SRX Series | 228
What’s New | 229
Application Security | 229
Chassis Clustering | 231
Flow-Based and Packet-Based Processing | 231
General Packet Radio Switching (GPRS) | 231
Hardware | 231
J-Web | 232
Logical Systems and Tenant Systems | 233
Network Address Translation (NAT) | 234
Network Management and Monitoring | 234
Platform and Infrastructure | 234
Routing Protocols | 235
Security | 235
Juniper Sky ATP | 236
Subscriber Management and Services | 237
Virtual Routing | 237
What's Changed | 238
Application Security | 238
Authentication and Access Control | 239
Junos OS XML API and Scripting | 239
J-Web | 239
Licensing | 239
Network Management and Monitoring | 239
System Logging | 240
Unified Threat Management (UTM) | 240
11
VPN | 240
Known Limitations | 241
J-Web | 241
Logical Systems and Tenant Systems | 241
VPNs | 241
Open Issues | 242
Application Security | 242
J-Web | 242
Platform and Infrastructure | 243
Routing Policy and Firewall Filters | 243
VPNs | 243
Resolved Issues | 244
Application Layer Gateways (ALGs) | 244
Application Security | 244
Authentication and Access Control | 245
Chassis Clustering | 245
Class of Service (CoS) | 245
Flow-Based and Packet-Based Processing | 245
Infrastructure | 247
Interfaces and Routing | 247
Installation and Upgrade | 247
Interfaces and Chassis | 247
Intrusion Detection and Prevention (IDP) | 248
J-Web | 248
Network Address Translation (NAT) | 248
Network Management and Monitoring | 248
Platform and Infrastructure | 249
Routing Policy and Firewall Filters | 250
Unified Threat Management (UTM) | 250
User Interface and Configuration | 251
VPNs | 251
Documentation Updates | 252
Migration, Upgrade, and Downgrade Instructions | 253
Upgrade and DowngradeSupport Policy for Junos OS Releases and Extended End-Of-Life
Releases | 253
12
Upgrading Using ISSU | 254
Licensing | 254
Finding More Information | 255
Documentation Feedback | 255
Requesting Technical Support | 256
Self-Help Online Tools and Resources | 256
Opening a Case with JTAC | 257
Revision History | 257
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.3R1 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
13
What's New | 14
What's Changed | 21
Known Limitations | 23
Open Issues | 25
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
These release notes accompany Junos OS Release 19.3R1 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 19.3R1-S1 | 14
What’s New in 19.3R1 | 15
Learn about new features introduced in this release for ACX Series routers.
What’s New in 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:
14
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 19.3R1
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.
15
[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:
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.
16
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
•
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.]
17
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.
[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.]
18
•
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:
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
RE-S-1600x8MX204
RE-S-1600x8MX10003
RE-MX2008-X8-64GMX2008
19
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
Routing Engine SupportedPlatforms
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 beforeinstalling this package
ERROR: Aborting the installation
20
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. ]
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 | 21
Known Limitations | 23
Open Issues | 25
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
What's Changed
IN THIS SECTION
General Routing | 22
Junos OS XML API and Scripting | 22
Interfaces and Chassis | 22
System Logging | 23
Operation, Administration, and Maintenance (OAM) | 23
21
See what changed in this release for ACX Series routers.
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.
[See gigether-options.]
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.
22
Interfaces and Chassis
Support for creating Layer 2 logical interfaces independently (ACXSeries)—In Junos OS Release 19.3R1
•
and later, ACX Series switches 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 EVPN routing instance separately. Note that the Layer
2 logical interfaces work fine when they are added to the bridge domain or EVPN routing instance.
In the earlier Junos OS releases, when a Layer 2 logical interface configuration (units with encapsulation
vlan-bridge configuration) is used, 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.
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)
Performance monitoring history data is lost when change in number of supported history records is
•
detected (ACX Series)—In Junos OS Release 19.3R1, when Ethernet Connectivity Fault Management
(ECFM) 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 19.3R1, then the existing Performance Monitoring history database is cleared and all performance
monitoring sessions are restarted with mi-index 1.
23
SEE ALSO
What's New | 14
Known Limitations | 23
Open Issues | 25
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
Known Limitations
IN THIS SECTION
General Routing | 24
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
For an et-interface, only PRE_FEC_SD defect is raised, and no OTN alarm is raised. PR1371997
•
clock-class to QL level mapping needs to be changed via CLI in Arb GM with network option-1 PR1384968
•
When a timing configuration and the corresponding interface configuration are 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 gets into inconsistency state, where the lookup is failing. PR1410746
Hardware-based fragmentation or reassembly is not supported. Software-based fragmentation rates
•
are going to be extremely slow depending on CPU load. PR1419371
This is the expected behaviour across all ACX Series platforms. The input packets account for all the
•
frames that are coming in, including the oversized frames, whereas the oversized frame counter only
accounts for oversized frames. PR1425748
24
These error messages can be seen sometimes if the optics is being unplugged during the EEPROM read.
•
This is expected and does not impact any functionality. PR1429016
Packet rates are not seen for aggregated Ethernet logical interface. PR1429590
•
Multicast packets are flooded in a BD if snooping is not enabled. If interfaces x and y belongs to a BD,
•
then all multicast packets will be flooded to both x and y interfaces. If packets are received from interface
x, packets will be flooded to x and y at ingress but discarded in the egress path for interface x because
packet is received from the same interface. But these packets are also counted in the VOQ and hence
we are seeing more queue statistics. It is a known Hardware limitation. monitor interface xe-0/0/30
Input packets: 177958 (64 pps) [0] Output packets: 357306 (128 pps) [0] monitor interface xe-0/0/12
Input packets: 361161 (128 pps) [642] Output packets: 179878 (63 pps) [320] user@router> show
interfaces queue xe-0/0/30 Queue: 0, Forwarding classes: best-effort Queued: Packets : 544032 192
pps . => Sum of 64 + 128pps user@router> show interfaces queue xe-0/0/12 Queue: 0, Forwarding
classes: best-effort Queued: Packets : 550929 192 pps . => Sum of 64 + 128pps. PR1429628
Any packet with size greater than the MTU size are accounted for as oversized packets. Packets exceeding
•
MTU sizes are not considered for Jabber check. PR1429923
The statistics are accessed through Broadcom API, which is the same for both tagged and untagged
•
packets. This cannot be changed in accordance with MX since it is direct access from Broadcom without
any statistics changes specific to tagging from ACX5448 side. It will impact other statistics if the change
is made. PR1430108
The port LEDs glowing during system/vmhost halt state is the expected behaviour across all ACX Series
•
platforms. Even the system LED glows during halt state. PR1430129
Packets dropped due to MTU checks in the output interface are not accounted for as MTU errors. All
•
packets with sizes greater than the MTU size are accounted for as Oversized-packets in the input
interface. PR1430446
If Layer 2 VPN sessions have OAM control-channel option set to router-alert-label, the no-control-word
•
option in Layer 2 VPN shouldn't be used for BFD sessions to come up. PR1432854
With an asymmetric network connection, EX: a 10-Gbps MACsec port connected to a 10-Gbps
•
channelized port, high and asymmetric T1 and T4 time errors are seen. This situation introduces a high
two-way time error and also different CF updates in forward and reverse paths. PR1440140
By default, the management interface speed is always displayed as 1000 Mbps in Junos OS command
•
output. PR1440675
With the MACsec feature enabled and introduction of traffic, the peak-to-peak value varies with the
•
percentage of traffic introduced. Please find the max and mean values of the Time errors with different
traffic rates(two router scenario). Can have max value jumps as high as 1054ns with 95% traffic, 640ns
for 90% traffic and 137ns with no traffic. PR1441388
Synchronous Ethernet jitter tolerance test fails for MACsec ports. For Synchronous Ethernet and MACsec,
•
there seems to be additional framing header and footer that would get added by the MACsec protocol.
The impact on the jitter test is not obvious and appears undefined in the standards and not qualifiable
with a single DUT and Calnex. PR1447296
25
SEE ALSO
What's New | 14
What's Changed | 21
Open Issues | 25
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
Open Issues
IN THIS SECTION
General Routing | 26
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
The switchover time observed was more than 50ms under certain soak test conditions with an increased
•
scale with a multi-protocol multi-router topology. PR1387858
The optic comes with Tx enabled by default. As the port is administratively disabled, the port is stopped
•
but as the port has not been started, it does not disable Tx. PR1411015
FEC NONE should be configured through cli in case of speed 40G with SR optics combination for
•
ACX5448 to interop with other platforms. PR1414649
Clock Class value is wrong in Default Data (show ptp clock) when the slave interface is down in PTP-OC
•
device. PR1416421
With ACX5448 platform devices, the ztp process will proceed with image upgrade even in situations
•
when there is a mismatch in platform name of the software image stored on ftp/ztp servers and actual
platform where the ztp process is being run. PR1418313
26
On ethernet bridge, L2 filters may not work as expected when trying to match vlan based fields for
•
untagged packets. PR1423214
DHCP clients are not able to scale to 96K PR1432849
•
With scaled interface config, delete/add or deactivate/activate interface take time. This is due to the
•
reason that we need to clear mac-entries associated with L2 ifl's and the BCM api's for that are time
consuming. PR1433426
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. So it will be fixed in DCB first. Our
target is to fix this in 19.4DCB. PR1435648
On ACX5448 box, after issuing deactivate/activate "class-of-service", traffic drop might be seen.
•
PR1436494
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(i.e 5-10% 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 not plugged in. PR1438039
•
Memory leaks are expected in this release. PR1438358
•
When the interface is flapped between channelized configurations (25G to 100 G), the parent AE interface
•
configuration is not cleaned up properly. It leads to fail the traffic in that interface. The issue is happening
with channelized interfaces with ae and the issue dependent on delete sequence. Only channelized
interface deletion doesn't reproduce the issue, both the interface and chassis deletion is creating the
issue. PR1441374
In ACX, auto exported route between VRFs might not reply for icmp echo requests. PR1446043
•
Recovery of JUNOS volume isn't possible from OAM menu. PR1446512
•
Drop profile max threshold may not be reached to its limit when the packet size is other than 1000
•
bytes. PR1448418
When a XE interface working in 1G mode in ACX5448-D, is added to a member link of an AE interface,
•
the speed of AE is wrongly shown as 10G. There is no functional impact. This is a display issue.PR1449887
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 isn't seen in normal operation but seen when interfaces are
deleted and re-created and configs are applied. PR1449937
Red Drops seen on the 25G Channelized AE Interfaces after some events (Deactivate, activate etc) on
•
the PEER box. PR1450674
Fan numbering is not the same in the two outputs: show chassis fan and show snmp mib walk
•
jnxContentsDescr. PR1456589
27
Route resolve resolution is not happening when the packet size is 10000. PR1458744
•
ACX5448 Macsec SKU Problem : On Enabling local Loopback on 10G interface, the link doesn't come
•
up. On 1G and 100G, link comes UP fine after local loopback is enabled. WorkAround : Disable/Enable
of the interface makes the link UP when local loopback is enabled. PR1460715
Arp issue is seen with aggregated Ethernet when one member of aggregated Ethernet is removed and
•
also when device is rebooted with aggregated Ethernet configuration. PR1461485
SEE ALSO
What's New | 14
What's Changed | 21
Known Limitations | 23
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 31
Resolved Issues
IN THIS SECTION
Resolved Issues: 19.3R1 | 28
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.3R1
Class of Service
28
When the forwarding-class is configured under firewall policer, the dfwd might crash. PR1436894
•
General Routing
On QFX10k Series platforms (QFX10002, QFX10008, QFX10016), the 1G copper module interface on
•
10G line card (QFX10000-60S-6Q) incorrectly displays with 'Link-mode: Half-duplex'. PR1286709
Upon classifying the L3 packets, DSCP will not be preserved or lost at the egress due to the limittations
•
of broadcom chipset. PR1322142
START_BY_START_ERR interrupt handler was not available with the previous version of bcm sdk code.
•
This lead to the status checking of this flag continously by bcmDPC process leading to high CPU utilization.
This has been fixed in this release by adding a handler for this interrupt. PR1329656
On ACX5000 platforms with Junos 16.2 onwards, if the ECC Errors occur, the FPC/fxpc process might
•
use high CPU. This issue can be hit after the upgrade in some cases. PR1360452
As part of the pic_periodic, before setting the port to master/slave mode, AN bit is checked if AN is
•
complete and this would return if AN is still in progress. Since An was disabled, this port wasn't set to
either mode and this was going on in a loop causing the CPU to go high. PR1360844
On ACX1x00/ACX2x00/ACX4x00 running in 15-releases previous to 15.1R8, when configuring
•
"mac-table-size" under bridge-domain, a wrong commit error appear not allowing the commit to pass.
PR1364811
ACX led on GE interface goes down when speed 10M is added. PR1385855
•
Link Fault Signaling (LFS) feature is not supported on ACX5448 10/40/100GbE interfaces. PR1401718
•
If user configures invalid speed config on TIC ports (PIC slot 1) on ACX6360-OR/OX, TIC interfaces are
•
not created. regress@tron# show chassis fpc 0 { pic 1 { port 0 { speed 40g; } } } PR1403546
Loading...