Silicon Graphics InfiniteStorage 4000 Series Installation and operation manual

SGI InfiniteStorage 4000 Series and 5000 Series
System Upgrade Guide
(ISSM 10.83)
007-5878-001 August 2012

The information in this document supports the SGI InfiniteStorage 4000 series and 5000 series storage
systems (ISSM 10.83). Refer to the table below to match your specific SGI InfiniteStorage product
with the model numbers used in this document.
SGI Model # Netapp Model
Netapp
Compliance
Model Notes
TP9600H 6091 1500
TP9700F 6091 1500
IS4500F 6091 1500
TP9600F 3994 and 3992 4600
IS4000H 3994 4600
IS350 3992 4600
IS220 1932
1333
DE1300
3600
IS4100 4900 4600 FC HICs only
IS-DMODULE16-Z FC4600 4600
IS-DMODULE60 DE6900 6900
IS4600 7091 1550 4Gb FC, 8Gb FC, HICs
only
IS5012 2600 3650 FC and SAS HICs only
IS5024 2600 5350
IS5060 2600 6600
IS-DMODULE12 & IS2212
(JBOD)
DE1600 3650
IS-DMODULE24 & IS2224
(JBOD)
DE5600 5350
IS-DMODULE60-SAS DE6600 6600
IS5512 5400 3650
IS5524 5400 5350
IS5560 5400 6600

ii Copyright information
Copyright information
Copyright © 1994–2012 NetApp, Inc. All rights reserved. Printed in the U.S.A.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE
HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein, except
as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a
license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987)

Trademark information iii
Trademark information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch,
ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express,
ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru
DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView, FlexCache,
FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go
further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP,
MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro, OnCommand,
ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen, SANshare, SANtricity,
SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape, Simplicity, Simulate ONTAP,
SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator,
SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault,
StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage,
Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or
registered trademarks of NetApp, Inc. in the United States, other countries, or both.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or other
countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem,
RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are
trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.

Table of Contents
Table of Contents v
Chapter 1 Preparing to Upgrade Your Storage Management Software . . . . . . . . . . . . . . . . 1
Upgrading the Storage Management Software and the Controller Firmware . . . 1
Storage Management Software Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Checking the Current Version of the Storage Management Software . . . . . 5
Supported Controller Trays and Controller-Drive Trays . . . . . . . . . . . . . . . . . . . 6
Maximum Number of Drives and Volumes for Controller-Drive Trays and
Controller Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Supported Storage Array Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2 Upgrading Trays in the Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Upgrading Options for Supported Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upgrading Cache Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upgrading Cache Memory for the CE7900 Controller Tray . . . . . . . . . . . 11
Upgrading Cache Memory for the E2600 Controller-Drive Trays . . . . . . . 21
Upgrading Cache Memory for the E5400 Controller-Drive Trays . . . . . . . 39
Upgrading Host Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Upgrading a Host Interface Card in the CE7900 Controller Tray . . . . . . . 59
Upgrading a Host Interface Card in the E2600 Controller-Drive Trays . . . 67
Upgrading a Host Interface Card in the E5400 Controller-Drive Trays . . . 83
Chapter 3 Using the Firmware Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 4 Upgrade Instructions for the HP-UX OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
System Requirements for HPUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Installing the Storage Management Software on the HP-UX OS . . . . . . . . . . 106
Checking the Installation on the HP-UX OS . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Uninstalling the Storage Management Software on the HP-UX OS . . . . . . . . 109

vi Table of Contents
Chapter 5 Upgrade Instructions for the Solaris OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Supported Components for Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Installing the Storage Management Software on the Solaris OS . . . . . . . . . . . 113
Checking the Installation on the Solaris OS. . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Uninstalling the Storage Management Software on the Solaris OS. . . . . . . . . 116
Chapter 6 Upgrade Instructions for the Linux OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
System Requirements for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
System Requirements for Linux with InfiniBand . . . . . . . . . . . . . . . . . . . . . . 120
Installing the Storage Management Software on the Linux OS . . . . . . . . . . . . 121
Checking the Installation on the Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Uninstalling Storage Management Software on the Linux OS . . . . . . . . . . . . 125
Chapter 7 Upgrade Instructions for the Windows OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
System Requirements for Windows Server 2003 and XP . . . . . . . . . . . . . . . . 127
System Requirements for Windows Server 2008, Hyper-V and Vista . . . . . . 130
Installing the Storage Management Software on the Windows OS . . . . . . . . . 132
Checking the Installation on the Windows OS. . . . . . . . . . . . . . . . . . . . . . . . . 136
Uninstalling Storage Management Software on the Windows OS . . . . . . . . . 136
Chapter 8 Upgrade Instructions for Asymmetric Logical Unit Access (ALUA) with the
VMware OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
System Requirements for VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Installing ALUA Support for VMware Versions ESX4.1U2, ESXi5.0, and Prior
Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Installing ALUA Support for VMware Versions ESX4.1U3, ESXi5.0U1, and
Subsequent Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Appendix A Boot Device Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Boot Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Installing the Boot Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Storage Array and Host Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Table of Contents vii
Preparing the Storage Array as a Boot Device . . . . . . . . . . . . . . . . . . . . . 146
Preparing the Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Completing the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

