Professional Documents
Culture Documents
² Link-State Protocol
² “Classless” Protocol
² Standards Based
² Large Scalability
² Topology summarizaPon
Why Use OSPF?
² Fast Convergence
² Efficient UpdaPng
² Extensible
² Step 2
² Step 3
² Hello packets contain a_ributes that neighbors must agree on to form “adjacency”
² Manual configuraPon
² Interface IP Address
² Interface MTU
² Network Type
² AuthenPcaPon
² Stub Flags
² Local Router-ID
² Local Area-ID
² Hello Interval
² Dead Interval
Database Synchronization
Negotiate master / slave relationship and DBD
ExStart State packet sequence number
More LSAs
required
No
Yes
DBD exchanged as LSAs are requested and sent
Exchange State Transit to either Loading or Full state after
completing the database description
Route Calculations
Router is synchronized with the neighbor and
Full State route calculations using the SPF algorithm begins
Neighbor Discovery – Hello Protocol
.1 172.16.5.0 /24 .2
R1 Fa0/0 Fa0/1 R2
Down State
ATempt State
R1 neighbor list:
172.16.5.2, int Fa0/0
Two-Way State
Database Synchronization & Route Calculation
.1 172.16.5.0 /24 .2
R1 Fa0/0 Fa0/1 R2
Exchange State
Here is a summary of my link-state database.
*
DBD
Here is a summary of my link-state database.
*
DBD
² Each router’s LSAs include a “cost” a_ribute for each described link
² Cisco’s implementaPon uses bandwidth based cost, but per RFC it is arbitrary
TenGigabitEthernet)
Step 3 – Neighbor & Topology Maintenance
² Once adjacencies established and SPT built, OSPF state machine tracks neighbor and topology
changes
² If a Hello packet is not received from a neighbor within RouterDeadInterval, the neighbor is
declared down
² Sequence number
² Age
² Checksum
² I.e. ip rouPng
² Process level
² Interface level
² show ip ospf
² Transport problems
² debug ip packet
² Down/A_empt
² Init
² 2-Way
² ExStart
² Exchange
² Loading
² Full
OSPF Adjacencies Attributes
² Unique OSPF Adjacency A_ributes
² Router-ID
² Interface IP Address
² Interface MTU
² Network Type
² AuthenPcaPon
² Stub Flags
² Changes inside the area require LSA flooding and full SPF
² Changes outside the area don’t always require LSA flooding or SPF
² Area 0 (0.0.0.0)
² Must be conPguous
² Non-backbone areas
² Internal routers
² At least one link in the OSPF domain•At least one link outside the OSPF domain
² Area type
OSPF LSA Types
² LSA types are…
² N1/N2
² LSA Type 7
LSA Type 1 – Router LSA
² Generated by every router in the OSPF domain
² Not flooded outside the area they originate in
² Metric Type
² Type 1 = E1
² Type 2 = E2 (default)
² Forward Address
² Who should I route towards to reach the link?
² Usually the ASBR itself, but could be someone else in some designs
² Route Tag
OSPF External Type 1 vs. Type 2
² External route type controls how metric for external link is calculated
² Type 1 (E1)
² Take the cost the ASBR reports in plus the cost to the ASBR
² Type 2 (E2)
² Take just the cost the ASBR reports in