330584751.doc (187.

00 KB)
9/22/2016 9:18 AM
Last saved by boykot

Prepare CX300, 500, 700, and CX3 series for update to Release 24 and above
upndu310_R083

General Notes
.1

CX200, CX400, CX600 cannot be upgraded to Release 24 or later.

Storage systems running Release 14, Release 16 or a version of Release 19 that is earlier than
patch .044, must upgrade to Release 19 patch .045 as an intermediate step, i.e. Release
14/16/17/19 Release 19 .045 Release 24, or Release 26 prior to patch .025. See
emc200423: CX Series storage processor panics when upgrading from FLARE Release 14, 16,
17, or Release 19 patches earlier than .044 to FLARE Release 24, or Release 26 prior to patch .
025.

Done

Do not upgrade directly to Release 24, or Release 26 prior to patch .025; there is a risk that the
NDU may fail.
.2

Are you upgrading from Release 22 patch 005?

If no, go to the next step.
If yes, are you upgrading to Release 26 patch .031?
If no, go to the next step.
If yes, does this storage system have DAE3P enclosures?
If no, go to the next step.
If yes, you will have to perform an interim upgrade before upgrading to R26 patch .031. See
Knowledgebase article emc248896 Enclosure speed mismatch after non-disruptive upgrade
(NDU) for details.

.3

During this procedure, each storage processor will reboot independently. Therefore, it is imperative
that all servers have access to both storage processors in the array and have properly
configured/working failover software or they will lose access to the array.
It is the customer's responsibility to check non-EMC host-based software and host hardware for
supported levels, HBA settings etc.
Ensure that the customer is aware of this and has made any necessary updates.
If necessary, explain what happens during an NDU.
Refer them to Knowledgebase solution emc231912 which gives the following information
.a The following page on Powerlink: Home > Support > Product and Diagnostic Tools > CLARiiON
Tools > CLARiiON Software Update Tools > CLARiiON Software Update (Standard). The
customer should perform Step 2 to run HAVT (High Availability Verification) for all servers attached
to the storage system, and then Step 3 to run the Prepare for Install portion of the Software
Assistant to verify that all servers are in an expected availability state.
.b The Technical Advisories that appear when USM is launched. These warn of issues that could
affect the upgrade.
.c Knowledgebase solution emc99467: What are the Initiator, Arraycommpath, and Failovermode
settings for PowerPath, DMP, PVLinks, and native failover software?
.d Knowledgebase solution emc203900: How EMC helps customer to maintain supported

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
architecture. This is a general document covering Symmetrix, CLARiiON, and switches.
Information pertaining to CLARiiON will already have been covered in steps (a) and (b) above.
The customer should have the final decision to continue host access during this service event.
.4

This update should be done during a time scheduled with the customer, when there is as little I/O
activity as possible on the array. Times of heavy I/O should be avoided. You will not be allowed to
perform a software upgrade (NDU) when the processor utilization for the two Storage Processors
within a Storage System sums to more than 100%. Factors which may impact this include:

heavy I/O activity

large numbers of LUNs on FLARE database drives (slots 0_0, 0_1, 0_2 or 0_3)
heavy administrative activity
If the storage system exceeds this limit, the Acceptable Processor Utilization pre-install rule will
prevent an upgrade from proceeding. This will not cause any disruption to the storage system, but
may cause a scheduled software upgrade to be delayed until the storage system is less busy.
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
.5

Changes to Navisphere in FLARE 24 and later may impact Navisphere classic CLI commands for
SnapView snapshots, SAN Copy, MirrorView and Replication Manager. Existing scripts using CLI
clients prior to R24 will not work when issued against an array running R24 or later. Hosts running
scripts using these commands with the Classic CLI client must upgrade to the Release 24 (or later)
CLI client and also have a valid Secure CLI Security file. No changes to the scripts themselves are
required. Full details of the symptoms, cause, and solution for this issue can be found in EMC
Knowledgebase article emc149075

