NCS Professional NCS-Core Nutanix Study Notes

When nodes are mistakenly configured with incorrect IP addresses and are on a different network, the most effective way to address this is to re-run the Foundation process. By using Foundation, the nodes can be completely re-imaged with the correct network settings and then properly integrated into a new cluster. This ensures that all hardware and software configurations align with the intended network and cluster settings, avoiding potential conflicts and issues that might arise from manual adjustments.

References:

• Nutanix Bible: Cluster Initialization and Foundation
• Nutanix University: Using Foundation for Node Deployment

The consultant should be aware that the subnet 192.168.5.0/24 is reserved for internal connectivity within a Nutanix cluster. This subnet is typically used for the internal operations of the Nutanix cluster, including CVM backplane communications. It is critical to ensure that this subnet does not overlap with any external network configurations to avoid networking conflicts that can affect cluster operations and communications.References: Nutanix Networking Best Practices, Nutanix Cluster Configuration Guide.

To execute the command manage_ovs --bridge_name br0 show_uplinks in a Nutanix cluster, the appropriate prompt is:

• A. nutanix@CVM-$: This command is intended for execution within the Controller Virtual Machine (CVM) environment, and "nutanix@CVM-$" is the standard user prompt in the CVM where such network commands are run.

References:

• Nutanix Bible (https://www.nutanixbible.com), especially sections on managing virtual bridges and networking commands.
• Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com), which includes details on command-line operations within the CVM.

According to Nutanix best practices for ESXi clusters, using a vSphere Standard Switch with "Route based on originating port ID" is recommended for load balancing. This method ensures that the same virtual port ID within a vSwitch uses the same uplink from the vSwitch. This load balancing policy provides an even distribution of traffic and redundancy by utilizing both NICs effectively without requiring any specific physical switch configurations, such as EtherChannel or LACP.References: The Nutanix Bible, NCS-Core 6.8 course content, and VMware’s documentation on vSphere Standard Switch load balancing methods.