7
mitted commands.
entered-but-not-submitted commands.
For more information about this command, see
Network Management and Monitoring
Command Reference.
Understanding command-line error messages
After you press Enter to submit a command, the command line interpreter examines the command
syntax.
If the command passes syntax check, the CLI executes the command.
If the command fails syntax check, the CLI displays an error message.
Table 4 Common command-line error messages
% Unrecognized command found at '^' position. The keyword in the marked position is invalid.
% Incomplete command found at '^' position.
One or more
required keywords or arguments are
missing.
% Ambiguous command found at '^' position.
The entered character sequence matches more than
one command.
% Too many parameters.
The entered character sequence contains excessive
keywords or arguments.
% Wrong parameter found at '^' position. The argument in the marked position is invalid.
Using the command history function
The system automatically saves commands successfully executed by a login user to the following
two command history buffers:
Command history buffer for the user line.
Command history buffer for all user lines.
Table 5 Comparison between the two types of command history buffers
Item
Command history buffer for a user
line
Command history buffer for all
commands are saved
in the buffer?
Commands
successfully executed by the
current user of the user line.
Commands successfully executed
by all login users.
user logs out?
Yes. No.
How to view buffered
commands?
Use the
display history-command
command.
Use the
display history-command all
command.
How to recall buffered
commands?
• (Method 1.) Navigate to the command
in the buffer and press Enter
navigate to a command in the buffer:
ï‚¡
In Windows 200x or Windows XP
You cannot call buffered commands.