.6

The revision level of software running on the array before the update can impact the process.
Reference the checks below to understand current and previous array based software revision level
interactions.

General FLARE Code Checks

.7

Is this array part of, or will it be part of, an iSCSI Microsoft cluster?
If no, go to the next step.

If yes, then Release 03.24.0x0.5.007 and later must be used. These versions add support for
Microsoft clusters that are connected via the iSCSI ports on the CX3-x0c storage systems,. See
Knowledgebase article emc150702 for requirements and recommendations for the iSCSI hosts
attached to the array.
.8

Is this a NEBS storage system?

If no, go to the next step.

If yes,
03.24.020.5.008 and later provide NEBS compliance for the CX3-20FDC models.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
03.24.040.5.008 and later provide NEBS compliance for the CX3-40FDC models.
.9

FRUMON Updates
Did you just perform an NDU on this array prior to this one?
If no, go to the next step.
If yes, was the FRUMON code updated as part of the NDU?
If no, go to the next step.
If yes, you must wait until the current FRUMON code update is complete before committing
the code and performing the next NDU.
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

-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.
Has the FRUMON code finished updating?
If yes, commit the FLARE code that was applied using Navisphere or Unisphere Manager, and
then go to the next step.
If no, repeat these steps until the FRUMON update has completed.
IMPORTANT: DO NOT commit the FLARE code from the NDU you just completed and begin the
next NDU FLARE update until the FRUMON code versions show as expected.
.10

Is the storage system running FLARE Release 24, or Release 26 lower than patch .026?
If no, go to the next step.
If yes, see emc209613 Background zeroing process stuck at high percentage for an extended period
of time.
If there is a stuck background zeroing process on the system, then the NDU may fail.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
The only way to check for a stuck process is to run TRiiAGE against SPCollects and look at the lustat
output. If you need help determining if a process is running, contact the support center or your
regional CLARiiON specialist.

FLARE Code Version-Specific Checks

.11

Are you updating to Release 24?

If no, go to the step entitled Upgrading to Release 26

If yes, read the following Release 24 notes.

Upgrading to Release 24
.12

Is this a large CX700 configuration?

If no, go to the next step.

If yes, be aware that large configuration CX700 storage systems must be upgraded to R24 patch .022
or later, or R26 instead. See Knowledgebase article ETA emc201367 for more information
.13

Is this a CX300, CX500, or CX700 storage system?

If no, go to the next step.

If yes, was this converted from a CX200, CX400, or CX600 array?
If no, go to the next step.
If yes, you must update to patch .019 (02.24.xxx.5.019) or later. See Knowledgebase article
emc180119: Upgrade to Release 24 or Release 26 fails for CX300, CX500, or CX700 storage
system that was converted from CX200, CX400, or CX600 storage system for more information.
.14

Is this a CX3-40 or a CX3-80 storage system?

If no, go to the next step.

If yes, was this originally a CX200, CX300, CX400, CX500, CX600 or CX700?
If no, go to the next step.
If yes, are you upgrading from Release 22?
If no, go to the next step.
If yes, you must upgrade to Release 24 patch .011 (03.24.xxx.5.011) or later. Do not upgrade
the array to a version of Release 24 that is earlier than patch .011. See Knowledgebase article
emc154285 for more information.
.15

Is MirrorView/S installed or will you be installing it?

If no, go to the next step.

If yes, Release 24 patch .015 or later must be installed. See ETA emc170213 and Knowledgebase
solution emc169553 for additional information.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.16

Does this configuration contain expanded metaLUNs?

If no, go to the next step.

If yes, see ETA emc172445: CLARiiON: A metaLUN that is expanded is left in a state where a future
reboot or NDU may cause the metaLUN to become inaccessible for full details and the workaround.
.17

Is this storage system running a version of Release 24 lower than patch .016?
If no, go to the next step.

