The following section is a summary of the major points you should be aware of in this chapter.
Open Short Path First Protocol Overview
- OSPF data structures store operational data, configured parameters and statistics
- There are four OSPF data structures. These are:
- The Interface Table
- The Neighbor Table
- The Link State Database
- The Routing Information Base
- The Interface Table provides a list of all interfaces that have been enabled for OSPF
- The Neighbor Table tracks all active OSPF neighbors
- The Link State Database (LSDB) contains information about the network topology
- The Routing Information Base (RIB) contains the results derived from the SPF calculation
- OSPF is a hierarchical routing protocol that logically divides the network into sub-domains
- This logical segmentation is used to limit the scope of LSA flooding
- In a multi-area OSPF network, one area must be designated as the backbone area
- The backbone is the logical center of the OSPF network
- All other non-backbone areas must be physically or logically connected to the backbone
- OSPF uses different default network types for different media. These are:
- Non-Broadcast
- Point-to-Point
- Broadcast
- Point-to Multipoint
- OSPF neighbors go through several states before the adjacency becomes FULL
- Valid OSPF states are Down, Attempt, Init, 2-Way, Exstart, Exchange, Loading and Full
- These parameters must match before an adjacency will go into the Full state:
- The interface MTU values
- The Hello and Dead Timers
- The Area ID
- The Authentication Type and Password
- The Stub Area flag
- IP Subnet and Subnet Mask
- Each LSA begins with a standard 20-byte LSA header that contains the following:
- Link State Age
- Options
- Link State Type
- Link State ID
- Advertising Router
- Link State Sequence Number
- Link State Checksum
- Length
- Type 1 LSAs are generated by each router for each area it belongs to
- Type 2 LSAs advertise the routers on the multi-access segment
- Type 3 LSAs are a summary of destinations outside of the local area
- Type 4 LSAs describe information about an Autonomous System Boundary Router
- Type 5 LSAs provide the network information necessary to reach the external networks
- Type 7 LSAs are used for external routing information from the ASBR in an NSSA
- OSPF supports addition special types of areas in addition to area 0 and normal areas
- These special types of areas are:
- Not-so-stubby Areas
- Totally Not-so-stubby Areas
- Stub Areas
- Totally Stubby Areas
- A virtual link is a logical extension of the OSPF backbone
Troubleshooting Neighbor Relationships
- OSPF neighbor relationship issues fall into one of the following categories:
- The Neighbor Table is Empty
- The Neighbor is stuck in the ATTEMPT state
- The Neighbor is stuck in the INIT state
- The Neighbor is stuck in the 2WAY state
- The Neighbor is stuck in the EXSTART/EXCHANGE state
- The Neighbor is stuck in the LOADING state
- The OSPF Neighbor Table may be empty due to one of the following:
- Basic OSPF Misconfigurations
- Layer 1 and Layer 2 Issues
- Access List Filtering
- Interface Misconfigurations
- The OSPF adjacency may be stuck in the ATTEMPT state due to the following:
- Incorrect NBMA Configuration
- Incorrect OSPF Configuration
- ACL Filtering
- Unidirectional Connectivity
- The OSPF adjacency may be stuck in the INIT state due to the following:
- ACL Filtering on One Side
- Layer 1 and Layer 2 Issues
- NBMA Misconfigurations
- The OSPF adjacency may be stuck in the 2WAY state due to the following:
- Neighbors all have their priority values set to zero (0)
- The OSPF adjacency may be stuck in the EXSTART/EXCHANGE state due to the following:
- Mismatched MTU Values
- Duplicate RIDs
- Broken Unicast Connectivity
- The OSPF adjacency may be stuck in the LOADING state due to the following:
- Corrupted LSR packets – which could be due to hardware or software issues