close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- About the CLI Guide
- CLI Overview
play_arrow Getting Started
play_arrow Using Configuration Statements to Configure a Device
play_arrow Managing Configurations
play_arrow Using Operational Commands to Monitor Devices
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Get Started with the Command-Line Interface
Switch Between Operational Mode and Configuration Mode
Use Keyboard Sequences to Navigate and Edit the CLI
Configure a User Account on a Juniper Networks Device
Use the CLI Editor in Configuration Mode
Check the Status of a Juniper Networks Device
Roll Back Configuration Changes
Configure a Routing Protocol

keyboard_arrow_right

Getting Started: A Quick Tour of the CLI

date_range 11-Nov-24

arrow_backward

arrow_forward

The following topics can help you (the network administrator) get started with the Junos OS CLI to perform configuration changes, switch between operational mode and configuration mode, create a user account, and execute some of the basic commands.

Note:

If you need a basic introduction to Junos OS, see the Getting Started Guide for Junos OS.

For more in-depth information, as well as to learn how to use Junos OS with Juniper Networks devices, see the Overview for Junos OS.

This Junos OS CLI Guide assumes that you are familiar with Junos OS concepts and operation principles.

Get Started with the Command-Line Interface

This topic shows you how to start the Junos OS CLI, view the command hierarchy, and make minor configuration changes.

Note:

Before you begin, make sure that your device hardware is set up and Junos OS is installed. You must have a direct console connection to the device or network access using SSH or Telnet. If your device is not set up, follow the installation instructions provided with the device before proceeding.

To log in to a device and start the CLI:

Log in as root.
The root login account has superuser privileges, with access to all commands and statements.
Start the CLI:
```
root# cli
root@>
```
The > command prompt shows that you are in operational mode. Later, when you enter configuration mode, the prompt will change to #.

Note:

If you are using the root account for the first time on the device, remember that the device ships with no password required for root. The first time you commit a configuration, you must set a root password. Root access is not allowed over a telnet session. To enable root access over an SSH connection, you must configure the system services ssh root-login allow statement.

CLI commands can vary by platform and software release. The CLI includes several ways to get help about available commands. This section demonstrates some examples showing how to get help:

Type ? to show the top-level commands available in operational mode.

content_copy zoom_out_map
root@>  ? 
Possible completions:
    clear           Clear information in the system
    configure       Manipulate software configuration information
    diagnose        Invoke diagnose script
    file            Perform file operations
    help            Provide help information
    monitor         Show real-time debugging information
    mtrace          Trace multicast path from source to receiver
    ping            Ping remote target
    quit            Exit the management session
    request         Make system-level requests
    restart         Restart software process
    set             Set CLI properties, date/time, craft interface message
    show            Show system information
    ssh             Start secure shell on another host
    start           Start shell
    telnet          Telnet to another host
    test            Perform diagnostic debugging
    traceroute      Trace route to remote host

Type file ? to show all possible completions for the file command.

content_copy zoom_out_map
root@> file ?
Possible completions:
    <[Enter]>            Execute this command
    archive              Archives files from the system
    checksum             Calculate file checksum
    compare              Compare files
    copy                 Copy files (local or remote)
    delete               Delete files from the system
    list                 List file information
    rename               Rename files
    show                 Show file contents
    source-address       Local address to use in originating the connection
    |                    Pipe through a command

Type file archive ? to show all possible completions for the file archive command.

content_copy zoom_out_map
root@>  file archive ? 
Possible completions:
    compress             Compresses the archived file using GNU gzip (.tgz)
    destination          Name of created archive (URL, local, remote, or floppy)
    source               Path of directory to archive

Switch Between Operational Mode and Configuration Mode

