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

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

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

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

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

In the scenario presented, the NC2 cluster was initially deployed with two Flow Gateways (FGW1 and FGW2) in HA. After adding four bare-metal nodes and additional workloads, two more Flow Gateways (FGW3 and FGW4) were added to handle the increased bandwidth for north/south traffic. Given the configuration, the existing workloads can utilize all available Flow Gateways (FGW1, FGW2, FGW3, and FGW4) for No-NAT (routed) traffic paths. This setup allows for Equal Cost Multipath (ECMP) routing, distributing traffic load across all Flow Gateways.

References

Nutanix Flow Networking

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

Node Termination Observation:When a node is terminated from the Azure portal, the NC2 cluster will detect that the node is no longer operational.

Marking as Degraded:NC2 will mark the node as degraded, indicating that the node is not functioning as expected. This status allows administrators to take necessary actions to resolve the issue, such as provisioning a new node or addressing the degradation cause.

References:

Nutanix NC2 Cluster Management Guide

Azure Instance Termination Documentation

NC2 Cluster Node Limit: NC2 on Azure has specific limitations regarding the maximum number of nodes supported in a single cluster.

Maximum Nodes: According to the current NC2 on Azure guidelines, a single cluster can support up to 18 nodes.

Workload Support: This limitation ensures optimal performance and management of resources within the Azure environment.

Comparison of Options:

14 nodes: Less than the maximum supported.

24 nodes and 28 nodes: Exceed the maximum supported, potentially leading to performance and management issues.

Conclusion: For supporting new workloads, the maximum number of nodes in an NC2 on Azure environment is 18.

References:

Nutanix Clusters on Azure Technical Specifications

Azure Virtual Machine Scale Sets Documentation

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

NC2 on Azure Deployment: Deploying Nutanix clusters in Azure involves configuring various components, each needing appropriate network isolation and configuration.

Components and vNets:

Bare-metal instance: Requires its own vNet to ensure proper network isolation and performance.

Prism Central: Needs a dedicated vNet to manage and monitor the Nutanix environment, ensuring it has the required network access and isolation.

Azure Load Balancer: Does not require its own vNet but needs to be associated with the appropriate vNet where services are deployed.

Virtual Network Gateway: Is used for VPN connections but does not necessitate a separate vNet; it operates within an existing vNet.

Network Isolation: Providing separate vNets for Bare-metal instances and Prism Central ensures optimal performance and management capabilities.

Conclusion: Both Bare-metal instances and Prism Central require their own vNets in the NC2 on Azure deployment.

References:

Nutanix Clusters on Azure Deployment Guide

Azure Virtual Network Documentation