eve-lab-topology-build

EVE Lab Topology Build

Use this skill for network objects and interface wiring inside an existing EVE-NG lab.

Workflow

1. Read the current topology first with eve_get_topology or eve_list_node_interfaces.
2. Before rewiring, follow {baseDir}/references/wiring-guardrails.md.
3. Create or reuse the required network object.
4. Connect interfaces only after confirming IDs from {baseDir}/references/network-and-interface-reference.md.
5. Re-read topology after the change; do not trust the write response alone.

Available tools

• eve_get_topology
• eve_list_networks
• eve_create_network
• eve_delete_network
• eve_list_node_interfaces
• eve_connect_interface
• eve_list_node_types

When to read references

• Read {baseDir}/references/wiring-guardrails.md for stop/start, direct-segment, node-ID, and image-verification rules.
• Read {baseDir}/references/network-and-interface-reference.md for network types and interface-index guidance.

Failure Behavior

• If a tool call fails with an authentication or connection error, check that EVE_PASSWORD, EVE_URL, EVE_USER are set and valid before assuming a data or device problem.
• On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
• For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.