During storage upgrades using NetApp Hybrid Cloud Control, you might encounter the following scenarios: The session times out after two hours into the upgrade, and you are logged out of the NetApp Hyb...During storage upgrades using NetApp Hybrid Cloud Control, you might encounter the following scenarios: The session times out after two hours into the upgrade, and you are logged out of the NetApp Hybrid Cloud Control UI You are logged out of NetApp Hybrid Cloud Control towards the end of the upgrade, and cannot log back in During a storage upgrade, users might see an error page if NetApp Hybrid Cloud Control is refreshed in the finishing stages of the upgrade
Applies to NetApp Hybrid Cloud Control (HCC) NetApp Element software Multiple storage clusters using a single management node (mNode) Description This article describes how to can find the authoritati...Applies to NetApp Hybrid Cloud Control (HCC) NetApp Element software Multiple storage clusters using a single management node (mNode) Description This article describes how to can find the authoritative storage cluster with REST API
Applies to ONTAP 9.6 REST API Issue Unable to retrieve policy using GET "/api/storage/snapmirror/policies" GET call to /api/snapmirror/policies does not return async-mirror and vault policies, only of...Applies to ONTAP 9.6 REST API Issue Unable to retrieve policy using GET "/api/storage/snapmirror/policies" GET call to /api/snapmirror/policies does not return async-mirror and vault policies, only of type mirror-vault, sync-mirror, and strict-sync-mirror POST call to /api/snapmirror/relationships to configure Snapmirror with MirrorAllSnapshots policy fails with Error code: 13303819 "error": { "message": "Could not fetch policy information. Reason: entry doesn't exist", "code": "13303819"
Applies to Management Node (mNode) NetApp HCI monitor NetApp Hybrid Cloud Control (HCC) Description The article explains how to update the vCenter credential and IP address in the Controller asset for...Applies to Management Node (mNode) NetApp HCI monitor NetApp Hybrid Cloud Control (HCC) Description The article explains how to update the vCenter credential and IP address in the Controller asset for vCenter.
Error is encountered when trying to create a new SnapMirror relationship over REST API while also trying to apply a SnapMirror policy during the creation: DEBUG: SnapmirrorRelationship({'destination':...Error is encountered when trying to create a new SnapMirror relationship over REST API while also trying to apply a SnapMirror policy during the creation: DEBUG: SnapmirrorRelationship({'destination': {'path': 'volume1:misc1'}, 'source': {'path': 'vserver_dr:misc1'}, 'policy': {'name': 'volume1'}}) ERROR: 13303866: Associating the specified SnapMirror policy with this SnapMirror relationship is not supported. 'policy': {'name': f'{svmname}_vault'}, #'state': 'snapmirror',
Applies to ONTAP 9 REST API CIFS Security Identifier(SID) Issue REST API POST for /api/protocols/cifs/local-users does not return SID Example: Expected output: loaction: /api/protocols/cifs/local-user...Applies to ONTAP 9 REST API CIFS Security Identifier(SID) Issue REST API POST for /api/protocols/cifs/local-users does not return SID Example: Expected output: loaction: /api/protocols/cifs/local-users/svm_uuid/sid Actual output: location: /api/protocols/cifs/local-users/svm_uuid
SnapCenter Plug-in for Microsoft Exchange Server (SCE) 5.0 | 5.0P1 | 6.0 SnapCenter Plug-in for Microsoft SQL Server (SCSQL) 5.0 | 5.0P1 | 6.0 SnapCenter Plug-in for Windows (SCW) 5.0 | 5.0P1 | 6.0 By...SnapCenter Plug-in for Microsoft Exchange Server (SCE) 5.0 | 5.0P1 | 6.0 SnapCenter Plug-in for Microsoft SQL Server (SCSQL) 5.0 | 5.0P1 | 6.0 SnapCenter Plug-in for Windows (SCW) 5.0 | 5.0P1 | 6.0 By default, SnapCenter versions 5.0, 5.0P1 and 6.0 use REST API calls to communicate with ONTAP. If it is determined that a REST API call is causing issues with operations in SnapCenter, REST API can be disabled, thereby switching communication with ONTAP back to ZAPI (ONTAPI).
Querying a volume with rest by volume name returns no results, however querying the same volume by UUID returns results. curl -X GET "https://1.2.3.4/api/storage/volumes?is_constituent=false&name=vol1...Querying a volume with rest by volume name returns no results, however querying the same volume by UUID returns results. curl -X GET "https://1.2.3.4/api/storage/volumes?is_constituent=false&name=vol1&return_records=true&return_timeout=15" -H "accept: application/json" -H "authorization: Basic AAWWYYTT123456789="