Harish Bainsla
Kilo Patron

1. Architecture and scope

ServiceNow uses the out-of-box Nutanix Components pattern to call Nutanix Prism REST APIs. A MID Server provides the network path from the ServiceNow instance to the Prism endpoint. Discovery then creates or updates Nutanix configuration items (CIs) and relationships in the CMDB.

High-level communication flow

HarishBainsla_0-1794367982833.png

Typical CI coverage

HarishBainsla_1-1794368041126.png

2. Infrastructure prerequisites

Verify that the following applications are up to date
  • Discovery and Service Mapping Patterns
  • Visibility Content
  • CMDB CI Class Models
Verify MID Server requirements
Deploy and connect a dedicated MID Server with network access to Prism Element and Prism Central.
Install Nutanix end-point SSL certificates for the MID Server JRE
  1. Collect the certificates by browsing the Nutanix Prism console on Internet Explorer.
  2. Add SSL certificates for the MID Server, as described in Add SSL certificates for the MID Server.
  3. Install Nutanix end-point SSL certificates for the MID Server JRE.
Verify API permissions for v1-3
Verify that the user has read-only access to the following API requests:
  • /PrismGateway/services/rest/v1/vms
  • /PrismGateway/services/rest/v1/storage_pools
  • /PrismGateway/services/rest/v2.0/tasks/list
  • /PrismGateway/services/rest/v2.0/hosts
  • /PrismGateway/services/rest/v2.0/clusters
  • /PrismGateway/services/rest/v2.0/vms
  • /PrismGateway/services/rest/v2.0/storage_containers
  • /api/nutanix/v3/clusters/list
  • /api/nutanix/v3/categories/list
  • /api/nutanix/v3/categories/{category_keys}/list
  • /api/nutanix/v3/category/query
Verify API permissions for v4
Verify that the user has read-only access to the following GET APIs. Note that the API call referencing /PrismGateway/services/rest/v1/vms uses a legacy endpoint because it's not available yet in the newer API.
  • /api/clustermgmt/v4/config/clusters
  • /api/clustermgmt/v4/config/clusters/{clusters_ID}/hosts​
  • /api/clustermgmt/v4/config/storage-containers
  • /api/vmm/v4/ahv/config/vms
  • /PrismGateway/services/rest/v1/vms
  • /api/prism/v4/config/categories?$expand=associations​
  • /api/prism/v4/config/categories/{categories_ID}?$limit=extId&$expand=detailedAssociations
  • 3. ServiceNow configuration and validation
  • A. Configure credentials • Navigate to Discovery > Credentials .
  •  Create a Basic Auth credential using the approved Nutanix API service account.
  • Step 1: Create the Discovery Schedule Record

    1. Navigate to All > Discovery > Discovery Schedules.

    2. Select New.

    3. Fill in the form fields:

      • Name: Unique name for this discovery schedule.

      • Discover: Select Serverless.

      • MID server: Name of the MID Server with access to the Nutanix environment.

      • Active: Check to enable this schedule for discovery.

      • Run: Set the run schedule frequency.

    4. Select Submit.

    Step 2: Create the Execution Pattern

    1. On the Discovery Schedules page, select the schedule record you just created.

    2. Go to the Serverless Execution Patterns tab and select New.

    3. Fill in the fields:

      • Name: Descriptive name for this record.

      • Pattern: Select Nutanix Components.

      • Proxy Host: (Optional) FQDN of the machine where the proxy server is installed (should be Global).

      • Active: Check to enable the schedule.

    4. Select Submit.

    Step 3: Set the Pattern Launcher Parameters

    1. In the Discovery Pattern Launcher Parameters tab, select the pattern record created in Step 2.

    2. Fill in the parameter field:

      • PRISM_Address: IP Address or FQDN associated with the Prism Central instance.

    3. Select Submit.

    Next Steps

    Execute the discovery immediately by selecting Discover now, or let it run automatically according to your predefined schedule.

    Thank You

    LinkedIn : https://www.linkedin.com/in/harish-baisla-8895aa22a/

    ServiceNow Community Rising Star 2024 , 2025 and 2026

Version history
Last update:
8m ago
Updated by:
Contributors