Hi All,
Installing 3.5 U4 from CDROM via kickstart. I specify my .ks file to be retrieved via HTTP, everything works great except for a few things:
When these commands run on first boot of ESX via /etc/rc.d/rc.local I get "Failed to connect: 514 Error connecting to hostd-vmdb service instance":
/usr/bin/vmware-vim-cmd /hostsvc/net/vswitch_setnumports vSwitch0 128
/usr/bin/vmware-vim-cmd hostsvc/vmotion/vnic_set vmk0
I've tried adding sleeps in various places, I've tried adding these commands at the end of the script with no luck.
These commands run perfectly fine under /bin/sh on next boot (when the build is complete). I've seen some posts stating that these commands are not working properly after 3.5 U2.
Any comments? As of now, I'm editing esx.conf fix the number of ports, have not found where to do this with enabling vMotion yet...
Ben
Hi Ben,
I'm messing with the vmware-vim-cmd currently, i find specifying the /usr/sbin/ path sorts some issues but can you shed a little more light on what you're working with?
What hardware?
What agents if any are you installing into the SC?
Cheers,
JW
I always have the post configs run upon the next reboot, since not all the modules are necessary loaded such as the VMkernel which can cause some issues when using vimsh
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
I'm working with /usr/bin/vmware-vim-cmd on HP Proliant G6 blades. At the time I'm running the latest HP agents for ESX.
Ben
William,
So you are running them in the 2nd or 3rd boot?
1st boot - Anaconda install
2nd boot - Booting ESX for the first time, using rc.local to run commands
3rd boot - Ready for production
I'm running all my commands in the 2nd boot, the VMKernel is loaded on the 2nd boot.
Ben
2nd boot and the systems are ESX 3.5u3 ... we haven't gone to U4, but I dont't think any should have changed drastically to cause this issue. Generally these type of errors may indicate an issue trying to communicate to the host services which vimsh relies on .
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
thx, I'll try some more "sleeps" and report back....
I'll check our kickstart script and provide the snippet later this evening.
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Hi, did you get anywhere with this, I have the same issue.