Command-Line Interface Overview This chapter provides an overview of the JUNOS software command-line interface (CLI). For more detailed information about using the JUNOS software CLI, see the JUNOS Sy stem Basics Configur ation Guide and the JUNOS Protocols, Class of Service and Sy stem Basics Command R eference . The CLI is the interface to the software that you use whenever you access the router—whether from the console or through a remote network connection. The CLI, which automatically starts after the router finishes booting, provides commands that you use to perform various tasks, including configuring the JUNOS software, and monitoring and troubleshooting the software, network connectivity, and the router hardware. The CLI has two modes: CLI Operational Mode on page 328 CLI Configuration Mode on page 333 327 JUNOS Interfaces Operations Guide 328 CLI Operational Mode In operational mode you enter commands to monitor and troubleshoot the software, network connectivity, and the router by entering commands. When you log in to the router and the CLI starts, you are at the top level of the CLI operational mode. At this level, there are several broad groups of CLI commands (see Table 61). Table 61: CLI Operational Mode Top-Level Commands Command Description clear Clear statistics and protocol database information. Syntax: clear (arp | bgp | chassis | firewall | igmp | interfaces | isis | ldp | log | mpls | msdp | multicast | ospf | pim | rip | route | rsvp | snmp | system | vrrp) configure Enter CLI configuration mode. Alternative commands: configure exclusive | configure private file Perform file manipulation operations, such as copy, delete, list, rename, and show. Syntax: file (compare | copy | delete | list | rename | show) help Provide help information. Syntax: help (reference | topic) monitor Monitor a log file or interface traffic in real time. Syntax: monitor (start | stop | interface | list | traffic) mtrace Display trace information about a multicast path from a source to a receiver. Syntax: mtrace (from-source | to-gateway | monitor) ping Try to connect to a remote target. pipe Filter the output of an operational mode or configuration mode command. Syntax: | (compare | count | display <detail | inheritance | xml> | except pattern | find pattern | hold | match pattern | no-more | resolve <full-names> | save filename | trim columns) quit Exit from the CLI to a UNIX shell. request Make system-level requests, such as stop or reboot the router, load software packages, and back up the router’s file systems. Syntax: request system (reboot | halt | software | snapshot) restart Restart the router software processes. Syntax: restart (fpc | interface-control | mib-process | routing | sampling | sfm | snmp | soft) set Set CLI properties, the router’s date and time, and the craft interface display text. Syntax: set (chassis | cli | date) show Show information about all aspects of the software, including interfaces and routing protocols. Syntax: (aps | arp | as-path | bgp | chassis | cli | configuration | connections | dvmrp | firewall | host | igmp | interfaces | isis | ldp | log | mpls | msdpl | multicast | ntp | ospf | pfe | pim | policy | ripl | route | rsvp | sap | snmp | system | task | ted | version | vrrp) ssh Open a secure shell to another host. start Start a software process. Syntax: start shell telnet Start a telnet session to another host. test Run various diagnostic debugging commands. Syntax: test (configuration | interface | msdp | policy) traceroute Trace the route to a remote host. CLI Operational Mode Command-Line Interface Overview Use the CLI Operational Mode This section describes how to use the CLI operational mode. You can do the following: Enter the CLI Operational Mode on page 329 Get Help on Commands at a Hierarchy Level on page 329 Get Help about Commands on page 330 Have the CLI Complete Commands on page 331 Use CLI Command Completion on page 332 Display CLI Command History on page 332 Enter the CLI Operational Mode To enter the JUNOS software CLI, use the following command: % cli You are in the CLI when you see the > prompt, which is preceded by a string that defaults to the name of the user and the name of the router. For example: user@host> Get Help on Commands at a Hierarchy Level The CLI provides context-sensitive help at every level of the command hierarchy. The help information tells you which commands are available at the current level in the hierarchy and provides a brief description of each. To get help while in the CLI, type ?. You do not need to press Enter after typing the question mark. You have the following options: If you type the question mark at the command-line prompt, the CLI lists the available commands and options. If you type the question mark after entering the complete name of a command or command option, the CLI lists the available commands and options, then redisplays the command names and options that you typed. If you type the question mark in the middle of a command name, the CLI lists possible command completions that match the letters you have entered so far, then redisplays the letters that you typed. Use the CLI Operational Mode 329 JUNOS Interfaces Operations Guide 330 Get Help about Commands To get help about operational mode CLI commands, you can do the following: List Top-Level Operational Mode CLI Commands on page 330 List CLI Commands that Start with a Particular Letter on page 330 List All Available Commands of a Particular Type on page 331 List Top-Level Operational Mode CLI Commands To list all available commands at the top level of the CLI operational mode, use the following command (see Table 61): user@host> ? Possible completions: clear Clear information in the system configure Manipulate software configuration information file Perform file operations help Provide help information mtrace Trace mtrace packets from source to receiver. monitor Real-time debugging ping Ping a remote target quit Exit the management session request Make system-level requests restart Restart a software process set Set CLI properties, date, time, craft display text show Show information about the system ssh Open a secure shell to another host start Start a software process telnet Telnet to another host test Diagnostic debugging commands traceroute Trace the route to a remote host user@host> List CLI Commands that Start with a Particular Letter To list all commands that start with the letter c, use the following CLI command: user@host> c? Possible completions: clear Clear information in the system configure Manipulate software configuration information user@host> c Use the CLI Operational Mode Command-Line Interface Overview List All Available Commands of a Particular Type To list all available clear commands, use the following CLI command: user@host> clear ? Possible completions: arp Clear address-resolution information bgp Clear BGP information chassis Clear chassis information firewall Clear firewall counters igmp Clear IGMP information interfaces Clear interface information ilmi Clear ILMI statistics information isis Clear IS-IS information ldp Clear LDP information log Clear contents of a log file mpls Clear MPLS information msdp Clear MSDP information multicast Clear Multicast information ospf Clear OSPF information pim Clear PIM information rip Clear RIP information route Clear routing table information rsvp Clear RSVP information snmp Clear SNMP information system Clear system status vrrp Clear VRRP statistics information user@host> clear Have the CLI Complete Commands You do not always have to remember or type the full command or option name for the CLI to recognize it. To display all possible command or option completions, type the partial command followed by a question mark. To complete a command or option that you have partially typed, press the Tab key or the spacebar. If the partially typed letters begin a string that uniquely identifies a command, the complete command name appears. Otherwise, a beep indicates that you have entered an ambiguous command, and the possible completions are displayed. Command completion also applies to other strings, such as filenames and usernames. To display all possible values, type a partial string followed by a question mark. However, to complete these strings, press the Tab key; pressing the space bar does not work. Use the CLI Operational Mode 331 JUNOS Interfaces Operations Guide 332 Use CLI Command Completion To complete the show interfaces command, do the following: user@host> show in<Spacebar>terfaces <Enter> Physical interface: at-0/1/0, Enabled, Physical link is Up Interface index: 11, SNMP ifIndex: 65 Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode Speed: OC12, Loopback: None, Payload scrambler: Enabled Device flags : Present Running Link flags : 0x01 [...Output truncated...] To display a list of all log files whose names start with the string “messages,” and then display the contents of one of the files, do the following: user@host> show log mes? Possible completions: <filename> Log file to display messages Size: 1417052, Last changed: Mar 3 00:33 messages.0.gz Size: 145575, Last changed: Mar 3 00:00 messages.1.gz Size: 134253, Last changed: Mar 2 23:00 messages.10.gz Size: 137022, Last changed: Mar 2 14:00 messages.2.gr Size: 137112, Last changed: Mar 2 22:00 messages.3.gz Size: 121633, Last changed: Mar 2 21:00 messages.4.gz Size: 135715, Last changed: Mar 2 20:00 messages.5.gz Size: 137504, Last changed: Mar 2 19:00 messages.6.gz Size: 134591, Last changed: Mar 2 18:00 messages.7.gz Size: 132670, Last changed: Mar 2 17:00 messages.8.gz Size: 136596, Last changed: Mar 2 16:00 messages.9.gz Size: 136210, Last changed: Mar 2 15:00 user@host> show log mes<Tab>sages.4<Tab>.gz<Enter> Jan 15 21:00:00 myhost newsyslog[1381]: logfile turned over [...Output truncated...] Display CLI Command History You can display a list of recent commands that you issued. To display the command history, use the show cli history command: user@host> show cli history 03-03 01:00:50 -- show cli history 03-03 01:01:12 -- show interfaces terse 03-03 01:01:22 -- show interfaces lo0 03-03 01:01:44 -- show bgp next-hop-database 03-03 01:01:51 -- show cli history By default, this command displays the last 100 commands issued in the CLI. Specify a number with the command to display that number of recent commands. For example: user@host> show cli history 3 01:01:44 -- show bgp next-hop-database 01:01:51 -- show cli history 01:02:51 -- show cli history 3 Use the CLI Operational Mode Command-Line Interface Overview CLI Configuration Mode In configuration mode, you configure the JUNOS software by creating a hierarchy of configuration statements by using the CLI or by creating a text (ASCII) file that contains the statement hierarchy. (The statement hierarchy is identical in both the CLI and text configuration file.) You can configure all properties of the JUNOS software, including interfaces, general routing information, routing protocols, and user access, as well as several system hardware properties. When you have finished entering the configuration statements, you commit them, which activates the configuration on the router. Table 62 explains each CLI configuration mode command. The commands are organized alphabetically. Table 62: CLI Configuration Mode Commands Command Description activate Remove the inactive: tag from a statement, effectively reading the statement or identifier to the configuration. Statements or identifiers that have been activated take effect when you next issue the commit command. Syntax: activate (statement | identifier) annotate Add comments to a configuration. You can add comments only at the current hierarchy level. Syntax: annotate statement "comment-string" commit Commit the set of changes to the database and cause the changes to take operational effect. Syntax: commit << at <string>> <and-quit> <check> <confirmed <minutes>> <synchronize> copy Make a copy of an existing statement in the configuration. Syntax: copy existing-statement to new-statement deactivate Add the inactive: tag to a statement, effectively commenting out the statement or identifier from the configuration. Statements or identifiers marked as inactive do not take effect when you issue the commit command. Syntax: deactivate (statement | identifier) delete Delete a statement or identifier. All subordinate statements and identifiers contained within the specified statement path are deleted with it. Syntax: delete <statement-path> <identifier> edit Move inside the specified statement hierarchy. If the statement does not exist, it is created. Syntax: edit statement-path exit Exit the current level of the statement hierarchy, returning to the level prior to the last edit command, or exit from configuration mode. The quit and exit commands are synonyms. Syntax: exit <configuration-mode> help Display help about available configuration statements. Syntax: help (apropos | topic | reference) <string > insert Insert an identifier into an existing hierarchy. Syntax: insert <statement-path> identifier1 (before | after) identifier2 load Load a configuration from an ASCII configuration file or from terminal input. Your current location in the configuration hierarchy is ignored when the load operation occurs. Syntax: load (replace | merge | override) (filename | terminal) CLI Configuration Mode 333 JUNOS Interfaces Operations Guide 334 quit Exit the current level of the statement hierarchy, returning to the level prior to the last edit command, or exit from configuration mode. The quit and exit commands are synonyms. Syntax: quit <configuration-mode> rename Rename an existing configuration statement or identifier. Syntax: rename <statement-path> identifier1 to identifier2 rollback Return to a previously committed configuration. The software saves the last 10 committed configurations, including the rollback number, date, time, and name of the user who issued the commit configuration command. The currently operational JUNOS software configuration is stored in the file juniper.conf, and the last three committed configurations are stored in the files juniper.conf.1, juniper.conf.2, and juniper.conf.3. These four files are located in the directory /config, which is on the router’s flash drive. The remaining six previous committed configurations, the files juniper.conf.4 through juniper.conf.9, are stored in the directory /var/db/config, which is on the router’s hard disk. Syntax: rollback <number> run Run a top-level CLI command without exiting from configuration mode. Syntax: run command save Save the configuration to an ASCII file. The contents of the current level of the statement hierarchy (and below) are saved, along with the statement hierarchy containing it. This allows a section of the configuration to be saved, while fully specifying the statement hierarchy. Syntax: save filename set Create a statement hierarchy and set identifier values. This is similar to edit except that your current level in the hierarchy does not change. Syntax: set <statement-path> identifier show Display the current configuration. Syntax: show <statement-path> <identifier> status Display the users currently editing the configuration. top Return to the top level of configuration command mode, which is indicated by the [edit] banner. Syntax: top <configuration-command> up Move up one level in the statement hierarchy. Syntax: up <number> <configuration-command> update Update a private database. Command Description CLI Configuration Mode Command-Line Interface Overview Configuration Statements and Identifiers You configure all router properties by including statements in the configuration. A statement consists of a keyword, which is fixed text, and, optionally, an identifier. An identifier is an identifying name that you define, such as the name of an interface, or a username, which allows you and the CLI to discriminate among a collection of statements. The following list shows the statements available at the top level of the configuration mode (that is, the trunk of the hierarchy tree). Table 63 on page 336 describes each statement. user@host# set ? Possible completions: > accounting-options Accounting data configuration + apply-groups Groups from which to inherit configuration data > chassis Chassis configuration > class-of-service Class-of-service configuration > firewall Define a firewall configuration > forwarding-options Configure options to control packet sampling > groups Configuration groups > interfaces Interface configuration > policy-options Routing policy option configuration > protocols Routing protocol configuration > routing-instances Routing instance configuration > routing-options Protocol-independent routing option configuration > snmp Simple Network Management Protocol > system System parameters An angle bracket ( > ) before the statement name indicates that it is a container statement and you can define other statements at levels below it. If there is no angle bracket ( > ) before the statement name, the statement is a leaf statement; you cannot define other statements at hierarchy levels below it. A plus sign ( + ) before the statement name indicates that it can contain a set of values. To specify a set, include the values in brackets. For example: [edit] user@host# set policy-options community my-as1-transit members [65535:10 65535:11] In some statements, you can include an identifier. For some identifiers, such as interface names, you must specify the identifier in a precise format. For example, the interface name so-0/0/0 refers to a SONET/SDH interface that is on the Flexible PIC Concentrator (FPC) in slot 0, in the first Physical Interface Card (PIC) location, and in the first port on the PIC. For other identifiers, such as interface descriptive text, policy, and firewall term names, you can specify any name, including special characters, spaces, and tabs. You must enclose in quotation marks (double quotes) identifiers and any strings that include the following characters: space tab ( ) [ ] { } ! @ # $% ^ & | ’ = ? CLI Configuration Mode 335 JUNOS Interfaces Operations Guide 336 Table 63 describes each top-level CLI configuration mode statement. Table 63: Configuration Mode Top-Level Statements Statement Description accounting-options Configure accounting statistics data collection for interfaces and firewall filters. For information about the statements in this hierarchy, see the JUNOS Netw ork Management Confi guration Guide . chassis Configure properties of the router chassis, including the clock source, conditions that activate alarms, and SONET/SDH framing and concatenation properties. For information about the statements in this hierarchy, see the JUNOS Netw ork Interf aces and Class of Service Confi guration Guide . class-of-service Configure class-of-service parameters. For information about the statements in this hierarchy, see the JUNOS Netw ork Interf aces and Class of Service Confi guration Guide . firewall Define filters that select packets based on their contents. For information about the statements in this hierarchy, see the JUNOS Policy Frame work Confi guration Guide . forwarding-options Define forwarding options, including traffic sampling options. For information about the statements in this hierarchy, see the JUNOS Netw ork Interf aces and Class of Service Confi guration Guide . groups Configure configuration groups. interfaces Configure interface information, such as encapsulation, interfaces, virtual channel identifiers (VCIs), and data-link channel identifiers (DLCIs). For information about the statements in this hierarchy, see the JUNOS Network Interf aces and Class of Service Confi guration Guide . policy-options Define routing policies, which allow you to filter and set properties in incoming and outgoing routes. For information about the statements in this hierarchy, see the JUNOS R outing Protocols Confi guration Guide . protocols Configure routing protocols, including Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), Routing Information Protocol (RIP), Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), and Resource Reservation Protocol (RSVP). For information about the statements in this hierarchy, see the chapters that discuss how to configure the individual routing protocols in the JUNOS Routing Protocols Confi guration Guide and the JUNOS MPLS Applications Confi guration Guide . routing-instances Configure multiple routing instances. For information about the statements in this hierarchy, see the JUNOS Routing Protocols Confi guration Guide . routing-options Configure protocol-independent routing options, such as static routes, autonomous system (AS) numbers, confederation members, and global tracing (debugging) operations to log. For information about the statements in this hierarchy, see the JUNOS R outing Protocols Confi guration Guide . snmp Configure Simple Network Management Protocol (SNMP) community strings, interfaces, traps, and notifications. For information about the statements in this hierarchy, see the JUNOS Network Management Confi guration Guide . system Configure systemwide properties, including the hostname, domain name, Domain Name System (DNS) server, user logins and permissions, mappings between hostnames and addresses, and software processes. CLI Configuration Mode Command-Line Interface Overview Configuration Statement Hierarchy The JUNOS software configuration consists of a hierarchy of statements . There are two types of statements: container statements , which are statements that contain other statements, and leaf statements , which do not contain other statements (see Figure 25). All of the container and leaf statements together form the configuration hierarchy. Figure 25: Configuration Mode Hierarchy of Statements Each statement at the top level of the configuration hierarchy resides at the trunk (or root level) of a hierarchy tree. The top-level statements are container statements, containing other statements that form the tree branches. The leaf statements are the leaves of the hierarchy tree. An individual hierarchy of statements, which starts at the trunk of the hierarchy tree, is called a statement path. Figure 25 illustrates the hierarchy tree, showing a statement path for the portion of the protocol configuration hierarchy that configures the hello interval on an interface in an OSPF area. The protocols statement is a top-level statement at the trunk of the configuration tree. The ospf, area, and interface statements are all subordinate container statements of a higher statement (they are branches of the hierarchy tree), and the hello-interval statement is a leaf on the tree, which, in this case, contains a data value: the length of the hello interval in seconds. 1412Trunk of hierarchy tree (Top-level statements) Branches of hierarchy tree (Container statements) Tree leaves (Leaf statements) Protocols bgp dvmrp icmp igmp isis mpis ospf rip router-discovery rsvp sap dead-interval hello-interval interface-type metric mtu poll-interval priority retransmit-interval transit-delay transmit-interval area-range interface stub virtual-link area traceoptions CLI Configuration Mode 337 JUNOS Interfaces Operations Guide 338 The CLI represents the statement path shown in Figure 25 on page 337as [protocols ospf area area-number interface interface-name], and displays the configuration as follows: protocols { ospf { area 0.0.0.0 { interface so-0/0/0 { hello-interval 5; } interface so-0/0/1 { hello-interval 5; } } } } The CLI indents each level in the hierarchy to indicate each statement’s relative position in the hierarchy and generally sets off each level with braces, using an open brace at the beginning of each hierarchy level and a closing brace at the end. If the statement at a hierarchy level is empty, the braces are not printed. Each leaf statement ends with a semicolon. If the hierarchy does not extend as far as a leaf statement, the last statement in the hierarchy ends with a semicolon. The CLI uses this indented representation when it displays the current system configuration, and you use this format when creating ASCII files that contain the software configuration. However, the format of ASCII configuration files is not as strict as the CLI output of the configuration. Although the braces and semicolons are required, the indentation and use of new lines, as shown above, are not required in ASCII configuration files. Use the CLI Configuration Mode This section describes how to use the CLI configuration mode. You can do the following: Enter Configuration Mode on page 339 Exit Configuration Mode on page 340 Move among Levels of the Hierarchy on page 340 Display the Current Configuration on page 341 Modify the Configuration on page 342 Remove a Statement on page 342 CLI Configuration Mode Command-Line Interface Overview Run Operational Mode CLI Commands from Configuration Mode on page 343 Display Configuration Mode Command History on page 343 Commit a Configuration on page 343 Save a Configuration to a File on page 344 Return to a Previously Committed Configuration on page 344 Get Help about Statements on page 346 Enter Configuration Mode If many users enter configuration mode at the same time, everyone can make configuration changes and commit all changes. If one user enters configuration mode when another user is also in configuration mode, a message indicates who the user is and what portion of the configuration that user is viewing or editing. To enter configuration mode, use the following CLI command: user@host> configure Entering configuration mode Current configuration users: root terminal p3 (pid 1088) on since 1999-05-13 01:03:27 EDT [edit interfaces so-3/0/0 unit 0 family inet] The configuration has been changed but not committed If, when you enter configuration mode, the configuration contains changes that have not been committed, a message appears: user@host> configure Entering configuration mode The configuration has been changed but not committed If, while in configuration mode, you try to make a change while the configuration is locked by another user, a message indicates that the configuration database is locked, who the user is, and what portion of the configuration the user is viewing or editing: user@host# set system host-name ipswitch error: configuration database locked by: user2 terminal d0 (pid 1828) on since 19:47:58 EDT, idle 00:02:11 exclusive [edit protocols] CLI Configuration Mode 339 JUNOS Interfaces Operations Guide 340 If you enter configuration mode with the configure exclusive command, you lock the candidate configuration for as long as you remain in configuration mode, allowing you to make changes without interference from other users. If another user is also in configuration mode and has the configuration locked, a message indicates who the user is and what portion of the configuration the user is viewing or editing: user@host> configure exclusive Entering configuration mode Users currently editing the configuration: root terminal p3 (pid 1088) on since 2000-10-30 19:47:58 EDT, idle 00:00:44 exclusive [edit interfaces so-3/0/0 unit 0 family inet] Exit Configuration Mode To exit configuration mode, use the exit configuration-mode configuration mode command from any level or use the exit command from the top level. If you try to exit from configuration mode using the exit command and the configuration contains changes that have not been committed, you see a message and prompt: [edit] user@host# exit The configuration has been changed but not committed Exit with uncommitted changes? [yes,no] (yes) <Enter> Exiting configuration mode user@host> To exit with uncommitted changes without having to respond to a prompt, use the exit configuration-mode command. Move among Levels of the Hierarchy The CLI commands in Table 64 help you navigate the levels of the configuration statement hierarchy. Table 64: CLI Configuration Mode Navigation Commands Display the Current Configuration You can display the following information about the current configuration: Display the Configuration at the Current Hierarchy Level on page 341 Display the Last Committed Current Configuration on page 341 Command Description edit To move down through an existing configuration command hierarchy, or to create a hierarchy and move down to that level, use the edit configuration mode command, specifying the hierarchy level at which you want to be. exit To move up the hierarchy, use the exit configuration mode command. This command is, in effect, the opposite of the edit command. up To move up the hierarchy one level at a time, use the up configuration mode command. top To move directly to the top level, use the top configuration mode command. CLI Configuration Mode Command-Line Interface Overview Display Users Currently Editing the Configuration on page 341 Display the Configuration at the Current Hierarchy Level To display the configuration at the current hierarchy level or at the specified level, use the show configuration mode command. user@host> show <statement-path> The configuration statements appear in a fixed order. The CLI indents each level in the hierarchy to indicate each statement’s relative position in the hierarchy and generally sets off each level with braces, using an open brace at the beginning of each hierarchy level and a closing brace at the end. If the statement at a hierarchy level is empty, the braces are not printed. Each leaf statement ends with a semicolon. If the hierarchy does not extend as far as a leaf statement, the last statement in the hierarchy ends with a semicolon. Interfaces appear alphabetically by type, and then in numerical order by slot number, PIC number, and port number. Display the Last Committed Current Configuration You also can use the CLI operational mode show configuration command to display the last committed current configuration, which is the configuration currently running on the router: user@host> show configuration Display Users Currently Editing the Configuration To display the users currently editing the configuration, use the status configuration mode command: user@host# status Current configuration users: user terminal p0 (pid 518) on since 2002-03-12 18:24:27 PST [edit protocols] The system displays who is editing the configuration (user), how the user is logged in (terminal p0), the date and time the user logged in (2002-03-12 18:24:27 PST), and what level of the hierarchy the user is editing ([edit protocols]). Modify the Configuration To configure the router or to modify an existing router configuration, you add statements to the configuration. For each statement hierarchy, you create the hierarchy starting with a statement at the top level and continuing with statements that move progressively lower in the hierarchy. To modify the hierarchy, you use two configuration mode commands: set—Creates a statement hierarchy and sets identifier values. After you issue a set command, you remain at the same level in the hierarchy. The set command has the following syntax: set <statement-path> statement <identifier> CLI Configuration Mode 341 JUNOS Interfaces Operations Guide 342 statement-path is the hierarchy to the configuration statement and the statement itself. If you have already moved to the statement’s hierarchy level, you omit this. statement is the configuration statement itself. identifier is a string that identifies an instance of a statement. edit—Moves to a particular hierarchy level. If that hierarchy level does not exist, the edit command creates it and then moves to it. The edit command has the following syntax: edit <statement-path> statement <identifier> Remove a Statement To delete a statement or identifier, use the delete configuration mode command. Deleting a statement or an identifier effectively “unconfigures” the functionality associated with that statement or identifier, returning that functionality to its default condition. When you delete a statement, the statement and all its subordinate statements and identifiers are removed from the configuration. delete <statement-path> <identifier> To delete the entire hierarchy starting at the current hierarchy level, do not specify a statement or an identifier in the delete command: [edit] user@host# delete Delete everything under this level? [yes, no] (no) ? Possible completions: no Don't delete everything under this level yes Delete everything under this level Delete everything under this level? [yes, no] (no) Run Operational Mode CLI Commands from Configuration Mode To display the output of an operational mode show or other command while configuring the software, you can execute a single operational mode command by issuing the run configuration mode command and specifying the operational mode command: [edit] user@host# run operational-mode-command Display Configuration Mode Command History To display a list of the recent commands you issued while in configuration mode, use the run show cli history command. By default, this command displays the last 100 commands issued in the CLI. user@host# run show cli history 12:40:08 -- show 12:40:17 -- edit protocols 12:40:27 -- set isis 12:40:29 -- edit isis 12:40:40 -- run show cli history CLI Configuration Mode Command-Line Interface Overview Commit a Configuration To commit a configuration, you can do the following: Save Configuration Changes and Activate the Configuration on page 343 Save Configuration Changes, Activate the Configuration, and Exit Configuration Mode on page 344 Save Configuration Changes and Activate the Configuration To save software configuration changes to the configuration database and activate the configuration on the router, use the commit configuration mode command: user@host# commit commit complete The configuration is checked for syntax errors. If the syntax is correct, the configuration is activated and becomes the current, operational router configuration. If the configuration contains syntax errors, a message indicates the location of the error and the configuration is not activated. You must correct the error before recommitting the configuration. Save Configuration Changes, Activate the Configuration, and Exit Configuration Mode To save software configuration changes, activate the configuration on the router, and exit configuration mode, use the commit and-quit configuration mode command. This command succeeds only if the configuration contains no errors. [edit] user@host# commit and-quit commit complete exiting configuration mode user@host> Save a Configuration to a File To save the configuration to a text (ASCII) file so that you can edit it with a text editor of your choice, use the save configuration mode command. By default, the configuration is saved to that file in your home directory, which is on the flash disk. [edit] user@host# save filename Return to a Previously Committed Configuration To return to a previously committed configuration, you can do the following: Return to the Most Recent Committed Configuration on page 344 Activate the Configuration You Loaded on page 345 CLI Configuration Mode 343 JUNOS Interfaces Operations Guide 344 Return to a Configuration Prior to the Most Recently Committed One on page 345 Display Previous Configurations on page 345 Return to the Most Recent Committed Configuration To return to the most recently committed configuration and load it into configuration mode without activating it, use the rollback configuration mode command: [edit] user@host# rollback load complete Activate the Configuration You Loaded To activate the configuration that you loaded, use the commit command: [edit] user@host# rollback load complete [edit] user@host# commit Return to a Configuration Prior to the Most Recently Committed One To return to a configuration prior to the most recently committed one, include the number in the rollback command. number can be a number in the range 0 through 9. The most recently saved configuration is number 0 (which is the default configuration to which the system returns), and the oldest saved configuration is number 9. [edit] user@host# rollback number load complete Display Previous Configurations To display previous configurations, including the rollback number, date, time, the name of the user who committed changes, and the method of commit, use the rollback ? command. [edit] user@host# rollback ? Possible completions: <[Enter]> Execute this command <number> Numeric argument 0 2001-02-27 12:52:10 PST by abc via cli 1 2001-02-26 14:47:42 PST by cde via cli 2 2001-02-14 21:55:45 PST by fgh via cli 3 2001-02-10 16:11:30 PST by hij via cli 4 2001-02-10 16:02:35 PST by klm via cli | Pipe through a command [edit] CLI Configuration Mode Command-Line Interface Overview Get Help about Statements In configuration mode, you can use the help command to display help based on a text string contained in a statement name. This command displays help for statements at the current hierarchy level and below. user@host# help string You can also display help based on a text string contained in a statement name using the help topic and help reference commands. The help topic command displays usage guidelines for the statement, whereas the help reference command displays summary information about the statement. user@host# help topic string user@host# help reference string If you do not type an option for a statement that requires one, a message indicates the type of information expected. In this example, you need to type an area number to complete the command: [edit] user@host# set protocols ospf area<Enter> syntax error, expecting <identifier>. In this example, you need to type a value for the hello interval to complete the command: [edit] user@host# set protocols ospf area 45 interface so-0/0/0 hello-interval<Enter> syntax error, expecting <data> If you have omitted a required statement at a particular hierarchy level, when you attempt to move from that hierarchy level or when you issue the show command in configuration mode, a message indicates which statement is missing. For example: [edit protocols pim interface so-0/0/0] user@host# top Warning: missing mandatory statement: 'mode' [edit] user@host# show protocols { pim { interface so-0/0/0 { priority 4; version 2; # Warning: missing mandatory statement(s): 'mode' } } } CLI Configuration Mode 345 JUNOS Interfaces Operations Guide 346 CLI Configuration Mode