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 18.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.

New and Changed Features

This section describes the features and enhancements in Junos OS Release 18.4R1 for ACX Series Universal Metro Routers.

Authentication, Authorizing, and Accounting (AAA)

  • Support for password change policy enhancement (ACX Series)—Starting in Junos OS Release 18.4R1, the Junos OS password change policy for local user accounts is enhanced to comply with additional password policies. As part of the policy improvement, you can configure the following:

    • maximum-lifetime-value—The maximum duration of a password. The password expires after the maximum is reached.

    • minimum-lifetime-value—The minimum duration of a password. You cannot change the password until the minimum duration is reached.

    [See password.]

Interfaces and Chassis

  • Multichassis link aggregation groups, configuration synchronization, and configuration consistency check (MC-LAG) (ACX5448 routers)—Starting in Junos OS Release 18.4R1, MC-LAG enables a client device to form a logical LAG interface using two switches. MC-LAG provides redundancy and load balancing between the two switches, multihoming support, and a loop-free Layer 2 network without running spanning tree protocols (STP).

    [See Multichassis Link Aggregation Features, Terms, and Best Practices .]

MPLS

  • Support for topology iIndependent loop-free alternate (TI-LFA) for IS-IS, advertising MPLS labels (ISIS, OSPF), and configuring SRGB for SPRING (ISIS, OSPF) (ACX5448)—Starting with Junos OS Release 18.4R1, ACX5448 router support topology independent (TI)-loop-free alternate (LFA), advertise MPLS labels (ISIS, OSPF), and segment routing global block (SRGB) for SPRING (ISIS, OSPF).

    Topology independent (TI)-loop-free alternate (LFA) with segment routing provides fast reroute (FRR) backup paths corresponding to the post-convergence path for a given failure. You can enable TI-LFA for IS-IS by configuring use-post-convergence-lfa statement at the [edit protocols isis backup-spf-options] hierarchy level.

    You can configure SRGB range label used by source packet routing in networking (SPRING). The labels from this SRGB range is used for SPRING in IS-IS domain. This way the labels advertised in the segment routing is more predictable and deterministic across the segment routing domain.

    • To configure the starting index value of the SRGB label block, use the start-label start-label-block-value statement at the [edit protocols isis source-packet-routing srgb] hierarchy level.

    • To configure the index range of the SRGB label block, use the index-range value configuration statement at the [edit protocols isis source-packet-routing srgb] hierarchy level.

    ACX5448 router supports IS-IS and OSPF segment routing enabled through MPLS. IS-IS and OSPF creates an adjacency segment per IS-IS and OSPF neighbor, for a given interface, adjacency, and area. A separate MPLS label is allocated for each adjacency segment created.

    To configure OSPF segment routing, use the following configuration statements at the [edit protocols ospf] hierarchy level:

    • source-packet-routing—Enable the source packet routing feature.

    • node-segment—Enable the node segment.

    To configure IS-IS segment routing, use the following configuration statements at the [edit protocols isis] hierarchy level:

    • source-packet-routing—Enable the source packet routing feature.

    • node-segment—Enable source packet routing at all levels.

    [See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS, Understanding Source Packet Routing in Networking (SPRING), and source-packet-routing (Protocols IS-IS and OSPF).]

Platform and Infrastructure

  • DMA recovery mechanism (ACX Series)—A recovery mechanism has been introduced that is triggered in case the router enters an Idle state on any DMA channels. The recovery mechanism reboots the PFE to recover from Idle state.

    The following recovery message is logged in the RE syslog message:

    The following recovery message is logged in the PFE syslog message:

Routing Protocols

