Open Shortest Path First

OSPF (Open Shortest Path First)

OSPF is a standardized Link-State routing protocol, designed to
scale efficiently to support larger networks.
OSPF adheres to the following Link State characteristics:
• OSPF employs a hierarchical network design using Areas.
• OSPF will form neighbor relationships with adjacent routers in the same
Area.
• Instead of advertising the distance to connected networks, OSPF
advertises the status of directly connected links using Link-State Advertisements
(LSAs).
• OSPF sends updates (LSAs) when there is a change to one of its links,
and will only send the change in the update. LSAs are additionally refreshed every
30 minutes.
• OSPF traffic is multicast either to address 224.0.0.5 (all OSPF routers) or
224.0.0.6 (all Designated Routers).
• OSPF uses the Dijkstra Shortest Path First algorithm to determine the
shortest path.
• OSPF is a classless protocol, and thus supports VLSMs.
Other characteristics of OSPF include:
• OSPF supports only IP routing.
• OSPF routes have an administrative distance is 110.
• OSPF uses cost as its metric, which is computed based on the bandwidth
of the link. OSPF has no hop-count limit.
The OSPF process builds and maintains three separate tables:
• A neighbor table – contains a list of all neighboring routers.
• A topology table – contains a list of all possible routes to all known
networks within an area.
• A routing table – contains the best route for each known network.
 OSPF Neighbors
OSPF forms neighbor relationships, called adjacencies, with other routers in
the same Area by exchanging Hello packets to multicast address 224.0.0.5.
Only after an adjacency is formed can routers share routing information.
Each OSPF router is identified by a unique Router ID. The Router ID
can be determined in one of three ways:
• The Router ID can be manually specified.
• If not manually specified, the highest IP address configured on any
Loopback interface on the router will become the Router ID.
• If no loopback interface exists, the highest IP address configured on any
Physical interface will become the Router ID.
By default, Hello packets are sent out OSPF-enabled interfaces every 10
seconds for broadcast and point-to-point interfaces, and 30 seconds for
non-broadcast and point-to-multipoint interfaces.
OSPF also has a Dead Interval, which indicates how long a router will wait
without hearing any hellos before announcing a neighbor as “down.”
Default for the Dead Interval is 40 seconds for broadcast and point-to-point
interfaces, and 120 seconds for non-broadcast and point-to-multipoint
interfaces. Notice that, by default, the dead interval timer is four times the
Hello interval.
These timers can be adjusted on a per interface basis:
Router(config-if)# ip ospf hello-interval 15
Router(config-if)# ip ospf dead-interval 60
 OSPF Neighbors (continued)
OSPF routers will only become neighbors if the following parameters
within a Hello packet are identical on each router:
• Area ID
• Area Type (stub, NSSA, etc.)
• Prefix
• Subnet Mask
• Hello Interval
• Dead Interval
• Network Type (broadcast, point-to-point, etc.)
• Authentication
The Hello packets also serve as keepalives to allow routers to quickly
discover if a neighbor is down. Hello packets also contain a neighbor
field that lists the Router IDs of all neighbors the router is connected to.
A neighbor table is constructed from the OSPF Hello packets,
which includes the following information:
• The Router ID of each neighboring router
• The current “state” of each neighboring router
• The interface directly connecting to each neighbor
• The IP address of the remote interface of each neighbor

