Topology: A Live Map You Can Diff, Diagram, and Reason About
Parse configs, ingest LLDP, render a force-directed graph or Mermaid diagram, and diff topologies across time — the network as a data structure.
Topologies are usually drawn in Visio, never updated, and quietly disagreed with by the network itself. The Topology module replaces that with a graph derived from real device data — config parsing, neighbor tables, optional manual annotations — that can be diffed, exported, and overlaid with operational findings.
Where topology data comes from
The parser ingests configs and LLDP-style neighbor data, normalises devices and links into a typed graph, and stores the result. You can supplement parsed data with manual edges for things the platform cannot see — circuits, cross-connects, planned cabling.
Two views, one model
The force-directed view is the explorer. Drag, zoom, group by site or role, and click any node for its inventory record and recent findings. The Mermaid view is the report. Generate a diagram you can paste into a doc, a wiki, or a code review.
Topology diffs
The diff panel compares two topology snapshots and renders the delta: added or removed devices, link changes, role reassignments. Topology drift is one of the most subtle classes of incident — a single missing uplink can hide for months — and a diff makes it loud.
Findings as overlays
Operational findings can be projected onto the graph. A broken BGP session is no longer a row in a table; it is a red link between two named routers. The cognitive load of reasoning about a fault drops dramatically once it has a position in space.
Exporters
Beyond Mermaid, the model exports to JSON for downstream analysis and to a few common diagramming formats for teams who already standardised on something else. The graph is yours; it is not locked into this UI.
Performance
The renderer comfortably handles low-thousand node graphs. For larger fabrics, group nodes by site or role and let the explorer expand groups on demand. A flat ten-thousand-node graph is technically renderable and humanly useless.
Tips
- Always seed topology from inventory before parsing configs — devices missing from inventory get added with thin metadata you will spend weeks fixing.
- Snapshot topology after every change window. The diff is gold.
- Use Mermaid exports in your runbooks; static diagrams age in days, exported ones age in seconds.
What to try first
Parse the configs from one site, render the explorer, and look for surprises. Most teams find at least one link that exists in production and not in any document.
Was this helpful?
Generate scripts for the task covered in this post
Describe what you need and NAPT writes production-ready automation in Netmiko, NAPALM, or Nornir.
Open Script Generator →Related posts
From Noise to Narrative: How the RCA Engine Builds a Causal Story From Your Findings
The Root Cause Analysis engine reads every finding your scripts produce and stitches them into a single causal chain — root, contributing, symptom.
Read →The Streaming Console: A Live Terminal That Remembers Everything
Run any diagnostic script against any device, watch output stream in real time, and end up with structured findings the platform can reason about.
Read →Intent: Saying What You Mean and Proving the Network Agrees
Write a one-line statement of how the network should behave. The Intent engine compiles it into checks and tells you where reality diverges.
Read →