Nutanix NCP-MCI-6.5 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) v6.5 exam Exam Practice Test

https://hyperhci.com/2019/07/22/nutanix-lcm-upgrade-process-failed-trouble-shooting/

According to section 5 of the exam blueprint guide1, one of the topics covered is live migration. Live migration is the process of moving a running VM from one host to another without any downtime or interruption of service. To perform live migration, there are some prerequisites that must be met, such as:

• All AHV hosts have IP addresses in the same subnet
• All VMs are configured for the same VLAN
• The source and destination hosts have enough resources to accommodate the VM
• The VM does not have any PCI devices attached

According to the web search results, one of the best practices for Nutanix AHV networking is to create a second bridge on each host and assign the 1GbE interfaces to it3. This way, the customer can use both 10GbE and 1GbE interfaces for VM traffic, and also benefit from network isolation and redundancy. 

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth3. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the “manage_ovs show_uplinks” command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.

CloudInit is a package that contains utilities for early initialization of cloud instances. It allows you to customize virtual machines provided by a cloud vendor by modifying the generic OS configuration on boot. You can use CloudInit to set the OS hostname, add custom users, add keys, run custom scripts, and more2. CloudInit is supported by most major Linux and FreeBSD operating systems and works across different cloud platforms3. Sysprep is a tool for Windows operating systems that prepares an installation for cloning, auditing, and customer delivery4.

References: 1: Replacing Nodes in Nutanix Cluster - Nutanix Support & Insights 2: Customize a Linux VM with cloud-init in Azure - Azure Virtual Machines 3: Cloud-Init - The standard for customising cloud instances 4: Sysprep (Generalize) a Windows installation

According to the Nutanix Support & Insights web search result1, erasure coding is a data savings technique that utilizes stripes and parity calculation in a Nutanix cluster. Erasure coding increases the usable capacity on a cluster by reducing the replication factor of data blocks. Instead of replicating data, erasure coding uses parity information to rebuild data in the event of a disk or node failure. Erasure coding can save up to 50% of storage space compared to replication factor 2, and up to 75% compared to replication factor 32.

According to the Nutanix Support & Insights web search result3, shadow clones are vDisk copies that are created by the cluster when a vDisk is read by multiple VMs. Shadow clones are immutable copies of a vDisk that are stored in different nodes in the cluster, and are used to improve read performance and reduce network traffic. Shadow clones are automatically created and deleted by the cluster, based on the demand and availability of resources.

According to section 4 of the exam blueprint guide1, one of the topics covered is AHV networking components and configuration settings. One of these components is Open vSwitch (OVS), which is a software switch that provides network connectivity between VMs and physical networks. OVS has two types of ports:

• Uplink ports: These are physical ports that connect to external networks or switches.
• Internal ports: These are virtual ports that connect to VMs or other internal networks.

To view the uplink state of all AHV nodes in the cluster, an administrator can use the manage_ovs command with the show_uplinks option. This command displays information such as port name, link state, speed, duplex mode, MTU size, bond mode, and bond status. However, this command only works on a single node. To run the command on all nodes in the cluster, an administrator can use the allssh command, which executes a command on all CVMs in parallel. Therefore, the correct command is:

allssh manage_ovs show_uplinks

According to the Nutanix Support & Insights, IPAM enables AHV to assign IP addresses automatically to VMs using DHCP. You can configure each virtual network and associated VLAN with a specific IP subnet, associated domain settings, and group of IP address pools available for assignment.

A constrained VM is one that does not have enough resources for the demand and can lead to performance bottlenecks. A VM is considered constrained when it exhibits one or more of the following baseline values, based on the past 21 days: CPU usage > 90% (moderate), 95% (severe) CPU ready time > 5%, 10% Memory usage > 90%, 95% Memory swap rate > 0 Kbps1. To provide adequate host resources, resize (increase) the constrained VMs1.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2023_3:mul-cluster-storage-policy-pc-c.html