(Reference: http://www.cisco.com/warp/public/104/29.html)
OSPF Designated Routers
In multi-access networks such as
Ethernet, there is the possibility of
many neighbor relationships on the
same physical segment. In the above
example, four routers are connected
into the same multi-access segment.
Using the following formula (where
“n” is the number of routers):
n(n-1)/2

…..it is apparent that 6 separate adjacencies are needed for a fully meshed
network. Increase the number of routers to five, and 10 separate adjacencies
would be required. This leads to a considerable amount of unnecessary
Link State Advertisement (LSA) traffic.
If a link off of Router A were to fail, it would flood this information to all
neighbors. Each neighbor, in turn, would then flood that same information
to all other neighbors. This is a waste of bandwidth and processor load.
To prevent this, OSPF will elect a Designated Router (DR) for each multi-
access networks, accessed via multicast address 224.0.0.6. For redundancy
purposes, a Backup Designated Router (BDR) is also elected.
OSPF routers will form adjacencies with the DR and BDR. If a change
occurs to a link, the update is forwarded only to the DR, which then
forwards it to all other routers. This greatly reduces the flooding of LSAs.
DR and BDR elections are determined by a router’s OSPF priority,
which is configured on a per-interface basis (a router can have interfaces
in multiple multi-access networks). The router with the highest priority
becomes the DR; second highest becomes the BDR. If there is a tie in
priority, whichever router has the highest Router ID will become the DR.
To change the priority on an interface:
Router(config-if)# ip ospf priority 125

Default priority on Cisco routers is 1. A priority of 0 will prevent the router

from being elected DR or BDR. Note: The DR election process is not
preemptive. Thus, if a router with a higher priority is added to the network,
it will not automatically supplant an existing DR. Thus, a router that should
never become the DR should always have its priority set to 0.
 OSPF Neighbor States
Neighbor adjacencies will progress through several states, including:
Down – indicates that no Hellos have been heard from the
neighboring router.
Init – indicates a Hello packet has been heard from the neighbor, but
two-way communication has not yet been initialized.
2-Way – indicates that bidirectional communication has been established.
Recall that Hello packets contain a neighbor field. Thus, communication
is considered 2-Way once a router sees its own Router ID in its neighbor’s
Hello Packet. Designated and Backup Designated Routers are elected at
this stage.
ExStart – indicates that the routers are preparing to share link state
information. Master/slave relationships are formed between routers
to determine who will begin the exchange.
Exchange – indicates that the routers are exchanging Database
Descriptors (DBDs). DBDs contain a description of the router’s Topology
Database. A router will examine a neighbor’s DBD to determine if it has
information to share.
Loading – indicates the routers are finally exchanging Link State
Advertisements, containing information about all links connected to each
router. Essentially, routers are sharing their topology tables with each other.
Full – indicates that the routers are fully synchronized. The topology table
of all routers in the area should now be identical. Depending on the “role” of
the neighbor, the state may appear as:
• Full/DR – indicating that the neighbor is a Designated Router (DR)
• Full/BDR – indicating that the neighbor is a Backup Designated Router
(BDR)
• Full/DROther – indicating that the neighbor is neither the DR or
BDR
On a multi-access network, OSPF routers will only form Full adjacencies
with DRs and BDRs. Non-DRs and non-BDRs will still form adjacencies,
but will remain in a 2-Way State. This is normal OSPF behavior.
 OSPF Network Types
OSPF’s functionality is different across several different network
topology types. OSPF’s interaction with Frame Relay will be explained in
another section
Broadcast Multi-Access – indicates a topology where broadcast occurs.
• Examples include Ethernet, Token Ring, and ATM.
• OSPF will elect DRs and BDRs.
• Traffic to DRs and BDRs is multicast to 224.0.0.6. Traffic from DRs
and BDRs to other routers is multicast to 224.0.0.5.
• Neighbors do not need to be manually specified.
Point-to-Point – indicates a topology where two routers are
directly connected.
• An example would be a point-to-point T1.
• OSPF will not elect DRs and BDRs.
• All OSPF traffic is multicast to 224.0.0.5.
• Neighbors do not need to be manually specified.
Point-to-Multipoint – indicates a topology where one interface can
connect to multiple destinations. Each connection between a source and
destination is treated as a point-to-point link.
• An example would be Point-to-Multipoint Frame Relay.
• OSPF will not elect DRs and BDRs.
• All OSPF traffic is multicast to 224.0.0.5.
• Neighbors do not need to be manually specified.
Non-broadcast Multi-access Network (NBMA) – indicates a
topology where one interface can connect to multiple destinations;
however, broadcasts cannot be sent across a NBMA network.
• An example would be Frame Relay.
• OSPF will elect DRs and BDRs.
• OSPF neighbors must be manually defined, thus All OSPF traffic is
unicast instead of multicast.

Remember: on non-broadcast networks, neighbors must be

manually specified, as multicast Hello’s are not allowed.
Configuring OSPF Network Types
The default OSPF network type for basic Frame Relay is Non-broadcast
Multi-access Network (NBMA). To configure manually:
Router(config)# interface s0
Router(config-if)# encapsulation frame-relay
Router(config-if)# frame-relay map ip 10.1.1.1 101
Router(config-if)# ip ospf network non-broadcast
Router(config)# router ospf 1
Router(config-router)# neighbor 10.1.1.1

Notice that the neighbor was manually specified, as multicasting is not

allowed on an NBMA. However, the Frame-Relay network can be
tricked into allowing broadcasts, eliminating the need to manually
specify neighbors:
Router(config)# interface s0
Router(config-if)# encapsulation frame-relay
Router(config-if)# frame-relay map ip 10.1.1.1 101 broadcast
Router(config-if)# ip ospf network broadcast

Notice that the ospf network type has been changed to broadcast, and the
broadcast parameter was added to the frame-relay map command. The
neighbor no longer needs to be specified, as multicasts will be allowed
out this map.
The default OSPF network type for Ethernet and Token Ring is
Broadcast Multi-Access. To configure manually:
Router(config)# interface e0
Router(config-if)# ip ospf network broadcast
The default OSPF network type for T1’s (HDLC or PPP) and Point-to-
Point Frame Relay is Point-to-Point. To configure manually:
Router(config)# interface s0
Router(config-if)# encapsulation frame-relay
Router(config)# interface s0.1 point-to-point
Router(config-if)# frame-relay map ip 10.1.1.1 101 broadcast
Router(config-if)# ip ospf network point-to-point
Configuring OSPF Network Types (continued)
The default OSPF network type for Point-to-Multipoint Frame Relay is still
Non-broadcast Multi-access Network (NBMA). However, OSPF
supports an additional network type called Point-to-Multipoint, which will
allow neighbor discovery to occur automatically. To configure:
Router(config)# interface s0
Router(config-if)# encapsulation frame-relay
Router(config)# interface s0.2 multipoint
Router(config-if)# frame-relay map ip 10.1.1.1 101 broadcast
Router(config-if)# ip ospf network point-to-multipoint

Additionally, a non-broadcast parameter can be added to the ip ospf

network command when specifying point-to-multipoint.
Router(config)# interface s0
Router(config-if)# encapsulation frame-relay
Router(config)# interface s0.2 multipoint
Router(config-if)# frame-relay map ip 10.1.1.1 101
Router(config-if)# ip ospf network point-to-multipoint non-broadcast
Router(config)# router ospf 1
Router(config-router)# neighbor 10.1.1.1

Notice the different in configuration. The frame-relay map command no

longer has the broadcast parameter, as broadcasts and multicasts are not
allowed on a non-broadcast network.
Thus, in the OSPF router configuration, neighbors must again be manually
specified. Traffic to those neighbors will be unicast instead of multicast.
OSPF network types must be set identically on two “neighboring”
routers, otherwise they will never form an adjacency.
 LSAs and the OSPF Topology Database
OSPF, as a link-state routing protocol, does not rely on routing-by-rumor
as RIP and IGRP do.
Instead, OSPF routers keep track of the status of links within their
respective areas. A link is simply a router interface. From these lists of links
and their respective statuses, the topology database is created. OSPF routers
forward link-state advertisements (LSAs) to ensure the topology database
is consistent on each router within an area.
Several LSA types exist:
• Router LSA (Type 1) – Contains a list of all links local to the router, and the
status and “cost” of those links. Type 1 LSAs are generated by all routers in OSPF,
and are flooded to all other routers within the local area.
• Network LSA (Type 2) – Generated by all Designated Routers in OSPF, and
contains a list of all routers attached to the Designated Router.
• Network Summary LSA (Type 3) – Generated by all ABRs in OSPF, and
contains a list of all destination networks within an area. Type 3 LSAs are sent
between areas to allow inter-area communication to occur.
• ASBR Summary LSA (Type 4) – Generated by ABRs in OSPF, and
contains a route to any ASBRs in the OSPF system. Type 4 LSAs are sent from an
ABR into its local area, so that Internal routers know how to exit the Autonomous
System.
• External LSA (Type 5) – Generated by ASBRs in OSPF, and contain routes
to destination networks outside the local Autonomous System. Type 5 LSAs can
also take the form of a default route to all networks outside the local AS. Type 5
LSAs are flooded to all areas in the OSPF system.
Multicast OSPF (MOSPF) utilizes a Type 6 LSA, but that goes beyond
the scope of this guide.
Later in this section, Type 7 NSSA External LSAs will be described
in detail.
The OSPF Metric
OSPF determines the best (or shortest) path to a destination network using a
cost metric, which is based on the bandwidth of interfaces. The total cost of
a route is the sum of all outgoing interface costs. Lowest cost is preferred.
Cisco applies default costs to specific interface types:

Type Cost
Serial (56K) 1785
Serial (64K) 1562
T1 (1.544Mbps) 64
Token Ring (4Mbps) 25
Ethernet (10 Mbps) 10
Token Ring (16 Mbps) 6
Fast Ethernet 1

On Serial interfaces, OSPF will use the configured bandwidth (measured in

Kbps) to determine the cost:
Router(config)# interface s0
Router(config-if)# bandwidth 64

The default cost of an interface can be superseded:

Router(config)# interface e0
Router(config-if)# ip ospf cost 5

Changing the cost of an interface can alter which path OSPF deems
the “shortest,” and thus should be used with great care.
To alter how OSPF calculates its default metrics for interfaces:
Router(config)# router ospf 1
Router(config-router)# ospf auto-cost reference-bandwidth 100

The above ospf auto-cost command has a value of 100 configured, which is
actually the default. This indicates that a 100Mbps link will have a cost of 1
(because 100/100 is 1). All other costs are based off of this. For example,
the cost of 4 Mbps Token Ring is 25 because 100/4 = 25.
 OSPF Area Types
In order to control the propagation of LSAs in the OSPF domain,
several area types were developed.
Standard Area – A “normal” OSPF area.

• Routers within a standard area will share Router (Type 1) and

Network (Type 2) LSAs to build their topology tables. Once fully synchronized,
routers within an area will all have identical topology tables.
• Standard areas will accept Network Summary (Type 3) LSAs, which
contain the routes to reach networks in all other areas.
• Standard areas will accept ASBR Summary (Type 4) and External
(Type 5) LSAs, which contain the route to the ASBR and routes to external
networks, respectively.
Configuration of standard areas is straight forward:
Router(config)# router ospf 1 Router(config-router)#
network 10.1.0.0 0.0.7.255 area 1
Stub Area – Prevents external routes from flooding into an area.

• Like Standard areas, Stub area routers will share Type 1 and Type 2
LSAs to build their topology tables.
• Stub areas will also accept Type 3 LSAs to reach other areas.
• Stub areas will not accept Type 4 or Type 5 LSAs, detailing routes to
external networks.
The purpose of Stub areas is to limit the number of LSAs flooded into the
area, to conserve bandwidth and router CPUs. The Stub’s ABR will
automatically inject a default route into the Stub area, so that those
routers can reach the external networks. The ABR will be the next-hop for
the default route.
Configuration of stub areas is relatively simple:
Router(config)# router ospf 1
Router(config-router)# network 10.1.0.0 0.0.7.255 area 1
Router(config-router)# area 1 stub

The area 1 stub command must be configured on all routers in the Stub area.
No ASBRs are allowed in a Stub area.
 OSPF Area Types (continued)
External
Networks
More External
Networks

Area 1 Area 2
Router G

Router A Router

Router C Router D

Router B Area 0 Router

Not So Stubby Area (NSSA) – Similar to a Stub area; prevents external

routes from flooding into an area, unless those external routes
originated from an ASBR within the NSSA area.
• Like Standard and Stub areas, NSSA area routers will share Type 1
and Type 2 LSAs to build their topology tables.
• NSSA areas will also accept Network Summary (Type 3) LSAs, which
contain the routes to reach networks in all other areas.
• NSSA areas will not accept Type 4 or Type 5 LSAs, detailing routes
to external networks.
• If an ASBR exists within the NSSA area, that ASBR will generate
Type 7 LSAs.
Again, NSSA areas are almost identical to Stub areas. If Area 1 was
configured as an NSSA, it would not accept any external routes
originating from Router G (an ASBR outside Area 1).
However, Area 1 also has an ASBR within the area (Router A). Those
external routes will be flooded into Area 1 as Type 7 LSAs. These external
routes will not be forwarded to other areas as Type 7 LSAs; instead, they will
be converted into Type 5 LSAs by Area 1’s ABR (Router C).
Configuration of NSSA areas is relatively simple:
Router(config)# router ospf 1
Router(config-router)# network 10.1.0.0 0.0.7.255 area 1
Router(config-router)# area 1 nssa
The area 1 nssa command must be applied to all routers in the NSSA area.
 OSPF Area Types (continued)
External
Networks
More External
Networks

Area 1 Area 2
Router G

Router A Router E

Router C Router D

Router B Area 0 Router F

Totally Not So Stubby Area (TNSSA) – Similar to a Totally Stubby area;

prevents both inter-area and external routes from flooding into an area, unless
those external routes originated from an ASBR within the NSSA area.
• Like Standard and Stub areas, TNSSA area routers will share Type 1
and Type 2 LSAs to build their topology tables.
• TNSSA areas will not accept Type 3 LSAs to other areas.
• TNSSA areas will not accept Type 4 or Type 5 LSAs, detailing routes
to external networks.
• If an ASBR exists within the TNSSA area, that ASBR will generate
Type 7 LSAs.
With the exception of not accepting inter-area routes, TNSSA areas
are identical in function to NSSA areas.
Configuration of TNSSA areas is relatively simple:
Router(config)# router ospf 1
Router(config-router)# network 10.1.0.0 0.0.7.255 area 1
Router(config-router)# area 1 nssa no-summary

The area 1 nssa no-summary command is configured only on the ABR of

the TNSSA area; other routers within the area are configured with the area
1 nssa command.
OSPF and Default Routes
We have learned about four types of OSPF areas:
• Standard areas • Totally Stubby areas
• Stub areas • Not So Stubby areas (NSSA)

The ABRs and ASBRs of Standard areas do not automatically generate

(or inject) default routes into the area. Consider the following example:
Area 1 Area 0

External
Networks
Router A Router C

Router B

Assume that Area 1 is configured as a Standard area. Router C will forward

Type 3 LSAs from all other areas into Area 1, allowing Router A and
Router B to reach inter-area networks.
Notice also that Router A is an ASBR, connecting to an external
Autonomous System. Thus, Router A will generate Type 5 LSAs,
detailing the routes to these external networks.
To additionally force Router A to generate a default route (indicating
itself as the next hop) for the external networks, and inject this into Area 1.
This default route will be advertised as a Type 5 LSA to all other areas:
RouterA(config)# router ospf 1 RouterA(config-
router)# default-information originate

