You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concept_cg_hci_accounts.adoc
+40-12Lines changed: 40 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,39 @@ summary: Each NetApp HCI system that has cloud services enabled is associated wi
5
5
keywords: netapp, hci, on premise, administrator, user account, cloud services, cluster
6
6
---
7
7
8
-
= NetApp HCI accounts
8
+
= User accounts
9
9
:hardbreaks:
10
10
:nofooter:
11
11
:icons: font
12
12
:linkattrs:
13
13
:imagesdir: ../media/
14
14
15
15
[.lead]
16
-
To use NetApp HCI, you'll need to set up some user accounts.
16
+
To access storage resources on your system, you'll need to set up user accounts.
17
17
18
-
== Storage cluster administrator account types
19
18
20
-
There are two types of administrator accounts that can exist in a storage cluster running NetApp Element software: the primary cluster administrator account and a cluster administrator account.
19
+
== User account management
20
+
21
+
User accounts are used to control access to the storage resources on a NetApp Element software-based network. At least one user account is required before a volume can be created.
22
+
23
+
When you create a volume, it is assigned to an account. If you have created a virtual volume, the account is the storage container.
24
+
25
+
Here are some additional considerations:
26
+
27
+
* The account contains the CHAP authentication required to access the volumes assigned to it.
28
+
* An account can have up to two thousand volumes assigned to it, but a volume can belong to only one account.
29
+
* User accounts can be managed from the NetApp Element Management extension point.
30
+
31
+
Using NetApp Hybrid Cloud Control, you can create and manage the following types of accounts:
32
+
33
+
* Administrator user accounts for the storage cluster
34
+
* Authoritative user accounts
35
+
* Volume accounts, specific only to the storage cluster on which they were created.
36
+
37
+
38
+
== Storage cluster administrator accounts
39
+
40
+
There are two types of administrator accounts that can exist in a storage cluster running NetApp Element software:
21
41
22
42
* *Primary cluster administrator account*: This administrator account is created when the cluster is created. This account is the primary administrative account with the highest level of access to the cluster. This account is analogous to a root user in a Linux system. You can change the password for this administrator account.
23
43
* *Cluster administrator account*: You can give a cluster administrator account a limited range of administrative access to perform specific tasks within a cluster. The credentials assigned to each cluster administrator account are used to authenticate API and Element UI requests within the storage system.
@@ -29,24 +49,32 @@ You can manage cluster administrator accounts by creating, deleting, and editing
29
49
For details, see the https://docs.netapp.com/sfe-122/topic/com.netapp.doc.sfe-ug/GUID-057D852C-9C1C-458A-9161-328EDA349B00.html[SolidFire and Element Documentation Center^].
30
50
31
51
32
-
== User account management
52
+
== Authoritative user accounts
33
53
34
-
User accounts are used to control access to the storage resources on a NetApp Element software-based network. At least one user account is required before a volume can be created.
54
+
Authoritative user accounts can authenticate against any storage asset associated with the NetApp Hybrid Cloud Control instance of nodes and clusters. With this account, you can manage volumes, accounts, access groups, and more across all clusters.
35
55
36
-
When you create a volume, it is assigned to an account. If you have created a virtual volume, the account is the storage container.
56
+
Authoritative user accounts are managed from the top right menu User Management option in NetApp Hybrid Cloud Control.
37
57
38
-
Here are some additional considerations:
58
+
The authoritative storage cluster is the storage cluster that NetApp Hybrid Cloud Control uses to authenticate users.
39
59
40
-
* The account contains the CHAP authentication required to access the volumes assigned to it.
41
-
* An account can have up to two thousand volumes assigned to it, but a volume can belong to only one account.
42
-
* User accounts can be managed from NetApp Element Management extension point.
60
+
All users created on the authoritative storage cluster can log into the NetApp Hybrid Cloud Control. Users created on other storage clusters _cannot_ log into Hybrid Cloud Control.
61
+
62
+
* If your management node only has one storage cluster, then it is the authoritative cluster.
63
+
* If your management node has two or more storage clusters, one of those clusters is assigned as the authoritative cluster and only users from that cluster can log into NetApp Hybrid Cloud Control.
64
+
65
+
While many NetApp Hybrid Cloud Control features work with multiple storage clusters, authentication and authorization have necessary limitations. The limitation around authentication and authorization is that users from the authoritative cluster can execute actions on other clusters tied to NetApp Hybrid Cloud Control even if they are not a user on the other storage clusters. Before proceeding with managing multiple storage clusters, you should ensure that users defined on the authoritative clusters are defined on all other storage clusters with the same permissions. You can manage users from NetApp Hybrid Cloud Control.
43
66
44
-
For details, see user account information in the https://docs.netapp.com/sfe-122/topic/com.netapp.doc.sfe-mg-vcp/GUID-A6418A61-29C6-4904-A434-3F1B7FD62340.html[SolidFire and Element Documentation Center^].
45
67
68
+
== Volume accounts
69
+
Volume-specific accounts are specific only to the storage cluster on which they were created. These accounts enable you to set permissions on specific volumes across the network, but have no effect outside of those volumes.
46
70
71
+
Volume accounts are managed within the NetApp Hybrid Cloud Control Volumes table.
47
72
48
73
[discrete]
49
74
== Find more information
75
+
* link:task_hcc_manage_accounts.html[Manage user accounts]
76
+
* link:concept_hci_clusters.html[Learn about clusters]
77
+
* https://docs.netapp.com/sfe-122/topic/com.netapp.doc.sfe-mg-vcp/GUID-A6418A61-29C6-4904-A434-3F1B7FD62340.html[SolidFire and Element Documentation Center^]
Copy file name to clipboardExpand all lines: docs/concept_hci_clusters.adoc
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,15 @@ The authoritative storage cluster is the storage cluster that NetApp Hybrid Clou
22
22
23
23
If your management node only has one storage cluster, then it is the authoritative cluster. If your management node has two or more storage clusters, one of those clusters is assigned as the authoritative cluster and only users from that cluster can log into NetApp Hybrid Cloud Control. To find out which cluster is the authoritative cluster, you can use the `GET /mnode/about` API. In the response, the IP address in the `token_url` field is the management virtual IP address (MVIP) of the authoritative storage cluster. If you attempt to log into NetApp Hybrid Cloud Control as a user that is not on the authoritative cluster, the login attempt will fail.
24
24
25
-
Many NetApp Hybrid Cloud Control features are designed to work with multiple storage clusters, but authentication and authorization have limitations. The limitation around authentication and authorization is that the user from the authoritative cluster can execute actions on other clusters tied to NetApp Hybrid Cloud Control even if they are not a user on the other storage clusters. Before proceeding with managing multiple storage clusters, you should ensure that users defined on the authoritative clusters are defined on all other storage clusters with the same permissions. You can manage users from the Element software user interface (Element web UI).
26
25
27
-
See link:task_mnode_manage_storage_cluster_assets.html[Manage storage cluster assets] for more information on working with management node storage cluster assets.
26
+
Many NetApp Hybrid Cloud Control features are designed to work with multiple storage clusters, but authentication and authorization have limitations. The limitation around authentication and authorization is that the user from the authoritative cluster can execute actions on other clusters tied to NetApp Hybrid Cloud Control even if they are not a user on the other storage clusters. Before proceeding with managing multiple storage clusters, you should ensure that users defined on the authoritative clusters are defined on all other storage clusters with the same permissions.
27
+
28
+
You can manage users with NetApp Hybrid Cloud Control.
29
+
30
+
31
+
Before proceeding with managing multiple storage clusters, you should ensure that users defined on the authoritative clusters are defined on all other storage clusters with the same permissions. You can https://docs.netapp.com/sfe-122/index.jsp?topic=%2Fcom.netapp.doc.sfe-ug%2FGUID-E54EF120-2F00-4F43-B7CA-CCCBAAD1B5B6.html[manage users] from the Element software user interface (Element web UI).
32
+
33
+
See link:task_mnode_manage_storage_cluster_assets.html[Create and manage storage cluster assets] for more information on working with management node storage cluster assets.
28
34
29
35
== Stranded capacity
30
36
If a newly added node accounts for more than 50 percent of the total cluster capacity, some of the capacity of this node is made unusable ("stranded"), so that it complies with the capacity rule. This remains the case until more storage capacity is added. If a very large node is added that also disobeys the capacity rule, the previously stranded node will no longer be stranded, while the newly added node becomes stranded. Capacity should always be added in pairs to avoid this from happening. When a node becomes stranded, an appropriate cluster fault is thrown.
Copy file name to clipboardExpand all lines: docs/concept_hci_performance.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,11 +78,11 @@ As an example, if block sizes are 4k, and bandwidth is 4000 KBps, the IOPS are 1
78
78
79
79
== QoS policies
80
80
81
-
A QoS policy enables you to create and save a standardized quality of service setting that can be applied to many volumes. You can create, edit, and delete QoS policies.
81
+
A QoS policy enables you to create and save a standardized quality of service setting that can be applied to many volumes.
82
82
83
-
QoS policies are best for service environments, for example, with database, application, or infrastructure servers that rarely reboot and need constant equal access to storage. QoSSIOC automation is best for light use VMs, such as virtual desktops or specialized kiosk-type VMs, that may be rebooted, powered on, or powered off daily or several times a day. QoSSIOC automation and QoS policies should not be used together. If you are using QoS policies, do not enable QoSSIOC. QoSSIOC will override and adjust QoS values for volume QoS settings.
83
+
QoS policies are best for service environments, for example, with database, application, or infrastructure servers that rarely reboot and need constant equal access to storage. Individual volume QoS is best for light use VMs, such as virtual desktops or specialized kiosk-type VMs, that may be rebooted, powered on, or powered off daily or several times a day.
84
84
85
-
You can view QoS policieson the *Management* > *QoS Policies* page from the NetApp Element Management extension point.
85
+
QoS and QoS policies should not be used together. If you are using QoS policies, do not use custom QoS on a volume. Custom QoS will override and adjust QoS policy values for volume QoS settings.
86
86
87
87
NOTE: The selected cluster must be Element 10.0 or later to use QoS policies; otherwise, QoS policy functions are not available.
summary: Learn about volume access groups and how you can use them to access and manage volumes.
5
+
keywords: netapp, hci, storage volume, solidfire volume, element volume, persistent volume, access group
6
+
---
7
+
8
+
= Volume access groups
9
+
:hardbreaks:
10
+
:nofooter:
11
+
:icons: font
12
+
:linkattrs:
13
+
:imagesdir: ../media/
14
+
15
+
[.lead]
16
+
A volume access group is a collection of volumes that users can access using either iSCSI or Fibre Channel initiators.
17
+
18
+
By creating and using volume access groups, you can control access to a set of volumes. When you associate a set of volumes and a set of initiators with a volume access group, the access group grants those initiators access to that set of volumes.
19
+
20
+
Volume access groups have the following limits:
21
+
22
+
* A maximum of 64 IQNs or WWPNs are allowed in an access group.
23
+
* An access group can be made up of a maximum of 2000 volumes.
24
+
* An IQN or WWPN can belong to only one access group.
25
+
* A single volume can belong to a maximum of four access groups.
0 commit comments