Command syntax
When entering a command, the CLI console requires that you use valid syntax and conform to expected input constraints. It rejects invalid commands. Indentation is used to indicate the levels of nested commands.
Each command line consists of a command word, usually followed by configuration data or a specific item that the command uses or affects.
Notation
Brackets, vertical bars, and spaces are used to denote valid syntax. Constraint notations, such as <address_ipv4>, indicate which data types or string patterns are acceptable value input.
All syntax uses the following conventions:
|
Angle brackets < > |
Indicate a variable of the specified data type. |
|
Curly brackets { } |
Indicate that a variable or variables are mandatory. |
|
Square brackets [ ] |
Indicate that the variable or variables are optional. For example: show system interface [<name_str>] To show the settings for all interfaces, you can enter To show the settings for the Port1 interface, you can enter |
|
Vertical bar | |
A vertical bar separates alternative, mutually exclusive options. For example: set protocol {ftp | sftp} You can enter either |
|
Space |
A space separates non-mutually exclusive options. For example: set allowaccess {ping https ssh snmp http fgfm radius-acct probe-response capwap ftm} You can enter any of the following: set allowaccess ping set allowaccess https ping ssh set allowaccess http https snmp ssh ping In most cases, to make changes to lists that contain options separated by spaces, you need to retype the entire list, including all the options that you want to apply and excluding all the options that you want to remove. |
Optional values and ranges
Any field that is optional will use square-brackets. The overall config command will still be valid whether or not the option is configured.
Square-brackets can be used is to show that multiple options can be set, even intermixed with ranges. The following example shows a field that can be set to either a specific value or range, or multiple instances:
config firewall service custom
set iprange <range1> [<range2> <range3> ...]
end
next
The next command is used to maintain a hierarchy and flow to CLI commands. It is at the same indentation level as the preceding edit command, to mark where a table entry finishes.
The following example shows the next command used in the subcommand entries:
After configuring table entry <2> then entering next, the <2> table entry is saved and the console returns to the entries prompt:
You can now create more table entries as needed, or enter end to save the table and return to the filepattern table element prompt.
end
The end command is used to maintain a hierarchy and flow to CLI commands.
The following example shows the same command and subcommand as the next command example, except end has been entered instead of next after the subcommand:
Entering end will save the <2> table entry and the table, and exit the entries subcommand entirely. The console returns to the filepattern table element prompt:
