AJER-12.a Student Guide Volume 1

»¿´·¿à±¬®¿·²ò½±³ò¶±
»¿´·¿à±¬®¿·²ò½±³ò¶±
Advanced Junos Enterprise Routing
12.a
Student Guide
Volume
Worldwide Education Services
1133 Innovation Way

Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Course Number: EDU-JUN-AJER
»¿´·¿à±¬®¿·²ò½±³ò¶±
This document is produced by Juniper Networks, Inc.
This document or any part thereof may not be reproduced or transmitted in any form under penalty of law, without the prior written permission of Juniper Networks
Education Services.
Juniper Networks, the Juniper Networks logo, Junos, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Advanced Junos Enterprise Routing Student Guide, Revision 12.a

Copyright © 2014 Juniper Networks, Inc. All rights reserved.
Printed in USA.
Revision History:
Revision 10.aMarch 2011
Revision 11.aApril 2012
Revision 12.aAugust 2014
The information in this document is current as of the date listed above.
The information in this document has been carefully verified and is believed to be accurate for software Release 12.1X46-D20.5. Juniper Networks assumes no
responsibilities for any inaccuracies that may appear in this document. In no event will Juniper Networks be liable for direct, indirect, special, exemplary,
incidental, or consequential damages resulting from any defect or omission in this document, even if advised of the possibility of such damages.
Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
YEAR 2000 NOTICE
Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The Junos operating system has
no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
SOFTWARE LICENSE
The terms and conditions for using Juniper Networks software are described in the software license provided with the software, or to the extent applicable, in an
agreement executed between you and Juniper Networks, or Juniper Networks agent. By using Juniper Networks software, you indicate that you understand and
agree to be bound by its license terms and conditions. Generally speaking, the software license restricts the manner in which you are permitted to use the Juniper
Networks software, may contain prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should
consult the software license for further details.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Contents
Chapter 1: Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Chapter 2: OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

OSPFv2 Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Link-State Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14
Protocol Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-41
OSPF Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-62
OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-68
Configuring and Monitoring OSPF Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-79
Chapter 3: OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Review of OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Stub Area Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Stub Area Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
NSSA Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17
NSSA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23
Route Summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26
Configuring and Monitoring OSPF Areas and Route Summarization Lab . . . . . . . . . . . . . . . .3-38
Chapter 4: OSPF Case Studies and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

IGP Transition Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Transition Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
OSPF Multi-Area Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
External Reachability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26
Virtual Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
Configuring and Monitoring Routing Policy and Advanced OSPF Options Lab . . . . . . . . . . . .4-53
Acronym List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ACR-1
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net Contents iii
»¿´·¿à±¬®¿·²ò½±³ò¶±
iv Contents www.juniper.net
Course Overview
This three-day course is designed to provide students with the tools required for implementing, monitoring, and
troubleshooting Layer 3 components in an enterprise network. Detailed coverage of OSPF, BGP, class of service (CoS), and
multicast is strongly emphasized.
Through demonstrations and hands-on labs, students will gain experience configuring and monitoring the Junos operating
system and monitoring device and protocol operations. This course is based on Junos OS Release 12.1X46-D20.5.
Objectives
After successfully completing this course, you should be able to:
Describe the various OSPF link-state advertisement (LSA) types.
Explain the flooding of LSAs in an OSPF network.
Describe the shortest-path-first (SPF) algorithm.
Describe OSPF area types and operations.
Configure various OSPF area types.
Summarize and restrict routes.
Identify scenarios that require routing policy or specific configuration options.
Use routing policy and specific configuration options to implement solutions for various scenarios.
Describe basic BGP operation and common BGP attributes.
Explain the route selection process for BGP.
Describe how to alter the route selection process.
Configure some advanced options for BGP peers.
Describe various BGP attributes in detail and explain the operation of those attributes.
Manipulate BGP attributes using routing policy.
Describe common routing policies used in the enterprise environment.
Explain how attribute modifications affect routing decisions.
Implement a routing policy for inbound and outbound traffic using BGP.
Identify environments that may require a modified CoS implementation.
Describe the various CoS components and their respective functions.
Explain the CoS processing along with CoS defaults on SRX Series Services Gateways.
Describe situations when some CoS features are used in the enterprise.
Implement some CoS features in an enterprise environment.
Describe IP multicast traffic flow.
Identify the components of IP multicast.
Explain how IP multicast addressing works.
Describe the need for reverse path forwarding (RPF) in multicast.
Explain the role of Internet Group Management Protocol (IGMP) and describe the available IGMP versions.
Configure and monitor IGMP.
Identify common multicast routing protocols.
Describe rendezvous point (RP) discovery options.
Configure and monitor Physical Interface Module (PIM) sparse modes.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configure and monitor RP discovery mechanisms.
www.juniper.net Course Overview v

Describe the basic requirements, benefits, and caveats of source-specific multicast (SSM).
List the address ranges used for SSM.
Illustrate the role of Internet Group Management Protocol version 3 (IGMPv3) and PIM sparse mode
(PIM-SM) in an SSM implementation.
Configure and monitor SSM.
Intended Audience
This course benefits individuals responsible for configuring and monitoring devices running the Junos OS.
Course Level
Advanced Junos Enterprise Routing is an advanced-level course.
Prerequisites
Students should have basic networking knowledge and an understanding of the Open Systems Interconnection (OSI)
model and the TCP/IP protocol suite. Students should also have working experience with basic routing principles.
Students should also attend the Introduction to the Junos Operating System (IJOS), Junos Routing Essentials (JRE), and
Junos Intermediate Routing (JIR) courses prior to attending this class.
»¿´·¿à±¬®¿·²ò½±³ò¶±
vi Course Overview www.juniper.net
Course Agenda
Day 1
Chapter 1: Course Introduction
Chapter 2: OSPF
Lab 1: Configuring and Monitoring OSPF
Chapter 3: OSPF Areas
Lab 2: Configuring and Monitoring OSPF Areas and Route Summarization
Chapter 4: OSPF Case Studies and Solutions
Lab 3: Configuring and Monitoring Routing Policy and Advanced OSPF Options
Day 2
Chapter 5: BGP
Lab 4: Implementing BGP
Chapter 6: BGP Attributes and Policy
Lab 5: BGP Attributes
Chapter 7: Enterprise Routing Policies
Lab 6: Implementing Enterprise Routing Policies
Day 3
Chapter 8: Introduction to Multicast
Chapter 9: Multicast Routing Protocols and SSM
Lab 7: Implementing PIM-SM
Lab 8: Implementing SSM
Chapter 10: Class of Service
Lab 9: Implementing CoS Features in the Enterprise
Appendix A: BGP Route Reflection
Lab 10: BGP Route Reflection (Optional)
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net Course Agenda vii
Document Conventions
CLI and GUI Text

Frequently throughout this course, we refer to text that appears in a command-line interface (CLI) or a graphical user
interface (GUI). To make the language of these documents easier to read, we distinguish GUI and CLI text from chapter
text according to the following table.
Style Description Usage Example
Franklin Gothic Normal text. Most of what you read in the Lab Guide
and Student Guide.
Courier New Console text:

commit complete
Screen captures
Noncommand-related Exiting configuration mode
syntax
GUI text elements:
Select File > Open, and then click
Menu names Configuration.conf in the
Filename text box.
Text field entry
Input Text Versus Output Text

You will also frequently see cases where you must enter input text yourself. Often these instances will be shown in the
context of where you must enter them. We use bold style to distinguish text that is input versus text that is simply
displayed.
Normal CLI No distinguishing variant. Physical interface:fxp0,

Enabled
Normal GUI
View configuration history by clicking
Configuration > History.
CLI Input Text that you must enter. lab@San_Jose> show route
GUI Input Select File > Save, and type
config.ini in the Filename field.
Defined and Undefined Syntax Variables

Finally, this course distinguishes between regular text and syntax variables, and it also distinguishes between syntax
variables where the value is already assigned (defined variables) and syntax variables where you must assign the value
(undefined variables). Note that these styles can be combined with the input style as well.
CLI Variable Text where variable value is already policy my-peers

assigned.
GUI Variable Click my-peers in the dialog.
CLI Undefined Text where the variables value is Type set policy policy-name.
the users discretion or text where
ping 10.0.x.y
the variables value as shown in
GUI Undefined the lab guide might differ from the Select File > Save, and type
value the user must input filename in the Filename field.
according to the lab topology.
»¿´·¿à±¬®¿·²ò½±³ò¶±
viii Document Conventions www.juniper.net
Additional Information
Education Services Offerings

You can obtain information on the latest Education Services offerings, course dates, and class locations from the World
Wide Web by pointing your Web browser to: http://www.juniper.net/training/education/.
About This Publication
The Advanced Junos Enterprise Routing Student Guide was developed and tested using software
Release 12.1X46-D20.5. Previous and later versions of software might behave differently so you should always consult
the documentation and release notes for the version of code you are running before reporting errors.
This document is written and maintained by the Juniper Networks Education Services development team. Please send
questions and suggestions for improvement to training@juniper.net.
Technical Publications
You can print technical manuals and release notes directly from the Internet in a variety of formats:
Go to http://www.juniper.net/techpubs/.
Locate the specific software or hardware release and title you need, and choose the format in which you
want to view or print the document.
Documentation sets and CDs are available through your local Juniper Networks sales office or account representative.
Juniper Networks Support
For technical support, contact Juniper Networks at http://www.juniper.net/customers/support/, or at 1-888-314-JTAC
(within the United States) or 408-745-2121 (from outside the United States).
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net Additional Information ix
»¿´·¿à±¬®¿·²ò½±³ò¶±
x Additional Information www.juniper.net
Chapter 1: Course Introduction
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Will Discuss:
Objectives and course content information;
Additional Juniper Networks, Inc. courses; and
The Juniper Networks Certification Program.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 12 Course Introduction www.juniper.net
Introductions
The slide asks several questions for you to answer during class introductions.
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net Course Introduction Chapter 13
Course Contents
The slide lists the topics we discuss in this course.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Prerequisites
The slide lists the prerequisites for this course.
»¿´·¿à±¬®¿·²ò½±³ò¶±
General Course Administration

The slide documents general aspects of classroom administration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Training and Study Materials

The slide describes Education Services materials that are available for reference both in the classroom and online.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Additional Resources
The slide provides links to additional resources available to assist you in the installation, configuration, and operation of
Juniper Networks products.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Satisfaction Feedback
Juniper Networks uses an electronic survey system to collect and analyze your comments and feedback. Depending on the
class you are taking, please complete the survey at the end of the class, or be sure to look for an e-mail about two weeks
from class completion that directs you to complete an online survey form. (Be sure to provide us with your current e-mail
address.)
Submitting your feedback entitles you to a certificate of class completion. We thank you in advance for taking the time to
help us improve our educational offerings.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Juniper Networks Education Services Curriculum

Juniper Networks Education Services can help ensure that you have the knowledge and skills to deploy and maintain
cost-effective, high-performance networks for both enterprise and service provider environments. We have expert training
staff with deep technical and industry knowledge, providing you with instructor-led hands-on courses in the classroom and
online, as well as convenient, self-paced eLearning courses.
Courses
You can access the latest Education Services offerings covering a wide range of platforms at
http://www.juniper.net/training/technical_education/.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Juniper Networks Certification Program

A Juniper Networks certification is the benchmark of skills and competence on Juniper Networks technologies.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Juniper Networks Certification Program Overview

The Juniper Networks Certification Program (JNCP) consists of platform-specific, multitiered tracks that enable participants
to demonstrate competence with Juniper Networks technology through a combination of written proficiency exams and
hands-on configuration and troubleshooting exams. Successful candidates demonstrate a thorough understanding of
Internet and security technologies and Juniper Networks platform configuration and troubleshooting skills.
The JNCP offers the following features:
Multiple tracks;
Multiple certification levels;
Written proficiency exams; and
Hands-on configuration and troubleshooting exams.
Each JNCP track has one to four certification levelsAssociate-level, Specialist-level, Professional-level, and Expert-level. The
Associate-level, Specialist-level, and Professional-level exams are computer-based exams composed of multiple choice
questions administered at Prometric testing centers worldwide.
Expert-level exams are composed of hands-on lab exercises administered at select Juniper Networks testing centers. Please
visit the JNCP website at http://www.juniper.net/certification for detailed exam information, exam pricing, and exam
registration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Preparing and Studying

The slide lists some options for those interested in preparing for Juniper Networks certification.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Junos Genius
The Junos Genius application takes certification exam preparation to a new level. With Junos Genius you can practice for
your exam with flashcards, simulate a live exam in a timed challenge, and even build a virtual network with device
achievements earned by challenging Juniper instructors. Download the app now and Unlock your Genius today!
»¿´·¿à±¬®¿·²ò½±³ò¶±
Find Us Online
The slide lists some online resources to learn and share information about Juniper Networks.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Any Questions?
If you have any questions or concerns about the class you are attending, we suggest that you voice them now so that your
instructor can best address your needs during class.
This chapter contains no review questions.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 2: OSPF
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Will Discuss:
OSPF link-state advertisements (LSAs);
How LSAs are flooded throughout the network;
The shortest path first (SPF) algorithm;
OSPF link metrics;
OSPF authentication methods; and
The differences between OSPFv2 and OSPFv3.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 22 OSPF www.juniper.net
OSPFv2 Review
The slide lists the topics we will discuss. We discuss the highlighted topic first.
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net OSPF Chapter 23
Link-State Protocol
OSPF is an interior gateway protocol (IGP) based on the concept of a link-state database (LSDB). As such, each
OSPF-speaking router in the network attempts to form an adjacency with each neighboring OSPF router. When these
adjacencies are in place, each router generates and floods LSAs into the network in a reliable manner. The LSAs are placed
into the LSDB on each router where the SPF algorithm is calculated to find the best path to each end node in the network.
Neighbors Use Hello Packets

OSPF routers send out hello packets to form and maintain adjacencies with their neighbors.
LSAs Are Flooded

