Verification & Packet Tracer Assembly Guide: PTL-0011

Lab ID: PTL-0011
Lab Title: Single-Area OSPFv2 Configuration and Verification
Category: routing
Difficulty: Intermediate

1. Physical & Packet Tracer Assembly Manifest#

Device Hardware & Module Schedule#

Port-to-Port Cabling Matrix#

Addressing Table#

2. Pre-Configuration & Starter State#

In the starter state (starter):

• Physical topology is fully cabled.
• IP addresses are configured on all router interfaces and hosts.
• Direct router-to-router ping across 10.0.0.0/30 succeeds, but neither router has knowledge of the remote LAN.
• Student must configure OSPF process 10, set explicit 32-bit router-id, advertise networks using wildcard masks in area 0, configure passive-interface on user-facing LAN ports, and verify OSPF adjacency and dynamic route propagation.

Complete reference configurations:

• configs/R1.txt
• configs/R2.txt

3. Positive Verification Tests#

Test POS-01: OSPF Neighbor Adjacency#

• Action: At R1#, issue show ip ospf neighbor.
• Expected Terminal Output:

  R1# show ip ospf neighbor
  Neighbor ID     Pri   State           Dead Time   Address         Interface
  2.2.2.2           1   FULL/BDR        00:00:33    10.0.0.2        GigabitEthernet0/0/1
  

• Criterion: Neighbor ID 2.2.2.2 is in FULL state (FULL/DR or FULL/BDR).

Test POS-02: Dynamic OSPF Route Learning#

• Action: At R1#, issue show ip route ospf.
• Expected Terminal Output:

  R1# show ip route ospf
  O        192.168.2.0/24 [110/2] via 10.0.0.2, 00:05:12, GigabitEthernet0/0/1
  

• Criterion: Remote network 192.168.2.0/24 is installed with code O, administrative distance of 110, metric of 2, via next-hop 10.0.0.2.

Test POS-03: End-to-End Inter-Branch Dynamic Reachability#

• Action: From PC-HQ (192.168.1.10), ping PC-Branch (192.168.2.10).
• Expected Terminal Output:

  C:\> ping 192.168.2.10
  Reply from 192.168.2.10: bytes=32 time<1ms TTL=126
  Reply from 192.168.2.10: bytes=32 time<1ms TTL=126
  Reply from 192.168.2.10: bytes=32 time<1ms TTL=126
  Reply from 192.168.2.10: bytes=32 time<1ms TTL=126
  

• Criterion: 100% packet success across the dynamic OSPF routed backbone.

4. Negative Verification Tests#

Test NEG-01: OSPF Hello / Dead Interval Mismatch#

• Action: On R1, change Hello timer on transit interface: interface Gi0/0/1 -> ip ospf hello-interval 5.
• Expected Behavior:
  • When Dead timer expires (40 seconds), OSPF drops adjacency: %OSPF-5-ADJCHG: Process 10, Nbr 2.2.2.2 on GigabitEthernet0/0/1 from FULL to DOWN, Neighbor Down: Dead timer expired
  • show ip route ospf shows remote routes immediately flushed.
  • Pings between PC-HQ and PC-Branch fail.

Test NEG-02: OSPF Area ID Mismatch#

• Action: On R2, configure network statement with wrong area: network 10.0.0.0 0.0.0.3 area 1.
• Expected Behavior:
  • OSPF neighbor adjacency will not form because routers must share the exact same Area ID on common transit links.

5. Diagnostic & Troubleshooting Reference#