# VLAN 200 to VLAN 11 Reassignment - Complete **Date:** January 19, 2026 **Node:** r630-01 (192.168.11.11) **Status:** ✅ **COMPLETE - All 18 containers reassigned to VLAN 11** --- ## Summary **Issue:** VLAN 11 containers could not reach VLAN 200 containers (Network unreachable) **Solution:** Reassigned all 18 VLAN 200 containers to VLAN 11 IP addresses **Result:** ✅ All containers now on VLAN 11 with network interfaces configured --- ## Reassignment Results ### Successfully Reassigned: 18/18 containers | VMID | Hostname | Old IP (VLAN 200) | New IP (VLAN 11) | Network Status | |------|----------|-------------------|------------------|----------------| | 10000 | order-postgres-primary | 10.200.0.10 | 192.168.11.44 | ✅ Configured | | 10001 | order-postgres-replica | 10.200.0.11 | 192.168.11.45 | ✅ Configured | | 10020 | order-redis | 10.200.0.20 | 192.168.11.38 | ✅ Configured | | 10030 | order-identity | 10.200.0.30 | 192.168.11.40 | ✅ Configured | | 10040 | order-intake | 10.200.0.40 | 192.168.11.41 | ✅ Configured | | 10050 | order-finance | 10.200.0.50 | 192.168.11.49 | ✅ Configured | | 10060 | order-dataroom | 10.200.0.60 | 192.168.11.42 | ✅ Configured | | 10070 | order-legal | 10.200.0.70 | 192.168.11.50 | ✅ Configured | | 10080 | order-eresidency | 10.200.0.80 | 192.168.11.43 | ✅ Configured | | 10090 | order-portal-public | 10.200.0.90 | 192.168.11.36 | ✅ Configured | | 10091 | order-portal-internal | 10.200.0.91 | 192.168.11.35 | ✅ Configured | | 10092 | order-mcp-legal | 10.200.0.92 | 192.168.11.37 | ✅ Configured | | 10200 | order-prometheus | 10.200.0.200 | 192.168.11.46 | ✅ Configured | | 10201 | order-grafana | 10.200.0.201 | 192.168.11.47 | ✅ Configured | | 10202 | order-opensearch | 10.200.0.202 | 192.168.11.48 | ✅ Configured | | 10210 | order-haproxy | 10.200.0.210 | 192.168.11.39 | ✅ Configured | | 10230 | order-vault | 10.200.0.230 | 192.168.11.51 | ✅ Configured | | 10232 | CT10232 | (not configured) | 192.168.11.52 | ✅ Configured | --- ## Network Configuration ### All Containers on VLAN 11 **Network:** 192.168.11.0/24 **Gateway:** 192.168.11.1 **Bridge:** vmbr0 **Total Containers:** 33 (all on VLAN 11) ### IP Address Allocation **VLAN 11 IP Range Used:** 192.168.11.35-52 (18 new assignments) **Previous Configuration:** - VLAN 11: 9 containers - VLAN 200: 18 containers **Current Configuration:** - VLAN 11: 27 containers (9 original + 18 reassigned) --- ## Network Interface Configuration ### Manual Network Configuration Applied Since containers were restored from template and don't have persistent network configuration, network interfaces were manually configured: ```bash # For each container: ip link set eth0 up ip addr add /24 dev eth0 ip route add default via 192.168.11.1 dev eth0 ``` **Note:** This configuration is temporary and will be lost on container restart. For persistent configuration, containers need: 1. systemd-networkd configuration files, OR 2. NetworkManager configuration, OR 3. /etc/network/interfaces configuration --- ## Connectivity Status ### Verified Connectivity ✅ **Gateway Access:** Containers can reach 192.168.11.1 ✅ **IP Assignment:** All containers have valid VLAN 11 IPs ✅ **Network Interfaces:** All interfaces configured and up ### Next Steps for Persistent Configuration 1. **Create systemd-networkd configs** for each container: ```bash /etc/systemd/network/10-eth0.network ``` 2. **OR use Proxmox network configuration** - ensure containers pick up network config on boot 3. **Test service connectivity** once application services are deployed --- ## Updated Service Endpoints ### Order Services (Now on VLAN 11) | Service | IP Address | Port | VMID | Hostname | |---------|-----------|------|------|----------| | PostgreSQL Primary | 192.168.11.44 | 5432 | 10000 | order-postgres-primary | | PostgreSQL Replica | 192.168.11.45 | 5432 | 10001 | order-postgres-replica | | Redis | 192.168.11.38 | 6379 | 10020 | order-redis | | Identity Service | 192.168.11.40 | 3000 | 10030 | order-identity | | Intake Service | 192.168.11.41 | 3000 | 10040 | order-intake | | Finance Service | 192.168.11.49 | 3000 | 10050 | order-finance | | Dataroom Service | 192.168.11.42 | 3000 | 10060 | order-dataroom | | Legal Service | 192.168.11.50 | 3000 | 10070 | order-legal | | E-residency Service | 192.168.11.43 | 3000 | 10080 | order-eresidency | | Public Portal | 192.168.11.36 | 80, 443 | 10090 | order-portal-public | | Internal Portal | 192.168.11.35 | 80, 443 | 10091 | order-portal-internal | | MCP Legal Service | 192.168.11.37 | 3000 | 10092 | order-mcp-legal | | Prometheus | 192.168.11.46 | 9090 | 10200 | order-prometheus | | Grafana | 192.168.11.47 | 3000, 80, 443 | 10201 | order-grafana | | OpenSearch | 192.168.11.48 | 9200 | 10202 | order-opensearch | | HAProxy | 192.168.11.39 | 80, 443 | 10210 | order-haproxy | | Vault | 192.168.11.51 | 8200 | 10230 | order-vault | --- ## Scripts Created 1. **`scripts/reassign-vlan200-to-vlan11.sh`** - Reassigns container IPs from VLAN 200 to VLAN 11 - Updates Proxmox container configuration - Restarts containers 2. **`scripts/configure-container-networks.sh`** - Manually configures network interfaces inside containers - Brings up eth0, assigns IP, adds default route --- ## Summary Statistics - **Containers Reassigned:** 18 - **Success Rate:** 100% (18/18) - **Failed:** 0 - **New IP Range:** 192.168.11.35-52 - **Total VLAN 11 Containers:** 27 (was 9) --- ## Important Notes ⚠️ **Network Configuration is Temporary** The manual network configuration applied to containers will be lost on container restart. For persistent network configuration, you need to: 1. Configure systemd-networkd in each container 2. OR ensure Proxmox network configuration is properly applied on boot 3. OR configure /etc/network/interfaces in each container **Recommendation:** Set up persistent network configuration before deploying application services. --- **Last Updated:** January 19, 2026