VMware Cloud Community
Mark_Higbie
Contributor
Contributor
Jump to solution

VM Cannot ping ESX host

I have a newly created VM Cluster with 3 ESX hosts. All of the ESX hosts can ping each other and other windows servers within the same vlan. I created a new VM on the first ESX host and it cannot ping out to the default GW or it's own ESX host. When you try and ping from the ESX host to the VM you get "destination host unreachable" going in the opposite direction the request times out. Here is some network configuration info that I pulled off of the ESX host:

cat /etc/sysconfig/network

NETWORKING=yes

GATEWAYDEV=vswif0

HOSTNAME=VAEFSXVMD01.efast2dev.local

GATEWAY=10.131.52.1

cat /etc/sysconfig/network-scripts/ifcfg-vswif0

  1. Broadcom Corporation|Broadcom NetXtreme II BCM5708 1000Base-T

DEVICE=vswif0

BOOTPROTO=static

IPADDR=10.131.52.22

NETMASK=255.255.255.0

ONBOOT=yes

PORTGROUP="Service Console"

MACADDR=00:50:56:44:94:dd

esxcfg-route -l

VMkernel Routes:

Network Netmask Gateway

default 0.0.0.0 Local Subnet

esxcfg-vswif -l

Name Port Group IP Address Netmask Broadcast Enabled DHCP

vswif0 Service Console 10.131.52.22 255.255.255.0 10.131.52.255 true false

esxcfg-vswitch -l

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 64 5 64 1500 vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

Virtual Machine Network720 1 vmnic0

Service Console 0 1 vmnic0

If anyone has any ideas I would greatly appreciate it!

Thanks,

Mark

0 Kudos
1 Solution

Accepted Solutions
weinstein5
Immortal
Immortal
Jump to solution

No problem - happy to help - no for shameless self promotion do not forget to award points -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

View solution in original post

0 Kudos
6 Replies
weinstein5
Immortal
Immortal
Jump to solution

Is the VM part of the same vlan? if not can it route to the vlan? What is the IP configuration for the VM?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
Mark_Higbie
Contributor
Contributor
Jump to solution

Yes, the VM is in the same VLAN and it's network config is:

IP: 10.131.52.25

SM: 255.255.255.0

DGW: 10.131.52.1

0 Kudos
weinstein5
Immortal
Immortal
Jump to solution

Looking at what you posted in your original post - looks like the VM traffic will be tagged with vlan 720 while the service console traffic will not be tagged - see if removing the vlan vm port group or adding a vlan tag to the service console reolves the problem -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Mark_Higbie
Contributor
Contributor
Jump to solution

Do you effectively turn vlan tagging off by removing the virtual machine network and then just adding it back but without specifing a vlan id?

0 Kudos
Mark_Higbie
Contributor
Contributor
Jump to solution

Vlan tagging was it. Removing the vlan id from the virtual machine network resolved it! Thanks a lot Weinstein5!!!

0 Kudos
weinstein5
Immortal
Immortal
Jump to solution

No problem - happy to help - no for shameless self promotion do not forget to award points -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos