Files
proxmox/docs/03-deployment/VLAN_FLAT_11_TO_SEGMENTED_RUNBOOK.md
defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.
- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor
2026-04-12 06:12:20 -07:00

2.1 KiB
Raw Blame History

VLAN migration runbook — flat 11 → segmented

Current: Single broadcast domain 192.168.11.0/24 (VLAN 11).
Target segments: Documented in NETWORK_CONFIGURATION_MASTER.md (e.g. 110112, 120, 160, 200203).
Policy: Enforce IP uniqueness and automated drift before cutover (SANKOFA_IT_OPERATIONS_CONTROLLER_SPEC.md section 4).

Preconditions

  1. bash scripts/it-ops/export-live-inventory-and-drift.sh exits 0 (no duplicate_ips for different guest names).
  2. Backup UDM/UniFi and Proxmox network configs.
  3. Maintenance window announced for default gateway moves.

Ordered segments (do not reorder without risk review)

Step Segment Intent
1 Out-of-band / IPMI (if any) Isolate management before touching data plane
2 Tenant-facing VLANs (200+) Reduce blast radius for external-facing workloads
3 Besu validators / RPC High sensitivity; coordinate with Chain 138 ops
4 Sankofa app tier Portal, Keycloak, NPM upstreams

Executable checklist

Run the shell helper (dry-run by default):

bash scripts/it-ops/vlan-segmentation-ordered-checklist.sh
bash scripts/it-ops/vlan-segmentation-ordered-checklist.sh --apply

--apply only records completion timestamps in a local state file under reports/status/; it does not configure switches. Use it as an operator log.

Per-step tasks (manual)

  1. Create VLANs on UDM/UniFi; assign subnets (no overlap with existing static leases).
  2. Add tagged ports on switches; update Proxmox bridges / CT net0 VLAN tags incrementally.
  3. Re-run IPAM export after each wave; fix drift before the next wave.
  4. Update ALL_VMIDS_ENDPOINTS.md and config/ip-addresses.conf after live matches intent.

Rollback

  • Keep previous UDM backup; revert trunk tagging if a segment loses gateway.
  • Document actual vs planned in reports/status/ for the IT controller audit log (Phase 3).