Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for ACX Series

 

These release notes accompany Junos OS Release 17.2R3 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

This section describes the new features and enhancements to existing features in the Junos OS main release and the maintenance releases for ACX Series.

Release 17.2R3 New and Changed Features

There are no new features or enhancements to existing features for ACX Series in Junos OS Release 17.2R3.

Release 17.2R2 New and Changed Features

There are no new features or enhancements to existing features for ACX Series in Junos OS Release 17.2R2.

Release 17.2R1 New and Changed Features

Hardware

  • Support for fixed and tunable DWDM Optics, 1GE and 10GE BIDI Optics (ACX Series)—Starting in Junos OS Release 17.2R1, ACX Series Universal Metro Routers support fixed and tunable 1-Gigabit Ethernet and 10-Gigabit Ethernet BIDI DWDM optics.

Interfaces and Chassis

  • Support for Ethernet ring protection switching (ACX Series, ACX500, ACX5000)—Starting in Junos OS Release 17.2R1, ACX Universal Metro Routers support Ethernet ring protection switching (G.8032v2). With the G.8032v2 capability, the ACX Series routers support manual commands (force switch, manual switch, and clear commands) and interconnection of multiple Ethernet rings without virtual channels. ERPS on the ACX5000 line of routers supports Aggregated Ethernet (AE) interfaces.

    [See Ethernet Ring Protection Switching Overview]

