Skip to content

Commit

Permalink
Merge pull request #177 from NetAppDocs/mgmt_svcs_yosemite_release
Browse files Browse the repository at this point in the history
Mgmt svcs yosemite release
  • Loading branch information
netapp-dbagwell committed Apr 22, 2021
2 parents bc09af1 + 0a1d6a2 commit b06b896
Show file tree
Hide file tree
Showing 27 changed files with 110 additions and 78 deletions.
2 changes: 2 additions & 0 deletions _data/sidebars/docs_sidebar.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,8 @@ entries:
url: /concept_hci_volume_access_groups.html
- title: Initiators
url: /concept_hci_initiators.html
- title: Custom protection domains
url: /concept_hcc_custom_protection_domains.html
# url: /concept_hci_storage.html
- title: Licensing
url: /concept_cg_hci_licensing.html
Expand Down
32 changes: 32 additions & 0 deletions docs/concept_hcc_custom_protection_domains.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
permalink: docs/concept_hcc_custom_protection_domains.html
sidebar: docs_sidebar
keywords: protection domain layout,user-defined,custom layout
summary: 'You can define a custom protection domain layout, where each node is associated with one and only one custom protection domain. By default, each node is assigned to the same default custom protection domain.'
---
= Custom protection domains
:icons: font
:imagesdir: ../media/

[.lead]
You can define a custom protection domain layout, where each node is associated with one and only one custom protection domain. By default, each node is assigned to the same default custom protection domain.

If no custom protection domains are assigned:

* Cluster operation is unaffected.
* Custom level is neither tolerant nor resilient.

If more than one custom protection domain is assigned, each subsystem will assign duplicates to separate custom protection domains. If this is not possible, it reverts to assigning duplicates to separate nodes. Each subsystem (for example, bins, slices, protocol endpoint providers, and ensemble) does this independently.

NOTE: Using custom protection domains assumes that no nodes share a chassis.

The following Element API methods expose these new protection domains:

* GetProtectionDomainLayout - shows which chassis and which custom protection domain each node is in.
* SetProtectionDomainLayout - allows a custom protection domain to be assigned to each node.

Contact NetApp support for further details on using custom protection domains.

== Find more information

link:api/index.html[Manage storage with the Element API]
2 changes: 1 addition & 1 deletion docs/reference_hcc_config_maximums.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ If you exceed these tested maximums, you might experience issues with NetApp Hyb

.Configuration maximums

NetApp Hybrid Cloud Control supports VMware vSphere environments with up to 100 ESXi hosts and 1000 virtual machines (comparable to a small vCenter Server Appliance configuration).
NetApp Hybrid Cloud Control supports VMware vSphere environments with up to 500 NetApp compute nodes. It supports up to 20 NetApp Element Software based storage clusters.
1 change: 1 addition & 0 deletions docs/reference_notices_hci.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ Notice files provide information about third-party copyright and licenses.
* link:../media/storage_firmware_bundle_2.27_notices.pdf[Notice for Storage Firmware Bundle 2.27^]
* link:../media/compute_iso_notice.pdf[Notice for compute firmware ISO^]
* link:../media/H610S_BMC_notice.pdf[Notice for H610S BMC^]
* link:../media/2.18_notice.pdf[Notice for Management Services 2.18.91^]
* link:../media/2.17.56_notice.pdf[Notice for Management Services 2.17.56^]
* link:../media/2.17_notice.pdf[Notice for Management Services 2.17.52^]
* link:../media/2.16_notice.pdf[Notice for Management Services 2.16^]
Expand Down
1 change: 1 addition & 0 deletions docs/rn_relatedrn.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ NOTE: You will be prompted to log in using your NetApp Support Site credentials.
* https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/Management_services_for_Element_Software_and_NetApp_HCI/Management_Services_Release_Notes[Management Services Release Notes]

== NetApp Element Plug-in for vCenter Server
* https://library.netapp.com/ecm/ecm_download_file/ECMLP2876748[vCenter Plug-in 4.7 Release Notes^]
* https://library.netapp.com/ecm/ecm_download_file/ECMLP2874631[vCenter Plug-in 4.6 Release Notes]
* https://library.netapp.com/ecm/ecm_download_file/ECMLP2873396[vCenter Plug-in 4.5 Release Notes]
* https://library.netapp.com/ecm/ecm_download_file/ECMLP2866569[vCenter Plug-in 4.4 Release Notes]
Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_edit_bmc_info.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ You can change Baseboard Management Controller (BMC) administrator credentials i

