EMC ® CLARiiON ™ SolVe Generator

Solution for Validating your engagement

Topic
Existing System Procedures
Selections
Select a procedure: Install / Update FLARE to Release 26
What release are you running now?: Release 26
Which company do you work for?: EMC

Generated: 16:15 > 一月 15,

2017
SolVe Generator Updated:

REPORT PROBLEMS

If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]

Copyright© 2001 – 2025 EMC Corporation. All rights reserved.

Publication Date: January, 2017
EMC 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.” EMC CORPORATION 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 EMC software described in this publication requires an applicable software
license.
For the most up-to-date regulatory document for your product line, search for “regulatory” on the applicable product
page at https://support.EMC.com
For the most up-to-date listing of EMC trademarks, see the list of EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.

EMC CONFIDENTIAL version: 6.0.0.41

1 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

Contents
 Verify FLARE versions incor040_R050..............................................................3
 Hardware/software upgrade readiness check cnhas010_R036............................4
 Prepare CX300, 500, 700, and CX3 series for update to Release 24 and above
upndu310_R083....................................................................................................................5
General Notes.............................................................................................................................................. 5
General FLARE Code Checks..................................................................................................................... 7
FLARE Code Version-Specific Checks........................................................................................................ 8
Upgrading to Release 24............................................................................................................................. 8
Upgrading to Release 26........................................................................................................................... 10
End of FLARE Code Version-Specific Checks........................................................................................... 13
General Pre-NDU Checks.......................................................................................................................... 13
Prepare for Upgrade.................................................................................................................................. 19

 Disable array from calling home cnalr010_R009.............................................20

CLARalert 6.22.X or greater Arrays running Release 22 or greater Central and Distributed Monitor
configuration (method 1)....................................................................................................................... 20
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Central Monitor configuration (method 2)............................................................................................. 21
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Distributed Monitor configuration (method 3)........................................................................................21
 Update software on a CX300 series/CX500 series/CX700/CX3 series array
upndu320_R040..................................................................................................................22
 Post hardware/software upgrade procedure cnhas020_R021............................35
 Restore array call home monitoring cnalr020_R010............................................36
CLARalert 6.22.X or greater Arrays running Release 22 or greater Central and Distributed Monitoring
configuration (method 1)....................................................................................................................... 36
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Central Monitoring configuration (method 2).........................................................................................37
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Distributed Monitoring configuration (method 3)...................................................................................38
Using the Install Base Group (IBG) Business Services Portal.......................................38
 Appendix: Locating the CX3-Series Service LAN port cnlan190_R001..............42

EMC CONFIDENTIAL version: 6.0.0.41

2 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

 Verify FLARE versions incor040_R050

1. As of April, 2012 the latest patch versions are:  Done

 CX4 series 
Note: There is a common bundle for all CX4 models

MODEL Release 28 Release 29 Release 30

CX4 all models 04.28.000.5.710** 04.29.000.5.019 04.30.000.5.525

** Last planned patch for Release

 CX3 series
As of October, 2008, these are being shipped with Release 26, patch .019 installed. It is strongly
recommended that the latest patch for the target FLARE release be installed when you are doing
an upgrade or an install, unless there is a technical reason not to do so.
See the CLARiiON Activity Guide (CAG) for target FLARE releases for installations and upgrades,
and any patch restrictions.
The patch version, and its corresponding Release Notes, can be found at on the CS Internal
Website or the EMC Services Partner Web via PowerLink.
MODEL Release 22 Release 24 Release 26
CX3-10 N/A 03.24.010.5.022** 03.26.010.5.032
CX3-20 series 03.22.020.5.514** 03.24.020.5.022** 03.26.020.5.032
CX3-40 series 03.22.040.5.514** 03.24.040.5.022** 03.26.040.5.032
CX3-80 03.22.080.5.514** 03.24.080.5.022** 03.26.080.5.032

** Last planned patch for Release

 CX series
MODEL Release 19 (last release for these models)
CX200 02.19.200.5.045**
CX400 02.19.400.5.045**
CX600 02.19.600.5.045**
** Last planned patch for Release

MODEL Release 19 Release 24 Release 26

