Nutanix horizontal Discovery does not create CIs — port 9440 not scanned by ShazzamIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } Running a horizontal Discovery schedule against IP ranges that include Nutanix Prism Central or Prism Element nodes does not produce any Nutanix CIs in the CMDB. The Nutanix Components pattern never fires because Shazzam does not scan TCP port 9440, which is required to trigger HTTP Classification for Nutanix endpoints. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0 0 0.75em 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.4em; } A horizontal Discovery schedule targeting IP ranges containing Nutanix Prism Central or Prism Element nodes completes without creating any Nutanix CIs in the CMDB.The Shazzam phase completes and the target IP is marked as alive, but no HTTP Classification probe fires and no pattern activity is visible for the target IP.Reviewing the Shazzam Output record in the ECC Queue for the affected IP shows port 9440 absent from the scanned ports.The Nutanix Components pattern is never triggered during horizontal Discovery. Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0 0 0.75em 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.4em; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; font-size: 11pt; font-family: monospace; } The Nutanix Prism Central and Prism Element REST API is exclusively served on TCP port 9440 (HTTPS).The Nutanix Components pattern is triggered via HTTP Classification, which requires Shazzam to detect an open port and pass it to the http port probe.Port 9440 is not included in the OOB Shazzam port scan list — the OOB http port probe scans only ports 80 (http) and 443 (https) by default.The Discovery and Service Mapping Patterns application ships an OOB IP Service [cmdb_ip_service] record for port 9440 (named Nutanix, TCP/9440), but this record is not added to any OOB port probe's Triggered by Services list.This issue only affects horizontal Discovery schedules. Serverless (targeted) Discovery schedules for Nutanix bypass Shazzam entirely and are not affected. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All releases shipping the Nutanix Components pattern (Discovery and Service Mapping Patterns application) Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; font-size: 11pt; font-family: monospace; } The OOB Nutanix IP Service record (TCP port 9440) ships with the Discovery and Service Mapping Patterns application but is not wired to the http port probe's Triggered by Services configuration. As a result, Shazzam never scans port 9440, HTTP Classification is never triggered for the Nutanix endpoint, and the Nutanix Components pattern never fires during horizontal Discovery. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper p { margin: 0 0 0.75em 0; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; font-size: 11pt; font-family: monospace; } .kb-wrapper .role-note { font-style: italic; color: #444; margin-bottom: 1em; } .kb-wrapper ol.steps { list-style: none; padding: 0; margin: 0 0 1.25em 0; counter-reset: step-counter; } .kb-wrapper ol.steps > li { display: flex; align-items: flex-start; gap: 0.75em; margin-bottom: 1.1em; counter-increment: step-counter; } .kb-wrapper ol.steps > li .step-num { flex-shrink: 0; width: 28px; height: 28px; border-radius: 50%; background: #032D42; color: #63DF4E; font-weight: 700; font-size: 11pt; display: flex; align-items: center; justify-content: center; margin-top: 2px; } .kb-wrapper ol.steps > li .step-body { flex: 1; } .kb-wrapper ol.steps > li .step-body strong { color: #032D42; font-size: 12pt; display: block; margin-bottom: 0.3em; } .kb-wrapper ol.steps > li .step-body ol { margin: 0.4em 0 0 0; padding-left: 1.4em; } .kb-wrapper ol.steps > li .step-body ol li { margin-bottom: 0.35em; } .kb-wrapper .callout-note { background: #e6f4ff; border-left: 4px solid #52B8FF; padding: 0.65em 0.9em; border-radius: 3px; margin-top: 1em; } .kb-wrapper .callout-note p { margin: 0; font-size: 12pt; } Role required: discovery_admin 1 Verify the Nutanix IP Service record exists Navigate to Discovery Definition > IP Services (or open cmdb_ip_service.list).Search for Name = Nutanix and confirm the record has Port = 9440 and Protocol = TCP.If the record is absent, update the Discovery and Service Mapping Patterns application from the ServiceNow Store. If the record is still absent after updating, create it manually with the values above. 2 Add Nutanix to the http port probe Navigate to Discovery Definition > Port Probes.Open the port probe named http.In the Triggered by Services related list, click Edit.Search for and add Nutanix to the list.Save the port probe record.Confirm the Triggered by Services list now shows: http (port 80), https (port 443), and nutanix-prism (port 9440). 3 Verify (recommended) Run a Quick Discovery against a known Nutanix Prism Central or Prism Element IP.In the ECC Queue, find the Shazzam Output record for the target IP (Topic = Shazzam, Queue = Output).Inspect the XML payload and confirm port 9440 appears with result="open".Confirm a subsequent HTTP - Classify probe was queued for the same IP. Adding port 9440 to the Shazzam scan list increases the number of ports scanned across all IPs in the schedule's range. In environments with large IP ranges, consider scoping Nutanix Discovery to a dedicated schedule covering only the Nutanix subnet(s) to avoid unnecessary overhead. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper ul { margin: 0; padding-left: 1.5em; } .kb-wrapper li { margin-bottom: 0.5em; } .kb-wrapper a { color: #032D42; } KB2360301 Shazzam probe, port probes, and protocolsKB2360297 Port probesKB2872460 Nutanix Acropolis discoveryKB2365014 Run discovery through an HTTP or HTTPS REST call