
Appendix A CLI Reference
Parvus SWI-22-10
Curtiss-Wright
Page 68 of 107
MNL-0641-01 Rev A3
ECO-4823
Effective: 04 Oct 16
H
OW THE
CLI
W
ORKS
The CLI has several different modes, and some commands are restricted to a specific mode.
The top-level mode is called
exec mode
. It allows the user to perform operations related to
configuration files, reloading defaults, displaying system information, etc., but it does not allow the
user to change detailed configuration. Such operations are performed while in
configuration
mode.
In turn, configuration mode has
sub-modes
for configuration of specific items, such as
VLANs or Ethernet interfaces (ports).
The CLI is line-based, i.e., no screen-editing features, and executes commands instantly upon
end-of-line (i.e., pressing Enter).
The CLI is designed to minimize the time required to type commands. Keywords and certain
parameters can be abbreviated (truncated) as long as they are unambiguous. (See "Command
Structure" for details.) For example, these commands are identical:
SWI2210# configure terminal
SWI2210# config term
SWI2210# conf t
The command line may be partially completed by the system, if the system can "guess" what you
need to enter. For example, if you request help on a particular command, the prompt displayed
after the list begins with that command, ready for you to enter the arguments. (GET NEW
EXAMPLE)
SWI2210-XXXX# clear ?
access Access management
access-list Access list
.
.
.
spanning-tree STP Bridge
statistics Clear statistics for one or more given interfaces
SWI2210-XXXX# clear
The system will tell notify you if there's a problem with the command you entered.
SWI2210-XXXX# config
% Incomplete command.
Frequently a caret is displayed under the incorrect entry along with the error message. If the
caret is below the prompt, the problem may be that you aren't in the correct mode to use that
command.
SWI2210-XXXX# show config
^
% Invalid word detected at '^' marker
Multiple sessions can co-exist at the same time, each providing separate environments with
differences in logged-in user ID, privilege level, command history, mode, and session settings. It
is therefore possible for the same user to control several concurrent sessions; for example, one
serial console session and one ssh session.
The user database is either local or provided by a RADIUS or server. In case of a local
user database, passwords and privilege levels are maintained on the device.