Unanswered questions

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" } ]}

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, 

Hello Team,I have recently deployed a Nutanix solution, and everything is working as expected. I have also deployed a virtual machine with the Veeam Backup solution, which is running successfully.I have an external USB HDD that I would like to map or make accessible within the VM as a storage. Could you please guide me on how this can be achieved?Thank you for your assistance.

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

Question is there a guide to implement firmware for DX servers Via the LCM

Last week I have completed a foundation of 6 HPE Proliant DL360 GEN12 server.This was not functioning like any other foundation in the past.I have encounterd 2 type of issues:ILO7 required HTTPS for the mount of the reuired ISO's ILO7 firmware was to low and therefor got some RESTAPI errors and the foundation failed.i have created a step by step bleg on how to fix those 2 steps (I think the first step already has been talked about here)details about these steps can be found here: https://thevirtualblueprint.com/nutanix-foundation-imaging-errors-on-hpe-proliant-gen12/ good luck 

Is there any way to perform this activity in Element or Prism?Using the console interface doesn't allow it.

Buenas,Según la documentación, no es posible que el ADS mueva una VM con numa activado, pero una cosa es el ADS y otra poner un nodo en mantenimiento o un evento de HA. En el caso ultimo de poner un nodo en mantenimiento, una VM con numa activo, (solo numa, sin CPU pin concreto que es otra config, aunque el numa ya hace un cpu pin realmente) la VM se movería o se quedaría apagada? La misma duda en caso de HA, se cae un nodo, esa VM reiniciaría en otro nodo?(en todos los casos solo es 1 VM “pequeña”, con lo cual habría memoria y CPU disponibles en otros nodos)https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2029-AHV:virtual-nonuniform-memory-access-and-guest-vms.htmlEsto está definido al final de este enlace, pero no se porqué me queda un 1% de duda que igual con la experiencia, podeis ayudarme.Gracias,

I am setting up recovery plans for disaster recovery between our two clusters. I have been through the documentation multiple times, and I still am confused by the test failover/failback subnets that are configured as part of the recovery plan. Production is easy. We have the primary cluster in one location in Subnet A. We have a recovery cluster in another location in Subnet B. I just set the production subnets to be Subnet A and B at each location respectively with their matching gateway and prefix. The Test Failover/Failback subnets continue to confuse me. The documentation indicates they should be isolated and non-routable subnets which makes sense. But WHERE are those subnets defined? We use external IPAM. Each cluster is connected to a core switch stack at its location. We have a few different subnets/VLANs defined on those core switches, with a defined IP range, /24 in each case. All VMs have static IP addresses, though the core switches do run DHCP for each subnet. We also have

Hi,Im working on a project where we need to deploy a new Nutanix Files instance on a new AHV cluster.The customer already has an existing Nutanix Files deployment running on an older AHV cluster that will be destroyed as soon as it is migrated. Also as part of the project we will have to migrate the existing shares and data from the old Files environment to the new one (as well as from other FS not related with nutanix files).I would like to clarify two main points:1. Deployment method: Prism Central vs Prism ElementFor a new Nutanix Files deployment, is it currently recommended to deploy and manage the File Server from Prism Central / Files Manager, or is it still preferable in some cases to deploy it directly from Prism Element?My understanding is that Prism Central / Files Manager is the more modern and centralized approach, especially when managing multiple clusters or using newer Files features, but this scenario means we have only one prism central and one cluster so I would like