Discovery Nutanix Server

[snowsid88]

Hi All,

i have to discovery 1500 Nutanix nodes 

is it possible through OOB "Nutanix Component" discovery patterns which is serverless 

or i have to configure discovery schedule based on the ip range set from  (10.177.44.01 to 10.177.44.99) like that.

it this case Discovery schedule will be On "Configuration items" not a serverless and establish a custom discovery patterns .

Please suggest asap.

[AJ-TechTrek · Accepted solution]

Hi @snowsid88 ,

Yes, you can discover Nutanix clusters & nodes at scale using OOB Nutanix Component serverless patterns, but it depends how your environment is set up

Here is the details solution for you:-

Option 1: Use OOB “Nutanix Component” serverless pattern (recommended if prerequisites are met)

ServiceNow provides an out-of-the-box serverless pattern called:* Nutanix Component
This is the recommended way, because:
* It scales better (especially for 1500 nodes)
* Works without needing an IP-based discovery schedule for each host
* Uses the Nutanix Prism API or vCenter to enumerate cluster nodes automatically

What you need to do:
1. Confirm you have the Nutanix discovery plugin activated.
2. Configure a Discovery schedule of type:
✔ Configuration Item discovery
* Create a Nutanix Cluster CI manually first, with correct management IP & credentials.
* Discovery will connect to the Nutanix Prism API → pull all member nodes.
3. Configure credentials:
* API-based credentials with access to Nutanix Prism (REST API).
* Make sure MID Server can reach the Prism management endpoint.
4. The OOB Nutanix pattern will:
* Discover the Prism cluster
* Then enumerate all cluster nodes (via API)
* Populate CIs in the CMDB (server class, hypervisors, etc.)

Option 2: Use IP range–based discovery schedule
Use this if:
* You don’t have the Prism API access
* Or nodes aren’t correctly associated to a Prism cluster
* Or you must discover additional components outside Nutanix scope

You can configure:
* Multiple IP range schedules (e.g., 10.177.44.1–10.177.44.99, etc.)
* Use standard Discovery patterns to classify hypervisors or servers
Downside:
* Does not scale as well
* Harder to manage (1500 nodes across many ranges)
* You will miss cluster relationships because you bypass the Nutanix Prism source

Best practices as per my understanding :

* Use serverless Nutanix pattern to discover clusters & nodes
* For exceptions (e.g., isolated nodes or non-cluster devices): add small IP range–based discovery schedules

Custom patterns:

Only needed if:
* You have extra attributes not covered by OOB pattern
* Or must discover something not exposed by Prism API
* Start with OOB pattern → clone & customize if needed

Action plan for you:
1. Verify Nutanix Prism API access


2. Configure credentials & MID Server access


3. Create Nutanix Cluster CI (with mgmt IP)


4. Set up Configuration Item discovery schedule → target that cluster CI


5. Run discovery → validate nodes are created


6. For exceptions → use small IP range discovery schedules

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025

[snowsid88]

Thanks a lot ajay kumar for your response.

it is real helpful.