the keywords that match the input characters will be displayed on the terminal screen if the input characters match more than one keyword.
Command History
CLI can store the latest executed commands as history commands so that users can recall and execute them again. By default, CLI can store 10 history commands for each user. Table
Table
| Operation | Operation | Description |
|
| Access the previous | Press the | This operation recalls the previous |
|
| history command | history command (if available). |
| |
|
|
| ||
|
|
|
|
|
| Access the next | Pressing the | This operation recalls the next |
|
| history command | <Ctrl+N> | history command (if available). |
|
|
|
|
|
|
|
|
|
|
|
z
z
You may use arrow keys to access history commands in Windows 2000/XP/2003 Terminal or Telnet. However, the
When you enter the same command several times, only one command is saved by the CLI as a history command.
Error Messages
If the command you enter passes the syntax check, it will be successfully executed; otherwise an error message will appear. Table
Table
| Error message |
| Description |
|
|
| The command does not exist. |
|
|
|
|
| Unrecognized command |
| The keyword does not exist. |
|
|
| |
|
| The parameter type is wrong. | |
|
|
| |
|
|
|
|
|
|
| The parameter value is out of range. |
|
|
| |
| Incomplete command | The command entered is incomplete. | |
|
|
|
|
| Too many parameters |
| You have entered too many parameters. |
|
|
| |
| Ambiguous command | The parameters entered are ambiguous. | |
|
|
| |
| Wrong parameter | A parameter entered is incorrect. | |
|
|
|
|