Management

  • Support for device family and release in Junos OS YANG modules (ACX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the module’s prefix. Device families include junos, junos-es, junos-ex, and junos-qfx.

    [See Understanding Junos OS YANG Modules.]

Network Management and Monitoring

  • Support for sFlow agent (ACX5000)—Starting in Junos OS Release 17.2R1, ACX5000 line of routers supports sFlow agent. sFlow is a statistical sampling based network monitoring protocol for high speed switched or routed networks. The sFlow monitoring system consists of an sFlow agent (embedded in a switch or router or in a stand alone probe) and a central data collector, or sFlow analyzer.

    sFlow technology uses the following two sampling mechanisms:

    • Packet-based sampling—Samples one packet out of a specified number of packets from an interface enabled for sFlow technology.

    • Time-based sampling—Samples interface statistics at a specified interval from an interface enabled for sFlow technology.

    • Adaptive sampling—Monitors the overall incoming traffic rate on the device and provides feedback to the interfaces to dynamically adapt their sampling rate to traffic conditions.

    [See Overview of sFlow Technology and Configuring sFlow Technology.]

Operation, Administration, and Maintenance (OAM)

  • Support for ITU-T Y.1731 ETH-LM, ETH-SLM, and ETH-DM on aggregated Ethernet interfaces (ACX Series, ACX5000)—Starting in Junos OS release 17.2R1, you can configure ITU-T Y.1731 standard-compliant Ethernet loss measurement (ETH-LM), Ethernet synthetic loss measurement (ETH-SLM), and Ethernet delay measurement (ETH-DM) capabilities on aggregated Ethernet (AE) interfaces. These performance monitoring functionalities are supported on ACX Series and ACX5000 line of routers.

    [See Understanding Ethernet OAM Link Fault Management for ACX Series Routers]

Routing Protocols

  • Support for IS-IS flooding groups (ACX5000)—Starting with Junos OS Release 17.2R1, you can configure flooding groups with IS-IS on the ACX5000 line of routers. This feature limits link-state PDU flooding over IS-IS interfaces. An LSP that is not self-originated is flooded only through the interface belonging to the flood group that has the configured area ID in the LSP. This helps minimize the routes and topology information, thus ensuring optimal convergence. You can segregate both level 1 and level 2 networks into flood groups by using area IDs as tags to identify a flood group. Configure interfaces with specific area IDs to modify the flooding behavior as per your requirements.

    To enable IS-IS flooding groups, include the flood-group flood-group-area-ID statement at the [edit protocols isis interface] hierarchy level.

    [See Understanding IS-IS Flood Group]

Software Installation and Upgrade

  • Support for In-Service Software Upgrade (ACX5000)—Starting with Junos OS Release 17.2R1, Junos OS for ACX5000 Universal Metro Routers supports ISSU, the ability to do software upgrades between two different software releases with minimal disruption to network traffic and no disruptions in the control plane. As a prerequisite, you need to have the graceful Routing Engine switchover (GRES), nonstop active routing (NSR), and nonstop bridging (NSB) enabled in the routing engine to support ISSU on ACX5000 line of routers.

    [See Understanding In-Service Software Upgrade (ISSU) in ACX5000 Series Routers]

Timing and Synchronization

  • Support for PHY timestamping in boundary clock mode (ACX Series)—Starting in Junos OS Release 17.2R1, ACX Series Universal Metro Routers supports timestamping at the physical layer, also known as PHY timestamping, in boundary clock mode. To enable PHY timestamping on ACX Series routers, configure clock-mode as boundary clock at the [edit protocols ptp] hierarchy level.

    [See Configuring Precision Time Protocol Clocking]

  • Support for defect and event management and SNMP get and walk management for timing (ACX Series)—Starting in Junos OS Release 17.2R1, the ACX Universal Metro Routers supports defect and event management capabilities for timing features. Defects and events are notified in the form of SNMP traps.

    The ACX Universal Metro Routers also supports SNMP get, get-next, and walk management capabilities for the timing features. These capabilities are enabled through the PTP MIB and SyncE MIB objects.

    [See Understanding Timing Defects and Event Management on ACX Series and Understanding SNMP MIB for Timing on ACX Series]

Changes in Behavior and Syntax

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 17.2R3 for the ACX Series Universal Metro Routers.

General Routing

  • Support for deletion of static routes when the BFD session goes down (ACX Series)—Starting with Junos OS 17.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. Therefore, the static routes are deleted when the BFD receives a session down message.

Management

  • Junos OS YANG module namespace and prefix changes (ACX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the module’s prefix. In earlier releases, Junos OS YANG modules used only a unique identifier to differentiate the namespace for each module, and the prefix for all juniper-command modules was jrpc.

    Device families include junos, junos-es, junos-ex, and junos-qfx. The Junos OS YANG extension modules, junos-extension and junos-extension-odl, use the junos device family identifier in the namespace, but the modules are common to all device families.

    [See Understanding Junos OS YANG Modules.]

  • Changes to the rfc-compliant configuration statement (ACX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. If you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level and request configuration data in a NETCONF session on a device running Junos OS Release 17.2 or later, the NETCONF server sets the default namespace for the <configuration> element in the RPC reply to the same namespace as in the corresponding YANG model.

    [See Configuring RFC-Compliant NETCONF Sessions and rfc-compliant.]

Subscriber Management and Services

  • DHCPv6 lease renewal for separate IA renew requests (ACX Series)—Starting in Junos OS Release 17.2R3, 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.]

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.2R3 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.

High Availability (HA) and Resiliency

  • Residual and baseline statistics loss from ISSU—Using ISSU to upgrade to Junos OS Release 17.2R1 or later will result in a loss of residual and baseline statistics for interfaces, interface set specific statistics, and BBE subscriber service statistics because of an update to the statistics database.

    [See Unified ISSU System Requirements.]

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 17.2R3 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.

Layer 2 Features

  • Under certain scenarios, if VPLS instances and Layer 3 NNI interfaces are deleted in the same commit, then a traffic duplication is observed for the VPLS traffic. To avoid such instances, it is recommended to delete or deactivate the Layer 3 NNI interfaces and VPLS instances in separate commits. PR1260156

Resolved Issues

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: 17.2R3

There are no fixed issues in the Junos OS Release 17.2R3 for ACX Series.

Resolved Issues: 17.2R2

There are no fixed issues in the Junos OS Release 17.2R2 for ACX Series.

Resolved Issues: 17.2R1

There are no fixed issues in the Junos OS Release 17.2R1 for ACX Series.

Documentation Updates

There are no errata or changes in Junos OS Release 17.2R3 for the ACX Series documentation.

Migration, Upgrade, and Downgrade Instructions

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

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

Upgrade and Downgrade Support Policy for Junos OS Releases

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

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 16.1, 16.2 and 17.1 are EEOL releases. You can upgrade from Junos OS Release 16.1 to Release 16.2 or even from Junos OS Release 16.1 to Release 17.1. However, you cannot upgrade directly from a non-EEOL 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.

Product Compatibility

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.