Silicon Graphics InfiniteStorage 4000 Series Assembly Instructions

SGI InfiniteStorage 4000 Series and 5000 Series
Configuring and Maintaining a Storage Array
(ISSM 10.86)






007-5882-002 April 2013

The information in this document supports the SGI InfiniteStorage 4000 series and 5000 series storage
systems (ISSM 10.86). Refer to the table below to match your specific SGI InfiniteStorage product
with the model numbers used in this document.

SGI Model #
NetApp Model
TP9600H 6091
TP9700F 6091
IS4500F 6091
TP9600F 3994 and 3992
IS4000H 3994
IS350 3992
IS220 1932
1333
DE1300
IS4100 4900
IS-DMODULE16-Z FC4600
IS-DMODULE60 DE6900
IS4600 7091
IS-DMODULE12 & IS2212 (JBOD) DE1600
IS-DMODULE24 & IS2224 (JBOD) DE5600
IS-DMODULE60-SAS DE6600
IS5012 E2600
IS5024 E2600
IS5060 E2600
IS5512 E5400
IS5524 E5400
IS5560 E5400
IS5600 E5500

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 About the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Structure of a CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
CLI Command Wrapper Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Command Line Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Alert Severities Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
AutoSupport Bundle Collection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Disable AutoSupport at the EMW Level SMcli Version . . . . . . . . . . . . . . 12
Enable AutoSupport at the EMW Level SMcli Version . . . . . . . . . . . . . . . 12
Set Storage Array AutoSupport Bundle Disable. . . . . . . . . . . . . . . . . . . . . 13
Set Storage Array AutoSupport Bundle Enable . . . . . . . . . . . . . . . . . . . . . 13
Test AutoSupport Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Formatting CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Formatting Rules for Script Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Formatting CLI Commands in Windows PowerShell . . . . . . . . . . . . . . . . . . . . 17
Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Exit Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2 About the Script Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Structure of a Script Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Synopsis of the Script Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Recurring Syntax Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding Comments to a Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 3 Configuration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hot Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

