1431768596
Parallel to refresh-server-info.sh but pipes proxmox_inspect.sh and writes to servers/<host>/proxmox-details.txt. Same discovery / ssh-target / validate-only / dry-run behavior. Fleet-wide `all` matches dir names containing `-pve` (covers *-pve and *-pve-* so esh-pve-nas is included alongside pfi-pve / nh3-pve / esh-pve). Explicit names are never filtered — useful for one-off PVE hosts with non-matching names. Validation checks the captured snapshot for: truncation, missing PVE version line, non-Proxmox target, and surfaces backup-coverage "NO" verdict counts so gaps show up in the validate-only output. Initial fleet snapshot refreshed.
nh3-pve
Proxmox VE hypervisor for the NH3 site (nh3-vmhost.phasefinal.com).
Network
- LAN IP: 10.100.250.60
- FQDN:
nh3-vmhost.phasefinal.com - Web UI:
https://10.100.250.60:8006 - SSH:
root@nh3-pve(key auth)
Hardware
- CPU: 13th Gen Intel Core i9-13900H
- RAM: 62.5 GB
- Kernel:
6.8.12-11-pve(Proxmox 8.x) - Storage: mostly networked —
/mnt/pve/pfi-nh3-nas(42 TB) mounted from the Synology at10.100.50.50:/volume1/VMStorage; ~27 TB used
What it runs
nh3-docker (10.100.50.40) is a VM on this hypervisor. Other VMs (if any) aren't catalogued yet — run qm list on the host when you need the current inventory.
Refresh state
scripts/refresh-server-info.sh nh3-pve
Same Proxmox-inspect caveat as pfi-pve: snapshots capture host-level detail only. VM/LXC/storage enumeration needs the Proxmox tooling manually.
Placement rule
Hypervisor. New NH-site workloads land here as VMs.