EMC2 EMC CLARiiON

Software Updates on a CX Series Array

Support
Procedure CLAR-PSP-084

REVISION HISTORY:
3/10/03 Initial release to support the GA of Release 11 software of
4/04/03 Reformatted for clarity regarding the need to add Utility partition and
recover image during the update.
4/15/03 Added step to remove Snap Cache LUNs from the Snap Cache LUN pool
during the NDU process of updating core to Release 11
5/7/2003 Removed references to CDs for Recovery images.
06/16/2003 Update procedure and array based revisions of software.
06/18/2003 Add note on Primus case for using a LAN cross-over cable for NDU

Introduction

This document describes the procedure for updating CX-series arrays based
software using the Non-Disruptive Upgrade (NDU) capability of the array.
Please read all the rules and comments about updating a CX-series array
based software. 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 fail-over
software or they will lose access to the array. It is important to ensure that I/O
is at a very low level when this update is performed. Times of heavy I/O should
be avoided. The revision level of software running on the array before the
update can impact the process. Reference Table 1 to understand current and
previous array based software revision levels. The update procedure differs if
the revision of software, which the array is running, is earlier than Release 11
(R11). If updating from a release prior to Release 11 (definition below), you
must load the “Utility Partition. The Utility partition allows for recovery of a
corrupted boot image for SPA or SPB.

Read this entire document before beginning an NDU software update.

CLAR-PSP-084 Page 1 of 23
Updating software on a CX Series Array

