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.1R3 for the ACX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os .

New and Changed Features

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

Release 17.1R3 New and Changed Features

There are no new features or enhancements to existing features for ACX Series Universal Metro Routers in Junos OS Release 17.1R3.

Release 17.1R2 New and Changed Features

There are no new features or enhancements to existing features for ACX Series Universal Metro Routers in Junos OS Release 17.1R2.

Release 17.1R1 New and Changed Features

This section describes the new features or enhancements to existing features for ACX Series Universal Metro Routers in Junos OS Release 17.1R1.

Application Level Gateways (ALGs)

  • Support for Application Level Gateways (ALGs) for NAT processing (ACX500)—Starting with Junos OS Release 17.1R1, ACX500 routers support basic TCP, basic UDP, DNS, FTP, ICMP, TFTP, and UNIX Remote-Shell Services ALGs for NAT processing.

    Note

    The ALG for NAT is supported only on the ACX500 indoor routers.

    [See ALGs Available by Default for Junos OS Address Aware NAT on ACX500 Router.]

Bridging

  • Support for DHCP option 82 over bridge domain (ACX5000)—Starting with Junos OS Release 17.1R1, ACX Universal Metro Routers supports configuring DHCP option 82 over bridge domain. ACX routers support option 82 type, length, and value (TLV) information for DHCP client messages over bridge domain.

    [See Using DHCP Relay Agent Option 82 Information.]

Firewall

  • Support for stateful firewall (ACX500)—Starting with Junos OS Release 17.1R1, ACX500 Universal Metro Routers supports configuring stateful firewall rules. Contrasted with a stateless firewall that inspects packets in isolation, a stateful firewall provides an extra layer of security by using state information derived from past communications and other applications to make dynamic control decisions for new communication attempts.

    Note

    The stateful firewall configuration is supported only on the ACX500 indoor routers.

    [See Junos Network Secure Overview.]

Generic Routing

  • Support for generic routing encapsulation (GRE) (ACX Series)—Starting with Junos OS Release 17.1R1, ACX Series Universal Metro Routers support configuring generic routing encapsulation (GRE). GRE provides a private, secure path for transporting packets through an otherwise public network by encapsulating (or tunneling) the packets inside a transport protocol known as an IP encapsulation protocol.

    [See Understanding Generic Routing Encapsulation on ACX Series.]

Interfaces and Chassis

  • Aggregated Ethernet load-balancing support for circuit cross-connect (CCC), VPLS, bridge domain, and Layer 3 VPN (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support aggregated Ethernet (AE) operation over Layer 2 circuit, Layer 3 VPN, bridge domain, CCC, OAM, no-local-switching, and IGMP snooping. Also supported are AE class of service and firewall support for families such as bridge domain, VPLS, CCC, MPLS, IPv4, and IPv6. The firewall support extends the support for single-rate two-color policer and two-rate two-color policer.

    [See Understanding Ethernet Link Aggregation on ACX Series Routers.]

Junos OS XML API and Scripting

  • Support for Python language for commit, event, op, and SNMP scripts (ACX500, ACX1000, ACX1100, ACX2000, ACX2100, ACX2200, and ACX4000)—Starting in Junos OS Release 17.1R1, you can author commit, event, op, and SNMP scripts in Python on devices that include the Python extensions package in the software image. Creating automation scripts in Python enables you to take advantage of Python features and libraries as well as leverage Junos PyEZ APIs to perform operational and configuration tasks on devices running Junos OS. To enable execution of Python automation scripts, which must be owned by either root or a user in the Junos OS super-user login class, configure the language python statement at the [edit system scripts] hierarchy level, and configure the filename for the Python script under the hierarchy level appropriate to that script type. Supported Python versions include Python 2.7.x.

    [See Understanding Python Automation Scripts for Devices Running Junos OS.]

Layer 2 Features

  • Support for pseudowire cross-connect (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers supports pseudowire cross-connect. The pseudowire cross-connect feature enables virtual circuit (VC) to terminate locally on a router and supports local switching of Layer 2 circuits. Layer 2 circuits allows the creation of point-to-point Layer 2 connections over an IP and MPLS-based network. Physical circuits with the same Layer 2 encapsulations can be connected together across such a network.

    [See Configuring Local Interface Switching in Layer 2 Circuits.]

Mirroring

  • Support for port mirroring (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers supports port mirroring to mirror a copy of a packet to a configured destination, in addition to the normal processing and forwarding of the packet. Port mirroring is supported on both ingress and egress ports, using a protocol analyzer application that passes the input to mirror through a list of ports configured through the logical interface.

    [See Port, VLAN, and Flow Mirroring Overview.]

MPLS

  • Support for the Path Computation Element Protocol (ACX Series)—Starting with Junos OS Release 17.1R1, ACX Series Universal Metro Routers support the Path Computation Element Protocol (PCEP). A Path Computation Element (PCE) is an entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints. A Path Computation Client (PCC) is any client application requesting a path computation to be performed by a PCE. PCEP enables communications between a PCC and a PCE, or between two PCEs (defined in RFC 5440). PCEP is a TCP-based protocol defined by the IETF PCE Working Group, and defines a set of messages and objects used to manage PCEP sessions and to request and send paths for multidomain traffic engineered LSPs (TE LSPs). It provides a mechanism for a PCE to perform path computation for a PCC’s external LSPs. The PCEP interactions include LSP status reports sent by the PCC to the PCE, and PCE updates for the external LSPs.

    [See PCEP Overview.]

Network Management and Monitoring

  • Support for hrProcessorTable object (ACX Series)—Starting in Junos OS Release 17.1R1, support is provided for the hrProcessorTable object (object id: 1.3.6.1.2.1.25.3.3) described in the RFC2790, Host Resources MIB. The hrProcessorTable object provides the load statistics information per CPU for multi-core devices.

    [See SNMP MIB Explorer.]

  • Support for RFC 2544 reflector (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support the Layer 1 reflector functionality for performing RFC 2544 benchmarking tests. The device that is configured as a reflector reflects or sends back the packets as they are received on the pseudowire. This feature does not support any packet modification functionality. To enable your ACX5000 router to reflect the packets back to the initiator, you can configure any unused physical port on the router as the reflector port. Use the reflector-port statement at the [edit services rpm rfc2544-benchmarking tests test-name] hierarchy level to configure the reflector port.

    [See RFC 2544-Based Benchmarking Tests Overview.]

Operations, Administration, and Management (OAM)

  • SNMP support for Service OAM (SOAM) performance monitoring functions (ACX Series)—Starting with Junos OS Release 17.1R1, ACX Series Universal Metro Routers SNMP support Service OAM (SOAM) performance monitoring functions that are defined in Technical Specification MEF 17, the Service OAM performance monitoring requirements specified in SOAM-PM, and the Service OAM management objects specified in Technical Specification MEF 7.1.

    A new enterprise-specific MIB, SOAM PM MIB, that defines the management objects for Ethernet services operations, administration, and maintenance for performance monitoring, has been added and SNMP support is available for the MIB objects defined in Technical Specification MEF 36.

    [See Interpreting the Enterprise-Specific Service OAM MIB.]

Spanning-Tree Protocols

Timing and Synchronization

  • Support for precision time protocol over integrated routing and bridging (ACX Series)—Starting with Junos OS Release 17.1R1, ACX Series Universal Metro Routers support configuring precision time protocol (PTP) over integrated routing and bridging (IRB). You can configure a boundary clock node with PTP (IPv4) over IRB in a master-only mode across single or multiple IRB logical interfaces.

    [See Configuring Precision Time Protocol Over Integrated Routing and Bridging.]

  • Support for timing and synchronization (ACX Series)—Starting with Junos OS Release 17.1R1, ACX Universal Metro Routers support external clock synchronization and automatic clock selection for Synchronous Ethernet, T1 or E1 line timing sources, and external inputs. The IEEE 1588v2 standard defines the Precision Time Protocol (PTP), which is used to synchronize clocks throughout a network. ACX Series routers support PTP ordinary clock and boundary clock features. ACX Series routers also support PTP over Ethernet.

    [See External Clock Synchronization Overview for ACX Series Routers, Automatic Clock Selection Overview.]

  • Support for transparent clock (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support the transparent clock functionality. Transparent clocks measure packet residence time for Precision Time Protocol (PTP) events. The packet delay variation experienced by PTP packets can be attributed to queuing and buffering delays inside the router. ACX5000 routers support only end-to-end transparent clock functionality as defined in the IEEE 1588 standard. The transparent clock functionality works for both PTP over IP (PTPoIP), and PTP over Ethernet (PTPoE).

    To configure the transparent clock functionality, you must include the e2e-transparent statement at the [edit protocol ptp] hierarchy level.

    Use the show ptp global-information command to check the status of the transparent clock functionality configured on the router.

    [See Understanding Transparent Clocks in Precision Time Protocol.]

Tunneling

  • Support for remote loop-free alternate (LFA) over LDP tunnels in IS-IS and OSPF networks (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support remote LFA over LDP tunnels in an IS-IS and OSPF network. Remote LFA increases the backup coverage for IS-IS and OSPF routes and provides protection especially for Layer 1 metro-rings. The IS-IS protocol creates a dynamic LDP tunnel to reach the remote LFA node from the point of local repair (PLR). The PLR uses this remote LFA backup path when the primary link fails.

    [See Configuring Remote LFA Backup over LDP Tunnels in an OSPF Network, Configuring Remote LFA Backup over LDP Tunnels in an IS-IS Network.]

  • Support for automatic bandwidth allocation for label-switched paths (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support automatic bandwidth allocation for label-switched paths (LSPs). Automatic bandwidth allocation allows an MPLS tunnel to automatically adjust its bandwidth allocation based on the volume of traffic flowing through the tunnel. You can configure an LSP with minimal bandwidth, and this feature can dynamically adjust the LSP’s bandwidth allocation based on current traffic patterns. The bandwidth adjustments do not interrupt traffic flow through the tunnel.

    [See Automatic Bandwidth Allocation for LSPs.]

VPLS

  • Mesh group support for VPLS routing (ACX5000)—Starting with Junos OS Release 17.1R1, ACX5000 Universal Metro Routers support mesh group configuration for VPLS routing instances. A mesh group within the routing instance is a group of PE interface members with common forwarding attributes. The following are the default member attributes in a mesh group:

    • no-local-switching—Traffic will not switch between members of the same mesh group (known-unicast, multicast, broadcast, unknown-unicast).

    • flood-to-all-other-mesh-group—Traffic can flow from a member of one mesh group to any set of members of other mesh groups.

    [See Configuring Interoperability Between BGP Signaling and LDP Signaling in VPLS.]

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.1R3 for the ACX Series.

General Routing

  • For the routing command, starting in Junos 15.1F3, 15.1R2, 15.1R3, and 15.2R1, 64-bit mode is enabled by default on systems that support it and that have at least 16 GB of RAM.

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

Interfaces and Chassis

  • Support for logical interfaces (ACX5048 and ACX5096)—ACX5048 and ACX5096 routers do not support configuring more than 1000 logical interfaces.

MPLS

  • Representation for OSPF DR node—Up until version -10 of the BGP-LS draft, the OSPF DR node representation was ambiguous. One could represent DR node as 'AdvertisingRouterId-InterfaceIpAddress' or 'InterfaceIpAddress-1'. Junos OS used to follow 'InterfaceIpAddress-1' format. Starting with version '-11' of the BGP-LS draft, the representation for OSPF DR node must be 'AdvertisingRouterId-InterfaceIpaddress'. Junos OS now follows the latest format.

Network Management and Monitoring

  • SNMP syslog messages changed (ACX Series)—Starting in Junos OS Release 17.1R1, two misleading SNMP syslog messages have been rewritten to accurately describe the event:

    • OLD —AgentX master agent failed to respond to ping. Attempting to re-register

      NEW — AgentX master agent failed to respond to ping, triggering cleanup!

    • OLD — NET-SNMP version %s AgentX subagent connected

      NEW — NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

  • Update to SNMP support of apply-path statement (ACX Series)—Starting in Junos OS Release 17.1R2, SNMP implementation for the apply-path configuration statement supports only two lists:

    • apply-path "policy-options prefix-list <list-name> <*>"

      This configuration has been supported from day 1.

    • apply-path "access radius-server <*>"

      This configuration is supported as of Junos OS Release 17.1R2.

  • Juniper MIBs loading errors fixed (ACX Series)—Starting in Junos OS Release 17.1R1, duplicated entries and errors while loading MIBs on ManageEngine MIB browser are fixed for the following MIB files:

    • jnx-gen-set.mib

    • jnx-ifotn.mib

    • jnx-optics.mib

    [See MIB Explorer.]

  • Change in default log level setting (ACX Series)—Starting in Junos OS Release 17.1R3, the following changes were made in default logging levels:

    Before this change:

    • SNMP_TRAP_LINK_UP was LOG_INFO for both the physical (IFD) and logical (IFL) interfaces.

    • SNMP_TRAP_LINK_DOWN was LOG_WARNING for both the physical (IFD) and logical (IFL) interfaces.

    After this change:

    • IFD LinkUp -> LOG_NOTICE (because this is an important message but less frequent)

    • IFL LinkUp -> LOG_INFO (no change)

    • IFD and IFL LinkDown -> LOG_WARNING (no change)

    [See the MIB Explorer.]

  • New context-oid option for trap-options configuration statement to distinguish the traps that come from a non-default routing instance and non-default logical system (ACX Series)—Starting in Junos OS Release 17.1R1, a new option, context-oid, for the trap-options statement allows you to handle prefixes such as <routing-instance name>@<trap-group> or <logical-system name>/<routing-instance name>@<trap-group> as an additional varbind.

    [See trap-options.]

  • Need to reconfigure SNMPv3 configuration after upgrade (ACX5048 and ACX5096)—Starting in Junos OS Release 17.1R2, you might need to reconfigure SNMPv3 after upgrading from an earlier release to this release. This is necessary only if you are using SNMPv3 and if the engine ID is based on the MAC address because the engine ID is changed. It used to be that customers had to reconfigure SNMPv3 every time after a reboot. This problem was fixed. If you upgrade, you must still reconfigure SNMPv3, but only once—if you have already reconfigured SNMPv3 in an earlier release, you do not need to reconfigure SNMPv3 again. To reconfigure SNMP v3, use the delete snmp v3 command, commit, and then reconfigure SNMPv3 parameters.

    [See Configuring the Local Engine ID.]

Platform and Infrastructure

  • DMA recovery mechanism (ACX Series)—Starting in Junos OS Release 17.1R3, a 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 Packet Forwarding Engine reboot to recover from idle state.

    The following recovery message is logged in the Routing Engine syslog message:

    The following recovery message is logged in the Packet Forwarding Engine syslog message:

Services Applications

  • Device discovery with device-initiated connection (ACX Series)—In Junos OS Release 17.1R1 and later releases, when you configure statements and options under the [system services ssh] hierarchy and commit the configuration, make sure that the system reaches a stable state before you commit any outbound-ssh configurations.

    You use the device discovery feature in the Devices workspace to add devices to Junos Space Network Management Platform. By default, Junos Space manages devices by initiating and maintaining a connection to the device.

    [See Device Discovery Overview.]

System Management

  • Peers option not supported in batch configuration mode— Starting in Junos OS Release 17.1R1, the peers option at the [edit system commit] hierarchy level is not supported in batch configuration mode.

User Interface and Configuration

  • Integers in configuration data in JSON format are displayed without quotation marks (ACX Series)—Starting in Junos OS Release 17.1R1, integers in Junos OS configuration data emitted in JavaScript Object Notation (JSON) format are not enclosed in quotation marks. Prior to Junos OS Release 17.1, integers in JSON configuration data were treated as strings and enclosed in quotation marks.

  • Changes to the show system schema module juniper-command output directory (ACX Series)—Starting in Junos OS Release 17.1R1, when you issue the show system schema module juniper-command operational command in the Junos OS CLI, the device places the generated output files in the current working directory, which defaults to the user’s home directory. Prior to Junos OS Release 17.1R1, the generated output files are placed in the /var/tmp directory.

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.1R3 for the ACX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • When you run the restart clksyncd-service CLI command, incorrect correction field values are seen when transparent clock is INACTIVE. This does not have any functional impact. PR1067583

  • ACX Series hardware does not have support for unicast RPF statistics. The values currently shown in Junos OS CLI at logical interface level for unicast RPF statistics can be ignored. PR1188020

  • ACX Series hardware supports unicast RPF mode at the physical interface level only, though Junos OS configurations are done at the logical interface level. To avoid confusion with respect to unicast RPF modes, only one mode (strict/loose) should be configured for all the logical interfaces within a physical interface. This applies to bridge-domain logical interface also, if IRB is present in the bridge domain and unicast RPF is enabled in the IRB logical interface. PR1196908

  • In a VPWS termination case, when no explicit expiration or default expiration classifier is configured for classification, it is expected that the packets should be classified to be queued to default queue 0. Instead they are getting queued to the assured forwarding queue. This issue is seen only with ACX4000. PR1201072

  • The following error logs will be seen in a scenario where the number of MPLS tunnels exceeds the limit for the platform: - acx_nh_mpls_tunnel_install(),1076:acx_nh_mpls_tunnel_install: BCM TNL InitiatorSet failed for NH #### (Table full) . As a consequence of a previous error, the following logs could also be seen: - fpc0 ACX_NH::acx_nh_l3_tag_hw_install(),#### :acx_nh_l3_tag_hw_install: Tunnel installed failed: NH #### - fpc0 NH: Failed to find nh (3662) for deletion. When the error persists for a while, you eventually get the following message: ACX_NH::acx_nh_mpls_tunnel_uninstall(),1171:acx_nh_mpls_tunnel_uninstall: BCM L3 Egress destroy object failed for (-10:Operation still running). Note: For the ACX5000 line of routers, the maximum number of MPLS tunnels supported is 1024. In scenarios with route flaps, new tunnels will be created and reach limits duringaddition and deletion. As a result, we recommend you avoid reaching over 1000 tunnels in a normal operation. > To check the number of tunnels use CLI command: request pfe execute the show pfe-hw mpls-tunnel command target fpc0. PR1231621

High Availability (HA) and Resiliency

  • Unified ISSU incompatibility with VPLS dynamic profiles (ACX Series)—Using unified ISSU to upgrade from an earlier Junos OS release to Junos OS Release 17.1R1 does not work if VPLS dynamic profiles are configured and enhanced subscriber management is not configured.

    [See ISSU System Requirements.]

Known Issues

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

General Routing

  • In Junos OS Release 12.3X54-D10.6, the aggregated Ethernet interface on ACX Series routers is permanently down after reboot, when link speed is configured. PR1022248

  • SNMP MIB walk on jnxDomCurrentTable and jnxDomNotifications is enabled. PR1076943

  • In some cases it was observed that the fan is running but CLI command and syslog give fan failure alarms, and the other fan is spinning at high speed: root@> show chassis alarms no-forwarding alarms currently active Alarm time Class Description 2010-01-01 00:12:04 UTC Minor Single FAN Failure root@> show chassis environment no-forwarding Class Item Status Measurement Fans Fan 1 Check Fan 2 OK Spinning at high speed. PR1127846

  • Load balancing does not work at LSR with multiple CCC/VPLS sessions. PR1198435

  • ACX: does not forward DHCP-RELAY requests with IRB interface after upgrade. PR1243687

  • On ACX Series routers with Dynamic Host Configuration Protocol (DHCP) relay configured, if rebooting scaling number of DHCP clients at the same time, the DHCP negotiations might fail and eventually cause outage. PR1335957

  • The remote fault signaling is not supported for 1 Gigabit fiber SFP during auto-negotiation. Therefore in releases without the fix of this PR, we get a cosmetic log error under show interfaces extensive: Link partner: Link mode: Full-duplex, Flow control: None, Remote fault: Down, Reason: Link partner offline. RFI ignored since AN is in default mode. PR1362490

  • On MX Series and ACX Series platforms, offlining and then bringing the MIC-3D-16CHE1-T1-CE-H card back online might cause the FPC to crash. PR1402563

Network Address Translation (NAT) and Stateful Firewall Services

  • On the ACX500 routers, when service application logging is enabled at [edit services service-set service-set-name syslog host host-name class] hierarchy level and when packets containing errors are received at higher rate toward the service engine, the resource scale requirements at the service engine cannot be met and the service processor might reboot. As a workaround, you can disable the application logging. PR1223500

  • On the ACX500 routers, when there is a fast ramp-up of scaled user applications, the resource requirements of the service engine cannot be met. As a workaround, you can disable the application logging. PR1226153

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.1R3

General Routing

  • Upgrade or large configuration commit fails are observed on ACX5000 router. PR1088017

  • ACX1100 with midplane part no 650-062965 might fail to initialize FPGA. PR1134335

  • MPLS LSP are being affected because NH failed to be programmed. PR1195419

  • The chassisd[1825]: pvidb_get_root_node: Error(2) retrieving rootnode value error messages might be seen. PR1198817

  • Several error logs are seen on the ACX Series router when a link in the primary path of LSP flaps. PR1204714

  • EVPN CLI is exposed on ACX1000, ACX2000, and ACX4000. PR1208248

  • The tagged/untagged LLDP and LACP packets are dropped on the VPLS CE device facing the aggregated Ethernet interface. PR1245242

  • The 100m/full-duplex setting does not work with SFP-T at rebooting. PR1262752

  • Transit ARP packets are being punted to the Routing Engine. PR1263012

  • ARP packets coming with a VLAN tag that not configured in the ACX Series router are hitting the default_arp_policer. PR1271100

  • In some rare scenarios, ACX500 IPsec will have a license activation error with the license not valid for this product message. PR1275149

  • SHEAF leak is seen on the ACX5000 line of routers. PR1280492

  • ACX2x00-AC is reporting false PEM0 alarms periodically. PR1310488

  • Error syslog on output/egress firewall filter occurs on ACX Series routers. PR1316588

  • Network events might cause Layer 2 circuit traffic forwarding to fail with the Table Full message. PR1319591

  • With auto-installation USB configured, interface-related commits might not take effect because of dcd error. PR1327384

  • An IPv6 service outage might occur after executing the clear ipv6 neighbor command. PR1330791

  • Unable to commit multiple Ethernet-ring instances on ACX Series routers. PR1337497

  • The ARP reply packet might be dropped in a Layer 2 circuit secondary path when using IEEE-802.1 classifier. PR1341126

  • Traffic destined for specific IP within a subnet gets discarded without notification. PR1345098

  • NAT might not work and the spd might crash. PR1346546

  • The fxpc might crash on Packet Fowarding engine command show pfe context_vlan. PR1349721

  • ARP reply is droped when temporal buffer-size is added on the NNI interface. PR1363153

  • IPsec SA as OSPFv3 authentication is not working in Junos OS Releases 16.2R2 and 17.3R2. PR1363487

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

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

Layer 2 Ethernet Services

  • JDHCPD memory leak occures during dhcp/pppoe login/logout loop. PR1289780

Platform and Infrastructure

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

Resolved Issues: 17.1R2

General Routing

  • The SNMP MIB walk for jnxOperatingState incorrectly shows the CB status as down. PR1191995

  • 10-Gigabit Ethernet interface fault detection behavior changed. PR1223457

Resolved Issues: 17.1R1

There are no fixed issues in Junos OS 17.1R1 for ACX Series.

Documentation Updates

This section lists the errata and changes in Junos OS Release 17.1R3 for the ACX Series documentation.

Protocol Independent Routing Properties

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

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 hours, 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 15.1, 16.1 and 16.2 are EEOL releases. You can upgrade from Junos OS Release 15.1 to Release 16.1 or even from Junos OS Release 15.1 to Release 16.2. 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.

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.