Virtualization

Hypervisors and virtualization management platforms.

VMware

VMware

Field	Value
Device type	VMWARE_DEVICE
User role	Custom role with the “Browse Datastore” privilege in the vSphere Client. Tagging data additionally requires “Assign or Unassign vSphere Tag on Object”.
Default ports	443
Collection method	API
Required parameters	IP: IP address or DNS name of a vCenter User: user name in vSphere login format, typically username@domain Password
Notes	Gathers cluster, host, datastore, and VM detail for the vCenter. This collection can take several hours in large environments.

vSAN

Field	Value
Device type	VSAN_DEVICE
User role	Custom role with the “Browse Datastore” privilege in the vSphere Client
Default ports	443
Collection method	API
Required parameters	IP: IP address or DNS name of a vCenter User: user name Password
Notes	Gathers storage detail for vSAN-enabled clusters and reports the vSAN as a “storage device”, similar to a traditional array. This collection can take several hours in large environments.

Nutanix

Prism / Acropolis

Field	Value
Device type	NUTANIX_V4_DEVICE (primary, preferred) NUTANIX_DEVICE (alternate, legacy)
User role	“Prism Viewer”
Default ports	9440, 443
Collection method	API
Required parameters	IP: IP address or DNS name of Prism Central User: user name Password
Notes	This is the same collector as the Nutanix / Prism entry under Storage, Backup and Hyperconverged: one collection reports both the storage layer and the hypervisor, ESXi or AHV. See that entry for full detail, including guidance on avoiding duplicate reporting with a mixed-hardware vCenter.

Microsoft

Hyper-V

Field	Value
Device type	WINDOWS_HYPER_V
User role	Administrator permissions are required for WMI access by default (LDAP).
Default ports	135, 443, 445
Collection method	Windows Management Instrumentation (WMI)
Required parameters	DNS Name User: a domain user is required Password
Notes	The WMI service startup type should be set to Automatic. Under Windows Firewall Inbound Rules, confirm that “Windows Management Instrumentation (WMI-In)” is enabled for the active profile. For a Hyper-V failover cluster managed through System Center Virtual Machine Manager, use the SCVMM collector below instead.

SCVMM (Hyper-V Cluster)

Field	Value
Device type	HYPER_V_CLUSTER
User role	An account able to run System Center Virtual Machine Manager PowerShell cmdlets over WinRM.
Default ports	5985, 5986
Collection method	WinRM and PowerShell Remoting, running SCVMM cmdlets
Required parameters	IP: IP address or DNS name of the SCVMM server, either the active node or the cluster virtual name User: user name Password
Notes	Requires the System Center Virtual Machine Manager PowerShell module on the target server, and WinRM enabled. Collects data for both clustered and standalone Hyper-V hosts managed by SCVMM. This is distinct from the “Hyper-V” entry above, which connects to a single host directly over WMI with no SCVMM management layer involved.

IBM

Hardware Management Console (HMC)

Field	Value
Device type	HMC_DEVICE (primary, preferred) HMC_CLI_DEVICE (alternate, for legacy HMC firmware)
User role	Read Only for both methods
Default ports	12443 (alternate: 22)
Collection method	API (alternate: SSH/CLI)
Required parameters	IP: IP address or DNS name User: user name Password
Optional parameters	Port
Notes	Collects data for IBM systems and LPARs through the HMC. Statistics must be enabled on each LPAR in order to collect performance data. Use the SSH/CLI alternate for HMC V7 and earlier, or in any environment where legacy TLS cipher suites are rejected by the API collector. It supports HMC V7R7.9.0 and later, including V8. The two methods use matching output structures, so downstream reporting is unaffected by which one is used.