CX300 02.19.300.5.045** 02.24.300.5.022** 02.26.300.5.031**
CX300i 02.19.301.5.045** 02.24.301.5.022** 02.26.301.5.031**
CX500 series 02.19.500.5.045** 02.24.500.5.022** 02.26.500.5.031**
CX700 02.19.700.5.045** 02.24.700.5.022** 02.26.700.5.031**
** Last planned patch for Release

** last planned patch for Release

Table of Contents

EMC CONFIDENTIAL version: 6.0.0.41

3 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

 Hardware/software upgrade readiness check cnhas010_R036

2. This module will instruct how to verify the state of the storage system and attached servers. P Done

If this activity will cause access to an SP to be interrupted (e.g. NDU, SP replacement), any hosts £
attached to the storage system must be able to maintain access to the storage system. 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.
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 NST or USM are 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
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.
View Failover Settings Reference Table

Note: For current support for ALUA, please consult the E-Lab Interoperability Navigator. See the
Installation Roadmap for CLARiiON Storage Systems P/N 069001166 for the required failovermode,
initiator type settings etc. for any failover software that is not listed.

Note: The Trusted column should be ignored as it applies to legacy arrays only.

Note: The customer should have the final decision to continue host access during this service event.

3. Ensure you have a Windows management station or service laptop with IP connectivity to both SPs
£
Verify connectivity by performing a ping command to both SPs.

4. Physical hardware check:

£
 Inspect for proper cable (power, SPS and LCC) connections. Correct any issues before
proceeding.
 Check for any fault lights being present, investigate cause and resolve before proceeding with the
assessment.
 Check the event logs or SPcollects for any drives reporting a high number or long history of soft
media errors. (0x6A0 or 0x820) To prevent a possible Data Unavailable event, proactively replace
any drive exhibiting this behavior.

5. Collect and Review CLARiiON Storage System information:

£
EMC CONFIDENTIAL version: 6.0.0.41
4 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

NST: Select Hardware Maintenance, Verify Storage System

USM: Select Diagnostics, Verify Storage System
a. Follow the prompts to connect to the storage system, and to generate the report.
b. The issues report will be generated. Save the report if desired.
Note that this procedure generates the following files which are saved in the repository:
 A combined SPCollects file
<repository location>/<serial
number/HCK/<date>_<time>_CLARiiON_Healthcheck_<serial
number>_<date>_<time>.zip
 An XML file
<repository location>/<serial number/HCK/<date>_<time>.CAP_<serial
number>_<date>_<time>.xml
c. Review the report. If there are any issues address them and rerun Verify Storage System.

Table of Contents

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

General Notes
6.  CX200, CX400, CX600 cannot be upgraded to Release 24 or later.  Done

 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.
Do not upgrade directly to Release 24, or Release 26 prior to patch .025; there is a risk that the
NDU may fail.

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

EMC CONFIDENTIAL version: 6.0.0.41

5 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

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

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

EMC CONFIDENTIAL version: 6.0.0.41

6 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

Knowledgebase article emc149075

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

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

13. 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.
 03.24.040.5.008 and later provide NEBS compliance for the CX3-40FDC models.

14. 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
navicli –h <SP_IP_address> getcrus –lccreva –lccrevb
or
naviseccli –h <SP_IP_address> getcrus –lccreva –lccrevb
-or-
 Navisphere Manager: Expand the array’s navigation tree to show the elements under Physical
> DAE-ATA > LCC or BCC, right-click on the icon for either SP A’s or SP B’s 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-

EMC CONFIDENTIAL version: 6.0.0.41

7 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

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

16. 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
17. 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

18. 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?

EMC CONFIDENTIAL version: 6.0.0.41

8 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.

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

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

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

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

23. 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,

EMC CONFIDENTIAL version: 6.0.0.41

9 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

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

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


Upgrading to Release 26
26. 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

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

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

29. Is the storage system running FLARE Release 26, patch .025, .026 or .028?
If no, go to the next step.

EMC CONFIDENTIAL version: 6.0.0.41

10 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.

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

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

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

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

EMC CONFIDENTIAL version: 6.0.0.41

11 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.

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

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

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

37. 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).

EMC CONFIDENTIAL version: 6.0.0.41

12 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

39. 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 0x0190481f Definition not found, Bugcheck in:
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.

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

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

EMC CONFIDENTIAL version: 6.0.0.41

13 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

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

44. Determine whether this NDU involves a FRUMON code update:


 In Navisphere Manager, expand the array’s navigation tree to show the elements under Physical