Router A must have a default route in its routing table in order for the
above command to function. Router A’s default route would point to some
upstream router in the external Autonomous System.
If a default route does not exist in its routing table, Router A can still
be forced to advertise a default route using the always parameter:
RouterA(config)# router ospf 1 RouterA(config-router)#
default-information originate always
OSPF and Default Routes (continued)
The ABRs of Stub and Totally Stubby areas automatically generate (and
inject) a default route (0.0.0.0/0) into the area. Routers in Stub areas use this
default route to reach external networks, while routers in Totally Stubby areas
use the default route to reach both inter-area and external networks.
To control the “cost” metric of the default route in Stub or Totally
Stubby areas (configured on the ABR):
Router(config)# router ospf 1
Router(config-router)# area 1 stub
Router(config-router)# area 1 default-cost 10

The ABRs of NSSA areas must be manually configured to generate

(and inject) a default route into the area:
Router(config)# router ospf 1
Router(config-router)# area 1 nssa default-information-originate

Additionally, the ASBR of an NSSA area can generate and inject a

default route. This default route will be advertised as a Type 7 LSA, as
Type 5 LSA’s are not allowed in NSSAs. The command is no different
than injecting a default route from an NSSA ABR:
Router(config)# router ospf 1
Router(config-router)# area 1 nssa default-information-originate

