Video summary

Free CCNA | Configuring OSPF (2) | Day 27 Lab | CCNA 200-301 Complete Course

Main summary

Key takeaways

Educational

Main ideas / lessons

  • OSPF can be enabled in two ways, and the lab uses the interface-specific approach:

    • Instead of using the network statement to enable OSPF based on IP ranges, the routers explicitly enable OSPF on selected interfaces.

  • Passive interfaces in OSPF prevent neighbor formation while still allowing OSPF to advertise networks.

    • Using PASSIVE-INTERFACE causes neighbors on that interface to go DOWN immediately.
    • PASSIVE-INTERFACE DEFAULT can be used, but specific interfaces can then be made non-passive with NO PASSIVE-INTERFACE.

  • OSPF cost depends on reference bandwidth and interface bandwidth.

    • The lab changes OSPF behavior by adjusting reference bandwidth so FastEthernet and GigabitEthernet costs change predictably.
    • Interfaces with faster bandwidth than the reference result in lower costs.

  • Packet Tracer may have limitations / quirks with certain OSPF behaviors:

    • The video explains that some expected routes (particularly with OSPF external type 2) may not appear exactly as they would on real equipment or GNS3.

  • Default route advertisement in OSPF is configured using DEFAULT-INFORMATION ORIGINATE, and its presence affects what other routers learn.

  • OSPF Hello message structure is examined in simulation mode:

    • Multicast destination 224.0.0.5 is used for OSPF Hellos.
    • The Hello message fields include version, type, router ID, area, timers, DR/BDR info, and neighbors.
    • OSPF in the IP header uses protocol 89 (shown as hex 0x59).

Methodology / step-by-step instructions (lab steps)

Step 3: Configure OSPF explicitly on interfaces + passive interface behavior

Goal: Enable OSPF on specific router interfaces and configure loopback as passive.

General concept

  • Enable OSPF using:
    • Enter interface-selection scope with INTERFACE RANGE ...
    • Then configure OSPF per-interface with:
      • IP OSPF 1 AREA 0
  • Do not enable OSPF on the G3/0 interface because neighbors do not need to know that transit network (the lab references Day 26 explanation).

Configuration examples

R1

conf t
interface range G0/0, F1/0, L0
ip ospf 1 area 0

R1 passive loopback

router ospf 1
passive-interface L0

R2

conf t
interface range G0/0, F1/0, L0
ip ospf 1 area 0

router ospf 1
passive-interface L0

R3

conf t
interface range F1/0, F2/0, L0
ip ospf 1 area 0

router ospf 1
passive-interface L0

R4

conf t
interface range G0/0, F1/0, F2/0, L0
ip ospf 1 area 0

Test passive-interface behavior

router ospf 1
passive-interface default
  • Observe neighbor changes to DOWN
  • Restore adjacency by exempting interfaces:
no passive-interface F1/0
no passive-interface F2/0

Verification commands

  • show ip protocols
  • show ip ospf neighbor
  • Note: dead time decreases with received Hello messages (Hello every 10s).

Step 4: Set OSPF reference bandwidth so FastEthernet cost becomes 100

Goal: Configure reference bandwidth so that FastEthernet cost = 100.

Command pattern

  • auto-cost reference-bandwidth <value>

Key formula (as explained)

  • OSPF cost = reference bandwidth / interface bandwidth

Find reference bandwidth for FastEthernet cost 100

  • FastEthernet bandwidth assumed default = 100 Mbps
  • Solve: reference / 100 = 100 → reference = 10,000

Implementation

  • On each router (recommended same value everywhere):
    • auto-cost reference-bandwidth 10000
  • Routers configured: R1, R2, R3

Verification

  • show ip ospf interface
  • Confirm FastEthernet1/0 cost is 100
  • Confirm Gigabit cost becomes 10 (per what the lab shows)

Configure and analyze a default route (advertised from R1)

Goal: Make R1 advertise a default route into OSPF.

Enable default information origination

  • In OSPF config mode on R1:
    • default-information originate

Create the actual default route on R1

ip route 0.0.0.0 0.0.0.0 203.0.113.2

Check what R4 learns

  • show ip route

Important note about OSPF external type 2 (Packet Tracer quirk explained)

  • Expected: both paths via R2 and R3 should appear with the same external cost behavior.
  • Packet Tracer may only display one of them until an interface is shut down.
  • The video attributes this to E2 (OSPF external type 2) behavior:
    • External type 2 ignores internal metric to reach the advertising router, so cost can appear the same across paths.

Demonstration (forcing route change)

On R4:

interface F1/0
shutdown
  • Wait for neighbor state update
  • Re-check:
    • show ip route
  • Result: route via the other neighbor appears (and still shows cost 1 in the lab behavior)

OSPF Hello message field inspection (simulation)

Goal: Observe OSPF Hello internals.

Observe packet details

  • Look at IP destination: 224.0.0.5
  • Open PDU Details to view:
    • Ethernet frame → IP packet → OSPF Hello

Highlighted OSPF Hello fields

  • Version number: 2
  • Type: 1 (Hello)
  • Router ID: shown
  • Area ID: 0.0.0.0 (Area 0)
  • Network mask and timers: Hello 10s / Dead 40s
  • DR/BDR addresses and neighbor address

IP protocol field check

  • IP protocol shown as hex 0x59
  • 0x59 = decimal 89, consistent with OSPF in the IP header

Boson NetSim lab preview (CCNA OSPF troubleshooting scenario)

Scenario summary

  • A new router “Key West” is added.
  • You must configure OSPF on Key West and troubleshoot OSPF issues elsewhere.
  • The preview focuses on Task 1 and includes several sub-steps (A through D).

Task 1: Config + troubleshooting steps (preview)

Step A (Part 1): Log in and check routing behavior

  • Log into Key West:
    • Username/password prompt indicates password is cisco
    • Use enable, then enable password is also cisco
  • Check routing table:
    • show ip route
  • Conclusion:
    • OSPF seems running but no OSPF routes from neighbors are being learned.

Step A (Part B): Examine configuration

  • Show current running config:
    • show running-config
  • Findings:
    • router ospf 1 exists
    • Includes a network statement, but likely incorrect.

Step A (Part C): Determine what prevents OSPF from detecting other networks

  • Confirm OSPF is running:
    • show ip protocols
  • Identify problem with the network statement:
    • Example issue described: wildcard mask is too specific (e.g., /32 only matching a single address not present on Key West interfaces).
  • Verify interfaces:
    • show ip interface brief
  • Conclusion:
    • The configured network statement does not match any interface IPs → OSPF not activated on required interfaces.

Step A (Part C/D): Fix configuration and verify

  • Plan to correct:

    • Update network statement to match the proper interface subnet (example used):
      • Change wildcard mask to correspond to a /24 match:
        • network 200.120.45.0 0.0.0.255 area 0 (wildcard shown as /24)

  • Implementation (routed config steps described):

    • Enter OSPF config:
      • conf t
      • router ospf 1
    • Remove incorrect network command
    • Add corrected network statement:
      • network 200.120.45.0 0.0.0.255 area 0

  • Verification

    • end
    • show ip route (wait for routing table updates)
    • Check neighbors once adjacency forms:
      • show ip ospf neighbor
  • Result in preview:
    • Neighbor adjacency forms with Miami (neighbor address shown ending in .246)

Speakers / sources featured (as present in subtitles)

  • Jeremy’s IT Lab (host/instructor) — Jeremy
  • Boson (product reference: Boson NetSim for CCNA, including guided labs)
  • Packet Tracer (simulation tool mentioned)
  • GNS3 (mentioned as an alternative where behavior should match real equipment)

Original video