e d u cat i o n s e r v i ce s co u rs ewa re

JUNOS CONFIGURATION
BASICS

Student Guide
 Junos Configuration Basics

NOTE: Please note this Student Guide has been developed from an audio narration. Therefore, it will have
conversational English. The purpose of this transcript is to help you follow the online presentation and may
require reference to it.

Slide 1

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 2

 Junos Configuration Basics

Slide 2

Junos Configuration Basics

© 2017 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential

Welcome to Juniper Networks “Junos Configuration Basics”

eLearning module.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 3

 Junos Configuration Basics

Slide 3

Navigation

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 3

Throughout this module, you will find slides with valuable detailed information. You can stop any slide
with the Pause button to study the details. You can also read the notes by using the Notes tab. You can
click the Feedback link at any time to submit suggestions or corrections directly to the Juniper Networks
eLearning team.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 4

 Junos Configuration Basics

Slide 4

Course Objectives

 After successfully completing this course,

you will be able to:
•Discuss the Junos OS command line interface
•Describe various configuration features and
commands
•Explore routing configuration fundamentals

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 4

After successfully completing this course, you will

•be Discuss
able to: the Junos OS command line interface;
• Describe various configuration features and
• commands; and
Explore routing configuration fundamentals.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 5

 Junos Configuration Basics

Slide 5

Agenda: Junos Configuration Basics

 The Command-line Interface

 Configuration Commands and Process
 Junos OS Routing

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 5

This course consists of three sections. The three main sections

•areThe
as follows:
Command-line Interface;
• Configuration Commands and
• Process; and
Junos OS Routing.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 6

 Junos Configuration Basics

Slide 6

Junos Configuration Basics

The Command-Line Interface

© 2017 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential

The Command-Line
Interface

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 7

 Junos Configuration Basics

Slide 7

Section Objectives

 After completing this section, you will be able

to:
•Introduce the Junos OS CLI
•Understand the difference between operational
mode and configuration mode
•Navigate the command hierarchy
•Use command-line shortcuts and get help

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 7

After completing this section, you will be

•able to:
Introduce the Junos CLI;
• Understand the difference between operational mode and
• configuration mode; Navigate the command hierarchy; and
• Use command-line shortcuts and get help.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 8

 Junos Configuration Basics

Slide 8

Junos OS User Interface Options

 Command-line interface (CLI)

•A powerful, hierarchical user interface
 J-Web GUI
•A web-based, graphical user interface (GUI)
 Junos Space Network Management Platform
•A central point of management
 Programmatic interfaces such as JET,
NETCONF, and
REST API (others are also available)
•Provide access to third-party tools as a user interface

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 8

Junos OS User Interface

Options
The command-line interface (CLI) is the user interface used to access a device. If you have used other command-
lines, the Junos CLI will look familiar. But, you will also quickly notice that there are some new and different
commands. These differences provide a rich set of tools and safeguards (such as, a commit model and use of a
candidate configuration) that can help your customers to efficiently manage their networks and maintain high uptime.

Another option for user management is the J-Web GUI, a powerful web-based management interface available on
Junos OS devices. J-Web lets you perform the actions available in the CLI, but in a graphical format. It provides
practical tools to monitor, configure, troubleshoot, and manage your device.

Additionally, customers can manage platforms running the Junos OS with an expanding set of Junos Space
applications. Junos Space is Juniper’s network management platform.

Since Junos OS supports standards-compliant and open protocols, APIs, and interfaces, many other
third-party network
management, monitoring, automation, and orchestration tools can be used to manage Juniper
devices. Programmatic interfaces, such as JET, NETCONF, and REST API are available to provide
access to third-party tools as a user interface.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 9

 Junos Configuration Basics

Slide 9

CLI Login

 Log in with your username and password

The command prompt Type cli at the

root
will command prompt
to
change to a > to
show
are in you
operational modestart the CLI

username @ symbol
hostname prompt symbol

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net | 9

CLI
Login
The Junos OS CLI is the software interface you use to access a device running the Junos OS—whether
from the console or through a network connection. By leveraging industry-standard tools and utilities,
the CLI provides a powerful set of commands that you can use to monitor and configure devices
running the Junos OS.
To access the CLI, you need to connect and log in. If you are using a brand new device, rather than
one that has already
been configured with your username and password, you would log in with a username of root, leave
the password blank, and press enter. The root login account has superuser privileges, with access to
all commands and statements. When you log in as root, the command prompt will end with a
percentage symbol. At this point, you are in a command shell. To enter the CLI you need to type cli
and press enter. The command prompt will change to a “greater-than” symbol, as shown in
the example on this slide. This new command prompt indicates that you are now in operational mode
of the CLI. On a brand
new device,
When you logyou should
in with youralways create
username anda password
secure password
(instead for theroot
of the rootusername),
user, then you
create
will other user
be taken
accountsinto
directly as the
needed.
CLI In fact, you are required to set a root password the first time you commit a
configuration.
operational mode, as shown in the second example on this slide where a username of lab was used.
Note that the default CLI prompt is comprised of the username, then an “at” symbol, the device host
name, and then the prompt symbol. The prompt symbol indicates whether you are in the shell,
operational mode, or configuration mode.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 10

 Junos Configuration Basics

Slide 10

CLI Modes

 Operational mode
•Monitor and manage device operations
The > character identifies
mike@jnpr1> operational mode

 Configuration mode
•Configure the device and its interfaces

[edit] The # character

mike@jnpr1# identifies
configuration mode

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 10

CLI
Modes
The Junos CLI organizes its commands into two groups, known as modes:
• Operational mode is for managing and monitoring device operations. For example, monitor the
status of the device interfaces, check chassis alarms, and upgrade or downgrade the device's
operating system.
• Configuration mode is for configuring the device and its interfaces. This includes configuring the
management console with its network settings, setting up user accounts for access to the
device, specifying the security measures used to protect the device and the network, and
The setting
promptupfollowing
routing and
the switching protocols.
device name indicates the mode you are currently in, as
illustrated on this slide.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 11

 Junos Configuration Basics

Slide 11

Hierarchical Command
Structure

 Logical structure organizes device

features and functions
•Deeper levels are more and more
specific
 Know where you are, find what you want,
quickly move around the interface, efficiently
enter commands
Top Level

2nd Level
... ... ...
3rd Level
... ... ... ...
... ... ... ...
... ... ... ...

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 11

Hierarchical Command
Structure
The Junos CLI structures the activities of each mode into hierarchies. The hierarchy of each mode is
made up of cascading branches of related functions commonly used together.

The structured hierarchy of the CLI is among the first of many preferred differences that new users
discover about the Junos CLI. By logically grouping activities, the Junos CLI provides a regular,
consistent syntax that is helpful to knowing where you are, finding what you want, quickly moving
around the interface, and efficiently entering commands. The hierarchy of commands makes learning
and using the Junos CLI easier. New users regularly comment on just how logical the command- line is.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 12

 Junos Configuration Basics

Slide 12

Operational Mode: Key

Functions

Common Administrative
Tasks
• Monitor and troubleshoot the
device
• Connect to other network
systems
• Restart software processes
• Enter configuration mode and
exit the CLI
• Display the configuration
• Control the CLI environment
• Perform system-level operations such as
stopping and rebooting the device and
loading Junos images

Operational Mode: Key CONFIDENTIAL

© 2017 Juniper Networks, Inc. All rights reserved. SSFJUN02A-ML5 www.juniper.net

Functions | 12

This slide shows some of the common administrative tasks that can be performed in operational
mode. The Junos OS provides an extensive set of on-board instrumentation capabilities for gathering
critical operational status, statistics, and other information. These tools deliver advance notification
of issues and speed problem-solving during events.
As part of your configuration setup you can specify the types of events to track, the event severity, and
the files in which to store the data, among other options. You can then access this information in
operational mode. Juniper devices come with sufficient processing power to collect and store critical
operational data, including SNMP management, system logging, and traceoptions (or debugging) that
help you to understand how the device operates in normal conditions and where, when, and why
changes occur.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 13

 Junos Configuration Basics

Slide 13

Operational Mode CLI Tree

mike@jnpr1> show ospf neighbor

top
Less Specific

clear configure file help monitor set show ...

chassis configuration interfaces ospf route

version ...

database interface neighbor route statistics ...

More Specific

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 13

Operational Mode CLI

Tree
When you first log in to the CLI, you are at the top level of the CLI's
operational mode.
This slide shows a view of the CLI's tree structure from the top of operational mode, with an
example of its cascading
hierarchy through a show command. The show command is one of the most commonly used
because it displays information ranging from interfaces (show interface), to hardware (show
chassis), to protocols (show ospf neighbor). The tree structure cascades from less specific to
more
For specific
the aswith
student you experience
get deeper using
into the hierarchy.
IOS, a basic difference of the Junos OS is that it does not use the
keyword IP. So, many of the show commands you already know from IOS will work in the Junos OS if you
drop thatthe
example, part
IOSof the command.
command show ip For
route simply becomes show route in the Junos
OS.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 14

 Junos Configuration Basics

Slide 14

Specifying Output

mike@jnpr1> show interfaces fe-1/1/1 ?

Possible completions:
<[Enter]> Execute this command
brief Display brief output
descriptions Display interface description
strings detail Display detailed output
extensive Display extensive output
media Display media information
snmp-index SNMP index of interface
statistics Display statistics and detailed
output terse Display terse output

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL

SSFJUN02A-ML5 www.juniper.net | 14

Specifying
Output
The show command includes other arguments to modify the output. This slide displays the available arguments for
the
show interfaces command for the fe-1/1/1 Fast Ethernet interface. The question mark (?) helps you
to complete commands by showing a list of possible completions available for that command at that
level, without you needing to reference a CLI manual. The question mark will become your best friend
while operating or configuring a Junos OS device.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 15

 Junos Configuration Basics

Slide 15

Output
Options
mike@jnpr1> show interfaces fe-1/1/1 brief
Physical interface: fe-1/1/1 Enabled, Physic link is
Down
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback:
Disabled, Source filtering: Disabled
Flow control: Enabled
Device flags: Present Running Down
Interface flags: Hardware-Down SNMP-Traps Internal: Ox4000
Link flags: None

Command
output with
brief option

mike@jnpr1> show interfaces fe-1/1/1 terse

Interface Admin Link Proto Local Remote
fe-1/1/1 up up
at-1/3/0.0 up up inet 1.0.0.1 --> 1.0.0.2
iso

Command
output with
terse option

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 15

Output
Options
Junos OS operational mode commands can include brief, detail, extensive, or terse options. You
can use these options to control the amount of information you want to view.

This slide illustrates the results of adding the keywords and terse to the show interfaces comman
brief d.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 16

 Junos Configuration Basics

Slide 16

Switching Between
Modes

 Enter configuration mode from

operational mode using the configure
command
mike@jnpr1> configure Entering
configuration mode [edit]
mike@jnpr1# The prompt will be > in
operational mode
and
# in configuration mode

 Enter operational mode from the top of

Use exit from the top of
configuration mode using the exitback to operational mode
mike@jnpr1# exit

you are at the top of