Reference: (http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094a74.shtml)
OSPF SPF Timers
To adjust the SPF timers in OSPF:
Router(config)# router ospf 1
Router(config-router)# timers spf 10 15

The timers spf command includes two parameters, measured in seconds.

The first (10) indicates the SPF-Delay, or how long the OSPF should wait
after receiving a topology change to recalculate the shortest path. The
second (15) indicates the SPF-Holdtime, or how long OSPF should wait in
between separate SPF calculations.
The timers spf command has actually become deprecated. It has
been replaced with:
Router(config)# router ospf 1 Router(config-router)#
timers throttle spf 5 10000 80000

The timers throttle spf command includes three parameters, measure in

milliseconds. The first (5) indicates how long OSPF should wait after
receiving a topology change to recalculate the shortest path. The second
(10000) indicates the hold-down time, or how long OSPF should wait in
between separate SPF calculations. If OSPF receives another topology
change during the hold-time interval, it will continue to double the hold-
time interval until it reaches the maximum hold-time (80000).
The purpose of the both SPF timer commands is to prevent OSPF from
constantly converging, if the network links are “flapping.” The timers
spf and timers throttle spf commands cannot be used together.
Advanced OSPF Configuration
To force the OSPF process to ignore OSPF Multicast (Type 6) LSAs:
Router(config)# router ospf 1
Router(config-router)# ignore lsa mospf
To force an interface to filter all outgoing OSPF LSA’s:
Router(config)# interface e0 Router(config-if)#
ip ospf database-filter all out

