Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Junos OS Release Notes for ACX Series

 

These release notes accompany Junos OS Release 20.3R1 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.

What's New

This section describes the new features or enhancements to existing features in Junos OS Release 20.3R1 for the ACX Series.

Hardware

  • We’ve added the following features to the ACX710 in Junos OS Release 20.3R1.

    Table 1: Features Supported by the ACX710

    Feature

    Description

    Class of service (CoS)

    • Support for hierarchical CoS. Support for up to three levels of hierarchical scheduling (physical interfaces, logical interfaces, and queues). [See Hierarchical Class of Service.]

    Network management and monitoring

    • Support for counters to display systemwide and interface-level statistics. You can configure new counters under flat-file (interface level, logical-interface-level, and ae-level statistics), interface (interface-level statistics), and Routing Engine profile (systemwide statistics) of the accounting options. [See Accounting Options Configurations.]

    Timing and synchronization

EVPNS

  • Multicast with IGMP or MLD snooping within VLANs for EVPN-MPLS (ACX5448, ACX5448-D, and ACX5448-M)—Starting in Junos OS Release 20.3R1, ACX5448 routers support multicast with IGMP or Multicast Listener Discovery (MLD) snooping within VLANs on provider edge (PE) devices in an EVPN-MPLS multihoming environment. You can configure IGMP or MLD snooping with IGMPv2, IGMPv3, MLDv1, or MLDv2 in multiple routing instances of type evpn. Multicast receivers must be within the EVPN instance (EVI). If you have only intra-VLAN traffic, you can have the multicast sources within the EVI. (Otherwise, inter-VLAN multicast requires sources to be in an external Layer 3 PIM domain.)

    With this support, PE devices:

    • Process IGMPv2 and MLDv1 any-source multicast (ASM) (*,G) reports by default.

    • Process IGMPv3 or MLDv2 reports in ASM mode (but only if you configure IGMPv3 or MLDv2 on all interfaces that receive multicast traffic).

    • Drop IGMPv3 or MLDv2 source-specific multicast (SSM) (S,G) reports.

    [See Overview of Multicast Forwarding with IGMP or MLD Snooping in an EVPN-MPLS Environment.]

  • Multicast with IGMP or MLD snooping across VLANs for EVPN-MPLS (ACX5448, ACX5448-D, and ACX5448-M)—Starting in Junos OS Release 20.3R1, ACX5448 routers support multicast with IGMP or MLD snooping across VLANs on provider edge (PE) devices in an EVPN-MPLS multihoming environment. You can configure IGMP or MLD snooping with IGMPv2, IGMPv3, MLDv1, or MLDv2 in multiple routing instances of type evpn.

    Multicast receivers must be within the EVPN instance (EVI). Sources must be outside the EVI in a Layer 3 Protocol Independent Multicast (PIM) domain. All PE devices connect to a PIM gateway using Layer 3 interfaces on which they receive the multicast source traffic. Then IRB interfaces in PIM distributed designated router (DR) mode forward or route the multicast traffic locally to interested receivers.

    PE devices can process ASM (*,G) reports by default, or IGMPv3 and MLDv2 SSM (S,G) reports with a configuration option.

    [See Overview of Multicast Forwarding with IGMP or MLD Snooping in an EVPN-MPLS Environment.]

  • Color-based mapping of EVPN-MPLS and EVPN services over SR-TE (ACX5448, EX9200, MX Series, and vMX)—Starting in Junos OS Release 20.3R1, you can specify a color attribute along with an IP protocol next hop. The color attribute adds another dimension to the resolution of transport tunnels over static colored and BGP segment routing traffic-engineered (SR-TE) label-switched paths (LSPs). This type of resolution is known as the color-IP protocol next-hop resolution. To enable the color-IP protocol next-hop resolution, you must configure a resolution map and apply it to EVPN-MPLS and EVPN services, which include E-Line, E-LAN and E-Tree. With this feature, you can enable color-based traffic steering of EVPN-MPLS and EVPN services.

    [See Segment Routing LSP Configuration.]

Multicast

  • Support for BGP MVPN (ACX5448)—Starting in Junos OS Release 20.3R1, ACX5448 routers support BGP MVPN (also known as “next generation,” or “NG,” MVPN) running on multipoint LDP provider tunnels, where BGP MVPN is the intra-AS and PIM-SM and multipoint LDP point-to-multipoint (P2MP) tunnels from the data plane. Other configurations and features are not supported in this release.

    [See Multiprotocol BGP MVPNs Overview.]

