Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Evolved Release Notes for ACX6160 Universal Metro Routers

 

These release notes accompany Junos OS Evolved Release 19.2R2 for ACX6160 optical transponders. The release notes describe new and changed features, limitations, and known and resolved problems in the hardware and software.

What’s New

Learn about the new features and enhancements to existing features in the Junos OS Evolved main release and the maintenance releases for ACX6160 optical transponders.

What’s New in Junos OS Evolved Release 19.2R2

Interfaces and Chassis

  • ACX6160 Universal Metro Router—Starting in Junos OS Evolved Release 19.2R2, the Juniper Networks ACX6160 Universal Metro Router is a standalone optical transponder that supports eight quad small form-factor pluggable transceiver QSFP28 100GbE/OTU4 client interfaces and four 100 Gbps CFP2-DCO line-side interfaces. It has removable DC power supplies and cooling fans. It supports the Open ROADM Multi-Source Agreements (MSA) (Version 2.2.1). The ACX6160 provides full Open ROADM compatible transponder support for metro packet optical transport applications in a 1 U platform.

    Note

    This release supports only four client ports.

    There is no CLI support for the ACX6160. You manage the ACX6160 through its NETCONF API using an Open ROADM compliant controller and the ACX6160 Open ROADM YANG data models.

    As an Open ROADM-compliant device, the configuration and management of the ACX6160 is controlled through the Open ROADM controller. The configuration is stored in the controller server infrastructure and on the device itself.

  • Support for notification replay (ACX6160) —Starting in Junos OS Evolved 19.2R2, the ACX6160 supports notification replay for the NETCONF stream. This allows a client (management station) to request the ACX6160 to send or resend event notifications that have occurred in the past, giving the client the ability to play back a device’s event notification history upon request. This is particularly useful for clients that discover a device for the first time, such as when a new management station assumes control of the device.

What’s New in Junos OS Evolved Release 19.2R1

There are no new or updated features released for ACX6160 optical transponders in Junos OS Evolved Release 19.2R1. The ACX6160 optical transponder was first introduced in Junos OS Evolved Release 19.2R2.

What’s Changed

Learn about what’s different in behavior and syntax in Junos OS Evolved for 19.2R2.

Changes in CLI Statements and Commands

  • To see the list of CLI statements and commands changed in Junos OS Evolved, see How Junos OS Evolved Differs from Junos OS in the Introducing Junos Os Evolved Guide.

General Routing

  • Support for full inheritance paths of configuration groups to be built into the database by default (ACX6160)—Starting with Junos OS Evolved Release 19.2R2, the persist-group-inheritance option at the [edit system commit] hierarchy level is enabled by default. To disable this option, use no-persist-groups-inheritance.

    [See commit (System).]

Junos OS XML API and Scripting

  • XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX6160)—Starting in Junos OS Evolved Release 19.2R2, we have included an XML RPC equivalent for the show bgp output-scheduler | display xml rpc CLI command.

    [See show bgp output-scheduler.]

Known Behavior

Interfaces and Chassis

  • The ACX6160 management interface does not show the correct operational state when it is manually configured 10M half/full duplex, 100M half duplex, or 1000M half/full duplex. The operational state is correctly reported when it is manually configured for 100M full duplex or with auto-neg enabled for any rate. PR1444112

Hardware

  • If an ACX6160 device goes into a Golden BIOS reset loop, you need to power cycle the device to get it back into a operating state. PR 1427141

Open Issues

Platform and Infrastructure

  • The ACX6160 management interface does not show the correct operational state when it is manually configured 10M half/full duplex, 100M half duplex, or 1000M half/full duplex. The operational state is correctly reported when it is manually configured for 100M full duplex or with auto-neg enabled for any rate. PR1444112

  • The Consequent action for trace (TTY) mismatch "tim-act-enable" on OTU-Line needs to be disabled, for PRBS-FAC to work on ODU-Line. PR1448480