Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting virtual machine default gateway connection issues (1007910)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 127109Language:
Chinese (Simplified)JapaneseEnglish

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

The default gateway connection fails.

Cannot connect to anything outside of the subnet.

You experience connectivity issues.

Purpose

This article troubleshoots virtual machine default gateway connection failures.

Note: If connection to the default gateway is successful, but connections to other subnets are unsuccessful, then there is an issue in routing/Layer 3. VMware recommends to contact your network team to determine why the Layer 3 connections are failing.

Resolution

To troubleshoot this issue

Compare the virtual machine with the issue to other virtual machines in the same port group/subnet.

If all VMs in the same subnet and on the same host have an issue reaching the default gateway, check the VLAN configuration on the port group and ask your network team to also check the VLAN configuration on the physical switch. For more information, see VLAN configuration on virtual switches, physical switches, and virtual machines (1003806) .

If only a few VMs have a gateway connectivity issue, open an SSH session to the host and run esxtop then n (for networking) to verify which vmnics the VMs are using.

If the working VMs are on one vmnic and the non-working VMs are on a different vmnic, then there is a misconfiguration on the non-working vmnic. Have your network team check the VLAN configuration for both vmnics on the physical switch.

If the VMs are using the same vmnic, yet one can ping the gateway and the other cannot ping the gateway, check Troubleshooting virtual machine network connection issues (1003893) for more troubleshooting.

To verify Default Gateway connectivity

Use the ipconfig command to determine and verify your computer's IP address and subnet mask. For more information, see Verifying virtual machine TCP/IP settings (1007875) .

Test pings to the default gateway using the command:

Ping 10.10.10.1

The output looks similar to:

Pinging 10.10.10.1 with 32 bytes of data:
Reply from 10.10.10.1: bytes=32 time=2ms TTL=255
Reply from 10.10.10.1: bytes=32 time<1ms TTL=255 <br>Reply from 10.10.10.1: bytes=32 time<1ms TTL=255 <br>Reply from 10.10.10.1: bytes=32 time<1ms TTL=255<br>
Ping statistics for 10.10.10.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

Note: If you do not know the correct IP address for your default gateway, contact your network administrator.

If there is more then one hop between the host and the gateway, run the Trace Route (tracert) command to see at which hop the ping fails to reply:

tracert 10.10.10.1

The output looks similar to:

Tracing route to 10.10.10.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.10.10.1<br>Trace complete

Related Information

The default gateway is an entry point and an exit point in a virtual machine sub-net, VLAN, or network.

In general, a gateway is a routing device that knows how to pass traffic between different subnets and networks.
Layer 2 and layer 3 switches with VLAN configuration allows IP assignment to each VLAN that will be used as default gateway as for that particular VLAN. A router contains routes for other subnets.

For more information, see:

Troubleshooting VM TCP/IP ping connection issues (1007842)

Troubleshooting virtual machine network connection issues (1003893)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant