NC2 Console:The NC2 console is specifically designed for deploying and managing Nutanix clusters on Azure. It provides the necessary tools and interface to configure, monitor, and manage the NC2 clusters effectively.

Cluster Deployment:Using the NC2 console ensures that all configurations and integrations with Azure are correctly handled, providing a seamless deployment experience.

References:

Nutanix NC2 Deployment Guide

Nutanix Console Documentation

Azure Directory Service Role: Azure Directory Service must be able to resolve specific Nutanix URLs to ensure proper communication and functionality during the deployment of an NC2 cluster.

Critical Endpoint: The address "Gateway-external-api.cloud.nutanix.com" is critical for establishing external API communications required for the deployment and management of the NC2 cluster.

DNS Resolution: Proper DNS resolution of this address ensures that the Azure Directory Service can interact with Nutanix services and APIs necessary for cluster operations.

Verification Process:

Ensure that DNS settings allow resolution of "Gateway-external-api.cloud.nutanix.com".

Test connectivity and resolution prior to deployment to avoid issues.

Importance: Without resolving this address, the deployment process might face connectivity issues, leading to potential deployment failures.

References:

Nutanix NC2 on Azure Setup Guide

Azure Active Directory Integration

Valid CIDR Range:When deploying an NC2 cloud cluster in Azure, a valid CIDR range is necessary to define the IP address space for the cluster and its associated networks. This range ensures that there are no conflicts with existing network configurations and provides sufficient addresses for the cluster resources.

My Nutanix Account:A my.nutanix.com account is required to access Nutanix services and manage NC2 deployments. This account allows administrators to log in, configure settings, and manage their Nutanix environment on Azure.

References:

Nutanix NC2 on Azure Deployment Guide

Azure Virtual Network Documentation

In this scenario, the issue arises from overlapping IP address ranges between the Transit VPC and the User VPC. Here’s a detailed breakdown:

Understanding ERPs (Elastic Routing Prefixes):

The ERP for the Transit VPC is 10.1.1.0/25, which covers IP addresses from 10.1.1.0 to 10.1.1.127.

The ERP for the User VPC is 10.1.1.0/24, which covers IP addresses from 10.1.1.0 to 10.1.1.255.

IP Address Overlap:

Since 10.1.1.0/25 is a subset of 10.1.1.0/24, there is a significant overlap in the IP address ranges of these two ERPs.

This overlap can cause routing issues because the same IP address range is being used in both VPCs, leading to ambiguity in routing and communication.

Communication Issue:

When a VM in the User VPC tries to communicate with other resources, the network cannot accurately determine the correct route due to the overlapping IP address ranges.

This overlap prevents proper routing and results in the VM being unable to communicate with other resources as intended.

Resolution:

To resolve this issue, the ERPs must be in different CIDR ranges. This means the IP address ranges for the Transit VPC and the User VPC should not overlap.

For example, if the Transit VPC uses 10.1.1.0/25, the User VPC could use a different range such as 10.1.2.0/24 or any other range that does not overlap with 10.1.1.0/25.

By ensuring that the ERPs are in different CIDR ranges, the network can properly route traffic between the VPCs without any conflicts or ambiguities, thereby enabling the VM in the User VPC to communicate with other resources effectively.

Azure Resource Providers: To prepare an Azure subscription for NC2, specific resource providers must be registered to enable necessary services and resources.

Required Providers:

Microsoft.Network: This provider is essential for networking functionalities, including virtual networks, subnets, and other network resources necessary for NC2 deployment.

Microsoft.Nutanix: This provider is specifically required for integrating and managing Nutanix resources within the Azure environment.

Other Providers:

Microsoft.HybridNetworkandMicrosoft.HybridCompute: These are not specifically required for NC2 but might be relevant for other hybrid or extended network configurations.

Conclusion: Registering both "Microsoft.Network" and "Microsoft.Nutanix" ensures that all necessary network and Nutanix-specific resources are available for NC2 deployment.

References:

