330627540.doc (155.

00 KB)
9/22/2016 3:32 PM
Last saved by boykot

Update software on a CX300 series/CX500 series/CX700/CX3 series array

.1

upndu320_R040

This procedure can be used to:

Done

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: FRUMON code packages are rebootless packages which are loaded using the Hot Fix
Wizard, which is part of Unisphere Service Manager. This procedure will also step you through
that process if necessary.
As part of the order, enablers will ship on individual CDs with the array. The FLARE bundles or
other array-based software can also be obtained from the CLARiiON Information section of the
EMC Services Partner Web via Powerlink.
.1 Enablers are shipped to the customer when the customer purchases the product and
should be available on-site during the installation.
.2 For EMC internal and ASP partners only:
Enablers are located on the EMC Services Partner Website, which is accessible from
Powerlink. From the EMC Services Partner website:
Option 1. Select the button for the applicable platform (CLARiiON or VNX), then
Array Based Enablers
Option 2. Select the Software button. Then select (a) Array Based Enablers or (b)
Licensed Software, then Download Enablers.
A table is shown that lists the enablers, OE version supported, whether a reboot is
required, and any applicable notes. Clicking the enabler allows you to download it.
.3 For all other partners:
If you are an EMC implementation partner seeking enabler files for
implementation/installation at your customer's sites then please contact your EMC
Partner relationship manager for guidance on the correct resource and channel from
which to obtain enablers. The enabler is shipped as part of the order on a DVD and
should be available at the customer site.
If your customer is seeking an enabler for an EMC software product, please have them
contact their EMC sales account manager. The sales representative should have
placed an order for the corresponding software. The enabler is shipped as part of the
order on a DVD.
Note: If the patch you are installing contains a new version of FRUMON code, you must wait
until the FRUMON code update is complete before you commit the new FLARE code. Do not
commit the code until the FRUMON update has completed. Write cache must not be reenabled, hot spares must not be rebound, and host I/O must not be allowed until the FRUMON
code update has been confirmed.
.2

Are you updating a CX3-series array?

If yes, go to the step entitled CX3-series Storage Systems only.

CX300, CX300i, CX500, CX500i, CX700 only.

.3

Are you updating from a version of Release 14 prior to 02.07.xxx.5.010?

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
If no, go to the next step.
If yes, you must load the rebootless NDU package called Prep_utility_91841-01.01.5.001.ndu
before you perform an NDU that will reboot the SPs.
.a This is a rebootless NDU and can be done using the array-based Navisphere GUI or the
SIW. The Prep_Utility should be loaded after all standard NDU precautions noted in this
document. It is a rebootless NDU that may take up to 20 minutes to complete. It prepares
the array to be able to do the next NDU to the new software destination without putting
customer data at risk as outlined in and EMC Knowledgebase solution ETA emc91841
.b View the log created by the Prep_utility as follows:
.a When Navisphere (still in Engineering Mode) has reported that the update was
successfully completed, right-click one of the SP icons in the Navisphere GUI.
.b Choose the File Transfer option.
.c The GUI will display all files on the SP available for transfer. Choose/highlight the file
called Prep_utility_91841.log and using the Transfer option, save/transfer it to the
server that you are using to run the browser.
.d Open the file with Notepad and look at the bottom of the one page log for Fixup
completed successfully.
.4

Are you updating from Release 14? (If you are updating from Release 16 or higher, all updates
are online.)
If no, go to the next step.
If yes, this update MAY be an offline NDU depending on the version you are upgrading from.
See the offline/online tables earlier in this procedure which will tell you if this upgrade should
be offline.
Is this an off-line update?
If no, go to the next step.
If yes, refer to the ATA section at the end of this document (module upndu050) which is
part of this procedure. Once that section is complete, return here to continue the NDU
procedure.

.5

Is this storage system running MirrorView/S?

If no, go to the next step.

