Junos OS 18.2R1 User Manual
Release
Published
2021-02-05
Notes
Junos®OS 18.2R1 Release Notes
SUPPORTED ON
ACX Series, EX Series, Junos Fusion Enterprise, Junos Fusion Provider Edge, MX Series,
•
NFX Series, PTX Series, QFX Series, and SRX Series
HARDWARE HIGHLIGHTS
Support for new universal metro routers (ACX5448)
•
Support for xDSL SFP module (NFX Series)
•
Support for QFX10000-30C-M line card channelization (QFX10008, QFX10016)
•
SOFTWARE HIGHLIGHTS
Support for VPWS with EVPN signaling mechanisms and flexible cross connect (ACX5448)
•
Support for virtualization (ACX5448)
•
Support for 48x1/10GE and 4x100GE interface ports (ACX5448)
•
Support for Layer 2 features (ACX5448)
•
Support for Layer 3 features (ACX5448)
•
Support for NSR and ISSU for point-to-multipoint LSP for EVPN provider tunnel (EX9200)
•
Support for excluding the overhead bytes from queue statistics (MX Series)
•
Support for OSPF, IS-IS, BGP, and static routing on IRB interfaces in EVPN-VXLAN networks
•
(MX Series, vMX)
Support for unified ISSU (MX10003)
•
Support for PTP over Ethernet and hybrid mode over link aggregation group (MX Series)
•
Support for ON_CHANGE expansion for Junos Telemetry Interface (JTI) (MX Series)
•
Support for local authentication and authorization for subscribers (MX Series)
•
Support for DHCP short-cycle protection to reduce excess loading (MX Series)
•
Support for global range setting for initial router advertisement intervals (MX Series)
•
Support for security features (NFX Series)
•
Support for vMX VNF (NFX250-S1, NFX250-S2)
•
Support for J-Insight device monitor (MX Series, vMX, and “PTX Series”)
•
Support for client link-layer address option 79 for DHCPv6 (QFX Series)
•
Support for zero touch provisioning (QFX10008, QFX10016)
•
Support for advanced policy-based routing (APBR) policy (SRX Series, vSRX)
•
Support for advanced features for logical systems (SRX Series, vSRX)
•
Support for TWAMP ALG traffic (SRX Series)
•
Support for unified policies (SRX Series, vSRX)
•
Release Notes: Junos®OS Release 18.2R1 for
the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and
Junos Fusion
1
05 February 2021
Contents
Introduction | 13
Junos OS Release Notes for ACX Series | 13
New and Changed Features | 14
Hardware | 15
Authentication Access Control | 15
Class of Service | 16
Dynamic Host Configuration Protocol | 16
EVPN | 16
General Routing | 17
Routing Policy and Firewall Filters | 19
Interfaces and Chassis | 19
Layer 2 Features | 19
Layer 3 Features | 21
Management | 21
MPLS | 21
Multicast | 22
Routing Protocols | 23
Security | 23
Software Installation and Upgrade | 23
Timing and Synchronization | 24
Changes in Behavior and Syntax | 25
High Availability (HA) and Resiliency | 25
Junos XML API and Scripting | 25
Layer 3 Features | 25
Known Behavior | 26
Known Issues | 26
Class of Service | 27
DHCP | 27
IGMP Snooping | 28
Timing and Synchronization | 28
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
2
Upgrade and Downgrade Support Policy for Junos OS Releases | 30
Product Compatibility | 30
Hardware Compatibility | 31
Junos OS Release Notes for EX Series Switches | 32
New and Changed Features | 32
Hardware | 33
Authentication, Access Control | 34
Authentication, Authorization, and Accounting (AAA) | 35
Class of Service (CoS) | 35
Dynamic Host Configuration Protocol (DHCP) | 35
EVPN | 35
Interfaces and Chassis | 38
Layer 2 Features | 39
Operation, Administration, and Maintenance (OAM) | 40
Port Security | 40
Restoration Procedures Failure | 43
Software Installation and Upgrade | 43
Software Licensing | 43
System Management | 44
User Interface and Configuration | 44
Virtual Chassis | 44
Changes in Behavior and Syntax | 45
EVPN | 47
High Availability (HA) and Resiliency | 47
Interfaces and Chassis | 47
Junos OS XML, API, and Scripting | 47
Junos Telemetry Interface | 47
Layer 2 Features | 48
Multicast | 48
Network Management and Monitoring | 48
Software Installation and Upgrade | 48
User Interface and Configuration | 49
Known Behavior | 50
General Routing | 50
3
Known Issues | 51
Authentication and Access Control | 51
General Routing | 51
High Availability (HA) and Resiliency | 52
Infrastructure | 52
Platform and Infrastructure | 52
Resolved Issues | 53
Forwarding and Sampling | 53
General Routing | 53
Interfaces and Chassis | 54
Layer 2 Features | 54
Layer 2 Ethernet Services | 54
MPLS | 54
Platform and Infrastructure | 54
Documentation Updates | 55
Migration, Upgrade, and Downgrade Instructions | 55
Upgrade and Downgrade Support Policy for Junos OS Releases | 56
Product Compatibility | 57
Hardware Compatibility | 57
Junos OS Release Notes for Junos Fusion Enterprise | 58
New and Changed Features | 58
Junos Fusion Enterprise | 59
Changes in Behavior and Syntax | 60
High Availability (HA) and Resiliency | 60
Known Behavior | 60
Junos Fusion Enterprise | 61
Known Issues | 61
Junos Fusion Enterprise | 62
Resolved Issues | 62
Resolved Issues: 18.2R1 | 62
Documentation Updates | 63
Migration, Upgrade, and Downgrade Instructions | 63
Basic Procedure for Upgrading Junos OS on an Aggregation Device | 64
4
Upgrading an Aggregation Device with Redundant Routing Engines | 66
Preparing the Switch for Satellite Device Conversion | 66
Converting a Satellite Device to a Standalone Switch | 68
Upgrade and Downgrade Support Policy for Junos OS Releases | 68
Downgrading from Junos OS Release 18.2 | 68
Product Compatibility | 69
Hardware and Software Compatibility | 69
Hardware Compatibility Tool | 69
Junos OS Release Notes for Junos Fusion Provider Edge | 70
New and Changed Features | 70
Changes in Behavior and Syntax | 71
High Availability (HA) and Resiliency | 71
Known Behavior | 72
Junos Fusion | 72
Known Issues | 73
Junos Fusion | 73
Resolved Issues | 74
Class of Service (CoS) | 74
Junos Fusion | 74
Documentation Updates | 75
Migration, Upgrade, and Downgrade Instructions | 75
Basic Procedure for Upgrading an Aggregation Device | 76
Upgrading an Aggregation Device with Redundant Routing Engines | 78
Preparing the Switch for Satellite Device Conversion | 79
Converting a Satellite Device to a Standalone Device | 80
Upgrading an Aggregation Device | 83
Upgrade and Downgrade Support Policy for Junos OS Releases | 83
Downgrading from Release 18.2 | 83
Product Compatibility | 84
Hardware Compatibility | 84
Junos OS Release Notes for MX Series 5G Universal Routing Platforms | 85
New and Changed Features | 86
Release 18.2R1-S4 New and Changed Features | 86
Release 18.2R1-S2 New and Changed Features | 86
5
Release 18.2R1 New and Changed Features | 87
Changes in Behavior and Syntax | 107
EVPN | 107
General Routing | 108
High Availability (HA) and Resiliency | 109
Interfaces and Chassis | 109
Junos OS XML API and Scripting | 109
Junos Telemetry Interface | 109
MPLS | 109
Network Management and Monitoring | 110
Software Installation and Upgrade | 110
Subscriber Management and Services | 111
User Interface and Configuration | 111
Known Behavior | 112
General Routing | 113
EVPN | 114
Forwarding and Sampling | 114
Interfaces and Chassis | 114
Routing Protocols | 115
Services Applications | 115
Known Issues | 116
EVPN | 116
Forwarding and Sampling | 117
General Routing | 118
Infrastructure | 121
Interfaces and Chassis | 122
Layer 2 Features | 122
MPLS | 122
Network Management and Monitoring | 123
Platform and Infrastructure | 123
Routing Protocols | 124
Resolved Issues | 125
Application Layer Gateways (ALGs) | 126
Class of Service (CoS) | 126
6
EVPN | 126
Forwarding and Sampling | 127
General Routing | 127
High Availability (HA) and Resiliency | 135
Infrastructure | 136
Interfaces and Chassis | 136
Layer 2 Ethernet Services | 137
Layer 2 Features | 137
MPLS | 137
Network Management and Monitoring | 138
Platform and Infrastructure | 138
Routing Policy and Firewall Filters | 140
Routing Protocols | 140
Services Applications | 142
Software Installation and Upgrade | 143
Subscriber Access Management | 143
User Interface and Configuration | 143
VPNs | 143
Documentation Updates | 144
Migration, Upgrade, and Downgrade Instructions | 144
Basic Procedure for Upgrading to Release 18.2 | 145
Procedure to Upgrade to FreeBSD 11.x based Junos OS | 146
Procedure to Upgrade to FreeBSD 6.x based Junos OS | 148
Upgrade and Downgrade Support Policy for Junos OS Releases | 150
Upgrading a Router with Redundant Routing Engines | 150
Downgrading from Release 18.2 | 151
Product Compatibility | 151
Hardware Compatibility | 151
Junos OS Release Notes for NFX Series | 152
New and Changed Features | 153
Hardware | 154
Advanced Policy-Based Routing (APBR) | 154
Security | 154
7
Virtual Network Functions | 154
Changes in Behavior and Syntax | 155
High Availability (HA) and Resiliency | 155
Known Behavior | 156
Allocation of hugepages | 156
Known Issues | 156
BIOS Upgrade | 157
Resolved Issues | 157
Resolved Issues: 18.2R1 | 158
Documentation Updates | 158
Migration, Upgrade, and Downgrade Instructions | 159
Upgrade and Downgrade Support Policy for Junos OS Releases | 159
Basic Procedure for Upgrading to Release 18.2 | 159
Product Compatibility | 161
Hardware Compatibility | 161
Software Version Compatibility | 161
Junos OS Release Notes for PTX Series Packet Transport Routers | 164
New and Changed Features | 164
Hardware | 165
Class of Service (CoS) | 166
High Availability (HA) and Resiliency | 166
Interfaces and Chassis | 166
Junos Telemetry Interface | 167
Layer 3 Features | 168
MPLS | 169
Multicast | 170
Network Management and Monitoring | 171
Operation, Administration, and Maintenance (OAM) | 172
Routing Policy and Firewall Filters | 172
Services Applications | 172
Software Installation and Upgrade | 173
System Management | 173
Changes in Behavior and Syntax | 175
High Availability (HA) and Resiliency | 175
8
Interfaces and Chassis | 175
Junos OS XML API and Scripting | 177
Junos Telemetry Interface | 177
Network Management and Monitoring | 177
Software Installation and Upgrade | 177
Known Behavior | 178
General Routing | 179
Infrastructure | 180
Interfaces and Chassis | 180
Known Issues | 181
General Routing | 181
Infrastructure | 182
Interfaces and Chassis | 183
MPLS | 183
Platform and Infrastructure | 183
Resolved Issues | 184
General Routing | 184
Infrastructure | 186
Interfaces and Chassis | 186
MPLS | 186
Platform and Infrastructure | 186
Routing Protocols | 187
Documentation Updates | 187
Migration, Upgrade, and Downgrade Instructions | 188
Upgrade and Downgrade Support Policy for Junos OS Releases | 188
Upgrading a Router with Redundant Routing Engines | 188
Basic Procedure for Upgrading to Release 18.2 | 189
Installing the Software on PTX10002-60C Routers | 193
Product Compatibility | 194
Hardware Compatibility | 194
Junos OS Release Notes for the QFX Series | 195
New and Changed Features | 195
Hardware | 196
Authentication Access Control | 196
9
EVPN | 197
Junos Telemetry Interface | 199
Port Security | 200
Restoration Procedures Failure | 201
Routing Protocols | 201
Security | 201
Software Installation and Upgrade | 201
System Management | 202
VLAN Infrastructure | 203
Changes in Behavior and Syntax | 203
High Availability (HA) and Resiliency | 205
Interfaces and Chassis | 205
Junos OS XML, API, and Scripting | 205
Junos Telemetry Interface | 205
Network Management and Monitoring | 205
Routing Policy and Firewall Filters | 206
Software Installation and Upgrade | 206
Known Behavior | 207
General Routing | 207
EVPN | 209
Interfaces and Chassis | 209
Layer 2 Features | 209
Routing Protocols | 209
Virtual Chassis | 210
Known Issues | 210
EVPN | 211
General Routing | 212
Interfaces and Chassis | 214
Layer 2 Features | 214
MPLS | 214
Platform and Infrastructure | 214
Routing Protocols | 215
Resolved Issues | 216
EVPN | 216
10
General Routing | 217
Interfaces and Chassis | 220
Junos Fusion Satellite Software | 220
Layer 2 Features | 220
MPLS | 221
Multicast | 221
Platform and Infrastructure | 221
Routing Protocols | 221
Documentation Updates | 222
Migration, Upgrade, and Downgrade Instructions | 223
Upgrading Software on QFX Series Switches | 223
Installing the Software on QFX10002-60C Switches | 226
Installing the Software on QFX10002 Switches | 226
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 | 227
Installing the Software on QFX10008 and QFX10016 Switches | 229
Performing a Unified ISSU | 233
Preparing the Switch for Software Installation | 234
Upgrading the Software Using Unified ISSU | 234
Upgrade and Downgrade Support Policy for Junos OS Releases | 236
Product Compatibility | 237
Hardware Compatibility | 237
Junos OS Release Notes for SRX Series | 238
New and Changed Features | 239
Release 18.2R1-S3 New and Changed Features | 240
Release 18.2R1-S1 New and Changed Features | 240
Release 18.2R1 New and Changed Features | 242
Changes in Behavior and Syntax | 249
API and Scripting | 250
Application Security | 250
Attack Detection and Prevention (ADP) | 252
Authentication and Access | 252
Chassis Cluster | 252
Ethernet Switching | 253
11
High Availability (HA) and Resiliency | 253
Interfaces and Chassis | 253
IDP | 253
Routing Protocols | 253
Security | 253
User Interface and Configuration | 254
UTM | 255
Known Behavior | 256
Chassis Cluster | 256
Interfaces and Chassis | 256
J-Web | 257
Network Management and Monitoring | 257
User Interface and Configuration | 257
Known Issues | 258
Application Layer Gateways (ALGs) | 258
Flow-Based and Packet-Based Processing | 258
Platform and Infrastructure | 258
Routing Policy and Firewall Filters | 259
Routing Protocols | 259
VPN | 259
Resolved Issues | 260
Application Layer Gateways (ALGs) | 260
Authentication and Access Control | 261
Chassis Clustering | 261
Class of Service (CoS) | 261
Flow-Based and Packet-Based Processing | 261
Intrusion Detection and Prevention (IDP) | 262
J-Web | 262
Layer 2 Ethernet Services | 262
Network Address Translation (NAT) | 262
Platform and Infrastructure | 262
Routing Policy and Firewall Filters | 263
Routing Protocols | 263
Unified Threat Management (UTM) | 264
12
VLAN Infrastructure | 264
VPN | 264
Documentation Updates | 264
Migration, Upgrade, and Downgrade Instructions | 265
Upgrade and Downgrade SupportPolicy for Junos OS Releases and Extended End-Of-Life
Releases | 265
Product Compatibility | 266
Hardware Compatibility | 266
Upgrading Using ISSU | 267
Compliance Advisor | 267
Finding More Information | 267
Documentation Feedback | 268
Requesting Technical Support | 269
Self-Help Online Tools and Resources | 269
Opening a Case with JTAC | 269
Revision History | 270
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.2R1 for the ACX Series, EX Series, MX Series, NFX
Series, PTX Series, QFX Series, SRX Series, and Junos Fusion. They describe new and changed features,
limitations, and known and resolved problems in the hardware and software.
NOTE: The recommended release for Junos Fusion Data Center is 18.1R2-S2. The subsequent
18.xRx mainline releases (18.2, 18.3, and 18.4) do not support Junos Fusion Data Center.
13
Junos OS Release Notes for ACX Series
IN THIS SECTION
New and Changed Features | 14
Changes in Behavior and Syntax | 25
Known Behavior | 26
Known Issues | 26
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
Product Compatibility | 30
These release notes accompany Junos OS Release 18.2R1 for the ACX Series. They describe new and
changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located
at https://www.juniper.net/documentation/product/en_US/junos-os.
New and Changed Features
IN THIS SECTION
Hardware | 15
Authentication Access Control | 15
Class of Service | 16
Dynamic Host Configuration Protocol | 16
EVPN | 16
General Routing | 17
Routing Policy and Firewall Filters | 19
Interfaces and Chassis | 19
Layer 2 Features | 19
Layer 3 Features | 21
14
Management | 21
MPLS | 21
Multicast | 22
Routing Protocols | 23
Security | 23
Software Installation and Upgrade | 23
Timing and Synchronization | 24
This section describes the features and enhancements in Junos OS Release 18.2R1 for ACX Series Universal
Metro Routers.
Hardware
New ACX5448 Universal Metro Routers—Starting with Junos OS Release 18.2R1, the ACX5448 Universal
•
Metro Routers are available as Juniper Networks’ top-of-rack router solutions for data centers and
campus distribution or aggregation environments. The ACX5448 router portfolio consists of
high-performance fixed-configuration routers that add higher port densities, additional scalability, and
improved latency to the ACX Series. The ACX5448 routers offers a compact 1U model that provides
wire-speed packet performance, very low latency, and a rich set of Layer 2 and Layer 3 features. The
router has a high-throughput Packet Forwarding Engine, and the performance of the control-plane
running on ACX5448 router is enhanced by the 1.9 Ghz six-core Intel CPU with 32 GB of memory and
two 100 GB of solid-state drive (SSD) storage.
The ACX5448 is a 10-Gigabit Ethernet enhanced small form-factor pluggable (SFP+) top-of-rack router
with 48 SFP+ ports, and four 100-Gigabit Ethernet QSFP28 ports. Each SFP+ port can operate as a
native 10-Gigabit Ethernet port, or as a 1-Gigabit Ethernet port when 1-Gigabit optics are inserted.
The ACX5448 is shipped with redundant fans and redundant power supplies. The router can be ordered
with front-to-back airflow (air out or AFO), or back-to-front airflow (air in or AFI), and with AC or DC
power supplies.
15
Authentication Access Control
Enhancement to NTP authentication method (ACX500, ACX1100)— Starting in Junos OS Release
•
18.2R1, Junos OS supports NTP authentication for both SHA-1 and SHA2-256, in addition to the existing
NTP authentication method, MD5. You can now choose from among MD5, SHA-1, and SHA2-256 for
synchronizing the clocks of Juniper Network routers, switches, and other security devices on the Internet.
Using SHA-1 instead of MD5 improves the security of devices with very little impact to timing, while
using SHA2-256 provides an increase in security over SHA-1.
NOTE: By default, network time synchronization is unauthenticated.
To implement authentication, use set authentication-key <key_number> type at the [edit system ntp]
hierarchy level.
To enable SHA-1 authentication, use set authentication key <key_number> type sha1 value <password>
•
at the [edit system ntp] hierarchy level.
To enable SHA2-256 authentication, use set authentication key <key_number> type sha256 value
•
<password> at the [edit system ntp] hierarchy level.
See authentication-key and Configuring NTP Authentication Keys
Class of Service
Support for logical interface-based classification and rewrites (ACX5448)—Starting with Junos OS
•
Release 18.2R1, ACX5448 router supports configuring logical interface-based classification and rewrite
rules. ACX5448 router supports fixed, behavior aggregate (IP precedence, DSCP, DSCP IPv6, MPLS EXP,
IEEE-802.1p, IEEE-802.1ad (DEI bit)), and multifield classifiers.
See Classifiers and Rewrite Rules at the Global, Physical and Logical Interface Levels Overview
Support for port-based queueing, scheduling, and shaping (ACX5448)—Starting with Junos OS Release
•
18.2R1, ACX5448 router supports port-based queueing, scheduling, and shaping. You can configure up
to eight queues (virtual output queues) per physical interface (port). Scheduling properties can be applied
at both physical as well as logical interface levels. The egress scheduler supports two priority levels
(strict-high and low). Multiple strict-high priority queues and multiple low (default) priority queues can
be configured.
16
Schedulers and their associated shapers control the traffic bandwidth, jitter (delay variation), and packet
loss priority at the egress of the device. By default a port on ACX5448 router gets a dedicated buffer
of 100ms and shared buffer from DRAM. Delay buffer controls the latency of the queue during congestion
and maximum number of packets that can be held in a queue. Default buffer size per port is 100ms.
See Understanding Schedulers Overview, Configuring Shared and Dedicated Buffer Memory Pools, and
Hierarchical Class of Service in ACX5000.
Dynamic Host Configuration Protocol
Support for DHCPv4 and DHCPv6 (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports DHCP server, DHCP client, and DHCP relay configuration for IPv4 and IPv6 services. You can
enable ACX5448 router to function as DHCP server and configure the DHCP server options on the
router. The DHCP server provides an IP address and other configuration information in response to a
client request. DHCP relay agent forwards DHCP request and reply packets between a DHCP client and
a DHCP server.
See Extended DHCP Local Server Overview and See Extended DHCP Relay Agent Overview
EVPN
Support for VPWS with EVPN signaling mechanisms and flexible cross connect (ACX5448)—Starting
•
with Junos OS Release 18.2R1, the ACX5448 router supports VPWS with EVPN signaling mechanisms
and flexible cross connect. The EVPN VPWS provides a framework for delivering the VPWS with EVPN
signaling mechanisms. The VPWS with EVPN signaling mechanisms supports single-active or all-active
multihoming capabilities and inter-autonomous system (AS) options associated with BGP-signaled VPNs.
The EVPN VPWS flexible cross connect addresses the label resource issue. The flexible cross-connect
(FXC) service enables interoperability of access router that uses EVPN FXC VLAN-aware and
VLAN-unaware FXC services. ACX5448 router do not support pseudowire services in EVPN VPWS
flexible cross connect.
The following limitations apply:
Control word is not supported for EVPN VPWS services.
•
When VLAN maps are applied on the ccc-interfaces (UNI) for EVPN VPWS, only the following VLAN
•
map operations are applicable:
IFD Encap/ IFL-TYPE Input-MAP Output-Map
------------------------------------------------------------ethernet-ccc unit 0;
TC2 push-push pop-pop
vlan-ccc
ST: vlan-id X
swap-push ..
DT: vlan-tags outer X inner Y
TC1 pop-pop push-push
TC4 swap-swap swap-swap
17
VLAN map with non-default TPIDs in the VLAN map operation is not supported.
•
Aggregated Ethernet interfaces with LAG interface for EVPN VPWS and EVPN VPWS FXC services
•
are not supported. However, for CE multihoming, the CE can have static-AE, and CE can multihome
to the ACX5448 PE router (PE in non-AE/LAG).
See Overview of VPWS with EVPN Signaling Mechanisms
General Routing
Support for virtualization (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 routers support
•
virtualization. Virtualization enables multiple instances of operating systems, called guests, to run
concurrently on the host and share virtualized hardware resources. A guest is a virtual machine (VM)
that runs on a hypervisor-based host and shares its resources. A host is a virtualized software whose
hypervisor allows multiple guest VMs to run on it concurrently and share its resources. A VM can be an
instance of Junos OS or any compatible third-party VM. Each VM runs its own operating system image
and applications that can be different from that of another VM running on the same host. ACX5448
router supports only one Junos VM. You can use the following chassis management commands to manage
the onboard FRUs:
show chassis hardware
•
show chassis temperature-thresholds
•
show chassis environment
•
show chassis alarms
•
ACX5448 router emulates one FPC with two PICs. One PIC represents the 48x1/10GE ports and other
represents the 4x100GE ports. The show chassis hardware CLI command shows the FPC and PICs as
built-in as shown in the following sample output:
user@host> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis DA805 ACX5448
Midplane REV 13 750-065110 ACNP4346 ACX5448
Routing Engine BUILTIN BUILTIN Routing Engine
RFEB
FPC 0 BUILTIN BUILTIN FPC BUILTIN
MIC 0 48x1GE/48x10GE
PIC 0 BUILTIN BUILTIN 48x1GE/48x10GE
MIC 1 24x10/25GE 6x40/100GE
PIC 1 BUILTIN BUILTIN 24x10/25GE 6x40/100GE
18
NOTE: ACX5448 routers do not support request system software upgrade and request system
software rollback commands, instead you must use request vmhost CLI commands.
ACX5448 routers do not support:
Multiple guest VMs
•
Redundant Junos VMs
•
ISSU
•
10/100 Mbps copper SFPs
•
See Routing Engines with VM Host Support and Architecture of Routing Engines with VM Host Support
Routing Policy and Firewall Filters
Support for firewall filters and policers (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448
•
router supports configuring firewall filters on packets (families such as bridge domain, IPv4, IPv6, CCC,
MPLS) based on packet match conditions. Along with the match conditions, actions such as count, discard,
log, syslog, policer are performed on the packets that match the filter. You can configure policers and
attach them to a firewall term.
See Standard Firewall Filter Match Conditions and Actions on ACX Series Routers Overview
Interfaces and Chassis
Support for 48x1/10GE and 4x100GE Interface Ports (ACX5448)—ACX5448 router has 48x1/10GE
•
interface ports and 4x100GE interface ports. The 48 ports on ACX5448 router can be configured as
1GE or 10GE modes and these ports are represented by xe interface type. The PIC 1 of FPC 0 has
4x100GE ports, where each port can be channelized as 1x100GE, or 1x40GE, or 4x25GE modes and
these ports are represented by et interface type. By default, the port speed in PIC 1 is 100GE.
19
See Understanding Interfaces on ACX Series Universal Metro Routers
Layer 2 Features
Support for Layer 2 features (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports the Layer 2 bridging, Q-in-Q tunneling, no-local switching, and Layer 2 protocol tunnel. A bridge
domain is a set of logical interfaces that share the same flooding or broadcast characteristics. Layer 2
logical interfaces are created by defining one or more logical units on a physical interface with
encapsulation as vlan-bridge and as ethernet-bridge. All the member ports of the bridge domain participate
in Layer 2 learning and forwarding. These bridging features are used to configure E-LINE, E-LAN and
E-TREE services. On ACX5448 router, you can configure bridge domains by using the following methods:
Bridge domain without a vlan-id number statement
•
Bridge domain with the vlan-id value set to none
•
Bridge domain with a single vlan-id
•
The Layer 2 Next Generation mode, also called Enhanced Layer 2 Software (ELS), is supported on
ACX5448 router for configuring the Layer 2 features.
If no-local-switching is configured in a bridge domain, then traffic cannot flow between CE to CE
interfaces. This includes known unicast/multicast, unknown unicast/multicast, and broadcast traffic.
However, traffic can flow between CE to PE interfaces and between PE to PE interfaces.
Q-in-Q tunneling allows you to create a Layer 2 Ethernet connection between two customer sites.
Providers can segregate different customers’ VLAN traffic on a link (for example, if the customers use
overlapping VLAN IDs) or bundle different customer VLANs into a single service VLAN. Service providers
can use Q-in-Q tunneling to isolate customer traffic within a single site or to enable customer traffic
flows across geographic locations.
Layer 2 protocol tunnel can be configured on the customer edge port using mac rewrite configuration.
MAC rewrite is supported for the STP, CDP, VTP, LLDP, ELMI, 802.1x, 802.3ah, LACP, MMRP, MVRP
protocol packets.
See Layer 2 Bridge Domains on ACX Series Overview, See Q-in-Q Tunneling on ACX Series Overview,
and See Understanding Layer 2 Next Generation Mode on ACX Series Routers
Support for Layer 2 services (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports configuring Layer 2 services such as RSTP, MSTP for loop resolutions, and storm control to
monitor traffic levels and to drop broadcast, unknown unicast, and multicast (BUM) packets if they
exceed the configured limit.
Storm control is applied on the following traffic types:
Layer 2 multicast packets
•
Layer 2 unregistered multicast packets
•
20
Layer 2 registered multicast packets
•
On ACX5448 router, storm control is only applicable at the physical interface level. No event will be
logged when a traffic storm hits an ACX5448 router. Also interfaces will not be bound to any default
profile. The default action is to drop the packets exceeding the configured bandwidth.
See Storm Control on ACX Series Routers Overview
Support for Layer 2 protection (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports configuring bridge protocol data unit (BPDU) protect, loop protect, and root protect on
spanning-tree instance interface. You can configure BPDU protection on individual interfaces or on all
the edge ports of the bridge.
See Understanding BPDU Protection for Spanning-Tree Instance Interfaces, Understanding Loop
Protection for Spanning-Tree Instance Interfaces, and Understanding Root Protection for Spanning-Tree
Instance Interfaces in a Layer 2 Switched Network
Layer 3 Features
Support for Layer 3 features (ACX5448)—Starting with Junos OS Release 18.2R1, the ACX5448 router
•
uses MPLS as a transport mechanism and they include support for label-switching router (LSR), label
edge routers (LERs), and pseudowire services. The protocols such as ECMP, OSPF, ISIS, and BGP are
also supported on ACX5448 router.
See MPLS Overview
Management
Support for NETCONF over SSH and custom YANG models (ACX5448)—Starting with Junos OS Release
•
18.2R1, ACX5448 router supports NETCONF OVER SSH and custom YANG modules.
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.
21
You can load custom YANG modules 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 Establishing an SSH Connection for a NETCONF Session and YANG Modules Overview
MPLS
Support for MPLS ping and Bidirectional Forwarding Detection over virtual circuit connection verification
•
(ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router supports MPLS ping and
Bidirectional Forwarding Detection over Virtual Circuit Connection Verification. MPLS ping functionality
diagnoses the state of label-switched paths (LSPs), where the router sends probe packets into the LSP.
Based on how the LSP at the remote endpoint of the connection replies to the probes, you can determine
the connectivity of the LSP. Each probe is an echo request sent to the LSP as an MPLS packet with a
UDP payload. If the outbound node receives the echo request, it checks the contents of the probe and
returns a value in the UDP payload of the response packet. If the Junos OS receives the response packet,
it reports a successful ping response.
Bidirectional Forwarding Detection (BFD) support for virtual circuit connection verification (VCCV)
allows you to configure a control channel for a pseudowire, in addition to the corresponding operations
and management functions to be used over that control channel. BFD provides a low resource mechanism
for the continuous monitoring of the pseudowire data path and for detecting data plane failures, as
described in RFC 5885.
You can use the following commands for debugging:
show bfd session extensive
•
show ldp database extensive
•
See Pinging LSPs and Configuring BFD for VCCV for Layer 2 Circuits
Support for MPLS ping and traceroute (ACX5448)—Starting with Junos OS Release 18.2R1, the ACX5448
•
router supports MPLS ping and traceroute. MPLS ping and traceroute [RFC-4379] are common tools
used to debug connectivity between two PEs for a LSP. The ping portion works by injecting an echo
request packet in a LSP and expecting the remote PE endpoint to receive and reply to the packet. The
traceroute function works the same as it does for IP where it sends multiple packets with an increasing
TTL to let the packet get progressively farther in the LSP path before sending message indication that
the TTL has expired.
See Pinging LSPs
Multicast
Support for multicast features (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports the following multicast protocol (IGMP and PIM) features for forwarding IPv4 and IPv6 traffic:
22
Anycast rendezvous point
•
Auto rendezvous point
•
Bidirectional Forwarding Detection (BFD) for PIM
•
IGMP version 1, version 2, and version 3
•
IGMP filter
•
IGMP proxy (relay)
•
IGMP querier
•
IGMP version 1, version 2, and version 3 snooping
•
Multicast Source Discovery Protocol (MSDP)
•
PIM static rendezvous point
•
PIM source-specific multicast (SSM)
•
PIM sparse mode
•
See Multicast Overview
Routing Protocols
Support for Two-Way Active Measurement Protocol (ACX5448)—Starting with Junos OS Release
•
18.2R1, ACX5448 router supports Two-Way Active Measurement Protocol (TWAMP). The TWAMP
defines a standard for measuring IP performance between two devices in a network. ACX5448 router
supports only the reflector side of TWAMP.
See Understanding Two-Way Active Measurement Protocol on Routers
Security
Support for secure boot and BIOS (ACX5448)—Starting with Junos OS Release 18.2R1, a significant
•
system security enhancement, secureboot, has been introduced in ACX5448 router. The secureboot
implementation is based on the UEFI 2.4 standard. BIOS in ACX5448 router has been hardened and is
responsible for initializing all the components of the router hardware. The following are some of the key
functionalities supported by the BIOS in ACX5448 router:
23
Initialization of hardware components
•
Watchdog support
•
Booting the operating system
•
Diagnostics support
•
Secure boot support
•
See Feature Explorer and enter Secure Boot.
Software Installation and Upgrade
Firmware upgrade (ACX6360 Router)—Starting in Junos OS Release 18.2R1, you can install or upgrade
•
the system firmware on ACX6360 router.
Install the firmware package by using:
request system firmware add path/package-name
•
Upgrade an existing firmware, by using any of the following command:
request system firmware upgrade pic
•
request system firmware upgrade cb
•
request system firmware upgrade re
•
request system firmware upgrade fpc
•
On the ACX6360 line card, you upgrade the following firmware components:
Uboot—Responsible for loading the operating system on the line card
•
FPGA—Controls all functions of the line card
•
You can also upgrade the following firmware components:
RE- FPGA—The RE-FPGA is located on the control board and manages board initialization, reboot,
•
and other functions.
TIC-FPGA—The TIC-FPGA is located on the 8x CFP2 optical port card and manages access to the
•
optical functions.
FTC FPGA—The FTC FPGA is located on the fan controllers and controls the fan controllers.
•
FPD FPGA—The FPD FPGA is located on the LED board and is responsible for the LED board.
•
SIB FPGA—The SIB FPGA is located on the SIB and handles the SIBs
•
Timing and Synchronization
24
Support for PTP transparent clock (ACX5448)—Starting with Junos OS Release 18.2R1, ACX5448 router
•
supports the PTP transparent clock functionality for PTP over IP, as well as PTP over Ethernet. A certain
amount of delay is always experienced by the PTP packets due to queuing and buffering within the
router, which could be due to network load or based on the architecture of the router. The PTP transparent
clock measures the residence time (the time that the packet spends passing through the router), and
adds the residence time into the correction field of the PTP packet. ACX5448 routers support end-to-end
transparent clocks. With an end-to-end transparent clock, only the residence time is included in the
correction field of the PTP packets. ACX5448 supports end-to-end (e2e) transparent clocks as defined
in IEEE1588.
See Understanding Transparent Clocks in Precision Time Protocol
SEE ALSO
Changes in Behavior and Syntax | 25
Known Behavior | 26
Known Issues | 26
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
Product Compatibility | 30
Changes in Behavior and Syntax
IN THIS SECTION
High Availability (HA) and Resiliency | 25
Junos XML API and Scripting | 25
Layer 3 Features | 25
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.2R1 for the ACX Series routers.
High Availability (HA) and Resiliency
25
commit fast-synchronize option not supported for products with single Routing Engine (ACX
•
Series)—Starting in Junos OS Release 18.2R1, Junos OS does not support the configuration option
commit fast-synchronize at the [edit system] hierarchy level for all the products with single Routing
Engine for which chassis redundancy graceful-switchover is not supported. This option is disabled from
the CLI.
Junos XML API and Scripting
Junos XML protocol <open-configuration> operation no longer emits an uncommitted changes warning
•
(ACX Series)—Starting in Junos OS Release 18.2R1, the Junos XML protocol <open-configuration>
operation does not emit an "uncommitted changes will be discarded on exit" warning message when
opening a private copy of the candidate configuration. However, Junos OS still discards the uncommitted
changes upon closing the private copy.
Layer 3 Features
DMA recovery mechanism (ACX Series)—Starting in Junos OS Release 18.2R1, a potential recovery
•
mechanism has been introduced that is triggered in case the router enters an Idle state on any DMA
channels. The recovery mechanism resets the necessary registers to recover from failure conditions and
therefore a PFE reboot is not required. The following recovery success message is logged in the PFE
syslog message:
BCM DMA error recovery: Recovery complete Success
SEE ALSO
New and Changed Features | 14
Known Behavior | 26
Known Issues | 26
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
Product Compatibility | 30
Known Behavior
There are no known limitations in Junos OS Release 18.2R1 for the ACX Series.
26
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 | 14
Changes in Behavior and Syntax | 25
Known Issues | 26
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
Product Compatibility | 30
Known Issues
IN THIS SECTION
Class of Service | 27
DHCP | 27
IGMP Snooping | 28
Timing and Synchronization | 28
This section lists the known issues in hardware and software in Junos OS Release 18.2R1 for the ACX
Series Universal Metro Routers.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks
online Junos Problem Report Search application.
Class of Service
On ACX5448 router, when loss priority is configured as either medium-low or medium-high, the rewrite
•
rule gets applied for loss priority low. PR1358721
27
On ACX5448 router, the clear interfaces statistics all CLI command takes long time to respond with
•
scaled interfaces configured. PR1366087
DHCP
On ACX5448 router, when an ingress interface is configured as a LAG interface and if DHCP request
•
packets arrive at that LAG Interface, the router might drop the packets erroneously. PR1353887
On ACX5448 router, when an ingress interface is configured as a XE Interface and if DHCP request
•
packets arrive at that XE interface, the router might drop the packets erroneously. PR1347906
IGMP Snooping
The IGMP snooping feature does not work on the ACX5448 router. PR1351422
•
Timing and Synchronization
When an ACX5448 router is configured as PTP-TC, incorrect UDP checksum errors are seen when
•
checksum 0x0 is sent from the transmitting node. This occurs when a packet type of 1588 enters the
ACX5448 router with UDP.checksum == 0x0 and the checksum field gets partially updated and the
packet egresses the router with an incorrect checksum. This incorrect checksum causes packet drops
in the next device. PR1327155
SEE ALSO
New and Changed Features | 14
28
Changes in Behavior and Syntax | 25
Known Behavior | 26
Resolved Issues | 28
Documentation Updates | 29
Migration, Upgrade, and Downgrade Instructions | 29
Product Compatibility | 30
Resolved Issues
There are no fixed issues in Junos OS 18.2R1 for 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 | 14
Changes in Behavior and Syntax | 25
Known Behavior | 26
Known Issues | 26
Loading...