OSPF uses IP protocol number 89 and the AllSPFRouters multicast address of 224.0.0.5 to flood LSAs. OSPF routers forward
all LSAs through all OSPF-configured interfaces except the one on which an LSA was received. The LSAs are then installed
into the OSPF database, which forms the topology map of the network. Finally, the SPF algorithm is run to determine the
shortest path to each destination subnet.
Hierarchical Design
OSPF gains scalability as a protocol through the use of a hierarchical design. Portions of the network are designated as
separate areas. These remote areas are then connected through a common area called the backbone.
Continued on the next page.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Designated Router Election
On a broadcast segment, OSPF routers elect a single node to represent the segment to the network. This node is called the
designated router (DR). It forms an OSPF adjacency with all routers on the segment and floods a network LSA into the
appropriate area. The criteria for electing the DR is the highest configured priority on the segment, which is set to 128 by
default. The second criteria for electing a DR is the highest router ID on the segment.
The election of a DR on a broadcast segment is a nondeterministic event. Thus, the router with the best criteria might not
always be the DR for the segment. An operational DR maintains its status on the segment until it stops operating.
The first OSPF router on a link determines itself as the DR if it does not detect a Hello from another router.
Currently, a lot of Ethernet segments are used as point-to-point, full-duplex links. This eliminates the need for a DR election.
Use the interface-type p2p command on both sides of the link to change the default interface type. Using this option
can save up to forty seconds of wait time to get the OSPF adjacency to a full state.
[edit protocols ospf]
user@router# show
area 0.0.0.0 {
interface ge-0/0/0.0 {
interface-type p2p;
}
}
»¿´·¿à±¬®¿·²ò½±³ò¶±
The Link-State Database

In addition to discovering neighbors and flooding LSAs, a third major task of the OSPF protocol is to create and maintain the
LSDB. The link-state, or topological, database stores the LSAs as a series of records. The records stored within the LSDB
include details such as the advertising routers ID, its attached networks and neighboring routers, and the cost associated
with those networks or neighbors. According to the OSPF RFC, each router in an OSPF area must have an identical LSDB to
ensure accurate routing knowledge. We discuss OSPF areas later in this course.
The information recorded in the database is used as input data to calculate the shortest paths (that is, least-cost paths) for
all destination prefixes within the network. OSPF uses the SPF algorithm (also known as the Dijkstra algorithm) to calculate,
all at once, the shortest paths to all destinations. It performs this calculation by creating a tree of shortest paths
incrementally and picking the best candidate from that tree. The results of this calculation are then handed to the routers
routing table for the actual forwarding of data packets. For the purposes of this course, the SPF and Dijkstra algorithm are
considered the same.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Packet Types
Every OSPF router uses a specific set of packets to perform its functions. The packet types include the following:
Hello: Sent by each router to form and maintain adjacencies with its neighbors.
Database description: Used by the router during the adjacency formation process. It contains the header
information for the contents of the LSDB on the router.
Link-state request: Used by the router to request an updated copy of a neighbors LSA.
Link-state update: Used by the router to advertise LSAs into the network.
Link-state acknowledgment: Used by the router to ensure the reliable flooding of LSAs throughout the network.
»¿´·¿à±¬®¿·²ò½±³ò¶±
.
Hierarchical Design
The slide graphically displays the hierarchical nature of OSPF. A backbone area (0.0.0.0) is the connecting point for all other
areas. By specification, each area must attach to the backbone in at least one location.
Areas 1, 2, and 3 each contain routers internal to that area as well as a single area border router (ABR). The ABR generates
summary LSAs that represent the routes within its area and floods those to the backbone. The ABR is also responsible for
generating summary LSAs that represent the backbone routes and injecting these LSAs into its attached area.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Routers
OSPF routers can take on a number of different roles within an OSPF domain. The following list shows the common types of
OSPF routers along with a brief description:
Area border router (ABR): An OSPF router with links in two areas, the ABR is responsible for connecting OSPF
areas to the backbone. It transmits network information between the backbone and other areas.
Autonomous system boundary router (ASBR): An OSPF router that injects routing information from outside the
OSPF autonomous system (AS), an ASBR is typically located in the backbone. However, the OSPF specification
allows an ASBR to be in other areas as well.
Backbone router: Defined as any OSPF router with a link to Area 0 (the backbone), this router can be completely
internal to Area 0 or an ABR depending on whether it has links to other, nonbackbone areas.
Internal router: An internal router is an OSPF router with all its links within an area. If that router is located
within the backbone area (Area 0.0.0.0), it is also known as a backbone router.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Single Area Configuration Example

The slide illustrates the basic hierarchy and syntax used to configure a single OSPFv2 area. OSPFv2 is configured at the
[edit protocols ospf] hierarchy as shown in the example.
OSPF Interfaces
All logical interfaces associated with the area should be listed under the area. Remember the loopback interface, if it should
be advertised.
»¿´·¿à±¬®¿·²ò½±³ò¶±
What If...?
In the slide, interface lo0.0 has four addresses configured on it. Typically, you would put interface lo0.0 into OSPF using the
set area <area-id> interface <interface-name> command. However, doing this will create four LSAs: one
for each of the configured addresses on interface lo0.0. You might come across a situation such as this for which you do not
want to advertise all of the addresses into OSPF. A solution to this problem is offered on the next page.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Then...
The slide shows a solution to our problem. By specifying the specific interface address to advertise, only one LSA is created
in the LSDB.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Multi-Area Configuration Example

The slide illustrates the basic hierarchy and syntax used to configure the OSPFv2 multiarea. As in the single area example
previously shown, the configuration is performed at the [edit protocols ospf] hierarchy.
OSPF Interfaces
All logical interfaces associated with the particular area should be listed under that area. Remember the loopback interface,
if it should be advertised.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Link-State Advertisements
The slide highlights the topic we discuss next.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Multiple LSAs in a Single Update

Each link-state update packet sent into the network by an OSPF-speaking router can carry multiple different LSAs. This ability
saves network resources by allowing routers to use transmission and routing capacity more efficiently.
Link-State Update Format

The graphic illustrates the format of the link-state update packet. Following the standard OSPF header, the update packet
contains a 4-byte field used to notify other routers as to the number of advertisements stored in the update message. This
field is followed by the LSAs themselves, each with its own header and format.
»¿´·¿à±¬®¿·²ò½±³ò¶±
LSA Types
The following list provides the details of the LSA types:
Router LSA: Sent by each router to describe its individual links and their status.
Network LSA: Sent by the DR on the broadcast network.
Summary LSA: Sent by an ABR to describe routes or other information from one area into another.
AS external LSA: Sent by an ASBR to describe routes external to the OSPF domain.
Group membership LSA: Used to support Multicast Open Shortest Path First (MOSPF).
NSSA LSA: Sent by an ASBR in a not-so-stubby area (NSSA) to describe routes external to the OSPF domain.
External attributes LSA: Used to tunnel attributes used by other routing protocols through OSPF.
Opaque LSAs: Used to transmit information not currently supported by other LSA types. Examples include
graceful restart and traffic engineering information.
»¿´·¿à±¬®¿·²ò½±³ò¶±
LSA Functions
Each of the LSA types listed previously has a specific function within the OSPF domain. They each describe a portion of the
topology used by the SPF algorithm to supply routing information to a routing table. We discuss each LSA in more detail on
future slides.
Each LSA has a maximum age of 3600 seconds (1 hour) associated with it. This maximum provides a mechanism for
removing stale information from the database. To ensure that its LSAs are up to date, each OSPF router periodically
refreshes them prior to reaching the maximum age limit. The Junos operating system performs this refresh every 3000
seconds (50 minutes).
LSAs Not Supported

The Junos OS does not support some of the LSA types listed here. These LSAs are the group membership (Type 6), external
attributes (Type 8), and the domain-scope opaque (Type 11) advertisements.
»¿´·¿à±¬®¿·²ò½±³ò¶±
LSA Header
The following list details the information contained in the LSA header:
Link-state age (2 bytes): Measured in seconds, the LS age is the time from when the LSA was first originated.
Each router increments this field prior to reflooding the LSA.
Options (1 byte): Indicates support for OSPF options. Within the context of an individual LSA, the E bit (position
7) is set in all external LSAs and the P bit (position 5) is set in all NSSA external LSAs.
Link-state type (1 byte): Encodes the specific LSA type.
Link-state ID (4 bytes): Describes various portions of the OSPF domain. Each LSA type uses this field in a
different manner.
Advertising router (4 bytes): The router ID of the router that first originated the LSA.
Link-state sequence number (4 bytes): Verifies that each router has the most recent version of an LSA. This field
is incremented each time a new version is generated. Values range from 0x80000000 to 0x7FFFFFFF.
Link-state checksum (2 bytes): The checksum of the entire LSA contents, minus the LS age field. This field is
used to ensure data integrity in the LSDB.
Length (2 bytes): The entire length of the individual LSA, including the header.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Router LSA
Each OSPF-speaking router generates a Type 1 LSA to describe the status and cost (metric) of all interfaces on the router.
This LSA is flooded to each router in the OSPF area. It is defined as having an area scope; therefore, it is not flooded across
an area boundary. In addition to the standard LSA header, the router LSA also contains the following fields:
V, E, and B bits (1 byte): Following five bits set to a value of 0, the V, E, and B bits represent the characteristics
of the originating router. The V bit is set when a virtual link is established. An ASBR sets the E bit. An ABR sets
the B bit.
Number of links (2 bytes): This value gives the total number of links represented by the following set of fields.
Link ID (4 bytes): This field represents to what the far side of the link is connected. It is used in conjunction with
the link type field.
Link data (4 bytes): This field represents to what the near side of the link is connected. It is used in conjunction
with the link type field.
Link type (1 byte): This field describes the type of link.
Number of Multi Topology IDs (MT-IDs) (1 byte)
Metric (2 bytes): This field provides the cost to transmit data out of the interface.
MT-ID (1 byte): Renamed TOS field to represent the multi topology ID.
MT-ID metric (2 bytes): Renamed TOS metric field to represent the Multi Topology (MT) metric.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Additional data (4 bytes):
bytes): This field is unused.

Link ID and Link Data Fields

The information in the router LSAs link ID and link data fields is associated with the type of link OSPF is operating. The
following link types are supported:
Point-to-point (Type 1): On a point-to-point interface, an OSPF router always forms an adjacency with its peer
over an unnumbered connection. As such, the link ID field contains the neighbors router ID. The link data field
contains the IP address of the interface on the local router.
Transit (Type 2): A connection to a broadcast segment is always noted as a transit link. The link ID field contains
the interface IP address of the segments DR. The link data field contains the interface IP address of the local
router.
Stub (Type 3): A router advertises a stub network when a subnet does not connect to any OSPF neighbors.
Advertising a stub network occurs for the loopback interface and any passive interfaces. In addition, the IP
subnet for any point-to-point interface is advertised as a stub because the adjacency was formed over an
unnumbered interface. The link ID field for a stub network contains the IP network number and the link data
field contains the subnet mask.
Virtual link (Type 4): A virtual link operates between an ABR connected to Area 0 and an ABR that is not
connected to Area 0. Once established, the virtual link appears in the Area 0 router LSA of each endpoint. The
link ID field contains the neighbors router ID, and the link data field contains the interface IP address of the
local router.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Router LSA Example

You can see the details of the router LSA in the example on the slide. By using the keyword extensive, you can see each of
the LSA fields. You can gather some important details about the local router by closely examining the LSA:
This router is both an ABR as well as an ASBR. We see this by the setting of bits 0x3. Recall that position 7 (0x2)
is for the E bit, which is set when the originating router is an ASBR. Bit position 8 (0x1) is for the B bit, which is
set when the originating router is an ABR. Combining these two fields results in a value of 0x3, which we see in
the database capture.
This router has three links connected to Area 0, which we can determine because of two factors. First, the link
count field is set to a value of 3. Second, the LSA is shown in the database within the Area 0.0.0.0 section.
Recall that a router LSA has area scope, so a separate LSA is generated for each area representing the links
only within that area.
A single point-to-point link exists, and two links are connected to stub networks. This fact is clearly visible from
the information in the type fields.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Router LSA Example (contd.)
This router LSA was originated by the same router from which the capture was taken. Notice the asterisk (*)
next to the link-state ID value of 192.168.16.1. Also note that the last line of the capture states that this LSA
is Ours.
The router LSA was installed 23 minutes and 21 seconds ago. If not refreshed, the LSA will expire in 36 minutes
and 39 seconds when its 3600 second maximum age is exceeded, and the LSA was last flooded 23 minutes
and 19 seconds ago. These details are shown in the Installed, expires, and sent fields, and they are
present for every LSA in the show ospf database extensive output.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Add Type 1 LSAs to an OSPF Network

Using the information in the router LSA, we can begin to draw a network map based on the LSDB:
We know of three routers within Area 0.0.0.0192.168.16.1 (the local router), 192.168.24.1, and
192.168.36.1;
Two point-to-point subnets connect the three routers10.222.28.0/24 and 10.222.4.0/24;
The IP address of the interface connecting 192.168.16.1 to 192.168.24.1 is 10.222.28.1; and
The IP address of the interface connecting 192.168.36.1 to 192.168.24.1 is 10.222.4.2.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Network LSA
Each OSPF router elected to be the DR on a broadcast link generates a Type 2 LSA. This LSA lists each router connected to
the broadcast link, including the DR itself. In addition to the standard LSA header, the network LSA also contains the
following fields:
Network mask (4 bytes): This field denotes the IP subnet mask for the interface connected to the broadcast
network.
Attached router (4 bytes): This field is repeated for each router connected to the broadcast network. The value
of each instance is the router ID of the attached routers. You can deduce the total number of routers listed by
the length of the LSA.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Network LSA Example

You can see the details of the network LSA in the example on the slide. By using the keyword extensive, you can see each
of the LSA fields. You can gather some important details about this network by closely examining the LSA:
The DR for this network is 10.222.1.2, which you can determine by examining the link-state ID field. This field
lists the DRs IP address.
Because only two instances of the attached router field are present, you can safely deduce that only two routers
are connected to the link. The router IDs of those two routers are 192.168.20.1 and 192.168.40.1.
»¿´·¿à±¬®¿·²ò½±³ò¶±

