Diagnostics for VMware Cloud Foundation: vMotion Troubleshooting Check Next Steps

Products

• VCF Operations

Issue/Introduction

VMware Cloud Foundation Operations provides a troubleshooting workflow to diagnose vMotion failures that could cause a vMotion to timeout. This KB lists the specific checks that are performed and recommended next steps.

Environment

Operations for VMware Cloud Foundation 9.0

Resolution

Below is the list of the specific checks that are performed and recommended next steps. 

Error Message	Troubleshooting
Netstack <netstack_name> is not enabled.	Navigate to your ESXi host in the vSphere Client.  Go to "Networking" and select the relevant VMkernel adapter.  Ensure the network settings are correctly configured.
Netstack <netstack_name> is not ready.	Navigate to your ESXi host in the vSphere Client.  Go to "Networking" and select the relevant VMkernel adapter.  Ensure the network settings are correctly configured.
Unable to find vMotion network interface for <netstack_name>	Navigate to the "Hosts and Clusters" view and choose the specific ESXi host you want to check. Go to the "Configure" tab and then select "Networking" > "VMkernel adapters". Look for the VMkernel port group dedicated to vMotion and ensure the "vMotion" service is checked as enabled.
Unable to fetch IP Interface details.	Navigate to your ESXi host in the vSphere Client.  Go to "Networking" and select the relevant VMkernel adapter.  Ensure the network settings are correctly configured.
Unable to fetch NIC for vSwitch <standard_or_dvs_switch_name>.	Restart management services
Admin Status of NIC <nic_name> is down.	To bring a NIC up: esxcli network nic up -n <NIC_name>
Link Status of NIC <nic_name> is down.	Verify the network adapter is properly connected and configured on the ESXi host. Check if the correct drivers are installed for your network card. https://knowledge.broadcom.com/external/article/324496
vSwitch <standard_or_dvs_switch_name> MTU <switch_mtu_value> is greater than NIC <nic_name> MTU <nic_mtu_value>.	Open the vSphere Client and navigate to the ESXi host  Click the Configure tab  Under Networking, click Virtual switches  Select the vSphere switch to modify  Click the Edit settings icon  On the Properties page, change the MTU parameter  Click OK
vSwitch <standard_or_dvs_switch_name> MTU <switch_mtu_value> is less than NIC <nic_name> MTU <nic_mtu_value>.	Open the vSphere client and navigate to Home > Inventory > Hosts and Clusters  Select the host  Click the Configuration tab  Select Networking in the Hardware menu  Choose vSphere Standard Switch in the View field  Click Properties  Select vSwitch on the Ports tab  Click Edit  On the General tab, change the MTU (under Advanced Properties) from the default value (1500) to 9000  Click OK
Unable to fetch MTU value for interface <network_interface_name>	Restart management services
MTU value <mtu_value> is less than default ping size of 64 for interface <network_interface_name>	Open the vSphere Client and navigate to the ESXi host  Click the Configure tab  Under Networking, click Virtual switches  Select the vSphere switch to modify  Click the Edit settings icon  On the Properties page, change the MTU parameter  Click OK
MTU value <mtu_value> is greater than maximum ping size of 9000 for interface <network_interface_name>	Open the vSphere Client and navigate to the ESXi host  Click the Configure tab  Under Networking, click Virtual switches  Select the vSphere switch to modify  Click the Edit settings icon  On the Properties page, change the MTU parameter  Click OK
Ping check has failed for <network_interface_name>. <number> packets lost.	Check physical network configuration Example: vmkping -I vmkX #.#.#.# -d -s 1472
Ping check has failed for <network_interface_name> as RTT is too high: <rtt_value>.	Check physical network configuration
Ping check has failed with warning for <network_interface_name> as RTT is high: <rtt_value>.	Check physical network configuration
IP Address <ip_address> is assigned to interfaces: [<ip_interface_name> on host <host_name>] and <ip_interface_name> on host <host_name>	Check physical network configuration
IP Interface <ip_interface_name> is using DHCP.	To set a static IPv4 address on a VMkernel (vmk) interface in ESXi, access the network settings of the specific VMkernel adapter through the vSphere Client, select "Static" under IPv4 settings, and then manually input the desired IP address, subnet mask, and default gateway;
Datastore <datastore_name> is inaccessible with reason <inaccessible_reason>	Please attempt to rescan to regain access to the datastore in question. If the rescan does not work please work with your storage team and/or storage vendor on resolution actions.

Additional Information

Understanding and troubleshooting vMotion