Installation & Configuration

I am trying to setup single node cluster using Foundation VM.  The Nutanix AHV provision and installation consistently failure on PowerEdge server with following error:CRITICAL clean_disks:151 Unable to initialize trusted storage deviceI assume; the installation could be failure because of the primary SSD drives are 447G drives.  But I do have other storage drives installed that has enough storage spaces. 2024-11-15 09:48:50,767Z log.py:102 INFO svm.py:733 Output of lsblk command. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTsda 8:0 0 447.1G 0 disk sdb 8:16 0 447.1G 0 disk sdc 8:32 0 745.2G 0 disk - sdc1 8:33 0 10G 0 part - sdc2 8:34 0 10G 0 part - sdc3 8:35 0 40G 0 part - sdc4 8:36 0 685.2G 0 part sdd 8:48 0 745.2G 0 disk - sdd1 8:49 0 10G 0 part - sdd2 8:50 0 10G 0 part - sdd3 8:51 0 40G 0 part - sdd4 8:52 0 685.2G 0 part sde 8:64 0 3.5T 0 disk - sde1 8:65 0 3.5T 0 part sdf

I am working to create a 4 node cluster.  I have 4 Dell Optiplex 7000s, each with 64gb ram, core i7 processors (12 cores) , I have a 32gb Samsung USB for the boot drive and 2 - WD Black SN770 2TB NVME drives for storage.  the install completes successfully.  but upon reboot, i get a couple of errors right after i get the login prompt and the CMV will enter a paused state.  

Hey.I have an old Nutanix appliance (NX-1065-5G)I’ve been told in this  post I want to install on my appliance AOS 6.10 (with competible AHV),Then I want to deploy Prism Central, In order to use Microsegmentation and self-service (Calm) It is really possible? my hardware support that? according to the Compatibility and Interoperability Matrix, deploy AOS 6.10 not supported But I successes to deploy it (by install CE then upgrade with Foundation tool)  Thanks Eviatar

Could we deploy a nutanix robo cluster using 3-nodes ? How it would be licensed ?

We have bought 4 units Lenovo Think Agile HX630 V3 ROBO Integrated System (IS) with SW-NCI-STR-PR license. Which one is the best practice deployment scheme :Opsi 1 : applied those license into one cluster consists 4-nodesOpsi 2 : applied those license into 3-nodes cluster and a single node clusterOpsi 3 : applied those license into two clusters which consists 2-nodes per cluster 

HelloI’m testing an install on a DL360 Gen10+ server. The server has an NS-204i boot controller with 2 x  disks and there is an MR216 controller with 2 x 3.84TB disks (believe they are PM893a).I have tried the install a few times but have been wiping the server each time it fails. I’ve now got to the stage where it fails with the same error each time so I need to know why its failing."CRITICAL svm_rescue:1046 No suitable SVM boot disk found"Should I have three arrays in the server? One for AHV, one for SVM/CVM and one for storage?How/where do I run lsscsi" to check for partitions that may need to be removed?Thanks in advance for any help with this.ThanksRussell

Background I have been using Dell Apex Backup Services (AKA Druva) for the past eleven months. Last month we deployed our first Nutanix AHV Cluster. Provisioning a backup proxy VM on AHV to facilitate backups to Dell Apex Backup Services should have taken a few hours at most but instead it took nearly a week.  Provisioning Backups to Dell Apex from Nutanix AHV  What you are doing here is getting two VMDK files from a link in the Druva Management Console, building a VM on AHV, and importing/attaching those VMDKs to your new backup proxy VM. This VM will be the backup and restore target for all of your storage volumes and VMs on AHV. You will need to configure networking for the VM and install a token (You get the token from the Management Console.) on the backup proxy VM. Next you will go back to the Management Console and (provided you made it this far) configure one or more of the AHV VMs for backup. You will also have to enable the Nutanix iSCSI Data Services IP Address and open seve

I have CE 2.1 installed and running nested in ESXi 7.02 but when trying to power on VMs, I notice under the Hardware tab it shows CPU oHz and memory 0Gib. I do have VM tools installed

Hi,I’m getting this error when trying to register the Prism Central. Has anyone seen this before and is there an easy fix?CE version 2.1PC 2024.2 Thanks,

Hello,we are evaluating Nutanix for our datacenter deployment, and were thinking to install CE on one of our older DL360 Gen10 servers that we have here, just to see the interface, UI etc.However, I am completely failing to install it. Neither USB (tried Rufus with GPT and MBR, as well as unetbootin) nor mounted ISO via ILO are being recognized. I tested with Proxmox ISO, and it loaded instantly via ILO/ISO.Any recommendations on what to check or what might be causing the issue?Thanks

Hello,Newbie here. We are just moving off of VMware to Nutanix and have an issue. We use HPE OneView to manage bare metal servers that we have at various locations and is running in VMware but HPE tells us it’s not supported on the Nutanix hypervisor. We can’t be the only shop that has a OneView appliance and are moving to Nutanix from VMware. So I am reaching out to the community here in the hope that someone has been down this path and can point the best way forward to still use OneView.

HeyMy environment:   And Prism Central 2024.2 I have some old NX-1465-G5 appliance and try to deploy AOS 6.10 as I been told in this topicCompatibility Check: Upgrading Nutanix NX-1465-G5 to AOS 6.10 | Nutanix CommunityMy procedure was:Install last CE on my appliance (all 4 nodes) Run Foundation tool Deploy Prism Central via Prism-Element (after config a network and set NTP / DNS servers) Connect Prism-Element to Prism-CentralAbout the end of the PC deployment (post-install stage) I get the error:Encountered Exception in post_deployment step: Failed to enable micro services infrastructure on PC: deploy msp:Error deploying addons: failed to deploy monitoring addon: failed to deploy and verify kube-prometheus: failed to verify kube-prometheus: Operation timed out: failed to verify kube-prometheus: expecting 1 available replica of k8s prometheus in ntnx-system namespace. Currently running: 0But the Now, at Prism-Central, Under Microsementation (That I need to enable), I cant to enable the

