Pearson NCP-MCI-6.5 New Attempt

The output in the exhibit indicates that the node's network interfaces (eth0-eth3) are bonded together using LACP (Link Aggregation Control Protocol) with 'balance-tcp' as the bonding mode and LACP speed set to 'fast'. For LACP to function correctly, the switch ports to which the node is connected must also be configured to support LACP. If the ports on the upstream switch are not configured for LACP, the bond will not be able to establish properly, and the node will not communicate effectively on the network, making it undiscoverable when attempting to expand the cluster.

The absence of an operational LACP configuration could prevent the new node from joining the existing cluster as the node's network interfaces would not be able to pass traffic correctly. This can be verified by checking the switch configuration to ensure that the ports are set to participate in an LACP bond.

The other options, such as a firewall blocking discovery traffic (Option A) or the node being on different VLANs (Option C), are possible causes for a node not being discovered, but given the specific command output provided, the most likely cause is related to the switch port configuration for LACP. Option D, regarding completing LACP configuration after cluster expansion, is not correct because LACP needs to be operational for the node to communicate with the cluster during the expansion process.

Proper LACP configuration is critical for network communication in a Nutanix AHV cluster, and this is covered in detail in the Nutanix AHV and Networking documentation. It outlines the steps for configuring network bonds and LACP on both the AHV hosts and the connecting network infrastructure.

Nutanix leverages a method for determining the bands called ‘Generalized Extreme Studentized Deviate Test’. A simple way to think about this is similar to a confidence interval where the values are between the lower and upper limits established by the algorithm.

Another web source3 shows an example of how anomaly detection works in Nutanix Prism Central. In the video, you can see that when the observed value of a metric deviates significantly from the predicted value based on historical data, an anomaly event is triggered and displayed on a chart.

Therefore, by comparing the observed values with the predicted values based on historical data, Nutanix anomaly detection can identify abnormal behavior and alert you accordingly.

Active-Active is a bond mode that allows all uplinks in the bond to be used simultaneously for traffic transmission and reception. This bond mode provides load balancing and increased bandwidth for the AHV host and its VMs. Active-Active bond mode uses a hashing algorithm based on source MAC addresses to distribute traffic across different uplinks in the bond. Each individual VM NIC uses only a single bond member interface at a time, but multiple VM NICs are spread across different bond member interfaces. As a result, it is possible for a Nutanix AHV node with two 10 Gb interfaces to use up to 20 Gbps of network throughput, while individual VMs have a maximum throughput of 10 Gbps6.

Therefore, if an administrator needs to optimize for maximum single VM throughput, they should select Active-Active bond mode for their AHV cluster. This bond mode can be configured using Prism Element UI or manage-ovs commands on each AHV host7. No additional configuration is required on the upstream switch side, as long as the switches are interconnected physically or virtually and both uplinks trunk the same VLANs8.