Skip to main content
The Proxmox scan module captures Proxmox clusters with their nodes, virtual machines, Linux containers and bridges. It requires a connected gateway.

​
Captured data

The scan creates assets of these types: How the detail pages of the types are structured is described in Virtualization.

​
Setting up the job

The wizard follows the standard path Basics › Targets › Schedule › Summary—see Creating a Scan Job. The Targets step is what sets this module apart. Each row carries the columns IP/Hostname and Credentials. IP/Hostname takes one Proxmox cluster per row, as an address or hostname. The Credentials column must be filled, with an entry of the type User Account. Enter the user name with its realm, such as docusnap@pam. An entry in Credentials for all targets applies to every row without an assignment of its own.

​
Prerequisites

The scan connects to the cluster over HTTPS.

​
Ports and protocols

​
Permissions

  • The account is a user with a realm, such as docusnap@pam, and has read permissions on the cluster.

​
Network requirements

  • The firewall allows the port.
  • If a proxy sits in between, it may need exceptions.
  • One node of the cluster is reachable.
If the gateway cannot reach the cluster, scan it with the Discovery-Proxmox.exe scan script from a computer that reaches the cluster—see Scanning by Script. After it is created, the job appears among the jobs; how you watch and adjust it is in Managing Jobs. How you provide and run the scan scripts and read in their results is in Scanning by Script.