Juniper

e d u c a t io n se rv ic e s c o u rsew a re
JUNOS OPERATING SYSTEM

HIGHLIGHTS
Student Guide
Junos Operating System Highlights
Slide 1
Juniper Networks
Sales Education
2011 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential
SSFJUN01-I
Juniper Networks, Inc.
Slide 2
JUNOS OPERATING
SYSTEM HIGHLIGHTS
Welcome to Juniper Networks Junos Operating System Highlights eLearning module.
SSFJUN01-I
Slide 3
Course Agenda
Introduction to Junos OS
The Junos OS CLI
The Junos CLI Rocks!
Routing with Junos
Junos OS adoption
2011 Juniper Networks, Inc. All rights reserved.
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 3
This course consists of five sections.

The Junos OS CLI
The Junos CLI Rocks!
Routing with Junos
Junos OS adoption
SSFJUN01-I
Slide 4
Course Objectives
Upon completing this course, you will be able to:
Describe the Junos OS command-line interface (CLI)
Demonstrate specialized features of the Junos CLI that
save time and avert downtime
Describe basics of routing using Junos OS
Discuss how to ease adoption of Junos OS
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 4
Upon completing this course, you will be able to:

Describe the Junos command-line interface (CLI)
Demonstrate specialized features of the Junos CLI that save time and prevent downtime
Describe basics of routing using Junos
Discuss how to ease adoption of Junos
SSFJUN01-I
Slide 5
Junos is the network operating system that runs an increasing spectrum of the Juniper portfolio product,
ranging from switches, to routers, and to firewall products. This is what sets Juniper apart as a strategic
portfolio vendor.
SSFJUN01-I
Slide 6
Section Objectives
After successfully completing this section, you will
be able to:
Discuss the Juniper Difference

Describe the Junos OS approach
Describe control and forwarding separation
Discuss Junos OS services
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 6
After successfully completing this section, you will be able to:

Discuss the Juniper Difference
Describe the Junos OS approach
Describe control and forwarding separation
Discuss Junos OS services
SSFJUN01-I
Slide 7
Introduction
The Junos operating system is a single network operating system
integrating routing, switching, security, and services
Junos OS delivers the power of one operating system to run
high-performance networking infrastructure
The Junos OS command-line interface offers specialized features
to save time for users and prevent downtime in the network
Juniper offers customers the training, tools, and services needed
to make the adoption of Junos OS simple and safe
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 7
Much of the value, the savings, and the streamlining of operations of our products and solutions are
delivered by the Junos operating system.
With the limited amount of time that you have to talk to customers and get their interest, its important to
understand how the operating system works, how customers use it, and how you can help to ease its
adoption into their own infrastructure. When we talk about Junos, we talk about the Junos advantage
offered by the Power of One operating system.
This course is designed to share with you the highlights of the Junos advantages, focusing on its key
differences and ease of operation that would aid to lower your customers operating costs. The course
provides operational and configurational commands, illustrating the power of Junos and its ease of use.
SSFJUN01-I
Slide 8
Why Is Juniper Different?
CONFIDENTIAL
SSFJUN01G
www.juniper.net13
| 8
Juniper Networks has always thought differently about the network. Whereas our competitors have
trended towards a box-on-box, multiple operating system approach; Juniper sees that this leads to spiraling
layers of complexity in customer networks.
We have purposely driven our strategy to simplify the network through specific investment and new
development looking towards convergence. Over more than a decade Juniper has evolved Junos software
as a single, end-to-end, high-performance operating platform of the network to deliver routing, switching,
security, services and cloud. This approach in how we innovate is fundamentally different than our
competitors enabling our customers to build their networks and deliver new services in converged offerings
with simplicity of operations and reduced costs.
SSFJUN01-I
Slide 9
How Competitors Manage the Complexity
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 9
The legacy networking providers approach has been hardware oriented. Sell another box to fix another
problem. As these vendors acquire companies and add more products they are also adding more operating
systems, more proprietary software, more complexity, and more problems.
Complexity is their strategy! Theyll sell more boxes. The customer must pay for a lot of services and
support to integrate and make it all work.
But this puts the customer in a constant state of upgrading, testing, and maintaining. The operating systems
may need to be individually tailored, and it is unknown how changes, bugs, and upgrades on one box will
affect the others. More boxes get sold to attempt to fix problems, but complexity and cost increases, while
customer satisfaction decreases. The bottom line for customers? Chronic complexity management.
SSFJUN01-I
10
Slide 10
Junos: A Universal Language

A consistent user experience
A complete, layered operating platform from client to cloud
For routing, switching, security and services
Scales up and down
Open programming interfaces and automation
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 10
Junos provides a simpler approach with fewer issues. When talking about Junos to customers, partners,
etc., we need to think outside of the normal box conversation. The discussion needs to be more about
selling a solution rather than just another box. Junos software is changing the way we should be looking at
the whole network experience.
As we stated earlier, Junos is much more than an operating system; it is a simplified, common language that
provides a consistent user experience across multiple devices. With Junos you get consistent core
functionality that scales from the smallest to the largest device on the network.
It is based on open standards so it integrates seamlessly into the network, even with our competitors
products. Customers can move, over time, to a network with fewer problems and lower cost.
SSFJUN01-I
11
Slide 11
An Open Platform Approach
CONFIDENTIAL
SSFJUN01G
Thinking boxes first limits your design perspective.

Rather than being about bottoms up deployment of boxes, migrating to the open platform approach of
Junos takes customers to a new way of network design. The layered, converged platform approach of
Juniper is about looking at the network as a whole from the top-down perspective of customer needs.
Providing a platform approach based on layers of silicon, system, and software, allows Juniper to deliver a
complete solution supporting many applications. With Junipers focus on innovation in software running on
silicon and systems layers built with the headroom capacity for innovation, customers can meet many new
requirements for new services delivery through the flexibility and lower costs of software changes alone.
Moreover, Juniper opens the door to third party innovation and integration by offering a set of Junos
software development kits to partners so they can release even more value from their network.
SSFJUN01-I
12
Slide 12
Open Across Software Layers
CONFIDENTIAL
SSFJUN01G
Multiple components of the Junos software platform give developers unmatched flexibility to create
dynamic applications that interact with the network from the client to the cloud.
- In the network, the open standards, open platform approach of the operating system inspires innovation.
-Junos Space is a programmable platform for developing and running applications across the network.
-And Junos Pulse is a multi-service network client that can be used on mobile devices such as notebooks,
netbooks, and smartphones. It too is a open, programmable, platform that simplifies the end user
experience.
-Running over these platform layers is a growing portfolio of Junos Ready Software applications developed
by Juniper and third-parties.
SSFJUN01-I
13
Slide 13
Difference of One Junos
CONFIDENTIAL
SSFJUN01G
The foundational component of the Junos software platform is the Junos operating system. Running a single
operating system across devices makes the day-to-day operation of the network less complex. The IT staff
can focus on rolling out new deployments and maintaining the network, making better use of their time
and effort. With a steady release of new features and a modular architecture they have predictable
performance and the ability to streamline their tasks through automation. They can evolve their current
network infrastructure rather than adding box on top of box.
This provides a consistent user experience for the IT staff and lower costs for the customer.
SSFJUN01-I
14
Slide 14
Junos OS Separate Control and Forwarding

Supports scale for highperformance
Assures performance of each
plane
Data Plane
Provides options for

redundancy
Control Plane
Enhances resiliency
Routing
Engine
Packet
Forwarding
Engine
CONFIDENTIAL
SSFJUN01G
Lets review some of the architecture highlights whats different in the design. From the beginning the
engineers decided to separate the functions of control and forwarding. Ask yourself a question what do
routers do for living? They determine the path and then, once they know the next hop, they switch packets.
So, it makes complete logical sense to separate the function of path determination, or control, from the
function switching, or packet forwarding.
Think of control as the brains of the system. Its really what runs the protocols. The forwarding is where the
packet handling happens. Its the brawn of the system. Its whats responsible for the high throughput
taking packets, inspecting them, and moving them on quickly down the network.
So, if youre not a software engineer, why do you care about this? Well, the bottom line here is - dedicated
resources means high resiliency, which gives you that incredibly high availability that carriers rely on. So,
again, carrier class is what weve got.
SSFJUN01-I
15
Slide 15
Junos OS Modular Architecture

Independent modules
Protected Memory for stability
Kernel
...
Module n
Interfaces
Routing
Control Plane
Well-defined interfaces for

expansion of functions/
platforms
Management
No overwrites
Contain faults and enable

rapid isolation
Kernel
Controls the modules