Timing and Synchronization

  • Support for PTP boundary clocks for phase and time synchronization (ACX5448)—Starting with Junos OS Release 18.4R1, ACX5448 routers support PTP boundary clocks for phase and time synchronization using IEEE-1588 Precision Timing Protocol (PTP). This feature also supports:

    • PTP over IPv4 (IEEE-1588v2)

    • PTP ordinary and boundary clocks

    • One-step clock mode operation for the PTP master clock

    • 10-MHz and 1-PPS output for measurement purpose

    All PTP packets use the best-effort queue instead of the network control queue.

    The ACX5448 router does not support the following features:

    • Hybrid mode

    • Boundary clock performance complying with G.8273.2

    • Dual-tagged PTP over IPv4

    [See IEEE 1588v2 PTP Boundary Clock Overview.]

VPNs

  • Support to control traceroute over Layer 3 VPN (ACX Series)—Starting in Junos OS Release 18.4R1, in a Layer 3 VPN topology with vrf-table-label configured and multiple customer edge (CE) routers configured in the same VPN routing and forwarding (VRF) routing instance, when traceroute is performed to a remote provider edge (PE) router for a CE-facing network, the ICMP time exceeded packet determines the correct IP address as the source address.

    To control the traceroute over Layer 3 VPN topology with vrf-table-label configured and multiple CE routers configured in the same VRF, you can configure allow-l3vpn-traceroute-src-select at the[edit system] hierarchy level that determines the correct IP source address by reviewing the destination routing instance and destination IP address.

    [See allow-l3vpn-traceroute-src-select.]

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 18.4R1 for the ACX Series routers.

Interfaces and Chassis

  • Support for creating layer 2 logical interface independently (ACX Series)—In Junos OS Releases 18.4R1, 18.4R2, and later, ACX Series routers support creating layer 2 logical interface independent of layer 2 routing instance type. That is, you can configure and commit the layer 2 logical interfaces separately and add the interface to bridge-domain or Ethernet VPN (EVPN) routing instance separately. Note that the layer 2 logical interfaces works fine only when the interface is added to bridge domain or EVPN routing instance.

    In the earlier Junos OS releases, when an layer 2 logical interface configuration (units with encapsulation vlan-bridge configuration) is used, then the logical interface must be added as part of a bridge-domain or EVPN routing instance for the commit to succeed.

Network Management and Monitoring

  • The NETCONF server omits warnings in RPC replies when the rfc-compliant statement is configured and the operation returns <ok/> (ACX Series)—Starting in Junos OS Release 18.4R1, when you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level to enforce certain behaviors by the NETCONF server, the server must not return an RPC reply that encloses both an <rpc-error> element and an <ok/> element. If the operation is successful, but the server reply would enclose one or more <rpc-error> elements of severity warning in addition to the <ok/> element, then the warnings are omitted. In earlier releases, or when the rfc-compliant statement is not configured, the NETCONF server might issue an RPC reply that encloses both an <rpc-error> element of severity warning and an <ok/> element.

Known Behavior

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

General Routing

  • When Layer 3 packets are classified, DiffServ code points are not preserved but are getting lost at the egress interface because of a chipset limitation.PR1322142

  • ARP learning rate is very low. PR1343221

  • PTX10001-20C Junos Telemetry Interface or Telemetery infrastructure does not support the interface-filtering capability. Therefore, after you enable a particular sensor for telemetry, it is turned-on for all the interfaces. PR1371996

  • For et-interfaces, only PRE_FEC_SD defect is raised and no OTN alarm is raised. PR1371997

  • The CLI static-cak command encryption does not work between two ACX-OX transpoder nodes. PR1389802

  • For ACX6360 TIC beacon port-range needs to be updated to 0-7 instead of 0-15. PR1399335

  • If user configures an invalid speed configuration on TIC ports (PIC slot 1) on ACX6360-OR/OX, the TIC interfaces are not created. PR1403546

  • Junos OS do not perform vlan-id check at the egress and vlan-id check is only performed at ingress. PR1403730

Known Issues

