eve-lab-topology-design

Designs EVE-NG lab topologies and validates .unl files for connectivity and resilience.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill eve-lab-topology-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eve-lab-topology-design
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/eve-lab-topology-design
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill eve-lab-topology-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Designing network labs in EVE-NG often starts with vague requirements and ends with broken topologies containing orphan nodes, single points of failure, or invalid device adjacencies. This Skill structures the entire design workflow from requirements discovery through validated build plans.

Core Features & Use Cases

  • Structured Discovery: Classifies requests by domain (campus, branch/WAN, ISP/SP, data center, hybrid) and gathers missing requirements with labeled defaults for routing, redundancy, images, and scale.
  • Design Guidance: Provides trade-off tables for L2 vs L3 access, routing protocol selection, redundancy levels, and image selection (IOL, vEOS, vMX, NX-OSv, VPCS).
  • UNL Validation: Runs a Python validator against .unl files to detect orphan nodes, dangling interfaces, graph partitions, SPOF nodes and links, forbidden role adjacencies, and asymmetric redundancy groups.
  • Use Case: Ask for a leaf-spine data center lab design, receive physical and logical topologies plus a build plan, then validate the resulting .unl file against your requirements JSON before starting nodes.

Quick Start

Ask the assistant to design a redundant three-tier campus lab in EVE-NG with OSPF routing and validate the resulting .unl topology file.

Frequently Asked Questions about eve-lab-topology-design

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

FAQPage Schema
How do I validate an EVE-NG .unl topology file?

Run the validate_unl_topology.py script with the path to your .unl file, optionally adding --verbose for the connectivity matrix or --json for machine-readable output. It checks orphan nodes, dangling interfaces, partitions, SPOFs, and role adjacency rules.

How to design a leaf-spine data center lab in EVE-NG?

Classify the request as data center, then follow the discovery workflow to confirm scale, routing, and redundancy targets. The design guidance enforces true leaf-spine rules: no leaf-to-leaf or spine-to-spine links, with eBGP underlay and EVPN/VXLAN only when requested.

What images should I use for EVE-NG lab nodes?

The image selection guidance recommends Cisco IOL L3 for routers, IOL L2 for switches, and VPCS for hosts due to low resource usage. Heavier options like vEOS-lab, vMX, and NX-OSv 9000 are suggested only for vendor-specific or EVPN labs.

Can the validator check my design against required links?

Yes, pass a requirements JSON file with --reqs containing required_links, forbidden_links, and redundancy_groups with minimum uplink counts. The validator reports each requirement as pass or fail and exits nonzero on failures.

Why does the validator report SPOF warnings on my topology?

SPOF warnings appear when articulation-point nodes or bridge links exist whose removal would partition the topology graph. These are computed with Tarjan's algorithm, and you resolve them by adding redundant links or dual-homing affected nodes.