
Command Syntax
4025561 Rev
15
01/06 MODULE>
In the first line of this example, the operator selects the Module command mode.
In the next line, the prompt has changed to reflect the new command mode. The
operator then selects chassis 1, slot 6 as the target for subsequent commands.
On pressing Enter, the prompt then changes from */* MODULE> to 01/06
MODULE> to show the selection of chassis 1, slot 6 in effect.
Next, the operator types the alarm module command.
On pressing Enter, the system response "No active alarms found for the specified
module range" reflects the alarm status of the module in chassis 1, slot 6 of the
current ICIM2 domain.
Modal command entry is often helpful for human operators. It can minimize the
need for keystrokes in some cases, thus saving time and eliminating a possible
source of error. Modal operation can also help streamline the work flow by focusing
commands and human attention on a particular chassis or module of interest.
Non-Modal Command Syntax
The general format for a non-modal CLI command, as usually sent from an element
management system, is as follows:
modeName modeOptions Action actionOptions Values Exit
The parameters in the command have the same functions as in modal command
entry:
Keyword Function
modeName The name of a mode switch: cli, module, icim, or terminal.
modeOptions Options that may be associated with the modename.
Action A command keyword such as set, show, info, etc.
actionOptions Options that may be associated with the action.
Values Values that may be associated with the action.
Exit Used to return to CLI command mode.
Example
A non-modal command is entered without changing command modes. For example,
the alarm module command shown above could have been entered as follows:
CLI> module chassis 1 slot 6 exit
SUCCESS!
CLI> module alarm module exit
No active alarms found for the specified module range
SUCCESS!
CLI>
Comentarios a estos manuales