> DAE > LCC or BCC.
 Right-click on the icon for either SP A’s or SP B’s 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
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.

45. 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.

46. 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.

47. MirrorView/Asynchronous

EMC CONFIDENTIAL version: 6.0.0.41
14 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.

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

EMC CONFIDENTIAL version: 6.0.0.41

15 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

49. 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
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_storage –list
b. Check if there are LUNs trespassed
# nas_storage –c –a
c. If LUNs are trespassed then trespass them back with this command
# nas_storage -failback id=xxxx
d. Check in Navisphere that all LUNs are assigned to their default owners.

EMC CONFIDENTIAL version: 6.0.0.41

16 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

51. 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.
52. 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
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

53. Solaris Hosts


Are there any Solaris hosts involved in this upgrade?

EMC CONFIDENTIAL version: 6.0.0.41

17 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.

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

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

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

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

58. SAN management software

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

EMC CONFIDENTIAL version: 6.0.0.41

18 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

If no, go to the next step.

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

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

60. 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
500 for CX500 and CX500i
700 for CX700

Note: The FLARE bundle continues to be a .pbu file

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

62. Pre-stage Software


You can now pre-stage software on the SPs so that the transfer step in the actual upgrade can be

EMC CONFIDENTIAL version: 6.0.0.41

19 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

 Disable array from calling home cnalr010_R009

63. To prevent multiple inconsequential call-homes from being generated it is important that you disable  Done
call home for the system you will be servicing. The FLARE release running on the system and
CLARalert/ESRS IP Client version running in the environment determines which method you should

perform to disable the array from calling home.
Method 1 is the preferred and the most common method of disabling call home for non NDU activities
where you enable/disable “Silent Mode” on the storage system. Systems running less than FLARE
Release 22 require that you use method 3 or 4 to disable call home where you manually reconfigure
Navisphere/Unisphere Event Monitor.

64.  Done
CLARalert 6.22.X or greater Arrays running Release 22 or greater Central and Distributed Monitor
configuration (method 1) 
Navisphere Service Taskbar v6.26.5 or greater and Unisphere Service Manager will automatically
attempt to set quiet mode (Disable/Enable Responses) for central and distributed monitoring call home
response when performing an NDU via the Install Software Wizard. The Install Software Wizard will
not allow the user to start the NDU until the call home responses are disabled. If the Wizard fails to set
quiet mode or you are disabling call home for other than an NDU via the Install Software Wizard
perform the steps below to manually disable call home.

Note: Network connectivity between the array you are upgrading and the call-home monitoring station
is required for the Install Software Wizard to automatically disable call-home and verify the call-home
rules.

EMC CONFIDENTIAL version: 6.0.0.41

20 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

From Navisphere Manager domain that contains the system you want to disable from calling home
select the Monitors tab and right click SP A monitor which you want to disable. Select Disable/Enable
Reponses. Select Disable Responses check box and set the disable time period from 30 to 240
minutes. Click OK. Repeat for SP B.
From the Unisphere Manager domain that contains the system you want to disable from calling home
select Monitoring > Event Notification > Distributed Monitors. Right click SP A monitor which you
want to disable and select Disable/Enable Reponses. Select Disable Responses check box and set
the disable time period from 30 to 240 minutes. Click OK. Repeat for SP B.
The array will now not call home or responded to any other template applied to the array until the timer
you set expires. You can enable the array responses before the timer expires by simply un-checking
the Disable Responses check box.

IMPORTANT: You must disable both SP A&B monitors to disable call home.

65.  Done
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Central Monitor configuration (method 2) 
Navisphere Service Taskbar v6.26.5 or greater and Unisphere Service Manager will automatically
attempt to disable central monitoring call home response when performing an NDU via the Software
Assistant. The Software Assistance Wizard will not allow the user to start the NDU until the
CLARalert/ESRS IP Client for CLARiiON call home responses are disabled. If the Wizard fails to
disable call home or you are disabling call home for other than an NDU or will be disconnecting the
array network management ports from the customer network and using your laptop to perform the
NDU. Perform the steps below to manually disable call home.

Note: Network connectivity between the array you are upgrading and the call-home monitoring station
is required for the Software Assistant to automatically disable call-home and verify the call-home rules.

