What’s Changed in Release 22.2R1

"Switchover Status Ready" incorrectly describes the status of the backup Routing Engine (RE) after node reboot (PTX10004, PTX10008, PTX10016)— During preparation for switchover between master RE and backup RE running Junos OS Evolved releases prior to 22.2R1, "Switchover Status Ready" from the show system switchover command on the backup RE node, after system reboot, incorrectly describes the status of the backup RE.

The incorrect status description results from a discrepancy between the master RE and the backup RE both using local uptime to determine if sufficient time had elapsed before declaring "Switchover Status Ready".

Use the request chassis routing-engine master switch command on the master RE and the backup RE to obtain the correct status when preparing for switchover.

[See show system switchover and request chassis routing-engine master.]

JNP10K-PWR-DC2 power supplies installed in PTX10008 and PTX10016 routers display as online when the power supplies are switched off— JNP10K-PWR-DC2 power supplies installed in PTX10008 and PTX10016 routers in which Junos OS Release 21.4R1 or Junos OS Evolved Release 21.4R1 is installed display as online in the output of the command show chassis environment psm when the input power feeds are connected, but the power switch on the power supplies are switched off.

OpenConfig container names for Point-to-Multipoint per interface ingress and egress sensors are modified for consistency from "signalling" to "signaling".

Changes to the NETCONF <edit-config> RPC response (ACX Series, PTX Series, and QFX Series)—When the <edit-config> operation returns an error, the NETCONF server does not emit a <load-error-count> element in the RPC response. In earlier releases, the <edit-config> RPC response includes the <load-error-count> element when the operation fails.

SSH TCP forwarding disabled by default—We've disabled the SSH TCP forwarding feature by default to enhance security. To enable the SSH TCP forwarding feature, you can configure the allow-tcp-forwarding statement at the [edit system services ssh] hierarchy level.

In addition, we've deprecated the tcp-forwarding and no-tcp-forwarding statements at the [edit system services ssh] hierarchy level.

When you configure max-cli-sessions at the edit system hierarchy level, it restricts the maximum number of cli sessions that can coexist at any time. Once the max-cli-sessions number is reached, new CLI access is denied. The users who are configured to get the CLI upon login, are also denied new login.