AVTEP (VXLAN Tunnel Endpoint) Gatewayshowing a status of " Down " indicates a connectivity or configuration failure within the control plane. In an NC2 environment, the gateway relies on consistent communication withPrism Central (PC)for management and synchronization, as well asNTP and DNSfor time-sync and name resolution. If the route tables in the AWS VPC are missing the necessary entries to reach these management services, the VTEP gateway will fail to initialize or maintain its heartbeat, resulting in a " Down " status. While on-premises reachability is important for traffic flow, the failure to create the extension entirely usually points to these missing internal routes that prevent the Nutanix software components from coordinating correctly within the cloud environment.

* For a VM to be accessible over the internet through a load balancer, the VM itself must have a public IP address.
* In this case, the health check for the VM target is failing and the DNS returns a " NOT Found " message because web-1 does not have a public IP assigned.
* Without a public IP, the load balancer cannot route traffic to web-1 from the internet.
* Assigning a public IP to web-1 ensures that the VM can be accessed via the load balancer, resolving the connectivity issue.
Refer to the AWS documentation on network load balancers and public IP assignments, and Nutanix documentation on VM network configurations.

* Upon creation, each node within an AWS NC2 cluster has3 Amazon Elastic Block Store (EBS)volumes attached.
* These volumes are used for different purposes, such as operating system storage, Nutanix services, and user data storage.
* The number of EBS volumes is designed to ensure adequate storage performance and capacity for the NC2 cluster ' s operations and workload demands.
Refer to the Nutanix documentation on NC2 cluster setup and AWS EBS volume configurations to confirm the details on the number and purpose of EBS volumes attached to each node.

A heterogeneous cluster allows organizations to mix different bare-metal instance types to satisfy diverse workload requirements, such as combining compute-heavy and storage-heavy nodes. According to Nutanix architectural guidelines for NC2 on AWS, administrators can mix amaximum of 3 different instance typeswithin a single cluster. This limitation ensures that the Distributed Storage Fabric (DSF) can maintain predictable performance and balanced data distribution across the varied hardware. When designing such a cluster, it is also vital that the number of nodes of each type is a multiple of the Replication Factor (RF) to ensure data redundancy is maintained. Mixing more than three types could lead to significant performance skews and complex management of hardware affinity rules.

When creating user VM subnets for multiple NC2 clusters in AWS, the best approach is to create guest-VM subnets for each cluster. This ensures that each cluster has its own dedicated subnets, which simplifies network management and avoids potential IP conflicts.
Advantages of Dedicated Subnets:
Isolation: Each cluster operates in its own subnet, providing better isolation and security.
Management: Easier to manage and troubleshoot network issues when each cluster has its own subnets.
Scalability: More scalable as each subnet can be managed and expanded independently.
Steps to Create Guest-VM Subnets:
Identify the IP range for each subnet.
In the AWS VPC console, create a new subnet for each cluster using the identified IP ranges.
Associate the new subnets with the respective clusters during or after the cluster deployment process.
Why Not Shared Subnets:
Shared subnets could lead to IP conflicts and make network management more complex, especially as the number of clusters grows.
Reference:
Nutanix Cloud Clusters on AWS Administration Guide
AWS VPC Subnet Creation Documentation