Manage Learn to apply best practices and optimize your operations.

PowersHell – enabling FT logging

Describes the formula for enabling FT logging.

I had a post/comment on my blog this week about enabling FT logging on VMKernel Port. It wasn’t immediately apparent...

how to do this, so I asked Carter Shanklin who is Product Manager of PowerCLI for a “how to". True to form, he has come up trumps. This is what he’s sent me. I have not had a chance to test it just yet. But I will post it here for the people who asked me.

# Enable or disable FT logging.
$esxHost = ""
$vmKernel = "vmk0" # You can get these out of Get-VMHostNetwork
$enable = $true
$hView = Get-VMHost $esxHost | Get-View -Property configManager
$nicManager = Get-View $hView.configManager.virtualNicManager
if ($enable -eq $true) {
	$nicManager.SelectVnicForNicType("faultToleranceLogging", $vmKernel)
} else {
	$nicManager.DeselectVnicForNicType("faultToleranceLogging", $vmKernel)


Anyway, the original poster of that comment, David Gontie got back in touch with me with a way of doing the same thing from the kickstart install %post script. Personally, I’m weening off my beloved COS in favor of Powershell. But here’s David’s full blog post on how its done:

vmware-vim-cmd hostsvc/advopt/update FT.Vmknic string vmk1

Where vmk1 is the second vmkernel port, I found you had to restart the management services to make sure the vSphere Client reflected the changes (service mgmt-vmware restart)

This was last published in September 2009

Dig Deeper on VMware ESX and ESXi administrative tips

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.