viii Table of Contents

Chapter 1: Preparing to Upgrade Your Storage Management Software 1
1
Preparing to Upgrade Your Storage Management Software
The following table shows the supported upgrade paths for controller trays and
controller-drive trays for storage management software version 10.83 and controller
firmware version 7.83.
Table 1 Supported Trays and Software Upgrade Paths
NOTE If you are upgrading from controller firmware version 7.75.26, you must first
upgrade to 7.75.28, and then upgrade to 7.83. All other supported upgrades are
performed directly without an intermediate step.
Upgrading the
Storage
Management
Software and
the Controller
Firmware
NOTE To make sure that your failover driver is compatible with the new hardware,
firmware, and software, refer to the SANtricity™ES Storage Manager Failover Drivers
User Guide for Version 10.83. For the RHEL 6.1 and SLES operating systems, if you
are setting up a configuration to support Asynchronous Logical Unit Access (ALUA),
additional steps are required to install software patches.
These steps are required for a successful upgrade to storage management software
version 10.83 and controller firmware version 7.83. Perform the steps in order. You
might find it helpful to print the Upgrade Checklist and refer to it as you work through
the upgrade steps.
1. Make sure that the controller trays and the controller-drive trays in your storage
array are compatible with the software level and the firmware level to which you
are upgrading.
2. Check that the host bus adapters (HBAs), switches, driver versions, firmware
levels, and specific hardware restrictions are supported.
Tray Name
Installed Storage
Management Software
Version
Installed Controller
Firmware Version
Controller-drive trays
E2612, E2624, E2660 10.70 or later 7.70 or later
CE4900 10.60 or later 7.60 or later
E5412, E5424, E5460 10.80 or later 7.80 or later
Controller tray
CE7900, CE7922 10.30 or later 7.30 or later

2
NOTE Install all storage area network (SAN) hardware before you work with the
storage management software.
3. Start the existing storage management software with the procedure for your
operating system.
4. Check that the storage array has Optimal status.
5. Save and print the storage array profile from the current Array Management
Window of the storage management software for each storage array.
a. In the Array Management Window, select Monitor >> Report >> Storage
Array Profile.
b. Click Save As
c. Select the All sections radio button.
d. Type a file name in the File name text box.
e. Click Save.
The storage array profile is used for this information:
—Configuration information that you might provide to your Technical Support
representative
—The current NVSRAM and controller firmware versions
—The current environmental services module (ESM) firmware version
6. Locate the cache and processor memory size (MB) in the storage array profile,
and record the listed size for later verification.
7. Locate the host interface in the storage array profile, and record the number listed
in the Preferred ID area for each Fibre Channel interface for later verification.
8. Make sure that your storage array has the minimum system requirements for your
operating system.
See the system requirements topics for each operating system in this document.
9. Make sure that your failover driver is compatible with the new hardware,
firmware, and software. Refer to the topics under SANtricity ES Storage Manager
Failover Drivers User Guide for Version 10.83.
NOTE Read the "dependence" section in the SANtricity ES Storage Manager
readme.txt file.
10. Make sure that the current version of storage management software can be
upgraded to SANtricity ES Storage Manager Version 10.83.
11. Install storage management software version 10.83 for your operating system
(OS). Use the procedure for your OS to install the storage management software.
12. Make sure that the installation was successful. Use the procedure for your
operating system to start the storage management software.

