Nutanix Discovery Does Not Support Mixed API v3 and API v4 Clusters on One MID ServerIssue .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Nutanix Acropolis Discovery does not support discovering a mixture of API v1-3 and API v4 clusters through the same MID Server configuration. Symptoms .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The Nutanix environment contains clusters that require different API versions.A single MID Server cannot be configured to discover both API v1-3 and API v4 clusters concurrently.After switching Discovery to API v4, new Nutanix Storage Pool and Nutanix Storage Container records are created.Storage pool and storage container records created through the earlier API version stop being updated after the switch.API v4 calls may retrieve or populate different values than API v1-3 calls. Facts .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } .kb-wrapper .kb-note { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 12px 16px; margin: 0 0 12px 0; } The Nutanix Components pattern uses REST APIs to collect information about Nutanix Acropolis components.Discovery and Service Mapping Patterns supports Nutanix API v4 starting with version 1.29.0.Nutanix API v4 Discovery requires Prism Central version 7.3 or later.The MID Server property sn_itom_pattern.nutanix_prism_version controls the Nutanix API version used by the MID Server.For API v4, configure the property with the exact v4 version to discover.A Serverless Discovery schedule identifies the MID Server that has access to the applicable Nutanix environment.Nutanix changed identifiers and field values for components such as storage pools and storage containers between API v1-3 and API v4. When Discovery is switched to API v4, it creates new storage pool and storage container records. Records created by the earlier API version stop being updated. Release All Releases Cause .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Nutanix changed the identifiers and values returned for components such as Nutanix Storage Pools and Nutanix Storage Containers between API v1-3 and API v4. The Nutanix API version is selected through the sn_itom_pattern.nutanix_prism_version MID Server property. Consequently, a single MID Server configuration cannot process API v1-3 and API v4 clusters concurrently. This design prevents records created from different Nutanix API identifier models from being treated as the same configuration items. Resolution .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } .kb-wrapper .kb-steps { counter-reset: kb-step; list-style: none; margin-left: 0; } .kb-wrapper .kb-steps > li { counter-increment: kb-step; position: relative; padding-left: 42px; margin-bottom: 16px; } .kb-wrapper .kb-steps > li::before { content: counter(kb-step); position: absolute; left: 0; top: 1px; width: 28px; height: 28px; line-height: 28px; border-radius: 50%; background: #032D42; color: #63DF4E; font-weight: bold; text-align: center; } .kb-wrapper .kb-note { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 12px 16px; margin: 0 0 12px 0; } Use separate MID Servers and Serverless Discovery schedules for clusters that require different Nutanix API versions. Deploy or select one MID Server with network access to the API v1-3 Nutanix environment. Deploy or select a different MID Server with network access to the API v4 Nutanix environment. Navigate to All > MID Server > Properties and locate the sn_itom_pattern.nutanix_prism_version property for each MID Server. Configure the property associated with the first MID Server for the API v1-3 clusters. In the property record, select the applicable MID Server in the MID Server field. Configure the property associated with the second MID Server for the exact API v4 version used by the API v4 clusters. For example, enter v4.0.b1 when that is the required API version. In the property record, select the applicable MID Server in the MID Server field. Create a Serverless Discovery schedule for the API v1-3 clusters and select the API v1-3 MID Server in the MID server field. Create a separate Serverless Discovery schedule for the API v4 clusters and select the API v4 MID Server in the MID server field. Run both schedules and verify that each schedule processes only the clusters assigned to its configured API version. Verify that the expected Nutanix configuration items are created or updated by each schedule. To request support for mixed API versions within the current design, search for an existing enhancement in the ServiceNow Idea Portal. Vote for an applicable idea or submit a new product enhancement request. Related Links .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Nutanix Acropolis DiscoveryEnable Nutanix v4 DiscoveryCreate a Serverless Schedule for Nutanix Acropolis DiscoveryIdea Management for Customer Enhancement Requests