PacketLab
OSPF · Fundamentals and adjacency

Neighbor states and requirements

Read the adjacency state before choosing the next diagnostic step.

Understand

StateWhat has happened / what to inspect
DownNo recent valid Hello; check link, activation and packet delivery.
AttemptNBMA manual-neighbor polling; not expected in this multicast point-to-point lab.
InitA Hello arrived, but our router ID was absent from its neighbor list: investigate one-way delivery.
2-WayBidirectional Hellos; adjacency selection follows. Normal between two DROTHERs on broadcast LANs.
ExStartNegotiate database-description roles and sequence. Persistent stalls suggest MTU, duplicate ID or packet-delivery issues.
ExchangeExchange database-description summaries.
LoadingRequest and receive missing LSAs. Persistent requests need delivery/retransmission investigation.
FullRelevant databases synchronized.

Normal progress on this lab is Down → Init → 2-Way → ExStart → Exchange → Loading → Full. Some states are brief or skipped in sampled output. Router IDs must differ. Area and hello/dead values must agree; area options and authentication must be compatible. On broadcast/NBMA links the subnet mask is checked; point-to-point has different mask handling. A network-type mismatch may form a misleading partial adjacency, so configure compatible types explicitly.

Lab setup

Use a fresh lab for this lesson; changes from other lessons are not cumulative. All outputs are illustrative excerpts, not recorded router tests. Transit cost is explicitly 10 and Loopback0 cost is 1. Interface names may vary by image.

Lab topologyIllustrative topology
192.0.2.0/30area 0R1Lo0 · 10.255.0.1/32R2Lo0 · 10.255.0.2/32
Solid lines are physical links, configured as point-to-point. Interfaces and areas are listed below. Router symbol: GNS3, GPL-2.0. Original layout.
RouterInterfaceIPv4 addressArea
R1Gi1192.0.2.1/300
R2Gi1192.0.2.2/300

Loopback0 is 10.255.0.<router number>/32; area assignments: R1: area 0, R2: area 0.

Complete baseline configurations

R1

Configuration
configure terminal
hostname R1
router ospf 1
 router-id 10.255.0.1
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.1 255.255.255.255
 ip ospf 1 area 0
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.1 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 0
 no shutdown
 exit
end

R2

Configuration
configure terminal
hostname R2
router ospf 1
 router-id 10.255.0.2
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.2 255.255.255.255
 ip ospf 1 area 0
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.2 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 0
 no shutdown
 exit
end

Apply

Use the pair baseline. Inspect before modifying anything. The following is an isolated fault: make R2 passive on the transit interface, wait for R1’s dead timer to expire, then remove that fault.

R2 · inject fault

Configuration
configure terminal
router ospf 1
 passive-interface GigabitEthernet1
end
Illustrative output · excerpt
R1# show ip ospf neighbor
[No entries; explanatory annotation]
R2# show ip ospf interface GigabitEthernet1
  No Hellos (Passive interface)

An empty neighbor table follows expiry; passive operation prevents neighbor formation.

R2 · repair

Configuration
configure terminal
router ospf 1
 no passive-interface GigabitEthernet1
end

Verify and interpret

Illustrative output · excerpt
R1# show ip ospf neighbor
Neighbor ID     Pri State   Dead Time Address     Interface
10.255.0.2        0 FULL/-  00:00:36  192.0.2.2  GigabitEthernet1

Full confirms restoration. If stuck earlier, use the state table to select evidence rather than repeatedly resetting the process.

Hellos discover and maintain neighbors; DBDs summarize LSAs; LSRs request missing LSAs; LSUs carry LSAs; acknowledgments support reliable flooding. A Hello can pass while larger DBD/LSU packets fail, which is why basic reachability alone is insufficient.

Technical references

OSPFv2 standard · Router configuration guide

Key Takeaways

  • Neighbor state narrows the fault domain.
  • 2-Way can be healthy between broadcast DROTHERs.
  • ExStart and Exchange involve database-description negotiation.
  • Loading means requested LSAs are still outstanding.
  • Validate compatible interface settings and packet delivery before restarting OSPF.

Neighbor states and requirements Quiz

Six questions · four options each · select one answer per question. Submit all answers to see your score and explanations.

1. What does Init suggest?
2. Where can stable 2-Way be normal?
3. What is negotiated in ExStart?
4. Which packet requests a missing LSA?
5. What does Full prove?
6. What repairs the injected transit fault?