Definitions
Flare Software available prior to Release 11
o CX200 – Core SW 02.03.x.20.5.xxx 6.2 Navisphere Array
components (release 10 Cx200 only)
o CX400 – Core SW 02.02.x.40.5.xxx 6.2 Navisphere Array
components (release 8)
o CX600 – Core SW 02.02.x.60.5.xxx 6.2 Navisphere Array
components (release 8)
o CX600 – Core SW 02.01.x.60.5.xxx 6.1 Navisphere Array
components (release

Release 11 Software Flare Software

o Core SW 02.04.x.XX.5.xxx with Navisphere 6.4 components for
all CX arrays.
.20 – CX200
.40 – CX400
.60 – CX600

NDU Software Update Types (visible in the NDU dialogue box during the
process.)
9 Disruptive – Updating an array with one functioning Storage
Processor. This is standard for a CX200LC but is only possible
if in engineering mode for all other array types via the GUI.
Navisphere CLI will prompt you for a confirmation.
9 Non-Disruptive – Updating an array that has 2 functioning
Storage Processors. Each Storage Processor updates
individually, always leaving one working on the array. If all
Servers have valid fail-over software, this typical update will not
disrupt server access to data on the array.
9 Rebootless – This type of Software update will reboot neither
storage processor. A Server will not be affected at all during
this procedure.
9 Utility Partition – Software loaded to previously unused but
reserved space on the first 4 drives of a CX-Series array that
provides menus/utilities to perform recovery and conversion of
an array.
9 Repository – A previously reserved but un-used space on
drive 0_4 (5th drive) in the boot chassis that holds Recovery
images that are NDU’d to the array or added via the FTP
method.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 2 of 23

Updating software on a CX Series Array

Utility Partition FAQs

Q What is the Utility Partition
A It is a new section added to each of the Fibre Channel boot drives. It is
loaded to previously un-used but reserved space. User space is not
affected between earlier releases and Release 11.

Q When is it loaded
A All arrays shipped since March 10th 2003 have the Utility partition pre-
loaded to each of the first 4 drives. In addition, there is a recovery image
preloaded at the factory. This Image is loaded to private space on drive 4
called the “repository”

Q How do you get to the Utility Partition

A To get to the utility partition, you interrupt the power up Of one of the SPs
during its POST test. When the correct password is entered, a menu is
presented. One of the options is to boot the utility partition. This tells the
SP to boot the alternate code rather than the standard NT image it would
typically boot.

Q Why would I want to Boot the Utility Partition

A The Utility partition allows you to use a recovery image to re-image a
corrupted boot image on one of the two mirrored boot pairs or to convert
the array from one CX type array to another.

Q Where exactly is the utility partition

A It is on the first 4 drives. It is in previously unused but reserved space.
The Utility partition area is on the Alternate boot drives. SPA boot drives
are drives 0 & 2, but it’s Utility boot area is on drives 1 & 3. SPB primary
boot drives are drives 1 & 3 with its Utility boot partition on drives 0 & 2.

Q What is the image repository

A This is an area on drive 4 that holds a recovery image or a conversion
image.

Q Where is it documented about the use of the Utility partition

A Clar-psp-078 documents and illustrates the use of the utility partition to
recover a corrupted boot image of an SP.

Q Why do some files have a .NDU extension and some have .MIF
A The Utility partition is available only as a .NDU file and must be loaded via
an NDU operation. The Recovery image is available as a .NDU file and a
.MIF. The .MIF is the version that is FTP’d directly from your laptop to the
SP. See clar-psp-078.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 3 of 23

Updating software on a CX Series Array

Rules for NDU

When performing software updates on a CX-Series array there are some
important RULES that always apply.
9 RULE - There should be no faults on the array. A green flashing SPS
indicating a charging SPS is acceptable.

9 RULE - Do Not Start an NDU operation if there are any LUN rebuilds, disk
equalizations, or Raid Group/LUN expansions in progress.

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

9 RULE – Load a Utility partition via NDU If updating from a release prior to
Release 11. This is done AFTER the array is running Release 11 minimum.
9 RULE All connected servers must have working and supported “path-
failover” software in order to perform this procedure. If they do not, stop and
prevent all I/O from that server to the array
9 RULE - Confirm that there is at least one working path from each
connected server to each Storage Processor of the array
9 RULE - You cannot NDU a new revision of code to the array if the previous
revision requires a commit. Perform a commit on the “active” version if the
Array software Tab shows that a “commit” is required.
9 RULE - All array based software within a “release” must be updated at the
same time unless stated otherwise. See the Software revision table in this
document.
9 RULE - CX600, CX400 and CX200 arrays should have less than 100 I/Os
per second to each of the first 4 drives in the array (drives 0_0 through
0_3). This low I/O activity to the boot drives ensures that the NDU will have
no time-out problems and will finish successfully. See appendix A for
instructions on measuring them I/O rate to the first 4 drives. This procedure
may not be necessary if there is little or no I/O running.
9 RULE - Following an NDU where Navisphere Management Server or the
Manager UI is revised, you MUST close your browser and re-open it in
order to use the new content that may be in the new revisions of
Navisphere Management server or UI.
9 RULE - Navisphere agents and CLI on Servers must be no more than one
revision behind the SP based Navisphere agent.
9 RULE – Navisphere CLI (being used to manage) must be equal to or one
revision greater than any Navisphere Host or SP Agent it will manage
9 RULE - Host based AdmSnap software must be at the same revision as
SnapView running in the array
9 RULE - If updating FROM a version prior to Release 11, add the Utility
Partition and the Recovery Image via a second NDU AFTER the array has
been update to Release 11 or higher.
9 RULE - Stop all SAN Copy sessions before starting an NDU
9 RULE - Stop all Snap Sessions prior to NDU

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 4 of 23

Updating software on a CX Series Array

9 RULE - Move Snap Cache LUNs out of the Snap Cache pool prior to NDU.
9 RULE – CLARalert software must be at the same release level as the SP
Agent
9 RULE – The Navisphere Agent used by the CLARalert monitoring (dial-
home) workstation must be at the same level as the SP Agent
9 RULE – Access Logix must be already loaded on the array before
SnapView or MirrorView, can loaded for the first time.
9 RULE - The Software Installation Wizard is for the CX200 and CX200LC
only.

Notes &
Warnings about
NDU
General comments

• When updating an array, all array based software to be updated MUST BE

updated via the SAME NDU software load. Perform ONE NDU operations
with all the software you intend to update. You will get a dependency error if
one of the already installed packages is missing from the NDU package set.
Check that you have updated revisions of all packages currently loaded on the
array.
• There are several Primus cases available to help diagnose NDU issues. Search
Primus using “NDU” as a keyword if needed.
• Loading the Utility Partition and the Recovery image is not required if updating
from Release 11 to Release 11-patch. It should already be loaded
• COMMIT - You cannot NDU a new revision of code to the array if the previous
revision requires a commit. Perform a commit on the “active” version if the Array
software Tab shows that a “commit” is required.
• The Software Installation Wizard is for use with the CX200 and CX200LC only
and automatically adds a 6 minute delay between SP reboot during the NDU
process, regardless of what you put for a delay.
• CX400 and CX600 Updates should use the standard Software update window
which has been moved to engineering mode in Navisphere 6.4.x
• No Update of the Utility partition or the Recovery Image is required if
updating to release 11.007 from a prior version of Release 11. See the table
later in this document.
• Using a Cross-over LAN cable connected to one SP will result in NDU failure
if updating to SnapView 2.10.06 if the solution procedure in Primus solution
emc69371 is not followed. When SnapView is being updated to Version 2.10.06
the 2 Storage Processors MUST be able to communicate with each other on the
same LAN in order for the NDU to complete if updating SnapView that is already
loaded. Primus solution emc69371 is a workaround solution to perform an

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 5 of 23

Updating software on a CX Series Array

NDU updated to SnapView 2.10.06 from a LAN crossover cable to one SP.
Notes for specific
attached host
environments
AIX Servers
• Stop all I/O from any connected AIX server during the NDU process if
it is running the native HBA driver. See primus emc67186

Red-hat Linux Servers

• Stop all I/O from any connected Red-hat Linux host during the NDU
process.

Solaris Servers
• Ensure that the no-device-delay setting is configured to '0' (zero) in
lpfc.conf. See PRIMUS emc66969
• NDU Delay - The Software Installation window of the Navisphere
Manager GUI has a check-box for NDU delay. When checked, the
default for time will be 360 seconds. When there is a Server zoned to
the array that has DMP fail-over software, use the default of 360
seconds.

Window 2000 Servers

• If the array that has a W2K server zoned to it and that W2K server is
using Dynamic Disks you must use an “NDU delay” of 360 seconds
when a Software NDU is performed. The NDU Wizard automatically
invokes a 360 second delay. It must be manually entered when not
using the Software Install Wizard.

Notes on NDU with

layered Applications
SnapView
• SnapView 1.30 and higher allocate Cache LUNs completely differently
than earlier revisions of SnapView, See clar-psp-073
• Stop all SnapView sessions
• Move Snap Cache LUNs out of the Snap Cache POOL prior to NDU.

• Using a Cross-over LAN cable connected to one SP for NDU will

result in failure if updating to SnapView 2.10.06 if the procedure in
Primus solution emc69371 is not followed. When SnapView is being
updated to Version 2.10.06 the 2 Storage Processors MUST be able to
communicate with each other on the same LAN in order for the NDU to
complete if updating SnapView that is already loaded. Primus solution
emc69371 is a workaround solution to perform an NDU updated to
SnapView 2.10.06 from a LAN crossover cable to one SP.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 6 of 23

Updating software on a CX Series Array

MirrorView
• Do not “deactivate” a mirror prior to an NDU. In fact, deactivating the
mirror will cause all server access to the primary LUN to be lost until the
Mirror is reactivated.
• Multiple Arrays involved in a MirrorView Configuration should not be
targeted during the same software NDU operation you should perform
the NDU on one Array at a time.
• Provided the software on the arrays is within 2 revisions, no special
preparation of the mirrors is required prior to an NDU. The array
software ensures that mirrors continue to operate correctly during an
NDU, without requiring a full re-synchronization of any secondary
image. System fractures are a normal part of the NDU operation, but
these result in partial re-synchronization only (which will automatically
start if the mirror recovery policy is set to “Automatic”)

If the destination revision is more than two revisions higher than

the current revision, you have 2 options
• Stop all I/O to the Mirrors before proceeding otherwise they will
become more than two revisions apart after the update of one
of the arrays.
• Update all the array based components of each array in
increments until the final destination, to ensure they are never
more than 2 revisions apart.

Clones
• Do not start an NDU operation while there are more than 4 reverse
synchronization operations active on the array.

San Copy
• All San Copy sessions should be stopped prior to NDU.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 7 of 23

Updating software on a CX Series Array

NDU Procedure 1. Repair any Faults on the array - Confirm there are no faults on the array
before you begin
2. Confirm valid working failover software and access to both SPs for
each Server with access to the array.
3. Ensure you have new versions of all array based software currently
running.
4. Ensure there are no LUN Rebuilds, Equalizations or RG/LUN
Expansions in progress. If there are, wait for them to complete.
5. Download the appropriate Recovery image and Utility partition (if
required) before starting the update.
6. Put all files to be updated, into the same directory on your Service laptop
or server you will be using to run Navisphere Manager. See the software
compatibility table in this document. As a general rule, all array-based
software must be updated at the same time via the same NDU.
7. Before SW update Measure I/O to the first 4 drives of the array
(CX200, CX400 and CX600) and ask the customer to reduce the I/O if
possible. There should be no more than 100 I/Os per sec to the first 4
drives.
8. Stop all snap sessions
9. Move all Snap Cache LUNs out of the Cache LUN Pool
10. Connect to the array using Navisphere Manager.
11. Enter Engineering mode (note: the Software Installation Wizard can be
used only for the CX200 and CX200LC)
12. Perform the Software update
• Right-click the array icon
• Select the array properties and the array Software tab of the
properties dialogue.
• Choose the update option and browse to the files to be updated
• Load the selected files.
13. Monitor status via the status window which automatically opens. When
the status “operation has completed successfully” appears, the update is
complete.
14. Confirm that the new SW is listed as ACTIVE via the Software tab of the
array properties dialogue box.
15. COMMIT the new Base (Flare or Access Logix) code.
16. Refresh the VIEW of the Browser. This step is necessary to begin using
the new Navisphere UI loaded to the array.
17. If Power path is running and LUNs are not listed under their default
owner, perform a powermt restore.

18. Ensure that all servers have access to their data

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 8 of 23

Updating software on a CX Series Array

19. Return Snap Cache LUNs to the Cache pool If previously removed and
restart snap sessions as needed.

20. If updating FROM a version of Core Software prior to Release 11 (see

definitions section), perform a second NDU Software update to the
array to load the Utility partition and the recovery image.
These will not be visible in the array properties tab after they are
loaded
NOTE: If the NDU of these files should fail with an error “An
attempt to save the software package to persistent storage failed”,
start the NDU process over and load only the Utility Partition. The
Recovery Image (.mif version) can be loaded via FTP at this time
or can be loaded later as needed, if the boot drives need to be
recovered. Recovery Files to be loaded are large files. They are
available on the Global Services WEB page and the
EMC/CLARiiON Partners Page in the Software Download
sections.

“Loading it via FTP at this time will be disruptive to the customer since you
must reboot one of the SPs and use it to add the recovery image to the
array. If this activity is not appropriate for this time it can be added to the
array at the time of need, without further interruption to the customer.”

NOTES:
o See Section in this Document titled “Utility Partition FAQs
o See Appendix B in this document for instructions for using the
Utility Partition and loading the recovery Image via the FTP
method.
o Refer to CLARiiON procedure clar-psp-078 for further
instruction on adding and using a recovery image.
21. Update CLARalert If installed and test call home

22. Confirm that there are no array faults (the SPS units may still be charging
based upon the SP reboots, this is normal).

23. Confirm that Cache Settings are set properly. If new layered applications
are being added, Cache setting may not be able to be set as they were
previously.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 9 of 23

Updating software on a CX Series Array

CX-Series Array based Software Compatibility

• If updating from one release to the next, update all the below “array-based” software via the same
software update
• Arrays shipped from the factory with Release 11 code on them had the utility partition and recovery
Image pre-loaded. Reloading the Utility Partition and Recovery Image is NOT required if updating from
Release 11 to Release 11 patch.
• There was not a release 9
• Latest Versions are noted below in RED

Release... Rel. 7 Rel. 8 Rel. 10 Rel. 11 Rel. 11 patched Rel 11

(05/08/03) .007 patch
Date of
release (08/02) (10/02) (12/02) (03/03)

CX600 Flare 02.01.0.60.5.x 02.02.0.60.xxx Not revised 02.04.0.60.5.002 02.04.0.60.5.005 02.04.0.60.5.007

xx
CX600 02.01.1.60.xxx 02.02.1.60.xxx Not revised 02.04.1.60.5.002 02.04.1.60.5.005 02.04.1.60.5.007

Access
Logix
CX400 Flare Not released 02.02.0.40.5.xxx Not revised 02.04.0.40.5.002 02.04.0.40.5.005 02.04.0.40.5.007

CX400 Not released 02.02.1.40.5.xxx Not revised 02.04.1.40.5.002 02.04.1.40.5.005 .02.04.1.40.5.007

Access
Logix
CX200 Flare Not released Not released CX200 introduced 02.04.0.20.5.002 02.04.0.20.5.005 02.04.0.20.5.007
02.03.0.20.5.xxx
CX200 Not released Not released CX200 introduced 02.04.1.20.5.002 02.04.1.20.5.005 02.04.1.20.5.007
02.03.1.20.5.xxx
Access
Logix
SnapView 1.5 2.0 Not released 2.1 2.10.04 2.10.06

MirrorView 1.5 1.6 Not released 1.7 1.70.02 Not revised

Not released Not released 01.00.02 01.01.01 Not revised Not revised
HA Enabler

Thirty Drive Not released Not released

Enabler 01.00.02 01.01.01 Not revised Not revised

Navisphere
Components 6.1.0 6.2.0 6..2.0 6.4.0 & 6.41 UIs Not revised Not revised
(The
Management
Svr/Agent went to
6.2.1)

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 10 of 23

Updating software on a CX Series Array

NOTES
1. Host Navisphere Agents follow the array based agent revision (one rev back on the host agent is
acceptable)
2. Host based AdmSnap revisions must follow the revision of SnapView
3. Navisphere UIs revised to 6.4.1 after Rel 11 GA and before 11+ GA
4. All Release 11 components are compatible, but the latest versions should always be run together
5. HA enabler is CX200 Only
6. Thirty-drive option is CX200 only (std for EMC customers)
7. Navi Base components for CX200 only
8. It is NOT required to update the Utility partition or the Recovery Image when going from Release 11 to
Release 11 .007.

Appendix A - Measuring I/O to the Boot Drives of a CX array.

To ensure the success of NDU operations on CX200, CX400 and CX600 systems, the I/O level on first
four disk drives (FRUs 0, 1, 2, 3) should be measured prior to executing an NDU operation.

• If the I/O level to any of these disk drives is higher than 100 IOs per second, the NDU should be
postponed or the IO load to the LUs based on these CRUs should be reduced until the I/O load
falls below these thresholds.
• The NDU may Time-out and fail if any of the first 4 drives are performing greater than 100 IOs per
second.

Using Navisphere Manager

1. Enable Performance Statistics

If the gathering of performance statistics is not currently enabled, it must be turned
on. To do this, right click on the CX400/CX600/CX200 array name, then select
"Properties". Select (check) both the "SPA Statistics Logging" and "SP B Statistics
Logging" checkboxes then click the "Update" button.

2. Gather Performance Statistics

Select (expand) the "Physical" attributes Icon in the tree, followed by selecting
(expanding) the "Bus 0 Enclosure 0" attribute selector. The first four FRUs (disk
drives) will be listed as "Bus 0 Enclosure 0 Disk 0", "Bus 0 Enclosure 0 Disk 1", "Bus
0 Enclosure 0 Disk 2", and "Bus 0 Enclosure 0 Disk 3".

For each of these disk drive selectors, right click on the selector, then select
"Properties". Select the "Statistics" tab in the new window. Add together the "Read
Throughput (IO/Second)" and "Write Throughput (IO/Second)" statistics to produce
the current number of I/O requests per second for the indicated CRU (disk drive). If
the values are displayed as "unavailable", go back to step one above to enable
gathering performance statistics.

The I/O requests per second load for the first four disk drives should each average
under 100 I/O requests per second on a CX200, CX400 or CX600.

3. Return Statistics logging to its setting

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 11 of 23

Updating software on a CX Series Array

When complete, ensure that the “check boxes” in the Array Properties dialogue box
which “enable statistics logging” for each SP are returned to the way they were prior
to this procedure.

Using the Navisphere CLI Interface

Enable Performance Statistics

If the gathering of performance statistics is not currently enabled, they must be turned-on
on both SPs. To do this, issue the following commands:

navicli -h <SP-A address> setstats -on

navicli -h <SP-B address> setstats -on

Gather Performance Statistics

The overall procedure for gathering performance statistics, using the first disk drive as an
example:

Example for Drive 0

1. Execute the Navi CLI command from a server with LAN or PPP access to the array.
navicli -h <SP-x address> getdisk 0_0_0

This gives Read and Writes since boot of the array. Note the results

2. Wait period (30 seconds recommended)

3. Request current performance numbers again

navicli -h <SP-x address> getdisk 0_0_0

4. Subtract the original cumulative read and write values returned in step one from the
values returned in step three and then add the two differences together to produce
the total number of I/Os performance for the wait period.

5. Divide the total number of I/Os by the wait period (in seconds) to produce the number
of IOs per second.

Example: First execution = 100,000 IOs (read and write combined)

Second execution = 100,995 (read and write combined)
Subtract 100,000 from 100,095 = 995
995/30 (30 “wait seconds”) = 33.2 I/Os per second for this drive.

The five steps above must be executed twice - once for SPA and once for SP-B for a
given disk and the number of IOs per second added together to produce the total number
of IOs per second for the disk drive.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 12 of 23

Updating software on a CX Series Array

The five steps above must also be executed on both SPs for all of the first four disk drives
(0_0_0, 0_0_1, 0_0_2, and 0_0_3).

The I/O requests per second load for the first four disk drives should each average under 100 I/O
requests per second on a CX200, CX400 or CX600.

Reducing Array I/O Load

If the I/O load exceeds the recommended limits listed above, it must be reduced for the LUs (disk
Logical Units) based on these disk drives. The Navisphere Manager windows and Navisphere
CLI commands used above to gather the statistics data display the LUNs based on these disk
drives.
When Complete, return the Statistics logging capability to off

navicli -h <SP-A address> setstats -off

navicli -h <SP-B address> setstats -off

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 13 of 23

Updating software on a CX Series Array

Appendix B - Loading a CX Recovery Image via the FTP method

The following procedure can be done to load the Recovery image to an array if the Utility partition is already loaded but the
Recovery image is not loaded or it fails to load via NDU with an error message similar to “attempt to store image to
persistent storage failed” .

1. Connect a serial cable from a Windows server/desktop/laptop. The cable connects from a Comm port on the computer to
the Serial Port on SPA. Use the characteristics below.
The Comm Port on the computer should be set to;
9600 baud
8-bit
No parity
1 stop-bit,
No flow control.
2. Open a hyper-terminal session on the Windows server/desktop/laptop using the port characteristics above.
3. While monitoring the hyper-terminal session, reboot SPA by entering Engineering mode and re-booting SPA. Note: SPB
Can be in and running I/O at this time.

4. The Storage Processor will begin its boot sequence running BIOS and POST Tests. While monitoring the power-up
sequence of the Storage Processor be prepared to interrupt this process by hitting the Esc Key on your keyboard at
anytime during the printout of this string of Alpha characters as noted in the figure below.

Hit Esc during this

alphabetical sequence

DB_key

5. Following the printout of the text “Call your service Representative” type the characters DB_key followed by an “enter”
on the keyboard. It is case sensitive
6. This will display the Diagnostic Menu a screen similar to the following figure

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 14 of 23

Updating software on a CX Series Array

7. Select the Image Sub-Menu

8. Note : The menu options and numbers will likely vary from product to product or revision to
Revision but “Image Sub-Menu” will always be available

9. The Image Submenu will be displayed as shown below. Select “Utility Partition Boot”. This means the SP you are
attached to will boot from the Utility partition of that alternate SP’s boot drives. The reason for this is to provide an
operating system that will allow the system to perform the tasks associated with system recovery.

10. You should then see the screen below. Press enter to continue to the Clariion Utility Toolkit Main Menu. If this screen
does not appear, the Utility Partition for this SP is not bootable. At this point, we have two options: 1) Attempt to boot

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 15 of 23

