Unanswered questions

Hello, I have downloaded and installed Nutanix CE with AOS rev. 6.8 yesterday.Afterwards I have updated AOS to rev .7.3.1.6, FSM to 5.3, Foundation to 5.10.4 and NCC to 5.3.0.1 via LCM successfully.However, AHV upgrade failed with error:Lcm prechecks detected 1 issue that would cause upgrade failures.Check 'test_ncc_checks' failed: test_ncc_checks: Failure while validating that all NCC pre-upgrade checks ran successfully, Error: The following ncc checks failed: host_disk_usage_check. Please refer to KB 10847 Does anyone have an idea to fix this issue?BR, Joachim

We are using the Data Protection v4.1 API compute-changed-regions endpoint from Prism Central 7.5 (AOS 11.0.0.1) to retrieve changed regions for VM recovery points.For most VMs, the workflow completes successfully. However, for VMs with large changed data disks, the API consistently fails with:401 UNAUTHORIZEDThe failure occurs approximately 15 minutes after the operation starts.Our current steps are:compute-changed-regions is invoked successfully for cluster prism element API - api/dataprotection/v4.1/content/recovery-points/{recoveryPointExtId}/vm-recovery-points/{vmRecoveryPointExtId}/disk-recovery-points/{extId}/$actions/compute-changed-regions Nutanix begins computing changed regions. The VM disks are highly fragmented and may contain a very large number of changed extents. Results are returned through pagination. The client continues fetching paginated results. Total processing time exceeds approximately 15 minutes. A subsequent page retrieval request returns 401 UNAUTHORIZED.Add

I am getting ready to deploy a new Nutanix cluster next week and am preparing my Foundation VM.  I have imported the 7.5.1.6 AOS package which then states that the minimum AHV version is 11.0.1.2-33.  I’ve then downloaded this ISO from the link direct within Foundation and imported but I then get the message that this in an unsupported Hypervisor.  I’ve updated the whitelist but the hypervisor is still showing as not in the whitelist.  Am I ok to just install or do I need to check something else?

I have a nutanix environment Running well and it is an OT Production environment. Due to some reason I want to change the Cluster Name, so before changing, I have a doubt that will cluster name change impact the virtual machine and its operation? and do I need to reboot the cluster when the cluster name is changed to new.

I am requesting the expected release date for my NCP-MCI 7.5 and NCP-BC beta exam results.As these are beta tracks,I would appreciate an estimated timeline for when scores will be finalized and reflected in the Nutanix University portal. Thanks you, 

I have encountered a roadblock while configuring LDAP and SAML authentication from the same domain for a Customer. The Customer wants that whenever a user logins , it does from SAML and whenever a service account is logging into PC , it uses LDAP. Is there a way to configure this in Prism Central?

i  have a nutanix cluster  of node with (25gb ) uplink  and LACP is configured on it . i need to to expand cluster with nodes with ( 100GB ) uplink .i prepared the new node with below configuration:1-  re-imaged the new node with same version of AOS and AHV  as the existing cluster 2-  configured the  the new node with LACP my questions:1- is there any impact  to cluster that we mix speed of network as some node work with 25g and other with 100g ?2-  in expand cluster steps the is tab of network configuration is mandatory to set its configuratiion or can skip this configuration as i configured on new node , what will happen if i skip network configuration during expand 3- how long the expand will take to expand 4 node ? 

