# IP Conflict Resolution: 192.168.11.14

**Date**: 2026-01-05  
**Status**: 🔄 **CONFLICT IDENTIFIED - RESOLUTION IN PROGRESS**

---

## Conflict Summary

| Property | Value |
|----------|-------|
| **IP Address** | 192.168.11.14 |
| **Assigned To** | r630-04 Proxmox host |
| **Currently Used By** | Unknown device (Ubuntu system) |
| **r630-04 Status** | Powered OFF, runs Debian/Proxmox |
| **Conflict Type** | IP address hijacked/misconfigured |

---

## Investigation Results

### Device Using 192.168.11.14

| Property | Value |
|----------|-------|
| **MAC Address** | `bc:24:11:ee:a6:ec` |
| **MAC Vendor** | Proxmox Server Solutions GmbH |
| **OS** | Ubuntu (OpenSSH_8.9p1 Ubuntu-3ubuntu0.13) |
| **SSH Port** | ✅ OPEN |
| **Proxmox Port** | ❌ CLOSED |
| **Cluster Status** | ❌ NOT IN CLUSTER |
| **Container Search** | ❌ NOT FOUND in cluster containers |

### r630-04 Physical Server

| Property | Value |
|----------|-------|
| **Status** | ✅ Powered OFF (confirmed) |
| **OS** | ✅ Debian/Proxmox (confirmed) |
| **Assigned IP** | 192.168.11.14 (should be) |
| **Current IP** | N/A (powered off) |

---

## Root Cause Analysis

### Most Likely Scenario

**Orphaned LXC Container**:
- An LXC container running Ubuntu is using 192.168.11.14
- Container was likely created on r630-04 before it was powered off
- Container may have been:
  - Created with static IP 192.168.11.14
  - Not properly removed when r630-04 was shut down
  - Running on a different host but configured with r630-04's IP

### Alternative Scenarios

1. **Container on Different Host**
   - Container exists on ml110, r630-01, or r630-02
   - Not visible in cluster view (orphaned)
   - Needs to be found and removed/reconfigured

2. **Misconfigured Device**
   - Another device manually configured with this IP
   - Needs to be identified and reconfigured

---

## Resolution Plan

### Step 1: Locate the Container/Device

**Actions**:
```bash
# Check all Proxmox hosts for containers with this MAC or IP
for host in 192.168.11.10 192.168.11.11 192.168.11.12; do
  echo "=== Checking $host ==="
  ssh root@$host "pct list --all"
  ssh root@$host "for vmid in \$(pct list | grep -v VMID | awk '{print \$1}'); do 
    pct config \$vmid 2>/dev/null | grep -E 'bc:24:11:ee:a6:ec|192.168.11.14' && echo \"VMID \$vmid on $host\"; 
  done"
done

# Check QEMU VMs as well
for host in 192.168.11.10 192.168.11.11 192.168.11.12; do
  ssh root@$host "qm list --all"
  ssh root@$host "for vmid in \$(qm list | grep -v VMID | awk '{print \$1}'); do 
    qm config \$vmid 2>/dev/null | grep -E 'bc:24:11:ee:a6:ec|192.168.11.14' && echo \"VMID \$vmid on $host\"; 
  done"
done
```

### Step 2: Resolve the Conflict

**Option A: If Container Found**
1. Identify the container (VMID and host)
2. Stop the container
3. Change container IP to different address (e.g., 192.168.11.28)
4. Restart container with new IP
5. Verify r630-04 can use 192.168.11.14 when powered on

**Option B: If Container Not Found**
1. Check if device is on network segment we haven't checked
2. Check router/switch ARP tables
3. Consider blocking the IP at router level
4. Reassign IP when r630-04 is powered on

### Step 3: Verify Resolution

**Actions**:
1. Power on r630-04
2. Configure r630-04 with IP 192.168.11.14
3. Verify no IP conflict
4. Add r630-04 to cluster
5. Update documentation

---

## Impact Assessment

### Current Impact

- **Low**: Doesn't affect current operations (r630-04 is off)
- **Medium**: Blocks r630-04 from using its assigned IP
- **High**: Will cause network issues when r630-04 is powered on

### Resolution Priority

**Priority**: 🔴 **HIGH**
- Must be resolved before powering on r630-04
- Prevents network conflicts
- Enables proper r630-04 cluster integration

---

## Recommended Actions

### Immediate (Before Powering On r630-04)

1. **Locate the conflicting device**
   - Search all Proxmox hosts thoroughly
   - Check for orphaned containers
   - Check router ARP tables

2. **Resolve the conflict**
   - Stop/remove conflicting container
   - Reassign IP if needed
   - Document the change

3. **Verify IP is available**
   - Confirm 192.168.11.14 is free
   - Test connectivity

### When Powering On r630-04

1. **Configure r630-04**
   - Set IP to 192.168.11.14
   - Verify no conflicts
   - Join to cluster

2. **Verify cluster integration**
   - Check cluster status
   - Verify storage access
   - Test migrations

---

## Next Steps

1. **Execute container search** (see Step 1 above)
2. **Identify conflicting device**
3. **Resolve IP conflict**
4. **Document resolution**
5. **Prepare r630-04 for cluster join**

---

**Last Updated**: 2026-01-05  
**Status**: 🔄 **RESOLUTION IN PROGRESS**  
**Blocking**: r630-04 cannot use assigned IP until conflict resolved
