Which action should be used to troubleshoot without disrupting the VMs running on this node?

An alert about RX errors on eth2 on a node is reported in the cluster. The administrator logs in to the CVM in question, checks the ping_* files in the data/logs/syststats folder, and notices intermittent ping loss.

The node in question has the following network configuration:

Which action should be used to troubleshoot without disrupting the VMs running on this node?
A . Replace the cable from eth2 to the switch
B . Remove eth3 from br0-up and monitor for new alerts
C . Check the port on the switch side for any errors
D . Enable balance-s1b on br0-up and monitor if a problem persists

View Answer

Answer: C

Explanation:

Given the reported RX errors on eth2 and the intermittent ping loss as observed from the CVM logs, the best initial troubleshooting step that avoids VM disruption is to inspect the switch port for errors. Option C, "Check the port on the switch side for any errors," is the most direct and non-invasive approach to determining if the issue lies with the network infrastructure rather than the server hardware itself or the configuration.

This action helps identify whether the problem is related to the physical connection (e.g., port issues, switch configuration errors) without altering the current active network setup on the Nutanix node. If errors are found on the switch port, adjustments or repairs can be made accordingly, potentially resolving the RX errors without impacting the running VMs.

Reference: This recommendation follows Nutanix’s best practices for network troubleshooting, focusing first on external network components before altering host configurations.