Cluster administrator permissions to change BMC credentials.

NOTE: If you set BMC credentials during a health check, there can be a delay of up to 15 minutes before the change is reflected on the *Nodes* page.
NOTE: If you set BMC credentials during a health check, there can be a delay of up to 2 minutes before the change is reflected on the *Nodes* page.

.Options

Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_manage_accounts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ If you configured users on the storage cluster with LDAP, those accounts show a
. Log out of NetApp Hybrid Cloud Control.
. link:task_mnode_manage_storage_cluster_assets.html#edit-the-stored-credentials-for-a-storage-cluster-asset[Update the credentials] for the authoritative cluster asset using the NetApp Hybrid Cloud Control API.
+
NOTE: It might take the NetApp Hybrid Cloud Control UI up to 15 minutes to refresh the inventory. To manually refresh inventory, access the REST API UI inventory service `https://[management node IP]/inventory/1/` and run `GET /installations​/{id}` for the cluster.
NOTE: It might take the NetApp Hybrid Cloud Control UI up to 2 minutes to refresh the inventory. To manually refresh inventory, access the REST API UI inventory service `https://[management node IP]/inventory/1/` and run `GET /installations​/{id}` for the cluster.

. Log into NetApp Hybrid Cloud Control.

Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_manage_storage_clusters.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ NOTE: Only remote storage clusters that are not currently managed by a managemen

. Select *Add*.
+
NOTE: After you add the storage cluster, the cluster inventory can take up to 15 minutes to refresh and display the new addition. You might need to refresh the page in your browser to see the changes.
NOTE: After you add the storage cluster, the cluster inventory can take up to 2 minutes to refresh and display the new addition. You might need to refresh the page in your browser to see the changes.

. If you are adding Element eSDS clusters, enter or upload your SSH private key and SSH user account.

Expand Down
78 changes: 36 additions & 42 deletions docs/task_hcc_manage_vol_management.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,11 +24,11 @@ You can manage volumes in NetApp Hybrid Cloud Control in the following ways:
* <<Apply a QoS policy to a volume>>
* <<Edit a volume>>
* <<Clone volumes>>
* <<Add volumes to a volume access group>>
* <<Delete a volume>>
* <<Restore a deleted volume>>
* <<Purge a deleted volume>>


== Create a volume
You can create a storage volume using NetApp Hybrid Cloud Control.

Expand All @@ -47,40 +47,37 @@ NOTE: The default volume size selection is in GB. You can create volumes using s
1GiB = 1 073 741 824 bytes

. Select a block size for the volume.
. From the Account list, select the account that should have access to the volume.
. From the *Account* list, select the account that should have access to the volume.
+
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create*. The account is created and associated with the new volume.
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create Account*. The account is created and associated with the new volume in the *Account* list.

+
NOTE: If there are more than 50 accounts, the list does not appear. Begin typing and the auto-complete feature displays values for you to choose.

. To set the Quality of Service, do one of the following:
.. Select an existing QoS policy.
.. Under QoS Settings, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.
. To configure the Quality of Service for the volume, do one of the following:

* Under *Quality of Service Settings*, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.
* Select an existing QoS policy by enabling the *Assign Quality of Service Policy* toggle and choosing an existing QoS policy from the resulting list.
* Create and assign a new QoS policy by enabling the *Assign Quality of Service Policy* toggle and clicking *Create New QoS Policy*. In the resulting window, enter a name for the QoS policy and then enter QoS values. When finished, click *Create Quality of Service Policy*.

+
Volumes that have a Max or Burst IOPS value greater than 20,000 IOPS might require high queue depth or multiple sessions to achieve this level of IOPS on a single volume.

. Click *Create Volume*.


== Apply a QoS policy to a volume
You can apply a QoS policy to an existing storage volume by using NetApp Hybrid Cloud Control.

You can apply a QoS policy to existing storage volumes by using NetApp Hybrid Cloud Control. If instead you need to set custom QoS values for a volume, you can <<Edit a volume>>. To create a new QoS policy, see link:task_hcc_qos_policies.html[Create and manage volume QoS policies^].

