ospf-analysis

Diagnose OSPF adjacency, LSDB integrity, and SPF convergence across multi-vendor networks.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill ospf-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ospf-analysis
Source: https://github.com/vahagn-madatyan/netsec-skills-suite/tree/main/skills/ospf-analysis
Command: npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill ospf-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses OSPF adjacency, LSDB integrity, and SPF convergence across Cisco IOS-XE, JunOS, and EOS.

Core Features & Use Cases

  • Multi-vendor OSPF diagnostics: adjacency FSM analysis, area topology validation, and LSDB checks.
  • Convergence troubleshooting: identify slow SPF and misconfigurations causing non-Full adjacencies.
  • Automated reporting: produces a structured OSPF ANALYSIS REPORT with actionable remediation guidance.

Quick Start

Provide live device outputs (or logs) from your OSPF domain and ask the skill to generate an OSPF analysis report.

Frequently Asked Questions about ospf-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot OSPF adjacency issues across multiple vendors?

OSPF adjacency troubleshooting across multiple vendors involves analyzing adjacency FSMs and LSDB contents from Cisco IOS-XE, JunOS, and EOS outputs to identify non-Full neighbors and misconfigurations causing routing failures.

What causes slow OSPF convergence in a multi-vendor network?

Slow OSPF convergence is typically caused by area design issues, LSDB inconsistencies, and SPF metric misconfigurations across multi-vendor deployments, which can be identified by analyzing SPF metrics and LSDB integrity.

How do I validate OSPF LSDB integrity and area topology?

Validating OSPF LSDB integrity and area topology requires reading device outputs to check LSDB contents for inconsistencies and verifying area design across your multi-vendor OSPF domain to ensure proper route propagation.

Does this OSPF analysis approach work with both Cisco IOS-XE and JunOS?

Yes, this OSPF analysis approach works with Cisco IOS-XE, JunOS, and EOS. It uses read-only SSH access to retrieve device outputs and diagnose multi-vendor OSPF deployments for adjacency and convergence issues.

What is the best way to diagnose non-Full OSPF neighbors?

The best way to diagnose non-Full OSPF neighbors is to analyze adjacency FSM states and LSDB contents across your network devices to pinpoint misconfigurations or inconsistencies preventing full adjacency formation.