Nutanix NCS-CORE - Questions & Answers

To satisfy the customer's requirements for maximum uptime and throughput in an AHV cluster deployment with link aggregation at the Top-of-Rack (TOR) switches, the consultant should: Bonded 2 x 40GbE Adapters with LACP Enabled for Storage Traffic and Guest Traffic using balance-tcp: This configuration leverages Link Aggregation Control Protocol (LACP) to combine the bandwidth of the two 40GbE adapters, enhancing both redundancy and throughput. The balance-tcp mode ensures effective load balancing of traffic based on TCP session ensuring optimal use of available bandwidth and improved fault tolerance.

References:
Nutanix Bible (https://www.nutanixbible.com)
, particularly the sections discussing network configurations and LACP. Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com)
, which covers advanced network settings for performance optimization.

In a Nutanix environment, if the Foundation VM is not discovering the hardware, it could be due to issues with the IPMI (Intelligent Platform Management Interface) settings. IPMI is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system's CPU, firmware (BIOS or UEFI), and operating system.

In this scenario, the consultant should connect a crash cart to each node, log in to the pre-installed AHV hypervisor, and run the IPMITool commands to set the IPMI IP Address, subnet, and gateway for each node. After setting the IPMI settings, the consultant should run Foundation using the configured IPMI addresses that were just set.

This will ensure that the Foundation VM can communicate with the nodes via IPMI and discover the hardware, allowing the installation to proceed.

References:
[Nutanix Support & Insights]
[Nutanix Community]
[Nutanix Documentation]
[Nutanix Certified services - core (NCS-Core) 6.8 - Nutanix University]
[Nutanix Bible]
[Nutanix Certified services - core (NCS-Core) 6.8 Playlist - YouTube]

For scenarios requiring VM availability during unplanned outages, AHV Metro with Witness Operation is designed to handle such situations. AHV Metro Availability enables synchronous replication between two sites with a witness that arbitrates site availability in case of a split-brain scenario. This setup is intended for automatic failover during service disruptions, ensuring continuous availability of VMs without manual intervention.

References:
Nutanix Bible (https://www.nutanixbible.com)
, particularly the sections on disaster recovery and AHV Metro Availability. Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com)
, covering disaster recovery strategies and configurations.

Ref:
https://next.nutanix.com/server-virtualization-27/iops-latency-issue-1168

The proper network configuration to solve the described issue involves using tagged VLANs for the CVM (Controller Virtual Machine) and host, allowing these components to correctly interact with the customer's VLAN-configured network. For the IPMI (Intelligent Platform Management Interface), which is used for out-of-band management and does not require connectivity to multiple VLANs, setting it to access mode is appropriate. This configuration ensures that the IPMI only communicates over a single, untagged VLAN, effectively isolating its traffic from the production network.

References:
Nutanix Bible (https://www.nutanixbible.com)
, particularly the sections on networking and VLAN configurations. Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com)
, where VLAN and network settings are covered.

In the deployment of a two-node cluster at a remote branch office, the presence of a Witness VM is essential to manage the cluster quorum and data integrity in case one of the nodes fails or becomes unreachable. The Witness VM acts as an external arbitrator that helps prevent data unavailability and split-brain scenarios in a situation where the cluster nodes cannot communicate with each other. This configuration is necessary because with only two nodes, there isn't a third node to maintain quorum natively.
References:
Nutanix Bible, Nutanix University

Given the symptoms where two nodes correctly failover but lose communication with the third node after an SFP+ is removed, the first action should be to:

Validate the SFP+ is fully plugged into the node and switch: This is critical because a loose or partially connected SFP+ can cause intermittent network issues, which seems to be the problem based on the scenario described.

References:
Nutanix Bible (https://www.nutanixbible.com)
, particularly the network troubleshooting sections. Nutanix Field Installation Guide, which provides detailed steps on how to ensure hardware components like SFPs are correctly installed.

Based on the subnet assignments from the exhibit provided, the Hypervisor Management IP addresses fall within the 10.170.0.5, 10.170.0.6, 10.170.0.7 range with a subnet mask of 255.255.240.0, indicating a /20 subnet. However, the Foundation VM (FVM) and the Consultant Laptop should ideally be on the same subnet as the Controller Virtual Machine (CVM) to facilitate easy access and management. The CVM IP addresses indicated are 10.170.0.4, 10.170.0.9, and 10.170.0.10 with subnet 255.255.240.0 (/20). Thus, the appropriate choice for the FVM and Laptop that matches the subnet without overlapping with existing IPs and allows network configuration without conflicts would be in the same /24 range as suggested in option D, i.e., FVM:
10.170.25.2/24, Laptop: 10.170.25.12/24.

References:
Nutanix Networking and Foundation Setup Guidelines