1. Check to make sure the Port group name associated with the VM's network adapter in the Virtual Distributed Switch (vDS) indeed exists and is spelled correctly. If not, go to Edit Settings on the VM and check that the Connected checkbox is selected.
2. Check to ensure that the VM has no underlying issues related to storage, like resource contention. You can log in to the VM console and check the following:
a. Connect to vCenter Server or the ESXi host, using vSphere Client.
b. Select the target VM in the inventory.
c. Click the Performance tab.
d. Click Chart Options to customize the performance chart.
e. Under the CPU heading, select Real-time.
f. Under the Chart Type heading, select Line Graph.
g. Under the Objects list, select the VM by name.
h. Under the Counters list, select Co-stop, Run, Ready, and Wait.
i. Optionally, save the chart settings to make re-use easier.
j. Click OK.
k. Make note of the four metrics displayed. Each is measured in milliseconds.
3. Verify that the virtual network adapter is present and connected.
4. Check the networking configuration within the VM's guest OS is correct and accurate.
5. Verify that the TCP/IP stack is functioning properly.
6. Verify that the vDS has enough ports for this VM.
7. Ensure that the VM's IPSec configuration is configured correctly and that it is not corrupted.
8. Check that the VM is configured with two vNICs to eliminate a NIC on a physical configuration issue.
* If the load balancing policy is set to Default Virtual Port ID at the vDS level:
* If the load balancing policy is set to IP Hash at the vDS level:
a. Ensure that the physical switch ports are configured as port-channel.
b. Shutdown all but one of the physical ports the NICs are connected to, and toggle this between all ports by keeping only one port connected at a time. Make a note of the port/NIC combination where the VM is losing networking connectivity.
* You can also use esxtop output using the n option (for networking) to see which pNIC the VM is using. Try shutting down the ports on the physical switch one at a time to determine where the VM is losing network connectivity. This also rules out any misconfiguration on the physical switch port(s).
2. Check to ensure that the VM has no underlying issues related to storage, like resource contention. You can log in to the VM console and check the following:
a. Connect to vCenter Server or the ESXi host, using vSphere Client.
b. Select the target VM in the inventory.
c. Click the Performance tab.
d. Click Chart Options to customize the performance chart.
e. Under the CPU heading, select Real-time.
f. Under the Chart Type heading, select Line Graph.
g. Under the Objects list, select the VM by name.
h. Under the Counters list, select Co-stop, Run, Ready, and Wait.
i. Optionally, save the chart settings to make re-use easier.
j. Click OK.
k. Make note of the four metrics displayed. Each is measured in milliseconds.
3. Verify that the virtual network adapter is present and connected.
4. Check the networking configuration within the VM's guest OS is correct and accurate.
5. Verify that the TCP/IP stack is functioning properly.
6. Verify that the vDS has enough ports for this VM.
7. Ensure that the VM's IPSec configuration is configured correctly and that it is not corrupted.
8. Check that the VM is configured with two vNICs to eliminate a NIC on a physical configuration issue.
* If the load balancing policy is set to Default Virtual Port ID at the vDS level:
Leave one vNIC connected with one uplink on the vDS, then try a different vNIC and pNIC combination until you determine which VM is losing connectivity.
* If the load balancing policy is set to IP Hash at the vDS level:
a. Ensure that the physical switch ports are configured as port-channel.
b. Shutdown all but one of the physical ports the NICs are connected to, and toggle this between all ports by keeping only one port connected at a time. Make a note of the port/NIC combination where the VM is losing networking connectivity.
* You can also use esxtop output using the n option (for networking) to see which pNIC the VM is using. Try shutting down the ports on the physical switch one at a time to determine where the VM is losing network connectivity. This also rules out any misconfiguration on the physical switch port(s).
No comments:
Post a Comment