Checking Command Line Errors; Using Command History; Accessing History Commands - HP 5120 series Configuration Manual

Gigabit ethernet switches
Table of Contents

Advertisement

To do...
Enable redisplaying of input but
not submitted commands
NOTE:
If you have no input at the command line prompt and the system outputs system information such as
logs, the system will not display the command line prompt after the output.
If the system outputs system information when you are typing interactive information (not YES/NO for
confirmation), the system will not redisplay the prompt information but a line break after the output and
then display what you have typed.
For more information about the info-center synchronous command, see the
Monitoring Command Reference

Checking command line errors

If a command contains syntax errors, the CLI reports error information.
Table 4 Common command line errors
Error information
% Unrecognized command found at '^' position.
% Incomplete command found at '^' position.
% Ambiguous command found at '^' position.
Too many parameters
% Wrong parameter found at '^' position.

Using command history

The CLI automatically saves the commands recently used in the history command buffer. You can access
and execute them again.

Accessing history commands

Follow a step below to access history commands:
To do...
Display history commands
Display the previous history
command
Display the next history
command
Use the command...
info-center synchronous
.
Cause
The command was not found.
Incomplete command
Ambiguous command
Too many parameters
Wrong parameters
Use the key/command...
display history-command
Up arrow key or Ctrl+P
Down arrow key or Ctrl+N
9
Remarks
Required
Disabled by default
Network Management and
Result
Displays valid history commands you
used
Displays the previous history command, if
any
Displays the next history command, if any

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents