Ospf

Open Shortest Path First
2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net
An Overview of OSPF
OSPF is a link-state IGP used within an AS
OSPF floods link-state advertisements
OSPF routers use the received LSAs to create a
complete database of the network
OSPF uses the shortest-path-first algorithm to
calculate the best path to each destination
network
OSPF
AS 64512
2010 Juniper Networks, Inc. All rights reserved.
ISP X
AS 64587
www.juniper.net | 2
The Link-State Database

All OSPF routers maintain a copy of the
database
Database contents consist of information learned
through LSAs and must match on all routers within
an area
SPF algorithm uses the contents of the link-state
database as input data to calculate network paths
R2
R1
OSPF
Area 0
R3
R4
www.juniper.net | 3
OSPF Packet Types

The five OSPF packet types include:
Type
1
Hello
Type 2
Type 3
Database LinkDescripti State

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Link-state advertisements are

flooded reliably using link-state
requests, link-state updates, and
link-state acknowledgments.
R1
R2
Link-State Request
Link-State Update
Link-State Acknowledgment
www.juniper.net | 4
Hello Packet
Type
1
Hello
Type 2
Type 3

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Multicast hello packets are used to establish

and maintain OSPF neighbor relationships
Sent to 224.0.0.5all OSPF routers address
Consist of the OSPF header plus the following
fields:
Network
Hello interval*
Dead interval*
Options*
mask*
Router
priority
Designated
router
Backup designated
router
Neighbo
r
* Fields that must match to form an adjacency over a broadcast

medium; a matching
network mask is not required for point-to-point links
www.juniper.net | 5
Database Description Packet

Type
1
Hello
Type 2
Type 3

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Database description packets are exchanged

during adjacency formation to determine
which router is in charge of the database
exchange
Describe the contents of the link-state database
and consist of the OSPF header, a sequence
number, and LSA headers
www.juniper.net | 6
Link-State Request Packet

Type
1
Hello
Type 2
Type 3

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Link-state request packets are sent by an

OSPF router when that router detects its
database is stale
Used to request precise version of database and
consist of the OSPF
header, link-state type,R2linkR1
state ID, and advertising Link-State
routerRequest
Link-State Update
www.juniper.net | 7
Link-State Update Packet

Type
1
Hello
Type 2
Type 3

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Link-state update packets are the basic

information block in OSPF and can carry
multiple LSAs
Transmitted using multicast to either the all OSPF
routers address
R1(224.0.0.5) or the all DRs address
R2
Link-State
Request header,
(224.0.0.6), and consist of
the OSPF
Link-State Update
number of advertisements,
and LSAs
www.juniper.net | 8
Link-State Acknowledgment Packet

Type
1
Hello
Type 2
Type 3

on
Request
Type 4
LinkState
Update
Type 5
Link-State
Acknowledgme
nt
Link-state acknowledgment packets are

received in response to link-state update
packets
A single acknowledgment packet can include
responses to multiple
update packets and consist
R1
R2
Link-State
Request
of the OSPF header and the
LSA
header
Link-State Update
www.juniper.net | 9
Adjacency Formation
R2
R1
Down
2Way
ExStart
Exchange
Loading
Full
Hello (DR=0, Seen = 0)

Hello (DR=RT2, Seen = RT1)
Down
Init
Hello (DR=RT2, Seen = RT2)
2Way
DD (Seq=x, Master)
DD (Seq=y, Master)
DD (Seq=y, Slave)
DD (Seq=y+1, Master)
DD (Seq=y+1, Slave)
DD (Seq=y+n, Master)
DD (Seq=y+n, Slave)
LS Request
LS Update
LS Request
LS Update
ExStart
Exchange
Full
www.juniper.net | 10
Adjacency Optimization (1 of 2)
By default, OSPF attempts to form
adjacencies with all neighbors discovered on
all interfaces
On a broadcast media like Ethernet, this approach
is suboptimal because it would require a full mesh
of adjacencies
Adjacencie
s
Adjacency Optimization (2 of 2)
OSPF elects a DR to represent the segment
Minimizes OSPF processes and reduces traffic on
segment
A BDR is also elected to recover if the DR fails
OSPF adjacencies are

