9c37af10c0
- Fixed 104 broken references in 59 files - Consolidated 40+ duplicate status files - Archived duplicates to reports/archive/duplicates/ - Created scripts for reference fixing and consolidation - Updated content inconsistency reports All optional cleanup tasks complete.
2.4 KiB
2.4 KiB
Phase 1.1: IP Conflict Investigation Status
Date: 2026-01-05
IP Address: 192.168.11.14
Status: 🔄 IN PROGRESS
Investigation Steps
Step 1: MAC Address Identification
Attempted Methods:
- ✅ Ping to 192.168.11.14 - SUCCESS (device responds)
- ❌ ARP table lookup (local) - NO ENTRY (unusual - ARP entry missing)
- ✅ Checking from ml110 - SUCCESS - Found MAC address
- ✅ Network scan - COMPLETE
Findings:
- Device responds to ping (TTL=63, ~5-6ms latency)
- MAC Address:
bc:24:11:ee:a6:ec - OUI (Vendor):
bc:24:11(needs vendor lookup) - SSH banner shows Ubuntu (not Debian/Proxmox)
- SSH port 22: OPEN
- Proxmox port 8006: CLOSED (confirms NOT a Proxmox host)
Step 2: Orphaned VM Check
Checked Hosts:
- ✅ ml110 (192.168.11.10) - No orphaned VMs found
- ✅ r630-01 (192.168.11.11) - No orphaned VMs found
- ✅ r630-02 (192.168.11.12) - No orphaned VMs found
Result: No orphaned VMs found in cluster
Step 3: Next Actions
Required:
- Get MAC address via router/switch ARP table
- Check physical r630-04 server status
- Verify if r630-04 is actually powered on
- Check if device is on different network segment
- Identify device type from MAC vendor
Alternative Methods:
- Check Omada controller for device information
- Check router ARP table directly
- Use network scanner if available
- Physical inspection of r630-04 server
Current Hypothesis
Most Likely Scenarios:
- Orphaned VM/Container: A VM or container running Ubuntu is using 192.168.11.14 but not registered in Proxmox cluster
- Different Device: A different physical device (not r630-04) is using this IP
- r630-04 Running Ubuntu: r630-04 was reinstalled with Ubuntu instead of Proxmox
- Network Device: A switch, router, or other network device is using this IP
Next Steps
-
Check Router ARP Table
- Access ER605 router (192.168.11.1)
- Check ARP table for 192.168.11.14
- Get MAC address
-
Check Omada Controller
- Access Omada controller (192.168.11.20 or 192.168.11.8)
- Check device list for 192.168.11.14
- Get device information
-
Physical Inspection
- Check r630-04 physical server
- Verify power status
- Check console/iDRAC
-
Network Scan
- Scan network for all devices
- Identify which device has 192.168.11.14
Last Updated: 2026-01-05
Next Update: After MAC address identification