command mike@jnpr1>
[edit]

[edit] indicates that Exiting configuration mode configuration mode to switch

configuration mode

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 16

Switching Between
Modes
As you monitor and configure a device, you will need to switch between operational mode and
configuration mode. When you change to configuration mode the command prompt changes from the
greater than symbol to the hashtag symbol, as shown in the examples on this slide.

To switch from operational mode to configuration mode, issue the configure command. The [edit] banner shows
your location at the top level of the configuration hierarchy. To switch back to operational mode, you
issue the exit
command.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 17

 Junos Configuration Basics

Slide 17

Configuration Mode CLI Tree

top
Less Specific
access chassis groups interfaces services system ...

accounting license location ports services

syslog ...

finger ftp netconf ssh telnet ... More

Specific

 Two types of statements

•Container statements which contain
other statements
•Leaf statements which do not contain other
statements

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 17

Configuration Mode CLI

Tree
Configuration mode has a hierarchical structure that logically groups related configuration statements.
This structure eases configuration set up, review, and changes, by allowing you to more readily find
and view related statements. The slide illustrates a portion of the configuration mode tree.

The configuration statement hierarchy includes the following two types

•of statements:
Container statements: This type of statement contains other statements, that is, they have
subordinate configuration levels. Each container statement represents a configuration stanza,
which could include other configuration stanzas. A configuration stanza is represented as the
• content between curly brackets in the CLI output.
Leaf statements: This type of statement does not contain other statements, that is, they are at the
end of a particular hierarchical path. Each leaf statement is located within a configuration stanza.
A semicolon identifies a leaf statement at a configuration hierarchy level.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 18

 Junos Configuration Basics

Slide 18

Configuration Mode Syntax

system {
services {
ftp;
}
}


Indentatio
n of
subordina
te levels
 Container statements are indicated with open
and close curly brackets { }
• In the example, system and services are cascading
container statements
 Leaf statements are indicated with a semicolon ;
• In the example, ftp; is a leaf statement
© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5
www.juniper.net | 18

Configuration Mode
Syntax
The CLI displays the hierarchy of the configuration mode through the
following syntax:levels are indicated by indenting each subordinate level. In the example shown on this slide,
• The hierarchy
services
• is a subordinate of system, and ftp is a subordinate of services.
Container statements are indicated between open and close curly brackets. In the example,
• system and services
are cascading container statements.
Leaf statements are indicated with a semicolon at the end. In the example, ftp; is a leaf
statement.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 19

 Junos Configuration Basics

Slide 19

Hierarchy Flexibility

 View from the top of configuration mode:

Configuration mode banner [edit]
system {
services {
ftp;
}
}

 View from a
sublevel of
configuration
mode:
Configuration mode banner [edit
system services]
ftp;

 Refer to the configuration command

banner before entering configuration
commands

Hierarchy CONFIDENTIAL
© 2017 Juniper Networks, Inc. All rights reserved.
www.juniper.net | 19
SSFJUN02A-ML5

Flexibility
The flexibility to work at a specific sublevel or stanza in the hierarchy is helpful when users want to
focus on just a small portion of the configuration.

Looking at the examples on this slide, the two configuration statements shown for the FTP service are
equal. In the top
example, you are looking at the statement from the root level of the hierarchy, and thus the ftp;
statement is shown in this listing within the system and services container statements.
In the bottom example, you are viewing the same ftp; statement from a deeper level within the hierarchy. When you
are in
deeper levels of the hierarchy, the [edit] banner displays the entire hierarchical path. In this example, the banner
[edit system services] indicates a place in the hierarchy lying within services (the 3rd level),
system (the
2nd level), and [edit] (the root or 1st level). At this level, whenever you view the configuration, the
command-line
To only displays
determine where you are the ftp;
in the statement.hierarchy, refer to the configuration mode banner
configuration
before entering configuration commands. While you can edit the configuration from the root
directory, often it is easier to navigate to the area within the configuration you are changing prior to
adding and removing commands.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 20

 Junos Configuration Basics

Slide 20

Navigating the Configuration Mode Tree

Command
s
• edit
• The user must know the full
hierarchical path
• This command will create new intermediate hierarchy levels
if they do not yet exist in your configuration
• up
• Moves you up one level in the hierarchy
• To move up multiple levels, add an optional count (up 2, for example)
• top
• Moves you to the top level in the hierarchy
• exit
• Leaves the current level of the configuration hierarchy,
returning to the level prior to the last edit command
• If you enter exit from the top level of the configuration hierarchy, you
exit
configuration mode and enter operational mode

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 20

Navigating the Configuration

Mode Tree
The edit, up, top, and exit commands let you navigate the configuration
tree.
Use the edit command to jump to a specific location within the candidate configuration. The
configuration mode banner changes to indicate your new location in the hierarchy. You must know the
full hierarchical path. If you navigate to a hierarchy location that does not exist in your configuration
yet, the CLI will create that hierarchy level.
The up command allows you to move up levels in the hierarchy. By default, you move one level. You
can add a number after the command to specify how many levels to move up.

The top command takes you to the first hierarchy

level.
The exit command returns you to the hierarchy location prior to the last edit command. If you use
the exit command at the top level of the configuration hierarchy, you exit configuration mode and go
back to operational mode.
The organized structure of the command hierarchy eases movement from one level to another
within the Junos CLI.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 21

 Junos Configuration Basics

Slide 21

CLI Shortcut Keys

 Go to next in command history Down arrow or
Ctrl+n
 Go to previous in command history Up arrow or
Ctrl+p
 Go to beginning of line Ctrl+a
 Go to end of line Ctrl+e
 Go left one character Ctrl+b
 Go right one character Ctrl+f
 Go forward one word Esc+f
 Go backward one word Esc+b
 Delete character over cursor Ctrl+d
 Delete word after cursor Esc+d
 Delete word before cursor Esc+backspace
 Delete text from the cursor to end of the line Ctrl+k
 Delete the line Ctrl+u
 Paste the deleted text at cursor Ctrl+y

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 21

CLI Shortcut
Keys
Fortunately, for new users, and even experienced users, the Junos CLI includes lots of shortcuts
and ways to get help.
Both configuration mode and operational mode offer options to shorten keystrokes. All standard UNIX
keyboard shortcuts are available to you when you are logged on to the Junos OS device. It might take
some repetition for these to become second nature, but once they are, these shortcuts can save you
a lot of typing time.
For example, the CLI stores every entered command in its command history. At any command
prompt, the up and down arrow keys let you scroll through this history. This allows you to re-use
commands that you previously entered, or modify them as needed.

Keyboard shortcut sequences can save you much time, for example, when you are configuring similar
items on the device, or you are repeating operational commands.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 22

 Junos Configuration Basics

Slide 22

Command and Variable Completion

 The spacebar completes commands

[edit]
mike@jnpr1# show i<space>
‘i’ is ambiguous
Possible completions:
igmp Show Internet Group Management Protocol
ike Show Interface Key Exchange Information
interfaces Show Interface Information
ipsec Show IP Security Information
isis Show Intermediate System-to
Intermediate

 The tab key completes commands,

filenames, and user defined variables
[edit policy-options]
mike@jnpr1# show policy-statement t<tab>his-is-my-policy
then accept;

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 22

Command and Variable

Completion
The CLI provides command completion to further speed your typing in both modes. Command
completion automatically finishes partially typed commands, filenames, usernames, and so forth, so
you do not need to recall the exact syntax of the desired input string. Command completion is a big
help to new users, especially when they are first learning the Junos OS CLI.

The spacebar completes most CLI commands. The tab key not only completes CLI commands, but also
filenames and user- defined variables such as policy names, community names, and IP addresses.
When the completion of the command or argument is ambiguous, hitting space or tab lists the possible
completions, as shown in the top example on this slide.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 23

 Junos Configuration Basics

Slide 23

Getting Help

[edit system] mike@jnp

r1# set s? Possible
completions:
saved-core-context Save context information for core files
saved-core-files Number of saved core files per
executable
(1..64)
> services System services
> static-host-mapping Static hostname database mapping
> syslog System logging facility

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 23

Getting
Help
You can query the command-line with the question mark character at any level of the operational or
configuration hierarchies for a list of available commands and a short description of each. Typing a
partial command followed by a question mark provides a list of all the valid ways to complete your
command, as shown in the example on this slide. Using the question mark in this way is known as
context-sensitive help in Junos OS lingo. For commands that require a filename as an argument, the
question mark lists the files in the working directory.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 24

 Junos Configuration Basics

Slide 24

More Help
 help apropos
•Displays help about a text string contained in a
statement or command name
 help reference
•Provides assistance with configuration syntax by
displaying summary information for the
statement
 help syslog
•Displays information on specific syslog events
 help tip
•Provides random tips for using the CLI
 help topic
•Displays usage guidelines for configuration
statements
© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5
www.juniper.net | 24

More
Help
When you want more information than provided by context-sensitive help, you can turn to the
Junos OS technical documentation included on your device by using the help commands. When
requesting help, follow each of these help commands with the string or topic for which you are
seeking information.
The help files are divided into major categories. You can access these files in operational
•mode.
helpYou can use:
apropos to display help about a text string contained in a statement or command name;
• help reference to provide assistance with configuration syntax by displaying summary
information for the
statemen
t;
• help syslog to display information on specific syslog events;
• help tip to provide random tips for using the CLI; and
• help topic to display usage guidelines for configuration
statements.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 25

 Junos Configuration Basics

Slide 25

Logging
Out

[edit protocols
ospf]
mike@jnpr1# exit
configuration-mode
Exiting configuration mode

mike@jnpr1> exit

jnpr1 (ttyu0)
login:

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL
SSFJUN02A-ML5 www.juniper.net | 25

Logging
Out
You must be in operational mode to log out completely from the device. If you are in configuration mode, use the
exit
configuration-mode command to enter operational mode. If you are at the top of the configuration
mode hierarchy, you only need to use the exit command. From operational mode, you can
completely exit the CLI by entering the exit command and hitting enter.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 26

 Junos Configuration Basics

Slide 26

Lab 1: Introduction to the Junos OS CLI

• Log into the Junos CLI • Explore the
Junos OS CLI
operational mode

 Pause this presentation, follow the link shown

below to Juniper’s Virtual Lab environment, open
the Lab Guide, and complete Lab 1

https://
virtuallabs.juniper.net/

Upon completing Lab 1, return to this

presentation and click the Play
button ( ) to proceed.

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 26

Lab 1: Introduction to the Junos

OS CLI
In this lab, you will:
• Log into the Junos CLI; and
• Explore the Junos OS CLI operational
mode.
At this point, you should pause this presentation, follow the link to Juniper’s Virtual Lab environment,
open the Lab Guide, and complete the lab portion of this section. When you are finished, return to
this presentation and click Play to continue.
Enter Virtual Lab
https://virtuallabs.juniper.
net/

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 27

 Junos Configuration Basics

Slide 27

Section Summary

 In this section, you have learned how to:

•Introduce the Junos OS CLI
•Describe the differences between operational
mode and configuration mode
•Navigate the command hierarchy
•Use command-line shortcuts and get help

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 27

