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?
