cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
88 lines
2.4 KiB
Markdown
88 lines
2.4 KiB
Markdown
# 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**:
|
|
1. ✅ Ping to 192.168.11.14 - **SUCCESS** (device responds)
|
|
2. ❌ ARP table lookup (local) - **NO ENTRY** (unusual - ARP entry missing)
|
|
3. ✅ Checking from ml110 - **SUCCESS** - Found MAC address
|
|
4. ✅ 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**:
|
|
1. Get MAC address via router/switch ARP table
|
|
2. Check physical r630-04 server status
|
|
3. Verify if r630-04 is actually powered on
|
|
4. Check if device is on different network segment
|
|
5. 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**:
|
|
1. **Orphaned VM/Container**: A VM or container running Ubuntu is using 192.168.11.14 but not registered in Proxmox cluster
|
|
2. **Different Device**: A different physical device (not r630-04) is using this IP
|
|
3. **r630-04 Running Ubuntu**: r630-04 was reinstalled with Ubuntu instead of Proxmox
|
|
4. **Network Device**: A switch, router, or other network device is using this IP
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. **Check Router ARP Table**
|
|
- Access ER605 router (192.168.11.1)
|
|
- Check ARP table for 192.168.11.14
|
|
- Get MAC address
|
|
|
|
2. **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
|
|
|
|
3. **Physical Inspection**
|
|
- Check r630-04 physical server
|
|
- Verify power status
|
|
- Check console/iDRAC
|
|
|
|
4. **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
|