only formed with the DR
and BDR.
DR
BDR
DR
DR
DROther
DROther
DROther
Electing the Designated Router

Every OSPF router has a DR election priority
Priority range is 0255 (default is 128)
If two routers share the highest priority, the router
with the highest RID is elected
The election of a DR is a nondeterministic event
An existing DR will not be replaced
The first router on the segment within 40 seconds wins
DR
Priority: 255
RID: 192.168.100.10DR
BDR
DR
Priority: 128
RID: 192.168.100.100
OSPF Neighbors Versus Adjacencies

R1 (RID: 1.1.1.1)
DR
R2 (RID: 1.1.1.2)
BDR
Adjacencie
s
DROther
DROther
2-way
R4 (RID: 1.1.1.4)
R3 (RID: 1.1.1.3)
user@R1> show ospf neighbor
Address
Interface
172.25.0.4
ge-0/0/1.0
172.25.0.3
ge-0/0/1.0
172.25.0.2
ge-0/0/1.0
State
Full
Full
Full
ID
1.1.1.4
1.1.1.3
1.1.1.2
Pri
128
128
254
Dead
33
38
38

Address
Interface
172.25.0.1
ge-0/0/1.0
172.25.0.2
ge-0/0/1.0
172.25.0.3
ge-0/0/1.0
State
Full
Full
2Way
ID
1.1.1.1
1.1.1.2
1.1.1.3
Pri
255
254
128
Dead
37
35
34
Scaling an OSPF Network

Problem: As OSPF networks grow, so does the
size of the link-state database, which can
overload resources
Area 0
Area 0
Solution: Implement OSPF areas to shrink the

size of the link-state database
Area 1
Area 0
Area 2
Area 1
Area 0
Area 2
OSPF Areas
AS 65415
Area 0.0.0.1
Areas
Area 0.0.0.0
Area 0.0.0.0 serves as backbone area and

distributes routing information between
attached areas.
Area 0.0.0.2
An AS can be divided into smaller groups called areas

LSA flooding can be constrained to an area, which
effectively reduces the size of the link-state database
All routers maintain an identical copy of the link-state
database on a per-area basis
OSPF Routers
Backbone routers have at
least one link in OSPF Area
0.0.0.0
Area border routers (ABRs)

belong to Area 0.0.0.0 and an
attached area.
AS 65415
Area 0.0.0.1
ASBRs inject routing

information from outside the
OSPF domain.
Area 0.0.0.0
Area 0.0.0.2
Internal routers have all

OSPF links in the same
area.
OSPF Area Types

Intra-Area Routes Stub
Area
Special stub area that allows
external routes to be
advertised from the area but
not received from another area
Does not carry external

routes and cannot contain
ASBRs
Stub area that receives
only a default route from
the backbone
Totally Stubby
Area
Interarea Routes
(Summary Routes)
Not-So-Stubby
Area
Backbone
(0.0.0.0)
RIP
External Routes
BGP
Default Route
Overview of the LSA Packet Types

Router Links
Type 1
Network Links
Type 2
Describe the state and cost of the

routers links (interfaces) to the
area (Intra-area).
Originated for multi-access segments

with more than one attached router.
Describe all routers attached to the
specific segment. Originated by a
designated router (DR).
Summary Links
Type 3 and Type 4
External Links
Type 5
NSSA External Links

Type 7
NSSA
ABR Describe
Originated by ABRs.
networks in the AS but outside of
area (Inter-area). Also describe the
location of the ASBR.
ASBR
Originated by an ASBR. Describe
external destination prefixes or a
default route.
ASBR
Used by not-so-stubby areas to

import external routes into a
stub area.
Test Your Knowledge

Which of the recently discussed LSAs would
you expect to find in each
Stub of the listed areas?
Area
Not-SoStubby
Area
Totally
Stubby Area
Backbone
(0.0.0.0)
RIP
BGP
Junos OS OSPF Support