.Steps
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
. Select *Volumes* > *Overview*.
. In the *Actions* column in the volumes table, expand the menu for the volume and select *Edit*.
. Change the Quality of Service by doing one of the following:
.. Select an existing policy.
.. Under Custom Settings, set the minimum, maximum, and burst values for IOPS or use the default values.
+
NOTE: If you are using QoS policies on a volume, you can set custom QoS to remove the QoS policy affiliation with the volume. Custom QoS override QoS policy values for volume QoS settings.
. Select one or more volumes to associate with a QoS policy.
. Click the *Actions* drop-down list at the top of the volumes table, and select *Apply QoS Policy*.
. In the resulting window, select a QoS policy from the list and click *Apply QoS Policy*.
+
TIP: When you change IOPS values, increment in tens or hundreds. Input values require valid whole numbers. Configure volumes with an extremely high burst value. This enables the system to process occasional large block, sequential workloads more quickly, while still constraining the sustained IOPS for a volume.

. Select *Save*.
NOTE: If you are using QoS policies on a volume, you can set custom QoS to remove the QoS policy affiliation with the volume. Custom QoS values override QoS policy values for volume QoS settings.


== Edit a volume
Expand Down Expand Up @@ -155,36 +152,36 @@ NOTE: Cloned volumes do not inherit volume access group membership from the sour
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
. Select the *Volumes* > *Overview* tab.
. Select each volume you want to clone and click the *Clone* button that appears.
. Do one of the following:
* To clone a single volume, perform the following steps:
.. In the *Clone Volume* dialog box, enter a volume name for the volume clone.
. Select each volume you want to clone.
. Click the *Actions* drop-down list at the top of the volumes table, and select *Clone*.
. In the resulting window, do the following:

.. Enter a volume name prefix (this is optional).
.. Choose the access type from the *Access* list.
.. Choose an account to associate with the new volume clone (by default, *Copy from Volume* is selected, which will use the same account that the original volume uses).
.. If an account does not exist, click *Create New Account*, enter a new account name, and click *Create Account*. The account is created and associated with the volume.
+
TIP: Use descriptive naming best practices. This is especially important if multiple clusters or vCenter Servers are used in your environment.

.. Select an account access level:
** Read Only
** Read/Write
** Locked
** Replication Target

.. Select a size in GB or GIB for the volume clone.
+
NOTE: Increasing the volume size of a clone results in a new volume with additional free space at the end of the volume. Depending on how you use the volume, you may need to extend partitions or create new partitions in the free space to make use of it.

.. Select an account to associate with the volume clone.
+
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create*. The account is created and associated with the volume.

.. Click *Clone Volumes*.
NOTE: The time to complete a cloning operation is affected by volume size and current cluster load. Refresh the page if the cloned volume does not appear in the volume list.

* To clone multiple volumes, perform the following steps:
.. In the *Clone Volumes* dialog box, enter an optional prefix for the volume clones in the *New Volume Name Prefix* field.
.. Select a new type of access for the volume clones or copy the access type from the active volumes.
.. Select a new account to associate with the volume clones or copy the account association from the active volumes.
.. Click *Clone Volumes*.
== Add volumes to a volume access group
You can add a single volume or a group of volumes to a volume access group.

.Steps
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
. Select *Volumes* > *Overview*.
. Select one or more volumes to associate with a volume access group.
. Click the *Actions* drop-down list at the top of the volumes table, and select *Add to Access Group*.
. In the resulting window, select a volume access group from the *Volume Access Group* list.
. Click *Add Volume*.

NOTE: The time to complete a cloning operation is affected by volume size and current cluster load. Refresh the page if the cloned volume does not appear in the volume list.

== Delete a volume
You can delete one or more volumes from an Element storage cluster.
Expand All @@ -202,11 +199,8 @@ IMPORTANT: Persistent volumes that are associated with management services are c
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
. Select *Volumes* > *Overview*.
. Select one or more volumes to delete.
. Do one of the following:
+
* If you selected multiple volumes, click the *Delete* quick filter at the top of the table.
* If you selected a single volume, in the *Actions* column of the Volumes table, expand the menu for the volume and select *Delete*.
. Confirm the delete by selecting *Yes*.
. Click the *Actions* drop-down list at the top of the volumes table, and select *Delete*.
. In the resulting window, confirm the action by clicking *Yes*.