Manages communication
between the modules and to the
PFE
CONFIDENTIAL
SSFJUN01G
A second design element to point out about the architecture is its modularity. Here we have a diagram of
the control plane and you see a group of modules responsible for different functions of the software
whether it be management or routing and each of these run as independent processes, all of which are
controlled by the underlying kernel.
Weve got dedicated resources. Because of the modular nature of these resources, if theres a problem, say,
in the routing module, it doesnt disrupt anything going on in the management or interface modules. So,
small problems dont become big ones, and that leads to really high availability and, when our engineers
want to add functionality, they do it in a modular fashion. We can roll out new features by building a new
module and putting it into this same model you see here.
Junos modular architecture allows customers to troubleshoot the problems much easier because they can
isolate whats going on in the software quicker versus other systems that are just monolithic blocks of code
where it is very difficult to understand whats going on.
SSFJUN01-I
16
Slide 16
Junos OS Services
Tailored services
flexibility
NSM
J-Web
Data Plane
Packet Forwarding
Physical Interfaces
SSFJUN01G
Service
App 2
Service
App 3
...
Services Plane
Services Interfaces
Kernel
CONFIDENTIAL
Service
App 1
Module n
Interfaces
Routing
...
NETCONF/XML
Partner development platform
Toolkit
Open Management Interfaces

Management
Open management and

development Interfaces
Scripts
CLI
Control Plane
Deep integration of new

functionality
Dedicated hardware in many
platforms
Create customized
service chains
Service
App n
Junos modularity permits very painless addition of two additional Junos design elements that are different.
First is a dedicated services plane in many platforms, such as the SRX Series Services Gateways. What this
means is that Juniper engineers are able to quickly introduce and integrate new service capabilities
whether it be bringing intrusion prevention, or Antivirus and have all of those services work together in
an integrated fashion. The next element to add is open management interfaces. Junos offers interfaces for
integrating both into our element management systems as well as some element management systems of
other vendors and other operational systems.
SSFJUN01-I
17
Slide 17
Junos Once, Junos Everywhere
CONFIDENTIAL
SSFJUN01G
So when we talk about selling Junos, we must mention that most of Junipers devices in the tool belt run
Junos. So it makes it an extremely easy sell. When we sell into the Data Center, we should be asking
questions about the customers branch office devices, or vice versa. No matter where in the network we
need devices, Juniper has the solution to fit the need, whether it be routing, security, or switching, Juniper
can do it, oh yeah and with the same operating system trans-versing from device to device. There is no
reason to learn separate operating systems as traditionally fed to network administrators for the past 40
years.
SSFJUN01-I
18
Slide 18
Section Summary
In this section, we:
Discussed the Juniper Difference

Described the Junos OS approach
Described control and forwarding separation
Discussed Junos OS services
CONFIDENTIAL
SSFJUN01G

Discussed the Juniper Difference
Described the Junos OS approach
Described control and forwarding separation
Discussed Junos OS services
SSFJUN01-I
19
Slide 19
Learning Activity 1, Question 1

Why is the Junos message important in your
sales presentations?
Platforms using Junos OS are subject to
greater discounts
b) Junos OS is capable of running competitors
routers and switches
c) The higher cost of Junos OS must be justified by
knowing its value
d) Much of the value, savings, and streamlining of
operations are delivered by Junos OS
a)
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

Why is the Junos message important in your sales presentations?
SSFJUN01-I
20
Slide 20

Junos OS runs an increasing spectrum of the
Juniper Networks portfolio, including which
three of the following?
a)
Switches
b)
Routers
c)
WAN Acceleration
d)
Firewall
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

Junos OS runs an increasing spectrum of the Juniper Networks portfolio, including which three of the
following?
SSFJUN01-I
21
Slide 21
The Junos OS CLI
Introducing the Junos CLI

This section introduces the Junos command-line interface used to configure the platforms running Junos
Software, monitor its operations, and adjust the configuration as needed.
SSFJUN01-I
22
Slide 22
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
CONFIDENTIAL
SSFJUN01G

Introduce the Junos CLI
Understand the difference between operational mode and configuration mode
Navigate the command hierarchy
Use command-line shortcuts and get help
SSFJUN01-I
23
Slide 23
Junos OS User Interface Options

1. Command-line interface
Available from the console interface
Available by using Telnet and SSH
Dedicated Ethernet management port on M Series routers

(fxp0) and EX Series switches (me0)
RJ-45 RS-232 @ 9600 Bps, 8/1/N (not configurable)

Requires network interface and related service configuration
All J Series network ports support management access and transit

traffic
2. Junos Web interface
A Web-based GUI
Perform actions available in
the command-line interface
CONFIDENTIAL
SSFJUN01G
The command-line interface (CLI) is the software interface used to access the device. One big differentiator
of Junos CLI from other CLIs in the market place is that Junos provides a rich set of new tools and
safeguards that can help your customers to efficiently manage their networks and maintain high uptime.
The material discussed in these slides is generally applicable to any device run by Junos.
You can access the CLI through either a console connection, through an out-of-band network interface, or
in-band through the network. By default, only the console connection is available for use. All other
connection methods require explicit configuration in the device.
Another option of operating and configuring a Junos device is J-Web, a powerful web-based management
interface available on Junos devices. J-Web lets you perform the actions available in the command-line
interface. It provides practical tools to monitor, configure, troubleshoot, and manage your device.
Generally to use J-Web, the user has to either manually enable http via the CLI, or through the LCD panel
externally to launch J-Web (by default J-Web is only set up on the J Series).
Additionally customers can manage platforms run by Junos with Juniper management products including
NSM.
SSFJUN01-I
24
Slide 24
CLI Login
Log in with your
username and
password
Default CLI prompt
shows:
username
device host name
user: mike
password: *******
mike@jnpr1>
CONFIDENTIAL
SSFJUN01G
To access the interface you need to connect and log in. These instructions assume that your device has
already been configured with your user name and password.
If youre using a brand-new device rather than one thats already been configured with your user name and
password, you log in as root and press enter as your password.
We use the convention of showing user input into the CLI in blue bold font
SSFJUN01-I
25
Slide 25
CLI Modes
Operational mode
Monitor and manage device operations
The > character
identifies operational
mode
mike@jnpr1>
Configuration mode
Configure the device and its interfaces
[edit]
The # character
identifies configuration
mode
mike@jnpr1#
CONFIDENTIAL
SSFJUN01G
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 and 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 setting up routing and switching
protocols.
The prompt following the device name indicates the mode as shown on the slide.
SSFJUN01-I
26
Slide 26
Hierarchical Command Structure

Logical structure organizes device features and
functions
Deeper levels are more and more specific
Know where you are at, find what you want, quickly
move around the interface, efficiently enter
commands
Top Level
Node
...
2nd Level
Nodes
3rd Level
Nodes
...
...
...
...
...
...
...
...
...
...
...
CONFIDENTIAL
...
...
...
SSFJUN01G
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 command-line interface 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 helpful in knowing where you are at, finding what you want, quickly moving
around the interface, and efficiently entering commands. The hierarchy of commands just makes
everything a lot easier in both learning and then using the Junos CLI. New users regularly comment on just
how logical the command-line is.
SSFJUN01-I
27
Slide 27
Operational Mode: Key Functions

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
CONFIDENTIAL
SSFJUN01G
The slide shows common administrative tasks completed in operational mode. Junos 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, 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 box operates in normal conditions and where, when, and why changes occur.
SSFJUN01-I
28
Slide 28
Operational Mode CLI Tree
top
Less Specific
clear configure file
help monitor set show etc.
chassis configuration interfaces ospf route version etc.
database interface neighbor route statistics etc.
CONFIDENTIAL
More Specific
SSFJUN01G
When you first log in to the CLI, the command-line interface is 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 the operational mode, with an example of
its cascading hierarchy through the 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).
For the student with experience using IOS, a basic difference of Junos is that it does not use the keyword IP.
So, many of the show commands you already know work if you drop this part of the command. For
example, the IOS command show ip route simply becomes show route in Junos.
SSFJUN01-I
29
Slide 29
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
CONFIDENTIAL
SSFJUN01G
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, enabling you to navigate through the command
hierarchy without referencing a CLI manual. In fact, question mark is your best friend while operating or
configuring a Junos running device.
You can add these options to adjust the output listings to what you need.
SSFJUN01-I
30
Slide 30
Example: Brief and Terse

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
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
CONFIDENTIAL
SSFJUN01G
This slide illustrates the results of adding the keywords brief and terse to the show interfaces
command.
SSFJUN01-I
31
Slide 31
Switching Between Modes

Enter configuration mode from operational mode
mike@jnpr1> configure
Entering configuration mode
[edit]
mike@jnpr1#
Enter operational mode from the top of configuration

mode
[edit]
mike@jnpr1# exit
Exiting configuration mode
mike@jnpr1>
CONFIDENTIAL
SSFJUN01G
As you monitor and configure a device, you need to switch between the operational mode and
configuration mode. When you change to configuration mode the command prompt changes from > to
#.
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 exit back to operational mode, you issue the exit command.
SSFJUN01-I
32
Slide 32
Configuration Mode CLI Tree

top
Less Specific
access chassis groups interfaces services system etc.
accounting license location ports services syslog etc.
finger
ftp
netconf
ssh
telnet
etc.
More Specific
Two types of statements

Container statements which contain other statements
Leaf statements which do not contain other statements
CONFIDENTIAL
SSFJUN01G
Configuration mode has a hierarchical structure logically grouping 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 tree, with nodes such as system
and interfaces at the 2nd level of the hierarchy.
The configuration statement hierarchy includes two types of statements:
container statements: which contain 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 by the content between curly brackets ({ and }).
leaf statements: which do 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.
SSFJUN01-I
33
Slide 33
Configuration Mode Syntax