The Junos OS supports OSPF version 2 and
version 3, as well as a number of supporting
features, such as:
Stub, not-so-stubby, and totally stubby areas
Authentication
Summarization
External prefix limits
Graceful restart
Bidirectional Forwarding Detection
Configuring OSPF
[edit protocols]
user@R1# show
ospf {
area <area-id> {
<area options>;
interface <interface-name> {
<interface options>;
}
}
}
ospf3 {
area <area-id> {
<area options>;
interface <interface-name> {
<interface options>;
}
}
}
Used for IPv4 routing

environments
Used for IPv4 or IPv6 routing

environments
The Router ID
OSPF uses the RID to identify the router from
which a packet originated
You can manually define the RID under the [edit
routing-options] hierarchy
[edit routing-options]
user@R1# show
router-id 192.168.100.1;
The RID is a 32-bit

number in dotted quad
notation.
If you do not configure a RID, a non-127/8 IP

address of the first interface to come online is
used (typically lo0)
If lo0 does not have a suitable address, the IP
address associated with first hardware interface is
Note: We strongly recommend that you configure a RID to avoid
used
unpredictable
behavior if the interface addresses are changed.
Case Study: Topology and Objectives

Use the following topology as a guide to
implement OSPF
On R1, redistribute the 172.18.1.0/24 network and
ensure that it is installed as an external OSPF
route
Use metrics to ensure that the path using the ge0/0/1 interfaces within the backbone area is
Area 0.0.0.0
preferred Area 0.0.0.1
Area 0.0.0.2
ge-0/0/1
172.18.1.0/24
ge-1/0/0
ge-0/0/3
172.26.1.0/30
R1 - lo0/RID:
192.168.1.1
ge-0/0/1
ge-0/0/2
R2 - lo0/RID:
192.168.1.2
172.26.2.0/30
172.26.3.0/30
ge-0/0/1
ge-0/0/3 ge-1/0/1
ge-0/0/2
172.26.4.0/30
R3 - lo0/RID:
192.168.1.3
R4 - lo0/RID:
192.168.1.4
Case Study: Configuring OSPF

[edit protocols]
ASBR (Policy is defined
user@R1# show
and applied on the
ospf {
area 0.0.0.1 { next slide.)
interface ge-1/0/0.0;
interface lo0.0;
}
}
[edit protocols]
user@R4# show
ospf {
area 0.0.0.2 {
interface lo0.0;
}
}
[edit protocols]
ABRs
user@R2# show
ospf {
area 0.0.0.0 {
interface ge-0/0/2.0 {
Increased
metric 100;
metric for
}
secondary
interface lo0.0;
}
area 0.0.0.1 {
}
}
[edit protocols]
user@R3# show
ospf {
area 0.0.0.0 {
interface ge-0/0/2.0 {
metric 100;
}
path
interface lo0.0;
}
area 0.0.0.2 {
}
}
Case Study: Redistributing the Route

[edit policy-options]
user@R1# show
Redistribution policy is defined
policy-statement 2ospf {
under [edit policy-options]
term match-direct-route {
hierarchy.
from {
protocol direct;
route-filter 172.18.1.0/24 exact;
}
then accept;
}
}
[edit protocols]
user@R1# show
ospf {
export 2ospf;
area 0.0.0.1 {
interface lo0.0;
}
}
Redistribution policy is applied

under [edit protocols ospf]
hierarchy.
Test Your Knowledge

What configuration option allows R1 to inject
the 172.18.1.0/24 prefix into OSPF as an
internal OSPF route while prohibiting
adjacency formation?
Include the
[edit protocols]
user@R1# set ospf area 1 interface ge-0/0/1.0 passive
Area 0.0.0.0
Area 0.0.0.1
ge-0/0/1
172.18.1.0/24
ge-1/0/0
ge-0/0/3
172.26.1.0/30
R1 - lo0/RID:
192.168.1.1
ge-0/0/1
ge-0/0/2
R2 - lo0/RID:
192.168.1.2
172.26.2.0/30
172.26.3.0/30
passive option for

the interface
Area 0.0.0.2
ge-0/0/1
ge-0/0/3 ge-1/0/1
ge-0/0/2
172.26.4.0/30
R3 - lo0/RID:
192.168.1.3
R4 - lo0/RID:
192.168.1.4
Case Study: Monitoring OSPF (1 of 2)