If yes, see ETA emc179184: CLARiiON: Storage Processor panics when upgrading a storage system
running Release 24 FLARE patch version .016 and earlier using Software Assistant (SA) in
Navisphere Service Taskbar (NST). If this storage system falls into the 24/240/240 category, then
install the Management server patch prior to upgrading. The Knowledgebase article contains
instructions as to how to do this.
.18

Are you upgrading to R24 patch .008 or lower?

If no, go to the next step.

If yes, are there fractured clones on this storage system?
If no, go to the next step.
If yes, an uninitialized variable can cause continual panics resulting in recurring reboots of both
SPs. If the variable happens to be zero, there will no problem. However, if the variable is non-zero
at any time, continual panics and reboots of that SP will occur until Release 24 is committed.
To avoid this issue,
upgrade to R24 patch .011 or later
or if you must upgrade to Release 24 patch .008 or lower, then
remove all clones,
upgrade and commit FLARE Release 24,
and then reinstate the clones.
This will require a full clone synchronization. See EMC Knowledgebase article emc155454 for
more details.
.19

Are you upgrading to Release 24 patch .011 (03.24.xxx.5.011) or earlier?

If no, then go to the next step.

If yes, does the storage system contain ATA enclosures?

If no, go to the next step.
If yes, note that R24 patch .011 and earlier does not contain ATA FRUMON 1.95. If this storage
system contains ATA enclosures, 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
.20

Go to the step entitled End of FLARE Code Version-Specific Checks

Upgrading to Release 26

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.21

Are you upgrading to Release 26 (applies to both CX and CX3) patch .031 (02.26.xxx.5.031 or
03.26.xxx.3.031)?

If no, go to the next step.

If yes, see Knowledgebase article emc248896 Enclosure speed mismatch after non-disruptive
upgrade (NDU). Enclosures in an array with LCCs running FRUMON 7.59 or prior, may not come
online and would report loop speed mismatch (a31 message) after array is upgraded to Release
26.031. Do not upgrade directly

.22

CX3 Release 26, patch .014 (03.26.xxx.5.014) has been withdrawn and cannot be used. See
Knowledgebase solutions: emc190031: CLARiiON non-disruptive upgrades (NDUs) to FLARE
Release 26 Patch .014. ETA emc190157: Non-disruptive upgrade (NDU) to FLARE Release 26 Patch
.014 may result in some drives rebuilding due to enclosures temporarily going offline

.23

CX3 Release 26, patches .026 and .028 (03.26.xxx.5.026, 03.26.xxx.5.028) have been withdrawn
and cannot be used. See Knowledgebase solution ETA emc226018: CX3 code upgrades to FLARE
Release 26 patch .026 or patch .028 should be postponed until new patch is released.

Patch .029 or later must be used instead.

.24

Is the storage system running FLARE Release 26, patch .025, .026 or .028?
If no, go to the next step.
If yes, you must update to FLARE Release 26, patch .029 or later. See Knowledgebase solution
emc231771: CX3 series code upgrades or enabler installations with a starting FLARE revision of
Release 26 patch .025, .026, or .028 must only be performed with a destination revision of Release
26 patch .029 or later.

.25

Are you upgrading a CX3 storage system to Release 26 patch .029 (03.26.xxx.5.029)?
If no, go to the next step.
If yes, are you upgrading from Release 26 patch .026 or patch .028?
If no, go to the next step.
If yes, perform the following steps before you start the upgrade. See Knowledgebase solution
emc227205 for more information.
In Navisphere Manager, right-click on the target array and select Properties.
Is Statistics Logging checked?
If it is not checked, go to the next step.
If it is checked:
.a Uncheck it and select Apply.
.b Wait for 10 minutes to see if either SP panics.
.c If a panic should occur, wait until the reboot completes and continue at the next step.
Note: If the NDU fails due to a panic, try the NDU again.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.26

