These release notes accompany Junos OS Release 20.4R1 for the ACX Series, Containerized Routing
Protocol Process (cRPD), cSRX Container Firewall (cSRX), EX Series, JRR Series, Juniper Secure Connect,
Junos Fusion Enterprise, Junos Fusion Provider Edge, MX Series, NFX Series, PTX Series, QFX Series, SRX
Series, virtual MX Series router (vMX), Virtual Route Reflector (vRR), and vSRX Virtual Firewall (vSRX).
They describe new and changed features, limitations, and known and resolved problems in the hardware
and software.
In Focus guide—We have a document called In Focus that provides details on the most important features
•
for the release in one place. We hope this document will quickly get you to the latest information about
Junos OS features. Let us know if you find this information useful by sending an e-mail to
techpubs-comments@juniper.net.
15
Important Information:
•
Upgrading Using ISSU on page 286
•
Licensing on page 287
•
Compliance Advisor on page 287
•
Finding More Information on page 287
•
Documentation Feedback on page 288
•
Requesting Technical Support on page 288
•
Junos OS Release Notes for ACX Series
IN THIS SECTION
What's New | 16
What's Changed | 22
Known Limitations | 24
Open Issues | 26
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 32
These release notes accompany Junos OS Release 20.4R1 for the ACX Series. They describe new and
changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located
at https://www.juniper.net/documentation/product/en_US/junos-os.
What's New
16
IN THIS SECTION
Hardware | 17
High Availability (HA) and Resiliency | 20
Junos Telemetry Interface | 20
Routing Protocols | 21
Timing and Synchronization | 21
This section describes the new features or enhancements to existing features in Junos OS Release 20.4R1
for the ACX Series.
Hardware
17
We've added the following features to the ACX5448 in Junos OS Release 20.4R1.
•
Table 1: Features Supported by the ACX5448 Routers
DescriptionFeature
18
Authentication, Authorization and
Accounting
Automation
Class of service (CoS)
Ethernet OAM
Support for 802.1X authentication on Layer 3 interfaces. 802.1X is an
•
IEEE standard for port-based network access control that authenticates
users connected to a LAN port. [See 802.1X Authentication.]
Support for either WAN interfaces or management interfaces to
•
automatically download and install the appropriate software and the
configuration file on your device during the ZTP bootstrap process.
[See Zero Touch Provisioning.]
Support for up to three levels of hierarchical scheduling (physical
•
interfaces, logical interfaces, and queues). Configurable buffer support
is also added. By default, all interfaces on the ACX5448 use port-based
scheduling (eight queues per physical port). To enable hierarchical
scheduling, set the hierarchical-scheduler statement at the [editinterfaces interface-name] hierarchy level. [See Hierarchical Class of
Service in ACX Series Routers.]
Support for Ethernet OAM CFM. You can now synchronize
•
local-interface status between two connected devices with remote
interface up/down trigger with OAM CFM. CFM provides end-to-end
signals even if the two devices are not directly connected. [See
Introduction to OAM Connectivity Fault Management (CFM).]
EVPN
Layer 2 features
Layer 3 features
Support for EVPNs and Interfaces. In EVPN-MPLS and MC-LAG
•
environments, the configuration of anycast gateways on ACX5448
routers that are multihomed in all-active mode is supported. [See
Anycast Gateways.]
Support for pseudowire redundancy in MC-LAG. ACX5448 routers
•
support pseudowire redundant Layer 2 circuits in MC-LAG routers.
VPLS is not supported. [See Understanding Pseudowire Redundancy
Mobile Backhaul Scenarios.]
Support for Layer 3 VPN in MC-LAG chassis. ACX5448 routers support
•
Layer 3 VPN in VRRP over IRB interfaces in MC-LAG routers. Layer
3 routing and Layer 3 VPN are not directly supported on the MC-LAG
interfaces. [See Understanding VRRP and Understanding Layer 3
VPNs.]
Table 1: Features Supported by the ACX5448 Routers (continued)
DescriptionFeature
19
Network Security
Software installation and upgrade
Timing and synchronization
Support for control plane DDoS protection, which is enabled by default
•
on ACX5448 routers for many Layer 2 and Layer 3 protocols. Control
Plane DDoS protection uses firewall filters and policers to discard or
rate-limit control plane traffic at the Routing Engine level, which
prevents malicious traffic from interfering with device operations. You
can disable this feature or change the default policer parameters for
supported protocol groups. [See Control Plane Distributed
Denial-of-Service (DDoS) Protection Overview]
Support for the ACX5448-M-LT, a top-of-rack router that supports
•
only Junos Limited image. The Junos Limited image does not have
data-plane encryption and is intended only for countries in the Eurasian
Customs Union because these countries have import restrictions on
software containing data-plane encryption. Unlike the JunosWorldwide
image, the Junos Limited image supports control plane encryption
through Secure Shell (SSH) and Secure Sockets Layer (SSL), thus
allowing secure management of the system. [See ACX5448 System
Overview.]
Support for Precision Time Protocol (PTP) G.8275.2 enhanced profile
•
with PTP over IPv4 and IPv6 unicast traffic. [See Understanding the
PTP G.8275.2 Enhanced Profile (Telecom Profile).]
Support for SFP-1GE-LH-ET transceivers (ACX1100 and ACX2100)—Starting in Junos OS Release
•
20.4R1, the ACX1100 and ACX2100 Universal Metro Routers support the SFP-1GE-LH-ET transceivers.
[See the Hardware Compatibility Tool (HCT) for details.]
Support for SFP-GE80KT14R15 and SFP-GE80KT15R14 transceivers (ACX5448, ACX5448-D, and
•
ACX5448-M)—Starting in Junos OS Release 20.4R1, the ACX5448, ACX5448-D, and ACX5448-M
Universal Metro Routers support the SFP-GE80KT14R15 and SFP-GE80KT15R14 transceivers.
[See the Hardware Compatibility Tool (HCT) for details.]
Support for SFPP-10GE-DWDM-IT transceivers (ACX5448, ACX5448-D, and ACX5448-M)—Starting
•
in Junos OS Release 20.4R1, the ACX5448, ACX5448-D, and ACX5448-M Universal Metro Routers
support the SFPP-10GE-DWDM-IT transceivers.
[See the Hardware Compatibility Tool (HCT) for details.]
High Availability (HA) and Resiliency
NSR support for IS-IS with SR (ACX Series, MX Series)—Starting in Junos OS Release 20.4R1, ACX Series
•
devices support NSR for IS-IS with segment routing (SR). To use NSR, you must first enable GRES on
your device.
[See Nonstop Active Routing Concepts]
Junos Telemetry Interface
•
JTI support for persistent active gRPC sessions between collector and server during an SSL certificate
update (ACX Series, MX Series, and PTX Series)—Junos OS Release 20.4R1 supports persistent active
remote procedure call (gRPC) sessions between the collector (client) and server during an SSL certificate
update.
For secure channel authentication, the TLS protocol is used to maintain a secure channel between the
collector and the server. TLS uses the server certificate and the client certificate to authenticate each
other and send encrypted messages over the network. When an SSL certificate is updated, existing gRPC
sessions are abruptly terminated, forcing the collector to initiate a new gRPC connection and subscribe
to sensors again.
20
To avoid this problem, you can enable persistent active gRPC sessions by configuring hot-reloading at
the [edit system services extension-service request-response grpc ssl] hierarchy level. After you enable
this feature, gRPC sessions will remain active even when authentication certificates are updated.
After the certificate is updated, any new gRPC session will use the updated certificate.
[See gRPC Services for Junos Telemetry Interface and ssl.]
•
Juniper Resiliency Interface for exception reporting and null route detection (ACX Series, PTX Series,
and MX Series)—Starting in Junos OS Release 20.4R1, you can use Juniper Resiliency Interface to detect
and reduce Mean Time to Repair (MTTR) first-order network issues. Juniper Resiliency Interface uses a
push model for data reporting from the entities in the system which encounter packet drops. This
automates the workflow for detecting, reporting, and mitigating adverse exceptions.
To collect kernel routing table and routing protocol process exceptions, configure the set system resiliencyexceptions statement at the [edit] hierarchy level to specify exception reporting based on kernel
exceptions, and routing exceptions.
You can display exceptions from a remote collector by means of remote procedure call (gRPC) services
or gRPC network management interface (gNMI) services. Display on-box exceptions by accessing the
/var/log file or the database at /var/db/ResiliencyExceptions.db. No Junos operational mode commands
display these exceptions.
Routing Protocols
Support for multiple single-hop EBGP sessions on different links using the same IPv6 link-local address
•
(ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—Starting in
Junos OS Release 20.4R1, you are no longer required to have unique peer addresses for Juniper devices
for every EBGP session. You can now enable single-hop EBGP sessions on different links over multiple
directly connected peers that use the same IPv6 link-local address.
In earlier Junos OS Releases, BGP peers could be configured with link-local addresses, but multiple BGP
peers could not be configured to use the same link-local address on different interfaces.
[See Configure Multiple Single-Hop EBGP Sessions on Different Links Using the Same Link-Local Address
(IPv6).]
Timing and Synchronization
Support for PTP G.8275.2 profile (ACX710)—Starting in Junos OS Release 20.4R1, we support the
•
Precision Time Protocol (PTP) G.8275.2 profile with node type T-BC-P (BC).
21
You can use the [edit protocols ptp profile-type g.8275.2 ] hierarchy level to configure the G.8275.2
profile.
[See Understanding the Time Management Administration Guide and profile-type.]
SEE ALSO
What's Changed | 22
Known Limitations | 24
Open Issues | 26
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 32
What's Changed
IN THIS SECTION
General Routing | 22
MPLS | 23
Network Management and Monitoring | 23
Routing Protocols | 23
User Interface and Configuration | 23
This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS
statements and commands in Junos OS Release 20.4R1 for the ACX Series routers.
22
General Routing
Support for unicast ARP request on table entry expiration—You can configure the device to send a
•
unicast ARP request instead of the default broadcast request when an ARP table entry is about to expire.
The retry requests are unicast at intervals of 5 seconds. Without this option, the retry requests are
broadcast at intervals of 800 milliseconds. This behavior reduces ARP overall broadcast traffic. It also
supports the use case where access nodes are configured not to forward broadcast ARP requests toward
customer CPEs for security reasons and instead translate ARP broadcasts to unicast requests. To confirm
whether this is configured, you can issue the following command: show configuration system arp | grepunicast-mode-on-expire.
[See arp.]
Support for gigether-options statement (ACX5048, ACX5096)—Junos OS supports the gigether-options
•
statement at the edit interfaces interface-name hierarchy on the ACX5048 and ACX5096 routers.
Previously, support for the gigether-statement was deprecated. See gigether-options and
MPLS
The show mpls lsp extensivel and show mpls lsp detail commands display next-hop gateway LSPid —
•
When you use the show mpls lsp extensivel and show mpls lsp detail commands, you'll see next-hop
gateway LSPid in the output.
Network Management and Monitoring
Warning changed for configuration statements that correspond to "deviate not-supported" nodes in
•
YANG data models (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—If you
configure a statement corresponding to a YANG data model node that defines the deviate not-supported
statement, the Junos OS configuration annotates that statement with the comment Warning: statement
ignored: unsupported platform. In earlier releases, the warning is Warning: 'statement' is deprecated.
Routing Protocols
23
Inet6 is disabled in VT interface (ACX5448)—Starting in this release, the inet6 statement at the edit
•
interfaces vt-interface-number unit unit-number family hierarchy level is disabled.
User Interface and Configuration
Verbose format option to export JSON configuration data (ACX Series, EX Series, MX Series, PTX
•
Series, QFX Series, and SRX Series)—The Junos OS CLI exposes the verbose statement at the edit system
export-format json hierarchy level. The default format to export configuration data in JSON changed
from verbose format to ietf format starting in Junos OS Release 16.1R1. You can explicitly specify the
default export format for JSON configuration data by configuring the appropriate statement at the editsystem export-format json hierarchy level. Although the verbose statement is exposed in the Junos OS
CLI as of the current release, you can configure this statement starting in Junos OS Release 16.1R1.
[See export-format.]
SEE ALSO
What's New | 16
Known Limitations | 24
Open Issues | 26
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 32
Known Limitations
IN THIS SECTION
General Routing | 24
Timing and Synchronization | 24
Learn about known limitations in this release 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.
General Routing
24
On the ACX710 router, Servo moves to the Holdover-in/Holdover-out/Acq state from the Phase-aligned
•
state with impairment. PR1550367
On the ACX710 router, PTP with Vlan-id-range does not work for specific VLANs. PR1550482
•
On the ACX710 router, the holdover error HOLDOVER OUT OF SPEC does not reset during the Servo
•
state change. PR1556798
Timing and Synchronization
On the ACX5448 router, the two-way time error and CTE for 1 PPS does not meet the class A metrics.
•
PR1535434
On the ACX5448-M router, the 1 PPS CTE does not meet the class A performance in 1-Gigabits interface.
•
PR1542744
On the ACX5448 router, due to BRCM KBP issue route lookup might fail. PR1533557
•
On the ACX5448 router, ping stops working even though the ARP entry is present during continuous
•
script executions. PR1533513
On the ACX710 router, T1 or T4 cTE should be tuned closer to two-way CTE. PR1527347
•
On the ACX710 router, huge offset is observed initially with ACQ and holdover inspec and outspec
•
conditions. PR1534470
On the ACX710 router, the incremental PTP FPGA upgrades do not bundle along with the regular image
•
upgrades. PR1540799
On the ACX710 router, changing the PTP profile type from g.8275.1 to g.8275.2 requires the Packet
•
Forwarding Engine to reboot and the clksyncd process to restart. As a workaround, you must reboot
the Packet Forwarding Engine and restart the clocking process before you change the profile. PR1546614
On the ACX710 router, the Servo transition is incorrect after chassis restart. PR1550270
•
On the ACX710 router, the delay-asymmetry compensation update does not work at CLI with the
•
G.8275.2 profile. PR1550441
On the ACX710 router, the PTP Servo status shows holdover during transition between virtual port and
•
PTP. PR1510880
On the ACX710 router, if the client clock candidate is configured with a virtual port, the clock class is
•
on T-BC. PR1520204
On the ACX710 router, the SyncE to 1PPS transient test results do not meet G.8273.2 SyncE to 1PPS
•
transient metric. PR1522796
On the ACX710 router, the clock parameters are incorrect in certain scenarios when the Servo is in the
•
FREERUN state. PR1548192
25
On the ACX710 router, the PTP Servo takes longer time to lock after the clksyncd process restarts.
•
PR1549952
On the ACX710 router, the show ptp global-information command does not display correct Clock Class
•
or ESMC QL details when the Servo goes to the Holdover-in state. PR1553213
On the ACX710 router, the Servo transition is incorrect during the T-GM switchover scenario. PR1553439
•
SEE ALSO
What's New | 16
What's Changed | 22
Open Issues | 26
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 32
Open Issues
IN THIS SECTION
Class of Service (CoS) | 26
General Routing | 26
Platform and Infrastructure | 27
VPNs | 27
Learn about open issues in this release 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.
26
Class of Service (CoS)
Unexpected behavior of Class of Service is observed with the wildcard classifier. PR1559516
•
General Routing
On the ACX5448 router, latency is observed for the host-generated ICMP traffic. PR1380145
•
Tx power cannot be configured using the + sign. PR1383980
•
On the ACX710 router, alarm is not raised when booting the system with recovery snapshot. PR1517221
•
On the ACX5448 router, the BGPV6LU traffic drop is observed when the node is deployed in ingress.
•
PR1538819
On the ACX500-I router, the show services session count does not work as expected. PR1520305
•
The ARP packets from the CE device are added with VLAN tag if the VLAN-ID is configured in the EVPN
•
routing instance. PR1555679
On the ACX710 router, the global configuration of IPv4-dscp naming convention must be corrected as
•
per the stream level dscp, which is more meaningful for both the the IPv6 and IPv4 services. PR1557262
On the ACX5448 router, the unicast packets from the CE devices might be forwarded by the PE devices
•
with additional VLAN tag if IRB is used. PR1559084
On the ACX5048 router, the fxpc process generates core file on the analyzer configuration. PR1559690
•
On the ACX5448 router, the following syslog message is reported every 30 seconds;
•
ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_dyn_entry_counter_get : Entry is invalid. PR1562323
On the ACX5448 router, the transit DHCPv4 and DHCPv6 packets drop in a Layer 2 domain. PR1517420
•
On the ACX5448 router, the ISSU upgrade fails due to the Packet Forwarding Engine restart issue.
•
PR1554915
On the ACX5048 router, all the OAM sessions are not established. PR1561751
•
Even though enhanced-ip is active, the following alarm is observed during ISSU: RE0 network-service
•
mode mismatch between configuration and kernel setting. PR1546002
The ACX5448 device as TWAMP server delays the start session acknowledgment by 10 seconds.
•
PR1556829
On the ACX2100 device, laser-output-power is seen after the interface is disabled and rebooted.
•
PR1560501
Inline BFD stays down with IS-IS or Static clients. PR1561590
•
27
Platform and Infrastructure
The CFM REMOTE MEP does not come up after configuration or if the MEP remains in the Start state.
•
PR1460555
VPNs
On the ACX5448 router, the MC-AE Layer 2 circuit states are not updated instantly and for some time
•
after disabling the core interface on the MC-LAG active node, double hit in traffic is observed. PR1543408
SEE ALSO
What's New | 16
What's Changed | 22
Known Limitations | 24
Resolved Issues | 28
Documentation Updates | 31
Migration, Upgrade, and Downgrade Instructions | 32
Resolved Issues
IN THIS SECTION
Forwarding and Sampling | 28
General Routing | 28
Interfaces and Chassis | 31
Layer 2 Features | 31
Routing Protocols | 31
This section lists the issues fixed in Junos OS Release 20.4R1 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.
28
Forwarding and Sampling
VLAN-ID based firewall match conditions might not work for the VPLS service. PR1542092
•
General Routing
The gigether-options command is enabled again under the interface hierarchy. PR1430009
•
Repeated powering-off or powering-on of the device, the SMBUS transactions timeout occurs. PR1463745
•
On the ACX5048 router, the egress queue statistics do not work for the aggregated Ethernet interfaces.
•
PR1472467
On the ACX5048 router, traffic loss is observed during the unified ISSU upgrade. PR1483959
•
The following syslog error message is observed: ACX_DFW_CFG_FAILED. PR1490940
•
On the ACX5048 and ACX5096 routers, the LACP control packets might be dropped due to high CPU
•
utilization. PR1493518
On the ACX710 router, high convergence is observed with the EVPN-ELAN service in a scaled scenario
•
during FRR switchover. PR1497251
On the ACX5448 router, the EXP rewrite for the Layer 3 VPN sends all traffic with incorrect EXP.
•
PR1500928
The following error message is observed during MPLS route add, change, and delete operation: mpls_extra
•
NULL. PR1502385
Loading...
+ 262 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.