Generate a complete Eve-ng lab guide for a CCNP ENCOR topic, and optionally deploy it automatically if Eve-ng MCP is connected.
Step 1 — Identify the Topic
Parse the argument provided:
- If a number (e.g.,
16), find the matching folder: 16-VLANs/
- If a name (e.g.,
OSPF or RSTP), fuzzy-match against folder names
- If no argument, ask the user which topic they want a lab for
Read the topic's README.md to understand what key concepts the lab should demonstrate.
Step 2 — Generate the Lab Guide
Create a complete lab document with these sections:
Objective
1–3 sentences: what the lab proves, what the user will configure, what they'll verify.
Topology Diagram
ASCII art showing the devices, their hostnames, interface labels, and connections.
Include an IP addressing table:
| Device | Interface | IP Address | Description |
Device List
| Hostname | Type | Eve-ng Image | Notes |
Use standard Eve-ng images:
- Cisco IOS router:
vios-adventerprisek9-m-15.9
- Cisco IOS switch:
viosl2-adventerprisek9-m-15.2
- Cisco IOSv:
vios-adventerprisek9 (lightweight)
Step-by-Step Configuration
Per device, in the order a real engineer would configure them. Every command in a code block. Brief comment before each block explaining what it does and why.
Verification Steps
Exact show commands with expected output snippets. Format as:
R1# show ip ospf neighbor
Neighbor ID Pri State Dead Time Interface
10.0.0.2 1 FULL/DR 00:00:37 GigabitEthernet0/0
Troubleshooting Tips
3–5 common mistakes for this topic and how to diagnose/fix them.
Step 3 — Save the Lab File
Save the lab guide to: ##-Topic-Name/lab/lab-guide.md
Create the lab/ directory if it doesn't exist. Use the Write tool to create the file.
Tell the user the file has been saved and where.
Step 4 — Offer Eve-ng Deployment
Check if the eveng MCP server is available (tools should be listed in the session).
If MCP is connected:
Ask the user: "Your Eve-ng server is connected. Want me to deploy this topology now? I'll create the lab, add nodes, connect interfaces, and start the devices."
If they say yes:
- Use
create_lab to create a new lab with a descriptive name (e.g., "RSTP-Lab-26")
- Use
add_node for each device in the topology
- Use
connect_node_to_node or connect_node_to_network to wire the interfaces
- Use
start_all to boot all nodes
- Report back: lab name, node console URLs or access info
- Tell the user: "Open Eve-ng and connect to the console of each device to start configuring."
If MCP is not connected:
Say: "Eve-ng MCP is not connected, so I can't deploy automatically. Run /install-eveng-mcp to set it up, then re-run /lab [topic] to deploy."
Notes
- Keep topologies small and focused (2–4 devices for most topics)
- Use realistic but simple IP addressing (e.g., 10.0.0.0/30 for point-to-point links)
- Labs should be completable in 30–60 minutes
- Every lab must have at least 3 verification commands
- If the topic README is empty (template not filled), still generate a solid lab from ENCOR knowledge