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.

Nutanix Move is a tool that allows you to migrate VMs from different sources to Nutanix AHV with minimal downtime and complexity. Nutanix Move supports migration from Hyper-V to AHV, including VMs configured for UEFI-boot. UEFI stands for Unified Extensible Firmware Interface, which is a standard for the software interface between the operating system and the firmware. UEFI-boot is a mode of booting that uses UEFI instead of BIOS (Basic Input/Output System) to load the operating system. UEFI-boot offers some advantages over BIOS-boot, such as faster boot time, larger disk support, and better security features1.
To migrate a VM configured for UEFI-boot from a Nutanix Hyper-V cluster to AHV, you need to use Nutanix Move and follow these steps2:
Download and deploy the Nutanix Move appliance on the AHV cluster.
Log in to the Nutanix Move web console and add the source Hyper-V environment and the target AHV environment.
Create a migration plan and select the VMs that you want to migrate. You can choose either automatic or manual preparation mode for the migration.
Start the migration plan and monitor the progress. The migration plan will perform data seeding, which is the process of copying the VM data from the source to the target in the background.
When the data seeding is complete, perform a cutover, which is the process of shutting down the source VMs and powering on the target VMs. The cutover will also configure the boot device for the UEFI-boot VMs on AHV.
Verify that the migrated VMs are working as expected on AHV.
References: 1: UEFI Boot - Nutanix Support & Insights 2: Hyper-V to AHV and Hyper-V to Nutanix Clusters on AWS VM Migration - Nutanix Support & Insights

Explanation:
Step 1 ---> Login into Prism Element.
Step 2 ---> Select the Gear Icon at top right of the page.
Step 3 ---> Click Upgrade Software.
Step 4 ---> Select the component to upgrade.
Step 5 ---> Click download.
Step 6 ---> Once the download completes, select upgrade.
Invalid:-
1 - Select Prism Central.
2 - Select user login.
3 - On left select upgrade Prism Central.

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.

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.