[edit]
system {
services {
ftp;
}
}
Indentation of subordinate levels

Container statements indicated by open and close curly
brackets { }
In the example, system and services are cascading container
statements
Leaf statements indicated with a semicolon ;

In the example ftp; is a leaf statement
CONFIDENTIAL
SSFJUN01G
The command-line interface displays the hierarchy of the configuration mode through specific syntax:
Indicating hierarchy by indenting each subordinate level
In this example, services is a subordinate of system, and ftp is a subordinate to
services.
Indicating container statements by open and close curly brackets.
In the example, system and services are cascading container statements.
Indicating leaf statements with a semicolon.
In the example, ftp; is a leaf statement.
Also, speaking of configuration stanzas, system is a configuration stanza and so is services.
SSFJUN01-I
34
Slide 34
Hierarchy Flexibility
View from the top of configuration mode
[edit]
system {
services {
ftp;
}
}
View from a sublevel of configuration mode

[edit system services]
ftp;
CONFIDENTIAL
SSFJUN01G
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.
For example, the two configuration statements shown for the FTP service are equal. In the first, you are
looking at the statement from the root level of the hierarchy; and so the ftp; statement is shown in this
listing within the system and services container statements.
In the second example, you are viewing the ftp; statement from deeper level within the hierarchy.
When you are in deeper levels of the hierarchy, the [edit] banner displays the entire hierarchical path.
Here, the banner [edit system services] indicates a place of the hierarchy lying within
services at the 3rd level, within system at the 2nd level, and within the root - first level.
In this 2nd example, as you are deeper within the hierarchy. Whenever you view the configuration, the
command-line only displays the ftp; statement.
To determine where you are in the configuration hierarchy refer to the configuration command banner
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.
SSFJUN01-I
35
Slide 35
Configuration Mode Commands

edit
Must know the full hierarchical path
Creates new intermediate hierarchy levels if they dont yet
exist in your configuration
up
Move up one level in the hierarchy
To move up multiple levels, add an optional count
top
Move to the top level in the hierarchy
exit
Leave 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
CONFIDENTIAL
SSFJUN01G
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 doesnt exist in your configuration yet, the CLI
will create the 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 exit this
command from the top level of the configuration hierarchy, you exit configuration mode.
The organized structure of the command hierarchy eases movement from one level to another within the
Junos CLI.
SSFJUN01-I
36
Slide 36
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
CONFIDENTIAL
SSFJUN01G
Fortunately for new (and 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 device. It may take a few days
for these to become second nature; however, once you have the muscle memory, these keys can save you
lots of typing time.
The command-line interface stores every entered command in its command history. At any command
prompt the up and down arrow keys let you scroll through this history. Re-use commands that you
previously entered, or modify them as needed. Keyboard sequences can save you much time, for example,
when you are configuring similar items on the device, or you are repeating operational commands, such as
when you are debugging an issue.
SSFJUN01-I
37
Slide 37
Command and Variable Completion

Spacebar completes commands
[edit]
mike@jnpr1# show i<space>
i is ambiguous
igmp
Show
ike
Show
interfaces
Show
ipsec
Show
isis
Show
Internet Group Management Protocol

Interface Key Exchange Information
Interface Information
IP Security Information
Intermediate System-to Intermediate
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;
CONFIDENTIAL
SSFJUN01G
The CLI provides command completion to further speed your typing in both modes. Command completion
automatically finishes partially typed commands, filenames, and user names, so you dont need to recall
the exact syntax of the desired input string. Command completion is a big help to new users, easing their
transition to the new command-line interface.
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.
SSFJUN01-I
38
Slide 38
Getting Help
[edit system]
mike@jnpr1# set s?
saved-core-context
saved-core-files
> services
> static-host-mapping
> syslog
Save context information for core files

Number of saved core files per executable (1..64)
System services
Static hostname database mapping
System logging facility
CONFIDENTIAL
SSFJUN01G
Query the command-line with the ? 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 and the ?
provides a list of all the valid ways to complete your command, as shown in this example. Using the ? in
either of these ways is known as context-sensitive help in Junos lingo. For commands that require a
filename as an argument, the question mark lists the files in the working directory. You can consider ? to
be your best friend while navigating through Junos CLI.
SSFJUN01-I
39
Slide 39
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
CONFIDENTIAL
SSFJUN01G
When you want more information than provided by context-sensitive help, you can turn to the Junos
technical documentation on your device through the help commands. Juniper loads it on new devices and
includes it as a part of new upgrade builds. When requesting help, follow each of these help commands
with the string or topic for which you're seeking information.
The help files are divided into major categories. You can access these files in operational mode. Use:
help 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 statement
help syslog to display information on specific syslog events
help tip to provide random tips for using the CLI
help topic to display usage guidelines for configuration statements
SSFJUN01-I
40
Slide 40
Logging out
[edit protocols ospf]
mike@jnpr1# exit configuration-mode
mike@jnpr1> exit
logout
Connection closed by foreign host.
CONFIDENTIAL
SSFJUN01G
When it's time to take a break, you must be in operational mode to log out completely from the device. So,
if you are in configuration mode use the exit configuration-mode command to enter operational
mode. Then, you can completely exit the CLI by entering the exit command in this mode.
SSFJUN01-I
41
Slide 41
Lab 1- Intro to the CLI

Log into the Junos CLI
Explore the Junos OS CLI operational mode
https://virtuallabs.juniper.net/
Click here to
continue
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 1
Lab 1- Intro to the CLI

Log into the Junos CLI
Explore the Junos OS CLI operational mode
Enter Virtual Lab
SSFJUN01-I
42
Slide 42
Section Summary
In this section, you have learned how to:
Introduced the Junos OS CLI
Described the differences between operational mode and
configuration mode
Navigated the command hierarchy
Used command-line shortcuts and get help
CONFIDENTIAL
SSFJUN01G

Introduced the Junos CLI
Described the differences between operational mode and configuration mode
Navigated the command hierarchy
Used command-line shortcuts and get help
SSFJUN01-I
43
Slide 43

Operational mode is identified by which
prompt?
a)
# character
b)
} character
c)
> character
d)
~ character
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

Operational mode is identified by which prompt?
SSFJUN01-I
44
Slide 44

Configuration mode is identified by which
prompt?
a)
> character
b)
# character
c)
* character
d)
} character
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

Configuration mode is identified by which prompt?
SSFJUN01-I
45
Slide 45

What are three key functions of operational
mode?
a)
Monitor and troubleshoot the device
b)
Connect to other network systems
c)
Specify the types of events to track
d)
Control the CLI environment
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

What are three key functions of operational mode?
SSFJUN01-I
46
Slide 46
Learning Activity 2, Question 4:

Which command do you used to switch from
operational mode to configuration mode?
a)
exit
b)
configure
c)
confmode
d)
switch
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

Which command do you used to switch from operational mode to configuration mode?
SSFJUN01-I
47
Slide 47
The Junos OS CLI Rocks!
The Junos CLI includes functionality not found in legacy network operating systems, such as Ciscos IOS. For
example, did you know that the Junos CLI has some special features for protecting the network from
configuration errors and mistakes? Sound helpful? Many of these features came from the inspiration and
ideas of early Junos users who demanded a safer way to set up and make changes to their device
configurations.
This section introduces you to the ground breaking and specialized features of the Junos CLI. These are the
reasons why so many users say that Junos saves them time (often lots of it), reduces repetitive tasks, and
helps them to avoid very costly mistakes. In other words to enthusiastically agree that the Junos CLI
rocks!
SSFJUN01-I
48
Slide 48
Section Objectives
Present and demonstrate the Junos OS configuration
process and its multiple safeguards
Highlight the advantages of operating devices run by
Junos OS
Discuss features of the Junos OS CLI to automate
operations
CONFIDENTIAL
SSFJUN01G

Present and demonstrate the Junos configuration process and its multiple safeguards
Highlight advantage of operating devices run by Junos
Discuss features of the Junos CLI to automate operations
SSFJUN01-I
49
Slide 49
Junos OS Configuration Process

Separation of configuration edit and activation
Validation checks
Version control
Automated rollback
Convenient deployment of standard configurations

and policy language across the network
commit
validated
configuration
candidate
Load configuration
commit
confirmed
commit
scripts
active
configuration
commit
validations
CONFIDENTIAL
SSFJUN01G
The presented graphic outlines the basic steps to configure a Junos run device. Do you notice anything
different from most other network operating systems? Foremost: configuration changes in Junos do not
become active until you are ready. The Junos approach provides multiple safety nets that can save
engineers hours of troubleshooting on those bad days when configuration updates can go horribly
wrong potentially resulting in network collapses.
Once they understand these safety nets, new users of Junos typically come to see the Junos CLI as much
more user-friendly than other 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 CLI protects you from these and other configuration headaches.
To operate a device Junos uses the active configuration file. When a user changes a configuration file,
he/she works with the candidate configuration file, which is different from the active one. In order for
configuration changes to take place, the user must commit the candidate configuration file.
SSFJUN01-I
50
Slide 50
Junos OS Configuration Process (contd)
commit
candidate
configuration
commit
confirmed
validated
configuration
commit
scripts
commit
validations
active
configuration
1
rollback
Load
49
Basic steps in the configuration process

