Get guidance, share wins, and ensure smooth Nutanix deployments.
Recently active
The business is growing, and this means more users, more virtual desktops, and you’re likely going to need more RAM. You could add a node or two, but what if rack space isn’t readily available? The existing nodes may still have room to grow. How do we add memory to nodes in a Nutanix cluster? The process for upgrading memory is covered in this KB: HW: Upgrading Physical Memory You should understand the restrictions and have a plan before purchasing DIMMs. If you need to review supported memory configurations, such as what DIMM capacities are supported and which slots to fill, check the NX Series Hardware Administration Guide for details. There are restrictions on mixing memory in the same node. You can’t just add any DIMM that fits into an existing node, but if each node has some slots available there are options to move forward. You could purchase new DIMMs to populate one node and complete this replacement first, and then use the removed DIMMs to add memory capacity to other nodes i
Hi Does anyone know how to use this Powershell cmdlet properly mount-ntnxguesttoll -vmid 54312c2a-2b7e-4dbe-b7ac-0fa58b575ad2 nor mount-ntnxguesttool -vmid 00054abc-11c2-77b7-2a9b-246e963f27a8::54312c2a-2b7e-4dbe-b7ac-0fa58b575ad2 work Trying to pipe to the mount-ntnxguesttool doesn’t help either. Help!!! Christopher
hello, I would like to know if, in addition to our AHV hypervisor on the NUTANIX, if it is possible to add the ORACLE hypervisor
I just migrated a VM with Windows 2008 R2 from ESXi 6.0 to AHV but I got blue screen when I turned it on in nutanix cluster. I used move version 3.4.1 somebody knows what happened.
Hi,I had a problem with the NTP server configured on the Nutanix cluster, unintentionally changed the date to 09012020 instead of 01092020, the point is that after solving that problem, now the cluster reports to me Critical alerts dated September 1, 2020. The date of the NTP is already corrected, but Web Console shows some critical alerts, but those alerts are not shown with ncli, but are shown with Alert tool. I have try to aknowledge and resolved them, but they are NOT eliminated from alert_list.Does anyone know what I can do so that the web console no longer shows them?
Let's say that you want to upgrade your physical memory on one of the nodes. On Nutanix Hardware, we allow users to add DIMMs on the empty slots without losing the support contract. When adding a DIMM, there are multiple things that you should take into consideration depending on your Nutanix Block Model, for example: Number of slots on each node Which DIMMs are supported, which manufacturer? The supported DIMM speed Are there any restrictions? To check the specification of your system, check out this page, choose the model type and the platform (NX-xxxx-Gx). you will be redirected to your model’s page. Good to know: The memory performance is most efficient with a configuration where every memory channel contains the same number of DIMMs. Nutanix supports other configurations, but be aware that these configurations result in lower performance. On G4 and G5 models, each node must contain only DIMMs of the same type and capacity. (Adding higher-speed DIMMs is supported, but the DIM
Hi All, I am pulling some data with the API. For example https://MYIP:9440/PrismGateway/services/rest/v2.0/hosts Results with , among other metrics, the following. Where can I find an explanation of each metric? "stats": { "hypervisor_avg_io_latency_usecs": "0", "num_read_iops": "319", "hypervisor_write_io_bandwidth_kBps": "0", "timespan_usecs": "20000000", "controller_num_read_iops": "696", "read_io_ppm": "641128", "controller_num_iops": "1588", "total_read_io_time_usecs": "-1", "controller_total_read_io_time_usecs": "196391465", "hypervisor_num_io": "0", "controller_total_transformed_usage_bytes": "-1", "hypervisor_cpu_usage_ppm": "60000", "controller_num_write_io": "17846", "avg_read_io_latency_usecs": "-1", "content_cache_logical_ssd_
Hi, I am dealing with an EOL cluster (3060). I am facing recently a case where the prism element does list a vm which does not exist on the AHV. It is a fake vm. There is no active support to ask them. Any help?
Q. Why does the home share have an icon to it as if it was a link and not a directory? The top-level directories act as a reparse point—essentially a shortcut. Consequently, administrators must create directories at the root of the share for optimal load balancing. Because it appears as a shortcut, we don’t allow user files in the root level of the share; we recommend setting permissions at the share or export root before deploying user folders. This step allows newly created top-level directories to inherit permissions, so you don’t have to adjust them after the fact using the Nutanix Files Microsoft Management Console (MMC) plug-in. Q. Why is it necessary to empty directory prior to deleting the home share? Distributed share directories with NFSv4 introduce some unique behaviors. To balance performance across FSVMs, each top-level directory you create becomes an automatically generated export. Nutanix Files mounts the export on demand when the directory is accessed. Since these a
If you are completing a security audit or setting up a firewall, you probably need details about the ports used by your Nutanix cluster. Thankfully, we have a reference provided which explains the ports needed by various services on an AOS cluster. You can find out about ports used by different AOS services in the KB article Port numbers used for inter CVM communication . The Security Guide found in our software documentation library is the best reference for firewall rules, which are detailed in this section. The Security Guide details which ports should be open and to what URL(s) specifically for Remote Support (reverse SSH tunnel), Pulse, Alerts (call-home for automatic case creation), SMTP sending, Data Replication to remote clusters, 1-click upgrades, and LCM.
I am reimaging my lab cluster after we had some serious problems with a conversion to AHV and rollback to ESXi. 2 of my 3 nodes reimaged fine, once I put a /firstboot directory in to the existing ESXi hosts. My 3rd node is losing track of where the firstboot directory would be. From the foundation log: 20200221 11:40:17 ERROR Command 'scp -i ~/.ssh/id_rsa /tmp/tmp.gkI7z6j7XG/nutanix_provision_network_utils-1.0-py2.7.egg root@192.168.5.1:./vmfs/volumes/4d501d79-cff63899-7951-75210fae7516/Nutanix ./vmfs/volumes/5e4c3359-4b398980-cc34-ac1f6bb9dd8a/Nutanix/firstboot/nutanix_provision_network_utils-1.0-py2.7.egg' returned error code 127 stdout: stderr: FIPS mode initialized bash: line 1: ./vmfs/volumes/5e4c3359-4b398980-cc34-ac1f6bb9dd8a/Nutanix/firstboot/nutanix_provision_network_utils-1.0-py2.7.egg: No such file or directory 20200221 11:40:17 ERROR Failed while copying file /tmp/tmp.gkI7z6j7XG/nutanix_provision_network_utils-1.0-py2.7.egg to host with error Command 'scp -i ~/.ssh/id_r
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 vendor documentation for compatibility. The matrix is presenting the fields in a cascading style, to show a clear components dependencies. Also in the compatibility matrix, you can see the Nutanix Ready Solution where we show the
It happens to the best of us. We are human beings and we make mistakes. Sometimes it means that we forget or lose root passwords to one or more of our AHV hosts. There are two ways out of that situation. Log into the AHV host from CVM using the host's local IP address. Make sure that you are logging into the CVM of the problematic host. Change root password. Re-image the AHV host. AHV Administration Guide: Changing the Acropolis Host Password KB-7068 AHV | Root account password reset Additional reading: .NEXT Modifying passwords in Nutanix Environment Nutanix Security Guide v5.16
The Nutanix Support portal includes a compatibility matrix available from the Compatibility Matrix link. You can filter and display compatibility by Nutanix NX model, AOS release, hypervisor, and feature (platform/cluster intermixing). Nutanix recommends that you consult the matrix before installing or upgrading software on your cluster. Do you want to know if you can mix different types of CPUs, memory, disks or hypervisors in your Nutanix environment? Start with this documents that provide the answers you might be looking for, like: Hardware Restrictions: mixing different Nutanix CPU families Storage restrictions: Mixing all-SSD and hybrid SSD/HDD Mixing NVMe and SSD/HDD Encryption restrictions DIMM restrictions: Mixing DIMM Types Mixing different DIMM Capacity Mixing different DIMM Manufactures Mixing different DIMM speed Hypervisor restrictions You can get all the answers in this document : Product Mixing Restrictions In case you need memory specific repla
Nutanix is continuously developing and improving it's features with new releases of different components, how could you know if the current software of component A is compatible with software B? For example if you are interested in upgrading your Prism Central or the Nutanix Files, there would be a specific set of Prism Central and Nutanix Files versions that can be installed with a limit of an older version depending on your AOS version. This goes both ways, if you are interested in upgrading your Operating System (AOS), you need to check your current Prism Central and Nutanix Files to understand which AOS version you can use on your current cluster's versions. We have a public page for our customers that can do the checks for you, on our Software Product Interoperability page you choose your software and the target software type, you choose your current version and the compatible version will be presented in green. The information there is dynamic and it could change with every relea
Most of us are aware of what maintenance mode is. But how is its execution different in ESXi and AHV in Nutanix? Well… it’s just a small tweak! While trying to put ESXi host in maintenance mode, it will get stuck as the CVM, which cannot be migrated off to other hosts, needs to be powered off and then the action will be completed. In the case of AHV, this need not be done, once you provide the instruction to put the host in maintenance mode, the user VMs will be migrated to other hosts and the host will enter maintenance mode, irrespective of the CVM being powered off. In short, “The CVM need not be powered off to put AHV host in maintenance mode, which is the case with ESXi” Have any questions? Leave them below and let’s start a discussion! Check out the community post https://next.nutanix.com/how-it-works-22/cluster-maintenance-or-relocation-33391 for more on cluster maintenance or relocation.
Whenever we hear the word cluster, the picture that comes in our mind is multiple nodes. So doesn’t a single or two-node cluster sound weird? But, it’s possible! Well… In a traditional Nutanix cluster at least 3 nodes are expected to form a cluster. There is an option however to form a single-node or a two-nodes cluster for ROBO (Remote Office/Branch Office) implementations or as a backup site. Confused or have questions regarding the implementation or requirements/dependencies? Check out Guide for single-node and two-node clusters for any clarifications. To know more on single-node clusters: Data Protection and Recovery with Prism Element: Single-Node Replication Target Clusters Prism Web Console Guide: Single-Node Clusters For more information on two-nodes cluster: Prism Web Console Guide v5.16: Two-Node Clusters
There are instances where it is necessary to reseat a node for troubleshooting purposes. So what exactly is node reseat? Node reseat is a process in which we stop all the services in the node, put the CVM and Hypervisor in maintenance mode and then physically detach the node from the block and re-seat it. A node re-seat is sometimes required in troubleshooting related to the power supply as during re-seat of the node the voltage drops to zero. So do we have a step by step guide explaining the process of the reseat of a node with video tutorials on how to physically remove a node? Of course, we do Go through the knowledge base article to understand the process of node reseat. KB-3182 Reseating a Node in a Cluster Need some guidance or still confused? Drop a comment and let us start a discussion.
Below are new knowledge base articles published on the week of February 16-22, 2020. KB 8880 - Understanding 3rd Party Backup Integration KB 8996 - Self Service Restore Failing for Microsoft Storage Spaces Disk Note: You may need to log in to the Support Portal to view some of these articles.
Your CVMs can upload log bundles directly to Nutanix for an open case, and this can speed case resolution especially if the alternative is the two-step process of pulling multiple GiB over WiFi to download and THEN upload. With common security restrictions around FTP or SFTP leaving the datacenter this may require explicit firewall rules. The logbay command to collect and upload logs looks like this: logbay collect --dst=sftp://nutanix -c <case_number> That destination “nutanix” isn’t helping us with that firewall rule, so where is the upload going? The software is really just automating the old manual methods described in this KB: Uploading Files for Nutanix Support Using FTP, SFTP or the Customer Portal. Referencing that article, we can see the DNS name for FTP uploads is ftp.nutanix.com . The IP address varies by region and might change, so I’d suggest using the URL. To allow log upload, you’ll need to allow port 22 for SFTP. You could also allow port 21 for FTP, but if it nee
Your hardware lease period is expired, and you have tried to destroy the cluster to clear the data off the cluster, but the cluster was not destroyed completely? Successful cluster destroy requires to have a clean environment. Clean out cluster config and cluster data. This operation will completely erase all data and all metadata, and each node will no longer belong to a cluster. There are some situations where cluster destroy does not succeed, especially if cluster destroy is executed while one of the nodes is down. In that case please follow this document KB 3436 [Forcibly Destroying the Cluster Using the .node_unconfigure File] which can help you further to clear the data from the cluster.
Let’s say that a VM migration is required for data protection or as part of a disaster recovery, what is the scenarios and the recommended practice? Check out our documentation about data protection and disaster recovery we wrote this guide for IT administrators and architects who want more information about the data protection and disaster recovery features built into the Nutanix Enterprise Cloud. The data protection subject is huge and has a lot of branches, let’s focus on a small component which is migrating the VMs from one location to another. The migration could be done between Nutanix hosts, Nutanix Clusters or migration from non-Nutanix Storage to a Nutanix Storage. The simplest scenario is migrating the VMs from one host to another in the same cluster, the VMs will migrate automatically after placing the host into maintenance mode by the recommended practice of the host’s hypervisor, the only CVM that would stay on that host is the Controller VM (CVM) which is responsible for
Let's say you have modified the license assignments, removed a node from the cluster and you got an alert in Prism stating that there is no current license for the cluster. You can reclaim and optionally re-apply licenses for nodes in your clusters. This procedure describes how to reclaim licenses where the cluster is not configured with Portal Connection or the cluster is not connected to the internet (also known as dark-site clusters). After you remove a node, you can also move the node to another cluster. More info. You must un-license your cluster when you plan to destroy a cluster. More info Return licenses to your inventory when you remove one or more nodes from a cluster. You can reclaim licenses for nodes in your clusters in cases where you want to make modifications or downgrade licenses. More info You do not need to reclaim Starter licenses for Nutanix NX Series platforms. These licenses are automatically applied whenever you create a cluster. For more information about rec
Customers can observe cluster issues when they use more than 90 percent of the total available storage on the cluster. For node resiliency and redundancy, the disk usage must be below the Max Usable value. One of the most common alerts is Cluster can not tolerate # node failure(s). This alert is fired by the NCC health check "sufficient_disk_space_check" that checks if there is sufficient storage space on the cluster to provide node resiliency. See more details on (KB 1863) Share your comments in this forum!
Besides the fact that LTS is Long Term Release and STS is Short Term Release, Is there any reason that STS shouldn't be used for production purposes over LTS ?I want to switch to 5.9 for the ESXi 6.7 compatibility.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.