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 19.2R3 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

Learn about new features introduced in the Junos OS main and maintenance releases for ACX Series routers.

What's New in Release 19.2R3

There are no new features or enhancements to existing features for ACX Series routers in Junos OS Release 19.2R3.

What's New in Release 19.2R2

There are no new features on ACX Series in Release 19.2R2.

What's New in Release 19.2R1-S1

Routing Protocols

  • Decouple RSVP for IGP-TE (MX Series, PTX Series, ACX Series, QFX Series, SRX Series, and EX Series)—Starting in Junos OS Release 19.2R1-S1, device can advertise selective traffic-engineering attributes such as admin-color and maximum-bandwidth, without enabling RSVP, for segment routing and interior gateway protocol (IGP) deployments.

What's New in Release 19.2R1

Class of Service (CoS)

  • Support for class of service (CoS)(ACX6360 routers)—Starting in Junos OS Release 19.2R1, ACX6360 routers support class of service (CoS) functionality.

    CoS is the assignment of traffic flows to different service levels. Service providers can use router-based CoS features to define service levels that provide different delay, jitter (delay variation), and packet loss characteristics to particular applications served by specific traffic flows.

    [See CoS on ACX Series Universal Metro Routers Features Overview.]

EVPN

  • EVPN support of VLAN ID ranges and lists in service provider style interface configurations (EX9200 switches, ACX5448 and MX Series routers, and vMX virtual routers)—Starting in Junos OS Release 19.2R1, EX9200 switches, ACX5448 and MX Series routers, and vMX virtual routers support the use of VLAN ID ranges and lists in a service provider style interface configuration, which must be referenced in an EVPN routing instance. This configuration is supported with the following EVPN environments, services, and features:

    • Environments:

      • EVPN with VXLAN encapsulation

      • EVPN with MPLS encapsulation

    • VLAN bundle service:

      • E-LAN

      • E-Tree

      • E-Line

    • Feature:

      • EVPN multihoming:

        • All-active

        • Single-active

      • Singlehoming

    [See VLAN ID Ranges and Lists in an EVPN Environment.]

Interfaces and Chassis

  • Support for 100-Mbps and 1-Gbps speeds on Tri-Rate Copper SFP (ACX5448 routers)—Starting in Junos OS Release 19.2R1, ACX5448 routers support 100-Mbps and 1-Gbps speeds on Tri-Rate Copper SFP optics (part number 740-013111).

    Note

    100-Mbps speed is supported only on ports xe-0/0/24 through xe-0/0/47.

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

Junos Telemetry Interface

  • Support for LSP statistics on JTI (ACX6360)—Starting with Junos OS Release 19.2R1, you can provision the LSP statistics sensor using the resource path /junos/services/label-switched-path/usage/ to monitor per-MPLS LSP statistics on the ACX6360 router and export telemetry data through Junos telemetry interface (JTI) to external collectors. You can stream data at configurable intervals through gRPC without involving polling.

    JTI support is only for RSVP LSPs.

    Statistics that are streamed are similar to the output displayed by the operational mode command show mpls lsp bypass statistics.

    To provision a sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support JTI.

    To enable statistics for export from the Junos OS, include the sensor-based-stats statement at the [edit protocols mpls] hierarchy level.

    [See Guidelines for gRPC Sensors (Junos Telemetry Interface) and Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

  • Specify Routing Instance for JTI (ACX Series, MX Series, PTX Series, and QFX Series)—Starting in Junos OS Release 19.2R1, you can specify the routing instance to use for remote procedure call (gRPC) services. Include the routing-instance instance-name at the [edit system services extension-service request-response grpc] hierarchy level. The routing instance name specified should match the name of the existing routing instance, such as a name configured under the [routing-instances] hierarchy level or mgmt_junos if system management-instance is configured (the dedicated management routing instance).

    Configuring the routing instance lets you choose the VRF for gRPC services. When the routing instance is not configured, the default behavior is that all gRPC-related services are available through the management fxp0/em0) interface.

Layer 3 Features

  • Support for Layer 3 unicast features (ACX 6360)—Starting in Junos OS Release  19.2R1, ACX routers support the following Layer 3 forwarding features for unicast IPv4 and IPv6 traffic:

    • Basic IPv6 forwarding

    • Virtual router (VRF-lite) for both IPv4 and IPv6

    • Layer 3 subinterfaces support for both IPv4 and IPv6

    • VRF-lite, subinterfaces, and IPv6 forwarding support on link aggregation groups (LAGs)

    • Statistics support for Layer 3 subinterfaces

    • 32-way equal-cost multipath (ECMP)

    • Centralized Bidirectional Forwarding Detection (BFD)

    • IPv4 Layer 3 protocols:

      • OSPF

      • IS-IS

      • BGP

    • IPv6 Layer 3 protocols:

      • OSPFv3

      • RIPng

