How It works

What is Nutanix Guest Tool (NGT)? Nutanix Guest Tools (NGT) is a software based in-guest agent framework which enables advanced VM management functionality through the Nutanix Platform. The solution is composed of the NGT installer which is installed on the VMs and the Guest Tools Framework which is used for coordination between the agent and Nutanix platform. The NGT installer contains the following components: Guest Agent Service Self-service Restore (SSR) aka File-level Restore (FLR) CLI VM Mobility Drivers (VirtIO drivers for AHV) VSS Agent and Hardware Provider for Windows VMs App Consistent snapshot support for Linux VMs (via scripts to quiesce) This framework is composed of a few high-level components: Guest Tools Service Guest Agent

Nutanix presents us with many management interfaces like HTML5(Prism), REST API, acli and ncli for managing and troubleshooting and maintaining work infrastructure.  We will look into how to access the Nutanix Command line Interface and what the capabilities and purpose of acli and ncli command-lets areaCLI: Acropolis Command Line Interface  Utility to create, modify and manage VMs in AHV. Provides extra abilities(commands) to manage AHV host networking, manual snapshot etc

Let’s say you want to know what are the uses and differences between Prism Element, Prism Central and Prism Pro   Nutanix Prism is the centralized management solution for Nutanix environments, however, Prism comes in different flavors depending on the functionality needed.   Prism Element: It is a service already built into the platform for every Nutanix cluster deployed. It provides the ability to fully configure, manage, and monitor Nutanix clusters running any hypervisors, however, It only manages the cluster it is part of.    Prism Central:

Many users are not aware that a recent change has been made to the default password setting of new Nutanix nodes. Specifically, the default password for the IPMI interface is now the serial number of the node itself (using capital letters). Please note that the node serial number is different from the block serial number. You can find more information regarding this change as per the Common BMC and IPMI Utilities and Examples Knowledge Base article.Also, if you desire to change the IPMI password, you can do so using the IPMI management utility located within the file system of the operating system running on the node. Further, you can even

What is the difference between the Redundancy Factor and Replication Factor? Redundancy factor 3 is a configurable option that allows a Nutanix cluster to withstand the failure of two nodes or drives in different blocks. By default, Nutanix clusters have redundancy factor 2, which means they can tolerate the failure of a single node or drive. The larger the cluster, the more likely it is to experience multiple failures. Redundancy Factor 3 requirements: Min 5 nodes in the cluster. CVM with 32GB RAM configured.

Shutting down and Restarting a Nutanix Cluster requires some considerations and ensuring proper steps are followed - in order to bring up your VMs & data in a healthy and consistent state. Nutanix is a Hypervisor agnostic platform, it supports AHV, Hyper-V, ESXi and XEN. This makes it all the more important to read the following Nutanix KB, which details the steps required to gracefully shutdown and restart a Nutanix cluster with any of the hypervisors. Nutanix KB : How to Shut Down a Cluster and Start it Again?  

Nutanix, like any other system is composed of several components including hardware, software and firmware. If a component has to communicate with another at any given moment, the connection has to be pre-integrated and supported. How do you keep-up and understand what is compatible with what? Easy! with our compatibility matrix. For example, you have a Nutanix block model NX-8035-G5 and you want to know the supported AOS and Hypervisor for the chosen Model. The matrix shows the AOS, AHV, and hypervisor compatibility for Nutanix NX and SX Series platforms and SW-Only Models qualified by Nutanix (such as Cisco UCS, Dell PowerEdge, HPE ProLiant and others listed here). For other platforms not listed here, such as Dell XC, Lenovo HX, and others, please see your

 Ever wondered what are some of the main services/components that make up Nutanix?The following is a simplified view of the main Nutanix cluster components.All components run on multiple nodes in the cluster and depend on connectivity between their peers that also run the same component. Cluster components ZeusKey Role

Want to know how to change the default credentials on the cluster? On Nutanix cluster’s if you have the default credentials you will receive an INFO message (default_password_check) in NCC health check informing you the same, you can change your CVM, Hypervisor and IPMI password using the guides below, you can also use script to change it on all nodes at once. Nutanix portal document  