If yes, did the system ever run a version of FLARE earlier than Release 19?
If no, go to the next step.
If yes, was the system then updated to any version of Release 19 .prior to patch .030 AND
the WIL was enabled during that NDU (refer to EMC Knowledgebase article emc135038)?
If no, go to the next step.
If yes, the data in the write intent logs (WIL) may not be correct.
Exposure to the problem is highlighted below and in EMC Knowledgebase article
emc135038.
Exposure - A CX-Series array that was running any version of FLARE less than
Release 19 and was updated to Release 19 less than patch .030 and the WIL was
enabled during that NDU. An SP reboot now (NDU included) could cause the WIL to
2

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
be faulted.
No Exposure - A CX-Series array that was running any version of FLARE less than
Release 19 then updated DIRECTLY to Release 19 patch .030 or higher (never ran a
lower Release 19).
No Exposure Any CX-Series array that was first INSTALLED with any version of
Release 19.

Is there any possibility that this array is exposed to this issue?

If no, go to the next step.
If yes, run the script available for download at the bottom of EMC Knowledgebase
article emc135038.
When the script is run, it will have one of three possible recommended actions for
you to do prior to the NDU you are about to do:
a. RecommendedAction:
Donothing;Noproblemsfound.

or
b. RecommendedAction:
MirrorsecondarycorruptionpossibleifanSPreboots.
DisableanddeallocateWILLUNs.
ReallocateWILLUNsandreenableWILs.

or
c.

RecommendedAction:
Mirrorsecondarycorruptionpossible.
a. DisableWILsanddeallocateWILLUNs.
b. Removeandreaddsecondaryimageswithsyncrequired
toresyncallmirrors.
c. ThenreallocateWILLUNsandreenableWILs.

Perform the recommended action (if any).

.6

Are you upgrading from a version of FLARE lower than Release 19?
If yes, then you must use Navisphere Service Taskbar to perform the update. Go to the step
labeled Updating from FLARE versions below Release 19 (NST)

If no, then you can use Unisphere Service Manager to perform the update. Go to the step
labeled Updating from FLARE version Release 19 and later (USM)
Updating from FLARE versions below Release 19 (NST)

.7

After loading the NST to a windows server/laptop with access to both SPs from the customers
LAN, or with a connection to one of the Service LAN ports (CX3-Series only), start the NST.
.a Select the Software Assistant option.
.b Select Install Software (Step 2).
.c A Connection window is displayed.
CX-Series or CX3-Series: If using the customers LAN, type in the IP address of one of

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
the SPs.
CX3-Series only: If you connected using the service LAN port, select the Options, NAT
connection and supply the IP addresses of BOTH SPs even though you are only
connected to one SP. For CX3-Series storage systems, the Service LAN has the
following factory set IP addresses:
SP-A: 128.221.1.250 (port is on SP-B or Management FRU-B)
SP-B: 128.221.1.251 (port is on SP-A or Management FRU-A)
.d The Login screen for Navisphere will appear. Enter the appropriate username and
password.
Note that once you connect to a storage system, you do not need to reconnect to it again
during the same NST session. To connect to a different storage system, you must
disconnect the current storage system by selecting File > Disconnect.
.e IMPORTANT: 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
Use this tool to update most storage systems running FLARE version 02.05 and
higher, 03.22 and higher. (Customers may only use the tool for 02.19 and higher,
03.22 and higher.)
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.
.f Select Custom Install. (Express Install will be offered if you pre-staged software within the
last 2 days. It is OK to accept this option if it is presented.)
.g A checkbox CX3 only: Allow Installation of Diagnostic Tools on SPs can be seen.
Disregard this message; it only applies to CX3 systems, not to CX systems.
.h 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.

CAUTION: This option must only be used if all hosts are off-line.
.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.
.8

Rules Checking