When you monitor and configure a device running Junos OS, you may need to switch between modes . When you switch between operational mode and configuration mode, the command prompt also changes. The operational mode prompt is a right-angle bracket (>). The configuration mode prompt is a pound or hash sign (#).

To switch between operational mode and configuration mode:

When you log in to the device and type the cli command and press Enter, you are automatically in operational mode:
```
---JUNOS 17.2B1.8 built 2018-05-09 23:41:29 UTC
% cli
user@host> 
```
To enter configuration mode, type the configure command or the edit command in CLI operational mode. The prompt in brackets ([edit]), also known as a banner, shows that you are in configuration mode at the top of the hierarchy. For example:
```
user@host> configure 
Entering configuration mode

[edit]
user@host# 
```
The CLI prompt changes from user@host> to user@host#, showing that you are in configuration mode, and a banner appears to indicate the hierarchy level.
You can exit configuration mode and return to operational mode in one of the following ways:
- To commit the configuration and exit:
  [edit] user@host# commit and-quit commit complete Exiting configuration mode user@host>
- To exit without committing:
  [edit] user@host# exit Exiting configuration mode user@host>
When you exit configuration mode, the CLI prompt changes from user@host# to user@host>, and the banner no longer appears. You can enter or exit configuration mode as many times as you wish without committing your changes.

To display the output of an operational mode command such as show while in configuration mode, issue the

run

configuration mode command. Then, specify the operational mode command:

content_copy zoom_out_map
[edit]
user@host# run operational-mode-command

For example, to display the currently set priority value of the Virtual Router Redundancy Protocol (VRRP) primary device while you are modifying the VRRP configuration for a backup device:

content_copy zoom_out_map
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# show 			
virtual-address [ 192.168.1.15 ];
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# run show vrrp detail 			
Physical interface: xe-5/2/0, Unit: 0, Address: 192.168.29.10/24
  Interface state: up, Group: 10, State: backup
  Priority: 190, Advertisement interval: 3, Authentication type: simple
  Preempt: yes, VIP count: 1, VIP: 192.168.29.55
  Dead timer: 8.326, Master priority: 201, Master router: 192.168.29.254
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# set priority ... 			

Use Keyboard Sequences to Navigate and Edit the CLI

You can use keyboard sequences in the Junos OS CLI to navigate and edit the command line. You can also use keyboard sequences to scroll through a list of recently executed commands. The following table lists some of the CLI keyboard sequences. They are the same as those used in Emacs.

Table 1: CLI Keyboard Shortcuts
Keyboard sequence	Action
Ctrl+b	Move the cursor back one character.
Esc+b or Alt+b	Move the cursor back one word.
Ctrl+f	Move the cursor forward one character.
Esc+f or Alt+f	Move the cursor forward one word.
Ctrl+a	Move the cursor to the beginning of the command line.
Ctrl+e	Move the cursor to the end of the command line.
Ctrl+h, Delete, or Backspace	Delete the character before the cursor.
Ctrl+d	Delete the character at the cursor.
Ctrl+k	Delete the all characters from the cursor to the end of the command line.
Ctrl+u or Ctrl+x	Delete the all characters from the command line.
Ctrl+w, Esc+Backspace, or Alt+Backspace	Delete the word before the cursor.
Esc+d or Alt+d	Delete the word after the cursor.
Ctrl+y	Insert the most recently deleted text at the cursor.
Ctrl+l	Redraw the current line.
Ctrl+p	Scroll backward through the list of recently executed commands.
Ctrl+n	Scroll forward through the list of recently executed commands.
Ctrl+r	Search the CLI history incrementally in reverse order for lines matching the search string.
Esc+/ or Alt+/	Search the CLI history for words for which the current word is a prefix.
Esc+. or Alt+.	Scroll backward through the list of recently entered words in a command line.
Esc+`number` `sequence` or Alt+`number` `sequence`	Specify the number of times to execute a keyboard sequence.

Configure a User Account on a Juniper Networks Device

This topic describes how to use a root account to log in to a Juniper Networks device and configure a new user account. You can configure an account for your own use or create a test account.

To configure a new user account on the device:

Log in as root and enter configuration mode:
```
root@host> configure
[edit]
root@host#
```
The ([edit]) prompt banner shows that you are in configuration edit mode at the top of the hierarchy.
Change to the [edit system login] section of the configuration:
```
[edit]
root@host# edit system login 
[edit system login]
root@host# 
```
The prompt in brackets changes to [edit system login] to show that you are at a new level in the hierarchy.
Now add a new user account. In the example, user1 represents a username:
```
[edit system login]
root@host# edit user user1
```
This example adds an account user1.

Note:
User account names can contain a period (.). For example, you can have a user account user.1. However, the username cannot begin or end with a period.
Configure a full name for the account. If the name includes spaces, enclose the entire name in quotation marks (" "):
```
[edit system login user user1]
root@host# set full-name "User One" 
```
Configure an account class. The account class sets the user access privileges for the account:
```
[edit system login user user1]
root@host# set class super-user 
```
Configure an authentication method and password for the account:
```
[edit system login user user1]
root@host# set authentication plain-text-password 
New password: 
Retype new password:
```
When the new password prompt appears, enter a clear-text password that the system can encrypt, and then confirm the new password.
Commit the configuration:
```
[edit system login user user1]
root@host# commit 
commit complete
```
Configuration changes are not active until you commit the configuration. If the commit is successful, a commit complete message appears.
Return to the top level of the configuration, and then exit:
```
[edit system login user user1]
root@host# top 
[edit]
root@host# exit 
Exiting configuration mode
```

Log out of the device:

content_copy zoom_out_map
root@host> exit 
% logout Connection closed.

To test your changes, log back in with the user account and password you just configured:
```
login: user1
Password: password
---JUNOS 17.2B1.8 built 2018-05-09 23:41:29 UTC
user1@host> 
```
When you log in, you should see the new username at the command prompt.

You have successfully used the CLI to view the device status and perform a simple configuration change.

Note:

For complete information about the commands to issue to configure your device, including examples, see the Junos OS configuration guides.

Use the CLI Editor in Configuration Mode

This topic describes basic commands that you can use to enter configuration mode in the CLI editor. The topic also describes commands that you use to navigate the configuration hierarchy, get help, and commit or revert the changes that you make during the configuration session.

Task	Command/Statement	Example
Edit Your Configuration
Enter configuration mode. When you start the CLI, the device is in operational mode. You must explicitly enter configuration mode. When you do, the CLI prompt changes from `user@host>` to `user@host#`, and the hierarchy level appears in square brackets.	configure	user@host> `configure` [edit] user@host#
Create a statement hierarchy. You can use the `edit` command to simultaneously create a hierarchy and move to that new level in the hierarchy. You cannot use the `edit` command to change the value of identifiers.	edit `hierarchy-level value`	[edit] user@host# `edit security zones security-zone myzone` [edit security zones security-zone myzone] user@host#
Create a statement hierarchy, and set identifier values. The `set` command is like `edit`, except that your current level in the hierarchy does not change.	set `hierarchy-level value`	[edit] user@host# `set security zones security-zone myzone` [edit] user@host#
Navigate the Hierarchy
Navigate down to an existing hierarchy level.	edit `hierarchy-level`	[edit] user@host# `edit security zones` [edit security zones] user@host#
Navigate up one level in the hierarchy.	up	[edit security zones] user@host# `up` [edit security] user@host#
Navigate to the top of the hierarchy.	top	[edit security zones] user@host# `top` [edit] user@host#
Commit or Revert Changes
Commit your configuration.	commit	[edit] user@host# `commit` commit complete
Roll changes back from the current session. Use the `rollback` command to revert all changes from the current configuration session. When you run the `rollback` command before you exit your session or commit changes, the software loads the most recently committed configuration onto the device. You must enter the `rollback`statement at the `edit` level in the hierarchy.	rollback	[edit] user@host# `rollback` load complete
Exit Configuration Mode
Commit the configuration, and exit configuration mode.	commit and-quit	[edit] user@host# `commit and-quit` user@host>
Exit configuration mode without committing your configuration. You must navigate to the top of the hierarchy using the `up` or `top` commands before you can exit configuration mode.	exit	[edit] user@host# `exit` The configuration has been changed but not committed Exit with uncommitted changes? [yes,no] (yes)
Get Help
Display a list of valid options for the current hierarchy level.	?	[edit ] user@host# `edit security zones ?` Possible completions: <[Enter]> Execute this command > functional-zone Functional zone > security-zone Security zones \| Pipe through a command [edit]

Check the Status of a Juniper Networks Device

In operational mode, you can use show commands to check the status of the device and monitor the activities on the device.

To help you become familiar with show commands:

Type show ? to display the list of show commands you can use to monitor the router:

content_copy zoom_out_map
root@>  show ? 
Possible completions:
  accounting           Show accounting profiles and records
  aps                  Show Automatic Protection Switching information
  arp                  Show system Address Resolution Protocol table entries
  as-path              Show table of known autonomous system paths
  bfd                  Show Bidirectional Forwarding Detection information
  bgp                  Show Border Gateway Protocol information
  chassis              Show chassis information
  class-of-service     Show class-of-service (CoS) information
  cli                  Show command-line interface settings
  configuration        Show current configuration
  connections          Show circuit cross-connect connections
  dvmrp                Show Distance Vector Multicast Routing Protocol        info
  dynamic-tunnels      Show dynamic tunnel information information
  esis                 Show end system-to-intermediate system information
  firewall             Show firewall information
  helper               Show port-forwarding helper information
  host                 Show hostname information from domain name server
  igmp                 Show Internet Group Management Protocol information
  ike                  Show Internet Key Exchange information
  ilmi                 Show interim local management interface information
  interfaces           Show interface information
  ipsec                Show IP Security information
  ipv6                 Show IP version 6 information
  isis                 Show Intermediate System-to-Intermediate System info
  l2circuit            Show Layer 2 circuit information
  l2vpn                Show Layer 2 VPN information
  lacp                 Show Link Aggregation Control Protocol information
  ldp                  Show Label Distribution Protocol information
  link-management      Show link management information
  llc2                 Show LLC2 protocol related information
  log                  Show contents of log file
  mld                  Show multicast listener discovery information
  mpls                 Show Multiprotocol Label Switching information
  msdp                 Show Multicast Source Discovery Protocol information
  multicast            Show multicast information
  ntp                  Show Network Time Protocol information
  ospf                 Show Open Shortest Path First information
  ospf3                Show Open Shortest Path First version 3 information
  passive-monitoring   Show information about passive monitoring
  pfe                  Show Packet Forwarding Engine information
  pgm                  Show Pragmatic Generalized Multicast information
  pim                  Show Protocol Independent Multicast information
  policer              Show interface policer counters and information
  policy               Show policy information
  ppp                  Show PPP process information
  rip                  Show Routing Information Protocol information
  ripng                Show Routing Information Protocol for IPv6 info
  route                Show routing table information
  rsvp                 Show Resource Reservation Protocol information
  sap                  Show Session Announcement Protocol information
  security             Show security information
  services             Show services information
  snmp                 Show Simple Network Management Protocol information
  system               Show system information
  task                 Show routing protocol per-task information
  ted                  Show Traffic Engineering Database information
  version              Show software process revision levels
  vpls                 Show VPLS information
  vrrp                 Show Virtual Router Redundancy Protocol information

Use the show chassis routing-engine command to view the Routing Engine status:

content_copy zoom_out_map
root@>  show chassis routing-engine  
Routing Engine status:
  Slot 0:
    Current state                  Master
    Election priority              Master (default)
    Temperature                 31 degrees C / 87 degrees F
    CPU temperature             32 degrees C / 89 degrees F
    DRAM                       768 MB
    Memory utilization          84 percent
    CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     1 percent
      Interrupt                  0 percent
      Idle                      99 percent
    Model                          RE-2.0
    Serial ID                      b10000078c10d701
    Start time                     2005-12-28 13:52:00 PST
    Uptime                        12 days, 3 hours, 44 minutes, 19 seconds
    Load averages:                 1 minute   5 minute  15 minute
                                       0.02       0.01       0.00

Use the show system storage command to view available storage on the device:

content_copy zoom_out_map
root@>  show system storage 
 
Filesystem        Size       Used     Avail  Capacity   Mounted on
/dev/ad0s1a       865M       127M      669M       16%  /
devfs             1.0K       1.0K        0B      100%  /dev
devfs             1.0K       1.0K        0B      100%  /dev/
/dev/md0          30M        30M         0B      100%  /packages/mnt/jbase
/dev/md1          158M       158M        0B      100%  /packages/mnt/jkernel-9.3B1.5
/dev/md2          16M        16M         0B      100%  /packages/mnt/jpfe-M7i-9.3B1.5
/dev/md3          3.8M       3.8M        0B      100%  /packages/mnt/jdocs-9.3B1.5
/dev/md4          44M        44M         0B      100%  /packages/mnt/jroute-9.3B1.5
/dev/md5          12M        12M         0B      100%  /packages/mnt/jcrypto-9.3B1.5
/dev/md6          25M        25M         0B      100%  /packages/mnt/jpfe-common-9.3B1.5
/dev/md7          1.5G       196K      1.4G        0%  /tmp
/dev/md8          1.5G       910K      1.4G        0%  /mfs
/dev/ad0s1e       96M        38K        88M        0%  /config
procfs            4.0K       4.0K        0B      100%  /proc
/dev/ad1s1f       17G        2.6G       13G       17%  /var

Roll Back Configuration Changes

This topic shows how to use the rollback command to return your uncommitted but revised configuration to the state of the most recently committed Junos OS configuration. The rollback command is useful if you make configuration changes and then decide not to keep them.

The following procedure shows how to configure an SNMP health monitor on a Juniper Networks device and then return to the most recently committed configuration that does not include the health monitor. When configured, the SNMP health monitor provides the network management system (NMS) with predefined monitoring for file system usage, CPU usage, and memory usage on the device.

Enter configuration mode:

content_copy zoom_out_map
user@host> configure 
entering configuration mode
[edit]
user@host# 

Show the current configuration (if any) for SNMP:
```
[edit]
user@host# show snmp
```
No snmp statements appear because SNMP has not been configured on the device.
Configure the health monitor:
```
[edit]
user@host# set snmp health-monitor 
```
Show the new configuration:
```
[edit]
user@host# show snmp 
health-monitor;
```
The health-monitor statement indicates that SNMP health monitoring is configured on the device.
Enter the rollback configuration mode command to return to the most recently committed configuration:
```
[edit]
user@host# rollback 
load complete
```
Show the configuration again to make sure your change is no longer present:
```
[edit]
user@host# show snmp 
```
No snmp configuration statements appear. The health monitor is no longer configured.
Enter the commit command to activate the configuration to which you rolled back:
```
[edit]
user@host# commit
```

Exit configuration mode:

content_copy zoom_out_map
[edit]
user@host# exit 
Exiting configuration mode

You can also use the rollback command to return to earlier configurations.

Configure a Routing Protocol

This topic provides a sample configuration that describes how to configure an OSPF backbone area that has two SONET interfaces.

The final configuration looks like this:

content_copy zoom_out_map
[edit]
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/0 {
                hello-interval 5;
                dead-interval 20;
            }
            interface so-0/0/1 {
                hello-interval 5;
                dead-interval 20;
            }
        }
    }
}