Using the information in the network LSA, we can add information to our OSPF network map. Remember that all information
is from the perspective of the 192.168.16.1 router.
We know of two routers within Area 0.0.0.1192.168.20.1 and 192.168.40.1;
A broadcast segment connects the two routers together whose address is
10.222.1.0/24; and
The DR for the segment is 192.168.20.1 and its interface address is 10.222.1.1.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Summary LSA
Each ABR that transmits information from one OSPF area into another generates a Type 3 LSA to describe that information.
This LSA is flooded to each router in the OSPF area. This LSA has an area scope; therefore, it is not reflooded across the area
boundary by another ABR. Instead, the receiving ABR generates a new Type 3 LSA describing the link and floods it into the
adjacent area.
In addition to the standard LSA header, the summary LSA also contains the following fields:
Network mask (4 bytes): This field represents the subnet mask associated with the network advertised. It is
used in conjunction with the link-state ID field, which encapsulates the network address in a Type 3 LSA.
Metric (3 bytes): This field provides the cost of the route to the network destination. When the summary LSA is
representing an aggregated route (using the area-range command), this field is set to the largest current
metric of the contributing routes.
MT-ID (1 byte): This field represents the MT-ID value used in a Multi Topology configuration.
MT-ID metric (3 bytes): This field represents the MT-ID metric used in a Multi Topology configuration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Summary LSA Example

You can see the details of the summary LSA in the example on the slide. By using the keyword extensive, you can see
each of the LSA fields. You can gather some important details about the local router by closely examining the LSA:
This router is an ABR because it contains a database for Area 0.0.0.0. Within that area, three summary LSAs
are listed. One of the LSAs (the third one listed) is from the router where the capture was taken. As with the
router LSA earlier, notice that there is an asterisk (*) next to the link-state ID value of 192.168.40.1. Also
note that the last line of the LSA states that the LSA is Ours.
A second router in the backbone (192.168.36.1) generates the two other summary LSAs. The two networks
advertised by that ABR are 10.222.44.0/24 and 192.168.32.1/32. Each of the networks has a metric of 1
encoded within the LSA. The local router adds the cost to reach 192.168.36.1 to the metric of 1 prior to
calculation of the SPF algorithm.
Note that the command output on the slide is truncated. A fourth summary LSA for the 192.168.20.1/32 network is present,
but not shown. This network, however, is shown on the next slide.


Once again, we view the database from the 192.168.16.1 router. Using the information in the summary LSAs, we can add
the following information to our map:
A new router exists in an OSPF area connected to 192.168.36.1;
We do not know the 32-bit value for the area, but we know that an internal area router exists within it
192.168.32.1;
Using the metric values in the summary LSAs, we can determine that the area router and the ABR are
connected over the 10.222.44.0/24 subnet; and
Within Area 0.0.0.1, we now know that the 192.168.20.1 router is directly connected to our local router of
192.168.16.1. We use the summary LSA metric value to make that determination.
»¿´·¿à±¬®¿·²ò½±³ò¶±
ASBR Summary LSA

Each ABR that must transmit information about an ASBR from one OSPF area into another generates a Type 4 LSA to
describe that information. This LSA is flooded to each router in the OSPF area. It is defined as having an area scope;
therefore, another ABR does not reflood it across the area boundary. In addition to the standard LSA header, the ASBR
summary LSA also contains the following fields:
Network mask (4 bytes): This field has no meaning in a Type 4 LSA and is set to 0.0.0.0. The address of the
ASBR is encoded in the link-state ID field.
Metric (3 bytes): This field provides the cost of the route to the ASBR.
MT-ID (1 byte): This field represents the MT-ID value used in a Multi Topology configuration.
MT-ID metric (3 bytes): This field represents the MT-ID metric used in a Multi Topology configuration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
ASBR Summary LSA Example

You can see the details of the ASBR summary LSA in the example on the slide. By using the keyword extensive, you can
see each of the LSA fields. You can gather some important details about the local router by examining the LSA closely.
This router is an ABR because it contains a database for Area 0.0.0.0. Within that area, currently two ASBR
summary LSAs are listed. The second LSA is from the local router (where the capture was taken). As with the
router LSA earlier, notice that there is an asterisk (*) next to the link-state ID value and that the last line of the
LSA states that the LSA is Ours.
The second router in the backbone (192.168.36.1) generates the other ASBR summary LSA.
The two ASBRs being advertised are 192.168.32.1 and 192.168.40.1. You can see this information coded in
the link-state ID fields. Because the router ID of the ASBR is a full 32-bit value, the network mask is not needed
and is set to a value of 0.0.0.0.
The metrics to each of the ASBRs are encoded in the appropriate field in the LSA. As with the summary LSA
(Type 3), the local router must add the cost to reach a remote ABR to the encoded metric prior to calculation of
the SPF algorithm.
»¿´·¿à±¬®¿·²ò½±³ò¶±

The network map does not change based on the information in the ASBR summary LSAs. However, these LSAs do provide a
clue as to the capabilities of the OSPF routers:
Routers 192.168.32.1 and 192.168.40.1 both have export policies configured within OSPF, which means that
they have set the E bit in their router LSAs.
Based on the E bit setting in the router LSAs, the ABRs of 192.168.16.1 and 192.168.36.1 generate ASBR
summary LSAs across the area boundaries. In our case, we see the Type 4 LSAs within Area 0.0.0.0.
»¿´·¿à±¬®¿·²ò½±³ò¶±
AS External LSA
Each ASBR generates a Type 5 LSA to advertise any networks external to the OSPF domain. This LSA is flooded to each
nonstub router in the entire OSPF domain. In addition to the standard LSA header, the AS external LSA also contains the
following fields:
Network mask (4 bytes): This field represents the subnet mask associated with the network advertised. It is
used in conjunction with the link-state ID field, which encapsulates the network address in a Type 5 LSA.
E bit (1 byte): The E bit determines the type of external metric represented by the metric field. It is followed by 7
bits, all set to 0 to make up the entire byte. A value of 0, the default value, indicates that this is a Type 2 external
metric. Thus, any local router should use the encoded metric as the total cost for the route when performing an
SPF calculation. A value of 1 indicates that this is a Type 1 external metric. Therefore, the encoded metric of the
route should be added to the cost to reach the advertising ASBR. This additive value then represents the total
cost for the route.
Metric (3 bytes): This field represents the cost of the network as set by the ASBR.
Forwarding address (4 bytes): This field provides the address toward which packets should be sent to reach the
network. A value of 0.0.0.0 represents the ASBR itself.
External route tag (4 bytes): This 32-bit value field can be assigned to the external route. OSPF does not use this
value, but it might be interpreted by other protocols.
MT-ID and MT-ID metric fields (4 bytes): These fields represent the MT-ID and MT-ID metric values used in a
Multi Topology configuration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
AS External LSA Example

You can see the details of the AS external LSA in the example on the slide. By using the keyword extensive, you can see
each of the LSA fields. You can gather some important details about the local router by examining the LSA closely:
The external LSDB lists all the LSAs. This listing denotes their domain scope status as not belonging to a
particular OSPF area.
This router is generating the first LSA listed. As with the router LSA earlier, an asterisk (*) exists next to the
link-state ID value, and the last line of the LSA states that the LSA is Ours.
Different routers generate each of the other three LSAs because the advertising router field is different for each
LSA.
Examination of the link-state ID and the network mask fields shows that the four different networks advertised
are 192.168.17.0/24, 192.168.33.0/24,
192.168.37.0/24, and 192.168.41.0/24. Each of these networks has a metric value of 0 encoded. In addition,
each of these LSAs is a Type 2 metric (as seen by the type field). Type 2 is the default type for route
redistribution. It reflects only the cost of the path from the ASBR to the destination. A Type 1 tells the local
router to add the cost to reach the remote ASBR to the encoded metric prior to calculation of the SPF algorithm.
The metric to the ASBR is used because the forwarding address field for each LSA is listed as 0.0.0.0.
»¿´·¿à±¬®¿·²ò½±³ò¶±

The addition of AS external LSAs to our network map displays the external routes being advertised into the network:
The 192.168.17.0/24 route is being injected by the 192.168.16.1 router;
The 192.168.33.0/24 route is being injected by the 192.168.32.1 router;
The 192.168.37.0/24 route is being injected by the 192.168.36.1 router; and
The 192.168.41.0/24 route is being injected by the 192.168.40.1 router.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA External LSA Origination

Each ASBR within the NSSA generates a Type 7 LSA to advertise any networks external to the OSPF domain. This LSA is
flooded to each router within the NSSA. Because the LSA has only an area flooding scope, it is not sent into other adjacent
areas.
The format of the NSSA external LSA is exactly the same as the AS external LSA (Type 5) described on an earlier slide. The
only difference between the two LSAs is in the use of the forwarding address field. With the Type 7 LSA, the forwarding
address depends on whether the network connecting the NSSA to the adjacent system is known as an internal route to the
NSSA. If the network is known, the next-hop address of the remote router is placed into the forwarding address field. If the
network is not known, the forwarding address field contains the router ID of the ASBR.
By definition, only NSSA-capable routers can interpret a Type 7 LSA. Having only NSSA-capable routers able to interpret this
LSA type causes a problem with flooding the routing knowledge throughout the OSPF domain because not all routers are
configured to support NSSA. Furthermore, the NSSA external LSA represents the same type of information as the AS external
LSA, and each OSPF router expects to receive an LSA for all external routes. This apparent contradiction is resolved by
allowing the ABR to generate an AS external LSA (Type 5) on behalf of the NSSA ASBR. For each Type 7 LSA received, the ABR
translates the information into a Type 5 LSA and sends that information into the backbone. This translation is performed by
the ABR with the highest router ID. The other backbone routers do not know that the original information came from an NSSA
and perform their duties as previously discussed.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA External LSA Translation
When an ASBR is also an ABR with an NSSA area attached to it, a Type 7 LSA is exported into the NSSA area by default. If the
ABR is attached to multiple NSSAs, a separate Type 7 LSA is exported into each NSSA by default. Use the no-nssa-abr
command to disable the export.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA External LSA Example

You can see the details of the NSSA external LSA in the example on the slide. The 192.168.32.1 ASBR generated this LSA. By
using the keyword extensive, you can see each of the LSA fields. You can gather some important details about the local
router by examining the LSA closely:
Notice that the LSA is listed within the Area 0.0.0.2 database. This listing denotes its area scope status as
belonging to a single NSSA area.
An examination of the link-state ID and the network mask fields shows that the network advertised is
192.168.33.0/24. This network has a metric value of 0 encoded. It also is listed as a Type 2 metric (as seen by
the type field).
The NSSA does not know the network connecting the ASBR to the remote domain. You can see this fact by
examining the forwarding address field where it lists the router ID of the ASBR, 192.168.32.1.
»¿´·¿à±¬®¿·²ò½±³ò¶±

When we focus our attention on the 192.168.36.1 ABR, we now get some added information about the network composition:
The area attached to the 192.168.36.1 router is Area 0.0.0.2. It is also currently configured as an NSSA.
The 192.168.33.0/24 route is being injected into Area 0.0.0.2 as a Type 7 LSA. It is translated into a Type 5 LSA
by the 192.168.36.1 router.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Future Extensibility
RFC 2370 defines the OSPF opaque LSA. It was designed to extend the protocol to support future enhancements without
generating new LSA types. As of this writing, production networks use both the Type 9 and Type 10 opaque LSAs. The Type 9
LSA supports graceful restart. The Type 10 LSA supports MPLS traffic engineering. The Type 11 opaque LSA is not used at
this time.
Flooding Scope
The main difference between the opaque LSAs is in the flooding scope of each type: The Type 9 LSA has a link-local scope,
the Type 10 LSA has an area scope, and the Type 11 LSA has domain scope.
Opaque LSA Format

The format of the opaque LSA has the standard LSA header followed by some number of octets containing
application-specific information. You can interpret the total number of octets contained in the message by examining the
length field in the LSA header. In addition, the link-state ID field is segmented into a 1-byte opaque type field and a 3-byte
opaque ID field. The Internet Assigned Numbers Authority (IANA) has the responsibility of assigning new opaque type codes
in the
0127 range. Values between 128 and 255 are set aside for private and experimental use only.
Opaque-capable routers communicate their ability to each other by using a new bit in the options field. Bit position 2 is
defined as the O bit. A value of 1 in this bit position allows a remote router to flood opaque LSAs to the local router. A value of
0 tells the remote router not to flood those LSA types.

Protocol Operations
»¿´·¿à±¬®¿·²ò½±³ò¶±
LSA Flooding Scopes

As discussed in previous slides, each LSA in the OSPF protocol has a specific scope within which it can be flooded. The slide
graphically displays those flooding scopes.
LSA Types 1 and 2 are generated within each area. Because these LSAs have an area flooding scope, they remain within
their own particular area and are not seen in other areas. The ABR places the routing information contained within these
LSAs into a Type 3 LSA and forwards it across the area boundary. In addition, existing Type 3 LSAs within the backbone are
forwarded into the nonbackbone areas to provide routing knowledge to those routers. This results in Type 3 LSAs within every
area that represent all OSPF routes. Within Area 1, for example, Type 3 LSAs exist that represent Area 0, Area 2, and Area 3.
In the diagram, two ASBRs inject routes into the OSPF domain. The AS external LSAs (Type 5) that represent those routes
have domain flooding scope (with the exception of stub areas). As such, they exist within each OSPF area. To reach those
external routes, the OSPF routers use either router LSAs or ASBR summary LSAs (Type 4) to have knowledge of the ASBRs.
Much like the Type 3 LSAs, the ASBR summary LSAs have area scope, so the area border binds them. Each ABR regenerates
the Type 4 summary LSAs into their respective areas to provide the knowledge of how to route toward the ASBR that is
advertising a given external prefix. This capability leads to Type 4 LSAs for Area 0 being injected into Areas 1, 2, and 3, while
a Type 4 for Area 3 is injected into Areas 0, 1, and 2.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Sample OSPF Database

You can see key details of the OSPF database in the database example on the slide, which has been edited for brevity. To this
point, we have examined small portions of the database through the use of the extensive keyword. We now take a step
back and examine the database as a whole. As before, you can gather some details by examining the database closely:
The local router is an ABR between the backbone and Area 0.0.0.1, which you can see clearly through the
existence of two databases on the router.
Within Area 0.0.0.1, a broadcast link is in use. In addition, the DR on that link is the router whose address is
10.222.1.1. Notice the Type 2 LSA within the Area 0.0.0.1 database. The link-state ID is 10.222.1.1, the DRs IP
address on the link.
Multiple routers act as ASBRs and inject routes into the OSPF domain. Those routers are 192.168.16.1,
192.168.20.1, 192.168.32.1, and 192.168.36.1. The routes advertised by those ASBRs can be used once the
local router has knowledge of how to reach the ASBR.
One of the ASBRs is the local router, 192.168.16.1. One of the external LSAs lists this router ID, and that LSA is
marked with an asterisk (*). A second ASBR is a router within Area 0.0.0.1 (192.168.20.1). This router ID is
found within a router LSA in the Area 0.0.0.1 database. A third ASBR is a router within the backbone
(192.168.36.1). This router ID is found within a router LSA in the Area 0.0.0.0 database. The fourth ASBR is a
router in an area beyond the backbone (192.168.32.1). This router ID is found within an ASBR summary LSA in
both the Area 0.0.0.0 and the Area 0.0.0.1 databases.

