viscid zenith
I have upgraded my PTSK to 9.16.1 and when I run the get-ncvolmove cmdlet it does not return values for many properties ones that I typically use are
replicationthroughput
phase
state
It just returns blank values for these, we use this to get lists of moving volumes before attempting to move others when migrating to new aggregates in a cluster so that we can keep a max running number of moves.
fervent grail
try passing -zapicall:$true ... many cmdlets do not return the full data via REST
especially annoying are the snapmirror cmdlets, those return completely different data in the same fields depending on if you call them with -zapicall or without
viscid zenith
Thats really bad since we have tons of functions and I am now unsure what they will do
but I will try it out
fervent grail
yeah it's a terrible state and I doubt it will get fixed any time soon. For anything more than simple day2 automation you absolutely need Zapi still
viscid zenith
looks like I need to go back to PTSK prior to 9.10 since thats when some other cmdlets got broken
fervent grail
are you using the DataONTAP module or the NetApp.ONTAP one?
viscid zenith
at least in my case for this one it just didn't run any moves because when it went to check how many were running with get-ncvolmove | where-object {$_.state -notlike "done" it just returned a huge list since state is no longer returned but that could be bad if it were something else
Netapp.ONTAP
fervent grail
at least in my case for this one it just didn't run any moves because when it we...
yeah in that case you either need to add -and $_.state -notlike "" or something similar (to get rid of "empty" state fields), or just use -zapicall:$true which only returns actually moving volumes
viscid zenith
But I need to know how many are running so the only way woudl be -zapicall:$true
fervent grail
have you tried Get-NCVol |? { $_.VolumeStateAttributes.IsMoving } ? Sometimes there are different ways to get the same information out of the system 🙂
viscid zenith
same issue I would still have to modify my existing functions , adding -zapicall:$true is easier than changing the cmdlet.
but I do believe that would work
I guess the real issue here is that I will have to go and modify/check a lot of functions before I can allow users to use them
Would be great if the toolkit could be set to use -zapicall:$true by default or some way to do that easily like in ansible
minor shore
I’ve been testing my group’s module that wraps the VMware PowerCLI module and NetApp.ONTAP 9.16 module. I’ve had to make a few hundred adjustments. Many need -ZapiCall:$True, some I needed to update the $Path passed to Get-|Read-|Write-NcFile and Get-NcDirectory because something changed there…