The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides an overview of how to access the command-line interface (CLI), the different command modes, and the commands that are available in each mode.
You can configure and monitor the through the web interface. You can also use the CLI to perform the configuration and monitoring tasks described in this guide.
You can access the CLI through a secure shell (SSH) client or the console port using one of the following machines:
Two different types of accounts are available on the CLI:
When you power on the appliance for the first time, you are prompted to run the setup utility to configure the appliances. During this setup process, an administrator user account, also known as an Admin account, is created. After you enter the initial configuration information, the appliance automatically reboots and prompts you to enter the username and the password that you specified for the Admin account. You must use this Admin account to log in to the CLI for the first time.
An Admin can create and manage Operator (user) accounts (which have limited privileges and access to the server). An Admin account also provides the functionality that is needed to use the CLI.
To create more users (with admin and operator privileges) with SSH access to the CLI, you must enter the username command in configuration mode (see Command Modes in the CLI, page 1-4).
Table 1-1 lists the command privileges for each type of user account: Admin and Operator (user).
|
banner |
* |
|
|
lms |
* |
|
|
ocsp |
* |
|
|
rsakey |
* |
|
|
shell |
* |
|
show icmp_status |
||
Logging in to the server places you in operator (user) mode or admin (EXEC) mode, which always requires a username and password for authentication.
You can tell which mode you are in by looking at the prompt. A right angle bracket (>) appears at the end of operator (user) mode prompt; a pound sign (#) appears at the end of admin mode prompt, regardless of the submode.
EXEC commands primarily include system-level commands such as show and reload (for example, application installation, application start and stop, copy files and installations, restore backups, and display information).
For detailed information on EXEC commands, see Understanding Command Modes, page 2-5.
Table 1-2 describes EXEC mode commands.
The show commands are used to display the settings and are among the most useful commands. See Table 1-3 for a summary of the show commands. The show commands must be followed by a keyword; for example, show application status. Some show commands require an argument or variable after the keyword to function; for example, show application version.
Configuration commands include interface and repository. To access configuration mode, run the configure command in EXEC mode.
Some of the configuration commands require that you enter the configuration submode to complete the configuration.
Table 1-4 describes the configuration commands.
For detailed information on configuration mode and submode commands, see Understanding Command Modes, page 2-5.
You must have administrator access to execute the configuration commands. Whenever an administrator logs in to configuration mode and executes a command that causes configurational changes in the server, the information related to those changes is logged in the operational logs.
Table 1-5 describes configuration mode commands that generate operational logs.
Allows synchronization of the software clock by the NTP server for the system. |
In addition to configuration mode commands, some commands in EXEC mode generate operational logs.
Table 1-6 describes EXEC mode commands that generate operational logs.
Restores from backup the file contents of a specific repository. |
|
Feedback