Loopback interfaces are treated differently than other interfaces, when

advertised in OSPF. OSPF will advertise a loopback interface as a
specific “host” route (with a mask of /32 or 255.255.255.255). To force
OSPF to advertise a loopback interface with its proper subnet mask:
Router(config)# interface loopback0
Router(config-if)# ip address 10.50.5.1 255.255.255.0
Router(config-if)# ip ospf network point-to-point
 Troubleshooting OSPF
To view the OSPF Neighbor Table:
Router# show ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
7.7.7.7 1 FULL/ - 00:00:36 150.50.17.2 Serial0
6.6.6.6 1 FULL/DR 00:00:11 150.50.18.1 Ethernet0

The Neighbor Table provides the following information about

each neighbor:
• The Router ID of the remote neighbor.
• The OSPF priority of the remote neighbor (used for DR/BDR elections).
• The current neighbor state.
• The dead interval timer.
• The connecting IP address of the remote neighbor.
• The local interface connecting to the remote neighbor.

To view the OSPF topology table:

Router# show ip ospf database
OSPF Router with ID (9.9.9.9) (Process ID 10)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
7.7.7.7 7.7.7.7 329 0x80000007 0x42A0 2
8.8.8.8 8.8.8.8 291 0x80000007 0x9FFC 1
Summary Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
192.168.12.0 7.7.7.7 103 0x80000005 0x13E4
192.168.34.0 7.7.7.7 105 0x80000003 0x345A