Shortcut
Longer Configuration
Make Changes to a Routing Protocol Configuration

Shortcut

You can create a shortcut for this entire configuration with the following two commands:

content_copy zoom_out_map
[edit]
user@host# set protocols ospf area 0.0.0.0 interface so-0/0/0 hello-interval 5 dead-interval 20
[edit]
user@host# set protocols ospf area 0.0.0.0 interface so-0/0/1 hello-interval 5 dead-interval 20

Longer Configuration

This section provides a longer example of creating the previous OSPF configuration. In the process, it illustrates how to use the different features of the CLI.

Enter configuration mode by issuing the configure command:
```
user@host> configure 
entering configuration mode
[edit]
user@host# 
```
Notice that the prompt has changed to a pound or hash sign (#) to indicate configuration mode.
To create the above configuration, you start by editing the protocols ospf statements:
```
[edit]
user@host# edit protocols ospf
[edit protocols ospf]
user@host# 
```

Now add the OSPF area:

content_copy zoom_out_map
[edit protocols ospf]
user@host# edit area 0.0.0.0
[edit protocols ospf area 0.0.0.0]
user@host# 

Add the first interface:

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0]
user@host# edit interface so-0/0/0
[edit protocols ospf area 0.0.0.0 interface so-0/0/0]
user@host# 