1. Enter changes in the candidate
2. Commit the candidate
3. Candidate becomes active
CONFIDENTIAL
SSFJUN01G
So what are the basic sets of the multi-stage Junos configuration process? Lets examine it in more details.
First: enter changes in the candidate configuration
The candidate configuration is a copy of the active configuration. You can enter configuration changes to the candidate
through the CLI via cut and paste, load or merge a text file with the updated configuration changes, or enter the changes by
hand through the CLI interface. After making all your candidate changes, you can review your work, including comparing the
candidate to the active running file.
Second: commit you changes, sending off a copy of the candidate to become the active configuration
Before finalizing the changeover, the software checks for certain statements within the candidate and performs other
context validations. If the device includes pre-loaded commit scripts, these scripts will also check and possibly correct errors
within the candidate configuration.
Third: the candidate becomes the active configuration
The candidate configuration 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.
Well explore explore each of these steps further in this section.
SSFJUN01-I
51
Slide 51
configure private, configure

exclusive
Use configure private for your own copy of the
candidate configuration
mike@jnpr1> configure private
warning: uncommitted changes will be discarded on
exit
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
CONFIDENTIAL
SSFJUN01G
To enter configuration mode, Junos provides several options. These options give users different ways to
manage who is making changes and when.
If users enter configuration mode with the base command: configure, as discussed in the prior section,
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, Junos offers the options to configure private or configure exclusive. These
prevent one user from inadvertently activating another users changes before they are ready.
In private mode, the device keeps a separate candidate copy holding only the changes by the private user.
In exclusive mode, the command-line 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.
SSFJUN01-I
52
Slide 52
show Command
List the complete candidate from
the top of configuration mode
[edit]
mike@juniper1# show
version "9.2R1.3";
groups
{
re0 {
system {
jnpr1-name jnpr1;
}
}
}
List a specific subset of the

candidate configuration from a
deeper level of the hierarchy
[edit interfaces ge-5/0/0]
mike@jnpr# show
gigether-options {
flow-control;
auto-negotiation;
}
unit 0 {
family inet {
address 1.2.3.4/28;
}
}
CONFIDENTIAL
SSFJUN01G
Initially, before any changes are entered, the candidate configuration is the same as the active running
configuration of the device.
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 listing of the example on the left.
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.
Note: You may 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 so the show
command represents different actions in each.
SSFJUN01-I
53
Slide 53
set Command
From the top of configuration mode
[edit]
mike@jnpr1#
mike@jnpr1#
mike@jnpr1#
mike@jnpr1#
set
set
set
set
system
system
system
system
services
services
services
services
finger
ftp
ssh
telnet
Either
adds
From a sublevel
[edit]
system {
services {
finger;
ftp;
ssh;
telnet;
}
}

mike@jnpr1# set finger
mike@jnpr1# set ftp
mike@jnpr1# set ssh
mike@jnpr1# set telnet
CONFIDENTIAL
SSFJUN01G
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, often it is easier to
navigate to the area within the configuration you are changing prior to adding and removing commands.
This is shown in the second example where changes are entered in the [edit system services]
sublevel of the hierarchy.
Either approach adds the same lines, shown on the right.
SSFJUN01-I
54
Slide 54
delete Command
Remove a statement along with any subordinate
statements
Deleting a statement effectively returns the affected
device, protocol, or service to an unconfigured state
Deleting a container statement removes everything under
that level of the hierarchy
[edit]
mike@jnpr1# delete system services
Now
CONFIDENTIAL
[edit]
system {
}
SSFJUN01G
The delete command removes statements from the candidate configuration.

In this example, we delete what we just added in the prior slide.
Deleting a statement effectively returns the affected device, protocol, or service to an unconfigured state.
Deleting a container statement removes everything under that level of the hierarchy.
So, be cautious here!! 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. Know where you are at
in the hierarchy and what all you are removing when you issue a delete statement!
SSFJUN01-I
55
Slide 55
compare Configurations
Display the differences between the candidate and
active configuration
Options to show any two configurations
mike@jnpr1# show | compare
- ssh;
+ telnet;
- web-management {
http {
port 8080;
}
- }
CONFIDENTIAL
SSFJUN01G
Have you ever entered changes to a configuration and then wanted to review them?
The compare command provides a convenient way to display the configured differences (and only these
differences) between the candidate configuration file and the active running configuration of the device (or
any other configurations you might choose). The CLI indicates new lines in the candidate with a plus (+) sign
and those removed with a minus (-) sign. In this example, the user has enabled telnet within system
services and also removed ssh and web-management.
SSFJUN01-I
56
Slide 56
commit check
Check that the device will accept your candidate
Validates the logic and completeness of the candidate
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
CONFIDENTIAL
SSFJUN01G
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 above.
SSFJUN01-I
57
Slide 57
commit
Activates the candidate to become the running
configuration of the device
If the validation checks find any errors, you must fix these
before the candidate can become the active file
[edit]Bullets
Add
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
CONFIDENTIAL
SSFJUN01G
The candidate file is only the proposed configuration, and your device does not use any of this
configuration until you issue a commit command. 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, Junos 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.
You must fix all mistakes before the candidate (or any part of the candidate) can become active.
The commit complete message tells you that the new configuration is up and running on the device.
SSFJUN01-I
58
Slide 58
Commit confirmed
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.
CONFIDENTIAL
SSFJUN01G
Are you among those of us who have made the mistake of adding security to a remote box, only to discover
the new firewall 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 box and then had to jump in the car and drive twoand-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. Then if you don't
follow up with a second commit, 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 other interval you specify). In
this way, if you have accidently isolated the device, you simply need to wait for the roll back instead of
agonizing over how you are going to otherwise undo your mistake.
SSFJUN01-I
59
Slide 59
Rollback
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
Dont forget to commit the changes!
[edit]
mike@host# rollback
load complete
[edit]
mike@host# commit
commit complete
CONFIDENTIAL
SSFJUN01G
Whenever you commit the candidate as the new active configuration, Junos automatically saves a copy of
the replaced active file. 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 to restore your candidate
configuration. Reset your candidate to match the active running configuration by entering rollback or
rollback 0.
Return to the most recently previous configuration file using the rollback 1 command, or add any
other number between 2 and 49 to go back to an even older version of the configuration.
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 the rollback file immediately, first make sure it's what you want by using the show
command, and then activate it with the commit command. That last bit was important. Dont forget to
complete a rollback for the active configuration of the device, you must also commit it.
This automatic backup mechanism lets you return quickly to a previous configuration for immediate use or
for fast updates.
SSFJUN01-I
60
Slide 60
Preparing Changes in Advance

