Nutanix NCS-Core Practice Test - Questions Answers, Page 19

To limit a datastore to a specific capacity within a Nutanix cluster, the best approach is to configure the advertised capacity in the Container Advanced Settings. Setting the advertised capacity to 100GB ensures that this amount of storage is reported to external entities (like hypervisors or operating systems) as the total usable capacity of the datastore, effectively preventing the storage of additional data beyond this limit. This method is preferred over reserving capacity, which guarantees space for specific uses but doesn't limit the total size visible to the system.

Nutanix Bible (https://www.nutanixbible.com), specifically the section on storage container configuration.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com), covering datastore management.

In this scenario, the connectivity issue arises because the VLAN settings require a specific configuration on the vSwitch settings when using LACP. When using LACP for load balancing network traffic, the vSwitch or Distributed Switch must be configured with the 'Route based on IP hash' load balancing algorithm. This setting is necessary to properly distribute the traffic across the LACP bonded links. Not selecting this setting in vSwitch0 settings would result in improper handling of network packets over the LACP bonded links, thereby causing the hosts and CVMs to be unreachable. Adjusting the vSwitch settings to 'Route based on IP hash' should resolve the connectivity issue.

Reference: VMware vSphere Networking documentation, Nutanix Bible LACP configuration guidelines.

To troubleshoot physical network mis-cabling without physical access to the data center and connected to Cisco Nexus 9k switches, the appropriate command to run from the Nutanix AHV host is lldpctl. This command allows the consultant to view the Link Layer Discovery Protocol (LLDP) information about directly connected devices. LLDP is supported on Nexus switches and provides detailed network topology information, which is crucial for identifying how the AHV nodes are connected to the switches, and to verify correct physical connections.

Reference: Nutanix Command Reference Guide, Cisco Nexus 9000 Series documentation.

For a Nutanix cluster to support Replication Factor 3 (RF3), a minimum of 5 nodes is required. RF3 means that three copies of the data are maintained across the cluster for fault tolerance and high availability. Having at least five nodes ensures that there are sufficient nodes to distribute these copies across different fault domains, minimizing the risk of data loss and providing improved resilience against node failures.

Reference: Nutanix Bible, Nutanix Technical Documentation on Data Resiliency.

If the Foundation VM fails to boot and other methods need to be considered, the best alternative is the Foundation Applet. This lightweight tool runs on a laptop or other device and doesn't require booting a VM, providing a straightforward method to image Nutanix hardware, particularly useful in situations where hardware constraints or other issues prevent the use of a full Foundation VM.

Nutanix Foundation Installation Guide: Nutanix Documentation

Nutanix Field Installation Guide and Tools Overview

When changing VLAN configurations for hosts and Controller Virtual Machines (CVMs) in a Nutanix cluster, doing so while the cluster is running can result in temporary communication losses, leading to alerts such as a node appearing down. To avoid these disruptions and ensure a smooth reconfiguration process, it is advisable to stop the cluster services before making VLAN changes. This prevents the cluster from detecting intermittent connectivity as node failures, thereby avoiding false alerts in Prism Element.

Nutanix Bible (https://www.nutanixbible.com), particularly the sections discussing cluster operations and network reconfiguration.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com), which includes best practices for network configuration.

The failure to discover nodes during installation can often be attributed to the lack of IPv6 support on the network, especially if the Foundation process relies on IPv6 for node discovery. If IPv6 is not enabled on the customer's switch, the discovery packets may not be properly routed, resulting in the nodes not being discovered. Enabling IPv6 on the switch could resolve this discovery issue.

Nutanix Foundation Troubleshooting Guide: Nutanix Support Portal

Network Configuration and Troubleshooting Documentation

During the Nutanix Foundation process, if imaging succeeds but cluster creation fails, the foundation.out log is the primary resource for investigating issues related to cluster creation. This log file contains detailed information about the steps undertaken by the Foundation process, including any errors or issues encountered during the cluster creation phase, making it invaluable for diagnosing problems that prevent successful cluster configuration.

Nutanix Bible (https://www.nutanixbible.com), particularly the sections on troubleshooting with logs.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com), where log file analysis is discussed in the context of deployment troubleshooting.

Ref: