There is a field in the volume efficiencies called "auto-state" that does not seem to be accessible using standard PowerShell commands (Get-NcSis or Get-NcVolume). From the CLI, it is only visable in diag mode. Does anyone know any way to pull this information using PowerShell, other than using Invoke-NcSSH? This is the command to view it in the CLI (while in diag): vol efficiency show -volume vol1 -fields auto-state I'm asking because we have workflows in WFA that are failing when we try to set the efficiencies on volumes that have been "deprioritized".
... View more
I recently update our NetApp PSTK from 9.8 to 9.14.1.2401, and since the queries in my scripts are failing (see output below from 9.8 and 9.14). OnTap version is 9.12.1P10. Get-NcNetDeviceDiscovery is the only command I use the query with, so I don't know if it's all commands or just that one. Does anyone know why I'm getting this error and how I can fix it? Query with PSTK 9.8: PS C:\> Get-NcNetDeviceDiscovery -Query @{Node="cluster01-01";Port="e0M"}
DiscoveredDevice Node Interface Port Platform Capabilities
---------------- ---- --------- ---- -------- ------------
switchname... cluster01-01 Gi1/0/3 e0M {router, trans_br... Query with PSTK 9.14.1.2401: PS C:\> Get-NcNetDeviceDiscovery -Query @{Node="cluster02-01";Port="e0M"}
Get-NcNetDeviceDiscovery : [400]: Field "return_unmatched_nested_array_objects" was specified twice (to "false" and "false").
At line:1 char:1
+ Get-NcNetDeviceDiscovery -Query @{Node=" cluster02-01";Port="e0M"}
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Get-NcNetDeviceDiscovery], Exception
+ FullyQualifiedErrorId : 400,DataONTAP.C.PowerShell.SDK.Cmdlets.Net.GetNcNetDeviceDiscovery It does work if I add -ONTAPI to the end of the command, but, from my understanding, that means it's reverting to ZAPI, and so will not work in future versions of OnTap, correct?
... View more
Our current implementation for archiving files in NetApp ONTAP consists of two steps: Copy the physical file via SFTP. Set the retention via NetApp SDK (Java bindings). We want to change our implementation and use the REST API for setting the retention with the same two-step approach: Copy the physical file via SFTP. Set the retention via NetApp REST API. In this case setting the retention does not work and we get this error in the response: { "error": { "message": "File is not retained by SnapLock.", "code": "13762576" } } After some try&error we noticed that for files which already had a retention set via the NetApp SDK (old way) we could use the REST API (new way) to set the new retention. So the error seems to be limited to new files for which there was not retention set via the NetApp SDK. In both cases we use exactly the same environment (NetApp 9.12). Does someone have any hints as to why this error occurs? Is this approach not supported with the REST API?
... View more
While working with newly provisioned C-series systems, our existing REST API scripts break when they call some REST APIS like things related to TSSE that apparently do not apply to AFF systems. I would like to know what specific REST APIs work for AFF / C-series systems. Can anyone recommend a place or document that we can refer to, and know which APIS apply only to AFF and which apply only to FAS models? Also, if there are ASA or MetroCluster specific APIs, that would be good to know too. While reviewing the available resources, we noted that there is a "Usage" in the API docs that describe which interfaces an API will work on (SVM LIF?) If there's no doc for this, could we request that the APIs themselves add information about what types of systems the API is expected to work for (AFF, ASA, FAS, MC, ETC.) 🙂
... View more
Hello, I'm trying to display file permissions using rest-api. I have an old vserver and it does not work when SECD cannot resolve SID. It's fine using ZAPI. It displays SID when it cannot resolve to windows name. GET https://ip/api/protocols/file-security/permissions/c26b5fac-1135-11ea-a956-00a098d1acc2/%2FVOLUME%2FDIR%2FSUBDIR User-Agent: python-requests/2.28.1 Accept-Encoding: gzip, deflate Accept: */* Connection: keep-alive X-Dot-Client-App: netapp-ontap-python-9.11.1.0 Authorization: Basic aW52ZW50YWlyZTpZb3VwbGFib3VtMzA= None ----------------------------- DEBUG:charset_normalizer:Encoding detection: ascii is most likely the one. DEBUG:netapp_ontap.host_connection: -----------RESPONSE----------- 404 Not Found Date: Thu, 02 Feb 2023 10:48:14 GMT Server: libzapid-httpd X-Content-Type-Options: nosniff Cache-Control: no-cache,no-store,must-revalidate Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; frame-ancestors: 'self' Content-Length: 144 Content-Type: application/hal+json Keep-Alive: timeout=5, max=99 Connection: Keep-Alive { "error": { "message": "Failed to convert SID to a Windows name. Reason: \"SecD Error: object not found\". ", "code": "4849677" } } ------------------------------ Traceback (most recent call last): File "/home/XXXXXX/projects/reporting_acls/test.py", line 14, in <module> resource.get() File "/srv/xxxxx/venv/netapp/lib/python3.9/site-packages/netapp_ontap/resources/file_directory_security.py", line 1048, in get return super()._get(**kwargs) File "/srv/xxxxx/venv/netapp/lib/python3.9/site-packages/netapp_ontap/utils.py", line 55, in wrapper return on_api_fail(erro) File "/srv/xxxxx/venv/netapp/lib/python3.9/site-packages/netapp_ontap/utils.py", line 78, in on_api_fail raise NetAppRestError(cause=erro) from None netapp_ontap.error.NetAppRestError: Caused by HTTPError('404 Client Error: Not Found for url: https://IP:443/api/protocols/file-security/permissions/c26b5fac-1135-11ea-a956-00a098d1acc2/%2FVOLUME%2FDIR%2FSUBDIR'): Failed to convert SID to a Windows name. Reason: "SecD Error: object not found".
... View more