Prepare for hardware being installed tomorrow
[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
mike@jnpr1>
CONFIDENTIAL
SSFJUN01G
Unlike other systems Junos lets you prepare for an installation before actually installing the hardware. The
software simply ignores any parts of the running configuration which are irrelevant to the existing
hardware installation. Whenever the hardware becomes available, the newly added section of the
configuration then becomes active.
The option to set up a configuration prior to hardware install is quite useful, especially when the person
installing the hardware is different than the person configuring the device, a common occurrence for
remote boxes. Here is a configuration for fe-3/0/0, which will be installed tomorrow.
Sometimes you want to prepare configuration changes for activation at a specific time, such as during a
maintenance window. The commit at command provides this option.
You can also make configuration changes and mark them as inactive until you are ready to use them by
using the deactivate command.
SSFJUN01-I
61
Slide 61
Handy Commands 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
Add the correct address for the new interface

[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
CONFIDENTIAL
SSFJUN01G
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 command, you copy the configuration associated with one userdefined element to a new, similarly configured element. You then modify that second element with any
needed changes.
The rename command is a convenient shortcut when you need to alter the value of a user-defined
variablesuch as policy names, filter names, IP addressesor to change the name of a user-defined
element.
The example on this slide illustrates a very useful technique for configuring similar interfaces, where only IP
addresses are different. First, you create identical configuration of se-0/0/1 based on the se-0/0/2
interface. 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. Also, you can use the rename command to change the ip address of the newly created
interface, thereby achieving the same result, as indicated on this slide.
SSFJUN01-I
62
Slide 62
Powerful | Pipe
Filter output in both operational and configuration
mode
Sends output of one command as input to another
Examples:
Use 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
CONFIDENTIAL
SSFJUN01G
The pipe | character lets you filter output in both operational and configuration modes. Pipe makes it
possible to display specific information in a single command step, sending the output of one command as
input to another, or redirecting the output to a file. 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 the slide creates a file that stores the output of the request support
information command of the operational mode by piping its output to a filename.
In the second, | count counts the number of lines in the output.
Many more examples for using pipe are available in the Junos technical documentation and other reference
resources.
SSFJUN01-I
63
Slide 63
Run is Cool
Issue operational mode commands while in
configuration mode
[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
<. . .>
CONFIDENTIAL
SSFJUN01G
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 the
configuration mode.
For example, entering the run show interfaces command displays the output as if show
interfaces had been entered from operational mode. Here we show an abbreviated listing of the
output.
SSFJUN01-I
64
Slide 64
Junos OS System Health: Monitoring

Real-time Performance
Monitoring (RPM)
Active probes to monitor performance
Per-destination and application basis
Flow accounting
cflowd and rich filtering
Active monitoring, passive monitoring,
port mirroring
Health monitor
Extends the Remote Network
Monitoring (RMON) alarm
infrastructure with minimum user
configuration
CONFIDENTIAL
SSFJUN01G
Juniper devices provide extensive on-board instrumentation that enables customers to proactively gather
status information. Self-monitoring allows continuous feedback and lets administrators capture networkwide down to highly granular perspectives on the operations of the network. Junos-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:
Real-time performance monitoring: 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 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 subinterface.
Health monitor: Notifies your network management system (NMS) when something requires attention.
Health monitor extends the Remote Network Monitoring (RMON) alarm infrastructure of Junos 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.
SSFJUN01-I
65
Slide 65
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
CONFIDENTIAL
SSFJUN01G
The logging and tracing operations of Junos 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 whats going on in your device.
SSFJUN01-I
66
Slide 66
Open to Innovation
CONFIDENTIAL
SSFJUN01G
Junos Automation allows power control on-box while also allowing flexible integration to off-box systems.
With the Junos approach to an open network architecture, Juniper can offer a common interface set across
all platforms. Providing a horizontal platform approach of silicon, system, and software, allows Juniper to
deliver a complete solution supporting many applications. Juniper delivers access to third party innovation
and integration by offering a Junos software development kit to partners so they can release even more
value from their network applications.
SSFJUN01-I
67
Slide 67
Junos OS Automation of Commands

Configuration-mode automation
Prevent errors and enforce compliance to
policies and procedures
CLI
Accept, reject, modify, or generate a

message
scripts
Macros minimize line entries
Operations-mode automation
Build custom operational commands
Automate remediation steps/guidance
Custom notifications, further diagnosis, or
corrective actions
Correlate specific events and perform a
set of actions
Junos
management
CONFIDENTIAL
SSFJUN01G
Junos command automation is available in configuration and operation modes. In the configuration mode
command automation prevents configuration errors and enforces compliance to pre-defined policies and
procedures. In the operations mode command automation allows you customize operational commands,
and automate custom-defined notifications, diagnosis, or corrective actions, correlating specific events and
actions.
SSFJUN01-I
68
Slide 68
Summary of the Junos OS CLI Rocks

Configuration Mode Highlights
Configure private, configure exclusive

Commit model
Compare
Rollback
Preconfigure changes
Copy and rename
Junos automation
Operational Mode Highlights

Powerful monitoring tools with performance
Powerful diagnostic tools with performance
Junos automation
CONFIDENTIAL
SSFJUN01G
In summary, the Junos CLI offers multiple specialized features that are not found in many other network
operating systems.
In configuration mode:
configure private and configure exclusive let engineers manage who is changing the
device and when.
The commit model lets engineers enter configuration changes in a candidate file. The approach provides
multiple safety nets that can prevent configuration problems and save hours of troubleshooting.
The compare command lets engineers review their changes, looking for any last-minute typos or
omissions, by comparing two different configurations, yet again providing safety nets ensuring maximum
network availability.
rollback restores the rescue or any of the prior 50 configurations.
Preconfigure a device before hardware install or specify a time for changes to become active.
A rich set of text editing tools saves engineers lots of typing, including the power of the copy and
rename commands to repurpose existing configuration elements.
Commit scripts to customize validation of configurations and define time-saving macros.
In operational mode, the highlights include:
Powerful monitoring and diagnostic tools that engineers can use without harming device performance.
Various scripts and event policies to automate event detection and troubleshooting as well as restoration
to normal operations.
SSFJUN01-I
69
Slide 69
Lab 2- Configuring the CLI

Explore the Junos OS CLI configuration mode
Save, view, and use a rescue configuration
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 2
Lab 2 Configuring the CLI

*Explore the Junos OS CLI configuration mode
*Save, view, and use a rescue configuration
Enter Virtual Lab

SSFJUN01-I
70
Slide 70
Section Objectives
Presented and demonstrated the Junos configuration
process and its multiple safeguards
Highlighted the advantages of operating devices run by
Junos
Discussed features of the Junos CLI to automate
operations
CONFIDENTIAL
SSFJUN01G

Presented and demonstrated the Junos configuration process and its multiple safeguards
Highlighted advantage of operating devices run by Junos
Discussed features of the Junos CLI to automate operations
SSFJUN01-I
71
Slide 71

True or False: As soon as you edit the
configuration file and press Enter the changes
are implemented on your device.
a)
True
b)
False
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

True or False: As soon as you edit the configuration file and press Enter the changes are implemented on
your device.
SSFJUN01-I
72
Slide 72

What is the purpose of configure private?
a)
Limits impact of configuration to the local

system only
b)
Creates your own copy of the candidate

configuration
c)
Prohibits others from making changes to the

configuration
d)
Produces a second copy of the

configuration for testing purposes
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

What is the purpose of configure private?
SSFJUN01-I
73
Slide 73

What is the purpose of commit check?
a)
Implements configuration changes for a

limited amount of time before an automatic
rollback
b)
Ensures that no one else has the

configuration open
c)
Ensures that all devices to be impacted on

online and running without error conditions
d)
Validates logic and completeness of the

candidate statements
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

What is the purpose of commit check?
SSFJUN01-I
74
Slide 74

True or False: Junos-based platforms come
with sufficient processing power to collect and
store critical operational data.
a)
True
b)
False
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

True or False: Junos-based platforms come with sufficient processing power to collect and store critical
operational data.
SSFJUN01-I
75
Slide 75
Routing with Junos OS
Junos supports various standards-based routing protocols. This section provides a quick overview of basic
routing, and the differences between static and dynamic routing.
SSFJUN01-I
76
Slide 76
Section Objectives
In this section, you will:
Compare and contrast routing and forwarding tables

Describe routing instances
Describe static routing and its configuration using Junos OS
Describe dynamic routing
CONFIDENTIAL
SSFJUN01G
Upon completion of this section, you will be able to:

Compare and contrast routing and forwarding tables;
Describe routing instances;
Describe static routing and its configuration using Junos; and
Describe dynamic routing.
SSFJUN01-I
77
Slide 77
What Is Routing?
The process of moving data between Layer 3
networks
Server
B
Server
A
Internet
User A
=
Router
=
User B
Switch
Data center
CONFIDENTIAL
SSFJUN01G
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 the slide consists of several Layer 3 networks, all connected to 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.
We look at the required components of routing and how devices running Junos Software make routing
decisions on subsequent slides within this section.
SSFJUN01-I
78
Slide 78
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
Internet
User A
=
Router
=
User B
Switch
Data center
CONFIDENTIAL
SSFJUN01G
Routing Components
You must consider several components and other aspects to effectively implement routing between remote
networks. However, you can classify the various components and considerations into two primary
requirementsend-to-end communications path and ensuring all Layer 3 devices within the
communications path have the required routing information.
In the example shown on the slide, you can see that a physical path exists between the highlighted
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 user and data center 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 transit traffic it receives. Devices
running Junos Software use the forwarding table, which is a subset of information found in the route table,
to make this determination. We discuss the route and forwarding tables next.
SSFJUN01-I
79
Slide 79
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
Routing
protocol
databases
Other routing
information
sources
OSPF
Routing
table
Forwarding
table
Direct Static
CONFIDENTIAL
SSFJUN01G
Routing Information Sources

The Junos Software 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 Junos Software receives multiple routes for a given prefix, it selects a single route as
the active route. With additional configuration, Junos Software supports 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 Junos Software.
Multiple Routing Tables
Devices running Junos Software 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 Junos
Software creates when required by the configuration.
The following is a summary of the common predefined routing tables you might see on a device running
Junos Software:
SSFJUN01-I
80
Slide 80
Predefined Routing Tables

The following is a summary of the common predefined routing tables you might see
on a device running Junos Software:
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; and
mpls.0: Used for MPLS next hops.
CONFIDENTIAL
SSFJUN01G
The following is a summary of the common predefined routing tables you might see on a device running
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; and
mpls.0: Used for MPLS next hops.
SSFJUN01-I
81
Slide 81
Route Preference
Ranks routes received from different sources
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
Local
Static
OSPF internal
RIP
OSPF AS external
BGP (both EBGP and IBGP)
0
0
5
10
100
150
170
CONFIDENTIAL
More Preferred
Less Preferred
SSFJUN01G
Preferred Routing Information Sources

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.
Selecting the Active Route
Route preference is similar to Ciscos administrative distance setting.
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 the slide shows the default preference values for a selected set of routing
information sources. Of course, any default can be changed.
SSFJUN01-I
82
Slide 82
Viewing the Routing Table

Use show route to display route table contents:
user@host> show route
inet.0: 6 destinations, 7 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.0/24
172.18.25.0/30
172.18.25.1/32
172.29.30.0/24
172.29.30.1/32
*[Static/5] 00:10:24
Route source and
> to 172.29.30.253 via ge-0/0/10.0 preference
[OSPF/10] 00:03:38, metric 2
> to 172.18.25.2 via ge-0/0/13.0
*[Direct/0] 00:11:05
> via ge-0/0/13.0
*[Local/0] 00:11:05
Local via ge-0/0/13.0
*[Direct/0] 00:11:05
> via ge-0/0/10.0
*[Local/0] 00:11:05
Asterisk (*) indicates that
the route is selected as
active
Route table name