You now have four nested statements.

Set the hello and dead intervals.

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0 interface so-0/0/0]
user@host# set hello-interval 5
user@host# set dead-interval 20
user@host#

You can see what is configured at the current level with the show command:

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0 interface so-0/0/0]
user@host# show 
hello-interval 5;
dead-interval 20;
[edit protocols ospf area 0.0.0.0 interface so-0/0/0]
user@host# 

You are finished at this level, so go up a level and view what you have done so far:

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0 interface so-0/0/0]
user@host# up 
[edit protocols ospf area 0.0.0.0]
user@host# show 
interface so-0/0/0 {
    hello-interval 5;
    dead-interval 20;
}
[edit protocols ospf area 0.0.0.0]
user@host# 

The interface statement appears because you have moved to the area statement.

Add the second interface:

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0]
user@host# edit interface so-0/0/1
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# set hello-interval 5
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# set dead-interval 20
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# up 
[edit protocols ospf area 0.0.0.0]
user@host# show 
interface so-0/0/0 {
    hello-interval 5;
    dead-interval 20;
}
interface so-0/0/1 {
    hello-interval 5;
    dead-interval 20;
}
[edit protocols ospf area 0.0.0.0]
user@host# 

Move up to the top level and review what you have:

content_copy zoom_out_map
[edit protocols ospf area 0.0.0.0]
user@host# top
[edit]
user@host# show 
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/0 {
                hello-interval 5;
                dead-interval 20;
            }
            interface so-0/0/1 {
                hello-interval 5;
                dead-interval 20;
            }
        }
    }
}
[edit]
user@host# 