Are you upgrading a CX3 storage system to Release 26 patch .028 (03.26.xxx.5.028) or later?
If yes, go to the next step.

If no, see Knowledgebase solution emc224227: How to proactively identify and prevent NDU failure
on a storage system when upgrading from FLARE Release 26 to a version of Release 26 prior to
patch .028. This applies to loading of both FLARE and enablers.
Is the system already running Release 26?
If yes, then perform the steps in emc224227.
If no, consider upgrading to patch .028 or later to avoid this issue.
.27

If you are installing an enabler or upgrading FLARE and you receive the message that the
EMCRemote Service could not be stopped, see emc213275 Non-disruptive upgrade (NDU)
installation of an enabler or FLARE bundle on a storage system running Release 26 FLARE fails with
a specific problem in the EMCRemoteNG package post-activate step. Do not attempt the NDU again
until the steps in that Knowledgebase solution have been performed

.28

Is this a CX300, CX500, or CX700 storage system?

If no, go to the next step.

If yes, was this converted from a CX200, CX400, or CX600 storage system?
If no, go to the next step.
If yes, you must update to patch .014 (02.26.xxx.5.014) or later. See Knowledgebase article
emc180119: Upgrade to Release 24 or Release 26 fails for CX300, CX500, or CX700 storage
system that was converted from CX200, CX400, or CX600 storage system for more information.
.29

Does the customer plan to run SnapView, MirrorView/Asynchronous or Incremental SAN Copy?
If no, go to the next step.

If yes, do not upgrade to Release 26 patch .010. Instead upgrade to a later version of Release 26.
See ETA emc203781: Possible storage processor panics when running SnapView, MirrorView/A, or
Incremental SAN Copy in Release 26 patch level .010
.30

Is the customer running or planning to run Navisphere Quality of Service Manager (NQM)?
If no, go to the next step.
If yes, is this a CX3 series storage system?
If no, go to the next step.
If yes, is the customer running a version Release 26 prior to patch .019 (03.26.xxx.5.019)?
If no, go to the next step.
If yes, see ETA emc194267: Rare condition may result in inconsistent data being returned to a
host when Navisphere Quality of Service Manager (NQM) is configured
Is NQM configured?
If no, advise the customer not to configure it.
If yes, advise the customer to disable it.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.31

Is the customer running MirrorView/Asynchronous?

If no, go to the next step.

If yes, do not upgrade to any version of Release 26 up to and including patch .010. The only versions
to which you should upgrade are Release 26 patch .011 and later. See ETA emc176189: Performing
a CLARiiON NDU upgrade to Release 26 may result in rolling reboots if MirrorView/Asynchronous is
configured
Note: The upgrade to R26 is the issue, so even if the customer has already upgraded successfully to
R26, they also should not upgrade to patch .010 or lower.
.32

Is the customer running or planning to run SnapView?

If no, go to the next step.

If yes, there is a potential performance issue under certain circumstances with R26 SnapView,
detailed in ETA emc171888. Storage systems running SnapView with FLARE Release 26 may
experience reduced performance.
This has been addressed in R26 patch .010 and later. If the customer is already running R26, but is
running a version lower than .010, then alert them to the possible issue, and advise to upgrade to R26
patch .010 or later, unless they are also running MirrorView/Asynchronous, in which case, they should
upgrade to Release 26 patch .011 and later (see ETA emc176189, above).
.33

Is this storage system running a version of Release 24 lower than patch .016?
If no, go to the next step.

If yes, see ETA emc179184: CLARiiON: Storage Processor panics when upgrading a storage system
running Release 24 FLARE patch version .016 and earlier using Software Assistant (SA) in
Navisphere Service Taskbar (NST). If this storage system falls into the 24/240/240 category, then
install the Management server patch prior to upgrading. The Knowledgebase article contains
instructions as to how to do this.
.34

Are you upgrading from Release 26 (02.26, 03.26) all patches up to and including patch .011?
If no go to the next step.

