Subcommands

Once you connect to the CLI, you can enter commands.

Each command line consists of a command word that is usually followed by words for the configuration data or other specific item that the command uses or affects, for example:

get system admin

Subcommands are available from within the scope of some commands.When you enter a subcommand level, the command prompt changes to indicate the name of the current command scope. For example, after entering:

config system admin

the command prompt becomes:

(admin)#

Applicable subcommands are available to you until you exit the scope of the command, or until you descend an additional level into another subcommand.

For example, the edit subcommand is available only within a command that affects tables; the next subcommand is available only from within the edit subcommand:

config system interface

edit port1

set status up

next

end

Available subcommands vary by command.From a command prompt within config, two types of subcommands might become available:

• commands that affect fields (see “Field commands”)

• commands that affect tables (see “Table commands”)


	Subcommand scope is indicated in this CLI Reference by indentation. See “Indentation”. Syntax examples for each top-level command in this CLI Reference do not show all available subcommands. However, when nested scope is demonstrated, you should assume that subcommands applicable for that level of scope are available.