Get guidance, share wins, and ensure smooth Nutanix deployments.
Recently active
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?
I am interested on visualizing east west traffic as well as egress within my NTX environment. With Open vSwitch it seems to be supported through the default vTap interface on the bridges created on my interfaces. My question is, has anyone successfully set up a Nutanix vTap interface to capture packet flow on an external appliance and are there any negative side effects of such a design (overhead, congestion, latency… etc)? I do have an upstream appliance that can handle the analysis similar to Gigamon, CloudLens and ExtraHop. https://docs.openvswitch.org/en/latest/topics/tracing/
LCM - Inventory - Perform Inventory operation encountered the following error The Foundation version is up to date.The LCM version is up to date.Only other clusters operate normally.
Hi All,I have a HP GL380p G8 and I have 1x30GB SSD 1 x 400GB SSD 2 x 600 SASWhen i start the install it asks for the location to install the hypervisor, CVM and what are data disks. Can I use the 30GB SSD for the hypervisor and the CVM. This will leave the 400GB SSD for performance tier and the 2 x 600GB for normal tier.
I recently used LCM to update the firmware on my 9 node cluster. One of the hosts did not come back up. I was able to get it to reboot back into the host OS, but it had no network connectivity. The interfaces were up, IP address assigned, just no traffic passing through the bridge. After fighting with it for some time, I decided to eject the node from the cluster and just re-foundation a new one. I initiated the removal process, but the node status remains in MARKED_FOR_REMOVAL_BUT_NOT_DETACHABLE:nutanix@NTNX-<REDACTED>-A-CVM:10.1.153.30:~$ ncli host ls id=21 Id : 0005adca-5f30-1bf1-0000-000000008d15::21 Uuid : 705089f7-2435-4a35-83fe-603470bd36d6 Name : 10.1.153.15 IPMI Address : 10.1.151.249 Controller VM Address : 10.1.153.34 Controller VM NAT Address : Controller VM NAT PORT : Hypervisor Address : 10.1.153.15 Host Status : MARKED_FOR_REMOVAL_BUT
Hi Team,I am planing to deploy Nutanix 3 node with Hyper V. so i want to know that intial deploymentcan I use LACP on Switch Side.please guide me LACP configuration for Nutanix side?Environment:Network : IPMI Hyperviser Management Subnet - 10 G Port 1 and 2 -LACP Guest VM Subnet - 10 G Port 3 and 4 -LACP Guest VM Second Subnet - 1 G Port 1 and 2 Two 10 G Switch Two 1 G Switch
We have created a new vlan for windows 10 VM and I wanted to update existing network to new network. I was not able edit the existing network and choose the new one, it is grayed out. Do I need to delete and re-add new nic and choose the new network? For ESXi, you simply browse the network and select the one you want and save it.
Below are new knowledge base articles published on the week of February 28-March 6, 2021.KB 10526 - Alert - A200401 - VM forcibly powered off KB 10856 - Cluster Maintenance Utility version via cli KB 10861 - Acropolis crashing with "KeyError: u'off'" error after upgrade to 5.19.x KB 10863 - Non-admin AD users cannot Clone a VM when added to a Custom RBAC role on PC KB 10878 - VMSA-2021-0002 / ESXi OpenSLP / Disable CIM Server KB 10882 - [Nutanix Move] 1-click-upgrade from 3.7.1 to 3.7.2 may fail when we have migration plans which were created in Move version less than 3.7.0Note: You may need to log in to the Support Portal to view some of these articles.
The flash mode for VM allows to set the storage tier preference to SSD for a virtual machine or a volume group. Without flash mode, data for a mission critical application such as a relational database can run out of the room in the SSD tier because other workloads running on the same cluster. When this happens, the database could potentially migrate to the HDD tier. For extreme latency sensitive workloads, this migration to the HDD tier could negatively affect the read and write performance. By default, you can use up to 25% of the cluster-wide SSD tier as flash mode space for VMs or VGs. If the data size for flash mode enabled VMs or VGs exceeds 25% of the SSD capacity, the system may down migrate the data. Before down migration, the flash mode feature tries to preserve the excess data on the SSD tier for some reasonable amount of time so that you can take corrective actions on the cluster and bring it back to stable. To reduce flash mode usage, we can disable the flash m
Hi Buddies!I would like to know if this possible to add GPUs card on a NX-8155-G6 hardware. I know that this model doesn’t came with GPU installed, but, is it possible to add it?
In the default AHV network schema, ther’s a connection between the AHV management and the virbr0. Can you explain me the purpose of that connection and the IP adresses used ?
As the Nutanix Life Cycle Management (LCM) platform evolves, more firmware entities are added to the module. The latest addition are the NICs associated with Nutanix hardware.Starting in LCM 2.3.4, firmware updates for Mellanox and SuperMicro NICs on AHV and ESXi are supported. Currently, Hyper-V platforms and Intel/Silicom NIC cards are not supported.For more information about this feature and software requirements, take a look at KB 10073 found on the Support Portal.
I upgrade AOS 5.15.4 and i have AHV older version I need Upgrade AHV after by LCM I Click LCM and loading… long time and show massage server error i have question ? LCM Need access internet ?
Hi,I would like to configure anti-afinity on on the VMs. I checked this only able to configure thru command. To configure the rules, does the VMs need to be powered down?
As Nutanix is constantly striving to be an API driven company and exposing more of its core functionality via API’s as well as improving integration with tools such as Ansible and Terraform, we hope you have been making the most of it. For example, did you know how to check the status of NGT and the NGT communication link using API’s? It is easily obtainable using the v3 REST API exposed from your Prism Central. Issue a GET request to https://<PC_IP_address>:9440/api/nutanix/v3/vms/<vm_uuid> Filter through the response to find a block similar to this. "guest_tools": { "nutanix_guest_tools": { "available_version": "1.90.1", "ngt_state": "INSTALLED", "iso_mount_state": "MOUNTED", "state": "ENABLED", "version": "1.1.2", "enabled_capability_list": [ "VSS_SNAPSHOT" ], "guest_os_version": "windows:64:WindowsServer2008R2Enterprise", "is_reachable": false } }
Hello, I am trying to collect some VM performance data from Prism element. I have noticed that some stats do not keep history for more than 5 minutes. Example: controller_io_bandwidth_kBps vs. controller_read/write_io_bandwidth_kBps GET 'https://{IP}:9440/PrismGateway/services/rest/v1/vms/{vmid}/stats/?metrics=controller_io_bandwidth_kBps&startTimeInUsecs=1589462400000000&intervalInSecs=300' "statsSpecificResponses": [ { "successful": true, "message": null, "startTimeInUsecs": 1589462400000000, "intervalInSecs": 300, "metric": "controller_io_bandwidth_kBps", "values": [ 8106, 5500, 8404, 5618, 12793 ] } ] } GET 'https://{IP}:9440/PrismGateway/services/rest/v1/vms/{vmid}/stats/?metrics=controller_read_io_bandwidth_kBps&startTimeInUsecs=1589462400000000&intervalInSecs=300' { "statsSpecificResponses": [ { "successful": true, "message": null, "startTimeIn
If the clusters are related with prism central (so I should use v3), Can i use v2 to actions like: manage NIC, Attach/Detach Disks, manage snapshots from API v2?Is recovery plans is the same as snapshots here? I want to create jobs for automatic snapshots, but I do not see thios possibility in v2I am using the same account for api v2 and v3 actions, in production environment with my own IP, it will be the same host? It is specified in API Documentation, but I want to be sure if the host for both will be the same - eg. nutanixtest.com/v2… and nutanixtest.com/v3…Thanks!
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
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.