proxmox/reports/analyses/R630-04_IP_CONFLICT_DISCOVERY.md

# R630-04 IP Conflict Discovery

**Date**: 2026-01-05  
**IP Address**: 192.168.11.14  
**Status**: ⚠️ **CRITICAL - IP CONFLICT IDENTIFIED**

---

## Executive Summary

**CRITICAL DISCOVERY**: **192.168.11.14 is NOT the r630-04 Proxmox host.**

The device responding on 192.168.11.14 is running **Ubuntu**, but Proxmox VE is **Debian-based**. This indicates an IP conflict or misconfiguration.

---

## Evidence

### 1. SSH Banner Analysis

**What We See**:
```
OpenSSH_8.9p1 Ubuntu-3ubuntu0.13
```

**What We Expect** (Proxmox hosts):
- ml110: `Debian GNU/Linux 13 (trixie)` ✅
- r630-01: `Debian GNU/Linux 13 (trixie)` ✅
- r630-02: `Debian GNU/Linux 13 (trixie)` ✅ (assumed)
- r630-04: Should be Debian, but shows **Ubuntu** ❌

### 2. Cluster Verification

**Active Cluster Members**:
- ml110 (192.168.11.10) - Debian ✅
- r630-01 (192.168.11.11) - Debian ✅
- r630-02 (192.168.11.12) - Debian ✅
- r630-04 (192.168.11.14) - **NOT IN CLUSTER** ❌

### 3. Container/VM Search

**Result**: **NO containers or VMs** in the cluster are configured with IP 192.168.11.14

**Checked**:
- All LXC containers on ml110, r630-01, r630-02
- All QEMU VMs on ml110, r630-01, r630-02
- No matches found

---

## Possible Scenarios

### Scenario A: Orphaned VM/Container (Most Likely)

**Description**: A VM or container running Ubuntu is using 192.168.11.14 but is not registered in Proxmox.

**Possible Causes**:
- VM/container created outside Proxmox management
- Proxmox database corruption (VM exists but not in cluster view)
- VM on a different Proxmox host not in the cluster
- Standalone VM running on r630-04 hardware

**How to Verify**:
```bash
# Check all Proxmox hosts for VMs
for host in 192.168.11.10 192.168.11.11 192.168.11.12; do
  ssh root@$host "qm list; pct list"
done

# Check for orphaned VMs
ssh root@192.168.11.10 "find /var/lib/vz -name '*.conf' | xargs grep -l '192.168.11.14'"
```

### Scenario B: Different Physical Device

**Description**: A different physical server or network device is using 192.168.11.14.

**Possible Causes**:
- Another server configured with this IP
- Network device (switch, router) using this IP
- Misconfigured device on the network

**How to Verify**:
```bash
# Get MAC address
arp -n 192.168.11.14
# or
ip neigh show 192.168.11.14

# Check MAC vendor to identify device type
```

### Scenario C: r630-04 Running Ubuntu (Not Proxmox)

**Description**: r630-04 was reinstalled with Ubuntu instead of Proxmox VE.

**Possible Causes**:
- Server was reinstalled with Ubuntu
- Proxmox was removed/replaced
- Server is running plain Ubuntu (not Proxmox)

**How to Verify**:
- Physical inspection of r630-04
- Console/iDRAC access to check actual OS
- Check if Proxmox is installed: `dpkg -l | grep pve`

### Scenario D: IP Conflict / Wrong IP Assignment

**Description**: The actual r630-04 Proxmox host is using a different IP, and something else is using 192.168.11.14.

**Possible Causes**:
- r630-04 Proxmox host is actually using a different IP
- Another device was assigned 192.168.11.14
- Network misconfiguration

**How to Verify**:
- Check all Proxmox hosts for their actual IPs
- Verify r630-04 physical server network configuration
- Check DHCP/static IP assignments

---

## Recommended Actions

### Immediate Actions

1. **Identify What's Actually Using 192.168.11.14**
   ```bash
   # Get MAC address
   ping -c 1 192.168.11.14
   arp -n 192.168.11.14
   
   # Try to identify device
   # Check MAC vendor database
   ```

2. **Find the Actual r630-04 Proxmox Host**
   - Check physical r630-04 server
   - Verify its actual IP address
   - Check if Proxmox is installed
   - Verify network configuration

3. **Check for Orphaned VMs**
   ```bash
   # On each Proxmox host
   ssh root@192.168.11.10 "qm list --all"
   ssh root@192.168.11.11 "qm list --all"
   ssh root@192.168.11.12 "qm list --all"
   
   # Check for VMs not in cluster view
   ```

4. **Verify Network Configuration**
   - Check router/switch ARP tables
   - Verify IP assignments in Omada controller
   - Check for duplicate IP assignments

### Long-term Actions

1. **Resolve IP Conflict**
   - If orphaned VM: Remove or reassign IP
   - If different device: Reassign IP or update documentation
   - If r630-04 is Ubuntu: Decide if Proxmox should be installed

2. **Update Documentation**
   - Correct IP assignments
   - Document actual r630-04 status
   - Update network topology

3. **Network Audit**
   - Complete IP address audit
   - Verify all device assignments
   - Check for other conflicts

---

## Network Topology Impact

### Current Understanding

| IP Address | Expected Device | Actual Device | Status |
|------------|----------------|---------------|--------|
| 192.168.11.10 | ml110 (Proxmox) | ml110 (Proxmox Debian) | ✅ Correct |
| 192.168.11.11 | r630-01 (Proxmox) | r630-01 (Proxmox Debian) | ✅ Correct |
| 192.168.11.12 | r630-02 (Proxmox) | r630-02 (Proxmox Debian) | ✅ Correct |
| 192.168.11.14 | r630-04 (Proxmox) | **Unknown (Ubuntu)** | ❌ **CONFLICT** |

### What We Need to Find

1. **Where is the actual r630-04 Proxmox host?**
   - Is it powered off?
   - Is it using a different IP?
   - Does it exist at all?

2. **What is using 192.168.11.14?**
   - VM/container?
   - Different physical device?
   - Misconfigured network device?

---

## Next Steps Checklist

- [ ] Get MAC address of device using 192.168.11.14
- [ ] Identify device type from MAC vendor
- [ ] Check physical r630-04 server status
- [ ] Verify r630-04 actual IP address
- [ ] Check for orphaned VMs on all Proxmox hosts
- [ ] Review network device configurations
- [ ] Check Omada controller for IP assignments
- [ ] Resolve IP conflict
- [ ] Update documentation with correct information

---

## Related Documentation

- `R630-04_DIAGNOSTIC_REPORT.md` - Initial diagnostic report
- `RESERVED_IP_CONFLICTS_ANALYSIS.md` - IP conflict analysis
- `docs/archive/historical/OMADA_CLOUD_CONTROLLER_IP_ASSIGNMENTS.md` - IP assignments

---

**Last Updated**: 2026-01-05  
**Status**: ⚠️ **REQUIRES INVESTIGATION**  
**Priority**: **HIGH** - IP conflict needs resolution