Proxmox VE — Cluster Management

Basic Information

Field	Value
Category	Infrastructure
Owner	Artem Ryzhkov
Deputy	Filip Kohák
SLA	24x7
Deployment	On-prem (2× Fujitsu server + QDevice)

Description

Proxmox VE is an open-source hypervisor (KVM + LXC) running on two Fujitsu physical servers in an HA cluster. A third node serves as QDevice for quorum maintenance. The cluster hosts all Etnetera on-prem virtualization.

Virtual machines in the cluster:

VM	Purpose
Windows Server (Srv01/Srv02)	Active Directory DC, DNS, DHCP
FortiNAC	NAC — network access control
SnipeIT	IT asset management
Webserver	Internal web services
FortiEMS	FortiClient Endpoint Management Server
Passbolt	IT team password manager

Access and Login

• URL: https://[proxmox-node-ip]:8006 (internal network or VPN only)
• Realm: PAM (system accounts on the host)
• Credentials stored in Passbolt

Warning

Proxmox console is accessible from VPN or office only. Never share root credentials via email.

Procedure — VM Management

Start / Shut down a VM

1. Log in to the Proxmox web interface
2. Select the desired VM in the left tree
3. Use Start / Shutdown / Stop buttons in the top right
4. Always prefer graceful Shutdown over Stop (force kill)

Migrate VM to another node

1. Right-click on the VM → Migrate
2. Select the target node
3. Check Online Migration if the VM cannot have downtime
4. Monitor progress in Tasks (Datacenter → Tasks)

Take a snapshot

1. Select VM → Snapshots tab
2. Click Take Snapshot, enter a name (e.g. pre-update-2025-06)
3. Optionally include RAM state (slower but more accurate)

Tip

Take a snapshot before any major system change. Snapshots don't require VM downtime (QEMU guest agent must be installed).

Check cluster status

1. Go to Datacenter → Cluster
2. Verify all nodes are online and quorum is 1
3. QDevice status: pvecm status via SSH on any node

Procedure — Network & VLANs

1. On a node, go to System → Network
2. Existing Linux Bridge vmbr0 carries tagged VLANs
3. For a new VLAN, edit /etc/network/interfaces on both nodes
4. Reload network interface: ifreload -a (no VM downtime)

Troubleshooting

Problem	Solution
VM won't start	Check RAM and storage on the node: Datacenter → node → Summary
Cluster quorum lost	Verify network connectivity between nodes; check QDevice (pvecm status)
Snapshot fails	Free up storage space; verify QEMU guest agent is running inside the VM
Migration hangs	Check network throughput between nodes (recommended: dedicated 1 Gb/s link)
Cannot log in via web	Verify PAM login via SSH: ssh root@proxmox-node

Related Guides

• Active Directory — VM on Proxmox
• FortiNAC — VM on Proxmox
• SnipeIT — VM on Proxmox
• Network Monitor — monitors Proxmox hosts

Contact

• Owner: Artem Ryzhkov — Slack @artem / artem.ryzhkov@etnetera.cz
• Deputy: Filip Kohák — Slack @filip
• Urgent incidents: Slack #it-alerts