About the Classic Device CLI
After you log into a classic device (7000 and 8000 Series, ASA FirePOWER, and NGIPSv) via the CLI (see Logging Into the Command Line Interface on Classic Devices), you can use the commands described in this appendix to view, configure, and troubleshoot your device.
If you reboot a 7000 or 8000 Series device and then log in to the CLI as soon as you are able, any commands you execute are not recorded in the audit log until the web interface is available.
Note that CLI commands are case-insensitive with the exception of parameters whose text is not part of the CLI framework, such as user names and search filters.
Classic Device CLI Modes
The CLI encompasses four modes. The default mode, CLI Management, includes commands for navigating within the CLI itself.
The remaining modes contain commands addressing three different areas of classic device functionality; the commands within
these modes begin with the mode name:
When you enter a mode, the CLI prompt changes to reflect the current mode. For example, to display version information about system components, you can enter the full command at the standard CLI prompt:
> show version
If you have previously entered
show mode, you can enter the command without the
show keyword at the show mode CLI prompt:
Classic Device CLI Access Levels
Within each mode, the commands available to a user depend on the user’s CLI access. When you create a user account, you can assign it one of the following CLI access levels:
Basic — The user has read-only access and cannot run commands that impact system performance.
Configuration — The user has read-write access and can run commands that impact system performance.
None — The user is unable to log in to the shell.
On 7000 and 8000 Series devices, you can assign command line permissions on the User Management page in the local web interface. On NGIPSv and ASA FirePOWER, you assign command line permissions using the CLI.