If yes, the NDU may fail with bugcheck 0x0190481fDefinitionnotfound,Bugcheckin:

FC_PANIC_BASE if the Recovery Image, the Conversion Image or the Utility Partition was loaded and
the SPs have not since been rebooted.
If you know that one of these images was loaded and that no reboots have taken place, you can
proactively reboot each SP in turn before starting the NDU.
If you should run into the bugcheck, then reboot the peer SP, and retry the NDU when that completes.
The reboots will solve the issue.
See Knowledgebase article emc179061 NDU from Release 26 to higher revision of Release 26 may
fail with bugcheck for details.
.35

Are you upgrading to a Release 26 patch that is earlier than patch .014?
If no, go to the next step.
If yes, see Knowledgebase solution emc188281: Host cannot log into array after FLARE code
upgrade.

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.36

Are you upgrading from either

02.26 patch .014 or 03.26 patch .014, .016 or .019?

If no, go to the next step.
If yes, are you upgrading to patch .020 or .later?
If no, go to the next step.
If yes, see Knowledgebase Solution emc203277: Non-disruptive upgrade (NDU) to FLARE
Release 26 Patch 25 and Patch 20 or later fails after SPs go unmanaged or reboot before
proceeding. Follow the instructions to load the Management Server .upf file.
Note: The new Management Server rule in the R29 Navisphere Service Taskbar will fail. Use the
bypass option documented later in this procedure.

End of FLARE Code Version-Specific Checks

General Pre-NDU Checks
.37

Perform the following checks prior to the NDU, as they apply to your configuration.
Note that checks that are performed by the Install Software Wizard are no longer listed in this
document. All checks performed can be seen in the Software Installation Rules document. Review
these prior to starting the upgrade if you want to see what checks will be automatically performed.

Software Installation Rules

.38

The Running check scripts step in the Software Installation phase will fail if there are active Windows
sessions on the SPs that are using clariion1992 as the login. The EMCRemote upgrade cannot be
performed if there is anything actively using clariion1992. If you have any active sessions, connect
to both SPs with EMCRemote and log out of Windows prior to starting the FLARE upgrade.

Check that the last EMCRemote session on each SP was logged out. If not, then the EMCRemote
upgrade portion of the NDU may fail.
.b Dial into each SP using EMCRemote Dialer.
.c If you do not see Press Ctrl-Alt-Delete to login screen, but see the SP Desktop instead, then
click on Start, Log Off <user> and confirm Yes.
.d Exit EMCRemote Dialer by clicking the End Session icon on the top left of the EMCRemote
Window.
.39

Determine whether this NDU involves a FRUMON code update:

In Navisphere Manager, expand the arrays navigation tree to show the elements under Physical >
DAE > LCC or BCC.
Right-click on the icon for either SP As or SP Bs LCCs and select Resume from the pop-up menu.
Record the FRUMON code version installed on the array.
Check the patch Release Notes for the FLARE software package you are about to install and
record the FRUMON code version contained in the package.
If the FRUMON code version number shown in the Navisphere Manager Resume dialog box is

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
different from the version number documented in the patch Release Notes for the software package
you plan to install, then this NDU involves a FRUMON code update. The LCCs in any attached DAE
chassis will automatically perform FRUMON code updates when the FLARE code update is complete.
IMPORTANT: After the NDU, you must wait until all FRUMON code updates are complete before
committing the new FLARE code.
.40

View the event log to confirm that the array has not been experiencing recent problems which should
be investigated and understood prior to this NDU.

.41

SnapView

Is the customer running SnapView?

If no, go to the next step.
If yes, stop any SnapView sessions that are not Persistent. Snap sessions that were not created
with persistence will not survive an NDU.
.42

MirrorView/Asynchronous

Is the customer running MirrorView/Asynchronous?

