Pass the Nutanix Nutanix Certified Professional (NCP) NCP-CI-Azure Questions and answers with CertsForce

Cloud Hardware Support: For issues related to cloud hardware, such as EC2 instances or VPC configurations, the responsible entity is typically the public cloud vendor.

Nutanix Responsibility: Nutanix manages the software layer and integration aspects of the NC2 service, but the underlying hardware support is managed by the cloud provider (e.g., AWS, Azure).

Support Process:

Public Cloud Vendor: Contact the public cloud vendor for issues directly related to the hardware, as they own and manage the physical infrastructure.

Nutanix: For software and configuration issues specific to the NC2 service, contact Nutanix support.

Conclusion: For cloud hardware-related support, the appropriate contact is the public cloud vendor.

References:

Nutanix Support Guide

Azure Support Documentation

Payment Method Options:When using a Pay As You Go subscription plan and opting to pay directly to Nutanix, wire transfer is a valid and secure payment method.

Direct Payment:Wire transfers allow for the direct transfer of funds from the organization's bank account to Nutanix, ensuring a straightforward and efficient payment process.

References:

Nutanix Billing and Payment Documentation

Pay As You Go Subscription Payment Methods 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 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.

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

To connect the company's on-premises datacenter to the Azure cloud environment while avoiding traffic over the public internet, the administrator should use Azure ExpressRoute. ExpressRoute provides a private connection to Azure, offering more reliability, faster speeds, and lower latencies compared to typical internet connections. This service ensures that data traffic does not traverse the public internet, enhancing security and performance.References

Azure ExpressRoute Overview

Cloud Account Configuration:When setting up a cloud account for the NC2 organization, the administrator can specify which regions are available for deploying clusters.

Restricting Regions:This ensures that the Finance organization can only deploy clusters into the designated regions, complying with organizational policies and requirements.

References:

Nutanix NC2 Configuration Guide

Azure Subscription and Resource Management Documentation

my.nutanix.com Portal:This portal provides access to various Nutanix services and features, including the NC2 deployment interface.

NC2 Tile:The NC2 tile within the portal is specifically designed for deploying and managing Nutanix Cloud Clusters. It provides the necessary tools and settings to initiate and configure NC2 clusters on Azure or other cloud environments.

References:

Nutanix NC2 Deployment Guide

my.nutanix.com Portal 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.

References:

Nutanix Clusters Expansion Guide

Azure NC2 Configuration Documentation

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