There are no known issues in hardware and software in Junos OS Release 18.4R1 for the ACX Series Router.

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 the ACX5000 Series platforms, in some cases, CoS configuration is not properly applied in the Packet Forwarding Engine, leading to unexpected egress traffic drop on some interfaces. PR1329141

  • Loopback status is not shown for OT interfaces on the CLI (available from vty only). PR1358017

  • ARP request is getting dropped and not forwarded to the NNI interface queue when the CoS configuration has temporal buffer size. PR1363153

  • Dedicated or minimum buffers are reserved for some queues according to the Junos OS working model. These buffers are always available to those queues irrespective of the traffic pattern throughout the system. When the clearing stat statement is used, these values are visible. This cosmetic or minor issue has no functional impact is seen. PR1367978

  • On ACX6360 and PTX10001-20C the SD threshold can be set above SF threshold. PR1376869

  • Because of a race condition, in which the class-of-service configuration request for an interface is received before the e1-interface is created, a circuit with specified class-of-service parameters is created. Because of this, the interface creation fails resulting in traffic not flowing on the e1-interface and then (if e1-interfaces are further disabled or enabled) a core file is generated. PR1378747

  • On ACX5448 running Junos OS Release 18.4R1 and earlier releases, channelized 25-Gbps et-interfaces might not come up after you restart the chassis management process (by using the restart chassis-control command). As a workaround, reuse the restart-chassis-control command. PR1379288

  • Enhancement is needed for FRR BER threshold SNMP support. PR1383303

  • On ACX6360 and PTX10001-20C the Tx power cannot be configured using + sign. PR1383980

  • The request chassis beacon CLI command is not working for PIC slot 1 (that is, CFP2 ports). PR1386711

  • Customer should avoid using the loss-priority high command in the firewall filters (MF classifiers). PR1388731

  • Explicit swap-push map operations are now introduced on VPLS logical interfaces in ACX5000. This is already supported as part of implicit map operations or routing instance-level configurations. PR1398118

  • The ccc logs are not compressed after rotation. PR1398511

Resolved Issues

This section lists the issues fixed in Junos OS 18.4R1 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.

General Routing

  • Incorrect packet statistics are reported in the ifHCInUcastPkts OID. PR1306656

  • ACX Series routers support from dual-tagged through untagged packets Layer 3 traffic. PR1307666

  • Port xe-0/3/0 did not come up. PR1328207

  • ACX Series routers are incorrectly allowing to configure higher values in burst-size-limit than what is supported by the hardware. PR1361482

  • ACX Series routers autonegotiation shows incorrect values for link-partner when using SFP-LH or SFP-SX transceivers in combo-ports or SFP ports. PR1362490

  • FEC PM error counters are accumulated instead of resetting after bin rollover. PR1363270

  • VPLS with vlan-id-list is not working properly in some releases when the link between a PE device and a CE device is an aggregated Ethernet interface with a single member link and child physical interface flap. PR1365894

  • The commit or commit check operation might fail because of the error cannot have lsp-cleanup-timer without lsp-provisioning. PR1368992

  • The fxpc might crash after an interface is changed on ACX5000 routers. PR1378155

  • Timestamp is incorrect for BER statistics after clearing. PR1386253

  • The request chassis beacon CLI command is not working for pic-slot 1 (that is, CFP2 ports). PR1386711

  • Certain builds of Junos OS do not allow you to upgrade or commit configuration changes when the SI service interface is used. PR1393729

  • ACX Series routers does not support physical-interface-filter semantic in egress direction for any filters. It supports interface-specific command only. PR1395362

  • High jsd or na-grpcd CPU usage might be seen when JET or JTI is not used. PR1398398

Platform and Infrastructure

  • On Junos OS, the next-hop index allocation fails and private index space get exhausted through incoming ARP requests to management interface (CVE-2018-0063). PR1360039

Documentation Updates

There are no errata or changes in Junos OS Release 18.4R1 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 Router. Upgrading or downgrading Junos OS might take several minutes, depending on the size and configuration of the network.

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

Upgrade and Downgrade Support Policy for Junos OS Releases

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

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

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

For 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://apps.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.