Chapter 1: Preparing to Upgrade Your Storage Management Software 3
13. Check that the storage array has an Optimal status. If one or more managed
devices has a Needs Attention status, contact your Technical Support
representative.
14. If you determined from the storage array profile that the NVSRAM firmware, the
controller firmware, or the ESM firmware is not the current version, download
the compatible firmware.
NOTE With the I/O Shipping feature, a storage array can use asymmetric logical unit
access (ALUA). ALUA enables a controller tray or a controller-drive tray to service
I/O requests through either controller in a duplex configuration. To use the I/O
Shipping feature with VMware, you must take additional steps to update the VMware
configuration. See Upgrade Instructions for Asymmetric Logical Unit Access (ALUA)
with the VMware OS on page 139 for instructions.
Storage
Management
Software
Packages
All storage management software packages are generally installed in the same
directory on the same system, whether the system is the host or a separate storage
management station.
Table 2 Storage Management Software Packages
Software Package Description and Usage
SMclient This package contains the graphical user interface
for managing the storage array. This package also
contains an optional monitor service that sends alerts
when a critical problem exists with the storage array.
SMagent The storage management software that is installed
only on a host machine to enable in-band
management.1
SMruntime The operating system (OS) -specific storage
management software that installs the appropriate
Java runtime environment (JRE), which allows Java
files to be displayed.

4
NOTE The Microsoft Virtual Disk Service (VDS) and Volume Shadow Copy Service
(VSS) providers are a part of the SANtricity ES Storage Manager package for the
Windows Server 2003 OS and the Windows Server 2008 OS.
Redundant Dual Active
Controller
(RDAC)/Multi-Path Proxy
(MPP)
A multi-path failover driver, proprietary to NetApp,
that is installed on Linux hosts. This software
package manages the I/O paths into the controllers in
the storage array. If a problem exists on the path or a
failure occurs on one of the controllers, the driver
automatically reroutes the request from the hosts to
the other controller in the storage array. For
information about other supported failover drivers
for your operating system, refer to the topics under
SANtricity ES Storage Manager Failover Drivers
User Guide for Version 10.83.
SMutil This package contains utilities that let the operating
system recognize the volumes that you create in the
storage array and to view the OS-specific device
names for each volume.
SMprovider The storage management software interface to the
Volume Shadow Copy Service (VSS) and Virtual
Disk Service (VDS) technologies (these technologies
are included with Microsoft’s .NET framework).
SMinstaller A package that installs the InstallAnywhere utility.
1In-band management is a method for managing a storage array in which the
controllers are managed from a storage management station attached to a host that
is running host-agent software. The host-agent software receives communication
from the storage management client software and passes it to the storage array
controllers along the input/output (I/O) path. The controllers also use the I/O
connections to send event information back to the storage management station
through the host.
Software Package Description and Usage

Chapter 1: Preparing to Upgrade Your Storage Management Software 5
Installation Options Install only the packages that are required for the type of installation you are
performing.
Table 3 Installation Options and Related Software Packages
Checking the
Current Version of
the Storage
Management
Software
The operating system-specific commands are listed below. To check the level of the
current storage management software, type the command that corresponds to your
operating system, and press Enter. The <package name> placeholder refers to the
name of the software package that is installed.
In the Linux operating system, type this command, and press Enter:
rpm -qi <package name>
In the Windows operating system, perform these tasks.
a. Select Start >> Run.
b. Type reged32, and press Enter.
The Register Editor window appears.
c. Select HKEY_LOCAL_MACHINE >> SOFTWARE >> STORAGE.
The host software versions are listed under the storage directory.
Installation Option SMruntime SMclient SMutil SMagent
RDAC
Failover
Driver1
Typical installation X X X X
Storage management
station2
XX
Host station X X X
A host station acting
as a storage
management station
(out-of-band
management)3
XXX X
Host with in-band
management
X XXX
1The RDAC/MPP failover driver is proprietary to NetApp and is available for
download to the Linux OS.
2The storage management station is a computer that runs storage management
software that adds, monitors, and manages the storage arrays on a network.
3Out-of-band management is a method to manage a storage array over the network
through an Ethernet connection, from a storage management station that need not
have an I/O path connection to the controllers.