vi Table of Contents
Drive Security with Full Disk Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Disk Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RAID Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Host Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Host Bus Adapter Host Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Logical Unit Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 4 Configuring a Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Determining What Is on Your Storage Array. . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Clearing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configuring a Storage Array with Volume Groups . . . . . . . . . . . . . . . . . . . . . . 56
Using the Auto Configure Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Using the Create Volume Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Tray Loss Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring a Storage Array with Disk Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Using the Create Disk Pool Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Using the Create Volume Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Modifying Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Setting the Controller Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Setting the Storage Array Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Setting the Storage Array Host Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Setting the Storage Array Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Setting the Modification Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Assigning Global Hot Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Saving a Configuration to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Table of Contents vii
Chapter 5 Using the Snapshot (Legacy) Premium Feature. . . . . . . . . . . . . . . . . . . . . . . . . . 81
How Snapshot (Legacy) Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
About Scheduling Snapshots (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Creating a Snapshot (Legacy) Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating a Snapshot (Legacy) Volume with User-Assigned Drives. . . . . . 85
Creating a Snapshot (Legacy) Volume with Software-Assigned 
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Creating a Snapshot (Legacy) Volume by Specifying a Number of 
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
User-Defined Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Snapshot (Legacy) Volume Names and Snapshot (Legacy) Repository
Volume Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Creating a Snapshot (Legacy) Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Changing Snapshot (Legacy) Volume Settings . . . . . . . . . . . . . . . . . . . . . . . . . 93
Stopping, Restarting, and Deleting a Snapshot (Legacy) Volume. . . . . . . . . . . 94
Starting, Stopping, and Resuming a Snapshot (Legacy) Rollback. . . . . . . . . . . 95
Chapter 6 Using the Snapshot Images Premium Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Differences Between Snapshots (Legacy) and Snapshot Image Operations . . 100
Snapshot Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Repository Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Snapshot Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Relationship Between Snapshot Images, Snapshot Groups, and Snapshot
Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Consistency Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Creating a Snapshot Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deleting a Snapshot Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Creating a Snapshot Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Canceling a Pending Snapshot Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating a Snapshot Image Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Deleting a Snapshot Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Creating a Snapshot Consistency Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

viii Table of Contents
Deleting a Snapshot Consistency Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Creating a Snapshot Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Resuming a Consistency Group Snapshot Volume . . . . . . . . . . . . . . . . . . . . . 114
Deleting a Snapshot Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Changing the Size of a Repository Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Starting, Stopping, and Resuming a Snapshot Image Rollback . . . . . . . . . . . . 117
Chapter 7 Using the Asynchronous Mirroring Premium Feature . . . . . . . . . . . . . . . . . . . 121
How Asynchronous Mirroring Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configurating for Asynchronous Mirroring . . . . . . . . . . . . . . . . . . . . . . . 124
Asynchronous Mirror Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Mirror Repository Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating an Asynchronous Mirrored Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Enabling the Asynchronous Mirroring Premium Feature . . . . . . . . . . . . . 128
Activating the Asynchronous Mirroring Premium Feature. . . . . . . . . . . . 128
Creating the Asynchronous Mirroring Group . . . . . . . . . . . . . . . . . . . . . . 129
Creating the Asynchronous Mirroring Pair. . . . . . . . . . . . . . . . . . . . . . . . 131
Changing Asynchronous Mirroring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Suspending and Resuming the Asynchronous Mirror Group. . . . . . . . . . . . . . 135
Manually Resynchronizing Volumes in an Asynchronous Mirror Group . . . . 136
Changing Asynchronous Mirroring Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Canceling a Pending Asynchronous Mirror Group Role Change . . . . . . . . . . 138
Resolving Role Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Removing Volumes from the Asynchronous Mirror Group . . . . . . . . . . . . . . 139
Deleting an Asynchronous Mirror Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Chapter 8 Using the Synchronous Mirroring Premium Feature . . . . . . . . . . . . . . . . . . . . 141
How Synchronous Mirroring Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Mirror Repository Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Mirror Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Table of Contents ix
Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Link Interruptions or Secondary Volume Errors. . . . . . . . . . . . . . . . . . . . 144
Resynchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Creating a Synchronous Mirroring Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Enabling the Synchronous Mirroring Premium Feature . . . . . . . . . . . . . . 147
Activating the Synchronous Mirroring Premium Feature. . . . . . . . . . . . . 147
Determining Candidates for a Remote Mirrored Pair . . . . . . . . . . . . . . . . 149
Creating a Remote Mirrored Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Changing Synchronous Mirroring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Suspending and Resuming a Synchronous Mirroring Relationship. . . . . . . . . 152
Removing a Mirror Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting a Primary Volume or a Secondary Volume. . . . . . . . . . . . . . . . . . . . 153
Disabling the Synchronous Mirroring Premium Feature . . . . . . . . . . . . . . . . . 153
Deactivating the Synchronous Mirroring Premium Feature . . . . . . . . . . . . . . 154
Interaction with Other Premium Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Storage Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Snapshot (Legacy) Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Volume Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Dynamic Volume Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Chapter 9 Using the Volume Copy Premium Feature . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 157
How Volume Copy Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Source Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Target Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Volume Copy and Persistent Reservations . . . . . . . . . . . . . . . . . . . . . . . . 159
Storage Array Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Volume Copy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

xTable of Contents
Creating a Volume Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Enabling the Volume Copy Premium Feature . . . . . . . . . . . . . . . . . . . . . 161
Determining Volume Copy Candidates . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Creating a Volume Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Viewing Volume Copy Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Changing Volume Copy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Recopying a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Stopping a Volume Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Removing Copy Pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Interaction with Other Premium Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Storage Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Snapshot (Legacy) Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Synchronous Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Chapter 10 Using the SSD Cache Premium Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Creating the SSD Cache, Adding Volumes, and Removing Volumes. . . . . . . 173
SSD Cache Performance Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
SSD Cache Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Chapter 11 Maintaining a Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Routine Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Running a Media Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Running a Redundancy Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Resetting a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Enabling a Controller Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Resetting the Battery Age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Removing Persistent Reservations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Synchronizing the Controller Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Locating Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Relocating a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Table of Contents xi
Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Monitoring the Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Changing the RAID Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Changing the Segment Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Changing the Cache Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Defragmenting a Volume Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Troubleshooting and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Detailed Error Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Collecting All Support Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Collecting Drive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Diagnosing a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Running Read Link Status Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Collecting Switch-on-a-Chip Error Statistics . . . . . . . . . . . . . . . . . . . . . . 197
Recovery Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Setting the Controller Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . 198
Changing the Controller Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Initializing a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Reconstructing a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Initializing a Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Redistributing Volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Replacing Canisters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Appendix A Examples of Information Returned by the Show Commands. . . . . . . . . . . . . . 205
Show Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Show Controller NVSRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Show Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Show Drive Channel Stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Show Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

xii Table of Contents
Appendix B Example Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configuration Script Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configuration Script Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Appendix C Asynchronous Write Mode Mirror Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Description of the Asynchronous Write Mode Mirror Utility . . . . . . . . . . . . . 251
Operation of the Asynchronous Synchronous Mirroring Utility . . . . . . . . . . . 252
Running the Asynchronous Synchronous Mirroring Utility . . . . . . . . . . . . . . 252
Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Appendix D Simplex-to-Duplex Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
General Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Tools and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Step 1 – Installing the Duplex NVSRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Downloading the NVSRAM by Using the Command Line Interface . . . 258
Downloading the NVSRAM by Using the GUI . . . . . . . . . . . . . . . . . . . . 258
Copying NVSRAM from the Installation CD. . . . . . . . . . . . . . . . . . . . . . 259
Step 2 – Setting the Configuration to Duplex . . . . . . . . . . . . . . . . . . . . . . . . . 259
Step 3 – Installing the Second Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Step 4 – Connecting the Host Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Step 5 – Connecting the Controller to a Drive Tray. . . . . . . . . . . . . . . . . . . . . 261
Step 6 – Running Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Chapter 1: About the Command Line Interface 1
1
About the Command Line Interface
The command line interface (CLI) is a software application that provides a way for
installers, developers, and engineers to configure and monitor storage arrays. Using
the CLI, you can run commands from an operating system prompt, such as the DOS
C: prompt, a Linux operating system path, or a Solaris operating system path.
Each command performs a specific action for managing a storage array or returning
information about the status of a storage array. You can enter individual commands,
or you can run script files when you need to perform operations more than once. For
example, you can run script files when you want to install the same configuration on
several storage arrays. The CLI enables you to load a script file from a disk and run
the script file. The CLI provides a way to run storage management commands on
more than one network storage array. You can use the CLI both in installation sites
and in development environments.
The CLI gives you direct access to a script engine that is a utility in the SANtricity ES
Storage Manager software (also referred to as the storage management software). The
script engine runs commands that configure and manage the storage arrays. The script
engine reads the commands, or runs a script file, from the command line and performs
the operations instructed by the commands.
NOTE You can also access the script engine by using the Enterprise Management
Window in the storage management software. If you access the script engine by using
the Enterprise Management Window, you can edit or run script commands on only one
storage array in the script window. You can open a script window for each storage array
in your configuration and run commands in each window. By using the CLI, you can
run commands on more than one storage array from a single command line.
You can use the command line interface to perform these actions:
Directly access the script engine and run script commands.
Create script command batch files to be run on multiple storage arrays when you
need to install the same configuration on different storage arrays.
Run script commands on an in-band managed storage array, an out-of-band
managed storage array, or a combination of both.
Show configuration information about the network storage arrays.
Add storage arrays to and remove storage arrays from the management domain.
Perform automatic discovery of all of the storage arrays that are attached to the
local subnet.
Add or delete Simple Network Management Protocol (SNMP) trap destinations
and email alert notifications.
Specify the mail server and sender email address or SNMP server for alert
notifications.

2Structure of a CLI Command
Show the alert notification settings for storage arrays that are currently
configured in the Enterprise Management Window.
Direct the output to a standard command line display or to a named file.
Structure of a
CLI Command The CLI commands are in the form of a command wrapper and elements embedded
into the wrapper. A CLI command consists of these elements:
A command wrapper identified by the term SMcli
The storage array identifier
Terminals that define the operation to be performed
Script commands
The CLI command wrapper is a shell that identifies storage array controllers, embeds
operational terminals, embeds script commands, and passes these values to the script
engine.
All CLI commands have the following structure:
SMcli storageArray terminal script-commands;
SMcli invokes the command line interface.
storageArray is the name or the IP address of the storage array.
terminal a CLI value that defines the environment and the purpose for the
command.
script-commands are one or more script commands or the name of a script
file that contains script commands. (The script commands configure and manage
the storage array.)
If you enter an incomplete or inaccurate SMcli string that does not have the correct
syntax, parameter names, options, or terminals, the script engine returns usage
information.
For an overview of the script commands, see "About the Script Commands." For
definitions, syntax, and parameters for the script commands, refer to the Command
Line Interface and Script Commands.
Interactive Mode If you enter SMcli and a storage array name but do not specify CLI parameters,
script commands, or a script file, the command line interface runs in interactive mode.
Interactive mode lets you run individual commands without prefixing the commands
with SMcli.
In interactive mode, you can enter a single command, view the results, and enter the
next command without typing the complete SMcli string. Interactive mode is useful
for determining configuration errors and quickly testing configuration changes.

Chapter 1: About the Command Line Interface 3
To end an interactive mode session, type the operating system-specific command for
terminating a program, such as Control-C on the UNIX operating system or the
Windows operating system. Typing the termination command (Control-C) while in
interactive mode turns off interactive mode and returns operation of the command
prompt to an input mode that requires you to type the complete SMcli string.
CLI Command
Wrapper Syntax General syntax forms of the CLI command wrappers are listed in this section. The
general syntax forms show the terminals and the parameters that are used in each
command wrapper. The conventions used in the CLI command wrapper syntax are
listed in the following table.
SMcli host-name-or-IP-address
[host-name-or-IP-address] 
[-c "command; {command2};"] 
[-n storage-system-name | -w wwID] 
[-o outputfile] [-p password] [-R (admin | monitor)]
[-e] [-S] [-quick]
SMcli host-name-or-IP-address [hostname-or-IP-address] 
[-f scriptfile] 
[-n storage-system-name | -w wwID] 
[-o outputfile] [-p password] [-R (admin | monitor)]
[-e] [-S] [-quick]
SMcli (-n storage-system-name | -w wwID) 
[-c "command; {command2};"] 
[-o outputfile] [-p password] [-R (admin | monitor)]
[-e] [-S] [-quick]
Convention Definition
a | b Alternative ("a" or "b")
italicized-words A terminal that needs user input to fulfill a parameter
(a response to a variable)
[ ... ] (square brackets) Zero or one occurrence (square brackets are also
used as a delimiter for some command parameters)
{ ... } (curly braces) Zero or more occurrences
(a | b | c) Choose only one of the alternatives
bold A terminal that needs a command parameter entered
to start an action

4Structure of a CLI Command
SMcli (-n storage-system-name -w wwID) 
[-f scriptfile] 
[-o outputfile] [-R (admin | monitor)] [-p password]
[-e] [-S] [-quick]
SMcli -a email: email-address
[host-name-or-IP-address1 
[host-name-or-IP-address2]] 
[-n storage-system-name | -w wwID | -h host-name] 
[-I information-to-include] [-q frequency] [-S]
SMcli -x email: email-address
[host-name-or-IP-address1 
[host-name-or-IP-address2]] 
[-n storage-system-name | -w wwID | -h host-name] [-S]
SMcli (-a | -x) trap: community,
host-name-or-IP-address 
[host-name-or-IP-address1 [host-name-or-IP-address2]] 
[-n storage-system-name | -w wwID | -h host-name] [-S]
SMcli -d [-w] [-i] [-s] [-v] [-S]
SMcli -m host-name-or-IP-address -F email-address 
[-g contactInfoFile] [-S]
SMcli -A [host-name-or-IP-address
[host-name-or-IP-address]] 
[-S]
SMcli -X (-n storage-system-name | -w wwID | -h
host-name)
SMcli -?

Chapter 1: About the Command Line Interface 5
Command Line
Terminals
Terminal Definition
host-name-or-IP-
address Specifies either the host name or the Internet Protocol (IP) address (xxx.xxx.xxx.xxx) of an in-band managed storage array or an
out-of-band managed storage array.
If you are managing a storage array by using a host through in-band
storage management, you must use the -n terminal or the -w terminal if
more than one storage array is connected to the host.
If you are managing a storage array by using out-of-band storage
management through the Ethernet connection on each controller, you
must specify the host-name-or-IP-address of the controllers.
If you have previously configured a storage array in the Enterprise
Management Window, you can specify the storage array by its
user-supplied name by using the -n terminal.
If you have previously configured a storage array in the Enterprise
Management Window, you can specify the storage array by its World
Wide Identifier (WWID) by using the -w terminal.
-A Adds a storage array to the configuration file. If you do not add the 
-A terminal with a host-name-or-IP-address, auto-discovery scans
the local subnet for storage arrays.
-a Adds a Simple Network Management Protocol (SNMP) trap destination or
an email address alert destination.
When you add an SNMP trap destination, the SNMP community is
automatically defined as the community name for the trap, and the
host is the IP address or Domain Name Server (DNS) host name of the
system to which the trap should be sent.
When you add an email address for an alert destination, the
email-address is the email address to which you want the alert
message to be sent.
-c Indicates that you are entering one or more script commands to run on the
specified storage array. End each command with a semicolon (;). You
cannot place more than one -c terminal on the same command line. You can
include more than one script command after the -c terminal.
-d Shows the contents of the script configuration file. The file content has this
format:
storage-system-name host-name1 host-name2
-e Runs the commands without performing a syntax check first.
-F (uppercase) Specifies the email address from which all alerts will be sent.

6Structure of a CLI Command
-f (lowercase) Specifies a file name that contains script commands that you want to run on
the specified storage array. The -f terminal is similar to the -c terminal in
that both terminals are intended for running script commands. The -c
terminal runs individual script commands. The -f terminal runs a file of
script commands.
By default, any errors that are encountered when running the script
commands in a file are ignored, and the file continues to run. To override this
behavior, use the set session errorAction=stop command in the
script file.
-g Specifies an ASCII file that contains email sender contact information that
will be included in all email alert notifications. The CLI assumes that the
ASCII file is text only, without delimiters or any expected format. Do not use
the -g terminal if a userdata.txt file exists.
-h Specifies the host name that is running the SNMP agent to which the storage
array is connected. Use the -h terminal with these terminals:
-a
-x
-I (uppercase) Specifies the type of information to be included in the email alert
notifications. You can select these values:
eventOnly – Only the event information is included in the email.
profile – The event and array profile information is included in the
email.
You can specify the frequency for the email deliveries using the -q terminal.
-i (lowercase) Shows the IP address of the known storage arrays. Use the -i terminal with
the -d terminal. The file contents has this format:
storage-system-name IP-address1 IPaddress2
-m Specifies the host name or the IP address of the email server from which
email alert notifications are sent.
-n Specifies the name of the storage array on which you want to run the script
commands. This name is optional when you use a
host-name-or-IP-address. If you are using the in-band method for
managing the storage array, you must use the -n terminal if more than one
storage array is connected to the host at the specified address. The storage
array name is required when the host-name-or-IP-address is not
used. The name of the storage array that is configured for use in the
Enterprise Management Window (that is, the name is listed in the
configuration file) must not be a duplicate name of any other configured
storage array.
Terminal Definition

Chapter 1: About the Command Line Interface 7
-o Specifies a file name for all output text that is a result of running the script
commands. Use the -o terminal with these terminals:
-c
-f
If you do not specify an output file, the output text goes to standard output
(stdout). All output from commands that are not script commands is sent to
stdout, regardless of whether this terminal is set.
-p Defines the password for the storage array on which you want to run
commands. A password is not necessary if a password has not been set on
the storage array.
If you set a monitor password for the storage array, the use of the -p
parameter is mandatory. Users cannot run any of the non -destructive
commands such as the show commands.
-q Specifies the frequency that you want to receive event notifications and the
type of information returned in the event notifications. An email alert
notification containing at least the basic event information is always
generated for every critical event.
These values are valid for the -q terminal:
everyEvent – Information is returned with every email alert
notification.
2 – Information is returned no more than once every two hours.
4 – Information is returned no more than once every four hours.
8 – Information is returned no more than once every eight hours.
12 – Information is returned no more than once every 12 hours.
24 – Information is returned no more than once every 24 hours.
Using the -I terminal you can specify the type of information in the email
alert notifications.
If you set the -I terminal to eventOnly, the only valid value for the
-q terminal is everyEvent.
If you set the -I terminal to either the profile value or the
supportBundle value, this information is included with the emails
with the frequency specified by the -q terminal.
Terminal Definition

8Structure of a CLI Command
-quick Reduces the amount of time that is required to run a single-line operation.
An example of a single-line operation is the recreate snapshot
volume command. This terminal reduces time by not running background
processes for the duration of the command.
Do not use this terminal for operations that involve more than one single-line
operation. Extensive use of this command can overrun the controller with
more commands than the controller can process, which causes operational
failure. Also, status updates and configuration updates that are collected
usually from background processes will not be available to the CLI. This
terminal causes operations that depend on background information to fail.
-R (uppercase) Defines the user role for the password. The roles can be one of the following
options:
admin – The user has privilege to change the storage array
configuration.
monitor – The user has privilege to view the storage array
configuration, but cannot make changes.
The -R parameter is valid only when used with the –p parameter, which
specifies that a you define a password for a storage array.
The -R parameter is required only if the dual password feature is enabled on
the storage array. The -R parameter is not necessary under these conditions:
The dual password feature is not enabled on the storage array.
Only one admin role is set and the monitor role is not set for the storage
array.
-S (uppercase) Suppresses informational messages describing the command progress that
appear when you run script commands. (Suppressing informational
messages is also called silent mode.) This terminal suppresses these
messages:
Performing syntax check
Syntax check complete
Executing script
Script execution complete
SMcli completed successfully
-s (lowercase) Shows the alert settings in the configuration file when used with the -d
terminal.
-v Shows the current global status of the known devices in a configuration file
when used with the -d terminal.
Terminal Definition