Table of Contents
Advertisement
Operational Commands
A user who logs in with the account name user or another account with normal privileges will
see the following top-level prompt:
gateway:> (or the previously configured gateway name)
CLI operational commands are structured in levels. At each level a list of sub-context
commands will move to the next lower level, while current-context commands will perform
various functions and then stay at the same level or return to the next higher level. The
operational command tree is shown in
At each level the prompt changes to reflect the path that has been taken from the top to the
current level. (A "#" is always used to terminate the prompt.)
Example: After the "config" option has been selected from the top level, the prompt becomes:
gateway/config#
Sub-context commands can be strung together in a single line.
Example: The following command will move two levels down from the top to the port
configuration option, and display the appropriate prompt as shown:
gateway:> config port
gateway/config/port#
At any level, entering a "?" will display lists of the sub-context and current-context commands
that are valid at that level. Entering help commands will list all the commands and their
descriptions. The top command returns to the top level. The logout or quit command closes
the CLI session. At any level below the top, exit or up moves to the next higher level.
At any level, entering one of the following will display information about a particular
command and the parameters it requires:
help <command-name>, <command-name> help, or <command-name> ?
.Any command can be abbreviated with the minimum number of letters that make it unique at
its level. For example under the "config" level, "card" can be abbreviated as "c", while
"system" and "snmp" must be abbreviated with at least two letters, "sy" and "sn", respectively.
Abbreviations longer than the minimum can also be used; for example "con", "sys" or "snm".
Figure
A-1.
CLI Reference
A-3
Advertisement
Table of Contents