OSPF Database Protection

This feature limits the number of LSAs that were not generated by the local router, protecting the LSDB from being flooded
with excessive LSAs. This is a very useful feature if a VPN routing and forwarding (VRF) instance is configured to use OSPF
between the PE and CE routers. Consider, for example, a situation in which a customer misconfigured their OSPF network
and inadvertently sent you several thousand of their routes. The maximum-lsa option can help to avoid such situations.
However, if you had configured the warning-only option, only a warning is issued and the database does not enter the
ignore state but continues to operate as before.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Dijkstra Algorithm
After a router receives a new LSA and places it into the LSDB, the router runs the SPF algorithm. This computation uses the
database as a data source and results in a loop-free network topology using the best metric from the local router to all nodes
in the network.
During the course of this calculation, the algorithm uses three databasesthe LSDB, the candidate database, and the tree
database. As we have explored, the LSDB is the total compilation of routing knowledge in the network. Conceptually, it
consists of multiple tuples in the form of: router ID, neighbor ID, cost. These tuples describe each link in the network.
The first step is as follows:
1. Evaluate each tuple in the candidate database and delete any tuples whose neighbor ID is currently in the tree
database and whose cost to the root is greater than the entry currently in the tree database. Repeat this step
until no more tuples can be deleted.
As the algorithm operates, the local router moves its own local tuple into the tree database and all tuples for its links into the
candidate database. It then performs the following steps until the candidate database is empty:
2. For each new entry in the candidate database, determine the cost from the root to each neighbor ID. Move the
tuple with the lowest cost from the candidate database into the tree database. If multiple tuples exist with an
equal cost, choose one randomly.
3. If a new neighbor ID appears in the tree database, move all tuples in the LSDB with a router ID equal to the new
tree entrys neighbor ID into the candidate database.

Run on a Per-Area Basis
The router calculates the Dijkstra algorithm for each LSDB present on the local router. Recall from an earlier slide that each
OSPF area maintains a separate copy of the database. These copies allow each area to have a separate forwarding topology
independent of another area.
Results Are Passed to the Routing Engine

Once the algorithm is run, the routing table on the Routing Engine receives the results of the tree database. At this point, the
Routing Engine controls the determination of whether to use any individual OSPF route to forward traffic. The preference
value assigned to each route often handles this choice.
The action of calculating the best OSPF route prior to the route being placed into the routing table has a consequence with
regard to the filtering of routing knowledge. An individual filter (or policy) operates on IP routes that enter the router as IP
routes and are placed into the routing table. This form of data flow is not present in OSPF because the routing information
enters the router as an LSA and is only placed into the routing table after the Dijkstra algorithm is performed. Hence, the
best method of filtering OSPF routing knowledge is to keep that information from being placed into the database (on a
per-area basis) in the first place.
OSPF does offer a limited import-policy functionality. You can use the import statement at the [edit protocols
ospf] configuration hierarchy to block external routesthose learned from Type 5 and Type 7 LSAsfrom being installed in
the routing table. This import policy does not, however, prevent LSAs from being flooded. We strongly discourage the use of
OSPF import policy because of the potential for unknowingly discarding traffic.
»¿´·¿à±¬®¿·²ò½±³ò¶±
SPF Calculation Example: Part 1

In the following slides, a sample SPF calculation is displayed. This graphic shows the beginning state of the network
including the routers involved, the configured link metrics, and the LSDB. The network and the LSDB have recently
converged and the local router, RTR-A, is running an SPF calculation to determine the shortest path to each node in the
network.
»¿´·¿à±¬®¿·²ò½±³ò¶±

RTR-A begins by moving its own local database tuple (A,A,0) into the candidate database. The total cost from the neighbor ID
to the root is calculated, which results in a 0 value. In other words, RTR-A is directly connected to itself!
The lowest, and only, tuple in the candidate database is moved to the tree database and RTR-A places itself on the network
map.
»¿´·¿à±¬®¿·²ò½±³ò¶±

All tuples from the most recent node added to the tree database are now added to the candidate database. Because RTR-A
is the most recent entry to the tree database, all of RTR-As tuples are moved from the LSDB into the candidate database.
All known nodes in the tree database are removed from the candidate, of which there are none. (For example, if B were
already in the tree database, the tuple (A,B,1) would be eliminated.)
The cost to each neighbor ID from the root is then calculated. It costs RTR-A 0 to reach itself and 1 to reach RTR-B, so the
total cost to RTR-B is 1. The same calculation is done for RTR-C, and the total cost of 2 is placed into the candidate database.
The lowest cost tuple in the candidate database, (A,B,1), is now moved to the tree database, and RTR-B is placed on the
network map.
The candidate database is not empty, so the algorithm continues.
»¿´·¿à±¬®¿·²ò½±³ò¶±

RTR-B is the most recent entry to the tree database, so all RTR-Bs tuples are moved from the LSDB into the candidate
database.
All known nodes in the tree database are then removed from the candidate. Thus, the (B,A,3) tuple is removed because
RTR-A already has the shortest path to RTR-B.
The cost to each neighbor ID from the root is then calculated. It costs RTR-B 3 to reach RTR-D, and it costs 1 to reach RTR-B
from the root. Therefore, the total cost to reach RTR-D from the root through RTR-B is 4.
The lowest cost tuple in the candidate database, (A,C,2), is now moved over to the tree database, and RTR-C is placed on the
network map.
»¿´·¿à±¬®¿·²ò½±³ò¶±

As RTR-C is the most recent entry to the tree database, its tuples are moved from the LSDB into the candidate database.
All known nodes in the tree database are then removed from the candidate. Thus, the (C,A,4) tuple is removed because
RTR-A already has the shortest path to RTR-C.
The cost to each neighbor ID from the root is then calculated. It costs RTR-C 4 to reach RTR-D, and it costs 2 to reach RTR-C
from the root. So the total cost to reach RTR-D through RTR-C is 6.
The lowest cost tuple in the candidate database, (B,D,3), is moved to the tree database, and RTR-D is placed on the network
map.
»¿´·¿à±¬®¿·²ò½±³ò¶±

RTR-D, through its link to router B, is the most recent entry to the tree database. Therefore, its tuples are moved from the
LSDB into the candidate database.
All known nodes in the tree database are then removed from the candidate. Thus, the (C,D,4), (D,B,1), and (D,C,2) tuples are
removed because RTR-A already has paths to RTR-B, RTR-C, and RTR-D. The candidate database is now empty of all tuples,
so the algorithm stops at this point.
RTR-A now has a complete network map built with the total cost to each node calculated. This information is then passed to
the Junos routing table for its use.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Consecutive SPF Calculations

To enhance the convergence time of an OSPF network during a time of topology changes, the Junos OS by default allows for
the SPF calculation to be run three times in a back-to-back fashion before encountering a mandatory hold-down period. The
5-second hold-down timer used to be hardcoded into the software but is now configurable. The timer ensures that the
network can continue to forward packets, with potentially incorrect routing knowledge, during the convergence period. The
timer also keeps the routing protocol process from hogging the CPU at the expense of other router functions.
Preconfigured Delay Between Calculations

A configurable timer slightly delays consecutive SPF calculations. The default timer value is 200 milliseconds; you can alter it
with the spf-options delay statement. The spf-options delay statement is supported both at the global OSPF
configuration hierarchy and within an OSPF routing instance. Delay values ranging from 50 milliseconds to 1000
milliseconds (1 second) are supported. Regardless of the configuration of this timer, the mandatory 5-second hold-down
timer still starts after the third consecutive rapid SPF calculation.
A current best practice in todays networking environment is setting the spf-options delay value to be slightly larger
than the worst possible propagation delay found in your network. For example, if the delay across the network is 200
milliseconds, you might set the spf-options delay to 250 milliseconds. This setting allows time for all of the duplicate
LSAs to arrive at all routers before the SPF calculation is performed.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Cost of an Interface
Prior to advertising a network into the OSPF domain, each router must determine the cost associated with that network.
Often referred to as the metric, the cost is simply what the router views as the overhead associated with transmitting a
packet on that interface. Because each OSPF-speaking router advertises these cost values in its router LSAs, each router
can determine the total cost (or metric) to reach any destination in the network.
OSPF Default Cost

Each router uses an algorithm to determine the cost of each interfacethe calculation is 100,000,000 divided by the
bandwidth of the interface. If the result of this calculation is less than 1, it is rounded up to a value of 1. Because
100,000,000 is the same as the bandwidth of a Fast Ethernet interface (100 Mbps), all interfaces operating at a faster
bandwidth have their calculated cost less than 1, which becomes rounded up to 1.
Set on a Per-Interface Basis

If you want to alter the automatic cost calculated by the formula above, you can manually set the cost for each interface.
Within the interface portion of the [edit protocols ospf] configuration hierarchy, the metric command assigns a
permanent cost to that interface. Each individual interface on the router can have a separate cost assigned to it.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Change the Cost Calculation

Although each interface can have a cost assigned to it statically, assigning static costs often proves to be an administrative
hassle in all but the smallest networking environments. A middle ground is available to administrators who would like an
automatic calculation but have large bandwidth links in their network.
The solution is to alter the values used in the bandwidth calculation. This alteration not only allows for an automatic cost
assignment but also maintains a consistent ratio across all the router interfaces.
Reference Bandwidth
To alter the calculation values, use the reference-bandwidth command within the [edit protocols ospf]
configuration hierarchy. The value entered has a value in bits per second. You can use the standard Junos shortcut notations
of k (kilobits per second), m (megabits), and g (gigabits). The entered value becomes the new numerator value in the
bandwidth calculation. As noted on the slide, you still can assign a metric statically to an individual interface.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Advertisement of Metric Values

After the OSPF process on a router decides what metric to assign to each interface, that information is flooded into the OSPF
domain within either a Type 1 LSA or a Type 2 LSA. Because these LSAs have an area flooding scope, each router in the
OSPF area receives a copy of the metric values.
SPF Calculations
After receiving a new LSA from another router in the area, the local router performs an SPF calculation using all the values
contained in the router and network LSAs. As mentioned on a previous slide, the cost is calculated from the root node to
every other node in the network using the metric cost of the outgoing interfaces.
Routers Can Disagree

Because each individual router performs a separate SPF calculation, it is possible for two routers on either side of a link to
disagree on the metric of that link. The example on the slide shows that each router has decided upon a different metric
value for its attached links. This discrepancy results in the Hong Kong router calculating a total cost of 45 to reach the
Amsterdam router, while the Amsterdam router calculates a total cost of 60 to reach the Hong Kong router.
While the configuration of different metrics for a single link does not affect the operation of OSPF, asymetric routing might
occur within the network. Asymetric routing might cause response delays for some end users and make it challenging for
network administrators to troubleshoot the network.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Avoid Transit Traffic

OSPF borrows the overload concept from the IS-IS protocol. Its function is to advertise information into the OSPF area, but it
is not to be used for transit traffic, if possible. This function can be useful in two situationswhen a router must be taken out
of the network for maintenance, and when the router has many BGP peers. In the first case, traffic should avoid the router
because it can compromise its ability to forward traffic. In the second case, a network administrator might want the router to
establish its BGP peering sessions fully before handling transit traffic.
Because the overload concept is not native to OSPF, the software is modified to allow for this functionality. When you
configure an OSPF-speaking router for overload, the metrics for all transit interfaces are set to the maximum value of
65,535. The overload router floods these LSAs into the network, where an SPF calculation is performed in each router. The
large metric values generally ensure that transit traffic through the overload router uses alternative paths through the
network. Unlike IS-IS, traffic transits the overload router if no alternative path exists to a given destination.
Overload Settings
You can turn on the overload setting, turn it off as a permanent value, or have a timer associated with it. If the timer is
omitted, the metric values are changed when you commit the configuration. The values will remain until you remove the
overload setting from the configuration and commit it again. However, if you assign a timer value, the metrics are not
changed automatically. The timer associated with the overload setting only initializes when the routing protocol process
initializes. This timer can run from 601800 seconds. When the timer expires, the metrics return to normal in the router
LSAs, but the configuration still contains the overload option.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Case Study
Enterprise networks are typically built with multiple paths from ingress and egress points for redundancy. During
maintenance operations on a router, it can be beneficial to prevent the router from receiving and forwarding transit traffic.
The overload feature provides this function.
In the graphic on the slide, R2 is scheduled for maintenance. An alternate path exists through R3. Once R2 is put in overload
mode the other routers will be notified and transit traffic will traverse R3. Any traffic destined for networks that terminate on
R2 will still be forwarded to R2.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Router ID
Each OSPF-speaking router in a network must select a 32-bit value to use as the router ID (RID) of the router. This RID
uniquely identifies the router within the OSPF domain. It is transmitted within the LSAs used to populate the LSDB and is
used to calculate the shortest-path tree using the method described on a previous slide.
It is very important in a link-state network that no two routers share the same RID value. If two routers share the same RID
value, the LSDB might not be consistent on all routers. This inconsistency happens because the RID is one method to verify
whether an LSA is already present in the database. Therefore, new critical information from one of the routers is never
present in all the routers. In addition, because the Dijkstra calculation uses the RID, it is possible that an individual router
might not generate a loop-free shortest path topology. This scenario could have a disastrous affect on IP routing.
Router ID Is the Primary Interface

Whenever the rpd restarts on a Juniper Networks router, the selection of the routers primary interface takes place. This
selection states that the primary interface will be the smallest non-127/8 IP address configured on the loopback interface. If
no non-127/8 address is configured, the interface uses the first available IP address on the router.
Because the OSPF routing process uses the primary router interface as the RID, its selection can have a very important
consequence. If the router addressing changes, the OSPF RID might also change, and a duplicate RID situation might arise.
The hazards of this type of situation were outlined in the previous section.

Manual Router ID Selection
To avoid possible problems with the OSPF RID changing, you can set the router ID manually within the Junos configuration.
Within the [edit routing-options] configuration hierarchy, the router-id command assigns a 32-bit value to the
RID. By setting this value, the process of using the routers primary interface value is not used.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Loopback Is Often the Router ID

