d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b7eebb87b33ea4af3efe689c5a0469df4a134313
proxmox/docs/04-configuration/NPMPLUS_VMID_MAPPING_CHANGES_REVIEW.md
defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers. 
- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor
2026-04-12 06:12:20 -07:00

12 KiB
Raw Blame History

NPMplus VMID Mapping Changes - Review Document

Historical note: This review captures pre-change mapping analysis from the RPC migration window. It intentionally includes old and proposed VMID mappings. Keep it as planning history, not as live configuration guidance. For current values, use docs/04-configuration/ALL_VMIDS_ENDPOINTS.md and docs/04-configuration/RPC_ENDPOINTS_MASTER.md.

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Date: 2025-01-20
Purpose: Review all required changes before applying updates

Summary of Changes

1. Backend Services VMID Updates

Current (Old) → New Mapping:

Old VMID Old IP New VMID New IP Service Name Status
2500 192.168.11.250 2101 192.168.11.211 besu-rpc-core-1 ✅ Active
2501 192.168.11.251 2201 192.168.11.221 besu-rpc-public-1 ✅ Active
2502 192.168.11.252 2301 192.168.11.231 besu-rpc-private-1 ✅ Active (IP corrected)
- - 2302 192.168.11.232 besu-rpc-private-2 ✅ New Service

Thirdweb RPC Services:

Old VMID Old IP New VMID New IP Service Name
2400 192.168.11.240 2401 192.168.11.241 besu-rpc-thirdweb-0x8a-1
2401 192.168.11.241 2402 192.168.11.242 besu-rpc-thirdweb-0x8a-2
2402 192.168.11.242 2403 192.168.11.243 besu-rpc-thirdweb-0x8a-3

Tenant RPC Services:

Old VMID Old IP New VMID New IP Service Name
2503 192.168.11.253 2303 192.168.11.233 besu-rpc-ali-0x8a
2504 192.168.11.254 2304 192.168.11.234 besu-rpc-ali-0x1
2505 192.168.11.201 2305 192.168.11.235 besu-rpc-luis-0x8a
2506 192.168.11.202 2306 192.168.11.236 besu-rpc-luis-0x1
2507 192.168.11.203 2307 192.168.11.237 besu-rpc-putu-0x8a
2508 192.168.11.204 2308 192.168.11.238 besu-rpc-putu-0x1

2. Port Forwarding Configuration

Current Configuration:

  • UDM Pro forwards ports 80/443 to: 192.168.0.166
  • NPMplus container is on: 192.168.11.166 (VLAN 11)

Issue: Port forwarding targets wrong IP address

Solution: Dual-home NPMplus container or update UDM Pro port forwarding

3. CCIP Monitor Services

Correction:

  • VMIDs 3000-3003 are CCIP monitors, not "ml110" backups
  • These should be renamed/identified as CCIP monitor services

Files Requiring Updates

File 1: scripts/list-all-vmids-final.sh

Current Backend Services (lines 127-135):

declare -A BACKEND_SERVICES=(
    ["5000"]="192.168.11.140:80|blockscout-1|192.168.11.12"
    ["10130"]="192.168.11.130:80|dbis-frontend|192.168.11.11"
    ["10150"]="192.168.11.155:3000|dbis-api-primary|192.168.11.11"
    ["10151"]="192.168.11.156:3000|dbis-api-secondary|192.168.11.11"
    ["7811"]="192.168.11.36:80|mim-api-1|192.168.11.12"
    ["2501"]="192.168.11.251:443|besu-rpc-2|192.168.11.10"      # ❌ OLD
    ["2502"]="192.168.11.252:443|besu-rpc-3|192.168.11.10"      # ❌ OLD
)

Should Be:

declare -A BACKEND_SERVICES=(
    ["5000"]="192.168.11.140:80|blockscout-1|192.168.11.12"
    ["10130"]="192.168.11.130:80|dbis-frontend|192.168.11.11"
    ["10150"]="192.168.11.155:3000|dbis-api-primary|192.168.11.11"
    ["10151"]="192.168.11.156:3000|dbis-api-secondary|192.168.11.11"
    ["7811"]="192.168.11.36:80|mim-api-1|192.168.11.12"
    ["2101"]="192.168.11.211:443|besu-rpc-core-1|192.168.11.10"         # ✅ NEW
    ["2201"]="192.168.11.221:443|besu-rpc-public-1|192.168.11.10"       # ✅ NEW
    ["2301"]="192.168.11.231:443|besu-rpc-private-1|192.168.11.10"      # ✅ NEW (IP corrected)
    ["2302"]="192.168.11.232:443|besu-rpc-private-2|192.168.11.10"      # ✅ NEW (ADD)
)