Hi, A customer moved his Nutanix Cluster (with Hyper-V) from a DC to another, after powering the Nodes up, the IPs of all Hyper-V host and CMs released, I logged it locally to Hyper-V hosts and configure the internal IP (192.168.5.1/28) and the external IP same like before shutting the cluster down. I repeated the previous step with CVMs, I went through cd/etc/sysconfigs/ and edit network-scripts file and added the the external IP in the eth0 and the internal one (192.168.5.2/28) in eth1. Now Hyper-V FC is working fine but cannot start VMs due to the Nutanix cluster issue, whenever I tried to start cluster from any CVM, I get this message “WARNING genesis_utils.py:1211 Failed to reach a node where Genesis is up. Retrying” Is there any way to fix this issue or to repair cluster configuration without disrupting existing data? Thanks in advance

Nutanix AHV is a bare metal Type-1 hypervisor developed by Nutanix. Nutanix AHV can be directly installed on any Nutanix certified OEM hardware server i.e SuperMicro NX, IBM CS , Lenovo HX , HPE ProLiant, Cisco UCS, Dell XC and many more being added along the way.AHV is built upon the CentOS KVM foundation and extends its base functionality to include features like HA and live migration, etc. Full hardware virtualization is used for guest VMs (HVM).In AHV deployments, the Controller VM (CVM) runs as a VM and disks are presented using PCI pass-through.  This allows the full PCI co

In order to check Nutanix AOS, AHV or 3rd Party Hypervisor Compatibility with certified hardware, you can visit the Nutanix portal and select "Compatibility Matrix". Home > Documentation > Compatibility MatrixYou can check compatibility for:Hardware model, for e.g. NX, HPE, Dell, Cisco UCS AOS Version Hypervisor Version (AHV, ESXi, Hyper-V, XEN)You can filter by hardware model, AOS version or Hypervisor Version.Visit Compatibility Matrix (Nutanix portal account required) to check for hardware compatibility with AOS and Hypervisors (AHV / ESXi / Hyper-V / XEN).From the same page, you can also check AHV Guest OS compatibility as well. 

Giving thought to change your replication factor from 2 to 3? What are the impacts and things to consider?   First, let’s take a look at what replication factor is. Redundancy factor is a configurable option that allows a Nutanix cluster to withstand the failure of nodes or drives in different blocks.   By default, Nutanix clusters have redundancy factor 2, which means they can tolerate the failure of a single node or drive.  So RF3 means cluster can tolerate the failure of 2 nodes or drive… Basic Maths isn’t it?   Redundancy factor 3 has the following requireme

Although Prism is user friendly, it will be nice to know some commands that are useful for cluster management.   Cluster status The cluster status or “cs | grep -v UP” command gives the status(up or down ) of all the CVMs and their services. Running this command is helpful when there are alerts in the prism about services being down on certain CVMs.   Metadata ring The command “nodetool -h0 ring” shows if all the CVMs are a part of the metadata ring. Being in a metadata ring is essential for the CVM to be an active part of the cluster and handle its designated responsibilities. It is essential

A traditional Nutanix cluster requires a minimum of three nodes, but Nutanix also offers the option of a two-node cluster for ROBO implementations and other situations that require a lower cost yet high resiliency option. Unlike a one-node cluster (see Single-Node Clusters), a two-node cluster can still provide many of the resiliency features of a three-node cluster. This is possible by adding an external Witness VM in a separate failure domain to the configuration (see Configuring a Witness (two-node cluster)). Nevertheless, there are some restrictions when employing a tw

All, I have a 6 Node 1065 system in 2 blocks.  Recently one of the CVMs (node 2, block A) crashed.  When rebooted it was just going in loops.  When diagnosed it seems the SSD (not the SATADOM) had failed and we replaced it.  When we try to boot the CVM, it still just loops. We were told to boot that node with Phoenix which the cluster provided me for download.  I do that and it doesn’t load Phoenix and gets errors instead.  I’m looking for a suggestion of how to get the node back to 100%.  At this point (and throughout) the ESXi on the SATADOM has booted fine and I guess if I didn’t care about the storage side I could just ignore this but I’d like the system to be fully healthy. Any suggestion about how to get the CVM working again would be appreciated. Thank you Johan