In a vast majority of the networks using OSPF, the routers have unique loopback IP addresses configured. As such, the
loopback address automatically becomes the router ID of the router, unless configured manually using the router-id
command.
Automatic Advertisement of the Router ID

As of Release 8.5, the Junos OS no longer automatically advertises the loopback (interface lo0.0) IP address, which
might also be your RID, into the network. However, there are several important points to keep in mind when configuring your
router.
If you do not configure interface lo0.0 within an OSPF area, the loopback IP address will not be advertised. Thus, the
loopback address will not be reachable.
When you configure interface lo0.0 within a specific OSPF area, the loopback IP address is only advertised in the
router LSA for that specific area. The ABR attached to Area 2 has its loopback configured within Area 0. It then advertises the
loopback in its Area 0 router LSA only. The address is still visible to Area 2, but it is encoded in a summary LSA as all the
other backbone routes are.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Authentication
»¿´·¿à±¬®¿·²ò½±³ò¶±
Authentication
The three different forms of authentication that the Junos OS supports are none, simple, and MD5. As of Junos Release 8.3,
IP Security (IPsec) was added.
Authentication Default
The default operation of the OSPF process is the none mode. Thus, no authentication key is configured on any interface.
Plain-Text Passwords
With simple authentication type configured, each OSPF packet includes a plain-text password. This password can be
captured easily through a packet analysis system. Therefore, although this password protects against an inadvertent
configuration, it does not provide any security.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Encrypted Checksum
To provide better security in an OSPF network, we recommend that you use an authentication type of MD5. MD5 includes an
encrypted checksum in all OSPF packets instead of a simple-text password. Each OSPF-speaking router uses the same MD5
algorithm to calculate the checksum value, so interoperability and a correct result can be virtually guaranteed.
Authentication Keys
The actual password to verify and authenticate packets is contained within the authentication command. You can configure
each individual interface with an authentication value.
Key ID Values
You configure each individual interface with a key value. All interfaces in the area might share the same key value, or each
interface might contain a separate value.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Multiple Key Values

When configuring multiple key values, you can also specify a start time for the router to begin using a new MD5 key. This
setting aids in the graceful transition from one password key to another. The example in the slide displays the format of the
start-time command. When the local routers time reaches the specified value, the router begins to transmit all OSPF
packets using the new key ID value and password. To begin using a new MD5 key ID immediately, you can use the keyword of
now in place of a specific time and date. The router automatically places the current system time in the configuration for you.
»¿´·¿à±¬®¿·²ò½±³ò¶±
View Authentication Information

The show ospf interface detail command displays the type of authentication used on the interface with the Auth
type output. Displaying this output occurs regardless of whether you use per-area or per-interface authentication in your
network.
The possible values displayed in the output are None, Password, and MD5. When MD5 authentication is in use, the router
also displays the current key ID value and the time at which that ID was first used. If start-time is not specified in the
configuration, the value of the Start time field in the show ospf interface detail command output is the UNIX
epoch (1970 Jan 1 00:00:00 UTC).

Authentication Mismatch
OSPF routers must agree on the authentication method to be neighbors. Use the traceoptions functionality if you
suspect there might be an authentication mismatch.
The log shows that the local router is ignoring an OSPF packet from 172.20.77.1 because of an authentication mismatch.
No authentication method is configured on the local router, so the type is none. The remote router has MD5 authentication
configured.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPFv3
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPFv3
OSPFv3 is defined in RFC 5340, with some additional features, such as grateful restart and authentication, defined in
separate documents (RFC 5781OSPFv3 Graceful Restart and RFC 4552 Authentication/Confidentiality for OSPFv3).
OSPFv3 maintains the fundamental mechanisms of OSPF, including LSA flooding scopes, areas, DR election, stub areas,
NSSAs, and so on. Though OSPFv3 is often associated with IPv6 addressing, it is also completely compatible with IP version
4 (IPv4) addressing schemes. However, some changes are necessary to account for the differences in IPv4 versus IP version
6 (IPv6) addressing. We address these differences on the following slides.
In terms of the Junos OS configuration, all that is required is to substitute ospf3 for ospf in the configuration.
[edit]
user@router# show protocols ospf?
Possible completions:
> ospf OSPF configuration
> ospf3 OSPFv3 configuration
»¿´·¿à±¬®¿·²ò½±³ò¶±
Differences Between OSPFv2 and OSPFv3: Part 1

Though much remains the same, several differences exist between OSPFv2 and OSPFv3:
Protocol processing per link, not per subnet: You need only a single adjacency per link even if multiple IPv6
subnets exist on the link. These adjacencies are formed using link-local addresses, which removes the
requirement of having matching subnet and subnet mask configurations for two routers to become adjacent.
Removal of addressing semantics: Addressing semantics were removed from OSPF headers, and no prefix
information is carried in the router LSAs or network LSAs. This change makes OSPFv3 somewhat protocol
independent. The router and network LSAs now express the topology in a protocol-independent fashion. To carry
the equivalent information that was carried in these LSAs with OSPFv2, a new LSA called the intra-area-prefix
LSA is introduced. The intra-area-prefix LSA carries the IPv6 addressing information.
Flooding scope is generalized: Flooding is now generalized and is coded into the LS type field. An LSA can be
either flooded on the local link, area, or throughout the AS. This flooding also assists in the handling of unknown
LSA types as the flood scope is encoded.
Support for multiple instances per link: This support allows multiple OSPF instances to run over a single link to
support separate routing domains or to support a single link belonging to multiple areas. Previously, this
functionality was achieved in OSPFv2 by tweaking authentication to hide OSPF packets from an OSPF router.
This functionality is now formalized by including an instance ID in the OSPF header.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Differences Between OSPFv2 and OSPFv3: Part 2

Further differences between OSPFv2 and OSPFv3:
Use of link-local addresses: OSPF packets are sent using the IPv6 link-local addressing. These link-local
addresses are also used as next-hop information during forwarding.
Authentication removed: Authentication uses the IPsec framework built into IPv6. As a result, it is not required
at the application layer and was removed.
LSA format changes: Summary LSAs are now referred to as inter-area-prefix LSAs, and ASBR summary LSAs are
now inter-area-router LSAs to account for differences in address size. The intra-area-prefix LSA is also included,
carrying prefix information internal to areas that were previously carried inside router and network LSAs.
Unknown LSA handling: The old way of discarding unknown LSA types is no longer supported because a mix of
capabilities in a network, especially on a single link, causes forwarding issues. OSPFv3 codes the proper
handling of an unknown LSA type in the LSA handing bit. The LSA is either treated as being of local scope only
or stored and forwarded as if it were understood.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Differences Between OSPFv2 and OSPFv3: Part 2 (contd.)
This list is a continuation of the further differences between OSPFv2 and OSPFv3:
The options field was expanded from 8 bits to 24 bits: The option field is included in OSPF hello packets,
database description packets, and certain LSAs (router LSAs, network LSAs, inter-area-router LSAs, and link
LSAs). Previously defined option bits are present, as well as added support for the V6-bit and R bits. The V6-bit
is used to indicate whether the route or link should be excluded from IPv6 routing calculations. The R bit is used
like the IS-IS overload bit and indicates whether the originator is an active router. If the R bit is clear (that is, 0)
in the OSPF options field, the advertising router can participate in OSPF without being used for transit traffic.
This would be a useful setting for hosts that are multihomed but never used to forward traffic between
interfaces.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPFv3 LSA Types

The link state (LS) type field is encoded in the LSA header and indicates the flooding behavior and the information contained
in the LS update. LSA types are now encoded with LSA properties and an LSA function code.
LSA properties include:
U bit: Used to indicate how a router that does not understand the LS function code should handle the LSA.
When the code is 0, the LSA should treat the LSA as if it has link-local scope only. When the code is 1, the router
should store and flood it as if it were understood.
S-bits and flooding scope: Used to indicate the flooding scope for the LSA:
S-bits and flooding scope
S2 S1 Flooding scope
0 0 Link-local scope.
0 1 Area scope.
1 0 AS scope.
1 1 Reserved.
Continued on the next page. »¿´·¿à±¬®¿·²ò½±³ò¶±

OSPFv3 LSA Types (contd.)
The function codes are very much like the OSPFv2 type codes. Some exceptions, however, do exist. Most notably, all
addressing semantics are removed from the router and network LSAs. The addresses that were advertised in the OSPFv2
versions of the LSAs are now carried in a new intra-area-prefix LSA.
Another addition is the presence of the link LSA. The link LSA is used to advertise to directly attached OSPF neighbors the
link-local IPv6 address assigned to the interface. As indicated by the LS type, the link LSA is not flooded beyond the physical
broadcast domain.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPFv2 and OSPFv3 Similarities

One similarity is the preservation of the 32-bit router ID. Like OSPF, in OSPFv3 every OSPF router has a single RID; it is a
32-bit number in dotted quad notation. If the RID is not explicitly configured under routing-options, the Junos OS uses
IPv4 addressing to derive a RID based upon the same rules as OSPFv2 (that is, it is likely the loopback address). However, it
is conceivable that IPv6 devices be deployed without any IPv4 addresses with which to derive the RID, and so we
recommend configuring the router ID explicitly.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPFv2 and OSPFv3 Feature Support Similarities

OSPFv3 is largely an adaptation of OSPFv2 and, as a result, features supported in OSPFv2 are also supported in OSPFv3.
Perhaps the only obviously missing feature is authentication. Authentication is removed from OSPFv3 because IPv6 has this
security feature built in (although it is off by default), and thus there is no need for both OSPFv3 and IPv6 to have the feature.
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Discussed:
OSPF LSAs;
How LSAs are flooded throughout the network;
The SPF algorithm;
OSPF link metrics;
OSPF authentication methods; and
The differences between OSPFv2 and OSPFv3.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Review Questions
1.
2.
3.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuring and Monitoring OSPF Lab

The slide lists the objectives for this lab.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Answers to Review Questions
1.
LSA Type 9 supports graceful restart.
2.
The metric or cost of a routers links can be automatically altered with the reference-bandwidth command.
3.
The different forms of OSPF authentication include none, simple, and MD5.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 3: OSPF Areas
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Will Discuss:
OSPF area types and operations;
How to configure various OSPF area types; and
How to summarize and restrict routes.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 32 OSPF Areas www.juniper.net
Review of OSPF Areas

»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net OSPF Areas Chapter 33
OSPF Scalability
With a link-state protocol, flooding link-state update packets and running the shortest-path-first (SPF) algorithm consumes
router resources. As the size of the network grows and more routers are added to the autonomous system (AS), this use of
resources becomes a bigger and bigger issue. This issue stems from the RFC requirement that all OSPF routers share an
identical link-state database (LSDB). Eventually, the routers spend so much time flooding and running the SPF algorithm that
they cannot route data packets. Clearly, this scenario is not optimal.
Shrinking the LSDB

The solution to this problem (and link-state protocol scalability in general) is to reduce the size of the LSDB. You can reduce
the size of the LSDB using multiple OSPF areas rather than a single area that encompasses the entire AS. Note that the type
of OSPF areas used is important when attempting to shrink the size of the LSDB. We discuss the various OSPF area types on
a subsequent slide.
In addition to adding new OSPF areas that restrict link-state advertisement (LSA) flooding, you can also perform route
summarization on the borders between OSPF areas. Route summarization has two key benefits: 1) It reduces the size of the
LSDB; and 2) it can hide some instabilities in one OSPF area from all other OSPF areas. For route summarization to be
effective, you must carefully plan the addressing within your OSPF network so that subnets can be more easily summarized.
Complete coverage of route summarization is beyond the scope of this course.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Areas
Using OSPF, you can segment an AS into smaller groups known as areas. Using areas achieves the OSPF hierarchy that can
facilitate growth and scalability. You can constrain LSA flooding by using multiple areas, which can effectively reduce the size
of the LSDB on an individual OSPF router. Each OSPF router maintains a separate and identical LSDB for each area to which
it is connected.
To ensure correct routing knowledge and connectivity, OSPF maintains a special area known as the backbone area. The
backbone area is designated as Area 0.0.0.0 (or simply Area 0). All other OSPF areas must connect themselves to the
backbone area. By default, all data traffic between OSPF areas transits the backbone. You can alter this default behavior
and eliminate the requirement of all interarea traffic transiting Area 0.0.0.0 by configuring a multiarea adjacency on the
same logical interface. The multiarea adjacency feature is documented in RFC 5185 and is discussed in the next chapter.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Area Types

This slide introduces some OSPF area types and illustrates the relationship between these areas, including the types of
routes exchanged between them. On the slide, all areas are connected directly to the backbone. In the rare situations where
a new area is introduced that cannot have direct physical access to the backbone, you can configure a virtual link. Virtual
links are covered in the next chapter.
OSPF classifies different types of routing information as follows:
Intra-area or internal routes: Routes that are generated from within an area, where the destination belongs to
the area;
Interarea or summary routes: Routes that originate from other areas; and
External routes: Routes that originate from other routing protocols, or different OSPF processes, and that are
injected into OSPF through redistribution.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Area Types (contd.)
Stub areas are areas through which, or into which, AS external advertisements are not flooded (LSA Type 4 and Type 5). You
might want to create stub areas when much of the topological database consists of AS external advertisements. Doing so
reduces the size of the topological databases and, therefore, the amount of memory required on the internal routers in the
stub area.
When you configure an area border router (ABR) for stub area operation, a default route is normally advertised in the place of
the external routes that are blocked from stub areas. The default route provides routers in the stub area with reachability to
external destinations. In the Junos operating system, ABRs require explicit configuration for default route generation.
Note that you cannot create a virtual link through a stub area, and a stub area cannot contain an AS boundary router.
A totally stubby area is a stub area that receives only the default route from the backbone. ABRs do not flood LSA Type 3,
Type 4, or Type 5 into totally stubby areas.
An OSPF stub area has no external routes in it, so you cannot redistribute routes from another protocol into a stub area. A
not-so-stubby area (NSSA) allows external routes to be flooded within the area. These routes are then leaked into other
areas. However, external routes from other areas still do not enter the NSSA. (ABR does not flood LSA Type 4 and Type 5 into
an attached NSSA.)
»¿´·¿à±¬®¿·²ò½±³ò¶±
Stub Area Operation