If no, go to the next step.
If yes:
Do not manually initiate any sync commands during any NDU update of FLARE from one major
revision to the next (for example, Release 19 to Release 24). No sync commands will be initiated
by the array during the NDU.
Fracture all asynchronous mirrors when performing an NDU if the array is running the initial
release of Release 14 (02.07.xxx.5.003 for CX300 or .005 for CX500 or CX700). Once the
upgrade has completed, synchronize all mirrors.
Multiple arrays involved in a MirrorView (MV/A or MV/S) configuration should not be targeted
during the same software NDU operation. Only perform the NDU on one array at a time
The software on arrays in a MirrorView relationship must be within 1 revision apart in active mirror
condition. If this situation exists on an array you are updating, then plan your array updates so the
arrays will not be 2 revisions apart in an active MirrorView relationship during the NDU. See the
Release Notes for the version of MirrorView that you are installing to determine recommended
(preferred) and supported configurations.
Updating usually involves starting with the lower revision arrays. The array software ensures that
mirrors continue to operate correctly during an NDU without requiring a full resynchronization of
any secondary image. System fractures are a normal part of the NDU operation, but these result
in partial resynchronization only (which will automatically start if the mirror recovery policy is set to
Automatic).
If you cannot maintain a recommended (preferred) or supported configuration during the upgrade:
Administratively fracture mirrors.
Update target arrays to their final software destination.
When the arrays in the MirrorView relationship are updated to their final software destination,
mirrors can be synchronized with a partial sync.

10

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.43

MirrorView/Synchronous

Is the customer running MirrorView/Synchronous?

If no, go to the next step.
If yes, do not deactivate a mirror prior to an NDU. Deactivating the mirror will cause all server
access to the primary LUN to be lost until the mirror is reactivated. (See Knowledgebase article
emc79767 for an explanation of deactivate vs. fracture
Multiple arrays involved in a MirrorView (MV/A or MV/S) configuration should not be targeted
during the same software NDU operation. Only perform the NDU on one array at a time)
The software on arrays in a MirrorView relationship must be within 1 revision apart in active mirror
condition. If this situation exists on an array you are updating, then plan your array updates so the
arrays will not be 2 revisions apart in an active MirrorView relationship during the NDU. See the
Release Notes for the version of MirrorView that you are installing to determine recommended
(preferred) and supported configurations.
Updating usually involves starting with the lower revision arrays. The array software ensures that
mirrors continue to operate correctly during an NDU without requiring a full resynchronization of
any secondary image. System fractures are a normal part of the NDU operation, but these result
in partial resynchronization only (which will automatically start if the mirror recovery policy is set to
Automatic).
If you cannot maintain a recommended (preferred) or supported configuration during the upgrade:
Administratively fracture mirrors.
Update target arrays to their final software destination.
When the arrays in the MirrorView relationship are updated to their final software destination,
mirrors can be synchronized with a partial sync
.44

Celerra

Does this storage system involve a Celerra?

If no, go to the next step.
If yes:
Contact Celerra Change Control before performing an NDU software upgrade on CLARiiON which
is the backend to a Celerra connected directly or via a SAN. There are special instructions and
limitations of which you must be aware. Ensure that the appropriate CLARiiON and Celerra CCA
approvals have been obtained.
If upgrading FLARE, ensure that the destination FLARE is compatible with the Celerra code.
If updating both the Celerra and the CLARiiON, upgrade the Celerra before upgrading the
CLARiiON
See ETA emc224962: Celerra: Celerra may panic during CLARiiON FRUMON or NDU activity due
to multi-path failover handling and determine if this applies.
If you are upgrading an array that is attached in a Celerra/NAS environment, refer to the directions
provided in the NAS CCA to obtain the correct software. The FLARE image may require a backend
enabler for the CLARiiON on the backend of the Celerra when there are direct copper FC
connections between the front-end Celerra and the back-end CLARiiON. The FLARE images on
the CLARiiON Web sites do not have this enabler. If the enabler is not needed, do not load it as it
will disable any front-end optical ports on the SPs. The only platforms that use the Backend
Enabler are the NS600 and NS700. Since these are integrated models, the CLARiiON arrays