Azure Resource Providers Documentation

Nutanix on Azure Setup Guide

Default Route for Internet Traffic:By setting the default route of 0.0.0.0/0 for the Nutanix User VPC pointing to the external-NAT network, all internet-bound traffic from the desktops will be routed through the Azure NAT Gateway, conserving bandwidth on the ExpressRoute connection.

On-Premises Route:Setting a specific route to the on-premises subnet for the Nutanix User VPC pointing to the external-No-NAT network ensures that traffic destined for on-premises resources bypasses the NAT Gateway and utilizes the ExpressRoute connection, optimizing the use of network paths.

References:

Azure NAT Gateway Documentation

Nutanix NC2 Networking Configuration Guide

Floating IP Address Limitation:The cluster already has 25 floating IP addresses in use by other VMs. If the administrator cannot assign a floating IP address to the new VM, it is because the pool of available floating IPs is exhausted.

Requesting Additional Floating IPs:To resolve this issue, the administrator needs to request additional floating IP addresses to be allocated to the NAT subnet. This will ensure that there are enough IP addresses available for all VMs requiring inbound connectivity.

References:

Nutanix Networking Configuration Guide

Azure IP Address Management Documentation

To collect the appropriate logs (Cluster_agent, Host_agent, and Hostsetup) for diagnosing the deployment issue with Nutanix Support, the administrator should:

Log in to Prism Element to access the Controller VM (CVM) console.

Run thelogbay collectcommand from the CVM console. This command collects the necessary logs and packages them for support.

This method ensures that the correct logs are gathered in a format that Nutanix Support can analyze.References

Nutanix Support Documentation on Log Collection

ERP Configuration: ERP (External Route Prefix) settings determine how traffic is routed between subnets and VPCs.

Objective: The goal is to isolate Darren-Tier3 while ensuring proper routing for Tier1 and Tier2.

Transit VPC ERP: Setting it to 10.0.0.0/16 ensures that it covers the entire VPC range, allowing traffic within Tier1 and Tier2.

Servers ERP: Setting it to 10.0.4.0/24 ensures isolation for Darren-Tier3 by limiting traffic to that specific subnet and preventing external traffic from reaching it.

Conclusion: This configuration achieves the isolation of Darren-Tier3 while allowing proper routing for Tier1 and Tier2.

References:

Nutanix Networking Documentation

Azure Virtual Network Documentation

SMTP Server Configuration:To send alert emails from Prism Central, it is essential to configure an SMTP server in the Prism Central settings. This server handles the email sending process, ensuring that alerts generated by Prism Central are properly delivered to the specified email addresses.

Email Notification Setup:The SMTP server settings include the server address, port, and authentication details. Once these settings are correctly configured, Prism Central can use the SMTP server to send out alert emails reliably.

References:

Nutanix Prism Central Administration Guide

SMTP Configuration for Email Alerts in Prism Central

Account Administrator Role:This role grants the necessary permissions for managing the Azure account, including the ability to open, close, or extend a support tunnel. These capabilities are crucial for the Nutanix Support team to perform diagnostics and troubleshooting efficiently.

Permissions Included:The Account Administrator role encompasses broader account management rights, ensuring that the user can interact with various support and operational aspects of the NC2 environment within Azure.

References:

Azure Role-Based Access Control (RBAC) Documentation

Nutanix NC2 Support Tunnel Requirements

Replication Factor (RF3):RF3 requires that data is replicated across three different nodes to ensure data durability and fault tolerance. This replication scheme allows the system to tolerate the failure of two nodes simultaneously.

Minimum Node Requirement for RF3:To meet the RF3 requirements while maintaining operational capability, a minimum of five nodes is necessary. This configuration ensures that there are enough nodes to distribute the data and provide the necessary redundancy.

References:

Nutanix Replication Factor Documentation

Nutanix NC2 on Azure Deployment Guide

Outbound Communication Whitelisting:For NC2 Azure API calls and telemetry data to function correctly, certain outbound communications must be allowed. If these communications are not whitelisted, API calls can fail, and telemetry or health data might not be reported correctly.