CONFIDENTIAL
SSFJUN01G
Viewing the Route Table

The slide shows the use of the show route command, which displays all route entries in the routing
table. As identified on the slide, all active routes are 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 filter the generated output by destination prefix, protocol type, and other distinguishing attributes.
The following sample capture illustrates the use of the protocol filtering option:
user@host> show route protocol ospf
10.1.1.0/24
224.0.0.5/32
SSFJUN01-I
[OSPF/10] 04:57:41, metric 2

> to 172.18.25.2 via ge-0/0/13.0
*[OSPF/10] 05:00:58, metric 1
MultiRecv
83
Slide 83
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
databases
OSPF
Routing
Table
Other routing
information
sources
DirectStatic
CONFIDENTIAL
Forwarding
Table
SSFJUN01G
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 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 router discards the packet and it sends an
ICMP destination unreachable message back to the sender. If you configured a user-defined default route,
the router uses it instead of the permanent default forwarding entry. Some examples of forwarding entries
are remote 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 local address on an interface.
SSFJUN01-I
84
Slide 84
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 out
Packets in
CONFIDENTIAL
SSFJUN01G
Determining the Next Hop

When a packet enters a device running 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, Junos OS
processes the packet locally. If the packet is destined to a remote device and a valid entry exists, the device
running Junos OS forwards the packet out the next-hop interface associated with the forwarding table
entry.
If multiple destination prefixes match the packets destination, 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 Junos OS responds to the source device
with a destination unreachable notification.
SSFJUN01-I
85
Slide 85
Overview of Routing Instances

A routing instance is a unique collection of routing
tables, interfaces, and routing protocol parameters
Device Running Junos Software
Routing instance (master) Routing instance (cust-A) Routing instance (cust-B)
inet.0
inet6.0
ge-0/0/0.0
ge-0/0/1.0
lo0.0
Default Route
OSPF
cust-A.inet.0
cust-A.inet6.0
ge-0/0/3.0
ge-0/0/4.0
lo0.1
Default Route
OSPF
CONFIDENTIAL
cust-B.inet.0
cust-B.inet6.0
ge-1/0/0.0
ge-1/0/1.0
lo0.2
Default Route
OSPF
SSFJUN01G
Overview of Routing Instances

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.
SSFJUN01-I
86
Slide 86
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
master
forwarding
inet.0
3/0/1
inet6.0
4/0/0
Participating route tables; the presence

Routing instance
of inet6.0 table indicates IPv6 is in use
name
CONFIDENTIAL
SSFJUN01G
Master Routing Instance

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.
SSFJUN01-I
87
Slide 87
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 ?
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

Junos OS; Check product documentation for actual support
CONFIDENTIAL
SSFJUN01G
User-Defined Routing Instances

For added flexibility, Junos OS allows you to configure additional routing instances under the [edit routinginstances] 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 as policy-based routing (PBR).
Some typical uses of 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:
forwarding: Used to implement filter-based forwarding for common Access 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;
vpls: Used for point-to-multipoint LAN implementations between a set of sites in a VPN; and
vrf: Used in Layer 3 VPN implementations.
Note that the actual routing instance types vary between platforms running Junos OS . Be sure to check the
technical documentation for your specific product.
SSFJUN01-I
88
Slide 88
Configuration Example
Routing instance configuration example:
[edit routing-instances new-instance]
Routing instance name is useruser@host# show
defined
instance-type virtual-router;
Routing instance type
interface ge-0/0/0.0;
Define interfaces under the [edit
interfaces] hierarchy and reference
interface lo0.1;
them under the routing instance
routing-options {
static {
route 0.0.0.0/0 next-hop 172.26.25.1;
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.1;
}
}
}
CONFIDENTIAL
SSFJUN01G
Configuration Example: Routing Instances

The slide illustrates a basic routing instance configuration example.
SSFJUN01-I
89
Slide 89
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)
0.0.0.0/0
172.25.182.0/24
172.25.182.5/32
172.26.25.0/24
172.26.25.5/32
192.168.100.52/32
*[Static/5] 02:06:18
> to 172.26.25.1 via ge-0/0/0.0
*[Direct/0] 02:06:18
> via ge-0/0/1.0
*[Local/0] 02:06:18
*[Direct/0] 02:06:18
> via ge-0/0/0.0
*[Local/0] 02:06:18
*[Direct/0] 02:06:18
> via lo0.1
Software automatically creates

IP unicast table when you
configure the corresponding
routing instance
CONFIDENTIAL
SSFJUN01G
Working with Routing Instances: Part 1

Once you configure a routing instance and the device learns routing information within the instance, Junos
OS automatically generates a route table. If you use IPv4 routing, the software creates an IPv4 unicast
routing table. The name of the 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 the slide, to view a routing table associated with a specific routing instance, you simply use
the show route table table-name CLI command.
SSFJUN01-I
90
Slide 90
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
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
Remote
--> 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
CONFIDENTIAL
SSFJUN01G
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 on the 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 the slide show this option in action with the ping and traceroute
utilities.
SSFJUN01-I
91
Slide 91
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 or
reject)
Network A
172.29.100.0/24
ge-0/0/1
.1
.2
.1
Internet
172.30.25.0/30
192.168.63.14
user@host> show route 192.168.63.14
0.0.0.0/0
*[Static/5] 01:09:34
> to 172.30.25.1 via ge-0/0/1.0
CONFIDENTIAL
Default static
route
SSFJUN01G
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.
Next Hop Required
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
Junos Software, 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 Junos Software 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 next-hop value, the system does not send back an ICMP message; the system
drops the packet silently.
By default, the next-hop IP address of static routes configured in Junos Software must be reachable using a
direct route. Unlike with software from other vendors, Junos Software 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.
SSFJUN01-I
92
SSFJUN01-I
93
Slide 92
Configuring Static Routing

Static route configuration example:
[edit routing-options]
user@host# show
rib inet6.0 {
static {
route 0::/0 next-hop 3001::1;
}
}
static {
route 0.0.0.0/0 next-hop 172.30.25.1;
route 172.28.102.0/24 {
next-hop 10.210.11.190;
no-readvertise;
}
}
IPv6 default static route
IPv4 default static route
Restricts route from being advertised into a

routing protocol through routing policy; Highly
suggested for static routes used for
management traffic
CONFIDENTIAL
SSFJUN01G
Configuration Example: Static Routing

The 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 noreadvertise 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.
SSFJUN01-I
94
Slide 93
Monitoring Static Routing

Monitoring:
Use show route protocol static to display static routes:
user@host> show route protocol static
0.0.0.0/0
Route source and preference

*[Static/5] 00:41:59
> 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 reachability:

user@host> ping 192.168.63.14 rapid count 25
PING 192.168.63.14 (192.168.63.14): 56 data bytes
Test confirms
!!!!!!!!!!!!!!!!!!!!!!!!!
reachability
--- 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
CONFIDENTIAL
SSFJUN01G
Monitoring Static Routing

The slide shows the basic verification steps when determining proper operation of static routing.
SSFJUN01-I
95
Slide 94
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
.1
Host-B
.2
172.25.1.0/30
user@Host-A# show
static {
route 172.20.3.0/24 {
next-hop 172.25.1.6;
resolve;
}
}
.5
.6
Host-C
.1
172.25.1.4/30
172.20.3.0/24
Indirect next
hop
resolve option required
CONFIDENTIAL
SSFJUN01G
Resolving Indirect Next Hops

By default, Junos OS requires that the next-hop IP address of static routes be reachable using a direct
route. Unlike software from other vendors, Junos OS does not perform recursive lookups of next hops by
default.
As illustrated on the 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.
SSFJUN01-I
96
Slide 95
Qualified Next Hops

Use qualified-next-hop to allow independent
preference for static routes to the same destination:
172.30.25.0/30
ge-0/0/1
Network A
172.29.100.0/24
.1
.2
primary
.1
.6
secondary
.5
Internet
se-1/0/0
172.30.25.4/30
user@host# show
static {
route 0.0.0.0/0 {
next-hop 172.30.25.1;
qualified-next-hop 172.30.25.5 {
preference 7;
}
}
}
CONFIDENTIAL
Primary next hop due to

default route preference
(5)
Secondary next hop due to

configured route preference
(7)
SSFJUN01G
Qualified Next Hops

The qualified-next-hop option allows independent preferences for static routes to the same
destination. The slide shows an example using the qualified-next-hop option.
In the sample configuration shown on the 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.
SSFJUN01-I
97
Slide 96
Dynamic Routing
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
CONFIDENTIAL
SSFJUN01G
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.
Benefits of Dynamic Routing
Dynamic routing resolves many of the limitations and drawbacks of static routing. Some of the general
benefits of dynamic routing include:
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.
SSFJUN01-I
98
Slide 97
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, IS-IS, and OSPF
EGPs operate among different autonomous systems

Independent administrative entities that communicate between
independent network infrastructures
Current EGP in use today is BGP
AS 64513
IGP
AS 64512
IGP
IGP
IBGP
CONFIDENTIAL
AS 65535
SSFJUN01G
A Summary of Dynamic Routing Protocols

