Release Notes: Junos®OS Release 18.1R3 for
the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and
Junos Fusion
1
13 January 2021
Contents
Introduction | 12
Junos OS Release Notes for ACX Series | 12
New and Changed Features | 13
Release 18.1R3 New and Changed Features | 13
Release 18.1R2 New and Changed Features | 13
Release 18.1R1 New and Changed Features | 13
Changes in Behavior and Syntax | 14
Interfaces and Chassis | 14
Known Behavior | 15
Known Issues | 15
Resolved Issues | 16
Resolved Issues: 18.1R3 | 16
Resolved Issues: 18.1R2 | 16
Resolved Issues: 18.1R1 | 17
Documentation Updates | 18
New Simplified Documentation Architecture | 18
Migration, Upgrade, and Downgrade Instructions | 19
Upgrade and Downgrade Support Policy for Junos OS Releases | 19
Product Compatibility | 20
Hardware Compatibility | 20
Junos OS Release Notes for EX Series Switches | 21
New and Changed Features | 21
Release 18.1R3-S3 New and Changed Features | 22
Release 18.1R3 New and Changed Features | 23
Release 18.1R2 New and Changed Features | 23
Release 18.1R1 New and Changed Features | 25
Changes in Behavior and Syntax | 30
Release 18.1R3-S10 Changes in Behavior and Syntax | 31
Release 18.1R3-S7 Changes in Behavior and Syntax | 31
Release 18.1R3 Changes in Behavior and Syntax | 32
Release 18.1R2 Changes in Behavior and Syntax | 34
Release 18.1R1 Changes in Behavior and Syntax | 34
2
Known Behavior | 35
Infrastructure | 36
Interfaces and Chassis | 36
Platform and Infrastructure | 36
Virtual Chassis | 37
Known Issues | 37
General Routing | 38
Infrastructure | 39
Layer 2 Features | 39
Platform and Infrastructure | 39
Resolved Issues | 40
Resolved Issues: 18.1R3 | 40
Resolved Issues: 18.1R2 | 42
Resolved Issues: 18.1R1 | 44
Documentation Updates | 48
New Simplified Documentation Architecture | 48
Migration, Upgrade, and Downgrade Instructions | 49
Upgrade and Downgrade Support Policy for Junos OS Releases | 49
Product Compatibility | 50
Hardware Compatibility | 50
Junos OS Release Notes for Junos Fusion Data Center | 51
New and Changed Features | 52
Release 18.1R3 New and Changed Features | 53
Release 18.1R2-S2 New and Changed Features | 53
Release 18.1R2 New and Changed Features | 57
Release 18.1R1 New and Changed Features | 57
Changes in Behavior and Syntax | 58
Known Behavior | 58
Junos Fusion Data Center | 59
Known Issues | 61
Junos Fusion Data Center | 61
Resolved Issues | 62
Resolved Issues: 18.1R3 | 62
Resolved Issues: 18.1R2 | 62
3
Resolved Issues: 18.1R1 | 63
Documentation Updates | 63
New Simplified Documentation Architecture | 63
Migration, Upgrade, and Downgrade Instructions | 64
Basic Procedure for Upgrading an Aggregation Device | 64
Preparing the Switch for Satellite Device Conversion | 66
Configuring Satellite Device Upgrade Groups | 68
Converting a Satellite Device to a Standalone Device | 69
Upgrade and Downgrade Support Policy for Junos OS Releases | 70
Downgrading from Junos OS Release 18.1 | 70
Product Compatibility | 71
Hardware and Software Compatibility | 71
Hardware Compatibility Tool | 71
Junos OS Release Notes for Junos Fusion Enterprise | 72
New and Changed Features | 72
Release 18.1R3 New and Changed Features | 73
Release 18.1R2 New and Changed Features | 73
Release 18.1R1 New and Changed Features | 73
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Junos Fusion Enterprise | 75
Resolved Issues | 76
Resolved Issues: 18.1R3 | 76
Resolved Issues: 18.1R2 | 76
Resolved Issues: 18.1R1 | 77
Documentation Updates | 77
New Simplified Documentation Architecture | 77
Migration, Upgrade, and Downgrade Instructions | 78
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 79
Upgrading an Aggregation Device with Redundant Routing Engines | 81
Preparing the Switch for Satellite Device Conversion | 81
Converting a Satellite Device to a Standalone Switch | 83
Upgrade and Downgrade Support Policy for Junos OS Releases | 83
4
Downgrading Junos OS | 83
Product Compatibility | 84
Hardware and Software Compatibility | 84
Hardware Compatibility Tool | 84
Junos OS Release Notes for Junos Fusion Provider Edge | 86
New and Changed Features | 86
Release 18.1R3 New and Changed Features | 88
Release 18.1R2 New and Changed Features | 88
Release 18.1R1 New and Changed Features | 88
Changes in Behavior and Syntax | 89
Known Behavior | 90
Junos Fusion | 90
Known Issues | 91
Junos Fusion | 91
Resolved Issues | 92
Resolved Issues: 18.1R3 | 92
Resolved Issues: 18.1R2 | 92
Resolved Issues: 18.1R1 | 93
Documentation Updates | 93
New Simplified Documentation Architecture | 94
Migration, Upgrade, and Downgrade Instructions | 94
Basic Procedure for Upgrading an Aggregation Device | 95
Upgrading an Aggregation Device with Redundant Routing Engines | 97
Preparing the Switch for Satellite Device Conversion | 98
Converting a Satellite Device to a Standalone Device | 99
Upgrading an Aggregation Device | 99
Upgrade and Downgrade Support Policy for Junos OS Releases | 99
Downgrading from Junos OS Release 18.1 | 100
Product Compatibility | 101
Hardware Compatibility | 101
Junos OS Release Notes for MX Series 5G Universal Routing Platforms | 102
New and Changed Features | 102
Release 18.1R3-S3 New and Changed Features | 103
Release 18.1R3 New and Changed Features | 104
5
Release 18.1R2 New and Changed Features | 104
Release 18.1R1 New and Changed Features | 104
Changes in Behavior and Syntax | 123
Release 18.1R3-S5 Changes in Behavior and Syntax | 123
Release 18.1R3 Changes in Behavior and Syntax | 123
Release 18.1R2 Changes in Behavior and Syntax | 127
Release 18.1R1 Changes in Behavior and Syntax | 128
Known Behavior | 132
EVPN | 133
General Routing | 133
Interfaces and Chassis | 134
MPLS | 135
Platform and Infrastructure | 135
Routing Protocols | 135
Services Applications | 135
Software Installation and Upgrade | 136
Subscriber Management and Services | 137
Known Issues | 137
Class of Service(CoS) | 138
EVPN | 138
Forwarding and Sampling | 139
General Routing | 139
Infrastructure | 144
Interfaces and Chassis | 144
Layer 2 Ethernet Services | 145
Layer 2 Features | 146
MPLS | 146
Platform and Infrastructure | 147
Routing Protocols | 150
Services Applications | 151
Software Installation and Upgrade | 151
Subscriber Management and Services | 152
VPNs | 152
Resolved Issues | 153
6
Resolved Issues: 18.1R3 | 153
Resolved Issues: 18.1R2 | 164
Resolved Issues: 18.1R1 | 171
Documentation Updates | 189
New Simplified Documentation Architecture | 189
Subscriber Management Access Network Guide | 189
Subscriber Management Provisioning Guide | 190
Migration, Upgrade, and Downgrade Instructions | 190
Basic Procedure for Upgrading to Release 18.1 | 191
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 191
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 194
Upgrade and Downgrade Support Policy for Junos OS Releases | 196
Upgrading a Router with Redundant Routing Engines | 196
Downgrading from Release 18.1 | 196
Product Compatibility | 197
Hardware Compatibility | 197
Junos OS Release Notes for NFX Series | 198
New and Changed Features | 199
Release 18.1R3 New and Changed Features | 199
Release 18.1R2 New and Changed Features | 199
Release 18.1R1 New and Changed Features | 199
Changes in Behavior and Syntax | 203
CLI | 204
Known Behavior | 204
Known Behavior: 18.1R3 | 205
Known Issues | 206
Known Issues: 18.1R3 | 206
Resolved Issues | 209
Resolved Issues: 18.1R3 | 209
Resolved Issues: 18.1R2 | 209
Resolved Issues: 18.1R1 | 210
Documentation Updates | 211
New Simplified Documentation Architecture | 211
Migration, Upgrade, and Downgrade Instructions | 212
7
Upgrade and Downgrade Support Policy for Junos OS Releases | 212
Basic Procedure for Upgrading to Release 18.1 | 212
Product Compatibility | 215
Hardware Compatibility | 215
Software Version Compatibility | 216
Junos OS Release Notes for PTX Series Packet Transport Routers | 218
New and Changed Features | 218
Release 18.1R3 New and Changed Features | 219
Release 18.1R2 New and Changed Features | 219
Release 18.1R1 New and Changed Features | 219
Changes in Behavior and Syntax | 227
Interfaces and Chassis | 227
Management | 229
Network Management and Monitoring | 229
Network Operations and Troubleshooting Automation | 229
Subscriber Management and Services | 230
Known Behavior | 231
General Routing | 231
Interfaces and Chassis | 232
Known Issues | 232
General Routing | 233
Infrastructure | 235
Interfaces and Chassis | 235
MPLS | 235
Resolved Issues | 235
Resolved Issues: 18.1R3 | 236
Resolved Issues: 18.1R2 | 237
Resolved Issues: 18.1R1 | 238
Documentation Updates | 241
New Simplified Documentation Architecture | 241
Migration, Upgrade, and Downgrade Instructions | 242
Upgrade and Downgrade Support Policy for Junos OS Releases | 242
Upgrading a Router with Redundant Routing Engines | 243
8
Basic Procedure for Upgrading to Junos OS Release 18.1 | 243
Product Compatibility | 247
Hardware Compatibility | 247
Junos OS Release Notes for the QFX Series | 248
New and Changed Features | 248
Release 18.1R3-S3 New and Changed Features | 249
Release 18.1R3 New and Changed Features | 252
Release 18.1R2 New and Changed Features | 254
Release 18.1R1 New and Changed Features | 255
Changes in Behavior and Syntax | 273
| 273
Known Behavior | 276
EVPN | 276
Interfaces and Chassis | 276
Layer 2 Features | 277
Multicast | 277
Platform and Infrastructure | 277
Routing Protocols | 280
Storage and Fibre Channel | 281
Virtual Chassis | 281
Services Applications | 281
Known Issues | 282
EVPN | 282
Interfaces and Chassis | 283
Layer 2 Features | 283
MPLS | 283
Platform and Infrastructure | 284
Routing Protocols | 286
Resolved Issues | 287
Resolved Issues: 18.1R3 | 288
Resolved Issues: 18.1R2 | 291
Resolved Issues: 18.1R1 | 294
Documentation Updates | 299
New Simplified Documentation Architecture | 299
9
Migration, Upgrade, and Downgrade Instructions | 300
Upgrading Software on QFX Series Switches | 301
Installing the Software on QFX10002-60C Switches | 303
Installing the Software on QFX10002 Switches | 303
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 | 304
Installing the Software on QFX10008 and QFX10016 Switches | 306
Performing a Unified ISSU | 310
Preparing the Switch for Software Installation | 311
Upgrading the Software Using Unified ISSU | 311
Upgrade and Downgrade Support Policy for Junos OS Releases | 313
Product Compatibility | 314
Hardware Compatibility | 314
Junos OS Release Notes for SRX Series | 315
New and Changed Features | 316
Release 18.1R3 New and Changed Features | 316
Release 18.1R2 New and Changed Features | 316
Release 18.1R1 New and Changed Features | 317
Changes in Behavior and Syntax | 323
Chassis Cluster | 323
Juniper Sky ATP | 323
VPN | 323
Known Behavior | 324
Chassis Clustering | 324
J-Web | 324
Platform and Infrastructure | 325
Software Installation and Upgrade | 325
User Interface and Configuration | 325
VPNs | 325
Known Issues | 326
Application Layer Gateways (ALGs) | 326
10
Chassis Clustering | 327
Class of Service (CoS) | 327
Flow-based and Packet-based Processing | 327
Interfaces and Routing | 328
Intrusion Detection and Prevention (IDP) | 328
Platform and Infrastructure | 328
Routing Policy and Firewall Filters | 329
Routing Protocols | 329
Software Installation and Upgrade | 329
VPNs | 329
Software Installation and Upgrade | 330
VPNs | 330
Resolved Issues | 330
Resolved Issues: 18.1R3 | 331
Resolved Issues: 18.1R2 | 333
Resolved Issues: 18.1R1 | 335
Documentation Updates | 341
New Simplified Documentation Architecture | 342
Migration, Upgrade, and Downgrade Instructions | 343
Upgrade and DowngradeSupport Policy for Junos OS Releases and Extended End-Of-Life
Releases | 343
Product Compatibility | 344
Hardware Compatibility | 344
Upgrading Using ISSU | 345
Compliance Advisor | 345
Finding More Information | 345
Documentation Feedback | 346
Requesting Technical Support | 347
Self-Help Online Tools and Resources | 347
Creating a Service Request with JTAC | 348
Revision History | 348
11
Introduction
Junos OS runs on the following Juniper Networks®hardware: ACX Series, EX Series, M Series, MX Series,
NFX Series, PTX Series, QFabric systems, QFX Series, SRX Series, T Series, and Junos Fusion.
These release notes accompany Junos OS Release 18.1R3 for the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and Junos Fusion. They describe new and changed features,
limitations, and known and resolved problems in the hardware and software.
Junos OS Release Notes for ACX Series
IN THIS SECTION
12
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Known Issues | 15
Resolved Issues | 16
Documentation Updates | 18
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
These release notes accompany Junos OS Release 18.1R3 for the ACX Series. They describe new and
changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located
at https://www.juniper.net/documentation/product/en_US/junos-os.
New and Changed Features
IN THIS SECTION
Release 18.1R3 New and Changed Features | 13
Release 18.1R2 New and Changed Features | 13
Release 18.1R1 New and Changed Features | 13
This section describes the features and enhancements in Junos OS Release 18.1R3 for ACX Series routers.
Release 18.1R3 New and Changed Features
There are no new features or enhancements to existing features for ACX Series Universal Metro Routers
in Junos OS Release 18.1R3.
13
Release 18.1R2 New and Changed Features
There are no new features or enhancements to existing features for ACX Series Universal Metro Routers
in Junos OS Release 18.1R2.
Release 18.1R1 New and Changed Features
Management
Support for NETCONF over SSH and custom YANG models (ACX Series)—Starting in Junos OS Release
•
18.1R1, ACX Series routers support NETCONF OVER SSH and custom YANG models.
Client applications can access the NETCONF server using the SSH protocol and use the standard SSH
authentication mechanism. After authentication, the NETCONF server uses the configured Junos OS
login usernames and classes to determine whether a client application is authorized to make each request.
You can load custom YANG models on the router to add data models that are not natively supported
by Junos OS but can be supported by translation. Doing this enables you to extend the configuration
hierarchies and operational commands with data models that are customized for your operations. You
can load custom YANG modules by using the request system yang add operational command.
[See Understanding the Management of Nonnative YANG Modules on Devices Running Junos OS.]
SEE ALSO
Changes in Behavior and Syntax | 14
Known Behavior | 15
Documentation Updates | 18
Known Issues | 15
Resolved Issues | 16
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Changes in Behavior and Syntax
IN THIS SECTION
Interfaces and Chassis | 14
14
This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS
statements and commands from Junos OS Release 18.1R3 for the ACX Series routers.
Interfaces and Chassis
Modified output of show-ptp-clock command (QFX Series switches)—Starting in Junos OS Release
•
18.1R1, the output of the show-ptp-clock command is modified to display the value of the GMC Class
field as 248 for a PTP boundary clock when the lock state of the clock is Acquiring.
SEE ALSO
New and Changed Features | 13
Known Behavior | 15
Documentation Updates | 18
Known Issues | 15
Resolved Issues | 16
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Known Behavior
There are no known limitations in Junos OS Release 18.1R3 for the ACX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Documentation Updates | 18
Known Issues | 15
Resolved Issues | 16
15
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Known Issues
There are no known issues in hardware and software in Junos OS Release 18.1R3 for the ACX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Documentation Updates | 18
Resolved Issues | 16
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Resolved Issues
IN THIS SECTION
Resolved Issues: 18.1R3 | 16
Resolved Issues: 18.1R2 | 16
Resolved Issues: 18.1R1 | 17
This section lists the issues fixed in the Junos OS main release and the maintenance releases.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
16
Resolved Issues: 18.1R3
There are no resolved issues in Junos OS 18.1R3 Release for ACX Series routers.
Resolved Issues: 18.1R2
There are no resolved issues in Junos OS 18.1R2 Release for ACX Series routers.
Resolved Issues: 18.1R1
Alarms
The major alarm about Fan & PSU Airflow direction mismatch was seen by removing management cable
•
PR1327561
Dynamic Host Configuration Protocol
ACX5000 line of routers did not forward DHCP-RELAY requests with IRB interface after upgrade.
•
PR1243687
Firewall Filters
On ACX Series routers, syslog error was seen on the output/egress firewall filter. PR1316588
•
Installation and Upgrade
fxpc core was observed during ISSU upgrade. PR1318771
•
Layer 2 Features
17
On ACX5000 line of routers, transit ARP packets were being punted to the RE. PR1263012
•
VPN
On ACX5000 line of routers, memory leak was seen during Layer 3 VPN scaling test when committing
•
Layer 3 VPN configuration. PR1115686
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Documentation Updates | 18
Known Issues | 15
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Documentation Updates
IN THIS SECTION
New Simplified Documentation Architecture | 18
This section lists the errata and changes in Junos OS Release 18.1R3 for the ACX Series documentation.
New Simplified Documentation Architecture
With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make
•
it easier for you to find information and know that you can rely on it when you find it. In the past, we
organized documentation about Junos OS software features into platform-specific documents. In many
cases, features are supported on multiple platforms, so you might not easily find the document you want
for your platform.
18
With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For
example, if you want to find documentation on OSPF, there is only one document regardless of which
platform you have. Here are some of the benefits of our new simplified architecture:
Over time, you will see better search results when looking for Juniper documentation. You will be able
•
to find what you want faster and be assured that is the right document.
If a software feature is supported on multiple platforms, you can find information about all the platforms
•
in one place.
Because we have eliminated many documents that covered similar topics, you will now find one
•
document with all the information.
You can know that you are always getting the most current and accurate information.
•
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Known Issues | 15
Resolved Issues | 16
Migration, Upgrade, and Downgrade Instructions | 19
Product Compatibility | 20
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Upgrade and Downgrade Support Policy for Junos OS Releases | 19
This section contains the upgrade and downgrade support policy for Junos OS for the ACX Series routers.
Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration
of the network.
19
For information about software installation and upgrade, see the Installation and Upgrade Guide.
Upgrade and Downgrade Support Policy for Junos OS Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not
provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases
provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the
next EEOL release even though EEOL releases generally occur in increments beyond three releases.
You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently
installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1,
17.2 and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from
Junos OS Release 17.1 to Release 17.3.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead
or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before
or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release
to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see
https://www.juniper.net/support/eol/junos.html.
For information about software installation and upgrade, see the Installation and Upgrade Guide.
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Documentation Updates | 18
Known Issues | 15
Resolved Issues | 16
Product Compatibility | 20
Product Compatibility
IN THIS SECTION
20
Hardware Compatibility | 20
Hardware Compatibility
To obtain information about the components that are supported on the devices, and the special compatibility
guidelines with the release, see the Hardware Guide for the product.
To determine the features supported on ACX Series routers in this release, use the Juniper Networks
Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature
information to find the right software release and hardware platform for your network. Find Feature
Explorer at https://pathfinder.juniper.net/feature-explorer/.
Hardware Compatibility Tool
For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms,
see the Hardware Compatibility tool.
SEE ALSO
New and Changed Features | 13
Changes in Behavior and Syntax | 14
Known Behavior | 15
Documentation Updates | 18
Known Issues | 15
Resolved Issues | 16
Migration, Upgrade, and Downgrade Instructions | 19
Junos OS Release Notes for EX Series Switches
IN THIS SECTION
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Behavior | 35
21
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
These release notes accompany Junos OS Release 18.1R3 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.
New and Changed Features
IN THIS SECTION
Release 18.1R3-S3 New and Changed Features | 22
Release 18.1R3 New and Changed Features | 23
Release 18.1R2 New and Changed Features | 23
Release 18.1R1 New and Changed Features | 25
This section describes the new features and enhancements to existing features in the Junos OS main
release and the maintenance releases for EX Series.
NOTE: The following EX Series switches are supported in Release 18.1R3: EX2300, EX3400,
EX4300, EX4600, and EX9200.
NOTE: In Junos OS Release 18.1R3, J-Web is supported on the EX2300, EX3400, EX4300, and
EX4600 switches in both standalone and Virtual Chassis setup.
22
The J-Web distribution model being used provides two packages:
Platform package—Installed as part of Junos OS; provides basic functionalities of J-Web.
•
Application package—Optionally installable package; provides complete functionalities of
•
J-Web.
For details about the J-Web distribution model, see J-Web Application Package Release 18.1A1
for EX2300, EX3400, EX4300, and EX4600 Switches.
Release 18.1R3-S3 New and Changed Features
EVPNs
Support for VMTO for ingress traffic (EX9200)—Starting in Junos OS Release 18.1R3-S3, you can
•
configure the PE device to support virtual machine traffic optimization (VMTO) for ingress traffic. VMTO
eliminates the unnecessary ingress routing to default gateways when a virtual machine is moved from
one data center to another.
To enable VMTO, configure remote-ip-host routes in the [edit routing-instances routing-instance-name
protocols evpn] hierarchy level. You can also filter out the unwanted routes by configuring an import
policy under the remote-ip-host routes option.
[See Configuring EVPN Routing Instances.]
Support for Multihomed Proxy Advertisement (EX9200)—Junos now provides enhanced support to
•
proxy advertise the Mac address and IP route entry from all PEs that are multi-homed to a CE device.
This can prevent traffic loss when one of the links to the PE fails. To support the multihomed proxy
advertisement, all multi-homed PE devices should have the same multihomed proxy advertisement bit
value. The multihomed proxy advertisement feature is enabled by default and Junos uses the default
multihomed proxy advertisement bit value of 0x20.
[See EVPN Multihoming Overview.]
Support for OSPF, IS-IS, BGP, and static routing on IRB interfaces in EVPN-VXLAN networks
•
(EX9200)—Starting in Junos OS Release 18.1R3-S3, you can configure OSPF, IS-IS, BGP, and static
routing with bidirectional forwarding detection (BFD) on an IRB interface that is used as a routed interface
in EVPN. This allows protocol adjacencies to be established between an IRB on a Layer 3 gateway and
a CE device connected directly to a Layer 3 gateway or to a Layer 2 leaf device in an EVPN-VXLAN
network.
[See Supported Protocols on an IRB Interface in EVPN-VXLAN .]
Release 18.1R3 New and Changed Features
23
There are no new features or enhancements to existing features for EX Series switches in Junos OS
•
Release 18.1R3.
Release 18.1R2 New and Changed Features
Hardware
EX2300-24MP and EX2300-48MP switches—Starting with Junos OS Release 18.1R2, two new models
•
of EX2300 switches—EX2300-24MP and EX2300-48MP—are available. EX2300-24MP switch models
have eight 100/1000/2500 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, 16 10/100/1000
BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, and four built-in 10-Gigabit Ethernet uplink
ports. EX2300-48MP switch models have 16 100/1000/2500 BASE-T Gigabit Ethernet ports with
PoE/PoE+ capability, 32 10/100/1000 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, and
six built-in 10-Gigabit Ethernet uplink ports.
[See EX2300 Switch Hardware Guide.]
Interfaces and Chassis
Support for Multi-Gigabit Ethernet (EX2300)—Starting in Junos OS Release 18.1R2, the Multi-Gigabit
•
Ethernet feature is supported on EX2300-48MP and EX2300-24MP switches. This feature fulfills the
high-speed requirements for a large and mid-size campus, and branch locations for the enterprise
customers.
The mge interface is a rate-selectable (multirate) Gigabit Ethernet interface that can support speeds of
10 Gbps, 5 Gbps, and 2.5 Gbps over CAT5e/CAT6/CAT6a cables. In the EX2300, the mge interface
supports 100 Mbps, 1 Gbps, and 2.5 Gbps speeds, which can be configured by using the speed
configuration statement.
NOTE: Power over Ethernet (PoE) is supported on Multi-Gigabit Ethernet interfaces. PoE
enables EX2300 switches to transfer electrical power through an Ethernet cable. PoE enables
electric power, along with data, to be passed over a copper Ethernet LAN cable.
[See Speed.]
Support for Power over Ethernet (EX2300-24MP and EX2300-48MP)—Starting in Junos OS Release
•
18.1R2, Power over Ethernet (PoE) is supported on EX2300-24MP and EX2300-48MP switch models,
including multigigabit interfaces. (PoE) permits electric power, along with data, to be passed over a
copper Ethernet LAN cable.
EX2300 24MP switches support PoE (IEEE 802.3af) and PoE+ (IEEE 802.at) and can simultaneously
deliver up to 15.4 watts of standards-based 802.3af Class 3 PoE to a maximum of 24 ports or 30 watts
of standards-based 802.3at PoE+ to a maximum of 12 ports, based on a total system budget of 380
watts.
EX2300 48MP switches support PoE (IEEE 802.3af) and PoE+ (IEEE 802.at) and can simultaneously
deliver up to 15.4 watts of standards-based 802.3af Class 3 PoE to a maximum of 48 ports or 30 watts
of standards-based 802.3at PoE+ to a maximum of 24 ports, based on a total system budget of 740
watts.
24
[See Understanding PoE on EX Series Switches.]
Restoration Procedures Failure
Device recovery mode introduced in Junos OS with upgraded FreeBSD (EX Series)—In Junos OS Release
•
18.1R2, for devices running Junos OS with upgraded FreeBSD, provided you have saved a rescue
configuration on the device, there is an automatic device recovery mode that goes into action should
the system go into amnesiac mode.The new process is for the system to automatically retry to boot with
the saved rescue configuration. In this circumstance, the system displays a banner "Device is in recovery
mode” in the CLI (in both the operational and configuration modes). Previously, there was no automatic
process to recover from amnesiac mode. A user with load and commit permission had to log in using
the console and fix the issue in the configuration before the system would reboot.
[See Saving a Rescue Configuration File.]
Virtual Chassis
Virtual Chassis support (EX2300-24MP and EX2300-48MP)—Starting in Junos OS Release 18.1R2,
•
multigigabit EX2300 switches can be interconnected into a Virtual Chassis and operate as one logical
device managed as a single chassis, as follows:
Members can be any combination of up to four EX2300-24MP and EX2300-48MP switches.
•
Multigigabit EX2300 switches cannot be mixed with any other switch models (including any other
•
EX2300 switches) in the same Virtual Chassis.
Any 10-Gbps uplink ports installed with SFP+ transceivers can be configured as Virtual Chassis ports
•
(VCPs) to interconnect the members. Multigigabit EX2300 switches do not have any dedicated or
default-configured VCPs.
To configure a multigigabit EX2300 Virtual Chassis, use similar steps as for configuring other EX Series
and QFX Series Virtual Chassis.
[See Understanding EX2300 Virtual Chassis.]
Release 18.1R1 New and Changed Features
Hardware
EX9251 switches—Starting with Junos OS Release 18.1R1, EX9251 switches are available as a fixed
•
configuration switch. It is an Ethernet-optimized switch that provides carrier-class Ethernet switching.
It has a throughput of up to 400 gigabits per second (Gbps). The switch is available in two variants—with
AC power supply and with DC power supply.
[See EX9251 Switch Hardware Guide.]
25
Authentication, Authorization, and Accounting (AAA) (RADIUS)
Access control and authentication (EX2300 and EX3400 switches)—Starting with Junos OS Release
•
18.1R1, EX2300 and EX3400 switches support controlling access to your network using 802.1X
authentication and MAC RADIUS authentication.
802.1X authentication provides port-based network access control (PNAC) as defined in the IEEE
•
802.1X standard. QFX5100 switches support 802.1X features including guest VLAN, private VLAN,
server fail fallback, dynamic changes to a user session, RADIUS accounting, and configuration of
port-filtering attributes on the RADIUS server using VSAs. You configure 802.1X authentication at
the [edit protocols dot1x] hierarchy level.
MAC RADIUS authentication is used to authenticate end devices independently of whether they are
•
enabled for 802.1X authentication. You can permit end devices that are not 802.1X-enabled to access
the LAN by configuring MAC RADIUS authentication on the switch interfaces to which the end devices
are connected. You configure MAC RADIUS authentication at the [edit protocols dot1x authenticator
interface interface-name mac-radius] hierarchy level.
This feature was introduced previously in an “X” release of Junos OS.
[See Understanding Authentication on Switches.]
TACACS+ authorization for operational commands using regular expressions (EX2300, EX3400, EX4300
•
switches and MX Series)—Starting in Junos OS Release 18.1R1, you can configure authorizations for
operational mode commands using regular expressions using the allow-commands-regexps and
deny-commands-regexps statements. Authorizations can also be configured remotely by specifying
Juniper Networks vendor-specific attributes (VSAs) in your TACACS+ authentication server's configuration.
[See Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands, Configuration
Statements, and Hierarchies.]
Class of Service (CoS)
Support for Class of service (EX2300 and EX3400 switches and EX3400 Virtual Chassis)—Starting in
•
Junos OS Release 18.1R1, when a packet traverses a switch, the switch provides the appropriate level
of service to the packet using either default class-of-service(CoS) settings or CoS settings that you
configure. On ingress ports, the switch classifies packets into appropriate forwarding classes and assigns
a loss priority to the packets. On egress ports, the switch applies packet scheduling and any rewrite rules
to re-mark packets.
This feature was previously supported in an “X” release of Junos OS.
[See Junos OS CoS for EX Series Switches Overview.]
High Availability (HA) and Resiliency
High availability features (EX3400 switches and EX3400 Virtual Chassis)—Starting with Junos OS Release
•
18.1R1, high availability features are supported. High availability features refer to the hardware and
software components that provide redundancy and reliability for network communications.
26
The following features are supported:
Graceful Routing Engine switchover (GRES), nonstop active routing and nonstop bridging
•
Virtual Router Redundancy Protocol (VRRP) support
•
VRRP enables you to provide alternative gateways for end hosts that are configured with static default
routes. You can implement VRRP to provide a high availability default path to a gateway without the
need to configure dynamic routing or router discovery protocols on end hosts.
[See High Availability User Guide.]
Layer 2 Features
Layer 2 features (EX3400 switches and EX3400 Virtual Chassis)—Starting with Junos OS Release 18.1R1,
•
the following Layer 2 features are supported:
VLAN support
•
VLANs enable you to divide one physical broadcast domain into multiple virtual domains.
Link Layer Discovery Protocol (LLDP) support
•
LLDP enables a switch to advertise its identity and capabilities on a LAN, as well as receive information
about other network devices.
Q-in-Q tunneling support
•
This feature enables service providers on Ethernet access networks to extend a Layer 2 Ethernet
connection between two customer sites.
Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol
•
(MSTP), and VLAN Spanning Tree Protocol (VSTP) support
These protocols enable a switch to advertise its identity and capabilities on a LAN and receive
information about other network devices.
This feature was previously supported in an “X” release of Junos OS.
[See Ethernet Switching User Guide.]
Layer 3 Features
Layer 3 feature support (EX2300 and EX3400 Switches)—Starting with Junos OS Release 18.1R1, the
•
Layer 3 features supported in Junos OS Release 15.1X53-D50 are now supported on EX2300 and
EX4300 Switches.
Multicast
27
Layer 2 and Layer 3 multicast support (EX2300 switches and Virtual Chassis, EX3400 switches and
•
Virtual Chassis)—Starting in Junos OS Release 18.1R1, the following IPv4 and IPv6 multicast protocols
are supported:
Internet Group Management Protocol (IGMP) v1, v2, and v3
•
IGMP snooping
•
Multicast Listener Discovery (MLD) protocol v1 and v2
•
MLD snooping
•
Multicast Source Discovery Protocol (MSDP)
•
Protocol Independent Multicast (PIM) sparse mode (SM), dense mode (DM), and source-specific
•
multicast (SSM)
These features were previously supported in an “X” release of Junos OS.
[See Multicast Protocols User Guide.]
Network Management and Monitoring
Pseudohardware RPM timestamps (EX4300 switches and EX4300 Virtual Chassis)—Starting in Junos
•
OS Release 18.1R1, you can configure a pseudo-hardware timestamp on the switch for real-time
performance monitoring (RPM). RPM enables you to configure active probes to track and monitor traffic
on the network. To achieve this, RPM exchanges a set of probes with other IP hosts in the network.
These probes are sent from a source node to other destination devices in the network that requires
tracking. To account for latency or jitter in the communication of probe messages, you can enable
timestamping of the probe packets. On the EX4300 switch, RPM timestamping is performed in the
software. The RPM probes at the requester and responder devices are timestamped in the Packet
Forwarding Engine instead of the Junos OS process (rmpod) that runs on the Routing Engine. This
timestamping method is referred to as pseudo-hardware timestamping. You must configure the switch
as both the RPM client (the requester) and the RPM server (the responder) to timestamp the RPM packet.
You configure pseudohardware timestamps at the [edit services rpm] hierarchy level.
[See Understanding Real-Time Performance Monitoring on EX Series Switches.]
Port mirroring support (EX2300, EX2300-C, and EX3400 switches and EX3400 Virtual Chassis)—Starting
•
in Junos OS Release 18.1R1, port mirroring is supported on EX2300, EX2300-C, and EX3400 switches
and EX3400 Virtual Chassis. Port mirroring copies packets entering or exiting a port or entering a VLAN
and sends the copies to a local interface for local monitoring. You can use port mirroring to send traffic
to applications that analyze traffic for purposes such as monitoring compliance, enforcing policies,
detecting intrusions, monitoring and predicting traffic patterns, and correlating events.
This feature was previously supported in an “X” release of Junos OS.
[See Understanding Port Mirroring and Analyzers on EX2300, EX3400, and EX4300 Switches.]
Port Security
IPv4/IPv6 source guard (EX4600 switches)—Starting in Junos OS Release 18.1R1, you can configure
•
the IP source guard access port security feature to mitigate the effects of source IP address spoofing
and source MAC address spoofing. If IP source guard determines that a host connected to an access
interface has sent a packet with an invalid source IP address or source MAC address in the packet header,
it discards the packet. This feature is supported for IPv4 and IPv6 source addresses.
28
[See Understanding IP Source Guard for Port Security on EX Series Switches.]
MACsec license enforcement (EX3400, EX4300, EX4600, EX9200, QFX5100 switches and Junos Fusion
•
Enterprise)—Starting in Junos OS Release 18.1R1, Media Access Control Security (MACsec) requires
the installation of a MACsec feature license. 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).]
Security
Distributed denial-of-service (DDoS) protection (EX2300 and EX3400 switches, EX2300 and EX3400
•
Virtual Chassis)—Starting in Junos OS Release 18.1R1, you can configure DDoS protection that enables
the switch to continue functioning while under attack. DDoS attacks use multiple sources to flood a
network or switch with protocol control packets. This malicious traffic triggers a large number of
exceptions in the network and tries to exhaust the system resources so that valid users are denied access
to the network or server. DDoS protection identifies and suppresses malicious control packets while
enabling legitimate control traffic to be processed.
[See Distributed Denial-of-Service (DDoS) Protection Overview.]
Support for firewall filters (EX2300 and EX3400 switches, EX2300 and EX3400 Virtual Chassis)—Starting
•
in Junos OS Release 18.1R1, you can define firewall filters on the switch that define whether to accept
or discard packets. You can use firewall filters on interfaces, VLANs, routed VLAN interfaces (RVIs), link
aggregation groups (LAGs), and loopback interfaces.
This feature was previously supported in an “X” release of Junos OS.
[See Firewall Filters for EX Series Switches Overview.]
Port security features (EX2300 and EX3400 switches, EX2300 and EX4300 Virtual Chassis)—Starting
•
in Junos OS Release 18.1R1, the following port security features are supported:
DHCP snooping (Pv4 and IPv6)—Filters and blocks ingress Dynamic Host Configuration Protocol
•
(DHCP) server messages on untrusted ports, and builds and maintains a database of DHCP lease
information, which is called the DHCP snooping database.
Dynamic ARP inspection (DAI)—Prevents Address Resolution Protocol (ARP) spoofing attacks. ARP
•
requests and replies are compared against entries in the DHCP snooping database, and filtering
decisions are made on the basis of the results of those comparisons. You enable DAI on a VLAN.
IPv6 neighbor discovery inspection—Prevents IPv6 address spoofing attacks. Neighbor discovery
•
requests and replies are compared against entries in the DHCPv6 snooping database, and filtering
decisions are made on the basis of the results of those comparisons. You enable neighbor discovery
inspection on a VLAN.
This feature was previously supported in an “X” release of Junos OS.
29
[See Understanding Port Security Features to Protect the Access Ports on Your Device Against the Loss
of Information and Productivity.]
Port mirroring to IP address (EX4600 switches and Virtual Chassis)—Starting with Junos OS Release
•
18.1R1, you can send mirrored packets to an IP address over a Layer 3 network (for example, if there is
no Layer 2 connectivity to the analyzer device).
[See Understanding Port Mirroring.]
User Interface and Configuration
Support for configuring the ephemeral database using the NETCONF and Junos XML protocols (EX2300,
•
EX3400, EX4300, EX4600, and EX9200 switches)—Starting in Junos OS Release 18.1R1, NETCONF
and Junos XML protocol client applications can configure the ephemeral configuration database. 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. Junos OS provides a
default instance and up to eight user-defined instances of the ephemeral 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. Ephemeral configuration
data is volatile and is deleted upon rebooting the device.
[See Understanding the Ephemeral Configuration Database.]
Virtual Chassis
Virtual Chassis support (EX2300, EX3400)—Starting in Junos OS Release 18.1R1, EX2300 or EX3400
•
switches can be interconnected into a Virtual Chassis and operate as one logical device managed as a
single chassis, as follows:
EX2300 Virtual Chassis: Up to four EX2300 and EX2300-C member switches, interconnected using
•
any 10-Gbps SFP+ ports configured as Virtual Chassis ports (VCPs)
EX3400 Virtual Chassis: Up to 10 EX3400 member switches, interconnected using the QSFP+ uplink
•
ports (default-configured VCPs) or any SFP+ uplink ports configured as VCPs
To configure an EX2300 or EX3400 Virtual Chassis, use similar steps as for configuring other EX Series
and QFX Series Virtual Chassis.
This feature was previously supported in an “X” release of Junos OS.
[See Virtual Chassis User Guide for Switches.]
SEE ALSO
Changes in Behavior and Syntax | 30
Known Behavior | 35
30
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Changes in Behavior and Syntax
IN THIS SECTION
Release 18.1R3-S10 Changes in Behavior and Syntax | 31
Release 18.1R3-S7 Changes in Behavior and Syntax | 31
Release 18.1R3 Changes in Behavior and Syntax | 32
Release 18.1R2 Changes in Behavior and Syntax | 34
Release 18.1R1 Changes in Behavior and Syntax | 34
This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS
statements and commands from Junos OS Release 18.1R3 for the EX Series.
Release 18.1R3-S10 Changes in Behavior and Syntax
Routing Protocols
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.]
Release 18.1R3-S7 Changes in Behavior and Syntax
Routing Protocols
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:
31
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.]
Release 18.1R3 Changes in Behavior and Syntax
Network Management and Monitoring
New context-oid option for trap-options configuration statement to distinguish the traps that come
•
from a non-default routing instance and a non-default logical system (EX Series)—Starting in Junos OS
Release 18.1R3, a new option, context-oid, for the trap-options statement allows you to handle prefixes
such as <routing-instance name>@<trap-group> or <logical-system name>/<routing-instance
name>@<trap-group> as an additional varbind.
[See trap-options.]
Layer 2 Features
Configuration option for LLDP VLAN name type, length, and value (TLV) (EX3400, EX4300)—Starting
•
in Junos OS Release 18.1R3, you can configure the vlan-name-tlv-option (name | vlan-id) statement at
the [edit protocols lldp] hierarchy level to select whether to transmit the VLAN name or simply the VLAN
ID for the Link Layer Discovery Protocol (LLDP) VLAN name TLV when exchanging LLDP messages. By
default, EX Series switches running Enhanced Layer 2 Software (ELS) transmit the VLAN ID for the LLDP
VLAN name TLV, and the show lldp detail command displays the default string vlan-vlan-id for an
interface’s VLAN name in the Vlan-name output field. Switches that support the vlan-name-tlv-option
statement behave the same as the default if you configure the vlan-id option with this statement. If you
configure the name option, the switch transmits the VLAN name instead, and the show lldp detail
command displays the VLAN name in the Vlan-name output field.
32
Security
Firewall warning message (EX2300 switches)—Starting in 18.1R3, a warning message is displayed
•
whenever a firewall term includes log or syslog with the accept filter action.
Subscriber Management and Services
DHCPv6 lease renewal for separate IA renew requests (EX Series)—Starting in Junos OS Release 18.1R3,
•
the jdhcpd process handles the second renew request differently in the situation where the DHCPv6
client CPE device does both of the following:
Initiates negotiation for both the IA_NA and IA_PD address types in a single solicit message.
•
Sends separate lease renew requests for the IA_NA and the IA_PD and the renew requests are received
•
back-to-back.
The new behavior is as follows:
1. When the reply is received for the first renew request, if a renew request is pending for the second
address type, the client stays in the renewing state, the lease is extended for the first IA, and the
client entry is updated.
2. When the reply is received for the second renew request, the lease is extended for the second IA
and the client entry is updated again.
In earlier releases:
1. The client transitions to the bound state instead of staying in the renewing state. The lease is extended
for the first IA and the client entry is updated.
2. When the reply is received for the second renew request, the lease is not renewed for the second
address type and the reply is forwarded to the client. Consequently, when that lease ages out, the
binding for that address type is cleared, the access route is removed, and subsequent traffic is dropped
for that address or address prefix.
[See Using DHCPv6 IA_NA with DHCPv6 Prefix Delegation Overview.]
Virtual Chassis
New configuration option to disable automatic Virtual Chassis port conversion (EX4300 and EX4600
•
Virtual Chassis)—Starting in Junos OS Release 18.1R3, you can use the no-auto-conversion statement
at the [edit virtual-chassis] hierarchy level to disable automatic Virtual Chassis port (VCP) conversion in
an EX4300 or EX4600 Virtual Chassis. Automatic VCP conversion is enabled by default on these switches.
When automatic VCP conversion is enabled, if you connect a new member to a Virtual Chassis or add
a new link between two existing members in a Virtual Chassis, the ports on both sides of the link are
automatically converted into VCPs when all of the following conditions are true:
33
LLDP is enabled on the interfaces for the members on both sides of the link. The two sides exchange
•
LLDP packets to accomplish the port conversion.
The Virtual Chassis must be preprovisioned with the switches on both sides of the link already
•
configured in the members list of the Virtual Chassis using the set virtual-chassis member command.
The ports on both ends of the link are supported as VCPs and are not already configured as VCPs.
•
Automatic VCP conversion is not needed when using default-configured VCPs on both sides of the link
to interconnect two members. On both ends of the link, you can also manually configure network or
uplink ports that are supported as VCPs, whether or not the automatic VCP conversion feature is enabled.
Deleting the no-auto-conversion statement from the configuration returns the Virtual Chassis to the
default behavior, which reenables automatic VCP conversion.
[See no-auto-conversion.]
Release 18.1R2 Changes in Behavior and Syntax
Interfaces and Chassis
EEE not supported on mge interfaces operating at 100-Mbps speed (EX2300-24MP and
•
EX2300-48MP)—In Junos OS Releases 18.1R2, if both Energy Efficient Ethernet (EEE) and 100-Mbps
speed are configured on a rate-selectable (or multirate) Gigabit Ethernet (mge) port on EX2300-24MP
and EX2300-48MP switches, the port operates only at 100-Mbps speed but EEE is not enabled on that
port. EEE is supported only on mge interfaces that operate at 1-Gbps and 2.5-Gbps speeds.
Multicast
Support for per-source multicast traffic forwarding with IGMPv3 (EX2300 and EX3400)—Starting in
•
Junos OS Release 18.1R2, EX2300 and EX3400 switches forward multicast traffic on a per-source basis
according to received IGMPv3 INCLUDE and EXCLUDE reports. In releases prior to this release, EX2300
and EX3400 switches process IGMPv3 reports, but instead of source-specific multicast (SSM) forwarding,
they consolidate IGMPv3 INCLUDE and EXCLUDE mode reports for a group into one route for all sources
sending to the group. As a result, with the prior behavior, receivers might get traffic from sources they
didn’t specify.
34
[See IGMP Snooping Overview.]
Release 18.1R1 Changes in Behavior and Syntax
Management
Enhancement to NPU memory sensors for Junos Telemetry Interface (EX9200 switches)—Starting with
•
Junos OS Release 18.1R1, the format of telemetry data exported through gRPC for NPU memory and
memory utilization implements prefix compression. This change reduces the payload size of data exported.
The following example shows the new format:
key: __prefix__
str_value: /components/component[name='FPC0:NPU0']/properties/property
key: [name='mem-util-edmem-size']/value
uint_value: 12345
Telemetry data is exported in key-value pairs. Previously, the data exported included the component
and property names in a single key string.
[See Guidelines for gRPC Sensors.]
Enhancement to LSP statistics sensor for Junos Telemetry Interface (EX9200 switches, QFX10000
•
switches, MX Series, and PTX Series)—Starting with Junos OS 18.1R1, the telemetry data exported for
the LSP statistics sensor no longer includes the phrase and source 0.0.0.0 after the LSP name in the
value string for the prefix key. This change reduces the payload size of data exported. The following is
an example of the new format:
str_value: /mpls/lsps/constrained-path/tunnels/tunnel[name='LSP-4-3']/state/
counters[name='c-27810']/
Network Management and Monitoring
SNMP syslog messages changed (EX Series)—Starting in Junos OS Release 18.1R1, two misleading
•
SNMP syslog messages have been rewritten to accurately describe the event:
OLD—AgentX master agent failed to respond to ping. Attempting to re-register
•
NEW—AgentX master agent failed to respond to ping, triggering cleanup!
OLD—NET-SNMP version %s AgentX subagent connected
•
NEW—NET-SNMP version %s AgentX subagent Open-Sent!
[See the MIB Explorer.]
SEE ALSO
35
New and Changed Features | 21
Known Behavior | 35
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Known Behavior
IN THIS SECTION
Infrastructure | 36
Interfaces and Chassis | 36
Platform and Infrastructure | 36
Virtual Chassis | 37
This section lists known behavior, system maximums, and limitations in hardware and software in Junos
OS Release 18.1R3 for the EX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Infrastructure
When the image is copied through FTP from a server to a switch, sometimes the ftpd WCPU might go
•
high, causing the CLI to freeze for approximately 10 seconds. PR1306286
On rare occasions, the EX2300-MP switch panics with fatal abort. This issue is seen when the rpd process
•
is aborted and it occurs only when dtrace is enabled with continuous rpd process killing. PR1329552
Issue is specific to downgrade (17.4T) and a core file is seen only once during downgrade due to timing
•
issue in the SDK toolkit upgrade. After the upgrade, dcpfe recovers on its own and no issues will be seen
after that. PR1337008
36
Interfaces and Chassis
Previously, the same IP address could be configured on different logical interfaces from different physical
•
interfaces in the same routing instance (including the master routing instance), but only one logical
interface was assigned with the identical address after commit. There was no warning during the commit,
only syslog messages indicating incorrect configuration. This issue is fixed and it is now not allowed to
configure the same IP address (the length of the mask does not matter) on different logical interfaces.
PR1221993
Platform and Infrastructure
On EX4300 switches, when 802.1X single-supplicant authentication is initiated, multiple EAP Request
•
Id Frame Sent packets might be sent. PR1163966
On EX4300 10G links, preexisting MACsec sessions might not come up after the following events (1)
•
Process (pfex, dot1x) restarts or the system restarts. (2) The link flaps. PR1294526
LAG interfaces flap during unified ISSU when fast LACP timers are configured. This might result in traffic
•
loss during the unified ISSU. This issue occurs because Fast LACP timers are not supported on EX-92XX
during unified ISSU. The fast LACP timer support needs to be added. PR1316251
NSSU upgrade from Junos OS Release 15.1X53-D58 to Junos OS Release 18.1R1 will fail with ksyncd
•
core in backup Routing Engine. PR1344686
When upgrading from certain release to Junos OS Release 18.1R1 statistics daemon PFED might be
•
seen generating core files. This issue is not service impacting. The issue can be cleared by rebooting the
chassis or by deleting all files from /mfs. PR1346925
Virtual Chassis
VC internal loop might happen at a node coming up from a reboot. During nonstop software upgrade
•
(NSSU) on a QFX5100 Virtual Chassis, a minimal traffic disruption or traffic loop(>2s) might occur and
it is considered to be known behavior. Release note reference:
https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/17.2/topic-118735.htmlPR1347902
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
37
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Known Issues
IN THIS SECTION
General Routing | 38
Infrastructure | 39
Layer 2 Features | 39
Platform and Infrastructure | 39
This section lists the known issues in hardware and software in Junos OS Release 18.1R3 for the EX 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
On an EX9200-12QS line card, interfaces with the default speed of 10 Gigabit Ethernet are not brought
•
down even when the remote end of a connection is misconfigured as 40 Gigabit Ethernet. PR1175918
On an EX9200-40XS line card, if you toggle the MACsec encryption option multiple times, encryption
•
and protected MACsec statistics might be updated incorrectly. As a workaround, restart the line card.
PR1185659
When a configuration that offlines a Packet Forwarding Engine and another configuration that brings
•
the Packet Forwarding Engine back online, is committed in quick succession, there could be Routing
Engine and Packet Forwarding Engine out of sync errors logged in syslog. Most of the time these are
benign errors, but sometimes they might result in Packet Forwarding Engine crashes. PR1232178
Some configurations that are valid in Junos OS Release 12.3 are not valid for Junos OS Release 15.1.
•
When you try to upgrade from Junos OS Release 12.3 to 15.1 with such configurations, after upgrade
the device goes into amnesiac mode. PR1313501
In a streaming telemetry scenario, if performing commit full, the na-grpd process might restart, causing
•
disconnection of the streaming telemetry. PR1326366
38
On EX2300 and EX3400 switches with SFP, when the actual receiver signal power exceeds 0.21 mW,
•
the output of the command show interfaces diagnostics optics might display an incorrect value for the
field Receiver signal average optical power. PR1326642
On an EX3400 platform, when force-renew is initiated from a server, the renewing entry for the bounded
•
client will not be displayed under show dhcp-security binding. PR1328542
On EX4600 platforms, in some cases, the CoS (class of Service) configuration is not properly applied in
•
the Packet Forwarding Engine, leading to unexpected egress traffic drop on some interfaces. PR1329141
On an EX9251 switch, after you perform the restart chassis-control for the first time after the software
•
image is upgraded or after the switch is rebooted, the MPC booting state changes from offline to online
directly, without staying at present state during booting. This issue is seen occasionally. There is no
functional impact because of this state change. PR1332613
On an EX9251 switch, physical links might not come up if you perform frequent port profile changes
•
while a line card reboot is in progress. PR1340140
On an EX9251 switch, if there is a packet loop between aggregation devices because of a redundant
•
link, one aggregation device in a dual aggregation device setup might reboot if you clear the DHCP relay
bindings. You must remove the redundant link to prevent such a reboot. PR1347507
On EX2300-48MP, EX2300-48T and EX2300-48P platforms, the show virtual-chassis command might
•
not display the model name. PR1362421
The show interface ge-x/x/x command indicates "Duplex: Half-duplex" when link-mode is set to automatic
•
or is not set. This is a display issue and it works as auto. PR1364659
The multicast router advertisement packets coming on a VLAN need to be flooded on the ports of all
•
FPCs belonging to the same VLAN. Packets traversing through HighGig ports need to hit the h/w filter
to transmit packets to other FPCs. In issue state, filter is not applicable for highgig ports, so multicast
RA packets are not traversing other FPCs. PR1370329
Infrastructure
The request system zeroize command will result in the device going for a continuous reboot in non-FIPS
•
mode. The restoration is to halt the boot sequence at the loader and install the media-net package
through TFTP. PR1337826
On EX2300, EX2300-C, and EX2300-MP platforms, if Junos OS is with FreeBSD kernel version 11 with
•
the build date on or after 2019-02-12, the switch might stop forwarding traffic or responding to console.
A reboot is required to restore the service. PR1442376
Layer 2 Features
No error or warning is displayed when you commit association of IRB interfaces with VLAN using set
•
vlans VLAN150 l3-interface irb.X without configuring the actual IRB interface using set interfaces irb
unit X. PR1359982
39
The eswd[1200]: ESWD_MAC_SMAC_BRIDGE_MAC_IDENTICAL: Bridge Address Add:
•
XX:XX:db:2b:26:81 SMAC is equal to bridge mac hence don't learn message is seen in syslog every few
minutes on the ERPS owner. Because the log is caused by ERPS PDU in ERPS setup, you can ignore the
message. PR1372422
Platform and Infrastructure
On EX4300, MACsec might not work properly on PHY84756 1G SFP ports, if AN is on and MACsec is
•
configured on those ports. On the EX4300 device, all four uplink ports (PIC 2) are attached to PHY84756.
On EX4300 fiber box, the last four ports of base board (PIC 0) and 8*1G/10G uplink ports (PIC 2) are
attached to PHY84756. PR1291724
On EX4300 switches, the filter-based forwarding (FBF) might not work properly after deactivating or
•
activating. This issue occurs because stale entries are not being freed in ternary content addressable
memory (TCAM), which leads to insufficient space in TCAM for processing filters. PR1293581
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Behavior | 35
Resolved Issues | 40
Documentation Updates | 48
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Resolved Issues
IN THIS SECTION
Resolved Issues: 18.1R3 | 40
Resolved Issues: 18.1R2 | 42
Resolved Issues: 18.1R1 | 44
40
This section lists the issues fixed in the Junos OS main release and the maintenance releases.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Resolved Issues: 18.1R3
General Routing
On EX2300 and EX3400 switches, the bridge-id is assigned to "02:00:00:00:00:10" irrespective of the
•
base-mac addresses. PR1315633
The MAC movement within a VLAN is not working as expected when setting up 802.1X for multiple
•
supplicant mode. PR1329654
After the EX9200 FPC comes online, other FPCs might have 100 percent CPU usage and a traffic loss
•
for up to 30 seconds. PR1346949
A commit error is observed if the device is downgraded from Junos OS Release 18.2 to Junos OS Release
•
17.3R3. PR1355542
On EX2300, EX3400, and EX4300MP platforms in a Virtual Chassis setup, dynamic ARP inspection
•
might fail after a Virtual Chassis switchover when VSTP is enabled along with no-mac-table-binding.
PR1359753
On EX2300, EX3400, EX4300-MP and EX2300-MP platforms used as a transit switch, routed traffic
•
sent out of IRB interface, uses old MAC address instead of the configured MAC address for the IRB.
PR1359816
On EX2300MP platforms, the fan count is wrong in jnxFruName, jnxFilledDescr and jnxContainersCount.
•
PR1361025
On EX4300-48MP, the dot1x protocol subsystem is taking long time to respond to management requests
•
with the error the dot1x-protocol subsystem is not responding to management requests. PR1361398
A nonexistent fan tray 1 is reported by chassisd on EX2300. PR1361696
•
A unicast ARP packet loop might be observed in DAI scenario. PR1370607
•
Port access list group is not properly reallocating TCAM slices. PR1375022
•
On EX4300-48MP, the Syslog error Error in bcm_port_sample_rate_set(ifl_cmd) : Reason Invalid port
•
is seen. PR1376504
EVPN
The proxy ARP might not work as expected in an EVPN environment. PR1368911
•
Infrastructure
EX4300 firewall rule ip-options used with commands other than "any" does not provide expected results.
•
PR1173347
41
Unable to provide management when em0 interface of FPC is connected to another FPC Layer 2 interface
•
of the same Virtual Chassis. PR1299385
The upgrade might fail if bad blocks occurs in the flash memory device or file system. PR1317628
•
Need support for archiving dmesg file /var/run/dmesg.boot*. PR1327021
•
Core file is generated upon attempt to commit configuration. PR1376362
•
Layer 2 Features
The dcpfe or fxpc process might crash on Packet Forwarding Engines with low memory when allocating
•
huge memory. PR1362332
Network Management and Monitoring
While toggling multiple times between baseline and CFM configs, all 30 CFM sessions are not up.
•
PR1360907
Platform and Infrastructure
The mismatch of VLAN ID between a logical interface and a VLAN configuration might result in traffic
•
being silently discarded. PR1259310
EX4300 crashes when it receives more than 120 KPPS ARPs on me0 interface. PR1329430
•
The SNMP trap message are always sent out with log about Fan/Blower OK on EX4300-VC switch.
•
PR1329507
The show spanning-tree statistics bridge command output gives 0 for all VLAN instance IDs. PR1337891
•
On MPC5, the inline-ka PPP echo requests are not transmitted when anchor-point is lt-x/2/x or lt-x/3/x
•
in a pseudowire deployment. PR1345727
Running RSI through the console port might cause the system to crash and reboot. PR1349332
•
A high usage chassis alarm in /var does not clear from the EX4300 Virtual Chassis when a file is copied
•
from fpc1 (master) to fpc0 (backup). PR1354007
The ports using an SFP-T transceiver might be still up after a system halt. PR1354857
•
The FPC would crash due to the memory leak caused by the VTEP traffic. PR1356279
•
Some interfaces cannot be added under the STP configuration. PR1363625
•
On EX4300 and EX4600 platforms, the l2ald process might crash in a dot1x scenario. PR1363964
•
The Packet Forwarding Engine might crash on encountering frequent MAC move. PR1367141
•
The request system zeroize command non-interactively might not erase the configuration on EX4300.
•
PR1368452
NTP broadcast packets are not forwarded out on VLAN Layer 2 ports. PR1371035
•
42
On EX4300, lldp advertisment appears with incorrect auto-negotiation values. PR1372966
•
Resolved Issues: 18.1R2
General Routing
The hawkeye alarmd transient error is observed on MX240, MX480, MX960, EX9200, and SRX5000
•
platforms. PR1312336
On an EX3400 switch, MACsec is not supported on 10G uplink ports. PR1325545
•
Traffic going through the aggregated Ethernet interface might be dropped if mastership changes.
•
PR1327578
The EX3400 switch floods unicast ARP replies in the VLAN when dynamic ARP inspection is enabled.
•
PR1331928
On an EX9200 switch, when an anchor FPC has no active child, bridge protocol data units (BPDUs) are
•
not sent out to the other active child. PR1333872
All the DHCP-Reply or DCHP-Offer packets might be discarded by the DHCP snooping if the DHCP
•
snooping is not enabled in that VLAN. PR1345426
On an EX2300 running Junos OS Release15.1X53-D56 with the fxpc process, issuing the
•
accept-source-mac command causes the CPU usage to spike up to 90 percent on an idle chassis.
PR1345978
The statistics PFED process might generate a core file on an upgrade between certain releases.
•
PR1346925
Starting in Junos OS Release 18.1R2, there is support for OPSFv3 authentication on EX Series
•
switches.PR1347630
Different behavior on the tagging of interfaces before and after reboot without any change in
•
configuration. PR1349712
On EX2300 and EX3400 switches, the lacp mac re-write protocol sends duplicate Link Aggregation
•
Control Protocol (LACP), bridge protocol data unit (BPDU) with different destination MAC addresses.
PR1350329
After an EX2300 switch reboots, if you have ECMP next hop configured, the ECMP group might only
•
be created on one Packet Forwarding Engine. PR1351418
Forwarding and Sampling
After an EX9251 switch is set to factory default by zeroize, the DHCP service crashes.PR1329682
•
Infrastructure
EX4300 firewall rule ip-options with knobs other than "any" doesn't provide expected results. PR1173347
•
43
On an EX4600 switch, priority-based flow control (PFC) frames might not work. PR1322439
•
The interface LED status might stay green even after disabling the interface and removing the cable.
•
PR1329903
Interfaces and Chassis
Some PoE devices might not receive PoE power from EX2300 or EX3400 switches due to a false report
•
of Underload Latch.PR1345234
On EX4600, the MC-lag after reboot of VRRP Master and Back up discards traffic to downstream
•
switches. PR1345316
Platform and Infrastructure
On the EX4300 Virtual Chassis switch , the FPC might crash and a PFEX core file might get generated.
•
PR1261852
Multicast receiver connected to the EX4300 switch might not be able to get the multicast streaming.
•
PR1308269
Autonegotiation is not working as expected between EX4300 and SRX5800. PR1311458
•
IGMPv3 on EX4300 does not have the correct outgoing interfaces in the Packet Forwarding Engine that
•
are listed in the kernel. PR1317141
On an EX4300 platform, a MAC learning issue and new VLANs creation failure might occur for some
•
VLANs. PR1325816
On an EX4300 platform, when exhausting TCAM, the table filter is still programmed.PR1330148
•
Internet Group Management Protocol (IGMP) packets are forwarded out of the redundant trunk group
•
(RTG) backup interface. PR1335733
MSTP might not work normally after permitting a commit. PR1342900
•
On EX4300, the loopback filter is not blocking unauthorized BGP peers. PR1343402
•
The firewall filter might not be programmed in the Packet Forwarding Engine even though TCAM entries
•
are available. PR1345296
The VLAN translation feature does not work for the control plane traffic. PR1348094
•
Traffic drop might occur if LLC packets are sent with DSAP and SSAP as 0x88 and 0x8e. PR1348618
•
Routing Protocols
Open Shortest Path First (OSFP) routes cannot be added to the routing table until the lsa-refresh timer
•
expires. PR1316348
The igmp-snooping protocol might be enabled unexpectedly. PR1327048
•
Resolved Issues: 18.1R1
Authentication and Access Control
44
The LLDP-MED cannot forward the correct POE class. PR1296547
•
The dot1x process might stop authenticating if continuous dot1x client reauthentication requests cannot
•
get processed. PR1300050
EX2300-C is missing the dot1xd_usr_authenticated help string. PR1311465
•
EVPN
Split horizon label is not allocated after switching the configuration of ESI from 'single-active' to 'all-active'.
•
PR1307056
Infrastructure
Reboot logs are not shown on the mini-USB console even though set system ports auxiliary port-type
•
mini-usb is configured. PR1192388
The file system might be corrupted multiple times during image upgrade or commit operation. PR1317250
•
PFC feature might not work on EX4600. PR1322439
•
The ifinfo might generate core files on the EX4600 Virtual Chassis. PR1324326
•
Interfaces and Chassis
On EX2300 and EX3400 IPV6 neighborship is not created on the IRB interface. PR1198482
•
On the EX4300 Virtual Chassis: LACP flap is observed, after rebooting the master FPC with PDT
•
configurations. PR1301338
The interface might not work properly after the FPC restarts. PR1329896
•
MPLS
QFX5100 and EX4600: Unified ISSU is not supported with MPLS configuration. PR1264786
•
Platform and Infrastructure
After access is rejected, the dot1x process might crash due to memory leak. PR1160059
•
On EX3400 and EX2300, LLDP, LACP, and MVRP protocols are not available under the mac-rewrite
•
configuration. PR1189353
The I2C log error message is printed. PR1251604
•
EX3400 Virtual Chassis has tail drops on multicast queues due to incorrect shared buffer programming.
•
PR1269326
Traffic loss might be observed for about 10 seconds if the master member FPC reboots. PR1283702
•
Doing load replace terminal and attempting to replace the interface stanza might terminate the current
•
CLI session and leave the user session hanging. PR1293587
Some packets might be dropped after GRE encapsulation on EX4300. PR1293787
•
45
Syslogs contain messages with %PFE-3: fpc0 ifd null, port 28 dc-pfe: %USER-3: ifd null, port 28 : %PFE-3:
•
fpc0 ifd null, port 29 dc-pfe: %USER-3: ifd null, port 29. PR1295711
Eswd core file might be observed if apply-groups is configured under interface-range. PR1300709
•
On EX4300 switches, when unknown unicast ICMP packets are received by an interface, packets are
•
routed, so TTL is decremented. PR1302070
Unknown IPv6 multicast traffic are dropped if mld-snooping is enabled. PR1304345
•
The show snmp mib walk CLI command used for jnxMIMstMstiPortState does not display anything in
•
Junos OS Release 17.1R2 on the EX4600 platform. PR1305281
On EX2300 and EX3400 Virtual Chassis or standalone chassis, IP routing fails for destination routes
•
(IPv4 or IPv6 routes) with prefix length of 32 or 128 when they point to ECMP nexthops. PR1305462
Inconsistent IEEE P-bit marking occurs in 802.1Q header for OSPF packets. PR1306750
•
The me0 link might stay up after the link is disabled. PR1307085
•
Multicast receiver connected to EX4300 might not be able to get the multicast streaming. PR1308269
•
Multicast receiver connected to EX4300 might not be able to receive the multicast streaming. PR1308269
•
VLAN rewrite is not working on aggregated Ethernet interface for EX2300/3400. PR1309998
•
Traceroute is not working in EX9200 device for routing instances running on Junos OS Release 17.1R3.
•
PR1310615
Traffic loss is observed while performing NSSU. PR1311977
•
IGMP snooping might not learn multicast router interface dynamically. PR1312128
•
The DHCP security binding table might not get updated. PR1312670
•
The PoE-enabled port does not come up after reboot of the line card member in EX3400 Virtual Chassis.
•
PR1312983
A memory leak is seen for dot1xd. PR1313578
•
The interface with 1G SFP might go down if no-auto-negotiation is configured. PR1315668
•
Policer does not work for 224.0.0.X MC traffic to the kernel on EX4300s. PR1313251
•
On EX2300 and EX3400 switches, access ports might incorrectly send VLAN-tagged traffic. PR1315206
•
Need to replace the show vlans evpn command with the show ethernet-switching evpn command for
•
EX92xx and QFX Series switches. PR1316272
Image upgrade fails with the error message ERROR: Failed to add Junos-. PR1317425
•
EX2300 interface statistics shows an incorrect bits-per-second (bps) value when the interface has line-rate
•
traffic at 10 Gbps. PR1318767
L2cpd core files might be seen if the interface is disabled under VSTP and enabled under RSTP.
•
PR1317908
A vmcore file might be seen, and the device might reboot after the ICL is changed from an aggregated
•
Ethernet to a physical interface. PR1318929
46
High latency might be observed between the Master Routing Engine and the other FPC. PR1319795
•
EX3400 changes FAN speed frequently with Over Temperature alarm after a software upgrade.
•
PR1320687
VLAN might not be processed, which leads to improper STP convergence. PR1320719
•
On the EX2300-48 platform, known unicast might be flooded if the source MAC address is on PFE1 and
•
the destination MAC address is on PFE0. PR1321612
Multicast traffic might not be forwarded to one of the receivers. PR1323499
•
EX3400: MACsec not supported on 10G uplink ports. PR1325545
•
L2cpd might create a core file. PR1325917
•
EX Series switches do not send RADIUS request after modifying the interface-range configuration.
•
PR1326442
Packets with the DEI bit set in the L2 header are not forwarded on the EX3400 switches. PR1326855
•
EX4600, QFX5100, and ACX5000: Major Alarm Fan & PSU Airflow direction mismatch is seen after
•
removing the management cable. PR1327561
DHCP packet duplication issue is seen on EX2300/EX3400. PR1326857
•
New operational status detail command is added in show poe interface. PR1330183
•
EX3400 CPU have hog when Continuous Telnet EC command are sent on more than 75 concurrent
•
telnet session. PR1331234
IP Directed broadcast traffic forwarding does not work on EX3400/EX2300 platform. Applications such
•
as Wakeup-on-lan do not work without this support. PR1331326
EX3400 floods unicast ARP replies when DAI is enabled. PR1331928
•
EX2300-48T: "Base power reserved" value seen is higher than "Total power supplied" in show chassis
•
power-budget-statistics command. PR1333032
Group unknown is seen on show filter hw 1 show_term_info CLI after adding tcam-group-optimization
•
CLI. PR1333367
EX9200 -- Major Errors - MQSS Error code: 0x2203cb. PR1334928
•
IGMP traffic going out of RTG backup link is causing a loop. PR1335733
•
VLAN rewrite might not work properly on trunk ports. PR1336174
•
Routing Protocols
An mcsnoopd core file is seen at core @
•
__raise,abort,__task_quit__,task_quit,task_terminate_timer_callback,task_timer_dispatch,task_scheduler_internal
(enable_slip_detector=true, no_exit=true) at
../../../../../../src/junos/lib/libjtask/base/task_scheduler.c:275.PR1305239
47
User Interface and Configuration
EX2300 Virtual Chassis committing from J-Web causes PHP process to spike high. PR1328323
•
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Behavior | 35
Known Issues | 37
Documentation Updates | 48
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Documentation Updates
IN THIS SECTION
New Simplified Documentation Architecture | 48
This section lists the errata and changes in Junos OS Release 18.1R3 for the EX Series switches
documentation.
New Simplified Documentation Architecture
With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make
•
it easier for you to find information and know that you can rely on it when you find it. In the past, we
organized documentation about Junos OS software features into platform-specific documents. In many
cases, features are supported on multiple platforms, so you might not easily find the document you want
for your platform.
48
With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For
example, if you want to find documentation on OSPF, there is only one document regardless of which
platform you have. Here are some of the benefits of our new simplified architecture:
Over time, you will see better search results when looking for Juniper documentation. You will be able
•
to find what you want faster and be assured that is the right document.
If a software feature is supported on multiple platforms, you can find information about all the platforms
•
in one place.
Because we have eliminated many documents that covered similar topics, you will now find one
•
document with all the information.
You can know that you are always getting the most current and accurate information.
•
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Behavior | 35
Known Issues | 37
Resolved Issues | 40
Migration, Upgrade, and Downgrade Instructions | 49
Product Compatibility | 50
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Upgrade and Downgrade Support Policy for Junos OS Releases | 49
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.
49
NOTE:
: EX2300 or EX3400 switches running Junos OS Software Release 15.1X53-D57 or earlier
•
revisions cannot be directly upgraded via CLI to Junos OS Software Release 18.1R1 because
of configuration incompatibilities between the two releases related to the uplink port
configurations. For example: Any configuration having interfaces on the uplink module (xe-0/2/*)
will throw errors during the upgrade process. To work around this problem, please specify the
validate option in the upgrade command to check for these errors, then remove the
configuration that results in the errors, and use the no-validate option to do the upgrade.
Alternately, an intermediate upgrade to 15.1X53-D58 can be performed by keeping the
configuration intact and then a subsequent upgrade to 18.1R1 is possible.
NSSU is not supported on EX2300-VC/EX3400-VC from Junos OS Release 15.1X53 to Junos
•
OS Release 18.1R1 or later releases. For example, NSSU is not supported from Junos OS
Release 15.1X53-D58 to Junos OS Release 18.1R1 or Junos OS Release 15.1X53-D57 to
Junos OS Release 18.2R1.
Upgrade and Downgrade Support Policy for Junos OS Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not
provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases
provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the
next EEOL release even though EEOL releases generally occur in increments beyond three releases.
You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently
installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1,
17.2 and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from
Junos OS Release 17.1 to Release 17.3.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead
or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before
or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release
to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see
https://www.juniper.net/support/eol/junos.html.
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
50
Known Behavior | 35
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
Product Compatibility | 50
Product Compatibility
IN THIS SECTION
Hardware Compatibility | 50
Hardware Compatibility
To obtain information about the components that are supported on the devices, and the special compatibility
guidelines with the release, see the Hardware Guide for the product.
To determine the features supported on EX Series switches in this release, use the Juniper Networks
Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature
information to find the right software release and hardware platform for your network. Find Feature
Explorer at https://pathfinder.juniper.net/feature-explorer/.
Hardware Compatibility Tool
For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms,
see the Hardware Compatibility tool.
SEE ALSO
New and Changed Features | 21
Changes in Behavior and Syntax | 30
Known Behavior | 35
Known Issues | 37
Resolved Issues | 40
Documentation Updates | 48
51
Migration, Upgrade, and Downgrade Instructions | 49
Junos OS Release Notes for Junos Fusion Data Center
IN THIS SECTION
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
These release notes accompany Junos OS Release 18.1R3 for the Junos Fusion Data Center. They describe
new and changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located
at https://www.juniper.net/documentation/product/en_US/junos-os
New and Changed Features
IN THIS SECTION
Release 18.1R3 New and Changed Features | 53
Release 18.1R2-S2 New and Changed Features | 53
Release 18.1R2 New and Changed Features | 57
Release 18.1R1 New and Changed Features | 57
52
This section describes the new features and enhancements to existing features in Junos OS Release 18.1R3
for Junos Fusion Data Center.
Release 18.1R3 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos
•
OS Release 18.1R3.
Release 18.1R2-S2 New and Changed Features
Class of Service
Class of service support (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, Junos
•
Fusion Data Center supports the standard Junos class of service (CoS) features and operational commands
in a quad-aggregation device configuration. Each extended port on a satellite device is a logical extension
to the aggregation device. Therefore, the default CoS policy on the aggregation device applies to each
extended port. You can also create standard CoS policies for extended ports.
A cascade port is a physical port or interface on an aggregation device that provides a connection to a
satellite device. Port scheduling is supported on cascade ports. Junos Fusion technology reserves a
separate set of queues with minimum bandwidth guarantees for in-band management traffic to protect
against congestion caused by data traffic.
53
[See Understanding CoS in Junos Fusion Data Center.]
EVPN
Designated event forwarding of SNMP traps in an EVPN topology (Junos Fusion Data Center)—Starting
•
with Junos OS Release 18.1R2-S2, you can enable SNMP on the aggregation device and designate trap
forwarding in an EVPN topology in Junos Fusion Data Center. In an EVPN topology, the satellite device
generates an SNMP trap event when a change occurs on any of the associated satellite devices. This
trap event information is sent to all connected aggregation devices who then sends the trap request to
the SNMP server. Because each aggregation devices sends its own copy of the trap, the SNMP server
receives multiple copies of the trap for the same event on the satellite device, thereby causing overhead
to the SNMP server. To prevent the trap from being generated for each aggregation device, you can
enable designated trap forwarding so that the trap request is only sent by the aggregation device selected
as the designated router. You enable designate trap forwarding under the [satellite-management]
hierarchy. Designated event forwarding is disabled by default.
[See Understanding Designated Event Forwarding of SNMP Traps in an EVPN Junos Fusion Data Center.]
Interfaces and Chassis
•
Configuration synchronization for up to four aggregation devices (Junos Fusion Data Center)—Starting
in Junos OS Release 18.1R2-S2, configuration synchronization enables you to easily propagate,
synchronize, and commit configurations from one aggregation device (AD) to another AD. Log in to
either AD to manage the other three ADs, and use configuration groups to simplify the configuration
process. You can create one configuration group each for the local ADs, and a global configuration
common to all ADs.
Create conditional groups to specify when configurations are synchronized. Enable peers-synchronize
at the [edit system commit] hierarchy to synchronize configurations and commits across ADs by default.
NETCONF over SSH provides a secure connection between ADs. Secure Copy Protocol (SCP) copies
configurations securely between them.
[See Understanding Multichassis Link Aggregation Group Configuration Consistency Check.]
•
Increased number of aggregated Ethernet interfaces (Junos Fusion Data Center)—Starting in Junos OS
Release 18.1R2-S2, you can configure up to 1750 aggregated Ethernet interfaces for a Junos Fusion
Data Center system. To configure, include the device-count statement with a value of 1000 at the [edit
chassis aggregated-devices ethernet] hierarchy level and add member links in each bundle.
[See Understanding Link Aggregation and Link Aggregation Control Protocol in a Junos Fusion.]
Junos Fusion Data Center
Junos Fusion Data Center with four aggregation devices and EVPN infrastructure (Junos Fusion Data
•
Center)—Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center supports four aggregation
devices to which each satellite device can be multihomed in active-active mode. In this topology, the
four aggregation devices comprise a core fabric in which Ethernet VPN (EVPN) is implemented as the
control plane in which host and server MAC addresses, network reachability, and other states learned
by an aggregation device are advertised to the other aggregation devices. For the data plane, the
aggregation devices use Virtual Extensible LAN (VXLAN) encapsulation when forwarding a Layer 2 data
packet to other aggregation devices. Namely, an aggregation device encapsulates a data packet in a
VXLAN UDP header and sends the packet by means of the Layer 3 network to another aggregation
device. Upon receipt of the packet, the aggregation device de-encapsulates the packet and forwards it
as appropriate.
54
Junos Fusion Data Center with four aggregation devices and an EVPN architecture implements IEEE
802.1BR processing between the aggregation devices and satellite devices.
[See Understanding EVPN in a Junos Fusion Data Center.]
Layer 2 unicast forwarding on extended ports (Junos Fusion Data Center)—Starting with Junos OS
•
Release 18.1R2-S2, Junos Fusion Data Center supports Layer 2 unicast forwarding on extended ports.
When a remote MAC address is learned from a Type-2 MAC route advertisement, the aggregation device
determines the corresponding extended port next hop from the Ethernet Segment Identifier (ESI) carried
in the MAC route advertisement. This extended port next hop is resolved in the set of local cascade
interfaces that are used to reach that extended port. Traffic sent to a destination extended port only
traverses the EVPN tunnel if the destination extended port cannot be resolved to a local cascade interface.
For non-extended port destinations located on a remote aggregation device (or external Provider Edge
(PE) device in the same EVPN), traffic is carried in the EVPN tunnel. When EVPN MAC aliasing is enabled,
aggregation devices signal their reachability towards the destination extended port using the per-EVI
Ethernet A-D route, so that a list of aggregation devices can be built for load-balancing even if those
aggregation devices have not advertised that specific MAC route.
[See Understanding EVPN in a Junos Fusion Data Center.]
Satellite device support (QFX5110 and QFX5200)—Starting with Junos OS Release 18.1R2-S2, you can
•
configure QFX5110-48S and QFX5200-32C switches as satellite devices in a Junos Fusion Data Center
topology. The satellite device in a Junos Fusion topology is managed and configured by the aggregation
device. Junos Fusion Data Center uses QFX10002, QFX10008 and QFX10016 switches in the aggregation
device role.
[See Junos Fusion Data Center Software and Hardware Requirements.]
Flow-based uplink selection (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, you
•
can configure flow-based uplink selection for satellite devices by defining a chassis group to which the
uplink traffic flows will be directed.
[See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.]
Multicast
Layer 2 multicast support with local replication in an EVPN topology (Junos Fusion Data Center)—Starting
•
with Junos OS Release 18.1R2-S2, Junos Fusion Data Center with EVPN combines elements of an EVPN
multicast infrastructure with 802.1BR local replication to support Layer 2 multicast forwarding. In this
environment, each extended port on a satellite device is multihomed to all aggregation devices and
modeled as an EVPN Ethernet Segment (ES). One aggregation device is elected as the designated
forwarder (DF) for each ES (based on the extended port’s satellite device DF), and the IGMP snooping
state is synchronized on all aggregation devices connected to that ES for faster convergence when DF
re-election is required.
55
To forward multicast traffic, a source aggregation device employs local bias forwarding towards any
locally reachable extended port multicast destinations, and uses ingress replication to the other aggregation
devices in the EVPN/VxLAN tunnel acting as DFs for other ES destinations. Any forwarding aggregation
device also uses 802.1BR local replication to destination satellite devices if you configure the
local-replication statement at the [edit forwarding-options satellite] hierarchy level. Local replication,
also referred to as egress replication at the satellite devices, helps distribute packet replication load and
reduce traffic on cascade ports for multicast traffic by having the forwarding aggregation device send
only one copy of a packet to each satellite device that has an extended port in the multicast group, and
the satellite device then does the replication for its local extended ports.
[See Multicast Forwarding at Layer 2 in a Junos Fusion Data Center with EVPN.]
Layer 3 multicast support in an EVPN topology (Junos Fusion Data Center)— Starting with Junos OS
•
Release 18.1R2-S2, Junos Fusion Data Center with EVPN includes support for sending Layer 3 multicast
traffic between extended ports, or link aggregations of extended ports, that are located in different
VLANs. Instead of running PIM on the aggregation devices, IGMP reports are sent to the gateways.
In the EVPN topology, two or more satellite devices are multihomed to four QFX10002 aggregation
devices, and a multicast VLAN is provisioned between the aggregation devices and the external gateways.
Both the source and receiver ports can be inside the fabric, or one can be external to the fabric while
the other is internal. Likewise, participating servers can be connected to the fabric through the same or
different tenants (in which case traffic must transit an external gateway so the gateway can handle the
routing between tenants).
[See Multicast Forwarding at Layer 3 in a Junos Fusion Data Center with EVPN.]
VLAN flooding support with local replication in an EVPN topology (Junos Fusion Data Center)—Starting
•
with Junos OS Release 18.1R2-S2, Junos Fusion Data Center with EVPN combines elements of an EVPN
multicast infrastructure with 802.1BR local replication to support Layer 2 VLAN flooding. Local replication
helps distribute packet replication load and reduce traffic on cascade ports for multicast and flooded
VLAN traffic. In this environment, each extended port on a satellite device is multihomed to all aggregation
devices and modeled as an EVPN Ethernet Segment (ES). One aggregation device is elected as the
designated forwarder (DF) for each ES (based on the extended port’s satellite device DF).
An aggregation device might initiate VLAN flooding (broadcasting or flooding the packet out to all
interfaces in the VLAN) to learn the MAC address for a destination that is not already in its Ethernet
switching tables. With local replication enabled, the aggregation device requests multicast ECIDs to
represent the extended ports in the VLAN on each satellite device. You configure 802.1BR local replication
to destination satellite devices by configuring the local-replication statement at the [edit
forwarding-options satellite] hierarchy level.
[See local-replication.]
56
Port Security
•
Storm control on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2,
storm control is supported on the extended ports of the satellite device in a Junos Fusion Data Center.
You can configure storm control from the aggregation device to rate-limit broadcast traffic, multicast
traffic, and unknown unicast traffic level so that the fabric drops packets when the specified traffic level
is exceeded, thus preventing packets from proliferating and degrading the LAN. You specify the storm
control level as the traffic rate in kilobits per second (Kbps) of the combined traffic streams, or as the
percentage of available link bandwidth used by the combined traffic streams. If the storm control is
exceeded, you can also configure the extended ports to shut down interfaces by using the
action-shutdown command, or by temporarily disabling the interfaces by using the port-error-disable
command. Additionally, you can disable storm control on registered or unregistered multicast traffic.
[See Understanding Storm Control.]
•
Firewall filter support on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release
18.1R2-S2, you can configure firewall filters on extended ports in a Junos Fusion Data Center. An
extended port is a physical interface on the satellite device that is managed through the aggregation
device. From the aggregation device, you can configure a firewall filter to accept or discard a packet
before it enters or exits the port. If a packet is accepted, you can configure additional actions to perform
on the packet, such as class-of-service (CoS) marking (grouping similar types of traffic together and
treating each type of traffic as a class with its own level of service priority) and traffic policing (controlling
the maximum rate of traffic sent or received).To use a firewall filter, you must first configure the filter
and then apply it to the port. Firewall filters are defined under the [edit firewall] hierarchy level. This
feature was previously supported in an "X" release of Junos OS.
[See Overview of Firewall Filters.]
Storage
DCBX Version 1.01 sequence number TLV mapping for multiple aggregation devices (Junos Fusion
•
Data Center)—Starting in Junos OS 18.1R2-S2, to ensure Junos Fusion Data Center with EVPN appears
as a single device to a DCBX Version 1.01 peer, satellite devices maintain a sequence number TLV
mapping table to coordinate DCBX message sequence numbers with those on multiple aggregation
devices. The satellite device maintains a local sequence number that is exchanged with the DCBX peer,
and maps that value to and from each aggregation device’s corresponding local sequence number before
relaying DCBX messages in either direction. The show dcbx neighbors interface interface-name command
displays both the aggregation device local sequence number (in the sequence-number field) and the
satellite device local sequence number (in the satellite sequence-number field) in the Local-Advertisement
section of the output. In addition, the peer-chassis sequence-number field displayed with dual aggregation
devices for Junos Fusion Data Center with MC-LAG is no longer included that section of the output.
[See Understanding DCBX on Junos Fusion Data Center.]
Release 18.1R2 New and Changed Features
57
There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos
•
OS Release 18.1R2.
Release 18.1R1 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos
•
OS Release 18.1R1.
SEE ALSO
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
Changes in Behavior and Syntax
There are no changes in behavior and syntax for Junos Fusion Data Center in Junos OS Release 18.1R3.
SEE ALSO
New and Changed Features | 52
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
58
Known Behavior
IN THIS SECTION
Junos Fusion Data Center | 59
This section lists known behavior, system maximums, and limitations in hardware and software in Junos
OS Release 18.1R3 for Junos Fusion Data Center.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Junos Fusion Data Center
The license installed will not be deleted, unless it is explicitly deleted using the request command. After
•
disabling the cascade port, the license count will be marked as zero only after the satellite information
is purged from the neighbor database. Previously, this satellite neighbor information persisted only for
8 minutes; now, neighbor information is being held for 8 hours. This time delay is introduced to avoid
repeating the initial recognition of the satellite device for interface-down events. As a workaround,
delete the FPC instance for the satellite device to see the license removed for the corresponding satellite
device. PR1192886
In a Junos Fusion Data Center, auto-channelization is not supported on 100G interfaces. As a workaround,
•
you can set the channelization using the channel-speed CLI statement at the [edit policy-options
satellite-policies extended-ports-template template-name pic pic-number port port-number] hierarchy
level.
The license installed will not be deleted, unless it is explicitly deleted using the request command. After
•
disabling the cascade port, the license count will be marked as zero only after the satellite information
is purged from the neighbor database. Previously this satellite neighbor information persisted for only
for 8 minutes; now neighbor information is being held for 8 hours. This time delay is introduced to avoid
repeating the initial recognition of the satellite device for interface-down events. user@host> show
configuration | display set | grep et-0/0/30 set groups user-host-grp interfaces et-0/0/30 cascade-port
set chassis satellite-management fpc 101 cascade-ports et-0/0/30 set interfaces et-0/0/30 disable
{master:0} user@host> show chassis satellite terse Device Extended Ports Slot State Model Total/Up
Version 100 Online EX4300-48T 50/1 17.4-20170726_common_xxx.0 102 Online QFX5200-32C-32Q
2/1 17.4-20170726_common_xxx.0 103 Online QFX5110-48S-4C 3/2 17.4-20170726_common_xxx.0
{master:0} user@host> show chassis satellite neighbor Interface State Port Info System Name Model
SW Version et-0/0/30 Dn et-0/0/18 Two-Way et-0/0/18 sd102 QFX5200-32C-32Q
17.4-20170726_common_xxx.0 et-0/0/12 Two-Way et-0/0/50 sd103 QFX5110-48S-4C
17.4-20170726_common_xxx.0 et-0/0/6 Two-Way et-0/1/3 sd100 EX4300-48T
17.4-20170726_common_xxx.0 {master:0} user@host> show system license License usage: Licenses
Licenses Licenses Expiry Feature name used installed needed bgp 1 0 1 invalid SD-QFX5100-48SH-48TH
0 4 0 permanent Licenses installed: License identifier: JUNOSxxxxxx License version: 4 Software Serial
Number: 99999B99999999 Customer ID: USER-SWITCH Features: SD-QFX5100-48SH-48TH-4PK SD 4 pack QFX5000-10-JFD permanent {master:0} user@host> show system license usage Licenses
Licenses Licenses Expiry Feature name used installed needed bgp 1 0 1 invalid SD-QFX5100-48SH-48TH
0 4 0 permanent {master:0} user@host> show system alarms 4 alarms currently active Alarm time Class
Description 2017-08-29 13:14:27 UTC Minor BGP Routing Protocol usage requires a license 2017-08-28
17:25:27 UTC Major FPC0: PEM 1 Not Powered 2017-08-28 17:25:27 UTC Major FPC Management1
Ethernet Link Down PR1294951
59
In a Junos Fusion Data Center, configuration synchronization is not triggered when you issue the rollback
•
command on the local aggregation device (AD). PR1298747
During a satellite device (SD) upgrade in Junos Fusion, there is a condition that the Link Aggregation
•
Control Protocol (LACP) defaulted PDU received from the peer device connected in a link aggregation
group (LAG) is incorrectly sent to an aggregation device (AD) with aggregated Ethernet e-Channel
Identifier (ECID) instead of member ECID, which causes that LACP PDU to be received on another
member in the LAG, resulting in the LAG interface flapping. PR1321575
In a Junos Fusion Data Center with EVPN solution, when an Aggregation Device loses EVPN connectivity
•
with rest of the aggregation devices, then LACP over extended ports on this core isolated aggregation
device will be brought down until EVPN connectivity is restored. PR1327784
On a Junos Fusion Data Center, traffic is dropped when the aggregation device (AD) goes down because
•
the routes advertised by that AD are withdrawn. As a workaround, configure the hold-time on uplink
interfaces using the set interfaces interface hold-time up <300 * 1000> command. PR1331465
On the QFX10000, EVPN NSR Unicast is not currently supported.PR1337645
•
This issue was seen with UBS scale: however, with PLM scale this issue is not seen in latest releases.
•
PR1338659
In the following Junos OS releases, the EVI-RT extended community as defined in
•
draft-ietf-bess-evpn-igmp-mld-proxy-00 was not being attached to advertised Type 7 routes: 17.2,
17.3R1, 17.3R2, and 17.4R1. Starting with the following Junos OS releases, the EVI-RT is mandatory
and Type 7 routes that do not carry this community will be ignored: 17.3R3, 17.4R2, 18.1R1 and later.
An EVPN network enabled with IGMP snooping and having a mix of multi-homed peer PEs with some
running the older releases (17.2, 17.3R1, 17.3R2, 17.4R1) and some running the newer releases (17.3R3,
17.4R2, 18.1R1 and later) will not be able to inter-operate since Type 7 routes advertised without the
EVI-RT community by PEs running an older release will be ignored by PEs running the newer releases
and will not result in creation of IGMP snooping state. PR1341807
60
In Junos Fusion with EVPN solution when an Aggregation Device looses EVPN connectivity with rest
•
of the aggregation devices, then LACP over extended ports on this core isolated Aggregation Device
will be brought down until EVPN connectivity is restored. PR1342045
When some of the EX4300 satellite devices are rebooted, they stay in offline state as packets get
•
corrupted or dropped due to internal FIFO logic error. As a workaround, restart the satellite device PFE
process. PR1349508
On platforms with dual routing engines, GRES will result in considerable traffic loss/duplication for EVPN
•
traffic. The traffic should restore eventually once convergence is complete. PR1350744
Partial ingress traffic can be mirrored on Junos Fusion Data Center setup with a few triggers, such as
•
aggregation device and satellite device reboot, configuration reboot of traffic generator connected to
satellite devices etc. As a workaround, flap of mirror output interface resolves the issue. PR1352827
In Junos OS, two different input filters cannot be configured on the same interface; if two filters are
•
configured, only the second filter (the one that was configured most recently) takes effect. Ingress
mirroring on extended ports in Junos Fusion Data Center (JFDC) can only be done by using firewall
filters. Due to the Junos OS filter behavior, in JFDC, ingress mirroring on extended ports and other
firewall filter configurations cannot be done on the same port. PR1353065
Since EVPN graceful restart is not supported, restart of the rpd process will result in considerable traffic
•
loss for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1353742
Two aggregation devices going down at the same time will result in considerable traffic loss/duplication
•
for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1354443
On an aggregation device (AD), if the mirror destination interface is down then the mirror gets globally
•
removed from all FPCs of the AD. The mirror is reprogrammed back when the mirror destination interface
is up again. Until the mirror stays down, sampling won’t be functional on the given AD. PR1360003
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Issues | 61
Resolved Issues | 62
61
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
Known Issues
This section lists the known issues in hardware and software in Junos OS Release 18.1R3 for Junos Fusion
Data Center.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Junos Fusion Data Center
Partial ingress traffic can be mirrored on Junos Fusion setup with some triggers, such as a reboot of the
•
aggregation or satellite device or a configuration reboot of traffic generator connected to the satellite
devices. As a workaround, flapping the mirror output interface resolves the issue. PR1352827
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
Resolved Issues
IN THIS SECTION
Resolved Issues: 18.1R3 | 62
Resolved Issues: 18.1R2 | 62
62
Resolved Issues: 18.1R1 | 63
This section lists the issues fixed in the Junos OS Release 18.1R3 for Junos Fusion Data Center.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Resolved Issues: 18.1R3
In a Junos Fusion setup, a DCPFE core file is generated after executing the sh shim bridge bd bd-index
•
command in the PFE. PR1296738
Resolved Issues: 18.1R2
Junos Fusion Data Center
On a Junos Fusion topology with QFX10002 switches as aggregate devices having dual cascade links
•
to each satellite devices for redundancy, duplicated multicast traffic might be seen on downstream
devices and multicast receivers if the multicast traffic passes through the aggregate devices. As a
workaround, deactivate and re-activate the VLAN in which duplicated multicast traffic is seen. PR1316499
In a Junos Fusion setup, an aggregate device may show a plus sign on the ICL link for a satellite device.
•
PR1335373
Resolved Issues: 18.1R1
Junos Fusion Data Center
In a Junos Fusion topology with LAG on extended ports from satellite devices which are dual-homed to
•
aggregation devices, the LAG interface might flap if rebooting one of the aggregation devices. PR1315879
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
63
Product Compatibility | 71
Documentation Updates
This section lists the errata or changes in Junos OS Release 18.1R3 for Junos Fusion Data Center
documentation.
New Simplified Documentation Architecture
With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make
•
it easier for you to find information and know that you can rely on it when you find it. In the past, we
organized documentation about Junos OS software features into platform-specific documents. In many
cases, features are supported on multiple platforms, so you might not easily find the document you want
for your platform.
With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For
example, if you want to find documentation on OSPF, there is only one document regardless of which
platform you have. Here are some of the benefits of our new simplified architecture:
Over time, you will see better search results when looking for Juniper documentation. You will be able
•
to find what you want faster and be assured that is the right document.
If a software feature is supported on multiple platforms, you can find information about all the platforms
•
in one place.
Because we have eliminated many documents that covered similar topics, you will now find one
•
document with all the information.
You can know that you are always getting the most current and accurate information.
•
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Migration, Upgrade, and Downgrade Instructions | 64
Product Compatibility | 71
64
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Basic Procedure for Upgrading an Aggregation Device | 64
Preparing the Switch for Satellite Device Conversion | 66
Configuring Satellite Device Upgrade Groups | 68
Converting a Satellite Device to a Standalone Device | 69
Upgrade and Downgrade Support Policy for Junos OS Releases | 70
Downgrading from Junos OS Release 18.1 | 70
This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for
Junos OS for Junos Fusion Data Center. Upgrading or downgrading Junos OS can 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 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.
65
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 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 command.
user@host> request system software add reboot source/package-name
All other customers, use the following command.
user@host> request system software add reboot source/package-name
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:
•
66
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 can take 5 to 10 minutes.
Rebooting occurs only if the upgrade is successful.
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 Junos
Fusion Hardware and Software Compatibility Matrices.
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 Junos switch can only be converted to SNOS 3.1 and higher.
•
The Junos switch must be either set to factory default configuration 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, replacing n with the spin number:
user@host> request system software add validate reboot
source/jinstall-ex-4300-14.1X53-D43.n-domestic-signed.tgz
Customers with QFX5100 switches, use the following command, replacing n with the spin number:
67
user@host> request system software add validate reboot
source/jinstall-qfx-5-14.1X53-D43.n-domestic-signed.tgz
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 entering 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:
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, and preconfiguration. See Configuring or Expanding a Junos
Fusion Data Center for detailed configuration steps for each method.
68
Configuring Satellite Device Upgrade Groups
To simplify the upgrade process for multiple satellite devices, you can create a software upgrade group at
the aggregation device, assign satellite devices to the group, and install the satellite software on a groupwide
basis.
To create a software upgrade group and assign satellite devices to the group, include the satellite statement
at the [edit chassis satellite-management upgrade-groups upgrade-group-name] hierarchy level.
To configure a software upgrade group and assign satellite devices to the group:
1. Log in to the aggregation device.
2. Create the software upgrade group, and add the satellite devices to the group.
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups
upgrade-group-name satellite satellite-member-number-or-range
upgrade-group-name is the name of the upgrade group, and the satellite-member-number-or-range is the
member numbers of the satellite devices that are being added to the upgrade group. If you enter an existing
upgrade group name as the upgrade-group-name, you add new satellite devices to the existing software
upgrade group.
For example, to create a software upgrade group named group1 that includes all satellite devices numbered
101 through 120, configure the following:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups group1 satellite
101-120
To install, remove, or roll back a satellite software version on an upgrade group, issue the following
operational mode commands:
request system software add upgrade-group group-name—Install the satellite software on all members
•
of the specified upgrade group.
request system software delete upgrade-group group-name—Remove the satellite software association
•
from the specified upgrade group.
request system software rollback upgrade-group group-name—Associate an upgrade group with a
•
previous version of satellite software.
69
Customers installing satellite software on EX4300 and QFX5100 switches referenced in a software upgrade
group, use the following command:
user@aggregation-device> request system software add upgrade-group group-name
source/package-name
NOTE: Before issuing request system software add upgrade-group group-name, you must issue
a one-time command to expand the storage capacity. Use the request system storage user-disk
expand command to increase the size of /user partition.
A copy of the satellite software is saved on the aggregation device. When you add a satellite device to an
upgrade group that is not running the same satellite software version, the new satellite device is
automatically updated to the version of satellite software that is associated with the upgrade group.
You can issue the show chassis satellite software command to see which software images are stored on
the aggregation device and which upgrade groups are associated with the software images.
Converting a Satellite Device to a Standalone Device
In the event that you need to convert a satellite device to a standalone device, you will need to 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
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 even
from Junos OS Release 17.1 to Release 17.3.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead
or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before
or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release
to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see
https://www.juniper.net/support/eol/junos.html.
70
Downgrading from Junos OS Release 18.1
To downgrade from Junos OS Release 18.1 to another supported release, follow the procedure for
upgrading, but replace the 18.1 jinstall package with one that corresponds to the appropriate downgrade
release.
NOTE: You cannot downgrade more than three releases.
For more information, see the Installation and Upgrade Guide.
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Documentation Updates | 63
Product Compatibility | 71
Product Compatibility
IN THIS SECTION
Hardware and Software Compatibility | 71
Hardware Compatibility Tool | 71
Hardware and Software Compatibility
For a complete list of all hardware and software requirements for a Junos Fusion Data Center, including
which Juniper Networks devices function as satellite devices, see Understanding Junos Fusion Data Center
Software and Hardware Requirements in the Junos Fusion Data Center User Guide.
71
To obtain information about the components that are supported on the devices, and special compatibility
guidelines with the release, see the Hardware Guides for the devices used in your Junos Fusion Data
Center topology.
To determine the features supported in a Junos Fusion, use the Juniper Networks Feature Explorer, a
Web-based application that helps you to explore and compare Junos OS feature information to find the
right software release and hardware platform for your network. Find Feature Explorer at
https://pathfinder.juniper.net/feature-explorer/
Hardware Compatibility Tool
For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms,
see the Hardware Compatibility tool.
SEE ALSO
New and Changed Features | 52
Changes in Behavior and Syntax | 58
Known Behavior | 58
Known Issues | 61
Resolved Issues | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 64
Junos OS Release Notes for Junos Fusion Enterprise
IN THIS SECTION
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
72
These release notes accompany Junos OS Release 18.1R3 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.
New and Changed Features
IN THIS SECTION
Release 18.1R3 New and Changed Features | 73
Release 18.1R2 New and Changed Features | 73
Release 18.1R1 New and Changed Features | 73
This section describes the new features and enhancements to existing features in Junos OS Release 18.1R3
for Junos Fusion Enterprise.
NOTE: For more information about the Junos Fusion Enterprise features, see the Junos Fusion
Enterprise User Guide.
Release 18.1R3 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Enterprise in Junos
•
OS Release 18.1R3.
Release 18.1R2 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Enterprise in Junos
•
OS Release 18.1R2.
73
Release 18.1R1 New and Changed Features
Junos Fusion Enterprise
Aggregation device support on EX9251 switches (Junos Fusion Enterprise)—Starting with Junos OS
•
Release 18.1R1, EX9251 switches are supported as aggregation devices in a Junos Fusion Enterprise.
The aggregation device acts as the single point of management for all devices in the Junos Fusion
Enterprise. Junos Fusion Enterprise supports the 802.1BR standard.
[See Junos Fusion Enterprise Overview.]
SEE ALSO
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
Changes in Behavior and Syntax
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 18.1R3 for Junos Fusion Enterprise.
SEE ALSO
New and Changed Features | 72
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
74
Known Behavior
There are no known behaviors, system maximums, and limitations in hardware and software in Junos OS
Release 18.1R3 for Junos Fusion 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
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
Known Issues
IN THIS SECTION
Junos Fusion Enterprise | 75
This section lists the known issues in hardware and software in Junos OS Release 18.1R3 for Junos Fusion
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 Enterprise
75
On a Junos Fusion, when using LLDP, the Power via MDI and Extended Power via MDI TLVs are not
•
transmitted. PR1105217
On a Junos Fusion Enterprise, when the satellite devices of a cluster are rebooted, the output of the CLI
•
command show chassis satellite shows the port state of the cascade ports as Present. PR1175834
In a Junos Fusion Enterprise, it could take 6 to 30 seconds for the traffic to converge when on the
•
aggregation device is powered OFF or powered ON. PR1257057
In a Junos Fusion Enterprise, during RE switchover, the BUM traffic is duplicated to indirectly connected
•
satellite devices. This is because there is no current support to notify the GRES event to indirectly
connected satellite devices. PR1298434
In a Junos Fusion Enterprise, after an automatic POE firmware upgrade, the satellite device reboots.
•
PR1359065
SEE ALSO
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
Resolved Issues
IN THIS SECTION
Resolved Issues: 18.1R3 | 76
Resolved Issues: 18.1R2 | 76
Resolved Issues: 18.1R1 | 77
This section lists the issues fixed in the Junos OS main release and the maintenance releases.
76
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Resolved Issues: 18.1R3
A satellite device does not recover PoE after the device is offline for more than 10 minutes and rejoins
•
the aggregation device. PR1345365
The ppm-lite process might generate a core file on the Fusion satellite devices. PR1364265
•
Resolved Issues: 18.1R2
In a Junos Fusion Enterprise in which port mirroring analyzers are configured, mirrored packets are
•
dropped when the packets must traverse the interchassis link (ICL) link to reach destination extended
ports. As a workaround, you can alternatively configure a remote switched port analyzer (RSPAN) VLAN
with the extended ports and the ICL link as members and configure the RSPAN VLAN as the analyzer
destination. PR1211123
In a Junos Fusion setup, an aggregate device may show a plus sign on the ICL link for a satellite device.
•
PR1335373
Issue with 802.1X re-authentication in Junos Fusion Enterprise. PR1345365
•
Resolved Issues: 18.1R1
Request chassis satellite beacon functionality to specific satellite device is not working, causing all the
•
satellite devices to enable the beacon LED. PR1272956
On a Junos Fusion Enterprise with dual aggregation devices (ADs), if you apply Routing Engine loopback
•
filters and bring down the cascade port on one of the ADs, the satellite device (SD) on the AD where
the cascade port is down goes to ProvSessDown due to a TCP session drop over the ICL interface.
PR1275290
Junos Fusion : SD EX4300 displaying U-Boot on LCD screen. PR1304784
•
All 802.1X authentication sessions are removed when the AUTO ICCP link is disabled. PR1307588
•
LACP aggregated Ethernet interfaces go to down state when performing commit synchronize. PR1314561
•
Packets loss for 2-3 seconds is seen in every 5 minutes on Junos Fusion. PR1320254
•
In a Junos Fusion Enterprise deployment, an SCPD core might be seen on an aggregation device when
•
DACL on dot1x enabled port is installed on a single homed satellite device.. PR1328247
77
When the ICCP and IFBDs are in transition--Down/Up--DHCP security binding entries might be missing
•
from server database. PR1332828
SEE ALSO
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
Documentation Updates
This section lists the errata and changes in Junos OS Release 18.1R3 documentation for Junos Fusion.
New Simplified Documentation Architecture
With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make
•
it easier for you to find information and know that you can rely on it when you find it. In the past, we
organized documentation about Junos OS software features into platform-specific documents. In many
cases, features are supported on multiple platforms, so you might not easily find the document you want
for your platform.
With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For
example, if you want to find documentation on OSPF, there is only one document regardless of which
platform you have. Here are some of the benefits of our new simplified architecture:
Over time, you will see better search results when looking for Juniper documentation. You will be able
•
to find what you want faster and be assured that is the right document.
If a software feature is supported on multiple platforms, you can find information about all the platforms
•
in one place.
Because we have eliminated many documents that covered similar topics, you will now find one
•
document with all the information.
You can know that you are always getting the most current and accurate information.
•
78
SEE ALSO
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Migration, Upgrade, and Downgrade Instructions | 78
Product Compatibility | 84
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 79
Upgrading an Aggregation Device with Redundant Routing Engines | 81
Preparing the Switch for Satellite Device Conversion | 81
Converting a Satellite Device to a Standalone Switch | 83
Upgrade and Downgrade Support Policy for Junos OS Releases | 83
Downgrading Junos OS | 83
This section contains the procedure to upgrade or downgrade Junos OS and satellite software for a Junos
Fusion 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.
79
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 Release 18.1R2:
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.
80
Customers in the United States and Canada, use the following command:
user@host> request system software add validate reboot source/package-name
All other customers, use the following command:
user@host> request system software add validate reboot source/package-name
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.
81
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 Junos switch can only be converted to SNOS 3.1 and higher.
•
The Junos switch must be either set to factory default configuration to factory default
•
configuration 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.
82
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
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.
83
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead
or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before
or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release
to your target release.
For more information on EEOL releases and to review a list of EEOL releases, see
https://www.juniper.net/support/eol/junos.html
Downgrading 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, follow the procedure for upgrading, but replace the junos-install
package with one that corresponds to the appropriate release.
SEE ALSO
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Product Compatibility | 84
Product Compatibility
IN THIS SECTION
Hardware and Software Compatibility | 84
Hardware Compatibility Tool | 84
84
Hardware and Software Compatibility
For a complete list of all hardware and software requirements for a Junos Fusion Enterprise, including
which Juniper Networks devices function as satellite devices, see Understanding Junos Fusion Enterprise
Software and Hardware Requirements in the Junos Fusion Enterprise User Guide.
To determine the features supported in a Junos Fusion, use the Juniper Networks Feature Explorer, a
Web-based application that helps you to explore and compare Junos OS feature information to find the
right software release and hardware platform for your network. Find Feature Explorer at:
https://pathfinder.juniper.net/feature-explorer/
Hardware Compatibility Tool
For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms,
see the Hardware Compatibility tool.
SEE ALSO
New and Changed Features | 72
Changes in Behavior and Syntax | 74
Known Behavior | 74
Known Issues | 75
Resolved Issues | 76
Documentation Updates | 77
Migration, Upgrade, and Downgrade Instructions | 78
85
Junos OS Release Notes for Junos Fusion Provider Edge
IN THIS SECTION
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Behavior | 90
Known Issues | 91
Resolved Issues | 92
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
86
These release notes accompany Junos OS Release 18.1R3 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.
New and Changed Features
IN THIS SECTION
Release 18.1R3 New and Changed Features | 88
Release 18.1R2 New and Changed Features | 88
Release 18.1R1 New and Changed Features | 88
This section describes the new features and enhancements to existing features in the Junos OS main
release and the maintenance releases for Junos Fusion Provider Edge.
87
Release 18.1R3 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos
OS Release 18.1R3.
Release 18.1R2 New and Changed Features
There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos
OS Release 18.1R2.
Release 18.1R1 New and Changed Features
Hardware
Support for QFX5110 and QFX5200 as satellite devices in Junos Fusion Provider Edge—Starting in
•
Junos OS Release 18.1R1, you can use QFX5110-48S or QFX5200-32C switches as satellite devices in
Junos Fusion Provider Edge.
88
[See Satellite Device Hardware Models and Preparing the Satellite Device.]
Class of Service (CoS)
Support for dynamic mapping of extend ports to cascade ports for hierarchical CoS (Junos Fusion
•
Provider Edge)—Junos Fusion treats the cascade ports connecting the aggregation device to the satellite
device as aggregated Ethernet ports with aggregation done automatically without configuration. By
default the Junos Fusion implementation of hierarchical CoS applies the scheduler parameters across
all cascade ports in scale mode. Because scale mode divides the configured shaper equally across the
cascade ports, traffic drops can start before a customer reaches its committed rate for a particular flow.
To avoid this problem, starting with Junos OS Release 18.1R1, you can set all cascade ports on an
aggregation device to be in replicate mode and automatically target all of a customer’s traffic to a specific
cascade port. To do this, simply enable target-mode at the [edit chassis satellite-management fpc
fpc-number] hierarchy level.
[See Understanding CoS on an MX Series Aggregation Device in Junos Fusion.]
Junos Fusion
Junos Fusion Provider Edge support for Junos Node Slicing (MX960, MX2010, MX2020)—Starting in
•
Junos OS Release 18.1R1, you can configure an aggregation device on guest network functions (GNFs),
or partitions created on a router, by using Junos Node Slicing. The Junos Fusion topology is composed
of an aggregation device and multiple satellite devices. An MX Series router supports a maximum of 10
GNFs, with each GNF supporting a separate aggregation device. The aggregation device on a GNF
supports a maximum of 10 satellite devices. The aggregation device acts as the single point of management
for all devices in a Junos Fusion topology, while the satellite devices provide interfaces that send and
receive network traffic.
For more information on Junos Node Slicing, see Junos Node Slicing Overview.
NOTE:
In a Junos Fusion Provider Edge topology that has a GNF configured as the aggregation
•
device, you can only use EX4300 switches as satellite devices.
Only the following line cards support the cascade port on the aggregation device:
•
MPC7E-MRATE, MPC7E-10G, MPC8 and MPC9.
89
[See Understanding Junos Fusion Provider Edge Components.]
SEE ALSO
Changes in Behavior and Syntax | 89
Known Behavior | 90
Known Issues | 91
Resolved Issues | 92
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Changes in Behavior and Syntax
There are no changes in default behavior and syntax for Junos Fusion Provider Edge in Junos OS Release
18.1R3.
SEE ALSO
New and Changed Features | 86
Known Behavior | 90
Known Issues | 91
Resolved Issues | 92
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Known Behavior
IN THIS SECTION
Junos Fusion | 90
90
This section lists known behavior, system maximums, and limitations in hardware and software in Junos
OS Release 18.1R3 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
Configuration synchronization is not triggered when you issue the rollback command on the local
•
aggregation device (AD). PR1298747
In Junos OS, two different input filters cannot be configured on the same interface; if two filters are
•
configured, only the second filter (the one that was configured most recently) takes effect. Ingress
mirroring on extended ports in Junos Fusion Data Center (JFDC) can only be done by using firewall
filters. Considering the Junos OS filter behavior described above, in JFDC, ingress mirroring on extended
ports and other firewall filter configurations cannot be done on the same port. PR1353065
Since EVPN GR is not supported, restart of rpd will result in considerable traffic loss for EVPN traffic.
•
The traffic should restore eventually once convergence is complete. PR1353742
Restart of rpd will result in considerable traffic loss/duplication for EVPN traffic. The traffic should
•
restore eventually once convergence is complete. PR1350040
SEE ALSO
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Issues | 91
Resolved Issues | 92
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Known Issues
IN THIS SECTION
91
Junos Fusion | 91
This section lists the known issues in hardware and software in Junos OS Release 18.1R3 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
During Satellite Device (SD) upgrade in Junos Fusion, there is a race condition that the Link Aggregation
•
Control Protocol (LACP) defaulted PDU received from the peer device connected in a link aggregation
group (LAG) is incorrectly sent to an aggregation device (AD) with aggregated Ethernet E-channel
Identifier (ECID) instead of member ECID, which causes that LACP PDU to be received on another
member in the LAG, resulting in the LAG interface flapping. PR1321575
SEE ALSO
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Behavior | 90
Resolved Issues | 92
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Resolved Issues
IN THIS SECTION
Resolved Issues: 18.1R3 | 92
Resolved Issues: 18.1R2 | 92
Resolved Issues: 18.1R1 | 93
92
This section lists the issues fixed in the Junos OS main release and the maintenance releases.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Resolved Issues: 18.1R3
There are no fixed issues in the Junos OS Release 18.1R3 for Junos Fusion Provider Edge.
Resolved Issues: 18.1R2
Junos Fusion
Duplicated packets might be received on the multicast downstream devices and multicast receivers.
•
PR1316499
In Junos Fusion, the show interfaces diagnostics optics satellite command does not display any outputs.
•
PR1327876
In a Junos Fusion setup, an aggregate device might show a plus sign (+) on the ICL link for a satellite
•
device. PR1335373
SSH key-based authentication does not work with Junos Fusion. PR1344392
•
AD failure (power off) in a DC fusion is causing complete or partial traffic loss for an extended period.
•
PR1352167
Resolved Issues: 18.1R1
Junos Fusion
Chassis alarms are not generated after the uplinks are made down from SD. PR1275480
•
The LAG interface might flap if rebooting aggregation device. PR1315879
•
Duplicated packets might be received on the multicast downstream devices and multicast receivers.
•
PR1316499
Not able to disable fpc-slot .Getting error Operation not supported for device assigned slot-id. PR1321268
•
93
SEE ALSO
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Behavior | 90
Known Issues | 91
Documentation Updates | 93
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Documentation Updates
IN THIS SECTION
New Simplified Documentation Architecture | 94
This section lists the errata and changes in Junos OS Release 18.1R3 for Junos Fusion Provider Edge.
New Simplified Documentation Architecture
With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make
•
it easier for you to find information and know that you can rely on it when you find it. In the past, we
organized documentation about Junos OS software features into platform-specific documents. In many
cases, features are supported on multiple platforms, so you might not easily find the document you want
for your platform.
With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For
example, if you want to find documentation on OSPF, there is only one document regardless of which
platform you have. Here are some of the benefits of our new simplified architecture:
Over time, you will see better search results when looking for Juniper documentation. You will be able
•
to find what you want faster and be assured that is the right document.
If a software feature is supported on multiple platforms, you can find information about all the platforms
•
in one place.
Because we have eliminated many documents that covered similar topics, you will now find one
•
document with all the information.
94
You can know that you are always getting the most current and accurate information.
•
SEE ALSO
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Behavior | 90
Known Issues | 91
Resolved Issues | 92
Migration, Upgrade, and Downgrade Instructions | 94
Product Compatibility | 101
Migration, Upgrade, and Downgrade Instructions
IN THIS SECTION
Basic Procedure for Upgrading an Aggregation Device | 95
Upgrading an Aggregation Device with Redundant Routing Engines | 97
Preparing the Switch for Satellite Device Conversion | 98
Converting a Satellite Device to a Standalone Device | 99
Upgrading an Aggregation Device | 99
Upgrade and Downgrade Support Policy for Junos OS Releases | 99
Downgrading from Junos OS Release 18.1 | 100
This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for
Junos OS for Junos Fusion 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.
95
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.
The download and installation process for Junos OS Release 18.1R3 is different 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 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.
96
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.
NOTE: We highly recommend that you see 64-bit Junos OS software when implementing
Junos Fusion Provider Edge.
For upgrades from Junos Release 14.2 and earlier:
user@host> request system software add no-validate reboot source/package-name
All other upgrades:
user@host> request system software add validate reboot source/package-name
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.
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.
97
NOTE: After you install a Junos OS Release 18.1R3 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 only be converted to SNOS 3.1 and higher.
•
The switch must be either set to factory-default configuration using the request system zeroize
•
command, or the following command must be included in the configuration: set chassis
auto-satellite-conversion.
98
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 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 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:
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
99
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, and preconfiguration. See Configuring Junos Fusion Provider
Edge for detailed configuration steps for each method.
Converting a Satellite Device to a Standalone Device
In the event that you need to convert a satellite device to a standalone device, you will need to 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.
Upgrading an Aggregation Device
When you upgrade an aggregation device to Junos OS Release 18.1R3, you must also upgrade your satellite
device to Satellite Device Software version 3.1R1.
Upgrade and Downgrade Support Policy for Junos OS Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not
provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases
provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the
next EEOL release even though EEOL releases generally occur in increments beyond three releases.
You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently
installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1,
17.2 and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from
Junos OS Release 17.1 to Release 17.3.
You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead
or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before
or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release
to your target release.
For more information about EEOL releases and to review a list of EEOL releases, see
https://www.juniper.net/support/eol/junos.html.
Downgrading from Junos OS Release 18.1
To downgrade from Junos OS Release 18.1 to another supported release, follow the procedure for
upgrading, but replace the 18.1 jinstall package with one that corresponds to the appropriate release.
100
NOTE: You cannot downgrade more than three releases.
For more information, see the Installation and Upgrade Guide.
SEE ALSO
New and Changed Features | 86
Changes in Behavior and Syntax | 89
Known Behavior | 90
Known Issues | 91
Resolved Issues | 92
Documentation Updates | 93
Product Compatibility | 101
Loading...