d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
3e9645274a5f6e2cbc5bae1dff55d3aed0295cbf
proxmox/docs/archive/completion/IP_ADDRESS_REVIEW_COMPLETE.md
defiQUG bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Details
Sync all local changes: docs, config, scripts, submodule refs, verification evidence 
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-21 15:46:06 -08:00

15 KiB
Raw Blame History

Complete IP Address Review - Hardware and VMs

Date: 2025-01-20
Status: Comprehensive Review
Purpose: Complete inventory of all IP addresses for physical hardware and virtual machines/containers

Executive Summary

This document provides a complete review of all IP address assignments across:

  • Physical Hardware: 11 servers + 2 routers + 1 modem
  • Virtual Machines/Containers: 36 VMIDs (31 running, 5 stopped)
  • Network Infrastructure: 1 gateway + 1 Omada controller

Key Findings:

  • ✅ Physical hardware IPs are properly documented and consistent
  • ✅ VM/container IP conflicts have been resolved (per VMID_IP_ADDRESS_LIST.md)
  • ⚠️ Some documentation inconsistencies between files
  • ✅ Public IP block (76.53.10.32/28) fully assigned per Omada Cloud Controller

Physical Hardware IP Addresses

Internal Network (192.168.11.0/24)

IP Address Hostname Type External IP Status Notes
192.168.11.1 er605-1 Router (LAN) 76.53.10.34 ✅ Active Gateway for 192.168.11.0/24
192.168.11.8 omada-controller Controller - ✅ Active Omada Controller (port 8043)
192.168.11.10 ml110 Server 76.53.10.35 ✅ Active Management node (Proxmox)
192.168.11.11 r630-01 (pve) Server 76.53.10.36 ✅ Active Compute node (Proxmox)
192.168.11.12 r630-02 (pve2) Server 76.53.10.37 ✅ Active Compute node (Proxmox)
192.168.11.13 r630-03 Server 76.53.10.38 ✅ Active Compute node (Proxmox)
192.168.11.14 r630-04 Server 76.53.10.39 ✅ Active Compute node (Proxmox)
192.168.11.15 r630-05 Server 76.53.10.40 ✅ Active Compute node (Proxmox)

Note: r630-01 and r630-02 have hostname mismatches (current: pve/pve2, should be: r630-01/r630-02)

SFValley #2 Servers (External IPs Only)

External IP Hostname Internal IP Status Notes
76.53.10.42 omnl-001 Not configured ⏳ Unknown SFValley #2 site
76.53.10.43 omnl-002 Not configured ⏳ Unknown SFValley #2 site
76.53.10.44 panda-000-001 Not configured ⏳ Unknown SFValley #2 site
76.53.10.45 panda-001-001 Not configured ⏳ Unknown SFValley #2 site
76.53.10.46 pan-fusion-000 Not configured ⏳ Unknown SFValley #2 site

Note: SFValley #2 servers have external IPs assigned but internal IPs are not documented. These may be on a different network or not yet configured.

Public IP Block (76.53.10.32/28)

IP Address Assignment Device Site Status
76.53.10.32 Network Address - - Reserved
76.53.10.33 Gateway Spectrum Router - Reserved
76.53.10.34 Gateway WAN er605-1 SFVALLEY ✅ Active
76.53.10.35 Server NAT ml110 SFVALLEY ✅ Assigned
76.53.10.36 Server NAT r630-01 SFVALLEY ✅ Assigned
76.53.10.37 Server NAT r630-02 SFVALLEY ✅ Assigned
76.53.10.38 Server NAT r630-03 SFVALLEY ✅ Assigned
76.53.10.39 Server NAT r630-04 SFVALLEY ✅ Assigned
76.53.10.40 Server NAT r630-05 SFVALLEY ✅ Assigned
76.53.10.41 Gateway WAN er605-2 SFVALLEY_2 ✅ Active
76.53.10.42 Server NAT omnl-001 SFVALLEY_2 ✅ Assigned
76.53.10.43 Server NAT omnl-002 SFVALLEY_2 ✅ Assigned
76.53.10.44 Server NAT panda-000-001 SFVALLEY_2 ✅ Assigned
76.53.10.45 Server NAT panda-001-001 SFVALLEY_2 ✅ Assigned
76.53.10.46 Server NAT pan-fusion-000 SFVALLEY_2 ✅ Assigned
76.53.10.47 Broadcast Address - - Reserved