This configuration now contains the statements that you want.

Before committing the configuration (and thereby activating it), verify that the configuration is correct:
```
[edit]
user@host# commit check
configuration check succeeds
[edit]
user@host#
```
Commit the configuration to activate it on the device:
```
[edit]
user@host# commit
commit complete
[edit]
user@host#
```

Make Changes to a Routing Protocol Configuration

Suppose you decide to use different dead intervals and hello intervals on interface so-0/0/1. You can make changes to the configuration.

Go directly to the appropriate hierarchy level by typing the full hierarchy path to the statement that you want to edit:

content_copy zoom_out_map
[edit]
user@host# edit protocols ospf area 0.0.0.0 interface so-0/0/1
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# show 
hello-interval 5;
dead-interval 20;
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# set hello-interval 7
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# set dead-interval 28
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# top
[edit]
user@host# show 
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/0 {
                hello-interval 5;
                dead-interval 20;
            }
            interface so-0/0/1 {
                hello-interval 7;
                dead-interval 28;
            }
        }
    }
}
[edit]
user@host# 

If you decide not to run OSPF on the first interface, delete the statement:

content_copy zoom_out_map
[edit]
user@host# edit protocols ospf area 0.0.0.0
[edit protocols ospf area 0.0.0.0]
user@host# delete interface so-0/0/0
[edit protocols ospf area 0.0.0.0]
user@host# top
[edit]
user@host# show 
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/1 {
                hello-interval 7;
                dead-interval 28;
            }
        }
    }
}
[edit]
user@host# 

