325816222.doc (156.

00 KB)
8/5/2016 7:49 AM
Last saved by boykot

Update CX4 series array to Release 30

.1

upndu410_R0013

This procedure can be used to:

Load an enabler to the array
Update the FLARE bundle or other array-based software on the array
Update/load a recovery image to the array

Note that this procedure also covers loading FRUMON code packages (which are rebootless
packages) using the Hot Fix Wizard, which is part of USM.
.2

Connect to the storage system from a management station on the same LAN as the primary
management ports of the SP. You cannot use the Service LAN port to perform the upgrade (USM
cannot retrieve diagnostic data).

.3

Running USM:

.a When you have loaded USM on a windows server/laptop with access to both SPs from the
customers LAN, start USM. (You cannot use the Service LAN port to perform the upgrade since
USM cannot retrieve diagnostic data)
.b Log into the storage system to be updated using the IP address of one of the SPs.
Note: If you are unable to login to the SP because of error Security Uninitialized refer to knowledge
base solutions emc101373, emc103955, and emc75148.
.c Enter Engineering mode by pressing Ctrl/shift/F12 and entering the password SIR (case
sensitive). This indicates that you are a service person performing the activity and you are allowed
to Override a failed rule if it can be overridden.
Perform a disruptive upgrade. If you select this, then both SPs will be rebooted at the same
time. Select this option only if the customer has arranged for all attached hosts to be off-line.
You will see Engineering Mode displayed.
.d Select Software, System Software, Install Software.
.e Select Custom Install.
(Express Install is offered if you pre-staged software within the last 2 days. It is OK to accept this
option if it is presented.)
.f Check the box labeled Allow Installation of Diagnostic Tools on SPs if the customer permits this.
Note: This utility (1) checks if there is an active session on the SP, and (2) monitors the processor
utilization and offers steps to reduce it if it is too high to allow the NDU to take place. These steps are
based on the recommendations in emc211113. You can choose to perform any, all, or none of the
steps. If the utilization drops to a satisfactory level after a task has been run, then the remaining steps
are skipped. Any change made will be reset at the end of the NDU.
Note: The utility is removed from the SPs at the end of the NDU.
.g A box labeled Enable Offline Upgrade is shown. If you check this box, then both SPs will be
rebooted at the same time.
Select this option only if the customer has arranged for all attached hosts to be off-line.
WARNING:

325816222.doc (156.00 KB)

8/5/2016 7:49 AM
Last saved by boykot
USM version 1.0.0.1: if you click on the Enable off-line Upgrade check-box, the check-box
does not show that the option has been selected!
-

The only confirmation that this option has been selected is the final screen before the
NDU process begins.

If you are not sure what option you selected, click on the Enable Off-line Upgrade box
again, and repeat the confirmation step.

USM versions 1.0.5.1 and later: the check-box selection will be displayed as expected.
.h The following pop-up is displayed.

If you respond Yes to this pop-up, a disruptive upgrade will be performed.

If you select No a disruptive upgrade will NOT be performed.
.i Any software pre-staged on the SPs is shown for selection. You can choose this or select others to
install instead, which will open a page that will require you to browse to where you have stored the
FLARE bundle.
.j From this point on, follow the steps presented by the Wizard.
.k Investigate any warnings and errors before proceeding with the NDU.
.l There will be a warning if you selected the disruptive upgrade option. Confirm that this is indeed
what you want to do.
.4

Rules Checking
.a If the Rules step Event Log rule takes a long time to complete or an NDU using CLI times out and
returns a failure message: see Knowledgebase solution emc213189 Event log rule takes a long
time to complete when Software Assistant (SA) rules are run
.b If the Rules step appears to hang (takes 20 minutes or longer), it may be that a large event log is
causing the delay. You can perform the following steps:
.a Restart CIMOM this will fail all the rules that have not yet returned so that you can exit the
wizard.
.b Copy off the event logs or run SPCollects to preserve the event log information.
.c Clear the event logs.
If these steps do not resolve the issue, restart CIMOM and use CLI to perform the upgrade.

325816222.doc (156.00 KB)

8/5/2016 7:49 AM
Last saved by boykot
.c If one of the rules fails, one of three options is presented for the rule.
You can fix it if a fix icon appears to the right of the failed rule. Click on the fix icon and
answer the prompt to override the rule.
If no fix icon is visible, hit alt and right-click on the failed icon. If it can be overridden, you
will be shown an override button. Click on this icon. (If a password is requested, type in the
password siw (case sensitive) to override this individual failed rule. Answer the prompt to
override the rule.)
If no fix icon is visible, and no override icon is shown when you hit alt and right-click on the
failed icon, then the rule cannot be overridden. You will have to fix the fault before continuing.
Details of the fault can be obtained by clicking on the fault icon for that rule.
After you have addressed or overridden the failed rule, it may be necessary to click on Rerun to
rerun the rules if the Next button is grayed out.
.5