Summary: All 13 usable IPs (76.53.10.34-46) are assigned per Omada Cloud Controller.

ER605 Router Details

Router External IP Internal IP (LAN) Internal IP (Spectrum) Device MAC WAN MAC Site
er605-1 76.53.10.34 192.168.11.1 192.168.1.177 50:3d:d1:f8:3b:8a 50:3d:d1:f8:3b:8b SFVALLEY
er605-2 76.53.10.41 - - 8c:86:dd:bb:01:80 - SFVALLEY_2

Virtual Machine/Container IP Addresses

Active Containers (Running)

Besu Validators (1000-1004)

VMID IP Address Hostname Status Proxmox Host
1000 192.168.11.100 besu-validator-1 ✅ Running ml110
1001 192.168.11.101 besu-validator-2 ✅ Running ml110
1002 192.168.11.102 besu-validator-3 ✅ Running ml110
1003 192.168.11.103 besu-validator-4 ✅ Running ml110
1004 192.168.11.104 besu-validator-5 ✅ Running ml110

Besu Sentries (1500-1503)

VMID IP Address Hostname Status Proxmox Host
1500 192.168.11.150 besu-sentry-1 ✅ Running ml110
1501 192.168.11.151 besu-sentry-2 ✅ Running ml110
1502 192.168.11.152 besu-sentry-3 ✅ Running ml110
1503 192.168.11.153 besu-sentry-4 ✅ Running ml110

Besu RPC Nodes (2500-2502)

VMID IP Address Hostname Status Proxmox Host
2500 192.168.11.250 besu-rpc-1 ✅ Running ml110
2501 192.168.11.251 besu-rpc-2 ✅ Running ml110
2502 192.168.11.252 besu-rpc-3 ✅ Running ml110

ThirdWeb RPC Nodes (2400-2402)

VMID IP Address Hostname Status Proxmox Host
2400 192.168.11.240 thirdweb-rpc-1 ✅ Running ml110
2401 192.168.11.241 thirdweb-rpc-2 ✅ Running ml110
2402 192.168.11.242 thirdweb-rpc-3 ✅ Running ml110

Named RPC Nodes (2505-2508)

VMID IP Address Hostname Status Proxmox Host
2505 192.168.11.201 besu-rpc-luis-0x8a ✅ Running ml110
2506 192.168.11.202 besu-rpc-luis-0x1 ✅ Running ml110
2507 192.168.11.203 besu-rpc-putu-0x8a ✅ Running ml110
2508 192.168.11.204 besu-rpc-putu-0x1 ✅ Running ml110

DBIS Core Services (10100-10151)

VMID IP Address Hostname Status Proxmox Host Notes
10100 192.168.11.105 dbis-postgres-primary ✅ Running ml110 ✅ Moved from .100
10101 192.168.11.106 dbis-postgres-replica-1 ✅ Running ml110 ✅ Moved from .101
10120 192.168.11.120 dbis-redis ✅ Running ml110 ✅ No conflict
10130 192.168.11.130 dbis-frontend ✅ Running ml110 ✅ No conflict
10150 192.168.11.155 dbis-api-primary ✅ Running ml110 ✅ Moved from .150
10151 192.168.11.156 dbis-api-secondary ✅ Running ml110 ✅ Moved from .151

Note: DBIS containers were moved to resolve IP conflicts with Besu nodes. All conflicts resolved.

Other Services