In this section, you have learned

•howIntroduce
to: the Junos CLI;
• Describe the differences between operational mode and
• configuration mode; Navigate the command hierarchy; and
• Use command-line shortcuts and get help.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 28

 Junos Configuration Basics

Slide 28

Learning Activity 1:Quiz

Question 1
Click the Quiz button

Operational mode is identified by which
to edit this object
prompt?

A. # (hashtag
symbol)
B. } (curly bracket
symbol)
C. > (greater-than
symbol)
D. ~ (tilde symbol)

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5

Learning Activity 1:
www.juniper.net | 28

Question 1
Operational mode is identified by which
prompt?
• # (hashtag symbol)
• } (curly bracket
• symbol)
• > (greater-than
symbol)
~ (tilde
That’s symbol)
correct.
The prompt for operational mode ends with the greater-
than symbol.
That’s incorrect. The correct option is C.
The prompt for operational mode ends with the greater-
than symbol.
Learning Activity 1:
Question 2
Configuration mode is identified by which
prompt?
• # (hashtag symbol)
• } (curly bracket
• symbol)
• ~ (tilde symbol)
% (percentage
symbol)
That’s correct.
The prompt for configuration mode ends with the
hashtag symbol.
That’s incorrect. The correct option is A.
The prompt for configuration mode ends with the
hashtag symbol.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 29

 Junos Configuration Basics

Slide 29

Junos Configuration Basics

Configuration Commands and Process

© 2017 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential

Configuration Commands and

Process

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 31

 Junos Configuration Basics

Slide 30

Section Objectives

 After completing this section, you will be able

to:
•Present and demonstrate the Junos OS
configuration process and its multiple
safeguards
•Highlight some key Junos OS CLI commands
•Discuss features and commands of the Junos OS
CLI that can be used to save time, automate
operations, and monitor the network

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 30

After completing this section, you will be

•ablePresent
to: and demonstrate the Junos OS configuration process and its multiple safeguards;
• Highlight some key Junos OS CLI commands; and
• Discuss features and commands of the Junos OS CLI that can be used to save time, automate
operations, and monitor the network.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 32

 Junos Configuration Basics

Slide 31

The Junos OS Configuration Process (1 of

2)

 Separation of configuration edit and activation

•Validation checks
•Version control
•Automated rollback
 Convenient deployment of standard
configurations and policy language across
the network
Load configuration configuration configuration

commit
candidate validated

active commit
confirmed commit commit
scripts
validations

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 31

The Junos OS Configuration Process:

Part 1
The graphic at the bottom of this slide outlines the basic steps of the Junos OS configuration process.
One of the foremost differences between the Junos OS and other operating systems is that Junos OS
configuration changes do not become active until the user is ready to make them active. The Junos OS
configuration approach provides multiple safety nets that can save users hours of troubleshooting on
those bad days when their configuration changes do not go quite as planned, potentially resulting in
network issues.
Once they understand these safety nets, new users of the Junos OS typically recognize the Junos OS CLI
as much more user- friendly than other operating systems that have line-by-line entry and instant
activation of configuration changes. Have you ever had to make line-by-line changes in other systems,
knowing that you were creating intermediate risks, such as
removing a firewall on an interface? Perhaps you have entered a single-line change that created
unwanted or unexpected results that you could not easily revert. The Junos OS CLI protects you from
these
To and other
operate configuration
a device, the Junos headaches.
OS uses the active configuration file. When a user wants to make
changes to the configuration file, they work with a candidate configuration file, which is a copy of
the active configuration. In order for
configuration changes made to the candidate configuration to become active, the user must
commit the candidate configuration file.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 33

 Junos Configuration Basics

Slide 32

The Junos OS Configuration Process (2 of

2)

Load candidate validated active

rollback
configuratio configurati
commit
commit
n on
commit configuratio 1
n commit

confirmed

s
cripts validations
49

Basic steps in the

configuration process:
1. Enter changes
in the candidate
2. Commit the
candidate
3. Candidate
becomes active
The Junos OS Configuration Process:
Part 2 CONFIDENTIAL
© 2017 Juniper Networks, Inc. All rights reserved.

Let’s take a look at the basic steps of the multi-stage Junos OS configuration process,
SSFJUN02A-ML5 www.juniper.net | 32

which arethe
• First, as user
follows:
makes changes to the candidate
configuration.
• The candidate configuration is a copy of the active configuration. You can enter
configuration changes to the candidate configuration through the CLI by using cut-and-
paste, loading or merging a text file with the updated
configuration changes, or entering the changes manually through the CLI interface. After
• Second, making all your
you will candidate
commit changes,
your changes, you can
which reviewthe
will make your work, including
candidate comparing
configuration the the
active
• candidate to the the
configuration.
Before finalizing active running file.
changeover, the software checks for certain statements within the
candidate configuration and performs other context validations. If the device includes pre-
loaded commit scripts, these scripts will also
check for errors and possibly correct errors within the candidate configuration. If there are
• Third,anyonceissues, the user
everything will be
checks notified
out, and the configuration
the candidate configuration will not become
becomes the active.
active
• configuration.
The candidate configuration you were working on becomes the active configuration and the
device places the previous active configuration into an archive of up to 49 of the past active
configurations, which you can access
through the rollback command if needed.
We will explore each of these steps in more detail on the
upcoming slides.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 34

 Junos Configuration Basics

Slide 33

The configure private,

configure exclusive Commands
 Use configure private for your own copy
of the candidate configuration
mike@jnpr1> configure private
warning: uncommitted changes will be discarded on exit
Entering configuration mode

 Use configure exclusive when you

want to prohibit others from also making
changes while you are in configuration
mode
mike@jnpr1> configure exclusive
warning: uncommitted changes will be discarded on exit
Entering configuration mode

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 33

The configure private, configure exclusive Commands

To enter configuration mode, the Junos OS provides several options. These options give users different
ways to manage who is making changes and when.

If users enter configuration mode with the command: configure, then they are in standard
configuration mode. Standard mode allows any number of users to edit the candidate configuration
simultaneously, and changes made by a single user
are visibly shared by all users, any of whom will activate all changes if they enter a commit command.
Alternatively, the Junos OS offers the options to configure private or configure exclusive. These
prevent one user from inadvertently activating another users changes before they are ready.

In configure private mode, the device keeps a separate candidate copy, which holds only the changes made by the
private user. In configure exclusive mode, the CLI locks all other users out of configuration mode
until the exclusive user closes the exclusive state. These two configuration options are very handy
when multiple users can change the candidate configuration of a device.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 35

 Junos Configuration Basics

Slide 34

The show Command

 List the complete candidate  List a specific
subset of the configuration from the top of
candidate configuration from a configuration mode
deeper level of the hierarchy

[edit] [edit interfaces ge-5/0/0]

mike@juniper1# show mike@jnpr# show version
"9.2R1.3"; gigether-options { groups
flow-control;
{ auto-
negotiation;
re0 { }
system { unit 0 {
jnpr1-name jnpr1; family inet {
} address
} 1.2.3.4/28;
} }
… }

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL

SSFJUN02A-ML5 www.juniper.net | 34

The show Command

Initially, before any changes are entered, the candidate configuration is the same as the active
running configuration.
To display the candidate configuration, use the show command in configuration mode. When entered
from the top of the configuration hierarchy, the CLI displays the entire candidate configuration, as
shown in the abbreviated example on the left of this slide.

Deeper in the hierarchy, the show command displays the configuration from the current hierarchy level
and below, as show in the example on the right of this slide.

You might have noticed that configuration mode uses the show command in a different way than operational mode.
The
commands of each mode are independent of each other, and thus the show command represents
different actions in each mode.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 36

 Junos Configuration Basics

Slide 35

The set Command

 From the top of configuration mode:
[edit]
mike@jnpr1# set system services finger
mike@jnpr1# set system services ftp
mike@jnpr1# set system services ssh [edit]
mike@jnpr1# set system services telnet system {

{ services
Either
finger; ftp;

 From a sublevel: approa

telnet;
resultsi
results
ch ssh;
[edit system services]
in }
}

mi
ke@jnpr1# set finger
mike@jnpr1# set ftp mi
ke@jnpr1# set ssh mike
@jnpr1# set telnet

© 2017 Juniper
Networks, Inc. All rights reserved.

CONFIDENTIAL
SSFJUN02A-ML5 www.juniper.net
| 35

The set Command

You can create or change the candidate configuration by entering a series of commands, including those
to add and remove
configuration statements. The set command inserts a statement and values into the candidate
configuration.
While you can edit the candidate from the root directory, as shown in the top example on this slide,
often it is easier to navigate to the area within the configuration you are changing prior to adding and
removing
second commands.
example Thiswhere
on this slide is shown in the
changes are entered in the [edit system services] sublevel of the
hierarchy.
Either approach provides the same results, as shown in the example on the
right of this slide.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 37

 Junos Configuration Basics

Slide 36

The delete Command

 Remove a statement along with any

subordinate statements
•Deleting a statement effectively returns the
device, protocol, or service to an un-configured
state
•Deleting a container statement removes
everything under that level of the hierarchy

