Nutanix Cloud Infrastructure

Estimado Foro,En relación a los procesos de migración donde el E2E, los procesos, flujos, ambitos incluso de permisos es un factor que limita y afecta una correcta migración.Queria consultar si alguien ha realizado algun documento de migración donde incluya: restricciones, compatibilidades, recomendaciones, el año anterior realice una migración en este ambito que me da un contexto inicial, sin embargo el reto es grande cuando todo incrementa en tamaño de Workload y criticidad, en este sentido si alguien tiene algun inicio seria importante lo comparta, o en su defecto lo ire documentando para aporte a la comunidad.Una consulta: alguien ha expermientado migrar un Active Directory to AHV, de pronto me puede compartir su experiencia? 

Hello has anyone used https://www.datamotive.io/ for a dr solution for AHV to AZURE ?  I am assuming they are new to this space. 

HiThis thread is related with the previous one that I opened some days ago but it was already closed as solved.https://next.nutanix.com/nutanix-disaster-recovery-29/replicated-recovery-points-not-found-error-45362In summary:I’ve recently deployed a pair of AHV clusters, each one with his on Prism Central. Later I’ve created a specific container for testing purpose called “Replica-Container” on both sites I’ve moved some test VMs to that specific container and and I’ve created a manual bi-directional syncronous replica between both sites. I’ve manualy added the test VMs to the protection plan and I’ve waited some time for them to replicate between sites. Finaly I’ve created two different Recovery plans Recovery Plan1 - recover VMs from site1 at site2 Recovery Plan2 - recover VMs from site2 at site1 I’ve validated both plans (succesfuly) and I’ve performed a Test.The initial test worked fine for plan2, however Recovery Plan1 shows this error:  I assumed that I should have to wait more t

When I hear the words clean room, my mind goes straight to Dexter — the TV show about a forensic blood spatter analyst who moonlights as a vigilante. His clean room is meticulous: sealed in plastic, no trace evidence, no contamination, nothing gets in or out. In some ways, it makes perfect sense as a metaphor. Dexter was in the business of containing and eliminating threats — and in the IT world, so are we. We are just going after ransomware actors instead of murderers. The plastic sheeting is a little different, but the principle is the same: isolate the threat completely before you do the work. Ransomware recovery used to mean one thing: restore from backup and hope for the best. That approach has a serious flaw — if your recovery environment connects to the same infected infrastructure you are restoring from, you risk reinfecting your clean data before you ever flip a switch. The answer is not faster backups. It is a clean room: an isolated, air-gapped environment where you can vali

Hi,I’m currently configuring synchronous replication (manual failover, no Witness VM yet) between two AHV clusters managed by Prism Central 7.5.0.5 (each cluster has it’s own PC).Since there is no Witness deployed, this is not Metro Availability, but a synchronous Protection Policy with manual failover. As soon as I have the Witness VM I will test the Metro Availability feature.Current setup Created a container named Metro_CPD1 on both clusters. Created 3 test VMs on Cluster1 and placed them in the Metro_CPD1 container. From PC1 I’ve created a Synchronous Protection Policy (ReplicaMetro-CPD1-to-CPD2) with manual failover. From PC1 I’ve created a Recovery Plan (Recovery-metro-replica1) : Primary location: Cluster1 Recovery location: Cluster2 Execution mode: Manual Added the 3 VMs to the Recovery Sequence. Configured Network Mappings (Prod LAN and Test LAN with IP pools). After creating the Recovery plan I do a “Validate” and it completes successfully on both site

Hi,I have recently deployed a pair of AHV clusters on a customer. Each cluster has its own Prism Central cause they are going to be part of a Metro availability environment with a witness VM on a third site.Now the customer is asking me if he could have some kind of overview and managing of both clusters from a single dashboard.I think that Nutanix Central could accomplish that request, however I’ve never deployed it and I have some questions.Checking the documentation I see that you can deploy it onpremise by downloading it from each Prism Central marketplace. So I assume it will deploy a VM appliance on each cluster (similar to prism central) and I should have to config it.Are there any specific tips that you could provide before deploying it?By the way, both clusters have PC 7.5.0.5 and AHV 11, everything is up to date, so I assume there is no incompatibility with nutanix central.Thanks in advance!

Prism central showing disconnected on prism elements. but VM is power on and also pingable. getting this error. 

Currently we are running VM’s workload in VXRail VMware, these VM’s replicating to Azure cloud using recovery vault.Now these VM’s migrating to Nutanix native AHV environment.Please advise how to replicate VM’s from Nutanix to Azure cloud using which tool,Thanks in advance.

Hello,  could you please advise the difference between difference between NVIDIA GRID for AHV 10.3.1.3 (AIE)  & NVIDIA GRID for AHV 10.3.1.3 (Graphics)   and when to use each of them in addition to the requirement for each one 