From the Navisphere Manager domain which contains the system you want to disable from calling
home select the Monitors tab and click the plus sign on the central monitor. Right click the system and
select Stop Monitoring.
From the Unisphere Manager domain which contains the system you want to disable from calling
home select Monitoring > Event Notification > Centralized Monitors > Monitored Systems. From
the monitored systems list right click the system and select Event Notification > Stop Monitoring.
From Navisphere/Unisphere Manager the system will be removed from the central monitor
configuration and the GUI will update not display the system icon under the central monitor.

IMPORTANT: You have just removed the system from the central monitor configuration. When you
are finished performing your service activities you MUST restore the system to the central monitor
configuration otherwise the array will no longer call home. Make sure you perform the “restore array
monitoring” section of this procedure.

66.  Done
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher
Distributed Monitor configuration (method 3) 
Navisphere Service Taskbar v6.26.5 or greater and Unisphere Service Manager does not disable a
distributed monitoring call home response. Follow the steps below to disable distributed monitoring call

EMC CONFIDENTIAL version: 6.0.0.41

21 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

home.

From Navisphere Manager domain which contains the system you want to disable from calling home
select the Monitors tab and expand the system SP A monitor icon. Right click the Call Home template
icon and select Stop Using. Repeat for SP B monitor.
From the Unisphere Manager domain which contains the system you want to disable from calling
home select Monitoring > Event Notification > Centralized Monitors > Monitored Systems. From
the monitored systems list right click the system and select Event Notification > Stop Monitoring.
From Navisphere/Unisphere Manager the call home template will be removed from both SP A & B
monitors and the GUI will update removing the call home template from both SP A & B distributed
monitors.

IMPORTANT: You have just removed the Call-Home template from the distributed monitor
configuration. When you are finished performing your service activities you MUST restore the Call-
Home template to the distributed monitor configuration otherwise the array will no longer call home.
Make sure you perform the “restore array monitoring” section of this procedure.

Table of Contents

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

series array upndu320_R040

67. 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:

EMC CONFIDENTIAL version: 6.0.0.41

22 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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 re-
enabled, hot spares must not be rebound, and host I/O must not be allowed until the FRUMON
code update has been confirmed.

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

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


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”.
70. 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

EMC CONFIDENTIAL version: 6.0.0.41

23 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.
71. 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
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. Recommended Action:
Do nothing; No problems found.
or
b. Recommended Action:
Mirror secondary corruption possible if an SP reboots.
- Disable and de-allocate WIL LUNs.
- Reallocate WIL LUNs and re-enable WILs.
or

EMC CONFIDENTIAL version: 6.0.0.41

24 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

c. Recommended Action:
Mirror secondary corruption possible.
a. Disable WILs and de-allocate WIL LUNs.
b. Remove and re-add secondary images with sync
required to re-sync all mirrors.
c. Then reallocate WIL LUNs and re-enable WILs.

Perform the recommended action (if any).

72. 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)

73. After loading the NST to a windows server/laptop with access to both SPs from the customer’s
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 customer’s LAN, type in the IP address of one of
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.

EMC CONFIDENTIAL version: 6.0.0.41

25 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

EMC CONFIDENTIAL version: 6.0.0.41

26 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

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.

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

EMC CONFIDENTIAL version: 6.0.0.41

27 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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:
naviseccli –h <SP_IP_address> getcrus –lccreva -lccrevb
-or-
 In Navisphere Manager, expand the array’s navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC.
Right-click on the icon for either SP A’s or SP B’s 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
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.

77. 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).

78. Does the storage system have ATA enclosures (ATA drives)?
£
If no, go to the next step.

EMC CONFIDENTIAL version: 6.0.0.41

28 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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: getcrus -lccreva -lccrevb
 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
–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) LCC Firmware Upgrade complete on all
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:
naviseccli –h <SP_IP_address> getcrus –lccreva -lccrevb
-or-

EMC CONFIDENTIAL version: 6.0.0.41

29 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

 In Navisphere Manager, expand the array’s navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC.
Right-click on the icon for either SP A’s or SP B’s 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.
79. Go to the step labeled After the NDU

CX3-Series Storage Systems only

80. Updating from FLARE version Release 19 and later (USM)

81. Running USM:


a. When you have loaded USM on a windows server/laptop with access to both SPs from the
customer’s 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.
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

EMC CONFIDENTIAL version: 6.0.0.41

