Proxmox Cluster

Proxmox VE cluster configuration and management

Cluster Overview

The Proxmox cluster consists of two nodes providing high availability for virtual machines and containers.

Cluster Information

  • Cluster Name: homelab-cluster
  • Version: Proxmox VE 8.x
  • Nodes: 2 (prox1, prox2)

Node Configuration

prox1 (Primary Node)

  • IP Address: 192.168.1.3
  • Web Interface: https://192.168.1.3:8006
  • Role: Primary hypervisor, hosts majority of VMs
  • Network Interface: enp86s0 (1 Gbps)

prox2 (Secondary Node)

  • IP Address: 192.168.1.2
  • Web Interface: https://192.168.1.2:8006
  • Role: Secondary hypervisor, failover node
  • Network Interface: enp114s0 (1 Gbps)

Virtual Machines

Current VM Allocation

VM IDNameNodeIP AddressPurpose
201k3s-master-01prox1192.168.1.210K3s control plane
202k3s-master-02prox1192.168.1.211K3s control plane
203k3s-worker-01prox1192.168.1.212K3s worker node
204k3s-worker-02prox2192.168.1.213K3s worker node

Common Operations

VM Migration

# Migrate VM to another node
qm migrate <vmid> <target-node> --online

# Migrate with local disks
qm migrate <vmid> <target-node> --with-local-disks

Cluster Status

# Check cluster status
pvecm status

# View cluster nodes
pvecm nodes

# Check VM status
qm status <vmid>

Storage Management

# List storage
pvesm status

# Add iSCSI storage
pvesm add iscsi <storage-id> --portal <ip> --target <iqn>

Network Configuration

Bridge Configuration

All VMs use the vmbr0 bridge for network connectivity:

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.x/24
    gateway 192.168.1.1
    bridge-ports enpXXs0
    bridge-stp off
    bridge-fd 0

Network Performance

  • Inter-node bandwidth: ~679 Mbps
  • Storage network: Same as management network
  • MTU: 1500 (standard)

High Availability

Cluster Features

  • Live VM migration between nodes
  • Shared configuration via pmxcfs
  • Automatic fence recovery
  • Resource scheduling

Best Practices

  1. Keep nodes time-synchronized (NTP)
  2. Maintain consistent storage configuration
  3. Regular cluster health checks
  4. Monitor corosync ring status

Troubleshooting

Common Issues

Network Speed Issues

If experiencing slow network between nodes:

# Check link speed
ethtool enp86s0

# Force 1Gbps if needed
ethtool -s enp86s0 speed 1000 duplex full autoneg on

Cluster Communication

# Check corosync status
systemctl status corosync

# View corosync logs
journalctl -u corosync -f

VM Won’t Start

# Check VM configuration
qm config <vmid>

# Check storage availability
pvesm status

# Force stop if needed
qm stop <vmid> --skiplock