VMID IP Address Hostname Status Proxmox Host Service
3000 192.168.11.60 ml110 ✅ Running ml110 ML Node
3001 192.168.11.61 ml110 ✅ Running ml110 ML Node
3002 192.168.11.62 ml110 ✅ Running ml110 ML Node
3003 192.168.11.63 ml110 ✅ Running ml110 ML Node
5200 192.168.11.80 cacti-1 ✅ Running ml110 Monitoring
6000 192.168.11.112 fabric-1 ✅ Running ml110 Hyperledger Fabric
6400 192.168.11.64 indy-1 ✅ Running ml110 Hyperledger Indy

Note: VMID 6400 was fixed from invalid IP 192.168.11.0 to 192.168.11.64.

DHCP-Assigned IPs

VMID IP Assignment Hostname Status Proxmox Host Service
3500 DHCP oracle-publisher-1 ✅ Running ml110 Oracle Publisher
3501 DHCP ccip-monitor-1 ✅ Running ml110 CCIP Monitor

Stopped Containers

VMID IP Address Hostname Status Notes
1504 192.168.11.154 besu-sentry-ali ⏸️ Stopped Reserved
2503 192.168.11.253 besu-rpc-ali-0x8a ⏸️ Stopped Reserved
2504 192.168.11.254 besu-rpc-ali-0x1 ⏸️ Stopped Reserved
6201 192.168.11.57 firefly-ali-1 ⏸️ Stopped Reserved

IP Address Allocation Summary

Internal Network (192.168.11.0/24) - Complete Allocation

IP Range Purpose Count Status
.0 Network Address 1 Reserved
.1 Gateway (ER605-1 LAN) 1 ✅ Active
.8 Omada Controller 1 ✅ Active
.10-.15 Physical Servers 6 ✅ Active (ml110, r630-01 to r630-05)
.57 Firefly (stopped) 1 ⏸️ Reserved
.60-.63 ML Nodes (3000-3003) 4 ✅ Active
.64 Indy-1 (6400) 1 ✅ Active (fixed from .0)
.80 Cacti-1 (5200) 1 ✅ Active
.100-.104 Besu Validators (1000-1004) 5 ✅ Active
.105-.106 DBIS PostgreSQL (10100-10101) 2 ✅ Active
.112 Fabric-1 (6000) 1 ✅ Active
.120 DBIS Redis (10120) 1 ✅ Active
.130 DBIS Frontend (10130) 1 ✅ Active
.150-.153 Besu Sentries (1500-1503) 4 ✅ Active
.154 Besu Sentry Ali (stopped) 1 ⏸️ Reserved
.155-.156 DBIS API (10150-10151) 2 ✅ Active
.201-.204 Named RPC (2505-2508) 4 ✅ Active
.240-.242 ThirdWeb RPC (2400-2402) 3 ✅ Active
.250-.252 Besu RPC (2500-2502) 3 ✅ Active
.253-.254 Besu RPC Ali (stopped) 2 ⏸️ Reserved
.255 Broadcast Address 1 Reserved

Total Allocated: ~40 static IPs + 2 DHCP
Total Available: ~213 IPs (excluding reserved .0, .1, .255)

Public IP Block (76.53.10.32/28) - Complete Allocation

IP Range Purpose Count Status
.32 Network Address 1 Reserved
.33 Gateway (Spectrum) 1 Reserved
.34 ER605-1 WAN 1 ✅ Active
.35-.40 SFVALLEY Servers 6 ✅ Assigned
.41 ER605-2 WAN 1 ✅ Active
.42-.46 SFVALLEY_2 Servers 5 ✅ Assigned
.47 Broadcast Address 1 Reserved

Total Allocated: 13 usable IPs (all assigned)
Total Available: 0 IPs

IP Address Conflicts - Status

✅ Resolved Conflicts