[edit]
mike@jnpr1# delete system services Res t [edit]
}
system {
ul

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 36

The delete Command

The delete command removes statements from the candidate configuration. In the example shown on this slide,
we
delete what we had just added in the prior slide, which was system services.
Deleting a statement effectively returns the device, protocol, or service to an un-configured state.
Deleting a container
statement removes everything under that level of the hierarchy. Proceed with caution. Remember,
the delete command removes all subordinate statements and identifiers. For example, if you
entered the simple command: delete protocols from the top of the CLI hierarchy, you would
remove all the protocols configured in your candidate file. You need to be aware of where you are
within the hierarchy and what you are removing when you issue a delete statement.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 38

 Junos Configuration Basics

Slide 37

The compare Command

 Used to display the differences

between the candidate and active
configurations
[edit system services]
mike@jnpr1# show | compare
- ssh;
+ telnet;
- web-management {
- http {
- port 8080;
- }
- }

 Options are also available for comparing

any configuration file to the candidate
configuration file
[edit]
mike@jnpr1# show | compare (filename| rollback n)

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 37

The compare Command

In configuration mode only, when you have made changes to the configuration and want to compare
the candidate
configuration with a prior version, you can use the compare command to display the differences. The
compare command compares the candidate configuration with either the current active configuration
or another configuration file and displays the differences between the two configurations. The CLI
indicates new lines in the candidate with a plus (+) sign and those removed with a minus (-) sign. In
the example shown at the top of this slide, the user has enabled telnet within system services and also
removed
To comparessh and web-management.
configurations, specify the compare command after the pipe symbol, as shown in the examples on this
slide. If
you do not specify any arguments after the compare command, then the candidate configuration is
compared against the active configuration file, as shown in the top example on this slide. If you want
to specify a file other than the active
configuration file for comparison, then you would specify the filename after the compare command, as
shown in the bottom example on this slide. You can also do a comparison to a previously active
configuration by using rollback n, where n is the index into the list of previously committed
configurations. The most recently saved configuration (which is the active configuration) is number 0,
and the oldest saved configuration is number 49.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 39

 Junos Configuration Basics

Slide 38

Using commit check

 Check that the device will accept your

candidate configuration
•Validates the logic and completeness of the
candidate configuration without activating
the changes
[edit]
mike@jnpr1# commit check

[edit interfaces lo0 unit 0 family inet]

'address 192.168.69.1/24'
Loopback addresses' prefix must be 32
bits error: configuration check-out failed

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net | 38

Using commit check

The CLI also provides a command to check that the system can process your candidate configuration. The commit
check
command validates the logic and completeness of the candidate semantics without activating any
changes. These are the
same validations which run when you commit a candidate. If the system finds a problem in the
candidate configuration, it lets you know, as the example on this slide illustrates.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 40

 Junos Configuration Basics

Slide 39

The commit Command

 Activates the candidate configuration to

become the active configuration of the
device
•If the validation checks find any errors, you
must fix them before the candidate can become
the active file
[edit]
mike@jnpr1# commit
error: Policy error: Policy my-policy referenced but not defined
error: BGP: export list not applied
error: configuration check-out failed

 The commit complete message tells you

that the new configuration is now active
[edit]
mike@jnpr1# commit
commit complete

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 39

The commit Command

The candidate configuration file is only the proposed configuration, and your device does not use any
of this configuration
until a commit command activates the configuration. After you have entered all desired changes, and
you have double checked your work, you are ready to activate your candidate as the active running
configuration. To activate the candidate configuration, enter the commit command.
Before actually activating the candidate configuration, the Junos OS checks basic syntax and
semantics. For example, the software makes sure that a policy has been defined before it is
referenced. If any syntax or semantic problems are found,
the commit command returns an error and the configuration is not activated, as shown in the first
example
You onallthis
must fix slide.
errors before the candidate can become active. The complete message tells you that the new
commit
configuration is up and running on the device.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 41

 Junos Configuration Basics

Slide 40

The commit confirmed Command

 Automate rollback in remote devices
•Commit a candidate configuration for a limited time:
[edit]
mike@jnpr1# commit confirmed
commit confirmed will be automatically rolled back in
10 minutes unless confirmed commit complete

•Finalize the commit, by entering a

2nd commit command:
[edit]
mike@jnpr1# commit
commit complete

•Or, wait for rollback to your

previous configuration:
Broadcast Message from root@jnpr1
(no tty) at 08:10:17 UTC
Commit was not confirmed; automatic
rollback complete.

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 40

The commit confirmed Command

Are you among those of us who have made the mistake of adding security to a remote device, only to
discover that the security configuration changes you made locked you out of the very interface that
you were using to access the device? Do you have a story about the time you accidently isolated a
remote device and then had to jump in the car and drive two-and-
a-half hours in the middle of the night just to reset it? The commit confirmed command can prevent
costly configuration mistakes by automatically rolling back problematic configurations.
The commit confirmed command commits a candidate configuration for 10 minutes (this is the default time
setting).
Then if you do not follow up with a second commit within that time period, the device automatically
rolls back to the previous configuration. You can use the commit confirmed command anytime you
want a safety net against potential configuration problems.
If you do not confirm the configuration by entering a second commit command, the CLI will roll back
the device to the previous active configuration at the end of the 10 minutes (or an interval you
specify). In this way, if you have accidently isolated the device, you simply need to wait for the
rollback instead of agonizing over how you are going to otherwise undo your mistake.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 42

 Junos Configuration Basics

Slide 41

The rollback Command

 Use rollback (or rollback 0 ) to

reset the candidate configuration to the
currently active configuration
• rollback 1 loads the previously active
configuration
• rollback n loads the nth previous active
configuration
• rollback rescue loads the previously
created rescue file
 rollback only modifies the candidate
configuration
•Don’t forget to commit the changes!
[edit]
mike@host# rollback
load complete

[edit]
mike@host# commit
commit complete

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 41

The rollback Command

Whenever you commit the candidate as the new active configuration, the Junos OS automatically saves
a copy of the active configuration file that is being replaced. As you store each newly replaced
configuration, all the prior configuration files move back one version number further in the configuration
archive. Each device can store up to 50 of the most recently active versions. This number includes the
current active configuration (also known as rollback 0). You can access this
configuration archive using the rollback command.
You can reset your candidate configuration to match the active running configuration by entering rollback or
rollback
0.
You can also return to the most recent previous active configuration file by using the rollback 1
command, or use any other number between 2 and 49 to go back to any of the previous
configurations.
The rollback command loads the requested archive as the candidate file. You can also create a rescue
configuration of a known working configuration so that you can rollback to it when all else fails.

If you want to use a rollback file you will need to commit the configuration. First, use the show command to view the
file so
you can be sure it is what you want. Then activate the file with the commit command. This is a
very important step—to complete a rollback for the active configuration of the device, you must
run the commit command to activate it.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 43

 Junos Configuration Basics

Slide 42

Preparing Changes in Advance

 Prepare for hardware being installed at a later

date:
[edit]
mike@jnpr1# edit interfaces fe-3/0/0 unit 0

[edit interfaces fe-3/0/0 unit 0]

mike@jnpr1# set family inet address 192.168.1.254/24

 Make changes during a maintenance window:

[edit]
mike@jnpr1# commit at 02:00:00
commit check succeeds
commit will be executed at 2009-02-02 02:00:00
UTC Exiting configuration mode
mike@jnpr1>

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL

SSFJUN02A-ML5 www.juniper.net | 42

Preparing Changes in
Advance
Unlike other systems, the Junos OS lets you prepare for an installation before actually installing the
hardware. The software simply ignores the areas of the running configuration which are irrelevant to
the existing hardware installation. Those areas of the running configuration will become active once
the hardware becomes available.
The option to set up a configuration prior to hardware installation is quite useful, especially when the
person installing the hardware is different than the person configuring the device, a common
occurrence for remote devices. At the top of this slide we show a configuration for fe-3/0/0, which will
be installed at a later date. Nevertheless, the configuration statement is the same. The settings will
simply be ignored until the hardware is installed. Then the setting will become active.
You can also schedule when you want your candidate configuration to become active. To save Junos
OS configuration
changes
mode and activate
command, thereboot
specifying configuration
or a future on the
time at device
the at a future time
hierarchy or as
level, upon reboot,
shown useexample
in the the at
commit
[edit] at configuration the bottom
of this slide.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 44

 Junos Configuration Basics

Slide 43

Commands That Save Time

 copy defines a new element by duplicating
a selected configuration statement and its
subordinate elements
[edit interfaces]
mike@jnpr1# copy se-0/0/2 to se-0/0/1

edit interfaces]
mike@jnpr1# delete se-0/0/1 unit 0 family inet address 10.0.22.1/24

•Then make any changes to the new element (if

needed)
[edit interfaces]
mike@jnpr1# set se-0/0/1 unit 0 family inet address 10.0.36.2/24

 rename changes the value of a user-defined

variable or the name to a user-defined
element
[edit interfaces]
mike@jnpr1# rename se-0/0/1 unit 0 family inet address 10.0.22.1/24 to
address 10.0.36.2/24

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 43

Commands That Save

Time
A typical configuration includes many similar elements named and defined by the user, such as
interface names, policy statements, and firewall filters. The Junos CLI includes commands to
duplicate and quickly change the configurations of these user-defined variables.

The copy command duplicates a configuration statement along with all the subordinate statements configured
underneath it. In using the copy command, you copy the configuration associated with one user-
defined element to a new, similarly configured element. You can then modify that second element with
any needed changes. Copying statements is useful when you are configuring many physical or logical
interfaces of the same type.
The rename command is a convenient shortcut when you need to alter the value of a user-defined
variable—such as policy names, filter names, and IP addresses—or to change the name of a user-
defined element.
The examples on this slide illustrate a very useful technique for configuring similar interfaces, where
only IP addresses are
different. First, you create an identical configuration of se-0/0/1 based on the se-0/0/2 interface using
the copy
command. Then, you change the IP address of the newly created se-0/0/1 interface by deleting the IP
address of the copied
se-0/0/2 interface and setting the IP address for the se-0/0/1 interface, which is 10.0.36.2/24 in the
example shown on this slide. You could also use the rename command to change the IP address of
the newly created interface, thereby achieving the same result, as shown in the bottom example on
this slide.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 45

 Junos Configuration Basics

Slide 44

Using the Pipe Symbol

 Use the pipe symbol “|” to filter output

in both operational and configuration
mode
 Sends output of one command as input
to another
 Examples:
•Use pipe to redirect output of a command to
a file
• Useful for re-using sections of configurations
across many devices
mike@jnpr1> request support information | save <filename>
Wrote 1143 lines of output to ’filename‘

• | count: gives the number of lines in the

output
mike@jnpr1> show interfaces terse | count
Count: 22 lines

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

Using the Pipe www.juniper.net | 44

Symbol
The pipe symbol lets you filter output in both operational and configuration modes. Pipe makes it
possible to achieve results such as: displaying specific information in a single command step, sending
the output of one command as input to another, or redirecting the output to a file, to name a few
examples. The output of the command to the left of the pipe symbol serves as input to the command or
file to the right of the pipe.
The first example shown on this slide creates a file that stores the output of the request support information
command entered in operational mode by piping its output to a filename specified by the user.

In the second example on this slide, the pipe symbol, followed by count, counts the number of lines in the
output.
These are only a few of the examples of what the pipe
symbol can do.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 46

 Junos Configuration Basics

Slide 45

The run
Command

 Issue operational mode commands

while in configuration mode using
run
[edit]
mike@jnpr1# run show interfaces
Physical interface: fe-4/0/2, Enabled, Physical link is Up
Interface index: 137, SNMP ifIndex: 29
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps,
Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags : Present Running
Interface flags: SNMP-Traps 16384
Link flags : 4
CoS queues : 8 supported

<...OUTPUT TRIMMED...>

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL

SSFJUN02A-ML5 www.juniper.net | 45

The run Command

The run command lets you issue CLI operational mode commands while in configuration mode. Just add the keyword
run
before any operational mode command that you want to execute while you are inside configuration
mode.
As shown in the example on the slide, entering the run show interfaces command displays the output as if show
interfaces had been entered from operational mode. The example on this slide shows an
abbreviated listing of the output.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 47

 Junos Configuration Basics

Slide 46

Junos OS System Health: Monitoring

 Real-time Performance Monitoring (RPM)

•Active probes to monitor performance
•Per-destination and per-application basis
 Flow accounting
•cflowd and rich filtering
•Active monitoring, passive
monitoring, port mirroring
 Health monitor
•Extends the Remote Network
Monitoring
alarm infrastructure with minimum user
configuration

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 46

Junos OS System Health:

