eve-ng-node-operations

Manage EVE-NG node lifecycle including creation, start, stop, deletion, and NVRAM wipe.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing EVE-NG lab nodes manually through the web UI is slow and error-prone, especially when tracking runtime state across labs that reuse node IDs. This Skill provides programmatic control over the full node lifecycle with guardrails that prevent common mistakes like starting nodes without images or misreading cross-lab status.

Core Features & Use Cases

  • Node Lifecycle Control: List, inspect, create, delete, start, and stop individual nodes or entire labs through the EVE-NG API.
  • Factory Reset: Wipe node NVRAM back to factory defaults when a clean configuration state is needed.
  • Safety Guardrails: Enforce single-lab operation, node-ID collision checks, image availability verification, and lab-UUID-scoped runtime status validation.
  • Use Case: Before a training session, start all nodes in a lab, verify each node's runtime state is correctly scoped to the lab UUID, and confirm consoles are ready before pushing configurations.

Quick Start

List all nodes in my EVE-NG lab and start the ones that are currently stopped.

Frequently Asked Questions about eve-ng-node-operations

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

FAQPage Schema
How do I start and stop EVE-NG nodes programmatically?

Use the eve_start_node and eve_stop_node tools with the target node ID, or eve_start_lab and eve_stop_lab to control the entire lab at once. Always verify the resulting runtime status before assuming the operation completed.

How do I create a new node in an EVE-NG lab?

Use eve_create_node after checking that the required image exists locally or in the ishare2 inventory. Verify the lab's node-ID block does not collide with other saved labs before creating the node.

What node types does EVE-NG support?

EVE-NG supports IOL, QEMU (vios, csr1000v, nxosv, vmx), Dynamips (c7200, c3725), VPCS, and Docker node types. IOL nodes are fast with low RAM usage, while QEMU nodes run full virtual machine images.

Why does an EVE-NG node show running but the console is not ready?

The EVE-NG API can report a node as running before its console is actually available. Use console discovery to confirm boot completion before sending configuration commands to the node.

Why does node status appear wrong when multiple labs use the same node IDs?

EVE-NG API status can leak across labs that reuse node IDs because runtime state is scoped by lab UUID. Verify the local runtime path under the lab UUID or use MCP-corrected status before concluding a node is up.