6
Supported
Controller Trays
and
Controller-Drive
Trays
This section describes the supported controller trays and controller-drive trays.
Table 4 Controller Trays and Controller-Drive Trays
Maximum
Number of
Drives and
Volumes for
Controller-Drive
Trays and
Controller Trays
Table 1shows the controller-drive trays, the controller trays, and the maximum
number of drives and the total number of volumes that are supported by each
controller tray or controller-drive tray. The total numbers include drives or volumes
that are contained in the controller-drive tray and in additional attached drive trays.
Table 5 Supported Trays and the Maximum Number of Drives and Volumes
The following table lists controller-drive trays and controller trays can co-exist in a
storage network with hardware running storage management software version 10.83
and controller firmware version 7.83. They cannot, however, be upgraded to storage
management software version 10.83 and controller firmware version 7.83.
Term Description
Controller tray A unit that contains one or two controllers, a battery
(optional), and redundant cooling fans and power
supplies. Controller trays do not contain environmental
services modules (ESMs).
Controller-drive tray A unit that contains up to 16 drives, redundant cooling
fans and power supplies, and (depending on the model)
one or two controllers. Controller-drive trays do not
contain ESMs.
Tray Name Controller
Type
Maximum
Drives per
Storage Array
Maximum
Volumes per
Storage Array1
Controller-drive trays
E2600 192 512
CE4900 1280 or 2560 112 1024
E5400 4096 or 8192 384 2048
Controller trays
CE7900,
CE7922
480
1Snapshot (Legacy) repository volumes and Synchronous Mirroring
repository volumes are included in the number of volumes supported.
2Additional drive trays are not supported.

Chapter 1: Preparing to Upgrade Your Storage Management Software 7
Table 6 Co-existing Trays and the Maximum Number of Drives and Volumes
Tray Name Controller
Type
Maximum
Drives per
Storage Array
Maximum
Volumes per
Storage Array1
Controller-drive trays
SHV2520 2880 (dual) 1421024
SHV2600 2882 112 1024
SAT2700 2820-SATA 142512
SAT2800 2822-SATA 112 512
CDE3994 3992 or 3994 112 1024
Controller trays
FC1250 4884 224 2048
FC1275 5884 224 2048
CE6998 6091 224 2048
1Snapshot (Legacy) repository volumes and Synchronous Mirroring
repository volumes are included in the number of volumes supported.
2Additional drive trays are not supported.

8
Supported
Storage Array
Configurations
The drive tray is a unit that contains up to 16 drives, redundant cooling fans and
power supplies, and one or two ESMs. Drive trays do not contain controllers.
Table 7 Supported Drive Trays
FC4600 DE6600
Mix of
CE4900
and
DE6600
DE1600/
DE5600 DE6600
Mix of
DE1600/
DE5600
and
DE6600
CE7900
CE7922
Maximum
of 7 drive
trays per
loop pair, 28
drive trays
total (total
drives=480
maximum)
Maximum
of 2 drive
trays per
loop pair, 8
drive trays
total (total
drives=480
maximum)
6xDE6600+
1xFC4600
or
1xDE6600+
21xFC4600
(total
drives=448
maximum)
Not
supported
Not
supported
Not
supported
CE4900 Maximum
of 6 drive
trays
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
E2600 Not
supported
Not
supported
Not
supported
total
drives=192
maximum
Maximum
of 2 drive
trays (total
drives=180
maximum)
Not
supported
E5400 Not
supported
Not
supported
Not
supported
Any mixture with total drives=384
maximum and total drive trays=16
maximum

Chapter 2: Upgrading Trays in the Storage Array 9
2
Upgrading Trays in the Storage Array
Keep these guidelines in mind before you upgrade trays in your storage array:
Always back up your data to an external source before starting an upgrade
procedure.
Keep in mind that requirements for SFPs and cabling might change when you
upgrade a host adapter. Refer to the Hardware Cabling Guide for a complete
description of various cabling options.
You can choose from these upgrade options:
Upgrade cache memory
Upgrade Host Adapters
ATTENTION Possible loss of data access – Before you start any upgrade procedure,
back up your data to an external source.