The Prism interface allows the investigation of the disk I/O latency. As a result, following questions are raised. Note: Nutanix recommends that maximum latency readings should not be used as a measure of cluster performance and health. Average latency is a useful measure of cluster performance and health. What should be the average latency on a production cluster? What should be the maximum latency? What point is the latency too high? How to investigate the high latency?

In some cases, you might have to permanently remove a physical node / host from a Nutanix cluster. There are two scenarios in node removal. Permanently Removing an online node Removing an offline / not-responsive node in a 4-node cluster, at least 30% free space must be available to avoid filling any disk beyond 95%. You cannot remove nodes from a 3-node cluster because a minimum of three Zeus nodes are required. Some Points to consider before initiating node removal: Sufficient Disk space available on other nodes in the cluster User Virtual Machine relocation (if required) Any software upgrade should not be running Checklist on verifying cluster health status Data resiliency is “OK” (green) in Prism Ru

Let’s say you have Nutanix cluster with 24 CPU cores and 2 sockets and now you’re confused regarding the terminology.  vCPU and cores per CPU and how to provision CPU to a Virtual Machine confusing you? Let’s break the terminology down in simple terms!In the world of Hardware, we have sockets and cores. In a host, there would be 2 sockets(or CPU) and 12 cores in each socket, resulting in 24 cores.So what is a vCPU?vCPU corresponds to the number of sockets for the VM. Cores per vCPU correspond to cores in a socket, so in conclusion, if you have provisioned your VM with the following configuration:2  vCPU 4 core per vCPUIn this scenario, your VM would have 2 sockets and 8 cores in total.How can I provision my vCPU, is there a guide or documentation regarding it?

Cluster data usage grows and occasionally it grows more rapidly then planned and expected before a new node to be added to handle this growth. Nutanix offers data Compression and Deduplication to hold more data in the container, by reducing the stored size and avoiding duplicate data, respectively. Usually Compression should be used first, as de-duplication is recommended only on some specific scenarios (please, check documentation links provided below).   Compression: ============ You can enable compression on a storage container. Compression can save physical storage space and improve I/O bandwidth and memory usage which may have a positive impact on overall system performance. The following types of compression are available. -  Post-process compression:   Data is compressed after it is written. The delay time between write and compression is configu

Receiving emails about EOL, but no clue what it means? Once a product is EOL (end of life), then there will be no further upgrades/updates released for it and will no longer be supported by Nutanix.   This may include the AOS version, Prism central, Nutanix files or Supported hardware platforms.   To view the EOL information, navigate as follows:-   Login into Nutanix Support Portal. Menu > Documentation. EOL Information

Here is a tip on how to reset the password for Nutanix Prism local user. The guide applies to Nutanix Prism Central as well. There are two ways. 1. Using Prism interface Log in to Prism Element with domain user and  go to User Management Prism user management   From the user's window choos

Hi,I can’t access LCM in my CE cluster. It just says “LCM Framework Update is in progress. Please check back when the update process is completed.” It’s been like this for days. Updating Foundation and NCC worked fine the old way.I can’t see any active tasks in Prism or using ecli task.listAny ideas?

Let’s say that you want to dive deeper into the performance of your AHV cluster to understand if the resource allocation has been done correctly and to check how many CPUs, Cores per CPU and Threads reside on each host. To see the CPU components, SSH to a CVM in your cluster and run ”hostssh lscpu”:   The result above is an output example of one node, for this host there are: Sockets = 2 Cores per socket = 6 (2x6 = 12 in total) Threads per core = 2 (2x12 = 24 in total) CPUs = 24 (threads in total) If you wish to see more information for each of the 24 CPUs on this host you can run "cat /proc/cpuinfo" on a host shell (not through the CVM). To jump from the CVM to it’s host, run “ssh root@192.168.5.1” and run the command

You might have noticed that the versions of AHV hypervisor have names starting from the year, such as 2017 and 2019. For example, AHV-20170830.434 and AHV-20190916.231.  The difference between them is that the versions starting with 2017 are built on CentOS 6 image, while the ones starting with 2019 are based on CentOS 7.    It is very important to note that all the 2019 AHV versions are only compatible with AOS versions 5.16 and newer. It means that the current LTS AOS versions 5.10.x and 5.15.x do not support AHV 2019. The AHV 2019 is currently supported only with STS AOS versions.