11

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
would be CX600 and CX700.
After the CLARiiON FLARE code is upgraded it is necessary to trespass back the Celerra LUNs to
their default owner. To perform this action you must login to the Celerra Control Station with user
nasadmin and do the following:
.a Check the Serial number id of the storage attached when multiple Arrays are connected to the
Celerra
#nas_storagelist

.b Check if there are LUNs trespassed

#nas_storageca

.c If LUNs are trespassed then trespass them back with this command
#nas_storagefailbackid=xxxx

.d Check in Navisphere that all LUNs are assigned to their default owners.
.45

UNIX Hosts
Are UNIX hosts being upgraded as part of this array FLARE upgrade?

If no, go to the step entitled VMware Hosts

If yes, a new Navisphere agent configuration file is loaded on the host. Ensure that any changes that
may have been made to the old agent configuration file are made to the new agent configuration file.
Either edit the new file, or save a copy of the old agent configuration file and restore it after the
upgrade to preserve the settings.
.46

AIX Hosts

Are AIX hosts involved in this upgrade?

If no, go to the next step.
If yes, is the array already at Release 19 patch 016 or higher?
If no, you cannot perform an on-line upgrade. Stop all I/O from any attached AIX server to the
array prior to an NDU.
If yes, NDU is now available under certain circumstances for certain configurations. Please refer
to EMC Knowledgebase article emc67186 to see if your configuration meets the criteria. Also note
that the NDU may require an RPQ.
If you do not have an approved NDU configuration, then stop all I/O from any connected AIX server
during the NDU process if it is running the native HBA driver. Refer to EMC Knowledgebase article
emc67186 for more information.
.47

HP-UX Hosts
Are there any HP-UX hosts involved in this upgrade?
If no, go to the next step.
If yes:
Does the the old agent.config file (/etc/Navisphere/agent.config) have OptionsSupported
AutoTrespass uncommented (to enable PVLinks)?
If yes, ensure that the new agent.config file is also uncommented. That line is commented out by

12

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
default in the new file. Without this AutoTrespass setting, the HP-UX host will only report 1 path to
each LUN when the ioscan command is run, which will affect both importing of volume groups, and
failover.
Are there any HP-UX 11.11 hosts involved in this upgrade?
If no, go to the next step.
If yes, if an array has an attached HP server running HP-UX 11.11 OS and VERITAS Volume
Manager 3.5 and the array SN 4th digit from the right is odd, the HP-UX server will have to have
all I/O stopped as VERITAS Volume Manager will not reestablish paths on either SP during or after
the NDU. This results in loss of access to the array from this HP-UX server. Refer to EMC
Knowledgebase article emc96074
.48

Solaris Hosts
Are there any Solaris hosts involved in this upgrade?

If no, go to the next step.

If yes, ensure that the no-device-delay setting is configured to 0 (zero) in the lpfc.conf file. Refer to
EMC Knowledgebase article emc66969 for more information about this setting.
.49

VMware Hosts

Are VMware hosts involved in this upgrade?

If no, go to the step entitled Windows Hosts
If yes, is the host running VMware software less than VMware ESX Server v2.1.0 with native failover?
If no, go to the next step.
If yes, you cannot perform an on-line upgrade. Stop all I/O from any attached VMware server to
the array prior to an NDU.
.50

Windows Hosts
Are Windows 2000 servers involved in this upgrade?

If no, go to the next step.

If yes, is the Windows server using Dynamic Disks?
If no, go to the next step.
If yes, you must use an NDU delay of 360 seconds when a Software NDU is performed. The
Wizard automatically invokes a 360 second delay. It must be manually entered when not using the
Software Assistant.
.51

