Nutanix Updated NCP-CI-Azure Exam Questions and Answers by aden

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

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

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

NAT Gateways:Necessary for providing outbound internet access to resources in the private subnet. It ensures that the virtual network can communicate with external services securely.

Delegated Subnets:Required for deploying specific Azure services within the virtual network, allowing controlled access and management of the resources within these subnets.

Flow Gateway Subnets:These subnets are used for managing traffic flow within the network, ensuring efficient routing and connectivity between different parts of the NC2 infrastructure.

VNet Peers:Establish connections between different virtual networks within Azure, enabling seamless communication and resource sharing across various parts of the NC2 deployment.

References:

Azure Virtual Network Documentation

Nutanix NC2 Networking Setup Guide