What’s Changed in Release 21.1R1

SSH session connection limit and rate limit per connection (PTX Series)—We have introduced the connection-limit and rate-limit options at the set system services ssh hierarchy levels. The default connection limit value is 75 connections, and the default rate limit value is 3 connections per second. Junos OS measures the rate limit value per minute but Junos OS Evolved measures the rate limit value per second.

Secure boot disabled alarm is raised (PTX10008)—The Secure boot disabled alarm is raised when the system boots with secure boot disabled in bios.

Fault alarm generated for feed failure on a DC power supply (PTX10008)— A fault alarm is generated when only one of the feeds on a DC power supply (A0 and B0 or A1 and B1) is faulty.

Deprecated command show system buffers—This command is not applicable in Junos OS Evolved because the command displays the status of kernel mbufs, which are not used in Linux-based systems like Junos OS Evolved. In releases before it was deprecated, the show system buffers command returns NULL.

Warning message when taking an FPC offline—PTX10003-80C and PTX10003-160C devices do not support the request chassis fpc slot slot-number online command. The only way to bring up an FPC (MPC) that is offline is by rebooting the chassis. So, when you take an FPC offline by using the request chassis fpc slot slot-number offline command, the screen displays the following message: 'Warning : FPC <slot> cannot be made online using a CLI command. You need to perform router reboot using "request system reboot" to online the FPC <slot>. Do you wish to continue ? [yes,no] (no).'

[See request chassis fpc.]

Python 3 add-on modules (PTX Series)—Junos OS Evolved includes additional Python 3 libraries and modules, which Python scripts can import and use.

[See Overview of Python Modules on Devices Running Junos OS.]

The jcs:invoke() function supports suppression of root login and logout events in system log files for SLAX event scripts (ACX Series, PTX Series, and QFX 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).]

The jcs:invoke() function supports suppression of root login and logout events in system log files for SLAX commit scripts (ACX Series, PTX Series, and QFX 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 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).]

Modification to sync-reset command (ACX Series, PTX Series, and QFX Series)—Starting from this release, the sync-reset command is disabled by default on all the Junos OS Evolved platforms. The Sync-reset command enables the device to send the sync bit in the LACP packets on minimum-link failure. Previously the sync-reset command was enabled by default on QFX Series, while it was by default disabled on PTX Series and ACX series.

[See sync-reset.]

New commit check for MC-LAG (PTX Series, QFX Series)—We've introduced a new commit check to check the values assigned to the redundancy group identification number on the MC-AE interface ( redundancy-group-id) and ICCP peer (redundancy-group-id-list) when you configure multichassis aggregation groups (MC-LAGs). If the values are different, the system reports a commit check error. In previous releases, if the configured values were different, the l2ald process would crash.

[See iccp and mc-ae.]

Support for specifying the YANG modules to advertise in the NETCONF capabilities and supported schema list (ACX Series, PTX Series, and QFX Series)—You can configure devices to emit third-party, standard, and Junos OS native YANG modules in the capabilities exchange of a NETCONF session by configuring the appropriate statements at the [edit system services netconf hello-message yang-module-capabilities] hierarchy level. In addition, you can specify the YANG schemas that the NETCONF server should include in its list of supported schemas by configuring the appropriate statements at the [edit system services netconf netconf-monitoring netconf-state-schemas] hierarchy level.

[See hello-message and netconf-monitoring.]

The write-file option at the monitor traffic interface hierarchy level takes precedence—The write-file option at the monitor traffic interface hierarchy level takes precedence over the extensive option when you configure them simultaneously. If you try to configure these options at the same time, Junos OS Evolved gives you a warning message that the options are not compatible, and it only runs the monitor traffic interface write-file command.

[See monitor traffic.]

[See Error Handling by Fabric OAM.]

Recommendation to include the local-address statement when configuring IBGP and multihop EBGP—When a device peers with a remote device's loopback interface address, use the local-address statement at the [edit protocols bgp group internal-peers] hierarchy to specify the source information in BGP update messages. Although a BGP session can be established when only one of the paired routing devices has local-address configured, we strongly recommend that you configure local-address on both paired routing devices for IBGP and multihop EBGP sessions. The local-address statement ensures that deterministic fixed addresses are used for the BGP session end-points.

[See local-address (Protocols BGP) and BGP Peering Sessions.]

Support for exclude option under file archive (ACX Series, PTX Series, and QFX Series)—The exclude option is added under the command file archive that specifies the file pattern to exclude. This option helps to exclude files that delay compression or files that do not require compression.

[See file archive.]

[See export-format.]