Our main objective is to provide a basic summary of dynamic routing protocols. Advanced coverage of
routing protocols is outside the scope of this class.
The slide provides a high-level summary of Interior Gateway Protocols (IGPs) and Exterior Gateway
Protocols (EGPs).
SSFJUN01-I
99
Slide 98
OSPF Protocol Overview

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
CONFIDENTIAL
Area 0.0.0.2
SSFJUN01G
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 linkstate 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 routers
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 is identical for all participating routers within that area.
SSFJUN01-I
100
To ensure correct routing knowledge and connectivity, OSPF 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.
SSFJUN01-I
101
Slide 99
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
Host-A
lo0: 192.168.100.1/32
ge-0/0/2
.1
.1
172.20.1.0/24
ge-0/0/3
Host-B
lo0: 192.168.100.2/32
OSPF Area 0
.10
.2
172.25.1.0/30
.1
172.20.2.0/24
.5
ge-0/0/1
.9
Host-C
lo0: 192.168.100.3/32
.6
.1
172.20.3.0/24
CONFIDENTIAL
SSFJUN01G
Case Study: Objective and Topology

The slide provides the objective and sample topology used in this case study.
SSFJUN01-I
102
Slide 100
Case Study: Configuring OSPF

Sample OSPF configuration taken from Host-A:
user@Host-A# set area 0 interface ge-0/0/1.0
Specify the logical

interface. If unit is not
referenced, Junos Software
assumes unit 0.

user@Host-A# set area 0 interface ge-0/0/2.0

user@Host-A# set area 0 interface ge-0/0/3.0 passive
user@Host-A# set area 0 interface lo0.0
user@Host-A# show
area 0.0.0.0 {
interface ge-0/0/3.0 {
passive;
}
interface lo0.0;
}
Use passive option to

prohibit adjacency
formation.
Junos Software converts area 0 to

its proper dotted decimal notation
(0.0.0.0).
CONFIDENTIAL
SSFJUN01G
Case Study: Configuring OSPF

Note that you must include the lo0 interface if you want the associated IP address(es) advertised into OSPF.
Prior to software Release 8.5, the IP address associated with the lo0 interface was automatically advertised
into OSPF as a router LSA.
The 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.
SSFJUN01-I
103
Slide 101
Case Study: Verifying OSPF Neighbor State

Use show ospf neighbor to display adjacencies
Use detail or extensive options for added information
user@Host-A> show ospf neighbor
Address
Interface
172.25.1.9
ge-0/0/1.0
172.25.1.2
ge-0/0/2.0
State
Full
Full
ID
192.168.100.3
192.168.100.2
Pri
128
128
Dead
38
35
The state of the adjacencies shows

Full, which means neighbors can
exchange routing information
CONFIDENTIAL
SSFJUN01G
Case Study: Verifying OSPF Neighbor State

The slide shows the CLI command used to determine OSPF adjacencies. In the sample output on the 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 output:
Address: 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 the most
likely router to be elected designated router.
Dead: The number of seconds until the neighbor becomes unreachable.
SSFJUN01-I
104
Slide 102
Case Study: Viewing OSPF Routes

Use show route protocol ospf to display
OSPF routes
user@Host-A> show route protocol ospf
172.20.2.0/24
172.20.3.0/24
172.25.1.4/30
192.168.100.2/32
192.168.100.3/32
224.0.0.5/32
*[OSPF/10] 00:03:55,
> to 172.25.1.2 via
*[OSPF/10] 00:00:04,
> to 172.25.1.9 via
*[OSPF/10] 00:03:46,
> to 172.25.1.9 via
to 172.25.1.2 via
*[OSPF/10] 00:03:55,
> to 172.25.1.2 via
*[OSPF/10] 00:03:46,
> to 172.25.1.9 via
*[OSPF/10] 00:16:13,
MultiRecv
metric 2
ge-0/0/2.0
metric 2
ge-0/0/1.0
metric 2
ge-0/0/1.0
ge-0/0/2.0
metric 1
ge-0/0/2.0
metric 1
ge-0/0/1.0
metric 1
CONFIDENTIAL
SSFJUN01G
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 routesit installs them as direct routes.
SSFJUN01-I
105
Slide 103
Lab 3- Configuring OSPF

Configure and monitor static routing
Configure and monitor OSPF
Click here to
continue
CONFIDENTIAL
SSFJUN01G
www.juniper.net | 3
Lab 3- Configuring OSPF

Configure and monitor static routing
Configure and monitor OSPF
Enter Virtual Lab
SSFJUN01-I
106
Slide 104
Section Objectives
Compared and contrast routing and forwarding tables;

Described routing instances;
Described static routing and its configuration using Junos;
Described dynamic routing.
CONFIDENTIAL
SSFJUN01G

Compared and contrasted routing and forwarding tables;
Described routing instances;
Described static routing and its configuration using Junos;
Described dynamic routing.
SSFJUN01-I
107
Slide 105

In Junos OS, route preference is similar to
what Cisco concept?
a) Administrative distance setting
b)
Route hierarchy
c)
Destination table
d)
Routing table
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

In Junos OS, route preference is similar to what Cisco concept?
SSFJUN01-I
108
Slide 106

What are three benefits of Dynamic Routing?
a)
Useful for small networks where only a few routes

exist
b)
Lower administrative overhead
c)
Increased network availability
d)
Greater network scalability
Submit
Submit
CONFIDENTIAL
SSFJUN01G
Clear
Clear

What are three benefits of Dynamic Routing?
SSFJUN01-I
109
Slide 107
Junos OS Adoption
Adoption of any new product or technology initially requires some effort; however, Junipers customers
have consistently found the initial short-term activities of Junos adoption to be far outweighed by the longterm benefits. This section introduces the interoperability features and migration tools available to Juniper
customers to make the move to Junos simple and safe.
SSFJUN01-I
110
Slide 108
Section Objectives
In this section, you will be able to:
Discuss how Junos OS interoperates with other devices
and integrates to other systems
Present ways in which Juniper eases Junos OS adoption
for new customers
CONFIDENTIAL
SSFJUN01G
In this section, you will be able to:

Discuss how Junos interoperates with other devices and integrates to other systems
Present ways in which Juniper eases Junos adoption for new customers
SSFJUN01-I
111
Slide 109
Time Tested Interoperability

Commitment to standards
IETF leadership
Extensive set of networking
protocols
Pragmatic approach
Run vendor interoperability tests
Interoperability that works
Not just compliance to standards
Extensive field experience

Top service providers
Thousands of business, government,
and education networks
Most deployments are mixed
environments
CONFIDENTIAL
SSFJUN01G
Do any of your customers have only one vendor in their network? For the most part, probably not. Just as
most of your customers likely have multiple vendors for servers, storage, and other IT systems, its good
practice to use multiple vendors in the network, as overall, an organization is likely to get better solutions
for lower costs. So how Junos interoperates and integrates into existing infrastructure is essential.
Juniper engineers have long been involved in building open standards for interoperability in industry
organizations. For example, Junos developers have been at the forefront of defining and implementing
MPLS applications, next-generation multicast VPN architectures, and high-availability features such as nonstop active routing and in-service software upgrades. Junos protocols engineers authored or co-authored
more than 20 IETF drafts in 2008 alone.
Junos OS supports hundreds of networking protocols standards such as spanning tree, LLDP, OSPF, BGP,
IPv6, and MPLS, to name just a few. Nonetheless, the practicalities of interoperability require that Juniper
goes beyond simply implementing the standards. For example, filling in gaps in cases of differences in
interpretation or where de-facto standards are used.
This practical approach is necessary to support the thousands of customers of Junos. Interoperability
between Juniper and other large networking vendors has been proven several times over, in the best
possible way, with live network implementations in the largest networks over the past decade.
SSFJUN01-I
112
Slide 110
What Doesnt Work?

Proprietary
EIGRP
PVST and PVST+
HSRP
WCCP
Etc.
Legacy
IPX
Appletalk
Etc.
Bleeding edge
New protocols that are draft standards
Synchronize over time
CONFIDENTIAL
SSFJUN01G
A few organizations may still be running proprietary or legacy protocols within their network. In these
cases, the customer will either have to transition to modern standards or adopt one of the available
methods of supporting these protocols over a standards-based infrastructure. For example, there are
various approaches to simultaneously running EIGRP and OSPF in legacy routers to support a long term
transition to OSPF. By moving to open standards, organizations benefit from the collective innovation of the
industry; open standards generally offer a broader set of capabilities than protocols developed exclusively
by one vendor.
SSFJUN01-I
113
Slide 111
Standards-Based Integration to Systems

Integration to NMS and other
operations tools
Retrieve operational and
configuration information
Efficiently search, modify, and upload full
or partial device configuration information
Standardized system logging messages
and SNMP interfaces
NETCONF XML Interface
NETCONF XML
Defines an XML-based data encoding for