Monitoring
Juniper devices provide extensive on-board instrumentation that enables customers to proactively
gather status
information. Self-monitoring allows continuous feedback and lets administrators capture information
network-wide, down to highly granular perspectives on the operations of the network. Junos OS-based
platforms come with sufficient processing power to collect and store critical operational data that help
you to understand how a device operates in normal conditions and where, when, and why changes
occur.
Available tools for automating network monitoring include
•the Real-time
following: performance monitoring (RPM) measures the performance of traffic as it travels
between network devices. The RPM probes can collect round-trip time minimums, averages,
maximums, jitter, and other data on both a per- destination and per-application basis.
• Flow accounting provides a method for collecting traffic flow statistics, enabling operations teams
to track link utilization for capacity planning, security analysis, fault isolation, internal billing, and
more. You can gather statistics on an individual physical device, logical device, interface, or sub-
• interface.
Health monitor notifies your network management system (NMS) when something requires
attention. Health monitor extends the Remote Network Monitoring (RMON) alarm infrastructure of
the Junos OS with minimum user configuration requirements by providing predefined monitoring of
the operating system processes and device hardware—for example: file system usage, CPU usage,
and memory usage.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 48

 Junos Configuration Basics

Slide 47

Junos OS System Health: Diagnostics

 System logging to record device events

•Hardware events
•Operating system events
 Trace logging (traceoptions)
to flag events specific to
operations
•Protocol operations
•SNMP operations
•Other device operations

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL

SSFJUN02A-ML5 www.juniper.net | 47

Junos OS System Health:

Diagnostics
The logging and tracing operations of the Junos OS allow administrators to find out about events that
occur in the device—
normal operations, as well as error conditions.
You can use the following tools to discover, trace, and analyze the sequence of events leading to
network or device issues for fast resolution:
• System logging generates system log messages (syslog messages) for recording events that occur on
the device, including hardware and within the processes of the operating system. A few examples,
among the thousands that we can cite: an interface starting up, login failure, or hardware failure
• conditions.
Trace logging (also called traceoptions) provides a wide range of variables for observing network
and system events specific to operations, such as protocol operations. Note that traceoptions is
similar to the debug function in IOS. Examples of trace logging include BGP state changes, graceful
restart events, and even tracking SNMP operations and statistics. Trace logging is a valuable tool
when you need to find out what is going on in your device.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 49

 Junos Configuration Basics

Slide 48

Junos Automates the Network

Automation API Service Automation Application
Automation

Junos Automation Juniper Care

Junos Space

XML
Configuratio
n

Actions
ACTIVE

Proactive Network
bug
Service Director:
On-Box thorough automated
end-Insight: data center
Automation: impact switches/routers
notifications
analysis and
management application
Puppe Service
enables
that
t Management of
Chef
Now:campus and administration
Automated …and many other easy-
Pytho that enables
n Juniper of-life/end-of-support to-use
Commit/Op/Event Scripts/Macros management for various
Per resolve a
domains
l Security Director: problem in
environme
SLAX networ scalable and
Off-Box Automation:
(Juise) nts
k
responsive security

improves security policy

Ansible troubleshooting client
Ruby to quickly identify and applications to optimize network

Java the customer's in service provider and enterprise

Junos Automates the CONFIDENTIAL

© 2017 Juniper Networks, Inc. All rights reserved.
| 48
SSFJUN02A-ML5 www.juniper.net

Network
Junos automation consists of a suite of tools used to automate operational and configuration tasks on
network devices running the Junos OS. The Junos automation tool kit is part of the standard Junos OS
available on all switches, routers, and security devices running Junos OS. Junos automation tools for on-
box automation, which leverage the native XML capabilities of the Junos OS, include commit scripts,
operational scripts (op scripts), event policies and scripts, and macros.
Junos automation simplifies complex configurations and reduces potential configuration errors. It saves
time by automating operational and configuration tasks. It also speeds troubleshooting and maximizes
network uptime by warning of potential problems and automatically responding to system events.

Junos automation can capture the knowledge and expertise of experienced network operators and
administrators and allow a business to leverage this combined expertise across the organization.

Where a Juniper Networks product does not provide an essential functionality in the creation or
monitoring of a robust automated network service, the Junos OS enables an interface, protocol, or API,
or adds a third-party client to integrate with a best-in-class product.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 50

 Junos Configuration Basics

Slide 49

Lab 2: Configuring the Junos OS

Using the CLI
• Explore the Junos OS CLI • Save, view, and
use a rescue configuration mode
configuration

https://
virtuallabs.juniper.net/

Upon completing the lab, return to this

presentation and click the Play button
( ) to proceed.
© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 49

Lab 2: Configuring the Junos OS Using

the CLI
In this lab, you
will:• Explore the Junos OS CLI configuration
• mode; and
Save, view, and use a rescue
configuration.
At this point, you should return to the Virtual Lab session you opened previously and complete the lab
portion of this section. When you are finished, return to this presentation and continue.

Enter Virtual Lab:

https://
virtuallabs.juniper.net/

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 51

 Junos Configuration Basics

Slide 50

Section Summary

 In this section, we:

•Presented and demonstrated the Junos OS
configuration process and its multiple
safeguards
•Highlighted some key Junos OS CLI commands
•Discussed features and commands of the Junos OS
CLI that can be used to save time, automate
operations, and monitor the network

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 50

In this section,
•we: Presented and demonstrated the Junos OS configuration process and its multiple safeguards;
• Highlighted some key Junos OS CLI commands; and
• Discussed features and commands of the Junos OS CLI that can be used to save time,
automate operations, and monitor the network.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 52

 Junos Configuration Basics

Slide 51

Learning Activity 2:Quiz

Question 1
Click the Quiz button

True or False: As soon as you edit the
to edit this object
configuration file and press “Enter” the
changes are implemented on your Junos OS
device.

A. True
B. False

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 51

Learning Activity 2:
Question 1
True or False: As soon as you edit the configuration file and press “Enter” the changes are
implemented on your Junos OS
device.
• True
•
False
That’s correct.
In the Junos OS, configuration changes are not activated every time you press Enter. Configuration
changes are made to a candidate configuration and are not activated until the user is ready to
commit the configuration.
That’s incorrect. The statement is false.
In the Junos OS, configuration changes are not activated every time you press Enter. Configuration
changes are made to a candidate configuration and are not activated until the user is ready to
commit the configuration.
Learning Activity 2:
Question 2
What is the purpose of configure private mode?

• Limits the impact of configuration changes to the local

• system
• Creates your own copy of the candidate configuration
• Prohibits others from making changes to the
configuration Produces a second copy of the
configuration
That’s correct. for testing purposes
In configure private mode, the device keeps a separate candidate copy, which holds only the
changes made by the private user.

That’s incorrect. The correct option is B.

In configure private mode, the device keeps a separate candidate copy, which holds only the
changes made by the private user.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 53

 Junos Configuration Basics

Slide 52

Junos Configuration Basics

Junos OS Routing

© 2017 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential

Junos OS
Routing

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 55

 Junos Configuration Basics

Slide 53

Section Objectives

 After completing this section, you will be able

to:
•Discuss routing and forwarding tables
•Describe routing instances
•Explore static routing and its configuration using the
Junos OS
•Describe dynamic routing

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 53

After completing this section, you will be

•able to:
Discuss routing and forwarding tables;
• Describe routing instances;
• Explore static routing and its configuration using the
• Junos OS; and
Describe dynamic routing.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 56

 Junos Configuration Basics

Slide 54

A Basic Definition of Routing

 The process of moving data between Layer 3

networks

Server
Server
A
B

Interne
t Legend

Data
User
User A Center
B

Router

Switch

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 54

A Basic Definition of
Routing
Routing, in its most basic form, is the process of moving data between Layer 3 networks. The sample
topology on shown on this slide consists of several Layer 3 networks, all connected by routers. Although
routers are the most common devices for performing routing operations, note that many switches and
security devices also perform routing operations. Note also that the Internet is actually a collection of
many networks rather than a single network.
In this section, we will look at the required components of routing, and how devices running the
Junos OS make routing decisions.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 57

 Junos Configuration Basics

Slide 55

The Components of
Routing

 For a device to communicate with another

device in a remote network, the following
requirements exist:
•End-to-end communications path
•Routing information on participating Layer 3
devices Network
2

Legend
Internet
Network 1
gatewa Data
User
y Center
B
User A

Route

r device
Switc
h

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net | 55

The Components of
Routing
There are several components and concerns you need to consider to effectively implement routing
between remote networks. However, you can classify the various components and considerations into
two primary requirements—an end-to- end communications path and ensuring all Layer 3 devices
within the communications path have the required routing information.

In the example shown on this slide, you can see that a physical path exists between the two networks
and the Internet. As long as the physical path is configured and functioning correctly, the first
requirement is satisfied.
For the second requirement, all Layer 3 devices participating in the communications path must have the
necessary routing information. The devices within the networks must have the proper gateway
configured (the router that connects to those networks as well as the Internet). The gateway device
must determine the proper next hop for each destination prefix for the transit traffic it receives. Devices
running the Junos OS use the forwarding table, which is a subset of information found in the routing
table, to make this determination.
We discuss the routing and forwarding
tables next.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 58

 Junos Configuration Basics

Slide 56

The Routing Table

 Compiles information learned from routing

protocols and other routing information
sources
 Selects an active route to each destination
 Populates the forwarding table
 Main unicast routing tables are inet.0,
for IPv4 routing, and inet6.0, for IPv6
routing
databas
es
Routing
protocol table table
Other OSPF
routing
Routing
source Forwarding
s
information Direct Static

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 56

The Routing
Table
The Junos OS routing table consolidates prefixes from multiple routing information sources
including various routing protocols, static routes, and directly connected routes.

Active Route Selection

When a device running the Junos OS receives multiple routes for a given prefix, it selects a single
route as the active route. With additional configuration, the Junos OS can support multiple, equal-cost
routes.
Forwarding Table
The router uses the active route for each destination prefix to populate the forwarding table. The
forwarding table determines the outgoing interface and Layer 2 rewrite information for each packet
forwarded by a device running the Junos OS.

Multiple Routing Tables

Devices running the Junos OS can accommodate multiple routing tables. The primary routing table,
inet.0, stores IPv4 unicast routes. Additional predefined routing tables exist, such as inet6.0, which the
Junos OS creates when required by the configuration.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 59

 Junos Configuration Basics

Slide 57

Predefined Routing
Tables

 The following is a summary of the common

predefined routing tables you might see on a
device running the Junos OS:
• inet.0: Used for IPv4 unicast routes
• inet.1: Used for the multicast forwarding cache
• inet.2: Used for MBGP routes to provide
reverse path forwarding (RPF) checks
• inet.3: Used for MPLS path information
• inet.4: Used for MSDP route entries
• inet6.0: Used for IPv6 unicast routes
• mpls.0: Used for MPLS next hops

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 57

Predefined Routing
Tables
The slide provides a summary of the common predefined routing tables you might see on a device
running the Junos OS.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 60

 Junos Configuration Basics

Slide 58

Route Preference

 Ranks routes received from different sources

 Used as the primary criterion for
selecting the active route
•Used as a tiebreaker when same destination
prefix is available through multiple sources
Route Preference
Values
Routing Information Source Default
Preference
Direct 0
More Preferred

Local
0
Static
5
OSPF internal
10
RIP
100
OSPF AS external
150
BGP (both EBGP and IBGP) 170
Less Preferred
Route CONFIDENTIAL
© 2017 Juniper Networks, Inc. All rights reserved. SSFJUN02A-ML5 www.juniper.net