30 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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 off-
line.

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

EMC CONFIDENTIAL version: 6.0.0.41

31 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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.
82. 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:
 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.

EMC CONFIDENTIAL version: 6.0.0.41

32 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

83. 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.
84. 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
navicli –h <SP_IP_address> getcrus –lccreva –lccrevb
or
naviseccli –h <SP_IP_address> getcrus –lccreva –lccrevb
-or-
 Navisphere Manager: Expand the array’s navigation tree to show the elements under
Physical > DAE-ATA > LCC or BCC, right-click on the icon for either SP A’s or SP B’s
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

EMC CONFIDENTIAL version: 6.0.0.41

33 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

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

86. 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

87. Restart all stopped SAN Copy sessions and any other replication software activities that were
stopped prior to this code load

88. 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
during powermt restore.

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

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

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

EMC CONFIDENTIAL version: 6.0.0.41

34 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

92. 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
93. 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

94. 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
95. 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 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.
96. 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

 Post hardware/software upgrade procedure cnhas020_R021

97. Check for any fault lights on the array if you have not already done so, and investigate the cause and
resolve before proceeding further.
£
98. Collecting CLARiiON Storage System information:
£
a. Start NST or USM and log into the storage system if you have not already done so
b. NST: Select Hardware Maintenance, from the left pane.
USM: Select Diagnostics, Verify Storage System
c. Follow the prompts to generate the report.
d. The issues report will be generated. Save the report if desired.
This procedure generates the following files which are saved in the repository:
 A combined SPCollects file
<repository location>/<serial

EMC CONFIDENTIAL version: 6.0.0.41

35 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

number/HCK/<date>_<time>_CLARiiON_Healthcheck_<serial
number>_<date>_<time>.zip
 An XML file
<repository location>/<serial number/HCK/<date>_<time>.CAP_<serial
number>_<date>_<time>.xml
e. Review the report. If there are any new issues address them and rerun Verify Storage System.
f. Review the SP Event logs for any issues, or run TRiiAGE and review the Triage_Analysis.txt file
that is created. If you need assistance running TRiiAGE, contact the Support Center.
To run TRiiAGE:

Note: This example assumes TRiiAGE is installed and in the DOS path, and that the 2 SP Collects are
in the working directory, not zipped up in the Healthcheck file.
Note: This example shows the command for reporting log entries created during the last 5 hours; this
can be changed depending on the time period to be reviewed. If the hours parameter is not used, the
default is 30 days.

Enter: C:\Data\customer>triage -hours 5 -c

This will review the SP logs for the last 5 hours and create the following report:

TRiiAGE REV: 26.0.6 BUILD DATE:

030410
************************************************************************
*******

Input specified: [ triage -hours 5 -c ]

Generating: [ 5 hour ] TRiiAGE Analysis.
Accessing TOOLS in: [ C:\Tools ]
…………….

When the program is done, review the TRiiAGE_Analysis_5hour.txt file for unexpected errors
during the NDU. Address any issues that are reported.

99. Post Software/Hardware Upgrade File Upload:

£
You will have been asked to send information at the end of your activity. This information will be used
to update the EMC SYR repository.

Table of Contents

 Restore array call home monitoring cnalr020_R010

100. Once the maintenance procedure is complete you must restore call home for the array you disabled  Done
from calling home. The FLARE release running on the system and CLARalert/ESRS IP Client version

EMC CONFIDENTIAL version: 6.0.0.41

36 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

running in the environment determines which method you should perform re-enable call home for the
array.

Method 1 is the preferred and the most common method of disabling call home for non NDU activities
where you enable/disable “Silent Mode” on the storage system. Systems running less than FLARE
Release 22 require that you use method 3 or 4 to disable call home where you manually reconfigure
Navisphere/Unisphere Event Monitor

101.
CLARalert 6.22.X or greater Arrays running Release 22 or greater Central and Distributed
Monitoring configuration (method 1)
Disable/Enable Responses (quiet mode) feature will automatically re-enable call home when the timer
you set to disable call home expires. Perform these steps only if you need to re-enable call home
immediately before the timer expires.

IMPORTANT: IMPORTANT! Network connectivity between the array you are upgrading and the call-
home monitoring station is required for the Software Assistant to automatically enable call-home and
verify the call-home rules.

