Previous page Next page

show command-log

Displays a list of commands that have been executed or configured on CNA during the specified period.

Syntax
show command-log [ historic ]
 
                 [ all | exec | config ] 
 
                 [ start-time <begin> ] 
 
                 [ end-time <end> ] 
 
                 [ detail ] 
 
                 [ reverse ]
 
                 [ | { include | exclude | begin } <exp> ] 
 
                 [ > <url> ]
 
Arguments
Prerequisites

System operations mode, login-level access.

Description

The show command-log command displays a list of all commands of the specified type that have been invoked on CNA during the specified time period.

When you execute the command with no type keyword (all, exec or config), the display will include all exec and config commands that the show command-log process can identify by command name.

When you invoke the command with the keyword all, the display will include a listing for every command executed during the specified period, including those that cannot be identified or categorized by the show command-log process.

The keyword historic will show commands prior to the last system boot.

Commands invoked by internal processes, as well as many commands invoked by the web client, are passed to the coreman process as XML tags, which do not use the same command names as the CLI. Those commands cannot be mapped to their CLI names by the show command-log process, and they will be listed as N/A (not available) in the output for both command name and type. Even though you will not be able to identify the command from the listing, you will be able to locate commands that take long periods of time to complete or consume large amounts of memory. By matching the start time with general CNA activity as recorded in log messages, you may be able to deduce the command name.

If you invoke the show command-log command with the exec keyword, the output will be limited to just those commands that the CNA software executes immediately upon entry without adding them to the configuration (such as show commands, for example).

The config keyword will limit the display to just those commands that the CNA software adds to the configuration. Config commands are also executed immediately.

The timestamps entered with the start-time and end-time keywords define the time period to be covered by the show command-log output. You must enter complete time stamps. Unlike the show report command, the show command-log command will not attempt to match a partial time stamp.

If you don’t specify a time range, the list will include all commands that have been issued since the most recent reboot, except that there are limits on the total number of commands that will be kept in the log. These limits, which are displayed at the end of the command output, are: 10,000 config commands entered through the CLI, 2,000 exec commands entered through the CLI, and 1,000 commands invoked by a process other than the CLI.

Output will include the following information about each command that was invoked during the specified time:

The detail keyword causes the display to include more details about each command entry, including the following additional columns:

d--days

h--hours

M--minutes

s--seconds

m--milliseconds

If you have configured an enable password, the enable command will always appear twice in the log for each time the command was executed. The CNA software allows you to enter privileged mode from a console connection without requiring that an enable password be configured. So it must first check to see if a password is required. If it is, the enable command will be rejected the first time and the CLI will prompt the user for a password. Then the enable command will be passed back to the CNA process a second time.

The reverse keyword causes the commands to be listed in reverse order (starting with the earliest command in the log).

You can pipe the command through one of the following filters:

The vertical-line pipe character | is required when a filter is used.

You can send the output to a remote file location, by piping the display to a remote URL (leading > required). See the copy command for URL syntax.


Previous page Next page