For ensuring that Nutanix storage containers can be mounted on non-Nutanix hosts for data migration workflows, the consultant should validate the configuration under: A. Prism Element - Settings - Filesystem Whitelist. This setting allows specific non-Nutanix hosts to access the Nutanix storage containers, which is essential for environments where data must be accessible to systems outside the Nutanix cluster. By whitelisting the IP addresses or hostnames of these external systems, they are granted the necessary permissions to mount and interact with the Nutanix file systems. References : Nutanix Prism Element User Guide, Nutanix Storage and Filesystem Configuration Best Practices.

In the As-Built Guide for an AHV cluster deployment with each node configured with four NICs, the consultant should manually update:

A. Node Port Layout Diagram : To reflect the physical connectivity and usage of each NIC on the nodes.

B. Network Cabling Diagram : To accurately document how each node is connected to the network infrastructure, ensuring clarity on physical network setup.

References :

Nutanix Bible ( https://www.nutanixbible.com ), where documentation standards and diagrams are emphasized.

Nutanix University: NCS-Core 6.8 Training ( https://university.nutanix.com ), covering the importance of accurate network and port documentation in deployment guides.

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. References : Nutanix Command Reference Guide, Cisco Nexus 9000 Series documentation.

When a NearSync Replication window is missed due to high write volume during nightly backups, the expected behavior of the system is to adjust the replication schedule temporarily and continuously attempt to return to the configured NearSync schedule. The correct answers are:

Option B, " Protection Domain transitions back to the hourly schedule. " If the NearSync cannot maintain the 15-minute schedule due to excessive write volume, it may temporarily fall back to a less frequent schedule, such as hourly, to stabilize.

Option D, " The system continuously tries to get to the NearSync schedule. " NearSync is designed to handle transient high-load situations by trying to catch up and revert to the pre-set NearSync schedule as conditions allow.

References : These behaviors are outlined in the Nutanix documentation for NearSync, which describes how the system manages periods of high I/O and missed replication windows.

Ref: https://next.nutanix.com/community-blog-40/nutanix-just-made-ahv-image-management-painless-33144

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.

To determine the correct answer, you must evaluate the requirements for installing a Nutanix NX-3460-G6 block. Each block typically occupies 2U of rack space. Since the customer has two blocks, a total of 4U is required, which fits within the available 5U rack space. Additionally, each block requires two power sockets (one for each node in the block), totaling four sockets. Since there are six available sockets, there is enough power availability. Therefore, the primary constraints are adequately met in terms of rack space and power sockets. The mention of network ports and their sufficiency is not required here, as it isn ' t the limiting factor based on the details provided.

References :

Nutanix Bible ( https://www.nutanixbible.com )

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

Nutanix Deployment Guide

Nutanix Hardware and Installation Guide

The IPMI address on a Nutanix hardware installation can be set in two ways:

BIOS configuration : Access the BIOS settings during boot-up to manually configure the IPMI address directly on the hardware.

ipmitool : Use the ipmitool command-line utility to configure the IPMI address from a remote session or script, which provides a way to automate or manage IP settings without needing physical access to the BIOS.

References :

Nutanix Bible ( https://www.nutanixbible.com ), particularly the sections on hardware installation and IPMI settings.

Nutanix University: NCS-Core 6.8 Training ( https://university.nutanix.com ), detailing tools and techniques for IPMI configuration.

In this scenario, the delay and packet loss during failover when one of the network cables is disconnected can be addressed by enabling " Portfast " on the switch ports connected to the Nutanix nodes. Portfast is a Cisco network switch feature that allows network switches to immediately bring ports into the forwarding state during connectivity changes, bypassing the usual listening and learning states of Spanning Tree Protocol (STP). This significantly reduces the time to re-establish network connectivity, thereby minimizing the packet loss during such failover events. Enabling Portfast is crucial for endpoints like servers where quick recovery from disconnections is necessary. References : Cisco Networking Academy materials on STP and Portfast, Nutanix Bible.

In scenarios where VMs have been migrated to a new cluster and they were previously on VLAN 10 but can no longer communicate, the most likely cause is that the VLAN ID setting on the virtual network interface cards (VNICs) of the VMs does not match the VLAN configuration of the new network. Ensuring that the VLAN IDs are correctly set to match the network configuration of the new cluster is essential for proper network communication. References :

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Networking chapter ( https://www.nutanixbible.com/ )