Instalar en Claude Code
Copiargit clone --depth 1 https://github.com/zw008/VMware-NSX /tmp/vmware-nsx && cp -r /tmp/vmware-nsx/skills/vmware-nsx ~/.claude/skills/vmware-nsxDespués abre una sesión nueva de Claude Code; el skill carga automáticamente.
Definición
SKILL.md
# VMware NSX > **Disclaimer**: This is a community-maintained open-source project and is **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc.** "VMware" and "NSX" are trademarks of Broadcom. Source code is publicly auditable at [github.com/zw008/VMware-NSX](https://github.com/zw008/VMware-NSX) under the MIT license. VMware NSX networking management — 32 MCP tools for segments, gateways, NAT, routing, and IPAM. > Domain-focused networking skill for NSX-T / NSX 4.x Policy API. > **Companion skills**: [vmware-nsx-security](https://github.com/zw008/VMware-NSX-Security) (DFW/firewall), [vmware-aiops](https://github.com/zw008/VMware-AIops) (VM lifecycle), [vmware-monitor](https://github.com/zw008/VMware-Monitor) (read-only monitoring), [vmware-storage](https://github.com/zw008/VMware-Storage) (iSCSI/vSAN), [vmware-vks](https://github.com/zw008/VMware-VKS) (Tanzu Kubernetes), [vmware-aria](https://github.com/zw008/VMware-Aria) (metrics/alerts/capacity), [vmware-avi](https://github.com/zw008/VMware-AVI) (AVI/ALB/AKO), [vmware-harden](https://github.com/zw008/VMware-Harden) (compliance baselines). > | [vmware-pilot](../vmware-pilot/SKILL.md) (workflow orchestration) | [vmware-policy](../vmware-policy/SKILL.md) (audit/policy) ## What This Skill Does | Category | Tools | Count | Read / Write | |----------|-------|:-----:|:------------:| | **Segments** | list, get details, create, update, delete | 5 | 2R / 3W | | **Tier-0 Gateways** | list, get details, BGP neighbors, configure BGP | 4 | 3R / 1W | | **Tier-1 Gateways** | list, get details, create, update, delete | 5 | 2R / 3W | | **NAT** | list rules, create rule, delete rule | 3 | 1R / 2W | | **Static Routes** | list, create, delete | 3 | 1R / 2W | | **IP Pools** | list, get usage, create pool, delete pool | 4 | 2R / 2W | | **Fabric Inventory** | transport zones, transport nodes, edge clusters | 3 | 3R / 0W | | **Health** | NSX alarms, transport node status, edge cluster status, manager status | 4 | 4R / 0W | | **Troubleshooting** | logical port status, VM-to-segment lookup | 2 | 2R / 0W | **Total**: 33 tools (20 read-only + 13 write) ## Quick Install ```bash uv tool install vmware-nsx-mgmt vmware-nsx doctor ``` ## When to Use This Skill - List, create, or modify NSX segments (overlay / VLAN-backed) - Create or manage Tier-0 / Tier-1 gateways - Configure NAT rules (SNAT, DNAT, reflexive) - View or add static routes, check BGP neighbors - Manage IP pools and subnet allocations - Check NSX alarms, transport node health, edge cluster status - Find which segment a VM is connected to - Troubleshoot logical port status **Use companion skills for**: - Distributed firewall, security groups, DFW rules, IDS/IPS → `vmware-nsx-security` - VM lifecycle, deployment, guest ops → `vmware-aiops` - vSphere inventory, health, alarms, events → `vmware-monitor` - Storage: iSCSI, vSAN, datastores → `vmware-storage` - Tanzu Kubernetes → `vmware-vks` - Load balancing, AVI/ALB, AKO, Ingress → `vmware-avi` ## Related Skills — Skill Routing | User Intent | Recommended Skill | |-------------|-------------------| | NSX networking: segments, gateways, NAT, routing, IPAM | **vmware-nsx** ← this skill | | NSX security: DFW rules, security groups, IDS/IPS | **vmware-nsx-security** | | Read-only vSphere monitoring, alarms, events | **vmware-monitor** | | VM lifecycle, deployment, guest ops | **vmware-aiops** | | Storage: iSCSI, vSAN, datastores | **vmware-storage** | | Tanzu Kubernetes (vSphere 8.x+) | **vmware-vks** | | Aria Ops: metrics, alerts, capacity planning | **vmware-aria** | | Multi-step workflows with approval | **vmware-pilot** | | Compliance baselines (CIS / 等保 / PCI-DSS), drift detection, LLM remediation advisor | **vmware-harden** (`uv tool install vmware-harden`) | | Load balancer, AVI, ALB, AKO, Ingress | **vmware-avi** (`uv tool install vmware-avi`) | | Audit log query | **vmware-policy** (`vmware-audit` CLI) | ## Common Workflows ### Create an App Network (Segment + T1 Gateway + NAT) **Pre-flight (judgment, not blind sequence)**: - Subnet conflict check: scan `inventory list-segments` and `networking list-ip-pools` for any overlap with the proposed CIDR. Overlapping subnets cause asymmetric routing or silent blackholing — NSX will not warn you. - Edge cluster capacity: confirm chosen `--edge-cluster` is healthy (`inventory list-edge-clusters` + `health edge-cluster-status <id>`) and not at SR (Service Router) limit. A fully-loaded edge cluster will accept the T1 creation but routing will fail. - T0 uplink: the parent T0 must already be configured with BGP/static routes upstream — otherwise SNAT works internally but external traffic goes nowhere. - NAT IP: `--translated` IP must be from a routable address pool announced by T0; using a random IP creates a half-working network. - **Always `--dry-run` first** — once a segment is attached to running VMs, deleting it requires detaching every port. **Steps**: 1. `vmware-nsx gateway create-tier1 app-t1 --name app-t1 --edge-cluster <ec-path> --tier0 <t0-path> --dry-run` → review, then run for real 2. `vmware-nsx segment create app-web-seg --name app-web-seg --tz <tz-overlay-path> --subnet <gw-cidr>` 3. `vmware-nsx nat create-rule --tier1 app-t1 --rule-id snat-1 --action SNAT --source <private-cidr> --translated <pub-ip>` 4. Verify end-to-end: `inventory list-segments`, `networking list-nat-rules app-t1`, AND test with a VM attached to the new segment 5. **On failure**: a connection error or HTTP error prints a single teaching line (e.g. 403 → check NSX role privileges; 404 → run the matching list command for the exact ID). Run `vmware-nsx doctor` to verify connectivity and credentials, fix, and re-run the failed step — earlier completed steps are idempotent PUTs and safe to re-apply. ### Check Network Health **Judgment**: don't just enumerate health endpoints — correlate them. The order below maps cause to symptom: if manager is down, transport nodes will look down too (fal