Merge pull request #186 from NetAppDocs/mgmt_node_recover_doc-3054

Merging management node recover changes from Matt, BMC RN fixes, and a fix for the left hand nav column.

_data/sidebars/docs_sidebar.yml

@@ -57,8 +57,6 @@ entries:
            url: /hci_prereqs_network_configuration_option_C.html
      - title: DNS and timekeeping requirements
        url: /hci_prereqs_timekeeping.html
-     - title: DNS and timekeeping requirements
-       url: /hci_prereqs_timekeeping.html
      - title: Environmental requirements
        url: /hci_prereqs_environmental.html
      - title: Protection Domains

docs/rn_H610S_BMC_3.84.07.adoc

@@ -21,7 +21,7 @@ The downloadable BMC update contains BMC feature enhancements and bug fixes for
 == What's New
 H610S BMC 3.84.07 contains various bug fixes and new features. This release brings to the field critical updated BMC firmware ahead of subsequent Element software and storage firmware bundle releases, which will also include this updated BMC firmware for H610S nodes.
 
-You can upgrade the H610S BMC firmware directly out-of-band, and upgrade instructions can be found in <<Upgrading BMC firmware on H610S nodes>>.
+This firmware package is supported on Element versions 11.8, 12.0, and 12.2. You can upgrade the H610S BMC firmware directly out-of-band, and upgrade instructions can be found in <<Upgrading BMC firmware on H610S nodes>>.
 
 == New Features
 The following are the new features and changes included in this release:
@@ -69,25 +69,41 @@ Perform the following steps to upgrade the BMC firmware version on your H610S no
 
 .What you'll need
 * You have checked for alerts by clicking *Reporting* > *Alerts* in the NetApp Element software web UI to ensure that there are no errors.
-* You have downloaded the BMC update file.
+* You have downloaded the BMC update package.
+* You have ensured that the BMC and the computer you are using to perform the update are located on the same network.
+* You have contacted NetApp Support for assistance with the BMC upgrade.
 
 .Steps
 . Log in to the BMC console using your web browser: `https://<BMC_IP>/#login`, where `<BMC_IP>` is the IP address of the BMC.
-. Click *Maintenance* > *Firmware Update*.
-. On the *Firmware Update* screen, do the following:
-.. Disable the *Preserve all configuration* checkbox.
+. Click *Maintenance*.
+. Click *Preserve Configuration*.
+. Do the following:
+.. Disable the *Check All* checkbox.
 .. Enable the *IPMI* checkbox.
 .. Enable the *Network* checkbox.
 .. Enable the *Authentication* checkbox.
 +
 ** The *IPMI* setting is used to preserve existing user accounts.
 ** The *Network* setting is used to preserve the DHCP assigned BMC IP address.
 ** The *Authentication* setting is used to preserve custom accounts configured for BMC login.
+. Click *Save*.
+. Click *Firmware Update*.
+. Disable the *Preserve all Configuration* checkbox.
 +
-NOTE: Ensure that you have disabled the *Preserve all configuration* checkbox.
+NOTE: Ensure that you have disabled the *Preserve all Configuration* checkbox.
 
-. Choose the BMC update file you downloaded and click *Start firmware update* to start the upgrade process.
 +
-The process can take up to 5 minutes to complete if the BMC firmware file is in the node's network; otherwise the process will take longer.
-. Verify the firmware version by looking at the version listed on the *Dashboard* > *More info* page.
+. On the computer you are using to perform the update, extract the contents of the BMC update package.
+. In the BMC web UI, under the *Select Firmware Image* section of the *Firmware Update* page, click *Choose File*.
+. Browse to the `rom.ima_enc` file within the extracted package contents and select it.
+. Click *Start firmware update* and click *OK* when the prompt appears asking if you want to continue.
+. Click *OK* when a prompt appears indicating that a firmware reset is happening.
+. After several minutes, use a new browser tab to log in to the BMC web UI.
+. On the BMC dashboard, go to *Device Information* > *More info*.
+. Confirm that the *Firmware Revision* is *3.84.07*.
 . Perform this procedure for the remaining H610S storage nodes in your cluster.