Use the show ospf neighbor command to
display OSPF adjacency information
Address
Interface
172.26.2.2
ge-0/0/1.0
172.26.3.2
ge-0/0/2.0
172.26.1.1
ge-0/0/3.0
State
Full
Full
Full
Area 0.0.0.0
Area 0.0.0.1
ge-0/0/1
172.18.1.0/24
ge-1/0/0
ge-0/0/3
172.26.1.0/30
R1 - lo0/RID:
192.168.1.1
ID
192.168.1.3
192.168.1.3
192.168.1.1
ge-0/0/1
ge-0/0/2
R2 - lo0/RID:
192.168.1.2
172.26.2.0/30
172.26.3.0/30
Pri
128
128
128
Dead
39
36
34
Area 0.0.0.2
ge-0/0/1
ge-0/0/3 ge-1/0/1
ge-0/0/2
172.26.4.0/30
R3 - lo0/RID:
192.168.1.3
R4 - lo0/RID:
192.168.1.4
Case Study: Monitoring OSPF (2 of 2)

Use show route commands to verify route
entries and their selected paths
External prefix injected
by R1
inet.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
user@R2> show route 172.18.1.0/24
172.18.1.0/24
*[OSPF/150] 02:37:46, metric 0, tag 0

> to 172.26.1.1 via ge-0/0/3.0
Remote subnet connecting R3

and R4 is reachable through
desired path.
inet.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
user@R2> show route 172.26.4.0/30
172.26.4.0/30
*[OSPF/10] 02:24:29, metric 2

> to 172.26.2.2 via ge-0/0/1.0
Other Key Monitoring Commands

Additional show commands exist to provide
detailed information on the operation of
OSPF:
show
show
show
show
show
ospf
ospf
ospf
ospf
ospf
interface
route
database
statistics
log
Displaying OSPF Interface Parameters

Use the show ospf interface command to
display OSPF interface parameters
user@R2> show ospf interface
Interface
State
Area
ge-0/0/1.0
BDR
0.0.0.0
ge-0/0/2.0
DR
0.0.0.0
lo0.0
DR
0.0.0.0
ge-0/0/3.0
DR
0.0.0.1
ge-0/0/1
172.18.1.0/24
ge-0/0/3
172.26.1.0/30
R1 - lo0/RID:
192.168.1.1
BDR ID
192.168.1.2
192.168.1.3
0.0.0.0
192.168.1.1
Nbrs
1
1
0
1
Area 0.0.0.0
Area 0.0.0.1
ge-1/0/0
DR ID
192.168.1.3
192.168.1.2
192.168.1.2
192.168.1.2
ge-0/0/1
ge-0/0/2
R2 - lo0/RID:
192.168.1.2
172.26.2.0/30
172.26.3.0/30
ge-0/0/1
ge-0/0/2
R3 - lo0/RID:
192.168.1.3
Displaying OSPF Route Information

Use the show ospf route command to
display routes learned from, and advertised
to, OSPF
user@R2>
show ospf route
Topology default Route Table:
Prefix
192.168.1.1
192.168.1.3
172.18.1.0/24
172.26.1.0/30
172.26.2.0/30
172.26.3.0/30
172.26.4.0/30
192.168.1.1/32
192.168.1.2/32
192.168.1.3/32
192.168.1.4/32
Path
Type
Intra
Intra
Ext2
Intra
Intra
Intra
Inter
Intra
Intra
Intra
Inter
External prefix injected

by R1
Route
Type
AS BR
Area BR
Network
Network
Network
Network
Network
Network
Network
Network
Network
NH
Metric
Type
IP
1
IP
1
IP
0
IP
1
IP
1
IP
100
IP
2
IP
1
IP
0
IP
1
IP
2
NextHop
Interface
ge-0/0/3.0
ge-0/0/1.0
ge-0/0/3.0
ge-0/0/3.0
ge-0/0/1.0
ge-0/0/2.0
ge-0/0/1.0
ge-0/0/3.0
lo0.0
ge-0/0/1.0
ge-0/0/1.0
Nexthop
addr/label
172.26.1.1
172.26.2.2
172.26.1.1
172.26.2.2
172.26.1.1
172.26.2.2
172.26.2.2
Metric for ge-0/0/2.0 interface was

