Skip to content
All free lab files

OSPF Neighbor Down: Area Mismatch

Two routers share a working /30 link, but their OSPF adjacency never forms. Work up from Layer 3 to find out why.

The lab as it opens in PNETLab: R1 and R2 on a point-to-point link, with the symptom, objectives and checklist on the canvas.

What you'll practise

  • Bring up a point-to-point OSPF adjacency between two routers
  • Read show ip ospf neighbor and show ip ospf interface
  • Recognize an OSPF area mismatch from a console log message
  • Correct a mismatched area on an OSPF network statement
  • Verify adjacency and OSPF-learned loopback reachability

Set it up

  1. 1

    Have the node image ready

    Images are not included. The file expects your own licensed copy of:

    • L3-ADVENTERPRISEK9-M-15.4-2T.bin

    If your copy has a different name, open each node's Edit dialog after importing and pick your image from the list.

  2. 2

    Copy it to the server and fix permissions

    Replace <your-server> with the IP address or hostname of your EVE-NG or PNETLab server.

    $ scp ospf-neighbor-area-mismatch-lab.unl root@<your-server>:/opt/unetlab/labs/
    # then, logged in to the server:
    $ /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
  3. 3

    Open it and start the nodes

    The canvas notes list the objectives, and the workbook walks through the fix.

Inside the lab

Real console output captured live: the adjacency drops the instant the area changes, and IOS names the exact fault, a mismatched area ID, in the same breath.
After the fix: a real FULL/BDR adjacency on Ethernet1/0, captured live from the router's own console.

Free to use and share under CC BY 4.0. Please credit LabFabric with a link to this page.