Updating software on a CX Series Array

the peer SP to its Utility Partition, or 2) Go to Scenario 2 at the beginning of this section, and install a Utility Partition
Image and a Recovery Image via NDU.

11. Select Enable LAN Service Port from the following menu

12. Enter the characteristics of the LAN Port of the SP which you are physically connected to via the serial cable.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 16 of 23

Updating software on a CX Series Array

13. Select Y at the following menu

14. After you answer Y from the previous Window, Open a browser or FTP Client software package. Type in the LAN
address of the SP you are connected to via the serial cable. . In the example below it is ftp://10.14.1.174. A Login
window will open as displayed below. The Username is clariion, the password is clariion!

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 17 of 23

Updating software on a CX Series Array

15. Open a Windows Explorer window, Drag and drop or move/copy the Recovery .mif file from the CD noted earlier in
this document or previously downloaded to your service laptop, to the large FTP window just opened.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 18 of 23

Updating software on a CX Series Array

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 19 of 23

Updating software on a CX Series Array

16. When the File is loaded to the FTP Window (actually loaded to a temporary area known as the RAM Disk) go back to
the Hyperterminal Window which is still open. Select Image Repository Sub-menu

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 20 of 23

Updating software on a CX Series Array

17. From the above screen, select Copy files from RAM disk to Repository. This copied the recovery file from the SP
memory to the repository on Drive 0_4.

18. Confirm your selection.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 21 of 23

Updating software on a CX Series Array

19. The above screen confirms that the file has been copied from RAM Disk to the repository. Go back to the main menu
and select RESET SP-A

20. At the main menu select Reset Storage Processor.

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 22 of 23

Updating software on a CX Series Array

21. Remove the Serial Cable from SPA and Ensure that SPA boots as normal. Confirm via Navisphere that the SP is running
the correct SW. Perform a commit of the Base SW if the SW Status Tab in Navisphere states that a commit is required.

END

EMC2 Global Services, Coslin Drive, Southboro, MA 01772 Page 23 of 23