Due to recurring discussions with customers, here again the question about the technical background. why can't I split Nutanix nodes in a cluster across 3 locations (these are less meters apart)? ESXi can do that, other virtualization solutions too (MS HV, PVE).I'm interested in a technical explanation, that it's not supported, I know, but why?In fact can we build stretched Clusters across Locations (No geolocations)? Thanks in advance  

Hello, anyone can help me ? i have problem on my nutanix ce, i cannot login to my prism, it just processing like in my pics.  

I was able to successfully overcome the lack of the proper igc modules for my Intel 2.5 gbps nics on my protectli homeserver (like a NUC but not).  The blog here helped, and I simply downloaded the igc module from Satoshi’s site.  But now the problem is I restart the installer with “./ce_installer && screen -r”, but it fails with the following error that makes it sound like it is upgrading versus installing for the first time.  Following is picture of the error:   Is there way to signal this is as a first time installation?  Should I wipe all the disks in my system before doing the install?  (The disks are currently part of a Ubuntu KVM install that I assumed could be be blown away by the Nutanix installation.)Thanks in advance for any tips.

Hi, is there anyway to disable ICMP timestamp request remote disclosure on nutanix? Or is there any articles that states that this is necessary for nutanix functionality.

Long story short we are swapping over to newer Nutanix chassis and replacing a few nodes. The previous tech had issues imaging the new chassis. However, in the prism hardware tab, the chassis is present (i think the previous tech was able to get it added somehow despite previous issues). I was able to go through foundation and get the new chassis nodes imaged and ready to be added back to the cluster, but the information remains in Prism and we cannot remove it. The new nodes show up when we select the expand cluster option, but the information (host ips, etc.) matches what is already in Prism, so it cannot be added. We are using a 5.x AOS and cannot upgrade.We need a way to forcibly remove the stale information regarding the nodes that is still present in the cluster. So far we have tried the following with support and are hoping someone has possibly seen something like this before. We tried removing the nodes through Prism, but the 1st node we tried to remove is showing the meta data

Attempting to install Nutanix CE on home build system for home lab. Running into issues finishing the installation. When the installer attempts to create a virtual machine it’s unable to find the KVM kernel module and it doesn’t look like qemu-kvm is actually preinstalled on the ISO. After the installation fails and kicks me into a fallback TTY I attempt to load the KVM module with no success due to it not being installed. After installing qemu-kvm I’m unable to get back into the installer to finish the installation. Seems like an oversight in the latest ISO? Any assistance on this would be greatly appreciated. Attempting to install on bare metal. 

What is the best way to rebuild a single node cluster to a 5 node cluster with all the VMs intact with minimal downtime?

I am trying to get the WInPE drivers so I can support our virtual device hosted on a Nutanix system.  However, every link directs me to the Nutanix support page where I have to activate my ID with a licence code or serial number.  I am the consumer of the system, I have none of these values, and my server team who might have these will not give me the codes.  What can I do to get the drivers I need so I can do my job and test our OSD processes with a Nutanix VM client?

Hi I am running AHV and CVM on centos 7 OS along with Nutanix instance with below software's version.  AOS - el7.nutanix.20191030.415CE 2019.11.22 I wanted to do patch/upgrade of AOS version on centos 7 OS.Please let me know the steps to do this activity, if it is still possible.  Thanks!!

Hi everyone, I was looking at the documentation and the switches recommended by Nutanix itself:https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2050-Physical-Networking.html Is there any reason why no Extreme Networks switch is on the list? Some clients have requested that the provided equipment be on this list, but there are some very similar (if not fully compatible) models with several Extreme Networks devices, like the Extreme Networks 7520-48Y or Extreme Networks 8520-48Y.Is there any reason for this? Or is it simply because someone needs to approve it from either side?

After completion of foundation of new Nutanix nodes, what are the steps & network configurations required for AHV & shifting the nodes from L2 switch to L3 switch / core switchPlease let me know the sequence . Thank you.

We made an update our Prism Central to 2023.4.0.2 version.Our administrators are unable to login to PC via ldap user after we made update to 2023.4.0.2 version.Only local admins could to login.I tried to upgrade PC to new version 2023.4.0.4 .But progress is stuck on 5 percent (Preupgrade step)LCM not works.We tried cluster restart.But it didn't help.Please help us to find some solution in this case

Hi all,First time posting, a little background on me and my environment. I am a VCP and have been doing VMware virtualization for the last 20 years. I have 2 Nutanix blocks at home loaded with 3060-G7’s. It’s a pretty nice setup (It went out of warranty, so was given to me to take home, so pretty lucky there.) So I got it all loaded up with community edition and everything was running smooth. I bought a new Uni-Fi 10gb switch for home, as well as a plethora of other unifi products. Here is where I fouled up big time:I set up link aggregation Active-Active on my only vswitch. After changing it, I realized I didn’t have any SFP’s for my switch. So I connected them to my UDM-SE. I assumed my UDM-SE supported LACP, but it did not and it threw my entire network into a frenzy. I eventually figured out that having the blades plugged into my UDM-SE, with LACP enabled, was causing a lot of routing confusion (which took my own home network offline for sometime). Next bad decision, I deleted the