A GPU (graphics processing unit) is a specialized hardware device that can accelerate graphics rendering and computation for applications that use APIs such as DirectX, OpenGL, CUDA, and OpenCL. A GPU can also offload the CPU from encoding and decoding tasks for remote display protocols such as Frame Remote Desktop Protocol (FRP). A VM can use a GPU either by directly accessing a physical GPU (pGPU) on the host or by using a virtual GPU (vGPU) that shares a pGPU with other VMs. A user running a computer aided design (CAD) application may benefit from using a GPU or a vGPU to improve the performance and responsiveness of the application, especially when moving windows or rendering images. However, if the GPU or vGPU is not properly configured or provisioned, the user may experience slow response time within the VM. Therefore, to diagnose the problem, the administrator should monitor the GPU Usage metric for the VM. The GPU Usage metric shows the percentage of GPU resources that are consumed by the VM over time3. The administrator can use Prism Central to view the GPU Usage metric for each VM in a chart or a widget4. The administrator can also use Prism Central to view other metrics related to GPU performance, such as GPU Memory Usage, GPU Encoder Usage, and GPU Decoder Usage3. By analyzing these metrics, the administrator can determine if the VM is using the GPU efficiently and optimally, or if it needs more or less GPU resources.

Nutanix leverages a method for determining the bands called ‘Generalized Extreme Studentized Deviate Test’. A simple way to think about this is similar to a confidence interval where the values are between the lower and upper limits established by the algorithm.

Another web source3 shows an example of how anomaly detection works in Nutanix Prism Central. In the video, you can see that when the observed value of a metric deviates significantly from the predicted value based on historical data, an anomaly event is triggered and displayed on a chart.

Therefore, by comparing the observed values with the predicted values based on historical data, Nutanix anomaly detection can identify abnormal behavior and alert you accordingly.

Curator is the process that runs on every node in a Nutanix cluster and is responsible for data management tasks such as deduplication, compression, erasure coding, and replication factor compliance. Curator also handles disk failure recovery by scanning Cassandra to find all data previously hosted on the failed disk, and all disks in that node. Curator then rebuilds the data on other nodes in the cluster using the distributed storage fabric1.

Data locality is the capability of storing VM data on the node where the VM is running and ensuring that the read I/O does not have to traverse the network. Data locality is a unique feature of Nutanix that provides high performance and low latency for VMs by minimizing network traffic and crosstalk. Data locality works by writing one copy of the data local to the VM and the other copy (or copies) on other nodes. When a VM migrates to another node, Nutanix also moves its data to the new node and serves all I/O requests locally. Data locality also adapts to changing workloads and access patterns by dynamically moving data to where it is needed most1.

According to the web search results, two steps that should be taken to prepare for relocating an AHV cluster to a new datacenter during a maintenance window are:

• Shut down all user VMs in the cluster: This step is necessary to ensure that there is no data loss or corruption during the relocation process. The user VMs can be shut down either individually or in bulk by using the Prism Element web console or the acli command-line interface1.
• Stop all Nutanix Files clusters: If the AHV cluster hosts any Nutanix Files clusters, they should be stopped before relocating the cluster. Nutanix Files clusters are composed of one or more virtual machines that provide file services to clients. Stopping a Nutanix Files cluster will stop all the file server VMs and release the resources they consume2. The Nutanix Files clusters can be stopped by using the Prism Element web console or the ncli command-line interface3.

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

Explanation/Reference:

The issue described pertains to the inability to ping the IPMI IPs after moving the IPMI network links to the actual switches with specific VLAN configurations. The two changes that the administrator needs to make are:

A. SSH to AHV and set the VLAN ID using IPMI Tool: Since all VLANs are tagged in the new network configuration, the IPMI network interface needs to be aware of the VLAN it’s supposed to communicate on. This can be achieved by setting the VLAN ID using the IPMI Tool on the AHV.

