How to update the ThinkSystem DM Series Storage controller firmware using the Lenovo Data ONTAP CLI
How to update the ThinkSystem DM Series Storage controller firmware using the Lenovo Data ONTAP CLI
How to update the ThinkSystem DM Series Storage controller firmware using the Lenovo Data ONTAP CLI
Description
This article introduces the procedure used to perform an automatic nondisruptive upgrade of the ThinkSystem DM Series Storage controller firmware using the Lenovo Data ONTAP CLI. You should regularly upgrade the controller firmware to make sure you have all the latest features and bug fixes. Before proceeding, ensure that all the data has been backed up properly, that the storage array and all drives have an Optimal status, and that no configuration changes are running on the storage array. Upgrading or downgrading a cluster to the current ONTAP release requires planning, preparation, the upgrade or downgrade itself, and several post-upgrade or downgrade procedures. You can use the CLI to verify that the cluster can be upgraded nondisruptively, install the target ONTAP image on each node, and then, execute an upgrade in the background.
Applicable Systems
ThinkSystem DM Series Storage Arrays
Before you begin
- You must have met the upgrade preparation requirements.
- For each storage array, each node should have one or more ports on the same broadcast domain.
- When a set of nodes is upgraded during a batch upgrade, the LIFs are migrated to the partner nodes. If the partners do not have any ports in the same broadcast domain, then the LIF migration will fail.
The software update process includes the following phases:
- Planning for the update
- Preparing for the update
- Performing the update
- Completing post-update tasks
For more detailed information, refer to the following page: Updating software on ONTAP clusters.
Installation Procedure
- Download the firmware update file from the Lenovo DCG Support Website.
- Navigate to support.lenovo.com.
- Enter a valid DM Series machine type in the search box, and then select the page for the machine type.
- Select the Drivers & Software tab.
- In the Warranty check area in the top right corner, enter a valid DM Series serial number.
- Expand the Product Firmware option.
- Download the desired controller firmware update bundle and save it to an http, https, or sftp, ftp server.
- The ftp server must be configured with no authentication. The http server must use port 80 for file download.
- Use SSH to connect to the cluster management IP address.
- In the examples shown here, PuTTY will be used.
- Open PuTTY, enter the HostName (or IP address), and then select SSH as the Connection type.
- Click Logging under the Session tree on the left.
- Select Printable Output.
- In the Log file name field, enter a name for the file, click Browse to select a folder for it to be saved in.
- Click Open and then log in to the Lenovo Data ONTAP CLI with your admin account and password.
- Verify the current cluster image and software repository.
- At the prompt enter cluster image show, and then cluster image package show-repository.
DM5000H::> cluster image show Node Current Version Installation Date -------------------- ----------------------- ------------------- DM5000H_1 9.7P5 7/30/2020 14:57:12 DM5000H_2 9.7P5 7/30/2020 14:57:40 2 entries were displayed. DM5000H::> cluster image package show-repository Package Version Package Build Time ---------------- ------------------ 9.6P5 12/13/2019 18:21:56 9.7P5 6/23/2020 04:02:30 2 entries were displayed. DM5000H::>
- To delete the previous ONTAP software package, enter cluster image package delete -version {previous_ONTAP_Version}
DM5000H::> cluster image package delete -version 9.6P5 Package Delete Operation Completed Successfully
- To download the target ONTAP software package, enter cluster image package get -url {location}
DM5000H::> cluster image package get -url http://10.10.0.221/DM%20Updates/lnvgy_fw_storage_97P9E_anyos_noarch.tgz.gz Package download completed. Package processing completed.
- To verify that the software package is available in the cluster package repository, enter cluster image package show-repository
DM5000H::> cluster image package show-repository Package Version Package Build Time ---------------- ------------------ 9.7P5 6/23/2020 04:02:30 9.7P9 11/6/2020 01:13:45 2 entries were displayed.
- To verify that the cluster is ready to be upgraded nondisruptively, enter cluster image validate -version {package_version_number}
- If you are upgrading a two-node or four-node MetroCluster configuration, you must run this command on all nodes before proceeding.
- If you are upgrading from ONTAP 9.4 to 9.7, use the 9.7 package for verification. You do not need to validate the 9.5 package separately.
Note: The cluster image validate command checks the cluster components to validate that the upgrade can be completed nondisruptively. It then provides the status of each check and any required action you must take before performing the software upgrade. The system will perform validation and return warning messages for any issues discovered.
DM5000H::> cluster image validate -version 9.7P9 It can take several minutes to complete validation... WARNING: There are additional manual upgrade validation checks that must be performed after these automated validation checks have completed successfully. Refer to the Upgrade Advisor Plan or "Performing manual checks before an automated cluster upgrade" section in the "Clustered Data ONTAP Upgrade Express Guide" for the remaining manual validation checks that need to be performed before update. Failing to do so can result in an update failure or an I/O disruption. Validation checks started successfully. Run the "cluster image show-update-progress" command to check validation status.
- To monitor the progress of the validation, enter cluster image show-update-progress
DM5000H::> cluster image show-update-progress
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:00:58
Details:
Pre-update Check Status Error-Action
-------------------- ----------------- --------------------------------------
CIFS status Warning Warning: CIFS is currently in use.
Any unprotected sessions may be
affected with possible loss of data.
Action: Stop all unprotected CIFS
workloads before performing the
update.To list the unprotected CIFS
workloads, run the command: vserver
cifs session show
-continuously-available No, Partial
Manual checks Warning Warning: Manual validation checks
need to be performed. Refer to the
Upgrade Advisor Plan or "Performing
manual checks before an automated
cluster upgrade" section in the
"Clustered Data ONTAP Upgrade Express
Guide" for the remaining validation
checks that need to be performed
before update. Failing to do so can
result in an update failure or an I/O
disruption.
Action: Refer to the Upgrade Advisor
Plan or "Performing manual checks
before an automated cluster upgrade"
section in the "Clustered Data ONTAP
Upgrade Express Guide" for the
remaining validation checks that need
to be performed before update.
SAN compatibility Warning Warning: Since this cluster is
configured for SAN, manually confirm
that the SAN configuration is fully
supported.
Action: Refer to the NetApp
Interoperability Matrix Tool for
interoperability information.
3 entries were displayed.
- Complete all the required actions identified by the validation.
- Required: To generate a software upgrade estimate, enter cluster image update -version {package_version_number} -estimate-only
- The software upgrade estimate displays details about each component to be updated, and the estimated duration of the upgrade.
DM5000H::> cluster image update -version 9.7P9 -estimate-only Cluster Items Requiring Component Updates Estimated Duration --------------------- ----------------- ----------------------------------- Node Updates 2 92 minutes Component Component ID Current Version Updated Version Estimated Duration --------- ------------ --------------- --------------- ------------------ Node DM5000H_1 9.7P5 9.7P9 31 minutes Node DM5000H_2 9.7P5 9.7P9 31 minutes 2 entries were displayed.
- To perform the software upgrade, enter cluster image update -version {package_version_number}
DM5000H::> cluster image update -version 9.7P9
Starting validation for this update. Please wait..
It can take several minutes to complete validation...
WARNING: There are additional manual upgrade validation checks...
Pre-update Check Status Error-Action
--------------------- ---------- --------------------------------------------
...
3 entries were displayed
Would you like to proceed with update ? {y|n}: y
Starting update...
DM5000H::>
- If the cluster consists of two through six nodes, a rolling upgrade will be performed. If the cluster consists of eight or more nodes, a batch upgrade will be performed by default. If desired, you can use the -force-rolling parameter to specify a rolling upgrade instead.
- After completing each takeover and each giveback, the upgrade waits for 8 minutes to enable client applications to recover from the pause in I/O that occurs during the takeover and giveback. If your environment requires more or less time for client stabilization, you can use the -stabilize-minutes parameter to specify a different amount of stabilization time.
- To display the cluster update progress, enter cluster image show-update-progress
DM5000H::> cluster image show-update-progress
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:00:59
Data ONTAP updates in-progress 01:32:00 00:03:00
Details:
Node name Status Status Description
-------------------- ----------------- --------------------------------------
DM5000H_1 waiting
DM5000H_2 in-progress Performing takeover operation.
8 entries were displayed.
Note: If you are upgrading a four node or eight node MetroCluster configuration, the cluster image show-update-progress command only displays the progress for the node on which you run the command. You must run the command on each node to see individual node progress.
- To verify that the upgrade was completed successfully on each node, enter cluster image show-update-progress
DM5000H::> cluster image show-update-progress
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:00:59
Data ONTAP updates completed 01:32:00 01:29:00
Post-update checks completed 00:10:00 00:01:39
3 entries were displayed.
Updated nodes: DM5000H_1, DM5000H_2.
DM5000H::>
- Trigger an AutoSupport notification: autosupport invoke -node * -type all -message "Finishing_NDU"
- If your cluster is not configured to send AutoSupport messages, a copy of the notification will be saved locally
Additional Information
Document ID:HT511575
Original Publish Date:12/16/2020
Last Modified Date:10/19/2023
