Junos OS Release Notes for ACX Series

What's New

• What's New in Release 20.3R3

• What's New in Release 20.3R2

• What's New in Release 20.3R1

What's New in Release 20.3R3

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

What's New in Release 20.3R2

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

What's New in Release 20.3R1

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	Support for logs, alarms, counters, and SNMP traps for Precision Time Protocol (PTP)/ Synchronous Ethernet. [See Enterprise-Specific SNMP Traps Supported by Junos OS and show chassis alarms.] Support for the g.8275.1 profile on the ACX710. [See Assisted Partial Timing Support.] Support for PTP G.8275.1. Use PTP profile-type g.8275.1 to enable the G.8275.1 profile. [See Profile Type.] Support for limited images on the ACX710. [See Software Installation and Upgrade Overview.] Support for RIP version 1, RIP version 2, and RIP next generation (RIPng) on PTX10008 routers. [See RIP and RIPng Overview.]

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

• What’s Changed in Release 20.3R3

• What’s Changed in Release 20.3R2

• What’s Changed in Release 20.3R1

What’s Changed in Release 20.3R3

Junos OS XML API and Scripting

• Refreshing scripts from an HTTPS server requires a certificate (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When you refresh a local commit, event, op, SNMP, or Juniper Extension Toolkit (JET) script from an HTTPS server, you must specify the certificate (Root CA or self-signed) that the device uses to validate the server's certificate, thus ensuring that the server is authentic. In earlier releases, when you refresh scripts from an HTTPS server, the device does not perform certificate validation.

  When you refresh a script using the request system scripts refresh-from operational mode command, include the cert-file option and specify the certificate path. Before you refresh a script using the set refresh or set refresh-from configuration mode command, first configure the cert-file statement under the hierarchy level where you configure the script. The certificate must be in Privacy-Enhanced Mail (PEM) format.

  [See request system scripts refresh-from and cert-file.]

What’s Changed in Release 20.3R2

Junos XML API and Scripting

• The jcs:invoke() function supports suppressing root login and logout events in system log files for SLAX commit scripts (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—The jcs:invoke() extension function supports the no-login-logout parameter in SLAX commit scripts. If you include the parameter, the function does not generate and log UI_LOGIN_EVENT and UI_LOGOUT_EVENT messages when the script logs in as root to execute the specified RPC. If you omit the parameter, the function behaves as in earlier releases in which the root UI_LOGIN_EVENT and UI_LOGOUT_EVENT messages are logged in system log files.

  [See invoke() Function (SLAX and XSLT).]

• The jcs:invoke() function supports suppression of root login and logout events in system log files for SLAX event scripts (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—The jcs:invoke() extension function supports the no-login-logout parameter in SLAX event scripts. If you include the parameter, the function does not generate and log UI_LOGIN_EVENT and UI_LOGOUT_EVENT messages when the script logs in as root to execute the specified remote procedure call (RPC). If you omit the parameter, the function behaves as in earlier releases in which the root UI_LOGIN_EVENT and UI_LOGOUT_EVENT messages are included in system log files.

  [See invoke() Function (SLAX and XSLT)..]

MPLS

• The show mpls lsp extensivel and show mpls lsp detail commands display next-hop gateway LSPid—When you use the show mpls lsp extensivel and show mpls lsp detail commands, you'll see next-hop gateway LSPid in the output.

User Interface and Configuration

• Verbose format option to export JSON configuration data (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—The Junos OS CLI exposes the verbose statement at the edit system export-format json hierarchy level. The default format to export configuration data in JSON changed from verbose format to ietf format starting in Junos OS Release 16.1R1. You can explicitly specify the default export format for JSON configuration data by configuring the appropriate statement at the edit system export-format json hierarchy level. Although the verbose statement is exposed in the Junos OS CLI as of the current release, you can configure this statement starting in Junos OS Release 16.1R1.

  [See export-format.]

What’s Changed in Release 20.3R1

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

• General Routing

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

• EVPN-VPWS, L3VPN and L2VPN FRR convergence time with aggregated Ethernet as the Active core interface is not meeting <50ms and may be 100ms to 150ms. PR1492730

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

• On ACX710, the PTP clock recovery is re-started when the clksyncd process is re-started. This will result in the PTP lock state moving to freerun on the clksyncd process restart. PR1502162

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

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

• Do not foresee any impact on customer use cases with current implementation. The explicit VLAN configuration knob available in PTP helps to cover the possible use cases related to VLAN mapping. Will be checking with Broadcom, if any alternate and better solution exists. If yes, then it will be considered for implementation in future release. PR1507809

• Unexpected delay counter values are seen in the output of the show ptp statistics detail command when the upstream primary 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 primary 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

• Whenever PTP configuration is deleted, syncE goes into HOLDOVER state and comes back to locked. PR1546681

• In ACX5448 device, the ping shall fail if the MAC address of the device is modified to a static MAC address as BCM supports only one base MAC address. PR1553472

• When ACX5448 or ACX710 is configured as Two-Way Active Measurement Protocol (TWAMP) server and a client sends a start session message, the response from ACX to send start session ack is delayed by 10 seconds which might cause the session to fail. PR1556829

Open Issues

• General Routing

• Interfaces and Chassis

• Network Management and Monitoring

• Virtual Chassis

General Routing

• The inet6-precendence under set class of service rewrite-rules is not supported on ACX5448. PR1344340

• 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

• On ACX6360 routers, enhancement is needed for FRR BER threshold SNMP support. PR1383303

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

• The ccc logs are not compressed after rotation. PR1398511

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

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

• Protocols get forwarded when using a nonexisting SSM map source address in IGMPv3 instead of pruning. PR1435648

• Memory leaks are expected in this release. PR1438358

• Drop profile, maximum threshold may not be reached when the packet size is other than 1000 bytes.PR1448418

• The CFM remote MEP is not coming up after configuration or remains in start state. PR1460555

• Multiple RMEP's are unsupported due to which remote defect indication is seen.PR1478346

• On ACX710 routers, packet drop is observed after changing ALT port cost for RSTP. PR1482566

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

• On ACX6360 routers, the port mirror will not work when the port-mirroring is configured with the firewall filter. PR1491789

• If we configure DHCP option 012 host-name in DHCP server configuration and the actual base configuration file also has the host-name in it, then overwriting of the base configuration file's host-name with the DHCP option 012 host-name is happening. PR1503958

• On ACX710 routers, when the following steps are done for PTP, chassis does not lock: 1. Use one or two ports as source for chassis synchronization and lock both PTP and SyncE locked. 2. Disable both logical interfaces. 3. Restart clksyncd. 4. Rollback 1. As a workaround, you can avoid this issue by deleting the PTP configuration, restarting clksyncd, and then reconfiguring PTP. PR1505405

• Experimental (exp) remarking is supported only for single MPLS label packet. PR1509627

• Experimental (exp) remarking is supported only for single MPLS label packet. PR1509635

• For ACX710, if the console cable is plugged in and the terminal connection is active and sending characters to the interface, the system boot may be interrupted and the ACX710 boot will be stalled at the uboot# prompt. PR1513553

• On ACX710 routers, when working in holdover mode after locking to GNSS, will rely on the local oscillator for holdover. The clock class will hence be for stratum 3/e clock. The APTS mode of operation of holding over by using synce is not supported. PR1525918

• On the ACX710 router, T1 or T4 cTE should be tuned closer to two-way CTE. PR1527347

• Microsemi servo doesn't lose lock immediately on loss of one way delay data. Depending on the quality of time delay data available, the lock state can continue. PR1528973

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

• Making CoS related changes when traffic is flowing such as deactivate/activate, chassis control restart could lead to not working CoS configuration as expected. It is advisable to stop traffic and then change.PR1538934

• The issue is only seen when chassisd debug trace is enabled. PR1539366

• Though enhanced-ip is active, observed alarm RE0 network-service mode mismatch between configuration and kernel setting during ISSU. PR1546002

• For ISIS and STATIC routes, ARP resolution of next hop is needed for BFD to start. Workaround is to ping or have any traffic towards the next hop. PR1561590

• As per the current code, ACX would not delete a mac address from the mac table, there is - (a) traffic destined to the mac address or (b) traffic sourced from the mac address or (c) both Fix of this PR will allow ACX to only look at (b) traffic sourced from mac address before deleting the mac address entry from mac table. So, if there is no traffic sourced from the mac for an interval of mac aging timer, the mac would be deleted from the mac table at the end of mac aging timer with out taking into account the traffic destined to the mac address.. PR1565642

• The Precision Time Protocol (PTP) clock might fail to be locking and stuck in acquiring state at clock servo. PR1570310

• On ACX710, if drop-profiles is configured for scheduler-map which is then applied to interfaces, the FPC might crash hence there is traffic loss. PR1588860

Interfaces and Chassis

• The mc-ae option need to have prefer-status-control-active set to avoid flap on the split brain case ( ICCP down or peer node reboot). Configure it on the status-control active PE device. PR1505841

Network Management and Monitoring

• On all Junos platforms, the SNMP polling might not be working if the IS-IS protocol is disabled under the same VRF (Virtual Routing and Forwarding) through which SNMP requests are sent. PR1527251

Virtual Chassis

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

Resolved Issues

• Resolved Issues: 20.3R3

• Resolved Issues: 20.3R2

• Resolved Issues: 20.3R1

Resolved Issues: 20.3R3

General Routing

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

• Packets dropped might be seen after configuring PTP transparent clock. PR1530862

• The ACX710 jnpr-clock-recovery.log exhausts storage and affects swap memory operation. PR1542018

• On the ACX710 platforms, traffic received under a VRF might be discarded if it is resolved by the default route under the VRF for forwarding.PR1551063

• Verifying multiple PD synchronizations with relay deletes and adds configurations. PR1554647

• On the ACX5448 routers, single-rate-three-color policer does not work. PR1559665

• On ACX5048 router, the fxpc process generates core file on the analyzer configuration. PR1559690

• On ACX platforms, ODIN NPI - MC-LAG:- When LACP daemon is restarted LACP local partner system id remains 0 in mc-ae output. PR1560820

• Inline BFD stays down with ISIS and Static clients. PR1561590

• On ACX5448 router, the syslog message ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_dyn_entry_counter_get : Entry is invalid is reported every 30 seconds. PR1562323

• Analyzer (Port Mirroring) might not work on ports above 20. PR1563774

• On ACX710 and ACX5448 platforms, loopback0 firewall might not take effect along with error logs. PR1566417

• LLDP does not work on the management interface of ACX5448, ACX5448-D, and ACX5448-M routers. PR1566454

• On ACX710, the log file of the lcklsyncd process shows empty. PR1567687

• The DF (Designated Forwarder) might not forward traffic. PR1567752

• ACX resets tunable optics to default wavelength after upgrade or reboot. PR1570192

• On the ACX5448 routers, the untagged traffic is being incorrectly queued and marked. PR1570899

• On the ACX710, PEM Feed snmp trap support. PR1571368

• On ACX5448, RFC2544 reflector feature could not work on a higher port. PR1571975

• The Layer 2 circuit and CFM sessions might go down with asynchronous-notification configured. PR1572722

• ARP traffic exceeding the policer limit is not discarded on ACX platforms. PR1573956

• Packets might get tagged with the default VLAN-ID and dropped at the peer under Layer 2 circuits local switching scenario. PR1574623

• ACX as a LSR router fails to process RSVP Path Message. PR1576585

• On the ACX710 routers, continuous reboot due to configuration under auxiliary ports observed. PR1580016

• There might be a traffic drop between customer edge and provider edge devices in case of ARP resolution failure. PR1580782

• The process rpd might get stuck in 100% due to race condition. PR1582226

• ACX710 log jnpr-clock-recovery.log file size too small and archives rotate too quick. PR1582350

• On the ACX710, unexpected results observed while verifying channelised interface check with snmp mib get ifHighSpeed output. PR1583995

• The IPv4 traffic loss with packet size more than 1410 on ACX5448. PR1584509

• On the ACX5448, ACX_ASIC_PROGRAMMING_ERROR detection time shows the default value (6.000) instead of the configured value for single hop BFD. PR1585382

• Traffic not passing through CCC interface when vlan-id-range is configured. PR1590969

Class of Service (CoS)

• FPC crash might be observed after the show class-of-service command. PR1568661

Infrastructure

• The vme/me0 management interface cannot process any incoming packets. PR1552952

Platform and Infrastructure

• In Junos OS, upon receipt of specific sequences of genuine packets destined to the device the kernel will crash and restart (vmcore) (CVE-2021-0283, CVE-2021-0284). PR1557881

Resolved Issues: 20.3R2

General Routing

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

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

• EXP rewrite might cause incorrect EXP marking of traffic on ACX5448 and ACX710 routers. PR1500928

• ACX1100, ACX2100, ACX2200, ACX2000, and ACX4000 routers might stop forwarding transit and control traffic. PR1508534

• Transit DHCP packets drop is seen on ACX5448 routers PR1517420

• Tagged traffic matching the vlan-id-list under vlan-ccc configuration might get dropped in the ingress interface. PR1519568

• On the ACX500-I router, the show services session count does not work as expected. PR1520305

• Interface does not come up with the auto-negotiation setting between the ACX1100 router and the other ACX Series routers, MX Series routers, and QFX Series switches as the other end. PR1523418

• [Cos] [Hqos] ACX-710 :: Hqos= PIR/CIR Hqos behavior is inconsistent. PR1525789

• The aggregated Ethernet interface might not come up with Link Fault Management configured after reboot PR1526283

• On the ACX5448 router with 1000 CFM, the CCM state does not go in the Ok state after loading the configuration or restarting the Packet Forwarding Engine. PR1526626

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

• VPLS traffic loss might be observed on the ACX5448 or ACX710 routers PR1527231

• The l2cpd memory leak could be observed with aggregated Ethernet interface flap. PR1527853

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

• Packets dropped might be seen after configuring PTP transparent clock. PR1530862

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

• Memory leak in Local OutLif in VPLS/CCC topology might be observed. PR1532995

• The clksyncd process generates core file. PR1537107

• 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

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

• On the ACX5448 router, unexpected behavior of the show chassis network-services command is observed. PR1538869

• The following 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: Err] clksync_mimic_delete_clock_entry Unexpected error. PR1539953

• The announcement or synchronization interval rate range is not as expected. PR1542516

• The ACX5448 router as transit for the BGP labeled unicast drops traffic. PR1547713

• The ARP packets from the CE device are added with VLAN tag if the VLAN-ID is configured in the EVPN routing instance. PR1555679

• On ACX5448 router, you cannot downgrade to Junos OS Release 18.4 code base. PR1556377

• On ACX5448 router, the unicast packets from the CE devices might be forwarded by the PE devices with additional VLAN tag if IRB is used. PR1559084

• On ACX5048 router, the fxpc process generates core file on the analyzer configuration. PR1559690

• On ACX5448 router, the syslog message ACX_DFW_CFG_FAILED: ACX Error (dfw):dnx_dfw_dyn_entry_counter_get : Entry is invalid is reported every 30 seconds.PR1562323

Class of Service

• The explicit classifier or rewrite-rule might not work as expected for a logical interface if the wildcard configuration is also applied. PR1556103

Forwarding and Sampling

• VLAN ID-based firewall match conditions might not work for the VPLS service. PR1542092

Layer 2 Features

• On ACX5448, VPLS traffic statistics information is not displayed when executing the show vpls statistics command. PR1506981

Resolved Issues: 20.3R1

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 primary 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 Drop Eligibility Indicator 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 Link Aggregation Control Protocol 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

Migration, Upgrade, and Downgrade Instructions

• Upgrade and Downgrade Support Policy for Junos OS Releases

Upgrade and Downgrade Support Policy for Junos OS Releases

We have two types of releases, EOL and EEOL:

• End of Life (EOL) releases have engineering support for twenty four months after the first general availability date and customer support for an additional six more months.

• • Extended End of Life (EEOL) releases have engineering support for thirty six months after the first general availability date and customer support for an additional six more months.

For both EOL and EEOL releases, you can upgrade to the next three subsequent releases or downgrade to the previous three releases. For example, you can upgrade from 19.2 to the next three releases – 19.3, 19.4 and 20.1 or downgrade to the previous three releases – 19.1, 18.4 and 18.3.

For EEOL releases only, you have an additional option - you can upgrade directly from one EEOL release to the next two subsequent EEOL releases, even if the target release is beyond the next three releases. Likewise, you can downgrade directly from one EEOL release to the previous two EEOL releases, even if the target release is beyond the previous three releases. For example, 19.2 is an EEOL release. Hence, you can upgrade from 19.2 to the next two EEOL releases – 19.3 and 19.4 or downgrade to the previous two EEOL releases – 19.1 and 18.4.4.

For more information about EOL and EEOL releases, see https://www.juniper.net/support/eol/junos.html.

For information about software installation and upgrade, see the Installation and Upgrade Guide.