Table of Contents
Advertisement
Chapter 3 Operation Using CLI
Usage Guidelines
CLI commands, unlike login passwords, are insensitive to case. For example, the
keywords Set, set, and SET all have the same meaning in CLI.
If a particular action requires modeoptions that are not included in the
command, an error message will be issued.
In general, CLI commands issued from a network monitoring system should
have the non-modal "single-line" form shown above. Exceptions may be made
where they will improve efficiency.
Mode changes can be used to restrict the scope of most CLI commands. When
the command mode changes, the prompt changes to reflect the new mode.
End of Line
The CLI syntax is command-line oriented. Accordingly, the eol delimiter (shown as
\n in the grammar) is functionally equivalent to Carriage Return or Enter; that is, it
terminates the command. The eol delimiter cannot be used to split a single command
across two or more lines.
Shown below, for example, is a legal form of a set command within module mode as
a craft operator might enter it:
20/11 Module> set control enable 1 eol
However, the following form of the same command is not legal:
20/11 Module> set control eol (continue the command on the next line)
20/11 Module> enable 1 eol
Wildcards
Some CLI command parameters can include one or more wildcard characters (*) to
give added flexibility.
The following sample dialog shows how a craft operator could use a wildcard to
check the output power on all modules in chassis 20:
CLI> module chassis 20 slot * <Enter>
20/* MODULE> show monitor outpwr <Enter>
MODID
20/05
20/07
20/13
SUCCESS!
20/* MODULE>
34
NAME
VALUE
UNITS
OutPwr
-5.33429
dBm
OutPwr
10.086
dBm
OutPwr
-6.15736
dBm
78-4025693-01 Rev D
Advertisement
Table of Contents
Troubleshooting