Preference | 58

The Junos OS uses route preference to differentiate routes received from different routing protocols or
routing information sources. Route preference is equivalent to administrative distance on equipment
from other vendors such as Cisco.
Selecting the Active Route
The Junos OS uses route preference to rank routes received through the various route information
sources and as the primary criterion for selecting the active route. The table at the bottom of this slide
shows the default preference values for a selected set of routing information sources. Any of these
default values can be changed.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 61

 Junos Configuration Basics

Slide 59

Viewing the Routing Table

 Use show route to display routing table
contents
user@host>
inet.0: show route

6 destinations, 7 routes (6 active, 0 holddown, 0 hidden)

+ = Active Route, - [Static/5]
= Last Active, * = Both
> to 172.29.30.253 via ge-0/0/10.0
10.1.1.0/24 * 00:10:24
[OSPF/10] Route
source and preference
00:03:38, metric 2
> to 172.18.25.2 via ge-
0/0/13.0
172.18.25.0/30 *[Direct/0] 00:11:05
> via ge-0/0/13.0
172.18.25.1/32 **[Local/0] 00:11:05
Asterisk (*) indicates he
Local
Local via
via ge-0/0/13.0
ge-0/0/10.0 that t
172.29.30.0/24 *[Direct/0] 00:11:05
> via ge-0/0/10.0
172.29.30.1/32 [Local/0] 00:11:05

…
route is selected as active

Route table name

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 59

Viewing the Routing

Table
This slide shows the use of the show route command, which displays all route entries in the routing table. As
on the slide, all active routes areidentified
marked with an asterisk (*) next to the selected entry. Each route
entry displays the source from which the device learned the route, along with the route preference for
that source.
The show route command displays a summary of active, holddown, and hidden routes. Active routes
are the routes the system uses to forward traffic. Holddown routes are routes that are in a pending
state before the system declares them as inactive. Hidden routes are routes that the system cannot
use for reasons such as an invalid next-hop and route policy.
You can also filter the output by destination prefix, protocol type, and other
distinguishing attributes.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 62

 Junos Configuration Basics

Slide 60

The Forwarding Table

 Stores required information for packet

forwarding operation
•Contents include the destination prefixes
and the associated outgoing interfaces
•Use show route forwarding-table to
view contents

Routing
protocol
databas OSPF
es Routing Forwardi
n
ng
table
Other routing
table
source
s
information Direct Static

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 60

The Forwarding
Table
The forwarding table stores a subset of information from the routing table. Within the forwarding table,
you can find the details used by a device running the Junos OS to forward packets such as the learned
destination prefixes and the outgoing
interfaces associated with each destination prefix. You use the show route forwarding-table CLI
command to view the forwarding table contents.
Note that the Junos OS kernel adds some forwarding entries and considers them permanent in nature.
One such example is the default forwarding entry, which matches all packets when no other matching
entry exists. When a packet matches this default forwarding entry, the device discards the packet and
sends an ICMP destination unreachable message back to the sender. If you configured a user-defined
default route, it will be used by the device instead of the permanent default forwarding entry.

The following are some examples of

forwarding
• Remoteentries:
addresses directly reachable through an interface;
• Routes installed by the kernel when the routing table initializes;
• Routes installed by the routing protocol process or as a result of the
• configuration; and
The local address on an interface.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 63

 Junos Configuration Basics

Slide 61

Determining the Next Hop

 Device compares incoming packets

against forwarding table entries to
determine appropriate next hop
•If multiple matches exist, it uses the most
specific entry
(longest match) to forward packet toward
destination
•If no matching entry exists, it sends a
destination unreachable notification
back to source device

Forwarding
Plane

FT
Packets in
Packets out

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 61

Determining the Next

Hop
When a packet enters a device running the Junos OS, it compares that packet against the entries within
the forwarding table to determine the proper next hop. If the packet is destined to the local device, the
Junos OS processes the packet locally. If the packet is destined to a remote device and a valid entry
exists, the device running the Junos OS forwards the packet out the next-hop interface associated with
the forwarding table entry.
If multiple destination prefixes match the packet’s destination, the Junos OS uses the most
specific entry (also called
longest match) when forwarding the packet to its destination.
In situations where no matching entry exists, the device running the Junos OS responds to the
source device with a destination unreachable notification.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 64

 Junos Configuration Basics

Slide 62

Overview of Routing Instances

 A routing instance is a unique collection of

routing tables, interfaces, and routing
protocol parameters
 A single device can effectively imitate multiple
devices

Device Running the Junos

OS
Routing instance (master) Routing instance (cust-A)
Routing instance (cust-B)
inet.0 cust-A.inet.0 cust-B.inet.0
inet6.0 cust-A.inet6.0 cust-B.inet6.0
ge-0/0/0.0 ge-0/0/3.0 ge-1/0/0.0
ge-0/0/1.0 ge-0/0/4.0 ge-1/0/1.0
lo0.0 lo0.1 lo0.2
Default Route Default Route
Default Route
OSPF OSPF
OSPF

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net

Overview of Routing | 62

Instances
The Junos OS logically groups routing tables, interfaces, and routing protocol parameters to form
unique routing instances. The device logically keeps the routing information in one routing instance
apart from all other routing instances. The use of routing instances introduces great flexibility because
a single device can effectively imitate multiple devices.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 65

 Junos Configuration Basics

Slide 63

Default Routing Instance

 The master routing instance is the primary

instance for all devices running Junos OS
and includes inet.0 route table
•Might include other route tables, such as inet6.0
user@host> show route instance
Instance Type
Primary RIB Active/holddown/hidden
forwarding
master
3/0/1
inet.0
4/0/0
inet6.0
…
Participating route tables; the presence of
Routing instance name
inet6.0 table indicates IPv6 is in use

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 63

Default Routing
Instance
The Junos OS creates a default unicast routing instance called the master routing instance. By default,
the master routing instance includes the inet.0 route table, which the device uses for IPv4 unicast
routing. The software creates other route tables, such as inet6.0, adds them to their respective
routing instance, and displays them when required by the configuration.

The Junos OS also creates private routing instances, which the device uses for internal communications
between hardware components. You can safely ignore these instances and their related information
when planning your network.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 66

 Junos Configuration Basics

Slide 64

User-Defined Routing Instances

 You configure user-defined routing instances at

the
[edit routing-instances] hierarchy level
•Typically used for filter-based forwarding, VPN
services, and system virtualization
•Routing instance types include:
[edit routing-instances <instance-name>]
user@host# set instance-type ?
Possible completions:
forwarding Forwarding instance
l2vpn Layer 2 VPN routing instance
no-forwarding Nonforwarding instance
virtual-router Virtual routing instance
vpls VPLS routing instance
vrf Virtual routing forwarding
instance

Note: Actual routing instance types vary

between platforms running the
Junos OS; Check product documentation for actual
support

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 64