According to VMID_IP_ADDRESS_LIST.md, all IP conflicts have been resolved:

  1. 192.168.11.100:

    • Previously: VMID 1000 (besu-validator-1) vs VMID 10100 (dbis-postgres-primary)
    • ✅ Resolved: VMID 10100 moved to 192.168.11.105

  2. 192.168.11.101:

    • Previously: VMID 1001 (besu-validator-2) vs VMID 10101 (dbis-postgres-replica-1)
    • ✅ Resolved: VMID 10101 moved to 192.168.11.106

  3. 192.168.11.150:

    • Previously: VMID 1500 (besu-sentry-1) vs VMID 10150 (dbis-api-primary)
    • ✅ Resolved: VMID 10150 moved to 192.168.11.155

  4. 192.168.11.151:

    • Previously: VMID 1501 (besu-sentry-2) vs VMID 10151 (dbis-api-secondary)
    • ✅ Resolved: VMID 10151 moved to 192.168.11.156

  5. 192.168.11.0 (Invalid IP):

    • Previously: VMID 6400 (indy-1) had invalid network address
    • ✅ Resolved: VMID 6400 moved to 192.168.11.64

⚠️ Potential Issues

  1. Documentation Inconsistency:

    • INFRASTRUCTURE_OVERVIEW_COMPLETE.md still shows DBIS containers with old IPs (conflicts)
    • This document needs to be updated to reflect resolved conflicts

  2. Missing Internal IPs for SFValley #2 Servers:

    • omnl-001, omnl-002, panda-000-001, panda-001-001, pan-fusion-000
    • These have external IPs but no internal IPs documented
    • May be on different network or not yet configured

  3. DHCP Containers:

    • VMIDs 3500 and 3501 use DHCP
    • IP addresses not tracked in static inventory
    • Should verify DHCP pool and lease assignments

Verification Checklist

Physical Hardware

  • All physical server IPs documented
  • All external IPs from Omada Cloud Controller verified
  • ER605 router IPs and MAC addresses documented
  • Spectrum modem information documented
  • Omada controller IP documented

Virtual Machines/Containers

  • All active VMIDs listed with IPs
  • All stopped VMIDs documented
  • IP conflicts resolved (per VMID_IP_ADDRESS_LIST.md)
  • Invalid IPs fixed (VMID 6400)
  • DHCP containers identified

Network Infrastructure

  • Gateway IP documented
  • Public IP block fully allocated
  • Internal network allocation documented
  • VLAN migration status noted (pending)

Documentation Consistency

  • INFRASTRUCTURE_OVERVIEW_COMPLETE.md needs update (DBIS IPs)
  • VMID_IP_ADDRESS_LIST.md is current
  • Physical hardware inventory is current
  • Omada Cloud Controller assignments documented

Recommendations

Immediate Actions

  1. Update INFRASTRUCTURE_OVERVIEW_COMPLETE.md:

    • Update DBIS container IPs to reflect resolved conflicts
    • Change VMID 10100 from 192.168.11.100 to 192.168.11.105
    • Change VMID 10101 from 192.168.11.101 to 192.168.11.106
    • Change VMID 10150 from 192.168.11.150 to 192.168.11.155
    • Change VMID 10151 from 192.168.11.151 to 192.168.11.156

  2. Verify DHCP Assignments:

    • Check DHCP leases for VMIDs 3500 and 3501
    • Document actual IPs assigned
    • Consider moving to static IPs if needed

  3. Document SFValley #2 Server Internal IPs:

    • Determine if these servers are on the same network (192.168.11.0/24)
    • Document internal IPs if they exist
    • Update inventory if they're on a different network

Short-term Actions

  1. IP Allocation Tracking:

    • Create automated IP conflict detection
    • Implement pre-deployment IP validation
    • Maintain centralized IP allocation registry

  2. Network Documentation:

    • Document VLAN migration plan
    • Update IP assignments when VLANs are implemented
    • Create network topology diagram

  3. Monitoring:

    • Set up IP address monitoring
    • Alert on duplicate IPs
    • Track IP usage trends

Related Documentation

Last Updated: 2025-01-20
Review Status: Complete
Next Review: After VLAN migration or significant infrastructure changes

Reference in New Issue View Git Blame Copy Permalink