Network Management and Monitoring

  • Support for displaying valid user input in the CLI for command options and configuration statements in custom YANG data models (ACX Series)—Starting in Junos OS Release 19.2R1, the CLI displays the set of possible values for a given command option or configuration statement in a custom YANG data model when you include the action-expand extension statement in the option or statement definition and reference a script that handles the logic. The action-expand statement must include the script child statement, which defines the Python action script that is invoked when a user requests context-sensitive help in the CLI for the value of that option or statement.

    [See Displaying Valid Command Option and Configuration Statement Values in the CLI for Custom YANG Modules.]

Software Installation and Upgrade

  • Zero Touch Provisioning (ACX5448)—Starting in Junos OS Release 19.2R1, 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 automatically installs a configuration file from the network through the management interface.

    [See Zero Touch Provisioning.]

System Management

  • Support for transferring accounting statistics files and router configuration archives using HTTP URL (ACX Series)—Starting in Junos OS Release 19.2R1, you can transfer accounting statistics files and router configuration archives to remote servers by using an HTTP URL. In addition to SCP and FTP, the following HTTP URL will be supported under the archive-sites statement:

    http://username@host:url-path password password

    • To transfer accounting statistics files, configure archive-sites under [edit accounting-options file <filename>] hierarchy.

    • To transfer router configuration archival, configure archive-sites under edit system archival configuration hierarchy.

    • To view the statistics of transfer attempted, succeeded, and failed, use the show accounting server statistics archival-transfer command.

    • To clear the statistics of transfer attempted, succeeded, and failed, use the clear accounting server statistics archival-transfer command.

    [See archive-sites, Backing Up Configurations to an Archive Site, show accounting server statistics archival-transfer, and clear accounting server statistics archival-transfer].

  • Precision Time Protocol (PTP) Transparent Clock with IPv6 Transport (PTX10001-20C and ACX6360-OR devices)—Starting with Junos OS Release 19.2R1, PTP uses IPv6 transport to synchronize clocks throughout a packet-switched network. With a transparent clock, the PTP packets are updated with theresidence time as the packets pass through the switch. There is no master/slaved designation. End-to-end transparent clocks are supported. With an end-to-end transparent clock, only the residence time is included. The residence time can be sent in a one-step process, which means that the timestamps are sent in one packet.

    You can configure the transparent clock at the [edit protocols ptp] Junos OS CLI hierarchy.

    [See Understanding Transparent Clocks in Precision Time Protocol.]

What's Changed

Learn about what changed in the Junos OS main and maintenance releases for ACX Series routers.

What’s Changed in 19.2R3-S1

General Routing

  • Support for gigether-options statement (ACX5048, ACX5096)—Junos OS supports the gigether-options statement at the edit interfaces interface-name hierarchy on the ACX5048 and ACX5096 routers. Previously, support for the gigether-statement was deprecated.

    [See gigether-options.]

What’s Changed in 19.2R3

General Routing

  • Advertising /32 secondary loopback addresses to traffic engineering database as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We've made changes to export multiple loopback addresses to the 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 releases, we added multiple secondary loopback addresses in the traffic engineering database to the lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router ID.

Juniper Extension Toolkit (JET)

  • Set the trace log to only show error messages (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series)— You can set the verbosity of the trace log to only show error messages using the error option at the edit system services extension-service traceoptions level hierarchy.

    See traceoptions (Services).

What’s Changed in 19.2R2

General Routing

  • LLDP ON_CHANGE statistics support with JTI (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series)—Enhanced telemetry ON_CHANGE event support provides the following LLDP attributes:

    • When LLDP is enabled on interfaces, LLDP interface counters are notified along with other interface-level attributes.

    • ON_CHANGE event reports LLDP neighbor age and custom TLVs, as well as when a neighbor is initially discovered.

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface]

Interfaces and Chassis

  • Support for creating Layer 2 logical interfaces independently (ACX Series, EX Series, MX Series, PTX Series, and QFX Series)—In Junos OS Release 19.2R2 and later, ACX Series routers support creating Layer 2 logical interfaces independent of the Layer 2 routing-instance type. That is, you can configure and commit the Layer 2 logical interfaces separately and add the interfaces to the bridge domain or Ethernet VPN (EVPN) routing instance separately. Note that the Layer 2 logical interfaces work fine only when they are added to the bridge domain or EVPN routing instance.

    In earlier Junos OS releases, when you use a Layer 2 logical interface configuration (units with encapsulation vlan-bridge configuration), then you must add the logical interface as part of a bridge domain or EVPN routing instance for the commit to succeed.

  • Support for disabling RS-FEC (ACX6360-OX)—By default, Junos OS software enables or disables forward error correction based on plugged-in optics. Starting with Junos OS Release 19.2R2, on ACX6360-OX routers functioning as transponders, you can now disable Ethernet FEC, also known as RS-FEC or FEC91. Previously, RS-FEC was enabled by default and could not be disabled.

    [See fec.]

