Pass the Nutanix Nutanix Certified Professional (NCP) NCP-MCI-6.5 Questions and answers with CertsForce

Active-Active is a bond mode that allows all uplinks in the bond to be used simultaneously for traffic transmission and reception. This bond mode provides load balancing and increased bandwidth for the AHV host and its VMs. Active-Active bond mode uses a hashing algorithm based on source MAC addresses to distribute traffic across different uplinks in the bond. Each individual VM NIC uses only a single bond member interface at a time, but multiple VM NICs are spread across different bond member interfaces. As a result, it is possible for a Nutanix AHV node with two 10 Gb interfaces to use up to 20 Gbps of network throughput, while individual VMs have a maximum throughput of 10 Gbps6.

Therefore, if an administrator needs to optimize for maximum single VM throughput, they should select Active-Active bond mode for their AHV cluster. This bond mode can be configured using Prism Element UI or manage-ovs commands on each AHV host7. No additional configuration is required on the upstream switch side, as long as the switches are interconnected physically or virtually and both uplinks trunk the same VLANs8.

According to the web search results, Distributed Storage Fabric (DSF) is the scale-out storage technology that makes HCI and cloud possible45. DSF pools the storage devices that are directly attached to a cluster of servers and presents them to applications across a variety of storage protocols4. DSF also manages and protects data by a fine-grained, distributed metadata system that ensures uniform distribution of data throughout the cluster to eliminate hot spots and speed up rebuilds

Automated live migration is a feature of Nutanix that allows the cluster to automatically move VMs from one host to another without any downtime, in order to optimize the performance and availability of the cluster. According to the Nutanix documentation1, automated live migration can occur in the following scenarios:

Cluster resource hotspot: When a host or a group of hosts experience high resource utilization, such as CPU, memory, or network, the cluster can automatically migrate some VMs to other hosts with lower utilization, in order to balance the load and avoid performance degradation.

AOS upgrade: When upgrading the Nutanix software (AOS), the cluster can automatically migrate the VMs from the host that is being upgraded to another host in the same availability zone, in order to maintain the VM availability and minimize the impact of the upgrade process.

AHV host maintenance mode: When putting an AHV host into maintenance mode, the cluster can automatically migrate all the VMs from that host to another host in the same availability zone, in order to prepare the host for maintenance operations such as hardware replacement or firmware update.

According to the Nutanix Support & Insights, in a two-node ROBO cluster with a witness VM, if one node goes down, the other node sends a leadership request to the witness VM and goes into single-node mode. The cluster remains available and can tolerate another failure of either the witness VM or the network link.

https://portal.nutanix.com/page/documen ts/details/?targetId=Prism-Central-Guide-Prism-v510:mul-alert-policies-user-defined-configure-pc-c.html

https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2029_AHV:BP-2029_AHV

Administrators can use Acropolis with IPAM to deliver a complete virtualization deployment, including network management, from the unified Prism interface. This capability radically simplifies the traditionally complex network management associated with provisioning VMs and assigning network addresses. To avoid address overlap, be sure to work with your network team to reserve a range of addresses for VMs before enabling the IPAM feature.

The Acropolis master assigns an IP address from the address pool when creating a managed VM NIC; the address releases back to the pool when the VM NIC or VM is deleted.

switch ports are configured with different VLANs could be the cause of this error. If the switch ports are not configured with the same VLANs as the network interfaces on each node, then there could be a mismatch in network connectivity when one interface is disconnected1. This could affect the guest VMs that are using a different VLAN than the hypervisor.

Based on the VM performance metrics shown in the exhibit, the most likely cause of the poor performance in the particular VM is that the host’s CPU is severely overloaded. This is indicated by the high percentage of Hypervisor CPU Ready Time, which is shown as 96% in the CPU ready chart. CPU Ready Time is a metric that shows the amount of time a VM is ready to run but is unable to run because the host CPU resources are not available. In a healthy environment, this value is typically low. A high percentage indicates that the VMs are waiting for available CPU cycles, which means the CPU is not able to schedule the VM effectively, often due to overcommitment or heavy CPU load.

When the CPU ready time is consistently high, it is a clear indicator that the VM is frequently waiting for CPU resources, which can lead to performance issues such as sluggishness or delays in processing. It is not related to the storage subsystem (Oplog fullness or SSD tier size), nor directly to the number of vCPUs assigned to the VM. While adding more vCPUs might seem like a solution, it could actually exacerbate the issue if the host is already CPU constrained.

To resolve this issue, an administrator should consider balancing the load across the hosts more effectively, possibly by using Nutanix's built-in automation and balancing features, or by scaling out the cluster to add more CPU resources. It is also advisable to check for any VMs with unusually high CPU demand and to adjust resource allocation as needed. Nutanix provides extensive documentation and guidelines in their Resource Management Guide to help administrators identify and resolve such performance issues.

Nutanix supports two types of deduplication: post-process and inline. Post-process deduplication runs periodically on a schedule and can be enabled on any cluster. Inline deduplication runs in real time before data is written to disk and can be enabled only on all-flash clusters.

Therefore, by checking the type of storage and the type of deduplication, you can determine if you can enable inline deduplication on a storage container or not.

 Nutanix inline deduplication is a feature that reduces the stored size and avoids duplicate data on a storage container1. It is recommended only on some specific scenarios, such as when using Nutanix Files or virtual desktop infrastructure (VDI) workloads12.