proxmox/reports/status/IP_CONFLICTS_RESOLUTION_COMPLETE.md

IP Conflicts Resolution - Complete

Date: 2026-01-02
Status: ✅ ALL CONFLICTS RESOLVED
Updated: 2026-01-02 - Documentation updated

---

Summary

All IP conflicts and invalid IP assignments have been resolved. All containers now have unique, valid IP addresses. Configuration files and documentation have been updated to reflect the new IP assignments.

---

Changes Made

1. ✅ Fixed VMID 6400 (Invalid IP)

Before: 192.168.11.0/24 (network address - INVALID)
After: 192.168.11.64/24 (valid host IP)
Status: ✅ Fixed and restarted

Action Taken:

pct stop 6400
pct set 6400 -net0 "name=eth0,bridge=vmbr0,gw=192.168.11.1,ip=192.168.11.64/24,hwaddr=BC:24:11:F7:E8:B8,type=veth"
pct start 6400

2. ✅ Resolved DBIS Container IP Conflicts

All DBIS containers have been reassigned to new, non-conflicting IP addresses:

VMID 10100 (dbis-postgres-primary)

• Before: 192.168.11.100/24 (conflict with VMID 1000)
• After: 192.168.11.105/24 ✅
• Status: ✅ Fixed and restarted

VMID 10101 (dbis-postgres-replica-1)

• Before: 192.168.11.101/24 (conflict with VMID 1001)
• After: 192.168.11.106/24 ✅
• Status: ✅ Fixed and restarted

VMID 10150 (dbis-api-primary)

• Before: 192.168.11.150/24 (conflict with VMID 1500)
• After: 192.168.11.155/24 ✅
• Status: ✅ Fixed and restarted

VMID 10151 (dbis-api-secondary)

• Before: 192.168.11.151/24 (conflict with VMID 1501)
• After: 192.168.11.156/24 ✅
• Status: ✅ Fixed and restarted

Action Taken for Each:

# Example for VMID 10100
pct stop <VMID>
pct set <VMID> -net0 name=eth0,bridge=vmbr0,gw=192.168.11.1,ip=<NEW_IP>/24,type=veth
pct start <VMID>

---

Documentation Updates

✅ Configuration Files Updated

1. dbis_core/config/dbis-core-proxmox.conf

   • Updated DBIS_POSTGRES_PRIMARY_IP to 192.168.11.105
   • Updated DBIS_POSTGRES_REPLICA_IP to 192.168.11.106
   • Updated DBIS_API_PRIMARY_IP to 192.168.11.155
   • Updated DBIS_API_SECONDARY_IP to 192.168.11.156
   • Updated IP range variables with notes about conflicts

2. dbis_core/DEPLOYMENT_PLAN.md

   • Updated all IP address references for VMIDs 10100, 10101, 10150, 10151
   • Updated IP range documentation to reflect adjustments

3. dbis_core/VMID_AND_CONTAINERS_SUMMARY.md

   • Updated IP addresses in the quick reference table

4. VMID_IP_ADDRESS_LIST.md

   • Updated with new IPs
   • Marked conflicts as resolved

---

Resolution Strategy

Chosen Approach: Option 1 - Reassign DBIS Container IPs

• Blockchain nodes (1000, 1001, 1500, 1501) kept their original IPs (production infrastructure)
• DBIS containers reassigned to adjacent, unused IPs:
  • 10100 → 192.168.11.105 (after validators at .100-104)
  • 10101 → 192.168.11.106
  • 10150 → 192.168.11.155 (after sentries at .150-154)
  • 10151 → 192.168.11.156

---

Verification Results

✅ No Duplicate IPs

All IP conflicts have been resolved. No containers share IP addresses.

✅ No Invalid IPs

VMID 6400 now uses a valid host IP (192.168.11.64) instead of the network address.

✅ All Containers Running

All affected containers have been restarted and are operational.

✅ Configuration Files Updated

All active configuration files and deployment documentation have been updated with new IPs.

---

Updated IP Assignments

VMID	Service	Old IP	New IP	Status
6400	indy-1	192.168.11.0/24	192.168.11.64/24	✅ Fixed
10100	dbis-postgres-primary	192.168.11.100/24	192.168.11.105/24	✅ Fixed
10101	dbis-postgres-replica-1	192.168.11.101/24	192.168.11.106/24	✅ Fixed
10150	dbis-api-primary	192.168.11.150/24	192.168.11.155/24	✅ Fixed
10151	dbis-api-secondary	192.168.11.151/24	192.168.11.156/24	✅ Fixed

---

Next Steps (Completed)

✅ Immediate Actions

1. ✅ All IP conflicts resolved
2. ✅ All containers restarted
3. ✅ Configuration files updated
4. ✅ Documentation updated

⏳ Optional Future Updates

1. Historical Documentation: Many deployment status files contain old IPs. These are historical records and may be left as-is, or updated if needed for reference.
2. Scripts: Some deployment scripts reference old IPs as defaults. These should work with environment variables, but could be updated if hardcoded values are problematic.
3. Service Configuration: If DBIS services have application-level configuration files that reference IPs, those may need updating.

---

Service Connectivity Notes

Important: After IP changes, any services that connect to DBIS containers (database connections, API endpoints, etc.) need to be updated with the new IPs:

• Database Connections: Update DATABASE_URL environment variables to use 192.168.11.105 instead of 192.168.11.100
• API Endpoints: Update API URLs to use 192.168.11.155 and 192.168.11.156 instead of 192.168.11.150 and 192.168.11.151
• Load Balancers/Proxies: Update any Nginx or load balancer configurations that reference the old IPs
• DNS/Service Discovery: If using service discovery, update records with new IPs

---

Verification Commands

Check for duplicate IPs:

ssh root@192.168.11.10 '
pct list | awk "NR>1{print \$1}" | while read -r vmid; do
  pct config "$vmid" 2>/dev/null | sed -n "s/.*ip=\([^,]*\).*/\$vmid \1/p"
done | sed "s#/.*##" | awk "\$2 != \"dhcp\" && \$2 != \"N/A\"" | \
sort -k2,2 | awk "{ ips[\$2]=ips[\$2] ? ips[\$2] \",\" \$1 : \$1; count[\$2]++ } \
END { for (ip in count) if (count[ip] > 1) print ip \" -> \" ips[ip] }" | sort -V'

Expected result: No output (no duplicates)

Check for invalid IPs:

ssh root@192.168.11.10 '
pct list | awk "NR>1{print \$1}" | while read -r vmid; do
  ip=$(pct config "$vmid" 2>/dev/null | sed -n "s/.*ip=\([^,]*\).*/\1/p")
  if [ -n "$ip" ] && [ "$ip" != "dhcp" ]; then
    ipbase=${ip%/*}
    last=${ipbase##*.}
    if [ "$last" = "0" ] || [ "$last" = "255" ]; then
      echo "$vmid $ip"
    fi
  fi
done'

Expected result: No output (no invalid IPs)

Test connectivity:

for ip in 64 105 106 155 156; do
  ping -c 1 192.168.11.$ip
done

---

Related Documents

• VMID_IP_CONFLICTS_ANALYSIS.md - Original conflict analysis
• VMID_IP_ADDRESS_LIST.md - Complete VMID/IP listing (updated)
• dbis_core/DEPLOYMENT_PLAN.md - DBIS deployment plan (updated)
• dbis_core/config/dbis-core-proxmox.conf - DBIS configuration (updated)

---

Last Updated: 2026-01-02
Status: ✅ COMPLETE - All conflicts resolved, documentation updated