First, the essential ideas
- OSPFv2
- Open Shortest Path First version 2 is a link-state routing protocol used here to learn IPv4 routes within one administrative routing domain.
- Area and area 0
- An area is an OSPF topology database scope. Area 0 is the backbone; this beginner exercise uses only area 0 and has no area-border router.
- Router ID
- A unique 32-bit OSPF identity displayed in dotted-decimal form. It is not necessarily an assigned interface address or a reachable ping target.
- Process ID
- A Cisco local number selecting an OSPF process on one router. Neighboring routers can use different process numbers.
- Hello and dead timers
- Hellos discover and maintain neighbors. The dead interval bounds how long the local router waits without an accepted Hello before declaring that neighbor lost.
- Neighbor and adjacency
- A neighbor is discovered through OSPF communication. An adjacency is a selected neighbor relationship that synchronizes topology information; Full indicates completed synchronization.
- LSA, LSDB and SPF
- A link-state advertisement describes topology information; the link-state database stores it. Shortest Path First calculates routes from that database using OSPF costs.
- Passive interface
- An OSPF interface that does not form neighbor relationships by sending Hellos. Its enabled connected prefix can still be advertised through other active adjacencies.
- Point-to-point network type
- An OSPF interface setting for a link with two routers. It forms a full adjacency without a designated-router election; the underlying medium can still be Ethernet.
Separate identity, scope and local bookkeeping. R1's process 10 and R2's process 20 can participate in the same area 0 while identifying themselves as 1.1.1.1 and 2.2.2.2. None of these labels replaces the transit addresses used to deliver packets.
See the idea
A neighbor is only the first proof
The transit adjacency must produce a remote loopback route and a complete endpoint exchange.
Form the adjacency
Both Gi0/0 interfaces use area 0 and point-to-point OSPF, despite different local process IDs.
What this model leaves out: One direct Ethernet cable and two logical loopback attachments. Router IDs are identities, not traffic endpoints. No DR election or captured packets are claimed.
Full visual explanation and references
R1 and R2 share a point-to-point area 0 transit. Their two router-owned loopbacks are the source and destination of the verification exchange.
One direct Ethernet cable and two logical loopback attachments. Router IDs are identities, not traffic endpoints. No DR election or captured packets are claimed.
- Form the adjacency
Both Gi0/0 interfaces use area 0 and point-to-point OSPF, despite different local process IDs.
www.cisco.com - Learn the endpoint
R1 must learn 203.0.113.34/32; seeing neighbor 2.2.2.2 alone is insufficient.
www.rfc-editor.org - Test request and reply
The fixed-source exchange reaches R2's loopback and needs R2's route back to R1's loopback.
www.cisco.com
One idea at a time
Start with something familiar.
Make three columns: process number, router ID and area. Fill R1 with 10,1.1.1.1,0 and R2 with 20,2.2.2.2,0. Put their transit IP addresses in a separate fourth column.
Why learn this?
Treating every number as a value that must match leads to unnecessary changes. Unique identities prevent confusion; shared link parameters let the actual neighboring interfaces communicate.
An everyday comparison
Two librarians can keep different internal catalog numbers while agreeing on a shared collection and using distinct names when exchanging updates.
What happens in a network
The local catalog numbers resemble process IDs, the names resemble router IDs, and the shared collection resembles the area's topology information.
Where the comparison stopsOSPF does not copy an entire forwarding table like a book list. It exchanges topology information and each router independently calculates its own routes.
Follow one worked example
- Create explicit identities first.
Each fresh process gets a unique router ID before any interface is enabled for OSPF.
Why: This avoids relying on automatic selection or disrupting an established process to change its identity.
- Enable only the intended interfaces.
The transit forms the adjacency and the passive loopback contributes a prefix.
Why: A passive endpoint still has useful advertised reachability without looking for neighbors.
- Verify three layers of evidence.
Inspect Full state, the OSPF route and the fixed-source ping separately.
Why: Database synchronization is not the same claim as successful final delivery.
Your first small task
Predict whether process 10 on R1 can become adjacent to process 20 on R2 when both transit interfaces use area 0 and compatible point-to-point settings.
Show a hint
Ask whether a value is local bookkeeping, shared link configuration or unique protocol identity.
Check the expected result
Yes. The local process IDs may differ; the router IDs must be unique and the neighbor-facing area and relevant parameters must agree.
Pause and explain it in your own words
Does router-id 2.2.2.2 make that address pingable?
Show a hint
The command sets an identity, not an interface address.
Show the explanation
No. Router ID is a 32-bit protocol identifier. A ping requires an actual assigned destination and valid forwarding; this lab instead tests R2 Loopback0 at 203.0.113.34.
Short answer
What should you understand today?
OSPFv2 discovers compatible IPv4 neighbors, synchronizes topology information and calculates routes. Use unique router IDs and matching area and interface parameters; local process IDs need not match. A Full neighbor is useful evidence, but verify the learned destination route and an end-to-end exchange before declaring the intended network reachable.
Before you begin
Learning targets
- Understand connected versus remote prefixes and source-qualified IPv4 ping.
- Use a fresh two-node CML 2.10 IOSv 15.9M project, with no static defaults masking OSPF failures.
- Map R1 Gi0/0 directly to R2 Gi0/0 and keep console access independent of the link.
- Distinguish local process ID, router ID and area ID.
- Configure single-area OSPFv2 on an explicit point-to-point link.
- Interpret basic neighbor states without equating them with application health.
- Verify learned loopback routes in both directions.
- Diagnose and reverse one passive-transit mistake.
Words you will meet
Open a word when you need its meaning. You do not need to memorize the whole list before reading.
OSPFv2
Open Shortest Path First version 2 is a link-state routing protocol used here to learn IPv4 routes within one administrative routing domain.
Area and area 0
An area is an OSPF topology database scope. Area 0 is the backbone; this beginner exercise uses only area 0 and has no area-border router.
Router ID
A unique 32-bit OSPF identity displayed in dotted-decimal form. It is not necessarily an assigned interface address or a reachable ping target.
Process ID
A Cisco local number selecting an OSPF process on one router. Neighboring routers can use different process numbers.
Hello and dead timers
Hellos discover and maintain neighbors. The dead interval bounds how long the local router waits without an accepted Hello before declaring that neighbor lost.
Neighbor and adjacency
A neighbor is discovered through OSPF communication. An adjacency is a selected neighbor relationship that synchronizes topology information; Full indicates completed synchronization.
LSA, LSDB and SPF
A link-state advertisement describes topology information; the link-state database stores it. Shortest Path First calculates routes from that database using OSPF costs.
Passive interface
An OSPF interface that does not form neighbor relationships by sending Hellos. Its enabled connected prefix can still be advertised through other active adjacencies.
Point-to-point network type
An OSPF interface setting for a link with two routers. It forms a full adjacency without a designated-router election; the underlying medium can still be Ethernet.
OSPF learns topology before calculating routes
OSPF is a link-state protocol: routers exchange descriptions of their local links and prefixes so each can calculate paths. A neighbor table, topology database and routing table answer different questions. Seeing a remote router ID in one output does not establish that every intended prefix was enabled, that a better route did not override OSPF, or that a final host answered.
- Inspect the remote prefix, not just any successful ping.
- An area 0-only lab requires no area-border or redistribution configuration.
Choose the router ID before enabling the links
An explicit router-id command removes ambiguity. Without it, traditional IOS selection prefers the highest eligible loopback IPv4 address, then an eligible interface address when the process starts. The selected value does not continuously follow whichever address later becomes highest. Changing an established identity can require process restart and disrupt adjacencies, so this lesson sets it on fresh processes and does not issue a broad clear command.
- Router IDs must be unique within the relevant OSPF domain.
- A router ID is neither automatically a gateway nor an assigned host address.
Know what a neighbor state actually says
Down means no recent accepted conversation; Init means a Hello was seen without confirmed two-way recognition. Two-Way means both sides recognize each other. ExStart and Exchange negotiate and exchange database summaries; Loading requests missing information; Full indicates synchronization is complete. Some transitions are too brief to observe in manual polling. On our point-to-point link, expect Full with no DR/BDR role. On broadcast segments, Two-Way can be normal between two non-designated routers.
- Full is a control-plane result, not an application health certificate.
- Do not require every transient state to appear in a captured manual transcript.
Enable the correct interface in the correct area
The interface command ip ospf process-id area 0 makes membership explicit. The older router-process network command selects local interfaces by address and wildcard; it does not create a route to an arbitrary remote network. On this two-router Ethernet cable, both ends deliberately use point-to-point OSPF type. Compare area, timers, network type, addressing and authentication policy when diagnosing a neighbor. No authentication is configured in this isolated exercise.
- Passive is suitable for this loopback, not the required neighbor-facing transit.
- OSPF network type is configured separately from the physical cable type.
Diagnose the intended fault without masking it
The controlled change makes R1's transit passive after a working baseline. After neighbor expiry and recalculation, the remote loopback route should disappear and its fixed-source exchange should fail. The connected transit can remain reachable. Restore only the passive setting, allow adjacency to reform, and repeat neighbor, route and traffic checks. Adding a static default would obscure the OSPF dependency instead of repairing it.
- Do not infer precise convergence time from a default timer or a simulation.
- Keep predictions distinct from actual terminal output and independent review.
Real-world walkthrough
The cable answered, but the routing conversation stopped
A hypothetical learner makes all interfaces passive to reduce unwanted OSPF Hellos. The intended transit is included accidentally. The connected neighbor still answers ping, yet remote loopbacks disappear because the only OSPF adjacency is lost.
- Confirm the cable and connected subnet remain usable.
- Inspect OSPF interface membership and passive settings on the actual transit.
- Check neighbor state and the missing remote loopback rather than adding a static workaround.
- Remove the transit from the passive list while keeping Loopback0 passive.
- Wait for Full and repeat the original loopback-source test.
Guided GNS3 lab
One area, two process numbers and a passive fault
Build a complete OSPFv2 point-to-point exchange between two named loopbacks, remove only the Hello capability on one transit, and restore it. No router output or runtime is claimed by the authored lesson.
Addressing plan
| Device | Interface | Address | Purpose |
|---|---|---|---|
| R1 | Gi0/0 | 192.0.2.1/30 | Point-to-point OSPF area 0 transit |
| R2 | Gi0/0 | 192.0.2.2/30 | Opposite transit endpoint |
| R1 | Loopback0 | 198.51.100.34/32 | Source, not router ID |
| R2 | Loopback0 | 203.0.113.34/32 | Destination, not router ID |
Set up the lab
- Use Cisco Modeling Labs 2.10 with its legally entitled bundled IOSv 15.9M reference image. Record the complete show version release; do not export that image to GNS3. No paid API is involved.
- Create fresh nodes and only the listed links. No External Connector, NAT node, bridge, public uplink or production network is permitted. Leave console access independent of the test data links.
- IOSv examples use GigabitEthernet0/0 and GigabitEthernet0/1. Confirm those exact ports in the workbench and show ip interface brief before configuring; if your image differs, document an explicit port substitution first.
- Decline the initial configuration dialog on a new authorized node, press Enter to reach the prompt, then use enable. Do not bypass unknown credentials. All displayed expected results are predictions, not author runtime.
- Without an entitled compatible image, complete the address and route-selection worksheet only. Mark command execution, packet forwarding and recovery unmeasured.
Address R1's two interfaces
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Record show version and confirm the cable before creating transit and loopback addresses.
enable
configure terminal
interface GigabitEthernet0/0
ip address 192.0.2.1 255.255.255.252
no shutdown
exit
interface Loopback0
ip address 198.51.100.34 255.255.255.255
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
interface GigabitEthernet0/0- Select the declared transit interface.
ip address 192.0.2.1 255.255.255.252- Assign this endpoint of the transit /30.
no shutdown- Enable the Ethernet transit.
exit- Return to global configuration.
interface Loopback0- Create the explicit software traffic endpoint.
ip address 198.51.100.34 255.255.255.255- Assign the endpoint as a /32 host address.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- R1 owns the declared transit and source addresses.
- Why this step matters
- The loopback makes remote-route and reverse-route tests independent of connected transit reachability.
Address R2's two interfaces
In the isolated CML workbench, select R2, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Record show version and use the opposite /30 address and distinct /32 endpoint.
enable
configure terminal
interface GigabitEthernet0/0
ip address 192.0.2.2 255.255.255.252
no shutdown
exit
interface Loopback0
ip address 203.0.113.34 255.255.255.255
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
interface GigabitEthernet0/0- Select the declared transit interface.
ip address 192.0.2.2 255.255.255.252- Assign this endpoint of the transit /30.
no shutdown- Enable the Ethernet transit.
exit- Return to global configuration.
interface Loopback0- Create the explicit software traffic endpoint.
ip address 203.0.113.34 255.255.255.255- Assign the endpoint as a /32 host address.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- Both endpoints and the direct transit should exist.
- Why this step matters
- No static route is installed to mask the later OSPF fault.
Set R1's local process and identity
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Use the fresh process 10 and set its identity before enabling adjacency-capable interfaces.
enable
configure terminal
router ospf 10
router-id 1.1.1.1
passive-interface Loopback0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
router ospf 10- Create the locally significant OSPFv2 process.
router-id 1.1.1.1- Choose this unique 32-bit protocol identity before forming neighbors.
passive-interface Loopback0- Advertise the loopback without seeking neighbors on it.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- R1 has an explicit unique router ID and passive Loopback0.
- Why this step matters
- Choosing an ID before startup avoids an unnecessary disruptive process restart.
Set R2's different local process
In the isolated CML workbench, select R2, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Use local process 20 intentionally; do not change it to match R1.
enable
configure terminal
router ospf 20
router-id 2.2.2.2
passive-interface Loopback0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
router ospf 20- Create the locally significant OSPFv2 process.
router-id 2.2.2.2- Choose this unique 32-bit protocol identity before forming neighbors.
passive-interface Loopback0- Advertise the loopback without seeking neighbors on it.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- R2 has its own unique ID and independent local process number.
- Why this step matters
- This demonstrates that the process number is local bookkeeping.
Enable R1's area 0 interfaces
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Apply point-to-point semantics on the two-router cable and advertise the passive loopback.
enable
configure terminal
interface GigabitEthernet0/0
ip ospf network point-to-point
ip ospf 10 area 0
exit
interface Loopback0
ip ospf 10 area 0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
interface GigabitEthernet0/0- Select the sole transit to the other router.
ip ospf network point-to-point- Use OSPF point-to-point semantics on this two-router Ethernet link.
ip ospf 10 area 0- Enable this interface in the local process and backbone area.
exit- Return to global configuration.
interface Loopback0- Select the local software endpoint.
ip ospf 10 area 0- Advertise this endpoint into the same area.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- R1 is ready to exchange Hellos on Gi0/0 only.
- Why this step matters
- A protocol-enabled loopback can advertise its address without forming a neighbor.
Enable R2's matching area and type
In the isolated CML workbench, select R2, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Use R2's local process 20 while matching area 0 and point-to-point type.
enable
configure terminal
interface GigabitEthernet0/0
ip ospf network point-to-point
ip ospf 20 area 0
exit
interface Loopback0
ip ospf 20 area 0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
interface GigabitEthernet0/0- Select the sole transit to the other router.
ip ospf network point-to-point- Use OSPF point-to-point semantics on this two-router Ethernet link.
ip ospf 20 area 0- Enable this interface in the local process and backbone area.
exit- Return to global configuration.
interface Loopback0- Select the local software endpoint.
ip ospf 20 area 0- Advertise this endpoint into the same area.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- The pair should progress to Full once compatible Hellos and database exchange complete.
- Why this step matters
- Area and network parameters matter across the link even though process IDs differ.
Verify R1's control and data baseline
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Do not introduce the fault until the remote route and fixed-source probe succeed.
enable
show ip ospf interface GigabitEthernet0/0
show ip ospf neighbor
show ip route 203.0.113.34
ping 203.0.113.34 source 198.51.100.34What each command means
enable- Enter authorized privileged EXEC mode to inspect this named router.
show ip ospf interface GigabitEthernet0/0- Inspect area, point-to-point type, router ID and timers.
show ip ospf neighbor- Expect neighbor 2.2.2.2 in Full state without a DR role.
show ip route 203.0.113.34- Verify an OSPF route to the remote /32.
ping 203.0.113.34 source 198.51.100.34- Test the remote endpoint and its return route.
- What you should see
- Expect Full adjacency, the remote OSPF /32 and replies.
- Why this step matters
- Three separate checks prevent neighbor state being mistaken for complete reachability.
Check the reverse baseline
In the isolated CML workbench, select R2, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Confirm R2 sees R1's identity and learns the opposite endpoint.
enable
show ip ospf neighbor
show ip route 198.51.100.34
ping 198.51.100.34 source 203.0.113.34What each command means
enable- Enter authorized privileged EXEC mode to inspect this named router.
show ip ospf neighbor- Expect neighbor 1.1.1.1 despite the different local process ID.
show ip route 198.51.100.34- Check the OSPF-learned source endpoint.
ping 198.51.100.34 source 203.0.113.34- Verify the original exchange in the opposite direction.
- What you should see
- Expect the reverse /32 and successful replies.
- Why this step matters
- The return direction has its own route lookup and must be checked.
Make only R1's transit passive
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Preserve the working configuration and deliberately suppress the sole neighbor-facing interface.
enable
configure terminal
router ospf 10
passive-interface GigabitEthernet0/0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
router ospf 10- Enter R1's actual local OSPF process.
passive-interface GigabitEthernet0/0- Stop OSPF neighbor formation on the transit without disabling IP.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- The adjacency should be lost; R2 may wait for its dead timer.
- Why this step matters
- This creates a controlled protocol fault while leaving the physical and IP link present.
Contrast connected and remote reachability
In the isolated CML workbench, select R2, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Wait beyond the displayed dead interval and record actual state without inventing elapsed-time precision.
enable
ping 192.0.2.1
show ip ospf neighbor
show ip route 198.51.100.34
ping 198.51.100.34 source 203.0.113.34What each command means
enable- Enter authorized privileged EXEC mode to inspect this named router.
ping 192.0.2.1- Check connected transit reachability independent of OSPF.
show ip ospf neighbor- Inspect the lost adjacency after expiry.
show ip route 198.51.100.34- Look for withdrawal of the remote OSPF /32.
ping 198.51.100.34 source 203.0.113.34- Repeat the remote test whose route dependency was removed.
- What you should see
- Expect connected ping to remain usable while the remote OSPF exchange fails.
- Why this step matters
- This separates link reachability from dynamic-route availability.
Restore the neighbor-facing transit
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Reverse only the accidental passive setting; keep Loopback0 passive.
enable
configure terminal
router ospf 10
no passive-interface GigabitEthernet0/0
endWhat each command means
enable- Enter authorized privileged EXEC mode; this does not change the network configuration.
configure terminal- Enter global configuration mode on this named router; accepted changes affect its running state.
router ospf 10- Select the same local process that owns the transit.
no passive-interface GigabitEthernet0/0- Restore Hellos and adjacency formation on the transit.
end- Return to privileged EXEC; this neither saves nor reverses accepted configuration changes.
- What you should see
- The pair should reform Full adjacency after exchange.
- Why this step matters
- No reload, broad clear or static-route workaround is required for this planned fault.
Retest the original endpoint exchange
In the isolated CML workbench, select R1, open its Console tab and connect before typing. Start at > or #; use end first if a prior task left configuration mode. Wait for synchronization and compare the same three checks with baseline.
enable
show ip ospf neighbor
show ip route 203.0.113.34
ping 203.0.113.34 source 198.51.100.34What each command means
enable- Enter authorized privileged EXEC mode to inspect this named router.
show ip ospf neighbor- Verify neighbor 2.2.2.2 returns to Full.
show ip route 203.0.113.34- Verify the remote OSPF /32 returns.
ping 203.0.113.34 source 198.51.100.34- Repeat the original source-qualified traffic test.
- What you should see
- Expect recovery; preserve any discrepancy for diagnosis.
- Why this step matters
- A successful rollback requires the original behavior, not just removal of one command.
Verify
- Distinguish process 10/20, router IDs 1.1.1.1/2.2.2.2 and shared area 0.
- Confirm point-to-point type and Full state without DR/BDR election.
- Show learned remote /32s rather than only connected transit routes.
- Retain baseline, passive fault and matching restoration observations.
Troubleshoot
- If no neighbor appears, compare passive status, enabled interface, area, timers and actual cable addressing before clearing the process.
- If exchange stalls, inspect unique IDs, MTU and packet delivery; do not blindly disable MTU checks.
- If Full appears but a loopback route is missing, verify that loopback's OSPF membership and any competing route.
GNS3 does not provide Cisco images. Use software only when the applicable license or entitlement permits that environment. Do not share or redistribute image files. Cisco Modeling Labs is the official alternative; its reference images are licensed for use within CML unless separately licensed. A paper exercise needs no image, but does not establish hands-on competence. Virtual routers do not reproduce physical radios, PoE delivery, hardware forwarding rates or failover timing.
- Restore the transit to nonpassive and leave the loopback passive on both routers.
- Keep actual outputs private and stop the isolated lab; no startup-save or performance claim is required.
Practice set
Answer before you reveal
01Must OSPF process numbers match across the cable?
R1 uses 10 and R2 uses 20 in this working design. Shared area and compatible neighbor-facing parameters are different requirements.
02Must router IDs match?
Duplicate router IDs can corrupt the intended topology identity. They are not shared area labels or default gateways.
03What does Full establish?
It does not prove every prefix is advertised or every destination application works. Route and traffic checks remain necessary.
04Why leave Loopback0 passive?
No second router is attached to that loopback. Passive prevents unnecessary Hello behavior without removing its OSPF-enabled prefix.
05Why can the transit ping survive the fault?
The fault changes Hello participation, not the Ethernet address. Remote loopbacks depend on learned routes and expose the difference.
06Why avoid a process reset to repair this fault?
A broad reset adds disruption and obscures attribution. The configured router IDs are already correct and need no restart.
Knowledge check
Quiz: prove the reasoning
Keep these
Technical takeaways
- OSPF exchanges topology information before calculating routes.
- Router IDs are unique identities; process IDs are local numbers.
- Area and compatible interface parameters matter to neighbors.
- Full does not replace a destination-route or traffic check.
- Passive endpoints differ from passive neighbor-facing transits.
- Restore the exact fault and preserve runtime uncertainty.