Respond quickly to network changes

Send triggered updates when a network change occurs

Send periodic updates, known as link-state refresh, at long intervals, such as e
very 30 minutes

LSAs are reliable; there is a method for acknowledging the delivery of LSAs.
LSAs are flooded throughout the area (or throughout the domain if there is only
one area).
LSAs have a sequence number and a set lifetime so that each router recognizes th
at it has the most up-to-date version of the LSA.
LSAs are periodically refreshed to confirm topology information before the infor
mation ages out of the link-state database.
LSAs are propagated to all neighb
LSAs are propagated to all neighboring devices using the reserved class D multic
ast address 224.0.0.5.
When a router receives an LSA, it updates its link-state database (LSDB).
The LSDB is used to calculate the best paths through the network
SAs are stored in a topology table, also called an LSDB
The OSPF protocol exchanges five packet types:
Hello
Database description (DBD)
Link-state request (LSR)
Link-state update (LSU)
Link-state acknowledgement (LSAck)

The hello protocol establishes and maintains neighbor relationships by ensuring

bidirectional (two-way) communication between neighbors
On broadcast OSPF networks, the default hello interval is ten seconds, and the d
efault dead interval is 40 seconds.
On nonbroadcast networks, the default hello interval is 30 seconds, and the defa
ult dead interval is two minutes or 120 seconds.
On point-to-point and multiaccess broadcast networks, the hello packet is sent o
ut using the multicast address 224.0.0.5.
On nonbroadcast multiaccess (NBMA), point-to-multipoint, and virtual links, the
hello packets are sent in unicast packets.

The link-state sequence number field in an LSA header is 32 bits

debug ip ospf packets
Point-to-point: A network that joins a single pair of routers.
Broadcast: A multiaccess broadcast network, such as Ethernet.
Nonbroadcast multiaccess (NBMA): A network that interconnects more than two rout
ers but that has no broadcast capability
On point-to-point networks, the router dynamically detects its neighboring route
rs by multicasting its hello packets to all OSPF routers, using the address 224.
0.0.5
The default OSPF hello and dead intervals on point-to-point links are 10 seconds
and 40 seconds, respectively.
The routers on a segment must elect a DR and a BDR to represent the multiaccess
broadcast network. The BDR does not perform any DR functions when the DR is oper
ating.
Instead, the BDR receives all the information, but the DR performs the LSA forwa
rding and LSDB synchronization tasks

The default OSPF hello and dead intervals on NBMA interfaces are 30 seconds and
120 seconds, respectively.

Nonbroadcast: Simulates the operation of OSPF in broadcast networks. Neighbors m

ust be manually configured, and DR and BDR election is required.
This configuration is typically used with fully meshed networks.

Point-to-multipoint: Treats a nonbroadcast network as a collection of point-to-p

oint links.
The routers automatically identify their neighboring routers but do not elect a
DR and BDR. This configuration is typically used with partially
meshed networks.

You can use the ip ospf network interface command to select the OSPF network typ
e for NBMA networks
OSPF point-to-multipoint works by exchanging additional LSUs that are designed t
o automatically discover neighboring routers and add them to the neighbor table
Duplicates LSA packets: Also as in nonbroadcast mode, when flooding out a nonbro
adcast interface in point-to-multipoint mode, the router must replicate the LSU.
The LSU packet is sent to each of the neighboring routers of the interface, as d
efined in the neighbor table.

The hello interval for a point-to-multipoint interface is 30 seconds, with a dea

d interval of 120 seconds.
Multipoint Frame Relay subinterfaces default to OSPF nonbroadcast mode, which re
quires that neighbors be statically configured and a DR and BDR be elected.

LSAs are the building blocks of the OSPF LSDB

A type 1 LSA describes the collective states of the directly connected links (in
terfaces) of the router.
A type 2 network LSA lists each of the attached routers that make up the transit
network, including the DR itself, as well as the subnet mask used on the link.
The type 2 LSA then floods to all routers within the transit network area. Typ
e 2 LSAs never cross an area boundary
A type 3 LSAs advertise any networks owned by an area to the rest of the areas i
n the OSPF autonomous system
A type 4 summary LSA is generated by an ABR only when an ASBR exists within an a
rea. A type 4 LSA identifies the ASBR and provides a route to it.
A type 5 external LSAs describe routes to networks outside the OSPF autonomous s
ystem. Type 5 LSAs are originated by the ASBR
A type 6 LSAs are specialized LSAs that are used in multicast OSPF applications.
A type 7 is an LSA type that is used in not-so-stubby areas (NSSAs)
A type 8 is a specialized LSA that is used in internetworking OSPF and Border Ga
teway Protocol (BGP)
The opaque LSAs, types 9, 10, and 11, are designated for future upgrades to OSPF
for application-specific purpose
(In "show ip ospf database" command) The router link-states are type 1 LSAs, the
net link-states are type 2, and the summary net link-states are type 3.
E1: Type O E1 external routes calculate the cost by adding the external cost to
the internal cost of each link that the packet crosses.
E2 (default): The external cost of O E2 packet routes is just the external cost

