Merge pull request #172 from NetAppDocs/21.1_hci_1.9_release

Merging internal main GA branch for 21.1 HCI 1.9 release to public main.

Author: netapp-mwallis

_data/sidebars/docs_sidebar.yml

@@ -98,6 +98,8 @@ entries:
            url: /task_nde_access_manual_ip.html
      - title: Start your deployment
        url: /task_nde_start_deployment.html
+     - title: Import an installation profile
+       url: /task_nde_import_installation_profile.html
      - title: Configure VMware vSphere
        entries:
          - title: vSphere configuration overview
@@ -249,9 +251,9 @@ entries:
         url: /concept_hci_upgrade_overview.html
       - title: Upgrade sequences
         entries:
-          - title: Upgrade your NetApp HCI system for version 1.8
+          - title: Upgrade your NetApp HCI system for version 1.9
             url: /task_hcc_upgrade_all.html
-          - title: Upgrade your NetApp SolidFire all-flash storage system for Element 12.2
+          - title: Upgrade your NetApp SolidFire all-flash storage system for Element 12.3
             url: /task_sf_upgrade_all.html
       - title: System upgrade procedures
         entries:
@@ -353,5 +355,7 @@ entries:
        url: /task_hci_snswitches.html
      - title: Replace storage node in a two-node cluster
        url: /task_hci_2noderepl.html
+  - title: Earlier versions
+    url: /reference_earlier_versions.html
   - title: Legal notices
     url: /reference_notices_hci.html

docs/concept_cg_hci_accounts.adoc

@@ -45,9 +45,6 @@ NOTE: A local (non-LDAP) cluster administrator account is required to access act
 
 You can manage cluster administrator accounts by creating, deleting, and editing cluster administrator accounts, changing the cluster administrator password, and configuring LDAP settings to manage system access for users.
 
-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^].
-
-
 == Authoritative user accounts
 
 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.
@@ -75,4 +72,3 @@ Volume accounts are managed within the NetApp Hybrid Cloud Control Volumes table
 * link:concept_hci_clusters.html[Learn about clusters]
 *	https://www.netapp.com/hybrid-cloud/hci-documentation/[NetApp HCI Resources page^]
 *	https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
-* https://docs.netapp.com/sfe-122/index.jsp[SolidFire and Element Documentation Center^]

docs/concept_hci_clusters.adoc

@@ -27,10 +27,7 @@ Many NetApp Hybrid Cloud Control features are designed to work with multiple sto
 
 You can manage users with NetApp Hybrid Cloud Control.
 
-
-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).
-
-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.
+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. 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.
 
 == Stranded capacity
 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.

docs/concept_hci_dataprotection.adoc

@@ -121,14 +121,12 @@ Two different protection domain layouts, called protection domain levels, are su
 ** The chassis level layout is automatically determined from the hardware when the node is added to the cluster.
 ** In a cluster where each node is in a separate chassis, these two levels are functionally identical.
 
-You can manually enable protection domain monitoring using the NetApp Element Configuration extension point in the NetApp Element Plug-in for vCenter Server. You can select a protection domain threshold based on node or chassis domains.
+You can manually https://docs.netapp.com/us-en/vcp/vcp_task_clusters_manage.html#set-protection-domain-monitoring[enable protection domain monitoring] using the NetApp Element Plug-in for vCenter Server. You can select a protection domain threshold based on node or chassis domains.
 
 When creating a new cluster, if you are using storage nodes that reside in a shared chassis, you might want to consider designing for chassis-level failure protection using the protection domains feature.
 
 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.
 
-See https://docs.netapp.com/sfe-122/topic/com.netapp.doc.sfe-ug/GUID-7D31AC22-8815-4BDA-984A-9AED750B96B1.html[SolidFire and Element 12.2 Documentation Center^].
-
 == Double Helix high availability
 
 Double Helix data protection is a replication method that spreads at least two redundant copies of data across all drives within a system. The “RAID-less” approach enables a system to absorb multiple, concurrent failures across all levels of the storage system and repair quickly.

docs/concept_hci_storage_maintenance_mode.adoc

@@ -40,4 +40,7 @@ You can see the states of maintenance mode operations when working with maintena
 * *ReadyForMaintenance*: The node is ready for maintenance to be performed.
 
 == Find more information
-* https://docs.netapp.com/sfe-122/index.jsp[SolidFire and Element Documentation Center^]
+
+*	https://docs.netapp.com/us-en/element-software/api/concept_element_api_about_the_api.html[NetApp Element API documentation^]
+*	https://www.netapp.com/hybrid-cloud/hci-documentation/[NetApp HCI Resources page^]
+*	https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]

docs/concept_hci_upgrade_overview.adoc

@@ -24,8 +24,8 @@ The content in this section introduces recommended upgrade sequences for compone
 
 Choose one of the following sequences based on your system:
 
-* link:task_hcc_upgrade_all.html[Upgrade your NetApp HCI installation for version 1.8].
-* link:task_sf_upgrade_all.html[Upgrade your NetApp SolidFire all-flash storage system for Element 12.2].
+* link:task_hcc_upgrade_all.html[Upgrade your NetApp HCI installation for version 1.9].
+* link:task_sf_upgrade_all.html[Upgrade your NetApp SolidFire all-flash storage system for Element 12.3].
 
 == vSphere upgrade sequences including Element Plug-in for vCenter Server
 