Operation, Administration, and Maintenance (OAM)

  • Performance monitoring history data is lost when a change in number of supported history records is detected (ACX Series and MX Series)—In Junos OS Release 19.2R2, when Ethernet connectivity fault management starts, it detects the number of history records supported by the existing Performance Monitoring history database and if there is any change from the number of history records supported (that is, 12) in Release 19.2R2, then the existing performance monitoring history database is cleared and all performance monitoring sessions are restarted with mi-index 1.

Routing Protocols

  • XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.2R2, we have included an XML RPC equivalent for the show bgp output-scheduler | display xml rpc CLI command. In Junos OS releases before Release 19.2R2, the show bgp output-scheduler | display xml rpc CLI command does not have an XML RPC equivalent.

    [See show bgp output-scheduler.]

What’s Changed in 19.2R1

Interfaces and Chassis

  • Monitoring information available only in trace log (ACX Series)—In Junos OS Release 19.2R1 and later, the Ethernet link fault management daemon (lfmd) in the peer router stops monitoring the locally occurred errors until ISSU completes. You can view the monitoring-related details only through the trace log file.

Network Management and Monitoring

  • The show system schema command and <get-yang-schema> RPC require specifying an output directory (ACX Series)—Starting in Junos OS Release 19.2R1, when you issue the show system schema operational mode command in the CLI or execute the <get-yang-schema> RPC in a remote session to retrieve schema files, you must specify the directory in which to generate the output files by including the output-directory command option in the CLI or the <output-directory> element in the RPC. In earlier releases, you can omit the output-directory argument when requesting a single module to display the module in standard output.

  • Custom YANG RPC support for input parameters of type empty (ACX Series)—Starting in Junos OS Release 19.2R1, custom YANG RPCs support input parameters of type empty when executing the RPC’s command in the Junos OS CLI, and the value passed to the action script is the parameter name. In earlier releases, input parameters of type empty are only supported when executing the RPC in a NETCONF or Junos XML protocol session, and the value passed to the action script is the string 'none'.

    [See Creating Action Scripts for YANG RPCs on Devices Running Junos OS.]

VLAN Infrastructure

  • Specifying a descending VLAN ID range ( ACX5448 routers)—In Junos OS releases prior to Junos OS Release 19.2R1, the system accepts a descending range—for example, 102-100, with the vlan-id-range configuration statement in the [edit interfaces interface-name unit logical-unit-number] hierarchy.

    Starting with Junos OS Release 19.2R1, the system considers a descending range specified with vlan-id-range to be invalid and raises an error if you try to commit this configuration.