== Restore a deleted volume
After a storage volume is deleted, you can still restore it if you do so before eight hours after deletion.
Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_nodes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ keywords: netapp, hci, on premise, cluster, inventory, nodes, storage, compute
[.lead]
You can view both your storage and compute assets in your system and determine their IP addresses, names, and software versions.

You can view storage information for your multiple node systems and any NetApp HCI Witness Nodes associated with two-node or three-node clusters.
You can view storage information for your multiple node systems and any NetApp HCI Witness Nodes associated with two-node or three-node clusters. If link:concept_hcc_custom_protection_domains.html[custom protection domains^] are assigned, you can see which protection domains are assigned to specific nodes.
Witness Nodes manage quorum within the cluster; they are not used for storage. Witness Nodes are applicable only to NetApp HCI and not to all-flash storage environments.

For more information about Witness Nodes, see link:concept_hci_nodes.html[Nodes definitions].
Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_update_management_services.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ NOTE: For a list of available services for each service bundle version, see the
+
The Management Services tab shows the current and available versions of management services software.
+
NOTE: If your installation cannot access the internet, only the current software version is shown.
NOTE: If your installation cannot access the internet, only the current software version is shown. If you have external connectivity but NetApp HCI is unable to access the NetApp online repository, check your link:task_mnode_configure_proxy_server.html[proxy configuration^].

. If your installation can access the internet and if a management services upgrade is available, click *Begin Upgrade*.
. If your installation cannot access the internet, do the following:
Expand Down
2 changes: 1 addition & 1 deletion docs/task_hcc_upgrade_element_prechecks.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ If all health checks are successful, the return is similar to the following exam

You can verify that the storage cluster is ready to be upgraded by using the `sfupgradecheck` command. This command verifies information such as pending nodes, disk space, and cluster faults.

If your management node is at a dark site, the upgrade readiness check needs the `metadata.json` file you downloaded during link:task_upgrade_element_latest_healthtools.html[HealthTools upgrades] to run successfully.
If your management node is at a dark site without external connectivity, the upgrade readiness check needs the `metadata.json` file you downloaded during link:task_upgrade_element_latest_healthtools.html[HealthTools upgrades] to run successfully.

.About this task

Expand Down
4 changes: 2 additions & 2 deletions docs/task_hcc_upgrade_element_software.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ Here are the different states that the *Upgrade Status* column in the UI shows b
|An error has occurred during the upgrade. You can download the error log and send it to NetApp Support. After you resolve the error, you can return to the page, and click *Resume*. When you resume the upgrade, the progress bar goes backwards for a few minutes while the system runs the health check and checks the current state of the upgrade.

|Unable to Detect
|NetApp Hybrid Cloud Control shows this status instead of *Versions Available* when it does not have external connectivity to reach the online software repository.
|NetApp Hybrid Cloud Control shows this status instead of *Versions Available* when it does not have external connectivity to reach the online software repository. If you have external connectivity but still see this message, check your link:task_mnode_configure_proxy_server.html[proxy configuration^].

|Complete with Follow-up
|Only for H610S nodes upgrading from Element version earlier than 11.8. After phase 1 of the upgrade process is complete, this state prompts you to perform phase 2 of the upgrade (see the https://kb.netapp.com/Advice_and_Troubleshooting/Hybrid_Cloud_Infrastructure/H_Series/NetApp_H610S_storage_node_power_off_and_on_procedure[KB article^]). After you complete phase 2 and acknowledge that you have completed it, the status changes to *Up to Date*.
Expand Down Expand Up @@ -529,7 +529,7 @@ Starting light cluster block service check
IMPORTANT: If you are upgrading an H610S series node to Element 12.3 and the node is running a version of Element earlier than 11.8, you will need to perform additional upgrade steps (<<Upgrading H610S storage nodes to Element 12.3 (phase 2),phase 2>>) for each storage node. If you are running Element 11.8 or later, the additional upgrade steps (phase 2) are not required.

== Upgrade Element software at dark sites using HealthTools
You can use the HealthTools suite of tools to update NetApp Element software at a dark site.
You can use the HealthTools suite of tools to update NetApp Element software at a dark site that has no external connectivity.

.What you'll need

Expand Down
Loading

0 comments on commit b06b896

Please sign in to comment.