Deployment Success

HPE® ProLiant® Hardware CompatibilityThis document specifies the hardware, software, and firmware that the Nutanix platform requires to run on HPE® ProLiant® servers. Supported Hardware Models Hardware Hardware Supported Models HPE® Gen10 Servers HPE® ProLiant® Servers DL360 Gen10 8SFF DL380 Gen10 12LFF DL380 Gen10 24SFF HPE® Apollo® System Apollo® R2600 XL170r Gen10 24SFF HPE® Gen9 Servers HPE® ProLiant® Servers DL360 Gen9 8SFF DL380 Gen9 8SFF DL380 Gen9 12LFF DL380 Gen9 24SFF  Note: HPE® and HPE® ProLiant® are registered trademarks or trademarks of Hewlett Packard Enterprise Company. All other brand names mentioned herein are for identification purposes only and may be the trademarks of their respective holder(s). HPE® ProLiant® Gen10 Servers Software and Firmware Compatibility for DL3x0 Gen10 HPE® ProLia

Nutanix cluster requires three nodes minimum but Nutanix also offers the option of two-node cluster. By configuring external witness VM in a separate failure domain to the configuration provides  resiliency features of a three-node cluster.Requirements: Controller VM minimum requirements: 6 vCPU and 20 GB memory Replication factor (RF): RF2 spanned over two nodes and RF4 for metadata on SSDs over two nodes. RF4 for metadata helps during a node failure scenario to quickly transition the healthy node to run in single-node mode with the metadata remaining disk fault tolerant. (Metadata in a two-node cluster is typically small, so the storage need for four copies is modest.) Drive failure effects: one node + one SSD failure (on other node) = read-only mode. Guidelines: Two-node clusters are supported only on a select set of hardware models. See KB 5943 for information about supported models. supported model The upgrade process in a two-node cluster may take longer than the usual proc

I could get a ballpark idea when the next LTS be designated. Seems like its been awhile. I would like to get off the STS train.

Below are new knowledge base articles published on the week of February 21-27, 2021.KB 9288 - Alert - A1102 - PhysicalDiskAdd KB 10533 - Alert - A200403 - Non Compliance with Host Affinity policies. KB 10535 - [ Karbon ] Alerts stay in firing state in a Karbon Cluster UI KB 10815 - VMDK disk image uploaded to Prism shows as "Inactive" with no size KB 10819 - [Karbon] Karbon UI not loading after scaleout PC upgrade to pc.2021.1 - "upstream connect error or disconnect/reset before headers. reset reason: connection failure" KB 10830 - vCenter /storage/seat partition becoming full KB 10832 - Nutanix Move | Migration Plans Disappear after Move-3.7.1 Upgrade KB 10840 - LCM: SATA DRIVEs firmware fails with error: 'EnvironmentModule' object has no attribute '__getitem__' KB 10850 - Physically relocating a block within an online clusterNote: You may need to log in to the Support Portal to view some of these articles.

Below are the top knowledge base articles for the month of February 2021.KB 7503 - NX Hardware [Memory] – G6, G7 platforms - DIMM Error handling and replacement policy KB 1540 - What to do when /home partition or /home/nutanix directory on a Controller VM is full KB 4141 - Alert - A1046 - PowerSupplyDown KB 4409 - LCM: (Life Cycle Manager) Troubleshooting Guide KB 4158 - Alert - A1104 - PhysicalDiskBad KB 1113 - HDD/SSD Troubleshooting KB 2090 - AHV host networking KB 4519 - NCC Health Check: check_ntp KB 6945 - How Upgrades Work at Nutanix KB 5582 - NCC Health Check: idf_db_to_db_sync_heartbeat_status_check KB 2473 - NCC Health Check: cvm_memory_usage_check KB 4639 - How to place CVM and host in maintenance mode KB 6153 - NCC Health Check: default_password_check and pc_default_password_check KB 8932 - NCC Health Check: pc_vm_resource_resize_check KB 1863 - NCC Health Check: sufficient_disk_space_check KB 3741 - NGT: Nutanix Guest Tools Troubleshooting Guide KB 4273 - NCC Health Check:

LCM simplifies Nutanix IT infrastructure life cycle operations by consolidating software and firmware component upgrades into a unified control plane. Prerequisites·   It's recommended to have a cluster with at least three nodes to perform a normal rolling hypervisor upgrade.·   The 2-node case isn't well supported and might require extra steps to enable rolling upgrades, like installing and configuring a Witness VM.·   The 1-node cluster upgrade is also supported but requires LCM 2.2.3 or newer. ·       LCM 2.0 is considered old and not recommended for the AHV upgrades, instead one has to use the legacy "Upgrade Software" method in "Settings".·       Starting LCM 2.2.3, AHV upgrade is supported, both single node cluster and regular cluster, but it only support el6 based AHV upgrade.·       Starting LCM 2.3, AHV upgrade is fully supported, single node, multiple nodes cluster, upgrade from el6 based AHV to el7 based AHV, el7 based AHV to el7 based AHV, UEFI el7 based AHV to UEFI el7