C. SSH to AHV and change the IP address using IPMI tool: If the IPMI IP addresses were initially set in a different subnet that is not routable in the new network configuration, the administrator would need to change the IPMI IP addresses to match the new network configuration. This can be done by SSHing to the AHV and using the IPMI Tool to change the IP address.

The correct answer is C. Network latency.

The diagram shows a solution that uses synchronous replication between two remote protection domains, cluster site A and cluster site B. Synchronous replication is a feature that allows near-zero RPO (recovery point objective) by replicating data to the remote site before acknowledging writes to the local site. However, synchronous replication has some requirements and limitations that must be met for it to work properly. One of these requirements is that the network latency between the two sites must be less than or equal to 5 ms1. If the network latency is higher than 5 ms, the synchronous replication will fail and the protection policy will be suspended2.

Therefore, based on the diagram, the most likely cause of the issue is that the network latency between cluster site A and cluster site B is higher than 5 ms, which prevents the synchronous replication from working. To verify this, the administrator can use the “ncli cluster ping” command to measure the network latency between the two sites3. If the network latency is indeed higher than 5 ms, the administrator can either improve the network performance or switch to a different replication mode, such as near-synchronous or asynchronous.

According to the web search results, the cluster redundancy factor (RF) determines how many copies of the cluster metadata and configuration data are stored on different nodes. By default, the cluster RF is 2, which means that there are three copies of the Zookeeper and Cassandra data on the cluster. If the cluster RF is increased to 3, then there will be five copies of the Zookeeper and Cassandra data on the cluster12. This means that the Zookeeper component can tolerate two failures, as it can still operate with a quorum of three nodes out of five3.

However, the container replication factor (RF) determines how many copies of the VM data and oplog are stored on different nodes. The container RF can be set independently for each container, and it can be different from the cluster RF. For example, a container can have RF 2 even if the cluster has RF 34. In this case, the container will only have two copies of the VM data and oplog on the cluster, regardless of the cluster RF. This means that the Extent Groups component can only tolerate one failure, as it needs at least one copy of the VM data and oplog to be available5.

Therefore, if the administrator increases the cluster RF to 3, but does not modify the containers, then the new values in the data resiliency dashboard will be Zookeeper = 2 and Extent Groups = 1.

A bully VM is a VM that consumes too many resources and causes other VMs to starve. A bully VM can affect the performance and availability of other VMs on the same host or cluster by hogging CPU, memory, disk, or network resources. A bully VM can be identified by using the VM Profile feature in Prism Central2. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows3:

• Efficient: The VM is well-provisioned and has optimal resource utilization.
• Over-provisioned: The VM has more resources than it needs and has low resource utilization.
• Constrained: The VM has less resources than it needs and has high resource utilization.
• Inactive: The VM has no resource utilization and is idle or powered off.
• Bully: The VM has high resource utilization and causes contention for other VMs.

To identify a bully VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

Prism Element and NCC are two ways to run all NCC checks manually on a Nutanix cluster. Prism Element is the web console that provides management and monitoring capabilities for a single Nutanix cluster. Prism Element has a Health dashboard that shows the status of various components and services in the cluster, such as disks, nodes, CVMs, NCC, and alerts. The Health dashboard also allows the administrator to run NCC checks manually by using the Actions drop-down menu on the right side of the screen. The administrator can choose to run all NCC checks or specific checks based on the category or severity. The NCC checks will run in the background and generate a report that can be viewed or downloaded from the Summary tab. This method is easier and faster than running NCC from the command line on the CVM.

NCC stands for Nutanix Cluster Check, which is a framework of scripts that performs system checks and validations on Nutanix clusters. NCC can detect issues related to hardware, software, configuration, hypervisor, networking, and more. NCC can be run from the command line interface (CLI) of any CVM in the cluster by using the ncc command. To run all NCC checks manually, the administrator can use the command ncc health_checks run_all, which will execute all available checks and display the results on the screen. This method is more comprehensive and detailed than running NCC from Prism Element.

