Files
bf-infra/mcp/mikromcp/config/routers.yaml
Christoph Emsenhuber 30301d40e2 TP21: routers.yaml auf finale MGMT-IPs aktualisiert; Sub-TP21.1 CRS326-Branch-Recovery dokumentiert; Nautobot-Image procps-Fix
- mcp/mikromcp/config/routers.yaml: ap1→10.40.99.11, ap2→10.40.99.12,
  crs326-core→10.40.99.1, crs326-branch→10.40.99.2 (tags aktualisiert).
- docs/teilprojekte.md: TP21.1 angelegt — Branch nach Reboot/Lockout recovery.
- docs/nas-vlan20/nautobot-image/Dockerfile: procps installiert (healthcheck).

Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-08 11:40:20 +02:00

55 lines
1.3 KiB
YAML

# MikroMCP Router-Registry — BF Netzwerk (final IPs, TP21)
# Credentials NICHT hier, sondern via ENV (envPrefix -> ROUTER_<PREFIX>_USER/PASS in .env).
# Alle Geräte sprechen REST über PLAIN HTTP auf Port 80.
# -> tls.enabled: false (rest-client.ts: scheme = tls.enabled ? https : http)
# Änderungen hier werden erst nach MikroMCP-Neustart wirksam.
routers:
ap1:
host: "10.40.99.11"
port: 80
tls:
enabled: false
rejectUnauthorized: true
credentials:
source: "env"
envPrefix: "ROUTER_AP1"
tags: ["bf", "wifi", "access-point"]
rosVersion: "7.23"
ap2:
host: "10.40.99.12"
port: 80
tls:
enabled: false
rejectUnauthorized: true
credentials:
source: "env"
envPrefix: "ROUTER_AP2"
tags: ["bf", "wifi", "access-point"]
rosVersion: "7.23"
crs326-core:
host: "10.40.99.1"
port: 80
tls:
enabled: false
rejectUnauthorized: true
credentials:
source: "env"
envPrefix: "CRS326_CORE"
tags: ["bf", "switch", "core", "l3-router"]
rosVersion: "7.19.5"
crs326-branch:
host: "10.40.99.2"
port: 80
tls:
enabled: false
rejectUnauthorized: true
credentials:
source: "env"
envPrefix: "CRS326_BRANCH"
tags: ["bf", "switch", "branch"]
rosVersion: "7.19.5"