User-Defined Routing
Instances
For added flexibility, the Junos OS allows you to configure additional routing instances under the routing-
instances]
[edit hierarchy. User-defined routing instances can be used for a variety of different situations
and provide users a great amount of flexibility in their respective environments.

We also commonly refer to filter-based forwarding (FBF) as policy-based routing (PBR). Some typical
uses for user-defined routing instances include filter-based forwarding (FBF), Layer 2 and Layer 3 VPN
services, and system virtualization.
The following are some of the common routing
instance types: Used to implement filter-based forwarding for common Access
• forwarding:
• Layer applications;
• l2vpn: Used in Layer 2 VPN implementations;
• no-forwarding: Used to separate large networks into smaller administrative
• entities;
• virtual-router: Used for non-VPN-related applications such as system
virtualization;
Notevpls:
thatUsed for point-to-multipoint
the actual routing instance LAN implementations
types between running
vary between platforms a set of the
sitesJunos OS. Be sure to
in athe
check VPN; and
technical documentation for your specific product.
vrf: Used in Layer 3 VPN implementations.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 67

 Junos Configuration Basics

Slide 65

Routing Instances Configuration Example

 Routing instance configuration example:

[edit routing-instances new-instance] Routing instance name is user-defined
user@host# show
instance-type virtual-router; Routing instance type
interface ge-0/0/0.0;
interface ge-0/0/1.0; Define interfaces under the
[edit interface lo0.1; interfaces] hierarchy and
reference routing-options { them under the routing
instance
static {

route 0.0.0.0/0 next-hop 172.26.25.1;

}
}
protocols {
ospf {
ar
ea
0.
0.
0.
0
{
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface lo0.1;
}
}
}

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 65

Routing Instances Configuration

Example
This slide illustrates a basic routing instance configuration example and points out some of the
highlights. Note that the routing instance name is user-defined.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 68

 Junos Configuration Basics

Slide 66

Working with Routing Instances (1 of

2)

 Reference the corresponding IP unicast

table for a given instance to view the
route table contents:
user@host> show route table new-instance.inet.0

new-instance.inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 02:06:18

> to 172.26.25.1 via ge-0/0/0.0
172.26.25.0/24
172.25.182.0/24 *[Direct/0]02:06:18
*[Direct/0] 02:06:18 routing instance
> via ge-0/0/1.0 The software automatically
creates
172.25.182.5/32 *[Local/0] 02:06:18 the IP unicast table when you
Local via ge-0/0/1.0 configure the corresponding

> via ge-0/0/0.0

172.26.25.5/32 *[Local/0] 02:06:18
Local via ge-0/0/0.0
192.168.100.52/32 *[Direct/0] 02:06:18
> via lo0.1
…

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 66

Working with Routing Instances:

Part 1
Once you configure a routing instance and the device learns routing information within the instance,
the Junos OS automatically generates a route table. If you use IPv4 routing, the software creates an
IPv4 unicast routing table. The name of the IPv4 unicast route table uses the format instance-
name.inet.0, where instance-name is the name of the routing instance within the configuration.
Likewise, if you use IPv6 within the instance, the software creates an IPv6 unicast routing table and it
follows the format instance-name.inet6.0.
As illustrated on this slide, to view a routing table associated with a specific routing instance, you simply use the
route
show table table-name CLI command.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 69

 Junos Configuration Basics

Slide 67

Working with Routing Instances (2 of

2)

 Reference the routing instance name

when viewing information for a given
instance or sourcing traffic from a given
instance
user@host> show interfaces terse routing-instance new-instance
Interface Admin Link Proto Local Remote
ge-0/0/0.0 up up inet 172.26.25.5/24
ge-0/0/1.0 up up inet 172.25.182.5/24
lo0.1 up up inet 192.168.100.52 --> 0/0

user@host> ping 172.26.25.1 rapid count 25 routing-instance new-instance

PING 172.26.25.1 (172.26.25.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!
--- 172.26.25.1 ping statistics ---
25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.014/1.875/2.073/0.285 ms

user@host> traceroute 192.168.100.25 routing-instance new-

instance
traceroute to 192.168.100.25 (192.168.100.25), 30 hops max,
40 byte packets
1 192.168.100.25 (192.168.100.25) 4.536 ms 4.503 ms
2.209 ms

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 67

Working with Routing Instances:

Part 2
You can filter many of the common outputs generated through CLI show commands by referencing the
name of a given routing instance. The first example shown on this slide shows a practical way of
viewing interfaces that belong to a specific routing instance.

You can also source traffic from a specific routing instance by referencing the name of the desired
routing instance. The last
two examples on this slide show this option in action with the ping and traceroute utilities.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 70

 Junos Configuration Basics

Slide 68

Static Routes

 Manually configured routes added to routing

table
•Defined under [edit routing-options] hierarchy
 Require a valid next hop
•Typically the IP address of a directly connected
device; other options exist such as the bit bucket
(discard
Network or reject) Internet
A
172.29.100.0/24
ge-0/0/1 192.168.63.14
.1 .2 .1

172.30.25.0/30

user@host> show route 192.168.63.14

0.0.0.0/0
inet.0: 4 destinations,[Static/5]
4 routes (4
active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * =
Both

* 01:09:34

Default static route

> to 172.30.25.1 via ge-0/0/1.0

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 68

Static
Routes
Static routes are used in a networking environment for multiple purposes, including a default route
for the autonomous system (AS) and as routes to customer networks. Unlike dynamic routing
protocols, you manually configure the routing information provided by static routes on each router or
multilayer switch in the network. All configuration for static routes
occurs at the [edit routing-options] level of the hierarchy.
Static routes must have a valid next-hop defined. Often, that next-hop value is the IP address of the
neighboring router headed toward the ultimate destination. On point-to-point interfaces, you can
specify the egress interface name rather than the IP address of the remote device. Another possibility is
that the next-hop value is the bit bucket. This phrase is analogous to dropping the packet off the
network. Within the Junos OS, the way to represent the dropping of packets is with the
keywords reject or discard. Both options drop the packet from the network. The difference between
them is in the action the device running the Junos OS takes after the drop action. If you specify reject
as the next-hop value, the system sends an ICMP message (the network unreachable message) back to
the source of the IP packet. If you specify discard
as the
By next-hop
default, value, the
the next-hop IP system
addressdoes not send
of static back
routes an ICMPinmessage,
configured the Junosthe
OSsystem just
must be drops the
reachable
packeta silently.
using direct route. Unlike with software from other vendors, the Junos OS does not perform
recursive lookups of next hops by default.
Static routes remain in the routing table until you remove them or until they become inactive. One
possible scenario in which a static route becomes inactive is when the IP address used as the next hop
becomes unreachable.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 71

 Junos Configuration Basics

Slide 69

Configuring Static Routing

 Static route configuration example:

[edit routing-options]
user@host# show
rib inet6.0 {
static {
route 0::/0 next-hop 3001::1; IPv6 default static route
}
}
static {
route 0.0.0.0/0 next-hop 172.30.25.1; IPv4 default static route
route 172.28.102.0/24 {
next-hop 10.210.11.190;
no-readvertise;
}
}
no-readvertize: Restricts route from
being advertised into a routing protocol
through routing policy, highly suggested
for static routes used for management
traffic

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 69

Configuring Static
Routing
This slide illustrates the basic configuration syntax for IPv4 and IPv6 static routes. The slide also highlights the no-
readvertise option which prohibits the redistribution of the associated route through routing policy
into a dynamic routing protocol such as OSPF. We highly suggest that you use the no-readvertise
option on static routes that direct traffic out the management Ethernet interface and through the
management network.
Note that IPv6 support varies between Junos OS platforms. Be sure to check the technical
documentation for your specific product for support information.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 72

 Junos Configuration Basics

Slide 70

Monitoring Static
Routing

 Monitoring
•Use show route protocol static to
display static routes
user@host> show route protocol static

inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

+ =0.0.0.0/0
Active Route, - = *[Static/5]
Last Active,00:41:59
* = Both
Route source and
preference

> to 172.30.25.1 via ge-0/0/1.0

Default static route Next-hop
…
interface and IP address

•Use the ping utility to verify end-to-end

!!!!!!!!!!!!!!!!!!!!!!!!! Test confirms reachability

reachability:
user@host> ping 192.168.63.14 rapid count 25
PING 192.168.63.14 (192.168.63.14): 56 data bytes

--- 192.168.63.14 ping statistics ---

25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.027/0.057/0.145/0.032 ms

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 70

Monitoring Static
Routing
This slide shows the basic verification steps when determining proper operation of static routing. Use the route
protocol static command to display static routes. The ping utility can be used to
show
verify reachability.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 73

 Junos Configuration Basics

Slide 71

Next-Hop Resolution

 Resolving indirect next hops:

•By default, the software can resolve only directly
connected next hops
•Use the resolve option to allow resolution of
indirectly connected next-hops:
Host-A Host-B Host-C
.1 .2 .5 .6 .1

172.25.1.0/30 172.25.1.4/30 172.20.3.0/24

[edit routing-options]
user@Host-A# show Indirect next-hop
static {
route 172.20.3.0/24 {
next-hop 172.25.1.6;
resolve; resolve option required
}
}

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL
SSFJUN02A-ML5 www.juniper.net | 71

Next-Hop
Resolution
By default, the Junos OS requires that the next-hop IP address of static routes be reachable using a
direct route. Unlike software from other vendors, the Junos OS does not perform recursive lookups
of next hops by default.
As illustrated on this slide, you can alter the default next-hop resolution behavior using the resolve CLI option. In
addition
to the resolve CLI option, a route to the indirect next-hop is also required. Indirect next-hops can be
resolved through another static route or through a dynamic routing protocol. We recommend,
whenever possible, that you use a dynamic routing protocol as your method of resolution. Using a
dynamic routing protocol rather than a static route to resolve indirect next-hops, dynamically removes
the static route if the indirect next-hop becomes unavailable.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 74

 Junos Configuration Basics

Slide 72

Qualified Next-Hops
 Use qualified-next-hop to allow
independent preference for static routes to
the same destination
172.30.25.0/3
0 ge-0/0/1 Intern
Network A .2 et
primary .1
172.29.100.0/24 .1 .6 secondary
.5

se-1/0/0
172.30.25.4/30

[edit routing-options]
user@host# show qualified-next-hop Primary
next-hop due to
static { default
route} preference (5) configured route
route 0.0.0.0/0 { preference (7)
next-hop 172.30.25.1;
172.30.25.5 {
preference 7;
}
Secondary
next-hop due to

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 72

Qualified Next-
Hops
The qualified-next-hop option allows independent preferences for static routes to the same destination. This slide
shows an example using the qualified-next-hop option.

In the example configuration shown on this slide, the 172.30.25.1 next-hop assumes the default static
route preference of
5, whereas the qualified 172.30.25.5 next-hop, uses the defined route preference of 7. All traffic using
this static route uses the 172.30.25.1 next-hop unless it becomes unavailable. If the 172.30.25.1 next-
hop becomes unavailable, the device
uses the 172.30.25.5 next-hop. Some vendors refer to this implementation as a floating static route.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 75

 Junos Configuration Basics

Slide 73

Dynamic Routing

 A method of dynamically learning routing

information
 Dynamic routing has the following benefits:
•Lower administrative overhead
•Increased network availability
•Greater network scalability

Static routing
Dynamic routing

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 73

Dynamic
Routing
Static routing is ideal in small networks where only a few routes exist, or in networks where absolute
control of routing is required. However, static routing has certain drawbacks that might make it
cumbersome and hard to manage in large environments where growth and change are constant. For
large networks or networks that change regularly, dynamic routing might be the best option.

With dynamic routing, you simply configure the network interfaces to participate in a routing
protocol. Devices running routing protocols can dynamically learn routing information from each
other. When a device adds or removes routing information for a participating device, all other
devices automatically update.
Dynamic routing resolves many of the limitations and drawbacks of static routing. Some of the general
benefits of dynamic routing include the following:
• Lower administrative overhead: The device learns routing information automatically, which
eliminates the need for manual route definition;
• Increased network availability: During failure situations, dynamic routing can reroute traffic
around the failure automatically (the ability to react to failures when they occur can provide
• increased network uptime); and
Greater network scalability: The device easily manages network growth by dynamically
learning routes and calculating the best paths through a network.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 76

 Junos Configuration Basics

Slide 74

Dynamic Routing Protocols

 A summary of dynamic routing protocols:

•IGPs operate within a single autonomous system
• Single network administration that provides for
unique routing policy and flexible use of network
resources
• Examples include RIP, OSPF, and IS-IS
•EGPs operate among different autonomous
systems
• Independent administrative entities that
communicate between independent network
infrastructures IGP

• Current
IGP EGP in use today is BGP
IBGP

EBGP = External BGP

IGP
AS 65535

AS 64512 AS =
Autonomous system

AS 64513
© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 74

Dynamic Routing
Protocols
Although there are many types of routing protocols, two major categories are in widespread use in
today’s IP network—
interior gateway protocols (IGPs) and exterior gateway protocols (EGPs).
IGPs distribute routing information to routers within an autonomous system (AS). Examples include
RIP, OSPF, and IS-IS.
EGPs distribute routing information to routers that connect separate autonomous systems. BGP is the
current EGP in use today.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 77

 Junos Configuration Basics

Slide 75

OSPF Protocol

 OSPF is a link-state IGP that:

•Reliably floods link-state information to neighbors
•Creates a complete database of network
•Calculates best path to each destination
•Uses areas to incorporate hierarchy and allow for
scalability

AS 64512

Area 0.0.0.1 Area 0.0.0.0

Area 0.0.0.2

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 75

OSPF
Protocol
OSPF is a link-state routing protocol designed for use within an AS. OSPF is an IGP. Link-state
protocols allow for faster reconvergence, support larger internetworks, and are less susceptible to
bad routing information than distance-vector protocols. It is common to refer to distance-vector
protocols learning as “learning by rumor”, where a router learns about prefixes from neighboring
routers’ perspectives. Routers using link-state routing protocols learn network topology by
“propaganda”, where they learn the topology from all the routers directly.
Devices running OSPF send out information about their network links and the state of those links to
other routers in the AS. This information transmits reliably to all other routers in the AS by means of
link-state advertisements (LSAs). The other routers receive this information, and each router stores it
locally. This total set of information now contains all possible links in the network.

In addition to flooding LSAs and discovering neighbors, a third major task of the link-state routing
protocol is establishing the link-state database. The link-state (or topological) database stores the LSAs
as a series of records. The important
information for the shortest path determination process is the advertising router’s ID, its attached
networks and neighboring routers, and the cost associated with those networks or neighbors.
OSPF uses the shortest-path-first (SPF) algorithm (also called the Dijkstra algorithm) to calculate the
shortest paths to all destinations. It does this calculation by calculating a tree of shortest paths
incrementally and picking the best candidate from that tree.

OSPF uses areas to allow for a hierarchical organization and facilitate scalability. An OSPF area is a
logical group of routers. The software can summarize the routing information from an OSPF area and
the device can pass it to the rest of the
network. Areas can reduce the size of the link-state database on an individual router. Each OSPF router
maintains a
separate link-state database for each area to which it is connected. The link-state database for a given
area
To is identical
ensure correctfor all participating
routing knowledgerouters within that OSPF
and connectivity, area. maintains a special area called the
backbone area. OSPF designates the backbone area as Area 0.0.0.0. All other OSPF areas must
connect themselves to the backbone for connectivity. All data traffic between OSPF areas must
transit the backbone.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 78

 Junos Configuration Basics

Slide 76

Case Study: Objective and Topology

 Use a single OSPF area to provide

connectivity among all connected subnets
and loopback addresses; ensure that no
adjacencies are formed on interfaces
connecting to the 172.20.x.0/24 subnets
lo0: 192.168.100.1/32 lo0: 192.168.100.2/32
Host-A OSPF Area 0 Host-B

ge-0/0/2
172.25.1.0/3
ge-0/0/3 .1
172.20.1.0/24 0 .1 .2 .1

172.20.2.0/24

.10
.5

ge-0/0/1
.1
lo0: 192.168.100.3/32
.9
.6

Host-C

172.20.
3.0/24

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 76

Case Study: Objective and

Topology
Over the next several slides, we will take a look at a case study example. This slide provides the
objective and sample topology used in this case study.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 80

 Junos Configuration Basics

Slide 77

Case Study: Configuring OSPF

 Sample OSPF configuration taken from Host-A:

[edit protocols ospf]
user@Host-A# set area 0 interface ge-0/0/1.0

[edit protocols ospf]

Specify the logical interface. If
unit is not referenced, the
user@Host-A# set area 0 interface ge-0/0/2.0
Junos OS assumes unit
0

user@Host-A# set area 0 interface ge-0/0/3.0 passive Use passive option to

[edit protocols
ospf]

prohibit
adjacency [edit protocols ospf]
formation user@Host-A# set area 0 interface lo0.0

[edit
protocols ospf]
user@Host-A#
show The Junos OS converts area 0 to its
area 0.0.0.0
{ proper dotted decimal notation (0.0.0.0)
i
nterface ge-0/0/1.0;
interface ge-0/0/2.0;
interface ge-0/0/3.0 {
p
assive;
}
i
nterface
lo0.0;
}

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net | 77

Case Study: Configuring

OSPF
Note that you must include the lo0 interface if you want the associated IP address (or IP addresses)
advertised into OSPF. Prior to Junos OS Release 8.5, the IP address associated with the lo0 interface was
automatically advertised into OSPF as a router link-state advertisement (LSA).

This slide illustrates the required OSPF configuration for Host-A. Although not shown, Host-B and
Host-C require a similar
OSPF configuration to establish adjacencies and share routing information.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 81

 Junos Configuration Basics

Slide 78

Case Study: Verifying OSPF Neighbor

State
 Use show ospf neighbor to display
adjacencies
•Use detail or extensiveFulloptions for added
information Full

user@Host-A> show ospf neighbor

Address Interface State ID Pri Dead
172.25.1.9 ge-0/0/1.0 192.168.100.3 128 38
172.25.1.2 ge-0/0/2.0 192.168.100.2 128 35

The state of the adjacencies shows

Full, which means neighbors can
exchange routing information

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 78

Case Study: Verifying OSPF

Neighbor State
This slide shows the CLI command used to determine OSPF adjacencies. In the sample output on this
slide, you can see that
Host-A has formed adjacencies with both Host-B and Host-C.
The following is a description of the fields displayed in
•the Address:
output: The address of the neighbor.
• Interface: The interface through which the neighbor is reachable.
• State: The state of the neighbor, which can be Attempt, Down, Exchange, ExStart, Full, Init,
• Loading, or 2-Way.
• ID: The router ID of the neighbor.
Pri: The priority of the neighbor to become the designated router, only used on broadcast
networks during designated router elections. By default, this value is set to 128, indicating the
• highest priority, and therefore the most likely router to be elected designated router.
Dead: The number of seconds until the neighbor becomes unreachable.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 82

 Junos Configuration Basics

Slide 79

Case Study: Viewing OSPF Routes

 Use show route protocol ospf to
display
OSPF routes
user@Host-A> show route protocol ospf

inet.0: 15 destinations, 15 routes (15 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

172.20.2.0/24 *[OSPF/10] 00:03:55, metric 2

> to 172.25.1.2 via ge-0/0/2.0
172.20.3.0/24 *[OSPF/10] 00:00:04, metric 2
> to 172.25.1.9 via ge-0/0/1.0
172.25.1.4/30 *[OSPF/10] 00:03:46, metric 2
> to 172.25.1.9 via ge-0/0/1.0
to 172.25.1.2 via ge-0/0/2.0
192.168.100.2/32 *[OSPF/10] 00:03:55, metric 1
> to 172.25.1.2 via ge-0/0/2.0
192.168.100.3/32 *[OSPF/10] 00:03:46, metric 1
> to 172.25.1.9 via ge-0/0/1.0
224.0.0.5/32 *[OSPF/10] 00:16:13, metric 1
MultiRecv…

© 2017 Juniper Networks, Inc. All rights reserved.

CONFIDENTIAL SSFJUN02A-ML5
www.juniper.net | 79

Case Study: Viewing OSPF

Routes
The slide illustrates the show route protocol ospf command, which displays OSPF routes learned by Host-A. Note
that Host-A does not actually install its directly connected subnets in its route table as OSPF routes—it
installs
routes them as direct
.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 83

 Junos Configuration Basics

Slide 80

Lab 3: Configuring OSPF on Junos

OS Devices
• Configure and monitor static • Configure and
monitor OSPF
routing

https://
virtuallabs.juniper.net/

Upon completing the lab, return to this

presentation and click the Play button
( ) to proceed.
© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 80

Lab 3: Configuring OSPF on Junos OS

Devices
In this lab, you
will:• Configure and monitor static
• routing; and
Configure and monitor OSPF.
At this point, you should return to the Virtual Lab session you opened previously and complete the lab
portion of this section. When you are finished, return to this presentation and continue.

Enter Virtual Lab:

https://
virtuallabs.juniper.net/

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 84

 Junos Configuration Basics

Slide 81

Section Summary

 In this section, we:

•Discussed routing and forwarding tables
•Described routing instances
•Explored static routing and its configuration using
the Junos
OS
•Described dynamic routing

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 81

In this section,
we:
• Discussed routing and forwarding tables;
• Described routing instances;
• Explored static routing and its configuration using the
• Junos OS; and
Described dynamic routing.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 85

 Junos Configuration Basics

Slide 82

Learning Activity 3:Quiz

Question 1
Click the Quiz button

In the Junos OS, route preference is similar to
to edit this object
what
Cisco concept?
A. Administrative distance
B. Route
hierarchy
C. Destination
table
D. Routing table

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 82

Learning Activity 3:
Question 1
In the Junos OS, route preference is similar to what
Cisco concept?
• Administrative
• distance Route
• hierarchy
• Destination table
Routing table
That’s correct.
Route preference is similar to administrative distance on equipment from other
vendors, such as Cisco.
That’s incorrect. The correct option is A.
Route preference is similar to administrative distance on equipment from other
vendors, such as Cisco.
Learning Activity 3:
Question 2
What are three benefits of dynamic routing?
(Choose three.)
• Most useful for small
• networks Lower
• administrative overhead
• Increased network
availability Greater
network
That’s scalability
correct.
Three benefits of dynamic routing include lower administrative overhead, increased network
availability, and greater network scalability.

That’s incorrect. The correct options are B, C, and D.

Three benefits of dynamic routing include lower administrative overhead, increased network
availability, and greater network scalability.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 86

 Junos Configuration Basics

Slide 83

Course Summary

 In this course, we:

•Discussed the Junos OS command line interface
•Described various configuration features and
commands
•Explored routing configuration fundamentals

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 83

In this course,
we:
• Discussed the Junos OS command line interface;
• Described various configuration features and
• commands; and
Explored routing configuration fundamentals.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 88

 Junos Configuration Basics

Slide 84

Additional Resources

 Education Services training classes

•http://www.juniper.net/training/
 Juniper Networks Certification Program Web
site
•www.juniper.net/certification
 Juniper Networks documentation and white
papers
•www.juniper.net/techpubs
 To submit errata or for general questions
•[email protected]

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5 www.juniper.net
| 84

For additional resources or to contact the Juniper Networks eLearning team, click the
links on the screen.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 89

 Junos Configuration Basics

Slide 85

Evaluation and Survey

 You have reached the end of this Juniper

Networks eLearning module
 You should now return to your Juniper
Learning Center to take the assessment
and the student survey
•After successfully completing the assessment,
you will earn credits that will be recognized
through certificates and non- monetary rewards
•The survey will allow you to give feedback on the
quality and usefulness of the course

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 85

You have reached the end of this Juniper Networks eLearning module. You should now return to your
Juniper Learning Center to take the assessment and the student survey. After successfully completing
the assessment, you will earn credits that will be recognized through certificates and non-monetary
rewards. The survey will allow you to give feedback on the quality and usefulness of the course.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 90

 Junos Configuration Basics

Slide 86

Copyright © 2017 Juniper Networks, Inc.

All rights reserved. JUNIPER NETWORKS, the Juniper

Networks logo, JUNOS, QFABRIC, NETSCREEN, and
SCREENOS are registered trademarks of Juniper
Networks, Inc. in the United States and other countries.
All other trademarks, service marks, registered
trademarks, or registered service marks are the
property of their respective owners.

© 2017 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SSFJUN02A-ML5

www.juniper.net | 86

Copyright © 2017 Juniper

Networks, Inc.
All rights reserved. JUNIPER NETWORKS, the Juniper Networks logo, JUNOS, QFABRIC, NETSCREEN,
and SCREENOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. All other trademarks, service marks, registered trademarks, or registered service marks
are the property of their respective owners. Juniper Networks reserves the right to change, modify,
transfer or otherwise revise this publication without notice.

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 91

 Junos Configuration Basics

Slide 87

CONFIDENTIAL

Course SSFJUN02A-ML5 © Juniper Networks, Inc. 92

 e d u cat i o n s e r v i ce s co u rs ewa re

Corporate and Sales Headquarters APAC Headquarters EMEA Headquarters Copyright 2010 Juniper Networks, Inc. All
rights reserved. Juniper Networks, the
Juniper Networks, Inc. Juniper Networks (Hong Kong) Juniper Networks Ireland Juniper Networks logo, Junos,
1194 North Mathilda Avenue 26/F, Cityplaza One Airside Business Park NetScreen, and ScreenOS are registered
Sunnyvale, CA 94089 USA 1111 King’s Road Swords, County Dublin, Ireland trademarks of Juniper Networks, Inc. in the
Phone: 888.JUNIPER Taikoo Shing, Hong Kong Phone: 35.31.8903.600 United States and other countries. All other
(888.586.4737) Phone: 852.2332.3636 EMEA Sales: 00800.4586.4737 trademarks, service marks, registered marks,
or 408.745.2000 or registered service marks are the property
Fax: 852.2574.7803 Fax: 35.31.8903.601
Fax: 408.745.2100 ww of their respective owners. Juniper Networks
w.juniper.net assumes no responsibility for any
inaccuracies in this document. Juniper
Networks reserves the right to change,
modify, transfer, or otherwise revise this
publication without notice.