Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- 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>
63 lines
3.1 KiB
Markdown
63 lines
3.1 KiB
Markdown
# Configuration Decision Tree
|
||
|
||
**Last Updated:** 2026-01-31
|
||
**Document Version:** 1.0
|
||
**Status:** Active Documentation
|
||
|
||
---
|
||
|
||
## Overview
|
||
|
||
Use this tree to choose the right configuration path (which VLAN, which service, deployment path).
|
||
|
||
---
|
||
|
||
## Which VLAN?
|
||
|
||
1. **Management / admin / Proxmox hosts?** → VLAN 11 (192.168.11.0/24). See [NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md).
|
||
2. **Besu validator?** → VLAN 110 (10.110.0.0/24). Planned; currently flat LAN.
|
||
3. **Besu sentry?** → VLAN 111 (10.111.0.0/24). Planned.
|
||
4. **Besu RPC / gateway?** → VLAN 112 (10.112.0.0/24). Planned.
|
||
5. **CCIP Commit?** → VLAN 132 (10.132.0.0/24). Planned.
|
||
6. **CCIP Execute?** → VLAN 133 (10.133.0.0/24). Planned.
|
||
7. **CCIP RMN?** → VLAN 134 (10.134.0.0/24). Planned.
|
||
8. **Sankofa/Phoenix service?** → VLAN 160 (10.160.0.0/22). Planned.
|
||
9. **Sovereign tenant?** → VLAN 200–203. Planned.
|
||
|
||
**Current:** Most services are on flat LAN 192.168.11.0/24 (VLAN 11). See [NETWORK_CONFIGURATION_MASTER.md](../11-references/NETWORK_CONFIGURATION_MASTER.md).
|
||
|
||
---
|
||
|
||
## Which Service / VMID Range?
|
||
|
||
| Service type | VMID range | Doc |
|
||
|--------------|------------|-----|
|
||
| Infrastructure | 100–130 | NETWORK_CONFIGURATION_MASTER |
|
||
| Besu validators | 1000–1499 | VMID_ALLOCATION_FINAL |
|
||
| Besu sentries | 1500–1999 | VMID_ALLOCATION_FINAL |
|
||
| RPC nodes | 2101, 2201, 2301–2308, 2400–2403 | NETWORK_CONFIGURATION_MASTER |
|
||
| Explorer | 5000 | NETWORK_CONFIGURATION_MASTER |
|
||
| NPMplus | 10233 | NETWORK_CONFIGURATION_MASTER |
|
||
| CCIP | 5400–5599 | CCIP_DEPLOYMENT_SPEC |
|
||
|
||
**See:** [02-architecture/VMID_ALLOCATION_FINAL.md](../02-architecture/VMID_ALLOCATION_FINAL.md).
|
||
|
||
---
|
||
|
||
## Deployment Path
|
||
|
||
1. **New deployment from scratch?** → [01-getting-started/PREREQUISITES.md](../01-getting-started/PREREQUISITES.md) → [03-deployment/DEPLOYMENT_READINESS.md](../03-deployment/DEPLOYMENT_READINESS.md) → [02-architecture/ORCHESTRATION_DEPLOYMENT_GUIDE.md](../02-architecture/ORCHESTRATION_DEPLOYMENT_GUIDE.md).
|
||
2. **Validated set only?** → [03-deployment/VALIDATED_SET_DEPLOYMENT_GUIDE.md](../03-deployment/VALIDATED_SET_DEPLOYMENT_GUIDE.md) → [12-quick-reference/VALIDATED_SET_QUICK_REFERENCE.md](../12-quick-reference/VALIDATED_SET_QUICK_REFERENCE.md).
|
||
3. **Production vs staging?** → Use VMID ranges and VLANs per [02-architecture/NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md); staging can share flat LAN with reserved VMIDs.
|
||
4. **Which components?** → See [03-deployment/OPERATIONAL_RUNBOOKS.md](../03-deployment/OPERATIONAL_RUNBOOKS.md) and [MASTER_INDEX.md](../MASTER_INDEX.md).
|
||
|
||
---
|
||
|
||
## Related Documentation
|
||
|
||
- [NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md) - Full network architecture
|
||
- [NETWORK_CONFIGURATION_MASTER.md](../11-references/NETWORK_CONFIGURATION_MASTER.md) - IP and VMID reference
|
||
- [VMID_ALLOCATION_FINAL.md](../02-architecture/VMID_ALLOCATION_FINAL.md) - VMID registry
|
||
- [ORCHESTRATION_DEPLOYMENT_GUIDE.md](../02-architecture/ORCHESTRATION_DEPLOYMENT_GUIDE.md) - Deployment workflow
|
||
- [TROUBLESHOOTING_FAQ.md](../09-troubleshooting/TROUBLESHOOTING_FAQ.md) - Troubleshooting flow
|