Discuss NetApp solutions for Microsoft Private Cloud and the Hyper-V platform, including FlexPod Datacenter, OnCommand Plug-in for Microsoft, and ONTAP PowerShell Toolkit.
Discuss NetApp solutions for Microsoft Private Cloud and the Hyper-V platform, including FlexPod Datacenter, OnCommand Plug-in for Microsoft, and ONTAP PowerShell Toolkit.
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
I am trying to set the "snaplock-expiry-time" of a bunch of snapshots using the ONTAP Powershell toolkit... Ontap 9.13.1P2, Powershell Toolkit 9.13.1.2306 I get the snapshot created value with the Get-NcSnapshot, then add 30 days with the $snapexpdate = $snapshot.Created.adddays(30) I verify that the variables have been set correctly. I then use the Set-NcSnapshotSnaplockExpTime with the -ExpiryTime $snapexpdate and the command executes OK. Only thing is that this sets the "expiry-time" of the snapshot and not the "snaplock-expiry-time" which is not the same thing... How do I set the "snaplock-expiry-time" of my snapshots? Of cause I have the correct license (ONTAP One), snaplock compliance clock has been set, and snaplock has been set on the volume... and I am able to set the snaplock-expiry-time from both the commandline and GUI... not apparently not via Powershell... ? Is this a bug? And is there other ways to set this?
... View more
I have a script that we use at several locations to set snapmirror-labels. Runs just fine on all my other systems, but here I'm getting an error on the Get-NCSnapshot command. WARNING: Record doesn't exist I've tried extending my timeout ($global:CurrentNCController.TimeoutMsec=600000), and that helped some, but I'm still getting this error. The system I'm connecting from is on the same subnet, and I can HTTPS or SSH into the system with no delay or issue. Running "volume snapshot show -vserver <vserver name> -volume <volume name>" via SSH runs instantly, no delay...but running "Get-NCSnapshot -vserver <vserver name> -volume <volume name>" takes forever...it will list a couple of snapshots, then give that warning message. I'm running ONTAP 9.12.1P4, with the Powershell module version 9.13.1.2306 on Powershell 5.1, in Windows Server 2019.
... View more
Hi I am trying to find a way to convert a LUN SerialNumber to a Serial-hex using powershell - unfortunately this is not an option off the get-nclun applet. I want to use a CSV column containing Lun Serials as my data source and replace the data with the serial-hex. I initially tried this # Replace 'input.csv' and 'output.csv' with your file paths $inputFile = 'input.csv' $outputFile = 'output.csv' # Read the CSV file $data = Import-Csv $inputFile # Convert the 'ColumnName' column from decimal to hexadecimal $data = $data | ForEach-Object { $_.ColumnName = [Convert]::ToString([int]$_.ColumnName, 16) $_ } # Export the updated data to a new CSV file $data | Export-Csv -Path $outputFile -NoTypeInformation However an error of this type is returned for each line - "Cannot convert value "83J6k$UbONg6" to type "System.Int32". Error: "Input string was not in a correct format." I found this article https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Any-way-to-get-lun-serial-number-in-hex-through-powershell/m-p/28647 However when the concept to CMODE I am getting back an 82 character string as opposed to the 24 character I would expect. I have also tried format-hex and other functions but what mechanism I use I end up with an incorrect result. Additionally I seem to be encountering is the use of '$' in the Lun Serials which confuses powershell. Help!
... View more