@@ -37,4 +37,4 @@ Choose one of the following sequences based on your system:
 [discrete]
 == Find more information
 * https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
-* https://docs.netapp.com/sfe-122/index.jsp[SolidFire and Element Documentation Center^]
+* https://docs.netapp.com/us-en/element-software/index.html[SolidFire and Element documentation^]

docs/concept_nde_node_compatibility.adoc

@@ -18,7 +18,7 @@ When choosing nodes for your deployment, some restrictions apply to the node con
 == Storage node compatibility
 NetApp HCI supports storage nodes and drives with SED (Self-encrypting drive) and FIPS 140-2 drive encryption capability. When deploying or expanding NetApp HCI, you can mix nodes with different reported levels of encryption, but NetApp HCI only supports the more basic form of encryption in this situation. For example, if you mix a storage node that is FIPS encryption capable with nodes that only support SED encryption, SED encryption is supported with this configuration, but FIPS drive encryption is not.
 
-NOTE: Adding storage nodes capable of FIPS drive encryption to the storage cluster does not automatically enable the FIPS drive encryption feature. After you deploy or expand an installation with FIPS-capable nodes, you need to manually enable FIPS drive encryption. See the Element Software User Guide for instructions.
+NOTE: Adding storage nodes capable of FIPS drive encryption to the storage cluster does not automatically enable the FIPS drive encryption feature. After you deploy or expand an installation with FIPS-capable nodes, you need to manually enable FIPS drive encryption. See the https://docs.netapp.com/us-en/element-software/index.html[Element software documentation^] for instructions.
 
 All storage nodes must run the same minor version of Element software to be compatible in the same deployment. For example, you cannot mix a storage node running Element 11.3.1 with other storage nodes running Element 11.5.
 
@@ -37,4 +37,4 @@ Compute nodes must meet the following requirements to be selectable as inventory
 
 == Find more information
 * https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
-* http://docs.netapp.com/sfe-122/index.jsp[SolidFire and Element Software Documentation Center^]
+* https://docs.netapp.com/us-en/element-software/index.html[SolidFire and Element software documentation^]

docs/hci_prereqs_network_switch.adoc

@@ -39,6 +39,7 @@ NetApp HCI has the following switch requirements:
 * The switches handling storage, virtual machine, and vMotion traffic must support speeds of at least 10GbE per port (up to 25GbE per port is supported).
 * The switches handling management traffic must support speeds of at least 1GbE per port.
 * You must configure jumbo frames on the switch ports handling storage and vMotion traffic. Hosts must be able to send 9000 byte packets end-to-end for a successful installation.
+* You must configure the management network switch ports to allow whatever size MTU the management NIC ports on each host are configured for. For example, if the host management network ports use an MTU size of 1750 bytes, the management network switch ports must be configured to allow at least an MTU of 1750 bytes (the management network does not require an MTU of 9000 bytes). The MTU settings should be consistent end-to-end.
 * Round-trip network latency between all storage and compute nodes should not exceed 2ms.
 
 All NetApp HCI nodes provide additional out-of-band management capabilities via a dedicated management port. NetApp H300S, H300E, H500S, H500E, H700S, H700E and H410C nodes also allow for IPMI access via Port A. As a best practice, you should ease remote management of NetApp HCI by configuring out-of-band management for all nodes in your environment.

docs/index.adoc

@@ -20,7 +20,7 @@ You can upgrade, expand, and monitor your system with the NetApp Hybrid Cloud Co
 == Discover what's new
 
 * link:rn_whatsnew.html[What's new in NetApp HCI]
-* http://docs.netapp.com/sfe-122/index.jsp[What's new in NetApp Element software^]
+* https://docs.netapp.com/us-en/element-software/concepts/concept_rn_whats_new_element.html[What's new in NetApp Element software^]
 * https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/Management_services_for_Element_Software_and_NetApp_HCI/Management_Services_Release_Notes[What's new in management services for Element software and NetApp HCI^]
 * https://library.netapp.com/ecm/ecm_download_file/ECMLP2866569[What's new in NetApp Element Plug-in for vCenter Server^]
 

docs/reference_earlier_versions.adoc

@@ -0,0 +1,19 @@
+---
+sidebar: docs_sidebar
+permalink: docs/reference_earlier_versions.html
+keywords: documentation, earlier, previous, versions
+summary: Documentation for previous releases of NetApp HCI is available in case you're not running the latest version.
+---
+
+= Earlier versions of NetApp HCI documentation
+:hardbreaks:
+:nofooter:
+:icons: font
+:linkattrs:
+:imagesdir: ../media/
+:keywords: hci, earlier, documentation, versions
+
+[.lead]
+Documentation for previous releases of NetApp HCI is available in case you're not running the latest version.
+
+* http://docs.netapp.com/us-en/hci18/docs/index.html[NetApp HCI 1.8P1^]