Command syntax
When entering a command, the command line interface (CLI) requires that you use valid syntax, and conform to expected input constraints. It will reject invalid commands.
Fortinet documentation uses the following conventions to describe valid command syntax.
See also
Terminology
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:
get system admin
To describe the function of each word in the command line, especially if that nature has changed between firmware versions, Fortinet uses terms with the following definitions.
config system interface
edit <port_name>
set status {up | down|
set ip <interface_ipv4mask>
next
end
Command syntax terminology:
- Command — A word that begins the command line and indicates an action that the FortiMail unit should perform on a part of the configuration or host on the network, such as
configorexecute. Together with other words, such as fields or values, that end when you press the Enter key, it forms a command line. Exceptions include multi-line command lines, which can be entered using an escape sequence (See Shortcuts and key commands ).
Valid command lines must be unambiguous if abbreviated (see Command abbreviation ). Optional words or other command line permutations are indicated by syntax notation (See Notation ).
|
This CLI reference is organized alphabetically by object for the |
- Object — A part of the configuration that contains tables and/or fields. Valid command lines must be specific enough to indicate an individual object.
- Subcommand — A kind of command that is available only when nested within the scope of another command. After entering a command, its applicable sub-commands are available to you until you exit the scope of the command, or until you descend an additional level into another sub-command. Indentation is used to indicate levels of nested commands (See Indentation ).
Not all top-level commands have sub-commands. Available sub-commands vary by their containing scope (See Sub-commands ).
- Table — A set of fields that is one of possibly multiple similar sets which each have a name or number, such as an administrator account, policy, or network interface. These named or numbered sets are sometimes referenced by other parts of the configuration that use them (See Notation ).
- Option — A kind of value that must be one or more words from of a fixed set of options (See Notation ).
- Field — The name of a setting, such as
iporhostname. Fields in some tables must be configured with values. Failure to configure a required field will result in an invalid object configuration error message, and the FortiMail unit will discard the invalid table. - Value — A number, letter, IP address, or other type of input that is usually your configuration setting held by a field. Some commands, however, require multiple input values which may not be named but are simply entered in sequential order in the same command line. Valid input types are indicated by constraint notation (See Notation ).
Indentation
Indentation indicates levels of nested commands, which indicate what other sub-commands are available from within the scope.
For example, the edit sub-command is available only within a command that affects tables, and the next sub-command is available only from within the edit sub-command:
config system interface
edit port1
set status up
next
end
For information about available sub-commands, see Sub-commands.
See also
Notation
Brackets, braces, and pipes are used to denote valid permutations of the syntax. Constraint notations, such as <address_ipv4>, indicate which data types or string patterns are acceptable value input.
Command syntax notation:
|
Convention |
Description |
|
|---|---|---|
|
Square brackets |
A non-required word or series of words. For example: [verbose {1 | 2 | 3}] indicates that you may either omit or type both the verbose 3 |
|
|
Angle brackets |
A word constrained by data type. To define acceptable input, the angled brackets contain a descriptive name followed by an underscore ( <retries_int> indicates that you must enter a number of retries, such as Data types include:
|
|
|
Curly braces |
A word or series of words that is constrained to a set of options delimited by either vertical bars or spaces. You must enter at least one of the options, unless the set of options is surrounded by square brackets [ ]. |
|
|
|
Options delimited by vertical bars |
Mutually exclusive options. For example: {enable | disable} indicates that you must enter either |
|
Options delimited by spaces |
Non-mutually exclusive options. For example: {http https ping snmp ssh telnet} indicates that you may enter all or a subset of those options, in any order, in a space-delimited list, such as: ping https ssh Note: To change the options, you must re-type the entire list. For example, to add ping https snmp ssh If the option adds to or subtracts from the existing list of options, instead of replacing it, or if the list is comma-delimited, the exception will be noted. |
|
See also