CLI command history

CLI commands executed on the device from any console, Telnet, or SSH sessions are stored in the warm memory.

By default, the history list of commands that are executed without any parse errors is persistent and is available after a user-executed reload or unexpected reload. Apart from the user-executed commands, data such as the username, session details, IP address, and time at which the command is executed are also saved in the memory. A maximum of 1024 commands are stored, beyond which the latest commands overwrite the oldest commands. The command log history can be viewed using the show cli-command-history command. You can clear the allocated logging memory and remove the command history using the clear cli-command-history command.

CLI command history persistence is also supported in a stacking environment. In a stack, only the commands that are executed from an active device are stored in the log and the same commands are sent to the stand-by device. The commands executed by other members of a stack and stand-by devices are not stored.

Note: CLI command history persistence is always enabled and cannot be disabled.
Note: CLI command history persistence is not related to Syslog.

In this section:

  1. CLI command history persistence limitations
  2. Displaying and clearing command log history
    By default, the CLI commands executed on the device are stored in the memory. The command history persistence is always enabled and cannot be disabled. The following steps allows you to view the command log history and clear the allocated logging memory to remove the command history.
Parent topic: Configuration Fundamentals