FoundationVMを使ってNutanixを導入しようとしているのですが、CVMをデプロイするところで、添付のエラーとなってしまいました。この場合、原因として考えれらることはどういったものがありますでしょうか？ご教示いただけますと幸いです。 CVM展開時画面エラーが起きているログは以下となります。2026-06-08 22:22:43,525Z log.py:102 INFO svm.py:849 Output of lsblk command. NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTsda       8:0    0   1.8T  0 disk sdb       8:16   0   1.8T  0 disk nvme2n1 259:0    0 447.1G  0 disk nvme0n1 259:1    0 447.1G  0 disk nvme1n1 259:2    0 447.1G  0 disk2026-06-08 22:22:43,533Z log.py:102 INFO svm.py:851 Output of mdstat command. Personalities : [raid1] unused devices: <none>2026-06-08 22:22:43,537Z log.py:102 ERROR svm.py:854 SVM rescue failed with reason [Unable to read /etc/nutanix/release_version: [Errno 2] No such file or directory: '/etc/nutanix/release_version'2026-06-09 07:55:10,609Z ERROR layout.py:40 Failed to parse factory_config.json:Traceback (most recent call last):  File "util/hardware/layout.py", line 35, in should_use_layoutFileNotFoundError: [Errno 2] No such file or directory:

Hi When entering a workload in Sizer, there is an option to select the existing CPU.For example, let’s assume that we are planning to deploy 100 VMs, each with 4 vCores and 8 GB of memory.  If I select “Yes, but I don’t know the current processor” and then choose Default, the estimated CPU utilization is approximately 75% when configured with a 3-node cluster, each node having 2 CPUs with 32 cores.However, if I edit the workload and select “Yes, but I don’t know the current processor”, the estimated CPU utilization increases to around 110%.In other words, I am not sure which criteria I should use when performing sizing.Why does the estimated utilization differ so significantly even though the workload itself is the same?Is there any detailed guidance available for this? It may be that I have not been able to find it, so I would appreciate your assistance.

Hello Since onw month, when change some VMs, of Data Protection to Ptotection Policie, show the next alerts: VSS is enabled, but Nutanix VSS provider or pre_freeze/post_thaw scripts are not installedVSS snapshot is not supported for the VM X because VSS software is not installed.I returned some VMs to Data Protection, and the alerts did not return.Why do it pass this behavior?

How to dump Linux Extractor memory in Nke or NKP? Can I just install lime.ko manually on the Linux Nke OS or does Nutanix have its own way to get the dump file of the memory extractor?

Buenos días,He estado revisando las opciones disponibles para la segregación del tráfico de Disaster Recovery en entornos Nutanix. Según la documentación oficial (Disaster Recovery Guide), es posible crear una interfaz de red adicional dedicada para este tipo de tráfico.No obstante, me surgen algunas dudas respecto a la implementación práctica:¿Cuál sería el procedimiento recomendado (how-to) para asegurar que el tráfico de DR se enruta correctamente a través de dicha interfaz? En escenarios de fallo o degradación de red, ¿Cómo se comportaría este tráfico dedicado? Concretamente, ¿Qué impacto tendría esta configuración en un entorno con Metro Availability, especialmente en términos de resiliencia y continuidad operativa?¿Alguien ha tenido experiencia implementando este enfoque y puede compartir mejores prácticas o consideraciones a tener en cuenta?Muchas gracias de antemano por vuestra ayuda.

Hi Team,Could you please help by sharing the documents/procedure for the below activities?Changing the Prism Central VM hostname. Migrating Prism Central VM disks from one container to another.Appreciate your support. Thanks.Shanmugavadivel Mahali

Hi Nutanix Support Team,I have completed and passed the Nutanix Certified Professional - MultiCloud Infrastructure (NCP-MCI) 6.10 exam on May 21, 2026.However, I have not yet received my certification badge or certificate.Could you please check and help me with this issue?

Hola,  Tengo un Prism Central con esta alerta.Como veis parece que no contacta con ldap, en ralidad lo que pasa es que a veces se va a buscar un servidor con alta latencia en vez de coger el que tiene al lado. Tengo otros Prism en misma localización y misma configuración y no tienen este problema. El Kb en mi caso no ha servido de mucho. Esta alerta la tuve en otro cluster, actualicé ncc y no volvio a salir. En este cluster no he tenido la misma suerte. Alguna idea? Gracias

Hi All,I’m developing a script to move away from GUI LCM click-ops for our Prism Central instances, I’m having some trouble with the lifecycle V4.1 namespace.https://{pc-ip}:9440/api/lifecycle/v4.1/operations/$actions/compute-recommendationsI’m getting errors trying to POST the following data. I understand recommendationSpec expects the UUID and targetVersion but I simply can’t get this to work, any suggestions?I’m following this documentation → https://developers.nutanix.com/api-reference?namespace=lifecycle&version=v4.1I have both a NTNX-Request-ID and X-Cluster-ID in my request, I recieve a a 400 bad request response.{ "recommendationSpec": [ { "entityUuid": "<LCM-uuid>", "toVersion": "3.1.0.1" }, { "entityUuid": "<Foundation-uuid>", "toVersion": "5.7.1" }, { "entityUuid": "<AOS-uuid>", "toVersion": "7.3.1.6" }, { "entityUuid": "<AHV-uuid>", "toVersion": "20230302.100173" } ]}

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Data-Services-for-Kubernetes-v2_1:top-configuring-pfo-t.html#:~:text=Configure%20the%20migrate%2Djob%20YAML%20with%20the%20names%20of%20the%20secrets%20created%20in%20the%20previous%20steps%20and%20the%20location%20of%20the%20Kubernetes%20job%20image. Hi everybody,I am following the NDK 2.1 documentation for Planned Failover:Configuring and Running Planned FailoverIn step 3, Configure the migrate-job YAML, the sample YAML contains this placeholder:containers:- name: ndk-dr-container image: # <image-repo-url>:<tag>I am not sure what image URL should be used here for the NDK recipe job.My environment is non-air-gapped. I already created the Docker registry secret using the Nutanix Docker Hub access token:kubectl -n ndk-recipes create secret docker-registry ndk-recipe-pull-secret \ --docker-server=https://index.docker.io/v1/ \ --docker-username=nutanixndk \ --docker-password="<REDACTED_ACCESS_TOKEN>"

We are trying to configure the CVM hardening recommendation to enable SNMPv3 only.  The Nutanix Bible lists the command as:ncli cluster edit-cvm-security-params enable-snmpv3-only=[true|false] #Default:falseHowever, the AOS 7.5 version of the Security hardening guide doesn’t list the command and execution fails with an invalid command. How can we enable SNMPv3 only or verify that SNMPv2c is disabled?

X-Ray 6.2, trying to run the resiliency test on a 5 node cluster where 3 nodes are storage only. Is there way to configure the test to only move VMs between the 2 hyperconverged nodes?

Hi Team, We have Nutanix Prism central deployed with scale out option by having 3 PC instances in it. We would like to make it one instance instead of 3. Could you help with Nutanix articles that gives the steps to do do.

Hi community,I'm in the middle of deploying a 3-node Nutanix AHV cluster and have a question about live migration traffic behavior with and without the Backplane LAN configured.My current setup:- 3 Nutanix AHV nodes- 10G SFP+ uplinks for VM traffic (VLAN 1 - e.g 10.10.100.0/24)- 1G RJ45 uplinks for DMZ and Corp networks on separate VLANs- Backplane LAN not yet configuredMy questions:1. Without the Backplane LAN configured, when a host is placed into maintenance mode and VMs are live migrated to other nodes,  does that migration traffic travel over the VM's own network? For example, if a VM is on my DMZ network (1G), does its live migration traffic also go over that 1G link?2. Once the Backplane LAN is configured on a dedicated VLAN (e.g. VLAN 10 - 192.168.10.0/24) on my 10G uplinks, will ALL live migration traffic route over the backplane regardless of which network the VM is connected to?3. Is there any official documentation that specifically covers this default migration traffic beh

Hi Experts!We are planning a migration from an existing AHV cluster (AOS 6.x) to a new AHV cluster running AOS 7.5.1, and we need to migrate our Active Directory Domain Controllers.We are aware that the official Move documentation states that DC migration is "not recommended but can be performed with some limitations", and that AOS 6.7+ supports VM Generation ID to reduce USN rollback risks.We have a few questions :Has anyone successfully migrated Domain Controllers using Nutanix Move in an AHV-to-AHV scenario on AOS 6.7 or higher ?Did you experience any USN rollback, replication issues, or post-migration AD inconsistencies ?Any specific pre/post-migration checks you would recommend for this use case ?Constraint: We need to keep the same IP addresses for our DCs after migrationThanks in advance