Home / Integrations / Nutanix
Integrations

Nutanix Integration

Connect to Nutanix Prism Central or Prism Element to import virtual machines, hosts, clusters, storage containers, and networks into the Clarity CMDB — and feed data directly into the Nutanix Move Management module for migration planning.

On this page

Overview

The Nutanix integration connects Clarity Migrate to your Nutanix environment via the Prism REST API (v3). It supports both Prism Central — which manages multiple clusters from a single pane of glass — and standalone Prism Element instances for environments without Prism Central.

In addition to populating the CMDB, discovered Nutanix assets feed directly into the Nutanix Move Management module, allowing migration teams to use CMDB data as the source of truth when building Nutanix Move migration plans.

Prism Central Support
Connect once to Prism Central and discover all managed clusters — no need to add each cluster separately.
Move Management Feed
Discovered assets automatically populate the Nutanix Move Management module for migration planning.
Full Stack Coverage
Imports VMs, AHV hosts, clusters, storage containers, and VLANs in a single discovery run.
Credential Vault
Prism service account credentials are stored securely in the Clarity credential vault.

Prerequisites

ℹ
Before you begin

Ensure all of the following are in place before creating a Nutanix integration endpoint.

  • Nutanix Prism Central 5.x or later (recommended), or Prism Element for standalone single-cluster environments. Prism Central is strongly preferred as it provides visibility across all clusters in one connection.
  • Service account with Viewer role. Create a dedicated Prism service account with the built-in Viewer role. This provides read-only access to the full inventory without any administrative permissions.
  • Network connectivity. The Clarity server must be able to reach the Prism Central (or Element) API on HTTPS (port 9440) by hostname or IP address.
  • Credentials stored in the vault. The Prism service account credentials must be saved in Administration → Credentials as type Nutanix before you create the endpoint.

Configuration

Follow these steps to add and configure a Nutanix integration endpoint in Clarity.

1
Add credentials to the vault

Navigate to Administration → Credentials → Add. Enter the Prism service account username and password, set the Type to Nutanix, give it a descriptive name (e.g. PrismCentral-Prod-Viewer), and click Save.

2
Navigate to Integration Endpoints

Go to Integrations → Integration Endpoints and click Add Endpoint.

3
Select Type: Nutanix

In the Type dropdown, select Nutanix. The form will update to show Nutanix-specific fields.

4
Fill in endpoint details
  • Name — a friendly label (e.g. Prism Central Production).
  • Prism URL — the full HTTPS URL of your Prism Central or Element instance (e.g. https://prism-central.company.com:9440).
  • Credential — select the Nutanix credential saved in Step 1.
  • API Version — leave at default (v3) unless directed otherwise.
5
Test the connection

Click Test Connection. A green success banner confirms that Clarity can authenticate to Prism and reach the API. If it fails, verify the URL includes the port (:9440), check network connectivity, and confirm the service account credentials.

6
Save the endpoint

Click Save. The endpoint will appear in the Integration Endpoints list and will be available when running a Nutanix discovery.

Running a Discovery

With an endpoint configured, you can run a discovery at any time to import or refresh Nutanix inventory data.

1
Open the Nutanix discovery page

Navigate to Integrations → Nutanix.

2
Select the endpoint

Choose the configured Prism endpoint from the dropdown.

3
Click Run Discovery

Click Run Discovery. A progress bar shows import status. For large environments, this may take several minutes.

4
Review results

Go to Integrations → History to review the run log — it shows object counts per type and any errors encountered during import.

What Gets Imported

The following Nutanix objects are discovered and imported into the Clarity CMDB:

Source Object CMDB Asset Type Notes
Virtual Machine Device VM name, power state, guest OS, vCPU count, memory, IP addresses, and parent cluster.
AHV Host Host Host name, model, CPU cores, total memory, AOS version, and parent cluster.
Nutanix Cluster Cluster Cluster name, AOS version, node count, and Prism Element IP.
Storage Container Storage Container name, total capacity, used capacity, and compression/deduplication settings.
Network (VLAN) Network Network name, VLAN ID, and subnet configuration where available.

Scheduling

Configure a recurring background job to keep the CMDB in sync with Nutanix automatically:

  1. Navigate to Administration → Background Jobs → Integration Sync — Nutanix.
  2. Set the desired schedule (default is daily).
  3. Select the Nutanix endpoints to include.
  4. Save the job.

Example Workflow

Real-world example
Populating the CMDB for a Nutanix Move migration plan

A Nutanix admin adds Prism Central credentials to the vault, creates an integration endpoint pointing to https://prism-central.company.com:9440, and runs a discovery.

The discovery imports 312 VM records and 6 cluster records across all managed clusters in under 2 minutes. The admin then opens the Nutanix Move Management module and finds the CMDB data pre-populated as the source inventory for the migration plan.

The migration team can now build move groups, assign VMs, and export migration manifests — all using the verified CMDB data rather than a manually curated spreadsheet.

Tips

Use Prism Central wherever possible

Prism Central covers all clusters in a single connection. Using individual Prism Element endpoints means creating one endpoint per cluster and running separate discoveries — considerably more overhead.

  • Reuse credentials across integrations. If you use the same Prism service account for both the CMDB integration and the Nutanix Move Management module, store it once in the vault and reference it in both places.
  • Check the port in your Prism URL. Prism Central uses port 9440 by default. Omitting the port from the URL is a common cause of Test Connection failures.
  • Run discovery after cluster expansions. When new nodes or clusters are added to Prism Central, run a fresh discovery to ensure the CMDB captures the new capacity and hosts.

Common Mistakes & Troubleshooting

  • Using Prism Element URL when Prism Central is available. If you point the endpoint at an individual cluster's Prism Element rather than Prism Central, the discovery will only import that single cluster. Other clusters managed by Prism Central will be missed entirely.
  • Nutanix API certificate errors. Prism Central often uses a self-signed certificate. If Test Connection fails with an SSL error, add the Prism Central CA certificate to the trusted root store on the Clarity server, or ask your administrator to configure a valid certificate on Prism Central.
  • Service account with insufficient role. If the Prism account is assigned a custom role with fewer permissions than the built-in Viewer role, certain object types may not be returned by the API. Always use the built-in Viewer role to guarantee read-only access to all inventory objects.
  • Omitting the port number from the URL. The Prism API runs on port 9440, not the standard HTTPS port 443. Always include :9440 in the Prism URL unless your environment uses a load balancer or reverse proxy on port 443.