How to Verify OSPF Configuration and Neighbors on Junos

Table of contents

• Check OSPF-enabled interfaces
• Read the interface output
• Check immediate OSPF neighbors
• Read the neighbor output
• Verification checklist

To verify OSPF status on Junos, use two checks in sequence. Start with show ospf interface to see which interfaces have OSPF enabled and to review interface-level details. Then use show ospf neighbor to view the current state of OSPF neighbors and inspect the listed immediate adjacencies.

This workflow focuses on verification. It identifies the interfaces listed by the OSPF process, shows the interface and neighbor fields available in the command output, and explains how to interpret the displayed states. It does not cover initial OSPF configuration or broader route-control design.

Check OSPF-enabled interfaces

From the CLI, enter:

show ospf interface

Use this output to verify that each interface on which OSPF is enabled is listed. The command provides the interface-level view: it shows the interfaces configured for OSPF and the status information associated with each listed interface.

The interface output can include entries such as at-5/1/0.0, ge-2/3/0.0, lo0.0, so-0/0/0.0, and so-6/0/1.0. It can also show different interface states, including PtToPt, DR, and Down, together with area, DR ID, BDR ID, and neighbor-count columns.

The first check is therefore a coverage check: compare the interfaces you expect to inspect with the interfaces listed by show ospf interface. The direct result is whether an interface appears in the OSPF interface output. Keep this check separate from initial configuration and from broader design assessment.

Read the interface output

Review the fields in the interface output together rather than treating the interface name as the only result. The output uses these columns:

• Intf: the listed interface.
• State: the interface state shown by the command.
• Area: the area for which the interface was configured.
• DR ID: the IP address of the OSPF network's designated router.
• BDR ID: the backup designated-router field shown in the output.
• Nbrs: the number of neighbors shown for the interface.

The Area value identifies the area for which each interface was configured. The DR ID field shows the IP address of the OSPF network's designated router. The BDR ID and neighbor-count columns add more interface-level context, so include those values in the review when they are displayed.

Pay attention to the state value. PtToPt indicates a point-to-point connection. A Down state indicates a problem, so treat it as an indication that requires further investigation rather than as a diagnosis of the cause.

A Waiting state also requires care. If an interface reports Waiting, check the output again after several seconds before drawing a conclusion from that state. Do not make a final determination from the first Waiting result alone.

The interface check answers two separate questions. First, is the interface listed in the OSPF interface output? Second, what state, area, DR ID, BDR ID, and neighbor count are shown for that interface? Keeping those questions separate prevents an interface listing from being confused with a neighbor-state result.

Check immediate OSPF neighbors

After reviewing the interface output, enter:

show ospf neighbor

This command shows the current state of OSPF neighbors. OSPF neighbors are interfaces that have an immediate adjacency, so use this command to inspect the immediate adjacencies currently shown by Junos.

The neighbor output represents active OSPF neighbors. It does not list neighbors that are missing. Therefore, an interface or neighbor that does not appear in this output is not, by itself, proof that the neighbor definitively does not exist. The narrower conclusion is that the output shows the active neighbors included in the current result.

Use the neighbor command after the interface check because the two commands answer different verification questions. show ospf interface identifies the interfaces listed as OSPF-enabled and presents interface-level fields. show ospf neighbor presents the current OSPF neighbor state and the immediate adjacencies listed in that result.

Read the neighbor output

Review each listed neighbor using the columns shown in the output:

• Address: the neighbor address.
• Intf: the interface associated with the neighbor.
• State: the neighbor state.
• ID: the neighbor router ID.
• Pri: the neighbor priority.
• Dead: the number of seconds allowed for inactivity, or dead time.

Neighbor output can include addresses such as 192.168.254.225, interfaces such as fxp3.0, states including 2Way and Full, router IDs, priority values of 128, and dead-time values. These values illustrate the fields to inspect; they do not change the purpose of the command.

The verification check expects each neighbor to show Full under State. Compare the state shown for each listed neighbor with that check. Also record the address, associated interface, router ID, priority, and dead time so the result includes the complete neighbor information exposed by the command rather than only the state.

A neighbor row with a state other than the described Full state should be treated as a result requiring attention. The output identifies the state and the fields to check, but it does not by itself provide a diagnosis for every alternate state. Do not assign a cause beyond what the displayed information establishes.

Verification checklist

Use the following sequence when checking OSPF on Junos:

1. Enter show ospf interface from the CLI.
2. Confirm that each interface on which OSPF is enabled is listed.
3. For each listed interface, check the interface name, state, area, DR ID, BDR ID, and neighbor count.
4. Interpret PtToPt as a point-to-point state.
5. If the state is Waiting, check the output again after several seconds.
6. Treat Down as an indication of a problem without assigning a cause from the state alone.
7. Enter show ospf neighbor to view the current OSPF neighbor state.
8. Check the listed neighbor address, interface, state, router ID, priority, and dead time.
9. Use the Full state as the neighbor verification check.
10. Remember that the neighbor output shows active neighbors and does not list missing neighbors.

This sequence keeps interface verification and immediate-neighbor verification distinct. It also preserves the limits of the output: a listed interface confirms what the interface command displays, a listed neighbor reflects the active-neighbor view, Waiting should be checked again after several seconds, and Down indicates a problem without establishing its cause.