isis-analysis

Diagnose IS-IS adjacency health and LSPDB integrity across multi-vendor devices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

IS-IS adjacency formation, LSP flooding, and inter-level routing can be opaque in multi-vendor networks. This skill provides a structured, protocol-first approach to analyzing adjacency states, LSPDB integrity, and level topology across Cisco IOS-XE, Juniper JunOS, and Arista EOS devices.

Core Features & Use Cases

  • Adjacency and DIS election diagnostics across Cisco, JunOS, and EOS platforms to surface state, area mismatches, and DIS status.
  • LSPDB health checks including lifetime, sequence numbers, purges, and overload (OL) flags, with cross-neighbor comparisons.
  • NET address validation, area boundary behavior, and route-leaking verification for IS-IS in L1/L2 networks.
  • Use Case: When IS-IS adjacencies are not forming or LSP floods are inconsistent, run the analysis and generate an IS-IS ANALYSIS REPORT.

Quick Start

Run the IS-IS analysis on the target device and review the generated report.

Frequently Asked Questions about isis-analysis

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

FAQPage Schema
How do I diagnose IS-IS adjacency issues across multi-vendor networks?

Diagnosing IS-IS adjacency issues involves validating area mismatches and DIS election outcomes across Cisco IOS-XE, Juniper JunOS, and Arista EOS devices using protocol-first command checks to surface state inconsistencies.

What is the best way to check LSPDB integrity and sequence numbers in IS-IS?

Checking LSPDB integrity involves analyzing LSP counts, lifetimes, sequence numbers, and overload flags, then performing cross-neighbor comparisons to detect inconsistent LSP flooding or unexpected purges.

Can I verify route-leaking and inter-level routing behavior for IS-IS L1/L2 networks?

Yes, you can verify route-leaking and inter-level routing behavior for IS-IS L1/L2 networks by validating NET addresses, checking area boundary behavior, and evaluating ATT bit status to ensure proper inter-level topology alignment.

Does this IS-IS analysis work with Cisco, JunOS, and EOS platforms?

Yes, this IS-IS analysis works with Cisco IOS-XE, Juniper JunOS, and Arista EOS platforms, implementing vendor-specific command checks to normalize adjacency and LSPDB health reporting across different device operating systems.

Why is my IS-IS adjacency not forming despite correct interface configurations?

IS-IS adjacency not forming can result from NET address anomalies, area mismatches, or inter-level routing behavior inconsistencies, which a structured protocol-first analysis identifies by validating area boundaries and DIS election states.