Impact: ✅ Low - Only affects display of backend services summary

File 2: scripts/diagnose-npmplus-backend-services.sh

Current Backend Services (lines 26-34):

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.251:443"]="VMID 2501 (besu-rpc-2)"      # ❌ OLD
    ["192.168.11.252:443"]="VMID 2502 (besu-rpc-3)"      # ❌ OLD
)

Should Be:

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.211:443"]="VMID 2101 (besu-rpc-core-1)"         # ✅ NEW
    ["192.168.11.221:443"]="VMID 2201 (besu-rpc-public-1)"       # ✅ NEW
    ["192.168.11.231:443"]="VMID 2301 (besu-rpc-private-1)"      # ✅ NEW
    ["192.168.11.232:443"]="VMID 2302 (besu-rpc-private-2)"      # ✅ NEW (ADD)
)

Note: ✅ RESOLVED - VMID 2301 uses 192.168.11.231 (corrected), VMID 2302 uses 192.168.11.232. No duplicate key issue.

Impact: ⚠️ MEDIUM - Affects connectivity diagnostics, will test wrong IPs

File 3: scripts/fix-npmplus-backend-services.sh

Current VMID Hosts (lines 27-35):

declare -A VMID_HOSTS=(
    ["5000"]="192.168.11.12"
    ["10130"]="192.168.11.11"
    ["10150"]="192.168.11.11"
    ["10151"]="192.168.11.11"
    ["7811"]="192.168.11.12"
    ["2501"]="192.168.11.10"      # ❌ OLD
    ["2502"]="192.168.11.10"      # ❌ OLD
)

Should Be:

declare -A VMID_HOSTS=(
    ["5000"]="192.168.11.12"
    ["10130"]="192.168.11.11"
    ["10150"]="192.168.11.11"
    ["10151"]="192.168.11.11"
    ["7811"]="192.168.11.12"
    ["2101"]="192.168.11.10"      # ✅ NEW
    ["2201"]="192.168.11.10"      # ✅ NEW
    ["2301"]="192.168.11.10"      # ✅ NEW
    ["2302"]="192.168.11.10"      # ✅ NEW (ADD)
)

Current Backend Services (lines 67-75):

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.251:443"]="VMID 2501 (besu-rpc-2)"      # ❌ OLD
    ["192.168.11.252:443"]="VMID 2502 (besu-rpc-3)"      # ❌ OLD
)

Should Be:

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.211:443"]="VMID 2101 (besu-rpc-core-1)"         # ✅ NEW
    ["192.168.11.221:443"]="VMID 2201 (besu-rpc-public-1)"       # ✅ NEW
    ["192.168.11.231:443"]="VMID 2301 (besu-rpc-private-1)"      # ✅ NEW
    ["192.168.11.232:443"]="VMID 2302 (besu-rpc-private-2)"      # ✅ NEW (ADD)
)

Impact: ⚠️ MEDIUM - Affects service startup and connectivity verification

File 4: scripts/test-npmplus-full-connectivity.sh

Current Backend Services (lines 31-39):

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1) on 192.168.11.12"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend) on 192.168.11.11"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary) on 192.168.11.11"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary) on 192.168.11.11"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1) on 192.168.11.12"
    ["192.168.11.251:443"]="VMID 2501 (besu-rpc-2) on 192.168.11.10"      # ❌ OLD
    ["192.168.11.252:443"]="VMID 2502 (besu-rpc-3) on 192.168.11.10"      # ❌ OLD
)

Should Be:

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1) on 192.168.11.12"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend) on 192.168.11.11"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary) on 192.168.11.11"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary) on 192.168.11.11"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1) on 192.168.11.12"
    ["192.168.11.211:443"]="VMID 2101 (besu-rpc-core-1) on 192.168.11.10"         # ✅ NEW
    ["192.168.11.221:443"]="VMID 2201 (besu-rpc-public-1) on 192.168.11.10"       # ✅ NEW
    ["192.168.11.231:443"]="VMID 2301 (besu-rpc-private-1) on 192.168.11.10"      # ✅ NEW (IP corrected)
    ["192.168.11.232:443"]="VMID 2302 (besu-rpc-private-2) on 192.168.11.10"      # ✅ NEW (ADD)
)

Impact: ⚠️ MEDIUM - Affects connectivity testing, will test wrong services

File 5: scripts/check-npmplus-network-connectivity.sh

Current Backend Services (around line 115):

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.251:443"]="VMID 2501 (besu-rpc-2)"      # ❌ OLD
    ["192.168.11.252:443"]="VMID 2502 (besu-rpc-3)"      # ❌ OLD
)

Should Be:

declare -A BACKEND_SERVICES=(
    ["192.168.11.140:80"]="VMID 5000 (blockscout-1)"
    ["192.168.11.130:80"]="VMID 10130 (dbis-frontend)"
    ["192.168.11.155:3000"]="VMID 10150 (dbis-api-primary)"
    ["192.168.11.156:3000"]="VMID 10151 (dbis-api-secondary)"
    ["192.168.11.36:80"]="VMID 7811 (mim-api-1)"
    ["192.168.11.211:443"]="VMID 2101 (besu-rpc-core-1)"         # ✅ NEW
    ["192.168.11.221:443"]="VMID 2201 (besu-rpc-public-1)"       # ✅ NEW
    ["192.168.11.231:443"]="VMID 2301 (besu-rpc-private-1)"      # ✅ NEW
    ["192.168.11.232:443"]="VMID 2302 (besu-rpc-private-2)"      # ✅ NEW (ADD)
)

Impact: ⚠️ MEDIUM - Affects network connectivity diagnostics

Important Notes

✅ Issue Resolved: Duplicate IP Address

Status: ✅ RESOLVED

  • VMID 2301 uses IP 192.168.11.231:443 (corrected per user confirmation)
  • VMID 2302 uses IP 192.168.11.232:443
  • No duplicate key issue - both have unique IP addresses
  • All scripts updated with correct mappings

Port Forwarding Issue

Current State:

  • UDM Pro forwards to: 192.168.0.166
  • NPMplus container: 192.168.11.166

This mismatch needs to be resolved for external access to work.

Change Summary

Files to Update: 5 scripts

  1. ✅ scripts/list-all-vmids-final.sh - Backend services summary
  2. ⚠️ scripts/diagnose-npmplus-backend-services.sh - Diagnosis tests
  3. ⚠️ scripts/fix-npmplus-backend-services.sh - Service fixes (2 mappings)
  4. ⚠️ scripts/test-npmplus-full-connectivity.sh - Connectivity tests
  5. ⚠️ scripts/check-npmplus-network-connectivity.sh - Network diagnostics

Changes Required:

Remove:

  • VMID 2501 → 192.168.11.251 (besu-rpc-2)
  • VMID 2502 → 192.168.11.252 (besu-rpc-3)

Add:

  • VMID 2101 → 192.168.11.211 (besu-rpc-core-1)
  • VMID 2201 → 192.168.11.221 (besu-rpc-public-1)
  • VMID 2301 → 192.168.11.231 (besu-rpc-private-1) ✅ IP CORRECTED
  • VMID 2302 → 192.168.11.232 (besu-rpc-private-2) ✅

Questions Before Applying Changes

  1. ✅ VMID 2301 IP Confirmed: VMID 2301 uses 192.168.11.231 (not 232) - corrected

  2. Port Forwarding: Should we:

    • Dual-home NPMplus (add 192.168.0.166 interface)?
    • Update UDM Pro to forward to 192.168.11.166?
    • Verify current routing between networks?

  3. CCIP Monitors: Should VMIDs 3000-3003 be included in any NPMplus backend service lists, or are they separate?

Status: ✅ COMPLETE - All changes applied to 5 scripts with corrected IP addresses

Applied Changes:

  • ✅ All 5 scripts updated with new VMID mappings
  • ✅ VMID 2301 IP corrected to 192.168.11.231 (confirmed by user)
  • ✅ VMID 2302 confirmed to use 192.168.11.232
  • ✅ No duplicate IP issues
Reference in New Issue View Git Blame Copy Permalink