configuration data as well as the protocol
messages
Enables other systems to request and
change configuration information in a
standard way
CONFIDENTIAL
SSFJUN01G
Operations teams use tens, sometimes hundreds, of different tools to manage their networks, for examples
tools for inventory, configuration, provisioning, monitoring, and managing faults. Many are home grown
while others are purchased from one of the many independent software vendors who develop network
management products. Juniper works in close partnership with these vendors to integrate management of
Junos into their solutions.
Juniper streamlines integration of partner and customer systems by providing a number of open, standard
interfaces in Junos. In addition to the CLI, standardized system logging messages, SNMP interfaces, and onboard instrumentation systems, Junos also provides an XML (eXtensible Markup Language) interface. All
these open options let network management tools interact with Junos in a reliable and predictable way.
For customers who want to use Juniper element management, Juniper provides its Network and Security
Manager (NSM), a powerful, centralized management solution that controls the entire device life cycle
across the broad portfolio of Junipers enterprise platforms, including firewall/IPSec VPN, Secure Access
(SSL), Infranet Controller, the J Series, M Series, and MX Series routing platforms and EX Series switches.
SSFJUN01-I
114
Slide 112
Junos Automates the Network
Operations Automation
Save Time: write custom
commands & automate
diagnostics
Event Automation
Speed Resolution:
Gather/correlate events and
automate response
Config Automation
Avoid Errors: Simplify
& enforce best practices
CONFIDENTIAL
SSFJUN01G
With Junos, we characterize Junos Automation with efficiency. Whether it be operations, event correlation,
or configuration, Junos will save time through automation that runs directly on the Junos device. We also
feature Juniper care with Service automation allowing a Juniper service team to work directly with
customers to maintain specific levels of incident response management. As explained earlier as well, we
offer Junos Space which through this platform we offer a programmable platform for developing and
running applications across the network.
SSFJUN01-I
115
Slide 113
I2J Conversion Tools

Converts from other to
Junos
IOS routing and switching
https://i2j.juniper.net/release/index.jsp
ScreenOS security to
Junos
Available on the Juniper

support site
Offered through AES 256bit encrypted website
CONFIDENTIAL
SSFJUN01G
Are your customers migrating from Cisco to Juniper? Ease the transition with the I2J tool, a configuration
translator that converts Cisco IOS software configurations to Junos software configurations. Automatic
access to the tool at https://i2j.juniper.net/release/index.jsp is provided at no charge to JNASC Support
Managers, JNASC Support Providers, Premier Accounts, and all support contract customers.
Training on the Juniper I2J translator can be found by using the link :
http://www.juniper.net/us/en/training/elearning/ios_junos/content/index.html
And additional conversion tools can be found using the link at the bottom of this slide: https://migrationtools.juniper.net/tools/index.jsp
SSFJUN01-I
116
Slide 114
Getting Started with Junos

Training/certification
New user to expert
Fast Track
Offers significant time
and cost savings
Books
Day One downloads
OReilly Technical Library
Community
J-Net: www.juniper.net/forums
Knowledge Base:
www.juniper.net/kb
CONFIDENTIAL
SSFJUN01G
So how do we get started with Junos? There is always training and certifications available from new user
Juniper Associate (JNCIA) Introduction to Junos curriculum, to expert level certifications (JNCIE). We also
offer a fast track program for those who are already familiar with other vendors products. This program will
offer the student discounts and time savings in certifying on the Junos OS. We also offer several books
including Day One downloads for eReaders as well as .PDF formats, and a full technical library of books
from the publisher OReilly.
SSFJUN01-I
117
Slide 115
Section Summary
Discussed how Junos OS interoperates with other devices
and integrates to other systems
Presented ways in which Juniper eases Junos adoption for
new customers
CONFIDENTIAL
SSFJUN01G

Discussed Junos interoperability with other devices and its integration into other systems
Presented ways in which Juniper eases Junos adoption for new customers
SSFJUN01-I
118
Slide 116

True or False: Junos OS is designed for Junosonly networks
a)
True
b)
False
Correct The statement is false.

Junos OS supports hundreds of
networking protocolsIncorrect - The statement is false.
Junos OS supports hundreds of
Click anywhere to continue networking protocols
Click anywhere to continue
Submit
Submit
SSFJUN01-I
CONFIDENTIAL
SSFJUN01G
Clear
Clear
119
Slide 117
Course Summary
In this course, we:
Described the Junos OS command-line interface (CLI)
Demonstrate specialized features of the Junos CLI that
save time and avert downtime
Described basics of routing using Junos OS
Discussed how to ease adoption of Junos OS
CONFIDENTIAL
SSFJUN01G
In this course, we:

Described the Junos OS command-line interface (CLI)
Demonstrated specialized features of the Junos CLI that save time and avert downtime
Described basics of routing using Junos OS
Discussed how to ease adoption of Junos OS
SSFJUN01-I
120
Slide 118
Additional Resources
Education Services training classes
http://www.juniper.net/training/technical_education/
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

elearning@juniper.net
CONFIDENTIAL
SSFJUN01G
For additional resources or to contact the Juniper Networks eLearning team, click the links on the screen.
SSFJUN01-I
121
Slide 119
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 Practice Test and the Student
Survey
The test will allow you to gauge your knowledge
of the material covered in this course
The survey will allow you to give feedback on
the quality and usefulness of the course
CONFIDENTIAL
SSFJUN01G
You have reached the end of this Juniper eLearning module. You should now return to your Juniper
Learning Center to take the Practice Test and the Student Survey. The test will allow you to gauge your
knowledge of the material covered in this course. The survey will allow you to give feedback on the quality
and usefulness of the course.
SSFJUN01-I
122
Slide 120
2011 Juniper Networks, Inc.
Juniper Networks, Inc. All rights reserved. Juniper Networks, the

Juniper Networks logo, Junos, NetScreen, and ScreenOS are
registered trademarks of Juniper Networks, Inc. in the United
States and other countries. Junose is a trademark of Juniper
Networks, Inc. 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.
CONFIDENTIAL
SSFJUN01G
Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen,
and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries.
Junose is a trademark of Juniper Networks, Inc. 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.
SSFJUN01-I
123
Slide 121
CONFIDENTIAL
SSFJUN01-I
124
e d u c a t io n se rv ic e s c o u rsew a re
Corp orat e and Sales Head q uart ers
APAC Head q uart ers
EMEA Head q uart ers
Junip er Net w orks, Inc.

119 4 Nort h Mat hild a Avenue
Sunnyvale, CA 9 4 0 8 9 USA
Phone: 8 8 8 .JUNIPER
( 8 8 8 .58 6 .4737)
or 4 0 8 .74 5.20 0 0
Fax: 4 0 8 .74 5.210 0
w w w.junip er.net
Junip er Net w orks ( Hong Kong)

26 / F, Cit yp laza One
1111 Kings Road
Taikoo Shing, Hong Kong
Phone: 8 52.2332.36 36
Fax: 8 52.2574 .78 0 3
Junip er Net w orks Ireland

Airsid e Business Park
Sw ord s, Count y Dub l in, Ireland
Phone: 35.31.8 9 0 3.6 0 0
EMEA Sales: 0 0 8 0 0 .4 58 6 .4737
Fax: 35.31.8 9 0 3.6 0 1
Copyright 20 10 Junip er Net w orks, Inc.

Al l right s reserved. Junip er Net w orks,
t he Junip er Net w orks logo, Junos,
Net Screen, and ScreenOS are regist ered
t rad em arks of Junip er Net w orks, Inc. in
t he Unit ed St at es and ot her count ries.
Al l ot her t rad em arks, service m arks,
regist ered m arks, or regist ered service
m arks are t he p rop ert y of t heir
resp ect ive ow ners. Junip er Net w orks
assum es no resp onsib il it y f or any
inaccuracies in t his d ocum ent . Junip er
Net w orks reserves t he right t o change,
m od if y, t ransf er, or ot herw ise revise t his
p ub l icat ion w it hout not ice.

Juniper

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Juniper

Transféré par

Droits d'auteur :

Formats disponibles

e d u c a t io n se rv ic e s c o u rsew a re

JUNOS OPERATING SYSTEM

Junos Operating System Highlights

Juniper Networks, Inc.

Junos Operating System Highlights

Welcome to Juniper Networks Junos Operating System Highlights eLearning module.

Juniper Networks, Inc.

Junos Operating System Highlights

2011 Juniper Networks, Inc. All rights reserved.

This course consists of five sections.

Juniper Networks, Inc.

Junos Operating System Highlights

2011 Juniper Networks, Inc. All rights reserved.

Upon completing this course, you will be able to:

Juniper Networks, Inc.

Junos Operating System Highlights

Juniper Networks, Inc.

Junos Operating System Highlights

Discuss the Juniper Difference

2011 Juniper Networks, Inc. All rights reserved.

After successfully completing this section, you will be able to:

Juniper Networks, Inc.

Junos Operating System Highlights

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

Why Is Juniper Different?

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

How Competitors Manage the Complexity

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

Junos: A Universal Language

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

An Open Platform Approach

2011 Juniper Networks, Inc. All rights reserved.

Thinking boxes first limits your design perspective.

Juniper Networks, Inc.

Junos Operating System Highlights

Open Across Software Layers

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

Difference of One Junos

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

Junos OS Separate Control and Forwarding

Provides options for

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

Junos OS Modular Architecture

Well-defined interfaces for

Contain faults and enable

Controls the modules

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Junos Operating System Highlights

2011 Juniper Networks, Inc. All rights reserved.