Known Limitations

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

  • All PTP packets go to the best-effort queue instead of the network control queue. This is because of the limitation on ACX5448 where DSCP values are not preserved. PR1361315

  • ACX6360 Junos telemetry interface or telemetry 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 an Ethernet (et) interface, only the 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 transponder nodes. PR1389802

  • The ACX6360 TIC has only 8 CFP2-DCO ports, so chassis beacon show/requests to port numbers larger than 7 do not work (as the ports don't exist) but also do not report an error. user@router> request chassis beacon fpc 0 pic-slot 1 port 15 on FPC 0 PIC 1 PORT 15 ON user@router> show chassis beacon fpc 0 pic-slot 1 port-range lower-limit 0 upper-limit 15 FPC 0 PIC 1 PORT 0 ON FPC 0 PIC 1 PORT 1 ON FPC 0 PIC 1 PORT 2 ON FPC 0 PIC 1 PORT 3 ON FPC 0 PIC 1 PORT 4 ON FPC 0 PIC 1 PORT 5 ON FPC 0 PIC 1 PORT 6 ON FPC 0 PIC 1 PORT 7 ON FPC 0 PIC 1 PORT 8 ON FPC 0 PIC 1 PORT 9 ON FPC 0 PIC 1 PORT 10 OFF FPC 0 PIC 1 PORT 11 OFF FPC 0 PIC 1 PORT 12 OFF FPC 0 PIC 1 PORT 13 OFF FPC 0 PIC 1 PORT 14 OFF FPC 0 PIC 1 PORT 15 ON. PR1399335

  • When a timing configuration and the corresponding interface configuration are flapped for multiple times in iteration, PTP is stuck in "INITIALIZE" state where the ARP for the neighbor is not resolved. In issue state, BCM hardware block gets into inconsistency state, where the lookup is failing. PR1410746

  • The input packet count given under the traffic statistics includes all packets that are coming in. The statistics are not segregated as IPv4, IPv6, MPLS, and so on. This is the same behavior across all the ACX Series platforms. PR1419143

  • Hardware-based fragmentation or reassembly is not supported. Software-based fragmentation rates are going to be extremely slow depending on CPU load. PR1419371

  • In the output of show SNMP mib walk jnxBoxAnatomy, the chassis CLEI code and contents model is reading data from the I2C bus and EEPROM. Because the fan is not present on the I2C bus and does not have EEPROM, fan data can’t be displayed for chassis CLEI code and contents model. PR1420639

  • There is no support on separate counters for egress-dropped packets. Counters are reflected as part of RED-dropped packets. PR1427148

  • Problem description: When end device (fan tray CPLD) I2C line is grounded or pulled low, other device write/reads are failing. From our testing, we have concluded the following: We have verified isolation functionality when the device is in the problem state, it's working fine (verified through software simulation). But in this case where we grounded one of the fan tray CPLD i2c lines to verify the failed test case, then entire circuit will get stalled and it leads to write fail for other devices also such as the PEM, and temperature. This is a hardware limitation. PR1427222

  • These error messages can be seen sometimes if the optics module is being unplugged in between the EEPROM read. This is expected and does not impact any functionality. PR1429016

  • Packet rates are not seen for aggregated Ethernet logical interface. PR1429590

  • Multicast packets are flooded in a BD if snooping is not enabled. If interfaces x and y belong to a BD, then all multicast packets will be flooded to both x and y interface. If packets are received from interface x, packets will be flooded to x and y in ingress but discarded in the egress path for interface x because packet is received from the same interface. But these packets are also counted in the VOQ and hence we are seeing more queue statistics. It is a known hardware limitation. monitor interface xe-0/0/30Input packets: 177958 (64 pps) [0]Output packets: 357306 (128 pps) [0] monitor interface xe-0/0/12Input packets: 361161 (128 pps) [642]Output packets: 179878 (63 pps) [320] root@rioxd-p2a-a> show interfaces queue xe-0/0/30 Queue: 0, Forwarding classes: best-effortQueued:Packets : 544032 192 pps . => Sum of 64 + 128pps root@rioxd-p2a-a> show interfaces queue xe-0/0/12 Queue: 0, Forwarding classes: best-effortQueued:Packets : 550929 192 pps . => Sum of 64 + 128pps. PR1429628

  • Any packet greater than the MTU size are accounted for oversized packets. Packets exceeding MTU sizes are not considered for Jabber check. PR1429923

  • The statistics are accessed through Broadcom API, which is the same for both tagged and untagged packets. This cannot be changed in accordance with MX Series, because it is direct access from Broadcom without any statistics changes specific to tagging from ACX5448 side. It will impact other statistics if changes are made. PR1430108

  • The port LEDs glowing during system/vmhost halt state is the expected behavior across all ACX Series platforms. Even the system LED glows during halt state. PR1430129

  • These are initial transient messages seen and do not have any functional impact. PR1430355

  • 1-Gigabit Ethernet interfaces are shown as “xe”. Therefore, the cosmetic issue is observed with respect to autonegotiation parameters although there is no impact on functionality. PR1430835

  • If Layer 2 VPN sessions have OAM control-channel option set to router-alert-label, the no-control-word option in L2VPN shouldn't be used for BFD sessions to come up. PR1432854

  • BCM SDK currently does support statistics, and we see routes are getting reinstalled on a periodic basis. SDK does not support statistics unless we move to Flex mode in KBP. This is a product limitation today. PR1435579

  • New rate of 1.8 MB/s and which takes 16-17 min to copy the ACX5448 image (1.9G image size) - ACX5448 rates are less than Misha because the rate limiter is in bps and does not support pps-based (hardware limitation from DNX)*Avg size is 512. Hence rate is approximately one third of Misha rate. In file copy cases, normal pkt size seen are 1500 pkt sizes. PR1439960

  • The hold timer expiry is common across all platforms. It is not specific to ACX5448-D. PR1439980

  • Remote loopback is not supported on ACX5448-D. PR1443517

  • The PEM entries for jnxFruName SNMP index are shown twice. PR1446215

  • ACX Series routers support only 900 joins of IGMPv3 users per second. PR1448146

  • The 2000 EVPN IRB scale is not hitting due to hardware limitation of filter entries that can be installed for EVPN instances. We can support only 1000 scale for Junos OS release 19.2. This is Broadcom limitation and cannot be changed. PR1461309

  • Counters for filtering based on DA MAC and SA MAC are not supported, because QMX doesn't have any separate counter to count matched or dropped packets with interface MAC address. PR1463981

Open Issues

Learn about open issues in this release for ACX Series 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

  • Forwarding when using nonexisting SSM map source address in IGMPv3 instead of pruning. This is a day-1 design issue and needs a design solution. PR1126699

  • 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

  • ACX5448: When a 1-Gigabit SFP transceiver is plugged into the router, autonegotiation is enabled by default. There is no functional impact. Only the output of the show interfaces <intf-name> extensive CLI command shows the autonegotiation field as disabled. PR1343679

  • If the set interfaces ae<>xaggregated-ether-options link-speed <x> configuration is used in the router, after reboot AE interface remains down. Error seen in logs: /kernel: kernel did not add link ae1, link speeds differ 1000000000 10000000000 /kernel: bundle ae1.0: link xe-0/3/0 not added due to speed mismatch. PR1357012

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

  • The SD (Signal Degrade) threshold is normally lower than the SF threshold (that is, so that as errors increase, SD condition is encountered first). For the ACX6360 optical links there is no guard code to prevent the user from setting the SD threshold, above the SF threshold which would cause increasing errors to trigger the SF alarm before the SD alarm. This will not cause any issues on systems with correctly provisioned SD/SF thresholds. PR1376869

  • ACX6360-OR: Enhancement is needed for FRR BER threshold SNMP support. PR1383303

  • On ACX6360/PTX10001 router, Tx power cannot be configured using + sign. PR1383980

  • More that expected traffic loss is observed during link failure (FRR convergence) and link restoration test on L3VPN traffic over LDP-OSPF MPLS LSP.

    Steps to re-create:

    1. Layer 3 VPN traffic was flowing end to end on the active path in steady state.

    2. Link down state is induced on primary path and traffic is shifted to backup path. Observation: More than expected traffic loss is observed (around 1.5 seconds).

    3. Link is restored and the traffic is moved to the active path. Observation: More than expected traffic loss is observed (around 21 seconds).

    The traffic loss percentage is not consistent and varies across each run, and this is the worst-case traffic loss percentage observed. PR1387834

  • The switchover time observed was more than 50 ms under certain soak test conditions with an increased scale with a multiprotocol multirouter topology. PR1387858

  • IGMP packets over L2 Circuit with Control-Word are dropped in ACX5048. PR1394301

  • The ccc logs are not compressed after rotation. PR1398511

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

  • Layer 2 rewrite is happening on regular bridge domain and VLAN interfaces, although there are some service dependencies (VPLS in this case) due to which, the egress interface map table is not updated properly with the Layer 2 rewrite map ID. As a result, the rewrite does not work. PR1414414

  • Clock class value is incorrect in default data (show ptp clock) when the slave interface is down in the PTP-OC device. PR1416421

  • On ACX5448 devices, the zero-touch provisioning (ZTP) process will proceed with image upgrade even in situations when there is a mismatch between the platform name of the software image stored on FTP or ZTP servers and the actual platform where the ZTP process is being run. PR1418313

  • The issue is not fixed in Junos OS Release 19.1 where inner VLAN tag classification will not work. It is not fixed in 18.3R2 release. Also not fixed in 19.2R1 Release. There was a behavior change introduced as part of PR1307666, where the inner VLAN tag is popped out on the ingress side when an IP packet with double-tagged VLAN is received, and this change is needed for IP packets to work on proper transmit on the egress interface. PR1422515

  • Under scale conditions, if multiple bridge-domains are deleted together, then sometimes Broadcom SDK returns error Entry not found. This indicates that the resource is already freed up. PR1423308

  • On an ACX5448, the request system reboot command triggers a reboot on the host (Linux) instead of just being limited to Junos OS. PR1426486

  • Traffic loss is seen if the configuration has /128 prefix routes and its limited to /128 only. This is due to a known issue tracked in PR1445231. PR1429833

  • Any packets greater than the MTU size are accounted for as oversized packets. Packets exceeding MTU sizes are not considered for Jabber check. PR1429923

  • The port LEDs glowing during system/vmhost halt state is the expected behavior across all ACX Series platforms. Even the system LED glows during halt state. PR1430129

  • Packets dropped due to MTU checks in the output interface are not accounted for MTU errors. All packets above MTU size are accounted for Oversized-packets in the input interface. PR1430446

  • Protocols get forwarded when using a nonexisting SSM map source address in IGMPv3 instead of pruning. This is a day 1 design issue, and needs a design solution. PR1435648

  • On ACX5448 box, after issuing deactivate/activate "class-of-service", traffic drop might be seen. PR1436494

  • In certain test conditions, it was observed that L2VPN at a scale of 16,000 had issues when all VPNs were brought down and up. PR1439471

  • Recovery of Junos volume is not possible from the OAM menu. PR1446512

  • Drop profile maximum threshold might not be reached when the packet size is other than 1000 bytes. This is due to the current design limitation. PR1448418

  • When an xe interface working in 1-Gigabit mode in ACX5448-D is added to a member link of an aggregated Ethernet interface, the speed of the aggregated Ethernet interface is incorrectly shown as 10 Gbps. There is no functional impact. This is a display issue. PR1449887

  • It is not possible to form 125,000 IGMP groups with the ACX5448 router receiving 125,000 IGMP v2 reports per second. This is a product limitation from BCM and CPU host path queuing model. PR1454465

  • The issue is seen during unified ISSU to Junos OS Releases 20.1, 20.2, and 19.4. The upgrade is successful but the forwarding plane (PFE) does not function. As a result, forwarding is affected. PR1483959

  • On ACX Series platforms with shaping configured, after deactivating and activating CoS the shaping might not work and traffic drop would appear. PR1488935

  • In PTP environment some vendor devices acting as slave expecting announce messages at an interval of -3 (8pps) from upstream master device. As of today announce message are configurable in range of 0 to 3. To support the above requirement engineering provided a hidden cli knob "set protocol ptp master announce-interval -3". In the networks/design where we have this requirement. we can configure the hidden cli otherwise regular cli which is in the range (0 to 3) can be configurable. Both the cli knobs are mutually exclusive, commit error is expected if both are configured. This new change is applicable to ACX platforms only excluding ACX5000. PR1507782

MPLS

  • The default behavior of local reversion has changed from Junos OS Release 16.1 and that impacts the LSPs for which the ingress does not perform make-before-break. Junos OS does not perform make-before-break for no-cspf LSPs. PR1401800

Resolved Issues

Learn which issues were resolved in the Junos OS main and maintenance releases for ACX Series routers.

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

Resolved Issues: 19.2R3

General Routing

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

  • ACX5448-D interfaces support: The input bytes value in the show interfaces extensive command output is not at par with older ACX Series or MX Series devices. PR1430108

  • CoS: Egress queue statistics are not applicable to ae interfaces on ACX5048. PR1472467

  • ERP might not come up properly when MSTP and ERP are enabled on the same interface. PR1473610

  • Link does not come up when 100-Gigabit Ethernet is channelized to 4x25-Gigabit Ethernet interfaces. PR1479733

  • During speed mismatch, QSFP28/QSFp+ the optics/cables might or might not work. PR1494600

  • Outbound SSH connection flap or memory leak issue might be observed during pushing configuration to ephemeral DB with high rate. PR1497575

  • SFW sessions are not getting updated on ms interfaces in ACX500-i. PR1505089

  • PIC slot may be shut down less than 240 seconds because the over-temperature start time is handled incorrectly. PR1506938

  • L2ALD crash is seen during stability test with traffic on scaled setup. PR1517074

MPLS

  • BGP session might keep flapping between two directly connected BGP peers because of the incorrect TCP MSS (maximum segment size) in use. PR1493431

Routing Protocols

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

VPNs

  • The Layer 2 circuit neighbor might be stuck in RD state at one end of MG-LAG peer. PR1498040

Resolved Issues: 19.2R2

Class of Service (CoS)

  • The dfwd crash can be seen with the forwarding-class configuration in policers. PR1436894

General Routing

  • ACX5000 MacDrainTimeOut and bcm_port_update failed: Internal error. PR1284590

  • bcmDPC task is high even though Interupt START_BY_START flag set to 0. PR1329656

  • On an ACX Series router, the LED on a Gigabit Ethernet interface goes down when the 10-Mbps speed is added. PR1385855

  • Link fault signaling (LFS) is not working on ACX5448 10/40/100GbE interfaces. PR1401718

  • Kernel memory leak in virtual-memory due to interface flaps (CVE-2020-1625). PR1407000

  • High CPU consumption for fxpc processes with class-of-service changes on AE interfaces. PR1407098

  • The optic comes with Tx enabled by default. As the port is administratively disabled, the port is stopped but as the port has not been started, it does not disable Tx. PR1411015

  • ACX5448: 40G FEC on ACX5448 is default FEC is enabled need to align with our platforms MX/QFX where FEC is NONE. PR1414649

  • ACX5448: BFD Timer values are not as per the configured 900ms with multiplier 3. The values are showing 6.000 with multiplier 3 instead for most of the sessions. PR1418680

  • [ARP] ACX5448-D: 96000 ARPs are getting populated but only 47,000 next-hop entries are present. Therefore, around 50% packet drop is observed. PR1426734

  • Drift messages in ACX2200, which is a PTP hybrid (PTP + Synchronous Ethernet) device. PR1426910

  • The chassisd process might crash with unsupported HCoS configuration when MX104 is used as the fusion aggregation device. PR1430076

  • On ACX5448, upon reboot of an MC_LAG peer, when the peer comes up (but before hardware comes up), there is a 10-20 second traffic hit on node1. PR1430910

  • ACX5448-D interface support: After chassis control restart, load balancing on the child interfaces of an ae interface stops. PR1431206

  • The l2cpd process might crash and generate a core file when interfaces are flapping. PR1431355

  • ACX5448 might malfunction in encapsulating small packets if egress link is 40G or 100G. PR1434900

  • In ACX Series platforms, no-vrf-propagate-ttl might not work after the CoS configuration is deactivated and then activated. PR1435791

  • LACP state might get stuck in 'Attached' state after disabling peer active members. PR1439268

  • Packet drop might be seen on an ACX Series platform when chained composite next hop is enabled for L3VPN. PR1439317

  • Interface on ACX1100 remains down when using SFP-1FE-FX (740-021487). PR1439384

  • On ACX5448, DHCP packets are not transparent over Layer 2 circuit. PR1439518

  • When the interface is flapped between channelized configurations (25GbE to 100GbE), the AE interface configuration is not cleaned up properly. PR1441374

  • ACX5448: Packet buffer error from Packet Forwarding Engine leading to memory leak when IGMP is sent from NNI AC in Layer 2 circuit and VPLS. PR1442901

  • RED drops might be seen after link flaps or CoS configuration changes. PR1443466

  • ACX5448: The encapsulation flexible-vlan-tagging is not supported with the MPLS family; need to provide commit error. PR1445046

  • ACX5448/18.3R1-S4.1 not performing proper dot1p CoS rewrite on interfaces configured with l2circuit/local-switching/family ccc. PR1445979

  • In ACX Series routers, auto-exported routes between VRFs might not reply for ICMP echo requests. PR1446043

  • Fans on an ACX5448-M might not be running at the correct speed. PR1448884

  • Layer 2 circuit with a backup-neighbor (hot-standby) configured might stop forwarding traffic after failovers. PR1449681

  • Oper-state for et interface does not transition from 'init' to 'Normal'. PR1449937

  • FPC core files might be seen after changing the configuration of PTP or Synchronous Ethernet. PR1451950

  • Platforms: ACX5448-D interfaces support: After the 100-Gbps and 40-Gbps interfaces are disabled, the Laser output power in show interfaces diagnostics optics shows some values. PR1452323

  • ACX5448 FPC crashed due to segmentation fault. PR1453766

  • Incorrect operating state displayed in SNMP trap for fan removal. PR1455577

  • ACX5048 SNMP polling will be stalled after a link flap or an SFP transceiver replacement, and ACX_COS_HALP(acx_cos_gport_sched_set_strict_priority:987): Failed to detach logs will be seen. PR1455722

  • ACX6360-OX: Enable the gigether option to configure Ethernet FEC on client ports. PR1456293

  • ACX5448-D and ACX5448-M devices do not display airflow information and temperature sensors as expected. PR1456593

  • ACX5448 L2VPN with encapsulation-type ethernet stops passing traffic after a random port is added with VLAN configuration. PR1456624

  • The rpd crash might be seen if a BGP route is resolved over the same prefix protocol next hop in an inet.3 table that has both RSVP and LDP routes. PR1458595

  • Route resolution is not happening when the packet size is 10,000. PR1458744

  • Traffic might be silently dropped during link recovery in an open Ethernet access ring with ERPS configured. PR1459446

  • ACX5000: SNMP MIB walk for jnxOperatingTemp not returning anything for FPC in new versions. PR1460391

  • ACX5448-D interfaces and optics support: Sometimes, when the AE interfaces are brought up, there are ARP resolution issues. PR1461485

  • On ACX Series platforms, the LLDP neighbor not up on a LAG after software upgrade to Junos OS Release 18.2R3-S1. PR1461831

  • Memory leak on l2cpd process might lead to l2cpd crash. PR1469635

  • RED drop on interface even without any congestion. PR1470619

  • Egress queue statistics are not applicable to ae interface on model ACX5048. PR1472467

  • ERP might not come up properly when MSTP and ERP are enabled on the same interface. PR1473610

  • dcpfe core files are seen when disabling/enabling MACsec using Toby scripts. PR1479710

  • ACX5448 Layer 2 VPN with interface ethernet-ccc input-vlan-map/output-vlan-map can cause traffic to be dropped silently. PR1485444

Interfaces and Chassis

  • Upgrade from releases before Junos OS Release 17.4R1 results in cfmd core files. PR1425804

  • MC-AE interface might show as unknown status if you are adding the subinterface as part of the VLAN on the peer MC-AE node. PR1479012

Layer 2 Ethernet Services

  • DHCP request might get dropped in a DHCP relay scenario. PR1435039

Platform and Infrastructure

  • The REST API process becomes nonresponsive when a number of requests come at a high rate. PR1449987

Routing Protocols

  • Export of loopback address to other VRF instances might not work on ACX Series, EX Series and QFX Series platforms. PR1449410

  • MPLS LDP might still use stale MAC addresses of the neighbor even if the LDP neighbor's MAC address changes. PR1451217

  • The rpd might crash continuously due to memory corruption in IS-IS setup. PR1455432

  • The routing protocol process (rpd) crashes while processing a specific BGP update information. PR1448425

  • Receipt of certain genuine BGP packets from any BGP speaker causes rpd to crash. PR1497721

VPN

  • The l2circuit neighbor might be stuck in RD state at one end of MG-LAG peer. PR1498040

Resolved Issues: 19.2R1-S1

General Routing

  • Link Fault Signaling (LFS) do not work on ACX5448, ACX5410, ACX5440, and 100-Gigabit Ethernet interfaces. PR1401718

  • In an ACX5448 platforms, when the Packet Forwarding Engine failed to allocate packet buffer, portion of packet memories might not be free. PR1442901

Resolved Issues: 19.2R1

Class of Service (CoS)

  • The error message STUCK_BUFF : port_sp not empty for port 35 sp 1 pkts:1 is seen when a lag bundle is configured with 64 lag links.. PR1346452

General Routing

  • The 1G copper module interface shows "Link-mode: Half-duplex". PR1286709

  • On an ACX ring topology, after link between ACX and MX flaps, VPLS RI on PE (MX) has no MAC of CE over l2circuit. PR1360967

  • ACX5000: fpc0 (acx_rt_ip_uc_lpm_install:LPM route add failed error) Reason : Invalid parameter after configuring lpm-profile. PR1365034

  • ACX5448: LIBCOS_COS_TVP_FC_INFO_NOT_FOUND: Forwarding-class information not specified" prints while committing on configuration prompt. PR1376665

  • On ACX5448, channelized ET interface of 25-Gigabit interface will not come up after chassis-control restart. PR1379288

  • ACX 5448:100 Gigabit link FEC enabled by default on 100G LR4. PR1389518

  • On ACX Series platforms, the forwarding-option dhcp-relay forward-only command stops working and the DHCP packets are dropped. PR1392261

  • On ACX5048, RPM RFC 2544 benchmarking test failed to start. PR1395730

  • CFM adjacency is not going down with distinct intervals. PR1397883

  • Dynamic tunnels are not supported on ACX Series routers. PR1398729

  • VLAN tagged traffic arriving on VPLS interface might get dropped. PR1402626

  • ot/et interface is not created when invalid speed is configured. PR1403546

  • ACX 5448: TrTCM Policer configuration parameters are as per RFC4115. PR1405798

  • The show services inline stateful-firewall flow or show services inline stateful-firewall flow extensive command might cause a memory leak. PR1408982

  • ACX Series routers drop DNS responses that contain an underscore. PR1410062

  • VPLS traffic might stop across ACX5000 with the aggregated Ethernet interface. PR1412042

  • Junos PCC might reject PCUpdate/PCCreate message if there is metric type other than type 2. PR1412659

  • Number of inet-arp policers implemented on ACX5000 has been increased from 16 to 64. PR1413807

  • Swap memory is not initialized on boot on ACX5048. PR1415898

  • Commit error while configuring firewall with term having log/syslog and accept actions. PR1417377

  • CoS table error can sometimes cause traffic outages and SNMP timeouts if the optic is plugged out and inserted back. PR1418696

  • Slow copy image speed to ACX5448. PR1422544

Documentation Updates

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

Installation and Upgrade Guide

  • Veriexec explained (ACX Series)—Verified Exec (also known as veriexec) is a file-signing and verification scheme that protects the Junos operating system (OS) against unauthorized software and activity that might compromise the integrity of your device. Originally developed for the NetBSD OS, veriexec was adapted for Junos OS and enabled by default from Junos OS Release 7.5 onwards.

    [See Veriexec Overview.]

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.

Release History Table
Release
Description
18.3R1
Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support JTI.