Cisco FC Switch
Is the array in a SAN environment with a Cisco FC Switch?
If no, go to the next step.
If yes, refer to EMC Knowledgebase article emc91792. This addresses a port (SP) not logging back
into the switch if the switch port has been up and enabled for 248 days or more. This could cause a
DU event during the SP update process during the NDU.

13

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
.52

Brocade or McData FC Switch

Is the array in a SAN environment with a Brocade or McData FC Switch?

If no, go to the next step.

If yes, does the environment include an HP-UX or AIX host?
If no go to the next step.
If yes, refer to EMC Knowledgebase article emc173171. This addresses connectivity issues
between HP-UX or AIX servers and a CLARiiON array. If the switch firmware has recently been
upgraded to EOSc 9.6 or higher please make sure that NPIV is Disabled. If NPIV is enabled it will
cause DU between the CLARiiON and HP-UX or AIX servers.
.53

SAN management software

Is any SAN management software present (for example, ERM)?

If no, go to the next step.

If yes, refer to CCA and CAG (CLARiiON Activity Guide) for the requirements.
.54

Invista software
Is an Invista Configuration Repository Volume (ICRV) LUN involved in this configuration?

If no, go to the next step.

If yes, make sure that it is correctly configured across two arrays before starting the NDU. See the
Invista Installation and Setup Guide, and the Invista Customer Setup Procedures document on
Powerlink, (Support > Technical Documentation and Advisories > Software ~ E-I ~ Documentation > Invista >
Installation/Configuration) which describe what has to be done to set up the ICRVs for the Invista
instance.
If you are updating the software on both arrays, then wait at least 10 minutes between the 2 updates
in order to allow the ICRV to sync between arrays.

Prepare for Upgrade

.55

Download the Software Bundle for the Release.

The software bundles can be obtained from the CLARiiON Information section of either the GS
Website or the EMC Services Partner Web via Powerlink.
All CX3-Series arrays: FLARE Operating Environment 03.rr.xxx.5.yyy
where rr is the Release number (24, 26 etc.)
xxx is: 010 for CX3-10 series
020 for CX3-20 series
040 for CX3-40 series
080 for CX3-80
CX-Series arrays as specified below: FLARE Operating Environment 02.rr.xxx.5.yyy
where rr is the Release number (24, 26 etc.)
xxx is: 300 for CX300
301 for CX300i

14

330584751.doc (187.00 KB)

9/22/2016 9:18 AM
Last saved by boykot
500 for CX500 and CX500i
700 for CX700
Note: The FLARE bundle continues to be a .pbu file
.56

Does your activity involve upgrading software on a storage system running a version of FLARE that is
lower than Release 19?
If yes, use version 6.29.2 NST. USM does not support software upgrades on systems running lower
than Release 19 code. See Knowledgebase solution emc228273 for information as to how to have
more than 1 version of NST/USM installed at the same time.

.57

Pre-stage Software
You can now pre-stage software on the SPs so that the transfer step in the actual upgrade can be
done ahead of time, and the software will already be present on the SPs when you come to do the
NDU.
To prestage software:
As mentioned previously, the version of FLARE currently running on the system will determine
which tool you will use to do the update:
USM (Release 19 and later):Select Software, System Software, Prepare for Installation
option, Verify storage system environment only.
NST (Prior to Release 19): Select Software Assistant as usual in the left-hand pane, select the
Prepare for Installation option, then Verify storage system environment only.
This will take you through transferring the software to the array and through all the rules checks
that are normally done prior to an NDU.
When you come to install after pre-staging:
If the staging was done up to 2 days before selecting to install, then you will be offered Express
Install as an option, otherwise you will be offered Custom Install.
If using the NST and the SPs have rebooted since the staging was done or CIMON (management
server) was restarted, the software will no longer be there and you will have to transfer it again.
This statement does no apply if you are using the USM.
The software staged on the SPs will be shown for selection. You can choose this or select others
to install instead.

Table of Contents

15