VMware Cloud Community
SandyB
Enthusiast
Enthusiast

Change LVE.EnableResignature using PowerCLI

Hi There

I'm running ESXi 4.1 update1 and PowerCLI 4.1.1

I'm trying to change the Advanced Configuration option LVM.EnableResignature using the script below (thanks RvdNieuwendijk)

$VMHosts = Get-VMHost

$VMHosts | Set-VMHostAdvancedConfiguration -Name LVM.EnableResignature -Value 1
$VMHosts | Get-VMHostStorage -RescanAllHBA -RescanAllVMFS
$VMHosts | Set-VMHostAdvancedConfiguration -Name LVM.EnableResignature -Value 0

However when I run it i get the following error:

Set-VMHostAdvancedConfiguration : 25/04/2011 11:35:30    Set-VMHostAdvancedConf
iguration        A specified parameter was not correct.

At C:\scripts\powercli\LVM-signaturing.ps1:2 char:43
+ $VMHosts | Set-VMHostAdvancedConfiguration <<<<  -Name LVM.EnableResignature
-Value 1
    + CategoryInfo          : NotSpecified: (:) [Set-VMHostAdvancedConfigurati
   on], InvalidArgument
    + FullyQualifiedErrorId : Client20_MoServiceImpl_Invoke_ViError,VMware.Vim
   Automation.ViCore.Cmdlets.Commands.Host.SetVMHostAdvancedConfiguration

running the command

Set-VMHostAdvancedConfiguration -Name LVM.EnableResignature

manually lists the current setting on all the hosts but i cant find the correct option to set the -value

any ideas?

S

0 Kudos
4 Replies
RvdNieuwendijk
Leadership
Leadership

Are you running the free version of ESXi? Setting values from PowerCLI is only possible with a licensed version of ESXi.

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
0 Kudos
SandyB
Enthusiast
Enthusiast

Running Enterprise Plus on all servers.

0 Kudos
LucD
Leadership
Leadership

It looks as if you are running ESX(i) 4.x.

In ESX(i) 4.x the handling of snapshot LUNs changed, see KB1011387.

In other words, that advanced configuration parameter doesn't exist on ESX 4.x


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
cblomart
Enthusiast
Enthusiast

Hello,

Effectively with ESX(i) 4.1 the SDK Api doesn't allow to update the resignature parameter.

Neverthless at least for ESX 4.1, the parameter is still available trought ssh and vim-cmd.

The task to allow all snapshot available is then not rendered easy.

Then again the SDK api adds functions to list snapshoted luns and to allow to mount them or the resignature them.

see these functions form the API:

QueryUnresolvedVolumes:

http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.host.DatastoreSystem.htm...

To list unresolved Volumes

ResolveMultipleUnresolvedVmfsVolumes: http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.host.StorageSystem.html#...

To mount or resignature a volume

UnresolvedVmfsResolutionSpec:

http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.host.UnresolvedVmfsResol...

to "resolve" an "unresolved" volume ;-).

The parameter uuidResolution allows to resignature or forcemount... "Resignature" or "forceMount"

I did'nt have time to test it properly yet. When I do i'll be sure to post a message...

Cédric

0 Kudos