OSPF Diagnostic Suite

OSPF full health check: neighbor state matrix, adjacency instability detection, LSA database consistency, stub/NSSA area verification, SPF convergence time analysis, and split-brain detection.

Cisco IOS/XE/XR

Juniper

Arista

Open in Generator Open in Platform

You're viewing a preview

The full script, parameters, and execution console are available with a free account.

Already have access? Sign in →

Capabilities

Neighbor adjacency matrix
LSA database cross-check
DR/BDR election verify
Area type consistency
SPF run frequency analysis
ECMP path count check
MTU mismatch detection

Required inputs

Parameters the script accepts. Defaults shown; some are vendor- or context-gated.

Parameter	Type	Default	Notes
OSPF process ID process_id	number	1	—
Expected areas (CSV) area_list	string	0,10,20	—
Max SPF runs/hour max_spf_runs	number	10	—
Cross-check LSDB check_lsdb	bool	true	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS/XE/XR, Juniper, Arista) so the generated analysis logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for OSPF process ID, Expected areas (CSV), Max SPF runs/hour instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can neighbor adjacency matrix and lSA database cross-check. Ask for the subset relevant to your incident to keep output focused.

Hint 4 — Describe your inventory format

Tell the assistant whether your device list is CSV, YAML, or JSON and which columns it has, so parsing matches your data.

Sample inventory schema

Authoritative shape of the device/policy data this script consumes.

ospf_topology.yaml

yaml

Backbone + 3 areas (standard, NSSA, stub) with auth and SPF throttling

yaml

# OSPFv2/v3 areas across LON1+FRA1 IGP
process: 100
router_id_block: 10.255.0.0/16
areas:

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

OSPF DIAGNOSTIC REPORT — Process 1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

NEIGHBOR MATRIX (12 devices, 34 adjacencies)
  core-rtr-01: 3/3 neighbors FULL ✓
  core-rtr-02: 2/3 neighbors FULL ← 1 in EXSTART state!
  dist-sw-01:  DR on Area 10, 8 neighbors FULL ✓

[HIGH] core-rtr-02 ↔ dist-sw-04: stuck in EXSTART (8 mins)
  Likely cause: MTU mismatch