Same problem here, guys.
Get-NaAggr always works fine.
Get-NaVol is the problematic cmdlet.
Running Data ONTAP 8.2.2P1 7-Mode on FAS6220's.
With PowerShell ToolKit 3.1, the error was:
"Get-NaVol : Connection to xxxxxxxx on port 443 for protocol HTTPS timed out"
With PowerShell ToolKit 3.2, the error is:
"Get-NaVol : Object reference not set to an instance of an object."
Tried setting
$global:CurrentNaController.TimeoutMsec = 120000
$global:CurrentNaController.RetryCount = 5
... no help.
The failure occurs with both RPC and HTTPS protocols.
When the failure occurs, systat indicates filer CPU utilization around 30 to 50%.
In the end, I had no choice but to work around the problem by modifying the schedule of the task to run at the time of the day where Get-NaVol does not seem to fail. This is/was not ideal, but as NetApp has not been able to provide a root-cause or fix/resolution, I had no choice.
Hoping NetApp fixes this in the next release of the DataONTAP PowerShell ToolKit.
- Tony