The Foundation for Your Hybrid Cloud
Recently active
Hi All, we have several Nutanix Clusters that are all managed by Prism that is on its own machine.ย ย We are looking to move one of the 4-Node Clusters to the DR Site that is on a different subnet, which means a RE-IP will be needed of this Nutanix Cluster.ย This is going to mean RE-IP of the Dell iDRAC setup, Nutanix AHV hosts IP, Nutanix CVM IPs, etc.ย ย Is a RE-IP straightforward? Or is it generally recommended to avoid a RE-IP due to issues and instead rebuild at the DR site on the network there?ย Thanks
After a ransomware incident, how do you choose the recommended recovery point for a VM when the attackerโs dwell time is unclear? The newest copy may still include persistence, while going further back can lose business data. Do you compare several candidate points in an isolated environment and validate identity, application data, and a real workflow before reconnecting? What decision criteria do you capture in the runbook?ย Disclosure: I work at CyberSnap on ransomware recovery tooling.
Snapshot at 10:00. Replication at 10:12. Disaster at 10:45. Is Your RPO 33 or 45 Minutes?ย A snapshot was created atย 10:00 AM.Replication completed successfully atย 10:12 AM.A disaster occurred atย 10:45 AM.Your production site is completely unavailable.Assume the 10:00 AM snapshot is the latest valid and recoverable point available at your DR site.ย What's your actual Recovery Point Age: 33 minutes or 45 minutes? And why?ย The question looks simple, but the answer depends on an important distinction in Disaster Recovery architecture:Is the replication completion time the same as the timestamp of the data you can actually recover?ย Let's break it down.ย 1. The Architecture ScenarioConsider two Nutanix clusters: Site A:ย Production Cluster Site B:ย Disaster Recovery Cluster A protected workload has a snapshot created at 10:00 AM on Site A.ย The snapshot represents the workload's point-in-time data state at 10:00 AM, within its consistency guarantees.ย Replication transfers the required data and
Hi,Iโm looking for clarification on AHV Metro Availability behavior and the supported procedure for temporarily isolating an entire site during network maintenance (switching replacement).The environment consists of two Nutanix AHV clusters with synchronous replication, managed through Prism Centrals (one per site)ย and a Witness VM deployed at a third site over a VPN. As aditional info AOS and PC versions are PC/AOS 7.6ย and AHV 11.0.2 .The customer reported the following sequence during a switch replacement: They disconnected the VPN to the witness, intending to make it unreachable from both clusters (that should avoid automatic launch ofย any recovery plan). Then theyย disconnected one swich on cluster A, so cluster B was unable to reach it. According to the customer, at that moment recovery automatically started and the VMs from cluster A were recovered on theย cluster B. As a result they reported duplicate VMs and had to determine which instances to retain (splitbrain scenario).
Move Appliance Deployment Nutanix Move 6.3.3 appliance deployed successfully in the VMware environment. VMware Source Configuration VMware vCenter added and source VM inventory discovered successfully. Nutanix Target Configuration Nutanix AOS/AHV destination added and validated successfully. VDDK-Free Migration Plan Migration plan created using Move 6.3.3 DirectPath without supplying VMware VDDK. Nutanix documents DirectPath as the Move 6.3.3 migration method that provides an ESXi migration path without requiring VDDK. Automatic Source VM Preparation Windows source VM preparation completed successfully. Source VM Validation VMware CBT and VMware Tools connectivity validated successfully. Initial Data SeedingMOVESnap-0 created and initial VM data seeded to the Nutanix target. Ready for Cutover VM successfully reached Ready to Cutover status. Periodic Data Synchronization Periodic synchronization continued between VMware and AHV before cutover. Source VM Quiescence Source VMware VM was s
We are encountering an issue during the NCC health check on our Nutanix cluster and would like to know if anyone has experienced a similar problem and can share the resolution.AOS Version:ย 7.3.1.1 NCC Version: 5.2.1 Hypervisor: AHVย v.10.3.1.9 Cluster Size: 16
Whatโs a vTPM?The vTPM module is the virtual equivalent of a physical TPM chip. It securely stores cryptographic keys used for BitLocker drive encryption, Windows Secure Boot, measured boot, and attestation features. Each vTPM holds unique cryptographic material, and without those keys, a VM may not be able to decrypt its disks or boot securely.Why Does Protection Domain (PD)-Based DR Fail with vTPM VMs?Legacy Protection Domains were built before vTPM was introduced, so PDs replicate only VM disks and metadata, not the vTPM device or its secure state. vTPM keys are encrypted and tied to the local clusterโs KMS. During PD-based replication, those keys cannot be transferred to the DR site. As a result, a vTPM-enabled VM may fail to boot or lose access to encrypted volumes after DR failover.Why Does Protection Policy (PP)-Based DR Support vTPM VMs?Modern Protection Policy-based DR introduces full vTPM awareness. It replicates vTPM state and keys alongside VM data. It integrates with Nutan
From Business RTO/RPO to Nutanix DR Architecture: Where Should the Design Really Start?ย Should we start designing Disaster Recovery by choosing a replication technology, or by understanding what the business actually needs to recover?In enterprise DR architecture, achieving a technical replication objective does not automatically mean achieving business continuity.A successful DR design must translate business recovery requirements into appropriate protection strategies, recovery orchestration, infrastructure capacity, and validated application recovery procedures.Let's consider a simplified, fictional enterprise scenario.The Business ScenarioAn organization has three critical workload groups with different recovery objectives:Workload Required RPO Required RTO Core Banking 0 minutes 15 minutes ERP 15 minutes 2 hours Internal HR 4 hours 8 hours These values are hypothetical business requirements, not guaranteed Nutanix recovery performance.Although all three workloa
I am not able to test drive any more. What has happened to my account? Will someone fix this?
ย 100% of your VMs are back online. But your customers still cannot complete a single transaction.ย How is that possible?Imagine a Disaster Recovery test where:โ All protected VMs are successfully recovered.โ Nutanix Recovery Plan execution completes successfully.โ The infrastructure dashboard reports healthy VMs.โ The business application remains unavailable.ย The infrastructure recovered. The business service did not.This is a challenge that goes beyond replication technology and VM boot sequencing.It raises a fundamental architecture question:ย Did we design the recovery process around virtual machines or around business service dependencies?ย 1. The Scenario: Mobile Banking on Nutanix AHVย Consider a fictional banking environment with a Mobile Banking application consisting of: Identity and DNS Services Database Tier Middleware and API Services Application Servers Load Balancers External Payment and Authentication Integrations During DR failover, the application VMs are started
ย Hello Nutanix Community,I'm trying to expand an existing 3-node Nutanix cluster by adding a fourth node, but the expansion process fails during the pre-expansion checks with the following error:Failure in pre expand-cluster tests.Errors:Precheck: test_cassandra_ssd_size_check failed.SSD tier on nodes ['172.22.129.4'] is not sized to accommodate expected metadata growth on cluster.Refer KB-8842 for more details.Environment Details: Platform: Cisco UCS C240 M7 AOS Version: 7.0 Storage Type: Hybrid Existing Cluster: 3 Nodes New Node: 1 Node (4th node) Additional Information: The new node has the same SSD and HDD configuration as the existing nodes. The SSD capacity on the affected node (172.22.129.4) is identical to the other cluster nodes. The issue occurs during the pre-expansion validation stage. My Questions: What could cause this error if all nodes have identical SSD configurations and capacities? What troubleshooting steps would you recommend to identify the root caus
Hi Nutanix Team,We are planning to run Windows/Linux VMs on Nutanix AHV with the following environment: Cisco UCS X210C M8 Nutanix AHV Dell PowerMax 2500 25GbE network Can a Windows/Linux Guest OS running on AHV use its native iSCSI initiator to directly access an external Dell PowerMax storage LUN?The architecture is:Guest OS โ iSCSI Initiator โ AHV/OVS โ 25GbE โ Dell PowerMaxIf yes, is this officially supported by Nutanix? Could you please provide the relevant documentation?Thank you.
Phase 1: Foundation Orchestration & Pre-Imaging Preparation1. Foundation Session InitializationFoundation does not immediately image the server. It first creates and activates its internal imaging workflow.Foundation associates the imaging workflow with a NodeConfig object representing the target CVM and spins up local CherryPy/Flask microservices on your laptop or deployment machine to handle the imaging tasks.2. Node DiscoveryFoundation attempts to locate the physical nodes. It broadcasts over the local Layer 2 network segment using IPv6 link-local multicast (via the WS-Discovery protocol). It listens for replies from factory-fresh nodes or unconfigured hardware listening on the network.Foundation is using its internal RPC mechanism to resolve information from the node before applying the final configuration.3. Network Provisioning & VerificationFoundation begins constructing the network configuration that will ultimately be applied to the target environment.ย It subsequently
We operate a hybrid VDI environment: Windows 10 on vSphere and Windows 11 on Nutanix AHV(Horizon 2603/2606).While vSphere works flawlessly, we face two critical blockers on Nutanix AHV that force inefficient manual workarounds.We request feature parity with vSphere.ย Issue 1: Manual Pool Registration LimitProblem: When deploying VMs from a master image with Horizon Agent pre-installed, only one VM successfully registers in a Manual Desktop Pool on Nutanix AHV.Current Workaround: To register multiple VMs, we must exclude the Horizon Agent from the master image and install it individually on every single VM after provisioning.Expectation: Nutanix AHV should support standard golden image deployment (Agent pre-installed) allowing multiple VMs to register simultaneously, just like vSphere.ย Issue 2: Persistent Black Console After DisconnectProblem: After a user disconnects a session, the VM's console screen remains Black. Administrators can not view the desktop state or perform maintenance vi
While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible with enabling Microservices Infrastructure.* Root Cause Analysis:When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices. For CMSP deployment on Prism Central, the internal CMSP services use the following default networks: 192.168.5.0/24 โ Kubernetes infrastructure network 10.100.0.0/16 โ Kubernetes Pod network 10.200.32.0/24 โ Kubernetes Services network The upstream network environment must not overlap with these network ranges. Since Kubernetes cannot differentiate between internal container traffic and the production management network, CMSP prechecks intentionally block the deployment to prevent potential routing conflicts.* Solution:If the environment requires using these subnet ranges in the upstream network, you must cha
๐๐ก๐๐ญโ๐ฌ ๐ ๐ฏ๐๐๐?- The vTPM module is the virtual equivalent of a physical TPM chip.- It securely stores cryptographic keys used for BitLocker drive encryption, Windows Secure Boot, measured boot & attestation features.- Each vTPM holds unique cryptographic material, and without those keys, a VM may not decrypt its disks or boot securely.๐๐ก๐ฒ ๐๐จ๐๐ฌ ๐๐ซ๐จ๐ญ๐๐๐ญ๐ข๐จ๐ง ๐๐จ๐ฆ๐๐ข๐ง (๐๐)-๐๐๐ฌ๐๐ ๐๐ ๐๐๐ข๐ฅ ๐ฐ๐ข๐ญ๐ก ๐ฏ๐๐๐ ๐๐๐ฌ?- Legacy Protection Domains were built before vTPM was introduced, so PDs replicate only VM disks + metadata, not the vTPM device or its secure state.- vTPM keys are encrypted and tied to the local clusterโs KMS.- During PD-based replication, those keys cannot be transferred to the DR site.- As a result, a vTPM-enabled VM fails to boot or loses access to encrypted volumes after DR failover.๐๐ก๐ฒ ๐๐จ๐๐ฌ ๐๐ซ๐จ๐ญ๐๐๐ญ๐ข๐จ๐ง ๐๐จ๐ฅ๐ข๐๐ฒ (๐๐)-๐๐๐ฌ๐๐ ๐๐ ๐ฌ๐ฎ๐ฉ๐ฉ๐จ๐ซ๐ญ ๐ฏ๐๐๐ ๐๐๐ฌ?- Modern Protection Policy-based DR introduce
While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible to enable Microservices Infrastructure.๐ก ๐ฅ๐ผ๐ผ๐ ๐๐ฎ๐๐๐ฒ ๐๐ป๐ฎ๐น๐๐๐ถ๐:- When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices.- For CMSP deployment on Prism Central, the CMSP internal services use the following default networks:ย --> ๐ฃ๐ซ๐ค.๐ฃ๐จ๐ช.๐ง.๐ข/๐ค๐ฆ - ๐๐ถ๐ฃ๐ฆ๐ณ๐ฏ๐ฆ๐ต๐ฆ๐ด ๐ช๐ฏ๐ง๐ณ๐ข๐ด๐ต๐ณ๐ถ๐ค๐ต๐ถ๐ณ๐ฆ ๐ฏ๐ฆ๐ต๐ธ๐ฐ๐ณ๐ฌย --> ๐ฃ๐ข.๐ฃ๐ข๐ข.๐ข.๐ข/๐ฃ๐จย - ๐๐ถ๐ฃ๐ฆ๐ณ๐ฏ๐ฆ๐ต๐ฆ๐ด ๐ฑ๐ฐ๐ฅ ๐ฏ๐ฆ๐ต๐ธ๐ฐ๐ณ๐ฌย --> ๐ฃ๐ข.๐ค๐ข๐ข.๐ฅ๐ค.๐ข/๐ค๐ฆ - ๐๐ถ๐ฃ๐ฆ๐ณ๐ฏ๐ฆ๐ต๐ฆ๐ด ๐ด๐ฆ๐ณ๐ท๐ช๐ค๐ฆ๐ด ๐ฏ๐ฆ๐ต๐ธ๐ฐ๐ณ๐ฌ- The upstream network environment cannot overlap with these networks.ย - Since Kubernetes cannot differentiate between internal container traffic and the production management network, the CMSP prechecks intentionally block the deployment
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
What actually happens?Traditional backups copy entire files or virtual disks, which takes time and slows down your system. Nutanix uses a Redirect-on-Write (RoW) architecture combined with instantaneous metadata pointers.1๏ธโฃ ๐๐ฉ๐ฆ ๐๐ฐ๐ช๐ฏ๐ต๐ฆ๐ณ๐ด ๐๐ณ๐ฆ๐ฆ๐ป๐ช๐ฏ๐จ (๐๐ฏ๐ด๐ต๐ข๐ฏ๐ต):- Instead of copying your data blocks, Nutanix copies the metadata map (the index or map that tells the system where your data blocks live on the physical disks).* The Process: The system takes a snapshot of this map, which takes milliseconds because metadata is incredibly small.* The Result: The original data blocks become read-only for that specific point in time.2๏ธโฃ ๐๐ฉ๐ฆ ๐๐ฆ๐ฅ๐ช๐ณ๐ฆ๐ค๐ต-๐ฐ๐ฏ-๐๐ณ๐ช๐ต๐ฆ ๐๐ฆ๐ค๐ฉ๐ข๐ฏ๐ช๐ด๐ฎ (๐๐ฐ ๐๐ท๐ฆ๐ณ๐ฉ๐ฆ๐ข๐ฅ):- The moment after the recovery point is created, your Virtual Machine (VM) keeps running and writing new data.* Old Data: Stays exactly where it was, safely frozen as your recovery point.* New Data: Instead of overwriting old data, any new changes are written t
The deployment of AHV/AOS through Phoenix ISO on a Hyper-V host failed before the actual imaging process could begin. During the Hyper-V customization stage, Phoenix terminated as it cannot find the required FAT32 partition. The deployment therefore stopped before Phoenix could continue with the normal AHV/AOS installation workflow.๐ก ๐ฅ๐ผ๐ผ๐ ๐๐ฎ๐๐๐ฒ ๐๐ป๐ฎ๐น๐๐๐ถ๐:- The underlying issue was related to the existing storage/partition metadata on the Hyper-V host.- Phoenix's Hyper-V customization logic was evaluating the existing disk layout and detecting the disk as having a previous partition structure.- The customize_hyperv.py script specifically flags sdo as your host boot disk. It triggers a function called Mounting Hyper-V FAT32 partition to search for a pre-existing staging partition.- Because /dev/sdo only contains standard Windows OS layout partitions (with an EFI system partition of only 99MB), it fails the hardcoded check for a size >= 1GB and triggers the FATAL halt.
์ฌ๋ฌ๋ถ, ์๋ ํ์ธ์,์ ํฌ ์ฌ๋ฌด์ค ํ ์คํธ ํ๊ฒฝ์ ์๋ EOSL Nutanix NX-3060-G4 ์๋ฒ์ Nutanix AOS ๋ฐ AHV์ ์ต์ ๋ฒ์ ์ ์ค์นํ๋ ๋ฐฉ๋ฒ์ ๋ํ ์๋ด๋ฅผ ๋ถํ๋๋ฆฝ๋๋ค.ํด๋น ์๋ฒ๋ ํ๋์จ์ด ์ง์ ์๋ช ์ฃผ๊ธฐ๊ฐ ์ข ๋ฃ๋์์ง๋ง, ํ ์คํธ ๋ฐ ์ฐ๊ตฌ ๋ชฉ์ ์ผ๋ก ์ฌ์ฌ์ฉํ๊ณ ์ถ์ต๋๋ค.์งํํ๊ธฐ ์ ์, ํด๋น ๊ตฌ์ฑ์ด ๋ ์ด์ ๊ณต์์ ์ผ๋ก ์ง์๋์ง ์๋๋ผ๋ ์ด ํ๋์จ์ด์ ์ต์ AOS ๋ฆด๋ฆฌ์ค์ ๊ทธ์ ์์ํ๋ AHV ๋ฒ์ ์ ์ค์นํ๋ ๊ฒ์ด ๊ธฐ์ ์ ์ผ๋ก ๊ฐ๋ฅํ์ง ์ฌ๋ถ๋ฅผ ํ์ธํ๊ณ ์ถ์ต๋๋ค.๋ค์ ์ง๋ฌธ๋ค์ ๋ํ ์กฐ์ธ์ ๋ถํ๋๋ฆฝ๋๋ค. ํ๋์จ์ด ํธํ์ฑ: NX-3060-G4๋ ์ต์ AOS ๋ฐ AHV ๋ฒ์ ์ ์คํํ ์ ์์ต๋๊น? ์๋๋ฉด ์ด ๋ชจ๋ธ์์ ์ง์ํ๋ ์ต๋ ๋ฒ์ ์ด ํน์ ๋์ด ์์ต๋๊น? ์ค์น ๋ฐฉ๋ฒ: Nutanix Foundation์ ์ฌ์ฉํ์ฌ ์ด ์๋ฒ์ AOS ๋ฐ AHV๋ฅผ ์๋ก ์ค์นํ ์ ์์ต๋๊น? ํ์ด๋ฐ์ด์ ์๊ตฌ ์ฌํญ: ์ด ํ๋์จ์ด์ ํ์ํ ํน์ ํ์ด๋ฐ์ด์ ๋ฒ์ ๋๋ ์ค์น ์ํฌํ๋ก๊ฐ ์์ต๋๊น? ์ค์น ์ ํ ์ฌํญ: EOSL ์์คํ ์ ์ค์น๋ฅผ ๋ฐฉํดํ ์ ์๋ ํ๋์จ์ด ํธํ์ฑ ๊ฒ์ฌ, ์ค์น ํ๋ก๊ทธ๋จ ์ ํ ๋๋ ๊ธฐํ ๊ธฐ์ ์ ์ ํ ์ฌํญ์ด ์์ต๋๊น? ๋์์ ์ธ ์ ๊ทผ ๋ฐฉ์: ์ต์ ๋ฒ์ ์ ์ง์ ์ค์นํ ์ ์๋ ๊ฒฝ์ฐ, ๋น์ด์ ์ฐ๊ตฌ์ค ํ๊ฒฝ์ ์ ํฉํ ๊ถ์ฅ ํด๊ฒฐ ๋ฐฉ๋ฒ์ด๋ ๋์ฒด ์ค์น ๊ฒฝ๋ก๊ฐ ์์ต๋๊น? ํด๋น ์๋ฒ๊ฐ ๋ ์ด์ ๊ณต์์ ์ผ๋ก ์ง์๋์ง ์์ ์ ์๋ค๋ ์ ์ ์ดํดํ๊ณ ์์ผ๋ฉฐ, ์ ๋ ์์ ํ ํ ์คํธ ๋ชฉ์ ์ผ๋ก๋ง ์ฌ์ฉํ ์์ ์ ๋๋ค.NX-3060-G4 ๋๋ ์ด์ ์ ์ฌํ ๊ตฌํ Nutanix ํ๋ซํผ์ ์ต์ AOS/AHV ๋ฒ์ ์ ์ค์นํด ๋ณธ ๊ฒฝํ์ด ์์ผ์ ๋ถ์ด ๊ณ์๋ค๋ฉด, ๊ด๋ จ ๊ถ์ฅ ์ฌํญ, ๋ฌธ์ ๋๋ ์ค์น ๊ฐ์ด๋๋ฅผ ๊ณต์ ํด ์ฃผ์๋ฉด ๋๋จํ ๊ฐ์ฌํ๊ฒ ์ต๋๋ค.๋์์ฃผ์ ์ ๊ฐ์ฌํฉ๋๋ค!
i need a nutanix command to change the ovs0 interfaces as theย command :nutanix@cvm$ manage_ovs --bridge_name br0 --interfaces eth0,eth2 --bond_name br0-up --bond_mode active-backup --require_link=false update_uplinksfrom AHV 11.2 doesnโt work if the cvm doesnโt reach to the gateway ,so if there is a command from ahv do that searched and found that command but i not sure it is valued or notย ovs-vsctl set port br0-up interfaces=eth2,eth4
Hi,Since upgrading to PC 7.6 / AOS 11.2 weโve tipped over the edge on available CPU resources and are experiencing some performance issues (Spikes in CPU Wait, application failures)ย weโve engaged with support who identified ADS/Solver being unable to moveย VMโs to reduce hotspots,ย because all hosts are hotspots, and weโre basically oversubscribed.ย I wonโt deny this, but we werenโt experiencing so many issues before the update.ย Support advice is to reduce vCPU allocation on vmโs that donโt need them. Weโve got a lot of VMโs reporting as over provisioned, the majority of these are windows VMโs with 2 vCPUโs our testing has shown that with only a single vCPU windows really doesnโt work well.ย So i have some questions:Has anyone else noticed an increase in consumed CPU resources following update to PC/AOS 7.6 Do others experience the same with windows server VMโs, or is it a feature of our environment that 2 vCPUโs is the minimum If you do experience the same, do you just live with a large
Please advise on vulnerability mitigation for nutanix-sa-57 security advisory and possible fix release date. We understand that upgrading to AOS 7.6 is the available option at the moment. ย The hardware is 3-node Lenovo HX650 V3 cluster.Please confirm the dark site upgrade sequence with the below bundles is correct, or if it can be done better.1 ย ย LCM Framework Bundle 3.4.0.12 ย ย NCC LCM Bundle 6.0.0.13 ย ย Nutanix Compatibility Bundle4 ย ย Prism Central LCM Bundle 7.65 ย ย Foundation LCM Bundle 5.116 ย ย AOS LCM Bundle 7.67 ย ย AHV LCM Bundle 11.38 ย ย LENOVO Firmware LCM Bundle 3.0All bundles to be uploaded and run from PE LCM except the "Prism Central Bundle LCM Bundle" from the PC LCM.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.