Hello,
I have upgraded my ESXi 4.1 hosts and my VCenter Server 4.1 (Windows 2008 64 BIT) without any Problems.
After installing vMA as VM, I want used the vMA to create a vSwitch with two vmkernel-ports for iscsi multipathing
The following commands without any problems.
esxcfg-vswitch -a vSwitch2
esxcfg-vswitch -m 9000 vSwitch2
esxcfg-vswitch -A iscsi1 vSwitch2
esxcfg-vswitch -A iscsi2 vSwitch2
But the esxi host crash after enter this line:
esxcfg-vmknic -a -i 192.168.70.200 -n 255.255.255.0 -m 9000 iscsi1
Now after this line the ESX crash, no response in vcenter server, no ping response.
After restart of the ESX the same problem, no network, no answer.
The procedure i used several times on different esxi-host without any problem.
What should i do, new install of esx-host. Where is the problem ? Hardware ?
are you able to use DCUI?
ckeck /var/log/vmkernel.log and syslog
I would suggest checking the logs. What about the used hardware? Is it all on the HCL?
Thank for the quick answer, yes i can use the DCUI
the esxi is booting normaly into the DCUI screen, login with username and password,
it looks fine. A test oft the management network failed, no ip-adress is responding (gateway or dns).
i will check the vmkernel.log and the syslog files looking for any errors.
thanks
the hardware is on the HCL but i will check it again.
the same procedure on this host under esx 4.1 no problem (this was a test last year and the vswitch was deleted,
now after upgrading i do the same procedure to use the new ISCSI-SAN with multipathing)
Are you using any sort of 3rd party software which might be causing the problem? Since u did an upgrade it might be not working anymore with the new ESXi version.
There is no 3rd party software, the two esx hosts are upgraded and the vma is new installed from ovf
template. the esx hosts are added with vifp addserver
Try gathering the logs through SSH and attach them here or if you can open up a case with VMware itself if you don't want to post them here
It strange.
Is the server crashed fully? something like PSOD or kernel panic.
Check it in iLO.
If you can access the host from iLO, i feel we can avoid re-installation.
If can see the DCUI of ESXi through iLO then enable Local Tech support mode and login.
1. once you are connected to the Local Tech support mode lis out the vmknics.
esxcfg-vmknic -l
2. note down the Interface name of newly created vmknic if it present.
3. Delete it using esxcfg-vmknic -d <vmknic name>
4. Try connecting the host from vCenter Server.
note: Before we enable jumbo frame at host level it should be configured at physical switch level.
Have you tried to define the vSwitches from the vSphere client?
In vSphere 5 you can define also the MTU both on vSwitch and vmkernel interface.
If from GUI it work, you can look why does not work from vMA (remember to deploy the latest version).