Junos OS 19.4R1 User Manual

Download

Release

Published

2021-04-22

Notes

Junos®OS 19.4R1 Release Notes

SUPPORTED ON

ACX Series, EX Series, JRR Series, Junos Fusion Enterprise, Junos Fusion Provider Edge,

•

MX Series, NFX Series, PTX Series, QFX Series, and SRX Series

HARDWARE HIGHLIGHTS

Wi-Fi Mini-Physical Interface Module (SRX320, SRX340, SRX345, and SRX550M)

•

SOFTWARE HIGHLIGHTS

Support for EVPN routing policies (ACX5448)

•

Inline monitoring services (MX Series with MPCs excluding MPC10E linecards)

•

Support for BGP PIC Edge with BGP labeled unicast (MX Series and PTX Series)

•

Integrating RIFT protocol into Junos OS (MX Series and VMX virtual routers)

•

Support for flexible algorithm in IS-IS for segment routing–traffic engineering (MX Series

•

and PTX Series)

Junos Multi-Access User Plane (MX240, MX480, MX960)

•

Support for Lawful Intercept on Junos Multi-Access User Plane (MX240, MX480, MX960)

•

Precision Time Protocol (PTP) transparent clock (QFX5120 and QFX5210)

•

Additional support for Bidirectional Forwarding Detection (QFX5110, QFX5120, QFX5200,

•

and QFX5210)

Selectively disable midstream APBR (SRX Series and vSRX)

•

Improved query performance in on-box reporting (SRX300, SRX320, SRX340, SRX345,

•

SRX550M, SRX1500, SRX4100, SRX4200, SRX4600, and vSRX)

UTM Support for Active/Active Chassis Cluster (SRX Series)

•

IN FOCUS GUIDE

Use this new guide to quickly learn about the most important Junos OS features and how

•

you can deploy them in your network.

Release Notes: Junos®OS Release 19.4R1 for

the ACX Series, EX Series, MX Series, NFX

Series, PTX Series, QFX Series, SRX Series, JRR

Series, and Junos Fusion

22 April 2021

Introduction | 14

Junos OS Release Notes for ACX Series | 14

What's New | 15

EVPN | 15

Junos OS XML API and Scripting | 16

MPLS | 18

OAM | 18

Routing Protocols | 18

System Logging | 19

Software Defined Networking (SDN) | 19

What's Changed | 20

General Routing | 20

Routing Protocols | 20

Known Limitations | 21

General Routing | 21

Open Issues | 22

General Routing | 22

Resolved Issues | 23

General Routing | 24

Layer 2 Ethernet Services | 26

Platform and Infrastructure | 26

Routing Protocols | 26

Documentation Updates | 26

Feature Guides Are Renamed As User Guides | 27

Migration, Upgrade, and Downgrade Instructions | 27

Upgrade and Downgrade Support Policy for Junos OS Releases | 27

Junos OS Release Notes for EX Series Switches | 28

What's New | 29

Authentication, Authorization, and Accounting | 30

Class of Service | 30

EVPN | 30

Junos OS XML, API, and Scripting | 32

Junos Telemetry Interface | 33

Layer 2 Features | 34

MPLS | 36

Multicast | 36

Operation, Administration, and Maintenance (OAM) | 36

Port Security | 37

Routing Policy and Firewall Filters | 38

System Logging | 38

System Management | 38

User Interface and Configuration | 39

What's Changed | 39

What’s Changed in Release 19.4R1-S3 | 40

What's Changed in Release 19.4R1 | 40

Known Limitations | 41

Open Issues | 42

Authentication and Access Control | 43

Class of Service (CoS) | 43

EVPN | 43

General Routing | 43

Infrastructure | 45

Interfaces and Chassis | 45

Junos Fusion Enterprise | 45

Junos Fusion Satellite Software | 45

Layer 2 Ethernet Services | 45

Layer 2 Features | 46

Platform and Infrastructure | 46

Routing Protocols | 46

User Interface and Configuration | 47

Resolved Issues | 47

Authentication and Access Control | 48

EVPN | 48

General Routing | 48

Infrastructure | 50

Interfaces and Chassis | 51

Junos Fusion Enterprise | 51

Junos Fusion Satellite Software | 51

J-Web | 51

Layer 2 Ethernet Services | 51

Layer 2 Features | 51

Platform and Infrastructure | 52

Routing Protocols | 52

User Interface and Configuration | 53

Virtual Chassis | 53

Documentation Updates | 53

Feature Guides Are Renamed As User Guides | 54

Migration, Upgrade, and Downgrade Instructions | 54

Upgrade and Downgrade Support Policy for Junos OS Releases | 54

Junos OS Release Notes for JRR Series | 55

What's New | 56

Hardware | 56

What's Changed | 57

Known Limitations | 57

Open Issues | 58

General Routing | 58

Resolved Issues | 58

Documentation Updates | 59

Feature Guides Are Renamed As User Guides | 59

Migration, Upgrade, and Downgrade Instructions | 60

Upgrade and Downgrade Support Policy for Junos OS Releases | 60

Junos OS Release Notes for Junos Fusion Enterprise | 61

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Junos Fusion for Enterprise | 63

Resolved Issues | 64

Documentation Updates | 64

Feature Guides Are Renamed As User Guides | 65

Migration, Upgrade, and Downgrade Instructions | 65

Basic Procedure for Upgrading Junos OS on an Aggregation Device | 66

Upgrading an Aggregation Device with Redundant Routing Engines | 67

Preparing the Switch for Satellite Device Conversion | 68

Converting a Satellite Device to a Standalone Switch | 69

Upgrade and Downgrade Support Policy for Junos OS Releases | 69

Downgrading from Junos OS | 70

Junos OS Release Notes for Junos Fusion Provider Edge | 71

What's New | 71

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Junos Fusion for Provider Edge | 73

Resolved Issues | 73

Documentation Updates | 74

Feature Guides Are Renamed As User Guides | 74

Migration, Upgrade, and Downgrade Instructions | 75

Basic Procedure for Upgrading an Aggregation Device | 75

Upgrading an Aggregation Device with Redundant Routing Engines | 78

Preparing the Switch for Satellite Device Conversion | 78

Converting a Satellite Device to a Standalone Device | 80

Upgrading an Aggregation Device | 82

Upgrade and Downgrade Support Policy for Junos OS Releases | 82

Downgrading from Junos OS Release 19.4 | 83

Junos OS Release Notes for MX Series 5G Universal Routing Platform | 83

What's New | 84

Hardware | 85

Class of Service | 88

EVPN | 88

Forwarding and Sampling | 89

General Routing | 90

High Availability (HA) and Resiliency | 90

Interfaces and Chassis | 90

Junos OS, XML, API, and Scripting | 93

Junos Telemetry Interface | 94

Layer 2 Features | 96

Layer 2 VPN | 96

MPLS | 96

Multicast | 97

Network Management and Monitoring | 98

OAM | 98

Routing Policy and Firewall Filters | 98

Routing Protocols | 99

Services Applications | 102

Software-Defined Networking | 102

Software Licensing | 103

Subscriber Management and Services | 103

System Logging | 104

What's Changed | 105

General Routing | 105

Interfaces and Chassis | 106

MPLS | 107

Network Management and Monitoring | 107

Routing Protocols | 107

Services Applications | 107

Software-Defined Networking | 107

Subscriber Management and Services | 108

Known Limitations | 109

General Routing | 109

Interfaces and Chassis | 110

MPLS | 111

Platform and Infrastructure | 111

Routing Protocols | 111

Open Issues | 112

Application Layer Gateways | 113

Class of Service | 113

EVPN | 113

Forwarding and Sampling | 113

General Routing | 114

Infrastructure | 122

Interfaces and Chassis | 122

Layer 2 Features | 123

Layer 2 Ethernet Services | 123

MPLS | 124

Network Management and Monitoring | 124

Next Gen Services MX-SPC3 Services Card | 124

Platform and Infrastructure | 125

Routing Protocols | 126

Services Applications | 127

Subscriber Access Management | 128

VPNs | 128

Resolved Issues | 129

Resolved Issues: 19.4R1 | 129

Documentation Updates | 150

Feature Guides Are Renamed As User Guides | 150

Migration, Upgrade, and Downgrade Instructions | 151

Basic Procedure for Upgrading to Release 19.4 | 152

Procedure to Upgrade to FreeBSD 11.x based Junos OS | 152

Procedure to Upgrade to FreeBSD 6.x based Junos OS | 155

Upgrade and Downgrade Support Policy for Junos OS Releases | 156

Upgrading a Router with Redundant Routing Engines | 157

Downgrading from Release 19.4 | 157

Junos OS Release Notes for NFX Series | 158

What’s New | 158

General routing | 159

Hardware | 159

Architecture | 159

What's Changed | 160

Known Limitations | 161

Interfaces | 161

Platform and Infrastructure | 161

Open Issues | 162

Mapping of Address and Port with Encapsulation (MAP-E) | 162

Interfaces | 162

Platform and Infrastructure | 163

Virtual Network Functions (VNFs) | 164

Resolved Issues | 164

Class of Service | 165

High Availability | 165

Interfaces | 165

Layer 2 Ethernet Services | 166

Platform and Infrastructure | 166

Routing Protocols | 167

SNMP | 167

Virtual Network Functions (VNFs) | 167

Documentation Updates | 168

Feature Guides Are Renamed As User Guides | 168

Migration, Upgrade, and Downgrade Instructions | 169

Upgrade and Downgrade Support Policy for Junos OS Releases | 169

Basic Procedure for Upgrading to Release 19.4 | 169

Junos OS Release Notes for PTX Series Packet Transport Routers | 171

What's New | 172

General Routing | 173

Hardware | 173

High Availability (HA) and Resiliency | 173

Junos OS, XML, API, and Scripting | 173

Junos Telemetry Interface | 174

MPLS | 176

Routing Protocols | 177

Services Applications | 178

Software Defined Networking | 179

System Logging | 179

What's Changed | 180

General Routing | 180

Interfaces and Chassis | 180

Routing Protocols | 181

Software-Defined Networking | 181

Known Limitations | 181

General Routing | 182

Open Issues | 183

General Routing | 183

Infrastructure | 185

Layer 2 Ethernet Services | 185

MPLS | 185

Routing Protocols | 185

Resolved Issues | 186

Forwarding and Sampling | 186

General Routing | 186

Infrastructure | 188

Interfaces and Chassis | 188

Layer 2 Ethernet Services | 188

MPLS | 188

Platform and Infrastructure | 188

Routing Protocols | 188

VPNs | 189

Documentation Updates | 189

Feature Guides Are Renamed as User Guides | 190

Migration, Upgrade, and Downgrade Instructions | 190

Basic Procedure for Upgrading to Release 19.4 | 190

Upgrade and Downgrade Support Policy for Junos OS Releases | 193

Upgrading a Router with Redundant Routing Engines | 194

Junos OS Release Notes for the QFX Series | 195

What's New | 195

EVPN | 196

General Routing | 200

Interfaces and Chassis | 200

Junos OS XML API and Scripting | 201

Junos Telemetry Interface | 202

Layer 2 Features | 202

MPLS | 203

Routing Protocols | 203

Software Defined Networking (SDN) | 203

System Logging | 204

System Management | 205

VLAN Infrastructure | 206

What's Changed | 206

General Routing | 208

Interfaces and Chassis | 208

Management | 208

Routing Protocols | 208

Software Defined Networking (SDN) | 208

Known Limitations | 209

Layer 2 Ethernet Services | 210

Layer 2 Features | 210

Network Management and Monitoring | 210

Platform and Infrastructure | 210

Routing Protocols | 211

Open Issues | 211

Class of Service (CoS) | 212

EVPN | 212

High Availability (HA) and Resiliency | 213

Interfaces and Chassis | 213

Junos Fusion for Provider Edge | 213

Layer 2 Features | 213

Layer 2 Ethernet Services | 214

MPLS | 214

Platform and Infrastructure | 214

Routing Protocols | 217

Resolved Issues | 218

Class of Service (CoS) | 218

EVPN | 219

Forwarding and Sampling | 219

Interfaces and Chassis | 219

Layer 2 Features | 219

MPLS | 220

Platform and Infrastructure | 220

Routing Protocols | 224

User Interface and Configuration | 225

Documentation Updates | 226

Feature Guides Are Renamed As User Guides | 226

Migration, Upgrade, and Downgrade Instructions | 226

Upgrading Software on QFX Series Switches | 227

Installing the Software on QFX10002-60C Switches | 229

Installing the Software on QFX10002 Switches | 229

Upgrading Software from Junos OS Release 15.1X53-D3X to Junos OS Release

15.1X53-D60, 15.1X53-D61.7, 15.1X53-D62, and 15.1X53-D63 on QFX10008 and QFX10016 Switches | 230

Installing the Software on QFX10008 and QFX10016 Switches | 232

Performing a Unified ISSU | 236

Preparing the Switch for Software Installation | 237

Upgrading the Software Using Unified ISSU | 237

Upgrade and Downgrade Support Policy for Junos OS Releases | 239

Junos OS Release Notes for SRX Series | 240

What’s New | 241

Application Security | 241

Chassis Clustering | 242

Flow-Based and Packet-Based Processing | 242

General Packet Radio Switching (GPRS) | 243

Hardware | 243

Interfaces and Chassis | 244

Intrusion Detection and Prevention (IDP) | 244

Junos OS XML API and Scripting | 245

J-Web | 246

Logical Systems and Tenant Systems | 246

Network Management and Monitoring | 247

System Logging | 248

Unified Threat Management (UTM) | 248

VPNs | 248

What's Changed | 249

Application Security | 250

Authentication and Access Control | 253

General Routing | 253

J-Web | 253

Network Management and Monitoring | 253

Port Security | 254

Routing Protocols | 254

VPNs | 254

Known Limitations | 255

Application Layer Gateways (ALGs) | 255

Ethernet Switching | 255

Flow-Based and Packet-Based Processing | 255

J-Web | 255

Open Issues | 256

ALG | 257

Flow-Based and Packet-Based Processing | 257

IDP | 257

J-Web | 257

Platform and Infrastructure | 257

Routing Policy and Firewall Filters | 257

VPNs | 258

Resolved Issues | 259

Application Layer Gateways | 259

Application Security | 259

Authentication and Access Control | 259

Chassis Clustering | 259

Class of Service | 260

Flow-Based and Packet-Based Processing | 260

Interfaces and Chassis | 262

Intrusion Detection and Prevention (IDP) | 262

J-Web | 262

Layer 2 Ethernet Services | 263

Network Address Translation | 263

Network Management and Monitoring | 263

Platform and Infrastructure | 263

Routing Policy and Firewall Filters | 264

Services Applications | 264

Unified Threat Management | 264

VLAN Infrastructure | 265

VPNs | 265

Documentation Updates | 266

Feature Guides Are Renamed As User Guides | 267

Migration, Upgrade, and Downgrade Instructions | 267

Upgrade and Downgrade Support Policy for Junos OS Releases and Extended End-Of-Life

Releases | 267

Upgrading Using ISSU | 268

Licensing | 269

Compliance Advisor | 269

Finding More Information | 269

Documentation Feedback | 270

Requesting Technical Support | 271

Self-Help Online Tools and Resources | 271

Creating a Service Request with JTAC | 272

Revision History | 272

Introduction

Junos OS runs on the following Juniper Networks®hardware: ACX Series, EX Series, M Series, MX Series,

NFX Series, PTX Series, QFabric systems, QFX Series, SRX Series, T Series, JRR Series, and Junos Fusion.

These release notes accompany Junos OS Release 19.4R1 for the ACX Series, EX Series, MX Series, NFX Series, PTX Series, QFX Series, SRX Series, JRR Series, and Junos Fusion. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

Feature Guides Are Renamed As User Guides—Starting with Junos OS 19.4R1, we renamed our Feature

•

Guides to User Guides to better reflect the purpose of the guides. For example, the BGP Feature Guide is now the BGP User Guide. We didn’t change the URLs of the guides, so any existing bookmarks you have will continue to work. To keep the terminology consistent on our documentation product pages, we renamed the Feature Guides section to User Guides. To find documentation for your specific product, check out this link.

New In Focus Guide—Starting on Junos Release 19.4R1, we are introducing a new document called In

•

Focus that provides details on the most important features for the release in one place. We hope this document will quickly get you to the latest information about Junos features. Let us know if you find this information useful by sending email to techpubs-comments@juniper.net.

Important Information:

•

Upgrading Using ISSU on page 268

•

Licensing on page 269

•

Compliance Advisor on page 269

•

Finding More Information on page 269

•

Documentation Feedback on page 270

•

Requesting Technical Support on page 271

•

Junos OS Release Notes for ACX Series

IN THIS SECTION

What's New | 15

What's Changed | 20

Known Limitations | 21

Open Issues | 22

Resolved Issues | 23

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

These release notes accompany Junos OS Release 19.4R1 for the ACX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

What's New

IN THIS SECTION

EVPN | 15

Junos OS XML API and Scripting | 16

MPLS | 18

OAM | 18

Routing Protocols | 18

System Logging | 19

Software Defined Networking (SDN) | 19

Learn about new features introduced in the Junos OS main and maintenance releases for ACX Series routers.

EVPN

SPRING support for EVPN (ACX5448)—Starting in Junos OS Release 19.4R1, you can use Source Packet

•

Routing in Networking (SPRING) as the underlay transport in EVPN on ACX5448 routers. SPRING tunnels enable routers to steer a packet through a specific set of nodes and links in the network.

To configure SPRING, use the source-packet-routing statement at the [edit protocols isis] hierarchy level.

[See Understanding Source Packet Routing in Networking (SPRING).]

Support for EVPN features on new hardware (ACX5448)—Starting with Release 19.4R1, Junos OS

•

supports the following EVPN features:

EVPN E-TREE. [See EVPN E-TREE Overview.]

•

ARP/NDP proxy and suppression with proxy MAC responses. [See EVPN Proxy ARP and ARP

•

Suppression, and Proxy NDP and NDP Suppression.]

EVPN with segment routing (SPRING). [See Understanding Source Packet Routing in Networking

•

(SPRING).]

EVPN E-LAN services over MPLS, including support for VLAN-based and VLAN-bundles services. [See

•

EVPN Overview and Overview of VLAN Services for EVPN.]

EVPN multihoming active/active. [See EVPN Multihoming Overview.]

•

Support for EVPN routing policies (ACX5448, EX4600, EX4650, EX9200, MX Series, QFX Series, and

•

vMX)—Starting in Junos OS Release 19.4R1, Junos OS has expanded routing policy support to include the creation and application of policy filters specific to EVPN routes. You can create policies and apply policy filters to import and export EVPN routes at the routing-instance level or at the BGP level. Junos OS supports the following matching criteria for EVPN routes:

Route distinguisher ID

•

NLRI route type

•

EVPN Ethernet tag

•

BGP path attributes

•

Ethernet Segment Identifier

•

MAC Address on EVPN route type 2 routes

•

IP address on EVPN route type 2 and EVPN route type 5 routes

•

Extended community

•

[See Routing policies for EVPN.]

Junos OS XML API and Scripting

Automation script library upgrades (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX

•

Series)—Starting in Junos OS Release 19.4R1, devices running Junos OS that support the Python extensions package include upgraded Python modules. Python scripts can leverage the upgraded versions of the following modules:

idna (2.8)

•

jinja2 (2.10.1)

•

jnpr.junos (Junos PyEZ) (2.2.0)

•

lxml (4.3.3)

•

markupsafe (1.1.1)

•

ncclient (0.6.4)

•

packaging (19.0)

•

paho.mqtt (1.4.0)

•

pyasn1 (0.4.5)

•

yaml (PyYAML package) (5.1)

•

[See Overview of Python Modules Available on Devices Running Junos OS.]

Python 3 support for commit, event, op, and SNMP scripts (ACX Series, EX Series, MX Series, PTX

•

Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, you can use Python 3 to execute commit, event, op, and SNMP scripts on devices running Junos OS. To use Python 3, configure the language python3 statement at the [edit system scripts] hierarchy level. When you configure the language python3 statement, the device uses Python 3 to execute scripts that support this Python version and uses Python 2.7 to execute scripts that do not support Python 3 in the given release.

The Python 2.7 end-of-support date is January 1, 2020, and Python 2.7 will be EOL in 2020. The official upgrade path for Python 2.7 is to Python 3. As support for Python 3 is added to devices running Junos OS for the different types of onbox scripts, we recommend that you migrate supported script types from Python 2 to Python 3, because support for Python 2.7 might be removed from devices running Junos OS in the future.

[See Understanding Python Automation Scripts for Devices Running Junos OS.]

MPLS

Support for Topology Independent Loop-Free Alternate, advertising MPLS labels, and configuring SRGB

•

for SPRING for ISIS and OSPF (ACX5448-D and ACX5448-M)—Starting with Junos OS Release 19.4R1, ACX5448-D and ACX5448-M router supports topology independent (TI)-loop-free alternate (LFA), advertise MPLS labels (ISIS, OSPF), and segment routing global block (SRGB) for SPRING (ISIS, OSPF).

[See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS,

Understanding Source Packet Routing in Networking (SPRING).]

OAM

Support for Ethernet OAM and Metro Ethernet services over segment routing (ACX5448-D, ACX5448-M,

•

MX Series)—Starting with Junos OS Release 19.4R1, ACX5448-D, ACX5448-M and MX Series routers support Ethernet OAM and Metro Ethernet services over segment routing.

[See Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING for IS-IS Protocol, Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS, Ethernet OAM Connectivity Fault Management .]

Routing Protocols

Support for configurable SRGB used by SPRING in OSPF protocols (ACX5448)— Starting in Junos OS

•

Release 19.4R1, you can configure the segment routing global block (SRGB) range label used by segment routing. Labels from this range are used for segment routing functionality in OSPF domain.

The SRGB is a range of the label values used in the segment routing. Prior to Junos OS Release 19.4R1, you could not configure the range for the SRGB block.

Locally you can configure srgb start-label <label-range> index-range <index-range> command under [edit protocols ospf source-packet-routing] hierarchy or globally under [edit protocols mpls label-range] hierarchy.

Following are the SRGB precedences for OSPF protocol:

Local SRGB

•

Global SRGB

•

Node-segment implementation of 256 label block

•

Unnumbered interface support for IS-IS and OSPFv2 with topology-independent loop-free alternate

•

(ACX Series, MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, you can enable IPv4 processing on a point-to-point interface without assigning it an explicit IPv4 address. The router borrows the IPv4 address of another Ethernet or loopback interface already configured on the router and assigns it to the unnumbered interface to conserve IPv4 addresses.

To enable IPv4 processing for unnumbered interfaces include unnumbered-address source at the [edit interfaces [name] unit [name] family inet] hierarchy level.

[See Configuring an Unnumbered Interface.]

System Logging

Improved intermodule communication between FFP and MGD (ACX Series, EX Series, MX Series, PTX

•

Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, intermodule communication is improved to enhance software debugging. To enhance error messages with more context, the exit conditions from libraries have been updated as follows:

Additional information is now logged for MGD-FFP intermodule communication.

•

Commit errors that previously were only shown onscreen are now logged.

•

We provide a new operational command, request debug information, to speed up the initial information-gathering phase of debugging.

[See request debug information.]

Software Defined Networking (SDN)

Tunnel templates for PCE-initiated segment routing LSPs (ACX Series)—Starting in Junos OS Release

•

19.4R1, you can configure a tunnel template for Path Computation Element (PCE)-initiated segment routing LSPs and apply it through policy configuration. These templates enable dynamic creation of segment routing tunnels with two additional parameters – Bidirectional forwarding detection (BFD) and LDP tunneling.

With the support for tunnel configuration, the LSPs that you would configure statically can now be automatically created from the PCE, thereby providing the benefit of reduced configuration on the device.

[See Understanding Static Segment Routing LSP in MPLS Networks.]

SEE ALSO

What's Changed | 20

Known Limitations | 21

Open Issues | 22

Resolved Issues | 23

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

What's Changed

IN THIS SECTION

General Routing | 20

Routing Protocols | 20

Learn about what changed in Junos OS main and maintenance releases for ACX Series.

General Routing

Support for full inheritance paths of configuration groups to be built into the database by default (ACX

•

Series, MX Series, PTX Series, and SRX Series)—Starting with Junos OS Release 19.4R1, the persist-groups-inheritance option at the [edit system commit] hierarchy level is enabled by default. To disable this option, use no-persist-groups-inheritance.

[See commit (System).]

Support for gigether-options statement (ACX5048, ACX5096)—Junos OS supports the gigether-options

•

statement at the edit interfaces interface-name hierarchy on the ACX5048 and ACX5096 routers. Previously, support for the gigether-statement was deprecated. See gigether-options and

Routing Protocols

XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX

•

Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release

19.4R1, we have included an XML RPC equivalent for the show bgp output-scheduler | display xml rpc CLI command. In Junos OS releases before Release 19.4R1, the show bgp output-scheduler | display xml rpc CLI command does not have an XML RPC equivalent.

[See show bgp output-scheduler.]

SEE ALSO

What's New | 15

Known Limitations | 21

Open Issues | 22

Resolved Issues | 23

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

Known Limitations

IN THIS SECTION

General Routing | 21

Learn about known limitations in Junos OS Release 19.4R1 for ACX Series routers. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem

Report Search application.

General Routing

ACX6360-OR Telemetry infrastructure does not support the interface-filtering capability. Therefore,

•

after you enable a particular sensor for telemetry, it is turned on for all the interfaces. PR1371996

When the timing configuration and the corresponding interface configuration is flapped for multiple

•

times in iteration, PTP is stuck in initialize state where the ARP for the neighbor is not resolved. In issue state, BCM hardware block get into inconsistency state, where the lookup is failing. PR1410746

The port LEDs and the system LED glow during system or vmhost halt state on all ACX Series devices.

•

PR1430129

With an asymmetric network connection (for example, 10G MACsec port connected to 10G channelized

•

port), high and asymmetric T1 and T4 time errors are seen, which introduces a high 2 way time error. This introduces different CF updates in forward and reverse paths. PR1440140

With MACsec feature enabled and introduction of traffic, the peak-to-peak value varies with the

•

percentage of traffic introduced. PR1441388

You cannot directly associate a policer in an IFL on ACX Series devices. It has to be achieved using

•

"filters" only. In this case, "family any" filter can be configured. Also, ACX5448 hardware ASIC does not support "egress policing". Egress shaping (H-QoS at the IFL level) can be used instead. PR1446376

ACX Series routers support rate of join of IGMPv3 users only around 900 joins per second. Same is

•

updated to PDD. PR1448146

SEE ALSO

What's New | 15

What's Changed | 20

Open Issues | 22

Resolved Issues | 23

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

Open Issues

IN THIS SECTION

General Routing | 22

Learn about open issues in Junos OS Release 19.4R1 for ACX Series routers. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report

Search application.

General Routing

High CPU usage for fxpc processes with class-of-service changes on aggregated Ethernet interfaces.

•

PR1407098

On ACX1000, ACX2000, ACX4000, ACX5048, and ACX5096 devices, after a new child logical interface

•

with VLAN and filter is added on an aggregated Ethernet physical interface or after changing the VLAN ID of a child logical interface with filter, traffic over the aggregated Ethernet physical interface might get filtered with that filter on the child logical interface. For example, ae-0/0/0 is a physical interface and ae-0/0/0.100 is a logical interface. PR1407855

Layer 2 rewrites happens on regular Bridge domain and VLAN interfaces. Though there are some service

•

dependencies, VPLS in this case, in which the Egress interface map table is not updated properly with the Layer 2 rewrite map id that causes rewrite to stop working. PR1414414

CoS table error can sometimes cause traffic outages and SNMP timeouts if the optic is removed and

•

inserted back. PR1418696

On the ACX5000 line of devices, high CPU usage might be seen for the fxpc process. PR1419761

•

The request system reboot command on the ACX5448 and ACX5448-D box triggers a reboot on the

•

host (Linux) instead of being limited to Junos OS. PR1426486

DHCP clients are not able to scale to 96000. PR1432849

•

The time consumed for 1-Gigabit performance is not equal to the time for 10-Gigabit performance.

•

Compensation is done to bring the mean value under class A, but the peak-to-peak variations are high and can go beyond 100ns. It has a latency variation with peak-to-peak variations of around 125ns-250ns without any traffic (for example, 5-10% of the mean latency introduced by each phy, which is around

2.5us). PR1437175

Memory leaks are expected. PR1438358

•

ACX can support rate of join of IGMPv3 users only around 900 joins per second. Same will be updated

•

to PDD. PR1448146

Drop profile maximum threshold might not reach its limit when the packet size is other than 1000 bytes.

•

This is due to the current design limitation. PR1448418

Not possible to form 125000 IGMP groups with ACX5448 receiving 125000 IGMP v2 Reports per

•

second. This is a product limitation from BCM and CPU host path queuing model. PR1454465

SEE ALSO

What's New | 15

What's Changed | 20

Known Limitations | 21

Resolved Issues | 23

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

Resolved Issues

IN THIS SECTION

General Routing | 24

Layer 2 Ethernet Services | 26

Platform and Infrastructure | 26

Routing Protocols | 26

Learn which issues were resolved in Junos OS Release 19.4R1 for ACX Series routers. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos

Problem Report Search application.

General Routing

On ACX5000 MacDrainTimeOut and bcm_port_update failed: Internal error error is seen. PR1284590

•

bcmDPC task is high even though Interuppt START_BY_START flag is set to 0. PR1329656

•

The AE interface with LACP stays down after the router reboots if link-speed is configured. PR1357012

•

On ACX Series devices, the LED on the GE interface goes down when speed 10M is added. PR1385855

•

Link Fault Signaling (LFS) doesn not work on ACX5448 10-, 40-, and 100-Gigabit Ethernet interfaces.

•

PR1401718

The optic comes with Tx enabled by default. Because the port is administratively disabled, the port is

•

stopped. However, because the port has not been started, it does not disable Tx. PR1411015

The ACX5448:40G FEC on ACX5448, which is FEC enabled by default, must be aligned with the MX

•

and QFX platforms, where FEC is NONE. PR1414649

On the ACX5448-X:SKU and ACX5448-D, 96000 ARPs get populated. However, only 47000 NH entries

•

are present. Around 50 percent of packet drop is observed. PR1426734

Chassisd might crash with unsupported hcos configuration when an MX104 is used as a fusion aggregation

•

device. PR1430076

The l2cpd process might crash and generate a core file when interfaces flaps. PR1431355

•

Deviation in traffic rate in the queue is around 8 % to 10% percent in some cases. PR1436297

•

1PPS performance metrics (class A) of G.8273.2 are not met for 1G interfaces because of the variable

•

latency added by the Vittesse PHY. PR1439231

The interface on ACX1100 devices remains down when using SFP-1FE-FX (740-021487). PR1439384

•

Transit DHCP packets are not punted to CPU and are transparently passthrough. PR1439518

•

When the interface is flapped between channelized configurations, 25-Gigabit Ethernet to 100-Gigabit

•

the aggregated Ethernet interface configuration is not cleaned up properly. PR1441374

In an ACX5448 platforms, when the PFE failed to allocate packet buffer, portion of packet memories

•

may not be freed. PR1442901

RED drops might be seen after link flaps or CoS configuration changes. PR1443466

•

ACX5448/18.3R1-S4.1 is not performing proper dot1p CoS rewrite on interfaces configured with

•

l2circuit/local-switching/family ccc. PR1445979

On ACX Series, the auto exported route between VRFs might not respond for icmp echo requests.

•

PR1446043

l2circuit with a backup-neighbor (hot-standby) configured might stop forwarding traffic after failovers.

•

PR1449681

oper-state for et interface does not transition from 'init' to 'Normal'. PR1449937

•

RMPC core files are found after configuration changes done on the network for PTP/Clock

•

Synchronization. PR1451950

After disabling 100G and 40G interface Laser output power in show interfaces diagnostics optics shows

•

some values. PR1452323

ACX5448 FPC crashed due to segmentation fault. PR1453766

•

Incorrect operating state is displayed in snmp trap for fan removal. PR1455577

•

Enable gigether option to configure Ethernet FEC on client ports. PR1456293

•

ACX5448-D and ACX5448-M Devices does not display airflow information and temperature sensors

•

as expected. PR1456593

ACX5448 Layer2 VPN with encapsulation-type ethernet stops passing traffic after a random port is

•

added with vlan configuration. PR1456624

The rpd crash might be seen if BGP route is resolved over same prefix protocol next-hop in inet.3 table

•

which has both RSVP and LDP routes. PR1458595

Route resolve resolution is not happening when the packet size is 10000. PR1458744

•

The traffic might be blackholed during link recovery in an open ethernet access ring with ERPS configured.

•

PR1459446

ACX5000: SNMP mib walk for jnxOperatingTemp not returning anything for FPC in new versions.

•

PR1460391

ACX5448-M Interfaces and Optics support: on enabling local loopback 10G interface is going down.

•

PR1460715

ACX5448-D Interfaces and Optics support: sometimes during the bring up of AE interface there are

•

ARP resolution issues. PR1461485

ACX Series routers LLDP neighbor not up on lag after software upgrade to Junos OS Release 18.2R3-S1.

•

PR1461831

RED drop on interface, no congestion. PR1470619

•

Layer 2 Ethernet Services

DHCP request might get dropped in DHCP relay scenario. PR1435039

•

Platform and Infrastructure

REST API process will get non-responsive when a number of request coming with a high rate. PR1449987

•

Routing Protocols

Loopback address are exported into other VRF instance might not work on EX/QFX/ACX platforms.

•

PR1449410

MPLS LDP might still use stale MAC of the neighbor even the LDP neighbor's MAC changes. PR1451217

•

The rpd might crash continuously due to memory corruption in an IS-IS setup. PR1455432

•

SEE ALSO

What's New | 15

What's Changed | 20

Known Limitations | 21

Open Issues | 22

Documentation Updates | 26

Migration, Upgrade, and Downgrade Instructions | 27

Documentation Updates

IN THIS SECTION

Feature Guides Are Renamed As User Guides | 27

This section lists the errata and changes in Junos OS Release 19.4R1 for the ACX Series documentation.

Feature Guides Are Renamed As User Guides

Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the

•

purpose of the guides. For example, the BGP Feature Guide is now the BGP User Guide. We didn’t change the URLs of the guides, so any existing bookmarks you have will continue to work. To keep the terminology consistent on our documentation product pages, we renamed the Feature Guides section to User Guides. To find documentation for your specific product, check out this link.

SEE ALSO

What's New | 15

What's Changed | 20

Known Limitations | 21

Open Issues | 22

Resolved Issues | 23

Migration, Upgrade, and Downgrade Instructions | 27

Migration, Upgrade, and Downgrade Instructions

IN THIS SECTION

Upgrade and Downgrade Support Policy for Junos OS Releases | 27

This section contains the upgrade and downgrade support policy for Junos OS for the ACX Series Router. Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration of the network.

For information about software installation and upgrade, see the Installation and Upgrade Guide.

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1,

17.2, and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3.

You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For information about software installation and upgrade, see the Installation and Upgrade Guide.

For more information about EEOL releases and to review a list of EEOL releases, see

https://support.juniper.net/support/eol/software/junosevo/.

SEE ALSO

What's New | 15

What's Changed | 20

Known Limitations | 21

Open Issues | 22

Resolved Issues | 23

Documentation Updates | 26

Junos OS Release Notes for EX Series Switches

IN THIS SECTION

What's New | 29

What's Changed | 39

Known Limitations | 41

Open Issues | 42

Resolved Issues | 47

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

These release notes accompany Junos OS Release 19.4R1 for the EX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

What's New

IN THIS SECTION

Authentication, Authorization, and Accounting | 30

Class of Service | 30

EVPN | 30

Junos OS XML, API, and Scripting | 32

Junos Telemetry Interface | 33

Layer 2 Features | 34

MPLS | 36

Multicast | 36

Operation, Administration, and Maintenance (OAM) | 36

Port Security | 37

Routing Policy and Firewall Filters | 38

System Logging | 38

System Management | 38

User Interface and Configuration | 39

Learn about new features introduced in the Junos OS main and maintenance releases for EX Series switches.

NOTE: The following EX Series switches are supported in Release 19.4R1: EX2300, EX2300-C,

EX3400, EX4300, EX4600-40F, EX4650, EX9200, EX9204, EX9208, EX9214, EX9251, and EX9253.

Authentication, Authorization, and Accounting

Disable LLDP TLV messages (EX4300-48MP switches)—Starting in Junos OS Release 19.4R1, you can

•

disable nonmandatory time, length, and value (TLV) messages so they will not be advertised by the Link Layer Discovery Protocol (LLDP) or Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED).

[See Device Discovery Using LLDP and LLDP-MED on Switches.]

Class of Service

Support for 802.1p rewrite of host outbound traffic (EX4300-MP)—Starting in Junos OS Release 19.4R1,

•

support is provided for 802.1p rewrite of host outbound traffic on EX4300-MP devices.

[See Applying Egress Interface Rewrite Rules to the IEEE 802.1p Field for All Host Outbound Traffic on

the Interface.]

EVPN

Support for EVPN routing policies (ACX5448, EX4600, EX4650, EX9200, MX Series, QFX Series, and

•

Route distinguisher ID

•

NLRI route type

•

EVPN Ethernet tag

•

BGP path attributes

•

Ethernet segment identifier

•

MAC address on EVPN Type 2 routes

•

IP address on EVPN Type 2 and EVPN Type 5 routes

•

Extended community

•

[See Routing policies for EVPN.]

Access security support in EVPN-VXLAN overlay networks (EX4300-48MP)—Starting in Junos OS

•

Release 19.4R1, we support access security features on EX4300-48MP switches that function as Layer 2 VXLAN gateways in an EVPN-VXLAN centrally-routed overlay network (two-layer IP fabric). We support the following features on Layer 2 server-facing interfaces that are associated with VXLAN-mapped VLANs:

DHCPv4 and DHCPv6 snooping. [See DHCP Snooping.]

•

Dynamic ARP inspection (DAI). [See Understanding and Using Dynamic ARP Inspection (DAI).]

•

Neighbor discovery inspection (NDI). [See IPv6 Neighbor Discovery Inspection.]

•

IPv4 and IPv6 source guard. [See Understanding IP Source Guard for Port Security on Switches.]

•

Router advertisement (RA) guard. [See Understanding IPv6 Router Advertisement Guard.]

•

The access security features function the same and you configure them in the same way in an EVPN-VXLAN environment as you do in a non-EVPN-VXLAN environment. However, keep these differences in mind:

We do not support these features on multihomed servers.

•

These features do not influence the VXLAN tunneling and encapsulation process.

•

Layer 3 VXLAN gateway support in EVPN-VXLAN overlay network (EX4300-48MP)—Starting in

•

Junos OS Release 19.4R1, the EX4300-48MP switch can function as a Layer 3 VXLAN gateway in an EVPN-VXLAN centrally-routed bridging overlay (two-layer IP fabric) and an edge-routed bridging overlay (collapsed IP fabric). As a Layer 3 VXLAN gateway, the switch supports these features:

Default gateway function through the configuration of an IRB interface. [See Using a Default Layer 3

•

Gateway to Route Traffic in an EVPN-VXLAN Overlay Network].

Routing of IPv6 data traffic through an EVPN-VXLAN overlay network with an IPv4 underlay. [See

•

Routing IPv6 Data Traffic through an EVPN-VXLAN Network with an IPv4 Underlay.]

EVPN pure Type 5 routes. [See Understanding EVPN Pure Type-5 Routes.]

•

Features supported on EX4650 and QFX5120 switches—Starting with Junos OS Release 19.4R1, the

•

following Junos OS features are supported on EX4650 and QFX5120 switches:

Automatically generated Ethernet segment identifiers (ESIs) in EVPN-VXLAN and EVPN-MPLS networks.

•

[See Understanding Automatically Generated and Assigned ESIs in EVPN Networks.]

Firewall filtering and policing on EVPN-VXLAN traffic.

•

[See Understanding VXLANs and Overview of Firewall Filters.]

Graceful restart on EVPN-VXLAN.

•

[See Graceful Restart in EVPN.]

IGMPv2 snooping for EVPN-VXLAN in a multihomed environment.

•

[See Overview of IGMP Snooping in an EVPN-VXLAN Environment.]

IPv6 data traffic support through an EVPN-VXLAN overlay network.

•

[See Routing IPv6 Data Traffic through an EVPN-VXLAN Network with an IPv4 Underlay.]

Layer 2 and 3 families, encapsulation types, and VXLAN on the same physical interface.

•

[See Understanding Flexible Ethernet Services Support with EVPN-VXLAN.]

MAC limiting, storm control, and port mirroring support in EVPN-VXLAN overlay networks.

•

[See MAC Limiting, Storm Control, and Port Mirroring Support in an EVPN-VXLAN Environment.]

Multihomed proxy advertisement.

•

[See EVPN Multihoming Implementation.]

Selective multicast forwarding and SMET route support in EVPN-VXLAN.

•

[See Overview of Selective Multicast Forwarding.]

Standard class-of-service (CoS) features—classifiers, rewrite rules, and schedulers—are supported on

•

VXLAN interfaces.

[See Understanding CoS on OVSDB-Managed VXLAN Interfaces.]

VMTO for ingress traffic.

•

[See Ingress Virtual Machine Traffic Optimization.]

Junos OS XML, API, and Scripting

Python 3 support for commit, event, op, and SNMP scripts (ACX Series, EX Series, MX Series, PTX

•

[See Understanding Python Automation Scripts for Devices Running Junos OS.]

Automation script library upgrades (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX

•

idna (2.8)

•

jinja2 (2.10.1)

•

jnpr.junos (Junos PyEZ) (2.2.0)

•

lxml (4.3.3)

•

markupsafe (1.1.1)

•

ncclient (0.6.4)

•

packaging (19.0)

•

paho.mqtt (1.4.0)

•

pyasn1 (0.4.5)

•

yaml (PyYAML package) (5.1)

•

[See Overview of Python Modules Available on Devices Running Junos OS.]

Junos Telemetry Interface

•

JTI Packet Forwarding Engine and Routing Engine sensor support (EX4300-MP switches)—Starting in Junos OS Release 19.4R1, you can use the Junos Telemetry Interface (JTI) and remote procedure calls (gRPC) to stream statistics from EX4300-MP switches to an outside collector.

The following Routing Engine statistics are supported:

LACP state export

•

Chassis environmentals export

•

Network discovery chassis and components

•

LLDP export and LLDP model

•

BGP peer information (RPD)

•

RPD task memory utilization export

•

Network discovery ARP table state

•

Network discovery NDP table state

•

The following Packet Forwarding Engine statistics are supported:

Congestion and latency monitoring

•

Logical interface

•

Filter

•

Physical interface

•

NPU/LC memory

•

Network discovery NDP table state

•

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 the Junos Telemetry Interface (JTI).

[See Configuring a Junos Telemetry Interface Sensor (CLI Procedure), Configure a Telemetry Sensor in

Junos and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

•

JTI and OpenConfig support for VLAN sensors (EX4650, QFX5120)—Junos OS Release 19.4R1 supports the export of VLAN statistics using either Junos Telemetry Interface (JTI) services or remote procedure call (gRPC) services. You can export statistics at configurable intervals to an outside collector.

This feature includes OpenConfig support for the data model openconfig-vlan.yang for VLAN configuration version 1.0.2.

Use the following resource paths in a gRPC or gNMI subscription:

/vlans/

•

/vlans/vlan/state/name

•

/vlans/vlan/state/vlan-id

•

/vlans/vlan/state/status

•

/vlans/vlan/members/

•

/vlans/vlan/members/member/interface-ref/state/interface/

•

/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/interface-mode

•

/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/native-vlan

•

/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/access-vlan

•

/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/trunk-vlan

•

/vlans/vlan/members/member/interface-ref/state/interface/vlan/state/vlan-id

•

Streaming telemetry data through gRPC or gNMI also requires the OpenConfig for Junos OS module.

[See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

Layer 2 Features

Redundant trunk group support (EX4650 and QFX5120)—Starting with Junos OS Release 19.4R1,

•

EX4650 and QFX5120 switches support redundant trunk group (RTG) links.

[See Redundant Trunk Groups.]

Ethernet ring protection switching (ERPS)(EX4300-MP)—Starting in Junos OS Release 19.4R1, the

•

EX4300-MP supports Ethernet ring protection switching (ERPS) to reliably achieve carrier-class network requirements for Ethernet topologies forming a closed loop. The ITU-T Recommendation is G.8032 version 1.

ERPS version 1 comprises the following features:

Revertive mode of operation of the Ethernet ring

•

Multiple ring instances on the same interfaces

•

Multiple ring instances on different interfaces

•

Interworking with Spanning Tree Protocol, Multiple Spanning Tree Protocol, and redundant trunk

•

groups

[See Ethernet Ring Protection Switching Overview.]

Ethernet ring protection switching (ERPS)(EX4650 and QFX5120)—Starting in Junos OS Release 19.4R1,

•

the EX4650 and QFX5120 support Ethernet ring protection switching (ERPS) to reliably achieve carrier-class network requirements for Ethernet topologies forming a closed loop. The ITU-T Recommendation is G.8032 version 1.

ERPS version 1 comprises the following features:

Revertive mode of operation of the Ethernet ring

•

Multiple ring instances on the same interfaces

•

Multiple ring instances on different interfaces

•

Interworking with Spanning Tree Protocol, Multiple Spanning Tree Protocol, and redundant trunk

•

groups

[See Ethernet Ring Protection Switching Overview.]

MPLS

MPLS scaling enhancements (EX4650 and QFX5120)—Starting in Junos OS Release 19.4R1, MPLS

•

scaling is enhanced on EX4650 and QFX5120 switches. For instance, you can increase the scale from its default 1024 to 8192 on QFX5120 switches. This enhancement optimizes and increases the ingress tunnel scale to address the current needs of data center networks either in IP-CLOS or IP over MPLS application spaces.

[See Supported MPLS Scaling Values.]

Multicast

Multicast VLAN registration (MVR) (EX4300-48MP switches and Virtual Chassis)—Starting in Junos

•

OS Release 19.4R1, EX4300 multigigabit (EX4300-48MP) switches and Virtual Chassis support multicast VLAN registration (MVR). MVR efficiently distributes IPTV multicast streams across an Ethernet ring-based Layer 2 network and reduces the bandwidth needed for this traffic. MVR uses a multicast VLAN (MVLAN) as a source VLAN associated with one or more multicast group addresses, and you designate other VLANs as MVR receiver VLANs that have listeners interested in the MVLAN traffic. The device selectively forwards the traffic from source interfaces on the MVLAN to receiver interfaces that are on the MVR receiver VLANs (but not on the MVLAN).

[See Understanding Multicast VLAN Registration.]

Operation, Administration, and Maintenance (OAM)

Ethernet CFM support (EX4300-MP switches)—Starting with Junos OS Release 19.4R1, the EX4300-MP

•

switch supports Ethernet connectivity fault management (CFM). You can use Ethernet CFM to:

Monitor faults, using the continuity check messages (CCM) protocol to discover and maintain adjacencies

•

at the VLAN or link level.

Discover paths and verify faults, using the linktrace protocol to map the path taken to a destination

•

MAC address.

Isolate faults, using loopback messages, and troubleshoot.

•

You configure Ethernet CFM using the set protocols oam ethernet connectivity-fault-management command, and verify the configuration using the show oam ethernet connectivity-fault-management command.

Support for Ethernet CFM (EX4650)—Starting with Junos OS Release 19.4R1, the EX4650 switch

•

supports Ethernet connectivity fault management (CFM). You can use Ethernet CFM to:

Monitor faults, using the continuity check messages (CCMs) to discover and maintain adjacencies at

•

the VLAN or link level.

Discover paths and verify faults, using the Link Trace protocol to map the path taken to a destination

•

MAC address.

Isolate and troubleshoot faults, using loopback messages. .

•

NOTE: Only down maintenance association end points (MEPs) are supported in CFM.

You configure Ethernet CFM using the set protocols oam ethernet connectivity-fault-management command, and verify the configuration using the show oam ethernet connectivity-fault-management command.

[See Understanding Ethernet OAM Connectivity Fault Management for Switches.]

Support for LFM (EX4650)—Starting with Junos OS Release 19.4R1, the EX4650 switch supports OAM link fault management (LFM). You can configure OAM LFM on point-to-point Ethernet links that are connected directly or through Ethernet repeaters, and on aggregated Ethernet interfaces. The LFM status of individual links determines the LFM status of the aggregated Ethernet interface. The EX4650 supports the following OAM LFM features:

Discovery and link monitoring

•

Remote fault detection

•

Remote loopback

•

[See IEEE 802.3ah OAM Link-Fault Management Overview.]

Port Security

Stateless address autoconfiguration (SLAAC) snooping (EX4300-48MP)—Starting in Junos OS Release

•

19.4R1, the EX4300-48MP switch supports Stateless address auto configuration (SLAAC) snooping. The switch validates IPv6 clients that use SLAAC for dynamic address assignment against the SLAAC snooping binding table before allowing the clients access to the network.

[See IPv6 Stateless Address Auto-configuration (SLAAC) Snooping.]

Untrusted mode on trunk interfaces for DHCP security (EX4300-48MP)—Starting in Junos OS Release

•

19.4R1, you can configure a trunk interface as untrusted for DHCP security features on EX4300-48MP switches. Trunk interfaces in untrusted mode support DHCP snooping and DHCPv6 snooping, dynamic ARP inspection (DAI), and IPv6 neighbor discovery inspection.

[See Understanding Trusted and Untrusted Ports.]

MACsec license enforcement (EX4300-48MP)—Starting in Junos OS Release 19.4R1, you must install

•

a Media Access Security (MACsec) feature license if you want MACsec functionality on your EX4300-48MP switch. If the MACsec license is not installed, MACsec functionality cannot be activated. You add the MACsec license using the request system license add command.

[See Understanding Media Access Control Security (MACsec).]

Routing Policy and Firewall Filters

Firewall filter support on IPv6 egress interfaces (EX4300-48MP)—Starting in Junos OS Release 19.4R1,

•

you can configure a firewall filter on an IPv6 egress interface to match the specified IPv6 source or destination addresses, for example, to protect a third-party device connected to the switch.

[See eracl-ip6-match and Configuring an Egress Filter Based on IPv6 Source or Destination IP Addresses.]

System Logging

Improved intermodule communication between FFP and MGD (ACX Series, EX Series, MX Series, PTX

•

Additional information is now logged for MGD-FFP intermodule communication.

•

Commit errors that previously were only shown onscreen are now logged.

•

We provide a new operational command, request debug information, to speed up the initial information-gathering phase of debugging.

[See request debug information.]

System Management

Change status LED for network port to chassis beacon light (EX2300, EX2300 Virtual Chassis, EX3400,

•

EX3400 Virtual Chassis)—By default, when a network port and its associated link are active, the status LED for that port blinks green 8 times per second. Starting in Junos OS Release 19.4R1, you can use the request chassis beacon command to slow down the current blinking rate to 2 blinks per second. The slower-blinking and steadier green light acts as a beacon that leads you to an EX2300 or EX3400 switch or a particular port in a busy lab.

Using options with the request chassis beacon command, you can do the following for one or all network port status LEDs on a specified FPC):

Turn on the beacon light for:

•

5 minutes (default)

•

A specified number of minutes (1 through 120)

•

Turn off the beacon light:

•

Immediately

•

After a specified number of minutes (1 through 120)

•

After the beacon light is turned off, the blinking rate for the network port’s status LED returns to 8 blinks per second.

[See request chassis beacon.]

User Interface and Configuration

Support for configuring the ephemeral database using the NETCONF and Junos XML protocols

•

(EX4300-48MP, EX9251, and EX9253 switches)—Starting in Junos OS Release 19.4R1, NETCONF and Junos XML protocol client applications can configure the ephemeral configuration database on EX4300-48MP, EX9251, and EX9253 switches. The ephemeral database provides a fast programmatic interface that enables multiple clients to simultaneously load and commit configuration changes on a device running Junos OS and with significantly greater throughput than when committing data to the candidate configuration database. The device’s active configuration is a merged view of the committed configuration database and the configuration data in all instances of the ephemeral configuration database.

[See Understanding the Ephemeral Configuration Database.]

SEE ALSO

What's Changed | 39

Known Limitations | 41

Open Issues | 42

Resolved Issues | 47

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

What's Changed

IN THIS SECTION

What’s Changed in Release 19.4R1-S3 | 40

What's Changed in Release 19.4R1 | 40

Learn about what changed in Junos OS main and maintenance releases for EX Series.

What’s Changed in Release 19.4R1-S3

General Routing

Command to view summary information for resource monitor (MX Series routers and EX9200 line of

•

switches)—You can use the show system resource-monitor command to view statistics about the use of memory resources for all line cards or for a specific line card in the device. The command also displays information about the status of load throttling, which manages how much memory is used before the device acts to reduce consumption.

[See show system resource-monitor.]

What's Changed in Release 19.4R1

General Routing

Enhancement to the show interfaces mc-ae extensive command—You can now view additional LACP

•

information about the LACP partner system ID when you run the show interfaces mc-ae extensive command. The output now displays the following two additional fields:

Local Partner System ID?LACP partner system ID as seen by the local node.

•

Peer Partner System ID?LACP partner system ID as seen by the MC-AE peer node.

•

Previously, the show interfaces mc-ae extensive command did not display these additional fields.

[See show interfaces mc-ae.]

Interfaces and Chassis

Logical Interface is created along with physical interface by default (MX Series, QFX Series, EX

•

Series)—Starting in Junos OS Release 19.4R1, logical interfaces are created on ge, et, and xe interfaces along with the physical interface, by default. In earlier Junos OS releases, by default, only physical interfaces are created.

For example, for ge interfaces, previously when you viewed the show interfaces command, by default, only the physical interface (ge-0/0/0), was displayed. Now, the logical interface (ge-0/0/0.16386) is also displayed.

Routing Protocols

XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX

•

Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release

[See show bgp output-scheduler.]

SEE ALSO

What's New | 29

Known Limitations | 41

Open Issues | 42

Resolved Issues | 47

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

Known Limitations

There are no known limitations for the EX Series switches in Junos OS Release 19.4R1.

SEE ALSO

What's New | 29

What's Changed | 39

Open Issues | 42

Resolved Issues | 47

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

Open Issues

IN THIS SECTION

Authentication and Access Control | 43

Class of Service (CoS) | 43

EVPN | 43

General Routing | 43

Infrastructure | 45

Interfaces and Chassis | 45

Junos Fusion Enterprise | 45

Junos Fusion Satellite Software | 45

Layer 2 Ethernet Services | 45

Layer 2 Features | 46

Platform and Infrastructure | 46

Routing Protocols | 46

User Interface and Configuration | 47

Learn about open issues in Junos OS Release 19.4R1 for EX Series. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Authentication and Access Control

Before running the command load ssl-certificate path PATHNAME, now we have to configure path

•

using CLI set protocols dot1x ssl-certificate-path PATHNAME, if pathname is not default path /var/tmp/.

PR1431086

Class of Service (CoS)

On EX4600 platforms, if shaping-rate is configured, the shaping feature might not work after a reboot.

•

The service might be impacted as the traffic cannot be rate limited. PR1432078

In Junos Fusion scenario, when traffic from aggregation device (AD) to satellite device (SD) is exported

•

with different DSCP marking, it might be changed into network-control queue on extended port of SD.

PR1433252

EVPN

In an EVPN environment, proxy ARP and ARP suppression is enabled on the PE device by default for

•

reducing the flooding of ARP packets; however, in the case of ARP probe packets used in the process of Duplicate Address Detection (DAD), the client might treat the IP address that it is in use as duplicated address after receiving the proxied packets from PE device. PR1427109

General Routing

On EX Series or QFX Series switches, if the switch is power cycled, then some processes (such as jdhcp,

•

lacp, and lldpd) might stop working after the switch reboots. PR1222504

If Non-NEBS (Network Equipment-Building System, a design guideline applied to telecommunications

•

equipment) compliant optics is used on MX MPC and chassis temperature exceeds non-nebs-optics-overheat-trigger (default: 50 degrees), the fan might not change to high speed because the temperature hasn't reached fan speed "High" threshold (default: 60 degrees). If the temperature remains over non-nebs-optics-overheat-trigger for about 10 minutes, the non-NEBS compliant optics might be disabled. PR1331186

On an EX2300 switch, the output of the show chassis routing-engine command might display an incorrect

•

value of mac reset for the last reboot reason field. PR1331264

EX4300 virtual-chassis systems may fail to register some jnxOperating SNMP OIDs related to the

•

routing-engines. This behavior is more likely if virtual-chassis members 0 and 1 (FPC0 and FPC1) are not selected as routing-engines. PR1368845

Traffic flooding occurs instead of routing, when VRRP is scaled more than 150. PR1371520

•

On the EX9208, a few xe-interfaces go down with the following error message:

•

if_msg_ifd_cmd_tlv_decode ifd xe-0/0/0 #190 down with ASIC Error. PR1377840

On EX Series platforms, the DHCP/PPP subscribers might fail to bind. The reason is that when installing

•

new software images, the shared memory (created by the previously running image) might not to be cleared out. As a result, the previous values in the shared memory are removed and the daemons affected by the data in the shared memory might continue to crash and generate core files. PR1396470

On the EX4650, uRPF check in strict mode might not work properly. PR1417546

•

When the chassisd process receives incorrect values from LCMD for the RPM values, it changes the Fan

•

status to "Failed" from "Ok", and vice versa. PR1417839

On EX2300/EX3400 Virtual Chassis platform with storm-control enabled, when multiple filter entries

•

get exhausted, VC becomes unstable and FXPC cores. PR1422132

In Virtual Chassis scenario, when the interfaces flaps or VLAN configuration is changed frequently, the

•

network topology will be changed accordingly, then CPU utilization will be dramatically increased to very high within a short time, which might cause the failure of essential communications between VC master and members. When the failure happens, FPC will automatically restart. As a result, VC is split and traffic is lost. PR1427075

EX4300-48MP switch cannot learn MAC address through some access ports that are directly connected

•

to a host when autonegotiation is used. PR1430109

The time taken to install or delete IPv4 or IPv6 routes into the FIB is slowed down in Junos OS Release

•

19.3. Analysis shows that rpd learning rates are not degraded but RIB to FIB download rate is degraded.

PR1441737

On the EX9214 device, if the MACsec-enabled link flaps after reboot, the error errorlib_set_error_log():

•

err_id(-1718026239) is observed. PR1448368

The sFlow sample packets might stop on one aggregated Ethernet member link if ingress sFlow is

•

configured on the member link. This might cause inaccurate monitoring on the network traffic. PR1449568

Traffic is dropped from SD to AD. The loss is intermediate and is not seen regularly. This occurs because

•

few packets that are transmitted from the egress of AD1 is short of FCS of data. It is observed that the normal data packets are of size 128 bytes while the corrupted data packet is of size 122 byte. PR1450373

On EX3400 with half-duplex mode on 10M or 100M speed at medium traffic rates due to PHY side

•

MAC buffer inconsistent state, MAC pause frames are seen on the port and egress traffic on the port stops to flow. PR1452209

In VXLAN setup containing a large number of child interfaces, significant link up delay was seen when

•

one of FPC in EX4600-40F rebooted. PR1456336

When tunnel-services are configured on a PIC, the optics measurements that subscribed through gRPC

•

might not be streamed. PR1468435

On EX Series platforms, the shaping of CoS does not work after reboot when the shaping rate is configured

•

with an absolute value. The line rate of traffic is sent out, no shaping occurs. This issue has traffic or service impact. PR1472223

Infrastructure

When xSTP/RTG is not configured in the network and there is a traffic loop, after the network loop is

•

broken, sometimes MAC address learning might not be learned. PR473454

On EX3400 and EX2300 line of switches during ZTP with configuration and image upgrade with FTP

•

as file transfer, image upgrade is successful but sometimes VM core files might be generated. PR1377721

On EX Series platforms, when you configure a large number of firewall filters on some interfaces, the

•

FPC crashes generating core files. PR1434927

Packet Forwarding Engine sometimes does not come up after system reboot. Timeout is required to

•

handle the fifo tx/rx error. Debug sysctls are been removed. PR1454950

On EX4300-48MP device acting as a leaf in Layer 2 IP fabric EVPN VXLAN environment, the 100 percent

•

traffic drop might be seen if unplug cable is connected to the et-interface and plug it back. PR1463318

Interfaces and Chassis

When dynamic DHCP sessions exist in the device, if multiple commits in parallel are performed, the

•

commit might hang up. PR1470622

Junos Fusion Enterprise

In a Junos Fusion Enterprise environment, when traffic originates from a peer device connected to the

•

aggregation device and the ICL is a LAG, there might be a reachability issue if the cascade port is disabled and traffic has to flow through the ICL LAG to reach the satellite device. As a workaround, use single interface as the ICL instead of a LAG. PR1447873

Junos Fusion Satellite Software

In Junos Fusion dpd might crash on satellite devices running SNOS. PR1460607

•

Layer 2 Ethernet Services

The jdhcpd_era log files constantly consume 121M of space out of 170M, resulting into file system full

•

and traffic impact. PR1431201

In EVPN multihomed ACTIVE-ACTIVE scenario when LACP is enable on PE-CE child member links and

•

after recovering from a core-isolation on PE device, the PE-CE child member links might be stuck in DETACHED state if LACP sync-reset feature is enabled on CE device. The child links on the CE device might show LACP state as "Collecting Distributing", but on the PE device the LACP state might be "DETACHED". PR1463791

Layer 2 Features

On EX4600 platforms, if copper base SFP-T is used, it might not get up on physical layer and the

•

MAC/ARP learning might not work if it gets up. PR1437577

Platform and Infrastructure

The commit synchronize command fails because the kernel socket gets stuck. PR1177692

•

On EX4300-32F platform, when SFP-T is used in a port earlier and SFP is inserted and then removed

•

from the same port, the pfex process might crash and core dump. PR1421257

On all Junos OS platform, in some rare conditions, there might be packet drops, replication failures or

•

ksynchd crashes on the logical system. This issue might appear at the time of Routing Engine switchover if the system is running for a long time and lot of configuration changes have been made over the time.

PR1427842

On EX9208, the traffic loss is observed if ingress and egress ports are in different FPC. PR1429714

•

On EX4300 platform, if FBF filters are applied on IRB with LAG configuration also existing on the box,

•

the firewall filters cannot be created and function correctly due to TCAM programming issues. PR1447012

On EX9208, 33 percent degradation with MAC learning rate in Junos OS Release 19.3R1 while comparing

•

with Junos OS Release 18.4R1. PR1450729

In the Virtual Chassis scenario, the IRB traffic might get dropped after master switchover. PR1453025

•

On EX4300 platforms in IGMP snooping scenario, if both SP/EP styles of Ethernet encapsulations are

•

used in one VLAN, IGMP reports are not forwarded from group member interfaces towards multicast routers interface in the VLAN. PR1466075

Routing Protocols

On EX4300 and EX4600 Series switches, if host destined packets (that is, the destination address belongs

•

to the device) come from the interface with ingress filter of log/syslog action (for example, 'filter <> term <> then log/syslog'), such packets should not be dropped and reach the Routing Engine. PR1379718

BGP IPv4 or IPv6 convergence and RIB install/delete time is degraded in Junos OS Releases 19.1R1,

•

19.2R1, 19.3R1, and 19.4R1. PR1414121

On EX4600 platforms, the received traffic will be dropped if the destination UDP port is 520/521 though

•

the device runs pure layer 2 switching. PR1429543

On EX4600 with service provider (SP) style VLAN configuration (in this method, each VLAN-ID is locally

•

significant to a physical interface), if interface-mac-limit or mac-table-size is configured (that is, software MAC learning is enabled) and the scale of MAC addresses on the box is more than 2000, traffic might be dropped after QinQ enabled interface is flapped or a change is made to the vlan-id-list. PR1441402

User Interface and Configuration

On EX Series switches, while checking add or delete interface-range configuration, couldn't find end-range

•

in deleted tree for member-range message is logged. PR1357574

SEE ALSO

What's New | 29

What's Changed | 39

Known Limitations | 41

Resolved Issues | 47

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

Resolved Issues

IN THIS SECTION

Authentication and Access Control | 48

EVPN | 48

General Routing | 48

Infrastructure | 50

Interfaces and Chassis | 51

Junos Fusion Enterprise | 51

Junos Fusion Satellite Software | 51

J-Web | 51

Layer 2 Ethernet Services | 51

Layer 2 Features | 51

Platform and Infrastructure | 52

Routing Protocols | 52

User Interface and Configuration | 53

Virtual Chassis | 53

Learn which issues were resolved in Junos OS main and maintenance releases for EX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Authentication and Access Control

After rebooting the preloaded box, the SSL certificate is not displayed. PR1431086

•

EVPN

In EVPN scenario, the IRB logical interface might not come up when the local Layer 2 interface is down.

•

PR1436207

ARP request or Neighbor Solicitation (NS) message might be sent back to the local segment by the DF

•

router. PR1459830

The rpd might crash after changing EVPN related configuration. PR1467309

•

General Routing

On the EX3400, when me0 ports are connected between two EX3400 switches, the link does not come

•

up. PR1351757

Transit OSPF traffic over Q-in-Q tunneling might be dropped if a firewall filter is applied to the Lo0

•

interface. PR1355111

The l2ald process might crash and generate a core file on EX2300 Virtual Chassis when converted a

•

trunk port is converted to a dot1x access port with tagged traffic flowing. PR1362587

The interface on the failed member FPC of EX2300 and EX3400 Virtual Chassis might stay up for 120

•

seconds. PR1422507

IPv6 multicast traffic received on one Virtual Chassis member might be dropped when egressing on

•

another Virtual Chassis member if MLD snooping is enabled. PR1423310

MAC addresses overlaps between different switches. PR1425123

•

The delay in transmission of BPDUs after GRES might result in loss of traffic on EX2300 and EX3400

•

Virtual Chassis. PR1428935

Erroneous log messages and chassis environment output related to the fan tray in EX4300MP and

•

EX4300-48P Virtual Chassis. PR1431263

The l2cpd process might crash and generate a core file when interfaces flap. PR1431355

•

Packet drop might be seen if native VLAN is configured along with flexible VLAN tagging. PR1434646

•

Micro BFD session might flap upon inserting a QSFP to other port. PR1435221

•

The mc-ae interface might get stuck in waiting state in a dual mc-ae scenario. PR1435874

•

Commit check error for VSTP on the EX9200 line of switches xSTP:Trying to configure too many

•

interfaces for given protocol. PR1438195

LED turns on even after the Virtual Chassis members are powered off. PR1438252

•

The DHCP snooping table might be cleared for VLAN ID 1 after adding a new VLAN ID to it. PR1438351

•

The rpd process might generate a core file when the router boots up because of a file pointer issue

•

because there are two code paths that can close the file. PR1438597

The dot1x might not work when captive-port is also configured on the interface on the backup or

•

nonmaster FPC. PR1439200

DHCPv6 relay binding is not up while verifying DHCP snooping along with DHCPv6 relay. PR1439844

•

EX4600 Virtual Chassis does not come up after replacing the Virtual Chassis port from fiber connection

•

to DAC cable. PR1440062

CPU might hang or interface might get stuck on a particular 100-Gigabit Ethernet port on EX Series

•

switches. PR1440526

MAC addresses learned on RTG might not be aged out after a Virtual Chassis member is rebooted.

•

PR1440574

Clients in isolated VLAN might not get IP addresses after completing authentication when both

•

dhcp-security and dot1x are configured. PR1442078

On the EX3400, the fan alarm Fan X not spinning appears and disappears repeatedly after the fan tray

•

is removed. PR1442134

The rpd might crash when the BGP sends a notification message. PR1442786

•

DHCPv6 client might fail to get an IP address. PR1442867

•

Non-designated port does not move to the backup port role. PR1443489

•

The /var/host/motd does not exist message is flooded every 5 seconds in chassisd logs. PR1444903

•

On the EX4300-MP, the following log messages is generated continuously: rpd[6550]: task_connect:

•

task AGENTD I/O.128.0.0.1+9500 addr 128.0.0.1+9500: Connection refused. PR1445618

On the EX3400 dot1xd core file is found at macsec_update_intf macsec_destroy_ca. PR1445764

•

Major alarm log messages for temperature conditions are generated for the EX4600 at 56 degrees

•

Celsius. PR1446363

Traffic might be dropped when a firewall filter rule uses 'then vlan' as the action in a Virtual Chassis

•

scenario. PR1446844

The phone-home feature might fail on EX3400 switches because sysctl cannot read the device serial

•

number. PR1447291

On EX3400, Virtual Chassis might hang when a disk error occurs. PR1447853

•

Unicast ARP requests do not receive a reply with the no-arp-trap option. PR1448071

•

On EX3400, IPv6 routes received through BGP do not show the correct age time. PR1449305

•

Except one aggregated Ethernet member link, the other links do not send out sFlow sample packets for

•

ingress traffic. PR1449568

DHCP snooping static binding does not take effect after deleting and readding the entries. PR1451688

•

The l2ald and eventd processes are hogging 100 percent after issuing the clear ethernet-switching table

•

command. PR1452738

Configuration change in the VLAN all option might affect the per-VLAN configuration. PR1453505

•

Version compare in PHC might fail and the same image might be downloaded. PR1453535

•

Packet drops might be seen after removing and reinserting the SFP transceiver of the 40-Gigabit Ethernet

•

uplink module ports. PR1456039

Syslog message Timeout connecting to peer database-replication is generated when the command show

•

version detail is issued. PR1457284

SNMP trap messages are generated after an upgrade even though the temperature is within the system

•

thresholds. PR1457456

The correct VoIP VLAN information in LLDP-MED packets might not be sent after commit if dynamic

•

VoIP VLAN assignment is used. PR1458559

The fxpc process might crash because the BGP IPv6 session flaps. PR1459759

•

Storage space limitation leads to image installation failure when the phone-home client is used on EX2300

•

and EX3400 devices. PR1460087

Configure any combination of VLANs and interfaces under VSTP/MSTP might cause VSTP/MSTP related

•

configuration cannot be committed. PR1463251

The Virtual Chassis function might brake after an upgrade on EX2300 and EX3400 devices. PR1463635

•

On the EX2300, FXPC core file is generated after mastership election based on user priority. PR1465526

•

Infrastructure

The operations on the console might not work if the system ports console log-out-on-disconnect

•

statement is configured. PR1433224

The recovery snapshot cannot be created after system zeroization. PR1439189

•

On EX4300 CLI configuration on-disk-failure is not supported in Junos OS Release 18.2R3-S2. PR1450093

•

Certain EX Series platforms might generate VM core files by panic and reboot. PR1456668

•

Error messages related to soft reset of port because the queue buffers are stuck might be seen on

•

EX4600-EX4300 VC. PR1462106

The traffic is dropped on EX4300-48MP device acting as a leaf in Layer 2 IP fabric EVPN VXLAN

•

environment. PR1463318

Interfaces and Chassis

VRRP-V6 state flaps with init and idle states after configuring vlan-tagging. PR1445370

•

The traffic might be forwarded to incorrect interfaces in MC-LAG scenario. PR1465077

•

Junos Fusion Enterprise

Reachability issue of the host connected to the SD might be affected in a Junos Fusion Enterprise

•

environment with EX9200 Series devices as AD. PR1447873

Junos Fusion Satellite Software

The dpd might crash on satellite devices in a Junos Fusion Enterprise environment. PR1460607

•

J-Web

Some error messages might be seen when using J-Web. PR1446081

•

Layer 2 Ethernet Services

The jdhcpd_era log files constantly consume 121M of space out of 170M, resulting in a full file system

•

and affecting traffic. PR1431201

DHCP request might get dropped in DHCP relay scenario. PR1435039

•

On EX9200, the DHCP relay strips the 'GIADDR' field in messages towards the DHCP clients. PR1443516

•

Layer 2 Features

Ethernet Ring Protection Switching (ERPS) nodes might not converge to IDLE state after failure recovery

•

or reboot. PR1431262

The MAC/ARP learning might not work for copper base SFP-T on EX4600. PR1437577

•

The fxpc core files might be generated when committing the configuration. PR1467763

•

Platform and Infrastructure

LACP DDoS policer is incorrectly triggered by other protocols traffic on all EX92XX Series platforms.

•

PR1409626

Over temperature SNMP trap is generated incorrectly for LC (EX4300-48P) based on master Routing

•

Engine (EX4300-48MP) temperature threshold value. PR1419300

Packet drops, replication failure, or ksyncd crash might be seen on the logical system of a Junos OS

•

device after Routing Engine switchover. PR1427842

IPv6 traffic might be dropped when static /64 IPv6 routes are configured. PR1427866

•

Unicast ARP requests are not replied to with no-arp-trap option. PR1429964

•

The device might not be accessible after the upgrade. PR1435173

•

The FPC/pfex might crash due to DMA buffer leaking. PR1436642

•

The laser TX might be enabled while the interface is disabled. PR1445626

•

The PoE might not work after upgrading the PoE firmware on EX4300 platforms. PR1446915

•

The firewall filters might not be created due to TCAM issues. PR1447012

•

NSSU causes traffic loss again after the backup to master transitions. PR1448607

•

On certain MPC line cards, cm errors need to be reclassified. PR1449427

•

The REST service might become nonresponsive when the REST API receives several continuous HTTP

•

requests. PR1449987

The traffic for some VLANs might not be forwarded when vlan-id-list is configured. PR1456879

•

ERP might not revert to idle state after reload or reboot of multiple switches. PR1461434

•

Routing Protocols

Host-destined packets with filter log action might not reach to the Routing Engine if log/syslog is enabled.

•

PR1379718

On EX9208, BGP IPv4/IPv6 convergence and RIB install/delete time is degraded in Junos OS Releases

•

19.1R1, 19.2R1, 19.3R1, and 19.4R1. PR1414121

The fxpc core file might be generated during the reboot of EX4600 switches. PR1432023

•

Error message RPD_DYN_CFG_GET_PROF_NAME_FAILED: Get profile name for session XXX failed:

•

-7 might be seen in syslog after restarting the routing daemon. PR1439514

Traffic might be dropped after the Q-in-Q enabled interface flaps or a change is made to the vlan-id-list.

•

PR1441402

IPv6 connectivity between MC-LAG peers might fail when multiple IRB interfaces are present. PR1443507

•

Junos OS BFD sessions with authentication flaps after a certain time. PR1448649

•

Loopback address exported into other VRF instance might not work on EX Series platforms. PR1449410

•

MPLS LDP might still use stale MAC of the neighbor even when the LDP neighbor's MAC changes.

•

PR1451217

Changing "other querier present interval" timer is not working on IGMP/MLD snooping device in the

•

existing bridge domain (BD) or listener domain (LD). PR1461590

User Interface and Configuration

EX4600 switches are unable to commit baseline configuration after zeroization. PR1426341

•

Problem with access to J-Web after updating from Junos OS Release 18.2R2 to 18.2R3. PR1454150

•

Virtual Chassis

Current MAC address might change after deleting one of the multiple Layer 3 interfaces. PR1449206

•

SEE ALSO

What's New | 29

What's Changed | 39

Known Limitations | 41

Open Issues | 42

Documentation Updates | 53

Migration, Upgrade, and Downgrade Instructions | 54

Documentation Updates

IN THIS SECTION

Feature Guides Are Renamed As User Guides | 54

This section lists the errata and changes in Junos OS Release 19.4R1 for the EX Series switches documentation.

Feature Guides Are Renamed As User Guides

Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the

•

SEE ALSO

What's New | 29

What's Changed | 39

Known Limitations | 41

Open Issues | 42

Resolved Issues | 47

Migration, Upgrade, and Downgrade Instructions | 54

Migration, Upgrade, and Downgrade Instructions

IN THIS SECTION

Upgrade and Downgrade Support Policy for Junos OS Releases | 54

This section contains the upgrade and downgrade support policy for Junos OS for the EX Series. Upgrading or downgrading Junos OS can take several hours, 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

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.

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.

For more information about EEOL releases and to review a list of EEOL releases, see

https://support.juniper.net/support/eol/software/junos/.

SEE ALSO

What's New | 29

What's Changed | 39

Known Limitations | 41

Open Issues | 42

Resolved Issues | 47

Documentation Updates | 53

Junos OS Release Notes for JRR Series

IN THIS SECTION

What's New | 56

What's Changed | 57

Known Limitations | 57

Open Issues | 58

Resolved Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

These release notes accompany Junos OS Release 19.4R1 for JRR Series. They describe new and changed features, limitations, and known and resolved problems in the hardware.

You can 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

Hardware | 56

Learn about new features introduced in Junos OS Release 19.4R1 for JRR Series.

Hardware

JRR200 Route Reflector—Starting with Junos OS Release 19.4R1, JRR200 Route Reflector a 1U form

•

factor appliance with a multicore x86 CPU and preinstalled vRR software that can host one route reflector instance is available. JRR200 is suitable for large enterprises, data centers and service providers for hosting vRR software to scale up to 30 million routing information base (RIB) entries. The JRR200 route reflector comes with eight 1/10 Gigabit Ethernet SFP+ ports, 64 GB of DDR4 memory, and two 240 GB solid-state drives (SSDs) in a RAID1 configuration. It is available in both AC and DC models which support Zero Touch Provisioning mode (ZTP) to ensure seamless insertion into the network and provide operational simplicity.

[See JRR200 Route Reflector Hardware Guide and JRR200 Route Reflector Quick Start]

ZTP Support for JRR200 Route Reflector—Starting in Junos OS Release 19.4R1, ZTP can automate the

•

provisioning of the device configuration and software image on JRR200 Route Reflector. ZTP supports self image upgrades and automatic configuration updates using ZTP DHCP options. In this release, ZTP supports revenue ports em2 thru em9, in addition to management port em0 which is supported in Junos OS Releases before 19.4R1.

[See Zero Touch Provisioning.]

SEE ALSO

What's Changed | 57

Known Limitations | 57

Open Issues | 58

Resolved Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

What's Changed

There are no changes in behavior and syntax for JRR Series in Junos OS Release 19.4R1.

SEE ALSO

What's New | 56

Known Limitations | 57

Open Issues | 58

Resolved Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

Known Limitations

There are no known limitations for JRR Series in Junos OS Release 19.4R1.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What's New | 56

What's Changed | 57

Open Issues | 58

Resolved Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

Open Issues

IN THIS SECTION

General Routing | 58

Learn about open issues in this release for JRR 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

USB install image does not work for JRR200 platform. PR1471986

•

SEE ALSO

What's New | 56

What's Changed | 57

Known Limitations | 57

Resolved Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

Resolved Issues

There are no fixed issues in Junos OS Release 19.4R1 for JRR Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What's New | 56

What's Changed | 57

Known Limitations | 57

Open Issues | 58

Documentation Updates | 59

Migration, Upgrade, and Downgrade Instructions | 60

Documentation Updates

IN THIS SECTION

Feature Guides Are Renamed As User Guides | 59

This section lists the errata and changes in Junos OS Release 19.4R1 documentation for JRR Series.

Feature Guides Are Renamed As User Guides

Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the

•

SEE ALSO

What's New | 56

What's Changed | 57

Known Limitations | 57

Open Issues | 58

Resolved Issues | 58

Migration, Upgrade, and Downgrade Instructions | 60

Migration, Upgrade, and Downgrade Instructions

IN THIS SECTION

Upgrade and Downgrade Support Policy for Junos OS Releases | 60

This section contains the upgrade and downgrade support policy for Junos OS for the JRR Series Route Reflector. 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

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.

For more information about EEOL releases and to review a list of EEOL releases, see

https://www.juniper.net/support/eol/junos.html.

For information about software installation and upgrade, see the Installation and Upgrade Guide.

SEE ALSO

What's New | 56

What's Changed | 57

Known Limitations | 57

Resolved Issues | 58

Open Issues | 58

Documentation Updates | 59

Junos OS Release Notes for Junos Fusion Enterprise

IN THIS SECTION

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Resolved Issues | 64

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

These release notes accompany Junos OS Release 19.4R1 for Junos Fusion Enterprise. Junos Fusion Enterprise is a Junos Fusion that uses EX9200 switches in the aggregation device role. These release notes describe new and changed features, limitations, and known problems in the hardware and software.

NOTE: For a complete list of all hardware and software requirements for a Junos Fusion

Enterprise, including which Juniper Networks devices can function as satellite devices, see

Understanding Junos Fusion Enterprise Software and Hardware Requirements .

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

There are no new features or enhancements to existing features in Junos OS Release 19.4R1 for Junos fusion for enterprise.

NOTE: For more information about the Junos Fusion Enterprise features, see the Junos Fusion

Enterprise User Guide.

SEE ALSO

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Resolved Issues | 64

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

What’s Changed

There are no changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 19.4R1 for Junos fusion for enterprise.

SEE ALSO

What’s New | 61

Known Limitations | 62

Open Issues | 63

Resolved Issues | 64

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

Known Limitations

There are no known behaviors, system maximums, and limitations in hardware and software in Junos OS Release 19.4R1 for Junos fusion for enterprise.

For the most complete and latest information about known Junos OS problems, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What’s New | 61

What’s Changed | 62

Open Issues | 63

Resolved Issues | 64

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

Open Issues

IN THIS SECTION

Junos Fusion for Enterprise | 63

Learn about open issues in this release for Junos fusion for enterprise. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Junos Fusion for Enterprise

In a Junos fusion for enterprise environment, when traffic originates from a peer device connected to

•

the aggregation device and the ICL is a LAG, there might be a reachability issue if the cascade port is disabled and traffic has to flow through the ICL LAG to reach the satellite device. As a workaround, use single interface as the ICL instead of a LAG. PR1447873

On a Junos fusion for enterprise system, intermediate traffic drop is sometime seen between the

•

aggregation device and satellite device when sFlow is enabled on the ingress interface. PR1450373

In Junos fusion for enterprise, the dpd process generate a core file on satellite devices running SNOS.

•

PR1460607

SEE ALSO

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

Resolved Issues

This section lists the issues fixed in Junos OS Release 19.4R1.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Documentation Updates | 64

Migration, Upgrade, and Downgrade Instructions | 65

Documentation Updates

This section lists the errata and changes in Junos OS Release 19.4R1 documentation for Junos Fusion for enterprise.

Feature Guides Are Renamed As User Guides

Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the

•

SEE ALSO

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Resolved Issues | 64

Migration, Upgrade, and Downgrade Instructions | 65

Migration, Upgrade, and Downgrade Instructions

IN THIS SECTION

Basic Procedure for Upgrading Junos OS on an Aggregation Device | 66

Upgrading an Aggregation Device with Redundant Routing Engines | 67

Preparing the Switch for Satellite Device Conversion | 68

Converting a Satellite Device to a Standalone Switch | 69

Upgrade and Downgrade Support Policy for Junos OS Releases | 69

Downgrading from Junos OS | 70

This section contains the procedure to upgrade or downgrade Junos OS and satellite software for a Junos fusion for enterprise. Upgrading or downgrading Junos OS and satellite software might take several hours, depending on the size and configuration of the Junos Fusion Enterprise topology.

Basic Procedure for Upgrading Junos OS on an Aggregation Device

When upgrading or downgrading Junos OS for an aggregation device, always use the junos-install package. Use other packages (such as the jbundle package) only when so instructed by a Juniper Networks support representative. For information about the contents of the junos-install package and details of the installation process, see the Installation and Upgrade Guide.

NOTE: Before upgrading, back up the file system and the currently active Junos OS configuration

so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:

user@host> request system snapshot

The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the routing platform, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. See the Junos OS Administration Library.

To download and install Junos OS:

1. Using a Web browser, navigate to the Download Software URL on the Juniper Networks webpage:

https://www.juniper.net/support/downloads/

2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.

3. Select By Technology > Junos Platform > Junos Fusion to find the software that you want to download.

4. Select the release number (the number of the software version that you want to download) from the Version drop-down list on the right of the page.

5. Select the Software tab.

6. Select the software package for the release.

7. Review and accept the End User License Agreement.

8. Download the software to a local host.

9. Copy the software to the routing platform or to your internal software distribution site.

10. Install the new junos-install package on the aggregation device.

NOTE: We recommend that you upgrade all software packages out of band using the console

because in-band connections are lost during the upgrade process.

Customers in the United States and Canada, use the following commands:

user@host> request system software add validate reboot source/package.tgz

All other customers, use the following commands, where n is the spin number.

user@host> request system software add validate reboot source/package-limited.tgz

Replace source with one of the following values:

/pathname—For a software package that is installed from a local directory on the router.

•

For software packages that are downloaded and installed from a remote location:

•

ftp://hostname/pathname

•

http://hostname/pathname

•

scp://hostname/pathname (available only for Canada and U.S. version)

•

The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes.

Rebooting occurs only if the upgrade is successful.

Upgrading an Aggregation Device with Redundant Routing Engines

If the aggregation device has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to minimize disrupting network operations as follows:

1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Preparing the Switch for Satellite Device Conversion

There are multiple methods to upgrade or downgrade satellite software in your Junos Fusion Enterprise. See Configuring or Expanding a Junos Fusion Enterprise.

For satellite device hardware and software requirements, see Understanding Junos Fusion Enterprise

Software and Hardware Requirements.

Use the following command to install Junos OS on a switch before converting it into a satellite device:

user@host> request system software add validate reboot source/package-name

NOTE: The following conditions must be met before a Junos switch that is running Junos OS

Release 14.1X53-D43 can be converted to a satellite device when the action is initiated from the aggregation device:

The switch running Junos OS can be converted only to SNOS 3.1 and later.

•

Either the switch must be set to factory-default configuration by using the request system

•

zeroize command, or the following command must be included in the configuration: set chassis auto-satellite-conversion.

When the interim installation has completed and the switch is running a version of Junos OS that is compatible with satellite device conversion, perform the following steps:

1. Log in to the device using the console port.

2. Clear the device:

[edit] user@satellite-device# request system zeroize

NOTE: The device reboots to complete the procedure for resetting the device.

If you are not logged in to the device using the console port connection, your connection to the device is lost after you enter the request system zeroize command.

If you lose connection to the device, log in using the console port.

3. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port port-number

For example, to convert all four built-in 40-Gbps QSFP+ interfaces on an EX4300-24P switch into network ports:

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 0 user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 1 user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 2 user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 3

This step is required for the 40-Gbps QSFP+ interfaces that will be used as uplink interfaces in a Junos Fusion topology. Built-in 40-Gbps QSFP+ interfaces on EX4300 switches are configured into VCPs by default, and the default settings are restored after the device is reset.

After this initial preparation, you can use one of three methods to convert your switches into satellite devices—autoconversion, manual conversion, or preconfiguration. See Configuring or Expanding a Junos

Fusion Enterprise for detailed configuration steps for each method.

Converting a Satellite Device to a Standalone Switch

If you need to convert a satellite device to a standalone device, you must install a new Junos OS software package on the satellite device and remove it from the Junos Fusion topology. For more information, see

Converting a Satellite Device to a Standalone Device.

Upgrade and Downgrade Support Policy for Junos OS Releases

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.

For more information about EEOL releases and to review a list of EEOL releases, see

https://www.juniper.net/support/eol/junos.html

Downgrading from Junos OS

Junos Fusion Enterprise is first supported in Junos OS Release 16.1, although you can downgrade a standalone EX9200 switch to earlier Junos OS releases.

NOTE: You cannot downgrade more than three releases.

For more information, see the Installation and Upgrade Guide.

To downgrade a Junos Fusion Enterprise from Junos OS Release 19.4R1, follow the procedure for upgrading, but replace the 19.2 junos-install package with one that corresponds to the appropriate release.

SEE ALSO

What’s New | 61

What’s Changed | 62

Known Limitations | 62

Open Issues | 63

Resolved Issues | 64

Documentation Updates | 64

Junos OS Release Notes for Junos Fusion Provider Edge

IN THIS SECTION

What's New | 71

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Resolved Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

These release notes accompany Junos OS Release 19.4R1 for the Junos Fusion Provider Edge. 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

There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 19.4R1.

SEE ALSO

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Resolved Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

What's Changed

There are no changes in the behavior of Junos OS features or in the syntax of Junos OS statements and commands in Junos OS Release 19.4R1 for Junos fusion for provider edge.

SEE ALSO

What's New | 71

Known Limitations | 72

Open Issues | 73

Resolved Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

Known Limitations

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What's New | 71

What's Changed | 72

Open Issues | 73

Resolved Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

Open Issues

IN THIS SECTION

Junos Fusion for Provider Edge | 73

Learn about open issues in this release for Junos Fusion Provider Edge.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Junos Fusion for Provider Edge

The sdpd process might continuously crash if there are more than 12 cascade-ports configured to a

•

satellite device. PR1437387

The aggregated Ethernet interface might flap whenever a new logical interface is added. PR1441869

•

SEE ALSO

What's New | 71

What's Changed | 72

Known Limitations | 72

Resolved Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

Resolved Issues

There are no fixed issues in the Junos OS Release 19.4R1 for Junos Fusion Provider Edge.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

SEE ALSO

What's New | 71

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Documentation Updates | 74

Migration, Upgrade, and Downgrade Instructions | 75

Documentation Updates

IN THIS SECTION

Feature Guides Are Renamed As User Guides | 74

This section lists the errata and changes in Junos OS Release 19.4R1 for Junos Fusion Provider Edge.

Feature Guides Are Renamed As User Guides

Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the

•

SEE ALSO

What's New | 71

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Resolved Issues | 73

Migration, Upgrade, and Downgrade Instructions | 75

Migration, Upgrade, and Downgrade Instructions

IN THIS SECTION

Basic Procedure for Upgrading an Aggregation Device | 75

Upgrading an Aggregation Device with Redundant Routing Engines | 78

Preparing the Switch for Satellite Device Conversion | 78

Converting a Satellite Device to a Standalone Device | 80

Upgrading an Aggregation Device | 82

Upgrade and Downgrade Support Policy for Junos OS Releases | 82

Downgrading from Junos OS Release 19.4 | 83

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for Junos fusion for provider edge. Upgrading or downgrading Junos OS might take several hours, depending on the size and configuration of the network.

Basic Procedure for Upgrading an Aggregation Device

When upgrading or downgrading Junos OS, always use the jinstall package. Use other packages (such as the jbundle package) only when so instructed by a Juniper Networks support representative. For information about the contents of the jinstall package and details of the installation process, see the Installation and

Upgrade Guide.

NOTE: Before upgrading, back up the file system and the currently active Junos OS configuration

so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:

user@host> request system snapshot

The download and installation process for Junos OS Release 19.4R1 is different from that for earlier Junos OS releases.

1. Using a Web browser, navigate to the Download Software URL on the Juniper Networks webpage:

https://www.juniper.net/support/downloads/

2. Log in to the Juniper Networks authentication system by using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.

3. Select By Technology > Junos Platform > Junos Fusion to find the software that you want to download.

4. Select the release number (the number of the software version that you want to download) from the Version drop-down list to the right of the page.

5. Select the Software tab.

6. Select the software package for the release.

7. Review and accept the End User License Agreement.

8. Download the software to a local host.

9. Copy the software to the routing platform or to your internal software distribution site.

10. Install the new jinstall package on the aggregation device.

NOTE: We recommend that you upgrade all software packages out-of-band using the console,

because in-band connections are lost during the upgrade process.

Customers in the United States and Canada, use the following commands.

For 64-bit software:

•

NOTE: We recommend that you use 64-bit Junos OS software when implementing Junos

Fusion Provider Edge.

user@host> request system software add validate reboot

source/jinstall64-19.4R1.SPIN-domestic-signed.tgz

For 32-bit software:

•

user@host> request system software add validate reboot

source/jinstall-19.4R1.SPIN-domestic-signed.tgz

All other customers, use the following commands.

For 64-bit software:

•

NOTE: We recommend that you use 64-bit Junos OS software when implementing Junos

Fusion Provider Edge.

user@host> request system software add validate reboot

source/jinstall64-19.4R1.SPIN-export-signed.tgz

For 32-bit software:

•

user@host> request system software add validate reboot

source/jinstall-19.4R1.SPIN-export-signed.tgz

Replace source with one of the following values:

/pathname—For a software package that is installed from a local directory on the router.

•

For software packages that are downloaded and installed from a remote location:

•

ftp://hostname/pathname

•

http://hostname/pathname

•

scp://hostname/pathname (available only for the Canada and U.S. version)

•

The validate option validates the software package against the current configuration as a prerequisite for adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is for a different release.

Rebooting occurs only if the upgrade is successful.

NOTE: After you install a Junos OS Release 19.4R1 jinstall package, you cannot return to the

previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

Upgrading an Aggregation Device with Redundant Routing Engines

If the aggregation device has two Routing Engines, perform a Junos OS installation on each Routing Engine separately as follows to minimize disrupting network operations:

1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Preparing the Switch for Satellite Device Conversion

Satellite devices in a Junos fusion topology use a satellite software package that is different from the standard Junos OS software package. Before you can install the satellite software package on a satellite device, you first need to upgrade the target satellite device to an interim Junos OS software version that can be converted to satellite software. For satellite device hardware and software requirements, see

Understanding Junos Fusion Software and Hardware Requirements

NOTE: The following conditions must be met before a standalone switch that is running Junos

OS Release 14.1X53-D43 can be converted to a satellite device when the action is initiated from the aggregation device:

The switch can be converted to only SNOS 3.1 and later.

•

Either the switch must be set to factory-default configuration by using the request system

•

zeroize command, or the following command must be included in the configuration: set chassis auto-satellite-conversion.

Customers with EX4300 switches, use the following command:

user@host> request system software add validate reboot

source/jinstall-ex-4300-14.1X53-D43.3-domestic-signed.tgz

Customers with QFX5100 switches, use the following command:

user@host> request system software add reboot

source/jinstall-qfx-5-14.1X53-D43.3-domestic-signed.tgz

When the interim installation has completed and the switch is running a version of Junos OS on one line that is compatible with satellite device conversion, perform the following steps:

1. Log in to the device by using the console port.

2. Clear the device:

[edit] user@satellite-device# request system zeroize

NOTE: The device reboots to complete the procedure for resetting the device.

If you are not logged in to the device by using the console port connection, your connection to the device is lost after you enter the request system zeroize command.

If you lose your connection to the device, log in using the console port.

3. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port port-number

For example, to convert all four built-in 40-Gbps QSFP+ interfaces on an EX4300-24P switch into network ports:

After this initial preparation, you can use one of three methods to convert your switches into satellite devices—autoconversion, manual conversion, and preconfiguration. See Configuring Junos Fusion Provider

Edge for detailed configuration steps for each method.

Converting a Satellite Device to a Standalone Device

If you need to convert a satellite device to a standalone device, you must install a new Junos OS software package on the satellite device and remove the satellite device from the Junos Fusion topology.

NOTE: If the satellite device is a QFX5100 switch, you need to install a PXE version of Junos

OS. The PXE version of Junos OS is software that includes pxe in the Junos OS package name when it is downloaded from the Software Center—for example, the PXE image for Junos OS Release 14.1X53-D43 is named install-media-pxe-qfx-5-14.1X53-D43.3-signed.tgz . If the satellite device is an EX4300 switch, you install a standard jinstall-ex-4300 version of Junos OS.

The following steps explain how to download software, remove the satellite device from Junos fusion, and install the Junos OS software image on the satellite device so that the device can operate as a standalone device.

1. Using a Web browser, navigate to the Junos OS software download URL on the Juniper Networks webpage:

https://www.juniper.net/support/downloads

2. Log in to the Juniper Networks authentication system by using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.

3. Select By Technology > Junos Platform > Junos Fusion from the drop-down list and select the switch platform series and model for your satellite device.

4. Select the Junos OS Release 14.1X53-D30 software image for your platform.

5. Review and accept the End User License Agreement.

6. Download the software to a local host.

7. Copy the software to the routing platform or to your internal software distribution site.

8. Remove the satellite device from the automatic satellite conversion configuration.

If automatic satellite conversion is enabled for the satellite device’s member number, remove the member number from the automatic satellite conversion configuration. The satellite device’s member number is the same as the FPC slot ID.

[edit] user@aggregation-device# delete chassis satellite-management auto-satellite-conversion

satellite member-number

For example, to remove member number 101 from Junos Fusion:

[edit] user@aggregation-device# delete chassis satellite-management auto-satellite-conversion

satellite 101

You can check the automatic satellite conversion configuration by entering the show command at the [edit chassis satellite-management auto-satellite-conversion] hierarchy level.

9. Commit the configuration.

To commit the configuration to both Routing Engines:

[edit] user@aggregation-device# commit synchronize

Otherwise, commit the configuration to a single Routing Engine:

[edit] user@aggregation-device# commit

10. Install the Junos OS software on the satellite device to convert the device to a standalone device.

[edit] user@aggregation-device> request chassis satellite install URL-to-software-package fpc-slot

member-number

For example, to install a PXE software package stored in the /var/tmp directory on the aggregation device onto a QFX5100 switch acting as the satellite device using FPC slot 101:

[edit] user@aggregation-device> request chassis satellite install

/var/tmp/install-media-pxe-qfx-5-14.1X53-D43.3-signed.tgz fpc-slot 101

For example, to install a software package stored in the var/tmp directory on the aggregation device onto an EX4300 switch acting as the satellite device using FPC slot 101:

[edit] user@aggregation-device> request chassis satellite install

/var/tmp/jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz fpc-slot 101

The satellite device stops participating in the Junos Fusion topology after the software installation starts. The software upgrade starts after this command is entered.

11. Wait for the reboot that accompanies the software installation to complete.

12. When you are prompted to log back into your device, uncable the device from the Junos Fusion topology. See Removing a Transceiver from a QFX Series Device or Remove a Transceiver, as needed. Your device has been removed from Junos Fusion.

NOTE: The device uses a factory-default configuration after the Junos OS installation is

complete.

Upgrading an Aggregation Device

When you upgrade an aggregation device to Junos OS Release 19.4R1, you must also upgrade your satellite device to Satellite Device Software version 3.1R1.

Upgrade and Downgrade Support Policy for Junos OS Releases

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.

For more information about EEOL releases and to review a list of EEOL releases, see

https://www.juniper.net/support/eol/junos.html.

Downgrading from Junos OS Release 19.4

To downgrade from Release 19.4 to another supported release, follow the procedure for upgrading, but replace the 19.4 jinstall package with one that corresponds to the appropriate release.

NOTE: You cannot downgrade more than three releases.

For more information, see the Installation and Upgrade Guide.

SEE ALSO

What's New | 71

What's Changed | 72

Known Limitations | 72

Open Issues | 73

Resolved Issues | 73

Documentation Updates | 74

Junos OS Release Notes for MX Series 5G Universal Routing Platform

IN THIS SECTION

What's New | 84

What's Changed | 105

Known Limitations | 109

Open Issues | 112

Resolved Issues | 129

Documentation Updates | 150

Migration, Upgrade, and Downgrade Instructions | 151

These release notes accompany Junos OS Release 19.4R1 for the MX 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

Hardware | 85

Class of Service | 88

EVPN | 88

Forwarding and Sampling | 89

General Routing | 90

High Availability (HA) and Resiliency | 90

Interfaces and Chassis | 90

Junos OS, XML, API, and Scripting | 93

Junos Telemetry Interface | 94

Layer 2 Features | 96

Layer 2 VPN | 96

MPLS | 96

Multicast | 97

Network Management and Monitoring | 98

OAM | 98

Routing Policy and Firewall Filters | 98

Routing Protocols | 99

Services Applications | 102

Software-Defined Networking | 102

Software Licensing | 103

Subscriber Management and Services | 103

System Logging | 104

Learn about new features introduced in Junos OS Release 19.4R1 for MX Series routers.

Hardware

MX-SPC3 Services Card (MX240, MX480, and MX960)—Starting with Junos OS Release 19.3R2, the

•

MX-SPC3 Services Card is available on MX240, MX480, and MX960 routers. The MX-SPC3 card provides additional processing power to run Next Gen Services. The MX-SPC3 contains two Services Processing Units (SPUs) with 128 GB of memory per SPU. Line cards such as DPCs, MICs, and MPCs intelligently distribute all traffic traversing the router to the SPUs to have services processing applied to it.

Next Gen Services provide the best of both routing and security features on MX Series routers MX240, MX480, and MX960. All Next Gen Services are provided by the MX-SPC3 services card Next Gen Services provide capabilities for manipulating traffic before it’s delivered to its destination. Next Gen Services features run on the MX Series, and are based on a different software architecture than legacy MX Series services. You can run Next Gen Services on MX240, MX480 and MX960 routers. Some Next Gen Services features use different Junos CLI statements than the equivalent legacy service.

NOTE: The only services card that supports Next Gen Services is the MX-SPC3. Next Gen

Services use their own software architecture, which is not compatible with legacy services.

Table 1 on page 86 summarizes the Next Gen Services supported in this release.

Table 1: Next Gen Services Summary

Next Gen Services Supported by MX-SPC3 Services Card

6rd SoftwiresCarrier Grade NAT

Deterministic NAT

Dynamic Address-Only Source NAT

Global System Logging

IPv4 Connectivity Across IPv6-Only Network Using 464XLAT

Network Address Port Translation

Port Forwarding

Stateful Firewall Services

Intrusion Detection Services

Traffic Load Balancing

DNS Request Filtering

Static Source NAT

Stateful NAT64

Static Destination NAT

Stateless Source Network Prefix Translation for IPv6

Twice NAPT

Twice Static NAT

Class of Service

Aggregated Multiservices Interfaces

NAT, Stateful Firewall, and IDS FlowsInter-chassis High Availability

Table 1: Next Gen Services Summary (continued)

Next Gen Services Supported by MX-SPC3 Services Card

See Protocols and Applications Supported by MX-SPC3 Services Card for information about the protocols and

applications that this SPC3 supports.

The MX-SPC3 services card is compatible end-to-end with the MX Series Switch Fabrics, Routing Engines and MS-MPC line cards. See Table 2 on page 87:

Table 2: MX-SPC3 Services Card Compatibility with MX Series Switch Fabrics, Routing Engines and MPC Line Cards

MPC Line CardsRoute EngineSwitch Fabric

SCBE

SCBE2

RE-S-1800X4-16G-UPG-BB

RE-S-1800X4-32G-UB

RE-S-1800X4-16G-UPG-BB

RE-S-1800X4-32G-UB

RE-S-X6-64G-UB

MPC2E-3D

MPC2-3D-NG

MPC3E and MPC3E-3D-NG

MPC4E-3D

MPC-3D-16XGE

MPC2E-3D

MPC2-3D-NG

MPC3E and MPC3E-3D-NG

MPC4E-3D

MPC5E and MPC5EQ

MPC7E, MPC7EQ, and

MPC-3D-16XGE

Refer to our TechLibrary for all MX router documentation. For Next Gen Services, refer to the following documentation: See

Next Gen Services Interfaces Overview for Routing Devices

•

Next Gen Services Interfaces User Guide for Routing Devices

•

Broadband Subscriber Services Feature Guide

•

Monitoring, Sampling, and Collection Services Interfaces Feature Guide

•

MX240 Universal Routing Platform Hardware Guide

•

MX480 Universal Routing Platform Hardware Guide

•

MX960 Universal Routing Platform Hardware Guide

•

MX Series 5G Universal Routing Platform Interface Module Reference

•

Class of Service

update-threshold statement modified to generate IGP update for lower bandwidth reservation (MX

•

Series)—Starting in Junos OS Release 19.4R1, you can configure the threshold value of the update-threshold statement to accept:

an integer or floating point values up to 3 significant digits after decimal point using the

•

threshold-percent option

an absolute value of bandwidth threshold which generates an IGP update using the threshold-value

•

option

These options are mutually exclusive and can be used for generating an IGP update for lower bandwidth reservations.

[See update-threshold.]

Support for seamless MPLS Layer 3 features (MX Series with MPC10E line cards)—Starting in Junos

•

OS Release 19.4R1, the following MPLS Layer 3 features are supported on MX Series routers with MPC10E line cards:

Redundant logical tunnel interfaces.

•

Pseudowire subscriber interfaces using logical tunnel or redundant logical tunnel interfaces as anchor

•

point.

[See Redundant Logical Tunnels Overview, and MPLS Pseudowire Subscriber Logical Interfaces.]

EVPN

Support for EVPN routing policies (ACX5448, EX4600, EX4650, EX9200, MX Series, QFX Series, and

•

Route distinguisher ID

•

NLRI route type

•

EVPN Ethernet tag

•

BGP path attributes

•

Ethernet segment identifier

•

MAC address on EVPN Type 2 routes

•

IP address on EVPN Type 2 and EVPN Type 5 routes

•

Extended community

•

[See Routing policies for EVPN.]

Exclusion list with MAC pinning in an EVPN network (EX9200 and MX Series)—When you enable

•

mac-pinning on an interface, all MAC addresses that are learned on that interface will be pinned and cannot be relearned on the other interfaces in the EVPN network. Starting in Junos OS Release 19.4R1, you can create a list of MAC addresses that would be excluded from being pinned and the MAC address can be moved and relearned on another interface within the EVPN network. While MAC pinning is configured on the interface, the exclusion list is configured for the device. To create an exclusion list, include a list of MAC addresses with the exclusive-mac parameter at the [edit protocols l2-learning global-mac-move] hierarchy level.

[See Creating exclusion list for MAC Pinning.]

Support for EVPN functionality (MX Series with MPC10 line card)—Starting in Junos OS 19.4R1, you

•

can configure MPC10 line cards on a MX Series router to support single-homed devices on an EVPN-MPLS network.

[See EVPN Multihoming Overview.]

Forwarding and Sampling

Inline monitoring services (MX Series with MPCs excluding MPC10E)—Starting in Junos OS Release

•

19.4R1, you can configure a new monitoring technology that provides the flexibility to monitor different streams of traffic at different sampling rates on the same interface. You can also export the packet up to the configured clip length to a collector in an IP Flow Information Export (IPFIX) format. The IPFIX format includes important metadata information about the monitored packets for further processing at the collector.

The inline monitoring services overcome the limitations of traditional sampling technologies, such as JFlow, sFlow, and port mirroring, thereby providing you the benefit of effective sampling and troubleshooting processes.

[See Inline Monitoring Services Configuration.]

Improved failover in conjunction with consistent load balancing for ECMP groups (MX Series routers

•

with MPCs)—Starting in Junos OS Release 19.4R1, we’ve added new functionality to prevent the reordering of flows to already active paths in an equal-cost multipath routing (ECMP) group if one or more path next-hops go down. Before this feature, when a server in the ECMP path failed, the flows directed to that server were redistributed to other, active links. If a second server in the ECMP path also went down, the newly redistributed traffic would be redistributed again, even though the ECMP path

is active. The improved failover and traffic rebalancing introduced in this release minimize the traffic redistribution when multiple servers in the ECMP path fail.

[See Configuring Consistent Load Balancing for ECMP Groups and Load Balance Traffic on MX Series

Routers.]

General Routing

Optimized BGP peer reestablishment (MX Series, PTX Series, and QFX Series)—Starting with Junos OS

•

Release 19.4R1, BGP peers in different groups can close in parallel. The connect/retry algorithm makes 16 attempts instead of 5 to reestablish BGP peers in the first 256 seconds after they go down. Peers can reestablish while cleanup of the Adj-RIB-In routes is in progress. If a peer comes back up before its route has been deleted from the routing table, that route is not deleted. The DeletePending flag in the show route detail and show route extensive command output indicates that a BGP route needs to be processed. PurgePending, PurgeInProgress, and PurgeImpatient flags in the show bgp neighbor command output show the status of the purge of routing table entries.

[See Understanding External BGP Peering Sessions, show bgp neighbor, show route detail, and show

route extensive.]

High Availability (HA) and Resiliency

View ISSU status during an upgrade (MX240, MX480, MX960, MX2010, MX2020, PTX3000, and

•

PTX5000)—Starting in Junos OS Release 19.4R1, you can use the request system software in-service-upgrade status command to display the status of a unified ISSU. You will need to run this

command on the Routing Engine where the unified ISSU was triggered to display the correct unified ISSU log file.

[See request system software in-service-upgrade.]

Interfaces and Chassis

Smart SFP transceivers for encapsulating and transporting PDH traffic (MX Series routers)—Starting

•

in Junos OS Release 19.4R1, on MX Series routers with MPCs (MPC1, MPC2, and MPC3) and MICs, you can configure and manage the following smart SFP transceivers to encapsulate PDH traffic:

DS3 smart SFP (SFP-GE-TDM-DS3)

•

E1 smart SFP (SFP-GE-TDM-E1)

•

T1 smart SFP (SFP-GE-TDM-T1)

•

The transceivers encapsulate PDH (E1 or T1 or DS3) packets as Ethernet frames while transporting legacy time division multiplexing (TDM) traffic over packet switched networks (PSNs). At the receiver end of the emulated circuit, another smart transceiver, paired with the first one and preconfigured to

carry packets that are in the same multicast MAC address group, de-encapsulates the Ethernet frames, rebuilds the TDM data stream, and forwards it onto the local TDM interface.

Support for 1-Gbps speed on 10-Gbps port (JNP10K-LC2101 line card on MX10008 and

•

MX10016)—Starting in Junos OS Release 19.4R1, you can configure the 10-Gigabit Ethernet port on the JNP10K-LC2101 line card to operate at 1-Gbps speed by using the speed statement at the [edit interfaces interfacename gigether-options] hierarchy level. After you commit the configuration, the operating speed of the 10-Gbps port changes to 1-Gbps speed.

To view the speed configured for the interface, use the show interfaces extensive command. The SpeedConfiguration field in the command output indicates the current operational speed of the interface. If the interface is configured with 1-Gbps speed, then the value of the SpeedConfiguration field is displayed as 1G; if the interface is configured with 10-Gbps speed, then SpeedConfiguration displays AUTO.

Autonegotiation is supported when the interface speed is configured for 1-Gbps speed.

NOTE: On the JNP10K-LC2101 line card, rate selectability at PIC level and port level does

not support 1-Gbps speed.

[See Introduction to Rate Selectability.]

Support for monitoring link degradation (MX Series routers with MPC7E, MPC8E, and MPC9E)—Starting

•

in Junos OS Release 19.4R1, you can monitor the quality of physical links on Ethernet Interfaces and take corrective action when the link quality degrades beyond a certain value. To enable your device to monitor the links, use the link-degrade-monitor statement at the [edit interfaces interface-name] hierarchy level. This feature monitors the bit error value (BER) of the link and initiates corrective action when the BER value crosses a user-configured threshold.

Starting in Junos OS Release 19.4R1, the following line cards support link degrade monitoring:

MPC7E (MPC7E-MRATE and MPC7E-10G (non-MACsec mode))

•

MPC8E (MIC-MRATE MICs)

•

MPC9E (MIC-MRATE MICs)

•

NOTE: Link degrade monitoring is not supported on the MACsec-enabled MPC7E-10G and

MIC-MACSEC-MRATE.

[See Link Degrade Monitoring Overview.]

Optimize fabric path to prevent traffic hop (MX2008, MX2010, and MX2020 with MPC9E)—Starting

•

in Junos OS Release 19.4R1, you can optimize the fabric path of the traffic flowing over abstracted fabric (af) interfaces between two guest network functions (GNFs) by configuring a fabric optimization mode.

This feature reduces fabric bandwidth consumption by preventing any additional fabric hop (switching of traffic flows from one Packet Forwarding Engine to another because of abstracted fabric interface load balancing) before the packets eventually reach the destination Packet Forwarding Engine.

To configure fabric optimization mode, use the following CLI commands at the base system (BSYS): set chassis network-slices guest-network-functions gnf id collapsed-forward <monitor | optimize>.

[See Optimizing Fabric Path for Abstracted Fabric Interface.]

SCBE3-MX interoperates with MPC 3D 16x10GE (MX240, MX480, and MX960)—Starting in Junos OS

•

Release 19.4R1, the Enhanced Switch Control Board SCBE3-MX (model number: SCBE3-MX-S) supports the 16-port 10-Gigabit Ethernet MPC (MPC 3D 16x10GE) on the MX240, MX480, and MX960 routers with enhanced midplane. The SCBE3-MX-S supports a pluggable Routing Engine and provides a control plane and data plane interconnect to each line card slot. The MPC 3D 16x10GE supports a fabric bandwidth of 160 Gbps.

[See SCBE3-MX Description and 16x10GE MPC.]

New universal PSM and PDM (MX2008, MX2010, and MX2020)—Starting in Release 19.4R1, Junos

•

OS supports the high-voltage second-generation universal power supply module (PSM; model number: MX2K-PSM-HV) and power distribution module (PDM; model number: MX2K-PDM-HV). The PSM has a main output and a standby output. The main output provides up to 3000 W power with a single feed, and up to 3400 W power with dual feeds. The standby output provides up to 30 W power. The PSM accepts either a AC input (voltage range: 180 VAC through 305 VAC) or DC input (voltage range: 190 VDC through 410 VDC). Each universal PDM has nine HVAC/HVDC inputs.

NOTE: We recommend that you use MX2K-PSM-HV PSM only with MX2K-PDM-HV PDM.

[See MX2010 Power System Description and MX2020 Power Subsystem Description.]

High-capacity second-generation AC PSM (MX960)—Starting in Release 19.4R1, Junos OS supports

•

the new high-capacity second-generation AC power supply module (PSM; model number: MX960-PSM-5K-AC-S) on MX960 routers. An enhanced version of the existing PSM used in the MX960 chassis, the new high-capacity PSM provides a maximum output power of 5100 W with dual feeds, and 2550 W with a single feed. The PSM supports a minimum input voltage of 180 VAC and a maximum input voltage of 264 VAC. The PSM supports 1+1 redundancy.

[See MX960 Power System Overview.]

Enhancement to increase the threshold of corrected single-bit errors (MPC7E, MPC8E, and MPC9E on

•

MX Series)—In Junos OS Release 19.4R1, the threshold of corrected single-bit errors is increased from 32 to 1024, and the alarm severity is changed from Major to Minor for those error messages. There is no operational impact upon corrected single-bit errors. Also, a log message is added to display how many single-bit errors have been corrected between the reported events as follows:

EA[0:0]: HMCIF Rx: Link0: Corrected single bit errordetected in HMC 0 - Total count 25

EA[0:0]: HMCIF Rx: Link0: Corrected single bit errordetected in HMC 0 - Total count 26

[See Alarm Overview.]

Junos OS, XML, API, and Scripting

Python 3 support for commit, event, op, and SNMP scripts (ACX Series, EX Series, MX Series, PTX

•

[See Understanding Python Automation Scripts for Devices Running Junos OS.]

Automation script library upgrades (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX

•

idna (2.8)

•

jinja2 (2.10.1)

•

jnpr.junos (Junos PyEZ) (2.2.0)

•

lxml (4.3.3)

•

markupsafe (1.1.1)

•

ncclient (0.6.4)

•

packaging (19.0)

•

paho.mqtt (1.4.0)

•

pyasn1 (0.4.5)

•

yaml (PyYAML package) (5.1)

•

[See Overview of Python Modules Available on Devices Running Junos OS.]

Support for 64-bit architecture added for use of management interface in a nondefault routing instance

•

in op scripts and JET applications (MX Series)—Junos OS Release 19.4R1 supports 64-bit architecture for Junos operating scripts and on-box JET applications being able to use the function

set_routing_instance() to program the protocol software (TCP/UDP) to use a nondefault routing instance instead of the default management routing interface.

[See set_routing_instance() Function (Python).]

Junos Telemetry Interface

•

Transceiver sensor support on JTI (MX960, MX2010, MX2020, PTX1000, PTX5000, PTX10000)—In Junos OS Release 19.4R1, you can use Junos telemetry interface (JTI) and remote procedure calls (gRPC) or gRPC Network Management Interface (gNMI) services to export transceiver statistics from MX960, MX2010, MX2020, PTX1000 and PTX5000 routers to outside collectors. This feature supports OpenConfig transceiver model openconfig-platform-transceiver.yang 0.5.0.

Both streaming and ON-CHANGE statistics are supported using the following base path:

/components/components/transceiver/

•

[See Understanding OpenConfig and gRPC on Junos Telemetry Interface and Guidelines for gRPC and

gNMI Sensors (Junos Telemetry Interface).]

•

Physical Ethernet interface sensor support on JTI (MX960, MX2020, PTX1000, PTX5000)—Starting in Junos OS Release 19.4R1, you can use Junos telemetry interface (JTI) and remote procedure calls (gRPC) services or gRPC Network Management Interface (gNMI) services to export physical Ethernet interface statistics from MX960, MX2020, PTX1000, and PTX5000 routers to outside collectors. This feature supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). Both streaming and ON-CHANGE statistics are supported using the following resource paths:

/interfaces/interface/ethernet/state/mac-address (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/auto-negotiate (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/duplex-mode (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/port-speed (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/enable-flow-control (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/hw-mac-address (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/negotiated-duplex-mode (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/negotiated-port-speed (with ON_CHANGE support)

•

/interfaces/interface/ethernet/state/counters/in-mac-control-frames

•

/interfaces/interface/ethernet/state/counters/in-mac-pause-frames

•

/interfaces/interface/ethernet/state/counters/in-oversize-frames

•

/interfaces/interface/ethernet/state/counters/in-jabber-frames

•

/interfaces/interface/ethernet/state/counters/in-fragment-frames

•

/interfaces/interface/ethernet/state/counters/in-8021q-frames

•

/interfaces/interface/ethernet/state/counters/in-crc-errors

•

/interfaces/interface/ethernet/state/counters/in-block-errors

•

/interfaces/interface/ethernet/state/counters/out-mac-control-frames

•

/interfaces/interface/ethernet/state/counters/out-mac-pause-frames

•

[See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

•

ON_CHANGE support for component sensors on JTI (MX960)—Junos OS Release 19.4R1 supports ON_CHANGE statistics for the following component sensors using Junos telemetry interface (JTI) and either remote procedure call (gRPC) services or gRPC Network Management Interface (gNMI) services. Junos OS releases before Release 19.4R1 support these component sensors on the MX960 router only to stream statistics.

/components/component

•

/components/component/name/

•

/components/component/state/type

•

/components/component/state/id

•

/components/component/state/description

•

/components/component/state/serial-no

•

/components/component/state/part-no

•

Streaming telemetry data through gRPC or gNMI requires the OpenConfig for Junos OS module.

[See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

Layer 2 Features

Support for an increase in MAC table size on the MPC10E-15C-MRATE line cards (MX Series)—Starting

•

in Junos OS Release 19.4R1, MX Series routers with MPC10E-15C-MRATE line cards support MAC table size of upto 1 million entries per PFE for Layer 2 services.

You can configure the MAC limit size at global level at the [edit protocols l2-learning global-mac-limit] hierarchy level.

You can also configure the MAC table size using bridge domains at the [edit bridge-domains bridge-domain-name bridge-options mac-table-size] hierarchy level.

[See Understanding Layer 2 Bridge Domains , Understanding Layer 2 Learning and Forwarding .]

Layer 2 VPN

Support for VPLS (MX series with MPC10 line card)—Starting in Junos OS 19.4R1, you can configure

•

VPLS on the MPC 10 line card in a MX Series router.

[See Introduction to VPLS and VPLS Configuration Overview.]

MPLS

Distributed CSPF for segment routing LSPs (MX Series)—Starting in Junos OS Release 19.4R1, you can

•

compute a segment routing LSP locally on the ingress device according to the constraints you have configured. With this feature, the LSPs are optimized based on the configured constraints and metric type. The LSPs are computed to utilize the available ECMP paths to the destination.

Prior to Junos OS Release 19.4R1, for traffic engineering of segment routing paths, you could either explicitly configure static paths, or use computed paths from an external controller.

[See Enabling Distributed CSPF for Segment Routing LSPs.]

Color-based mapping of VPN services over SRTE (MX Series)—Starting in Junos OS Release 19.4R1,

•

you can specify a color attribute along with an IP protocol next hop to resolve transport tunnels over static colored and BGP segment routing traffic-engineered (SRTE) label-switched paths (LSPs). This is called the color-IP protocol next hop resolution, where you are required to configure a resolution-map and apply it to the VPN services. Prior to this release, the VPN services were resolved over IP protocol next hops only.

With this feature, you can enable color-based traffic steering of Layer 2 and Layer 3 VPN services.

[See Color-Based Mapping of VPN Services Overview.]

Support for static adjacency segment identifier for aggregated Ethernet member links on

•

MPC10E-15C-MRATE line cards (MX240, MX480, and MX960)—Starting with Junos OS Release 19.4R1, you can configure a transit single-hop static label-switched path (LSP) for a specific member link of an aggregated Ethernet (ae) interface. The label for this route comes from the segment routing local block

(SRLB) pool of the configured static label range. Configure the ae member interface name using the

member-interface statement option at the [edit protocols mpls static-label-switched-path name transit name] hierarchy level. This feature is supported for ae interfaces only.

[See transit and Configuring Static Adjacency Segment Identifier for Aggregate Ethernet Member Links

Using Single-Hop Static LSP.]

Multicast

Next-generation multicast VPN supported on MPC10E-15C-MRATE line cards (MX240, MX480, and

•

MX960)—Starting in Junos OS Release 19.4R1, the MPC10E-15C-MRATE line card supports next-generation MVPN.

[See Multicast Overview.]

Continuous, persistent IGMP and MLD statistics (MX Series)—Starting in Junos OS Release 19.4R1, in

•

addition to collecting statistics on IGMP and MLD control traffic for currently active subscribers, MX Series routers also collect and maintain cumulative and persistent statistics that account for both past and current subscribers. The device stores these statistics and copies them to the backup Routing Engine at a configurable interval, so this information is preserved across routing daemon restarts, graceful Routing Engine switchovers (GRES), in-service software upgrade (ISSU) operations, or line card reboots. Use the continuous option with the show igmp statistics or show mld statistics command to view continuous statistics; without this option, you see default statistics only for currently active subscribers.

[See show igmp statistics or show mld statistics.]

Network Management and Monitoring

Packet mirroring with Layer 2 headers for Layer 3 forwarded traffic (MX Series routers with MPCs or

•

MICs)—Starting in Junos OS Release 19.4R1, you can enable port mirroring at packet level along with Layer 2 headers even if the filters are installed with Layer 3 match actions. Use the new firewall-filter action l2-mirror at the [edit firewall family inet|inet6 filter filter-name term tcp-flags then] hierarchy level to request Layer 2 header reporting.

OAM

Support for Ethernet OAM and Metro Ethernet services over segment routing (ACX5448-D, ACX5448-M,

•

MX Series)—Starting with Junos OS Release 19.4R1, ACX5448-D, ACX5448-M and MX Series routers support Ethernet OAM and Metro Ethernet services over segment routing.

Routing Policy and Firewall Filters

Support for firewall forwarding on MPC10E line cards (MX240, MX480, and MX960)—Starting in Junos

•

OS Release 19.4R1, the following traffic policers are fully supported on MX240, MX480, and MX960 routers with MPC10E line cards:

GRE tunnels, including encapsulation (family any), decapsulation, GRE-in-UDP over IPv6, and the

•

following sub-options: sample, forwarding class, interface group, and no-ttl-decrement

Input and output filter chains

•

Actions, including policy-map filters, do-not-fragment, and prefix

•

Layer 2 policers

•

Policer overhead adjustment

•

Hierarchical policers

•

Shared bandwidth

•

Percentages

•

Logical interfaces

•

[See Traffic Policer Types.]

GTP load balancing on MPC10E-15C-MRATE line cards (MX240, MX480, and MX960)—Starting in

•

Junos OS Release 19.4R1, the MPC10E-15C-MRATE line card supports GPRS tunneling protocol (GTP) load balancing.

Junos OS 19.4R1 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

SUPPORTED ON

Contents

Introduction

Junos OS Release Notes for ACX Series

What's New

EVPN

Junos OS XML API and Scripting

MPLS

Routing Protocols

System Logging

Software Defined Networking (SDN)

What's Changed

General Routing

Routing Protocols

Known Limitations

General Routing

Open Issues

General Routing

Resolved Issues

General Routing

Layer 2 Ethernet Services

Platform and Infrastructure

Routing Protocols

Documentation Updates

Feature Guides Are Renamed As User Guides

Migration, Upgrade, and Downgrade Instructions

Upgrade and Downgrade Support Policy for Junos OS Releases

Junos OS Release Notes for EX Series Switches

What's New

Authentication, Authorization, and Accounting

Class of Service

EVPN

Junos OS XML, API, and Scripting

Junos Telemetry Interface

Layer 2 Features

MPLS

Multicast

Operation, Administration, and Maintenance (OAM)

Port Security

Routing Policy and Firewall Filters

System Logging

System Management

User Interface and Configuration

What's Changed

What’s Changed in Release 19.4R1-S3

General Routing

What's Changed in Release 19.4R1

General Routing

Interfaces and Chassis

Routing Protocols

Known Limitations

Open Issues

Authentication and Access Control

Class of Service (CoS)

EVPN

General Routing

Infrastructure

Interfaces and Chassis

Junos Fusion Enterprise

Junos Fusion Satellite Software

Layer 2 Ethernet Services

Layer 2 Features

Platform and Infrastructure

Routing Protocols

User Interface and Configuration

Resolved Issues

Authentication and Access Control

EVPN

General Routing

Infrastructure

Interfaces and Chassis

Junos Fusion Enterprise

Junos Fusion Satellite Software

J-Web

Layer 2 Ethernet Services

Layer 2 Features