References: : [Health Dashboard - Prism Element Guide] : [Nutanix Cluster Check (NCC) - Nutanix Support & Insights] : [Running NCC Checks - Nutanix Support & Insights]

A managed network is a type of network that can be created on an AHV cluster and allows VMs to automatically be assigned an IP address at creation time. A managed network uses the Nutanix IP Address Management (IPAM) service, which provides DHCP and DNS functionality for the VMs on the network. A managed network can be configured with a subnet range, a default gateway, and DNS servers. The IPAM service will allocate IP addresses from the subnet range to the VMs and register their hostnames in the DNS servers. The IPAM service will also release the IP addresses when the VMs are deleted or moved to another network1.

To create a managed network on an AHV cluster, the administrator can use Prism Element or Prism Central. The steps are as follows2:

• In Prism Element, go to the Network Configuration page and click Create Network.
• In Prism Central, go to the Networks page and click Create.
• Enter a name and description for the network.
• Select Managed as the network type.
• Enter the subnet range, default gateway, and DNS servers for the network.
• Optionally, enable VLAN tagging and enter a VLAN ID for the network.
• Click Save.

The best way to configure the VM for optimal performance is to set it up with 2 vNUMA nodes. This will ensure that the VM is configured to take advantage of the CPU and memory resources available in each node, and it will also ensure that all of the cores are utilized for the best performance. Additionally, the administrator should ensure that the VM has an affinity policy set up so that the vCPUs are evenly distributed across the four nodes. Finally, Flash Mode should be enabled in order to take advantage of the high-performance SSDs that are available in the cluster

An Application Security Policy is a security feature in Nutanix AHV that can be used to restrict network communication between virtual servers based on a variety of criteria, such as IP address, port, and protocol. By creating a policy that restricts communication to authorized hosts and applying it to the servers in enforce mode, the administrator can prevent unauthorized communication between virtual servers.

https://www.nutanix.com/products/ahv

These are the three steps that the administrator must take to increase throughput to the host. According to the network diagram, the host has two 10Gb interfaces and two 1Gb interfaces in the default bond, but only one of the 10Gb interfaces is connected to a switch. The other 10Gb interface is disconnected and has a red “X” on it. The two 1Gb interfaces are also disconnected and have dotted lines. This means that the host is using only one 10Gb interface for all its network traffic, which limits its maximum bandwidth to 10 Gbps.

To increase the throughput, the administrator should connect both 10Gb interfaces to the physical switch, preferably to different switches for redundancy and high availability. This will allow the host to use both 10Gb interfaces for network traffic, which can increase its maximum bandwidth to 20 Gbps. However, this also requires changing the bond mode from active-backup to balance-slb or balance-tcp, which are load balancing modes that distribute network traffic across multiple interfaces based on source MAC address or TCP session1. The default bond mode of active-backup only uses one interface at a time and switches to another interface only when the active one fails2.

Finally, the administrator should remove any 1Gb interfaces still connected from the default bond, as they are not needed and may cause performance issues or conflicts with the load balancing modes. The 1Gb interfaces can be used for other purposes, such as management or backup networks, by creating separate bonds or bridges for them3. Alternatively, they can be left disconnected if they are not required.

Port 389 is the default port for LDAP without SSL encryption. Port 636 is used for LDAP over SSL (LDAPS). Port 3268 and 3269 are used for Global Catalog (GC) and Global Catalog over SSL (GCSSL), respectively2.

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.

https://portal.nutanix.com/page/documents/details/?targetId=Web_Console_Guide-Prism_v4_7:lic_licensing_managing_c.html

Reclaiming Licenses (Including License Renewal)

You can reclaim and optionally re-apply licenses for nodes in your clusters:

