Purpose
A common set of operations you can check is when users log in to the router and the CLI commands they issue.
To check the commands that users are entering, follow these steps:
Action
To configure the log file for tracking CLI commands, follow these steps:
For example:
Meaning
The configuration example shows that the log file cli-commands is configured with the interactive-commands facility at the info severity level. Table 45 lists and describes the severity levels.
Table 45: Severity Levels
To display the log file in configuration mode, enter the following command:
For example:
[edit system syslog] user@host# run show log cli-commands Sep 16 11:24:25 nut mgd[3442]: UI_COMMIT_PROGRESS: commit: signaling 'Syslog daemon', pid 2457, signal 1, status 0 Sep 16 11:24:25 nut mgd[3442]: UI_COMMIT_PROGRESS: commit: signaling 'SNMP daemon', pid 2592, signal 31, status 0 Sep 16 11:28:36 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'run show log cli-commands ' Sep 16 11:30:39 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'run show log security ' Sep 16 11:31:26 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'run show log messages ' Sep 16 11:41:21 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'edit file cli-commands ' Sep 16 11:41:25 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'show ' Sep 16 11:44:57 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'set interactive-commands info ' Sep 16 14:32:15 nut mgd[3442]: UI_CMDLINE_READ_LINE: User 'user', command 'run show log cli-commands '
The sample output shows the CLI commands that were entered since the log file was configured.