The Discoveries menu in Portal is a new feature that allows customers to view critical issues in their environment with a more holistic approach. Using Nutanix Insights, Portal will provide this view based on Field Advisories, constant health checks, end of support equipment, etc.The Discoveries Details View provides the background, analysis, and corrective actions that can be done to remedy these issues. This will also give you the option to create a case based on the specific issue/topic.For more information, take a look at the “Discoveries Menu” in the Support Portal.

If you have cloned multiple VMs from a single VM (master VM), you can enable NGT and mount the NGT installer simultaneously on multiple VMs by using the master VM image.Before you beginEnsure the following before you perform this task: Install NGT on the master VM. Clone the required number of VMs from the master VM. Shut down the cloned VMs. Perform the following procedure to enable NGT and mount the NGT installer simultaneously on multiple VMs by using the master VM image.Note: After you perform the following procedure, you do not need to separately install NGT on the cloned VMs.Procedure For every cloned VM, log on to the Controller VM and run the following command.ncli> ngt mount vm-id=clone_vm_id Replace clone_vm_id with the ID of the cloned VM. To find the ID of the cloned VM, run ncli> vm list name="<clone-vm-name>" command. Note the value of the Id field as clone_vm_id.<ncli> vm list name="<clone-vm-name>"Id                        : 00058a81-64bb-2

The iSCSI Data Services IP address is used to provide iSCSI access to the cluster storage. It is primarily used by Nutanix Volumes, but is also leveraged by other products such as Calm, Leap, Karbon, Objects and Files. This IP address is owned by one CVM of a cluster at a time, with ownership changing among the CVMs as needed to ensure that it is always available. To note, the iSCSI Data Services IP address CVM owner does not necessarily correlate with the CVM that currently maintains Prism service leadership.To find the current CVM acting as the iSCSI Data Services IP address owner, simply obtain the IP address output from all of the CVMs (generally by using the “allssh ifconfig” command) and verify which CVM reports as having this address. To find when a ownership change has occurred, the Stargate service logs from each CVM can be filtered for entries regarding “eth0:2”.You can find more information regarding the iSCSI Data Services IP Address from the Nutanix Volumes Guide along wit

Great pleasure to say Sizer 5.0 is now liveTwo very big thingsCluster settings/cluster policy.  We always allowed you to edit the model list and set thresholds for cpu/ram etc that the cluster must meet.  Lot more now.  Mihn cpu speed.  Required networking.  Also added policy.  So you can state I want production, test/dev, or mission critical policy.  This gives you more rigor in the sizing as enforces best practicesMultiple recommendations  Sizer by default gives you the lowest cost solution.  That is there but now core optimized and storage optimized too.  So solution with more cores or more storage that fits in cost range you state.  Good to have multiple options

I know that this question has been asked in this forum a few years back but I wanted to see if the answer changed since the newer releases of AOS.  In my case, I’m running AOS version 5.15.4 LTS and found that our 7-node cluster was configured for RF3 - although most of our containers are RF2 (the exceptions being the “NutanixManagementShare: and “SelfServiceContainer” containers).Since most of our containers are only RF2 I’m not too concerned about extra overhead but was curious if AOS now supports the switchback from RF3 on the cluster. 

From the AHV Best Practices document,  live migration network is in host management network(br0).In the network segment enviroment, backplane is isolated in another network which maybe has high bandwidth, does the live migration has any change under this condition? or Live Migration network can do some setting like ESXi vmotion network?

Hi. I have a question while using Xi Frame.If I want to use the List active session and stop  session functions among the Xi Frame functions, what privileges should the administrator at least be given to use them??For detailed functions, please check the red underlined area in the attached photo. 

Hello,I'm trying to setup four nodes on Lenovo HX3321 with vm foundation, but the vm foundation is not start.We have  verify the address vm foundation is correctvm foundation and IPMI same network can you help !!thanks. 

Hi all,How many blocks can be added in one rack? I mean min and max numbers.Thanks in advance.

Hi Nutanix Community, We often wonder what is the real storage capacity available on a Nutanix cluster. We have a three node cluster, in RF2. In Prism Element main page, under "Storage Summary", I see : 20.87TiB free (logical) of 22.37 TiB https:// Data Resiliency is OK. (green) Which one of the following statements is correct ? I can fill my storage up to 22.37 TiB without losing the data resiliency (=I can lose a node without losing data). I can fill my storage only up to 66% of 22.37Tib (= 14.76Tib) without losing the data resiliency Thank you 🙂

