Skip to main content
The Nutanix module addresses clusters, not individual hosts. Otherwise it follows the standard path from Creating a Scan Job: Basics › Targets › Schedule › Summary

​
Prerequisites

The scan captures Nutanix clusters on VMware or on Nutanix AHV through the vendor’s API.

​
Ports and protocols

​
Permissions

The account needs the View permission on the cluster. A user who has no role assigned—neither User Admin nor Cluster Admin nor Backup Admin—has this permission. So only create the user. For Search Nutanix Clusters through Prism Central, the account needs the View permission on all clusters.

​
Network requirements

  • The firewall allows the port.
  • If a proxy sits in between, it may need exceptions.
If the gateway cannot reach the cluster, scan it with the Discovery-Nutanix.exe scan script—see Scanning by Script.

​
Entering the targets

The Targets step carries a table with one row per cluster and two columns: Unlike with Windows DNS, Windows DHCP, DFS, Hyper-V and Microsoft SQL Server, the Credentials column may not stay empty here; without an entry the step stops.

​
Having clusters searched for through Prism Central

Instead of entering the clusters one by one you can have them searched for. Above the table there is Search Nutanix Clusters for that. The dialog takes the address of Prism Central plus an account with password or a stored entry. Afterwards it proposes the clusters found as rows. The messages of the search appear at the top of the dialog; the dialog stays open:
The search starts a short-lived scan in the background. It has no name and no schedule and appears in no job list—the job comes about only at the end of the wizard.

​
Common issues

Which types this scan produces—from the management layer through the hosts to the guests—is under Virtualization. How you watch the job afterwards is in Managing Jobs.