4.6 Interpreting CLI Messages


From time to time while navigating the CLI, there will be messages displayed on the screen. These messages occur when entering and exiting configurations, as well as when committing a configuration change. Messages will also be displayed if you have entered invalid or incorrect input to the CLI. In this section, we will show an example of CLI messages that could be displayed in the operational mode. Configuration-mode messages will be covered in the next section.

In the following example, the user enters the ambiguous value con . Notice that the caret symbol (^) is displayed at the location in question. This helps us to identify where we went wrong. The user then tries to set a CLI command and does not enter enough information. This is noted again by the caret symbol, which is pointing this time to the space after the parameter CLI, and the message displayed lets us know that a command was expected. In this event, the user may need to include a parameter, such as terminal or complete-on-space , for the expected command value. This particular example lets us know that while what we have entered is not incorrect, it is not enough information.

 lab@Chicago> show con                      ^ 'con' is ambiguous. lab@Chicago> set CLI                    ^ syntax error, expecting <command> 


Juniper Networks Reference Guide. JUNOS Routing, Configuration, and Architecture
Juniper Networks Reference Guide: JUNOS Routing, Configuration, and Architecture: JUNOS Routing, Configuration, and Architecture
ISBN: 0201775921
EAN: 2147483647
Year: 2002
Pages: 176

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net