+
+[discrete]
+== Find more Information
+* https://docs.netapp.com/hci/index.jsp[NetApp HCI Documentation Center^]
+* https://docs.netapp.com/us-en/documentation/hci.aspx[NetApp HCI Resources Page^]

docs/rn_compute_firmware_2.27.adoc

@@ -87,11 +87,15 @@ a|
 === Mellanox NIC firmware driver compatibility
 The updated Mellanox firmware versions 14.25.1020 and 14.24.1000 are compatible only with the following versions of the VMware ESXi driver:
 
-* *ESXi 6.5*: Version 4.16.13.5
+* *ESXi 7.0*: H300E/H500E/H700E/H410C: Version 4.19.16.1
+* *ESXi 7.0*: H610C/H615C: Version 4.17.15.16
 * *ESXi 6.7*: Version 4.17.15.16
+* *ESXi 6.5*: Version 4.16.13.5
 
 NOTE: Before upgrading to version 2.27, make sure you check the current ESXi driver version.  If the driver is out of date, upgrade the driver first. Then upgrade the compute firmware to version 2.27 for your compute nodes. Visit link:task_hcc_upgrade_compute_node_drivers.html[Update compute node drivers^] for instructions on updating your compute node drivers, which include the ESXi driver.
 
+While NetApp Deployment Engine 1.8P1 does not deploy ESXi version 7.0, ESXi 7.0 is supported as a self-install or manual upgrade option. When you manually install or upgrade host OSes, NetApp cannot control the drivers and firmware for these OSes.
+
 == Download Compute Firmware Bundle 2.27
 To download the Compute Firmware Bundle:
 
@@ -147,7 +151,7 @@ After you update the BIOS and BMC, update the H410C node firmware using the comp
 |None
 
 |CSESF-293 / PE-10130
-|Mellanox NIC firmware can be downgraded by BootstrapOS after you upgrade to the Compute Firmware Bundle version 2.27.
+|Mellanox NIC firmware can be downgraded by Bootstrap OS after you upgrade to the Compute Firmware Bundle version 2.27.
 |Reinstall Compute Firmware Bundle version 2.27.
 
 |PE-11033

docs/task_mnode_recover.adoc

@@ -1,7 +1,7 @@
 ---
 sidebar: docs_sidebar
 permalink: docs/task_mnode_recover.html
-summary: You can recover and redeploy a management node for your cluster running NetApp Element software.
+summary: You can recover and redeploy a management node for your cluster running NetApp Element software. Depending on your configuration, you might need to reconfigure authentication for the management node.
 keywords: netapp, element, management node, mnode, disaster recovery, VM
 ---
 
@@ -41,9 +41,11 @@ You can deploy a new OVA and run a redeploy script to pull configuration data fr
 .About this task
 Prior to completing this procedure, you should have an understanding of link:concept_hci_volumes.html#persistent-volumes[persistent volumes] and whether or not you want to use them.
 
-* <<Download ISO or OVA and deploy the VM>>
-* <<Configure the network>>
-* <<Configure the management node>>
+.Steps
+
+. <<Download ISO or OVA and deploy the VM>>
+. <<Configure the network>>
+. <<Configure the management node>>
 
 == Download ISO or OVA and deploy the VM
 
@@ -61,7 +63,7 @@ NetApp HCI: https://mysupport.netapp.com/site/products/all/details/netapp-hci/do
 .. Create a new 64-bit virtual machine from your hypervisor with the following configuration:
 +
 * Six virtual CPUs
-* 12GB RAM
+* 24GB RAM
 * 400GB virtual disk, thin provisioned
 * One virtual network interface with internet access and access to the storage MVIP.
 * (Optional for SolidFire all-flash storage) One virtual network interface with management network access to the storage cluster. If your storage cluster is on a separate subnet from your management node (eth0) and you want to use persistent volumes, add a second network interface controller (NIC) to the VM on the storage subnet (eth1) or ensure that the management network can route to the storage network.
@@ -85,8 +87,8 @@ TIP: To move through the menu options, press the Up or Down arrow keys. To move
 NOTE: If you need an additional NIC to isolate storage traffic, see instructions on configuring another NIC: link:task_mnode_install_add_storage_NIC.html[Configure a storage Network Interface Controller (NIC)].
 
 == Configure the management node
-. SSH into the management node or use the console provided by your hypervisor.
-. Using SSH, run the following command to gain root privileges. Enter your password when prompted:
+. Log in to the management node using SSH or the console provided by your hypervisor.
+. Run the following command to gain root privileges. Enter your password when prompted:
 +
 ----
 sudo su
@@ -96,6 +98,32 @@ sudo su
 +
 NOTE: In vSphere, the *Synchronize guest time with host* box should be checked in the VM options. Do not disable this option if you make future changes to the VM.
 
+. Create a temporary destination directory for the management services bundle contents:
++
+----
+mkdir -p /sf/etc/mnode/mnode-archive
+----
+. Download the management services bundle (version 2.15.28 or later) that was previously installed on the existing management node and save it in the `/sf/etc/mnode/` directory.
+. Extract the downloaded bundle using the following command, replacing the value in [ ] brackets (including the brackets) with the name of the bundle file:
++
+----
+tar xvf /sf/etc/mnode/[management services bundle file]
+----
+. Extract the resulting file to the `/sf/etc/mnode-archive` directory:
++
+----
+tar -C /sf/etc/mnode/mnode-archive -xvf /sf/etc/mnode/services_deploy_bundle.tar.gz
+----
+. Create a configuration file for accounts and volumes:
++
+----
+echo '{"trident": true, "mvip": "[mvip IP address]", "account_name": "[persistent volume account name]"}' | sudo tee /sf/etc/mnode/mnode-archive/management-services-metadata.json
+----
+.. Replace the value in [ ] brackets (including the brackets) for each of the following required parameters:
++
+* *[mvip IP address]*: The management virtual IP address of the storage cluster.
+* *[persistent volume account name]*: The name of the account associated with all persistent volumes in this storage cluster.
+
 . Configure and run the management node redeploy command to connect to persistent volumes hosted on the cluster and start services with previous management node configuration data:
 +
 NOTE: You will be prompted to enter passwords in a secure prompt. If your cluster is behind a proxy server, you must configure the proxy settings so you can reach a public network.
@@ -104,21 +132,13 @@ NOTE: You will be prompted to enter passwords in a secure prompt. If your cluste
 ----
 /sf/packages/mnode/redeploy-mnode --mnode_admin_user [username]
 ----
-
-.. Replace the value in [ ] brackets (including the brackets) for each of the following required parameters:
+.. Replace the value in [ ] brackets (including the brackets) with the user name for the management node administrator account. This is likely to be the username for the user account you used to log into the management node.
 +
-NOTE: The abbreviated form of the command name is in parentheses ( ) and can be substituted for the full name. You can add the following required parameters or allow the script to prompt you for the information.
+NOTE: You can add the user name or allow the script to prompt you for the information.
 
 +
-* *--mnode_admin_user (-mu) [username]*: The username for the management node administrator account. This is likely to be the username for the user account you used to log into the management node.
-* *--storage_mvip (-sm) [MVIP address]*: The management virtual IP address (MVIP) of the storage cluster running Element software with the persistent volumes that contain management node data for recovery.
-* *--storage_username (-su) [username]*: The storage cluster administrator username for the cluster specified by the `--storage_mvip` parameter.
-* *--persistent_volumes_account (-pva) [account_name]*: Enter the storage account name from the cluster containing the persistent volumes. This is the exact name of the storage user account that owns the volumes in the cluster.
-.. (Optional) Use parameter help if you need additional information about each parameter:
-+
-* *--help (-h)*: Returns information about each parameter. Parameters are defined as required or optional based on initial deployment. Upgrade and redeployment parameter requirements might vary.
-.. Run the `redeploy-mnode` command.
-
+.. Run the `redeploy-mnode` command. The script displays a success message when the redeployment is complete.
+.. If you access Element or NetApp HCI web interfaces (such as the management node or NetApp Hybrid Cloud Control) using the Fully Qualified Domain Name (FQDN) of the system, link:task_hcc_upgrade_management_node.html#reconfigure-authentication-using-the-management-node-rest-api[reconfigure authentication for the management node^].
 
 [discrete]
 == Find more Information