Recently, I have performed testing to get our current set of Powershell scripts working with REST API.   I would like to share some of my results, in the spirit of trying to improve the product and ease our transition from ONTAPI to REST API   I tested a number of existing Powershell scripts which my team has developed over the years.  I tested with PSTK v9.13.1.2306 and OnTAP v9.10.1p12   On the positive side, the very basic functionality is there.  You can "drop in" the new PSTK package into Windows, use the same cmdlets with REST and ONTAPI, and they work at a basic level.  PSTK hides the complexity of the underlying calls and provides a consistent set of cmdlets.   On the not-so-great side, many common cmdlets (get-ncvol, get-ncvserver, et-ncsnapshot to name a few) do not return all of the properties with REST which they do with ONTAPI.  Since my scripts require these properties to be returned, I am unable to use the REST API and have to specify -ONTAPI for many of my calls.   There are other issues with REST, among them: REST calls in some cases are much slower than the same call with ONTAPI, The help pages for the cmdlets in many cases have not been fully updated to match the cmdlet (example the -ONTAPI option is not even mentioned), Some cmdlets behave differently with REST than with ONTAPI.  I have seen the REST flavor return a Warning message that the ONTAPI flavor does not.  While this is not a functional issue, it requires me to change my code to suppress or handle the warning message. I would be happy to share specific cmdlets which I have tested and which are inconsistent between REST and ONTAPI   I call on the PSTK maintainers to continue to improve and evolve the toolkit to provide consistent functionality, behavior, and performance between REST and ONTAPI flavors of their cmdlets.   I would encourage other users to post their replies here, regarding their experience in migrating to REST with PSTK. ... View more

Hi everyone, I need help here… but first let me explain;   Environment:  ONTAP HA-Cluster  hosted in Azure Cloud as Cloud Volumes ONTAP (v 9.13.1)   Using Powershell where I need to define a ‘probe-port’ while creating an  DataLIF because its required using CVO in Azure with his Loadbalancer. Question: Using New-NcNetInterface this parameter ‘probe-port’ cannot be found/ is missing. How can I add a probe-port using Powershell on a new network interface?   Many thanks!         ... View more

Hello Community,   We currently try to update to PSTK  9.12.1.2302. But when you use  Get-NcSnapshot -volume $volume    You get an exception: Object reference not set to an instance of an object.   Same when you use New-NcSnapshot command.   Did anyone here get a solution or is PSTK only usable with "-zapi" legacy switch?   Regards Dennis ... View more

Hello together,   we have a problem with the PowerShell Kit and Session IDs for CIFS. We are running PowerShell Kit 9.13.1.2306 and OnTAP Version 9.12.1P3   We have a two node cluster and one SVM running on Node A have the problem when the corresponding LIF is also on Node A.   The error: When we try to run the cmdlet "Get-NcCifsSessionFile -Vserver xxx" we encounter an error, that the Session ID is out of range from INT64.   Workaround: When we move the LIF of the SVM to Node B, there is no error anymore. Back to Node A, the Session ID is again greater than INT64.   On the OnTAP CLI the session ID can be checked with:  vserver cifs session show     Does anyone knows about that behaviour or has a solution?  Maybe it is possible to decrease the range for CIFS session ids? ... View more

Hello,   I want to create snapshot policies through a script. This works on physical filers but for some reason the same code does not work on our virtual netapp ONTAP filers.   I get the following error code when executing : New-NcSnapshotPolicy -Name $policyName -Schedule $scheduleName -Count $retentionCount -SnapmirrorLabel $snapshotmirrorlabel -Comment $comment -Enabled $true   Error: New-NcSnapshotPolicy : Svm parameter neither specified nor set At \\nur0fs02\data\IT\Scripts\Netapp-Snapshot-Script.ps1:117 char:1 + New-NcSnapshotPolicy -Name $policyName -Schedule $scheduleName -Count ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-NcSnapshotPolicy], ArgumentException + FullyQualifiedErrorId : Svm is empty,DataONTAP.C.PowerShell.SDK.Cmdlets.Snapshot.NewNcSnapshotPolicy       Not sure if this is a bug on the virtual ONTAP ?  I always connect to the cluster and not to an SVM. The Snapshot Policy I want to create should have a cluster scope.   Thank you ... View more