Hi,I have a two-nodes cluster with Nutanix CE (AOS 6.8.1 )which was built on hybrid (HDD& SSD) nodes. There is the issue:Current memory configuration 20,20 does not support the HDD capacity on the node(s): 192.168.XXX.XXX,192.168.XXX.XXY.For All-NVMe systems sized and deployed before AOS 6.8 with a minimum of 48GB CVM vRAM, it's recommended to upgrade to at least 64GB for optimal performance. Refer to the Prism Web Console Guide for instructions on Increasing the Controller VM Memory Size. I tried to increse CVM ram size from 20GB per node to at least 40GB by following this document.Then we saw the situation below:Committed memory update intent.The task is stucking on 50%. Task status:~$ ecli task.list include_completed=falseTask UUID                               Parent Task UUID        Component       Sequence-id     Type            Status          Creation Time(UTC)      Completion Time(UTC)ffc53d0a-6e9e-41c7-7c4f-d9b337263be3                            kGenesis        3        

Need AHV iso trial key or iso for inhouse testing of software .

HiImagine you have two AHV clusters that are Active-Active (each site has live VMs on it). They are both connected and they are doing Metro-Sync between them.Now you want to move some VMs from one site to the second site. As far as I know I could perform that migration by using MOVE or by doing a manual failover of a protection policy. Is there any way to do a “live migration” between clusters without shuting down any VM?Also, is there any way to do that even if you have Async migration?I have found this but I understand is only talking about migration between nodes): https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2029-AHV:nutanix-ahv-live-migration.htmlThanks

I’m encountering an issue where an additional IP address is attached to a VM being built by Packer - this address appears at the point Packer  runs theConnecting to VNC over websocket…andTyping the boot command over VNC…stage - so very early and no where where we have much if any control!At this point the VM isn’t even up and no virtio drivers have been loaded - and so it isn’t ‘known’ by Windows but it’s the first listed IP address so that’s the one Packer tries to communicate on - so the build fails as communication is never established.I’ve tried releasing and renewing an IP address in Windows during the build but Windows doesn’t know about the address at all so it doesn’t do anything useful.  The VM shows as having 2 addresses from DHCP in Prism Central… I’m all out of ideas!  Any insight gratefully received!

Hi Guy’s I'm trying to update our Dev environment which runs on community edition, and AOS, NCC etc all working via LCM, for the AHV though it will just keep failing every single time.It just goes round in a loop watching from the ilo, it first does choose AHV re image, the it reboots and get to that same screen and then just boots to current AHV OS.So is there a way to do this manually without it affecting the CVM’s config running on them?ThanksMark

HiI’m reviewing the network design for a Nutanix AHV cluster and I would like to clarify best practices regarding CVM backplane traffic.Specifically: Is it considered a best practice to separate the CVM backplane (CVM-to-CVM traffic, Stargate/metadata replication, etc.) onto a dedicated network or VLAN? Or is it generally recommended to keep the backplane traffic on the same network as the CVM/host data network (as long as bandwidth and latency requirements are met)? Assuming a standard production environment (10/25GbE, properly sized switching, no extreme east-west congestion), does separating the backplane provide measurable operational or performance benefits? Is it buggy in therms of troubleshooting? does it mainly add complexity without real gain?I’m particularly interested in official guidance or field experience from larger deployments.Thanks in advance!

Hi, We have two cluster, Prod and DR. We have protection policies all set up, as well as recovery plans. However, when performing a planned failover (for testing) ​​​​​​, the execution of the recovery fails. But it also succeeds… with warnings. The warnings say as follow:------VMs/Recovery Points detected on Prism Element(s) with unsupported licenseIMPACTSome VMs might not be recovered.CAUSESome of the VMs/Recovery Points are located on Prism Element(s) with unsupported license.RESOLUTIONMake sure that the Prism Element(s) have supported license. Supported License includes Ultimate License or Pro license with add-on advanced replication.-----The (planned) failover is also successful - so why the warnings? We have Pro licence. As far as I understand it, we need Ultimate licence for Test failover, but not for the planned failover (as long as we don’t do staging in bringing VMs back up). Are these warnings a red herring? Also, what about unplanned failover? Will we also just get the warni

From PC/VMs - select VM - Power Operations - Power onTasks comes back as failed   

HI!Microsoft certificates for Secure Boot expire in June 2026Will AHV, CVM, and VM legacy boot continue to function properly after the certificate expires?Secure Boot expiration will only affect guest VMs using UEFI? 

Hello, we are experiencing issues trying to deploy AppsAnywhere appliances (based on Rocky Linux). Issue as I understand is AppsAnywhere appliances doesn’t come with correct drivers for Nutanix. Official line from AppsAnywhere is they currently don’t support Nutanix, but their support and development teams are in contact with me via support case. Couple of years back when we migrate from VMware we used Nutanix Move and a root account, I guess this take care of the drivers, and appliance works fine.We now have a new Nutanix cluster and like to deploy the latest build of AppsAnywhere, but we no longer have access to VMware. We tried following to deploy: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA03200000099TXCAY and https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_7_5:mul-ova-deploy-as-vm-t.html but the appliances only boot in to an emergency mode! I have a request and a question…Request: If you can please vote for AppsAnywhere to s

