admin/bf-infra
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases Wiki Activity

TP2 🔄 omada-mcp deployed (.176/pve-LXC) — braucht Open-API-Client-Creds

Browse Source 
- omada-mcp Container auf pve-LXC (.126, endpointId=2, ipvlan .176), Stack Id=200, gestoppt
- Erkenntnis: jmtvms/tplink-omada-mcp nutzt Omada OPEN API (CLIENT_ID/SECRET/OMADAC_ID/SITE_ID),
  NICHT username/password → .env-Schema + compose-Kommentare + .env.template angepasst
- omada-mcp in ~/.claude/settings.json eingetragen (SSE .176:3000)
- Letzter manueller Schritt: Open-API-App im Controller-UI anlegen (Platform Integration),
  Client-Creds + SITE_ID in .env → Container starten → reload → dann VLANs + Adoption

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Christoph Emsenhuber
2026-06-15 14:49:51 +02:00
parent c5d4ee8bfa
commit bf5d2b2741
4 changed files with 39 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/teilprojekte.md
View File

@@ -39,13 +39,15 @@ Kontrolle: MikroMCP (MikroTik) live · ALLNET = Klickanleitungen (inline) · Oma
### TP2 — Omada Access-Switch + Controller ▸ 🔄 IN ARBEIT (2026-06-15)
- ✅ Omada Controller 6.2.10.17 auf DS923 (macvlan `.175`): `omada/docker-compose.yml`, Stack via Portainer endpointId=14. **Wizard abgeschlossen** (configured=true), Creds in `mcp/omada/.env`.
- ✅ pve-mcp (samik081) in Claude Code eingetragen (`~/.claude/settings.json`, SSE `.173:3000`).
- ✅ omada-mcp staged: `mcp/omada/` (compose + .env fertig befüllt), macvlan `.174`.
- ✅ omada-mcp Container deployed auf **pve-LXC (`.126`, endpointId=2), ipvlan-IP `.176`**, in `~/.claude/settings.json` eingetragen. **Aktuell gestoppt** (Crash-Loop).
- ⚠️ **Erkenntnis:** `jmtvms/tplink-omada-mcp` nutzt die **Omada OPEN API** (`OMADA_CLIENT_ID/SECRET/OMADAC_ID/SITE_ID`), **nicht** User/Passwort. `.env`-Schema entsprechend angepasst.
- ⚠️ Admin-API-Login (admin / Wizard-PW) gibt `-30109` → im UI verifizieren.
**Noch offen (Reihenfolge):**
1. omada-mcp Container deployen (Portainer endpointId=14, `mcp/omada/docker-compose.yml`)
2. `~/.claude/settings.json` → `"omada-mcp": {"url": "http://10.40.41.174:3000/sse"}` eintragen
3. Claude Code neu starten → omada-mcp Tools verfügbar
4. VLANs 10/20/30/40/50/90/99/100 im Controller anlegen
5. `.12` adoptieren → Port 2 (ap2) + Uplink-Port → Trunk-All, Restports → Access VLAN10
1. Controller-UI https://10.40.41.175:8043 → Settings → Platform Integration → **Open API** → App anlegen (Grant: Client Credentials) → Client ID + Secret notieren
2. `OMADA_SITE_ID` holen (UI oder `GET /{omadacId}/api/v2/sites`)
3. `mcp/omada/.env` befüllen (CLIENT_ID/SECRET/SITE_ID) → Container neu starten (Portainer Stack `omada-mcp`, Id=200)
4. SSE-Test `http://10.40.41.176:3000/health` → Claude Code reload → omada-mcp Tools verfügbar
5. VLANs 10/20/30/40/50/90/99/100 anlegen → `.12` adoptieren → Port 2 (ap2) + Uplink → Trunk-All, Rest → Access VLAN10
- ✅ Port-Plan: Omada-Switch Port 2 = ap2 (Trunk all), Uplink-Port (→ ALLNET GE8) = Trunk all.
- ✅ Portainer-Ablösung: **Komodo** empfohlen (einzige Option mit nativem MCP `mcp-server-komodo`). Eigener Task.
- Abh. erfüllt: TP1 (GE8 Trunk ✅).