• You must reclaim licenses when you plan to destroy a cluster. First reclaim the licenses, then destroy the cluster. You do not need to reclaim Starter licenses. These licenses are automatically applied whenever you create a cluster, including after you have destroyed a cluster.
• Return licenses to your inventory when you remove one or more nodes from a cluster. Also, if you move nodes from one cluster to another, first reclaim the licenses, move the nodes, then re-apply the licenses.
• You can reclaim licenses for nodes in your clusters in cases where you want to make modifications or downgrade licenses. For example, applying an Ultimate license to all nodes in a cluster where some nodes are currently licensed as Pro and some nodes are licensed as Ultimate. You might also want to transition nodes from Ultimate to Pro licensing.
• You must reclaim licenses when you renew licenses. First reclaim the expired licenses, then apply new licenses.

According to section 6 of the exam blueprint guide1, one of the topics covered is VM placement options. When creating a new VM on an AHV cluster, there are two ways to determine its initial placement:

• Automatic placement: The Acropolis Dynamic Scheduler (ADS) selects a host that provides adequate resources for the VM’s configuration, such as CPU, memory, disk space, and network bandwidth. ADS also considers factors such as host load, power state, availability domains, and affinity rules.
• Manual placement: The administrator can specify a host or a host group where they want to place the VM.

This will allow the administrator to quickly identify VMs that are overprovisioned or underutilized based on their performance metrics.

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-multicloud-infrastructure-6_5

According to the Nutanix Prism Central Guide, you can click on any chart in a widget to expand it and view more details about the data elements.

According to the web search results, the most efficient action an administrator should take to ensure a supported state when adding a node with a higher AOS release to an existing cluster is to perform a standalone reimage of the new node and then add it to the cluster1. This way, the new node will have the same AOS version as the existing nodes, and there will be no compatibility issues or downtime. Therefore, option C is correct, while options A, B, and D are not.

Stargate is the AOS process that handles all I/O operations for the cluster. It is responsible for determining whether an I/O from a user will be written to the OpLog or to the Extent Store, based on the type and size of the I/O. Stargate also performs data tiering, compression, deduplication, and erasure coding1. Stargate runs on every CVM and communicates with other Stargates to ensure data locality and redundancy2.

First Preference:

• Policy is applied to a specific entity

2nd Preference:

• Policy is applied to an entity type in a category

3rd Preference:

• Policy is applied to an entity type in a cluster

4th Preference:

• Policy is applied to all entities of an entity type

Comprehensive Detailed Explanation with References:In Nutanix Prism, when multiple alert policies are created and applied to the same entities, the policies are evaluated based on their specificity. The order of precedence from highest to lowest is as follows:

• Policy is applied to a specific entity: Custom alert policies that are applied to specific entities take precedence over those applied to broader categories. This is because the more specific policy is usually created with a particular context or requirement in mind for that entity.
• Policy is applied to an entity type in a category: The next level of precedence is given to policies that are applied to all entities of a certain type within a specific category. Categories allow grouping of entities based on certain criteria, and policies applied here are more specific than to an entire cluster or entity type.
• Policy is applied to an entity type in a cluster: This refers to policies that are applied to all entities of a certain type within a specific cluster. This is more general than the above two but still targets a specific cluster environment.
• Policy is applied to all entities of an entity type: The lowest precedence is given to policies that are broadly applied to all entities of a particular type across the entire Nutanix environment.

This order ensures that the most specifically targeted policies are given priority, which allows for fine-tuned control and customization of alert policies. The details of alert policy precedence are typically covered in the Nutanix Prism Central Guide and the documentation related to Prism Central's alerting and policies.

The best method to provide access for a user to view real-time performance metrics for all VMs on all clusters across the datacenter is to configure AD authentication create a custom role, assign the user to the role, and apply the role to all clusters and VMs. This method accomplishes this with the least effort and ongoing maintenance because:

