* BGP Gateway Deployment:The BGP gateway is deployed as Azure native VMs within the Prism Central VNet. This deployment ensures seamless integration with Azure's networking infrastructure.
* Route Advertisement:The BGP gateway advertises the externally routable IP addresses to the Azure Route Server. This setup allows for dynamic routing and efficient traffic management.
* Flow Gateways (FGW) as Next Hops:Each active Flow Gateway's external IP address is used as the next hop. This configuration ensures that southbound traffic is correctly routed to the appropriate Flow
* Gateway, providing efficient and reliable connectivity.
References:
* Nutanix NC2 Networking Guide
* Azure Route Server and BGP Documentation

Cluster State Requirement: To expand a cluster, it must be operational and in a connected state to ensure seamless integration of additional nodes.
Cluster Stopped State: If the cluster is stopped, it cannot perform expansion operations.
Minimum Nodes Requirement: There is no minimum node count prerequisite for expanding the cluster as long as the cluster is connected.
Cluster Connected State: Ensuring the cluster is connected verifies that it is operational and can communicate with additional nodes being added.
Conclusion: The cluster must be in a Cluster Connected state to expand successfully.
Reference:
Nutanix Clusters Expansion Guide
Azure NC2 Configuration Documentation

* Outbound Rule Necessity: For successful cluster deployment, certain outbound connections must be allowed to ensure proper download and configuration of resources.
* Critical Destination: "Https://downloads.cloud.nutanix.com/*" is a critical endpoint from which the Nutanix software and updates are downloaded during the cluster deployment process.
* Functionality: Ensuring an outbound rule for this destination allows the deployment to fetch necessary files and updates, enabling smooth cluster setup and operation.
* Other Destinations:
* Https://portal.nutanix.com/: Used for accessing the Nutanix portal, not directly related to deployment downloads.
* Https://support.nutanix.com/: Used for support-related tasks, not for deployment-specific downloads.
* https://nutanix.dev/: Related to development and API documentation, not necessary for initial deployment.
* Conclusion: Outbound connectivity to "Https://downloads.cloud.nutanix.com/*" is essential for downloading deployment resources.
References:
* Nutanix NC2 on Azure Network Configuration Guide
* Azure Network Security Documentation

Storage Capacity Requirement: The requirement specifies that the bare metal instance must support up to 20 TB of storage capacity.
Instance Selection: Among the provided options, the AN36P instance is designed to support higher storage capacities and performance needs.
AN36P Capabilities: The AN36P instance is optimized for storage-intensive applications and provides the necessary hardware specifications to handle up to 20 TB of storage.
Comparison with Other Instances:
ND96asr: Typically optimized for GPU workloads rather than storage.
AN36: May not meet the 20 TB storage requirement.
HB176rs: Geared towards high-performance computing rather than large storage capacities.
Conclusion: Based on the requirements and instance specifications, AN36P is the most suitable choice for supporting up to 20 TB of storage.
Reference:
Nutanix NC2 Instance Types
Azure Virtual Machine Sizes