• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1999
  • Last Modified:

ESXi network troubleshooting

I'm having networking issues with my new ESXi 5.1 host. I'm pretty sure it's a setting that I missed. I'm getting no ping replies when I'm trying to ping the management or the vMotion vmnic. However, vCenter can communicate with that host just fine, and the other vSwitch handling NFS traffic, I can ping that VMkernel just fine.

Since I can configure only a single gateway address for an ESXi host, I set it to
As mentioned I can ping the NFS (VLAN 1002) VMkernel (vSwitch1) just fine whose IP is

However, I cannot ping the vMotion (VLAN 1001) VMkernel with IP: I also cannot ping the management (VLAN 1000) VMkernel with IP:

However, if I change the default gateway to let's say, then all of a sudden I can ping the management VMkernel, but no longer the NFS VMkernel.

On all my other ESXi hosts, I can ping all VMkernels on that host, even though all of them have their default gateways setup as

What do I need to do to be able to ping all of the VMkernels on this new ESXi 5.1 host?
  • 5
  • 3
2 Solutions
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you are carrying out these tests on the console of the ESXi 5.1 host?

Can you upload a screenshot of your networking?
pzozulkaAuthor Commented:
I tried pinging from the console using vmkping -I vmk# ip_addr as well as trying to ping the various VMkernel IPs from my workstation.
pzozulkaAuthor Commented:
Any thoughts on this?

From my workstation I can ping all my other ESXi hosts, and each one of their individual vmkernel IPs. On this new host, I can only ping a single vmkernel IP (the one that's on the same subnet as the default gateway).

I don't think it has anything to do with the phsycal network because the VMkernels I'm trying to ping -- are on the same subnet as the VMkernels on the other ESXi hosts. Since I can reach those VMkernels, I should be able to reach this one as well.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If when pinging the management network or vMotion interface you get no reply, that's likely because the gateway defined for Management Network or vMotion Interface is incorrect.

I'm assuming that vCenter Server is on the same network as Management Network/vMotion Interface network, and hence that's why no communication issues between the two, because traffic does not need to route to the ESXi host.

We would normally configure the Default Gateway for the ESXi host to be the Default Gateway on the Management Network.

what is also odd, is you have different VLANs, but carrying the same IP Address range?

1001, 1000, 1002 -, 10.0.128,4,

normally different IP Addresses are assigned to different VLANs.

If this is working for you on different hosts, I would compare configurations of ESXi networking, and also physical switch port configurations.
pzozulkaAuthor Commented:
vSwitch 0 is setup for vMotion VMkernel and Management VMkernel. vSwitch 1 is setup for NFS VMkernel. The default gateway is defined on the same subnet as NFS VMkernel.

Our VLANs are:

As you can see they are not carrying the same IP Address range.

Having said that, let me ask you this question.

If you have a VMware environement that you can test, are you able to ping all of your VMkernels from your workstation? And is your workstation on the same or different subnet?

I'm wondering if maybe this is the default behavior, that you're not suppose to be able to ping all of your VMkernels. Because VMware does recommend to separate Management, vMotion, and Storage traffic.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No we cannot ping our vmkernel port groups because they exist on a secure storage network.

Workstations on completely network range.

Storage network 10.10.x.x private
Workstations 150.xxx.xxx.xxx

That is correct to isolate networkd
pzozulkaAuthor Commented:
Change to ICMP ping response behavior in ESXi 5.1. Found KB article causing issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now