# NPMplus VMID Changes Review - Current vs Planned

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

---

**Date:** 2025-01-20  
**Review Status:** 📋 **PENDING VERIFICATION**

---

## Current State (Verified)

### Active VMIDs on 192.168.11.10:
- **2400** - thirdweb-rpc-1 (running)
- **2401** - thirdweb-rpc-2 (running)
- **2402** - thirdweb-rpc-3 (running)
- **2500** - besu-rpc-1 (running)
- **2501** - besu-rpc-2 (running) ← Currently used in scripts
- **2502** - besu-rpc-3 (running) ← Currently used in scripts
- **2503** - besu-rpc-ali-0x8a (running)
- **2504** - besu-rpc-ali-0x1 (running)
- **2505** - besu-rpc-luis-0x8a (running)
- **2506** - besu-rpc-luis-0x1 (running)
- **2507** - besu-rpc-putu-0x8a (running)
- **2508** - besu-rpc-putu-0x1 (running)

### CCIP Monitor Services on 192.168.11.11:
- **3000** - ml110 (stopped) ← Should be renamed "ccip-monitor-1"
- **3001** - ml110 (stopped) ← Should be renamed "ccip-monitor-2"
- **3002** - ml110 (stopped) ← Should be renamed "ccip-monitor-3"
- **3003** - ml110 (stopped) ← Should be renamed "ccip-monitor-4"

---

## Planned Changes (Per User Request)

### Backend Services for NPMplus - VMID Remapping:

| Current VMID | Current Name | Planned VMID | Planned IP | Planned Name | Notes |
|--------------|--------------|--------------|------------|--------------|-------|
| 2500 | besu-rpc-1 | 2101 | 192.168.11.211 | besu-rpc-core-1 | Need to verify new VMID exists |
| 2501 | besu-rpc-2 | 2201 | 192.168.11.221 | besu-rpc-public-1 | Need to verify new VMID exists |
| 2502 | besu-rpc-3 | 2301 | 192.168.11.231 | besu-rpc-private-1 | ✅ Verified - IP corrected |
| - | - | 2302 | 192.168.11.232 | besu-rpc-private-2 | ✅ NEW Service |

### Thirdweb RPC Services - VMID Remapping:

| Current VMID | Current Name | Planned VMID | Planned IP | Planned Name |
|--------------|--------------|--------------|------------|--------------|
| 2400 | thirdweb-rpc-1 | 2401 | 192.168.11.241 | besu-rpc-thirdweb-0x8a-1 |
| 2401 | thirdweb-rpc-2 | 2402 | 192.168.11.242 | besu-rpc-thirdweb-0x8a-2 |
| 2402 | thirdweb-rpc-3 | 2403 | 192.168.11.243 | besu-rpc-thirdweb-0x8a-3 |

### Tenant RPC Services - VMID Remapping:

| Current VMID | Planned VMID | Planned IP | Planned Name |
|--------------|--------------|------------|--------------|
| 2503 | 2303 | 192.168.11.233 | besu-rpc-ali-0x8a |
| 2504 | 2304 | 192.168.11.234 | besu-rpc-ali-0x1 |
| 2505 | 2305 | 192.168.11.235 | besu-rpc-luis-0x8a |
| 2506 | 2306 | 192.168.11.236 | besu-rpc-luis-0x1 |
| 2507 | 2307 | 192.168.11.237 | besu-rpc-putu-0x8a |
| 2508 | 2308 | 192.168.11.238 | besu-rpc-putu-0x1 |

---

## ⚠️ Critical Issues to Resolve

### Issue 1: ~~Duplicate IP Address~~ ✅ RESOLVED

**Status:** ✅ **RESOLVED**
- VMID 2301 uses IP `192.168.11.231:443` (corrected)
- VMID 2302 uses IP `192.168.11.232:443`
- No duplicate IP issue - both have unique addresses

### Issue 2: New VMIDs Don't Exist Yet

**Status:** New VMIDs (2101, 2201, 2301-2308, 2401-2403) are **not found** on the system

**Questions:**
1. Have these VMIDs been created yet?
2. Should we wait for migration before updating scripts?
3. Or should scripts be updated now to prepare for migration?

### Issue 3: Port Forwarding Mismatch

**Current:**
- UDM Pro port forwarding: `192.168.0.166`
- NPMplus container IP: `192.168.11.166` (VLAN 11)

**Impact:** External traffic won't reach NPMplus

