Storage and Backups-Netapp
Can a Volume ID be reused in Element Software?
Applies to
Element Software.
Answer
No. The Volume ID is uniquely generated for every volume that is created. Even if a volume is deleted, the number will always increment when a new volume is created based on the last Volume ID that was used.
Data ONTAP 8: How to accurately determine CPU utilization of a Data ONTAP 8.0 Cluster-Mode cluster
Applies to
-
Clustered Data ONTAP 8
-
PERF
Description
How to use the various statistics commands to determine which controller and CPU is running hot in a Data ONTAP 8.0 Cluster-Mode cluster?
How to upgrade Cisco switch firmware in a fabric-attached MetroCluster (7mode)?
Applies to
-
ONTAP 8.2
-
ONTAP 8.1
-
MetroCluster
-
7-mode
Description
This article describes how to upgrade Cisco switch firmware in a fabric-attached MetroCluster while the HA pair nodes are online.
API calls to ONTAP 9.1-9.3 fail when using a readonly LDAP service account
Applies to
ONTAP 9.1 - 9.3P7
Issue
API calls made to an ONTAP cluster fail when using a readonly LDAP service account
Error output may be returned by the application sending the API to the effect of the following(this exact output from OnCommand Insight):
2019-02-26 13:04:34,920 ERROR [com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource] myCluster [Invalid login credentials] - Failed to authenticate with cluster: 10.0.0.2 ([Device name 10.0.0.2]: cluster-identity-get; errno: 13003, reason: not authorized for that command)
com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Failed to authenticate with cluster: 10.0.0.2
at com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException.createWithEnhanced(DataSourceErrorException.java:70)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.transport.zapi.ZAPIConnection.parseResponseXMLFromZAPIOutput(ZAPIConnection.java:709)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.transport.zapi.ZAPIConnection.invokeElem(ZAPIConnection.java:514)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.transport.zapi.ZAPIConnection.invokeElem(ZAPIConnection.java:436)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.transport.zapi.ZAPIConnection.invokeElem(ZAPIConnection.java:429)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.transport.zapi.ZAPIConnection.invokeCommandDesiredAttributes(ZAPIConnection.java:237)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.builders.zapi.ClusterBuilder.buildAndAddCluster(ClusterBuilder.java:341)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.builders.zapi.ClusterBuilder.buildClusterModel(ClusterBuilder.java:284)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.builders.zapi.ClusterBuilder.getCModeCluster(ClusterBuilder.java:253)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.builders.zapi.ClusterBuilder.executeAndBuild(ClusterBuilder.java:98)
at com.onaro.sanscreen.acquisition.datasource.netapp_cmode.NetAppCModeDataSource.doFoundation(NetAppCModeDataSource.java:130)
at com.onaro.sanscreen.acquisition.foundation.datasource.BaseFoundationPackage.pollNow(BaseFoundationPackage.java:195)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:409)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runInitClassLoader(BaseDataSource.java:397)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runNotifyListeners(BaseDataSource.java:370)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runInitLog(BaseDataSource.java:344)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runInitRecordingSession(BaseDataSource.java:309)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runInitThreadName(BaseDataSource.java:294)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.runWithProfiler(BaseDataSource.java:273)
at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:249)
at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:734)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.Throwable: not authorized for that command
How to troubleshoot MetroCluster check config replication errors
Applies to
-
MetroCluster
-
metrocluster check
-
Config replication errors
Description
MetroCluster check reports errors on the node object:
ClusterA::> metrocluster check show
Last Checked On: mm/dd/yyyy hh:mm:ss
Component Result
------------------- ---------
nodes ok
lifs ok
config-replication warning
aggregates ok
clusters ok
5 entries were displayed.
FAS8020 storage initiator connection rules in a MetroCluster solution
Applies to
-
MetroCluster
-
ONTAP 9
-
FAS8020 only
Issue
In a MetroCluster in clustered Data ONTAP, each controller must have two HBA initiator connections to each of the two fabrics to connect storage. Along with that, each controller requires four HBA initiator ports.
When using FAS8020 controllers, there might be a need to only use two, instead of four, HBA initiator ports to connect storage to use the single free slot for host connectivity or tape backup. This applies to the FAS8020 only and no other platform. This type configuration can also be called as a 'single initiator per fabric' configuration.
Note
: If a MetroCluster is configured using FAS8020 controllers and the hardware configuration is changed, these rules must be evaluated in order to add / remote paths so the configuration remains supported.