proxmox/reports/status/RESERVED_IP_CONFLICTS_ANALYSIS.md

Reserved IP Range Conflicts - Analysis and Fix

Date: 2026-01-02
Status: ⚠️ CONFLICTS FOUND
Reserved Range: 192.168.11.10 - 192.168.11.25 (Physical Servers)

---

Summary

192.168.11.14 is responding because it's the physical server r630-04, not a VMID.

However, 2 VMIDs are using IPs in the reserved range for physical servers:

VMID	Hostname	Current IP	Node	Status	New IP
105	nginxproxymanager	192.168.11.21	r630-02	running	192.168.11.26
130	monitoring-1	192.168.11.22	r630-02	running	192.168.11.27

---

Physical Server IP Assignments

The following IPs are reserved for physical servers:

IP Address	Server	Hostname	Status
192.168.11.10	ml110	ml110	✅ Active
192.168.11.11	r630-01	pve	✅ Active
192.168.11.12	r630-02	pve2	✅ Active
192.168.11.13	r630-03	r630-03	❌ Not plugged in
192.168.11.14	r630-04	r630-04	⚠️ Reachable (password issue)
192.168.11.15	r630-05	r630-05	❓ Unknown
192.168.11.16-25	Reserved	-	For future physical servers

---

VMIDs Using Reserved IPs

VMID 105 (nginxproxymanager)

• Current IP: 192.168.11.21
• Node: r630-02
• Service: Nginx Proxy Manager
• Status: Running
• New IP: 192.168.11.26 (recommended)

VMID 130 (monitoring-1)

• Current IP: 192.168.11.22
• Node: r630-02
• Service: Monitoring service
• Status: Running
• New IP: 192.168.11.27 (recommended)

---

Why 192.168.11.14 is Responding

192.168.11.14 is the IP address of the physical server r630-04, not a VMID. When you ping this IP, you're pinging the physical Proxmox host itself.

Current Status:

• ✅ Server is powered on and reachable
• ⚠️ SSH password authentication is failing
• ⚠️ Proxmox Web UI is not accessible (pveproxy issue)

Action Required: Access r630-04 via console/iDRAC to reset password and fix Proxmox services.

---

Fix Script

A script has been created to automatically fix the IP conflicts:

Script: scripts/fix-reserved-ip-conflicts.sh

What it does:

1. Stops the affected containers
2. Changes IP addresses to new values outside reserved range
3. Restarts containers
4. Verifies the changes

To run:

cd /home/intlc/projects/proxmox
./scripts/fix-reserved-ip-conflicts.sh

---

Recommended New IPs

Available IP Ranges

Option 1: Use 192.168.11.26-99 (Recommended)

• ✅ Close to current IPs (minimal configuration changes)
• ✅ Well within safe range
• ✅ No conflicts with existing infrastructure

Option 2: Use 192.168.11.113-139

• ✅ Between existing services
• ✅ Clear separation from reserved range

Option 3: Use 192.168.11.200+

• ✅ Already used by some RPC nodes
• ✅ Clear separation

Recommended Assignments

VMID	Service	Current IP	New IP	Reason
105	nginxproxymanager	192.168.11.21	192.168.11.26	Next available after reserved range
130	monitoring-1	192.168.11.22	192.168.11.27	Next available after reserved range

---

Impact Analysis

Services Affected

VMID 105 (nginxproxymanager):

• Impact: Any services routing through Nginx Proxy Manager
• Action: Update DNS records, firewall rules, and service configurations
• Downtime: Minimal (container restart only)

VMID 130 (monitoring-1):

• Impact: Monitoring services, dashboards, alerts
• Action: Update monitoring configurations, dashboard URLs
• Downtime: Minimal (container restart only)

Configuration Files to Update

After changing IPs, update:

1. DNS records (if any)
2. Firewall rules
3. Service configurations that reference these IPs
4. Monitoring configurations
5. Load balancer configurations (if applicable)

---

Verification

After running the fix script, verify:

# Check new IPs
ssh root@192.168.11.12 "pct config 105 | grep net0"
ssh root@192.168.11.12 "pct config 130 | grep net0"

# Test connectivity
ping -c 2 192.168.11.26
ping -c 2 192.168.11.27

# Test services
curl -k https://192.168.11.26:8443  # Nginx Proxy Manager
curl -k https://192.168.11.27:3000  # Monitoring (if applicable)

---

Related Documentation

• Physical Hardware Inventory
• VMID IP Address List
• R630-03/04 Connectivity Status

---

Last Updated: 2026-01-02
Fix Script: scripts/fix-reserved-ip-conflicts.sh