First Check:Given the symptoms (failing API calls and missing telemetry), the first step should be to ensure that all necessary outbound communications are correctly whitelisted. This includes ensuring that endpoints and services required for NC2 operation are accessible.

References:

Nutanix NC2 Networking Requirements

Azure Networking and Security Configuration Guide

Jump Host VM in External VNet with VNet Peering:

Deploy Jump Host VM:Deploy a VM in an external VNet that is not within the same network as Prism Central.

VNet Peering:Establish VNet peering between the external VNet and the Prism Central VNet. This allows the Jump Host to communicate with Prism Central securely.

Jump Host VM in Prism Central VNet Inside a Delegated Subnet:

Deploy Jump Host VM:Deploy the Jump Host VM directly in the Prism Central VNet within a delegated subnet. This places the Jump Host in the same network environment as Prism Central, allowing direct access.

References:

Azure VNet Peering Documentation

Nutanix NC2 Networking and Access Configuration Guide

Free Trial Expiration:Once the NC2 free trial period expires, the administrator needs to switch to a paid subscription plan to continue using all the features and functionalities provided by Nutanix NC2.

Paid Subscription Benefits:Transitioning to a paid subscription ensures uninterrupted access to NC2 features, support, and updates, maintaining the operational capabilities of the existing clusters.

References:

Nutanix Subscription and Billing Documentation

Nutanix NC2 Support and Subscription Guide

Flow Gateway VMs: Flow Gateway VMs are used to manage and route network traffic within an NC2 on Azure cluster, ensuring sufficient bandwidth for workloads.

Scalability: To ensure enough available bandwidth, multiple Flow Gateway VMs can be deployed.

Maximum Limit: The highest number of Flow Gateway VMs that can be deployed within an NC2 on Azure environment is 6, providing the necessary capacity to handle high traffic volumes and ensure optimal performance.

Conclusion: Deploying up to 6 Flow Gateway VMs ensures adequate bandwidth for NC2 workloads.

References:

Nutanix Clusters Networking Guide

Azure Network Performance Documentation

In the NC2 on Azure cluster scenario, the existing workloads were using floating IPs for inbound traffic before the addition of new Flow Gateways (FGW3 and FGW4). The NAT traffic path established initially will continue to direct traffic through the originally assigned Flow Gateways (FGW1 and FGW2). The existing workloads will not automatically utilize the new Flow Gateways (FGW3 and FGW4) without a reconfiguration or reboot, which reassigns the NAT paths.

References

Nutanix Flow Networking and Configuration Guide

Azure Monitor Overview: Azure Monitor is a comprehensive monitoring service that collects, analyzes, and acts on telemetry data from Azure resources.

Key Metrics Monitoring: Azure Monitor enables the monitoring of various Azure services such as virtual networks, virtual machines, and bare metal hosts, providing insights and visibility into their performance and health.

Comparison of Services:

Resource Manager: Manages Azure resources but does not provide detailed monitoring capabilities.

Azure Service Health: Provides personalized alerts and guidance when Azure service issues affect you but is not a comprehensive monitoring solution.

Azure Network Watcher: Focuses on network performance monitoring and diagnostics but does not cover all resource types.

Conclusion: Azure Monitor is the most suitable service for monitoring key metrics across a wide range of Azure services.

References:

Azure Monitor Documentation

Nutanix NC2 on Azure Monitoring Guide

No-NAT Path Requirement:For a No-NAT path to function, the external networks must be able to route traffic directly to the Nutanix User VPC without translation.

Externally Routable IP Address:The externally routable IP address ensures that traffic from outside networks can reach the Nutanix User VPC.

Address Space Compatibility:Sharing the same address space as the Nutanix User VPC allows for seamless integration and communication between the external network and the User VPC.

References:

Azure Virtual Network Documentation on IP Addressing

Nutanix NC2 Configuration Guide on No-NAT Networking