<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: About Powershell toolkit cmdlet timeout value in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436636#M6535</link>
    <description>&lt;P&gt;Since it is implemented in Windows, does it depend on the following values?&lt;/P&gt;&lt;P&gt;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters&lt;BR /&gt;InitialRtt&lt;BR /&gt;TcpMaxConnectRetransmissions&lt;/P&gt;</description>
    <pubDate>Wed, 13 Jul 2022 03:38:55 GMT</pubDate>
    <dc:creator>shuhei</dc:creator>
    <dc:date>2022-07-13T03:38:55Z</dc:date>
    <item>
      <title>About Powershell toolkit cmdlet timeout value</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436635#M6534</link>
      <description>&lt;P&gt;If the Cluster management LIF takes a long time to switch, the cmdlet will error as follows&lt;/P&gt;&lt;P&gt;====================================&lt;/P&gt;&lt;P&gt;PS C:\Users\Administrator&amp;gt; Get-NcAggr&lt;BR /&gt;Get-NcAggr : Connection to XXX.XXX.XXX.XXX on port 443 for protocol HTTPS timed out.&lt;BR /&gt;+ Get-NcAggr&lt;BR /&gt;+ ~~~~~~~~~~&lt;BR /&gt;+ CategoryInfo : InvalidOperation: (XXX.XXX.XXX.XXX:NcController) [Get-NcAggr]、NaConnectionTimeoutException&lt;BR /&gt;+ FullyQualifiedErrorId : ApiException,DataONTAP.C.PowerShell.SDK.Cmdlets.Aggr.GetNcAggr&lt;/P&gt;&lt;P&gt;====================================&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the default timeout value and retry count for this cmdlet?&lt;/P&gt;&lt;P&gt;Looking at the actual machine, it appears to timeout in about 20 seconds.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:58:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436635#M6534</guid>
      <dc:creator>shuhei</dc:creator>
      <dc:date>2025-06-04T09:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: About Powershell toolkit cmdlet timeout value</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436636#M6535</link>
      <description>&lt;P&gt;Since it is implemented in Windows, does it depend on the following values?&lt;/P&gt;&lt;P&gt;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters&lt;BR /&gt;InitialRtt&lt;BR /&gt;TcpMaxConnectRetransmissions&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 03:38:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436636#M6535</guid>
      <dc:creator>shuhei</dc:creator>
      <dc:date>2022-07-13T03:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: About Powershell toolkit cmdlet timeout value</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436640#M6536</link>
      <description>&lt;P&gt;self-resolution (of a problem)&lt;BR /&gt;Measured Timeou time and it was 21 seconds, so it must be the TCP timeout value.&lt;/P&gt;&lt;P&gt;0th 1*3 seconds&lt;BR /&gt;1th 2*3 seconds&lt;BR /&gt;2th 4*3 seconds&lt;BR /&gt;(Wait twice as long as last time when retrying)&lt;/P&gt;&lt;P&gt;3+6+12= 21 seconds&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 07:30:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/About-Powershell-toolkit-cmdlet-timeout-value/m-p/436640#M6536</guid>
      <dc:creator>shuhei</dc:creator>
      <dc:date>2022-07-13T07:30:43Z</dc:date>
    </item>
  </channel>
</rss>

