<< All versions
Skill v1.0.1
currentLLM-judged scan90/100automateyournetwork/netclaw/evpn-vxlan-fabric
audit(jev): use TypeSafe Jev to find and fix skill-quality issues (#264)
──Details
PublishedSeptember 21, 2026 at 01:41 AM
Content Hashsha256:d1d2bc6164c3d3dd...
Git SHAad6a4a8a5e12
──Files
Files (1 file, 2.6 KB)
SKILL.md2.6 KBactive
SKILL.md · 63 lines · 2.6 KB
version: "1.0.1" name: evpn-vxlan-fabric description: "EVPN/VXLAN fabric audit and troubleshooting — VTEPs, VNIs, route types, multihoming, underlay/overlay validation. Use when troubleshooting VXLAN overlay reachability, auditing leaf-spine fabric health, debugging silent hosts or asymmetric flooding, or validating anycast gateway and ESI multihoming state." license: Apache-2.0 user-invocable: true metadata: { "openclaw": { "requires": { "bins": ["python3"], "env": ["PYATS_TESTBED_PATH"] } } }
EVPN/VXLAN Fabric
Primary Backends
pyats-networkpyats-routingpyats-topologynetbox-reconcile
Focus Areas
- VTEP reachability and loopback consistency
- VXLAN VNI to VLAN mapping
- EVPN route types 2, 3, and 5
- Anycast gateway consistency
- Multihoming and Ethernet Segment state
- Underlay routing health vs overlay symptoms
When to Use
- EVPN MAC/IP reachability issues
- Silent hosts or asymmetric flooding complaints
- Anycast gateway or ARP suppression problems
- Leaf-spine underlay failures impacting overlay forwarding
- Data-center fabric audit and documentation
Workflow: Overlay Reachability
- Verify underlay reachability between VTEPs.
- Check BGP EVPN session health and route-type presence.
- Validate VNI mapping, bridge domains, and anycast gateway settings.
- Cross-check local MAC learning against EVPN advertisements.
- Reconcile intended VLAN/VNI mappings against NetBox or ACI intent.
Workflow: Multihoming / ESI Trouble
- Confirm the access device and leaf pair are both healthy.
- Validate Ethernet Segment identifiers and DF election state.
- Check for duplicate MAC movement or split-horizon symptoms.
- Verify LACP state, access VLANs, and host-facing port consistency.
Important Rules
- Always validate the underlay before blaming the overlay
- Do not push fabric config without approved change control
- Use route-type evidence, not assumptions, to explain forwarding
Failure Behavior
- If a tool call fails with an authentication or connection error, check that
PYATS_TESTBED_PATHis 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.