modified in earlier configuration
example.
Displaying the OSPF Link-State

Database
Use the show ospf database commands to
view the OSPF link-state database
user@R2> show ospf database
OSPF database, Area 0.0.0.0
Type
ID
Adv Rtr
Router *192.168.1.2
192.168.1.2
Router
192.168.1.3
192.168.1.3
Network 172.26.2.2
192.168.1.3
Network 172.26.3.2
192.168.1.3
Summary *172.26.1.0
192.168.1.2
Summary 172.26.4.0
192.168.1.3
Summary *192.168.1.1
192.168.1.2
Summary 192.168.1.4
192.168.1.3
ASBRSum *192.168.1.1
192.168.1.2
OSPF database, Area 0.0.0.1
Type
ID
Adv Rtr
Router
192.168.1.1
192.168.1.1
OSPF AS SCOPE link state database

Type
ID
Adv Rtr
Extern
172.18.1.0
192.168.1.1
2010
Juniper Networks,
Inc. All rights reserved.
ABRs maintain a separate database

for each OSPF area to which they
are attached.
Seq
Age Opt Cksum Len
0x8000000c 1387 0x22 0x84ae 60
0x80000023 1249 0x22 0x545e 60
0x80000005 2049 0x22 0x43e3 32
0x80000005 2449 0x22 0x38ed 32
0x80000007 2541 0x22 0x4db7 28
0x80000025 2249 0x22 0xe9f8 28
0x80000006 1618 0x22 0xa3bb 28
0x8000001a 1649 0x22 0x57ef 28
0x80000007 2310 0x22 0x93c9 28
Seq
0x80000007
Age
56
Opt Cksum Len

0x22 0x82c3 48
Seq
0x80000005
Age
96
Opt Cksum Len

0x22 0x374c
36
www.juniper.net
| 33
Displaying OSPF SPF-Related Information

Use the show ospf log command to display
OSPF SPF-related information
user@R2> show ospf log
Last instance of each event type
When
Type
Elapsed
04:28:24
SPF
0.000074
04:28:24
Stub
0.000030
04:28:24
Interarea
0.000042
04:28:24
External
0.000016
04:28:24
NSSA
0.000003
04:28:24
Cleanup
0.000049
Maximum length of each event type
When
Type
Elapsed
20:09:11
SPF
0.000110
Last 100 events

When
Type
16:38:21
NSSA
Elapsed
0.000003
Displaying OSPF Statistics

Use the show ospf statistics command to
view OSPF statistics
user@R2> show ospf statistics
Packet type
Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs
Sent
52
9
2
46
37
Total
Received
17
7
2
45
33
retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:
Last 5 seconds
Sent
Received
0
0
0
0
0
0
0
0
0
0
0,
40,
10,
0,
8,
2,
39,
last
last
last
last
last
last
last
5
5
5
5
5
5
5
seconds
seconds
seconds
seconds
seconds
seconds
seconds
:
:
:
:
:
:
:
0
0
0
0
0
0
0
OSPF Troubleshooting Tool Kit

Primary troubleshooting tools for OSPF
include traceoptions and CLI show commands
Protocol traceoptions
CLI show commands
Common Adjacency Problems

Adjacency problems and checklist items
include:
Problem
Checklist
No neighbor
detected
Check physical and data link layer

connectivity
Check for mismatched IP subnet/mask,
area number, area type,
authentication, hello/dead interval, or
network type
Stuck in ExStart
state
Check MTU settings to ensure that they

match
Stuck in 2-way
state
Normal for DR-Other neighbor
Using Traceoptions
Use traceoptions to identify adjacency
formation issues; a sample configuration is
shown:
[edit protocols]
user@R1# show
ospf {
traceoptions {
file trace-ospf;
flag error detail;
flag event detail;
}
area 0.0.0.0 {
interface lo0.0;
}
}
R1 - lo0:
192.168.1.1
User-defined file-name and flag