g. Log into the Navisphere/Unisphere Manager domain that contains the array call home was disabled
on.
h. From Navisphere Manager select the Monitors tab and right click the array SP A monitor you are
enabling and select Disable/Enable Reponses. De-select Disable/Enable Responses check box
and click OK.
i. From Unisphere Manager select Monitoring > Event Notification > Distributed Monitors. Right
click SP A monitor you are enabling and select Disable/Enable Reponses. De-select
Disable/Enable Responses check box and click OK.
j. Repeat step b or c for SP B

IMPORTANT: IMPORTANT! You MUST enable responses on BOTH SP A and SP B to enable the
array call home.

k. The array will now call home or responded to any other template applied to the array.

102.
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher 
Central Monitoring configuration (method 2)

Navisphere Service Taskbar v6.26.5 or greater and Unisphere Service Manager will automatically
attempt to enable central monitoring call home response when performing an NDU via the Software
Assistant. The install wizard will try to add the array to the configuration when the user clicks “Next” on
the Software Maintenance Status screen. The user will not be able to close NST until the install wizard
has tried at least once to restore the configuration i.e., until the user has clicked “Next” at least once on
the Software Maintenance Status screen. If the Wizard fails to enable call home or you are enabling
call home for other than an NDU or disconnected the array network management ports from the
customer network and used your laptop to perform the NDU perform the steps below to manually
enable call home.

IMPORTANT: IMPORTANT! Network connectivity between the array you are upgrading and the call-
home monitoring station is required for the Software Assistant to automatically enable call-home and

EMC CONFIDENTIAL version: 6.0.0.41

37 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

verify the call-home rules.

a. Log into the Navisphere/Unisphere Manager domain that contains the array call home was disabled
on.
b. From Navisphere Manager select the Monitor tab, right-click the central monitor, and click Monitor
System. In the Select System window that appears, select the array you disabled from the drop-
down list and click OK.
c. From Unisphere Manager select Monitoring > Event Notification > Cenralized Monitors. Right
click the central monitor and select Monitor System. Select System opens, select the array you
disabled and click OK.
d. The storage system is now restored to the Central Monitor configuration and call home for the
system is re-enabled.

103.
CLARalert 6.7 through 6.22.X or higher Arrays running Release 14 through Release 22 or higher 
Distributed Monitoring configuration (method 3)
Navisphere Service Taskbar v6.26.5 or greater and Unisphere Service Manager does not enable a
CLARalert distributed monitoring call home response. Follow the steps below to enable distributed
monitoring call home.

a. Log into the Navisphere/Unisphere Manager domain that contains the storage system call home
was disabled on.
b. From Navisphere Manager select the Monitor tab, expand the storage system you disabled SP A
monitor icon. Right click the array icon under SP A monitor and select Monitor Using Template
from the drop down menu. From the dialog box template drop down list select the Call-Home
template and click OK.
c. From Unisphere Manager select Monitoring > Event Notification > Distributed Monitors. Right
click SP A monitor you are enabling and select Use Template. Select your Call Home template
and click OK.
d. Repeat step b or c for SP B.
e. The storage system is now restored to the Distributed Monitor configuration and call home for the
array is re-enabled.

Table of Contents

Using the Install Base Group (IBG) Business Services Portal

Note: This procedure is only valid for EMC employees. EMC Service Partners should continue using the
Partner Notification Tool (PNT) or the Storage System Registration Utility (also known as ARU) to update
the EMC Install Base.

Business Services Portal: Provides a centralized location for users to submit requests directly to the
Install Base Group. The Portal is accessible outside the EMC network.

EMC CONFIDENTIAL version: 6.0.0.41

38 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

IMPORTANT: Completion of this activity is a mandatory requirement to closing a CSI Service

Request.

1. [ ] Navigate to http://emc.force.com/BusinessServices to access the Portal (Figure 1)

Figure 1 Navigate to Business Portal

2. [ ] On the Business Services Portal home page, navigate to the Post Sales section and click
on ‘Install Base Group’ (Figure 2)

Figure 2 Install Base Group Link

3. [ ] This will bring you to the Install Base Group case creation page. Make sure to choose the
specific Case sub-type for your request from the dropdown menu (Fig 3):

Note: If entering extra data not included in the chosen Case sub-type, enter the extra data in the
Description field or attach a document with the extra data.