Network Management and Monitoring

  • Probe command to query the status of the probed interfaces (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 20.3R1, you can use the probe command to query the status of the probed interface. The proxy interface resides on the same node as the probed interface, or it can reside on a node to which the probed interface is directly connected.

    The Probe command helps to capture the interface details such as probe packet statistics, and interface state (active/inactive), irrespective of whether the network family address configured is IPv4 or IPv6 on the probed interfaces.

    To enable the probe command, configure the extended-echo statement under the [edit system] hierarchy.

    [See What is the Probe command?.]

Routing Protocols

  • Support for multiple MD5 for RIPv2 (ACX Series)—Starting in Junos OS Release 20.3R1, you can define multiple MD5 authentication keys for RIPv2. This feature supports adding of MD5 keys with their start-time. RIPv2 packets are transmitted with MD5 authentication using the first configured key. RIPv2 authentication switches to the next key based on its configured key start-time. This provides automatic key switching without user intervention to change the MD5 keys as in the case of having only one MD5 key.

    To enable multiple MD5 support for RIPv2, include the authentication-selective-md5 statement at the [edit protocols rip] hierarchy level.

    [See Example: Configuring Route Authentication for RIP using multiple MD5 keys.]

  • Support for implicit filter for default EBGP route propagation behavior without policies (ACX Series, JRR200, MX204, vRR and PTX5000)—Starting in Junos OS Release 20.3R1, we’ve introduced a new configuration hierarchy, defaults ebgp no-policy at the existing [edit protocols bgp] hierarchy level. The configuration option separates the default policy for receive and advertise, into separate clauses (accept, reject, or reject-always) to allow the route propagation behavior of EBGP speakers to vary independently from its default behavior.

    In earlier releases, the default behavior of BGP was to receive and advertise all routes. With the introduction of this feature, the default behavior still remains to “accept” all routes for both receive and advertise, but you also have an option to reject routes by default.

    With the reject configuration, you can reject routes of type inet unicast and inet6 unicast in instance types master, vrf, virtual-router, and non-forwarding. With the reject-always configuration, you can reject all routes from being received or getting advertised, irrespective of address family or instance type. By using this feature, you can control traffic in leaf autonomous systems (AS) and thereby, prevent them from having to accidentally function as transit autonomous systems.

    Note

    The introduction of this implicit filter does not affect the existing deployments that rely on the default behavior.

    [See Implicit Filter for Default EBGP route propagation behavior without policies and defaults.]

  • IS-IS and OSPF support (ACX5448, ACX5448-M, and ACX5448-D)—Starting in Release 20.3R1, Junos OS supports the following features for IS-IS and OSPF:

    • Base Segment routing (SR) support for prefix SID and Segment Routing Global Block (SRGB)

    • Anycast SID

    • BGP-LS

    • SRMS (LDP mapping server)

    • OAM

    • Topology-Independent Loop-Free Alternate (TI-LFA) link and node protection

    In addition to these features, OSPF also supports Unnumbered Ethernet interface.

    [See Introduction to OSPF and IS-IS Overview.]

Segment Routing

  • Support for LDP Tunneling over Segment Routing Traffic Engineering (MX Series, PTX Series, and ACX5448)—Starting in Junos OS Release 20.3R1, you can tunnel LDP LSPs over Segment Routing Traffic Engineering (SR-TE) in your network. Tunneling LDP over SR-TE provides consistency and co-existence of both LDP LSPs and SR-TE LSPs.

    [See Tunneling LDP over SR-TE.]

What's Changed

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 20.3R1 for the ACX Series routers.

Junos OS, XML, API, and Scripting

  • Changes to Junos XML RPC request tag names (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We've updated the Junos XML request tag name for some operational RPCs to ensure consistency across the Junos XML API. Devices running Junos OS still accept the old request tag names, but we recommend that you use the new names going forward. The changes include:

    • Most, but not all, request tag names that start with show replace show with get in the name.

    • Uppercase characters are converted to lowercase.

    [See Junos XML API Explorer - Operational Tags.]

Routing Protocols

  • Advertising 32 secondary loopback addresses to Traffic Engineering Database (TED) as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—In Junos OS Release, multiple loopback addresses export into lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router-ids instead of prefixes. In earlier Junos OS releases, multiple secondary loopback addresses in TED were added into lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router-id.

  • Inet6 is disabled in VT interface (ACX5448)—Starting in this release, the inet6 statement at the edit interfaces vt-interface-number unit unit-number family hierarchy level is disabled.

Known Limitations

Learn about known limitations in this release 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

  • The time consumed on 1-Gigabit Ethernet performance is not the same compared to 10-Gigabit Ethernet. Compensation is done to bring the mean value under class A but the peak-to-peak variations are high and might go beyond 100 ns. It has a latency variation with peak-to-peak variations of around 125 ns—250 ns without any traffic. (For example, 5—10 percent of the mean latency introduced by the each phy, which is of around 2.5 microseconds). PR1437175

  • With an asymmetric network connection, a 10-Gbps MACsec port connected to a 10-Gbps channelized port, high and asymmetric T1 and T4 time errors are seen. This situation introduces a high two-way time error and also different CF updates in the forward and reverse paths. PR1440140

  • With the MACsec feature enabled and introduction of traffic, the peak-to-peak value varies with the percentage of traffic introduced. Finding the maximum and mean values of the time errors with different traffic rates (for example, two-router scenarios) can have the maximum value as high as 1054 ns with 95 percent traffic, 640 ns for 90 percent traffic, and 137 ns with no traffic. PR1441388

  • Difference between minimum and maximum latency is very high in a latency test. PR1483370

  • Transient traffic drop is seen on an aggregated Ethernet interface if a member does not carry traffic flaps. PR1486997

  • The throughput test fails for the 64 bytes packet in the 100-Gigabit Ethernet line rate. PR1489248

  • On the ACX710 router, traffic loss is beyond the tolerance limit of 200 ms during convergence. PR1499965

  • Not able to scale BFD to 1024 sessions with IPv4 and IPv6. PR1502170

  • Satellites do not track intermittently with GPS-only constellation. PR1505325

  • Unexpected delay counter values are seen in the output of the show ptp statistics detail command when the upstream master clock stops sending the PTP packets. PR1508031

  • Inconsistencies in the PTP lock status behavior is observed during chassis control restart. PR1508385

  • High FRR convergence is observed. PR1515512

  • Sometimes PTP takes longer time to lock PTP after being locked to GPS. PR1527346

  • The announce interval -1,0 sent from the upstream master clock gets stuck in the HOLDOVER IN mode. PR1529761

  • PTP to 1PPS noise transfer test fails for frequency 1.985 Hz. PR1522666

  • SyncE to 1PPS transient test results do not meet G.8273.2 SyncE to 1PPS transient metric. PR1522796

  • Virtual port and T-GM are not supported in Junos OS Release 20.3R1. Only G.8275.1 T-BC is supported. PR1533018

  • The g8275.1 announcement or synchronization interval rate range is not as per FS. PR1542516

Open Issues

Learn about open issues in this release 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.

Forwarding and Sampling

  • VLAN-Id based firewall match conditions might not work for a VPLS service. PR1542092

General Routing

  • A jnxIfOtnOperState trap notification is sent for all ot- interfaces. PR1406758

  • The DHCP clients are not able to scale to 96,000. PR1432849

  • Protocols get forwarded when you use the nonexisting SSM map source address in IGMPv3 instead of pruning. PR1435648

  • Drop profile max threshold might not reach its full limit when the packet size is other than 1000 bytes. PR1448418

  • The vpls-oam sessions are detected with error (RDI sent by some MEP) after changing VLANs. PR1478346

  • On the ACX710 routers, traffic loss is observed after changing the ALT port cost for RSTP. PR1482566

  • Mirroring does not work in Junos OS Release 19.4R2. PR1491789

  • In some scenarios of port disabling and restart of clock recovery process followed by port enabling might not lock until it is reconfigured. PR1505405

  • EXP marking is not as expected for the Layer 2 CKT, Layer 3 VPN, and Layer 2 VPN traffics. PR1509627

  • Transit traffic MPLS EXP bits are wrongly marked as per queue-num and not as per rewrite-rule configuration. PR1509635

  • The APTS mode of operation is not supported in G.8275.1. PR1525918

  • The IPv6 BFD sessions flap when configured below 100 ms flaps. PR1456237

  • On the ACX5448 router, the EXP rewrite for the Layer 3 VPN sends all traffic with incorrect EXP. PR1500928

  • FEC field is not displayed when the interface is down. PR1530755

  • The syslog error messages related to ACX_DFW_CFG_FAILED are observed. PR1490940

  • The show class-of-service routing-instance command does not show the configured classifier. PR1531413

  • The clksyncd process generates core file. PR1537107

  • Management Ethernet link down alarm is observed while verifying the system alarms in the Virtual Chassis setup. PR1538674

  • In the ACX5048 router, queue-counters-trans-bytes-rate are more than expected while configuring the IFD and logical interface shaping with the transmit rate and scheduler-map. PR1538934

  • The following unexpected error message is observed while deleting the remote stream 0 0 0 0 0 0 along with feb core file at 0x00ae6484 in bcmdnx_queue_assert (queue=0xc599b60) at ../../../../../src/pfe/common/drivers/bcmdnx/bcmdnx_sdk_ukern_layer.c: clksync_mimic_delete_clock_entry. PR1539953

  • On the ACX710 router, cTE should be tuned closer to 2Way cTE. PR1527347

Interfaces and Chassis

  • When reboot is issued to the standby MC-LAG node, one-time traffic hit of active path traffic is seen and later when this node comes up, the MC-LAG active and standby roles get changed to the other device. PR1505841

Platform and Infrastructure

  • The CFM remote MEP does not come up after configuration or if it remains in the Start state. PR1460555

Virtual Chassis

  • In the ACX5000 router, the following false positive parity error messages are observed: _soc_mem_array_sbusdma_read. PR1276970

Resolved Issues

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

  • Policer discarded count is shown incorrectly to the enq count of the interface queue, but the traffic behavior is as expected. PR1414887

  • The gigether-options command is enabled again under the interface hierarchy. PR1430009

  • The statistics are accessed through Broadcom API, which is the same for both tagged and untagged packets. This cannot be changed in accordance with the MX Series routers since it is directly accessed from Broadcom without any statistics changes specific to tagging from the ACX5448 router side. This impacts other statistics if the change is made. PR1430108

  • While performing repeated power-off or power-on of the device, the SMBUS transactions timeout occurs. PR1463745

  • Unable to get shared buffer count as expected. PR1468618

  • The router might become nonresponsive and bring the traffic down when the disk space becomes full. PR1470217

  • On the ACX5048 router, the egress queue statistics do not work for the aggregated Ethernet interfaces. PR1472467

  • The links might not come up when the 100-Gigabit Ethernet interface is channelized into the four 25-Gigabit Ethernet interfaces. PR1479733

  • On the ACX6360 router, the disk usage might keep increasing. PR1480217

  • Memory utilization enhancement is needed. PR1481151

  • ACX AUTHD process memory usage enhancement is needed. PR1482598

  • BFD over Layer 2 VPN or Layer 2 circuit does not work because of the SDK upgrade to version 6.5.16. PR1483014

  • On the ACX5048 router, traffic loss is observed during the unified ISSU upgrade. PR1483959

  • On the ACX5448 router, the fpc process might crash. PR1485315

  • The LSP might not come up in an LSP externally-provisioned scenario. PR1494210

  • When 40-Gigabit Ethernet or 10-Gigabit Ethernet interface optics are inserted in 100-Gigabit Ethernet or 25-Gigabit Ethernet interface port with 100-Gigabit Ethernet or 25-Gigabit Ethernet interface speed configured and vice versa, the Packet Forwarding Engine log message displays a speed mismatch. PR1494591

  • When 40-Gigabit Ethernet or 10-Gigabit Ethernet interface optics are inserted in 100-Gigabit Ethernet or 25-Gigabit Ethernet interface with 100-Gigabit Ethernet interface speed configured and vice versa, there is a speed mismatch. PR1494600

  • Outbound SSH connection flaps or leaks memory during the push configuration to the ephemeral database with a high rate. PR1497575

  • All the autonegotiation parameters are not shown in the output of the show interface media command. PR1499012

  • The hardware FRR for EVPN-VPWS, EVPN-FXC, and Layer 3 VPN with a composite next hop are not supported in Junos OS Release 20.2R1. PR1499483

  • SFP-T is unrecognized on Junos OS Release 20.3DCB after FPGA upgrade and power cycle. PR1501332

  • On the ACX710 router, the BFD sessions are in the Init state with CFM scale of 1000 on reboot or chassis-control restart. PR1503429

  • On the ACX500 router, the SFW sessions might not get updated on ms interfaces. PR1505089

  • The wavelength changes from CLI but does not update the hardware for the tunable optics. PR1506647

  • The PIC slot might shut down in less than 240 seconds due to the over temperature start time being handled incorrectly. PR1506938

  • In the PTP environment, some vendor devices acting as slave are expecting announce messages at an interval of -3 (8pps) from the upstream master device. PR1507782

  • The BFD session flaps with the following error message after a random time interval: ACX_OAM_CFG_FAILED: ACX Error (oam):dnx_bfd_l3_egress_create : Unable to create egress object. PR1513644

  • On the ACX710 router, the following error message is observed in the Packet Forwarding Engine while the EVPN core link flaps: dnx_l2alm_add_mac_table_entry_in_hw. PR1515516

  • The VM process generates a core file while running stability test in a multidimensional scenario. PR1515835

  • The l2ald process crashes during stability test with traffic on a scaled setup. PR1517074

  • On the ACX710 router, whenever a copper optic interface is disabled and enabled, the speed shows 10 Gbps rather than 1 Gbps. This issue is not seen with the fiber interface. PR1518111

  • The IPv6 neighbor state change causes Local Outlif to leak by two values, which leads to the following error: DNX_NH::dnx_nh_tag_ipv4_hw_install. PR1519372

  • The Incompatible Media type alarm is not raised when the Synchronous Ethernet source is configured over the copper SFP. PR1519615

  • If the client clock candidate is configured with a virtual port, the clock class is on T-BC. PR1520204

  • On the ACX710 router, the alarm port configuration is not cleared after deleting the alarm-port. PR1520326

  • The show class-of-service interface command does not show classifier information. PR1522941

  • On the ACX5448 chassis, mac-address and label mac-address might not match. PR1489034

  • On the ACX5000 router, the IEEE 802.1p priority and DEI values in the locally generated VLAN-based IP packets might be changed when sourced from the IRB interface. PR1490966

  • VPLS flood groups result in IPv4 traffic drop after the core interface flaps. PR1491261

  • On the ACX5048 and ACX5096 routers, the LACP control packets might be dropped due to high CPU utilization. PR1493518

  • On the ACX710 router, high convergence is observed with the EVPN-ELAN service in a scaled scenario during FRR switchover. PR1497251

  • The loopback filter cannot take more than 2 TCAM slices. PR1513998

  • On the ACX5448 and ACX710 routers, the vlan-id-list statement might not work as expected. PR1527085

  • Memory leak is observed in the local OutLif in the VPLS or CCC topology. PR1532995

  • On the ACX710 router, the following error message is observed: PFE_ERROR_FAIL_OPERATION: Failed to install in h/w, LOG: Err] dnx_nh_unilist_install: BCM L3 Egress create object failed for:Unilist nh 2097369 (0:Ok) nh 0. PR1495563

  • The following error message is observed during the MPLS route add, change, and delete operation: mpls_extra NULL. PR1502385

  • On the ACXR6675 router, the rpd process generates core file at l2ckt_vc_adv_recv, l2ckt_adv_rt_flash (taskptr=0x4363b80, rtt=0x4418100, rtl=< optimized out>, data=< optimized out>, opcode=< optimized out>) at ../../../../../../../../../src/junos/usr.sbin/rpd/l2vpn/l2ckt.c:7982. PR1537546

Interfaces and Chassis

  • The fpc process might crash with in an inline mode with CFM configured. PR1500048

MPLS

  • If there are two directly connected BGP peers established over MPLS LSP, and the MTU of the IP layer is smaller than the MTU of the MPLS layer, and also if the BGP packets from the host have the DF bit set, then the BGP session might flap because of the usage of the wrong TCP-MSS. PR1493431

Routing Protocols

  • The BGP route-target family might prevent the RR from reflecting the Layer 2 VPN and Layer 3 VPN routes. PR1492743

VPNs

  • The l2circuit neighbor might become nonresponsive in the RD state at one end of the MG-LAG peer. PR1498040

  • The rpd process might crash in certain conditions after deleting the l2circuit configuration. PR1502003

Documentation Updates

There are no errata or changes in Junos OS Release 20.3R1 documentation for ACX Series routers.

Migration, Upgrade, and Downgrade Instructions

This section contains the upgrade and downgrade support policy for Junos OS for ACX Series 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 19.3, 19.4, and 20.1 are EEOL releases. You can upgrade from Junos OS Release 19.3 to Release 19.4 or from Junos OS Release 19.3 to Release 20.1.

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.