You can configure OSPF LSDB overload protection with Cisco IOS Release 12.3(7)T
and later
cost = 100Mbps / bandwidth
(config-router)# auto-cost reference-bandwidth ref-bw
The ref-bw is a reference bandwidth in megabits per second, and ranges from 1 to
4,294,967

Standard area: Accepts link updates, route summaries, and external routes (the d
efault).
Backbone area (transit area): The central entity to which all other areas connec
t to exchange and route information.
Stub area: Does not accept information about routes external to the autonomous s
ystem, such as routes from non-OSPF sources. (type 4 n 5)
Stub areas cannot contain ASBRs
Totally stubby area: Does not accept external autonomous system routes or summar
y routes from other areas internal to the autonomous system (type summary 3 4 n
5)
The ASBR originates type 7 LSAs to advertise the external destinations. The type
7 LSAs are flooded throughout the NSSA but are blocked by the ABR.
The ABR converts the type 7 LSA into a type 5 LSA, which is then propagated thro
ugh the remainder of the autonomous system.

Stub area
-there is a single abr, of if suboptimal routing paths to the other areas or ext
ernal autonomous systems are acceptable there can be more than one ABR
-all routers in the area are configs as stub
-there is no ASBR in the are
-the are is not area 0
-No virtual links go through the area
Routing from a stub area to the outside is based on a default route (0.0.0.0)
(config-router)# area 1 stub no-summary (for stupid Totally Stubby Fucken Area)
<<< THATS FOR FUCKEN ABRs

Redistribution into an NSSA creates a special type of LSA (type 7), which can ex
ist only in an NSSA. An NSSA ASBR generates this LSA,
and an NSSA ABR translates it into a type 5 LSA, which then gets propagated into
the OSPF domain
N1 means that the metric is calculated like an external type 1; N2 means that th
e metric is calculated like an external type 2.
(config-router)# area 1 nssa (no-summary - creates a nssa TSA )

show ip ospf - displays which ares are normal, stub or nssa

show ip ospf database - details of LSA
show ip ospf database nssa-external - displays specific details of each lsa type
7 update in database
A virtual link is a link that allows discontiguous area 0s to be connected or a
disconnected area to be connected to area 0 via a transit area.
An LSA usually refreshes every 30 minutes. LSAs learned through a virtual link h
ave the DoNotAge (DNA)

Whenever an LSA is sent, all affected OSPF routers have to recompute their LSDB
and the SPF tree.
Summary LSAs (type 3) and external LSAs (type 5) by default do not contain summa
rized routes.
Interarea route summarization: Can be configured on ABRs and applies to routes f
rom within each area. It does not apply to external routes injected into OSPF vi
a redistribution.
To perform effective interarea route summarization, network numbers within areas
should be assigned contiguously so that these addresses
can be summarized into a minimal number of summary addresses
External route summarization: Specific to external routes that are injected into
OSPF via route redistribution.
(config-router)# summar-address command is for fucken external asbr

There are two ways to advertise a default route into a standard area. The first
is to advertise 0.0.0.0 into the OSPF domain, provided that the advertising rout
er already has a default route.
The second is to advertise 0.0.0.0 regardless of whether the advertising router
already has a default route. The second method can be accomplished
by adding the keyword always to the default-information originate command.
A default route shows up in the OSPF database as an external LSA type 5.

OSPF supports two authentication methods:

Simple password authentication (also called plain-text authentication)
Message Digest (MD) 5 authentication
(config-if) ip ospf authentication
(config-if) ip ospf authentication-key password
If the service password-encryption command is not used when configuring OSPF aut
hentication, the key is stored as plain text in the router configuratio
To enable authentication for an OSPF area, use the area area-id authentication m
essage-digest router configuration command

(config-if) ip ospf message-digest-key key-id md5 key

(config-if) ip ospf message-digest-key 1 md5 password
(on debug)
The different types of authentication have these type codes: null type 0, simple p
assword type 1, MD5 type 2.