The Topology Table provides the following information:

• The actual link (or route).
• The advertising Router ID.
• The link-state age timer.
• The sequence number and checksum for each entry.
(Reference: http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/products_command_reference_chapter09186a008017d02e.html)
 Troubleshooting OSPF (continued)
To view the specific information about an OSPF process:
Router# show ip ospf 1
Routing Process "ospf 1" with ID 9.9.9.9
Supports only single TOS(TOS0) routes
Supports opaque LSA
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm executed 3 times
Area ranges are
Number of LSA 2. Checksum Sum 0xDDEC
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0

The show ip ospf command provides the following information:

• The local Router ID.
• SPF Scheduling information, and various SPF timers.
• The number of interfaces in specific areas, including the type of area.
• The link-state age timer.
• The sequence number and checksum for each entry.
 Troubleshooting OSPF (continued)
To view OSPF-specific information on an interface:
Router# show ip ospf interface s0
Serial0 is up, line protocol is up
Internet Address 192.168.79.2/24, Area 0
Process ID 10, Router ID 9.9.9.9, Network Type POINT_TO_POINT, Cost:
64 Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit
5 Hello due in 00:00:04
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 7.7.7.7
Suppress hello for 0 neighbor(s)

The show ip ospf interface command provides the following information:

• The local Router ID.
• The interface network type.
• The OSPF cost for the interface.
• The interface Hello and Dead timers.
• A list of neighbor adjacencies.
To view routing protocol specific information for OSPF:
Router# show ip protocols
Routing Protocol is “ospf 10"
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Routing for Networks:
192.168.79.0 0.0.0.255 area 0
192.168.109.0 0.0.0.255 area 0
Routing Information Sources:
Gateway Distance Last Update
7.7.7.7 110 00:01:05
Distance: (default is 110)

The show ip protocols command provides the following information:

• Locally originated networks that are being advertised.
• Neighboring sources for routing information
• The administrative distance of neighboring sources.
Troubleshooting OSPF (continued)
To reset an OSPF process, including neighbor adjacencies:
Router# clear ip ospf process

To display information about OSPF virtual-links:

Router# show ip ospf virtual-links

To display routes to both ABRs and ASBRs:

Router# show ip ospf border-routers

To debug OSPF in realtime:

Router# debug ip ospf adj
Router# debug ip ospf events
Router# debug ip ospf hello