I have a cluster of 6 nodes including 3 nodes 1065-G5 and 3 other nodes 1065-G6 which run a hyper-v.I wanted to update from Aos 5.10.5 to 5.17.1 through LCM but I am having issues with the processors.I therefore want to proceed node by node in maintenace mode.Can you give me the procedure for updating the aos by proceeding by this method?

after  change IPMI i found warning IPMI not match I see the reference https://portal.nutanix.com/page/documents/details?targetId=Hardware-Admin-Ref-AOS-v5_17:ipc-ipmi-ip-addr-change-t.html how to step genesis restartI must stop cluster before ?i can run command genesis restart when cluster start ? Thank for support 

Below are new knowledge base articles published on the week of February 14-20, 2021.KB 9314 - Nutanix-Auth-FAQ KB 9866 - NCC Health Check: ergon_checks KB 10310 - Alert A801101 - L2StretchDeletionFailure KB 10574 - Pre-Upgrade check: test_vmd_node_esxi_upgrade_versions_compatible KB 10657 - Discrepancy between Memory Capacity on Prism and Hyper-V KB 10720 - Modify snapshot expiration date and time for Xi Leap snapshots KB 10758 - PDF Report generation fails on Prism Central after upgrading to pc.2021.1 KB 10762 - Prism Central reports showing "No Data" when multiple filtering rules are applied to filter specific entities KB 10765 - AHV upgrades from 20170830.x to 20190916.x and 20201105.x on Dell clusters fail with "Failed to run 'yum remove -y DellPTAgent dcism': 1" error message. KB 10776 - NGT installation fails on Linux VM with Permission denied error KB 10787 - LCM pre-check failing with Failed while performing pre_actions err: Unable to boot cvm [xx.xx.xx.xx] into ivu. KB 10789 -

Hi,My company is going through a major organization change, and we will be driving a lot of VM automation through Ansible.  Since all of us know that the Powershell support is woefully lacking in AHV, I would like to try to get more automation plugged in through Ansible.  Is there an example playbook out there for upgrading/installing NGT for both Windows and Linux?I know that updating NGT via Prism Central works pretty well for Windows, but once again, it fails miserably for Linux (at least OUL).  I would like to do it in an automated fashion, however, instead of 60 checkboxes at a time.  I need a feature that I can upgrade hundreds of VM’s at once and schedule it.Any assistance would be appreciated!

The shutdown token is used by a Nutanix cluster to prevent more than one entity from being down or offline during the occasion of software upgrades or other cluster maintenance. The CVM that is holding the token is the only entity allowed to be down or offline. Sometimes, for various reasons, a CVM can remain holding the token even after an upgrade or maintenance has been successfully completed. This usually does not cause any issues, however, until another upgrade or maintenance is invoked on the cluster sometime in the future. Upgrades or other maintenance pre-checks will search for any unrevoked tokens and, if existing, not proceed until that token has been properly revoked. Before manually revoking the token, it is good practice to verify that there are indeed no outstanding or ongoing upgrades or maintenance activities currently occurring with the cluster. Once confirmed, manual token revocation is often accomplished by a simple restart of the Genesis service on the CVM currently

Please advise me is it support Server 2019 Hyper V on Nutanix? I unable to Find the article on Nutanix Portal with server 2019? I am planing to migrate from Server 2012 hyper v failover cluster to 2019 Server Hyper V failover Cluster? Which AOS Version is support Server 2019?

We’ve migrated a handful of test VMs from our vSphere legacy architecture to Nutanix (also running ESXi)  Both on ESXi 6.5 and latest Prism/software builds, etc.  When using Nutanix Move to do the migration, we’ve noticed that the migrated VM is taking on GMT for its time when the VM boots up.  We are in Michigan so the VM is five hours ahead, but the local windows timezone Eastern. After logging in and/or rebooting, the time typically syncs up fine.  However, this proved to be a major problem when we moved a domain controller and it caused time to be off everywhere.   ncc health_checks network_checks check_ntp all comes back fine and our time sources are defined properly both in Nutanix as well as NTP oin the ESXi host.  What are we missing or is this a bug?

Windows 10 VM stuck at boot and giving black screen. Tried reboot but no luck.

Hello All, I have created this great powershell script that makes VM’s in AHV. It has been a journey let me tell you, but I made it through. The one thing I would like to add to this is creating a vm with UEFI boot option. I know this needs to be done at creation and I can create it in the acli with the following: acli vm.create UEFIVM2 uefi_boot=true However; is there a way to do this with powershell? I will look at finding a way to wrap the ssh command above but it sure would be nice if it was just a parameter on the                         new-ntnxvirtualmachine cmdletIs there a way I can create the vm with UEFI with powershell? Thanks,Scott