• AD authentication allows Nutanix Prism Central to integrate with an existing Active Directory (AD) domain and use AD users and groups for authentication and authorization5. This simplifies user management and avoids creating local users on Prism Central.
• Creating a custom role allows Nutanix Prism Central to define granular permissions for different actions and entities based on specific needs6. This ensures that users only have access to what they need and nothing more.
• Assigning the user to the custom role allows Nutanix Prism Central to grant access rights for that user based on the role definition7. This avoids assigning permissions individually for each user.
• Applying the role to all clusters and VMs allows Nutanix Prism Central to propagate the access rights for that role across all entities in scope8. This ensures that users can view real-time performance metrics for all VMs on all clusters without having to configure each entity separately.

References: 1: Health Dashboard - Prism Element Guide 2: Understanding Native VLANs - Cisco 3: VMs may lose network connectivity if connected to virtual network with … - Nutanix Support & Insights 4: VLAN Configuration - AHV Networking Guide 5: Active Directory Authentication - Prism Central Guide 6: Create Custom Roles - Prism Central Guide 7: Assign Roles - Prism Central Guide 8: Apply Roles - Prism Central Guide

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.

According to the Nutanix Support & Insights web search result1, if the owner Controller VM becomes unavailable, the address moves to another Controller VM, ensuring that it is always available. This IP address is also used as a cluster-wide address by clients configured as part of Nutanix Files and other products. Therefore, the host will automatically redirect I/O and VMs will continue running without any interruption.

This is because there is no GUI method to unregister a cluster from Prism Central, so the process requires SSH access to the PC VM as well as to a CVM of the cluster2. The unregistration process involves getting the UUID of the cluster from the CVM and then using that to trigger de-registration from PC command line2. The unregistration process also involves cleaning up any associated metadata and configuration on both PC and PE2. Therefore, the administrator needs to use a Host SSH session to perform this task.

According to the web search results, Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments12. One of the features of Prism Central is multi-cluster Single Sign On (SSO), which allows users to log in once and access multiple clusters without re-entering credentials3.

In Nutanix AHV, when creating a virtual switch and trying to add network interfaces (NICs) to it, the NICs must be connected to the network before they can be selected and assigned to the switch. If the interfaces are showing as disconnected, the system will not allow them to be added to a virtual switch because it cannot verify their operational status or the presence of a live network connection.

It is a standard requirement for the interfaces to have physical connectivity (i.e., network cables plugged in and connected to a live switch port) so that the AHV host can detect the link status as up. Once the interfaces are connected and recognized by the host, they can then be added to a virtual switch in the Nutanix AHV.

It's important to note that while the command-line interface (CLI) is indeed a powerful tool for managing network configurations on AHV hosts, and some configurations do indeed require CLI, the inability to select disconnected interfaces is not specifically a limitation that requires the use of CLI to overcome. The focus should be on ensuring that the physical connectivity is established for the interfaces in question.

This behavior is consistent with networking best practices and Nutanix's network configuration guidelines, as detailed in the Nutanix AHV Networking Guide. This guide explains the requirements and procedures for configuring virtual switches and managing NICs in a Nutanix AHV environment.

when you create a custom alert policy, you can choose between two types of thresholds: Static Threshold and Behavioral Anomaly. Static Threshold allows you to set a fixed value for the metric that triggers the alert. Behavioral Anomaly allows you to use machine learning to detect abnormal behavior based on historical data.

If you select Behavioral Anomaly as the threshold type, you cannot set a warning level for the alert. You can only set a critical level that indicates how much deviation from normal behavior is considered an anomaly3. Therefore, the Alert warning if field is greyed out when you select Behavioral Anomaly.

According to the Nutanix Support & Insights web search result3, advertised capacity is an advanced container setting that allows the administrator to reserve an advertised storage space for a storage container. An advertised capacity setting gives the hypervisor a maximum storage size that the storage container can use. This setting can be any arbitrary value greater than or equal to the resiliency required. The hypervisor ensures that the storage container storage doesn’t go beyond the advertised capacity. If the administrator wants a container to be displayed and limited to 1TB in the hypervisor, they should set the advertised capacity to 1TB.

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.