sbn
Contributor
Contributor

6.5.0 Update 2 & default gateway

Recently a server's SD card failed, so ESXi had to be freshly installed on a new SD card. At the time I downloaded 6.5 Update 2, installed and brought the VMs back online. All was good until I see I am unable to access the server from another subnet. I have 4 other servers running ESXi, never experienced this. Now the VMKernel, VMnics, etc.. are all connected to the physical server ports connected to VLAN 1 (i.e. no vlan configured). Basically configuration wise this is almost the same as the other 4 ESX servers. The one difference is that before the crash this was configured to use a different VLAN that used a different firewall. This time around I configured ESX with different IP & subnet, and changed the VLAN on the switch to the VLAN 1 primary as the other servers are using.

The interesting thing is this, from within ESX I can ping every device on the same subnet except 1 address. That address is of course the gateway. First, I know this is a long shot, but was there anything added into update 2 that limited or turned off routing/access to remote subnets? Second, anyone else experienced similar problem? I know this is a long shot, but I am at a loss for ideas on the next step.

0 Kudos
1 Reply
rcporto
Leadership
Leadership

You mean from ESXi management you can ping all devices in the network, including devices in different subnet, except the default gateway? If the default gateway is a firewall, can you confirm if ICMP is allowed to the ESXi management IP?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos