Recently upgraded my vcenter to version 5.5 which went without any hickups also update VUM to 5.5.
Uploaded the new vSphere 5.5 image in VUM and after scanning, run ran that upgrade on a test server.
Test server was running v. 5.0. It comes back up but has lost all network connectivity. It has lost the management network - options which show up as greyed out in the System Configuration page (see screenshot).
Looking at the host log, I can see errors like: RefreshVmKernelNic: Unable to getVmKernelNIcs: Sysinfo error on operation returned status: not found.
Both the host file and the config file show the "old" network info (e..g correct IP addresses and hostname)
esxcfg-vswitch -l shows no results
esxcfg-nics -l shows all nics and the link is up.
Server is an IBM Blade H22 and the NICs are Broadcom NetXtreme II BCM5709s (which are on the HAL for 5.5)
Also had a look in the vkernel log and that reports:
etherswitch: esvsigetparamportcfg:424: Management network: not found
any ideas?
Hi,
Can you post the output of this command please :
esxcli software vib list and look for your nics drivers.
Because as you can see, it is not the same drivers available for 5.1 and 5.5
Regards,
Julien.
Ok:
net-bnx2 2.2.3d.v55.2-1vmw.550.0.0.1331820 VMware VMwareCertified 2013-10-01
net-bnx2x 1.72.56.v55.2-1vmw.550.0.0.1331820 VMware VMwareCertified 2013-10-01
These are the Broadcom drivers.
I have fixed it for now applying a "Reset System Configuration". After the reboot the ESX host is contactable but networking has to be setup from scratch. I had to add/name portgroup, adding additional nics. Even thought that works there is a lot of manual fixing to do. Wouldn't like to do that with my Production hosts.
Ok, are you using a VDs?
Regards,
Julien
Nope, standard switches.
Really strange...
is there a problem with a DVs?
Vi have 10 x Dell m610 with bnx2 NIC's, when we add a DVs and migrate the management network to that DVs, a ping to the management interface wont worke - we get only 1/10 ping return, rest just timed out.
VMKERNAL.LOG
bnx2 vmnic0: NIC SerDes Link isDown
Generally this kind of interface comes when your management network is connected to a vSphere Distributed switch.
Can you type this command and post the O/P (if you still has any such setup intact)
# esxcli network vswitch dvs vmware list
This will list out all vDS switches in the ESXi host, if any.
which version(vCenter) do you use?
We run the management Network on a vSphere Distributed switch, we are running 5.5.
I found the problem: If i disable "Network I/O Control" on the Distributed switch, everything goes back to normal.
"Network I/O Control" - does not work with broadcom netxtreme ii in my Dell m610
I have experienced the same behaviour as RuneSvendsen. We have firmware 7.2 on a BCM 5709S sitting inside a Dell M915.
Solution was to turn of Network I/O Control.
Same problem here, BCM 5709S on Dell M610. Updating from ESXi 5.0 to 5.5. Lost connection (ping fails)
Solution: Disable "Network I/O Control" and host come back!
I agree!
\aleph
have a look here
VMware KB: ESXi/ESX host loses network connectivity after adding new NICs or an upgrade
\aleph0
remember to give points if this is correct and set the question as answered
"Network I/O Control" issue described here: VMware KB: ESXi 5.5 Uplink Port using Broadcom bnx2 driver flaps when connected to a vSphere Distrib...
No solution yet, only a workaround.
I tried to update to the newest driver, but still "link down".
Will have to postpone ESXi 5.5 upgrade.