PS /> Test-v3Prerequisites [?] You are using a PowerShell version 7.3.9. [√] PSGallery is available. [√] PSGallery is Trusted. [√] Repositories are available and configured correctly. [√] VMware.PowerCLI 13.2.1.22851661 [√] NetApp.ONTAP 9.14.1.2401 ---------------------------------------------------------------------------------- [√] All the required Modules are installed in the required version ---------------------------------------------------------------------------------- passed prerequisites check PS /> PS /> Get-Command -Syntax New-NcVolClone New-NcVolClone [-CloneVolume] <string> [-ParentVolume] <string> [[-ParentSnapshot] <string>] [-SpaceReserve <string>] [-JunctionPath <string>] [-JunctionActive <bool>] [-VolumeType <string>] [-QosPolicyGroup <string>] [-CachingPolicy <string>] [-Option <string[]>] [-Comment <string>] [-Vserver <string>] [-ParentVserver <string>] [-VserverDrProtection <string>] [-Uid <long>] [-Gid <long>] [-MatchParentStorageTier <bool>] [-Style <string>] [-SnaplockType <string>] [-VserverContext <string>] [-Controller <NcController[]>] [-ZapiCall] [-WhatIf] [-Confirm] [-ZapiRetryCount <int>] [<CommonParameters>] PS /> $global:currentNcController Name Address Vserver Version ---- ------- ------- ------- <REDACTED> <REDACTED> vserver NetApp Release 9.13.1P6: Tue Dec 05 16:06:25 UTC 2023 PS /> $global:currentNcController.Vserver vserver PS /> $Params = @{ >> ParentSnapshot = $snapshotName >> CloneVolume = $vAppName >> VserverDrProtection = "unprotected" <<<<<<<<<< >> JunctionPath = $junctionPath >> JunctionActive = $True >> Vserver = $global:currentNcController.Vserver >> } PS /> $sourceVol | New-NcVolClone @Params New-NcVolClone: [failure]: Cannot protect volume "vserver:VolClone" because the parent volume is unprotected in the Vserver DR relationship. If volume requires Vserver DR protection, protect the parent volume first using the "volume modify -vserver-dr-protection protected" command. Otherwise, to create a clone without protection, specify the "-vserver-dr-protection unprotected" parameter. PS />   PS /> $Params = @{ >> ParentSnapshot = $snapshotName >> CloneVolume = $vAppName >> VserverDrProtection = "unprotected" >> JunctionPath = $junctionPath >> JunctionActive = $True >> Vserver = $global:currentNcController.Vserver >> "vserver-dr-protection" = "unprotected" >> } PS /> PS /> $sourceVol | New-NcVolClone @Params New-NcVolClone: A parameter cannot be found that matches parameter name 'vserver-dr-protection'. PS />   Any thoughts on this? ... View more

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

The ONTAP CLI, qos workload show , gives the volume wid number. any powershell command can give me this wid ? ... View more

Hi, Script was running fine on previous PSTK version so no firewall issues. Today I tested a simple line it can't connect to the cluster in version 9.10.1. PS C:\Users\sanamn\Scripts> Connect-NcController  <Filer FQDN> Connect-NcController : Invalid URI: The hostname could not be parsed. At line:1 char:1 + Connect-NcController <Filer FQDN> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidResult: (Filer FQDN:NcController) [Connect-NcController], UriFormatException + FullyQualifiedErrorId : HttpConnectionFailed,DataONTAP.C.PowerShell.SDK.ConnectNcController   My OnTap version is 9.9.1p6. Windows 10 enterprise running Powershell version 5.1   Thanks ... View more