options. Include the detail option
to generate additional details in the
associated log file.
Area 0.0.0.0
ge-1/0/0
.1
ge-0/0/3
172.26.1.0/30
.2
R2 - lo0:
192.168.1.2
Displaying the Log File Contents

Use the show log file-name command to
display the contents of the traceoptions log
file
user@R1> show log trace-ospf
Oct 13 09:05:51.748087 OSPF packet ignored: area mismatch (0.0.0.1) from
172.26.1.2 on intf ge-1/0/0.0 area 0.0.0.0
Oct 13 09:05:51.748208 OSPF rcvd Hello 172.26.1.2 -> 224.0.0.5 (ge-1/0/0.0
IFL 73 area 0.0.0.0)
Oct 13 09:05:51.748237
Version 2, length 44, ID 192.168.1.1, area 0.0.0.1
Oct 13 09:05:51.748250
checksum 0x8c5c, authtype 0
Oct 13 09:05:51.748264
mask 255.255.255.252, hello_ivl 10, opts 0x2, prio
128
Oct 13 09:05:51.748281
dead_ivl 40, DR 172.26.1.2, BDR 0.0.0.0
According to the log file, R2
has the wrong OSPF area
configured.
Area 0.0.0.0
R1 - lo0:
192.168.1.1
ge-1/0/0
.1
ge-0/0/3
172.26.1.0/30
.2
R2 - lo0:
192.168.1.2
Viewing OSPF Error Counters

Use the show ospf statistics command to
view OSPF errors
user@R1> show ospf statistics
Receive errors:
410 area mismatches
17 mtu mismatches
81 Hellos received with our router ID
Use clear ospf statistics to refresh counters

user@R1> clear ospf statistics

Ospf

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ospf

Încărcat de

Drepturi de autor:

Formate disponibile

Open Shortest Path First

2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net

The Link-State Database

2010 Juniper Networks, Inc. All rights reserved.

OSPF Packet Types

Database LinkDescripti State

Link-state advertisements are

2010 Juniper Networks, Inc. All rights reserved.

Database LinkDescripti State

Multicast hello packets are used to establish

* Fields that must match to form an adjacency over a broadcast

Database Description Packet

Database LinkDescripti State

Database description packets are exchanged

Link-State Request Packet

Database LinkDescripti State

Link-state request packets are sent by an

2010 Juniper Networks, Inc. All rights reserved.

Link-State Update Packet

Database LinkDescripti State

Link-state update packets are the basic

2010 Juniper Networks, Inc. All rights reserved.

Link-State Acknowledgment Packet

Database LinkDescripti State

Link-state acknowledgment packets are

2010 Juniper Networks, Inc. All rights reserved.

Hello (DR=0, Seen = 0)

Hello (DR=RT2, Seen = RT2)

2010 Juniper Networks, Inc. All rights reserved.

OSPF adjacencies are

2010 Juniper Networks, Inc. All rights reserved.

Electing the Designated Router

2010 Juniper Networks, Inc. All rights reserved.

OSPF Neighbors Versus Adjacencies

user@R4> show ospf neighbor

2010 Juniper Networks, Inc. All rights reserved.

Scaling an OSPF Network

Solution: Implement OSPF areas to shrink the

2010 Juniper Networks, Inc. All rights reserved.

Area 0.0.0.0 serves as backbone area and

An AS can be divided into smaller groups called areas

Area border routers (ABRs)

ASBRs inject routing

Internal routers have all

OSPF Area Types

Does not carry external

2010 Juniper Networks, Inc. All rights reserved.

Overview of the LSA Packet Types

Describe the state and cost of the

Originated for multi-access segments

NSSA External Links

2010 Juniper Networks, Inc. All rights reserved.

Used by not-so-stubby areas to

Test Your Knowledge

2010 Juniper Networks, Inc. All rights reserved.

Junos OS OSPF Support

2010 Juniper Networks, Inc. All rights reserved.

2010 Juniper Networks, Inc. All rights reserved.

Used for IPv4 routing

Used for IPv4 or IPv6 routing

The RID is a 32-bit

If you do not configure a RID, a non-127/8 IP

Case Study: Topology and Objectives