Figure 3 Case Sub-Type Selection

Sub-Type Selections:
a. IB Status Change - Update the status in the Oracle Install Base
b. PDR Update - Add or change Preferred Dispatch Resource on a TLA

EMC CONFIDENTIAL version: 6.0.0.41

39 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

c. Move or Party Change - Move or change what customer a TLA is located at

d. Upgrade/Conversion - Updating a product to the latest version based on a Sales Order Shipment
e. Debrief - Part Usage on the different task types in Oracle
f. Model Quantity Update - Changing the quantity on a Model in the IB
g. Secure Credentials - SP Upgrades and enabling the field to obtain secure credentials
h. Other - All other requests that don’t fit into categories
i. Model Separation - Splitting multiple models into single instances
j. Microcode Update - Updating the microcode to the desired version

Note: Once a sub-type is chosen, click on the ‘Select’ button which will populate the form with all the
relevant fields for your specific service request

4. [ ] Populate your contact name, e-mail address, phone and theatre (Fig 4)
You can also include the e-mail addresses of any other users that you would like to include on this
request in the ‘Additional Notification Email’ fields

Figure 4 Contact Form

Note: All fields marked in red are required for submission

5. [ ] In the Case Details section, populate the ‘Subject’ and ‘Description’ fields to provide
details on the type of support needed (Fig 5)

Figure 5 Case Details

EMC CONFIDENTIAL version: 6.0.0.41

40 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

Note: If this is a Federal request, make sure to check the “Federal Case’ check box. If not, do not make
a Federal Case out of it.

6. [ ] Select the corresponding Product Families that apply to your request (Fig 6)

Note: Family is defined as the TLA/Model product family for your request. If you have multiple product
families in your request and one of them is listed here, choose that family, otherwise choose All Other
Families

7. [ ] Fill out the additional fields that are relevant to your specific Case sub-type (Fig 6)

Figure 6 Product Information

8. [ ] If you need to include additional documents with your request, navigate to the Upload
Attachments section and click on ‘Choose file’. Provide details on the file selected in the ‘Description’
field (Fig 7)

Figure 7 Upload Attachments

9. [ ] Once you have provided all the relevant information and included any necessary
attachments, click on the ‘Submit’ button (Fig 8)

Figure 8 Submit

EMC CONFIDENTIAL version: 6.0.0.41

41 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

10. [ ] This will send the request to the Install Base Group for their review. You will receive
automated e-mail notifications to stay up-to-date on the progress of your request (Fig 9)

Figure 9 Done

 Appendix: Locating the CX3-Series Service LAN port cnlan190_R001

104. Connecting your laptop to the Service LAN port allows management and code loads without having to P Done
load code to a customer system or put your laptop on the customer’s network.
£
Note: The storage system’s internal network (Service LAN) is mutually exclusive from the customer’s
main management ports on the SP.

The Service LAN of the two SPs in every CX3-Series storage system 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)

105. Locate the Service LAN port using the applicable figure below for your storage system model:
£
CX3-80: The Service LAN ports are on the A-side and B-side management FRUs. The primary LAN
management and SPS connectors are on this same FRU. When you connect to the B-side
management FRU Service LAN port, you are actually connected to SP-A, and must use its IP address.

Figure 1 CX3-80

CX3-40-Series/CX3-20-Series/CX3-10c/CX3-10DC: On CX3-40-Series, CX3-20-Series, CX3-10c,

and CX3-10DC models, the Service LAN ports are on the SPs directly beneath the primary
Management LAN port. It is important to remember that when you connect to the Service LAN port on
SP-A, you are actually talking to SP-B and you must use its IP address and vice versa. The figures
below show the location of the Service LAN port on CX3-40-Series and CX3-10c models. The location
is the same for a CX3-20-Series and CX3-10DC as indicated.

EMC CONFIDENTIAL version: 6.0.0.41

42 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

Figure 2 CX3-40/CX3-20/CX3-10DC

Figure 3 CX3-40c/CX3-20c

Figure 4 CX3-40f/CX3-20f:

EMC CONFIDENTIAL version: 6.0.0.41

43 of 44
 EMC ® CLARiiON ™ SolVe Generator
Solution for Validating your engagement

Figure 5 CX3-10c

Table of Contents

EMC CONFIDENTIAL version: 6.0.0.41

44 of 44