NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Microsoft Virtualization Discussions

About Powershell toolkit cmdlet timeout value

shuhei
2,900 Views

If the Cluster management LIF takes a long time to switch, the cmdlet will error as follows

====================================

PS C:\Users\Administrator> Get-NcAggr
Get-NcAggr : Connection to XXX.XXX.XXX.XXX on port 443 for protocol HTTPS timed out.
+ Get-NcAggr
+ ~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (XXX.XXX.XXX.XXX:NcController) [Get-NcAggr]、NaConnectionTimeoutException
+ FullyQualifiedErrorId : ApiException,DataONTAP.C.PowerShell.SDK.Cmdlets.Aggr.GetNcAggr

====================================

 

What is the default timeout value and retry count for this cmdlet?

Looking at the actual machine, it appears to timeout in about 20 seconds.

1 ACCEPTED SOLUTION

shuhei
2,867 Views

self-resolution (of a problem)
Measured Timeou time and it was 21 seconds, so it must be the TCP timeout value.

0th 1*3 seconds
1th 2*3 seconds
2th 4*3 seconds
(Wait twice as long as last time when retrying)

3+6+12= 21 seconds

View solution in original post

2 REPLIES 2

shuhei
2,894 Views

Since it is implemented in Windows, does it depend on the following values?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
InitialRtt
TcpMaxConnectRetransmissions

shuhei
2,868 Views

self-resolution (of a problem)
Measured Timeou time and it was 21 seconds, so it must be the TCP timeout value.

0th 1*3 seconds
1th 2*3 seconds
2th 4*3 seconds
(Wait twice as long as last time when retrying)

3+6+12= 21 seconds

Public