Modifying the idle timeout value for CLI sessions

A single idle timeout applies to all CLI engines in a CLI session (classic and MD-CLI). The idle timeout can be modified to a value between 1 and 1440 minutes.

The following points apply:

The idle timeout only affects new CLI sessions. Existing and current sessions retain the previous idle timeout.
The idle timeout can be disabled by setting the value to none.
The "Idle time" column in the show users display is reset after an action in either CLI engine.

Example

A warning message is displayed when a session reaches one-half the value of the idle timeout, and another message is displayed when the idle timeout expires and the user is logged out.

[/]
A:admin@node-2# show users
===============================================================================
User                             Type      Login time           Idle time
  Session ID   (Router instance)
               From
===============================================================================
                                 Console         --             0d 21:44:02 --
  6            (--)
               --
admin                            SSHv2     16FEB2021 20:42:15   0d 00:00:04 --
  12           (management)
               192.168.144.97
admin                            SSHv2     16FEB2021 19:49:45   0d 00:00:00 --
 #11           (management)
               192.168.144.97
-------------------------------------------------------------------------------
Number of users: 2
'#' indicates the current active session
===============================================================================

Idle timeout interaction with the classic CLI

The idle timeout configured in the classic CLI affects all new sessions as well as the current session. However, the current session is only affected if the classic CLI engine is active when the idle timeout expires. Configuration changes via the MD-CLI or any other interface only affect new sessions that begin after the change.