If the NDU fails to complete, BEFORE performing any attempts to diagnose and address the issue, do
the following:

.a Capture the diagnostic data file created by USM as the very first step in the NDU process. This will
be on the station from which USM was run, in the C:\EMC\repository\DiagnosticData\<serial
number> folder and will be named <date_time>.clariion_Healthcheck_<serial
number>_<date_time>.zip
.b Generate and capture a new diagnostic data file using USM, Diagnostics, Capture Diagnostic
Data. This will contain fresh SPcollects. Again, this will be on the station from which USM was run,
in the C:\EMC\repository\DiagnosticData\<serial number> folder and will be named
<date_time>.clariion_Healthcheck_<serial number>_<date_time>.zip
.c Escalate the issue and provide the 2 diagnostic data files that you captured.
.6

The USM will step you through some post-update tasks:

Committing the software just loaded, if you did not select to have the USM commit the code
automatically for you.

Re-enabling statistics logging if the wizard had you turn it off (if it was enabled prior to the NDU)
Follow the directions given by the utility, including the steps to send the updated system storage
information.
Note: If you do not have Internet connectivity at the time of the upgrade, the file can be uploaded after
the activity by using the Submit Configuration Report option in the left-hand pane and following the
directions given by the Utility. The saved registration file is located at C:\emc\repository\Registration
on the workstation the activity was performed on. If necessary, the file can be copied and sent from a
different computer that has the USM installed and an Internet connection.
.7

Using USM, install the Recovery Image for the FLARE version you have just installed.
This NDU is rebootless.

It does not matter if this has already been loaded; reloading this image will not cause a problem.
.8

Was this an upgrade from Release 28 to Release 30?

If no, go to the next step.

325816222.doc (156.00 KB)

8/5/2016 7:49 AM
Last saved by boykot
If yes, install the Utility Partition for the FLARE version you have just installed, using USM.
This NDU is rebootless.
It does not matter if this has already been loaded; reloading it will not cause a problem.
This must be done because the Release 28 Utility Partition will not support 8GB FC SLICs (introduced
with Release 29) in slot 0. The R30 UP must be present if upgrading from a 4GB FC SLIC to 8GB FC
SLIC in slot 0.
After the NDU

.9

View the event logs of both SPs to ensure there are no unexpected events that could signal a problem
that occurred during or immediately after the NDU

.10

Restart all stopped SAN Copy sessions and any other replication software activities that were stopped
prior to this code load

.11

Is PowerPath running on the hosts?

If no, go to the next step.

If yes, are the LUNs listed under their default owner?
If yes, go to the next step.
If no, perform a powermtrestore. Confirm that all LUNs are now listed under their default owner.
Note: For AIX hosts only: If it is necessary to use the powermtrestore command, see
Knowledgebase article ETA emc163961: AIX, PowerPath: AIX Host Lost access to storage during
powermt restore.
.12

If host operating systems are running native multipath software ask the customer to verify that LUNs
are trespassed back to their default SP owner.

Note: Sancopy source LUNs must be listed to their default owner SP or a Sancopy operation will fail.
.13

If required, upgrade ESRS IP Client for CLARiiON to the version that corresponds to the FLARE that
was upgraded to in this procedure. Even if you are loading a patch version of the bundle, there could
be a new Dial-Home template that must be updated if it has been revised.

.14

Using Unisphere Release Notes and the CLARiiON activity Guide (CAG), check that all host based
and array-based software is at an acceptable/compatible revision. If not, then update as required.

.15

Confirm that there are no array faults (note that the SPS units may still be charging based upon the SP
reboots; this is normal). Write cache will automatically re-enable if it was enabled prior to the NDU as
soon as one SPS is fully charged and ready

.16

Confirm that the cache settings are set properly. If new replication software (layered applications) is
being added, cache settings may not be able to be set as they were previously

.17

Were you instructed earlier to manually disable and zero write cache?

325816222.doc (156.00 KB)

8/5/2016 7:49 AM
Last saved by boykot
If no, go to the next step.
If yes, reset the write cache settings to what they previously were. Use the CLI getcache command to
verify that cache is re-enabled
.18

Are there any unowned private LUNs?

If no, go to the next step.

If yes, refer to EMC Knowledgebase article emc105448. CPLs, WIL private LUNs, or SnapView
reserved pool LUNs may show as un-owned after a code upgrade. If the storage processor (SP) is not
tracking changes, the LUN will be un-owned. Once the clones, mirrors, or snapshots start up, the
ownership will revert to the status of "owned". You can also try dealllocating/reallocating LUNs from
the CPL, WIL, or reserved LUN pool to reinstate ownership to these LUNs. Refer to EMC
Knowledgebase article emc105448 for more information.
.19

Is there a VMware server attached to the array?

If no, go to the next step.

If yes, are all the LUNs are on the same SP?
If no, go to the next step.
If yes, see Knowledgebase solution emc190865 After a non-disruptive upgrade (NDU) all VMware
LUNs are on one storage processor
Table of Contents