10
Upgrading
Options for
Supported
Trays
Table 1 Upgrading Options for Supported Trays
Upgrading
Cache Memory
There are several option for upgrading cache memory in a controller-drive tray or a
controller tray.
Each controller canister in the CE7900 controller tray has two sockets for cache
memory DIMMs and a cache backup memory device. Use this procedure to add a
cache memory DIMM, if the space is available, or upgrade an existing cache
memory DIMM and, if necessary, add a cache backup memory device.
Tray Name Tray Upgrading Option
Upgrade Host Adapters
CE7900 Upgrade 4-Gb/s FC to 8-Gb/s FC.
Upgrade 1-Gb/s iSCSI to 10-Gb/s iSCSI.
Install a second HIC (4-Gb/s FC, 8-Gb/s FC, 1-Gb/s
iSCSI, 10-Gb/s iSCSI).
E5400 Install a HIC in addition to the base host ports (8-Gb/s FC or
40-Gb/s InfiniBand).
E2600 Install a HIC in addition to the base host ports (8-Gb/s FC,
1-Gb/s iSCSI, 10-Gb/s iSCSI, 6-Gb/s SAS).
Upgrade Cache Memory
CE7900 Populate empty DIMM slots to increase capacity to 8-GB
and add an additional cache backup memory device.
Replace 1-GB DIMMS with 2-GB DIMMs to increase
capacity to 16 GB and add an additional cache backup
memory device.
Replace 2-GB DIMMS with 4-GB DIMMs to increase
capacity to 16 GB and add an additional cache backup
memory device.
E5400 Replace 2-GB DIMMS with 4-GB DIMMs to increase
capacity to 12GB and add an additional cache backup
memory device.
Replace 4-GB DIMMS with 8-GB DIMMs to increase
capacity to 24 GB and add an additional cache backup
memory device.
E2600 Replace 1-GB DIMMS with 2-GB DIMMs to increase
capacity to 2 GB.
Replace 2-GB DIMMS with 4-GB DIMMs to increase
capacity to 4 GB.

Chapter 2: Upgrading Trays in the Storage Array 11
Each controller canister in the E5400 controller-drive tray has two sockets for
cache memory DIMMs and a cache backup memory device. Use this procedure
to upgrade existing cache memory DIMMs and, if necessary, add a cache backup
memory device.
Each controller canister in the E2600 controller-drive tray has one socket for
cache memory DIMMs and a cache backup memory device. Use this procedure
to upgrade existing cache memory DIMM and, if necessary, add a cache backup
memory device.
Upgrading Cache
Memory for the
CE7900 Controller
Tray
Before you start this procedure, gather antistatic protection, cache memory DIMMs,
and, if necessary, cache backup memory devices. Perform each of the following tasks
in order.
1. Remove the controller canisters from the controller-drive tray or a controller tray.
2. Upgrade the cache memory DIMM.
3. Upgrade the Cache Backup Memory Device.
4. Reinstall the controller canisters from the controller-drive tray or the controller
tray.
ATTENTION Data loss or corruption might result if the steps in this upgrade
procedure are not followed correctly – You must upgrade the cache memory DIMMs
and the cache backup memory devices in both controller canisters in the controller tray
or the controller-drive tray. Otherwise, you receive event messages indicating that the
controllers have mismatched and incompatible configurations. This event might cause
the controllers to lock down.
NOTE Do not perform this upgrade procedure with the power turned on. This
procedure requires that you first set controller A offline to make sure that all of the
data, which is currently in cache on both controller canisters, is successfully written to
disk before the upgrade. Second, you will turn off the power to both controller canisters
as described in the steps for "Removing a Controller Canister" on page 11.
Removing a Controller
Canister
NOTE Before you remove the controller canisters, make sure that you set controller
A to Offline, as described in the following steps, to ensure that all the data currently in
the cache for controller A is successfully written to disk prior to the upgrade. This step
also ensures that the data currently in the cache for controller B is successfully written
to disk before you turn off the power to both controller canisters.
ATTENTION Possible hardware damage – To prevent electrostatic discharge
damage to the tray, use proper antistatic protection when handling tray components.

12
1. Gather support data about your updated storage array by using one of these
methods:
2. Use the Locate function in the storage management software to identify the
controller canisters to upgrade.
3. Put on antistatic protection.
4. Label each host interface cable, drive interface cable, and Ethernet cable that is
attached to each controller canister so that you can reconnect the cables correctly
after the controller canisters are reinstalled.
ATTENTION Potential degraded performance – To prevent degraded
performance, do not twist, fold, pinch, or step on the fiber-optic cables. Do not bend
the fiber-optic cables tighter than a 5-cm (2-in.) radius.
5. Stop all host I/O operations.
SANtricity ES From the Array Management Window toolbar, select
Monitor >> Health >> Collect Support Data. Then
name and specify a location on your system where
you want to store the support bundle.
Command line interface Enter the following command on the command line:
save storageArray supportData
This command gathers comprehensive support data
about the storage array. For more information about
this command, refer to Command Line Interface and
Script Commands Programming Guide. Running this
command can temporarily impact performance on
your storage array.