.a The Software Assistant Event Log rule may report that it cannot access the event log and
issue a warning. This problem will occur when a storage system is set up with incorrect
zoning and SAN Copy or MirrorView/A is enabled. It will not be seen in any case when a
4

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
storage system zoning is correctly configured. This will not prevent the NDU from
occurring, but the message issued does not reflect that a possible zoning configuration
error could be the cause. See EMC Knowledgebase article emc148512 for more
information.
.b If the 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
.c 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.
.d If the drive firmware rule fails (CX series only), then consult EMC Knowledgebase article
emc158525 and run the check listed in that solution.
If no drives are found when the exception bit tool is run, then it is OK to override the rule
(see below).
If drives have to be updated, then do that before retrying this FLARE upgrade.
Note: The drive firmware rule may still fail after doing the drive firmware upgrade,. The
Software Assistant checks for the presence of the drive firmware and FLARE combinations. It
does not contain the check exception bit utility that determines if the drives really need to be
updated. If you have verified the drives, and are confident that there are none to be updated,
then override the rule as detailed below.
.e Processor Utilization rule may report that the utilization is too high to proceed.
Perform the following steps in the stated order and rerun the rules after each step:
If not already done, disable statistics logging (there will be an option on the Rules
screen to do this)
Reduce I/O as much as possible
Disable write cache (see Appendix: Disabling write cache located at the end of this
procedure) and wait until this has completed
Shut down one or more hosts if possible
See Knowledgebase solutions
emc204935 What SP utilization rate value will cause a CLARiiON non-disruptive
upgrade (NDU) to fail?
emc211113 Troubleshooting checklist for when a non-disruptive upgrade (NDU)
cannot proceed because a rules check has failed
If the rule still fails, then escalate to obtain assistance in determining the cause of the
CPU Utilization. If you are then sure that it is OK to bypass the utilization rule, then
do so.
Remember to re-enable write cache if necessary when the update completes, before
leaving the site.
.9

Did any rule fail?

If no, go to the next step.

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
If yes, one of three options is presented:
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,
an override button is shown. 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 failure can be obtained by clicking on the fault icon for that rule.
Note: 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.
.10

The Software Assistant steps you through some post update tasks, which include:
Committing the FLARE just loaded.
Note that Software Assistant will not commit the new FLARE code until FRUMON updates
have completed. The LCCs in any attached DAE chassis will automatically perform
FRUMON code updates immediately after the FLARE update is complete. Do not commit
the code until the FRUMON update has completed.
To verify that the FRUMON code has been applied either:
Perform a getcrus command to determine the version of ATA LCC/BCC FRUMON
code:
navisecclih<SP_IP_address>getcruslccrevalccrevb

-or In Navisphere Manager, expand the arrays navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC.
Right-click on the icon for either SP As or SP Bs ATA LCCs/BCCs and select Resume
from the pop-up menu.
-or From the Navisphere Service Taskbar Toolbar, select Tools, Disk Enclosure Firmware
(FRUMON) Status.
The LCCs requiring update and their update status (details available) are displayed.
Check that the FRUMON code versions shown are as expected.
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 Register Storage System utility found under Hardware
Registration in the NST task bar. Select Register storage system from saved data and

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
follow the directions given by the Utility.
The saved registration file is located at
C:\emc\repository\ARU on the workstation the activity was performed on. If necessary, the file
can be copied and sent from a different computer that has the NST installed and an Internet
connection.
.11

Using Software Assistant, 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.
Note: For CX-series systems, there must be a drive 0_0_4 in the array for this NDU to work.
Note: If you just upgraded to Release 26, patch version up to and including patch .011, and
then loaded the recovery image, reboot that targeted SP after you load the image. If you do
not, then there is a chance of a bugcheck if the next NDU is also to a Release 26 patch
version, up to and including patch .011. (See Knowledgebase article emc179061 NDU from
Release 26 to higher revision of Release 26 may fail with bugcheck for details).
.12

Does the storage system have ATA enclosures (ATA drives)?