HiI’m looking for guidance on the best practice to upgrade a Metro Availability setup with a Witness VM and would like to confirm the recommended and supported approach.Scenario: Two AHV clusters configured with Metro Availability External Witness VM providing quorum on a third site Prism Central deployed (one per cluster) Upgrade-related questions: During maintenance, is it recommended or even possible to: Temporarily pause or disable the Witness service Upgrade Prism Central Re-enable the Witness afterward Or is this not required / not supported? Can Prism Central be upgraded without impacting Metro Availability, assuming both clusters remain healthy and communication between them is intact? My concern is the following scenario: During a Prism Central upgrade, communication with the Witness is temporarily lost due to the reboot of the VM or the services Both clusters are still communicating correctly with each other all time In that case, should the env

Hello,I’m reviewing the official Nutanix documentation regarding Metro Availability with Witness VM, and I have a question I’d like to clarify.We are planning a Metro Availability (synchronous replication) setup between two Nutanix AHV clusters, and we would like to deploy a Witness VM in a third site to provide quorum and avoid split-brain scenarios.From what I have seen so far in the official Nutanix documentation, most references to Metro Availability with a Witness VM seem to be focused on VMware HA (ESXi) environments, and I have not found a clear and explicit confirmation regarding AHV-to-AHV Metro Availability using a Witness VM.Could someone please confirm: Whether Metro Availability between two AHV clusters using a Witness VM in a third site is officially supported And if there is any official documentation or KB that explicitly covers this scenario for AHV I just want to make sure the design is fully supported before moving forward.Thanks in advance for the clarifications!

hello,I’ve made rufus stick of the iso.. get stuck on “getting AOS ..”I’ve tried to install via cimc attach dvd and used the iso phoenix file.. get stuck on “getting AOS..”“INFO Getting AOS version from /mnt/iso/images/svm/nutanix.installer package.tar.p00 This may take a few minutes if phoenix is running from BMC”and then you can wait for hours …. all help is welcome.kind regards,johan claes

We are using Nutanix Data protection APIs to compute the changed regions between VM recovery points, where we are seeing in-consistent behaviour. API version - v4.1API First we do discover cluster on Prism central IP - /api/dataprotection/v4.1/config/recovery-points/{extId}/$actions/discover-cluster Then we Compute VM change regions on Prism Element IP - api/dataprotection/v4.1/content/recovery-points/{recoveryPointExtId}/vm-recovery-points/{vmRecoveryPointExtId}/disk-recovery-points/{extId}/$actions/compute-changed-regionsSo for Second request the start offset is provided as 0 to compute the regions from the start. It provides the change regions and let’s say the last offset changed is n. Now when we request the same compute regions API with the start offset n, it stills gives more compute regions which should not be the case as the last request ended the compute regions in n. We check below meta data response for if the response in paginated - isPaginated - flag nextOffset - extraIn

Hello All,We are trying to create disk on a VM from a source VM Disk, It was running fine but after sometime it started to error out with error - VMM-10000:Failed to perform the operation due to an internal error. API Used - /api/vmm/v4.1/ahv/config/vms/{vmExtId}/disksAHV - 10.3AOS- 7.3Prism - 7.3 CVM acropolis logs - 2026-01-29 10:43:36,252Z INFO base_task.py:635 Running task b417bd15-c4e9-4297-6b2d-2830f3afd181(VmDiskCreate 3aac3b95-f5ef-48a5-5db3-fb18647ee0e5)2026-01-29 10:43:36,257Z WARNING client.py:89 CastorRPC returned error 8.2026-01-29 10:43:36,267Z INFO base_task.py:775 Task b417bd15-c4e9-4297-6b2d-2830f3afd181(VmDiskCreate 3aac3b95-f5ef-48a5-5db3-fb18647ee0e5) failed with message: RPC GetVolumeDiskPath forwarded to Castor failed with error Unknown volume disk 8c3cadcc-6cf3-4749-9447-0a8078913db0Checked the Source Disk ID  8c3cadcc-6cf3-4749-9447-0a8078913db0, it is correct in the infra and Source VM Disk is shown on acli VM Disk list.Check Cluster health status -   ncc healt

HiI’m in the process of designing a Metro Availability architecture between two identical AHV clusters, with each site having its own Prism Central.The first cluster has already been deployed, and some VMs have been migrated to it from the customer’s legacy VMware environment. Once those VMs were running on the first AHV cluster, I assigned them a temporary local Protection Policy (within the same cluster and PC) as a precaution, in case a restore was needed during the following days. The idea is to have at least 1 daily recovery point with a retention of 7 days.At the moment, all these VMs are located in the cluster’s default container. In order to implement Metro Availability between both clusters, my understanding is that I need to: Create a new container with the same name on both clusters  Migrate the VMs from the default container to this new Metro container Then create the sync policy between both sites etc. Since these VMs are already in production, I’d like to minimize s