Unity P Software Upgrades
Unity P Software Upgrades
Version 4.3
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
Preface 5
Chapter 1 Introduction 7
About this document.................................................................................... 8
Types of software updates........................................................................... 8
Information on changes and new features in a release..................................8
DANGER
WARNING
CAUTION
NOTICE
Note
Introduction 7
Introduction
This chapter includes information that you must review before performing an upgrade:
Note
OE software updates sometimes include system firmware updates. In such cases, the
upgrade may take a bit longer to complete.
l Upload a File: If there are other images available on your system, but you
want to upload a file now by navigating to a previously downloaded image file
on your local machine.
8. Select the checkbox if you want the storage processors to reboot automatically
during the upgrade. For more information, see Automatically reboot storage
processors on page 15
9. Review the planned upgrade and select Finish.
Results
The screen shows the progress of the upgrade as both storage processors are
upgraded and rebooted.
Note
If you did not select the option to reboot the storage processors automatically, the
upgrade process will pause before rebooting the first storage processor, and wait for
your input to proceed with the upgrade.
Note
All system components must be healthy, prior to upgrading the system. If any system
components are degraded, the update will fail. Perform a system health check on page
20 explains how to run a health check on the system.
Attribute Description
Status Current status of the upgrade session. Value is one of the
following:
l running — Session is upgrading the system software.
l completed — Session has completed upgrading the
system software.
l paused— Upgrade session has paused before rebooting
the SPs.
l failed— Upgrade session has failed.
Creation time Date and time the upgrade session was created.
Elapsed time Amount of time that the upgrade session has been running.
Estimated time left Estimated time required to complete the upgrade session.
Format
/sys/soft/ver [{-id <value>|-type {installed|candidate|
downloaded}}] show
Object qualifier
Qualifier Description
-id Type the ID of the system software.
-type Type the software type. Value is one of the following:
l installed — View the version of the system software that is
installed.
l candidate — View the version of the system software upgrade
candidate that was uploaded to the system.
l downloaded — Software image that was automatically pushed to the
system by support.
Example
The following command displays details about the installed system software and an
uploaded upgrade candidate:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/soft/ver show
1: ID = INST_1
Type = installed
Version = 4.3.0.1498853411
Release date = 2017-06-30 23:33:44
Image type =
Reboot required =
Pause allowed =
Image filename =
2: ID = CAND_1
Type = candidate
Version = 4.3.0.1502142551
Release date = 2017-08-08 05:19:50
Image type = software
Reboot required = yes
Pause allowed = yes
Image filename = Unity-c4dev_PIE_471-
upgrade-4.3.0.1502142551-4.3.0.1502142551-GNOSIS_DEBUG.tgz.bin
3: ID = ASD_1
Type = downloaded
Version = 4.2.0.9215195
Release date =
Image type = software
Reboot required =
Pause allowed =
Image filename = Unity-_dev_001-
upgrade-4.2.0.9215195.9215195-4.2.0.9215195.9215195-
GNOSIS_DEBUG.tgz.bin.gpg
4: ID = ASD_2
Type = downloaded
Version = V2-Dec-19-2016
Release date =
Note
Before upgrading the system software, a system health check must be performed. All
system components must be healthy prior to upgrading the system software. If any of
the system components are degraded, the software update will fail.
Format
/sys/general healthcheck
Example
The following command performs a health check of the system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/general
healthcheck
Note
l The results of the health check may show errors and warnings, but a message of
Operation completed successfully. displays in the output. This is only an
indication that the health check action was performed, not that it was successfully
completed without errors and warnings. Attempt to resolve all errors and rerun the
health check.
l If errors occur, a system software upgrade is not allowed. If warnings occur, they
can be bypassed during the upgrade procedure.
candidate file to the system, use an upgrade session to start the upgrade process.
Create upgrade sessions on page 21 explains configuring upgrade sessions.
Prerequisites
Download the latest system software upgrade candidate from the support website.
Format
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! -upload -f
<file> upgrade
Options
Qualifier Description
-f Type the path and file name of the upgrade candidate file to upload. Wrap
the path and file name in quotes.
Example
The following example upload a upgrade candidate file to the system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! -upload -f
“upgrade-2.0.0.12190-MAGNUM-RETAIL.tgz.bin” upgrade
NOTICE
Do not use Unisphere or Unisphere CLI to manage or configure the system during a
software upgrade.
Format
/sys/upgrade create –type { software [–candId <value>] [-
pauseBeforeReboot] | sp -newSPModel <value>} [-offline]} [-
pauseBetweenReboots]
Action qualifiers
Qualifier Description
-candId Type the ID of the uploaded upgrade candidate. View
system software versions on page 18 explains how to
view the ID of the uploaded software candidate.
Note
Qualifier Description
-pauseBeforeReboot Specify whether to pause during the upgrade,
executing all tasks before the SPs reboot.
Note
Example 1
The following command creates a session to upgrade the system software:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/upgrade create
–type software
Note
All warning messages, if any, appear the first time you run the upgrade process. When
a potential issue results in a warning message, the upgrade process stops. Once you
review the warning message, run the upgrade command again to continue with the
upgrade process. This time the upgrade process will run the checks again, but it will
not stop for any warnings. The upgrade process will only stop when an error occurs.
Example 2
The following command creates a session to upgrade the storage processor:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/upgrade create
–type sp –newSPModel SP500
Example 3
The following command initiates an offline DIP upgrade.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/upgrade create
-type sp -newSPModel SP500 -offline
Example 4
The following command initiates a software upgrade that pauses after the first SP
reboots.
uemcli /sys/upgrade create -type software -pauseBetweenReboots
Note
The show action command on page 24 explains how to change the output format.
Format
/sys/upgrade show
Example 1
The following command displays details about the hardware upgrade session:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/upgrade show
1: Type = SP
Status = Running
Status message =
Creation time = 2015-11-09 19:43:08
Elapsed time = 01h 3m 08s
Estimated time left = 01h 70m 00s
Progress = Task 2 of 5 (Running health checks)
Percent complete = 5%
Example 2
The following command displays details about the software upgrade session:
1: Type = Software
Status = Failed
Status message = Stopping c4 stack on SPA timeout
expired
Creation time = 2009-11-09 18:04:12
Elapsed time = 00h 20m 08s
Estimated time left =
Progress = Task 5 of 25 (Stopping c4 stack on SPA)
Percent complete = 15%
Example 3
The following command shows an issue with the pre-upgrade health check in
Additional info.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /sys/upgrade show -
detail
1: Type = Software
Status = Failed
Creation time = 2009-11-09 18:04:12
Elapsed time = 00h 20m 08s
Estimated time left =
Progress =
Percent complete = 5%
Additional info = "Error: The health check has failed.
An internal error is preventing the health check from completing
successfully. Record the error code and search the EMC Online
Support website for available support options. [Error Code:
platform::check_boot_control_status_2]","Error: One or more LUNs
are in degraded state. Record the error code and contact your
service provider. [Error Code:
flr::check_if_lun_recovery_is_required_2]"
Action qualifier
Qualifier Description
-output|-o Specify the output format. Value is one of the following:
l nvp — The name-value pair (NVP) format displays output as
name=value. Name-value pair format on page 25 provides an
example of the NVP format.
l table — The table format displays output as a table, with
column headers and rows. By default, values that are too long to
fit in a column are cut off. Add -wrap after the table qualifier,
separated by a space, so that the values wrap. Table format on
page 25 provides an example of the table format.
l csv — The comma-separated values (CSV) format is similar to
the table format, but the names and values are separated by
commas. Comma-separated values format on page 25 provides
an example of the CSV format.
1: ID = la0_SPA
SP = SPA
Ports = eth0_SPA,eth1_SPA
Health state = OK (5)
2: ID = la0_SPB
SP = SPB
Ports = eth0_SPB,eth1_SPB
Health state = OK (5)
Table format
ID,SP,Ports,Health state
la0_SPA,SPA,”eth0_SPA,eth1_SPA”,OK (5)
la0_SPB,SPB,”eth0_SPB,eth1_SPB”,OK (5)
Example
The following command modifies the set of attributes in the show action output. For
example, if you add -filter "ID,ID,ID,ID" to the command, in the output you will see
four lines with the "ID" attribute for each listed instance:
1: ID = la_0
ID = la_0
ID = la_0
ID = la_0
uemcli /net/nas/server show -filter “ID, SP, Health state, ID, Name”
Filter format
1: ID = nas_1
SP = SPA
Health state = OK (5)
ID = nas_1
Name = Mynas1
2: ID = nas_2
SP = SPA
Health state = OK (5)
ID = nas_2
Name = Mynas2
Note
The checksum value appears when you click the Checksum link that appears
with each downloadable upgrade file listed on the Downloads page of the
support website for the system.
2. On the system where the upgrade file is downloaded, do one of the following:
l On a Linux-based system, run the command: sha256sum <downloaded
upgrade file name>.
l On a Windows-based system, use one of the open source or freeware
applications to calculate the checksum value.
3. Compare the checksum value generated for the upgrade file with the one you
noted in Step 1.
Matching values indicate the upgrade file is intact and not corrupt.
l For upgrades that terminated unexpectedly—Select the Settings icon, and then
select Software and Licenses > Software Updates and review information about
the upgrade candidate. Try running the upgrade again.
l For upgrades that failed—The Software Updates page lists the errors the system
encountered during the update. Select the Settings icon, and then select
Software and Licenses > Software Updates and review information about the
upgrade candidate. Try running the upgrade again.
l If you recently added new hardware, new disks and other similar hardware
components, they may be on an incompatible image or you may not have
configured them yet. New ports must be committed before they can be used, for
example. Plan downtime and restart the entire system. When the system starts up,
during the power-on self test, it will check for new firmware images and update all
or any parts to latest images as required, self-healing the box. Once this is
complete, try running the upgrade again.
l Before contacting support, access the Unisphere Online Help (click the Help icon
in the top-right corner of the Unisphere screen) or the knowledgebase in the
Online Support website for more information on steps you can take to fix the
issue.
If none of the options above help resolve the issue, do not apply in your scenario,
or if you are not sure about the issue causing the failure, go to Support > Contact
Us > Chat to chat with support personnel. If this option is not available, contact
your service provider.