A standard NC2 deployment typically requires a management subnet and a public subnet for basic internet and console access. However, when moving to aFlow-based deployment(using Flow Virtual Networking), the architecture becomes more complex, requiringManagementandFlow Virtual Networksubnets specifically tailored for the overlay. TheManagement subnetis used for the bare-metal hosts and CVMs to communicate with the NC2 portal and Prism Central. TheFlow Virtual Network subnet(often the Transit VPC subnet) is required to host the distributed gateways that manage encapsulated Geneve traffic. These subnets are essential for segregating the management traffic from the virtualized workload traffic, ensuring that the software- defined overlay has a dedicated and secure path through the AWS VPC infrastructure.

* For the NC2 cluster deployed in the North Virginia region (us-east-id), consuming IPs from the
10.78.2.0/24 range, the subnets configured within the same CIDR range of 10.78.0.0/16 will be recognized.
* The subnetDR01 (10.78.2.0/24)is directly within the range of the deployed cluster.
* The subnetL2stretch (10.19.101.0/24)is also configured in the NC2 AWS VPC, although not in the immediate range of the cluster, it may show up due to broader network configurations for stretched L2 operations.
* SubnetsVDI (10.78.130.0/22)andDR02 (10.79.120.0/24), although part of the same VPC, are not directly within the immediate CIDR range or may not be recognized in this specific configuration scenario.
Refer to the Nutanix documentation on NC2 AWS VPC subnet configurations and Prism Element settings for detailed guidelines on network visibility and configuration.

* The 192.168.5.0/24 range is often reserved for internal cluster communication within Nutanix deployments.
* Using this CIDR range for other purposes could lead to network conflicts and connectivity issues, as it might interfere with the internal operations and communication channels of the Nutanix cluster.
* Ensuring that the CIDR range is not overlapping with any reserved ranges is crucial for maintaining proper network connectivity and cluster functionality.
Refer to the Nutanix documentation on network configuration and best practices for NC2 deployments to confirm reserved IP ranges and their appropriate use.

In an NC2 architecture usingFlow Virtual Networking (FVN)for centralized routing, the goal is to allow User VMs to communicate with external networks using their original, non-NATed IP addresses. To achieve this when connected to an AWS Transit Gateway, the routing infrastructure must be manually updated. First, astatic route must be added to the cluster ' s AWS VPC route tableto direct traffic destined for non-AWS prefixes toward the Transit Gateway. Second, astatic route must be added to the Transit Gateway ' s own route tableto ensure it knows that traffic for the Nutanix overlay CIDR should be sent back to the Cluster AWS VPC. This bidirectional static routing ensures that traffic can flow seamlessly between the Nutanix overlay and on-premises or other VPC environments without the need for address translation.

Upon creation, each node within an AWS NC2 cluster has 3 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.
Reference:
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.