Everything inside the statement you deleted was deleted with it. You can also eliminate the entire OSPF configuration by simply entering delete protocols ospf while at the top level.

Maybe you decide to use the default values for the hello intervals and dead intervals on your remaining interface but want OSPF to run on that interface. In that case, delete the hello interval timer and dead interval timer:
```
[edit]
user@host# edit protocols ospf area 0.0.0.0 interface so-0/0/1
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# delete hello-interval
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# delete dead-interval
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# top
[edit]
user@host# show 
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/1;
        }
    }
}
[edit]
user@host# 
```
You can set multiple statements at the same time as long as they are all part of the same hierarchy. The hierarchy consists of the path of statements from the top inward, as well as one or more statements at the bottom of the hierarchy. Setting multiple statements at the same time can reduce considerably the number of commands you must enter.

To go back to the original hello interval timer and dead interval timer on interface so-0/0/1, enter:

content_copy zoom_out_map
[edit]
user@host# edit protocols ospf area 0.0.0.0 interface so-0/0/1
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# set hello-interval 5 dead-interval 20
[edit protocols ospf area 0.0.0.0 interface so-0/0/1]
user@host# exit
[edit]
user@host# show
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/1 {
                hello-interval 5;
                dead-interval 20;
            }
        }
    }
}
[edit]
user@host#

You also can re-create the other interface, as you had it before, with only a single entry:

content_copy zoom_out_map
[edit]
user@host# set protocols ospf area 0.0.0.0 interface so-0/0/0 hello-interval 5 dead-interval 20
[edit]
user@host# show
protocols {
    ospf {
        area 0.0.0.0 {
            interface so-0/0/0 {
                hello-interval 5;
                dead-interval 20;
            }
            interface so-0/0/1 {
                hello-interval 5;
                dead-interval 20;
            }
        }
    }
}
[edit]
user@host#

arrow_backward PREVIOUS CLI Overview

NEXT arrow_forward Online Help in the CLI

CLI User Guide for Junos OS

ON THIS PAGE

Getting Started: A Quick Tour of the CLI

Get Started with the Command-Line Interface

Switch Between Operational Mode and Configuration Mode

Use Keyboard Sequences to Navigate and Edit the CLI

Configure a User Account on a Juniper Networks Device

Use the CLI Editor in Configuration Mode

Check the Status of a Juniper Networks Device

Roll Back Configuration Changes

Configure a Routing Protocol

Shortcut

Longer Configuration

Make Changes to a Routing Protocol Configuration

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

CLI User Guide for Junos OS

ON THIS PAGE

Getting Started: A Quick Tour of the CLI

Get Started with the Command-Line Interface

Switch Between Operational Mode and Configuration Mode

Use Keyboard Sequences to Navigate and Edit the CLI

Configure a User Account on a Juniper Networks Device

Use the CLI Editor in Configuration Mode

See Also

Check the Status of a Juniper Networks Device

See Also

Roll Back Configuration Changes

See Also

Configure a Routing Protocol

Shortcut

Longer Configuration

Make Changes to a Routing Protocol Configuration

Stay in touch