**Solutions:**
1. Dual-home NPMplus (add 192.168.0.166 interface)
2. Update UDM Pro to forward to 192.168.11.166
3. Configure routing between networks

---

## Files Requiring Updates

### Files to Update (5 scripts):

1. `scripts/list-all-vmids-final.sh`
   - **Line 127-135:** Backend services array
   - **Change:** Replace 2501/2502 with 2101/2201/2301/2302

2. `scripts/diagnose-npmplus-backend-services.sh`
   - **Line 26-34:** Backend services array
   - **Change:** Replace 2501/2502 IPs with new IPs

3. `scripts/fix-npmplus-backend-services.sh`
   - **Line 27-35:** VMID_HOSTS array (replace 2501/2502 with 2101/2201/2301/2302)
   - **Line 67-75:** BACKEND_SERVICES array (update IPs)

4. `scripts/test-npmplus-full-connectivity.sh`
   - **Line 31-39:** Backend services array
   - **Change:** Replace 2501/2502 with new mappings

5. `scripts/check-npmplus-network-connectivity.sh`
   - **Line 115:** Backend services array
   - **Change:** Replace 2501/2502 with new mappings

---

## Detailed Change Specifications

### Change Pattern for All Files:

**Remove these entries:**
```bash
["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
# OR
["192.168.11.251:443"]="VMID 2501 (besu-rpc-2)"             # OLD
["192.168.11.252:443"]="VMID 2502 (besu-rpc-3)"             # OLD
```

**Add these entries:**
```bash
["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.232:443|besu-rpc-private-1|192.168.11.10"      # NEW
# ⚠️ NOTE: 2302 has same IP - need to handle duplicate key
```

**For IP-based arrays (diagnose/test scripts), need alternative approach:**
```bash
# Option 1: Use unique identifier (if different ports)
["192.168.11.232:443"]="VMID 2301 (besu-rpc-private-1)"
["192.168.11.232:8443"]="VMID 2302 (besu-rpc-private-2)"  # Different port?

# Option 2: Combine into single entry
["192.168.11.232:443"]="VMID 2301/2302 (besu-rpc-private-1/2)"

# Option 3: Use VMID as key instead
["2301"]="192.168.11.232:443|besu-rpc-private-1"
["2302"]="192.168.11.232:443|besu-rpc-private-2"
```

---

## Recommended Actions

### Before Applying Changes:

1. ✅ **Verify New VMIDs Exist**
   ```bash
   ssh root@192.168.11.10 "pct list | grep -E '^2101|^2201|^2301|^2302'"
   ```

2. ✅ **Verify IP Addresses**
   ```bash
   for vmid in 2101 2201 2301 2302; do
       ssh root@192.168.11.10 "pct exec $vmid -- hostname -I | awk '{print \$1}'" 2>/dev/null || echo "$vmid: Not found"
   done
   ```

3. ✅ **Resolve Duplicate IP Issue**
   - Confirm if 2301 and 2302 share same IP
   - Decide on approach (different port, combine, or different IP)

4. ✅ **Port Forwarding Fix**
   - Decide on dual-homing vs. routing solution
   - Implement chosen solution

### After Verification:

1. Update all 5 scripts with new mappings
2. Test updated scripts
3. Update documentation
4. Fix port forwarding configuration

---

## Questions for User

1. **Timing:** Are the new VMIDs (2101, 2201, 2301-2308, etc.) already created, or should scripts be updated now in preparation for migration?

2. **Duplicate IP:** VMID 2301 and 2302 both use `192.168.11.232:443`. How should this be handled in scripts?
   - Different ports?
   - Different IP?
   - Combined entry?

3. **Port Forwarding:** Should we fix the port forwarding mismatch now (192.168.0.166 vs 192.168.11.166)?

4. **Scope:** Should we update only backend service mappings for NPMplus, or also update all the thirdweb/tenant mappings in the listing script?

---

**Status:** ✅ **CHANGES APPLIED** - All 5 scripts updated with corrected mappings

**Applied Changes:**
- ✅ All 5 scripts updated (list-all-vmids-final.sh, diagnose-npmplus-backend-services.sh, fix-npmplus-backend-services.sh, test-npmplus-full-connectivity.sh, check-npmplus-network-connectivity.sh)
- ✅ VMID 2301 corrected to use 192.168.11.231 (not 192.168.11.232)
- ✅ VMID 2302 confirmed to use 192.168.11.232
- ✅ No duplicate IP issues

**Review Document Location:** `docs/04-configuration/NPMPLUS_VMID_CHANGES_REVIEW.md`