If no, go to the next step.
If yes, the FRUMON code contained in R24 patch .011 and earlier does not contain ATA
FRUMON 1.95. If this storage system contains ATA enclosures and you are upgrading to R24
patch .011 or earlier, it is recommended that you load this FRUMON code after performing the
upgrade to R24. Later versions of R24 are not affected. See Knowledgebase article
emc155543 for full details.
What is the current version of ATA LCC (BCC) FRUMON code on the storage system? Use
one of the following methods to determine the version:
CLI: getcruslccrevalccrevb
Navisphere Manager: Physical > DAE-ATA > LCC (or BCC),Resume
Navisphere Service Taskbar: Tools, Disk Enclosure Firmware (FRUMON) Status.
Are any of the FRUMON code versions shown lower than the current recommended level?
If no, go to the next step.
If yes, then the FRUMON code must be updated using the Hot Fix Wizard in the NST.
Note: The FRUMON update may take up to an hour to complete, and once you start it, you
should not leave until you have checked that it has successfully completed.
Note: The Hot Fix Wizard can only be used to load software that does not require a storage
system reboot. The Hot Fix Wizard will check the software being installed and will not allow
installation of inappropriate packages. However, the Hot Fix Wizard does not differentiate to
the patch level. If you are running a version of FLARE that is lower than R14 patch .016
(02.07.xxx.5.016), then you must not apply this FRUMON code.
.a Start the Navisphere Service Taskbar if necessary.
.b Select Software Assistant.
.c Select Download and Install Hot Fix if you do not already have the FRUMON code

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
or- Select Install Hot Fix if you have already downloaded the code.
.d If the Select Storage System to Connect screen opens, enter SP A or SP B IP address,
click Connect, enter your Navisphere login username, password, and account type (global
or local) and click OK.
.e Follow the directions given by the utility, including the steps to send the updated system
storage information.
.f The FRUMON code on the ATA LCCs/BCCs in any attached ATA DAE chassis is updated.
Note that even though the Hot Fix Wizard completes, the FRUMON upgrade may take up to
an hour to complete.
.g To confirm that the FRUMON code update is complete, check the SP Event log for each SP.
The following event should be in both SP Event logs:
(778)LCCFirmwareUpgradecompleteonall

.h To verify that the FRUMON code has been applied, either:

Perform a getcrus command to determine the version of ATA LCC/BCC FRUMON
code:
navisecclih<SP_IP_address>getcruslccrevalccrevb

-or In Navisphere Manager, expand the arrays navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC.
Right-click on the icon for either SP As or SP Bs ATA LCCs/BCCs and select Resume
from the pop-up menu.
-or From the Navisphere Service Taskbar Toolbar, select Tools, Disk Enclosure Firmware
(FRUMON) Status.
The LCCs requiring update and their update status (details available) are displayed.
Check that the FRUMON code versions shown are as expected.
Note: If any of the ATA LCCs/BCCs does not update to the new version, then repeat this
update step (i.e. reload the rebootless package).
.i View the event logs of both SPs to ensure there are no unexpected events that could signal
a problem.
.13

Go to the step labeled After the NDU

CX3-Series Storage Systems only

.14
.15

Updating from FLARE version Release 19 and later (USM)

