Subcommands

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 until you exit the command, or descend an additional level into another subcommand. Subcommand scope is indicated by indentation.

For example, the edit subcommand is only available in commands that affects tables, and the next subcommand is available only in the edit subcommand:

config system interface

edit port1

set status up

next

end

The available subcommands vary by command. From a command prompt under the config command, subcommands that affect tables and fields could be available.

Table subcommands

edit <table_row>

Create or edit a table value.

In objects such as security policies, <table_row> is a sequence number. To create a new table entry without accidentally editing an existing entry, enter edit 0. The CLI will confirm that creation of entry 0, but will assign the next unused number when the entry is saved after entering end or next.

For example, to create a new firewall policy, enter the following commands:

config firewall policy

edit 0

....

next

end

To edit an existing policy, enter the following commands:

config firewall policy

edit 27

....

next

end

The edit subcommand changes the command prompt to the name of the table value that is being edited.

delete <table_row>

Delete a table value.