Nutanix Cloud Infrastructure

Hi,I am trying to deploy an AHV cluster using Nutanix Foundation VM against HPE DX380 G12 servers with iLO7, but the deployment consistently fails in Phase 1 during "Preparing installer image".The relevant error in the VM Foundation log is:Imaging requires Foundation HTTPS to be enabled on port 8001 for nodes that require HTTPS boot media.What I have verified so farOn the Foundation VM:firewalld is not running port 8000 is listening port 8001 is not listening at all curl -vk https://127.0.0.1:8001 returns connection refused curl -v https://127.0.0.1:8000 returns wrong version number, which seems to confirm that port 8000 is only serving HTTP, not HTTPS ss -lntp | egrep '8000|8001' only shows *:8000 nginx -T does not show any active listen 8001 ssl configurationThe Foundation process listening on 8000 is: /home/nutanix/foundation/lib/python/bin/python3.9 /home/nutanix/foundation/bin/foundation --foreground Deployment behavior All nodes fail with the same status:fatal: Preparing installe

I have a 1 node clusterOuter AHV - 10.1.10.103Outer CVM/Prism - 10.1.10.82Data Service ip - 10.1.10.95Network-0 having vlan id 1490 - gateway - 10.1.149.1, useable ips 10.1.149.2 to 10.1.149.61Prism - https://10.1.10.82:9440/-------------------------------------------------------------------created a 3 node nested clusterAHV VM1 - 10.1.149.51AHV VM2 - 10.1.149.53AHV VM3 - 10.1.149.55Data Service ip - 10.1.149.11 Inner Prism - https://10.1.149.52:9440/nested CVM1 - 10.1.149.52nested CVM1 - 10.1.149.54nested CVM1 - 10.1.149.56vlan1 having vlan id 1490 - gateway - 10.1.149.1, useable ips 10.1.149.2 to 10.1.149.61-------------------------------------------------------------------I am trying to create a Distributed FSVM on the nested cluster, Creating Distributed FSVM on inner cluster on vlan 1490  Client Network - 10.1.149.12,10.1.149.13,10.1.149.14  Storage Network - 10.1.149.15,10.1.149.16,10.1.149.17,10.1.149.118FSVM creation is failing in cluster initialisation with error as CVM not ab

Hello, I have recently deployed nutanix with Foundation, and every went well and I can access the PE from web browser. But when I go the Virtual Switch section, I cannot See vs0 in Switch Tab, not sure what is the issue. I go to Cluster Setting and Reboot the cluster, but it keep on processing and so on entering in maintenance mode. Can anyone help.    Regards

Cloud-based disaster recovery with Nutanix MST (Multi-cloud Snapshot Technology) gives organizations a cost-effective way to replicate VM snapshots to object storage targets like AWS S3, Azure Blob, or Nutanix Objects and recover workloads when it matters most. Object storage is purpose-built for durability and geographic distribution, which makes it an ideal replication target. The trade-off has always been recovery speed: pulling data back from object storage to the AOS cluster is slower than reading from local NVMe or SAN-backed storage, and for large workloads that gap translated into hours of hydration time before a recovered VM could power on. For latency-sensitive workloads including clinical applications, financial systems, and operational databases, that recovery window was the one remaining challenge to address.Nutanix Instant Restore changes the equation for MST-protected workloads. Now generally available in AOS and Prism Central 7.5.1, it decouples recovery from object sto

We have created Auto shutdown playbook of AHV host with scheduled but facing issue, when Prism Central ON , these scheduled initiated before time and we not  able to to access prism central , so disable  playbook task. Prism element started then PC started and excuted these playbook schedule and shutdown 2 AHV from Prism cluster.

Dear Community members,We are using Cisco HX with following specifications and are interested to know for the proposed nutanix configurations, we need to know the pros and cons on the proposed specs and also would like to know or need to discuss on future expensions.HCI Configuration:CPU 59.73%120.42 GHz Consumed201.6 GHz Total96 Total Physical CoresMemory 87.09%1559 GiB Consumed1790 GiB TotalRaw Storage 75.57%13.48 TiB Consumed17.84 TiB TotalOther DetailsIOPS 4327Read/Write Ratio44/56Estimated Daily Usage28.25 GiB Proposed Specications:  Part No Description Qty NX-8170-G10-6515P-CM NX-8170-G10, 1 Node; 2x Intel Xeon 6515P processor (2.3 GHz/ 16-core/ 150W, Granite Rapids SP) per node 3 C-MEM-32GB-6400-CM 32GB Memory Module (DDR5-6400 RDIMM) 72 C-NVM-7.68TB-AB1A-CM 7.68 TB NVMe SSD - PCIe Gen5 (U.2) 12 C-LOM-10G2D1BT-CM LOM Module: Broadcom 10GbE, 2-port, Base-T NIC (BCM 57416)

HiI have a customer with an old Nutanix AHV Cluster:Prism Central: pc.2023.4.0.2  AOS: 6.5.6.6  AHV: el7.nutanix.20220304.511 We wil deploy a new Nutanix AHV Cluster:Prism Central: 7.5.0.6  AOS: 7.5.0.6 AHV: 11.0.0.2  But the problem here is Veeam compatibility between enviroments. Right now the customer has two Veeam 12 apliances, the initial proposal was to eliminate one of them and use a single Veeam appliance with Veeam13.However when I was checking the compatibility matrix I can see the following info:https://helpcenter.veeam.com/docs/vbr/userguide/ahv_system_requirements.html?ver=13https://portal.nutanix.com/page/compatibility-interoperability-matrix/software?partnerName=Veeam&solutionType=Data%20Protection&componentVersion=all&hypervisor=AHV&validationType=all As far as I understand from the previous links if you want to use Veeam 13 you need at least:Prism Central → pc.2022.6 or above AOS → 6.5.6.6 or above AHV → 10.3.1.1 or above So checking the inventory from

Hello,I have some hands-on experience with Nutanix AHV. Currently, we are starting a project that involves a full migration of our Nutanix environment from on-premises infrastructure to Azure NC2.I have been searching for an official step-by-step guide or a recommended migration workflow, but so far I have not been able to find a clear document that explains the correct process for planning and executing this migration.Could anyone please share documentation, best practices, or a high-level migration flow for moving workloads from Nutanix AHV to Azure NC2?Any guidance or references would be greatly appreciated.Thank you.

Hello,  I’ve deployed several test Nutanix Single-Node clusters for test purposes. Actually I’m encountering strange error during LCM update for AHV (I’m running version 10.0.1.6 update to version 10.3.1.2 is available). During update process LCM returns an error: Operation Failed. Reason: LCM operation update failed on leader, ip: [x.x.x.x] due to Upgrade failed: Unable to run upgrade plugin prepare_reimage: exit status 1Plugin stdout:Staging AHV media to /media/ahv.iso'/dev/sdd' -> '/media/ahv.iso'Preparing for reimagingAHV installation on LVM, PV device: /dev/sda3Plugin stderr:No symlink matching */md/* or */disk/by-id/* found for block device /dev/sdaFailed to prepare for reimaging. Logs have been collected and are available to download at /home/nutanix/data/logbay/bundles/auto-lcm-log-collection-2026-03-12-27553431714.zip  I have no idea what can I do to resolve this issue, I’ve also tried deploying Prism Central but it seems that not a single version is compatible, because in

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