»¿´·¿à±¬®¿·²ò½±³ò¶±
Reduce LSDB Size

The operation of an OSPF stub area reduces the size of the LSDB within that area by eliminating AS external routing
information. When all of an areas routers agree to operate in stub mode, the ABR stops forwarding Type 5 external LSAs into
the area. The ABR also stops generating Type 4 summary LSAs, which are no longer needed because of the suppression of
Type 5 external LSAs.
ABR Provides Reachability

The routers within the stub area still might require IP reachability to the external routes they no longer have in their
databases. A 0.0.0.0/0 default route generated by the ABR in the area accomplishes this reachability. Within the Junos OS,
the advertisement of a default route does not occur automatically; this allows for better control of which ABR, if any, should
be used for outbound traffic flows.
No ASBRs in a Stub Area

Because the definition of a stub area does not allow the use of external LSA information within the area, no functional AS
boundary routers can exist within a stub area. If any ASBR configuration exists, the router generates one or more Type 5 LSAs
and places them into its local database. These external LSAs cannot be sent out any interfaces supporting stub operation,
however.

No Virtual Links in a Stub Area
For similar reasons, a stub area cannot support a virtual link because the area attached to the backbone through the stub
area might require external LSA information. Because the transit routers cannot forward the Type 5 LSAs, the far-end area
would not receive the correct information.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Stub Area Flooding Scopes

In the example on the slide, Area 1 is now configured as a stub area. This configuration causes the ABR of Area 1 to stop
forwarding the Type 5 LSAs from Area 0 and Area 3. Because the routers within Area 1 no longer have the external LSA
information, they also no longer require the knowledge of any ASBRs in the network. As such, the Area 1 ABR stops
generating Type 4 LSAs for reachability of the ASBRs in Area 0 and Area 3.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Further Reduces LSDB Size

The operation of an OSPF stub area with no summaries further reduces the size of the LSDB within that area by also omitting
Type 3 summary LSAs. This behavior has the effect of the routers within the area only having Type 1 router and Type 2
network LSAs in their databases. As noted previously, this type of area is known as a totally stubby area because a default
route is now needed to reach AS external and interarea prefixes.

The routers within a stub area with no summaries still might require IP reachability to interarea and external routes that are
no longer represented in their databases. A 0.0.0.0/0 default route generated by the ABR in the area accomplishes this
reachability. Within the Junos OS, this advertisement is a manual step for the network administrator that allows for better
control of which ABR, if any, should be used for traffic flowing to interarea or external destinations.
No ASBRs in a Stub Area

As before, no functional AS boundary routers can exist within a stub area, regardless of whether summaries are permitted.
No Virtual Links in a Stub Area

Like a stub area, a stub area with no summaries cannot support virtual links.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Flooding Scopes for Stub Area with No Summaries

The slide shows that Area 1 is still configured as a stub area as shown on a previous slide. In addition, Area 3 has now been
configured as a stub area with no summaries.
As discussed previously, the ABR of Area 3 has stopped forwarding the Type 5 LSAs from Area 0 and has also stopped
generating the Type 4 LSAs from Area 0. In addition, Area 3s ABR no longer generates Type 3 LSAs for the other OSPF areas.
This fact has left the LSDB for Area 3 quite small.
Another interesting phenomenon has occurred as well. Recall that one of the Area 3 routers previously acted as an ASBR.
Although the ASBR portion of that routers configuration did not change, its operation changed into a stub network. This
change causes the router to generate Type 5 LSAs and place them into its own database. However, because all interfaces
are now operating in stub mode, the router has no ability to forward them. As such, notice that the entire network has lost
knowledge of the Type 5 LSAs from Area 3.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Stub Area Configuration

»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuration on All Routers

For an OSPF stub area to function successfully, you must configure each router in that area to treat the area as a stub. This
configuration alters the E bit setting in the options field of the OSPF hello packet to notify all neighbors that the local router
does not support external LSAs. An OSPF router only forms an adjacency with another router when the E bit values match
hence, the requirement that all routers agree on whether the area is a stub area.
ABR Injects a Default Route

The ABR of the stub area can optionally inject a 0.0.0.0/0 default route into the stub area. Using the default-metric
command accomplishes this task, which causes the ABR to generate a Type 3 summary LSA advertising the 0.0.0.0/0 route
with the associated metric attached.
The need to manually assign the metric before the default route is generated provides additional control. The administrator
can control how, or if, traffic will leave the stub area by controlling which (if any) ABRs advertise a default route as well as the
metric for that route.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuration on the ABR Only

Because the ABR generates new Type 3 summary LSAs for injection into the areas it serves, you configure the
no-summaries option only on ABR routers by adding the no-summaries command to the stub areas stanza. Because
non-ABR routers in the area do not require the suppression of Type 3 LSAs, you do not have to perform this configuration on
those routers.

The ABR of an area configured as a stub with no summaries can optionally inject a 0.0.0.0/0 default route into the stub
area. Use the default-metric command to accomplish this task, as described on previous pages.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA Operation
»¿´·¿à±¬®¿·²ò½±³ò¶±
Altering the Stub Area Behavior

Much like a stub area, the operation of an OSPF NSSA assists the routers within that area by reducing the size of the LSDB.
The main difference between a stub area and an NSSA is that external routing information, in the form of a Type 7 LSA, is
allowed within the NSSA area. The ABR with the highest router ID converts the Type 7 LSAs into Type 5 LSAs and forwards
them toward the backbone as if they had originated from an ASBR in a non-stub area. This process keeps knowledge of the
NSSA contained within the area.

The routers within the NSSA might require IP reachability to the external routes from the backbone they no longer have in
their databases. A 0.0.0.0/0 default route generated by the ABR in the area can accomplish this reachability. Within the
Junos OS, this advertisement is a manual step for the network administrator, which allows for better control over which ABR
should be used for outbound traffic flows. For an NSSA, the default route is carried in a Type 7 LSA using the default-lsa
option by itself. Using both the default-lsa and no-summaries options together causes a Type 3 LSA to be used. A
NSSA no-summaries area then has an option to change this Type 3 back to a Type 7 again by using the the type-7 option.
The slide shows example of all three types of configurations.
No Virtual Links in an NSSA

In a similar fashion to a stub area, an NSSA cannot support a virtual link. Again, the area attached to the backbone through
the NSSA area might require external LSA information. Because the transit routers cannot forward the Type 5 LSAs, the
far-end area does not receive the correct information.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA Flooding Scopes

Area 3 now is configured as an NSSA. This configuration causes the ABR of Area 3 to stop forwarding the Type 5 LSAs from
Area 0. Because the routers within Area 3 cannot use the external LSA information, they also do not require the knowledge of
any ASBRs in the rest of the network. As such, the Area 3 ABR stops generating Type 4 LSAs from Area 0.
Recall that an ASBR is configured within Area 3. To allow that routing information to be propagated to the rest of the OSPF
domain, the ASBR generates a Type 7 LSA for these routes. Each of the routers in Area 3 now can forward these LSAs
because they each are configured as an NSSA router. When the information reaches the Area 3 ABR, it performs a Type 7
LSA to Type 5 LSA conversion and injects the Type 5 LSA into the backbone. All other OSPF routers in the domain use the
Type 5 LSA as normal and have no knowledge that the routes originated within an NSSA.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Disabling Export of LSAs into NSSAs Attached to ASBR ABRs

When an ASBR is also an ABR with an NSSA area attached to it, a Type 7 LSA is exported into the NSSA area by default. If the
ABR is attached to multiple NSSA areas, a separate Type 7 LSA is exported into each NSSA area by default.
Type 7 LSAs are not exported into an NSSA if only one NSSA and backbone area are connected to the ABR. To disable
exporting Type 7 LSAs into NSSAs, include the no-nssa-abr statement. This statement is needed on the ABR only.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Behaves Like Stub Area with No Summaries

The operation of an OSPF NSSA with no summaries assists the routers within that area by further reducing the size of the
LSDB. In addition to the ABR not forwarding Type 5 external LSAs, and not generating Type 4 summary LSAs, the ABR also
stops flooding Type 3 LSAs into the NSSA. This process has the effect of the routers within the area having only Type 1 router,
Type 2 network, and Type 7 (NSSA) LSAs in their databases.

The routers within the NSSA with no summaries might require IP reachability to routes they no longer have in their
databases. A 0.0.0.0/0 Type 3 LSA is generated by the ABRs to provide this reachability, when so configured. The
advertisement of a default route is a manual step for the network administrator, which allows for better control over which
ABR (if any) should be used for outbound traffic flows. A Type 7 LSA can be used for the advertisement of the default route
for compatibility with earlier Junos OS releases.
No Virtual Links in an NSSA with No Summaries

Like a regular NSSA, an NSSA with no summaries cannot support a virtual link.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA with No Summaries Flooding Scopes

Area 3 is now configured as an NSSA with no summaries. In addition to the functionality described on a previous slide, the
ABR of Area 3 stops generating Type 3 summary LSAs from Area 0.
»¿´·¿à±¬®¿·²ò½±³ò¶±
NSSA Configuration
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuration on All Routers

To operate an OSPF NSSA successfully, you must configure each router to participate. This configuration alters the N/P bit
setting in the Options field of the OSPF hello packet to notify all neighbors that the local router does not support Type 5
external LSAs, but does support Type 7 external LSAs. An OSPF router only forms an adjacency with another router when the
N/P bit values matchhence, the requirement that all routers perform the configuration.

The ABR of the NSSA can optionally inject a 0.0.0.0/0 default route into the area. Within the default-lsa configuration
hierarchy, the default-metric command accomplishes this. The command causes the ABR to generate a Type 3
summary LSA to advertise the 0.0.0.0/0 default route into the area with the configured metric.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuration Only on the ABR

Because it is the job of the ABR to generate new Type 3 summary LSAs into the area, configuration takes place only on this
router to create a no-summaries area. To configure an ABR to support a no-summaries configuration, apply the
no-summaries command to the NSSA setting within the ABR. Because all other routers in the area do not require the
suppression of a Type 3 LSA, you do not need configuration on those routers.

The ABR of the NSSA no-summaries area can inject a 0.0.0.0/0 default route into the NSSA when the default-metric
command is issued. This causes the ABR to advertise a default route with the configured metric.
Type 3 LSA Generated by Default

When the NSSA is configured with the no-summaries command, the 0.0.0.0/0 default route is advertised using a Type 3
summary LSA. This behavior reflects a change in the default operation of the Junos OS starting with Release 5.0. To
interoperate with older Junos OS versions (earlier than 5.0), a Type 7 LSA might be required. The type-7 command within
the default-lsa hierarchy accomplishes this task, which causes the ABR to generate a Type 7 LSA advertising the
0.0.0.0/0 route with the associated metric.
This Type 7 LSA is advertised using a Type 1 metric, which means that all routers calculate the cost to the ABR and add to it
the advertised default metric. You can alter this behavior with the metric-type command within the default-lsa
hierarchy. The Type 7 LSA is then advertised using a Type 2 metric, which means that each area router uses only the
advertised metric of the route.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Route Summarization
»¿´·¿à±¬®¿·²ò½±³ò¶±
Local Area Routes Forwarded to Area 0.0.0.0

The default operation of an ABR is to generate a Type 3 summary LSA into the backbone area for each Type 1 and Type 2 LSA in
the LSDB. The configuration of a stub area or stub area with no summaries does not affect this operation because a stub
configuration only alters information that enters the nonbackbone area.
Route Summarization
To reduce the size of the LSDB in Area 0.0.0.0 (and other remote OSPF areas), you can configure the ABR not to perform its
default one-for-one mapping function. This is accomplished using an address range statement on the ABR with the
area-range command. All Type 1 and Type 2 LSAs that fall within that address range will no longer be advertised
individually into the backbone. Instead, a single Type 3 summary LSA is advertised. The metric associated with this summary
route will be equal to the highest metric associated with the individual contributing routes.
Because only the ABR performs this mapping function, you configure the area-range command on ABR routers only.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Type 7 External Routes Forwarded to Area 0.0.0.0

The default operation of the ABR for Type 7 LSA routes local to a nonbackbone area is to generate a single Type 5 external
LSA for each Type 7 LSA in the LSDB. The configuration of an NSSA or an NSSA area with no summaries does not affect this
operation because an NSSA configuration only alters information that enters the nonbackbone area.
Route Summarization
To reduce the size of the LSDB in Area 0.0.0.0 (and other remote OSPF areas), you can configure the ABR not to perform its
default one-for-one mapping function. You can configure an address range on the ABR by using the area-range
command within the NSSA configuration hierarchy. All Type 7 LSAs that fall within that address range are not advertised
individually into the backbone. Instead, a single Type 5 external LSA is advertised.
Because only the ABR performs this mapping function, only the ABR is configured with the area-range command.
Note that the area-range command referenced here is specific to the NSSA configuration hierarchy and only affects Type
7 LSA routes. The area-range command discussed in the previous slide was within the area hierarchy itself and affected
Type 1 and Type 2 LSA routes. The configuration can have these two commands in place at the same time, and they will
summarize different aspects of the local area routing domain.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Suppressing Routes
The default action of the area-range command causes the generation of a single Type 3 summary LSA into the backbone
for all prefixes that fall within the defined range. You can configure the ABR with the restrict keyword to block one or
more prefixes from advertisement into the OSPF backbone. Such a configuration prevents routing information from each
Type 1 and Type 2 LSA that falls within the address range from being advertised to the backbone, which in turn can block
connectivity to those prefixes for routers in other areas.
Use the restrict function when you want to prevent interarea routing, or when you want a default route to be used
instead of the more preferred summary information that would otherwise be generated.
Because only the ABR is responsible for this mapping function, you configure only ABR routers with the area-range
restrict command.
»¿´·¿à±¬®¿·²ò½±³ò¶±
The restrict Command Suppresses Routes

The default action of the area-range command is to send a single Type 5 external LSA into the backbone. This
functionality already alters the default OSPF protocol operation. You then can configure the ABR additionally with the
keyword restrict. This keyword prevents routing information from each Type 7 LSA that falls within the address range
from being advertised to the backbone at all.
Because only the ABR is responsible for this mapping function, you must configure only the ABR with the area-range
restrict command.
»¿´·¿à±¬®¿·²ò½±³ò¶±
i
Case Study: Route SummarizationPart 1

