We use a Kick Start installation script to install ESX V3.50 Update 1 on our ESX hosts. The Kick Start script works beautifully. I had a request come in a short while ago to start prepping our ESX hosts to support a migration from Fiber SAN disks to NFS disks. I need to increase the NFS.HeartbeatFrequency and the NFS.HeartbeatMaxFailures settings in Advanced Options. I am using vmware-vim-cmd to make the NFS changes. The problem I am having is that the Kick Start script appears to not like the . (period) that is in my command line.
I am specifying the following commands in the Kick Start script:
vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatFrequency int 12
vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatMaxFailures int 10
When the Kick Start script hits the lines with the . (period) in them it blows up and does not finish the script. The commands are valid and do work. If I manually enter the commands from an SSH session once the ESX host is up they work like a champ. Does anyone have any suggestions?
Give this way a try
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatFrequency int 12"
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatMaxFailures int 10"
just going to need to play untill we find what it likes
Moving this question to the ESX 3.5 thread.
Have you tried using quotes "" in the script?
Steve Beaver
VMware Communities User Moderator
Orlando Area VMware User Group Leader
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
*Virtualization is a journey, not a project.*
I have not. Would I need to put quotes around the whole command like this:
"vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatFrequency int 12"
"vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatMaxFailures int 10"
or just for the value like this?
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatFrequency int 12"
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatMaxFailures int 10"
Give this way a try
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatFrequency int 12"
vmware-vim-cmd hostsvc/advopt/update "NFS.HeartbeatMaxFailures int 10"
just going to need to play untill we find what it likes
Thank's for the input. I'll let you know what I find later this morning..............
OK I figured out the command line syntax to use in the Kick Start script. This worked in my Kick Start script:
/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS"."HeartbeatFrequency int 12
/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS"."HeartbeatMaxFailures int 10
Thanks for the help Steve. As always you are a tremendous help to this forum.........
Hi Guys,
Still can't figure out the correct syntax for NSF setup using kickstart script
/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS"."HeartbeatFrequency int 12/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS"."HeartbeatMaxFailures int 10or even/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatFrequency int 12
/usr/bin/vmware-vim-cmd hostsvc/advopt/update NFS.HeartbeatMaxFailures int 10
Both commands works fine when executed manually via SC but the kickstart script just hungs when it comes to do this task.
Using ESX 3.5 U2
Any help will be appreciated
Thanks in advnace
Vishal