VMware Cloud Community
Ryan_1
Contributor
Contributor

ESX not in network after upgrading to 3.5

Hi Guyz.

am having a weird issue that ESX server, that i upgraded from 3.0.1 to 3.5 is not pingable from LAN; but is pinging the other ESX servers in the same cluster.

there were 3 ESX hosts in a cluster, all of 3.0.1. I upgraded the other two servers, which came back fine in network. But the third server after upgrading, is not reachable.

I deleted the vswif & vswitch and recreated them, rebooted the server; still no luck. the NIC is in 100FULL. the surprising thing is that it can ping the other hosts in the cluster & i can ping this server from other hosts in the same cluster. I cant take putty of the server & neither can connect in VC.

mgmt-vmware service is running; but vmware-vpxa service is returning as an unrecognized service.

Reply
0 Kudos
3 Replies
kjb007
Immortal
Immortal

Check your gateway, and make sure it is pingable. Sounds like you're able to get to your switch (layer 2), if you can ping the other ESX hosts. If you can't ping your gateway, or connect from other subnets, then you're having trouble with the router (layer 3).

Check to make sure you're going to the same router as the other ESX hosts, and that router is not disabling you somehow. Make sure your gateway is correct and it is pingable and available by your ESX host.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
Ryan_1
Contributor
Contributor

thank you for your quick reply.

am able to ping the gateway and is the same settings as the other servers in the cluster.

Reply
0 Kudos
Ryan_1
Contributor
Contributor

i changed the default gateway in /etc/sysconfig/network

it works now.

thanks your reply though.

Reply
0 Kudos