This slide introduces the simple topology for this case study. Current highlights include the following:
Router R3 is an ABR between NSSA Area 3 and the Area 0 backbone. Its networks are 10.0.4.0/30, 10.0.4.4/
30, and 10.0.4.8/30. These can be summarized into 10.0.4.0/28. Furthermore, the 3.0.0.8/30 route exists in
this area which you prevent from flooding throughout the OSPF domain.
Router R5 is an ABR between stub Area 4 and the Area 0 backbone. Its networks are 10.0.8.0/30, 10.0.8.4/
30, and 10.0.8.8/30. These can be summarized into 10.0.8.0/28.
»¿´·¿à±¬®¿·²ò½±³ò¶±

First off, lets take a look at what the R4 router currently has in its routing table. From the output, you can see the networks,
in Area 3 and Area 4, that we intend to summarize.
»¿´·¿à±¬®¿·²ò½±³ò¶±

The area-range option is configured as shown on the slide on both R3 and R5 to summarize the routes from each routers
respective area.
»¿´·¿à±¬®¿·²ò½±³ò¶±

This slide shows the results of our recent changes. Previously, six routes were present for the Area 3 and Area 4 networks.
Now, there are only the two summarized routes.
»¿´·¿à±¬®¿·²ò½±³ò¶±

Recall that we also wanted to suppress the 3.0.0.8/30 route from flooding outside Area 3. This slide shows how to use the
restrict modifier of the area-range command to accomplish our objective. As shown on the slide, after committing the
configuration on R3, the 3.0.0.8/30 route is no longer present in R4s routing table.
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Discussed:
OSPF area types and operations;
How to configure various OSPF area types; and
How to summarize and restrict routes.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Review Questions
1.
2.
3.
4.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuring and Monitoring OSPF Areas and Route Summarization Lab

The slide provides the objectives for this lab.
»¿´·¿à±¬®¿·²ò½±³ò¶±
1.
The ABR does not forward Type 4 and Type 5 LSAs into a stub area or NSSA. Type 3 LSAs are also not forwarded in an OSPF NSSA
with no summaries.
2.
You must configure all routers that are in the stub area or NSSA.
3.
The ABR of the stub area can optionally inject a 0.0.0.0/0 default route into the stub area or NSSA.
4.
The backbone area is directly affected by the area-range command. However, any area that is able to receive summary LSAs also
benefits from this command.
»¿´·¿à±¬®¿·²ò½±³ò¶±
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 4: OSPF Case Studies and Solutions
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Will Discuss:
Three interior gateway protocol (IGP) transition strategies;
Transitioning between IGPs with minimal or no network disruption while maintaining network stability;
Configuring OSPF multiarea adjacencies;
OSPF external reachability; and
Configuring OSPF virtual links.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Chapter 42 OSPF Case Studies and Solutions www.juniper.net
IGP Transition Overview

www.juniper.net OSPF Case Studies and Solutions Chapter 43

IGP Transition Overview

There are many reasons why you might decide to transition your network from using one IGP to using a different IGP. When you
find it necessary to move from one IGP to another, you have several goals. Your primary goal is to end with a well-designed
network. When you design a network well, the IGP design is an integral part of the network design. So, moving between IGPs
often requires you to make some network design changes to create a well-designed network by the end of the transition
process. Your secondary goal is to maintain network stability while transitioning IGPs. Your tertiary goal is to minimize downtime
during the transition. This chapter does not directly teach good IGP design; rather, it focuses on how to maintain network
stability and minimize network downtime during the transition.
Generic Transition Strategies

While you might decide to transition your network from using one IGP to using a different IGP for many reasons, a common
reason is to move from proprietary protocols (such as Extended IGRP [EIGRP)]) to protocols based on open standards (such as
OSPF). In this chapter, we discuss generic transition strategies. The examples in the chapter show how to transition a network of
routers running the Junos operating system from RIP to OSPF. However, the transition strategies are generic, and you can use
them for any beginning and ending IGPs, and you can apply the concepts to routers running any operating system.
Common Elements
The IGP transition strategies contain a few common elements. Every IGP transition strategy requires that you know which IGP
provides the active routing information for the network at every point. You control this information in the Junos OS using
»¿´·¿à±¬®¿·²ò½±³ò¶±
route preferences. Additionally, most transition strategies require
two IGPs so that you can ensure that all routers
require you to export appropriate routing information between the
routers have access to full routing information.

Preferred Routing Information Sources

The router uses route preference to differentiate routes received from various routing protocols or routing information sources.
Route preference is equivalent to administrative distance on other vendors equipment. To ensure the routers make consistent
routing decisions, you should set route preferences consistently on every router in the network (including other vendors
routers).
Primary Tiebreaker
The Junos OS uses route preference as the primary criterion for selecting the active route. Preference values cause routes
from certain information sources to be ranked more preferably than the same route received from another information
source. The table on the slide shows the default preference values for a selected set of routing information sources.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Lower Is Better
Routing preference values are a 32-bit number that is 0 or higher. The router prefers lower preference values over higher
preference values. This command output demonstrates that a direct route with a preference of 0 is preferred over an OSPF
internal route with a preference of 10:
user@router> show route 10.251.254.130/31 exact
inet.0: 18 destinations, 19 routes (17 active, 0 holddown, 1 hidden)

+ = Active Route, - = Last Active, * = Both
10.251.254.130/31 *[Direct/0] 1d 07:53:39

> via ge-4/0/0.0
[OSPF/10] 1d 07:53:32, metric 65
> via ge-4/0/0.0
»¿´·¿à±¬®¿·²ò½±³ò¶±
Avoiding Exporting Problems

You can cause problems when you indiscriminately export routes from one IGP to another. In particular, you can cause
routing loops or route oscillation when you configure unconditional bidirectional exporting.
On the slide, a network administrator is transitioning from one IGP (RIP) to another IGP (OSPF). In an effort to provide
redundancy during the transition, the network administrator configures two routers on the border between the old and new
IGPs and configures both routers to export all RIP routes to OSPF and export all OSPF routes to RIP.
The slide shows the way the routers react when they receive a route through OSPF for the prefix 10.14.15.0/24. The OSPF
route is an external Type 1 route with a metric of 100. When R1 and R2 receive the route, they install it in the routing table as
the active route, export the route to RIP, and send a RIP advertisement. However, R1 accomplishes this process
microseconds before R2. So, R2 receives the RIP route and installs it in the routing table. Because the routers in this
network are configured to prefer RIP routes over OSPF external routes, R2 prefers the route it received from R1 through RIP.
When R2 receives the route through RIP from R1, it installs it in the routing table as the active route, exports the route to
OSPF (as an external Type 1 route with a metric of 1), and sends an OSPF link-state advertisement (LSA). When R1 receives
the OSPF LSA, it examines the metrics and determines that the OSPF route through R2 is the best path to 10.14.15.0/24. It
therefore installs that route as the active route in the routing table. It continues exporting this route to RIP, as it is configured
to do. As you can see, this configuration has caused a routing loop to form!
To avoid problems like this, you must configure bidirectional exporting very carefully. In particular, the safest way to configure
bidirectional exporting is to configure very explicit export filters that only allow expected routes to be exported between each
protocol. As you continue the transition, you must continually update these filters.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Avoiding Exporting Problems (contd.)
In the example on the slide, the routing loop (and routing information loop) would continue even if the router that originally
advertised the 10.14.15.0/24 prefix in OSPF ceased making the announcement. The only way you can end the routing loop
is to break the exporting loop. Configuring filters to only allow expected routes to be exported between each protocol would
end the routing information loop.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Overlay Transition
In the overlay transition, you configure all routers in the network to run the new IGP while they are still running the old IGP.
Once you verify the proper operation of the new IGP, you configure all routers in the network to stop running the old IGP. This
transition strategy is appropriate when all routers have the necessary resources (in particular, CPU and memory) to run both
protocols simultaneously. Additionally, you must accomplish any network redesign necessary to accommodate the new IGP
as part of the transition.
Route Redistribution
If all routers cannot run both protocols simultaneously or if you must make some topology changes as part of the IGP
change, you can gradually migrate the network one portion at a time. For example, if you are migrating to OSPF, you might
migrate one future OSPF area at a time. As you progress from one portion of the network to another, you must configure
routers on the border of the two IGPs to conduct mutual route redistribution, exporting routes between the two IGPs.
Integrated
If you must significantly redesign your existing topology to make it a well-designed network with the new IGP, the integrated
strategy might be the best approach. In this strategy, you create a new network core running the new IGP, connect it to the
old network core, and export routes between the new and old IGPs. You then gradually migrate connections from the old core
to the new core.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Transition Case Study

»¿´·¿à±¬®¿·²ò½±³ò¶±
Sample Topology
This slide shows the topology this chapter uses as an overlay example. We start off with a RIP network and then transition it
to an OSPF network.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Step 1: Configuring Route Preferences

You begin the overlay transition by configuring the router to assign the existing IGP a better (in other words, numerically lower)
route preference than the new IGP. This configuration ensures that the router continues to use the existing IGP for routing
information while you configure the new IGP.
Step 2: Configuring the New IGP

You continue the overlay transition by configuring the new IGP on all routers. You should configure it with the target end state (or
at least as close to the target end state as possible).
Step 3: Verifying Routing Information

The next step in the overlay transition process is for you to verify that all routers are receiving full routing information through the
new IGP. At the same time, you should verify that the router is making the routing decisions you expect and want it to make.
Step 4: Deleting the Old IGP

The final step is for you to deactivate the old IGP on all routers, verify the proper operation of the new IGP, and delete the old IGP
configuration. You should proceed from one end of the network to the other to ensure that any untransitioned routers are not in
the path between two already-transitioned routers.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Overlay Transition Example: Step 1

This slide and the next few slides show an example of how you can transition the sample network from RIP to OSPF.
The first step in the overlay transition is for you to configure the router to assign a better route preference to the existing IGP
than the new IGP. By configuring the old IGP to have a better route preference than the new IGP, you avoid extra cleanup and
verification steps at the end of the transition. If you instead configure the routers to modify the new IGPs route preferences to
be worse than the old IGP, you must remove the configuration that modified the new IGPs route preference at the end of the
transition process. Note that this removal might cause the router to make different route selection decisions in some cases.
Therefore, you would really need to verify each routers configuration and routing decisions after making this change.
In general, you want to configure the new routing protocol as it will exist at the end of the transition and make any temporary
changes necessary for the transition to the existing IGPs configuration. For these reasons, it is best to begin by configuring all
routers to assign the existing IGP a better route preference than the new IGP.
Recall from the route preferences table that OSPF internal routes have a default preference of 10, so you must choose a
preference for RIP routes that is numerically lower than 10. Also note that static routes have a default preference value of 5.
Therefore, you want to choose a preference for RIP routes that is numerically higher than 5. In this case, you choose 7 and
configure all routers using the command shown on the slide.
»¿´·¿à±¬®¿·²ò½±³ò¶±

The next step is for you to configure OSPF on all the routers. Because you configured RIP routes to have a lower preference,
the routers will continue using the RIP routes. Therefore, configuring OSPF does not change the routers routing decisions.
»¿´·¿à±¬®¿·²ò½±³ò¶±

Now that you have configured both routing protocols to run side by side, you should confirm that you are receiving the same
routing information through both protocols. Note that the previous slide showed that you configured OSPF summary routes
for the OSPF areas. Because of this configuration, you notice that the router is receiving summary routes through OSPF that
it is not receiving through RIP (on the slide, R2 is summarizing 10.14.16.0/24 from Area 3). Likewise, the router is receiving
more specific routes through RIP that it is not receiving through OSPF (on the slide, 10.14.16.0/27 and 10.14.16.64/27).
Because each area border router (ABR) has full routing information for the area, you should ensure that each ABR is
receiving the same routing information through both RIP and OSPF for the routes within each OSPF area.
»¿´·¿à±¬®¿·²ò½±³ò¶±

Once you verify that you are receiving the same routing information through both the old and new IGPs, you are ready to start
using the new IGP. To do this, gradually deactivate the old IGP throughout your network. On a router running the Junos OS, you
should follow the procedure on the slide. First, deactivate the protocol (allowing it to be quickly reactivated, should the need
arise). Then, commit the configuration. If you are accessing the router in-band, you should use the commit confirmed
command. Anytime you make major routing protocol changes using Telnet, it is always advisable to use commit confirmed
to ensure that the router returns to a working state should a problem arise. After you confirm the router is still reachable and has
full routing information, run the commit command again to confirm the configuration changes.
After you are confident that you do not need to reactivate the old IGP, delete the old IGPs configuration.
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Multi-Area Adjacencies

»¿´·¿à±¬®¿·²ò½±³ò¶±
Multiarea Adjacencies
By default, a single interface can belong to only one OSPF area. However, in some situations, you might want to configure an
interface to belong to more than one area. Doing so allows the corresponding link to be considered an intra-area link in
multiple areas and to be preferred over other higher-cost intra-area paths.
Beginning with Junos Release 9.2, you can configure a logical interface to belong to more than one OSPF area. As defined in
RFC 5185, OSPF Multi-Area Adjacency, the area border routers establish multiple adjacencies belonging to different areas
over the same logical interface. Each multiarea adjacency is announced as a point-to-point unnumbered link in the
configured area by the routers connected to the link.
For a given logical interface, it is considered as primary for one single area. To configure that same logical interface in
additional areas, you must use the secondary option. In the slide, you can see that interface ge-1/0/0.0 has been
configured in two areas, Area 0 and Area 1. Because the Area 1 interface has the secondary option set, the Area 0
occurrence is considered the primary.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Case Study Topology

The slide displays the case study topology.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Link Failure
In normal operation, if a link failure occurred between R1 and R3, traffic from R1 to R3 would flow from R4 to R2 and then to
R3. This creates three hops to reach a router that was previously one hop away.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Link Failure with Multiarea Adjacency

With multiarea adjacency configured, a hop to reach R3 is eliminated.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Adjacency Verification
Verify adjacencies with the show ospf neighbor command.
Normal Trace
For the case study, R3 is one hop away from R1.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Disable the Interface

To test normal operations, disable the interface between R1 and R3.
Trace Under Link Failure

The trace from R1 to R3 now takes a three-hop path.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Multi-Area Adjacency Configuration

When configuring multi-area adjacencies, keep in mind that you are assigning a single interface to at least two distinct
areas: one as the primary, and the others as secondary using the secondary option. As stated previously, a given logical
interface can be considered as primary for only one area. For any other areas in which you configure that interface, it must
be set as a secondary interface.
Point-to-Point Interface
The output shows that the ge-1/1/0.0 interface now appears in two distinct OSPF areas, Area 0 and Area 100. However,
note the secondary link in Area 100 shows up as a point-to-point interface.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Adjacency Is Formed
Two adjacencies are now formed over ge-1/1/0.0 for Area 0 and Area 100.
Trace with Multi-Area

With the multi-area adjacency feature configured, the trace now requires only two hops, compared with the default case of
three hops.
»¿´·¿à±¬®¿·²ò½±³ò¶±
External Reachability
»¿´·¿à±¬®¿·²ò½±³ò¶±
OSPF Default Export Policy

Recall that any policy applied to OSPF affects only external routes that are either Type 5 or Type 7 LSAs. Because OSPF does
not inject any external routes by default, the default export policy is to reject all routes. In other words, no external routes are
sent without a routing policy applied.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Route Redistribution
For route distribution to occur, an export policy must be written and applied. Because external routes in OSPF have an
interarea flooding scope, the policies are applied globally. This feature allows external routes to be sent into all areas that
allow it. When an external route is brought into OSPF, it appears as an external Type 5 LSA of Type 2. If an external LSA Type
1 must be configured, you can modify it with a policy.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Mutual Redistribution
Special care must be taken when redistribution is configured in a network. When multiple redistribution points are present,
sub-optimal routing and loops could occur. Generally, if the source route has a lower preference than the protocol into which
it is being redistributed, no issues occur. However, when the source route has a higher preference, issues can occur. Several
methods exist to resolve these issues, but the easiest method usually involves modifying route preference values.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Case Study Topology

The slide displays the case study topology that will be used in subsequent slides. R1, R2, and C1 are all running RIP.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Case Study Background

The slide describes the goal of the case study. The goal is to advertise a single RIP route into OSPF as well as send a default
route to RIP.

Create a Policy for the RIP Route

The first step is to create a policy and apply the policy to OSPF. In this case, two match conditions are used, creating a logical
AND. This policy will be applied to both R1 and R2 under the [edit protocols ospf] hierarchy by performing a set
protocols ospf export redistribute-rip command.
Verify Policy Operation

Verify that the policy is working by examining the database and finding the Type 7 associated with the RIP route.
»¿´·¿à±¬®¿·²ò½±³ò¶±
ABR Translation
Because the route was originated from the not-so-stubby area (NSSA), the ABR must convert the Type 7 LSA to a Type 5 for
interarea advertisement.
Forwarding Address
When the ABR translates the Type 7 into a Type 5, it places the address of the autonomous system boundary router (ASBR)
into the forwarding address. This behavior provides for optimal routing because only one ABR translates the Type 7 LSAs to
Type 5 LSAs in the presence of multiple ABRs.
ASBR Summary
The ABR also creates a Type 4 LSA to represent the ASBR to other areas.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Redistribution of Default Route

The next step is to redistribute the default route from OSPF into RIP using an export policy under RIP. By default, RIP has a
lower preference than OSPF external routes.
Because RIP has a better preference, the default route for RIP is preferred. In the sample network, this preference creates a
loop, because the OSPF routers point to the RIP router as their gateway, and the RIP router points to the OSPF ASBRs. To fix
the loop, modify the OSPF external route preference to a lower value than the RIP route.
»¿´·¿à±¬®¿·²ò½±³ò¶±
The Result
The result of the preference change is now a default that points properly to the ABRs in the NSSA.
»¿´·¿à±¬®¿·²ò½±³ò¶±
SPF Review
After a router receives a new LSA and places it into the link-state database (LSDB), the router runs an algorithm known as
the Dijkstra algorithm (also called the shortest-path-first [SPF] algorithm). This computation uses the database as a data
source and results in a loop-free network topology using the best metric from the local router to all nodes in the network.
During the course of this calculation, the algorithm uses three databasesthe LSDB, the candidate database, and the tree
database. As we have explored, the LSDB is the total compilation of routing knowledge in the network. Conceptually, it
consists of multiple tuples in the form of (router ID, neighbor ID, cost), which describe each link in the network.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Import Policy
An import policy can be applied between the tree database and the routing table. This allows filtering of routes from the
LSDB to the routing table but it only applies to external routes, as in the case for OSPF export policy. Note that the database
stays consistent and the import policy does not block any normal LSA flooding.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Flooding Protection
Some OSPF implementations encounter problems when large numbers of external routes are injected into the LSDB. The
Junos OS does not behave in this manner, however, and a large number of routes are handled without a problem. Although
this protocol stability is a nice feature, a configuration mistake could make a portion of your network unusable as only
routers capable of handling such large numbers would be operating effectively.
To help you when a configuration mistake occurs, the Junos OS allows a limit to be placed on the number of external routes
exported into OSPF. The prefix-export-limit command informs the router how many routes to accept using a routing
policy configuration. The command accepts a 32-bit value, which provides a range of routes from 1 to 4,294,967,295. Once
the route limit is reached, the router transitions into an overload state where the local links are set to a metric of 65,535 in
the router LSA. Additionally, all Type 5 LSAs from the router are purged from the database and the network in general. The
local router remains in this state until the number of external routes returns to a level below the configured limit. This
situation requires the administrator to manually change the existing configuration; either the number of advertised routes
must be reduced or the routing policy must be changed.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Modify Policy
To see prefix limits in action, a policy is modified to send all RIP routes into OSPF.
RIP Redistribution
This policy causes all RIP routes to be sent into OSPF.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Prefix Limit
To stop the large amount of LSAs that could enter the router, a prefix-limit of six is configured.
The Result
The result is that no RIP routes are distributed. This prefix-limit setting ensures that a configuration error does not affect your
network.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Virtual Links
»¿´·¿à±¬®¿·²ò½±³ò¶±
Acquisitions and Mergers

Companies are acquired or merged with other companies every day. These mergers present many interesting challenges,
including how to combine the IP networks into one network. For example, imagine two companies running OSPF that must
merge networks. For OSPF to work correctly, each company must connect their respective Area 0s together to form a single
contiguous backbone. At first glance, you might think the easiest solution would be to create new physical connections
between the routers in each company. However, this is often easier said than done. In addition, time can be a deciding
factor. For these cases, a temporary solution such as a virtual link can be deployed.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Case Study
In this case study, Alpha Corp. has acquired Bravo Corp. Both networks are running multiarea OSPF and the integration team
must get both networks communicating with each other.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Integration Case Study

During the acquisition phase, an integration team is formed to look at all facets of combining the two corporations, including
their OSPF networks. The determination is that connecting both Area 0 networks together with physical connections is not a
viable short term option. An alternative solution must be used.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Initial Physical Connection

The first step is to establish some physical connectivity between the two corporations. In this case, the integration team
chose to connect Alpha Corps A6 router and Bravo Corps B4 router. For now, the new interface will be configured in Area 10
on the A6 and B4 routers.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Connectivity Issues
As soon as the physical connection is created, limited connectivity is achieved. For example, the B4 router can now reach the
A1 router in Alpha Corps Area 0. However, Alpha Corps Area 0 routers cannot reach Bravo Corps Area 0 routers. The cause
of this limited connectivity is the lack of a contiguous Area 0 backbone.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Virtual Link
One solution to the connectivity problem is to create a virtual tunnel between the two backbone areas of the corporations.
This feature, known as a virtual link, provides a logical connection between areas. Essentially, OSPF packets are tunneled
through a transit area to establish an OSPF adjacency and logically connect the two areas together. This establishes full
connectivity between the two corporations.
Remember that a virtual link is a control plane feature only. SPF will still calculate the shortest physical path between two
points, which might not be the same path as the virtual tunnel. This calculation could create some confusion when
troubleshooting, which is one of the primary reasons virtual tunnels are not considered long term solutions.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Virtual Link Established

In this case, a virtual link is established between ABRs in each corporation. These ABRs must be attached to Area 0. In the
slide, A4 and B2 were chosen as the ABRs on which to establish the virtual link.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Virtual Link Configuration

The configuration of a virtual link takes place within the Area 0.0.0.0 portion of the OSPF hierarchy. The virtual-link
command itself requires both a transit area and a neighbor ID to be configured. The transit area is the OSPF area through
which you configure the virtual link. The neighbor ID is the 32-bit router ID (RID) of the router on the far end of the virtual link.
Once each side completes this configuration, each router begins to send unicast OSPF traffic towards the far-end router to
complete the link setup and form an adjacency.
Virtual Link as an Interface

Once the two ends of the link can communicate, the virtual link becomes an operational OSPF interface. It appears in show
commands and within the OSPF LSDB. It is always noted in a format of vl-neighbor-id, where vl denotes it as a virtual
link, and the neighbor-id is the RID of the far-end router.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Contiguous Area 0
Once the neighbor is established over the virtual link, connectivity is restored, all LSAs are processed, and routes to each
company are installed into the routing table. As shown in the slide, router B1 can now successfully ping router A1.
»¿´·¿à±¬®¿·²ò½±³ò¶±
We Discussed:
Three IGP transition strategies;
Transitioning between IGPs with minimal or no network disruption while maintaining network stability;
Configuring OSPF multiarea adjacencies;
OSPF external reachability; and
Configuring OSPF virtual links.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Review Questions
1.
2.
3.
4.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Configuring and Monitoring Routing Policy and Advanced OSPF Options Lab
The slide provides the objectives for this lab.
»¿´·¿à±¬®¿·²ò½±³ò¶±
1.
You risk double-exporting routes, which can lead to routing loops.
2.
Although technically you do not need a backbone area, functionally you need one because of the loop prevention mechanisms in OSPF.
3.
Virtual links would be deployed if two companies were merging their networks together and physical link connectivity was not an
option. This could be because of cost or time constraints.
4.
If the source route has a lower preference, there usually are no issues. If a source route has a higher preference, suboptimal routing or
loops can occur.
»¿´·¿à±¬®¿·²ò½±³ò¶±
Acronym List
ABR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . area border router
AF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . assured forwarding
AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . autonomous system
ASBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . autonomous system boundary router
ASM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . any-source multicast
BE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . best effort
BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Border Gateway Protocol
BGP4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Border Gateway Protocol version 4
CBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .class-of-service-based forwarding
CBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . connection-based forwarding
CIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . committed information rate
CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .command-line interface
CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .class of service
C-RP-adv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .candidate RP advertisement
CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . class selector
DR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .designated router
DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DiffServ code point
DVMRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Distance Vector Multicast Routing Protocol
EGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . exterior gateway protocol
GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .graphical user interface
HDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .High-Level Data Link Control
IANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Internet Assigned Numbers Authority
IBGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . internal BGP
IGMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Group Management Protocol
IGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . interior gateway protocol
IPsec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IP Security
IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IP version 4
ISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet service provider
JNCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Juniper Networks Certification Program
LSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . link-state advertisement
LSDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . link-state database
MAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .media access control
MDRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . modified deficit round-robin
MOSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Multicast Open Shortest Path First
NC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . network control
NLRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . network layer reachability information
NSSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . not-so-stubby area
OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Shortest Path First
PID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .process ID
PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Independent Multicast
PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-Point Protocol
QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . quality of service
RID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . router ID
RP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rendezvous point
rpd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . routing protocol daemon
RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . reverse path forwarding
RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . reverse-path multicasting
RR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .route reflector
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Network Management Protocol
SPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .shortest-path-first
SPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . shortest path tree
SSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .source-specific multicast
ToS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . type of service
TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . time-to-live
»¿´·¿à±¬®¿·²ò½±³ò¶±
www.juniper.net Acronym List ACR1
»¿´·¿à±¬®¿·²ò½±³ò¶±
ACR2 Acronym List www.juniper.net

AJER-12.a Student Guide Volume 1

Uploaded by

Copyright:

Available Formats

AJER-12.a Student Guide Volume 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AJER-12.a Student Guide Volume 1

Uploaded by

Copyright:

Available Formats

What are the main routing protocols discussed in the document?

What are the main routing protocols discussed in the document?

What are some of the acronyms used related to routing?

What are some of the acronyms used related to routing?

»¿´·¿à±¬®¿·²ò½±³ò¶±

Worldwide Education Services

1133 Innovation Way

Course Number: EDU-JUN-AJER

Advanced Junos Enterprise Routing Student Guide, Revision 12.a

Chapter 1: Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Chapter 2: OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Chapter 3: OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Chapter 4: OSPF Case Studies and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Acronym List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ACR-1

www.juniper.net Course Overview  v

CLI and GUI Text

Style Description Usage Example

Courier New Console text:

Input Text Versus Output Text

Style Description Usage Example

Normal CLI No distinguishing variant. Physical interface:fxp0,

Defined and Undefined Syntax Variables

Style Description Usage Example

CLI Variable Text where variable value is already policy my-peers

Education Services Offerings

Chapter 1: Course Introduction

General Course Administration

Training and Study Materials

Juniper Networks Education Services Curriculum

Juniper Networks Certification Program

Juniper Networks Certification Program Overview

Preparing and Studying

Neighbors Use Hello Packets

LSAs Are Flooded

The Link-State Database

Single Area Configuration Example

Multi-Area Configuration Example

Multiple LSAs in a Single Update

Link-State Update Format

LSAs Not Supported

www.juniper.net OSPF  Chapter 219

Link ID and Link Data Fields

Router LSA Example

Add Type 1 LSAs to an OSPF Network

Network LSA Example

Add Type 2 LSAs to an OSPF Network

Summary LSA Example

Chapter 228  OSPF www.juniper.net

Add Type 3 LSAs to an OSPF Network

ASBR Summary LSA

ASBR Summary LSA Example

Add Type 4 LSAs to an OSPF Network

AS External LSA Example

Add Type 5 LSAs to an OSPF Network

NSSA External LSA Origination

NSSA External LSA Example

Add Type 7 LSAs to an OSPF Network

Opaque LSA Format

Chapter 240  OSPF www.juniper.net

LSA Flooding Scopes

www.juniper.net Course Overview v

www.juniper.net OSPF Chapter 219

Chapter 228 OSPF www.juniper.net

Chapter 240 OSPF www.juniper.net

www.juniper.net OSPF Chapter 243

www.juniper.net OSPF Chapter 245

www.juniper.net OSPF Chapter 259

Chapter 266 OSPF www.juniper.net

www.juniper.net OSPF Areas Chapter 39