Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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