Running USM:
.a When you have loaded USM on a windows server/laptop with access to both SPs from the
customers LAN: (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.

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
.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, unless the
customer does not allow it to be installed. (No reboot is required to install this utility.)
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.
Note: Timings for the new tasks (typical, approximate timings): Installation of the utility: 5
minutes, No Active Login Check: 5 minutes, Utilization assessment: 2 minutes, Disable
Write Cache: 1.5 minutes to check and fix (normally this task alone will reduce processor
utilization to an acceptable level), Disable Alert Provider: 1 minute to check and fix,
Minimize Management Overhead: 10 minutes to check and fix, Reboot SP: 30-35 minutes.
Note: When the utility is not loaded, the old Processor utilization check will run and take
about 3 minutes.
.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 offline.
WARNING:
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.

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
.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 will be 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 There will be a warning if you selected the disruptive upgrade option. Confirm that this is
indeed what you want to do.
From this point on, follow the Wizard by selecting your software to download. Follow the steps
presented by the wizard. Investigate any warnings and errors before proceeding with the
NDU.
.16

Rules Checking

.a The Event Log rule may report that it cannot access the event log and issue a warning.
This problem will occur when a storage system is set up with incorrect zoning and SAN
Copy or MirrorView/A is enabled. It will not be seen in any case when a storage system
zoning is correctly configured. This will not prevent the NDU from occurring, but the
message issued does not reflect that a possible zoning configuration error could be the
cause. See EMC Knowledgebase article emc148512 for more information.
.b If the 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
.c 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.
.d Processor Utilization rule may report that the utilization is too high to proceed.
Did you load the utility above?
If no, perform the following steps in the stated order and rerun the rules after each step:

10

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
If not already done, disable statistics logging (there will be an option on the Rules
screen to do this)
Reduce I/O as much as possible
Disable write cache (see Appendix: Disabling write cache located at the end of this
procedure) and wait until this has completed
Shut down one or more hosts if possible
See Knowledgebase solutions
emc204935 What SP utilization rate value will cause a CLARiiON non-disruptive
upgrade (NDU) to fail?
emc211113 Troubleshooting checklist for when a non-disruptive upgrade (NDU)
cannot proceed because a rules check has failed
If the rule still fails, then escalate to obtain assistance in determining the cause of the
CPU Utilization. If you are then sure that it is OK to bypass the utilization rule, then
do so.
Remember to re-enable write cache if necessary when the update completes, before
leaving the site.
If yes, follow the steps shown by the Processor Utilization Mitigation utility.
.17

Did any rule fail?

If no, go to the next step.

If yes, one of three options is presented:
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,
an override button is shown. 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 failure 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.

.18

The USM will take you through some post update tasks, which include:
Committing the FLARE just loaded.
Note that the new FLARE code will not be committed until FRUMON updates have
completed. The LCCs in any attached DAE chassis will automatically perform FRUMON
code updates immediately after the FLARE update is complete. Do not commit the code
until the FRUMON update has completed.
To verify that the FRUMON code has been applied either:
Perform a getcrus command to determine the version of ATA LCC/BCC FRUMON code
naviclih<SP_IP_address>getcruslccrevalccrevb

or
navisecclih<SP_IP_address>getcruslccrevalccrevb

11

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
-or Navisphere Manager: Expand the arrays navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC, right-click on the icon for either SP As or SP Bs
ATA LCCs/BCCs and select Resume from the pop-up menu.
Unisphere: Select the storage system, System, Hardware and expand each DAE
and/or SP to the LCC level and select View Resume
-or In USM, Hardware, Hardware Installation, select Tools, Disk Enclosure Firmware
(FRUMON) Status.
The LCCs requiring update and their update status (details available) are displayed.
Select Show details. The current LCC FRUMON code is displayed.
Check that the FRUMON code versions shown are as expected.
Re-enabling statistics logging that the wizard had you turn off (if it was enabled prior to the
NDU)
Perform the steps to send the updated system storage information.
NOTE: If you do not have Internet connectivity at the time of the upgrade, make sure to follow
the instructions given by the NST Storage System Registration Wizard. The file can be
uploaded by the service provider after the activity by using the Register Storage System utility
found under Hardware Registration in the NST task bar. Select Register storage system
from saved data and follow the directions given by the Utility. The saved registration file is
located at C:\emc\repository\ARU on the workstation the activity was performed on. If
necessary, the file can be copied and sent from a different computer that has the NST installed
and an Internet connection.
.19

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.
After the NDU

.20

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

.21

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

.22

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 powermt restore. Confirm that all LUNs are now listed under their default
owner.
Note: For AIX hosts only: If it is necessary to use the powermt restore command, see
Knowledgebase article ETA emc163961: AIX, PowerPath: AIX Host Lost access to storage

12

330627540.doc (155.00 KB)

9/22/2016 3:32 PM
Last saved by boykot
during powermt restore.
.23

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.
.24

Upgrade remote support to the latest available ESRS IP Client for CLARiiON software
package. Re-run the CPG for remote support upgrade procedures choosing the appropriate
remote support configuration type that is implemented at this customer site.

.25

Using Navisphere 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.

.26

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

.27

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

.28

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

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
.29

Are there any unowned private LUNs?

If no, go to the next step.

If yes, refer to EMC Knowledgebase article emc105448. If updating from Release 16 it is not
uncommon to see CPLs, WIL private LUNs, or SnapView reserved pool LUNs un-owned after
a code upgrade. If the storage processor (SP) is not tracking changes, the LUN will be unowned. 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.
.30

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

13