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>
204 lines
5.0 KiB
Markdown
204 lines
5.0 KiB
Markdown
# UDM Pro - Proxmox Cluster Configuration
|
|
|
|
**Last Updated:** 2026-01-14
|
|
**Status:** ✅ ml110 accessible, other hosts to be verified
|
|
|
|
---
|
|
|
|
## Proxmox Cluster Overview
|
|
|
|
### Cluster Members
|
|
|
|
| Host Name | IP Address | Status | Web UI | Notes |
|
|
|-----------|------------|--------|--------|-------|
|
|
| **ml110** | 192.168.11.10 | ✅ Reachable | https://192.168.11.10:8006 | Primary Proxmox host |
|
|
| **r630-01** | 192.168.11.11 | ✅ Reachable | https://192.168.11.11:8006 | Dell R630 server |
|
|
| **r630-02** | 192.168.11.12 | ✅ Reachable | https://192.168.11.12:8006 | Dell R630 server |
|
|
|
|
### Network Configuration
|
|
|
|
- **Network:** MGMT-LAN (VLAN 11)
|
|
- **Subnet:** 192.168.11.0/24
|
|
- **Gateway:** 192.168.11.1 (UDM Pro)
|
|
- **Dev Machine:** 192.168.11.4 (for access to cluster)
|
|
|
|
---
|
|
|
|
## Expected IP Addresses
|
|
|
|
**Confirmed IP Addresses:**
|
|
|
|
- **ml110:** 192.168.11.10 ✅ (confirmed)
|
|
- **r630-01:** 192.168.11.11 ✅ (confirmed)
|
|
- **r630-02:** 192.168.11.12 ✅ (confirmed)
|
|
|
|
All three hosts are accessible and Proxmox web UI is responding on port 8006.
|
|
|
|
---
|
|
|
|
## Connectivity Testing
|
|
|
|
### Test All Proxmox Hosts
|
|
|
|
```bash
|
|
# Test ml110 (confirmed working)
|
|
ping -c 3 192.168.11.10
|
|
|
|
# Test r630-01 (expected IPs)
|
|
ping -c 3 192.168.11.11
|
|
ping -c 3 192.168.11.13
|
|
|
|
# Test r630-02 (expected IPs)
|
|
ping -c 3 192.168.11.12
|
|
ping -c 3 192.168.11.14
|
|
```
|
|
|
|
### Test Proxmox Web Interface
|
|
|
|
```bash
|
|
# Test HTTPS access (Proxmox web UI typically on port 8006)
|
|
curl -k https://192.168.11.10:8006
|
|
curl -k https://192.168.11.11:8006 # r630-01
|
|
curl -k https://192.168.11.12:8006 # r630-02
|
|
```
|
|
|
|
### Test SSH Access
|
|
|
|
```bash
|
|
# Test SSH (if configured)
|
|
ssh root@192.168.11.10 # ml110
|
|
ssh root@192.168.11.11 # r630-01
|
|
ssh root@192.168.11.12 # r630-02
|
|
```
|
|
|
|
---
|
|
|
|
## Proxmox Cluster Configuration
|
|
|
|
### Cluster Communication
|
|
|
|
Proxmox clusters typically require:
|
|
- ✅ **Network connectivity** between all nodes
|
|
- ✅ **Corosync** communication (usually on same network)
|
|
- ✅ **Shared storage** access (if using shared storage)
|
|
- ✅ **Firewall rules** allowing cluster traffic
|
|
|
|
### Required Ports
|
|
|
|
Proxmox cluster communication uses:
|
|
- **8006:** Web interface (HTTPS)
|
|
- **22:** SSH
|
|
- **5405, 5406, 5407:** Corosync (cluster communication)
|
|
- **3128:** Spice proxy
|
|
- **5900-5999:** VNC console
|
|
- **111:** Portmapper (if using NFS)
|
|
|
|
### Firewall Considerations
|
|
|
|
If hosts are blocking traffic:
|
|
1. **Check Proxmox firewall** on each host
|
|
2. **Check UDM Pro firewall rules** (should allow Internal → Internal)
|
|
3. **Verify Network Isolation** is disabled on MGMT-LAN
|
|
4. **Check Zone Matrix** (Internal → Internal = Allow All)
|
|
|
|
---
|
|
|
|
## DHCP Reservations (Recommended)
|
|
|
|
To ensure consistent IP addresses, configure DHCP reservations:
|
|
|
|
| Host | MAC Address | Reserved IP | Status |
|
|
|------|-------------|-------------|--------|
|
|
| ml110 | TBD | 192.168.11.10 | ⏳ To configure |
|
|
| r630-01 | TBD | 192.168.11.11 | ⏳ To configure |
|
|
| r630-02 | TBD | 192.168.11.12 | ⏳ To configure |
|
|
|
|
**Configuration Location:**
|
|
- UDM Pro Web UI: Settings → Networks → MGMT-LAN → DHCP Reservations
|
|
|
|
---
|
|
|
|
## Access URLs
|
|
|
|
Once all hosts are accessible:
|
|
|
|
- **ml110:** https://192.168.11.10:8006
|
|
- **r630-01:** https://192.168.11.11:8006 (or actual IP)
|
|
- **r630-02:** https://192.168.11.12:8006 (or actual IP)
|
|
|
|
---
|
|
|
|
## Troubleshooting
|
|
|
|
### Cannot Access r630-01 or r630-02
|
|
|
|
1. **Verify IP addresses:**
|
|
```bash
|
|
# Scan VLAN 11 for Proxmox hosts
|
|
nmap -p 8006 192.168.11.0/24
|
|
```
|
|
|
|
2. **Check if hosts are online:**
|
|
- Check UDM Pro dashboard for connected devices
|
|
- Look for devices with MAC addresses matching Dell R630
|
|
|
|
3. **Verify firewall:**
|
|
- Check Proxmox firewall on each host
|
|
- Check UDM Pro firewall rules
|
|
- Verify Network Isolation is disabled
|
|
|
|
4. **Test from ml110:**
|
|
```bash
|
|
# SSH to ml110
|
|
ssh root@192.168.11.10
|
|
|
|
# Test connectivity to other nodes
|
|
ping 192.168.11.11 # r630-01
|
|
ping 192.168.11.12 # r630-02
|
|
```
|
|
|
|
### Cluster Communication Issues
|
|
|
|
If cluster nodes can't communicate:
|
|
|
|
1. **Check Corosync:**
|
|
```bash
|
|
# On any Proxmox node
|
|
systemctl status corosync
|
|
pvecm status
|
|
```
|
|
|
|
2. **Verify network:**
|
|
- All nodes on same VLAN (VLAN 11)
|
|
- All nodes can ping each other
|
|
- Firewall allows Corosync ports (5405-5407)
|
|
|
|
3. **Check cluster configuration:**
|
|
```bash
|
|
# View cluster config
|
|
cat /etc/pve/corosync.conf
|
|
```
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ **ml110 access** - Working (192.168.11.10)
|
|
2. ✅ **r630-01 access** - Working (192.168.11.11)
|
|
3. ✅ **r630-02 access** - Working (192.168.11.12)
|
|
4. ✅ **All hosts accessible** - Ping and HTTPS access confirmed
|
|
5. ⏳ **Configure DHCP reservations** - For consistent IPs (optional)
|
|
6. ⏳ **Verify cluster communication** - Check Corosync status (optional)
|
|
|
|
---
|
|
|
|
## Related Documentation
|
|
|
|
- [UDM_PRO_ROUTING_ISSUE_RESOLVED.md](./UDM_PRO_ROUTING_ISSUE_RESOLVED.md) - Routing issue resolution
|
|
- [UDM_PRO_IP_CHANGE_GUIDE.md](./UDM_PRO_IP_CHANGE_GUIDE.md) - IP change guide
|
|
- [VLAN_11_SETTINGS_REFERENCE.md](./VLAN_11_SETTINGS_REFERENCE.md) - VLAN 11 settings
|
|
|
|
---
|
|
|
|
**Last Updated:** 2026-01-14
|