Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

What’s Changed in Release 22.2R1

General Routing

  • Instance type change is not permitted from default to L3VRF in open configuration (ACX Series and QFX Series)—DEFAULT_INSTANCE is the primary instance that runs when there is no specific instance type configured in the route set routing-options?. Any instance you explicitly configure is translated into set routing-instance r1 routing-options?. The issue appears in translation, when you change instance type DEFAULT_INSTANCE (any instance to DEFAULT_INSTANCE) to L3VRF or L3VRF to DEFAULT_INSTANCE. As a result, such changes are not permitted. Additionally, DEFAULT_INSTANCE can only be named DEFAULT, and DEFAULT is reserved for DEFAULT_INSTANCE, therefore allowing no such changes.

  • DSCP rewrite on EVPN VXLAN NNI ports (QFX5130 and QFX5700)— QFX5130 and QFX5700 platforms support DSCP rewrite on EVPN VXLAN NNI ports with limitations.

    [See Implementing CoS on VXLAN Interfaces (Junos OS Evolved.]

OpenConfig

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

Network Management and Monitoring

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

  • Enhanced system log messages (QFX5130, QFX5200, QFX5220, and QFX5700)— We've added multiple events inside the event tag using the UI_LOGIN_EVENT|UI_LOGOUT_EVENT format, which has an option (|) to separate the events, to generate system log messages.

    Earlier to this release, the event tag used the UI_LOGIN_EVENT UI_LOGOUT_EVENT format and for various combinations of rpc filters was not getting logged.

    [See Overview of System Logging https://www.juniper.net/documentation/us/en/software/junos/network-mgmt/topics/topic-map/system-logging.html#id-overview-of-junos-os-system-log-messages.]

Routing Protocols

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

  • The RPD_OSPF_LDP_SYNC message not logged—On all Junos OS and Junos OS Evolved devices, when LDP session goes down there is a loss of synchronization between LDP and OSPF. After this loss of synchronization, when an interface is in the holddown state for more than 3 minutes, a system log message with a warning level is sent. This message appears in both the messages file and the trace file.

    However, this system log message does not get logged when you have explicitly configured the hold-time for ldp-synchronization at the [edit protocols ospf area area id interface interface name hierarchy level . If the configured ldp-synchronization hold-time is less than 3 minutes, then the syslog is not printed. However, the message is printed after 3 minutes.

User Interface and Configuration

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