VMware Cloud Community
varun11babu
Contributor
Contributor
Jump to solution

PowerCLI for SCSI Unmap

Hi,

I am getting following error while performing powerCLI, i assume it's still running in the back ground, but would like to know what is causing this error.

The operation has timed out

At <Location>.ps1:21 char:1

+ $esxcli.storage.vmfs.unmap.Invoke($arguments)

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : OperationStopped: (:) [], ViError

    + FullyQualifiedErrorId : VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.

   VimException.ViError

Any inputs will help. The ESXi running in 6.0 Update3 and powercli is 6.5

Out of 85 data stores, it succeeds on 74 and fails on 11 with above error

0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

An unmap can go on for a rather long time.

The default timeout is 300 seconds, you are probably hitting that timeout with those LUNs.

Try disabling the timeout, and see if that makes a difference.

Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Scope Session -Confirm:$false


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

View solution in original post

6 Replies
LucD
Leadership
Leadership
Jump to solution

An unmap can go on for a rather long time.

The default timeout is 300 seconds, you are probably hitting that timeout with those LUNs.

Try disabling the timeout, and see if that makes a difference.

Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Scope Session -Confirm:$false


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

vMarkusK1985
Expert
Expert
Jump to solution

You can also verify VAAI stats in ESXTOP to make sure that you "only" hit the timeout that LucD mentioned.

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
0 Kudos
varun11babu
Contributor
Contributor
Jump to solution

I had defined weboperationtimeoutseconds to 600. But let me set that to -1 and try that..

0 Kudos
varun11babu
Contributor
Contributor
Jump to solution

So far it's working without any errors that i encountered earlier.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Also for the 11 that had errors earlier?


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

0 Kudos
varun11babu
Contributor
Contributor
Jump to solution

Yes, It did fixed all the 11. I think it was the weboperationtimeout parameter causing it..

0 Kudos