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 features and enhancements in Junos OS Release 18.4R2 for ACX Series Universal Metro Routers.

New and Changed Features: 18.4R2

Interfaces and Chassis

  • Support for 100-Mbps and 1-Gbps speeds Tri-Rate Copper SFP (ACX5448 routers)—Starting in Junos OS Releases 18.4R2, ACX5448 router support 100-Mbps and 1-Gbps speeds on Tri-Rate Copper SFP optics (740-013111). Note that 100-Mbps speed is supported only from ports xe-0/0/24 to xe-0/0/47.

    Note

    10-Mbps speed is not supported on Tri-Rate Copper SFP due to hardware limitations.

    • To set the speed for the optics, issue the Set interfaces interface-name speed auto command. See Speed for more details.

    • To enable autonegotiation, issue the Set interfaces interface-name gigether-options auto-negotiation command. See auto-negotiation.

Software Installation and Upgrade

  • Zero Touch Provisioning (ACX5448))—Starting in Junos OS Release 18.4R1-S2, Zero Touch Provisioning (ZTP) automates the provisioning of the device configuration and software image with minimal manual intervention on management interface em0.

    When you physically connect a router to the network and boot it with a factory configuration, the router upgrades the Junos OS software image automatically and autoinstalls configuration file from the network through the management interface.

New and Changed Features: 18.4R1

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