Understanding Cli Error Messages - HP ProCurve 7102dl Reference Manual

SROS Command Line Interface Reference Guide
Command
show running config
debug
undebug all
Caution
The overhead associated with the debug command takes up a large portion of your
product's resources and at times can halt other processes. It is best to only use the debug
command during times when the network resources are in low demand (non-peak hours,
weekends, etc.).

Understanding CLI Error Messages

The following table lists and defines some of the more common error messages given in the CLI
Message
%Ambiguous command
%Unrecognized Command
%Invalid or incomplete
command
%Invalid input
detected at "^" marker
5991-2114
Description
Displays the current configuration.
Use the
may be experiencing on your network. These commands
provide additional information to help you better interpret
possible problems. For information on specific debug
commands, refer to the section
Set
To turn off any active debug commands, enter this
command.
Helpful Hints
The command may not be valid in the current command mode, or you may
not have entered enough correct characters for the command to be
recognized. Try using the "?" command to determine your error. See
CLI Shortcuts
on page 7 for more information.
The command may not be valid in the current command mode, or you may
not have entered all of the pertinent information required to make the
command valid. Try using the "?" command to determine your error. See
Using CLI Shortcuts
The error in command entry is located where the caret (^) mark appears.
Enter a question mark at the prompt. The system will display a list of
applicable commands or will give syntax information for the entry.
© Copyright 2007 Hewlett-Packard Development Company, L.P.
Understanding CLI Error Messages
command to troubleshoot problems you
debug
on page 20.
on page 7 for more information.
Enable Mode Command
.
Using
9