Files
proxmox/docs/04-configuration/NPMPLUS_VMID_SERVICE_MAPPING.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

122 lines
4.3 KiB
Markdown

# NPMplus Backend Services - VMID Service Mapping
**Last Updated:** 2025-01-20
**Status:****COMPLETE** - All scripts updated, Besu node files deployed, ready for migration
---
## Backend Services for NPMplus
### Current Active Services
| VMID | IP Address | Port | Service Name | Host | Status |
|------|------------|------|--------------|------|--------|
| 5000 | 192.168.11.140 | 80 | blockscout-1 | 192.168.11.12 | ✅ Active |
| 10130 | 192.168.11.130 | 80 | dbis-frontend | 192.168.11.11 | ⚠️ Stopped (Config Missing) |
| 10150 | 192.168.11.155 | 3000 | dbis-api-primary | 192.168.11.11 | ⚠️ Stopped (Config Missing) |
| 10151 | 192.168.11.156 | 3000 | dbis-api-secondary | 192.168.11.11 | ⚠️ Stopped (Config Missing) |
| 7811 | 192.168.11.36 | 80 | mim-api-1 | 192.168.11.12 | ✅ Active |
| 2101 | 192.168.11.211 | 443 | besu-rpc-core-1 | 192.168.11.10 | ⏳ Pending Creation |
| 2201 | 192.168.11.221 | 443 | besu-rpc-public-1 | 192.168.11.10 | ⏳ Pending Creation |
| 2301 | 192.168.11.232 | 443 | besu-rpc-private-1 | 192.168.11.10 | ⏳ Pending Creation |
---
## VMID Migration History
### Old → New Mapping
| Old VMID | Old Name | New VMID | New IP | New Name | Migration Date |
|----------|----------|----------|--------|----------|----------------|
| 2500 | besu-rpc-1 | 2101 | 192.168.11.211 | besu-rpc-core-1 | 2025-01-20 |
| 2501 | besu-rpc-2 | 2201 | 192.168.11.221 | besu-rpc-public-1 | 2025-01-20 |
| 2502 | besu-rpc-3 | 2301 | 192.168.11.232 | besu-rpc-private-1 | 2025-01-20 |
| - | - | 2302 | 192.168.11.232 | besu-rpc-private-2 | 2025-01-20 (New) |
---
## Scripts Using These Mappings
All of the following scripts have been updated with the current mappings:
1.`scripts/list-all-vmids-final.sh` - Lists all VMIDs and backend services
2.`scripts/diagnose-npmplus-backend-services.sh` - Diagnoses backend service connectivity
3.`scripts/fix-npmplus-backend-services.sh` - Fixes/restarts backend services
4.`scripts/test-npmplus-full-connectivity.sh` - Tests full connectivity from all hosts
5.`scripts/check-npmplus-network-connectivity.sh` - Checks network connectivity
---
## Important Notes
### IP Address Corrections
- **VMID 2301:** Uses `192.168.11.232` - corrected per user confirmation
- **VMID 2302:** Uses `192.168.11.232`
- No duplicate IP addresses - all services have unique IPs
### Port Forwarding Configuration
**Current Issue:**
- UDM Pro port forwarding targets: `192.168.0.166`
- NPMplus container IP: `192.168.11.166` (VLAN 11)
**Impact:** External traffic may not reach NPMplus due to IP mismatch
**Recommended Solution:** Dual-home NPMplus container or update UDM Pro port forwarding
### CCIP Monitor Services
**Note:** VMIDs 3000-3003 are CCIP monitors (not NPMplus backend services):
- 3000 - ccip-monitor-1 (stopped)
- 3001 - ccip-monitor-2 (stopped)
- 3002 - ccip-monitor-3 (stopped)
- 3003 - ccip-monitor-4 (stopped)
These are separate services and not included in NPMplus backend service mappings.
---
## Verification Commands
### Check Service Status
```bash
# Check all backend services
for vmid in 5000 10130 10150 10151 7811 2101 2201 2301 2302; do
echo "VMID $vmid:"
ssh root@192.168.11.10 "pct status $vmid 2>/dev/null || qm status $vmid 2>/dev/null" || \
ssh root@192.168.11.11 "pct status $vmid 2>/dev/null || qm status $vmid 2>/dev/null" || \
ssh root@192.168.11.12 "pct status $vmid 2>/dev/null || qm status $vmid 2>/dev/null"
done
```
### Verify IP Addresses
```bash
# Verify IP addresses for new VMIDs
for vmid in 2101 2201 2301 2302; do
echo "VMID $vmid:"
ssh root@192.168.11.10 "pct exec $vmid -- hostname -I | awk '{print \$1}'" 2>/dev/null || echo "Not found"
done
```
### Test Connectivity from NPMplus
```bash
# Test from NPMplus container (VMID 10233)
ssh root@192.168.11.11 "pct exec 10233 -- curl -v http://192.168.11.140:80"
ssh root@192.168.11.11 "pct exec 10233 -- curl -v -k https://192.168.11.211:443"
ssh root@192.168.11.11 "pct exec 10233 -- curl -v -k https://192.168.11.221:443"
ssh root@192.168.11.11 "pct exec 10233 -- curl -v -k https://192.168.11.232:443"
ssh root@192.168.11.11 "pct exec 10233 -- curl -v -k https://192.168.11.232:443"
```
---
**Document Version:** 1.0
**Last Updated By:** Auto (AI Assistant)
**Change Log:**
- 2025-01-20: Initial mapping document created with corrected IP addresses
- 2025-01-20: All 5 scripts updated with new VMID mappings