I've upgraded our host from ESXi 5 to ESXi 5.1,
After upgrading, we can connect to our host by vSphere client but we can't ping that,
Please help me.
is your host connected to a vcenter? is the vcenter also 5.1?
your vcenter has to be 5.1 before your esxi hsot is
if you can access the console go to troubleshooting options and do a test of the management network.
if you need to revert hold shift+R when booting
We have exactly the same scenario:
* Vcenter server was upgraded to 5.1 (from 5.0)
* Then I upgraded the first host from ESXi 5 to ESXi 5.1
* Everything works 100% with the new host joint to the cluster (DRS, vmotion, all the VMs, vSphere Client, etc)
* The only thing that is different is that I cannot ping the management IP addres of the upgraded host
* I also cannot ping the vmotion IP address (separate dedicated pnic)
* I have also disabled the firewall on the upgraded ESXi host:
~ # esxcli network firewall set --enabled FALSE
~ # esxcli network firewall unload
~ # esxcli network firewall get
Default Action: PASS
* With the firewall disabled the pings still does not work ...
Johan du Buson
Nope, no replies. I have found that one host I re-installed from CD and it is working 100% but all the hosts that were upgraded via VUM is blocking the pings on Managment and vMotion interfaces.
Johan du Buson - Technical Specialist
Gijima - www.gijima.com
(c) 0823200912 - (t) 0132473076 - (f) 0132472622
From: Auzman <firstname.lastname@example.org>
Date: 2012/11/13 04:25 PM
sounds silly but
disconnect all nics and try the management network in each Physical nic one at a time.
has been known for esx to reorder nics on an upgrade.
although it hasnt happened to me since 4.0
I checked my management IP and VLAN ID,
My first management IP address was changed cuase of change VLAN ID after upgrade,
I couldn't ping it because my host is registered with first IP address,
Please check your network configurations even basic configurations.
Thanks all for your help.
I had the same issue and found that the GW on my Management network was set to the Gateway of a different VLAN by the system. I changed it to the correct VLAN GW and it worked.
When I changed the Gateway for the Management network on vSwitch0 it also change the GW for my VMkernal ports on vSwitch2.
So it appears that I can only have 1 GW set at a time.
I am having the same issues...IP's GW, are all the same as previous config, but it fails when testing the managment network.
Tried switching the vnics. still no luck...completely clueless.
It should have been a simple upgrade. Only one host..luckily I had no VMS...but I would like to get this host back on line..
think I'm gonna revert back 4.1 and reinstall just to back track.
Old thread. But i had this issue after doing an update to U1 of 5.1.
Turned out my vmnics were renumbered, we have 2x 10GBe and 2x 1GBe. It swapped the numbers around. a quick edit of the /etc/esx.conf and properly renumbering the nics and a reboot fixed our issue.
just did a vi /etc/esx.conf and changed the number on each corresponding nic. Oddly enough this only happened on one server out of 10 identical hosts.
I just had this same issue in one of our clusters when I upgraded from 5.0 to 5.1.U1. After working for several hours, we realized cause of the issue to be following:
It seems that in locking down ICMP to only the management interface, ESXi may get confused after an upgrade as to which interface this actually is. I would recommend taking a close look at the management network vSwitch before an upgrade to 5.1 to avoid any related issues.
Trying to install vcenter Log Insight and integrate it with vSphere forced me to take another look at the issue of not being able to ping host from vCenter. After a bit of research, I honed in on the idea it was DNS related and started to look at the fact that on some hosts, I was not being able to ping esxi host after upgrade
For my resolution, I put the host into maintenance mode and then edited the network configuration (managed virtual adapters in my distributed switch) of each host that exhibited this behavior. I deleted vmk's that were configured for 2nd service console and FT Logging. I was able to ping my host again from vCenter. When I added a 2nd service console port for redundancy, and I lost the ability to ping again.