IBM System Storage SAN Volume Controller and IBM

Storwize V7000
Version 6.4.0

Command-Line Interface User's Guide



GC27-2287-03
 Note
Before using this information and the product it supports, read the information in “Notices” on page 599.

This edition applies to IBM System Storage SAN Volume Controller, Version 6.4.0, and the IBM Storwize V7000,
Version 6.4.0, and to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces GC27-2287-02.
© Copyright IBM Corporation 2003, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
Tables . . . . . . . . . . . . . . . ix Modifying the amount of available memory for
Copy Services and Volume Mirroring features using
About this guide . . . . . . . . . . . xi the CLI . . . . . . . . . . . . . . . . 26
Creating volumes using the CLI . . . . . . . 28
Who should use this guide . . . . . . . . . xi
Adding a copy to a volume using the CLI . . . . 30
3 Summary of changes for GC27-2287-03 SAN Volume
Deleting a copy from a volume using the CLI . . . 31
3 Controller Command-Line Interface User's Guide . . xi
Configuring host objects using the CLI . . . . . 32
Emphasis . . . . . . . . . . . . . . . xiii
Creating host mappings using the CLI . . . . . 33
SAN Volume Controller library and related
Creating FlashCopy mappings using the CLI . . . 34
publications . . . . . . . . . . . . . . xiv
Preparing and starting a FlashCopy mapping
How to order IBM publications . . . . . . . xvi
using the CLI. . . . . . . . . . . . . 35
Sending your comments . . . . . . . . . xvii
Stopping FlashCopy mappings using the CLI . . 36
Syntax diagrams . . . . . . . . . . . . xvii
Deleting a FlashCopy mapping using the CLI . . 36
Terminology . . . . . . . . . . . . xviii
Creating a FlashCopy consistency group and adding
CLI special characters. . . . . . . . . . xix
mappings using the CLI . . . . . . . . . . 37
Using wildcards in the SAN Volume Controller
Preparing and starting a FlashCopy consistency
CLI . . . . . . . . . . . . . . . . xix
group using the CLI . . . . . . . . . . 38
Data types and value ranges. . . . . . . . xx
Stopping a FlashCopy consistency group using
CLI commands and parameters . . . . . . xxiv
the CLI . . . . . . . . . . . . . . . 39
CLI flags . . . . . . . . . . . . . . xxv
Deleting a FlashCopy consistency group using
CLI messages . . . . . . . . . . . . xxvi
the CLI . . . . . . . . . . . . . . . 40
Attributes of the -filtervalue parameters . . . xxvi
Creating Metro Mirror or Global Mirror
relationships using the CLI . . . . . . . . . 40
Chapter 1. Setting up an SSH client . . . 1 Modifying Metro Mirror or Global Mirror
e Setting up an SSH client on a Windows host. . . . 2 relationships using the CLI . . . . . . . . 41
Generating an SSH key pair using PuTTY . . . 2 Starting and stopping Metro Mirror or Global
Configuring a PuTTY session for the CLI . . . . 3 Mirror relationships using the CLI. . . . . . 41
Connecting to the CLI using PuTTY . . . . . 4 Displaying the progress of Metro Mirror or
Starting a PuTTY session for the CLI . . . . . 6 Global Mirror relationships using the CLI . . . 41
Preparing the SSH client on an AIX or Linux host . . 6 Switching Metro Mirror or Global Mirror
Generating an SSH key pair using OpenSSH. . . 7 relationships using the CLI . . . . . . . . 42
Connecting to the CLI using OpenSSH . . . . 8 Deleting Metro Mirror and Global Mirror
e Working with local and remote users . . . . . . 8 relationships using the CLI . . . . . . . . 42
Creating Metro Mirror or Global Mirror consistency
Chapter 2. Copying the SAN Volume groups using the CLI . . . . . . . . . . . 43
Controller software upgrade files using Modifying Metro Mirror or Global Mirror
PuTTY scp . . . . . . . . . . . . . 11 consistency groups using the CLI . . . . . . 43
Starting and stopping Metro Mirror or Global
Mirror consistency-group copy processes using
Chapter 3. Using the CLI . . . . . . . 13 the CLI . . . . . . . . . . . . . . . 44
Setting the clustered system time using the CLI . . 13 Deleting Metro Mirror or Global Mirror
Setting cluster date and time . . . . . . . . 14 consistency groups using the CLI . . . . . . 44
Viewing and updating license settings using the CLI 14 Creating Metro Mirror and Global Mirror
Displaying clustered system properties using the partnerships using the CLI . . . . . . . . . 44
CLI . . . . . . . . . . . . . . . . . 15 Modifying Metro Mirror and Global Mirror
Maintaining passwords for the front panel using the partnerships using the CLI . . . . . . . . 45
CLI . . . . . . . . . . . . . . . . . 16 Starting and stopping Metro Mirror and Global
Re-adding a repaired node to a clustered system Mirror partnerships using the CLI . . . . . . 45
using the CLI. . . . . . . . . . . . . . 17 Deleting Metro Mirror and Global Mirror
Displaying node properties using the CLI . . . . 20 partnerships using the CLI . . . . . . . . 46
Discovering MDisks using the CLI . . . . . . 21 Determining the WWPNs of a node using the CLI 46
Creating storage pools using the CLI . . . . . . 22 Listing node-dependent volumes using the CLI . . 46
Adding MDisks to storage pools using the CLI . . 25 Determining the VDisk name from the device
Setting a quorum disk using the CLI . . . . . . 26 identifier on the host . . . . . . . . . . . 47
Determining the host that a VDisk (volume) is
mapped to. . . . . . . . . . . . . . . 48

© Copyright IBM Corp. 2003, 2012 iii

 Determining the relationship between volumes and Setting up email event notifications and inventory
MDisks using the CLI . . . . . . . . . . . 49 reports using the CLI . . . . . . . . . . . 79
Determining the relationship between MDisks and Setting up email servers using the CLI . . . . . 80
controller LUNs using the CLI . . . . . . . . 49 Changing clustered system passwords using the CLI 81
Increasing the size of your clustered system using Changing the locale setting using the CLI . . . . 81
the CLI . . . . . . . . . . . . . . . . 50 Viewing the feature log using the CLI . . . . . 81
Adding a node to increase the size of a clustered Analyzing the error log using the CLI . . . . . 82
system using the CLI . . . . . . . . . . 50 Shutting down a clustered system using the CLI . . 82
Validating and repairing mirrored volume copies Upgrading the software automatically using the CLI 83
using the CLI. . . . . . . . . . . . . . 51
Repairing a space-efficient volume using the CLI . . 53 Chapter 4. Overview of the dumps
Recovering from offline volumes using the CLI . . 53 commands . . . . . . . . . . . . . 87
Recovering a node and returning it to the
clustered system using the CLI . . . . . . . 54
Recovering offline volumes using the CLI . . . 55 Chapter 5. Array commands . . . . . 89
Moving offline volumes to their original I/O charray . . . . . . . . . . . . . . . . 89
group using the CLI . . . . . . . . . . 56 charraymember . . . . . . . . . . . . . 89
Recording WWPN changes of replaced host HBAs 56 lsarray . . . . . . . . . . . . . . . . 91
Expanding VDisks (volumes) using the CLI . . . 57 lsarrayinitprogress . . . . . . . . . . . . 95
Expanding a VDisk (volume) that is mapped to lsarraylba . . . . . . . . . . . . . . . 96
an AIX host . . . . . . . . . . . . . 58 lsarraymember . . . . . . . . . . . . . 97
Expanding a volume that is mapped to a lsarraymembergoals . . . . . . . . . . . 99
Microsoft Windows host using the CLI . . . . 58 lsarraymemberprogress . . . . . . . . . . 100
Shrinking a volume using the CLI . . . . . . . 59 lsarraysyncprogress . . . . . . . . . . . 101
Migrating extents using the CLI . . . . . . . 60 mkarray . . . . . . . . . . . . . . . 102
Migrating volumes between storage pools using the recoverarray . . . . . . . . . . . . . . 103
CLI . . . . . . . . . . . . . . . . . 61 1 recoverarraybycluster. . . . . . . . . . . 104
e Moving a volume between I/O groups using the recoverarraybysystem . . . . . . . . . . 104
CLI . . . . . . . . . . . . . . . . . 63 rmarray . . . . . . . . . . . . . . . 104
Creating an image mode volume using the CLI . . 64
Migrating data to an image mode virtual disk using Chapter 6. Audit log commands . . . 107
the CLI . . . . . . . . . . . . . . . . 65 catauditlog . . . . . . . . . . . . . . 107
Deleting a node from a clustered system using the dumpauditlog . . . . . . . . . . . . . 108
CLI . . . . . . . . . . . . . . . . . 65 lsauditlogdumps (Deprecated) . . . . . . . . 109
Performing the clustered system maintenance
procedure using the CLI . . . . . . . . . . 67 Chapter 7. Backup and restore
Modifying the clustered system IP addresses using commands . . . . . . . . . . . . 111
the CLI . . . . . . . . . . . . . . . . 68
backup . . . . . . . . . . . . . . . 111
Changing the clustered system gateway address
clear . . . . . . . . . . . . . . . . 111
using the CLI. . . . . . . . . . . . . . 69
help . . . . . . . . . . . . . . . . 112
Changing the relationship bandwidth for a clustered
restore . . . . . . . . . . . . . . . . 113
system using the CLI . . . . . . . . . . . 69
Configuring the clustered system for iSCSI using the
CLI . . . . . . . . . . . . . . . . . 70 Chapter 8. Clustered system
Configuring or modifying an iSCSI alias using commands . . . . . . . . . . . . 115
the CLI . . . . . . . . . . . . . . . 71 addnode (SAN Volume Controller only) . . . . 115
Configuring the iSNS server address using the cfgportip . . . . . . . . . . . . . . . 117
CLI . . . . . . . . . . . . . . . . 72 1 chcluster . . . . . . . . . . . . . . . 119
Configuring clustered system iSCSI 1 chsystem . . . . . . . . . . . . . . . 119
authentication using the CLI. . . . . . . . 72 1 chsystemip . . . . . . . . . . . . . . 122
Configuring remote authentication service using CLI 73 chiogrp . . . . . . . . . . . . . . . 124
Configuring remote authentication service with chnode (SAN Volume Controller) / chnodecanister
Tivoli Integrated Portal (TIP) using the CLI. . . 73 (Storwize V7000) . . . . . . . . . . . . 127
Configuring remote authentication service with chnodehw (SAN Volume Controller) /
Lightweight Directory Access Protocol (LDAP) chnodecanisterhw (Storwize V7000) . . . . . . 128
using the CLI. . . . . . . . . . . . . 74 e cleardumps . . . . . . . . . . . . . . 129
Creating and working with user groups using the cpdumps . . . . . . . . . . . . . . . 130
CLI . . . . . . . . . . . . . . . . . 75 detectmdisk . . . . . . . . . . . . . . 132
Creating and working with users using the CLI . . 76 ping . . . . . . . . . . . . . . . . 133
Setting up SNMP notifications using the CLI . . . 77 rmnode (SAN Volume Controller) /
Setting up syslog notifications using the CLI . . . 78 rmnodecanister (Storwize V7000) . . . . . . . 134

iv SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 rmportip . . . . . . . . . . . . . . . 136 rmemailserver . . . . . . . . . . . . . 184
1 setclustertime . . . . . . . . . . . . . 137 rmemailuser . . . . . . . . . . . . . . 185
1 setsystemtime . . . . . . . . . . . . . 137 rmsnmpserver . . . . . . . . . . . . . 186
setpwdreset . . . . . . . . . . . . . . 137 rmsyslogserver . . . . . . . . . . . . . 186
settimezone . . . . . . . . . . . . . . 138 sendinventoryemail . . . . . . . . . . . 187
startstats . . . . . . . . . . . . . . . 139 startemail. . . . . . . . . . . . . . . 187
stopstats (Deprecated) . . . . . . . . . . 140 stopemail. . . . . . . . . . . . . . . 188
1 stopcluster . . . . . . . . . . . . . . 140 testemail . . . . . . . . . . . . . . . 188
stopsystem . . . . . . . . . . . . . . 140
Chapter 13. Enclosure commands . . 191
Chapter 9. Clustered system addcontrolenclosure . . . . . . . . . . . 191
diagnostic and service-aid commands 143 chenclosure . . . . . . . . . . . . . . 191
applysoftware . . . . . . . . . . . . . 143 chenclosurecanister . . . . . . . . . . . 192
caterrlog (Deprecated) . . . . . . . . . . 145 chenclosureslot . . . . . . . . . . . . . 193
caterrlogbyseqnum (Deprecated) . . . . . . . 145 lsenclosure . . . . . . . . . . . . . . 194
cherrstate. . . . . . . . . . . . . . . 145 lsenclosurebattery . . . . . . . . . . . . 196
clearerrlog . . . . . . . . . . . . . . 145 lscontrolenclosurecandidate. . . . . . . . . 198
dumperrlog . . . . . . . . . . . . . . 146 lsenclosurecanister. . . . . . . . . . . . 198
finderr . . . . . . . . . . . . . . . 146 lsenclosurepsu . . . . . . . . . . . . . 201
lserrlogbyfcconsistgrp (Deprecated) . . . . . . 147 lsenclosureslot . . . . . . . . . . . . . 202
lserrlogbyfcmap (Deprecated) . . . . . . . . 147 triggerenclosuredump . . . . . . . . . . 205
lserrlogbyhost (Deprecated) . . . . . . . . 147
lserrlogbyiogrp (Deprecated) . . . . . . . . 147 Chapter 14. Licensing commands . . 207
lserrlogbymdisk (Deprecated) . . . . . . . . 147 chlicense . . . . . . . . . . . . . . . 207
lserrlogbymdiskgrp (Deprecated) . . . . . . . 147 dumpinternallog . . . . . . . . . . . . 209
lserrlogbynode (Deprecated) . . . . . . . . 147
lserrlogbyrcconsistgrp (Deprecated) . . . . . . 147 Chapter 15. IBM FlashCopy
lserrlogbyrcrelationship (Deprecated) . . . . . 147
commands . . . . . . . . . . . . 211
lserrlogbyvdisk (Deprecated) . . . . . . . . 148
chfcconsistgrp . . . . . . . . . . . . . 211
lserrlogdumps (Deprecated) . . . . . . . . 148
chfcmap . . . . . . . . . . . . . . . 211
1 cheventlog . . . . . . . . . . . . . . 148
mkfcconsistgrp . . . . . . . . . . . . . 213
lseventlog . . . . . . . . . . . . . . 148
mkfcmap . . . . . . . . . . . . . . . 214
lsservicestatus . . . . . . . . . . . . . 152
prestartfcconsistgrp . . . . . . . . . . . 216
lssyslogserver . . . . . . . . . . . . . 160
prestartfcmap . . . . . . . . . . . . . 218
setlocale . . . . . . . . . . . . . . . 161
rmfcconsistgrp . . . . . . . . . . . . . 219
svqueryclock . . . . . . . . . . . . . 162
rmfcmap . . . . . . . . . . . . . . . 219
writesernum. . . . . . . . . . . . . . 162
startfcconsistgrp . . . . . . . . . . . . 220
startfcmap . . . . . . . . . . . . . . 222
Chapter 10. Controller command . . . 165 stopfcconsistgrp . . . . . . . . . . . . 223
chcontroller . . . . . . . . . . . . . . 165 stopfcmap . . . . . . . . . . . . . . 224

Chapter 11. Drive commands. . . . . 167 Chapter 16. Host commands . . . . . 227
applydrivesoftware . . . . . . . . . . . 167 addhostiogrp . . . . . . . . . . . . . 227
chdrive . . . . . . . . . . . . . . . 168 addhostport . . . . . . . . . . . . . . 227
lsdrive. . . . . . . . . . . . . . . . 169 chhost . . . . . . . . . . . . . . . . 228
lsdrivelba. . . . . . . . . . . . . . . 171 mkhost . . . . . . . . . . . . . . . 230
lsdriveprogress . . . . . . . . . . . . . 172 rmhost . . . . . . . . . . . . . . . 231
triggerdrivedump . . . . . . . . . . . . 173 rmhostiogrp . . . . . . . . . . . . . . 232
rmhostport . . . . . . . . . . . . . . 233
Chapter 12. Email and event
notification commands . . . . . . . 175 Chapter 17. Information commands 235
chemail . . . . . . . . . . . . . . . 175 ls2145dumps (Deprecated) . . . . . . . . . 235
chemailserver . . . . . . . . . . . . . 176 lscimomdumps (Deprecated) . . . . . . . . 235
chemailuser . . . . . . . . . . . . . . 177 lscopystatus . . . . . . . . . . . . . . 235
chsnmpserver . . . . . . . . . . . . . 178 1 lscluster . . . . . . . . . . . . . . . 236
chsyslogserver . . . . . . . . . . . . . 179 1 lsclustercandidate . . . . . . . . . . . . 236
mkemailserver . . . . . . . . . . . . . 180 lscluster . . . . . . . . . . . . . . . 236
mkemailuser . . . . . . . . . . . . . 181 lsclusterip . . . . . . . . . . . . . . 236
mksnmpserver . . . . . . . . . . . . . 182 1 lssystem . . . . . . . . . . . . . . . 236
mksyslogserver . . . . . . . . . . . . . 183

Contents v
1 lssystemip . . . . . . . . . . . . . . 240 lssnmpserver . . . . . . . . . . . . . 335
1 lssystemstats . . . . . . . . . . . . . 242 lssoftwaredumps (Deprecated). . . . . . . . 336
lscontroller . . . . . . . . . . . . . . 244 lssoftwareupgradestatus . . . . . . . . . . 336
1 lspartnershipcandidate . . . . . . . . . . 247 lstimezones . . . . . . . . . . . . . . 337
lscontrollerdependentvdisks . . . . . . . . 248 lsuser . . . . . . . . . . . . . . . . 338
lscurrentuser . . . . . . . . . . . . . 248 lsusergrp . . . . . . . . . . . . . . . 339
lsdiscoverystatus . . . . . . . . . . . . 249 lsvdisk . . . . . . . . . . . . . . . 340
lsdumps . . . . . . . . . . . . . . . 250 1 lsvdiskaccess . . . . . . . . . . . . . 347
lsemailserver . . . . . . . . . . . . . 251 lsvdiskcopy . . . . . . . . . . . . . . 348
lsemailuser . . . . . . . . . . . . . . 252 lsvdiskdependentmaps . . . . . . . . . . 352
lsfabric . . . . . . . . . . . . . . . 253 lsvdiskextent . . . . . . . . . . . . . 352
lsfcconsistgrp . . . . . . . . . . . . . 255 lsvdiskfcmapcopies . . . . . . . . . . . 354
lsfcmap . . . . . . . . . . . . . . . 257 lsvdiskfcmappings. . . . . . . . . . . . 355
lsfcmapcandidate . . . . . . . . . . . . 259 lsvdiskhostmap. . . . . . . . . . . . . 355
lsfcmapprogress . . . . . . . . . . . . 260 lsvdisklba . . . . . . . . . . . . . . 357
lsfcmapdependentmaps . . . . . . . . . . 261 lsvdiskmember . . . . . . . . . . . . . 358
lsfeaturedumps (Deprecated) . . . . . . . . 262 lsvdiskprogress . . . . . . . . . . . . . 360
lsfreeextents . . . . . . . . . . . . . . 262 lsvdisksyncprogress . . . . . . . . . . . 360
lshbaportcandidate . . . . . . . . . . . 262 lsdependentvdisks. . . . . . . . . . . . 361
lshost . . . . . . . . . . . . . . . . 263 lssasfabric . . . . . . . . . . . . . . 362
lshostiogrp . . . . . . . . . . . . . . 266 showtimezone . . . . . . . . . . . . . 364
lshostvdiskmap. . . . . . . . . . . . . 267
lsiogrp . . . . . . . . . . . . . . . 269 Chapter 18. Livedump commands . . 365
lsiogrphost . . . . . . . . . . . . . . 271 cancellivedump. . . . . . . . . . . . . 365
lsiogrpcandidate . . . . . . . . . . . . 271 lslivedump . . . . . . . . . . . . . . 365
lsiostatsdumps (Deprecated) . . . . . . . . 272 preplivedump . . . . . . . . . . . . . 366
lsiotracedumps (Deprecated) . . . . . . . . 272 triggerlivedump . . . . . . . . . . . . 366
lsiscsiauth . . . . . . . . . . . . . . 272
lslicense . . . . . . . . . . . . . . . 274
Chapter 19. Managed disk commands 369
lsmdisk . . . . . . . . . . . . . . . 275
applymdisksoftware (Discontinued) . . . . . . 369
lsmdiskdumps (Deprecated) . . . . . . . . 279
chmdisk . . . . . . . . . . . . . . . 369
lsmdisklba . . . . . . . . . . . . . . 280
chquorum . . . . . . . . . . . . . . 369
lsmdiskcandidate . . . . . . . . . . . . 281
dumpallmdiskbadblocks. . . . . . . . . . 371
lsmdiskextent . . . . . . . . . . . . . 282
dumpmdiskbadblocks . . . . . . . . . . 372
e lsmdiskgrp . . . . . . . . . . . . . . 284
includemdisk . . . . . . . . . . . . . 373
lsmdiskmember . . . . . . . . . . . . 288
setquorum (Deprecated) . . . . . . . . . . 374
lsmigrate . . . . . . . . . . . . . . . 289
triggermdiskdump (Discontinued) . . . . . . 374
lsnode (SAN Volume Controller) / lsnodecanister
(Storwize V7000) . . . . . . . . . . . . 290
lsnodecandidate (SAN Volume Controller). . . . 294 Chapter 20. Managed disk group
lsnodedependentvdisks (Deprecated) . . . . . 295 commands . . . . . . . . . . . . 375
lsnodehw (SAN Volume Controller) / addmdisk . . . . . . . . . . . . . . 375
lsnodecanisterhw (Storwize V7000) . . . . . . 295 chmdiskgrp . . . . . . . . . . . . . . 376
lsnodestats (SAN Volume Controller) / mkmdiskgrp . . . . . . . . . . . . . 377
lsnodecanisterstats (Storwize V7000). . . . . . 297 rmmdisk . . . . . . . . . . . . . . . 379
lsnodevpd (SAN Volume Controller) / rmmdiskgrp . . . . . . . . . . . . . . 380
lsnodecanistervpd (Storwize V7000) . . . . . . 304
lspartnership . . . . . . . . . . . . . 310 Chapter 21. Metro Mirror and Global
lspartnershipcandidate . . . . . . . . . . 311 Mirror commands . . . . . . . . . 383
lsportip . . . . . . . . . . . . . . . 312
chpartnership . . . . . . . . . . . . . 383
3 lsportfc . . . . . . . . . . . . . . . 316
chrcconsistgrp . . . . . . . . . . . . . 384
lsquorum . . . . . . . . . . . . . . . 318
chrcrelationship . . . . . . . . . . . . 385
lsrcconsistgrp . . . . . . . . . . . . . 319
mkpartnership . . . . . . . . . . . . . 389
lsrcrelationship . . . . . . . . . . . . . 322
mkrcconsistgrp . . . . . . . . . . . . . 389
lsrcrelationshipcandidate . . . . . . . . . 325
mkrcrelationship . . . . . . . . . . . . 390
lsrcrelationshipprogress . . . . . . . . . . 326
rmpartnership . . . . . . . . . . . . . 393
lsrepairsevdiskcopyprogress . . . . . . . . 327
rmrcconsistgrp . . . . . . . . . . . . . 394
lsrepairvdiskcopyprogress . . . . . . . . . 328
rmrcrelationship . . . . . . . . . . . . 394
lsrmvdiskdependentmaps . . . . . . . . . 330
startrcconsistgrp . . . . . . . . . . . . 395
lsroute. . . . . . . . . . . . . . . . 331
startrcrelationship . . . . . . . . . . . . 398
lssevdiskcopy . . . . . . . . . . . . . 332
stoprcconsistgrp . . . . . . . . . . . . 400

vi SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
stoprcrelationship . . . . . . . . . . . . 402 Chapter 27. Tracing commands. . . . 445
switchrcconsistgrp . . . . . . . . . . . . 403 setdisktrace . . . . . . . . . . . . . . 445
switchrcrelationship . . . . . . . . . . . 404 settrace . . . . . . . . . . . . . . . 445
starttrace . . . . . . . . . . . . . . . 447
Chapter 22. Migration commands . . . 407 stoptrace . . . . . . . . . . . . . . . 448
migrateexts . . . . . . . . . . . . . . 407
migratetoimage. . . . . . . . . . . . . 408 Chapter 28. User management
migratevdisk . . . . . . . . . . . . . 409 commands . . . . . . . . . . . . 449
chauthservice . . . . . . . . . . . . . 449
Chapter 23. Service information chcurrentuser . . . . . . . . . . . . . 451
commands . . . . . . . . . . . . 411 chldap. . . . . . . . . . . . . . . . 452
lscmdstatus . . . . . . . . . . . . . . 411 chldapserver . . . . . . . . . . . . . 454
lsfiles . . . . . . . . . . . . . . . . 411 chuser . . . . . . . . . . . . . . . . 456
lshardware . . . . . . . . . . . . . . 412 chusergrp . . . . . . . . . . . . . . 457
lsservicenodes . . . . . . . . . . . . . 415 getstatus . . . . . . . . . . . . . . . 458
lsservicerecommendation . . . . . . . . . 417 mkuser . . . . . . . . . . . . . . . 458
lsservicestatus . . . . . . . . . . . . . 417 lsldap . . . . . . . . . . . . . . . . 459
lsldapserver . . . . . . . . . . . . . . 461
Chapter 24. Service mode commands mkldapserver . . . . . . . . . . . . . 462
mkusergrp . . . . . . . . . . . . . . 463
(Discontinued) . . . . . . . . . . . 425
rmldapserver . . . . . . . . . . . . . 464
applysoftware (Discontinued) . . . . . . . . 425
rmuser . . . . . . . . . . . . . . . 465
cleardumps (Discontinued) . . . . . . . . . 425
rmusergrp . . . . . . . . . . . . . . 465
dumperrlog (Discontinued) . . . . . . . . . 425
testldapserver . . . . . . . . . . . . . 466
exit (Discontinued) . . . . . . . . . . . 425

Chapter 29. Virtual disk commands 469

Chapter 25. Service mode information
addvdiskcopy . . . . . . . . . . . . . 469
commands (Discontinued) . . . . . . 427 1 addvdiskaccess . . . . . . . . . . . . . 474
ls2145dumps (Discontinued) . . . . . . . . 427 chvdisk . . . . . . . . . . . . . . . 475
lscimomdumps (Discontinued) . . . . . . . 427 1 movevdisk . . . . . . . . . . . . . . 477
lsclustervpd (Discontinued). . . . . . . . . 427 expandvdisksize . . . . . . . . . . . . 479
lserrlogdumps (Discontinued) . . . . . . . . 427 mkvdisk . . . . . . . . . . . . . . . 481
lsfeaturedumps (Discontinued) . . . . . . . 427 mkvdiskhostmap . . . . . . . . . . . . 489
lsiostatsdumps (Discontinued) . . . . . . . . 427 recovervdisk. . . . . . . . . . . . . . 490
lsiotracedumps (Discontinued) . . . . . . . 427 1 recovervdiskbycluster . . . . . . . . . . 491
lsmdiskdumps (Discontinued) . . . . . . . . 427 1 recovervdiskbysystem . . . . . . . . . . 491
lssoftwaredumps (Discontinued) . . . . . . . 427 recovervdiskbyiogrp . . . . . . . . . . . 492
repairsevdiskcopy . . . . . . . . . . . . 493
Chapter 26. Service task commands 429 repairvdiskcopy . . . . . . . . . . . . 493
chenclosurevpd. . . . . . . . . . . . . 429 rmvdisk . . . . . . . . . . . . . . . 495
chnodeled . . . . . . . . . . . . . . 430 rmvdiskcopy . . . . . . . . . . . . . 497
chserviceip . . . . . . . . . . . . . . 430 1 rmvdiskaccess . . . . . . . . . . . . . 497
chwwnn . . . . . . . . . . . . . . . 432 rmvdiskhostmap . . . . . . . . . . . . 498
cpfiles . . . . . . . . . . . . . . . . 433 shrinkvdisksize . . . . . . . . . . . . . 499
installsoftware . . . . . . . . . . . . . 434 splitvdiskcopy . . . . . . . . . . . . . 501
leavecluster . . . . . . . . . . . . . . 435
metadata . . . . . . . . . . . . . . . 435 Chapter 30. Command-line interface
mkcluster. . . . . . . . . . . . . . . 436 messages . . . . . . . . . . . . . 503
rescuenode . . . . . . . . . . . . . . 437
resetpassword . . . . . . . . . . . . . 438
restartservice . . . . . . . . . . . . . 438 Appendix. Accessibility . . . . . . . 597
setlocale (satask) . . . . . . . . . . . . 439
setpacedccu . . . . . . . . . . . . . . 440 Notices . . . . . . . . . . . . . . 599
settempsshkey . . . . . . . . . . . . . 440 Trademarks . . . . . . . . . . . . . . 601
snap . . . . . . . . . . . . . . . . 441
startservice . . . . . . . . . . . . . . 441 Index . . . . . . . . . . . . . . . 603
stopnode . . . . . . . . . . . . . . . 442
stopservice . . . . . . . . . . . . . . 442
t3recovery . . . . . . . . . . . . . . 443

Contents vii
viii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Tables
3 1. Terminology mapping table for version 6.3.0 xi 1 34. Attribute values. . . . . . . . . . . 237
2. SAN Volume Controller library. . . . . . xiv 1 35. lssystemstats attribute values . . . . . . 243
3. Other IBM publications . . . . . . . . xv 36. MDisk output . . . . . . . . . . . 277
4. IBM documentation and related websites xvi 37. lsmdisklba command output . . . . . . 281
5. Valid filter attributes . . . . . . . . xxvii 38. lsnode or lsnodecanister attribute values 292
6. Maximum volume capacity by extent size 24 39. lsnodecandidate outputs . . . . . . . . 295
7. Memory required for Volume Mirroring and 40. lsnodehw attribute values . . . . . . . 296
Copy Services . . . . . . . . . . . . 27 41. lsnodestats or lsnodecanister attribute values 298
8. RAID level comparisons . . . . . . . . 27 42. Stat_name field values . . . . . . . . 302
9. Volume copy resynchronization rates . . . . 29 43. lspartnership attribute values . . . . . . 310
10. charraymember combination options . . . . 90 1 44. lsportip output . . . . . . . . . . . 314
11. MDisk output . . . . . . . . . . . . 93 3 45. lsportfc output . . . . . . . . . . . 317
12. lsarrayinitprogress output . . . . . . . . 95 46. lsrcconsistgrp command output values 320
13. lsarraylba output. . . . . . . . . . . 96 47. lsrcrelationship command attributes and
14. lsarraymemberoutput . . . . . . . . . 97 values . . . . . . . . . . . . . . 323
15. lsarraymembergoals output . . . . . . . 99 48. lsvdisklba command output scenarios 358
16. lsarraymemberprogress output . . . . . . 101 49. lssasfabric output . . . . . . . . . . 363
17. lsarraysyncprogress output . . . . . . . 102 50. lslivedump outputs . . . . . . . . . 366
1 18. IP address list formats . . . . . . . . 124 51. Number of extents reserved by extent size 371
19. Memory required for VDisk Mirroring and 52. stoprcconsistgrp consistency group states 401
Copy Services . . . . . . . . . . . 126 53. stoprcrelationship consistency group states 403
20. RAID level comparisons . . . . . . . . 126 54. lshardware attribute values . . . . . . . 413
21. lseventlog output . . . . . . . . . . 149 55. lsservicenodes outputs . . . . . . . . 415
22. lsservicestatus output . . . . . . . . . 153 56. lsservicenodes outputs . . . . . . . . 416
23. lsservicestatus output . . . . . . . . . 155 57. lsservicestatus output . . . . . . . . . 418
24. lsdrive output . . . . . . . . . . . 169 58. lsservicestatus output . . . . . . . . . 420
25. lsdrivelba output . . . . . . . . . . 171 59. lsldap attribute values . . . . . . . . 460
26. lsenclosure output . . . . . . . . . . 195 60. lsldapserver attribute values . . . . . . 461
27. lsenclosurebattery outputs . . . . . . . 197 61. testldapserver attribute values . . . . . . 467
28. lscontrolenclosurecandidate attribute values 198 e 62. Storage pool Easy Tier settings . . . . . . 471
29. lsenclosurecanister output . . . . . . . 199 63. Relationship between the rate value and the
30. lsenclosurepsu output. . . . . . . . . 201 data copied per second . . . . . . . . 473
31. lsenclosureslot output . . . . . . . . . 203 64. Relationship between the rate value and the
32. Relationship between the rate, data rate and data copied per second . . . . . . . . 487
grains per second values . . . . . . . . 213
33. Relationship between the rate, data rate and
grains per second values . . . . . . . . 216

© Copyright IBM Corp. 2003, 2012 ix

x SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 About this guide
This publication provides information that helps you configure and use the IBM® System Storage® SAN
Volume Controller and IBM Storwize® V7000.

Who should use this guide

This guide is intended for system administrators or others who install and use the SAN Volume
Controller or Storwize V7000.

Before you use the SAN Volume Controller, you should have an understanding of storage area networks
(SANs), the storage requirements of your enterprise, and the capabilities of your storage units.

3 Summary of changes for GC27-2287-03 SAN Volume Controller

3 Command-Line Interface User's Guide
3 This topic describes the changes that have been made to the SAN Volume Controller Command-Line
3 Interface User's Guide since the previous edition (GC27-2287-02).

3 6.4.0 Terminology changes

3 To coincide with new and existing IBM products and functions, several common terms have changed and
3 are incorporated in the SAN Volume Controller information. Certain SAN Volume Controller information,
3 particularly command-line interface (CLI) documentation, remains primarily unchanged.

3 The following table shows the current and previous use of the changed common terms in the commands
3 for version 6.3.0.
3 Table 1. Terminology mapping table for version 6.3.0
3 6.3.0 SAN Volume Previous SAN Volume
3 Controller term Controller term Description
3 clustered system or cluster A collection of nodes that are placed in pairs (I/O groups)
3 system for redundancy, which provide a single management
3 interface.
3

3 New information

3 The following new commands have been added for this edition:
3 v “addvdiskaccess” on page 474
3 v “cheventlog” on page 148
3 v lsenclosurechassis
3 v “lsportfc” on page 316
3 v “lsvdiskaccess” on page 347
3 v “movevdisk” on page 477
3 v “rmvdiskaccess” on page 497

© Copyright IBM Corp. 2003, 2012 xi

3 Changed commands

3 The following commands and topics have been updated for this edition:
3 v “addnode (SAN Volume Controller only)” on page 115
3 v “addvdiskcopy” on page 469
3 v “applysoftware” on page 143
3 v “cfgportip” on page 117
3 v “chauthservice” on page 449
3 v “chvdisk” on page 475
3 v “chenclosure” on page 191
3 v “chenclosurecanister” on page 192
3 v “chlicense” on page 207
3 v “chnodehw (SAN Volume Controller) / chnodecanisterhw (Storwize V7000)” on page 128
3 v chnodecanisterhw
3 v “chserviceip” on page 430
3 v “chsystem” on page 119
3 v “chsystemip” on page 122
3 v “rmvdiskhostmap” on page 498
3 v “installsoftware” on page 434
3 v “lsenclosure” on page 194
3 v “lsenclosurecanister” on page 198
3 v “lsenclosurepsu” on page 201
3 v “lseventlog” on page 148
3 v “lsfabric” on page 253
3 v “lshardware” on page 412
3 v “lshost” on page 263
3 v “lslicense” on page 274
3 v “lshostvdiskmap” on page 267
3 v “lsmdiskgrp” on page 284
3 v “lsnode (SAN Volume Controller) / lsnodecanister (Storwize V7000)” on page 290
3 v lsnodecanister
3 v “lsnodehw (SAN Volume Controller) / lsnodecanisterhw (Storwize V7000)” on page 295
3 v lsnodecanisterhw
3 v lsnodevpd (Discontinued)
3 v lsnodecanistervpd
3 v “lsiogrp” on page 269
3 v “lsrepairvdiskcopyprogress” on page 328
3 v “lsservicestatus” on page 152
3 v “lssevdiskcopy” on page 332
3 v “lssoftwareupgradestatus” on page 336
3 v “lssystem” on page 236
3 v “lssystemip” on page 240
3 v “lsvdisk” on page 340
3 v “lsvdiskcopy” on page 348
3 v “lsvdiskhostmap” on page 355

xii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
3 v “lsvdisklba” on page 357
3 v “lsmdisklba” on page 280
3 v “mkcluster” on page 436
3 v “mkvdisk” on page 481
3 v “mkvdiskhostmap” on page 489
3 v “mkhost” on page 230
3 v “recoverarraybysystem” on page 104
3 v “repairvdiskcopy” on page 493
3 v “rmhostiogrp” on page 232
3 v “recovervdiskbysystem” on page 491
3 v “setsystemtime” on page 137
3 v “shrinkvdisksize” on page 499
3 v “splitvdiskcopy” on page 501
3 v “stopsystem” on page 140

3 Deprecated commands

3 The following topics have been updated for this edition:

3 v “cherrstate” on page 145

3 New topics

3 The following topics have been updated for this edition:

3 v None

3 Changed topics

3 The following topics have been updated for this edition:

e v “Moving a volume between I/O groups using the CLI” on page 63
e
Emphasis
Different typefaces are used in this guide to show emphasis.

The following typefaces are used to show emphasis:

Boldface Text in boldface represents menu items.

Bold monospace Text in bold monospace represents command names.
Italics Text in italics is used to emphasize a word. In command
syntax, it is used for variables for which you supply
actual values, such as a default directory or the name of
a system.
Monospace Text in monospace identifies the data or commands that
you type, samples of command output, examples of
program code or messages from the system, or names of
command flags, parameters, arguments, and name-value
pairs.

About this guide xiii

SAN Volume Controller library and related publications
Product manuals, other publications, and websites contain information that relates to SAN Volume
Controller.

SAN Volume Controller Information Center

The IBM System Storage SAN Volume Controller Information Center contains all of the information that
is required to install, configure, and manage the SAN Volume Controller. The information center is
updated between SAN Volume Controller product releases to provide the most current documentation.
The information center is available at the following website:

publib.boulder.ibm.com/infocenter/svc/ic/index.jsp

SAN Volume Controller library

Unless otherwise noted, the publications in the SAN Volume Controller library are available in Adobe
portable document format (PDF) from the following website:

www.ibm.com/storage/support/2145

Each of the PDF publications in Table 2 is available in this information center by clicking the number in
the “Order number” column:
Table 2. SAN Volume Controller library
Title Description Order number
IBM System Storage SAN Volume This guide provides the instructions GC27-3923
Controller Model 2145-CG8 Hardware that the IBM service representative
Installation Guide uses to install the hardware for SAN
Volume Controller model 2145-CG8.
IBM System Storage SAN Volume This guide provides the instructions GC27-2283
Controller Hardware Maintenance Guide that the IBM service representative
uses to service the SAN Volume
Controller hardware, including the
removal and replacement of parts.
IBM System Storage SAN Volume This guide describes the features of GC27-2284
Controller Troubleshooting Guide each SAN Volume Controller model,
explains how to use the front panel,
and provides maintenance analysis
procedures to help you diagnose and
solve problems with the SAN Volume
Controller.
IBM System Storage SAN Volume This guide provides guidelines for GC27-2286
Controller Software Installation and configuring your SAN Volume
Configuration Guide Controller. Instructions for backing
up and restoring the cluster
configuration, using and upgrading
the management GUI, using the CLI,
upgrading the SAN Volume
Controller software, and replacing or
adding nodes to a cluster are
included.

xiv SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 2. SAN Volume Controller library (continued)
Title Description Order number
IBM System Storage SAN Volume This guide describes the concepts of GC27-2288
Controller CIM Agent Developer's Guide the Common Information Model
(CIM) environment. Procedures
describe such tasks as using the CIM
agent object class instances to
complete basic storage configuration
tasks, establishing new Copy Services
relationships, and performing CIM
agent maintenance and diagnostic
tasks.
IBM System Storage SAN Volume This guide contains translated GA32-0844
Controller Safety Notices caution and danger statements. Each
caution and danger statement in the
SAN Volume Controller
documentation has a number that
you can use to locate the
corresponding statement in your
language in the IBM System Storage
SAN Volume Controller Safety Notices
document.
IBM System Storage SAN Volume This document introduces the major GA32-0843
Controller Read First Flyer components of the SAN Volume
Controller system and describes how
to get started installing the hardware
and software.
IBM System Storage SAN Volume This guide describes the commands GC27-2287
Controller and IBM Storwize V7000 that you can use from the SAN
Command-Line Interface User's Guide Volume Controller command-line
interface (CLI).
IBM Statement of Limited Warranty This multilingual document provides Part number: 85Y5978
(2145 and 2076) information about the IBM warranty
for machine types 2145 and 2076.
IBM License Agreement for Machine This multilingual guide contains the SC28-6872 (contains Z125-5468)
Code License Agreement for Machine Code
for the SAN Volume Controller
product.

Other IBM publications

Table 3 lists IBM publications that contain information related to the SAN Volume Controller.
Table 3. Other IBM publications
Title Description Order number
IBM System Storage Productivity This guide introduces the IBM System SC23-8824
Center Introduction and Planning Storage Productivity Center hardware and
Guide software.
Read This First: Installing the IBM This guide describes how to install the GI11-8938
System Storage Productivity Center IBM System Storage Productivity Center
hardware.
IBM System Storage Productivity This guide describes how to configure the SC27-2336
Center User's Guide IBM System Storage Productivity Center
software.

About this guide xv

 Table 3. Other IBM publications (continued)
Title Description Order number
IBM System Storage Multipath This guide describes the IBM System GC52-1309
Subsystem Device Driver User's Guide Storage Multipath Subsystem Device
Driver for IBM System Storage products
and how to use it with the SAN Volume
Controller.
IBM Storage Management Pack for This guide describes how to install, GC27-3909
Microsoft System Center Operations configure, and use the IBM Storage
Manager User Guide Management Pack for Microsoft System publibfp.dhe.ibm.com/epubs/
Center Operations Manager (SCOM). pdf/c2739092.pdf
e IBM Storage Management Console for This publication describes how to install, GA32-0929
e VMware vCenter, version 3.0.0, User configure, and use the IBM Storage
e Guide Management Console for VMware vCenter, publibfp.dhe.ibm.com/epubs/
e which enables SAN Volume Controller and pdf/a3209295.pdf
e other IBM storage systems to be integrated
e in VMware vCenter environments.

IBM documentation and related websites

Table 4 lists websites that provide publications and other information about the SAN Volume Controller
or related products or technologies.
Table 4. IBM documentation and related websites
Website Address
Support for SAN Volume Controller (2145) www.ibm.com/storage/support/2145
Support for IBM System Storage and IBM www.ibm.com/storage/support/
TotalStorage products
IBM Publications Center www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss
®
IBM Redbooks publications www.redbooks.ibm.com/

Related accessibility information

To view a PDF file, you need Adobe Acrobat Reader, which can be downloaded from the Adobe website:

www.adobe.com/support/downloads/main.html

How to order IBM publications

The IBM Publications Center is a worldwide central repository for IBM product publications and
marketing material.

The IBM Publications Center offers customized search functions to help you find the publications that
you need. Some publications are available for you to view or download at no charge. You can also order
publications. The publications center displays prices in your local currency. You can access the IBM
Publications Center through the following website:

www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

xvi SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Sending your comments
Your feedback is important in helping to provide the most accurate and highest quality information.

To submit any comments about this book or any other SAN Volume Controller documentation:
v Go to the feedback page on the website for the SAN Volume Controller Information Center at
publib.boulder.ibm.com/infocenter/svc/ic/index.jsp?topic=/com.ibm.storage.svc.console.doc/
feedback.htm. There you can use the feedback page to enter and submit comments or browse to the
topic and use the feedback link in the running footer of that page to identify the topic for which you
have a comment.
v Send your comments by email to [email protected]. Include the following information for this
publication or use suitable replacements for the publication title and form number for the publication
on which you are commenting:
– Publication title: IBM System Storage SAN Volume Controller and IBM Storwize V7000 Command-Line
Interface User's Guide
– Publication form number: GC27-2287-01
– Page, table, or illustration numbers that you are commenting on
– A detailed description of any information that should be changed

Syntax diagrams
A syntax diagram uses symbols to represent the elements of a command and to specify the rules for
using these elements.

The following table explains how to read the syntax diagrams that represent the command-line interface
(CLI) commands. In doing so, it defines the symbols that represent the CLI command elements.

Element Syntax Description

Main path line >>><>() () () >>Begins on the left with double
arrowheads ()>< and ends on the
right with two arrowheads facing
each other (). If a diagram is longer
than one line, each line to be
continued ends with a single>
arrowhead () and the next line
begins with a single arrowhead.
Read the diagrams from
left–to–right, top–to–bottom,
following the main path line.
Keyword Represents the name of a command,


esscli
 flag, parameter, or argument. A
keyword is not in italics. Spell a
keyword exactly as it is shown in
the syntax diagram.
Required keywords Indicate the parameters or


–a AccessFile
 arguments that you must specify for
–u Userid the command. Required keywords
–p Password appear on the main path line.
Required keywords that cannot be
used together are stacked vertically.

About this guide xvii

Element Syntax Description
Optional keywords Indicate the parameters or



 arguments that you can choose to
–h specify for the command. Optional
-help keywords appear below the main
–? path line. Mutually exclusive
optional keywords are stacked
vertically.
Default value Appears above the main path line.
FCP


protocol = FICON


Repeatable keyword Represents a parameter or argument

or value

newports = ALL
 that you can specify more than once.
PortId1,PortId2,... A repeatable keyword or value is
represented by an arrow returning to
the left above the keyword or value.
Variable Represents the value that you need


AccessFile
 to supply for a parameter or
argument, such as a file name, user
name, or password. Variables are in
italics.
Space separator Adds a blank space on the main


–u Userid p Password
 path line to separate keywords,
parameters, arguments, or variables
from each other.
Quotation mark Indicates the start and end of a
delimiters

–d " ess = EssId host =
parameter or argument that contains
multiple values. Enclose one or more

'Host Name' profile = ProfileName
name–value pairs in a set of double
quotation marks for a particular

"
 parameter or argument. If the value
of a parameter or name–value pair
contains a blank or white space,
enclose the entire value in a set of
single quotation marks.
Equal–sign operator Separates a name from its value in a


" ess = EssId profile =
name–value pair.

ProfileName "


Syntax fragment Breaks up syntax diagrams that are

Fragment Name
 too long, too complex, or repetitious.
The fragment name is inserted in the
Fragment name: main diagram, and the actual
fragment is shown below the main
( fragment details ) diagram.

Terminology
These are abbreviations that are most commonly used for the command-line interface operations.

Name Object type

Host host

xviii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Name Object type
Virtual disk (volume) vdisk
Virtual disk copy vdiskcopy
Space-efficient (thin-provisioned) virtual disk copy sevdiskcopy
Managed disk mdisk
Managed disk group (storage pool) mdiskgrp
I/O group iogrp
Node node
Cluster clustered system (system)
Controller controller
®
IBM FlashCopy mapping fcmap
FlashCopy consistency group fcconsistgrp
Metro Mirror or Global Mirror relationship rcrelationship
Metro Mirror or Global Mirror consistency group rcconsistgrp
Unsupported/unknown object unknown

CLI special characters

The following special characters are used in the command-line interface (CLI) command examples.
minus (-) sign
Flags are prefixed with a - (minus) sign. Flags define the action of a command or modify the
operation of a command. You can use multiple flags, followed by parameters, when you issue a
command. The - character cannot be used as the first character of an object name.
vertical bar (|)
A vertical bar signifies that you choose only one value. For example, [ a | b ] in brackets
indicates that you can choose a, b, or nothing. Similarly, { a | b } in braces indicates that you
must choose either a or b.

Using wildcards in the SAN Volume Controller CLI

You can use wildcards in the SAN Volume Controller Command-Line Interface.

The SAN Volume Controller supports the use of the asterisk character (*) as a wildcard within the
arguments of certain parameters. There are some behavioral issues that must be considered when using
wildcards in order to prevent unexpected results. These behavioral issues and the ways to avoid them are
as follows:
1. Running the command while logged onto the node.
The shell will attempt to interpret any of the special characters if they are not escaped (preceded with
a backslash character). Wildcards will be expanded into a list of files if any files exist that match the
wildcards. If no matching files exist, the wildcard is passed to the SAN Volume Controller command
untouched.
To prevent expansion, issue the following command in one of its formats:

cleardumps -prefix '/dumps/*.txt' with single quotation marks

(’’), or

cleardumps -prefix /dumps/\*.txt using a backslash (\), or

About this guide xix

 cleardumps -prefix "/dumps/*.txt" with double quotation marks
("").
2. Running the command through Secure Shell (SSH), for example from a host.
This method is slightly more complicated because the host shell processes the command line before it
is passed through SSH to the shell on the clustered system (system). This means an extra layer of
protection is required around the wildcard as the host shell will strip off any protecting quotes, and if
the wildcard is exposed to the system shell, this will result in the wildcard being expanded in the
system shell.
To prevent expansion, issue the following command in one of its formats:

cleardumps "'/dumps/*.txt'" with single quotation marks (’’)

inside of double quotation marks (""), or

cleardumps '/dumps/\*.txt' using a backslash (\) inside of

single quotation marks (’’), or

cleardumps '"/dumps/*.txt"' with double quotation marks ("")

inside of single quotation marks (’’).

Data types and value ranges

The maximum length of any single parameter entered into the command line is 2176 bytes.

Note: When creating a new object, the clustered system (system) assigns a default -type name if one is
not specified. The default -type name consists of the object prefix and the lowest available integer starting
from 0 (except for nodes starting from 1); for example, vdisk23; the default -type name must be unique.

Data types Value ranges

filename_arg This is a (optionally fully qualified) file name, containing a maximum of 169
characters. Valid characters are:
v . (period; the field must not start with, end with, or contain two consecutive
periods)
v / (forward slash)
v - (hyphen)
v _ (underscore)
v a–z (lowercase letters, A through Z)
v A–Z (uppercase letters, A through Z)
v 0–9 (numerals 0 through 9)

xx SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Data types Value ranges
directory_or_file_filter Specifies a directory, file name filter, or both, within the specified directory. Valid
directory values are:
v /dumps
v /dumps/audit
v /dumps/configs
v /dumps/elogs
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/software

The file name filter can be any valid file name, containing a maximum of 128
characters, with or without the “*” (wildcard), and appended to the end of a
directory value. Valid characters are:
v * (asterisk/wildcard)
v . (the field must not start with, end with, or contain two consecutive periods)
v /
v -
v _
v a–z
v A–Z
v 0–9
filename_prefix The prefix of a file name, containing a maximum of 128 characters. Valid characters
are:
v -
v _
v a–z
v A–Z
v 0–9
name_arg Names can be specified or changed using the create and modify functions. The view
commands provide both the name and ID of an object.
Note: The system name is set when the system is created.

The first character of a name_arg must be nonnumeric. The first character of an object
name cannot be a–(dash) because the CLI (command-line interface) interprets it as
being the next parameter.

Valid characters are:

v . (period; the field must not start with, end with, or contain two consecutive
periods)
v /
v -
v _
v space
v a–z
v A–Z
v 0–9

About this guide xxi

Data types Value ranges
password This is a user-defined password containing a maximum of 15 characters. Valid
characters are:
v - (cannot be used as the first character)
v _
v a–z
v A–Z
v 0–9
serial_number The format of this number conforms to IBM standard C-S 1-1121-018 1999-06 Serial
Numbering for IBM products. The serial number is 7 digits, the first two of which
define the manufacturing location, leaving 5 digits for the product.

The standard defines a way to extend the serial number using letters in the place of
numbers in the 5-digit field.
ip_address_arg The argument follows the standard rules for dotted decimal notation.

The following Internet Protocol 4 (IPv4) and Internet Protocol 6 (IPv6) address
formats are supported:
IPv4 (no port set, SAN Volume Controller uses default)
1.2.3.4
IPv4 with specific port
1.2.3.4:22
Full IPv6, default port
1234:1234:0001:0123:1234:1234:1234:1234
Full IPv6, default port, leading zeros suppressed
1234:1234:1:123:1234:1234:1234:1234
Full IPv6 with port
[2002:914:fc12:848:209:6bff:fe8c:4ff6]:23
Zero-compressed IPv6, default port
2002::4ff6
Zero-compressed IPv6 with port
[2002::4ff6]:23
dns_name This is the dotted domain name for the system subnet (for example, ibm.com).
hostname The host name assigned to the system. This name can be different from the system
name, and is modifiable.

A combination of the host name and the dns_name is used to access the system, for
example: https://hostname.ibm.com/
capacity_value The capacity expressed within a range of 512 bytes to 2 petabytes (PB).
Tip: Specify the capacity as megabytes (MB), kilobytes (KB), gigabytes (GB), or PB.
When using MB, specify the value in multiples of 512 bytes. A capacity of 0 is valid
for a striped or sequential volume. The smallest number of supported bytes is 512.
node_id A node ID differs from other IDs in that it is a unique ID assigned when a node is
used to create a system, or when a node is added to a system. A node_id value is
never reused in a system.

Node IDs are internally represented as 64-bit numbers, and like other IDs, cannot be
modified by user commands.

xxii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Data types Value ranges
xxx_id All objects are referred to by unique integer IDs, assigned by the system when the
objects are created. All IDs are represented internally as 32-bit integers; node IDs are
an exception.

IDs in the following ranges identify the various types of objects:

v node_id: A positive decimal integer greater than or equal to 1
v mdisk_grp_id: 0–127
v io_grp_id: 0–3 (See Note.)
v mdisk_id: 0–4095
v vdisk_id: 0–8191
v copy_id: 0–1
v host_id: 0–1023
v flash_const_grp_id: 0–255
v remote_const_grp_id: 0–255
v fcmap_id: 0–4095
v rcrel_id: 0–8191
v controller_id: 0–63
Note: The io_group 4 exists but is used only in certain error recovery procedures.

These IDs, like node IDs, cannot be modified by user commands.

Note: IDs are assigned at run time by the system and cannot be relied upon to be
the same after; for example, the configuration restoration. Use object names in
preference to IDs when working with objects.
xxx_list A colon-delimited list of values of type “xxx”.
wwpn_arg The Fibre Channel worldwide port name (WWPN), expressed as a 64-bit
hexadecimal number and consisting of the characters 0–9, a–f, and A–F; for example:
1A2B30C67AFFE47B.
Note: Entering WWPN 0 in the command string causes a command failure.
panel_name This is a string of up to six characters corresponding to the number on the printed
label below the display on the front panel of a node in the system.
sequence_number A 32-bit unsigned integer, expressed in decimal format.
csi_num_arg A 32-bit unsigned integer, expressed in decimal format.
percentage_arg An 8-bit unsigned integer, expressed in decimal 0–100 format.
extent_arg A 32-bit unsigned integer, expressed in decimal format.
num_extents_arg A 32-bit unsigned integer, expressed in decimal format.
threads_arg An 8-bit unsigned integer, expressed in decimal format. Valid values are 1, 2, 3, or 4.
velocity_arg The fabric speed in gigabytes per second (GBps). Valid values are 1 or 2.
timezone_arg The ID as detailed in the output of the lstimezones command.
timeout_arg The command timeout period. An integer from 0 to 600 (seconds).
stats_time_arg The frequency at which statistics are gathered. Valid values are 1 to 60 minutes in
increments of 1 minute.

About this guide xxiii

Data types Value ranges
directory_arg Specifies a directory, file name filter, or both, within the specified directory. Valid
directory values are:
v /dumps
v /dumps/audit
v /dumps/cimom
v /dumps/configs
v /dumps/elogs
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /home/admin/upgrade

The file name filter can be any valid file name, containing a maximum of 128
characters, with or without the “*” (wildcard), and appended to the end of a
directory value. Valid characters are:
v *
v . (the field must not start with, end with, or contain two consecutive periods)
v /
v -
v _
v a–z
v A–Z
v 0–9
locale_arg The system locale setting. Valid values are:
v 0 en_US: US English (default)
v 1 zh_CN: Simplified Chinese
v 2 zh_TW: Traditional Chinese
v 3 ja_JP: Japanese
v 4 fr_FR: French
v 5 de_DE: German
v 6 it_IT: Italian
v 7 es_ES: Spanish

key_arg A user-defined identifier for a secure shell (SSH) key, containing a maximum of 30
characters.
user_arg Specifies the user: admin or service.
copy_rate A numeric value of 0–100.
copy_type Specifies the Mirror copy type: Metro or Global.

The maximum number of values entered into a colon-separated list is 128; exceeding this maximum
number returns an error.

CLI commands and parameters

CLI commands and parameters are represented in the syntax diagram.

The SAN Volume Controller command-line interface offers command line completion for command entry.
Command line completion allows you to type in the first few characters of a command and press the Tab

xxiv SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
key to fill in the rest of the command name. If there are multiple commands that start with the same
characters, then a list of possible commands is returned. You can type in more characters until the
command name is unambiguous.

CLI parameters can be entered in any order except in the following situations:
v When a command name is specified, the first argument given must be the action that you want to be
performed.
v Where you are performing an action against a specific object, the object ID or name must be the last
argument in the line.

A valid parameter meets the following requirements:

v Parameters can be entered in any order.
v If a parameter has an associated argument, the argument must always follow the parameter.
v A parameter must start with a '-'; otherwise, it is assumed to be an argument.
v The maximum length of any single parameter that can be entered into the CLI is 128 bytes.
v An argument can contain multiple data items. The maximum number of data items that you can enter
into such a list is 128. For a component list, separate the individual items by a colon.
v Any parameter with an argument can be entered as -parameter=argument.
v Entering -param= means the argument is an empty string, equivalent to -param.
v The symbol '--' is valid as the next to last entry on the command line. It specifies that the next entry is
the target object name or ID, even if it begins with a hyphen.
chuser -usergrp=-usergrp -- -password
v The symbol '--' is valid as the final word on the command line.

Examples that are valid:

mkuser -name fred -usergrp 0 -password buckets
mkuser -name fred -usergrp 0 -password=buckets
mkuser -name fred -usergrp 0 -password=buckets --
mkuser -name=-barney -usergrp=0 -password=buckets

chuser -usergrp 1 fred

chuser -usergrp 1 -- fred
chuser -usergrp 1 -- -barney

Examples that are invalid:

chuser -usergrp 1 fred --
chuser -usergrp 1 -- fred --
chuser -- -usergrp 1 fred
chuser -usergrp 1 -barney

CLI flags
The following flags are common to all command-line interface (CLI) commands.
-? or -h
Print help text. For example, issuing lscluster -h provides a list of the actions available with the
lscluster command.
-nomsg
When used, this flag prevents the display of the successfully created output. For example, if
you issue the following command:

mkmdiskgrp -ext 16

it displays:

About this guide xxv

 MDisk Group, id [6], successfully created

However, if the -nomsg parameter is added, for example:

mkmdiskgrp -ext 16 -nomsg

the following information is displayed:

This parameter can be entered for any command, but is only acted upon by those commands that
generate the successfully created outputs. All other commands ignore this parameter.

CLI messages
Ensure that you are familiar with the command-line interface (CLI) messages.

When some commands complete successfully, textual output is normally provided. However, some
commands do not provide any output. The phrase No feedback is used to indicate that no output is
provided. If the command does not complete successfully, an error is generated. For example, if the
command has failed as a result of the cluster being unstable, the following output is provided:
v CMMVC5786E The action failed because the cluster is not in a stable state.

Attributes of the -filtervalue parameters

The -filtervalue parameter filters a view that is based on specific attribute values that relate to each object
type. You can combine multiple filters to create specific searches, for example, -filtervalue
name=fred:status=online. The help (-filtervalue?) specifies the attributes that are available for each object
type.

The -filtervalue parameter must be specified with attrib=value The -filtervalue? and -filtervalue
parameters cannot be specified together.

Note: The qualifier characters left bracket (<) and right bracket (>) must be enclosed within double
quotation marks (""). For example, -filtervalue vdisk_count "<"4 or port_count ">"1. It is also valid to
include the entire expression within double quotation marks. For example,-filtervalue "vdisk_count<4"

When an attribute requires the -unit parameter, it is specified after the attribute. For example, -filtervalue
capacity=24 -unit mb. The following input options are valid for the -unit parameter:
v b (bytes)
v mb (Megabytes)
v gb (Gigabytes)
v tb (Terabytes)
v pb (Petabytes)

Capacity values displayed in units other than bytes might be rounded. When filtering on capacity, use a
unit of bytes, -unit b, for exact filtering.

Table 5 on page xxvii provides a list of valid filter attributes, as well as descriptions, qualifiers and
wildcards for each object type.

You can use the asterisk (*) character as a wildcard character when names are used. The asterisk
character can be used either at the beginning or the end of a text string, but not both. Only one asterisk
character can be used in a -filtervalue parameter.

xxvi SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 5. Valid filter attributes
Object Attribute Valid Qualifiers Wildcard Description
Valid
cluster cluster_name or name = Yes The cluster name.
cluster_unique_id or id =, <, <=, >, >= No The cluster ID.
node node_name or name = Yes The node name.
id =, <, <=, >, >= No The node ID.
status = No The status of the node. The
following values are valid for node
status:
v adding
v deleting
v online
v offline
v pending
IO_group_name = Yes The I/O group name.
IO_group_id =, <, <=, >, >= No The I/O group ID.
hardware = No The following values are valid for
hardware type: 8F2, 8F4, 8G4, CF8,
and 8A4.
io_grp HWS_name or name = Yes The I/O group name.
HWS_unique_id or id =, <, <=, >, >= No The I/O group ID.
node_count =, <, <=, >, >= No The number of nodes in the I/O
group.
host_count =, <, <=, >, >= No The number of hosts associated with
the io_grp.
controller controller_id or id =, <, <=, >, >= No The controller ID.

About this guide xxvii

Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
mdisk name = Yes The name of the MDisk.
id =, <, <=, >, >= No The ID of the MDisk.
controller_name = Yes The name of the controller the
MDisk belongs to.
status = No The status of the MDisk.

The following values are valid for

MDisk status:
v online
v degraded_ports
v degraded_paths
v offline
v excluded
mode = No The mode of the MDisk.

The following values are valid for

MDisk mode:
v unmanaged
v managed
v image
mdisk_grp_name = Yes The MDisk group name.
mdisk_grp_id =, <, <=, >, >= No The MDisk group ID.
capacity =, <, <=, >, >= No The capacity. Requires the -unit
parameter.
tier = No The tier information being reported:
v generic_hdd
v generic_ssd
mdiskgrp name = Yes The MDisk group name.
storage_pool_id or id =, <, <=, >, >= No The MDisk group ID.
mdisk_count =, <, <=, >, >= No The number of MDisks in the group.
vdisk_count =, <, <=, >, >= No The number of VDisks in the group.
status = No The status of the MDisk group. The
valid input options are online,
degraded_ports, degraded_paths,
excluded, and offline.
extent_size =, <, <=, >, >= No The extent size. (MB)
easy_tier = No Determines if Easy Tier is permitted
to manage the storage pool:
v on
v off
easy_tier_status = No Determines if automatic data
placement function on a storage pool
is activated:
v active
v inactive

xxviii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
vdisk vdisk_name or name = Yes The name of the VDisk.
vdisk_id or id =, <, <=, >, >= No The ID of the VDisk.
IO_group_name = Yes The name of the I/O group.
IO_group_id =, <, <=, >, >= No The ID of the I/O group.
status = No The status of the VDisk.

The valid input options for VDisk

status are online, degraded, and
offline.
mdisk_grp_name = Yes The MDisk group name.
mdisk_grp_id =, <, <=, >, >= No The MDisk group ID.
capacity =, <, <=, >, >= No The capacity. Requires the -unit
argument.
type = No The VDisk type. The valid value
options are seq, striped, and image.
FC_name = Yes The FlashCopy mapping name.
FC_id =, <, <=, >, >= No The FlashCopy mapping ID.
fc_map_count =, <, <=, >, >= No The number of VDisk mappings
(either source or target).
copy_count =, <, <=, >, >= No The number of VDisk mirrored
copies.
RC_name = Yes The Metro Mirror relationship name.
RC_id =, <, <=, >, >= No The Metro Mirror relationship ID.

About this guide xxix

Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
vdisk_copy primary = No Indicates that this copy is the
primary copy. The valid values are
yes and no.
status = No The status of the MDisk group. Valid
values are online, degraded, or
offline.
sync = No Indicates whether the VDisk copy is
synchronized. Valid values are true
or false.
mdisk_grp_name = Yes The name of the MDisk group.
mdisk_grp_id =, <, <=, >, >= No The ID of the MDisk group.
type = No The type of the VDisk copy. The
valid values are seq, striped, or
image.
easy_tier = No Determines if Easy Tier is permitted
to manage the storage pool:
v on
v off
easy_tier_status = No Determines if automatic data
placement function on a storage pool
is activated:
v active
v measured
v inactive
se_vdiskcopy mdisk_grp_id =, <, <=, >, >= No The ID of the MDisk group.
mdisk_grp_name = Yes The name of the MDisk group.
overallocation = No The percentage of overallocation,
which is displayed as a number.
autoexpand = No Autoexpand flags. The valid values
are on and off.
grainsize =, <, <=, >, >= No Space-efficient grain size.

The valid values are 32, 64, 128, or

256.
host host_name or name = Yes The host name.
host_id or id =, <, <=, >, >= No The host ID.
port_count =, <, <=, >, >= No The number of ports.
iogrp_count =, <, <=, >, >= No The number of I/O groups that are
associated with the host.

xxx SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
fcmap FC_mapping_name or name = Yes The FlashCopy mapping name.
FC_id or id =, <, <=, >, >= No The FlashCopy mapping ID.
source_vdisk_name = Yes The source VDisk name.
source_vdisk_id =, <, <=, >, >= No The source VDisk ID.
target_vdisk_name = Yes The target VDisk name.
target_vdisk_id =, <, <=, >, >= No The target VDisk ID.
group_name = Yes The consistency group name.
group_id =, <, <=, >, >= No The consistency group ID.
status = No The mapping status.

The following values are valid for

fcmap status:
v idle_or_copied
v preparing
v prepared
v copying
v stopped
v suspended
v stopping
v empty
copy_rate =, <, <=, >, >= No The background copy rate.
fcconsistgrp name = Yes The consistency group name.
FC_group_id or id =, <, <=, >, >= No The consistency group ID.
status = No The consistency group status. The
following values are valid for
fcconsistgrp status:
v idle_or_copied
v preparing
v prepared
v copying
v stopped
v suspended
v stopping
v empty

About this guide xxxi

Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
rcrelationship RC_rel_id or id =, <, <=, >, >= No The Metro Mirror relationship ID.
RC_rel_name or name = Yes The Metro Mirror relationship name.
master_cluster_id =, <, <=, >, >= No The master cluster ID.
master_cluster_name = Yes The master cluster name.
master_vdisk_id =, <, <=, >, >= No The master VDisk ID.
master_vdisk_name = Yes The master VDisk name.
aux_cluster_id =, <, <=, >, >= No The aux cluster ID.
aux_cluster_name = Yes The aux cluster name.
aux_vdisk_id =, <, <=, >, >= No The aux VDisk ID.
aux_vdisk_name = Yes The aux VDisk name.
primary = No The relationship primary. The
following values are valid for
primary:
v master
v aux
consistency_group_id =, <, <=, >, >= No The Metro Mirror consistency group
ID.
consistency_group_name = Yes The Metro Mirror consistency group
name.
state = Yes The relationship state. The following
values are valid for state:
v inconsistent_stopped
v inconsistent_copying
v consistent_stopped
v consistent_synchronized
v idling
v idling_disconnected
v inconsistent_disconnected
v consistent_disconnected
progress =, <, <=, >, >= No The progress of the initial
background copy (synchronization)
for the relationship.

xxxii SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
rcconsistgrp group_id or id =, <, <=, >, >= No The consistency group ID.
name = Yes The consistency group name.
master_cluster_id =, <, <=, >, >= No The master cluster ID.
master_cluster_name = Yes The master cluster name.
aux_cluster_id =, <, <=, >, >= No The aux cluster ID.
aux_cluster_name = Yes The aux cluster name.
primary = No The consistency group primary. The
following values are valid for
primary:
v master
v aux
state = No The consistency group state. The
following values are valid for state:
v inconsistent_stopped
v inconsistent_copying
v consistent_stopped
v consistent_synchronized
v idling
v idling_disconnected
v inconsistent_disconnected
v consistent_disconnected
v empty
relationship_count =, <, <=, >, >= No The relationship count.
user password = No Specifies if a password is associated
with the user. The valid values are
yes or no.
ssh_key = No Specifies if a Secure Shell (SSH)
public key is associated with the
user. The valid values are yes or no.
remote = No Specifies if the user authenticates to
the cluster using a remote
authentication service. The valid
values are yes or no.
usergrp_id =, <, <=, >, >= No The ID of the user group.
usergrp_name = Yes The name of the user group.
usergrp role = No The role associated with all users
that belong to this user group. The
valid values are Monitor,
CopyOperator, Service,
Administrator, or SecurityAdmin.
remote = No Specifies if the user group is used to
set the role of remote users. The
valid values are yes or no.

About this guide xxxiii

Table 5. Valid filter attributes (continued)
Object Attribute Valid Qualifiers Wildcard Description
Valid
clusterip port_id =, <, <=, >, >= No The port ID. The valid values are 1
or 2.
cluster_name = Yes The cluster name.
cluster_id =, <, <=, >, >= No The cluster ID.

xxxiv SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 1. Setting up an SSH client
Secure Shell (SSH) is a client-server network application. It is used as a communication vehicle between
the host system and the SAN Volume Controller command-line interface (CLI).

Overview

The SAN Volume Controller clustered system acts as the SSH server in this relationship. The SSH client
provides a secure environment in which to connect to a remote machine. Authentication is performed
using an SVC_username and password. If you require command-line access without entering a password,
it uses the principles of public and private keys for authentication.

Authenticating SSH logins

e You must generate a Secure Shell (SSH) key pair to use the SAN Volume Controller command-line
e interface (CLI). Additionally, when you use the Secure Shell (SSH) to log in to the SAN Volume
e Controller or Storwize V7000, you must use the RSA-based private key authentication.

When you are using AIX® hosts, SSH logins are authenticated on the system using the RSA-based
authentication that is supported in the OpenSSH client that is available for AIX. This scheme is based on
the supplied password (or if you require command-line access without entering a password, then
public-key cryptography is used) by using an algorithm known commonly as RSA.

Note: The authentication process for host systems that are not AIX is similar.

With this scheme (as in similar OpenSSH systems on other host types), the encryption and decryption is
done using separate keys. This means that it is not possible to derive the decryption key from the
encryption key.

Because physical possession of the private key allows access to the system, the private key must be kept
in a protected place, such as the .ssh directory on the AIX host, with restricted access permissions.

When SSH client (A) attempts to connect to SSH server (B), the SSH password (if you require
command-line access without entering a password, the key pair) authenticates the connection. The key
consists of two halves: the public keys and private keys. The SSH client public key is put onto SSH
Server (B) using some means outside of the SSH session. When SSH client (A) tries to connect, the private
key on SSH client (A) is able to authenticate with its public half on SSH server (B).

To connect to the system, the SSH client requires a user login name and an SSH password (or if you
require command-line access without entering a password, the key pair). Authenticate to the system
using a SAN Volume Controller management user name and password. When using an SSH client to
access a SAN Volume Controller system, you must use your SVC_username and password. The SAN
Volume Controller system uses the password (and if not a password, the SSH key pair) to authorize the
user accessing the system.

You can connect to the system using the same user name with which you log into SAN Volume
Controller.

For Microsoft Windows hosts, PuTTY can be downloaded from the Internet and used at no charge to
provide an SSH client.

Storwize V7000: You can connect to the system using the same user name with which you log into
Storwize V7000.

© Copyright IBM Corp. 2003, 2012 1

e For more information, see:
e v “Setting up an SSH client on a Windows host” for a description of how to prepare the SSH client on a
Windows host.
v “Preparing the SSH client on an AIX or Linux host” on page 6 for a description of how to prepare the
SSH client on an AIX or Linux host.
v “Creating and working with users using the CLI” on page 76 for a discussion of how a local or a
e remote user accesses a SAN Volume Controller system.

e Setting up an SSH client on a Windows host

e You can prepare the SSH client on a Windows host.

The IBM System Storage Productivity Center (SSPC) and the workstation for the SAN Volume Controller
include the PuTTY client program, which is a Microsoft Windows SSH client program. The PuTTY client
program can be installed on your SSPC or workstation server in one of these ways:
v If you purchased the SSPC or the workstation hardware option from IBM, the PuTTY client program
has been preinstalled on the hardware.
v You can use the workstation software installation CD to install the PuTTY client program. The SSPC,
workstation hardware option, and the software-only workstation each provide this CD.
v You can use the separate PuTTY client program-installation wizard, putty-version-installer.exe. You can
download the PuTTY client program from this website:
Download Putty (http://www.putty.org/)

Note: Before you install the PuTTY client program, ensure that your Windows system meets the system
requirements. See the IBM System Storage Productivity Center Introduction and Planning Guide for system
requirements.

If you want to use an SSH client other than the PuTTY client, this website offers SSH client alternatives
for Windows:

www.openssh.org/windows.html

You can connect to the system using the same user name with which you log into SAN Volume
Controller.

Storwize V7000: You can connect to the system using the same user name with which you log into
Storwize V7000.

Generating an SSH key pair using PuTTY

e To use the SAN Volume Controller command-line interface, you must generate a Secure Shell (SSH) key
e pair using PuTTY.

About this task

Perform the following steps to generate SSH keys using the PuTTY key generator (PuTTYgen):

Procedure
1. Start PuTTYgen by clicking Start > Programs > PuTTY > PuTTYgen. The PuTTY Key Generator
panel is displayed.
2. Click SSH-2 RSA as the type of key to generate.

Note: Leave the number of bits in a generated key value at 1024.

2 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
3. Click Generate and then move the cursor around the blank area of the Key section to generate the
random characters that create a unique key. When the key has been completely generated, the
information about the new key is displayed in the Key section.
Attention: Do not modify the Key fingerprint or the Key comment fields; this can cause your key to
no longer be valid.
4. (Optional) Enter a passphrase in the Key passphrase and Confirm passphrase fields. The passphrase
encrypts the key on the disk; therefore, it is not possible to use the key without first entering the
passphrase.
5. Save the public key by performing the following steps:
a. Click Save public key. You are prompted for the name and location of the public key.
b. Type icat.pub as the name of the public key and specify the location where you want to save the
public key. For example, you can create a directory on your computer called keys to store both the
public and private keys.
c. Click Save.
6. Save the private key by performing the following steps:
a. Click Save private key. The PuTTYgen Warning panel is displayed.
b. Click Yes to save the private key without a passphrase.
c. Type icat as the name of the private key, and specify the location where you want to save the
private key. For example, you can create a directory on your computer called keys to store both the
public and private keys. It is recommended that you save your public and private keys in the
same location.
d. Click Save.
7. Close the PuTTY Key Generator window.

Configuring a PuTTY session for the CLI

You must configure a PuTTY session using the Secure Shell (SSH) password. If you require command line
access without entering a password, use the SSH key pair that you created for the command-line
interface (CLI).

About this task

Attention: Do not run scripts that create child processes that run in the background and call SAN
Volume Controller commands. This can cause the system to lose access to data and cause data to be lost.

Perform the following steps to configure a PuTTY session for the CLI:

Procedure
1. Select Start > Programs > PuTTY > PuTTY. The PuTTY Configuration window opens.
2. Click Session in the Category navigation tree. The Basic options for your PuTTY session are
displayed.
3. Click SSH as the Protocol option.
4. Click Only on clean exit as the Close window on exit option. This ensures that connection errors are
displayed.
5. Click Connection > SSH in the Category navigation tree. The options controlling SSH connections
are displayed.
6. Click 2 as the Preferred SSH protocol version.
7. Click Connection > SSH > Auth in the Category navigation tree. The Options controller SSH
authentication are displayed.
8. Click Browse or type the fully qualified file name and location of the SSH client and password. If no
password is used, the private key in the Private key file for authentication field.

Chapter 1. Secure Shell 3

 9. Click Connection > Data in the Category navigation tree.
10. Type the user name that you want to use on the SAN Volume Controller in the Auto-login
username field.
11. Click Session in the Category navigation tree. The Basic options for your PuTTY session are
displayed.
12. In the Host Name (or IP Address) field, type the name or Internet Protocol (IP) address of one of the
SAN Volume Controller clustered system (system) IP addresses or host names.
13. Type 22 in the Port field. The SAN Volume Controller system uses the standard SSH port.
14. Type the name that you want to use to associate with this session in the Saved Sessions field. For
example, you can name the session SAN Volume Controller System 1.
15. Click Save.

Results

You have now configured a PuTTY session for the CLI.

Note: If you configured more than one IP address for the SAN Volume Controller system, repeat the
previous steps to create another saved session for the second IP address. This can then be used if the first
IP address is unavailable.

Connecting to the CLI using PuTTY

Ensure that you are familiar with how to run the PuTTY and plink utilities.

Note: Windows users can download PuTTY from the following website: Download Putty.

The Secure Shell (SSH) protocol specifies that the first access to a new host server sends a challenge to
the SSH user to accept the SSH server public key. Because this is the first time that you connect to an
SSH server, the server is not included in the SSH client list of known hosts. Therefore, there is a
fingerprint challenge, which asks if you accept the responsibility of connecting with this host. If you type
y, the host fingerprint and IP address are saved by the SSH client.

When you use PuTTY, you must also type y to accept this host fingerprint. However, the host fingerprint
and IP address are stored in the registry for the user name that is logged onto Windows.

The SSH protocol also specifies that once the SSH server public key is accepted, another challenge is
presented if the fingerprint of an SSH server changes from the one previously accepted. In this case, you
must decide if you want to accept this changed host fingerprint.

Note: The SSH server keys on the SAN Volume Controller are regenerated when a microcode load is
performed on the clustered system. As a result, a challenge is sent because the fingerprint of the SSH
server has changed.

All command-line interface (CLI) commands are run in an SSH session. You can run the commands in
one of the following modes:
v An interactive prompt mode
v A single line command mode, which is entered one time to include all parameters

Interactive mode

For interactive mode, you can use the PuTTY executable to open the SSH restricted shell.

The following is an example of the command that you can issue to start interactive mode:
C:\support utils\putty <username>@svcconsoleip

4 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
where support utils\putty is the location of your putty.exe file, svcconsoleip is the IP address of your
management GUI, and <username> is the user name that you want to use on SAN Volume Controller.

If you were to issue the lsuser command, which lists the SSH client public keys that are stored on the
SAN Volume Controller clustered system, the following output is displayed when ssh_key=yes:
IBM_2145:cluster0:superuser>lsuser
id name password ssh_key remote usergrp_id usergrp_name
0 superuser yes yes no 0 SecurityAdmin
1 smith no yes no 4 Monitor
2 jones no yes no 2 CopyOperator

You can type exit and press Enter to escape the interactive mode command.

The following is an example of the host fingerprint challenge when using plink in interactive mode:
C:\Program Files\IBM\svcconsole\cimom>plink [email protected]
The server’s host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server’s key fingerprint is:
ssh-rsa 1024 e4:c9:51:50:61:63:e9:cd:73:2a:60:6b:f0:be:25:bf
If you trust this host, enter "y" to add the key to
PuTTY’s cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
Using user name "superuser".
Authenticating with public key "imported-openssh-key"
IBM_2145:your_cluster_name:superuser>

Single line command

For single line command mode, you can type the following all on one command line:
C:\Program Files\IBM\svcconsole\cimom>
plink [email protected] lsuser
Authenticating with public key "imported-openssh-key"
id name password ssh_key remote usergrp_id usergrp_name
0 superuser yes yes no 0 SecurityAdmin
1 smith no yes no 4 Monitor
2 jones no yes no 2 CopyOperator

Note: If you are submitting a CLI command with all parameters in single line command mode, you are
challenged upon first appearance of the SSH server host fingerprint. Ensure that the SSH server host
fingerprint is accepted before you submit a batch script file.

The following is an example of the host fingerprint challenge when using plink in single line command
mode:

Chapter 1. Secure Shell 5

 C:\Program Files\IBM\svcconsole\cimom>
plink [email protected] lsuser
The server’s host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server’s key fingerprint is:
ssh-rsa 1024 e4:c9:51:50:61:63:e9:cd:73:2a:60:6b:f0:be:25:bf
If you trust this host, enter "y" to add the key to
PuTTY’s cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
Authenticating with public key "imported-openssh-key"
id name password ssh_key remote usergrp_id usergrp_name
0 superuser yes yes no 0 SecurityAdmin
1 smith no yes no 4 Monitor
2 jones no yes no 2 CopyOperator

Starting a PuTTY session for the CLI

You must start a PuTTY session to connect to the command-line interface (CLI).

Before you begin

This task assumes that you have already configured and saved a PuTTY session using the Secure Shell
(SSH) password. If you require command line access without entering a password, use the SSH key pair
that you created for the CLI: “Generating an SSH key pair using PuTTY” on page 2

About this task

Perform the following steps to start a PuTTY session:

Procedure
1. Select Start > Programs > PuTTY > PuTTY. The PuTTY Configuration window opens.
2. Select the name of your saved PuTTY session and click Load.
3. Click Open.

Note: If this is the first time that the PuTTY application is being used since you generated and
uploaded the SSH password or key pair, a PuTTY Security Alert window is displayed. Click Yes to
accept the change and trust the new key.
4. Type the SVC_username in the login as: field and press Enter.

Preparing the SSH client on an AIX or Linux host

e You can prepare the SSH client on an AIX or Linux host.

Before you begin

Ensure that you have an SSH client installed on your system:

IBM AIX operating systems
For IBM AIX 5L™ for POWER®, versions 5.1, 5.2, 5.3, and AIX version 6.1 for IBM POWER6®
architecture, you can obtain the OpenSSH client from the bonus packs, but you also must obtain
its prerequisite, OpenSSL, from the IBM AIX toolbox for Linux applications for IBM Power

6 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Systems™. For AIX 4.3.3, you can obtain the software from the AIX toolbox for Linux applications.
You can also obtain the AIX installation images from IBM developerWorks® at the following
website:

oss.software.ibm.com/developerworks/projects/openssh
Linux operating systems
The OpenSSH client is installed by default on most Linux distributions. If it is not installed on
your system, consult your Linux installation documentation or visit the following website:

www.openssh.org/portable.html

The OpenSSH client can run on a variety of additional operating systems. For more information
about the openSSH client, visit the following website:

www.openssh.org/portable.html

About this task

Authentication to the system generally requires the use of a password, but if there is no password you
can use a key pair. Perform the following steps to set up an RSA key pair on the AIX or Linux host and
the SAN Volume Controller or Storwize V7000 cluster:

Results

To authenticate using an SSH key use the following command instead:

ssh -i full_path_to_key username@my_system

Where my_system is the name of the system IP, SVC_username is the user name that you also log into the
system with, and full_path_to_key is the full path to the key file that was generated in the previous step.
Authenticate to the system using a SVC_username and password. (If you require command-line access
without using a password, SSH keys can be used.) The SAN Volume Controller software determines
which user is logging in from the key the user is using.

Note: You can omit -i full_path_to_key if you configure the SSH client to use the key file
automatically. For more information, refer to the OpenSSH documentation.

If you use the Secure Shell (SSH) to log in to the SAN Volume Controller or Storwize V7000, use the
password defined for accessing the GUI. You can also use RSA-based private key authentication.

e For more information, see “Connecting to the CLI using OpenSSH” on page 8.

Generating an SSH key pair using OpenSSH

This topic describes how to generate an SSH key pair using OpenSSH.

About this task

Perform these steps to set up an RSA key pair on the AIX or Linux host and the SAN Volume Controller
or Storwize V7000 clustered system:

Procedure
1. Create an RSA key pair by issuing a command on the host that is similar to this command:
ssh-keygen -t rsa

Chapter 1. Secure Shell 7

 Tip: Issue the command from the $HOME/.ssh directory.
This process generates two user named files. If you select the name key, the files are named key and
key.pub. Where key is the name of the private key and key.pub is the name of the public key.
2. Associate the public key with a user on the SAN Volume Controller or Storwize V7000 system. using
the management GUI.

Connecting to the CLI using OpenSSH

This topic describes how to connect to the CLI using OpenSSH.

To connect to a clustered system using an SVC_username and SSH password, issue:

ssh username@my_system

Issue:
-i full_path_to_key

to use SSH key.Where my_system is the name of the system IP, full_path_to_key is the full path to the key
file that was generated in the previous step, and SVC_username is the user name that you want to use on
SAN Volume Controller.

Note: You can omit -i full_path_to_key if you configure the SSH client to use the key file
automatically. For more information, refer to the OpenSSH documentation.

e Working with local and remote users

You can create either a local or a remote user to access a SAN Volume Controller clustered system
(system).

Before you begin

You can create two categories of users that access the system. These types are based on how the users are
authenticated to the system. Local users must provide the SVC_username and password, and if you
require command line access without entering a password, a Secure Shell (SSH) key - or both. Local users
are authenticated through the authentication methods that are located on the SAN Volume Controller
system.

If the local user needs access to management GUI, a password is needed for the user. Access to the
command-line interface (CLI) is also possible with the same password or (alternatively) a valid SSH key
can be used. An SSH password is required if a user is working with both interfaces. Local users must be
part of a user group that is defined on the system. User groups define roles that authorize the users
within that group to a specific set of operations on the system.

A remote user is authenticated on a remote service usually provided by a SAN management application,
such as IBM Tivoli® Storage Productivity Center, and does not need local authentication methods. For a
remote user, a password (preferred) is required, and if you require command line access without entering
a password an SSH key is required to use the command-line interface.

Remote users only need local credentials to access to the management GUI if the remote service is down.
Remote users have their groups defined by the remote authentication service.

e For more information on working with users for authentication, see “Creating and working with users
e using the CLI” on page 76.

Storwize V7000: You can connect to the system using the same user name with which you log into
Storwize V7000.

8 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
About this task

Complete these steps to create either a local or remote user:

Procedure
1. Select User Management > Users .
2. Click New User .
3. Enter the information on the new user and click Create.

Chapter 1. Secure Shell 9

10 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 2. Copying the SAN Volume Controller software
upgrade files using PuTTY scp
PuTTY scp (pscp) provides a file transfer application for secure shell (SSH) to copy files either between
two directories on the configuration node or between the configuration node and another host.

Before you begin

To use the pscp application, you must have the appropriate permissions on the source and destination
directories on your respective hosts.

About this task

The pscp application is available when you install an SSH client on your host system. You can access the
pscp application through a Microsoft Windows command prompt.

Perform these steps to use the pscp application:

Procedure
1. Start a PuTTY session.
2. Configure your PuTTY session to access your SAN Volume Controller clustered system (system).
3. Save your PuTTY configuration session. For example, you can name your saved session SVCPUTTY.
4. Open a command prompt.
5. Issue this command to set the path environment variable to include the PuTTY directory:
set path=C:\Program Files\putty;%path%
where Program Files is the directory where PuTTY is installed.
6. Issue this command to copy the package onto the node where the CLI runs:
pscp -load saved_putty_configuration
directory_software_upgrade_files/software_upgrade_file_name
username@cluster_ip_address:/home/admin/upgrade
where saved_putty_configuration is the name of the PuTTY configuration session,
directory_software_upgrade_files is the location of the software upgrade files, software_upgrade_file_name is the
name of the software upgrade file, username is the name that you want to use on the SAN Volume
Controller, and cluster_ip_address is an IP address of your clustered system.
If there is insufficient space to store the software upgrade file on the system, the copy process fails.
Perform these steps:
a. Use pscp to copy data that you want to preserve from the /dumps directory. For example, issue
this command to copy all event logs from the system to the IBM System Storage Productivity
Center:
pscp -unsafe -load saved_putty_configuration
username@cluster_ip_address:/dumps/elogs/*
your_preferred_directory
where saved_putty_configuration is the name of the PuTTY configuration session, username is the
name that you want to use on the SAN Volume Controller, cluster_ip_address is the IP address of
your system, and your_preferred_directory is the directory where you want to transfer the event
logs.
b. Issue the cleardumps command to free space on the system:
cleardumps -prefix /dumps
c. Then repeat step 6.

© Copyright IBM Corp. 2003, 2012 11

12 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 3. Using the CLI
The SAN Volume Controller clustered system command-line interface (CLI) is a collection of commands
that you can use to manage the SAN Volume Controller.

Overview

The CLI commands use the Secure Shell (SSH) connection between the SSH client software on the host
system and the SSH server on the SAN Volume Controller clustered system.

Before you can use the CLI, you must have already created a clustered system.

You must perform these actions to use the CLI from a client system:
v Install and set up SSH client software on each system that you plan to use to access the CLI.
v Authenticate to the system using a password.
v If you require command line access without entering a password, use an SSH public key. Then store
the SSH public key for each SSH client on the SAN Volume Controller.

Note: After the first SSH public key is stored, you can add additional SSH public keys using either the
management GUI or the CLI.

You can use the CLI to perform these functions:

v Setup of the clustered system, its nodes, and the I/O groups
v Analyze error logs (event logs)
v Setup and maintenance of managed disks (MDisk) and storage pools
v Setup and maintenance of client public SSH keys on the clustered system
v Setup and maintenance of volumes
v Setup of logical host objects
v Map volumes to hosts
v Navigate from managed hosts to volumes and to MDisks, and the reverse direction up the chain
v Set up and start Copy Services:
– FlashCopy and FlashCopy consistency groups
– Synchronous Metro Mirror and Metro Mirror consistency groups
– Asynchronous Global Mirror and Global Mirror consistency groups

Setting the clustered system time using the CLI

You can use the command-line interface (CLI) to set the clustered system time.

About this task

Perform the following steps to set the clustered system time:

Procedure
1. Issue the showtimezone CLI command to display the current time-zone settings for the clustered
system. The time zone and the associated time-zone ID are displayed.

© Copyright IBM Corp. 2003, 2012 13

2. Issue the lstimezones CLI command to list the time zones that are available on the clustered system.
A list of valid time-zone settings are displayed. Each time zone is assigned an ID. The time zone and
the associated ID are indicated in the list.
3. Issue the following CLI command to set the time zone for the clustered system.
settimezone -timezone time_zone_setting
where time_zone_setting is the new time zone ID that you have chosen from the list of time zones that
are available on the clustered system.
4. Issue the following CLI command to set the time for the clustered system:
setsystemtime -time 031809142005
where 031809142005 is the new time that you want to set for the clustered system. You must use the
MMDDHHmmYYYY format to set the time for the clustered system.

Setting cluster date and time

You can set the date and time for a SAN Volume Controller cluster from the System Date and Time
Settings panel.

Before you begin

This task assumes that you have already launched the management GUI.

About this task

You can set the System Date and time manually, or by specifying an NTP server:

Procedure
1. Click Manage Systems > Set System Time in the portfolio. The System Date and Time Settings panel
is displayed.
2. To use NTP to manage the clustered system date and time, enter an Internet Protocol Version 4 (IPv4)
address and click Set NTP Server.

Note: If you are using a remote authentication service to authenticate users to the SAN Volume
Controller clustered system, then both the system and the remote service should use the same NTP
server. Consistent time settings between the two systems ensure interactive performance of the
management GUI and correct assignments for user roles.
3. To set the clustered system date and time manually, continue with the following steps.
4. Type your changes into the Date, Month, Year, Hours and Minutes fields and select a new time zone
from the Time Zone list
5. Select Update cluster time and date, Update cluster time zone, or both.
6. Click Update to submit the update request to the clustered system.

Viewing and updating license settings using the CLI

You can use the command-line interface (CLI) to view and update your license settings.

About this task

SAN Volume Controller provides two license options: Physical Disk Licensing and Capacity Licensing.
Perform the following steps to view and update your SAN Volume Controller license settings:

14 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Procedure
1. Issue the lslicense CLI command to view the current license settings for the clustered system.
2. Issue the chlicense CLI command to change the licensed settings of the clustered system.
Attention:
v License settings are entered when the clustered system is first created; do not update the settings
unless you have changed your license.
v To select Physical Disk Licensing, run the chlicense command with one or more of the
physical_disks, physical_flash, and physical_remote parameters.
v To select Capacity Licensing, run the chlicense command with one or more of the -flash, -remote,
and -virtualization parameters. If the physical disks value is nonzero, these parameters cannot be
set.

Displaying clustered system properties using the CLI

You can use the command-line interface (CLI) to display the properties for a clustered system.

About this task

Perform the following step to display clustered system properties:

Procedure

Issue the lssystem command to display the properties for a clustered system.
The following is an example of the command you can issue:
e lssystem -delim : build1

where build1 is the name of the clustered system.

Chapter 3. Using the CLI 15

Results
id:000002007A00A0FE
name:build1
location:local
partnership:
bandwidth:
total_mdisk_capacity:90.7GB
space_in_mdisk_grps:90.7GB
space_allocated_to_vdisks:14.99GB
total_free_space:75.7GB
statistics_status:on
statistics_frequency:15
required_memory:0
cluster_locale:en_US
time_zone:522 UTC
code_level:6.1.0.0 (build 47.3.1009031000)
FC_port_speed:2Gb
console_IP:9.71.46.186:443
id_alias:000002007A00A0FE
gm_link_tolerance:300
gm_inter_cluster_delay_simulation:0
gm_intra_cluster_delay_simulation:0
email_reply:
email_contact:
email_contact_primary:
email_contact_alternate:
email_contact_location:
email_state:stopped
inventory_mail_interval:0
total_vdiskcopy_capacity:15.71GB
total_used_capacity:13.78GB
total_overallocation:17
total_vdisk_capacity:11.72GB
cluster_ntp_IP_address:
cluster_isns_IP_address:
iscsi_auth_method:none
iscsi_chap_secret:
auth_service_configured:no
auth_service_enabled:no
auth_service_url:
auth_service_user_name:
auth_service_pwd_set:no
auth_service_cert_set:no
relationship_bandwidth_limit:25
gm_max_host_delay:5
tier:generic_ssd
tier_capacity:0.00MB
tier_free_capacity:0.00MB
tier:generic_hdd
tier_capacity:90.67GB
tier_free_capacity:75.34GB
email_contact2:
email_contact2_primary:
email_contact2_alternate:
total_allocated_extent_capacity:16.12GB

Maintaining passwords for the front panel using the CLI

You can use the command-line interface (CLI) to view and change the status of the password reset
feature for the SAN Volume Controller front panel.

The clustered system (system) superuser password can be reset using the front panel of the configuration
node. To meet varying security requirements, this functionality can be enabled or disabled using the CLI.

Complete the following steps to view and change the status of the password reset feature:
1. Issue the setpwdreset CLI command to view and change the status of the password reset feature for
the SAN Volume Controller front panel.

16 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2. Record the system superuser password because you cannot access the system without it.

Storwize® V7000: The system superuser password can be reset using a USB key. To meet varying security
requirements, this functionality can be enabled or disabled using the CLI. Complete the following steps to
view and change the status of the password reset feature:
1. Issue the setpwdreset CLI command to view and change the status of the password reset feature for
the Storwize® V7000.
2. Record the system superuser password because you cannot access the system without it.

Re-adding a repaired node to a clustered system using the CLI

You can use the command-line interface (CLI) to re-add a failed node back into a clustered system after it
was repaired.

Before you begin

Before you add a node to a clustered system, you must make sure that the switchd\ zoning is configured
such that the node being added is in the same zone as all other nodes in the clustered system. If you are
replacing a node and the switch is zoned by worldwide port name (WWPN) rather than by switch port,
make sure that the switch is configured such that the node being added is in the same VSAN/zone.

Attention:
1. If you are re-adding a node to the SAN, ensure that you are adding the node to the same I/O group
from which it was removed. Failure to do this can result in data corruption. You must use the
information that was recorded when the node was originally added to the clustered system. If you do
not have access to this information, call the IBM Support Center to add the node back into the
clustered system without corrupting the data.
2. The LUNs that are presented to the ports on the new node must be the same as the LUNs that are
presented to the nodes that currently exist in the clustered system. You must ensure that the LUNs are
the same before you add the new node to the clustered system.
3. LUN masking for each LUN must be identical on all nodes in a clustered system. You must ensure
that the LUN masking for each LUN is identical before you add the new node to the clustered
system.
4. You must ensure that the model type of the new node is supported by the SAN Volume Controller
software level that is currently installed on the clustered system. If the model type is not supported
by the SAN Volume Controller software level, upgrade the clustered system to a software level that
supports the model type of the new node. See the following website for the latest supported software
levels:
www.ibm.com/storage/support/2145

About this task

Special procedures when adding a node to a clustered system

Applications on the host systems direct I/O operations to file systems or logical volumes that are
mapped by the operating system to virtual paths (vpaths), which are pseudo disk objects supported by
the Subsystem Device Driver (SDD). SDD maintains an association between a vpath and a SAN Volume
Controller volume. This association uses an identifier (UID) which is unique to the volume and is never
reused. The UID permits SDD to directly associate vpaths with volumes.

SDD operates within a protocol stack that contains disk and Fibre Channel device drivers that are used to
communicate with the SAN Volume Controller using the SCSI protocol over Fibre Channel as defined by

Chapter 3. Using the CLI 17

the ANSI FCS standard. The addressing scheme provided by these SCSI and Fibre Channel device drivers
uses a combination of a SCSI logical unit number (LUN) and the worldwide node name (WWNN) for the
Fibre Channel node and ports.

If an error occurs, the error recovery procedures (ERPs) operate at various tiers in the protocol stack.
Some of these ERPs cause I/O to be redriven using the same WWNN and LUN numbers that were
previously used.

SDD does not check the association of the volume with the vpath on every I/O operation that it
performs.

Before you add a node to the clustered system, you must check to see if any of the following conditions
are true:
v The clustered system has more than one I/O group.
v The node being added to the clustered system uses physical node hardware or a slot which has
previously been used for a node in the clustered system.
v The node being added to the clustered system uses physical node hardware or a slot which has
previously been used for a node in another clustered system and both clustered systems have visibility
to the same hosts and back-end storage.

If any of the previous conditions are true, the following special procedures apply:
v The node must be added to the same I/O group that it was previously in. You can use the
command-line interface (CLI) command lsnode or the management GUI to determine the WWN of the
clustered system nodes.
v Before you add the node back into the clustered system, you must shut down all of the hosts using the
clustered system. The node must then be added before the hosts are rebooted. If the I/O group
information is unavailable or it is inconvenient to shut down and reboot all of the hosts using the
clustered system, then do the following:
– On all of the hosts connected to the clustered system, unconfigure the Fibre Channel adapter device
driver, the disk device driver, and multipathing driver before you add the node to the clustered
system.
– Add the node to the clustered system, and then reconfigure the Fibre Channel adapter device driver,
the disk device driver, and multipathing driver.

Scenarios where the special procedures can apply

The following two scenarios describe situations where the special procedures can apply:
v Four nodes of an eight-node clustered system have been lost because of the failure of a pair of 2145
UPS or four 2145 UPS-1U. In this case, the four nodes must be added back into the clustered system
using the CLI command addnode or the management GUI.

Note: You do not need to run the addnode command on a node with a partner that is already in a
clustered system; the clustered system automatically detects an online candidate.

Note: The addnode command is a SAN Volume Controller command. For Storwize V7000, use the
addcontrolenclosure command.
v A user decides to delete four nodes from the clustered system and add them back into the clustered
system using the CLI command addnode or the management GUI.

Note: The addnode command is a SAN Volume Controller command. For Storwize V7000, use the
addcontrolenclosure command.

For 5.1.0 nodes, the SAN Volume Controller automatically re-adds nodes that have failed back to the
clustered system. If the clustered system reports an error for a node missing (error code 1195) and that

18 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
node has been repaired and restarted, the clustered system automatically re-adds the node back into the
clustered system. This process can take up to 20 minutes, so you can manually re-add the node by
completing the following steps:

Procedure
1. Issue the lsnode CLI command to list the nodes that are currently part of the clustered system and
determine the I/O group for which to add the node.
The following is an example of the output that is displayed:
lsnode -delim :

id:name:UPS_serial_number:WWNN:status:IO_group_id:IO_group_name
:config_node:UPS_unique_id:hardware:iscsi_name:iscsi_alias
:panel_name:enclosure_id:canister_id:enclosure_serial_number
1:node1::50050868010050B2:online:0:io_grp0:yes::100:iqn.1986-03.com.ibm
:2145.cluster0.node1::02-1:2:1:123ABCG
2:node2::50050869010050B2:online:0:io_grp0:no::100:iqn.1986-03.com.ibm
:2145.cluster0.node2::02-2:2:2:123ABDG

Storwize V7000 example:

lsnode -delim :

id:name:UPS_serial_number:WWNN:status:IO_group_id:IO_group_name
:config_node:UPS_unique_id:hardware:iscsi_name:iscsi_alias
:panel_name:enclosure_id:canister_id:enclosure_serial_number
1:node1::50050868010050B2:online:0:io_grp0:yes::100:iqn.1986-03.com.ibm
:2145.cluster0.node1::02-1:2:1:123ABCG
2:node2::50050869010050B2:online:0:io_grp0:no::100:iqn.1986-03.com.ibm
:2145.cluster0.node2::02-2:2:2:123ABDG

2. Issue the lsnodecandidate CLI command to list nodes that are not assigned to a clustered system and
to verify that a second node is added to an I/O group.

Note: The lsnodecandidate command is a SAN Volume Controller command. For Storwize V7000,
use the lscontrolenclosurecandidate command.
The following is an example of the output that is displayed:
lsnodecandidate -delim :

id:panel_name:UPS_serial_number:UPS_unique_id:hardware
5005076801000001:000341:10L3ASH:202378101C0D18D8:8A4
5005076801000009:000237:10L3ANF:202378101C0D1796:8A4
50050768010000F4:001245:10L3ANF:202378101C0D1796:8A4
....

3. Issue the addnode CLI command to add a node to the clustered system.

Note: The addnode command is a SAN Volume Controller command. For Storwize V7000, use the
addcontrolenclosure command.

Important: Each node in an I/O group must be attached to a different uninterruptible power supply.
The following is an example of the CLI command you can issue to add a node to the clustered system
using the panel name parameter:
addnode -panelname 000237
-iogrp io_grp0
Where 000237 is the panel name of the node, io_grp0 is the name of the I/O group that you are
adding the node to.
The following is an example of the CLI command you can issue to add a node to the clustered system
using the WWNN parameter:

Chapter 3. Using the CLI 19

 addnode -wwnodename 5005076801000001
-iogrp io_grp1
Where 5005076801000001 is the WWNN of the node, io_grp1 is the name of the I/O group that you
are adding the node to.
4. Issue the lsnode CLI command to verify the final configuration.
The following example shows output that is displayed:
lsnode -delim :

id:name:UPS_serial_number:WWNN:status:IO_group_id:IO_group_name:config_node:UPS_unique_id:
hardware:iscsi_name:iscsi_alias
1:node1:10L3ASH:0000000000000000:offline:0:io_grp0:no:1000000000003206:
8A4:iqn.1986-03.com.ibm:2145.ndihill.node1:

Record the following information for the new node:

v Node name
v Node serial number
v WWNN
v IQNs (if using hosts attached using iSCSI connections)
v All WWPNs
v I/O group that contains the node

Note: If this command is issued quickly after you have added nodes to the clustered system, the
status of the nodes might be adding. The status is shown as adding if the process of adding the nodes
to the clustered system is still in progress. You do not have to wait for the status of all the nodes to be
online before you continue with the configuration process.

Results

The nodes have been added to the clustered system.

Displaying node properties using the CLI

You can use the command-line interface (CLI) to display node properties.

About this task

Perform the following steps to display the node properties:

Procedure
1. Issue the lsnode CLI command to display a concise list of nodes in the system.
The following is an example of the CLI command you can issue to list the nodes in the system:
lsnode -delim :
The following is an example of the output that is displayed:
id:name:UPS_serial_number:WWNN:status:IO_group_id:IO_group_name:config_node:UPS_unique_id:hardware:iscsi_name:iscsi_alias:
panel_name:enclosure_id:canister_id:enclosure_serial_number
1:node1:UPS_Fake_SN:50050768010050B1:online:0:io_grp0:yes:10000000000050B1:8G4:iqn.1986-03.com.ibm:2145.cluster0.node1:000368:::

2. Issue the lsnode CLI command and specify the node ID or name of the node that you want to receive
detailed output.
The following is an example of the CLI command you can issue to list detailed output for a node in
the system:
lsnode -delim : group1node1

20 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Where group1node1 is the name of the node for which you want to view detailed output.
The following is an example of the output that is displayed:
id:1
name:group1node1
UPS_serial_number:10L3ASH
WWNN:500507680100002C
status:online
IO_group_id:0
IO_group_name:io_grp0
partner_node_id:2
partner_node_name:group1node2
config_node:yes
UPS_unique_id:202378101C0D18D8
port_id:500507680110002C
port_status:active
port_speed:2GB
port_id:500507680120002C
port_status:active
port_speed:2GB
port_id:500507680130002C
port_status:active
port_speed:2GB
port_id:500507680140003C
port_status:active
port_speed:2GB
hardware:8A4
iscsi_name:iqn.1986-03.com.ibm:2145.ndihill.node2
iscsi_alias
failover_active:no
failover_name:node1
failover_iscsi_name:iqn.1986-03.com.ibm:2145.ndihill.node1
failover_iscsi_alias

Discovering MDisks using the CLI

You can use the command-line interface (CLI) to discover managed disks (MDisks).

About this task

The clustered system (system) automatically discovers the back-end controller and integrates the
controller to determine the storage that is presented to the SAN Volume Controller nodes when back-end
controllers are:
v Added to the Fibre Channel
v Included in the same switch zone as a SAN Volume Controller system
The Small Computer System Interface (SCSI) logical units (LUs) that are presented by the back-end
controller are displayed as unmanaged MDisks. However, if the configuration of the back-end controller
is modified after this has occurred, the SAN Volume Controller system might be unaware of these
configuration changes. You can request that the SAN Volume Controller system rescans the Fibre Channel
SAN to update the list of unmanaged MDisks.

Note: The automatic discovery that is performed by SAN Volume Controller system does not write
anything to an unmanaged MDisk. You must instruct the SAN Volume Controller system to add an
MDisk to a storage pool or use an MDisk to create an image mode volume.

Perform these steps to discover and then view a list of MDisks:

Procedure
1. Issue the detectmdisk CLI command to manually scan the Fibre Channel network. The scan discovers
any new MDisks that might have been added to the system and rebalances MDisk access across the
available controller device ports.

Chapter 3. Using the CLI 21

 Notes:
a. Only issue the detectmdisk command when you are sure that all of the disk controller ports are
working and correctly configured in the controller and the SAN zoning. Failure to do this can
result in errors that are not reported.
b. Although it might appear that the detectmdisk command has completed, extra time might be
required for it to run. The detectmdisk is asynchronous and returns a prompt while the command
continues to run in the background. You can use the lsdiscoverystatus command to view the
discovery status.
2. When the detection is complete, issue the lsmdiskcandidate CLI command to show the unmanaged
MDisks. These MDisks have not been assigned to a storage pool.
3. Issue the lsmdisk CLI command to view all of the MDisks.

Results

You have now seen that the back-end controllers and switches have been set up correctly and that the
SAN Volume Controller system recognizes the storage that is presented by the back-end controller.

Example

This example describes a scenario where a single back-end controller is presenting eight SCSI LUs to the
SAN Volume Controller system:
1. Issue detectmdisk.
2. Issue lsmdiskcandidate.
This output is displayed:
id
0
1
2
3
4
5
6
7

3. Issue lsmdisk -delim :

This output is displayed:
lsmdisk -delim :
id:name:status:mode:mdisk_grp_id:mdisk_grp_name:capacity:ctrl_LUN_#:controller_name:UID:tier
0:mdisk0:online:unmanaged:::68.4GB:0000000000000000:controller0:
20000004cf2422aa000000000000000000000000000000000000000000000000:
1:mdisk1:online:unmanaged:::68.4GB:0000000000000000:controller1:
20000004cf1fd19d000000000000000000000000000000000000000000000000:
2:mdisk2:online:unmanaged:::68.4GB:0000000000000000:controller2:
20000004cf242531000000000000000000000000000000000000000000000000:

Creating storage pools using the CLI

You can use the command-line interface (CLI) to create a storage pool.

Before you begin

Attention: If you add an MDisk to a storage pool as an MDisk, any data on the MDisk is lost. If you
want to keep the data on an MDisk (for example, because you want to import storage that was
previously not managed by SAN Volume Controller), you must create image mode volumes instead.

22 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Assume that the clustered system has been set up and that a back-end controller has been configured to
present new storage to the SAN Volume Controller.

If you are using a SAN Volume Controller solid-state drive (SSD) managed disk, ensure that you are
familiar with the SSD configuration rules.

If you intend to keep the volume allocation within one storage system, ensure that all MDisks in the
storage pool are presented by the same storage system.

Ensure that all MDisks that are allocated to a single storage pool are of the same RAID type. If the
storage pool has more than one tier of storage, ensure that all MDisks in the same tier are of the same
RAID type. When using Easy Tier®, all of the MDisks in a storage pool in the same tier should be similar
and have similar performance characteristics. If you do not use Easy Tier, the storage pool should contain
only one tier of storage, and all of the MDisks in the storage pool should be similar and have similar
performance characteristics.

Consider the following factors as you decide how many (storage pools) to create:
v A volume can only be created using the storage from one storage pool. Therefore, if you create small
(storage pools), you might lose the benefits that are provided by virtualization, namely more efficient
management of free space and a more evenly distributed workload for better performance.
v If any MDisk in an storage pool goes offline, all the (volumes) in the storage pool go offline. Therefore
you might want to consider using different (storage pools) for different back-end controllers or for
different applications.
v If you anticipate regularly adding and removing back-end controllers or storage, this task is made
simpler by grouping all the MDisks that are presented by a back-end controller into one storage pool.
v All the MDisks in a storage pool should have similar levels of performance or reliability, or both. If a
storage pool contains MDisks with different levels of performance, the performance of the (volumes) in
this group is limited by the performance of the slowest MDisk. If a storage pool contains MDisks with
different levels of reliability, the reliability of the (volumes) in this group is that of the least reliable
MDisk in the group.

Note: When you create a storage pool with a new solid-state drive (SSD), the new SSD is automatically
formatted and set to a block size of 512 bytes.

About this task

Even with the best planning, circumstances can change and you must reconfigure your (storage pools)
after they have been created. The data migration facilities that are provided by the SAN Volume
Controller enable you to move data without disrupting I/O.

Choosing a storage pool extent size

Consider the following factors as you decide the extent size of each new storage pool:
v You must specify the extent size when you create a new storage pool.
v You cannot change the extent size later; it must remain constant throughout the lifetime of the storage
pool.
v Storage pools can have different extent sizes; however, this places restrictions on the use of data
migration.
v The choice of extent size affects the maximum size of a volume in the storage pool.

Table 6 on page 24 compares the maximum volume capacity for each extent size. The maximum is
different for thin-provisioned volumes. Because the SAN Volume Controller allocates a whole number of
extents to each volume that is created, using a larger extent size might increase the amount of storage

Chapter 3. Using the CLI 23

that is wasted at the end of each volume. Larger extent sizes also reduces the ability of the SAN Volume
Controller to distribute sequential I/O workloads across many MDisks and therefore can reduce the
performance benefits of virtualization.
Table 6. Maximum volume capacity by extent size
Maximum volume capacity in GB (not Maximum volume capacity in GB
Extent size (MB) thin-provisioned volumes) (thin-provisioned volumes)
16 2048 (2 TB) 2000
32 4096 (4 TB) 4000
64 8192 (8 TB) 8000
128 16,384 (16 TB) 16,000
256 32,768 (32 TB) 32,000
512 65,536 (64 TB) 65,000
1024 131,072 (128 TB) 130,000
2048 262,144 (256 TB) 260,000
4096 262,144 (256 TB) 262,144
8192 262,144 (256 TB) 262,144

Important: You can specify different extent sizes for different (storage pools); however, you cannot
migrate (volumes) between (storage pools) with different extent sizes. If possible, create all your (storage
pools) with the same extent size.

Perform the following steps to create a storage pool:

Procedure

Issue the mkmdiskgrp CLI command to create a storage pool.

The following is an example of the CLI command you can issue to create a storage pool:
mkmdiskgrp -name maindiskgroup -ext 32
-mdisk mdsk0:mdsk1:mdsk2:mdsk3

where maindiskgroup is the name of the storage pool that you want to create, 32 MB is the size of the
extent you want to use, and mdsk0, mdsk1, mdsk2, mdsk3 are the names of the four MDisks that you want
to add to the group.

Results

You created and added MDisks to a storage pool.

Example

The following example provides a scenario where you want to create a storage pool, but you do not have
any MDisks available to add to the group. You plan to add the MDisks at a later time. You use the
mkmdiskgrp CLI command to create the storage pool bkpmdiskgroup and later used the addmdisk CLI
command to add mdsk4, mdsk5, mdsk6, mdsk7 to the storage pool.
1. Issue mkmdiskgrp -name bkpmdiskgroup -ext 32
where bkpmdiskgroup is the name of the storage pool that you want to create and 32 MB is the size of
the extent that you want to use.
2. You find four MDisks that you want to add to the storage pool.
3. Issue addmdisk -mdisk mdsk4:mdsk5:mdsk6:mdsk7 bkpdiskgroup

24 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 where mdsk4, mdsk5, mdsk6, mdsk7 are the names of the MDisks that you want to add to the storage
pool and bkpdiskgroup is the name of the storage pool for which you want to add MDisks.

Adding MDisks to storage pools using the CLI

You can use the command-line interface (CLI) to add managed disks (MDisks) to storage pools.

Before you begin

The MDisks must be in unmanaged mode. Disks that already belong to a storage pool cannot be added
to another storage pool until they have been deleted from their current storage pool. An MDisk can be
deleted from a storage pool under these circumstances:
v If the MDisk does not contain any extents in use by a virtual disk volume
v If you can first migrate the extents in use onto other free extents within the group

About this task

Important: Do not add an MDisk using this procedure if you are mapping the MDisk to an image mode
volume. Adding an MDisk to a storage pool enables the SAN Volume Controller to write new data to the
MDisk; therefore, any existing data on the MDisk is lost. If you want to create an image mode volume,
use the mkvdisk command instead of addmdisk.

If you are using a SAN Volume Controller solid-state drive (SSD) managed disk, ensure that you are
familiar with the SSD configuration rules.

The SAN Volume Controller performs tests on the MDisks in the list before the MDisks are allowed to
become part of a storage pool when:
v Adding MDisks to a storage pool using the addmdisk command
v Creating a storage pool using the mkmdiskgrp -mdisk command

These tests include checks of the MDisk identity, capacity, status and the ability to perform both read and
write operations. If these tests fail or exceed the time allowed, the MDisks are not added to the group.
However, with the mkmdiskgrp -mdisk command, the storage pool is still created even if the tests fail, but
it does not contain any MDisks. If tests fail, confirm that the MDisks are in the correct state and that they
have been correctly discovered.

These events contribute to an MDisk test failure:

v The MDisk is not visible to all SAN Volume Controller nodes in the clustered system.
v The MDisk identity has changed from a previous discovery operation.
v The MDisk cannot perform read or write operations.
v The status of the MDisk can be either degraded paths, degraded ports, excluded, or offline.
v The MDisk does not exist.

These events contribute to an MDisk test timeout:

v The disk controller system on which the MDisk resides is failing.
v A SAN fabric or cable fault condition exists that is preventing reliable communication with the MDisk.

Note: The first time that you add a new solid-state drive (SSD) to a storage pool, the SSD is
automatically formatted and set to a block size of 512 bytes.

Perform these steps to add MDisks to storage pools:

Chapter 3. Using the CLI 25

Procedure
1. Issue the lsmdiskgrp CLI command to list the existing storage pools.
This example is a CLI command that you can issue to list the existing storage pools:
lsmdiskgrp -delim :
This is an example of the output that is displayed:
id:name:status:mdisk_count:vdisk_count:
capacity:extent_size:free_capacity:virtual_capacity:
used_capacity:real_capacity:overallocation:warning
0:mdiskgrp0:online:3:4:33.3GB:16:32.8GB:64.00MB:64.00MB:64.00MB:0:0
1:mdiskgrp1:online:2:1:26.5GB:16:26.2GB:16.00MB:16.00MB:16.00MB:0:0
2:mdiskgrp2:online:2:0:33.4GB:16:33.4GB:0.00MB:0.00MB:0.00MB:0:0

2. Issue the addmdisk CLI command to add MDisks to the storage pool.
This is an example of the CLI command you can issue to add MDisks to a storage pool:
addmdisk -mdisk mdisk4:mdisk5:mdisk6:mdisk7 bkpmdiskgroup
Where mdisk4:mdisk5:mdisk6:mdisk7 are the names of the MDisks that you want to add to the storage
pool and bkpmdiskgroup is the name of the storage pool for which you want to add the MDisks.

Setting a quorum disk using the CLI

You can set an external managed disk (MDisk) as a quorum disk by using the command-line interface
(CLI).

Note: Quorum functionality is not supported for internal drives on SAN Volume Controller nodes.

To set an MDisk as a quorum disk, use the chquorum command. Storwize V7000: To set an external
MDisk as a quorum disk, use the chquorum command.

When setting an MDisk as a quorum disk, keep the following recommendations in mind:
v When possible, distribute the quorum candidate disks so that each MDisk is provided by a different
storage system. For a list of storage systems that support quorum disks, refer to http://www.ibm.com/
support/docview.wss?uid=ssg1S1003703 ( http://www.ibm.com/support/
docview.wss?uid=ssg1S1003703).
v Before you set the quorum disk with the chquorum command, use the lsquorum command to ensure
that the MDisk you want is online.

Storwize V7000: Quorum disk configuration describes how quorum disks are used by the system, and how
they are selected. The system automatically assigns quorum disks. Do not override the quorum disk
assignment if you have a Storwize V7000 without external MDisks. For a Storwize V7000 with more than
one control enclosure and with external MDisks, distribute the quorum candidate disks (when possible)
so that each MDisk is provided by a different storage system. For a list of storage systems that support
quorum disks, refer to http://www.ibm.com/support/docview.wss?uid=ssg1S1003703 (
http://www.ibm.com/support/docview.wss?uid=ssg1S1003703).

Modifying the amount of available memory for Copy Services and

Volume Mirroring features using the CLI
You can use the command-line interface (CLI) to modify the amount of memory that is available for the
VDisk (Volume) Mirroring feature and the FlashCopy, Metro Mirror, or Global Mirror Copy Services
features.

26 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
About this task

Table 7 provides an example of the amount of memory that is required for Volume Mirroring and each
Copy Service feature.
Table 7. Memory required for Volume Mirroring and Copy Services
1 MB of memory provides the following volume
Feature Grain size capacity for the specified I/O group
Metro Mirror or Global Mirror 256 KB 2 TB of total Metro Mirror and Global Mirror volume
capacity
FlashCopy 256 KB 2 TB of total FlashCopy source volume capacity
FlashCopy 64 KB 512 GB of total FlashCopy source volume capacity
Incremental FlashCopy 256 KB 1 TB of total incremental FlashCopy source volume
capacity
Incremental FlashCopy 64 KB 256 GB of total incremental FlashCopy source volume
capacity
Volume Mirroring 256 KB 2 TB of mirrored volume capacity
Notes:
1. For multiple FlashCopy targets, you must consider the number of mappings. For example, for a mapping with a
grain size of 256 KB, 8 KB of memory allows one mapping between a 16 GB source volume and a 16 GB target
volume. Alternatively, for a mapping with a 256 KB grain size, 8 KB of memory allows two mappings between
one 8 GB source volume and two 8 GB target volumes.
2. When creating a FlashCopy mapping, if you specify an I/O group other than the I/O group of the source
volume, the memory accounting goes towards the specified I/O group, not towards the I/O group of the source
volume.
3. For Volume Mirroring, the full 512 MB of memory space provides 1 PB of total mirroring capacity.
4. In this table, capacity refers to the virtual capacity of the volume. For thin-provisioned volumes with different
virtual capacities and real capacities, the virtual capacity is used for memory accounting.

Table 8 provides an example of RAID level comparisons with their bitmap memory cost, where MS is the
size of the member drives and MC is the number of member drives.
Table 8. RAID level comparisons
Approximate bitmap memory
Level Member count Approximate capacity Redundancy cost
RAID-0 1-8 MC * MS None (1 MB per 2 TB of MS) * MC
RAID-1 2 MS 1 (1 MB per 2 TB of MS) *
(MC/2)
RAID-5 3-16 (MC-1) * MS 1 1 MB per 2 TB of MS with a
strip size of 256 KB; double
RAID-6 5-16 less than (MC-2 * MS) 2
with strip size of 128 KB.
RAID-10 2-16 (evens) MC/2 * MS 1 (1 MB per 2 TB of MS) *
(MC/2)
Note: There is a margin of error on the approximate bitmap memory cost of approximately 15%. For example, the
cost for a 256 KB RAID-5 is ~1.15 MB for the first 2 TB of MS.

To modify and verify the amount of memory that is available, perform the following steps:

Chapter 3. Using the CLI 27

Procedure
1. Issue the following command to modify the amount of memory that is available for Volume Mirroring
or a Copy Service feature:
chiogrp -feature flash|remote|mirror -size memory_size io_group_id | io_group_name
where flash|remote|mirror is the feature that you want to modify, memory_size is the amount of
memory that you want to be available, and io_group_id | io_group_name is the ID or name of the I/O
group for which you want to modify the amount of available memory.
2. Issue the following command to verify that the amount of memory has been modified:
lsiogrp object_id | object_name
where object_id | object_name is the ID or name of the I/O group for which you have modified the
amount of available memory.
The following information is an example of the output that is displayed.
id 0
name io_grp 0
node_count 2
vdisk_count 28
host_count 2
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 20.0MB
mirroring_total_memory 10.0MB
mirroring_free_memory 10.0MB
raid_total_memory 20.0MB
raid_free_memory 19.2MB
maintenance no <---

Creating volumes using the CLI

You can use the command-line interface (CLI) to create a volume.

Before you begin

If the volume that you are creating maps to a solid-state drive (SSD), the data that is stored on the
volume is not protected against SSD failures or node failures. To avoid data loss, add a volume copy that
maps to an SSD on another node.

This task assumes that the clustered system has been set up and that you have created storage pools. You
can establish an empty storage pool to hold the MDisks that are used for image mode volumes.

About this task

Note: If you want to keep the data on an MDisk, create image mode (volumes). This task describes how
to create a volume with striped virtualization.

Perform the following steps to create volumes:

Procedure
1. Issue the lsmdiskgrp CLI command to list the available storage pools and the amount of free storage
in each group.
The following is an example of the CLI command you can issue to list storage pools:
lsmdiskgrp -delim :
The following is an example of the output that is displayed:

28 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 id:name:status:mdisk_count:vdisk_count:capacity:extent_size:free_capacity:virtual_capacity:
used_capacity:real_capacity:overallocation:warning:easy_tier:easy_tier_status
0:mdiskgrp0:degraded:4:0:34.2GB:16:34.2GB:0:0:0:0:0:auto:inactive
1:mdiskgrp1:online:4:6:200GB:16:100GB:400GB:75GB:100GB:200:80:on:active

2. Decide which storage pool you want to provide the storage for the volume.
3. Issue the lsiogrp CLI command to show the I/O groups and the number of volumes assigned to each
I/O group.

Note: It is normal for clustered systems with more than one I/O group to have storage pools that
have volumes in different I/O groups. You can use FlashCopy to make copies of volumes regardless
of whether the source and target volume are in the same I/O group. If you plan to use intra-clustered
system Metro Mirror or Global Mirror, both the master and auxiliary volume must be in the same I/O
group.
The following is an example of the CLI command you can issue to list I/O groups:
lsiogrp -delim :
The following is an example of the output that is displayed:
id:name:node_count:vdisk_count:host_count
0:io_grp0:2:0:2
1:io_grp1:2:0:1
2:io_grp2:0:0:0
3:io_grp3:0:0:0
4:recovery_io_grp:0:0:0

4. Decide which I/O group you want to assign the volume to. This determines which SAN Volume
Controller nodes in the clustered system process the I/O requests from the host systems. If you have
more than one I/O group, make sure you distribute the volumes between the I/O groups so that the
I/O workload is shared evenly between all SAN Volume Controller nodes.
5. Issue the mkvdisk CLI command to create a volume.
The rate at which the volume copies will resynchronize after loss of synchronization can be specified
using the syncrate parameter. The following table defines the rates:
Table 9. Volume copy resynchronization rates
Syncrate value Data copied per second
1-10 128 KB
11-20 256 KB
21-30 512 KB
31-40 1 MB
41-50 2 MB
51-60 4 MB
61-70 8 MB
71-80 16 MB
81-90 32 MB
91-100 64 MB

The default setting is 50. The synchronization rate must be set such that the volume copies will
resynchronize quickly after loss of synchronization.
e The following is an example of the CLI command that you can issue to create a volume with two
e copies using the I/O group and storage pool name and specifying the synchronization rate:
e mkvdisk -iogrp io_grp1 -mdiskgrp grpa:grpb -size500 -vtype striped
e -copies 2 –syncrate 90

Chapter 3. Using the CLI 29

 where io_grp1 is the name of the I/O group that you want the volume to use, grpa is the name of the
storage pool for the primary copy of the volume and grpb is the name of the storage pool for the
second copy of the volume, and 2 is the number of volume copies and the synchronization rate is 90
which is equivalent to 32MB per second.
The following is an example of the CLI command you can issue to create a volume using the I/O
group ID and storage pool ID:
mkvdisk -name mainvdisk1 -iogrp 0
-mdiskgrp 0 -vtype striped -size 256 -unit gb
where mainvdisk1 is the name that you want to call the volume, 0 is the ID of the I/O group that want
the volume to use, 0 is the ID of the storage pool that you want the volume to use, and 256 is the
capacity of the volume.
The following is an example of the CLI command that you can issue to create a volume using the I/O
group and storage pool name:
mkvdisk -name bkpvdisk1 -iogrp io_grp1
-mdiskgrp bkpmdiskgroup -vtype striped -size 256 -unit gb
where bkpvdisk1 is the name that you want to call the volume, io_grp1 is the name of the I/O group
that want the volume to use, bkpmdiskgroup is the name of the storage pool that you want the volume
to use, and 256 is the capacity of the volume.
The following is an example of the CLI command that you can issue to create a space-efficient volume
using the I/O group and storage pool name:
mkvdisk -iogrp io_grp1 -mdiskgrp bkpmdiskgroup -vtype striped
-size 10 unit gb -rsize 20% -autoexpand -grainsize 32
where io_grp1 is the name of the I/O group that you want the volume to use and 20% is how much
real storage to allocate to the volume, as a proportion of its virtual size. In this example, the size is 10
GB so that 2 GB will be allocated.
The following is an example of the CLI command that you can issue to create a volume with two
copies using the I/O group and storage pool name:
mkvdisk -iogrp io_grp1 -mdiskgrp grpa:grpb
-size 500 -vtype striped -copies 2
where io_grp1 is the name of the I/O group that you want the volume to use, grpa is the name of the
storage pool for the primary copy of the volume and grpb is the name of the storage pool for the
second copy of the volume, and 2 is the number of volume copies.

Note: If you want to create two volume copies of different types, create the first copy using the
mkvdisk command and then add the second copy using the addvdiskcopy command.
6. Issue the lsvdisk CLI command to list all the volumes that have been created.

Adding a copy to a volume using the CLI

You can use the command-line interface (CLI) to add a mirrored copy to a volume. Each volume can
have a maximum of two copies.

Before you begin

The addvdiskcopy command adds a copy to an existing volume, which changes a nonmirrored volume
into a mirrored volume.

Creating mirrored copies of a volume allows the volume to remain accessible even when a managed disk
(MDisk) that the volume depends on becomes unavailable. You can create copies of a volume either from
different storage pools or by creating an image mode copy of the volume. Copies allow for availability of
data; however, they are not separate objects. You can only create or change mirrored copies from the
volume.

30 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
In addition, you can use volume mirroring as an alternative method of migrating volumes between
storage pools. For example, if you have a nonmirrored volume in one storage pool and want to migrate
that volume to a second storage pool, you can add a new copy of the volume by specifying the second
storage pool for that volume copy. After the copies have synchronized, you can delete the copy in the
first storage pool. The volume is migrated to the second storage pool while remaining online during the
migration.

This alternative method of migrating volumes has the following advantages:

v Access to the volume data is not lost if the second storage pool goes offline during the migration.
v The speed of the migration can be adjusted, using the volume synchronization rate, and the migration
can be paused.
v The migration can be ended by deleting the volume copy in the second storage pool before migration
completes.
v The storage pools can have different extent sizes.

This alternative method has the following limitations:

v You cannot use this method for volumes that are already mirrored.
v There are more manual steps that are associated with this method.
v Write I/O performance is slightly affected during the migration, because the mirrored copies must be
kept synchronized.

Use the -copies parameter to specify the number of copies to add to the volume; this is currently limited
to the default value of 1 copy. Use the -mdiskgrp parameter to specify the managed disk group that will
provide storage for the copy; the lsmdiskgrp CLI command lists the available managed disk groups and
the amount of available storage in each group.

For image copies, you must specify the virtualization type using the -vtype parameter and an MDisk that
is in unmanaged mode using the -mdisk parameter. This MDisk must be in the unmanaged mode. The
-vtype parameter is optional for sequential (seq) and striped volumes. The default virtualization type is
striped.

Use the syncrate parameter to specify the rate at which the volume copies will resynchronize after loss of
synchronization. The topic that describes creating volumes using the CLI describes this parameter.

About this task

Issue the addvdiskcopy CLI command to add a mirrored copy to a volume:

addvdiskcopy -mdiskgrp 0 vdisk8

where 0 is the name of the managed disk group and vdisk8 is the volume to which the copy will be
added.

The command returns the IDs of the newly created volume copies.

Deleting a copy from a volume using the CLI

You can use the command-line interface (CLI) to delete a mirrored copy from a volume.

Before you begin

If you are using solid-state drives (SSDs) that are inside a SAN Volume Controller node, always use
volume mirroring with these SSDs. Data stored on SSDs inside SAN Volume Controller nodes is not
protected against SSD failures or node failures. Therefore, if you are deleting a volume copy that uses a
SSD, ensure that the data that is stored on the copy is protected with another volume copy.

Chapter 3. Using the CLI 31

The rmvdiskcopy CLI command deletes the specified copy from the specified volume. The command fails
if all other copies of the volume are not synchronized; in this case, you must specify the -force
parameter, delete the volume, or wait until the copies are synchronized. You must specify the
vdisk_name|vdisk_id parameter last on the command line.

About this task

Issue the rmvdiskcopy CLI command to delete a mirrored copy from a volume:
rmvdiskcopy -copy 1 vdisk8

where 1 is the ID of the copy to delete and vdisk8 is the virtual disk to delete the copy from.

The command does not return any output.

Configuring host objects using the CLI

You can use the command-line interface (CLI) to create host objects.

Before you begin

If you are configuring a host object on a Fibre Channel attached host, ensure that you have completed all
zone and switch configuration. Also test the configuration to ensure that zoning was created correctly.

If you are configuring a host object on the cluster that uses iSCSI connections, ensure that you have
completed the necessary host-system configurations and have configured the cluster for iSCSI
connections.

At least one WWPN or iSCSI name must be specified.

About this task

Perform the following steps to create host objects:

Procedure
1. Issue the mkhost CLI command to create a logical host object for a Fibre Channel attached host.
Assign your worldwide port name (WWPN) for the host bus adapters (HBAs) in the hosts.

The following is an example of the CLI command that you can issue to create a Fibre Channel attached host:
mkhost -name new_name -hbawwpn wwpn_list

where new_name is the name of the host and wwpn_list is the WWPN of the HBA.

Note: For more information about worldwide port names: “Determining the WWPNs of a node using the CLI” on
page 46.

2. To create an iSCSI-attached host, issue the following CLI command:

mkhost -iscsiname iscsi_name_list

where iscsi_name_list specifies one or more iSCSI qualified names (IQNs) of this host. Up to 16 names can be
specified, provided that the command-line limit is not reached. Each name should comply with the iSCSI standard,
RFD 3720.

3. To add ports to a Fibre Channel attached host, issue the addhostport CLI command.

32 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
For example, issue the following CLI command:
addhostport -hbawwpn wwpn_list new_name

This command adds another HBA WWPN wwpn_list to the host that was created in step 1 on page 32.

4. To add ports to an iSCSI-attached host, issue the addhostport CLI command.

For example, issue the following CLI command:

addhostport -iscsiname iscsi_name_list new_name

where iscsi_name_list specifies the comma-separated list of IQNs to add to the host. This command adds an IQN to
the host that was created in step 2 on page 32.

5. To set the Challenge Handshake Authentication Protocol (CHAP) secret that is used to authenticate
the host for iSCSI I/O, issue the chhost CLI command. This secret is shared between the host and the
cluster. For example, issue the following CLI command:
chhost -chapsecret chap_secret

where chap_secret is the CHAP secret that is used to authenticate the host for iSCSI I/O. To list the
CHAP secret for each host, use the lsiscsiauth command. To clear any previously set CHAP secret
for a host, use the chhost -nochapsecret command.

What to do next

After you have created the host object on the cluster, you can map volumes to a host.

If you are unable to discover the disk on the host system or if there are fewer paths available for each
disk than expected, test the connectivity between your host system and the cluster. Depending on the
connection type to the host, these steps might be different. For iSCSI-attached hosts, test your
connectivity between the host and SAN Volume Controller ports by pinging SAN Volume Controller from
the host. Ensure that the firewall and router settings are configured correctly and validate that the values
for the subnet mask and gateway are specified correctly for the SAN Volume Controller host
configuration.

For Fibre Channel attached hosts, ensure that the active switch configuration includes the host zone and
check the host-port link status. To verify end-to-end connectivity, you can use the lsfabric CLI command
or the View Fabric panel under Service and Maintenance container in the management GUI.

Creating host mappings using the CLI

You can use the command-line interface (CLI) to create volume-to-host mappings (host mappings).

About this task

To create host mappings, follow these steps:

Procedure
1. Issue the mkvdiskhostmap CLI command to create host mappings.
This example is a CLI command you can issue to create host mappings:
mkvdiskhostmap -host demohost1 mainvdisk1
Where demohost1 is the name of the host and mainvdisk1 is the name of the volume.
2. After you have mapped volumes to hosts, discover the disks on the host system. This step requires
that you access the host system and use the host-system utilities to discover the new disks that are

Chapter 3. Using the CLI 33

 made available by the SAN Volume Controller. You also have the option of creating a file system for
those new disks. Consult your host-system documentation for more information on completing this
task.

Creating FlashCopy mappings using the CLI

You can use the command-line interface (CLI) to create FlashCopy mappings.

Before you begin

A FlashCopy mapping specifies the source and target virtual disk (VDisk) (volume). Source VDisks
(volumes) and target VDisks (volumes) must meet the following requirements:
v They must be the same size
v They must be managed by the same clustered system

About this task

A VDisk (volume) can be the source in up to 256 mappings. A mapping is started at the point in time
when the copy is required.

Perform the following steps to create FlashCopy mappings:

Procedure
1. The source and target VDisk (volume) must be the exact same size. Issue the lsvdisk -bytes CLI
command to find the size (capacity) of the VDisk (volume) in bytes.
2. Issue the mkfcmap CLI command to create a FlashCopy mapping.
The following CLI command example creates a FlashCopy mapping and sets the copy rate:
mkfcmap -source mainvdisk1 -target bkpvdisk1
-name main1copy -copyrate 75
Where mainvdisk1 is the name of the source VDisk (volume), bkpvdisk1 is the name of the VDisk
(volume) that you want to make the target VDisk (volume), main1copy is the name that you want to
call the FlashCopy mapping, and 75 is the copy rate.
The following is an example of the CLI command you can issue to create FlashCopy mappings
without the copy rate parameter:
mkfcmap -source mainvdisk2 -target bkpvdisk2
-name main2copy
Where mainvdisk2 is the name of the source VDisk (volume), bkpvdisk2 is the name of the VDisk
(volume) that you want to make the target VDisk (volume), main2copy is the name that you want to
call the FlashCopy mapping.

Note: The default copy rate of 50 is used if you do not specify a copy rate.
If the specified source and target VDisks (volume) are also the target and source VDisks (volumes) of
an existing mapping, the mapping that is being created and the existing mapping become partners. If
one mapping is created as incremental, its partner is automatically incremental. A mapping can have
only one partner.
3. Issue the lsfcmap CLI command to check the attributes of the FlashCopy mappings that have been
created:
The following is an example of a CLI command that you can issue to view the attributes of the
FlashCopy mappings:
lsfcmap -delim :
Where -delim specifies the delimiter. The following is an example of the output that is displayed:

34 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 id:name:source_vdisk_id:source_vdisk_name:target_vdisk_id:target_vdisk_name:
group_id:group_name:status:progress:copy_rate:clean_progress:incremental
0:main1copy:77:vdisk77:78:vdisk78:::idle_or_copied:0:75:100:off
1:main2copy:79:vdisk79:80:vdisk80:::idle_or_copied:0:50:100:off

Preparing and starting a FlashCopy mapping using the CLI

Before you start the FlashCopy process using the command-line interface (CLI), you must prepare a
FlashCopy mapping.

About this task

Starting a FlashCopy mapping creates a point-in-time copy of the data on the source virtual disk (VDisk)
and writes it to the target VDisk (volume) for the mapping.

Perform the following steps to prepare and start a FlashCopy mapping:

Procedure
1. Issue the prestartfcmap CLI command to prepare the FlashCopy mapping.
To run the following command, the FlashCopy mapping cannot belong to a consistency group.
prestartfcmap -restore main1copy
Where main1copy is the name of the FlashCopy mapping.
This command specifies the optional restore parameter, which forces the mapping to be prepared
even if the target VDisk is being used as a source in another active FlashCopy mapping.
The mapping enters the preparing state and moves to the prepared state when it is ready.
2. Issue the lsfcmap CLI command to check the state of the mapping.
The following is an example of the output that is displayed:
lsfcmap -delim :
id:name:source_vdisk_id:source_vdisk_name:target_vdisk_id:
target_vdisk_name:group_id:group_name:status:progress:copy_rate
0:main1copy:0:mainvdisk1:1:bkpvdisk1:::prepared:0:50

3. Issue the startfcmap CLI command to start the FlashCopy mapping.

The following is an example of the CLI command you can issue to start the FlashCopy mapping:
startfcmap -restore main1copy
Where main1copy is the name of the FlashCopy mapping.
This command specifies the optional restore parameter, which forces the mapping to be started even
if the target VDisk is being used as a source in another active FlashCopy mapping.
4. Issue the lsfcmapprogress CLI command with the FlashCopy mapping name or ID to check the
progress of the mapping.
The following is an example of the output that is displayed; the FlashCopy mapping ID 0 is 47%
completed.
lsfcmapprogress -delim :
id:progress
0:47

Results

You have created a point-in-time copy of the data on a source VDisk and written that data to a target
VDisk. The data on the target VDisk is only recognized by the hosts that are mapped to it.

Chapter 3. Using the CLI 35

Stopping FlashCopy mappings using the CLI
You can use the command-line interface (CLI) to stop a FlashCopy mapping.

About this task

Follow these steps to stop a single stand-alone FlashCopy mapping.

Procedure
1. To stop a FlashCopy mapping, issue the following stopfcmap command:
stopfcmap fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the mapping to stop.
2. To stop immediately all processing associated with the mapping and break the dependency on the
source VDisk (volume) of any mappings that are also dependent on the target disk, issue the
following command:
stopfcmap -force -split fc_map_id or fc_map_name
When you use the force parameter, all FlashCopy mappings that depend on this mapping (as listed
by the lsfcmapdependentmaps command) are also stopped. The split parameter can be specified only
when stopping a map that has a progress of 100 as shown by the lsfcmap command. The split
parameter removes the dependency of any other mappings on the source VDisk. It might be used
prior to starting another FlashCopy mapping whose target disk is the source disk of the mapping
being stopped. After the mapping is stopped with the split option, you can start the other mapping
without the restore option.

Deleting a FlashCopy mapping using the CLI

You can use the command-line interface (CLI) to delete a FlashCopy mapping.

Before you begin

The rmfcmap CLI command deletes an existing mapping if the mapping is in the idle_or_copied or
stopped state. If it is in the stopped state, the force parameter is required to specify that the target VDisk
(volume) is brought online. If the mapping is in any other state, you must stop the mapping before you
can delete it.

If deleting the mapping splits the tree that contains the mapping, none of the mappings in either
resulting tree can depend on any mapping in the other tree. To display a list of dependent FlashCopy
mappings, use the lsfcmapdependentmaps command.

About this task

Procedure
1. To delete an existing mapping, issue the rmfcmap CLI command:
rmfcmap fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the mapping to delete.
2. To delete an existing mapping and bring the target VDisk online, issue the following command:
rmfcmap -force fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the mapping to delete.

Results

The command does not return any output.

36 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Creating a FlashCopy consistency group and adding mappings using
the CLI
You can use the command-line interface (CLI) to create and add mappings to a FlashCopy consistency
group.

About this task

If you have created several FlashCopy mappings for a group of virtual disks (volumes) that contain
elements of data for the same application, it can be convenient to assign these mappings to a single
FlashCopy consistency group. You can then issue a single prepare or start command for the whole group.
For example, you can copy all of the files for a database at the same time.

Perform the following steps to add FlashCopy mappings to a new FlashCopy consistency group:

Procedure
1. Issue the mkfcconsistgrp CLI command to create a FlashCopy consistency group.
The following is an example of the CLI command you can issue to create a FlashCopy consistency
group:
mkfcconsistgrp -name FCcgrp0 -autodelete
Where FCcgrp0 is the name of the FlashCopy consistency group. The -autodelete parameter specifies
to delete the consistency group when the last FlashCopy mapping is deleted or removed from the
consistency group.
2. Issue the lsfcconsistgrp CLI command to display the attributes of the group that you have created.
The following is an example of the CLI command you can issue to display the attributes of a
FlashCopy consistency group:
lsfcconsistgrp -delim : FCcgrp0
The following is an example of the output that is displayed:
id:1
name:FCcgrp0
status:idle_or_copied
autodelete:on
FC_mapping_id:0
FC_mapping_name:fcmap0
FC_mapping_id:1
FC_mapping_name:fcmap1

Note: For any group that has just been created, the status reported is empty
3. Issue the chfcmap CLI command to add FlashCopy mappings to the FlashCopy consistency group:
The following are examples of the CLI commands you can issue to add Flash Copy mappings to the
FlashCopy consistency group:
chfcmap -consistgrp FCcgrp0 main1copy
chfcmap -consistgrp FCcgrp0 main2copy
Where FCcgrp0 is the name of the FlashCopy consistency group and main1copy, main2copy are the
names of the FlashCopy mappings.
4. Issue the lsfcmap CLI command to display the new attributes of the FlashCopy mappings.
The following is an example of the output that is displayed:
lsfcmap -delim :
id:name:source_vdisk_id:source_vdisk_name:target_vdisk_id:
target_vdisk_name:group_id:group_name:status:progress:copy_rate
0:main1copy:28:maindisk1:29:bkpdisk1:1:FCcgrp0:idle_copied::75
1:main2copy:30:maindisk2:31:bkpdisk2:1:FCcgrp0:idle_copied::50

Chapter 3. Using the CLI 37

5. Issue the lsfcconsistgrp CLI command to display the detailed attributes of the group.
The following is an example of a CLI command that you can issue to display detailed attributes:
lsfcconsistgrp -delim : FCcgrp0
Where FCcgrp0 is the name of the FlashCopy consistency group, and -delim specifies the delimiter.
The following is an example of the output that is displayed:
id:1
name:FCcgrp0
status:idle_or_copied
autodelete:off
FC_mapping_id:0
FC_mapping_name:main1copy
FC_mapping_id:1
FC_mapping_name:main2copy

Preparing and starting a FlashCopy consistency group using the CLI

You can use the command-line interface (CLI) to prepare and start a FlashCopy consistency group to start
the FlashCopy process.

About this task

Successful completion of the FlashCopy process creates a point-in-time copy of the data on the source
virtual disk (VDisk) and writes it to the target VDisk (volume) for each mapping in the group. When
several mappings are assigned to a FlashCopy consistency group, only a single prepare command is
issued to prepare every FlashCopy mapping in the group; only a single start command is issued to start
every FlashCopy mapping in the group.

Perform the following steps to prepare and start a FlashCopy consistency group:

Procedure
1. Issue the prestartfcconsistgrp CLI command to prepare the FlashCopy consistency group. This
command must be issued before the copy process can begin.

Remember: A single prepare command prepares all of the mappings simultaneously for the entire
group.
An example of the CLI command issued to prepare the FlashCopy consistency group:
prestartfcconsistgrp -restore maintobkpfcopy
Where maintobkpfcopy is the name of the FlashCopy consistency group.
The optional restore parameter forces the consistency group to be prepared—even if the target
volume is being used as a source volume in another active mapping. An active mapping is in the
copying, suspended, or stopping state. The group enters the preparing state, and then moves to the
prepared state when it is ready.
2. Issue the lsfcconsistgrp command to check the status of the FlashCopy consistency group.
An example of the CLI command issued to check the status of the FlashCopy consistency group.
lsfcconsistgrp -delim :
An example of the output displayed:
id:name:status
1:maintobkpfcopy:prepared

3. Issue the startfcconsistgrp CLI command to start the FlashCopy consistency group to make the copy.

Remember: A single start command starts all the mappings simultaneously for the entire group.
An example of the CLI command issued to start the FlashCopy consistency group mappings:

38 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 startfcconsistgrp -prep -restore maintobkpfcopy
Where maintobkpfcopy is the name of the FlashCopy consistency group.
Include the prep parameter, and the system automatically issues the prestartfcconsistgrp command
for the specified group.

Note: Combining the restore parameter with the prep parameter, force-starts the consistency group.
This occurs even if the target volume is being used as a source volume in another active mapping. An
active mapping is in the copying, suspended, or stopping state.
The FlashCopy consistency group enters the copying state and returns to the idle_copied state when
complete.
4. Issue the lsfcconsistgrp command to check the status of the FlashCopy consistency group.
An example of the CLI command issued to check the status of the FlashCopy consistency group:
lsfcconsistgrp -delim : maintobkpfcopy
Where maintobkpfcopy is the name of the FlashCopy consistency group.
An example of the output displayed during the copying process:
id:name:status
1:maintobkpfcopy:copying

An example of the output displayed when the process copying is complete:

id:1
name:maintobkpfcopy
status:idle_copied
autodelete:off
FC_mapping_id:0
FC_mapping_name:main1copy
FC_mapping_id:1
FC_mapping_name:main2copy

Stopping a FlashCopy consistency group using the CLI

You can use the command-line interface (CLI) to stop a FlashCopy consistency group.

Before you begin

The stopfcconsistgrp CLI command stops all processing that is associated with a FlashCopy consistency
group that is in one of the following processing states: prepared, copying, stopping, or suspended.

About this task

Procedure
1. To stop a FlashCopy consistency group, issue the stopfcconsistgrp CLI command:
stopfcconsistgrp fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the mapping to delete.
2. To stop a consistency group and break the dependency on the source VDisks of any mappings that
are also dependent on the target VDisk, issue the following command:
stopfcconsistgrp -split fc_map_id or fc_map_name
You can specify the split parameter when all the maps in the group have a progress of 100. It
removes the dependency of any other maps on the source VDisks. You can use this option before you
start another FlashCopy consistency group whose target disks are the source disks of the mappings
that are being stopped. After the consistency group is stopped with the split option, you can start the
other consistency group without the restore option

Chapter 3. Using the CLI 39

Results

The command does not return any output.

Deleting a FlashCopy consistency group using the CLI

You can use the command-line interface (CLI) to delete a FlashCopy consistency group.

Before you begin

The rmfcconsistgrp CLI command deletes an existing FlashCopy consistency group. The force parameter
is required only when the consistency group that you want to delete contains mappings.

About this task

Procedure
1. To delete an existing consistency group that does not contain mappings, issue the rmfcconsistgrp CLI
command:
rmfcconsistgrp fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the consistency group to delete.
2. To delete an existing consistency group that contains mappings that are members of the consistency
group, issue the following command:
rmfcconsistgrp -force fc_map_id or fc_map_name
where fc_map_id or fc_map_name is the ID or name of the mapping to delete.
All the mappings that are associated with the consistency group are removed from the group and
changed to stand-alone mappings. To delete a single mapping in the consistency group, you must use
the rmfcmap command.

Results

The command does not return any output.

Creating Metro Mirror or Global Mirror relationships using the CLI

You can use the command-line interface (CLI) to create Metro Mirror or Global Mirror relationships.

About this task

To create Metro Mirror or Global Mirror relationships, perform these steps:

Procedure
1. To create a Metro Mirror relationship, run the mkrcrelationship command. For example, enter:
mkrcrelationship -master master_vdisk_id
-aux aux_vdisk_id -system cluster_id
Where master_vdisk_id is the ID of the master volume, aux_vdisk_id is the ID of the auxiliary volume,
and system_id is the ID of the remote clustered system.
2. To create a new Global Mirror relationship, run the mkrcrelationship command with the -global
parameter. For example, enter either one of the following commands:
Where master_vdisk_id is the ID of the master volume, aux_vdisk_id is the ID of the auxiliary volume,
and system_id is the ID of the remote system.
3. To create a new relationship with cycling enabled:
mkrcrelationship -global -cycling multi

40 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note: Add change volumes to a relationship by issuing chrcrelationship -auxchange or
chrcrelationship-masterchange.

Modifying Metro Mirror or Global Mirror relationships using the CLI

You can use the command-line interface (CLI) to modify certain attributes of Metro Mirror or Global
Mirror relationships. You can change only one attribute at a time for each command submission.

About this task

To modify Metro Mirror or Global Mirror relationships, run the chrcrelationship command.

Procedure
1. Run the chrcrelationship command to change the name of a Metro Mirror or Global Mirror
relationship. For example, to change the relationship name, enter:
chrcrelationship -name new_rc_rel_name previous_rc_rel_name
Where new_rc_rel_name is the new name of the relationship and previous_rc_rel_name is the previous
name of the relationship.
2. Run the chrcrelationship command to remove a relationship from whichever consistency group it is a
member of. For example, enter:
chrcrelationship -force -noconsistgrp rc_rel_name/id
Where rc_rel_name/id is the name or ID of the relationship.

Note: For a full list of applicable options, refer to “chrcrelationship” on page 385.

Starting and stopping Metro Mirror or Global Mirror relationships using

the CLI
You can use the command-line interface (CLI) to start and stop stand-alone Metro Mirror and Global
Mirror relationships. Relationships that are members of consistency groups must be started and stopped
using the consistency group CLI commands.

About this task

To start and stop Metro Mirror or Global Mirror relationships, perform these steps:

Procedure
1. To start a Metro Mirror or Global Mirror relationship, run the startrcrelationship command. For
example, enter:
startrcrelationship rc_rel_id
Where rc_rel_id is the ID of the relationship that you want to start in a stand-alone relationship.
2. To stop a Metro Mirror or Global Mirror relationship, run the stoprcrelationship command. This
command applies to a stand-alone relationship.
For example, enter:
stoprcrelationship rc_rel_id
Where rc_rel_id is the ID of the stand-alone relationship that you want to stop mirroring I/O.

Displaying the progress of Metro Mirror or Global Mirror relationships

using the CLI
You can use the command-line interface (CLI) to display the background copy of Metro Mirror or Global
Mirror relationships as a percentage. When the initial background copy process for a relationship has
completed, null is displayed for the progress of that relationship.

Chapter 3. Using the CLI 41

About this task

To display the progress of the background copy of Metro Mirror or Global Mirror relationships, run the
lsrcrelationshipprogress command.

Procedure
1. To display data progress without headings for columns of data or for each item of data in a Metro
Mirror or Global Mirror relationship, run the lsrcrelationshipprogress -nohdr command. For example,
to display data of the relationship with headings suppressed, enter:
lsrcrelationshipprogress -nohdr rc_rel_name
Where rc_rel_name is the name of the specified object type.
2. To display the progress of a background copy of a Metro Mirror or Global Mirror relationship as a
percentage, run the lsrcrelationshipprogress -delim command. The colon character (:) separates all
items of data in a concise view, and the spacing of columns does not occur. In a detailed view, the
data is separated from its header by the specified delimiter. For example, enter:
lsrcrelationshipprogress -delim : 0
The resulting output is displayed, such as in this example:
id:progress
0:58

Switching Metro Mirror or Global Mirror relationships using the CLI

You can use the command-line interface (CLI) to reverse the roles of primary and secondary virtual disks
or VDisks (volumes) in a stand-alone Metro Mirror or Global Mirror relationship when that relationship
is in a consistent state. Relationships that are members of consistency groups must be switched by using
the consistency group CLI commands.

About this task

To switch the roles of primary and secondary volumes in Metro Mirror or Global Mirror relationships,
follow these steps:

Procedure
1. To make the master disk in a Metro Mirror or Global Mirror relationship to be the primary, run the
switchrcrelationship -primary master command. For example, enter:
switchrcrelationship -primary master rc_rel_id
Where rc_rel_id is the ID of the relationship to switch.
2. To make the auxiliary disk in a Metro Mirror or Global Mirror relationship to be the primary, run the
switchrcrelationship -primary aux command. For example, enter:
switchrcrelationship -primary aux rc_rel_id
Where rc_rel_id is the ID of the relationship to switch.

Remember:
v You cannot switch a global relationship if cycling is (automatically) set.
v To switch the direction of a multi cycling mode-based relationship, the relationship must stop with
access enabled. Then, start by using -force in the opposite direction.

Deleting Metro Mirror and Global Mirror relationships using the CLI
You can use the command-line interface (CLI) to delete Metro Mirror and Global Mirror relationships.

42 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Procedure

To delete Metro Mirror and Global Mirror relationships, run the rmrcrelationship command. For
example, enter:
rmrcrelationship rc_rel_name/id

where rc_rel_name/id is the name or ID of the relationship.

Creating Metro Mirror or Global Mirror consistency groups using the

CLI
You can use the command-line interface (CLI) to create Metro Mirror or Global Mirror consistency
groups.

About this task

To create Metro Mirror or Global Mirror consistency groups, perform these steps:

Procedure
1. To create a Metro Mirror or Global Mirror consistency group, run the mkrcconsistgrp command. For
example, enter:
mkrcconsistgrp -name new_name -cluster cluster_id
where new_name is the name of the new consistency group and cluster_id is the ID of the remote
cluster for the new consistency group. If -cluster is not specified, a consistency group is created only
on the local cluster. The new consistency group does not contain any relationships and will be in the
empty state.
2. To add Metro Mirror or Global Mirror relationships to the group, run the chrcrelationship command.
For example, enter:
chrcrelationship -consistgrp consist_group_name rc_rel_id
where consist_group_name is the name of the new consistency group to assign the relationship to and
rc_rel_id is the ID of the relationship.

Modifying Metro Mirror or Global Mirror consistency groups using the

CLI
You can use the command-line interface (CLI) to assign a new name or modify the name of an existing
Metro Mirror or Global Mirror consistency group.

About this task

To assign or modify the name of a Metro Mirror or Global Mirror consistency group, run the
chrcconsistgrp command.

Procedure
1. Run the chrcconsistgrp command to assign a new name of a Metro Mirror or Global Mirror
consistency group. For example, enter:
chrcconsistgrp -name new_name_arg
Where new_name_arg is the assigned new name of the consistency group.
2. Run the chrcconsistgrp command to change the name of the consistency group. For example, enter:
chrcconsistgrp -name new_consist_group_name previous_consist_group_name
Where new_consist_group_name is the assigned new name of the consistency group and
previous_consist_group_name is the previous name of the consistency group.

Chapter 3. Using the CLI 43

Starting and stopping Metro Mirror or Global Mirror consistency-group
copy processes using the CLI
You can use the command-line interface (CLI) to start and stop Metro Mirror or Global Mirror
consistency-group copy processes.

About this task

To start and stop Metro Mirror or Global Mirror consistency-group copy processes, perform these steps:

Procedure
1. To start a Metro Mirror or Global Mirror consistency-group copy process, set the direction of copy if it
is undefined and optionally mark the secondary VDisks of the consistency group as clean. Run the
startrcconsistgrp command. For example, enter:
startrcconsistgrp rc_consist_group_id
Where rc_consist_group_id is the ID of the consistency group to start processing.
2. To stop the copy process for a Metro Mirror or Global Mirror consistency group, run the
stoprcconsistgrp command.
For example, enter:
stoprcconsistgrp rc_consist_group_id
Where rc_consist_group_id is the ID of the consistency group that you want to stop processing.
If the group is in a consistent state, you can also use this command to enable write access to the
secondary virtual disks (VDisks) in the group.

Deleting Metro Mirror or Global Mirror consistency groups using the

CLI
You can use the command-line interface (CLI) to delete Metro Mirror or Global Mirror consistency
groups.

About this task

To delete existing Metro Mirror or Global Mirror consistency groups, follow these steps:

Procedure
1. To delete a Metro Mirror or Global Mirror consistency group, run the rmrcconsistgrp command. For
example, enter:
rmrcconsistgrp rc_consist_group_id
Where rc_consist_group_id is the ID of the consistency group to delete.
2. If a Metro Mirror or Global Mirror consistency group is not empty, you must use the -force
parameter to delete the consistency group. For example, enter:
rmrcconsistgrp -force rc_consist_group_id
Where rc_consist_group_id is the ID of the consistency group to delete. This command causes all
relationships that are members of the deleted group to become stand-alone relationships.

Creating Metro Mirror and Global Mirror partnerships using the CLI
You can use the command-line interface (CLI) to create Metro Mirror and Global Mirror partnerships
between two clusters.

About this task

Perform the following steps to create Metro Mirror and Global Mirror partnerships:

44 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Procedure
1. To create Metro Mirror and Global Mirror partnerships, run the mkpartnership command. For
example, enter:
mkpartnership -bandwidth bandwidth_in_mbps remote_cluster_id
where bandwidth_in_mbps specifies the bandwidth (in megabytes per second) that is used by the
background copy process between the clusters and remote_cluster_id is the ID of the remote cluster.
2. Run the mkpartnership command from the remote cluster. For example, enter:
mkpartnership -bandwidth bandwidth_in_mbps local_cluster_id
where bandwidth_in_mbps specifies the bandwidth (in megabytes per second) that is used by the
background copy process between the clusters and local_cluster_id is the ID of the local cluster.

Modifying Metro Mirror and Global Mirror partnerships using the CLI
You can use the command-line interface (CLI) to modify Metro Mirror and Global Mirror partnerships.

About this task

The partnership bandwidth, which is also known as background copy, controls the rate at which data is
sent from the local clustered system to the remote clustered system. The partnership bandwidth can be
changed to help manage the use of intersystem links. It is measured in megabytes per second (MBps).

Perform the following steps to modify Metro Mirror and Global Mirror partnerships:

Procedure
1. To modify Metro Mirror and Global Mirror partnerships, run the chpartnership command. For
example, enter:
chpartnership -bandwidth bandwidth_in_mbps remote_cluster_id
where bandwidth_in_mbps is the new bandwidth (in megabytes per second) from the local clustered
system to the remote clustered system, and remote_cluster_id is the ID of the remote system.
2. Run the chpartnership command from the remote clustered system. For example, enter:
chpartnership -bandwidth bandwidth_in_mbps local_cluster_id
where bandwidth_in_mbps is the new bandwidth (in megabytes per second) from the remote clustered
system to the local clustered system, and local_cluster_id is the ID of the local system.

Starting and stopping Metro Mirror and Global Mirror partnerships

using the CLI
You can use the command-line interface (CLI) to start and stop Metro Mirror and Global Mirror
partnerships.

About this task

Perform the following steps to start and stop Metro Mirror and Global Mirror partnerships:

Procedure
1. To start a Metro Mirror or Global Mirror partnership, run the chpartnership command from either
cluster. For example, enter:
chpartnership -start remote_cluster_id
Where remote_cluster_id is the ID of the remote cluster. The mkpartnership command starts the
partnership by default.
2. To stop a Metro Mirror or Global Mirror partnership, run the chpartnership command from either
cluster.
For example, enter:

Chapter 3. Using the CLI 45

 chpartnership -stop remote_cluster_id
Where remote_cluster_id is the ID of the remote cluster.

Deleting Metro Mirror and Global Mirror partnerships using the CLI
You can use the command-line interface (CLI) to delete Metro Mirror and Global Mirror partnerships.

About this task

Perform the following steps to delete Metro Mirror and Global Mirror partnerships:

Procedure
1. If a Metro Mirror or Global Mirror partnership has configured relationships or groups, you must stop
the partnership before you can delete it. For example, enter:
chpartnership -stop remote_cluster_id
Where remote_cluster_id is the ID of the remote cluster.
2. To delete a Metro Mirror and Global Mirror partnership, run the rmpartnership command from either
cluster. For example, enter:
rmpartnership remote_cluster_id
Where remote_cluster_id is the ID of the remote cluster.

Determining the WWPNs of a node using the CLI

You can determine the worldwide port names (WWPNs) of a node using the command-line interface
(CLI).

About this task

Perform the following steps to determine the WWPNs of a node:

Procedure
1. Issue the lsnode CLI command to list the nodes in the clustered system.
2. Record the name or ID of the node for which you want to determine the WWPNs.
3 3. Issue the lsportfc CLI command and specify the node name or ID that was recorded in step 2.
3 The following is an example of the CLI command you can issue:
3 svcinfo lsportfc -filtervalue node_id=2
3 Where node_id=2 is the name of the node for which you want to determine the WWPNs. The
3 following is the output from the command:
3 id fc_io_port_id port_id type port_speed node_id node_name WWPN nportid status
3 0 1 1 fc 8Gb 2 node2 5005076801405F82 010E00 active
3 1 2 2 fc 8Gb 2 node2 5005076801305F82 010A00 active
3 2 3 3 fc 8Gb 2 node2 5005076801105F82 010E00 active
3 3 4 4 fc 8Gb 2 node2 5005076801205F82 010A00 active
3 4 5 3 ethernet 10Gb 2 node2 5005076801505F82 540531 active
3 5 6 4 ethernet 10Gb 2 node2 5005076801605F82 E80326 active
3 4. Record the four port IDs (WWPNs). The Fibre Channel (FC) ports are identified by the port type fc
3 and Fiber Channel over Ethernet (FCoE) ports are identified by the port type ethernet.

Listing node-dependent volumes using the CLI

You can use the command-line interface (CLI) to list the volumes that are dependent on the status of a
node.

46 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Before you begin

If a node goes offline or is removed from a clustered system, all volumes that are dependent on the node
go offline. Before taking a node offline or removing a node from a clustered system, run the
lsdependentvdisks command to identify any node-dependent volumes.

About this task

By default, the lsdependentvdisks command also checks all available quorum disks. If the quorum disks
are accessible only through the specified node, the command returns an error.

Various scenarios can produce node-dependent volumes. The following examples are common scenarios
in which the lsnodedependentvdisks command will return node-dependent volumes:
1. The node contains solid-state drives (SSDs) and also contains the only synchronized copy of a
mirrored volume.
2. The node is the only node that can access an MDisk on the SAN fabric.
3. The other node in the I/O group is offline (all volumes in the I/O group are returned).
4. Pinned data in the cache is stopping the partner node from joining the I/O group.
To resolve (1), allow volume mirror synchronizations between SSD MDisks to complete. To resolve (2-4),
bring any offline MDisks online and repair any degraded paths.

Note: The command lists the node-dependent volumes at the time the command is run; subsequent
changes to a clustered system require running the command again.

Procedure
1. Issue the lsdependentvdisks CLI command.
The following example shows the CLI format for listing the volumes that are dependent on node01:
lsdependentvdisks -drive -delim : 0:1
The following example shows the output that is displayed:
vdisk_id:vdisk_name
4:vdisk4
5:vdisk5
2. If the lsdependentvdisks command returns an error, you must move your quorum disks to MDisks
that are accessible through all nodes. Rerun the command until no errors are returned.
3. Reissue the lsdependentvdisks command. When the command returns no volumes, the clustered
system is free from any node-dependent volumes.
The following example shows the command syntax for listing the volumes that are dependent on
node01:
lsdependentvdisks -node01 :
The following example shows the command output if there are no node-dependent volumes in the
clustered system:
vdisk_id vdisk_name

Determining the VDisk name from the device identifier on the host
You can use the command-line interface (CLI) to determine the virtual disk (VDisk) name from the device
identifier on the host.

Chapter 3. Using the CLI 47

About this task

Each VDisk that is exported by the SAN Volume Controller is assigned a unique device identifier. The
device identifier uniquely identifies the VDisk (volume) and can be used to determine which VDisk
corresponds to the volume that the host sees.

Perform the following steps to determine the VDisk name from the device identifier:

Procedure
1. Find the device identifier. For example, if you are using the subsystem device driver (SDD), the disk
identifier is referred to as the virtual path (vpath) number. You can issue the following SDD command
to find the vpath serial number:
datapath query device
For other multipathing drivers, refer to the documentation that is provided with your multipathing
driver to determine the device identifier.
2. Find the host object that is defined to the SAN Volume Controller and corresponds with the host that
you are working with.
a. Find the worldwide port numbers (WWPNs) by looking at the device definitions that are stored
by your operating system. For example, on AIX the WWPNs are in the ODM and if you use
Windows you have to go into the HBA Bios.
b. Verify which host object is defined to the SAN Volume Controller for which these ports belong.
The ports are stored as part of the detailed view, so you must list each host by issuing the
following CLI command:
lshost id | name
Where name/id is the name or ID of the host.
c. Check for matching WWPNs.
3. Issue the following command to list the VDisk-to-host mappings:
lshostvdiskmap hostname
Where hostname is the name of the host.
4. Find the VDisk UID that matches the device identifier and record the VDisk name or ID.

Determining the host that a VDisk (volume) is mapped to

You can determine the host that a virtual disk (VDisk) is mapped to using the command-line interface
(CLI). To view the host mapping for a volume in the management GUI, select Volumes > Volumes by
Hosts.

About this task

Perform the following steps to determine the host that the VDisk (volume) is mapped to:

Procedure
1. Find the VDisk name or ID that you want to check.
2. Issue the following CLI command to list the hosts that this VDisk is mapped:
lsvdiskhostmap vdiskname/id
where vdiskname/id is the name or ID of the VDisk.
3. Find the host name or ID to determine which host this VDisk is mapped to.
v If no data is returned, the VDisk is not mapped to any hosts.

48 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Determining the relationship between volumes and MDisks using the
CLI
You can determine the relationship between volumes and managed disks (MDisks) using the
command-line interface (CLI).

About this task

Select one or more of the following options to determine the relationship between volumes and MDisks:

Procedure
v To display a list of the IDs that correspond to the MDisks that comprise the volume, issue the
following CLI command:
lsvdiskmember vdiskname/id
where vdiskname/id is the name or ID of the volume.
v To display a list of IDs that correspond to the volumes that are using this MDisk, issue the following
CLI command:
lsmdiskmember mdiskname/id
where mdiskname/id is the name or ID of the MDisk.
v To display a table of volume IDs and the corresponding number of extents that are being used by each
volume, issue the following CLI command:
lsmdiskextent mdiskname/id
where mdiskname/id is the name or ID of the MDisk.
v To display a table of MDisk IDs and the corresponding number of extents that each MDisk provides as
storage for the given volume, issue the following CLI command:
lsvdiskextent vdiskname/id
where vdiskname/id is the name or ID of the volume.

Determining the relationship between MDisks and controller LUNs

using the CLI
You can determine the relationship between managed disks (MDisks) and RAID arrays or LUNs using
the command-line interface (CLI).

About this task

Each MDisk corresponds with a single RAID array, or with a single partition on a given RAID array. Each
RAID controller defines a LUN number for this disk. The LUN number and controller name or ID are
needed to determine the relationship between MDisks and RAID arrays or partitions.

Perform the following steps to determine the relationship between MDisks and RAID arrays:

Procedure
1. Issue the following command to display a detailed view of the MDisk:
lsmdisk mdiskname
Where mdiskname is the name of the MDisk for which you want to display a detailed view.
2. Record the controller name or controller ID and the controller LUN number.
3. Issue the following command to display a detailed view of the controller:
lscontroller controllername
Where controllername is the name of the controller that you recorded in step 2.

Chapter 3. Using the CLI 49

4. Record the vendor ID, product ID, and WWNN. You can use this information to determine what is
being presented to the MDisk.
5. From the native user interface for the given controller, list the LUNs it is presenting and match the
LUN number with that noted in step 1 on page 49. This tells you the exact RAID array or partition
that corresponds with the MDisk.

Increasing the size of your clustered system using the CLI

You can increase throughput by adding more nodes to the clustered system. The nodes must be added in
pairs and assigned to a new I/O group.

About this task

Perform the following steps to increase the size of your clustered system:

Procedure
1. Add a node to your clustered system and repeat this step for the second node.
2. If you want to balance the load between the existing I/O groups and the new I/O groups, you can
migrate your volumes to new I/O groups. Repeat this step for all volumes that you want to assign to
the new I/O group.

Adding a node to increase the size of a clustered system using the CLI
You can use the command-line interface (CLI) to increase the size of a clustered system by adding a pair
of nodes to create a full I/O group.

Before you begin

Attention: If you are adding a node that was previously removed from a clustered system (system) ,
ensure that the following conditions have been met:
v All hosts that accessed the removed node through its WWPNs have been reconfigured to use the
WWPN for the new node or to no longer access the enclosure. Failure to do so can result in data
corruption. .
v Ensure that the system ID has been reset on the new control enclosure. This can be performed using
– Either of the new control enclosure nodes using the Command-Line Interface (CLI) - visit:
“chenclosurevpd” on page 429
– The Service Assistant system by performing the following steps:
- Connect to the service assistant on either of the nodes in the control enclosure.
- Select Configure Enclosure.
- Select the Reset the system ID option. Do not make any other changes on the panel.
- Click Modify to make the changes.

About this task

Complete the following steps to add a node and increase the size of a clustered system:

Procedure
1. Install the new nodes. Connect the nodes to the Fibre Channel.
2. Using the front panel of the node, record the WWNN. The front panel only shows the last 5 digits of
the WWNN.
3. Issue the following command to verify that the node is detected on the fabric:
lsnodecandidate

50 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The following example shows the output for this command:
# svcinfo lsnodecandidate
id panel_name UPS_serial_number UPS_unique_id hardware
5005076801002838 104890 10004BC010 20400001124C0040 8G4
5005076801003205 106142 10004BC052 20400001124C0142 8G4
4. Verify that the last 5 digits on the WWNN that was reported by lsnodecandidate match the WWNN
that was recorded from the front panel. Record the full WWNN (id) for use in later steps.
5. Issue the following command to determine the I/O group where the node should be added:
lsiogrp
6. Record the name or ID of the first I/O group that has a node count of zero (0). You will need the ID
for the next step.

Note: You only need to do this step for the first node that is added. The second node of the pair uses
the same I/O group number.
7. Issue the following command to add the node to the clustered system:
addnode -wwnodename WWNN -iogrp newiogrpname/id [-name newnodename]
Where WWNN is the WWNN of the node, newiogrpname/id is the name or ID of the I/O group that
you want to add the node to and newnodename is the name that you want to assign to the node. If you
do not specify a new node name, a default name is assigned; however, it is recommended you specify
a meaningful name.
8. Record the following information for future reference:
v Serial number.
v Worldwide node name.
v All of the worldwide port names.
v The name or ID of the I/O group that contains the node.
9. Issue the following command to verify that the node is online:
lsnode

What to do next

Add additional nodes until the I/O group contains two nodes. You may need to reconfigure your storage
systems to allow the new nodes to access them. If the storage system uses mapping to present RAID
arrays or partitions to the clustered system and the WWNNs or the worldwide port names have changed,
you must modify the port groups that belong to the clustered system.

Validating and repairing mirrored volume copies using the CLI

You can use the repairvdiskcopy command from the command-line interface (CLI) to validate and repair
mirrored volume copies.

Attention: Run the repairvdiskcopy command only if all volume copies are synchronized.

When you issue the repairvdiskcopy command, you must use only one of the -validate, -medium, or
-resync parameters. You must also specify the name or ID of the volume to be validated and repaired as
the last entry on the command line. After you issue the command, no output is displayed.
-validate
Use this parameter if you only want to verify that the mirrored volume copies are identical. If any
difference is found, the command stops and logs an error that includes the logical block address
(LBA) and the length of the first difference. You can use this parameter, starting at a different LBA
each time to count the number of differences on a volume.
-medium
Use this parameter to convert sectors on all volume copies that contain different contents into virtual

Chapter 3. Using the CLI 51

 medium errors. Upon completion, the command logs an event, which indicates the number of
differences that were found, the number that were converted into medium errors, and the number
that were not converted. Use this option if you are unsure what the correct data is, and you do not
want an incorrect version of the data to be used.
-resync
Use this parameter to overwrite contents from the specified primary volume copy to the other
volume copy. The command corrects any differing sectors by copying the sectors from the primary
copy to the copies being compared. Upon completion, the command process logs an event, which
indicates the number of differences that were corrected. Use this action if you are sure that either the
primary volume copy data is correct or that your host applications can handle incorrect data.
-startlba lba
Optionally, use this parameter to specify the starting Logical Block Address (LBA) from which to start
the validation and repair. If you previously used the validate parameter, an error was logged with
the LBA where the first difference, if any, was found. Reissue repairvdiskcopy with that LBA to
avoid reprocessing the initial sectors that compared identically. Continue to reissue repairvdiskcopy
using this parameter to list all the differences.

Issue the following command to validate and, if necessary, automatically repair mirrored copies of the
specified volume:
repairvdiskcopy -resync -startlba 20 vdisk8

Notes:
1. Only one repairvdiskcopy command can run on a volume at a time.
2. Once you start the repairvdiskcopy command, you cannot use the command to stop processing.
3. The primary copy of a mirrored volume cannot be changed while the repairvdiskcopy -resync
command is running.
4. If there is only one mirrored copy, the command returns immediately with an error.
5. If a copy being compared goes offline, the command is halted with an error. The command is not
automatically resumed when the copy is brought back online.
6. In the case where one copy is readable but the other copy has a medium error, the command process
automatically attempts to fix the medium error by writing the read data from the other copy.
7. If no differing sectors are found during repairvdiskcopy processing, an informational error is logged
at the end of the process.

Checking the progress of validation and repair of volume copies using the CLI

Use the lsrepairvdiskcopyprogress command to display the progress of mirrored volume validation and
repairs. You can specify a volume copy using the -copy id parameter. To display the volumes that have
two or more copies with an active task, specify the command with no parameters; it is not possible to
have only one volume copy with an active task.

To check the progress of validation and repair of mirrored volumes, issue the following command:
lsrepairvdiskcopyprogress –delim :

The following example shows how the command output is displayed:

vdisk_id:vdisk_name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:medium:50:070301120000
0:vdisk0:1:medium:50:070301120000

52 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Repairing a space-efficient volume using the CLI
You can use the repairsevdiskcopy command from the command-line interface to repair the metadata on
a space-efficient volume.

The repairsevdiskcopy command automatically detects and repairs corrupted metadata. The command
holds the volume offline during the repair, but does not prevent the disk from being moved between I/O
groups.

If a repair operation completes successfully and the volume was previously offline because of corrupted
metadata, the command brings the volume back online. The only limit on the number of concurrent
repair operations is the number of virtual disk copies in the configuration.

When you issue the repairsevdiskcopy command, you must specify the name or ID of the volume to be
repaired as the last entry on the command line. Once started, a repair operation cannot be paused or
cancelled; the repair can only be terminated by deleting the copy.

Attention: Use this command only to repair a space-efficient volume (thin-provisioned volume) that has
reported corrupt metadata.

Issue the following command to repair the metadata on a space-efficient volume:

repairsevdiskcopy vdisk8

After you issue the command, no output is displayed.

Notes:
1. Because the volume is offline to the host, any I/O that is submitted to the volume while it is being
repaired fails.
2. When the repair operation completes successfully, the corrupted metadata error is marked as fixed.
3. If the repair operation fails, the volume is held offline and an error is logged.

Checking the progress of the repair of a space-efficient volume using the CLI

Issue the lsrepairsevdiskcopyprogress command to list the repair progress for space-efficient volume
copies of the specified volume. If you do not specify a volume, the command lists the repair progress for
all space-efficient copies in the system.

Note: Only run this command after you run the repairsevdiskcopy command, which you must only run
as required by the fix procedures or by IBM support.

Recovering from offline volumes using the CLI

If a node or an I/O group fails, you can use the command-line interface (CLI) to recover offline volumes.

About this task

If you have lost both nodes in an I/O group and have, therefore, lost access to all the volumes that are
associated with the I/O group, you must perform one of the following procedures to regain access to
your volumes. Depending on the failure type, you might have lost data that was cached for these
volumes and the volumes are now offline.

Data loss scenario 1

One node in an I/O group has failed and failover has started on the second node. During the failover
process, the second node in the I/O group fails before the data in the write cache is written to hard disk.

Chapter 3. Using the CLI 53

The first node is successfully repaired but its hardened data is not the most recent version that is
committed to the data store; therefore, it cannot be used. The second node is repaired or replaced and has
lost its hardened data, therefore, the node has no way of recognizing that it is part of the clustered
system.

Perform the following steps to recover from an offline volume when one node has down-level hardened
data and the other node has lost hardened data:

Procedure
1. Recover the node and add it back into the system.
2. Delete all IBM FlashCopy mappings and Metro Mirror or Global Mirror relationships that use the
offline volumes.
3. Run the recovervdisk, recovervdiskbyiogrp or recovervdiskbysystem command.
4. Re-create all FlashCopy mappings and Metro Mirror or Global Mirror relationships that use the
volumes.

Example
Data loss scenario 2

Both nodes in the I/O group have failed and have been repaired. The nodes have lost their hardened
data, therefore, the nodes have no way of recognizing that they are part of the system.

Perform the following steps to recover from an offline volume when both nodes have lost their hardened
data and cannot be recognized by the system:
1. Delete all FlashCopy mappings and Metro Mirror or Global Mirror relationships that use the offline
volumes.
2. Run the recovervdisk, recovervdiskbyiogrp or recovervdiskbysystem command.
3. Recreate all FlashCopy mappings and Metro Mirror or Global Mirror relationships that use the
volumes.

Recovering a node and returning it to the clustered system using the

CLI
After a node or an I/O group fails, you can use the command-line interface (CLI) to recover a node and
return it to the clustered system.

About this task

Perform the following steps to recover a node and return it to the clustered system:

Procedure
1. Issue the following command to verify that the node is offline:
lsnode
2. Issue the following command to remove the old instance of the offline node from the clustered
system:
rmnode nodename/id

Where nodename/id is the name or ID of the node.

3. Issue the following command to verify that the node can be seen on the fabric:
lsnodecandidate

54 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note: Remember the worldwide node names (WWNNs) for each node because you will need them in
the following step.
4. If the nodes are repaired by replacing the service controller, or the node is replaced, be sure to follow
the replacement instructions for the specific node or controller. You will be instructed to reset the
WWNN of the node to that of the original node. If you do not do that, you may need to reconfigure
your SAN fabric, your hosts, and your storage systems.
Attention: If more than one I/O group is affected, ensure that you are adding the node to the same
I/O group from which it was removed. Failure to do this can result in data corruption. Use the
information that was recorded when the node was originally added to the clustered system. This can
avoid a possible data corruption exposure if the node must be removed from and re-added to the
clustered system. If you do not have access to this information, call the IBM Support Center to add
the node back into the clustered system without corrupting the data. If you are adding the node into
the clustered system for the first time, you must record the following information:
v Node serial number
v WWNN
v All WWPNs
v I/O group that contains the node
5. Issue the following command to add the node back into the clustered system:
addnode -wwnodename WWNN -iogrp
IOGRPNAME/ID [-name NODENAME]

Where WWNN is the worldwide node name, IOGRPNAME/ID is the I/O group name or ID and
NODENAME is the name of the node.
In a service situation, a node should normally be added back into a clustered system using the
original node name. As long as the partner node in the I/O group has not been deleted too, this is the
default name used if -name is not specified.
6. Issue the following command to verify that the node is online:
lsnode

Recovering offline volumes using the CLI

You can recover offline volumes using the command-line interface (CLI).

About this task

Perform the following steps to recover offline volumes:

Procedure
1. Issue the following CLI command to list all volumes that are offline and belong to an I/O group,
enter:
lsvdisk -filtervalue IO_group_name=
IOGRPNAME/ID:status=offline
where IOGRPNAME/ID is the name of the I/O group that failed.
2. To acknowledge data loss for a volume with a fast_write_state of corrupt and bring the volume back
online, enter:
recovervdisk vdisk_id | vdisk_name
where vdisk_id | vdisk_name is the name or ID of the volume.

Notes:
v If the specified volume is space-efficient or has space-efficient copies, the recovervdisk command
starts the space-efficient repair process.
v If the specified volume is mirrored, the recovervdisk command starts the resynchronization process.

Chapter 3. Using the CLI 55

3. To acknowledge data loss for all virtual disks in an I/O group with a fast_write_state of corrupt and
bring them back online, enter:
recovervdiskbyiogrp io_group_id | io_group_name
where io_group_id | io_group_name is the name or ID of the I/O group.

Notes:
v If any volume is space-efficient or has space-efficient copies, the recovervdiskbyiogrp command
starts the space-efficient repair process.
v If any volume is mirrored, the recovervdiskbyiogrp command starts the resynchronization process.
4. To acknowledge data loss for all volumes in the clustered system with a fast_write_state of corrupt and
bring them back online, enter:
recovervdiskbycluster

Notes:
v If any volume is space-efficient or has space-efficient copies, the recovervdiskbycluster command
starts the space-efficient repair process.
v If any volume is mirrored, the recovervdiskbycluster command starts the resynchronization
process.

Moving offline volumes to their original I/O group using the CLI
You can move offline volumes to their original I/O group using the command-line interface (CLI).

About this task

After a node or an I/O group fails, you can use the following procedure to move offline volumes to their
original I/O group.

Attention: Do not move volumes to an offline I/O group. Ensure that the I/O group is online before
you move the volume back to avoid any further data loss.

Perform the following steps to move offline volumes to their original I/O group:

Procedure
1. Issue the following command to move the volume back into the original I/O group:
chvdisk -iogrp IOGRPNAME/ID -force
vdiskname/ID
where IOGRPNAME/ID is the name or ID of the original I/O group and vdiskname/ID is the name or
ID of the offline volume.
2. Issue the following command to verify that the volumes are now online:
lsvdisk -filtervalue IO_group_name=
IOGRPNAME/ID
where IOGRPNAME/ID is the name or ID of the original I/O group.

Recording WWPN changes of replaced host HBAs

You can use the command-line interface (CLI) to record a change to a defined host object.

Before you begin

Because it is sometimes necessary to replace the host-bus adapter (HBA) that connects the host to the
SAN, you must inform the SAN Volume Controller of the new worldwide port names (WWPNs) that this
HBA contains.

56 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Ensure that your switch is zoned correctly.

Perform the following steps to inform the SAN Volume Controller of a change to a defined host object:

Procedure
1. Issue the following CLI command to list the candidate HBA ports:
lshbaportcandidate

You should see a list of the HBA ports that are available for addition to host objects. One or more of
these HBA ports should correspond with the one or more WWPNs that belong to the new HBA port.
2. Locate the host object that corresponds with the host in which you have replaced the HBA. The
following CLI command lists all the defined host objects:
lshost
3. Issue the following CLI command to list the WWPNs that are currently assigned to the host object:
lshost hostobjectname
where hostobjectname is the name of the host object.
4. Issue the following CLI command to add the new ports to the existing host object:
addhostport -hbawwpn one or more existing WWPNs
separated by : hostobjectname/ID
where one or more existing WWPNs separated by : is the WWPNs that are currently assigned to the host
object and hostobjectname/ID is the name or ID of the host object.
5. Issue the following CLI command to remove the old ports from the host object:
rmhostport -hbawwpn one or more existing WWPNs
separated by : hostobjectname/ID
where one or more existing WWPNs separated by : is the WWPNs that are currently assigned to the host
object and hostobjectname/ID is the name or ID of the host object.

Results

Any mappings that exist between the host object and the virtual disks (VDisks) are automatically applied
to the new WWPNs. Therefore, the host sees the VDisks as the same SCSI LUNs as before.

What to do next

See the IBM System Storage Multipath Subsystem Device Driver User's Guide or the documentation that is
provided with your multipathing driver for additional information about dynamic reconfiguration.

Expanding VDisks (volumes) using the CLI

You can use the command-line interface (CLI) to expand a virtual disk (VDisk).

About this task

VDisks (volumes) that are mapped for FlashCopy or that are in Metro Mirror relationships cannot be
expanded.

Ensure that you have run Windows Update and have applied all recommended updates to your system
before you attempt to expand a VDisk that is mapped to a Windows host.

Determine the exact size of the source or master VDisk by issuing the following CLI command:
lsvdisk -bytes vdiskname

where vdiskname is the name of the VDisk for which you want to determine the exact size.

Chapter 3. Using the CLI 57

VDisks can be expanded under Windows concurrently with I/O operations.

You can expand VDisks for the following reasons:

v To increase the available capacity on a particular VDisk that is already mapped to a host.
v To increase the size of a VDisk so that it matches the size of the source or master VDisk and so that it
can be used in a FlashCopy mapping or Metro Mirror relationship.

A VDisk that is not mapped to any hosts and does not contain any data can be expanded at any time. If
the VDisk contains data that is in use, you can expand the VDisks if your host has a supported AIX or
Microsoft Windows operating system.

The following table provides the supported operating systems and requirements for expanding VDisks
that contain data:

Operating system Supported Requirement

AIX Yes AIX version 5.2 or later
HP-UX No -
Linux No -
SUN Solaris No -
Microsoft Windows NT No -
Microsoft Windows Yes Windows version 2000 or later

Expanding a VDisk (volume) that is mapped to an AIX host

The SAN Volume Controller supports the ability to dynamically expand the size of a virtual disk (VDisk)
if the AIX host is using AIX version 5.2 or later.

About this task

The chvg command options provide the ability to expand the size of a physical volume that the Logical
Volume Manager (LVM) uses, without interruptions to the use or availability of the system. See the AIX
System Management Guide Operating System and Devices for more information.

Expanding a volume that is mapped to a Microsoft Windows host

using the CLI
You can use the command-line interface (CLI) to dynamically expand the size of a volume that is mapped
to a Microsoft Windows host.

About this task

Perform the following steps to expand a volume that is mapped to a Windows host:

Procedure
1. Issue the following CLI command to expand the volume:
expandvdisksize -size disk_size -unit
b | kb | mb | gb | tb | pb vdisk_name/vdisk_id
where disk_size is the capacity by which you want to expand the volume, b | kb | mb | gb | tb | pb is
the data unit to use in conjunction with the capacity and vdisk_name/vdisk_id is the name of the
volume or the ID of the volume to expand.
2. On the Windows host, start the Computer Management application and open the Disk Management
window under the Storage branch.

58 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Results

You will see the volume that you expanded now has some unallocated space at the end of the disk.

You can expand dynamic disks without stopping I/O operations in most cases. However, in some
applications the operating system might report I/O errors. When this problem occurs, either of the
following entries might be recorded in the System event log:
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 31
Description: dmio:
Harddisk0 write error at block ######## due to
disk removal

Event Type: Information

Event Source: dmio
Event Category: None
Event ID: 34
Description: dmio:
Harddisk0 is re-online by PnP

Attention: This is a known problem with Windows 2000 and is documented in the Microsoft knowledge
base as article Q327020. If either of these errors are seen, run Windows Update and apply the
recommended fixes to resolve the problem.

What to do next

If the Computer Management application was open before you expanded the volume, use the Computer
Management application to issue a rescan command.

If the disk is a Windows basic disk, you can create a new primary or extended partition from the
unallocated space.

If the disk is a Windows dynamic disk, you can use the unallocated space to create a new volume
(simple, striped, mirrored) or add it to an existing volume.

Shrinking a volume using the CLI

You can reduce the size of a volume using the command-line interface (CLI).

About this task

Volumes can be reduced in size, if it is necessary. You can make a target or auxiliary volume the same
size as the source or master volume when you create FlashCopy mappings, Metro Mirror relationships, or
Global Mirror relationships. However, if the volume contains data, do not shrink the size of the disk.

Chapter 3. Using the CLI 59

Attention:
1. The SAN Volume Controller arbitrarily reduces the capacity of the volume by removing one or more
extents from those that are allocated to the volume. You cannot control which extents are removed so
you cannot guarantee that it is unused space that is removed.
2. If the volume contains data that is being used, do not attempt under any circumstances to shrink a volume
without first backing up your data.
3. For performance reasons, some operating systems or file systems use the outer edge of the disk.

You can use the shrinkvdisksize command to shrink the physical capacity that is allocated to the
particular volume by the specified amount. You can also shrink the virtual capacity of a thin-provisioned
volume without altering the physical capacity assigned to the volume.

For more information about the command parameters, see the IBM System Storage SAN Volume Controller
and IBM Storwize V7000 Command-Line Interface User's Guide.

Procedure

Perform the following steps to shrink a volume:

1. Validate that the volume is not mapped to any host objects. If the volume is mapped, data is
displayed.
2. You can determine the exact capacity of the source or master volume. Issue the following command:

lsvdisk -bytes vdiskname

3. Shrink the volume by the required amount. Issue the following command:

shrinkvdisksize -size capacitytoshrinkby -unit

unitsforreduction vdiskname/ID

Migrating extents using the CLI

To improve performance, you can migrate extents using the command-line interface (CLI).

About this task

The SAN Volume Controller provides various data migration features. These can be used to move the
placement of data both within storage pools and between storage pools. These features can be used
concurrently with I/O operations. You can use either of these methods to migrate data:
1. Migrating data (extents) from one MDisk to another (within the same storage pool). This can be used
to remove highly utilized MDisks.
2. Migrating volumes from one storage pool to another. This can be used to remove highly utilized
storage pools. For example, you can reduce the utilization of a group of MDisks.

Migration commands fail if the target or source volume is offline, or if there is insufficient quorum disk
space to store the metadata. Correct the offline or quorum disk condition and reissue the command.

You can determine the usage of particular MDisks by gathering input/output (I/O) statistics about nodes,
MDisks, and volumes. After you have gathered this data, you can analyze it to determine which MDisks
are highly utilized. The procedure then takes you through querying and migrating extents to elsewhere in
the same storage pool. This procedure can only be performed using the command-line tools.

If performance monitoring tools, such as IBM Tivoli Storage Productivity Center, indicate that a managed
disk in the pool is being overutilized, you can migrate some of the data onto other MDisks within the
same storage pool.

60 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Procedure
1. Determine the number of extents that are in use by each volume for the given MDisk by issuing this
CLI command:

lsmdiskextent mdiskname

This command returns the number of extents that each volume is using on the given MDisk. You
should pick some of these to migrate elsewhere in the group.
2. Determine the other MDisks that reside in the same storage pool.
a. To determine the storage pool that the MDisk belongs to, issue this CLI command:

lsmdisk mdiskname | ID
b. List the MDisks in the group by issuing this CLI command:

lsmdisk -filtervalue mdisk_grp_name=mdiskgrpname

3. Select one of these MDisks as the target MDisk for the extents. You can determine how many free
extents exist on an MDisk by issuing this CLI command:
lsfreeextents mdiskname

You can issue the lsmdiskextent newmdiskname command for each of the target MDisks to ensure that
you are not just moving the over-utilization to another MDisk. Check that the volume that owns the
set of extents to be moved does not already own a large set of extents on the target MDisk.
4. For each set of extents, issue this CLI command to move them to another MDisk:

migrateexts -source mdiskname | ID -exts num_extents

-target newmdiskname | ID -threads 4 vdiskid

where num_extents is the number of extents on the vdiskid. The newmdiskname | ID value is the name
or ID of the MDisk to migrate this set of extents to.

Note: The number of threads indicates the priority of the migration processing, where 1 is the lowest
priority and 4 is the highest priority.
5. Repeat the previous steps for each set of extents that you are moving.
6. You can check the progress of the migration by issuing this CLI command:

lsmigrate

Migrating volumes between storage pools using the CLI

You can migrate volumes between storage pools using the command-line interface (CLI).

About this task

You can determine the usage of particular MDisks by gathering input/output (I/O) statistics about nodes,
MDisks, and volumes. After you have gathered this data, you can analyze it to determine which volumes
or MDisks are hot. You can then migrate volumes from one storage pool to another.

Perform the following step to gather statistics about MDisks and volumes:
1. Use secure copy (scp command) to retrieve the dump files for analyzing. For example, issue the
following:
scp clusterip:/dumps/iostats/v_*

This copies all the volume statistics files to the AIX host in the current directory.

Chapter 3. Using the CLI 61

 2. Analyze the dumps to determine which volumes are hot. It might be helpful to also determine which
MDisks are being used heavily as you can spread the data that they contain more evenly across all
the MDisks in the group by migrating the extents.

After you analyze the I/O statistics data, you can determine which volumes are hot. You also need to
determine the storage pool that you want to move this volume to. Either create a new storage pool or
determine an existing group that is not yet overly used. To do this, check the I/O statistics files that you
generated and then ensure that the MDisks or VDisks in the target storage pool are used less than those
in the source group.

You can use data migration or volume mirroring to migrate data between MDisk groups. Data migration
uses the command migratevdisk. Volume mirroring uses the commands addvdiskcopy and rmvdiskcopy.

When you issue the migratevdisk command, a check is made to ensure that the destination of the
migration has enough free extents to satisfy the command. If it does, the command proceeds. The
command takes some time to complete.

Notes:
v You cannot use the SAN Volume Controller data migration function to move a volume between storage
pools that have different extent sizes.
v Migration commands fail if the target or source volume is offline, or if there is insufficient quorum disk
space to store the metadata. Correct the offline or quorum disk condition and reissue the command.

1 For more information, refer to the following commands:

1 v “addvdiskaccess” on page 474
1 v “lsvdiskaccess” on page 347
1 v “movevdisk” on page 477
1 v “rmvdiskaccess” on page 497

When you use data migration, it is possible for the free destination extents to be consumed by another
process; for example, if a new volume is created in the destination storage pool or if more migration
commands are started. In this scenario, after all the destination extents are allocated, the migration
commands suspend and an error is logged (error ID 020005). To recover from this situation, use either of
the following methods:
v Add additional MDisks to the target storage pool. This provides additional extents in the group and
allows the migrations to be restarted. You must mark the error as fixed before you reattempt the
migration.
v Migrate one or more VDisks that are already created from the storage pool to another group. This frees
up extents in the group and allows the original migrations to be restarted.

Perform the following steps to use the migratevdisk command to migrate volumes between storage
pools:

Procedure
1. After you determine the volume that you want to migrate and the new storage pool you want to
migrate it to, issue the following CLI command:
migratevdisk -vdisk vdiskname/ID -mdiskgrp
newmdiskgrname/ID -threads 4
2. You can check the progress of the migration by issuing the following CLI command:
lsmigrate

62 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 What to do next

When you use data migration, the volume goes offline if either storage pool fails. Volume mirroring can
be used to minimize the impact to the volume because the volume goes offline only if the source storage
pool fails.

Perform the following steps to use volume mirroring to migrate volumes between storage pool:
1. After you determine the volume that you want to migrate and the new storage pool that you want to
migrate it to, issue the following command:
addvdiskcopy -mdiskgrp newmdiskgrname/ID vdiskname/ID
2. The copy ID of the new copy is returned. The copies now synchronize such that the data is stored in
both storage pools. You can check the progress of the synchronization by issuing the following
command:
lsvdisksyncprogress
3. After the synchronization is complete, remove the copy from the original I/O group to free up extents
and decrease the utilization of the storage pool. To remove the original copy, issue the following
command:
rmvdiskcopy -copy original copy id vdiskname/ID

e Moving a volume between I/O groups using the CLI

3 This task explains how to move a VDisk (volume).

About this task

Attention: These migration tasks can be non-disruptive if performed correctly and hosts mapped to the
volume support non disruptive volume move The cached data that is held within the clustered system
(system) must first be written to disk before the allocation of the volume can be changed.

e Modifying the I/O group that services the volume can be done concurrently with I/O operations if the
e host supports non disruptive volume move. It also requires a rescan at the host level to ensure that the
e multipathing driver is notified that the allocation of the preferred node has changed and the ports by
e which the volume is accessed has changed. This can be done in the situation where one pair of nodes has
e become over utilized.

If there are any host mappings for the volume, the hosts must be members of the target I/O group or the
migration fails.

Perform the following steps to migrate a volume between I/O groups:

Procedure
1. Issue the following command: addvdiskaccess -iogrp iogrp id/name volume id/name
2. Issue the following command: movevdisk -iogrp destination iogrp -node new preferred node
volume id/name
3. Issue the appropriate commands on the hosts mapped to the volume to detect the new paths to the
volume in the destination I/O group.
4. Once you confirm the new paths are online, remove access from the old I/O group: rmvdiskaccess
-iogrp iogrp id/name volume id/name
5. Issue the appropriate commands on the hosts mapped to the volume to remove the paths to the old
I/O group.

Chapter 3. Using the CLI 63

Creating an image mode volume using the CLI
You can use the command-line interface (CLI) to import storage that contains existing data and continue
to use this storage. You can also the advanced functions, such as Copy Services, data migration, and the
cache. These disks are known as image mode virtual volumes.

About this task

Make sure you are aware of the following before you create image mode volumes:
1. Unmanaged-mode managed disks (MDisks) that contain existing data cannot be differentiated from
unmanaged-mode MDisks that are blank. Therefore, it is vital that you control the introduction of
these MDisks to the clustered system by adding these disks one at a time. For example, map a single
LUN from your RAID storage system to the clustered system and refresh the view of MDisks. The
newly detected MDisk is displayed.
2. Do not manually add an unmanaged-mode MDisk that contains existing data to a storage pool. If you
do, the data is lost. When you use the command to convert an image mode volume from an
unmanaged-mode disk, you will select the storage pool where it should be added.
See the following website for more information:

www.ibm.com/storage/support/2145

Perform the following steps to create an image mode volume:

Procedure
1. Stop all I/O operations from the hosts. Unmap the logical disks that contain the data from the hosts.
2. Create one or more storage pools.
3. Map a single array or logical unit from your RAID storage system to the clustered system. You can do
this through a switch zoning or a RAID storage system based on your host mappings. The array or
logical unit appears as an unmanaged-mode MDisk to the SAN Volume Controller.
4. Issue the lsmdisk command to list the unmanaged-mode MDisks.
If the new unmanaged-mode MDisk is not listed, you can perform a fabric-level discovery. Issue the
detectmdisk command to scan the Fibre Channel network for the unmanaged-mode MDisks.

Note: The detectmdisk command also rebalances MDisk access across the available storage system
device ports.
5. Convert the unmanaged-mode MDisk to an image mode virtual disk.

Note: If the volume that you are converting maps to a solid-state drive (SSD), the data that is stored
on the volume is not protected against SSD failures or node failures. To avoid data loss, add a volume
copy that maps to an SSD on another node.
Issue the mkvdisk command to create an image mode virtual disk object.
6. Map the new volume to the hosts that were previously using the data that the MDisk now contains.
You can use the mkvdiskhostmap command to create a new mapping between a volume and a host.
This makes the image mode volume accessible for I/O operations to the host.

Results

After the volume is mapped to a host object, the volume is detected as a disk drive with which the host
can perform I/O operations.

64 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
What to do next

If you want to virtualize the storage on an image mode volume, you can transform it into a striped
volume. Migrate the data on the image mode volume to managed-mode disks in another storage pool.
Issue the migratevdisk command to migrate an entire image mode volume from one storage pool to
another storage pool.

Migrating data to an image mode virtual disk using the CLI

You can use the command-line interface (CLI) to migrate data to an image mode virtual disk (VDisk).

About this task

The migratetoimage CLI command allows you to migrate the data from an existing VDisk (volume) onto
a different managed disk (MDisk).

When the migratetoimage CLI command is issued, it migrates the data of the user specified source VDisk
onto the specified target MDisk. When the command completes, the VDisk is classified as an image mode
VDisk.

Note: Migration commands fail if the target or source VDisk is offline, or if there is insufficient quorum
disk space to store the metadata. Correct the offline or quorum disk condition and reissue the command.

The MDisk specified as the target must be in an unmanaged state at the time the command is run.
Issuing this command results in the inclusion of the MDisk into the user specified MDisk group.

Issue the following CLI command to migrate data to an image mode VDisk:

migratetoimage -vdisk vdiskname/ID

-mdisk newmdiskname/ID -mdiskgrp newmdiskgrpname/ID
-threads 4

where vdiskname/ID is the name or ID of the VDisk, newmdiskname/ID is the name or ID of the new
MDisk, and newmdiskgrpname/ID is the name or ID of the new MDisk group (storage pool).

Deleting a node from a clustered system using the CLI

You can use the command-line interface (CLI) to remove a node from a clustered system.

Before you begin

After the node is deleted, the other node in the I/O group enters write-through mode until another node
is added back into the I/O group.

By default, the rmnode command flushes the cache on the specified node before taking the node offline.
When operating in a degraded state, the SAN Volume Controller ensures that data loss does not occur as
a result of deleting the only node with the cache data.

Chapter 3. Using the CLI 65

Attention:
v If you are removing a single node and the remaining node in the I/O group is online, the data can be
exposed to a single point of failure if the remaining node fails.
v If both nodes in the I/O group are online and the volumes are already degraded before deleting the
node, redundancy to the volumes is already degraded. Removing a node might result in loss of access
to data, and data loss might occur if the force option is used.
v Removing the last node in the clustered system destroys the clustered system. Before you delete the
last node in the clustered system, ensure that you want to destroy the clustered system.
v When you delete a node, you remove all redundancy from the I/O group. As a result, new or existing
failures can cause I/O errors on the hosts. These failures can occur:
– Host configuration errors
– Zoning errors
– Multipathing software configuration errors
v If you are deleting the last node in an I/O group and there are volumes assigned to the I/O group,
you cannot delete the node from the clustered system if the node is online. You must back up or
migrate all data that you want to save before you delete the node. If the node is offline, you can delete
the node.
v To take the specified node offline immediately without flushing the cache or ensuring that data loss
does not occur, run the rmnode command with the force parameter. The force parameter forces
continuation of the command even though any node-dependent volumes will be taken offline. Use the
force parameter with caution; access to data on node-dependent volumes will be lost.

About this task

Perform these steps to delete a node:

Procedure
1. If you are deleting the last node in an I/O group, determine the volumes that are still assigned to this
I/O group:
a. Issue this CLI command to request a filtered view of the volumes:
lsvdisk -filtervalue IO_group_name=name

Where name is the name of the I/O group.

b. Issue this CLI command to list the hosts that this volume is mapped to:
lsvdiskhostmap vdiskname/identification
Where vdiskname/identification is the name or identification of the volume.

Note: If volumes are assigned to this I/O group that contain data that you want to continue to access,
back up the data or migrate the volumes to a different (online) I/O group.
2. If this node is not the last node in the clustered system, turn off the power to the node that you
intend to remove. This step ensures that the multipathing device driver, such as the subsystem device
driver (SDD), does not rediscover the paths that are manually removed before you issue the delete
node request.

66 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Attention:
a. If you are removing the configuration node, the rmnode command causes the configuration node to
move to a different node within the clustered system. This process might take a short time,
typically less than a minute. The clustered system IP address remains unchanged, but any SSH
client attached to the configuration node might must reestablish a connection.
b. If you turn on the power to the node that has been removed and it is still connected to the same
fabric or zone, it attempts to rejoin the clustered system. The clustered system causes the node to
remove itself from the clustered system and the node becomes a candidate for addition to this
clustered system or another clustered system.
c. If you are adding this node into the clustered system, ensure that you add it to the same I/O
group that it was previously a member of. Failure to do so can result in data corruption.
d. In a service situation, a node should normally be added back into a clustered system using the
original node name. As long as the partner node in the I/O group has not been deleted too, this is
the default name used if -name is not specified.
3. Before you delete the node, update the multipathing device driver configuration on the host to
remove all device identifiers that are presented by the volumes that you intend to remove. If you are
using the subsystem device driver, the device identifiers are referred to as virtual paths (vpaths).
Attention: Failure to perform this step can result in data corruption.
See the IBM System Storage Multipath Subsystem Device Driver User's Guide for details about how to
dynamically reconfigure SDD for the given host operating system.
4. Issue this CLI command to delete a node from the clustered system:
Attention: Before you delete the node: The rmnode command checks for node-dependent volumes,
which are not mirrored at the time that the command is run. If any node-dependent volumes are
found, the command stops and returns a message. To continue removing the node despite the
potential loss of data, run the rmnode command with the force parameter. Alternatively, follow these
steps before you remove the node to ensure that all volumes are mirrored:
a. Run the lsdependentvdisks command.
b. For each node-dependent volume that is returned, run the lsvdisk command.
c. Ensure that each volume returns in-sync status.
rmnode node_name_or_identification
Where node_name_or_identification is the name or identification of the node.

Performing the clustered system maintenance procedure using the CLI

You can use the command-line interface (CLI) to perform the clustered system maintenance procedure.

About this task

Perform the following steps for clustered system maintenance:

Procedure
1. Issue the finderr command to analyze the error log for the highest severity of unfixed errors. This
command scans the error log for any unfixed errors. Given a priority ordering defined within the
code, the highest priority of unfixed errors is returned.
2. Issue the dumperrlog command to dump the contents of the error log to a text file.
3. Locate and fix the error.
4. Issue the clearerrlog command to clear all entries from the error log, including status events and any
unfixed errors. Only issue this command when you have either rebuilt the clustered system or have
fixed a major problem that has caused many entries in the error log that you do not want to fix
individually.

Chapter 3. Using the CLI 67

 Note: Clearing the error log does not fix the errors.
5. Issue the cherrstate command to toggle the state of an error between unfixed and fixed.

Modifying the clustered system IP addresses using the CLI

You can use the command-line interface (CLI) to change the IP addresses that are associated with a
clustered system (system).

About this task

Attention: When you specify a new IP address for a system, the existing communication with the
system is broken. You must reconnect to the system with the new IP address.

Perform the following steps to change the system IP address:

Procedure
e 1. Issue the lssystemip command to list the current IP addresses that are used by the system.
e 2. Record the current IP addresses for future reference.
e 3. To change an Internet Protocol Version 4 (IPv4) system IP address, issue the following command:
e chsystemip -clusterip cluster_ip_address -port cluster_port
e where cluster_ip_address is the new IP address for the cluster and cluster_port specifies which port (1
e or 2) to apply changes to.
e 4. To change an IPv4 system IP address to an IPv6 system IP address, issue the following command:
e chsystemip -clusterip_6 cluster_ip_address -port cluster_port
e where cluster_ip_address is the new Internet Protocol Version 6 (IPv6) address for the cluster and
e cluster_port specifies which port (1 or 2) to apply changes to.
e 5. To change an IPv4 default gateway IP address, issue the following command:
e chsystemip -gw cluster_gateway_address -port cluster_port
e where cluster_gateway_address is the new gateway address for the cluster and cluster_port specifies
e which port (1 or 2) to apply changes to.
e 6. To change an IPv6 default gateway address, issue the following command:
e chsystemip -gw_6 cluster_gateway_address -port cluster_port
e where cluster_gateway_address is the new gateway address for the cluster and cluster_port specifies
e which port (1 or 2) to apply changes to.
e 7. Issue the following command to change an IPv4 system subnet mask
e chsystemip -mask cluster_subnet_mask -port cluster_port
e where cluster_subnet_mask is the new subnet mask for the cluster and cluster_port specifies which port
e (1 or 2) to apply changes to.
e 8. For IPv6 addresses, you can issue the following command to set the prefix for the system:
e chsystemip -prefix_6 -port cluster_port
e where cluster_port specifies which port (1 or 2) to apply changes to.
e 9. Optionally, if you want to delete all of the IPv4 addresses in the system after you have changed all
e addresses to IPv6, issue the following command:
e chsystem -noip
e 10. Optionally, if you want to delete all of the IPv6 addresses in the system after you have changed all
e addresses to IPv4, issue the following command:
e chsystem -noip_6
e 11. The IP routing table provides details of the gateway that is used for IP traffic to a range of IP
e addresses for each Ethernet port. This information can be used to diagnose configuration node
e accessibility problems. To display the IP routing table, enter the following CLI command:

68 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e lsroute
e 12. The ping command can be used to diagnose IP configuration problems by checking whether a given
e IP address is accessible from the configuration node. The command can be useful for diagnosing
e problems where the configuration node cannot be reached from a specific management server. For
e example, enter the following CLI command:
e ping ipv4_address | ipv6_address

e where ipv4_address | ipv6_address is either the IPv4 address or the IPv6 address.

Changing the clustered system gateway address using the CLI

You can use the command-line interface (CLI) to change the gateway address for a clustered system
(system).

About this task

Perform the following steps to change the system gateway address:

Procedure
1. Issue the lssystemip command to list the current gateway address of the system.
2. Record the current gateway address for future reference.
3. Issue the following command to change an IPv4 clustered system gateway address:
chsystemip -gw cluster_gateway_address -port cluster_port
where cluster_gateway_address is the new gateway address for the system. The port parameter specifies
which port (1 or 2) to apply changes to.
4. Issue the following command to change an IPv6 system gateway address:
chsystemip -gw_6 cluster_gateway_address -port cluster_port
where cluster_gateway_address is the new gateway address for the system. The port parameter specifies
which port (1 or 2) to apply changes to.

Changing the relationship bandwidth for a clustered system using the

CLI
You can use the command-line interface (CLI) to change the relationship bandwidth for a clustered
system.

About this task

The relationship bandwidth limit controls the maximum rate at which any one remote-copy relationship
can synchronize. The overall limit is controlled by the bandwidth parameter of each clustered system
partnership. The default value for the relationship bandwidth limit is 25 megabytes per second (MBps),
but you can change this by following these steps:

Procedure
1. Issue the lssystem command to list the current relationship bandwidth limit of the system. For
example:
lssystem system_id_or_system_name

Where system_id_or_system_name is the ID or name of the clustered system.

2. For future reference, record the current relationship bandwidth limit that is displayed. For example:
relationship_bandwidth_limit 25
3. To change the relationship bandwidth limit of the clustered system, issue the following command:

Chapter 3. Using the CLI 69

 chsystem -relationshipbandwidthlimit
system_relationship_bandwidth_limit
Where system_relationship_bandwidth_limit is the new limit for the cluster. Issue the command on both
clusters in a relationship.

Configuring the clustered system for iSCSI using the CLI

You need to complete several tasks to configure the clustered system to work with iSCSI-attached hosts.
The tasks include general tasks on the host system before you configure a clustered system on the SAN
Volume Controller.

Before you begin

Before completing any iSCSI-configuration tasks on the system, it is important that you complete all the
iSCSI-related configuration on the host machine. Because the SAN Volume Controller supports a variety
of host machines, consult the documentation for specific instructions and requirements for a particular
host. For a list of supported hosts, see this website:

www.ibm.com/storage/support/2145

About this task

To configure a system for iSCSI, follow these general tasks on the host system:
1. Select a software-based iSCSI initiator, such as Microsoft Windows iSCSI Software Initiator and verify
the iSCSI driver installation.
2. If required, install and configure a multipathing driver for the host system.

In addition, determine a naming convention for iSCSI names, such as iSCSI qualified names (IQNs) for
your system. Hosts use iSCSI names to connect to the node. Each node, for example, has a unique IQN,
and the system name and node name are used as part of that IQN. Each node, for example, has a unique
IQN, and the system name and node name are used as part of that IQN.

Port IP addresses are the IP addresses that are used by iSCSI-attached hosts to perform I/O.

Procedure
1. To configure a new port IP address to a specified Ethernet port of a node with an IPv4 address, enter
the following command-line interface (CLI) command:
cfgportip -node node_name | node_id -ip ipv4addr
-gw ipv4gw -mask subnet_mask -failover port_id
where node_name | node_id specifies the name or ID of the node that is being configured, ipv4addr is
the IPv4 address for the Ethernet port, ipv4gw is the IPv4 gateway IP address, subnet_mask is the IPv4
subnet mask, and port_id specifies the Ethernet port ID (1 or 2). To view a list of ports, use the
lsportip command.
The optional -failover parameter specifies that the port is to be used during failover. If the node that
is specified is the only online node in the I/O group, the address is configured and presented by this
node. When another node in the I/O group comes online, the failover address is presented by that
node. If two nodes in the I/O group are online when the command is issued, the address is presented
by the other node to the partner node.
2. To configure a new port IP address that belongs to a partner node with an IPv6 address in the I/O
group, enter the following CLI command:
cfgportip -node node_name | node_id -ip_6 ipv6addr
-gw_6 ipv6gw -prefix_6 prefix -failover port_id
where node_name | node_id specifies the name or ID of the node that is being configured, ipv6addr is
the IPv6 address for the iSCSI port, ipv6gw if the gateway address for the given IP address, prefix is

70 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 the IPv6 prefix for the gateway, and port_id specifies the Ethernet port ID (1 or 2). To view a list of
ports, use the lsportip command. If the partner node is offline, the address is configured and
presented by this node. When a partner node comes online, the failover address is presented by that
node.
The optional -failover parameter specifies that the data is failover data, which is data that is related
to the partner node. If the node that is specified is the only online node in the I/O group, the address
is configured and presented by this node. When another node in the I/O group comes online, the
failover address is presented by that node. If two nodes in the I/O group are online when the
command is issued, the address is presented by the other node to that specified.
3. To remove an iSCSI IP address from a node Ethernet port, enter either of these CLI commands. The
following command deletes an IPv4 configuration for the specified iSCSI Ethernet port:
rmportip -failover
-node node_name | node_id port_id
where node_name | node_id specifies the name or ID of the node with the Ethernet port that the IP
address is being removed from and port_id specifies the Ethernet port ID. To list the valid values for
the Ethernet port, enter the lsportip command. The optional -failover parameter indicates that the
specified data is failover data.
The following command deletes an IPv6 configuration for the specified iSCSI Ethernet port:
rmportip -ip_6 -failover
-node node_name | node_id port_id
where -ip_6 indicates that this command will remove an IPv6 configuration, node_name | node_id
specifies the name or ID of the node with the Ethernet port that the IP address is being removed
from, and port_id specifies the Ethernet port ID. To list the valid values for the Ethernet port, enter the
lsportip command. The optional -failover parameter indicates that the specified data is failover
data.

What to do next

After you configure your IP addresses, you can optionally create iSCSI aliases.

Configuring or modifying an iSCSI alias using the CLI

You can use the command-line interface (CLI) to optionally create or change the iSCSI alias for the
selected node. An iSCSI alias is a user-assigned name that identifies the SAN Volume Controller node to
the iSCSI-attached host.

About this task

To configure or modify an iSCSI alias, follow these steps:

Procedure
1. To configure a new port IP address to a specified Ethernet port of a node, enter the following CLI
command:
chnode -iscsialias alias node_name | node_id
where alias node_name | node_id specifies the name or ID of the node.
2. To specify that the name or iSCSI alias that is being set is the name or alias of the partner node in the
I/O group, enter the following CLI command. When there is no partner node, the values set are
applied to the partner node when it is added to the clustered system. If this parameter is used when
there is a partner node, the name or alias of that node changes
chnode -iscsialias alias -failover node_name | node_id
where alias specifies the iSCSI name of the node and node_name | node_id specifies the node to be
modified.

Chapter 3. Using the CLI 71

 What to do next

After you create iSCSI aliases, you can optionally configure the address for the Internet Storage Name
Service (iSNS) server for the system.

Configuring the iSNS server address using the CLI

If you are using iSCSI-attached hosts with the SAN Volume Controller clustered system, you can use the
command-line interface (CLI) to optionally configure the address for the Internet Storage Name Service
(iSNS) server for the system. Host systems use the iSNS server to manage iSCSI targets and for iSCSI
discovery.

Procedure
1. To specify an IPv4 address for the iSCSI storage name service (SNS), enter the following CLI
command:
e chsystem -isnsip sns_server_address

where sns_server_address is the IP address of the iSCSI storage name service in IPv4 format.
2. To specify an IPv6 address for the iSCSI storage name service (SNS), enter the following CLI
command:
e chsystem -isnsip_6 ipv6_sns_server_address

where ipv6_sns_server_address is the IP address of the iSCSI storage name service in IPv6 format.

What to do next

Configuring clustered system iSCSI authentication using the CLI

You can use the command-line interface (CLI) to configure the Challenge-Handshake Authentication
Protocol (CHAP) to authenticate the SAN Volume Controller clustered system to the iSCSI-attached hosts.
After the CHAP is set for the clustered system, all attached hosts must be configured to authenticate this
way. To help in problem determination, this step can be delayed until after the first one or two hosts
have been configured and their connectivity has been tested without authentication configured.

About this task

To configure authentication between the SAN Volume Controller clustered system and the iSCSI-attached
hosts, follow these steps:

Procedure
1. To set the authentication method for the iSCSI communications of the clustered system, enter the
following CLI command:
3 chsystem -iscsiauthmethod chap -chapsecret chap_secret

where chap sets the authentication method for the iSCSI communications of the clustered system and
chap_secret sets the CHAP secret to be used to authenticate the clustered system via iSCSI. This
parameter is required if the iscsiauthmethod chap parameter is specified. The specified CHAP secret
cannot begin or end with a space.
2. To clear any previously set CHAP secret for iSCSI authentication, enter the following CLI command:
3 chsystem -nochapsecret

The nochapsecret parameter is not allowed if the chapsecret parameter is specified.

72 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
3. The lsiscsiauth command lists the Challenge Handshake Authentication Protocol (CHAP) secret that
is configured for authenticating an entity to the SAN Volume Controller clustered system. The
command also displays the configured iSCSI authentication method. For example, enter the following
CLI command:
lsiscsiauth

What to do next

After you configure the CHAP secret for the SAN Volume Controller clustered system, ensure that the
clustered system CHAP secret is added to each iSCSI-attached host. On all iSCSI-attached hosts, specify a
CHAP secret that the hosts use to authenticate to the SAN Volume Controller clustered system.

Configuring remote authentication service using CLI

You can use the command-line interface (CLI) to configure the SAN Volume Controller to use remote
authentication.

About this task

If a user is configured on the clustered system as a local user, only local credentials are used. Otherwise,
when using the management GUI or the command-line interface (CLI), users entering their password are
authenticated against the remote service, and their roles are determined according to group memberships
defined on the remote service. If a user is configured on the clustered system as a remote user with an
SSH key, the user can additionally access the command-line interface using this Secure Shell (SSH) key.
Group memberships continue to be determined from the remote service.

Configuring remote authentication service with Tivoli Integrated Portal

(TIP) using the CLI
You can use the command-line interface (CLI) to configure the SAN Volume Controller to allow users of
SAN Volume Controller management applications, such as IBM Tivoli Storage Productivity Center, to
authenticate to the clustered system using Tivoli Integrated Portal (TIP).

About this task

To use the SAN Volume Controller with TIP, follow these steps:

Procedure
1. Configure the system with the location of the remote authentication server. Issue the chauthservice
command to change system settings, and issue the lssystem command to view system settings.

Remember: You can use either an http or https connection to the server. If you use http, the user,
password, and SSH key information is transmitted as clear text over the IP network.
2. Configure user groups (with roles) on the system by matching those that are used by the
authentication service. For each group of interest known to the authentication service, a SAN Volume
Controller user group must be created with the same name and with the remote setting enabled. For
example, if members of a group called sysadmins require the SAN Volume Controller Administrator
(Administrator) role, issue the following command:
mkusergrp -name sysadmins -remote -role Administrator
If none of the groups for a user match any of the SAN Volume Controller user groups, the user
cannot access the system.
3. Configure users who do not require Secure Shell (SSH) access. SAN Volume Controller users use the
remote authentication service and do not require SSH access should be deleted from the system.

Remember: A superuser cannot be deleted and cannot use the remote authentication service.

Chapter 3. Using the CLI 73

 4. Configure users who require SSH access. All SAN Volume Controller users who use the remote
authentication service and require SSH access must have remote settings enabled and the same
password and an SSH key set both on the system and on the authentication service.
5. Configure the system time. The current time of both the SAN Volume Controller clustered system and
the system that is running the remote authentication service must match.

Important: Use the same Network Time Protocol (NTP) server for both systems.

Configuring remote authentication service with Lightweight Directory

Access Protocol (LDAP) using the CLI
You can use the command-line interface (CLI) to configure the SAN Volume Controller to authenticate
users against servers implementing the Lightweight Directory Access Protocol (LDAP), including IBM
Tivoli Directory Server (ITDS) and Active Directory (AD).

About this task

e Remember: A superuser cannot be authenticated using a remote Lightweight Directory Access Protocol
e (LDAP server). However, other users can authenticate in this manner.

e To enable user authentication with LDAP, follow these steps:

Procedure
1. Configure LDAP by issuing the chldap command.
This command provides default settings for both IBM Tivoli Directory Server (ITDS) and Active
Directory (AD). For example, to configure authentication with ITDS schema defaults and Transport
Layer Security (TLS), issue the following command:
chldap -type itds -security tls
LDAP configuration can be inspected with the lsldap command.

Note: TLS is recommended because transmitted passwords are encrypted.

2. Specify the mkldapserver command to define up to six LDAP servers to use for authentication.
Multiple servers can be configured to provide access to different sets of users or for redundancy. All
servers must share the settings configured with chldap. For example, to configure an LDAP server
with a Secure Socket Layer (SSL) certificate and users in the cn=users,dc=company,dc=com subtree,
issue:
mkldapserver -ip 9.71.45.108 -basedn cn=users,dc=company,dc=com -sslcert /tmp/sslcert.pem
You can also configure which servers are preferred to authenticate users.
Specify lsldapserver for LDAP server configuration information. Specify chldapserver and
rmldapserver to make changes to the configured LDAP servers.
3. Configure user groups on the system by matching those that are used by the authentication service.
For each group of interest known to the authentication service, a SAN Volume Controller user group
must be created with the same name and with the remote setting enabled. For example, if members of
a group called sysadmins require the SAN Volume Controller Administrator (admin) role, issue the
following command:
mkusergrp -name sysadmins -remote -role Administrator
If none of the user groups match a SAN Volume Controller user group, the user cannot access the
system.
4. Verify your LDAP configuration using the testldapserver command.
To test the connection to the LDAP servers, issue the command without any options. A username can
be supplied with or without a password to test for configuration errors. To perform a full
authentication attempt against each server, issue the following commands:

74 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 testldapserver -username username -password password
5. Issue the following command to enable LDAP authentication:
chauthservice -type ldap -enable yes
6. Configure users who do not require Secure Shell (SSH) key access.
SAN Volume Controller users who must use the remote authentication service and do not require SSH
key access should be deleted from the system.

Remember: A superuser cannot be deleted or use the remote authentication service.

7. Configure users who require SSH key access.
All SAN Volume Controller users who use the remote authentication service and require SSH key
access must have the remote settings enabled and a valid SSH key configured on the system.

Creating and working with user groups using the CLI

You can use the command-line interface (CLI) to create and work with users and user groups. User
groups organize users of a clustered system by role.

About this task

Roles apply to both local and remote users on the system and are based on the user group to which the
user belongs. A local user can only belong to a single group; therefore, the role of a local user is defined
by the single group that the user belongs to. Remote users can belong to one or more groups; therefore,
the roles of remote users are assigned according to the groups that the remote user belongs to.

To create and work with user groups, follow these steps:

Procedure
1. Issue the mkusergrp CLI command to create a new user group. For example:
mkusergrp -name group_name -role role_name -remote

where group_name specifies the name of the user group and role_name specifies the role that is
associated with any users that belong to this group. The remote parameter specifies that the group is
visible to the remote authentication service.
The command returns the ID of the user group that was created. To create user groups in the
management GUI, select Access > Users. From the Global Actions menu, select New User Group.
2. Issue the chusergrp CLI command to change attributes of an existing user group. For example:
chusergrp -role role_name -remote yes | no group_id_or_name

where role_name specifies the role that is associated with any users that belong to this group and
group_id_or_name specifies the group to be changed. The remote parameter specifies whether the
group is visible to the authentication server.
To change a user group in the management GUI, select Access > Users. Select a user group and select
Properties from the Actions menu.
3. Issue the rmusergrp CLI command to delete a user group: For example:
rmusergrp -force group_id_or_name

where group_id_or_name specifies the group to delete. The force parameter specifies to delete the
group even if there are users in the user group. All users that were assigned to this group are
assigned to the Monitor group.
To delete a user group in the management GUI, select Access > Users. Select a user group and select
Delete from the Actions menu.

Chapter 3. Using the CLI 75

 4. Issue the lsusergrp CLI command to display the user groups that have been created on the system.
For example:
lsusergrp usergrp_id_or_name

where group_id_or_name specifies the user group to view. If you do not specify a user group ID or
name, all user groups on the system are displayed.

Creating and working with users using the CLI

You can use the command-line interface (CLI) to create and work with users.

Before you begin

e Local users must provide either a password, a Secure Shell (SSH) key, or both. Local users are
e authenticated through the authentication methods that are located on the Storwize V7000 or SAN Volume
e Controller system.

You can create two categories of users that access the clustered system (system). These user types are
based on how they authenticate to the system:
v Local users must provide an SSH password (or if not possible an SSH key).
v If the local user needs access to the management GUI, a password is needed for the user.
v If the user requires access to the command-line interface (CLI), a valid SSH key file is necessary and if
a user is working with both interfaces, both a password and SSH key must be used.
v Local users must be part of a user group that is defined on the system.

e Remote users should also configure local credentials if they need to access the system when the remote
e service is down. Remote users have their groups defined by the remote authentication service.
3 v For information about remote users with Tivoli Integrated Portal (TIP) support, see “Configuring
3 remote authentication service with Tivoli Integrated Portal (TIP) using the CLI” on page 73.
3 v For information about users with Lightweight Directory Access Protocol (LDAP), see “Configuring
3 remote authentication service with Lightweight Directory Access Protocol (LDAP) using the CLI” on
3 page 74.
e v For more information about local and remote users, see “Working with local and remote users” on
e page 8.

About this task

To create and work with users, follow these steps:

Procedure
1. Issue the mkuser CLI command to create either a local or remote user to access Storwize V7000. For
example:
mkuser -name user_name -remote

where user_name specifies the name of the user. The remote parameter specifies that the user
authenticates to the remote authentication service.
mkuser -name user_name -usergrp group_name_or_id

where user_name specifies the name of the user and group_name_or_id specifies the name or ID of the
user group with which the local user is associated.
v
v The usergrp parameter specifies the user authenticates to the system by using system
authentication methods.

76 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2. Issue the chuser CLI command to change the attributes of an existing user. For example:
chuser -usergrp group_id_or_name user_id_or_name

where the group_id_or_name specifies the new group for the user and user_id_or_name specifies the
user to be changed.
3. Issue the chcurrentuser CLI command to change the attributes of the current user. For example:
chcurrentuser -nokey

where the nokey parameter specifies that the SSH key of the user is to be deleted.
4. Issue the rmuser CLI command to delete a user: For example:
rmuser user_id_or_name

where user_id_or_name specifies the user to be removed.

5. Issue the lsuser CLI command to display a list of users that have been created on the system. For
example:
lsuser user_id_or_name

where user_id_or_name specifies the ID or name of the user view. If you do not specify an ID or name,
the concise view is displayed. If you do not specify a user ID or name, all users on the system are
displayed.
6. Issue the lscurrentuser CLI command to display the name and role of the logged-in user. For
example:
lscurrentuser
The name and the role of the user are displayed.

Setting up SNMP notifications using the CLI

You can set up event notifications using the command-line interface (CLI).

About this task

The notification settings apply to the entire cluster. You can specify the types of events that cause the
cluster to send a notification. The cluster sends a Simple Network Management Protocol (SNMP)
notification. The SNMP setting represents the type of notification.

SNMP is the standard protocol for managing networks and exchanging messages. SNMP enables the
SAN Volume Controller to send external messages that notify personnel about an event. You can use an
SNMP manager to view the messages that the SNMP agent sends.

The possible types of event notifications are error, warning, and information. Event notifications are
reported to the SNMP destinations of your choice. To specify an SNMP destination, you must provide a
valid IP address and SNMP community string.

Note: A valid community string can contain up to 60 letters or digits (most characters). A maximum of
six SNMP destinations can be specified.

In configurations that use SNMP, the SAN Volume Controller uses the notifications settings to call home
if errors occur. You must specify Error and send the trap to the IBM System Storage Productivity Center
or the master console if you want the SAN Volume Controller to call home when errors occur.

To configure the SNMP notification settings, use the following commands:

Chapter 3. Using the CLI 77

Procedure
1. To create a new SNMP server to receive notifications, use the mksnmpserver CLI command. For
example, enter one of the following commands:
mksnmpserver -ip 9.11.255.634
where 9.11.255.634 is the IP addresses for this server.
mksnmpserver -ip 9.11.255.634 -port remoteportnumber

where 9.11.255.634 is the IP addresses for this server and remoteportnumber is the port number for the
remote SNMP server.
2. To change the settings of an existing SNMP server, enter the chsnmpserver command. For example:
chsnmpserver -name newserver snmp_server_name_or_id

where newserver is the new name or ID of the server and snmp_server_name_or_id is the name or ID of
the server to be modified.
3. To remove an existing SNMP server from the system, enter the rmsnmpserver command. For example:
rmsnmpserver snmp_server_name_or_id

where snmp_server_name_or_id is either the name or the ID of the SNMP server to be deleted.
4. To display either a concise list or a detailed view of the SNMP servers that are detected by the cluster,
enter the lssnmpserver command. For example, to display a concise view, enter the following
command:
lssnmpserver -delim :

To display a detailed view of an SNMP server, enter the following command:

lssnmpserver snmp_server_name_or_id

Setting up syslog notifications using the CLI

You can set up syslog event notifications using the command-line interface (CLI).

About this task

The syslog protocol is a standard protocol for forwarding log messages from a sender to a receiver on an
IP network. The IP network can be either IPv4 or IPv6. The system can send syslog messages that notify
personnel about an event. The system can transmit syslog messages in either expanded or concise format.
You can use a syslog manager to view the syslog messages that the system sends. The system uses the
User Datagram Protocol (UDP) to transmit the syslog message. You can use the management GUI or the
SAN Volume Controller command-line interface to configure and modify your syslog settings.

The syslog event notification settings apply to the entire cluster. You can specify the types of events that
cause the cluster to send a notification. The possible types of notifications are error, warning, or
information.

To specify a syslog destination, you must provide a valid IP address.

Note: Servers that are configured with facility values of 0 - 3 receive syslog messages in concise format.
Servers that are configured with facility values of 4 - 7 receive syslog messages in fully expanded format.

The SAN Volume Controller uses the notifications settings to call home if errors occur.

To configure and work with notification settings, use the following commands:

78 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Procedure
1. Issue the mksyslogserver CLI command to specify the action that you want to take when a syslog
error or event is logged to the error log. For example, you can issue the following CLI command to
set up a syslog notification:
mksyslogserver -ip 9.11.255.634
where 9.11.255.634 is the IP address of the syslog server.
2. To modify a syslog notification, issue the chsyslogserver command. For example:
chsyslogserver -name -facility facility_number syslog_server_name_or_id
where facility number is a facility number to identify the origin of the message to the receiving server
and syslog_server_name_or_id is the name or ID of the server to be modified.
3. To delete a syslog notification, issue the rmsyslogserver command. For example:
rmsyslogserver syslog_server_name_or_id
4. To display either a concise list or a detailed view of syslog servers that are configured on the cluster,
issue the lssyslogserver command. For example, to display a concise view, enter the following
command:
lssyslogserver -delim :

To display a detailed view of a syslog server, enter the following command:

lssyslogserver snmp_server_name_or_id

Setting up email event notifications and inventory reports using the

CLI
You can use the command-line interface (CLI) to set up your system to send event notification and
inventory reports to specified recipients and the IBM Support Center

Before you begin

About this task

To set up, manage, and activate email event and inventory notifications, complete the following steps:

Procedure
1. Enable your system to use the email notification function. To do this, issue the mkemailserver CLI
command. Up to six SMTP email servers can be configured to provide redundant access to the
external email network.
The following example creates an email server object. It specifies the name, IP address, and port
number of the SMTP email server. After you issue the command, you see a message that indicates
that the email server was successfully created.
mkemailserver -ip ip_address -port port_number

where ip_address specifies the IP address of a remote email server and port_number specifies the port
number for the email server.
2. Add recipients of email event and inventory notifications to the email event notification facility. To do
this, issue the mkemailuser CLI command. You can add up to twelve recipients, one recipient at a
time.
The following example adds email recipient manager2008 and designates that manager2008 receive
email error-type event notifications.
mkemailuser -address [email protected]
-error on -usertype local
3. Set the contact information that is used by the email event notification facility. To do this, issue the
chemail CLI command. If you are starting the email event notification facility, the reply, contact,

Chapter 3. Using the CLI 79

 primary, and location parameters are required. If you are modifying contact information used by the
email event notification facility, at least one of the parameters must be specified.
The following example sets the contact information for the email recipient manager2008.
chemail -reply [email protected] -contact manager2008
-primary 0441234567 -location ’room 256 floor 1 IBM’
4. Optionally, generate a report that lists email event notification settings for all email recipients, or
change or delete email recipients.
v To generate a report that lists the email event notification settings for all email recipients, an
individual email recipient, or a specified type of email recipient (local or support), issue the
lsemailuser CLI command.
v To change the settings that are defined for a recipient, issue the chemailuser CLI command. You
must specify the user ID or name of the email recipient for whom you are modifying settings.
v To remove a previously defined email recipient, issue the rmemailuser CLI command. You must
specify the user ID or name of the email recipient that you want to remove.
5. Activate the email and inventory notification function. To do this, issue the startemail CLI command.
There are no parameters for this command.

Note: Inventory information is automatically reported to IBM when you activate error reporting.
6. Optionally, test the email notification function to ensure that it is operating correctly and send an
inventory email notification.
v To send a test email notification to one or more recipients, issue the testemail CLI command. You
must either specify all or the user ID or user name of an email recipient that you want to send a
test email to.
v To send an inventory email notification to all recipients that are enabled to receive inventory email
notifications, issue the sendinventoryemail CLI command. There are no parameters for this
command.

Setting up email servers using the CLI

You can set up email server objects using the command-line interface (CLI).

About this task

You can specify a server object that describes a remote Simple Mail Transfer Protocol (SMTP) email server
to receive event notifications from the clustered system. You can specify up to six servers to receive
notifications. To configure and work with email servers, use the following commands:

Procedure
1. Issue the mkemailserver CLI command to create an email server object that describes a remote Simple
Mail Transfer Protocol (SMTP) email server. For example, issue the following CLI command to set up
an email server:
mkemailserver -ip ip_address
where ip_address is the IP address of a remote email server. This must be a valid IPv4 or IPv6 address.
2. To change the parameters of an existing email server object, issue the chemailserver command. For
example:
chemailserver -ip ip_address email_server_name_or_id
where ip_address is the IP address of the email server object and email_server_name_or_id is the name or
ID of the server object to be changed.
3. To delete a specified email server object, issue the rmemailserver command. For example:
rmemailserver email_server_name_or_id

80 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 4. To display either a concise list or a detailed view of email servers that are configured on the system,
issue the lsemailserver command. For example, to display a concise view, enter the following
command:
lsemailserver -delim :

To display a detailed view of an email server, enter the following command:

lsemailserver email_server_name_or_id

Changing clustered system passwords using the CLI

You can use the command-line interface (CLI) to change the superuser and service passwords.

About this task

Passwords only affect the management GUI that accesses the clustered system. To restrict access to the
CLI, you must control the list of SSH client keys that are installed on the clustered system.

Perform the following steps to change the superuser and service passwords:

Procedure
1. Issue the following command to change the superuser password:
chuser -password superuser_password superuser
Where superuser_password is the new superuser password that you want to use.
2. Issue the following command to change the service password:
e chsystem -servicepwd service_password
Where service_password is the new service password that you want to use.

Changing the locale setting using the CLI

You can use the command-line interface (CLI) to specify the locale for a SAN Volume Controller cluster.
The language that you select as your locale setting is used to display command results and error
messages in the CLI.

About this task

The following locales are available:

v 0 US English (default)
v 3 Japanese

Procedure

Issue the setlocale CLI command with the ID for the locale.

Example

For example, issue the following CLI command to change the locale setting from US English to Japanese:

setlocale 3

where 3 is the ID for the Japanese locale setting.

Viewing the feature log using the CLI

You can use the command-line interface (CLI) to view the feature log.
Chapter 3. Using the CLI 81
About this task

Perform the following steps to view the feature log:

Procedure
1. Issue the svcinfo lsfeaturedumps command to return a list of dumps in the /dumps/feature
destination directory. The feature log is maintained by the cluster. The feature log records events that
are generated when license parameters are entered or when the current license settings have been
breached.
2. Issue the svcservicemodeinfo lsfeaturedumps command to return a list of the files that exist of the
type specified on the given node.

Analyzing the error log using the CLI

You can use the command-line interface (CLI) to analyze the error log (event log).

About this task

Perform the following step to analyze the error log:

Procedure

Issue the following CLI command to list error log entries by file type: lseventlog

Results

This command lists the error log entries. You can filter by type; for example, lseventlog -filtervalue
object_type=mdisk displays the error log by managed disks (MDisks).

You can display the whole log or filter the log so that only errors, events, or unfixed errors are displayed.
You can also request that the output is sorted either by error priority or by time. For error priority, the
most serious errors are the lowest-numbered errors. Therefore, the most serious errors are displayed first
in the table. For time, either the older or the latest entry can be displayed first in the output.

Shutting down a clustered system using the CLI

You can use the command-line interface (CLI) to shut down a clustered system.

Before you begin

If you want to remove all input power to a clustered system (for example, the machine room power must
be shutdown for maintenance), you must shut down the system before the power is removed. If you do
not shut down the system before turning off input power to the uninterruptible power supply, the SAN
Volume Controller nodes detect the loss of power and continue to run on battery power until all data
that is held in memory is saved to the internal disk drive. This increases the time that is required to make
the system operational when input power is restored and severely increases the time that is required to
recover from an unexpected loss of power that might occur before the uninterruptible power supply
batteries have fully recharged.

When input power is restored to the uninterruptible power supply units, they start to recharge. However,
the SAN Volume Controller nodes do not permit any I/O activity to be performed to the VDisks
(volumes) until the uninterruptible power supply is charged enough to enable all the data on the SAN
Volume Controller nodes to be saved in the event of an unexpected power loss. This might take as long

82 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 as two hours. Shutting down the system prior to removing input power to the uninterruptible power
supply units prevents the battery power from being drained and makes it possible for I/O activity to
resume as soon as input power is restored.

Before shutting down a system, quiesce all I/O operations that are destined for the system. Failure to do
so can result in failed I/O operations being reported to your host operating systems.

Attention: If you are shutting down the entire system, you lose access to all volumes that are provided
by this system. Shutting down the system also shuts down all SAN Volume Controller nodes. This
shutdown causes the hardened data to be dumped to the internal hard drive.

Begin the following process of quiescing all I/O to the system by stopping the applications on your hosts
that are using the volumes that are provided by the system.
1. Determine which hosts are using the volumes that are provided by the system.
2. Repeat the previous step for all volumes.

About this task

If input power is lost and subsequently restored, you must press the power button on the uninterruptible
power supply units before you press the power buttons on the SAN Volume Controller nodes.

Perform the following steps to shut down a system:

Procedure
1. Issue the following command to shut down a clustered system:
e stopsystem

The following output is displayed:

Are you sure that you want to continue with the shut down?

2. Type y to shut down the entire clustered system.

Upgrading the software automatically using the CLI

You can use the command-line interface (CLI) to install software upgrades.

Before you begin

This procedure is for upgrading from SAN Volume Controller version 6.1.0 or later. To upgrade from
version 5.1.x or earlier, see the relevant information center or publications that are available at this
website:

www.ibm.com/storage/support/2145

Attention: Before you start a software upgrade, you must check for offline or degraded volumes. An
offline volume can cause write data that has been modified to be pinned in the SAN Volume Controller
cache. This prevents volume failover and causes a loss of I/O access during the software upgrade. If the
fast_write_state is empty, a volume can be offline and not cause errors during the software upgrade.

About this task

Perform the following steps to upgrade the software:

Chapter 3. Using the CLI 83

Procedure
1. Download, install, and run the latest version of the Software Upgrade Test Utility to verify that there
are no issues with the current clustered system environment. You can download the most current
version of this tool at the following website:
http://www.ibm.com/support/docview.wss?uid=ssg1S4000585
2. Download the SAN Volume Controller code from the www.ibm.com/storage/support/2145.
v If you want to write the SAN Volume Controller code to a CD, you must download the CD image.
v If you do not want to write the SAN Volume Controller code to a CD, you must download the
installation image.
3. Use PuTTY scp (pscp) to copy the software upgrade files to the node.
4. Ensure that the software upgrade file has been successfully copied.
Before you begin the software upgrade, you must be aware of the following:
v The installation process fails under the following conditions:
– If the software that is installed on the remote system is not compatible with the new software or
if there is an intersystem communication error that does not allow the software to check that the
software is compatible.
– If any node in the system has a hardware type that is not supported by the new software.
– If the SAN Volume Controller software determines that one or more volumes in the system
would be taken offline by rebooting the nodes as part of the upgrade process. You can find
details about which volumes would be affected by using the lsdependentvdisks command. If
you are prepared to lose access to data during the upgrade, you can use the force flag to
override this restriction.
v The software upgrade is distributed to all the nodes in the system by using Fibre Channel
connections between the nodes.
v Nodes are updated one at a time.
v Nodes will run the new software concurrently with normal system activity.
v While the node is updated, it does not participate in I/O activity in the I/O group. As a result, all
I/O activity for the volumes in the I/O group is directed to the other node in the I/O group by the
host multipathing software.
v There is a 30-minute delay between node updates. The delay allows time for the host multipathing
software to rediscover paths to the nodes which have been upgraded, so that there is no loss of
access when another node in the I/O group is updated.
v The software update is not committed until all nodes in the system have been successfully updated
to the new software level. If all nodes successfully restart with the new software level, the new
level is committed. When the new level is committed, the system vital product data (VPD) is
updated to reflect the new software level.
v You cannot invoke the new functions of the upgraded software until all member nodes are
upgraded and the update has been committed.
v Because the software upgrade process takes some time, the installation command completes as soon
as the software level is verified by the system. To determine when the upgrade has completed, you
must either display the software level in the system VPD or look for the Software upgrade
complete event in the error/event log. If any node fails to restart with the new software level or
fails at any other time during the process, the software level is backed off.
v During a software upgrade, the version number of each node is updated when the software has
been installed and the node has been restarted. The system software version number is updated
when the new software level is committed.
v When the software upgrade starts an entry is made in the error or event log and another entry is
made when the upgrade completes or fails.
5. Issue the following CLI command to start the software upgrade process:
applysoftware -file software_upgrade_file

84 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 where software_upgrade_file is the name of the software upgrade file.If the system identifies any
volumes that would go offline as a result of rebooting the nodes as part of the system upgrade, the
software upgrade does not start. An optional force parameter can be used to indicate that the
upgrade continue in spite of the problem identified. Use the lsdependentvdisks command to identify
the cause for the failed upgrade. If you use the force parameter, you are prompted to confirm that
you want to continue. The behavior of the force parameter has changed, and it is no longer required
when applying an upgrade to a system with errors in the event log.
6. Issue the following CLI command to check the status of the software upgrade process:
lssoftwareupgradestatus

This command displays inactive when the upgrade is complete.

Note: If a status of stalled_non_redundant is displayed, proceeding with the remaining set of node
upgrades might result in offline volumes. Contact an IBM service representative to complete the
upgrade.
7. To verify that the software upgrade successfully completed, issue the lsnodevpd CLI command for
each node that is in the system. The software version field displays the new software level.

Results

When a new software level is applied, it is automatically installed on all the nodes that are in the system.

Note: The software upgrade can take up to 30 minutes per node.

Chapter 3. Using the CLI 85

86 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 4. Overview of the dumps commands
The lsdumps command returns a list of dumps in a particular directory.

Dumps are contained in the following directory structure:

v /dumps
v /dumps/audit
v /dumps/cimom
v /dumps/elogs
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/mdisk
v /home/admin/upgrade
v /dumps/drive
v /dumps/enclosure

Use the lsdumps command with the optional prefix parameter to specify a directory. If you do not
specify a directory, /dumps is used as the default. Use the optional node_id_or_name parameter to specify
the node to list the available dumps for. If you do not specify a node, the available dumps on the
configuration node are listed.

An audit log keeps track of action commands that are issued through an SSH session or from the
management GUI. To list a specified number of the most recently audited commands, issue the
catauditlog command. To dump the contents of the audit log to a file on the current configuration node,
issue the dumpauditlog command. This command also clears the contents of the audit log.

Dumps contained in the /dumps/cimom directory are created by the CIMOM (Common Information Model
Object Manager) that runs on the clustered system (system). These files are produced during normal
operations of the CIMOM.

Dumps that are contained in the /dumps/elogs directory are dumps of the contents of the error and event
log at the time that the dump was taken. An error or event log dump is created by using the dumperrlog
command. This dumps the contents of the error or event log to the /dumps/elogs directory. If no file
name prefix is supplied, the default errlog_ is used. The full default file name is
errlog_NNNNNN_YYMMDD_HHMMSS, where NNNNNN is the node front panel name. If the command
is used with the -prefix parameter, the prefix value is used instead of errlog.

Dumps contained in the /dumps/feature directory are dumps of the featurization log. A featurization log
dump is created by using the dumpinternallog command. This dumps the contents of the featurization
log to the /dumps/feature directory to a file called feature.txt. Only one of these files exists, so every
time the dumpinternallog command is run, this file is overwritten.

Dumps that are contained in the /dumps/iostats directory are dumps of the per-node I/O statistics for
disks on the system. An I/O statistics dump is created by using the startstats command. As part of this
command, you can specify a time interval for the statistics to be written to the file; the default is 15
minutes. Every time the time interval is encountered, the I/O statistics that have been collected are
written to a file in the /dumps/iostats directory. The file names that are used for storing I/O statistics
dumps are Nm_stats_NNNNNN_YYMMDD_HHMMSS, Nv_stats_NNNNNN_YYMMDD_HHMMSS,

© Copyright IBM Corp. 2003, 2012 87

Nn_stats_NNNNNN_YYMMDD_HHMMSS, and Nd_stats_NNNNNN_YYMMDD_HHMMSS, where
NNNNNN is the node name for the MDisk, VDisk, node, or drive.

Dumps that are contained in the /dumps/iotrace directory are dumps of I/O trace data. The type of data
that is traced depends on the options specified by the settrace command. The collection of the I/O trace
data is started by using the starttrace command. The I/O trace data collection is stopped when the
stoptrace command is used. It is when the trace is stopped that the data is written to the file. The file
name is prefix_NNNNNN_YYMMDD_HHMMSS, where prefix is the value entered for the filename
parameter in the settrace command, and NNNNNN is the node name.

Dumps that are contained in the /dumps/mdisk directory are copies of solid-state drive (SSD) MDisk
internal logs. These dumps are created using the triggerdrivedump command. The file name is
mdiskdump_NNNNNN_MMMM_YYMMDD_HHMMSS, where NNNNNN is the name of the node that
contains the MDisk, and MMMM is the decimal ID of the MDisk.

Software upgrade packages are contained in the /home/admin/upgrade directory. These directories exist on
every node in the system.

Dumps of support data from a disk drive are contained in the /dumps/drive directory. This data can help
to identify problems with the drive, and does not contain any data that applications may have written to
the drive.

Dumps from an enclosure or enclosures are contained in the /dumps/enclosure directory.

Dumps that are contained in the /dumps directory result from application abends. Such dumps are written
to the /dumps directory. The default file names are dump.NNNNNN.YYMMDD.HHMMSS, where NNNNNN
is the node front panel name. In addition to the dump file, there might be some trace files written to this
directory that are named NNNNNN.trc.

Because files can only be copied from the current configuration node (using secure copy), you can issue
the cpdumps command to copy the files from a nonconfiguration node to the current configuration node.

88 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 5. Array commands
Array commands capture information that can assist you with managing arrays.

charray
Use the charray command to change array attributes.

Syntax


charray

-name new_name_arg -sparegoal 0-100 -balanced

mdisk_id | mdisk_name


Parameters
-name
(Optional) The new name to apply to the array MDisk.
-sparegoal
(Optional) Sets the number of spares to protect the array members with.
-balanced
(Optional) Forces the array to balance and configure the spare goals of the present drives.
mdisk_id
Identifies (by ID) which array the MDisk command applies to.
mdisk_name
Identifies (by user-defined name) which array the MDisk command applies to.

Description

This command changes an array's attributes.

Invocation examples
charray -name raid6mdisk0 0
charray -sparegoal 2
charray -balanced 3

The resulting output

No feedback

charraymember
Use the charraymember command to modify an array member's attributes, or to swap a member of a
RAID array with that of another drive.

© Copyright IBM Corp. 2003, 2012 89

Syntax


charraymember -member member_id -balanced mdisk_id

-newdrive new_drive_id mdisk_name
-immediate -unbalanced

Parameters
-member
Identifies the array member index to operate on.
-balanced
(Optional) Forces the array member spare goals to be set to the:
v Present array member goals
v Existing exchange goals
v The newDrive goals
-newdrive
(Optional) Identifies the drive to add to the array.
-immediate
(Optional) Specifies that the old disk is to be immediately removed from the array, and the new disk
rebuilt. If you do not choose this option, exchange is used; this preserves redundancy during the
rebuild.
-unbalanced
(Optional) Forces the array member to change if the newDrive does not meet array member goals.
mdisk_id
(Either the ID or the name is required.) Identifies which ID array the MDisk command applies to.
mdisk_name
(Either the ID or the name is required.) Identifies which name array the MDisk command applies to.

Description

This command modifies an array member's attributes, or to swap a member of a RAID array with that of
another drive. Table 10 shows the command combination options.
Table 10. charraymember combination options
Option Description
-balanced v Member goals are set to the properties of the existing member or exchange drive.
v The command will fail if the member is not populated with a drive.
v Member goals are set to the properties of the current member drives being
exchanged into the array count as members.
v If no exchange exists, the existing member drive goals are used.
-newdrive drive_id v The command processes the exchange, and does NOT update the member goals.
v You must specify a new drive that is an exact match for the member goals.
v The command will fail if the drive is not an exact match.
-newdrive drive_id -balanced The processes the exchange and updates the member goals to the properties of the
new drive.

90 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 10. charraymember combination options (continued)
Option Description
-newdrive drive_id v The command processes the exchange and does NOT update the member goals.
-unbalanced
v This is only permitted when the array is degraded and the member is empty.
v This means -immediate is mute, the exchange will always be immediate.
v Later, if drives are a sufficient member goal match, the array rebalance will select
those drives.
v A balancing exchange will restart the member goals.

An invocation example

To swap a spare/candidate drive for a member 0 drive using exchange:

charraymember -member 0 -newdrive 4 mdisk2

An invocation example

To swap a spare/candidate drive for a member 1 drive and start component rebuild for the new member:
charraymember -member 1 -newdrive 3 -immediate mdisk3

An invocation example

To swap in a spare/candidate drive for member index 2. If there is an drive present there then the
exchange is:
charraymember -member 2 -newdrive 4 mdisk4

An invocation example

To force member 4 to change its spare goals to its associated drive:

charraymember -member 4 -balanced mdisk6

An invocation example

To force an exchange and make the array change its goals to the new drive:
charraymember -member 3 -newdrive 9 -balanced mdisk5

An invocation example

To force an unbalancing exchange when drive 8 does not match the goals:
charraymember -member 2 -newdrive 8 -unbalanced mdisk5

An invocation example

To force an immediate exchange and make the array change its goals to the new drive:
charraymember -member 3 -newdrive 9 -balanced -immediate mdisk5

lsarray
Use the lsarray command to list the array MDisks.

Chapter 5. Array commands 91

 Syntax


lsarray

-filtervalue attribute=value -bytes
-unit b
kb
mb
gb
pb
tb


mdisk id mdisk_name

Parameters
-filtervalue attribute=value
e (Optional) Specifies a list of one or more filter attributes matching the specified values; see
e -filtervalue? for the supported attributes. Only objects with a value that matches the filter attribute
e value are returned. If capacity is specified, the units must also be included. Use the unit parameter to
e interpret the value for size or capacity.

e Note: Some filters allow the use of a wildcard when entering the command. The following rules
e apply to the use of wildcards with the SAN Volume Controller CLI:
e v The wildcard character is an asterisk (*).
e v The command can contain a maximum of one wildcard, which must be the first or last character in
e the string.
e v When using a wildcard character, you must enclose the filter entry within double quotation marks
e (""), as follows:
e lsarray -filtervalue "name=md*"
e -filtervalue?
(Optional) Includes all of the valid filter attributes in the report. The following filter attributes are
valid for the lsarray command:
v mdisk_id
v mdisk_name
v status
v mode
v mdisk_grp_id
v mdisk_grp_name
v capacity
v fast_write_state
v raid_status
v raid_level
v redundancy
v strip_size
v write_verify
v spare_goal
v spare_protection_min
v balanced
v tier

92 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Any parameters specified with the -filtervalue? parameter are ignored.

e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-bytes
(Optional) Requests output of capacities in bytes (instead of rounded values).
mdisk_id
(Optional) The identity of the array MDisk.
mdisk_name
(Optional) The MDisk name that you provided.

Description

This command returns a concise list or a detailed view of array MDisks visible to the clustered system
(system). The lsmdisk command provides the potential output for array MDisks.
Table 11. MDisk output
Attribute Values
status v online
v offline
v excluded
v degraded (applies only to internal MDisks)
mode unmanaged, managed, image, array
quorum_index 0, 1, 2, or blank if the MDisk is not being used as a quorum disk
block_size 512, 524 bytes in each block of storage
ctrl_type 4, 6, where 6 is a solid-state drive (SSD) attached inside a node and 4 is any other
device
tier The tier this MDisk has been assigned to by auto-detection (for internal arrays) or
by the user:
v generic_ssd
v generic_hdd (the default value for newly discovered or external MDisk)
Note: You can change this value using the chmdisk command.
raid_status v offline - the array is offline on all nodes
v degraded - the array has deconfigured or offline members; the array is not fully
redundant
v syncing - array members are all online, the array is syncing parity or mirrors to
achieve redundancy
v initting - array members are all online, the array is initializing; the array is fully
redundant
v online - array members are all online, and the array is fully redundant
raid_level The RAID level of the array (RAID0, RAID1, RAID5, RAID6, RAID10).
redundancy The number of how many member disks can fail before the array fails.
strip_size The strip size of the array (in KB).
spare_goal The number of spares that the array members should be protected by.
spare_protection_min The minimum number of spares that an array member is protected by.

Chapter 5. Array commands 93

Table 11. MDisk output (continued)
Attribute Values
balanced Describes if the array is balanced to its spare goals:
v exact: all populated members have exact capability match, exact location match
v yes: all populated members have at least exact capability match, exact chain, or
different enclosure or slot
v no: anything else

The following define the status fields:

Online
The MDisk is online and available.
Degraded
(Internal MDisks only) The array has members that are degraded, or the raid_status is degraded.
Offline
All paths to the MDisk are lost.
Excluded
The MDisk is excluded from use by the clustered system (system); the MDisk port error count
exceeded the threshold.

A concise invocation example

lsarray -delim :

The resulting output

mdisk_id:mdisk_name:status:mdisk_grp_id:mdisk_grp_name:capacity:raid_status:
raid_level:redundancy:strip_size:tier
1:mdisk1:online:0:mdiskgrp0:68.4GB:online:raid0:0:256:generic_hdd
2:mdisk2:online:0:mdiskgrp0:88.4GB:syncing:raid5:1:256:generic_hdd
533:mdisk533:degraded:1:mdiskgrp1:78.2GB:syncing:raid6:2:128:generic_hdd
534:mdisk534:online:2:mdiskgrp1:94.2GB:initting:raid6:2:64:generic_ssd

A full invocation example

lsarray mdisk1

The resulting output

mdisk_id:1
mdisk_name:mdisk1
status:online
mode:array
mdisk_grp_id:0
mdisk_grp_name:mdiskgrp0
capacity:68.4GB
quorum_index:
block_size:
controller_name:
ctrl_type:
ctrl_WWNN:
controller_id:
path_count:
max_path_count:
ctrl_LUN_#:
UID:
preferred_WWPN:
active_WWPN:
fast_write_state:empty
raid_status:online
raid_level:raid0

94 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
redundancy:0
strip_size:256
spare_goal:2
spare_protection_min:2
balanced:yes
tier:generic_hdd

lsarrayinitprogress
Use the lsarrayinitprogress command to view the progress of array background initialization that
occurs after creation.

Syntax


lsarrayinitprogress

mdisk id | mdisk_name

Parameters
mdisk_id
(Optional) The identity of the array MDisk.
mdisk_name
(Optional) The user-defined MDisk name.

Description

This command shows the progress of array background initialization. Table 12 shows possible outputs.
Table 12. lsarrayinitprogress output
Attribute Value
progress The percentage of initialization task that has been completed.
estimated_completion_time The expected initialization task completion time (YYMMDDHHMMSS).

A concise invocation example

lsarrayinitprogress –delim :

The resulting output

mdisk_id:mdisk_name:progress:estimated_completion_time
0:mdisk0:50:070301120000
1:mdisk1:51:070301130000
2:mdisk2:32:070301153500

A concise invocation (qualified with MDisk) example

lsarrayinitprogress –delim : mdisk2

The resulting output

mdisk_id:mdisk_name:progress:estimated_completion_time
2:mdisk2:32:070301153500

An invocation example for an array that has finished initialization

lsarrayinitprogress –delim : mdisk4

The resulting output

Chapter 5. Array commands 95

mdisk_id:mdisk_name:progress:estimated_completion_time
4:mdisk4:100:

lsarraylba
Use the lsarraylba command to permit an array logical block address (LBA) to be found from a drive
and LBA.

Syntax


lsarraylba -drivelba lba -drive drive_id

-delim delimiter

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-drivelba
The LBA on the drive to convert to the array LBA. The LBA must be specified in hex, with a 0x
prefix.
-drive
The ID of the drive to view.

Description

This command permits an array LBA to be found on a drive and LBA.Table 13 shows possible outputs.
Table 13. lsarraylba output
Attribute Value
type The type of MDisk extent allocation:
v allocated
v unallocated
mdisk_lba The LBA on the array MDisk (blank if none).
mdisk_start The start of range of LBAs (strip) on the array MDisk (blank if none).
mdisk_end The end of range of LBAs (strip) on the array MDisk (blank if none).
drive_start The start of range of LBAs (strip) on the drive (blank if none).
drive_end The end of range of LBAs (strip) on the drive (blank if none).

This example demonstrates how drive 2 LBA -xff maps to MDisk 2 LBA 0xff.

An invocation example
lsarraylba -delim : -drivelba 0xff -drive 2

The resulting output

96 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
mdisk_id:mdisk_name:type:mdisk_lba:mdisk_start:mdisk_end:drive_start:drive_end
0:mdisk2:allocated:0x00000000000001ff:0x0000000000000100:0x00000000000001ff:
0x0000000000000000:0x00000000000000ff

lsarraymember
Use the lsarraymember command to list the member drives of one or more array MDisks.

Syntax


lsarraymember

-delim delimiter -bytes mdisk_id mdisk_name

Parameters
-delim delimiter
(Optional) By default, in a concise view all columns of data are space-separated, with the width of
each column set to the maximum possible width of each item of data. In a detailed view, each item of
data is an individual row, and if displaying headers, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. Enter -delim : on the command line, and the colon character (:) separates all
items of data in a concise view (for example, the spacing of columns does not occur); in a detailed
view, the specified delimiter separates the data from its header
-bytes
(Optional) Requests output of capacities in bytes (instead of rounded values).
mdisk_id
(Optional) The identity of the array MDisk.
mdisk_name
(Optional) The MDisk name that you provided.

Description

This command lists the member drives of one or more array MDisks. It describes positions within an
array not occupied by a drive. The positions determine how mirroring the RAIDs takes place; for
example, determining if x is mirrored to y for RAID-10, where parity starts from RAID-5.

Table 14 provides the potential output for this command.

Table 14. lsarraymemberoutput
Attribute Value
member_id The identity of the array member; represents drive order in RAID array
drive_id The identity of the drive for member ID, or the source drive if an exchange is in
progress (blank if there is none configured).
new_drive_id The ID of the drive being exchanged with this member ID (blank if there is none)
spare_protection The number of spares protecting the array member
balanced If the array member drive matches the spare goals:
v exact - exact capability match, exact location match
v yes - exact capability match, exact chain, different enclosure or slot
v no - anything else
v (blank) - there is no drive configured for the member

Chapter 5. Array commands 97

A concise invocation example
lsarraymember -delim :

The resulting output

lsarraymember -delim :
mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced
2:mdisk1:0:55::1:exact
2:mdisk1:1:56::1:exact
2:mdisk2:0:0::2:exact
2:mdisk2:1:2:5:3:exact
2:mdisk2:2::::
2:mdisk2:3:8::0:no

A concise invocation example (qualified with MDisk)

lsarraymember mdisk2 -delim :

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced
2:mdisk2:0:0::2:exact
2:mdisk2:1:2:5:3:exact
2:mdisk2:2::::
2:mdisk2:3:8::0:no

Note: From this output, you can see that:

v The array has four members (possibly a 4-member RAID-10 array).
v The second array member is undergoing exchange for drive5.
v The third array member is not configured. It might have gone offline or failed, without a hot spare
available.
v The fourth array member has no spare protection and is not balanced.

An invocation example (two arrays)

lsarraymember -delim :

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced
2:mdisk1:0:55:::1:exact
2:mdisk1:1:56:::1:exact
2:mdisk2:0:0:::2:exact
2:mdisk2:1:2:5::3:exact
2:mdisk2:2:::::
2:mdisk2:3:8:::0:no

An invocation example (an array expanding from membership (55,56) to (55,57,58))

lsarraymember -delim : mdisk3

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced
3:mdisk3:0:55::55:1:exact
3:mdisk3:1:56::57:1:exact
3:mdisk3:2:::58:1:exact

An invocation example (an array contracting from membership (55,57,58) to (55,56))

lsarraymember -delim : mdisk3

The resulting output

98 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced
3:mdisk3:0:55::55:1:exact
3:mdisk3:1:57::56:1:exact
3:mdisk3:2:58:::1:exact

lsarraymembergoals
Use the lsarraymembergoals command to list the spare goals for member drives of one or more array
MDisks.

Syntax


lsarraymembergoals

-delim delimiter -bytes mdisk_ id mdisk_name

Parameters
-delim delimiter
(Optional) By default, in a concise view all columns of data are space-separated, with the width of
each column set to the maximum possible width of each item of data. In a detailed view, each item of
data is an individual row, and if displaying headers, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. Enter -delim : on the command line, and the colon character (:) separates all
items of data in a concise view (for example, the spacing of columns does not occur); in a detailed
view, the data is separated from its header by the specified delimiter.
-bytes
(Optional) Requests output of capacities in bytes (instead of rounded values).
mdisk_id
(Optional) The identity of the array MDisk.
mdisk_name
(Optional) The MDisk name that you provided.

Description

This command lists the spare goals for member drives of one or more array MDisks. Table 15 provides
the potential output for this command.
Table 15. lsarraymembergoals output
Attribute Values
member_id The ID of the array member which represents the drive order in the RAID array.
drive_id The ID of the drive for the member ID (blank if none is configured).
capacity_goal The capacity goal for the array member (same for all members in the array).
tech_type_goal The technology goal for the array member:
v sas_ssd
v sas_hdd
v sas_nearline_hdd
RPM_goal The RPM goal for array member (blank for SSDs).
enclosure_id_goal The ID of the member enclosure goal (blank if any can be selected).
slot_id_goal The ID of the member slot goal.
node_id_goal The node ID of the goal.

Chapter 5. Array commands 99

An invocation example (a four-member RAID 10 SAS array that is split across chains)
lsarraymembergoals mdisk2 -delim :

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:capacity_goal:
tech_type_goal:RPM_goal:enclosure_id_goal:slot_id_goal
2:mdisk2:0:0:68.4GB:sas_hdd:15000:1:1
2:mdisk2:1:17:68.4GB:sas_hdd:15000:1:2
2:mdisk2:2:1:68.4GB:sas_hdd:15000:14:1
2:mdisk2:3:18:68.4GB:sas_hdd:15000:14:2

An invocation example (a six-member RAID 10 SAS or SATA array )

lsarraymembergoals -delim : mdisk3

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:capacity_goal:
tech_type_goal:RPM_goal:enclosure_id_goal:slot_id_goal
3:mdisk3:0:10:155.0GB:sas_ssd::1:4
3:mdisk3:1:21:155.0GB:sas_hdd:15000:2:3
3:mdisk3:2:12:155.0GB:sas_nearline_hdd:7200:7:3
3:mdisk3:4:23:155.0GB:sas_ssd::2:2
3:mdisk3:5:14:155.0GB:sas_nearline_hdd:7200:9:3
3:mdisk3:6:25:155.0GB:sas_hdd:15000:2:8

An invocation example (a four-member RAID 0 SAS array contained within a single enclosure)
lsarraymembergoals -delim : mdisk4

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:capacity_goal:
tech_type_goal:RPM_goal:enclosure_id_goal:slot_id_goal
2:mdisk2:0:0:222.0GB:sas_nearline_hdd:15000:1:1
2:mdisk2:1:1:222.0GB:sas_nearline_hdd:15000:1:2
2:mdisk2:2:2:222.0GB:sas_nearline_hdd:15000:1:3
2:mdisk2:3:3:222.0GB:sas_nearline_hdd:15000:1:4

lsarraymemberprogress
Use the lsarraymemberprogress command to display array member background process status.

Syntax


lsarraymemberprogress

mdisk id mdisk_name

Parameters
mdisk_id
(Optional) The identity of the array MDisk.
mdisk_name
(Optional) The MDisk name that you provided.

Description

This command displays array member background process status. Exchange cannot start on a rebuilding
member because both component rebuild and exchange are shown in the same view. Table 16 on page
101 provides the potential output for this command.

100 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 16. lsarraymemberprogress output
Attribute Value
member_id The array member index.
drive_id The ID of the drive.
task The identity of task:
v rebuild
v exchange
new_drive_id The identity of drive being exchanged.
progress The task percentage complete.
estimated_completion_time The expected task completion time (YYMMDDHHMMSS; blank if completion
time unknown).

A concise invocation example

lsarraymemberprogress –delim :

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:task:new_drive_id:progress:estimated_completion_time
0:mdisk0:2:3:rebuild::50:070301120000
1:mdisk1:0:5:rebuild::51:070301130000
2:mdisk2:4:1:exchange:12:32:070301153500
2:mdisk2:5:16:exchange:13:0:
2:mdisk2:5:17:exchange:14:0:

An MDisk qualified concise example

lsarraymemberprogress mdisk2

The resulting output

mdisk_id:mdisk_name:member_id:drive_id:task:new_drive_id:progress:estimated_completion_time
2:mdisk2:4:1:exchange:12:32:070301153500
2:mdisk2:5:16:exchange:13:0:
2:mdisk2:5:17:exchange:14:0:

lsarraysyncprogress
The lsarraysyncprogress command displays how synchronized a RAID array is.

Syntax


lsarraysyncprogress

mdisk_id
mdisk_name

Parameters
mdisk_id
(Optional) The ID of the MDisk you want to view.
mdisk_name
(Optional) The user-defined name of the MDisk you want to view.

Chapter 5. Array commands 101

Description

This command shows you how synchronized a RAID array is. It includes internal activity that is working
toward a fully synchronized array. Table 17 provides the potential output.
Table 17. lsarraysyncprogress output
Attribute Value
progress The percentage of the array that is synchronized.
estimated_completion_time The expected synchronization completion time (YYMMDDHHMMSS; blank if
completion time unknown).

A concise invocation example

lsarraysyncprogress –delim :

The resulting output

mdisk_id:mdisk_name:progress:estimated_completion_time
0:mdisk0:50:070301120000
1:mdisk1:51:070301130000
2:mdisk2:32:070301153500

A concise view (qualified with mdisk id for mdisk2) invocation example

lsarraysyncprogress –delim : mdisk2

The resulting output

mdisk_id:mdisk_name:progress:estimated_completion_time
2:mdisk2:32:070301153500

A concise view (qualified with mdisk id for in sync mdisk10) invocation example
lsarraysyncprogress –delim : mdisk10

The resulting output

mdisk_id:mdisk_name:progress:estimated_completion_time
0:mdisk0:100:

mkarray
Use the mkarray command to create an MDisk array and add it to a storage pool.

Syntax


mkarray -level raid0 -drive drive_id_list

raid1 -strip 128
raid10 256

mdiskgrp_id

-sparegoal 0-(MAX_DRIVES-1) -name new_name_arg mdiskgrp_name

Parameters
-level
Sets the RAID level for the array MDisk being created.
-drive
Identifies the drive or drives to use as members of the RAID array.

102 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Drives are specified as a sequence of mirrored drive pairs. For example, if an array is created with
-drive a:b:c:d, drive b contains the mirror copy of drive a, and drive d contains the mirror copy of
drive c.
The following requirements apply for certain RAID levels:
v RAID-0: All drives in a RAID-0 array of internal drives must be located in the same node.
v RAID-1: The pair of drives must contain one drive from one node in the I/O group, and one drive
from the other node.
v RAID-10: The drives are specified as a sequence of drive pairs. Each pair of drives must contain
one drive from a node in the I/O group, and a drive from the other node.
-strip
(Optional) Sets strip size (in kilobytes) for the array MDisk being created. The default is 256 KB.
-sparegoal
(Optional) Sets the number of spares that this array's members should be protected by. The default is
1 (except for RAID 0 arrays, which have a default of 0).
-name
(Optional) Specifies the name to which you want to apply the array MDisk.
mdiskgrp_id
Identifies the storage pool (by ID) to which you want to add the created array mdisk.
mdiskgrp_name
Identifies storage pool (by the user-defined name) to which you want to add created array MDisks.

Description

This command creates an array MDisk RAID array and adds it to an storage pool. Although the array's
tier is automatically determined, you can change it later using the chmdisk command.

Standard output
MDisk, id [x], successfully created

An invocation example (to create arrays)

mkarray -level raid0 -drive 0:1:2:3 raid0grp

The resulting output

MDisk, id [0], successfully created

An invocation example (to create fully redundant arrays)

mkarray -level raid1 -drive 4:5 -strip 128 mdiskgrp4

The resulting output

MDisk, id [1], successfully created

recoverarray
Use the recoverarray command to recover a specific corrupt array in a dead domain scenario.

Syntax


recoverarray mdisk_id mdisk_name


Chapter 5. Array commands 103

 Parameters
mdisk_id
Identifies (by ID) the specific array to recover.
mdisk_name
Identifies (by user-assigned name) the specific array to recover.

Description

This command recovers a specific corrupt array. An array has metadata representing ongoing/pending
platform writes, which are lost when the domain nodes are lost.

An invocation example
recoverarray mdisk1

The resulting output

There is no output if the command is successful.

1 recoverarraybycluster
1 Attention: The recoverarraybycluster command has been discontinued. Use the recoverarraybysystem
1 command instead.
1
recoverarraybysystem
Use the recoverarraybysystem command to recover a specific corrupt array in a dead domain scenario.

Syntax


recoverarraybysystem


Parameters

None.

Description

Use the recoverarraybysystem command to recover a specific corrupt array in a dead domain scenario.

An invocation example
recoverarraybysystem

The resulting output

There is no output if the command is successful.

rmarray
Use the rmarray command to remove an array MDisk from the configuration.

104 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


rmarray -mdisk mdisk_id_list mdisk_group_id

mdisk_name_list -force mdisk_group_name

Parameters
-mdisk
Identifies the array MDisk or MDisks to remove from the storage pool
-force
(Optional) Forces a remove when the MDisk has allocated extents by migrating the used extents to
free extents in the storage pool
mdiskgrp_id
Identifies (by ID) the MDisk group to remove the created array MDisk from.
mdiskgrp_name
Identifies (by user-defined name) the MDisk group to remove the created array MDisk from.

Description

This command removes an array MDisk from the configuration. Each array is divided into candidate
drives.

An invocation example
rmarray -mdisk 6 mdiskgrp10

The resulting output

No feedback

Chapter 5. Array commands 105

106 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 6. Audit log commands
An audit log keeps track of action commands that are issued through a Secure Shell (SSH) session or
through the management GUI.

The audit log entries provide the following information:

v Identity of the user who issued the action command
v The name of the actionable command
v The timestamp of when the actionable command was issued on the configuration node
v The parameters which were issued with the actionable command
The following commands are not documented in the audit log:
v dumpconfig
v cpdumps
v cleardumps
v finderr
v dumperrlog
v dumpinternallog
v svcservicetask dumperrlog
v svcservicetask finderr
The following items are also not documented in the audit log:
v Commands that fail are not logged
v A result code of 0 (success) or 1 (success in progress) is not logged
v Result object ID of node type (for the addnode command) is not logged
v Views are not logged

catauditlog
Use the catauditlog command to display the in-memory contents of the audit log.

Syntax


catauditlog

-delim delimiter -first number_of_entries_to_return

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-first number_of_entries_to_return
(Optional) Specifies the number of most recent entries to display.

© Copyright IBM Corp. 2003, 2012 107

Description

This command lists a specified number of the most recently audited commands.

The in-memory portion of the audit log holds approximately 1 MB of audit information. Depending on
the command text size and the number of parameters, this equals 1 MB records or approximately 6000
commands.

Once the in-memory audit log reaches maximum capacity, the log is written to a local file on the
configuration node in the /dumps/audit directory. The catauditlog command only displays the
in-memory part of the audit log; the on-disk part of the audit log is in readable text format and does not
require any special command to decode it.

The in-memory log entries are reset and cleared automatically, ready to accumulate new commands. The
on-disk portion of the audit log can then be analyzed at a later date.

The lsdumps command with -prefix /dumps/audit can be used to list the files on the disk.

The dumpauditlog command transfers the on-memory portion of the audit log to an on-disk file, clearing
the in-memory portion of the log.

This example lists the five most recent audit log entries.

An invocation example
catauditlog -delim : -first 5

The resulting output

audit_seq_no:timestamp:cluster_user:ssh_ip_address:result:res_obj_id:action_cmd
35:091012114520:superuser:9.20.160.249:0::dumpauditlog
36:091012115150:superuser:9.20.160.249:0::chquorum -mdisk 45 3
37:091012115256:superuser:9.20.160.249:0::chvdisk -name vdisk_master 1
38:091012115302:superuser:9.20.160.249:0::chvdisk -name vdisk_aux 2
39:091012115328:superuser:9.20.160.249:0::chvdisk -name disk 3

dumpauditlog
Use the dumpauditlog command to reset or clear the contents of the in-memory audit log. The contents
of the audit log are sent to a file in the /dumps/audit directory on the current configuration node.

Syntax


dumpauditlog


Parameters

There are no parameters.

Description

This command dumps the contents of the audit log to a file on the current configuration node. It also
clears the contents of the audit log. This command is logged as the first entry in the new audit log.

Audit log dumps are automatically maintained in the /dumps/audit directory. The local file system
space is used by audit log dumps and is limited to 200 MB on any node in the clustered system (system).
The space limit is maintained automatically by deleting the minimum number of old audit log dump files

108 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
so that the /dumps/audit directory space is reduced below 200 MB. This deletion occurs once per day on
every node in the system. The oldest audit log dump files are considered to be the ones with the lowest
audit log sequence number. Also, audit log dump files with a cluster ID number that does not match the
current one are considered to be older than files that match the system ID, regardless of sequence
number.

Other than by running dumps (or copying dump files among nodes), you cannot alter the contents of the
audit directory. Each dump file name is generated automatically in the following format:
auditlog_firstseq_lastseq_timestamp_systemid

where
v firstseq is the audit log sequence number of the first entry in the log
v lastseq is the audit sequence number of the last entry in the log
v timestamp is the timestamp of the last entry in the audit log that is being dumped
v systemid is the system ID at the time that the dump was created
The audit log dump files names cannot be changed.

The audit log entries in the dump files contain the same information as displayed by the catauditlog
command; however, the dumpauditlog command displays the information with one field per line. The
lsauditlogdumps command displays a list of the audit log dumps that are available on the nodes in the
system.

An invocation example
dumpauditlog

The resulting output

No feedback

lsauditlogdumps (Deprecated)
Attention: The lsauditlogdumps command is deprecated. Use the lsdumps command to display a list of
files in a particular dumps directory.

Deprecated.

Chapter 6. Audit log commands 109

110 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 7. Backup and restore commands
The following commands are used for backing up and restoring configuration information with the SAN
Volume Controller.

backup
Use the backup command to back up the configuration. Enter this command any time after creating
clustered system (system).

Syntax


svcconfig backup

-quiet off
-v on

Parameters
-quiet
Suppresses standard output (STDOUT) messages from the console.
-v on | off
Displays normal (off, the default state) or verbose (on) command messages.

Description

The backup command extracts and stores configuration information from the system. The backup
command produces the svc.config.backup.xml, svc.config.backup.sh, and svcconfig.backup.log files, and
saves them in the /tmp folder. The .xml file contains the extracted configuration information; the .sh file
contains a script of the commands used to determine the configuration information; and the .log file
contains details about command usage.

Note: If a previous svc.config.backup.xml file exists in the /tmp folder, it is archived as

svc.config.backup.bak; only one archive file is stored in the /tmp folder.

The underscore character (_) prefix is reserved for backup and restore command usage; do not use the
underscore character in any object names.

An invocation example
svcconfig backup

The resulting output

No feedback

clear
Use the clear command to erase files in the /tmp directory that were previously produced by other
svcconfig commands. You can enter this command any time after a clustered system (system) has been
created.

© Copyright IBM Corp. 2003, 2012 111

Syntax


svcconfig clear

-all -q -v on
-quiet off

Parameters
-all
Erases all configuration files.
-q | quiet
Suppresses console output (STDOUT).
-v on | off
Produces verbose output (on); the default is regular output (off).

Description

This command erases configuration files on the current config node.

You can use the svcconfig clear command without the -all parameter to erase files of the form:
/tmp/svc.config*.sh
/tmp/svc.config*.log

You can use the svcconfig clear command with the -all parameter to erase files of the form:
/tmp/svc.config*.sh
/tmp/svc.config*.log
/tmp/svc.config*.xml
/tmp/svc.config*.bak

An invocation example
svcconfig clear -all

The resulting output

No feedback

help
Use the help command to obtain summary information about the syntax of the svcconfig command. You
can enter this command any time after a clustered system (system) has been created.

Syntax


svcconfig -ver -?

backup -h
clear
restore

Parameters
-ver
Returns the version number for the svcconfig command.
(action) -h | -?
Provides command help: the possible values for (action) are backup, clear, and restore.

112 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-h | -?
Provides general help.

Description

This command provides syntax help for svcconfig.

An invocation example
svcconfig -ver
svcconfig -?
svcconfig backup -h

The resulting output

The help text displays.

restore
The restore command uses the configuration files in the /tmp folder to restore the clustered system
(system) to its previous configuration.

Syntax


svcconfig restore

-f -q -prepare
-force -quiet -fmt
-fmtdisk
-execute
-fmt
-fmtdisk


off
-v on

Parameters
-f | force
Forces continued processing where possible.
-q | quiet
Suppresses console output (STDOUT).
-prepare
Verifies the current configuration against the information in svc.config.backup.xml; then prepares
commands for processing in svc.config.restore.sh, and then produces a log of events in
svc.config.restore.prepare.
-fmt | fmtdisk
Includes the -fmtdisk option on all mkvdisk commands to be issued.

Note: This option is not allowed with the -execute parameter.

-execute
Runs the command script svc.config.restore.sh, and produces a log of events in
svc.config.restore.execute.log.
-v on | off
Produces verbose output (on); the default is regular output (off).

Chapter 7. Backup and restore commands 113

Description

The restore command restores the target system configuration from the svc.config.backup.xml file in the
/tmp folder. If neither the -prepare nor the -execute option is specified, the command performs both
phases in sequence, producing only a single event log: svc.config.restore.log.

The restore operation is also known as a T4 (Tier 4) Recovery, and should only be used on a system
having just been started. The restore operation should not be used on a system having any nonautomatic
objects configured, such as MDisk groups (storage pools) or VDisks (volumes).

The restore operation is performed in two phases: prepare and execute.

The command pauses for eight minutes if any nodes are added during this process, informing the user of
this at run-time.

An invocation example
svcconfig restore -prepare -fmt
svcconfig restore -execute
svcconfig restore

The resulting output

No feedback

114 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 8. Clustered system commands
Clustered system commands are used to monitor and modify clustered systems.

addnode (SAN Volume Controller only)

e You can use the addnode command to add a new (candidate) node to an existing clustered system
e (system). You can enter this command any time after a system has been created. If you are adding a new
e node to a system, you must ensure that the model type of the new node is supported by the SAN
e Volume Controller software version of the system. If the model type is not supported by the system
e software, you must upgrade the system to a software version that supports the model type of the new
node.

Syntax


addnode -panelname panel_name

-wwnodename wwnn_arg -name new_name_arg

-iogrp iogroup_name

iogroup_id

Parameters
-panelname panel_name
(Required if you do not specify the -wwnodename parameter) Specifies the node that you want to
e add to a system by the name that is displayed on the display panel. You cannot use this parameter
with the -wwnodename parameter.
-wwnodename wwnn_arg
(Required if you do not specify the -panelname parameter) Specifies the node that you want to add
e to the system by the worldwide node name (WWNN). You cannot use this parameter with the
-panelname parameter.
-name new_name_arg
e (Optional) Specifies a name for the node that you want to add to the system. You can use this name
in subsequent commands to refer to the node, instead of using the node ID.

Note: Node names supplied with the -name parameter on the addnode and chnode commands must
not already be in use as node names or as node failover_names.
If you assign a name, this name is displayed as the node name from then on. If you do not assign a
name, a default name is used. The default name that is used depends on whether the node is
replacing one that has previously been deleted. When a node is deleted, its name is retained in the
I/O group as the failover name of its partner node. If no nodes remain in an I/O group, no failover
names are retained. Only one failover name can be stored for each node. If you add a node into an
I/O group that has a retained failover name and do not specify a node name, the retained failover
name is assigned to this node. If you do not specify a name and there is no retained failover name,
the name assigned has the format nodeX.

e Important: The iSCSI Qualified Name (IQN) for each node is generated using the system and node
names. If you are using the iSCSI protocol and the target name for this node is already active on its
partner node, and iSCSI hosts are attached to it. Adding the node with a different name changes the
e IQN of this node in the system and might require reconfiguration of all iSCSI-attached hosts.

© Copyright IBM Corp. 2003, 2012 115

 -iogrp iogroup_name | iogroup_id
(Required) Specifies the I/O group to which you want to add this node.

Description

Note: The addnode command is a SAN Volume Controller command. For Storwize V7000, use the
addcontrolenclosure command.

e This command adds a new node to the system. You can obtain a list of candidate nodes (those that are
e not already assigned to a system) by typing lsnodecandidate.

Note: The lsnodecandidate command is a SAN Volume Controller command. For Storwize V7000, use
the lscontrolenclosurecandidate command.

e Note: This command is successful only if the node-enclosure system ID matches the system, or is blank.

e Before you add a node to the system, you must check to see if any of the following conditions are true. If
the following conditions exist, failure to follow the procedures that are documented here might result in
e the corruption of all data that is managed by the system.
e v Is the new node being used to replace a failed node in the system?
e v Does the node being added to the system use physical node hardware that has been used as a node in
e another system, and are both system recognized by the same hosts?

If any of the previous conditions are true, you must take the following actions:
1. Add the node to the same I/O group that it was previously in. You can use the command-line
e interface command lsnode or the management GUI to determine the WWNN of the system nodes.
e 2. Shut down all of the hosts that use the system, before you add the node back into the system.
e 3. Add the node back to the system before the hosts are restarted. If the I/O group information is
e unavailable or it is inconvenient to shut down and restart all of the hosts that use the system, you can
do the following:
e a. On all of the hosts that are connected to the system, unconfigure the Fibre Channel adapter device
e driver, the disk device driver, and the multipathing driver before you add the node to the system.
e b. Add the node to the system, and then reconfigure the Fibre Channel adapter device driver, the
disk device driver, and multipathing driver.

e If you are adding a new node to a system, take the following actions:
1. Ensure that the model type of the new node is supported by the SAN Volume Controller software
e version of the system. If the model type is not supported by the system software, you must upgrade
e the system to a software version that supports the model type of the new node.
2. Record the node serial number, the WWNN, all WWPNs, and the I/O group to which the node has
been added. You might need to use this information later. Having it available can prevent possible
data corruption if the node must be removed from and re-added to the clustered system.

e Other considerations when you add a node to a system:

e When you add a node to the system using the addnode command or the system GUI, you must confirm
e whether the node has previously been a member of the system. If it has, follow one of these two
procedures:
v Add the node to the same I/O group that it was previously in. You can determine the WWNN of the
e nodes in the system using the lsnode command.
v If you cannot determine the WWNN of the nodes in the cluster, call the support team to add the node
e back into the system without corrupting the data.

116 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e When a node is added to a system, it displays a state of adding. It can take as long as 30 minutes for the
e node to be added to the system, particularly if the software version of the node has changed.

Attention: If the node remains in the adding state for more than 30 minutes, contact your support
representative to assist you in resolving this issue.

When a node is deleted, its name is retained in an I/O group as the failover name of its partner node. If
no nodes remain in an I/O group, no failover names are retained. The addnode command fails if you
specify a name that is either an existing node name or a retained failover name. Specify a different name
for the node being added.

An invocation example
addnode -wwnodename 5005076801e08b -iogrp io_grp0

The resulting output

Node, id [6], successfully added

cfgportip
The cfgportip command assigns an Internet Protocol (IP) address to each node ethernet port for Internet
Small Computer System Interface (iSCSI) input/output (I/O).

Syntax

e For Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6):

cfgportip -node node_name -ip ipv4addr -mask subnet_mask -gw ipv4gw port_id

node_id -ip_6 ipv6addr prefix_6 prefix -gw_6 ipv6gw -failover
2

For maximum transmission unit (MTU):

e

cfgportip -mtu mtu port_id


defaultmtu -iogrp io_grp
e

Parameters
-node node_name | node_id
(Required) Specifies which node has the ethernet port that the IP address is being assigned to.

e Note: This parameter is required for setting a port IP address. It cannot be used with the -mtu
e parameter.
-ip ipv4addr
(Required) Sets the Internet Protocol Version 4 (IPv4) address for the ethernet port. You cannot use
this parameter with the ip_6 parameter.
-ip_6 ipv6addr
(Required) Sets the Internet Protocol Version 6 (IPv4) address for the ethernet port. You cannot use
this parameter with the ip parameter.
-gw ipv4addr
(Required) Sets the IPv4 gateway IP address. You cannot use this parameter with the gw_6 parameter.
-gw_6 ipv6gw
(Required) Sets the IPv6 default gateway address for the port. You cannot use this parameter with the
gw parameter.

Chapter 8. Clustered system commands 117

 -mask subnet_mask
(Required) Sets the IPv4 subnet mask. You cannot use this parameter with the prefix_6 parameter.
-prefix_6prefix
(Required) Sets the IPv6 prefix. You cannot use this parameter with the mask parameter.
-failover
(Optional) Specifies that the IP address belongs to the partner node in the I/O group. If the partner
node is not configured or offline, the address is configured and presented by this node. When
another node comes online in the I/O group, the failover address is presented by that node.
If the partner node is online, do not use this option.
e -mtu mtu | defaultmtu
e (Required) Specifies the maximum transmission unit (MTU). The default is 1500, with a maximum of
e 9000. An MTU of 9000 enables you to save CPU utilization for packets of 4 K and over in size. The
e increased MTU provides you with improved Internet Small Computer System Interface (iSCSI)
e performance.

e Note: This parameter:

e v Must be used when setting the system MTU This parameter
e v Cannot be used with the -node parameter
e -iogrp iogrp
(Optional) Specifies the I/O group containing the nodes to modify.
port_id
(Required) Specifies which port (1, 2, 3, or 4) to apply changes to.

Description

2 The cfgportip command either sets the IP address of an ethernet port for iSCSI or configure the MTU of
2 a group of ports. This command assigns either an IPv4 or IPv6 address to a specified ethernet port of a
node. The IP address is used for iSCSI I/O. Use the chsystemip command to assign clustered system IP
addresses.

For an IPv4 address, the ip, mask, and gw parameters are required. All of the IPv4 IP parameters must be
specified to assign an IPv4 address to an ethernet port.

For an IPv6 address, the ip_6, prefix_6, and gw_6 parameters are required. All of the IPv6 IP parameters
must be specified to assign an IPv6 address to an ethernet port.

Use the lsportip command with the optional ethernet_port_id parameter to list the port IP addresses
for the specified port.

An invocation example for IPv4

cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 1

The resulting output

No feedback

An invocation example for IPv6

cfgportip -node 1 -ip_6 3:3:0:4::0 -gw_6 ffe8::0 -prefix_6 64 2

The resulting output

No feedback

An invocation example to set an MTU of 1600 on port #1 in I/O group 0

118 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 cfgportip –mtu 1600 -iogrp 0 1

An invocation example to set the MTU to its default value

cfgportip –defaultmtu -iogrp 0 1

1 chcluster
1 The chcluster command has been discontinued. Use the chsystem command instead.
1
1 chsystem
1 The chsystem command modifies the attributes of an existing clustered system. You can enter this
1 command any time after a system has been created. All the parameters that are associated with this
1 command are optional. However, you must specify one or more parameters with this command.

1 Syntax

1

chsystem

1 -name system_name -consoleip console_ip_address

1


1 -rcbuffersize new size in MB -speed fabric_speed

1


1 -alias id_alias -invemailinterval interval

1


1 -gmlinktolerance link_tolerance -gmmaxhostdelay max_host_delay

1


1 -gminterdelaysimulation inter_system_delay_simulation

1


1 -gmintradelaysimulation intra_system_delay_simulation

1


1 -icatip_6 ipv6_icat_ip_address -ntpip ipv4_ntp_ip_address

1


1 -ntpip_6 ipv6_ntp_ip_address -isnsip sns_server_address

1


1 -isnsip_6 ipv6_sns_server_address

1


1 -relationshipbandwidthlimit bandwidth_in_mbps -infocenterurl url

1


1 -iscsiauthmethod none -chapsecret chap_secret -layer replication | storage
chap -nochapsecret
1

1 Parameters
1 -name system_name
1 (Optional) Specifies a new name for the system.

Chapter 8. Clustered system commands 119

1 Important: The iSCSI Qualified Name (IQN) for each node is generated using the system and node
1 names. If you are using the Internet Small Computer System Interface (iSCSI) protocol, changing
1 either name also changes the IQN of all of the nodes in the system and might require reconfiguration
1 of all iSCSI-attached hosts.
1 -consoleip console_ip_address
1 (Optional) Specifies the address of the file system management virtual Internet Protocol (IP) or other
1 valid location for the management GUI. This must be in a valid Internet Protocol Version 4 (IPv4)
1 address or the value 0.0.0.0.

1 Important: The console Internet Protocol (IP) is restored in T3 as part of the configuration process.
1 The console ip address is automatically set to the system IP. If an Internet Protocol Version 4 (IPv4)
1 address has been set for system port 1 it is used (otherwise, an IPv6 address is used). If the console
1 IP is set it overrides this automatic default. If the console IP is set, issuing chsystemip does not
1 change the console IP. If the console IP is the same as the system port 1 IP, issuing chsystemip
1 continues to change the console IP. Setting the consoleip to 0.0.0.0 resets it to the system port 1 IP
1 address.
1 -rcbuffersize new size in MB
1 Specifies the size (in megabytes) of the resource pool.
1 -speed fabric_speed
1 (Optional) Specifies the speed of the fabric to which this system is attached. Valid values are 1 or 2
1 (GB).

1 Attention: Changing the speed on a running system breaks I/O service to the attached hosts. Before
1 changing the fabric speed, stop I/O from active hosts and force these hosts to flush any cached data
1 by unmounting volumes (for UNIX host types) or by removing drive letters (for Windows host
1 types). Some hosts might need to be rebooted to detect the new fabric speed.
1 -alias id_alias
1 (Optional) Specifies an alternate name that does not change the basic ID for the system, but does
1 influence the VDisk_UID of every vdiskhostmap, both existing and new. These objects appear to
1 have been created for a system whose ID matches the alias. Therefore, changing the system alias
1 causes loss of host system access, until each host rescans for volumes presented by the system.
1 -invemailinterval interval
1 (Optional) Specifies the interval at which inventory emails are sent to the designated email recipients.
1 The interval range is 0 to 15. The interval is measured in days. Setting the value to 0 turns the
1 inventory email notification function off.
1 -gmlinktolerance link_tolerance
1 (Optional) Specifies the length of time, in seconds, for which an inadequate intersystem link is
1 tolerated for a Global Mirror operation. The parameter accepts values from 10 to 400 seconds in steps
1 of 10 seconds. The default is 300 seconds. You can disable the link tolerance by entering a value of
1 zero (0) for this parameter.
1 -gmmaxhostdelay max_host_delay
1 (Optional) Specifies the maximum time delay, in milliseconds, above which the Global Mirror link
1 tolerance timer starts counting down. This threshold value determines the additional impact that
1 Global Mirror operations can add to the response times of the Global Mirror source volumes. You can
1 use this parameter to increase the threshold from the default value of 5 milliseconds.
1 -gminterdelaysimulation inter_system_delay_simulation
1 (Optional) Specifies the intersystem delay simulation, which simulates the Global Mirror round trip
1 delay between two systems, in milliseconds. The default is 0; the valid range is 0 to 100 milliseconds.
1 -gmintradelaysimulation intra_system_delay_simulation
1 (Optional) Specifies the intrasystem delay simulation, which simulates the Global Mirror round trip
1 delay in milliseconds. The default is 0; the valid range is 0 to 100 milliseconds.

120 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 -ntpip ipv4_ntp_ip_address
1 (Optional) Specifies the IPv4 address for the Network Time Protocol (NTP) server. Configuring an
1 NTP server address causes the system to immediately start using that NTP server as its time source.
1 To stop using the NTP server as a time source, invoke the -ntpip parameter with a zero address, as
1 follows:
1 chsystem -ntpip 0.0.0.0
1 -ntpip_6 ipv6_ntp_ip_address

1 Note: An IPv6 prefix and gateway must be set for the system before running this command.
1 (Optional) Specifies the IPv6 address for the NTP server. Configuring an NTP server address causes
1 the system to immediately start using that NTP server as its time source. To stop using the NTP
1 server as a time source, invoke the -ntpip_6 parameter with a zero address, as follows:
1 chsystem -ntpip_6 0::0
1 -isnsip sns_server_address
1 (Optional) Specifies the IPv4 address for the iSCSI storage name service (SNS). To stop using the
1 configured IPv4 iSCSI SNS server, invoke the -isnsip parameter with a zero address, as follows:
1 chsystem -isnsip 0.0.0.0
1 -isnsip_6 ipv6_sns_server_address
1 (Optional) Specifies the IPv6 address for the iSCSI SNS. To stop using the configured IPv6 iSCSI SNS
1 server, invoke the -isnsip_6 parameter with a zero address, as follows:
1 chsystem -isnsip_6 0::0
1 -relationshipbandwidthlimit bandwidth_in_mbps
1 (Optional) Specifies the new background copy bandwidth in megabytes per second (MBps), from 1 -
1 1000. The default is 25 MBps. This parameter operates system-wide and defines the maximum
1 background copy bandwidth that any relationship can adopt. The existing background copy
1 bandwidth settings defined on a partnership continue to operate, with the lower of the partnership
1 and volume rates attempted.

1 Note: Do not set this value higher than the default without establishing that the higher bandwidth
1 can be sustained.
2 -infocenterurl url
2 Specifies the preferred infocenter URL to override the one used by the GUI. Because this information
2 is interpreted by the Internet browser, the information returned might contain a hostname or an IP
2 address.

2 Remember: View the currently-configured URL in the GUI preferences panel. This panel can also
2 help reset this value to the default setting.
1 -iscsiauthmethod none | chap
1 (Optional) Sets the authentication method for the iSCSI communications of the system. The
1 iscsiauthmethod value can be none or chap.
1 -chapsecret chap_secret
1 (Optional) Sets the Challenge Handshake Authentication Protocol (CHAP) secret to be used to
1 authenticate the system via iSCSI. This parameter is required if the iscsiauthmethod chap parameter
1 is specified. The specified CHAP secret cannot begin or end with a space.
1 -nochapsecret
1 (Optional) Clears any previously set CHAP secret for iSCSI authentication. This parameter is not
1 allowed if the chapsecret parameter is specified.
1 -layer replication | storage
1 (Optional) Specifies the layer a system resides in. The system can create partnerships with systems in
1 the same layer.

Chapter 8. Clustered system commands 121

1 Note: If you specify -layer you must specify either replication or storage. This option can only be used
1 if no other systems are visible on the fabric, and no system partnerships are defined.

1 Description

1 This command modifies specific features of a system. Multiple features can be changed by issuing a
1 single command.

1 Using the -ntpip or -ntpip_6 parameter allows the system to use an NTP server as an outside time
1 source. The system adjusts the system clock of the configuration node according to time values from the
1 NTP server. The clocks of the other nodes are updated from the configuration node's clock. In the NTP
1 mode, the setsystemtime command is disabled.

1 All command parameters are optional; however, you must specify at least one parameter.

1 Use the chsystemip command to modify the system IP address and service IP address.

1 An invocation example
1 chsystem -ntpip 9.20.165.16

1 The resulting output

1 No feedback

1 An invocation example to change the buffer size

1 chsystem -rcbuffersize 256

1 The resulting output

1 No output

1 An example to set up an external NTP server

1 chsystem -ntpip 123.234.123.234

1 The resulting output

1 No output

2 An example to change the preferred infocenterurl

2 svctask chsystem -infocenterurl http://miscserver.company.com/ibm/infocenter

2 The resulting output

2 No output
1
1 chsystemip
1 The chsystemip command modifies the Internet Protocol (IP) configuration parameters for the clustered
1 system.

1 Syntax

1

chsystemip -clusterip ipv4addr

1 -gw ipv4addr

1


1 -mask subnet_mask -noip -clusterip_6 ipv6addr

1
122 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1
1


1 -gw_6 ipv6addr -prefix_6 prefix -noip_6

1


1 -port system_port
1

1 Parameters
1 -clusterip ipv4addr
1 (Optional) Changes the IPv4 system IP address. When you specify a new IP address for a system, the
1 existing communication with the system is broken.
1 -gw ipv4addr
1 (Optional) Changes the IPv4 default gateway IP address of the system.
1 -mask subnet_mask
1 (Optional) Changes the IPv4 subnet mask of the system.
1 -noip
1 (Optional) Unconfigures the IPv4 stack on the specified port, or both ports if none is specified.

1 Note: This parameter does not affect node service address configurations.
1 -clusterip_6 ipv6addr
1 (Optional) Sets the IPv6 system address for the port.
1 -gw_6 ipv6addr
1 (Optional) Sets the IPv6 default gateway address for the port.
1 -prefix_6 prefix
1 (Optional) Sets the IPv6 prefix.
1 -noip_6
1 (Optional) Unconfigures the IPv6 stack on the specified port, or both ports if none is specified.

1 Note: This parameter does not affect node service address configurations.
1 -port system_port
1 Specifies which port (1 or 2) to apply changes to. This parameter is required unless the noip or
1 noip_6 parameter is used.

1 Description

1 This command modifies IP configuration parameters for the system. The first time you configure a
1 second port, all IP information is required. Port 1 on the system must always have one stack fully
1 configured.

1 There are two active system ports on the configuration node. There are also two active service ports on
1 any node in which you are performing a service action.

1 If the system IP address is changed, the open command-line shell closes during the processing of the
1 command. You must reconnect to the new IP address if connected through that port.

1 If there is no port 2 available on any of the system nodes, the chsystemip command fails.

1 The noip and noip_6 parameters can be specified together only if the port is also specified. The noip and
1 noip_6 parameters cannot be specified with any parameters other than port.

1 Note: The noip and noip_6 parameters do not affect node service address configurations.
1 Port 1 must have an IPv4 or IPv6 system address. The configuration of port 2 is optional.

Chapter 8. Clustered system commands 123

1 Service IP addresses for all ports and stacks are initialized to Dynamic Host Configuration Protocol
1 (DHCP). A service IP address is always configured.

1 Note: If the console_ip is the same as IP address system port 1, Internet Protocol Version 4 (IPv4)
1 followed by IPv6, change the console_ip when the system IP is changed. If the console_ip differs from the
1 system port 1 IP address, do not change the console_ip when the system IP is changed.

1 Modifying an IP address: List the IP address of the system by issuing the lssystem command. Modify
1 the IP address by issuing the chsystemip command. You can either specify a static IP address or have the
1 system assign a dynamic IP address.

1 Table 18 provides IP address formats that are supported.

1 Table 18. IP address list formats
1 IP type IP address list format
1 IPv4 1.2.3.4
1 Full IPv6 1234:1234:abcd:0123:0000:0000:7689:6576
1 Full IPv6, leading zeros suppressed 1234:1234:abcd:123:0:0:7689:6576
1 IPv6 with zero compression 1234:1234:abcd:123::7689:6576
1

1 An invocation example
1 chsystemip -clusterip 9.20.136.5 -gw 9.20.136.1 -mask 255.255.255.0 -port 1

1 The resulting output

1 No feedback
1
chiogrp
The chiogrp command modifies the name of an I/O group, or the amount of memory that is available
for Copy Services or VDisk mirroring operations.

Syntax


chiogrp

-name new_name

-feature flash -size memory_size

remote -kb
mirror
raid

-maintenance yes|no io_group_id


io_group_name

Parameters
-name new_name
(Optional) Specifies the name to assign to the I/O group. The -name parameter cannot be specified
with the -feature, -size, or -kb parameters.
-feature flash | remote | mirror | raid
(Optional) Specifies the feature to modify the amount of memory for: Copy Services or VDisk
mirroring. You must specify this parameter with the -size parameter. You cannot specify this
parameter with the -name parameter.

124 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note: Specifying remote changes the amount of memory that is available for Metro Mirror or Global
Mirror processing. Any VDisk that is in a Metro Mirror or Global Mirror relationship uses memory in
its I/O group, including master and auxiliary VDisks, and VDisks that are in inter-cluster or
intra-cluster relationships.
-size memory_size
(Optional) Specifies the amount of memory that is available for the specified Copy Services or VDisk
mirroring function. Valid input is 0 or any integer. The default unit of measurement for this
parameter is megabytes (MB); you can use the kilobytes -kb parameter to override the default. You
must specify this parameter with the -feature parameter. You cannot specify this parameter with the
-name parameter.
-kb
(Optional) Changes the units for the -size parameter from megabytes (MB) to kilobytes (KB). If you
specify this parameter, the -size memory_size value must be any number divisible by 4. You must
specify this parameter with the -feature and -size parameters. You cannot specify this parameter with
the -name parameter.
io_group_id | io_group_name
(Required) Specifies the I/O group to modify. You can modify an I/O group by using the -name or
the -feature parameter.
-maintenance yes|no
(Optional) Specifies whether the I/O group should be in maintenance mode. The I/O group should
be placed in maintenance mode while carrying out service procedures on storage enclosures. Once
you enter maintenance mode, it continues until either:
v It is explicitly cleared, OR
v 30 minutes elapse

Note: Changing the maintenance mode on any I/O group changes the maintenance mode on all I/O
groups.

Description

The chiogrp command modifies the name of an I/O group or the amount of memory that is available for
Copy Services or VDisk mirroring. You can assign a name to an I/O group or change the name of a
specified I/O group. You can change the amount of memory that is available for Copy Services or VDisk
mirroring operations by specifying the -feature flash | remote | mirror parameter, and a memory size.
For VDisk mirroring and Copy Services (FlashCopy, Metro Mirror, and Global Mirror), memory is traded
against memory that is available to the cache. The amount of memory can be decreased or increased.
Consider the following memory sizes when you use this command:
v The default memory size for FlashCopy is 20 MB.
v The default memory size for Metro Mirror and Global Mirror is 20 MB.
v The default memory size for mirrored VDisks is 20 MB.
v The maximum memory size that can be specified for FlashCopy is 512 MB.
v The maximum memory size that can be specified for Metro Mirror and Global Mirror is 512 MB.
v The maximum memory size that can be specified for mirrored VDisks is 512 MB.
v The maximum combined memory size across all features is 552 MB.

Table 19 on page 126 demonstrates the amount of memory required for VDisk mirroring and Copy
Services. Each 1 MB of memory provides the following VDisk capacities and grain sizes:

Chapter 8. Clustered system commands 125

Table 19. Memory required for VDisk Mirroring and Copy Services
1 MB of memory provides the
following VDisk capacity for the
Feature Grain size specified I/O group
Metro Mirror and Global Mirror 256 KB 2 TB of total Metro Mirror and
Global Mirror VDisk capacity
FlashCopy 256 KB 2 TB of total FlashCopy source VDisk
capacity
FlashCopy 64 KB 512 GB of total FlashCopy source
VDisk capacity
Incremental FlashCopy 256 KB 1 TB of total Incremental FlashCopy
source VDisk capacity
Incremental FlashCopy 64 KB 256 GB of total Incremental
FlashCopy source VDisk capacity
VDisk mirroring 256 KB 2 TB of mirrored VDisks

Table 20 provides an example of RAID level comparisons with their bitmap memory cost, where MS is
the size of the member drives and MC is the number of member drives.
Table 20. RAID level comparisons
Approximate bitmap memory
Level Member count Approximate capacity Redundancy cost
RAID-0 1-8 MC * MS None (1 MB per 2 TB of MS) * MC
RAID-1 2 MS 1 (1 MB per 2 TB of MS) *
(MC/2)
RAID-5 3-16 (MC-1) * MS 1 1 MB per 2 TB of MS with a
strip size of 256 KB; double
RAID-6 5-16 less than (MC-2 * MS) 2
with strip size of 128 KB.
RAID-10 2-16 (evens) MC/2 * MS 1 (1 MB per 2 TB of MS) *
(MC/2)
Note: There is a margin of error on the approximate bitmap memory cost of approximately 15%. For example, the
cost for a 256 KB RAID-5 is ~1.15 MB for the first 2 TB of MS.

For multiple FlashCopy targets, you must consider the number of mappings. For example, for a mapping
with a 256 KB grain size, 8 KB of memory allows one mapping between a 16 GB source VDisk and a 16
GB target VDisk. Alternatively, for a mapping with a 256 KB grain size, 8 KB of memory allows two
mappings between one 8 GB source VDisk and two 8 GB target VDisks.

When you create a FlashCopy mapping, if you specify an I/O group other than the I/O group of the
source VDisk, the memory accounting goes towards the specified I/O group, not towards the I/O group
of the source VDisk.

An invocation example
chiogrp -name testiogrpone io_grp0

The resulting output

No feedback

An invocation example for changing the amount of FlashCopy memory in io_grp0 to 30 MB

chiogrp -feature flash -size 30 io_grp0

126 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The resulting output
No feedback

chnode (SAN Volume Controller) / chnodecanister (Storwize V7000)

Use the chnode / chnodecanister command to change the name that is assigned to a node or node
canister as well as other options. You can then use the new name when running subsequent commands.
All parameters that are associated with this command are optional. However, you must specify one or
more parameters.

Syntax


chnode | chnodecanister

-iscsialias alias -failover
-noiscsialias

2
object_id

-name new_node_or_nodecanister_name object_name

Parameters
-iscsialias alias
(Optional) Specifies the iSCSI name of the node or node canister. The maximum length is 79
characters.
-noiscsialias
(Optional) Clears any previously set iSCSI name for this node or node canister. This parameter cannot
be specified with the iscsialias parameter.
-failover
(Optional) Specifies that the name or iSCSI alias being set is the name or alias of the partner node or
node canister in the I/O group. When there is no partner node or node canister, the values set are
applied to the partner node or node canister when it is added to the clustered system (system). If this
parameter is used when there is a partner node or node canister, the name or alias of that node or
node canister changes.
-name new_node_or_nodecanister_name
(Optional) Specifies the name to assign to the node or node canister.

Note: Node or node canister names supplied with -name on chnode / chnodecanister commands
must not be in use already as node or node canister names or as node or node canister failover
names.

Important: The iSCSI Qualified Name (IQN) for each node or node canister is generated using the
clustered system and node or node canister names. If you are using the iSCSI protocol, changing
either name also changes the IQN of all of the nodes or node canisters in the clustered system and
might require reconfiguration of all iSCSI-attached hosts.
2 object_id | object_name
2 (Required) Specifies the object name or ID that you want to modify. The variable that follows the
2 parameter is either:
2 v The object name that you assigned when you added the node to the clustered system
2 v The object ID that is assigned to the node (not the worldwide node name)

Chapter 8. Clustered system commands 127

 Description

If the failover parameter is not specified, this command changes the name or iSCSI alias of the node or
node canister. The name can then be used to identify the node or node canister in subsequent commands.

The failover parameter is used to specify values that are normally applied to the partner node or node
canister in the I/O group. When the partner node or node canister is offline, the iSCSI alias and IQN are
assigned to the remaining node or node canister in the I/O Group. The iSCSI host data access is then
preserved. If the partner node or node canister is offline when these parameters are set, the node or node
canister they are set on handles iSCSI I/O requests to the iSCSI alias specified, or the IQN that is created
using the node or node canister name. If the partner node or node canister in the I/O group is online
when these parameters are set, the partner node or node canister handles iSCSI requests to the iSCSI alias
specified, and its node or node canister name and IQN change.

An invocation example for chnode

chnode -name testnodeone nodeone

An invocation example for chnodecanister

chnodecanister -name testnodeone nodeone

The resulting output

No feedback

chnodehw (SAN Volume Controller) / chnodecanisterhw (Storwize

V7000)
The chnodehw / chnodecanisterhw command updates the hardware configuration for a node or node
canister.

Syntax
12

chnodehw | chnodecanisterhw -legacy version

-force object_id
object_name

Parameters
1 -legacyversion
1 (Optional) Sets the hardware configuration to make it compatible with the 6.3.0.0 code level. The
1 format is four decimal numbers separated by periods, and there can be up to sixteen characters.
e -force
e (Optional) Allow the node to restart and change its hardware configuration even if this will cause
e volumes to go offline.
2 object_id | object_name
2 (Optional) Specifies the object name or ID.

Description
This command automatically reboots the node or node canister if the node or node canister hardware is
different than its configured hardware. After rebooting, the node or node canister begins to use its
hardware, and does not use the previous configuration.

128 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 Use the -legacy parameter if you want to establish a partnership with another clustered system that is
1 running an earlier level of code than the local system. The value supplied for the -legacy parameter must
1 be the code level of the other clustered system.

An invocation example of how to update the node hardware configuration of node

ID 7
chnodehw 7

An invocation example of how to update the node hardware configuration for the
node named node7 (even if the reboot of the node causes an I/O outage)
chnodehw -force node7

2 An invocation example of how to update the node hardware configuration for

2 compatibility with software level 6.3.0.0
2 chnodehw -legacy 6.3.0.0 node2

An invocation example of how to update the node canister hardware configuration

of canister ID 7
chnodecanisterhw 7

An invocation example of how to update the node canister hardware configuration

for the canister named canister7 (even if the reboot of the canister causes an I/O
outage)
chnodecanisterhw -force canister7

2 An invocation example of how to update the node hardware configuration for

2 compatibility with software level 6.3.0.0
2 chnodehw -legacy 6.3.0.0 node2

e cleardumps
e The cleardumps command clears (or deletes) the various dump directories on a specified node.

e Syntax

e

cleardumps -prefix directory_or_file_filter


node_id
node_name
e

e Parameters
e -prefix directory_or_file_filter
e (Required) Specifies the directory, files, or both to be cleared. If a directory is specified, with no file
e filter, all relevant dump or log files in that directory are cleared. You can use the following directory
e arguments (filters):
e v /dumps (clears all files in all subdirectories)
e v /dumps/cimom
e v /dumps/configs
e v /dumps/elogs
e v /dumps/feature
e v /dumps/iostats
e v /dumps/iotrace

Chapter 8. Clustered system commands 129

e v /dumps/mdisk
e v /home/admin/upgrade
e In addition to the directory, you can specify a filter file. For example, if you specify
e /dumps/elogs/*.txt, all files in the /dumps/elogs directory that end in .txt are cleared.

e Note: The following rules apply to the use of wildcards with the SAN Volume Controller CLI:
e v The wildcard character is an asterisk (*).
e v The command can contain a maximum of one wildcard.
e v With a wildcard, you must use double quotation marks (" ") around the filter entry, such as in the
e following entry:
e >cleardumps -prefix "/dumps/elogs/*.txt"
e node_id | node_name
e (Optional) Specifies the node to be cleared. The variable that follows the parameter is either:
e v The node name, that is, the label that you assigned when you added the node to the clustered
e system (system)
e v The node ID that is assigned to the node (not the worldwide node name).

e Description

e This command deletes all the files that match the directory/file_filter argument on the specified node. If
e no node is specified, the configuration node is cleared.

e You can clear all the dumps directories by specifying /dumps as the directory variable.

e You can clear all the files in a single directory by specifying one of the directory variables.

e You can list the contents of these directories on the given node by using the lsxxxxdumps commands.

e You can use this command to clear specific files in a given directory by specifying a directory or file
e name. You can use the wildcard character as part of the file name.

e Note: To preserve the configuration and trace files, any files that match the following wildcard patterns
e are not cleared:
e v *svc.config*
e v *.trc
e v *.trc.old

e An invocation example
e cleardumps -prefix /dumps/configs

e The resulting output

e No feedback
e
cpdumps
The cpdumps command copies dump files from a nonconfiguration node onto the configuration node.

Note: In the rare event that the /dumps directory on the configuration node is full, the copy action ends
when the directory is full and provides no indicator of a failure. Therefore, clear the /dumps directory
after migrating data from the configuration node.

130 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


cpdumps -prefix directory node_name

file_filter node_id

Parameters
-prefix directory | file_filter
(Required) Specifies the directory, or files, or both to be retrieved. If a directory is specified with no
file filter, all relevant dump or log files in that directory are retrieved. You can use the following
directory arguments (filters):
v /dumps (retrieves all files in all subdirectories)
v /dumps/audit
v /dumps/cimom
v /dumps/configs
v /dumps/elogs
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/mdisk
v /home/admin/upgrade
v (Storwize V7000) /dumps/enclosure
In addition to the directory, you can specify a file filter. For example, if you specified
/dumps/elogs/*.txt, all files in the /dumps/elogs directory that end in .txt are copied.

Note: The following rules apply to the use of wildcards with the CLI:
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard.
v When you use a wildcard, you must surround the filter entry with double quotation marks (""), as
follows:
>cleardumps -prefix "/dumps/elogs/*.txt"
node_id | node_name
(Required) Specifies the node from which to retrieve the dumps. The variable that follows the
parameter can be one of the following:
v The node name, or label that you assigned when you added the node to the cluster
v The node ID that is assigned to the node (not the worldwide node name).
If the node specified is the current configuration node, no file is copied.

Description

This command copies any dumps that match the directory or file criteria from the given node to the
current configuration node.

You can retrieve dumps that were saved to an old configuration node. During failover processing from
the old configuration node to another node, the dumps that were on the old configuration node are not
automatically copied. Because access from the CLI is only provided to the configuration node, cluster files
can only be copied from the configuration node. This command enables you to retrieve files and place
them on the configuration node so that you can then copy them.

You can view the contents of the directories by using the lsxxxxdumps commands.

Chapter 8. Clustered system commands 131

An invocation example
cpdumps -prefix /dumps/configs nodeone

The resulting output

No feedback

detectmdisk
Use the detectmdisk command to manually rescan the Fibre Channel network for any new managed
disks (MDisks) that might have been added, and to rebalance MDisk access across all available controller
device ports.

Syntax


detectmdisk


Description

This command causes the clustered system (system) to rescan the Fibre Channel network. The rescan
discovers any new MDisks that have been added to the system and rebalances MDisk access across the
available controller device ports. This command also detects any loss of controller port availability, and
updates the SAN Volume Controller configuration to reflect any changes.

Note: Although it might appear that the detectmdisk command has completed, some extra time might
be required for it to run. The detectmdisk is asynchronous and returns a prompt while the command
continues to run in the background. You can use the lsdiscoverystatus command to list the discovery
status.

In general, the system automatically detects disks when they appear on the network. However, some
Fibre Channel controllers do not send the required SCSI primitives that are necessary to automatically
discover the new disks.

If you have attached new storage and the system has not detected it, you might need to run this
command before the system detects the new disks.

When back-end controllers are added to the Fibre Channel SAN and are included in the same switch
zone as a system, the system automatically discovers the back-end controller and determines what
storage is presented to it. The SCSI LUs that are presented by the back-end controller are displayed as
unmanaged MDisks. However, if the configuration of the back-end controller is modified after this has
occurred, the system might be unaware of these configuration changes. Run this command to rescan the
Fibre Channel network and update the list of unmanaged MDisks.

Note: The automatic discovery that is performed by the system does not write to an unmanaged MDisk.
Only when you add an MDisk to a storage pool, or use an MDisk to create an image mode virtual disk,
is the storage actually used.

To identify the available MDisks, issue the detectmdisk command to scan the Fibre Channel network for
any MDisks. When the detection is complete, issue the lsmdiskcandidate command to show the
unmanaged MDisks; these MDisks have not been assigned to a storage pool. Alternatively, you can issue
the lsmdisk command to view all of the MDisks.

If disk controller ports have been removed as part of a reconfiguration, the SAN Volume Controller
detects this change and reports the following error because it cannot distinguish an intentional
reconfiguration from a port failure:

132 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1630 Number of device logins reduced

If the error persists and redundancy has been compromised, the following more serious error is reported:
1627 Insufficient redundancy in disk controller connectivity

You must issue the detectmdisk command to force SAN Volume Controller to update its configuration
and accept the changes to the controller ports.

Note: Only issue the detectmdisk command when all of the disk controller ports are working and
correctly configured in the controller and the SAN zoning. Failure to do this could result in errors not
being reported.

An invocation example
detectmdisk

The resulting output

No feedback

ping
The ping command can be used to diagnose IP configuration problems by checking whether the specified
IP address is accessible from the configuration node.

Syntax


ping ipv4_address

ipv6_address

Parameters
ipv4_address | ipv6_address
(Required) Specifies the clustered system IP address.

Description

This command checks whether the specified IP address is accessible from the configuration node.

Note: You can only use this command on ports 1 and 2 (for management traffic).
The ping takes place only from the configuration node. It can be useful for diagnosing problems where
the configuration node cannot be reached from a specific management server.

An invocation example
ping 9.20.136.11

The resulting output

PING 9.20.136.11 (9.20.136.11) 56(84) bytes of data.
64 bytes from 9.20.136.11: icmp_seq=1 ttl=249 time=0.690 ms
64 bytes from 9.20.136.11: icmp_seq=2 ttl=249 time=0.382 ms
64 bytes from 9.20.136.11: icmp_seq=3 ttl=249 time=0.311 ms
--- 9.20.136.11 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.311/0.461/0.690/0.164 ms

Chapter 8. Clustered system commands 133

 rmnode (SAN Volume Controller) / rmnodecanister (Storwize V7000)
The rmnode / rmnodecanister command deletes a node from the clustered system. You can enter this
command any time after a clustered system has been created.

Syntax
2

rmnode | rmnodecanister object_id

-force object_name

Parameters
-force
(Optional) Overrides the checks that this command runs. The parameter overrides the following two
checks:
v If the command results in volumes going offline, the command fails unless the force parameter is
used.
v If the command results in a loss of data because there is unwritten data in the write cache that is
contained only within the node or node canister to be removed, the command fails unless the
force parameter is used.
If you use the force parameter as a result of an error about volumes going offline, you force the node
or node canister removal and run the risk of losing data from the write cache. The force parameter
should always be used with caution.
2 object_id | object_name
2 (Required) Specifies the object name or ID that you want to modify. The variable that follows the
2 parameter is either:
2 v The object name that you assigned when you added the node to the clustered system
2 v The object ID that is assigned to the node (not the worldwide node name)

Description

This command removes a node or node canister from the clustered system. This makes the node or node
canister a candidate to be added back into this clustered system or into another system. After the node or
node canister is deleted, the other node in the I/O group enters write-through mode until another node
or node canister is added back into the I/O group.

By default, the rmnode / rmnodecanister command flushes the cache on the specified node before the
node or node canister is taken offline. In some circumstances, such as when the system is already
degraded (for example, when both nodes in the I/O group are online and the virtual disks within the
I/O group are degraded), the system ensures that data loss does not occur as a result of deleting the only
node or node canister with the cache data.

The cache is flushed before the node or node canister is deleted to prevent data loss if a failure occurs on
the other node or node canister in the I/O group.

To take the specified node or node canister offline immediately without flushing the cache or ensuring
data loss does not occur, run the rmnode / rmnodecanister command with the -force parameter.

Prerequisites:

Before you issue the rmnode / rmnodecanister command, perform the following tasks and read the
following Attention notices to avoid losing access to data:

134 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1. Determine which virtual disks (VDisks, or volumes) are still assigned to this I/O group by issuing the
following command. The command requests a filtered view of the volumes, where the filter attribute
is the I/O group.
lsvdisk -filtervalue IO_group_name=name

where name is the name of the I/O group.

Note: Any volumes that are assigned to the I/O group that this node or node canister belongs to are
assigned to the other node or node canister in the I/O group; the preferred node or node canister is
changed. You cannot change this setting back.
2. Determine the hosts that the volumes are mapped to by issuing the lsvdiskhostmap command.
3. Determine if any of the volumes that are assigned to this I/O group contain data that you need to
access:
v If you do not want to maintain access to these volumes, go to step 5.
v If you do want to maintain access to some or all of the volumes, back up the data or migrate the
data to a different (online) I/O group.
4. Determine if you need to turn the power off to the node or node canister:
v If this is the last node or node canister in the clustered system, you do not need to turn the power
off to the node or node canister. Go to step 5.
v If this is not the last node or node canister in the cluster, turn the power off to the node or node
canister that you intend to remove. This step ensures that the Subsystem Device Driver (SDD) does
not rediscover the paths that are manually removed before you issue the delete node or node
canister request.
5. Update the SDD configuration for each virtual path (vpath) that is presented by the volumes that you
intend to remove. Updating the SDD configuration removes the vpaths from the volumes. Failure to
update the configuration can result in data corruption. See the Multipath Subsystem Device Driver:
User's Guide for details about how to dynamically reconfigure SDD for the given host operating
system.
6. Quiesce all I/O operations that are destined for the node or node canister that you are deleting.
Failure to quiesce the operations can result in failed I/O operations being reported to your host
operating systems.

Attention:
1. Removing the last node in the cluster destroys the clustered system. Before you delete the last node or
node canister in the clustered system, ensure that you want to destroy the clustered system.
2. If you are removing a single node or node canister and the remaining node or node canister in the
I/O group is online, the data can be exposed to a single point of failure if the remaining node or node
canister fails.
3. This command might take some time to complete since the cache in the I/O group for that node or
node canister is flushed before the node or node canister is removed. If the -force parameter is used,
the cache is not flushed and the command completes more quickly. However, if the deleted node or
node canister is the last node or node canister in the I/O group, using the -force option results in the
write cache for that node or node canister being discarded rather than flushed, and data loss can
occur. The -force option should be used with caution.
4. If both nodes or node canisters in the I/O group are online and the volumes are already degraded
before deleting the node or node canister, redundancy to the volumes is already degraded and loss of
access to data and loss of data might occur if the -force option is used.

Notes:
1. If you are removing the configuration node or node canister, the rmnode / rmnodecanister command
causes the configuration node or node canister to move to a different node or node canister within the
clustered system. This process might take a short time: typically less than a minute. The clustered

Chapter 8. Clustered system commands 135

 system IP address remains unchanged, but any SSH client attached to the configuration node or node
canister might need to reestablish a connection. The management GUI reattaches to the new
configuration node or node canister transparently.
2. If this is the last node or node canister in the clustered system or if it is currently assigned as the
configuration node, all connections to the system are lost. The user interface and any open CLI
sessions are lost if the last node or node canister in the clustered system is deleted. A time-out might
occur if a command cannot be completed before the node or node canister is deleted.

An invocation example for rmnode

rmnode 1

An invocation example for rmnodecanister

rmnodecanister 1

The resulting output

No feedback

rmportip
The rmportip command removes an iSCSI IP address from a node ethernet port.

Syntax


rmportip -node node_name port_id

-failover -ip_6 node_id

Parameters
-failover
(Optional) Specifies that the failover IP address information be removed for the specified port.
-ip_6
(Optional) Specifies that the IPv6 address be removed for the specified port. If this parameter is not
used, the IPv4 address is removed by default.
-node node_name | node_id
(Required) Specifies the node with the ethernet port that the IP address is being removed from.
port_id
(Required) Specifies which port (1, 2, 3, or 4) to apply changes to.

Description

This command removes an IPv4 or IPv6 address from an ethernet port of a node.

An invocation example for IPv4

rmportip -node 1 1

The resulting output

No feedback

An invocation example for IPv6

rmportip -node 1 -ip_6 2

The resulting output

136 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 No feedback

1 setclustertime
1 Attention: The setclustertime command has been discontinued. Use the setsystemtime command
1 instead.
1
1 setsystemtime
1 The setsystemtime command sets the time for the clustered system (system).

1 Syntax

1

setsystemtime -time time_value


1

1 Parameters
1 -time time_value
1 (Required) Specifies the time to which the system must be set. This must be in the following format
1 (where 'M' is month, 'D' is day, 'H' is hour, 'm' is minute, and 'Y' is year):

1 MMDDHHmmYYYY

1 Description

1 This command sets the time for the system.

1 An invocation example
1 setsystemtime -time 040509142003

1 The resulting output

1 No feedback
1
setpwdreset
Use the setpwdreset command to view and change the status of the password-reset feature for the
display panel.

Syntax


setpwdreset -disable

-enable
-show

Parameters
-disable
Disables the password-reset feature that is available through the front panel menu system.
-enable
Enables the password-reset feature that is available through the front panel menu system.
-show
Displays the status of the password-reset feature, which is either enabled or disabled.

Chapter 8. Clustered system commands 137

 Description

e The system provides an option to reset the system superuser password to the default value.

e For SAN Volume Controller systems this can be done using the front panel menu system.

e For all systems this can be done using the USB stick. For more information, visit Using the initialization
e tool.

e This command allows access if the system superuser password is forgotten. If this feature remains
e enabled, make sure there is adequate physical security to the system hardware.

e You can view or change the status of this feature.

An invocation example
setpwdreset -show

The resulting output

Password status: [1]

This output means that the password or reset feature that is available through the front panel menu
system is enabled. If the password status is [0], this feature is disabled.

settimezone
Use the settimezone command to set the time zone for the cluster.

Syntax


settimezone -timezone timezone_arg


Parameters
-timezone timezone_arg
Specifies the time zone to set for the cluster.

Description

This command sets the time zone for the cluster. Use the -timezone parameter to specify the numeric ID
of the time zone that you want to set. Issue the lstimezones command to list the time-zones that are
available on the cluster. A list of valid time-zones settings are displayed in a list.

The time zone that this command sets will be used when formatting the error log that is produced by
issuing the following command:

dumperrlog

Note: If you have changed the timezone, you must clear the error log dump directory before you can
view the error log through the web application.

Issue the showtimezone command to display the current time-zone settings for the cluster. The cluster ID
and its associated time-zone are displayed. Issue the setsystemtime command to set the time for the
cluster.

An invocation example

138 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
settimezone -timezone 5

The resulting output

No feedback

startstats
Use the startstats command to modify the interval at which per-node statistics for virtual disks
(VDisks), managed disks (MDisks), and nodes are collected.

Syntax


startstats -interval time_in_minutes


Parameters
-interval time_in_minutes
Specifies the time in minutes. This is the time interval between the gathering of statistics, from 1 to 60
minutes in increments of 1 minute.

Description

Running the startstats command will reset the statistics timer to zero (0), and give it a new interval at
which to sample. Statistics are collected at the end of each sampling period as specified by the -interval
parameter. These statistics are written to a file, with a new file created at the end of each sampling
period. Separate files are created for MDisks, VDisks and node statistics.

The files generated are written to the /dumps/iostats directory.

A maximum of 16 files are stored in the directory at any one time for each statistics file type, for
example:
Nm_stats_nodepanelname_date_time
Nv_stats_nodepanelname_date_time
Nn_stats_nodepanelname_date_time

Statistics files are created for all time intervals. Before the 17th file for each type is created, the oldest file
of that type is deleted.

These files can be listed by using the lsiostatsdumps command.

The following naming convention is used for these files:

stats_type_stats_nodepanelname_date_time

Where stats_type is Nm for MDisks, Nv for VDisks, and Nn for node statistics. nodepanelname is the
current configuration node panel name, date is in the format of yymmdd, and time is in the format of
hhmmss.

The following is an example of an MDisk statistics file name:

Nm_stats_000229_031123_072426

The following is an example of a VDisk statistics file name:

Nv_stats_000229_031123_072426

The following is an example of a node statistics file name:

Chapter 8. Clustered system commands 139

 Nn_stats_000229_031123_072426

Statistics are collected for each MDisk and recorded in the Nm_stats_nodepanelname_date_time file,
including the following statistical information:
v The number of SCSI read and write commands that are processed during the sample period
v The number of blocks of data that are read and written during the sample period
v Per MDisk, cumulative read and write external response times in milliseconds
v Per MDisk, cumulative read and write queued response times

Statistics are collected for each VDisk and recorded in the Nv_stats_nodepanelname_date_time file,
including the following statistical information:
v The total number of processed SCSI read and write commands
v The total amount of read and written data
v Cumulative read and write response time in milliseconds
v Statistical information about the read/write cache usage
v Global Mirror statistics including latency

Statistics are collected for the node from which the statistics file originated and recorded in the
Nn_stats_nodepanelname_date_time file, including the following statistical information:
v Usage figure for the node from which the statistic file was obtained
v The amount of data transferred to and received from each port on the node to other devices on the
SAN
v Statistical information about communication to other nodes on the fabric

An invocation example
startstats -interval 25

The resulting output

No feedback

stopstats (Deprecated)
The stopstats command has been deprecated. You can no longer disable statistics collection.

1 stopcluster
1 The stopcluster command has been discontinued. Use the stopsystem command instead.
1
stopsystem
The stopsystem command shuts down a single node or the entire clustered system in a controlled
manner. When you issue this command, you are prompted with a confirmation of intent to process the
command.

Syntax


stopsystem

-force -node node_name
node_id

140 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
-force
(Optional) Specifies that the node that is being shut down is the last online node in a given I/O
group. The force parameter also overrides the checks that this command runs. The parameter
overrides the following two checks:
v If the command results in volumes going offline, the command fails unless the force parameter is
used.
v If the node being shut down is the last online node in the I/O group, the command fails unless the
force parameter is used.
If you use the force parameter as a result of an error about volumes going offline, you force the node
to shut down, even if it is the last online node in the I/O group. The force parameter should always
be used with caution.
-node node_name | node_id
(Optional) Specifies the node that you want to shut down. You can specify one of the following
values:
v The node name, or label that you assigned when you added the node to the system.
v The node ID that is assigned to the node (not the worldwide node name).
If you specify -node node_name | node_id, only the specified node is shut down; otherwise, the entire
system is shut down.

Description

If you enter this command with no parameters, the entire system is shut down. All data is flushed to disk
before the power is removed.

If you enter this command with either a node ID or node name, the specified node is shut down. After
the command completes, the remaining node in the I/O group enters write-through mode until the
power to the node is returned, and the node rejoins the system.

Entering y or Y to the confirmation message processes the command. No feedback is then displayed.
Entering anything other than y or Y results in the command not processing. No feedback is displayed.

If you need to shut down the entire system or a single node, use this command instead of using the
power button on the nodes or powering off the main power supplies to the system.

Attention: Do not power off the uninterruptible power supply or remove the power cable from the
node.

Storwize V7000: If you need to shut down the system or a single node, use this command instead of
using the power button on power supplies, or powering off the mains to the system.

Before shutting down a node or system, complete the following requirements:

1. Quiesce all I/O operations that are destined for this node or system. If you do not quiesce these,
failed I/O operations might be reported to your host operating systems.
2. Stop all FlashCopy, Metro Mirror, Global Mirror, and data migration operations.
3. Ensure that all asynchronous deletion operations have completed.

Using this command to shut down a single node fails if shutting down the node makes any volumes
inaccessible, or if it is the last node in an I/O group. If you still need to shut down the node, you can use
the -force option to override these checks.

Chapter 8. Clustered system commands 141

An invocation example
stopsystem

The resulting output

The following confirmation prompt is displayed:

Are you sure that you want to continue with the shut down?

142 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 9. Clustered system diagnostic and service-aid
commands
Clustered system diagnostic and service-aid commands are designed to diagnose and find clustered
system problems.

The SAN Volume Controller enables you to perform service activity, such as problem determination and
repair activities, with a limited set of command-line tools. When you are logged in under the
administrator role, all command-line activities are permitted. When you are logged in under the service
role, only those commands that are required for service are enabled. The clustered system diagnostic and
service-aid commands apply under the service role.

applysoftware
The applysoftware command upgrades the clustered system (system) to a new level of software.

Syntax
2

applysoftware -file filename_arg

-force -file filename_arg -prepare
-abort

Parameters
-force
(Optional) Specifies that the upgrade or abort should proceed even if there are non-redundant nodes
in the system.

Important: Using this option might result in a loss of access.

e Note: The force parameter can be used with the abort parameter. If one or more nodes are offline,
e you must use the force parameter with the abort parameter.
-file filename_arg
(Required for performing an upgrade) Specifies the file name of the new software package to be
applied.

2 Note: The file parameter cannot be used with the abort parameter.
2 -prepare
2 (Optional) Prepares the system for a manual software level upgrade.

2 Note: You can:

2 v Use the prepare parameter with the file parameter
2 v Not use the prepare parameter with the abort parameter
2 v Not use the force parameter with the prepare parameter to go to prepared status
2 -abort
2 (Required for stopping an upgrade) Specifies that a stalled or preparedupgrade should be stopped,
returning the system to the original software level.

e Note: The abort parameter can be used with the force parameter, but not the file or prepare
e parameters.

© Copyright IBM Corp. 2003, 2012 143

2 The abort parameter can also be used when the lssoftwareupgradestatus command reports a status
2 of:
2 v prepare_failed
2 v prepared (if all nodes are online)

Description

This command starts the upgrade process of the system to a new level of SAN Volume Controller
software. The applysoftware command applies a level of software to the node as a service action (Paced
Upgrade) to upgrade the specific node, or as an automatic upgrade process that upgrades all of the nodes
in the entire system.

2 The applysoftware command cannot be used in service state, which means the system must be running
2 in order for the command to be used and be successful. This command is synchronous and therefore
2 reports success or failure.

The software package as specified by the file name must first be copied onto the current configuration
node in the /home/admin/upgrade directory; use the PuTTy secure copy (scp) application to copy the file.

2 If the applysoftware command is successful, the lssoftwareupgradestatus command reports the status is
2 prepared. If the applysoftware command fails, the lssoftwareupgradestatus command reports the status
2 the status will be reported is inactive.

2 If specified, the prepare parameter must succeed in order to successfully upgrade. It is recommended to
2 use the same package for the prepare as the actual upgrade. The prepare parameter can be canceled by
2 using the abort parameter (even after the system is prepared) as long as the lssoftwareupgradestatus
2 command reports the status as prepared.

2 Important: The -prepare might time out. If this occurs, the prepare causes an asynchronous condition,
2 and the lssoftwareupgradestatus command reports the prepare as "preparing". If this occurs then wait
2 until lssoftwareupgradestatus reports the upgrade as "prepared" before proceeding with the manual
2 upgrade process.

2 The command completes as soon as the upgrade process is successful. The command fails and the
upgrade package is deleted if:
v The given package fails an integrity check due to corruption.
v Any node in the system has a hardware type not supported by the new software.
v The new software level does not support upgrades from the currently installed software.
v The software level of a remote system is incompatible with the new software.
v There are any volumes that are dependent on the status of a node.

Note: The force parameter can be used to override this if you are prepared to lose access to data
during the upgrade. Before proceeding, use the lsdependentvdisks command with the node parameter
to list the node-dependent volumes at the time the command is run. If the command returns an error,
move the quorum disks to MDisks that are accessible through all nodes. Rerun the command until no
errors are returned.

The actual upgrade completes asynchronously.

The lsdumps command allows you to view the contents of the /home/admin/upgrade directory.

An invocation example

applysoftware –file softwareupdate

144 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The resulting output

No feedback

2 An invocation example

2 applysoftware -prepare -file IBM2145_INSTALL_7.1.0.0

2 The resulting output

2 No feedback

2 An invocation example

2 svctask applysoftware -abort

2 The resulting output

2 No feedback

caterrlog (Deprecated)
The caterrlog command has been deprecated. Use the lseventlog command instead.

caterrlogbyseqnum (Deprecated)
The caterrlogbyseqnum command has been deprecated. Use the lseventlog command instead.

cherrstate
The cherrstate command has been discontinued. Use the cheventlog command instead.

clearerrlog
The clearerrlog command clears all entries from the error log including status events and any unfixed
errors.

Syntax


clearerrlog

-force

Parameters
-force
(Optional) Specifies that the clearerrlog command be processed without confirmation requests. If the
-force parameter is not supplied, you are prompted to confirm that you want to clear the log.

Description

This command clears all entries from the error log. The entries are cleared even if there are unfixed errors
in the log. It also clears any status events that are in the log.

Chapter 9. Clustered system diagnostic and service-aid commands 145

Attention: This command is destructive. Use it only when you have either rebuilt the clustered system
or have fixed a major problem that has caused entries in the error log that you do not want to manually
fix.

An invocation example
clearerrlog -force

The resulting output

No feedback

dumperrlog
The dumperrlog command dumps the contents of the error log to a text file.

Syntax


dumperrlog

-prefix filename_prefix

Parameters
-prefix filename_prefix
(Optional) A file name is created from the prefix and a time stamp, and has the following format:

prefix_NNNNNN_YYMMDD_HHMMSS

where NNNNNN is the node front panel name.

Note: If the -prefix parameter is not supplied, the dump is directed to a file with a system-defined
prefix of errlog.

Description

When run with no parameters, this command dumps the clustered system (system) error log to a file
using a system-supplied prefix of errlog, which includes the node ID and time stamp. When a file name
prefix is provided, the same operation is performed but the details are stored in the dumps directory
within a file with a name that starts with the specified prefix.

A maximum of ten error-log dump files are kept on the system. When the 11th dump is made, the oldest
existing dump file is overwritten.

Error log dump files are written to /dumps/elogs. The contents of this directory can be viewed using the
lsdumps command.

Files are not deleted from other nodes until you issue the cleardumps command.

An invocation example
dumperrlog -prefix testerrorlog

The resulting output

No feedback

finderr
The finderr command analyzes the error log for the highest severity unfixed error.

146 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


finderr


Description

The command scans the error log for any unfixed errors. Given a priority ordering within the code, the
highest priority unfixed error is returned to standard output.

You can use this command to determine the order in which to fix the logged errors.

An invocation example
finderr

The resulting output

Highest priority unfixed error code is [1010]

lserrlogbyfcconsistgrp (Deprecated)
The lserrlogbyfcconsistgrp command has been deprecated. Use the lseventlog command instead.

lserrlogbyfcmap (Deprecated)
The lserrlogbyfcmap command has been deprecated. Use the lseventlog command instead.

lserrlogbyhost (Deprecated)
The lserrlogbyhost command has been deprecated. Use the lseventlog command instead.

lserrlogbyiogrp (Deprecated)
The lserrlogbyiogrp command has been deprecated. Use the lseventlog command instead.

lserrlogbymdisk (Deprecated)
The lserrlogbymdisk command has been deprecated. Use the lseventlog command instead.

lserrlogbymdiskgrp (Deprecated)
The lserrlogbymdiskgrp command has been deprecated. Use the lseventlog command instead.

lserrlogbynode (Deprecated)
The lserrlogbynode command has been deprecated. Use the lseventlog command instead.

lserrlogbyrcconsistgrp (Deprecated)
The lserrlogbyrcconsistgrp command has been deprecated. Use the lseventlog command instead.

lserrlogbyrcrelationship (Deprecated)
The lserrlogbyrcrelationship command has been deprecated. Use the lseventlog command instead.

Chapter 9. Clustered system diagnostic and service-aid commands 147

 lserrlogbyvdisk (Deprecated)
The lserrlogbyvdisk command has been deprecated. Use the lseventlog command instead.

lserrlogdumps (Deprecated)
Attention: The svcinfo lserrlogdumps command is deprecated. Use the svcinfo lsdumps command to
display a list of files in a particular dumps directory.

1 cheventlog
1 The cheventlog command to modify events in the event log.

1 Syntax

12

cheventlog -fix sequence_number


-checklogoff
1

1 Parameters
1 -fix sequence_number
e (Optional) Mark an unfixed event as fixed.
1 -checklogoff
1 (Optional) Turns off check log light emitting diode (LED).

1 Description

2 Important: You must specify either the -fix or -checklogoff parameter.

1 An invocation example to mark an event fixed

1 cheventlog -fix 120
1 cheventlog -checklogoff
1
lseventlog
Use the lseventlog command to display a concise view of the system event log, or a detailed view of one
entry from the log.

Syntax


lseventlog

-alert yes|no -message yes|no -monitoring yes|no

-expired yes|no -fixed yes|no -count entry_limit


-order date|severity sequence_number

Parameters
-alert
(Optional) Includes (or excludes) events with alert status. The default value is yes.

148 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -message
(Optional) Includes events with message status. The default value is yes.
e -monitoringyes|no
e (Optional) Includes events with monitoring status. The default value is yes.
-expiredyes|no
(Optional) Includes (or excludes) events with expired status. The default value is yes.
-fixedyes|no
(Optional) Includes (or excludes) events with fixed status. The default value is yes.
-countentry_limit
(Optional) Indicates the maximum number of events to display.
-order date|severity
(Optional) Indicates what order the events should be in. Ordering by date displays the oldest events
first. Ordering by severity displays the events with the highest severity first. If multiple events have
the same severity, then they are ordered by date, with the oldest event being displayed first.
The following list shows the order of severity, starting with the most severe:
1. Unfixed alerts (sorted by error code; the lowest error code has the highest severity)
2. Unfixed messages
3. Monitoring events (sorted by error code; the lowest error code has the highest severity)
4. Expired events
5. Fixed alerts and messages
sequence_number
(Optional) Indicates if the command should display a full view of the event.

Description

This command displays a concise view of the system event log, or a detailed view of one entry from the
log. You can sort the events and entries by severity or age.

Table 21 provides the attribute values that can be displayed as output view data.
Table 21. lseventlog output
Attribute Description Value
1 machine_type Node machine type and model Alphanumeric string (up to 7
1 number characters long )
1 serial number Node serial number Alphanumeric string (up to 7
1 characters long )
sequence_number Sequence number of the event Numeric 0-8000000
first_timestamp When the event was added to the log YYMMDDHHMMSS
1 first_timestamp_epoch When the event was added to the log Numeric 32-bit
1 (in seconds) after the epoch occurs
last_timestamp When the event was most recently YYMMDDHHMMSS
updated
1 last_timestamp_epoch Most recent update (in seconds) after Numeric 32-bit
1 an epoch for an event
1 fixed_timestamp Time stamp when event is fixed YYMMDDHHMMSS
1 fixed_timestamp_epoch Time stamp (in seconds) when an Numeric string
1 event is fixed after an epoch occurs

Chapter 9. Clustered system diagnostic and service-aid commands 149

 Table 21. lseventlog output (continued)
Attribute Description Value
1 fru Field-replaceable unit (FRU) for error ASCII string up to 255 characters
1 or event; this field contains probable long
1 FRUs (separated by commas)
object_type The type of the object the event is v mdisk
logged against
v mdiskgrp
v vdisk (or vdisk copy)
v node
v host
v io_grp (iogroup in dumperrlog)
v fc_consist_grp (fcgrp in dumperrlog)
v rc_consist_grp (rcgrp in
dumperrlog)
v fc_map (fcmap in dumperrlog; flash
in caterrlog)
v rc_relationship (rcmap in
dumperrlog; remote in caterrlog)
v cluster
v controller (device in caterrlog and
dumperrlog)
v quorum
v migrate
v email_server (email server in
caterrlog and dumperrlog)
v enclosure
v drive
e object_id ID of the object the event is logged Numeric 64-bit; displayed in decimal
e against for all object types except clustered
e systems

e For clustered system it is

e hexadecimal, and blank for events
e with object_type cluster.
object_name Name of the object the event is Object name format; blank if the
logged against. object was deleted or does not have a
name
copy_id VDisk (volume) copy ID the event is 0-1; blank if not a vdiskcopy event
logged against
reporting_node_id ID of the node that reported the Numeric 64-bit; blank if the event
event was reported by the clustered system
reporting_node_name Name of the node that reported the Object name format; blank if node is
event. deleted or event is reported by the
clustered system
root_sequence_number Sequence number of the root or Numeric, 1-8000000; blank if there is
e causal event no root or if the event is not directly
e3 Important: If the event is directly caused by another event
3 caused by another event then the
3 sequence_number of the related event
3 is shown here.

150 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Table 21. lseventlog output (continued)
Attribute Description Value
event_count Number of reported events that have Numeric 32-bit.
been combined into this event
status Event category v alert
v message
v monitoring
v expired
fixed Indicates whether the event was v yes
marked fixed (for an alert) or read
v no (for events that cannot be fixed,
(for a message)
or are not fixed)
auto_fixed Indicates if event is marked fixed by v yes
the code
v no (for events that cannot be fixed,
or are not fixed)
notification_type Type of event notification v error
v warning
v informational
v none
event_id Event ID 6-digit numeric
e event_id_text Description associated with the event Text, max 200 bytes
e ID
e This appears in CLI requested
e language.
error_code Error code associated with this event 4-digit numeric; blank if there is no
error code
e error_code_text Description associated with the error Text (maximum of 200 bytes); blank if
e code there is no error code

e This appears in CLI requested

e language.
description Description associated with the event Text (maximum of 200 bytes).

If the event has an error code, this

value is the same as the
error_code_text field; otherwise, it is
the same as the event_id_text field
sense1 Sixteen bytes of hex-encoded sense Sixteen two-character hex numbers
data; least significant byte is on the separated by spaces
sense2
left
sense3
sense4
sense5
sense6
sense7
sense8

An invocation example

This example shows events in January 2010:

Chapter 9. Clustered system diagnostic and service-aid commands 151

 lseventlog -filtervalue last_timestamp>=100101000000:last_timestamp<100201000000

This example shows all unfixed 1065 errors, in order of occurrence:

lseventlog -filtervalue error_code=1065:fixed=no

This example lists the most critical event:

lseventlog -order severity -count 1

This example shows the concise view:

lseventlog

sequence_number:last_timestamp:object_type:object_id:object_name:copy_id:
status:fixed:event_id:error_code:description
400:100106132413:vdisk:2:my_vdisk:1:alert:no:060001:1865:
Space Efficient Virtual Disk Copy offline due to insufficient space
401:100106140000:cluster::ldcluster-2::message:no:981001:
:Cluster Fabric View updated by fabric discovery

This example shows the full view:

1 lseventlog 120
1
1 sequence_number 120
1 first_timestamp 111130100419
1 first_timestamp_epoch 1322647459
1 last_timestamp 111130100419
1 last_timestamp_epoch 1322647459
1 object_type node
1 object_id 1
1 object_name node1
1 copy_id
1 reporting_node_id 1
1 reporting_node_name node1
1 root_sequence_number
1 event_count 1
1 status alert
1 fixed yes
1 auto_fixed no
1 notification_type error
1 event_id 073003
1 event_id_text More/Less fibre channel ports operational
1 error_code 1060
1 error_code_text Fibre Channel ports not operational
1 machine_type 21458F4
1 serial_number 75BZPMA
1 fru none
1 fixed_timestamp 111202141004
1 fixed_timestamp_epoch 1322835004
1 sense1 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1 sense8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

lsservicestatus
The lsservicestatus command displays the current status of a node.

152 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


sainfo lsservicestatus

panel_name

Parameters
panel_name
(Optional) If a panel_name is provided, the service recommendation for the local node is returned. If a
panel_name from the list returned by lsservicenodes is specified, then the service recommendation
for that node is returned. The command fails if the panel_name ID is not in the list returned by
lsservicenodes. This output is returned as the node status on all Universal Serial Bus (USB) flash
drive commands.

Note: For 2145 nodes the panel name is a six digit number on the node front panel. For 2076 nodes
the panel name is the value of the enclosure ID and canister ID or the enclosure serial number and
canister location.

Description

Use this command to display the current status of a node. This command provides all the information
that can be obtained using the front panel of a SAN Volume Controller node. You can run this command
on any node, even one that is not part of a clustered system (system), to obtain the vital product data
(VPD) and error status.

Table 22 shows possible outputs.

Table 22. lsservicestatus output
Attribute Value
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
console_ip An Internet Proticol (IP) Version 4 or 6 address
Note: This field might be blank if the node is not present in a system.
has_nas_key yes | no
Note: This field might be blank if the node is not present in a system.
system_id Specifies the ID of a system.
system_name Specifies the name of a system. When you use this parameter, the detailed view of the
specific system is displayed and any value that you specified by the -filtervalue parameter
is ignored. If you do not specify the system_name parameter, the concise view of all clusters
that match the filtering requirements that are specified by the -filtervalue parameter are
displayed.
system_status The error code is the same as the one displayed on the front panel.
system_ip_count The maximum number of management addresses you can configure.
system_ip_port This, and fields down to prefix_6, are repeated for each management address.
system_ip The IPv4 management IP address.
system_gw The IPv4 management IP gateway.
system_mask The IPv4 management IP mask.
system_ip_6 The IPv6 management IP address.
system_gw_6 The IPv6 management IP gateway.
system_prefix_6 The IPv6 management IP prefix.
node_id The ID of the node that is being configured.

Chapter 9. Clustered system diagnostic and service-aid commands 153

 Table 22. lsservicestatus output (continued)
Attribute Value
node_name The name of the node that is being configured.
node_status active | starting | service | candidate
config_node yes | no
hardware 8F2 | 8F4 | 8G4 | CF8 | 8A4 | other
service_IP_address The IPv4 service address for the node.
service_gateway The IPv4 service gateway for the node.
service_subnet_mask The IPv4 service mask for the node.
service_IP_address_6 The IPv6 service address for the node.
service_gateway_6 The IPv6 service gateway for the node.
service_prefix_6 The IPv6 service gateway for the node.
node_sw_version The software version of the node.
node_sw_build The build string for software on the node.
system_sw_build The CSM build that the system is running.
node_error_count The number of node errors.
node_error_data The type of node errors.
FC_port_count The number of Fibre Channel ports.
FC_port_id The beginning of repeating fields for each Fibre Channel port; the whole set of fields
indicated is repeated for each port.
port_status This should match the port on the front panel, enclosure, or canister.
port_speed This should match the port speed on the front panel, enclosure, or canister.
port_WWPN The worldwide port number of the port.
SFP_type long-wave | short-wave
ethernet_port_count The number of detected Ethernet ports.
ethernet_port_id Specifies the ID of an Ethernet port.
port_status online | offline | not configured
port_speed 10Mbps | 100Mbps | 1Gbps | 10Gbps | full | half
MAC A single MAC address.
3 vnport_count Number of VN ports created on top of each physical Fiber Channel over Ethernet (FCoE)
3 port.
3 vnport_id The VN port ID.
3 vnport_wwpn The WWPN assigned to the VN port.
3 vnport_FCF_mac The MAC address for the FCF to which the VN port is connected.
3 vnport_vlanid The VLAN ID used by the VN port. The value is blank for FC ports.
product_mtm The machine type and model.
product_serial The node serial number.
time_to_charge The estimated start time (in minutes) needed for 50% of the battery to be charged.
battery_charging The percentage of charge of the batteries.
disk_WWNN_prefix The most recently used WWNN prefix.
node_WWNN N/A
enclosure_WWNN_1 N/A

154 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 22. lsservicestatus output (continued)
Attribute Value
enclosure_WWNN_2 N/A
node_part_identity N/A
node_FRU_part N/A
enclosure_part_identity N/A
PSU_count N/A
PSU_id N/A
PSU_status N/A
battery_count N/A
battery_id N/A
battery_status N/A

Storwize® V7000: Table 23 shows possible outputs.

Note: On a node that is not part of a system, some of the fields are blank or N/A.
Table 23. lsservicestatus output
Attribute Value
console_ip An Internet Proticol (IP) Version 4 or 6 address
Note: This field might be blank if the node is not present in a system.
has_nas_key yes | no
Note: This field might be blank if the node is not present in a system.
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
system_id Specifies the ID of a system.
system_name Specifies the name of a system. When you use this parameter, the detailed view of
the specific system is displayed and any value that you specified by the -filtervalue
parameter is ignored. If you do not specify the cluster_name parameter, the concise
view of all systems that match the filtering requirements that are specified by the
-filtervalue parameter are displayed.
system_status The error code is the same as the one displayed on the front panel.
system_ip_count The maximum number of management addresses you can configure.
system_ip_port This, and fields down to prefix_6, are repeated for each management address.
system_ip The IPv4 management IP address.
system_gw The IPv4 management IP gateway.
system_mask The IPv4 management IP mask.
system_ip_6 The IPv6 management IP address.
system_gw_6 The IPv6 management IP gateway.
system_prefix_6 The IPv6 management IP prefix.
node_id The ID of the node that is being configured.
node_name The name of the node that is being configured.
node_status active | starting | service | candidate
config_node yes | no
hardware 8F2 | 8F4 | 8G4 | CF8 | 8A4 | other
service_IP_address The IPv4 service address for the node.

Chapter 9. Clustered system diagnostic and service-aid commands 155

Table 23. lsservicestatus output (continued)
Attribute Value
service_gateway The IPv4 service gateway for the node.
service_subnet_mask The IPv4 service mask for the node.
service_IP_address_6 The IPv6 service address for the node.
service_gateway_6 The IPv6 service gateway for the node.
service_prefix_6 The IPv6 service gateway for the node.
node_sw_version The software version of the node.
node_sw_build The build string for software on the node.
system_sw_build The CSM build that the system is running.
node_error_count The number of node errors.
node_error_data The type of node errors.
FC_port_count The number of Fibre Channel ports.
FC_port_id The beginning of repeating fields for each Fibre Channel port; the whole set of fields
indicated is repeated for each port.
port_status This should match the port on the front panel, enclosure, or canister.
port_speed This should match the port speed on the front panel, enclosure, or canister.
port_WWPN The worldwide port number of the port.
SFP_type long-wave | short-wave
ethernet_port_count The number of detected Ethernet ports.
ethernet_port_id Specifies the ID of an Ethernet port.
port_status online | offline | not configured
port_speed 10Mbps | 100Mbps | 1Gbps | 10Gbps | full | half
MAC A single MAC address.
product_mtm The machine type and model.
product_serial The node serial number.
time_to_charge The estimated start time (in minutes) needed for 50% of the battery to be charged.
battery_charging The percentage of charge of the batteries.
node_WWNN The last active WWNN stored in the node; blank if no system data.
enclosure_WWNN_1 Canister 1 WWNN from the enclosure VPD.
enclosure_WWNN_2 Canister 2 WWNN from the enclosure VPD.
node_part_identity The 11S string from the hardware VPD.
node_FRU_part if stored in node VPD
enclosure_part_identity The S11 data.
PSU_count The number of expected PSUs (two).
PSU_id The ID of the slot the PSU is in.
PSU_status missing | failed | active
battery_count The number of expected batteries (two).
battery_id The ID of the slot the battery is in.
battery_status missing | failed | charging | active
node_location_copy Equivalent to the panel name; blank if a node has been removed from a system.
node_product_mtm_copy Equivalent to panel product_mtm; blank if a node has been removed from a system.

156 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Table 23. lsservicestatus output (continued)
Attribute Value
node_product_serial_copy Equivalent to product_serial; blank if a node has been removed from a system.
node_WWNN_1_copy Equivalent to enclosure_WWNN_1; blank if a node has been removed from a
system.
node_WWNN_2_copy Equivalent to enclosure_WWNN_2; blank if a node has been removed from a
system.
latest_system_id The system ID running on the current enclosure; blank if a node has been removed
from a system.
next_system_id The system ID used to create the next system on this enclosure; it is blank if a node
has been removed from a system.
1 service_IP_mode Current mode of the service IPv4
1 v Empty if IPv4 is not active
1 v One of the following:
1 – static (if the service IP is set by the user)
1 – dhcp (if the service IP is set successfully using DHCP server)
1 – dhcpfallback (if the service IP is set to a default value after a DHCP server
1 request failed)
1 service_IP_mode_6 Current mode of the service IPv6
1 v Empty if IPv6 is not active
1 v Either static (if the service IP is set by the user) or dhcp (if the service IP set
1 successfully using DHCP server).

An invocation example
lsservicestatus

The resulting output

e panel_name 150434
e cluster_id 000002006ee1445e
e cluster_name Cluster_192.168.8.241
e cluster_status Active
e cluster_ip_count 2
e cluster_port 1
e cluster_ip 192.168.8.241
e cluster_gw 192.168.8.1
e cluster_mask 255.255.255.0
e cluster_ip_6
e cluster_gw_6
e cluster_prefix_6
e cluster_port 2
e cluster_ip
e cluster_gw
e cluster_mask
e cluster_ip_6
e cluster_gw_6
e cluster_prefix_6
e node_id 1
e node_name node1
e node_status Active
e config_node Yes
e hardware CF8
e hardware IT1
e service_IP_address
e service_gateway
e service_subnet_mask
e service_IP_address_6

Chapter 9. Clustered system diagnostic and service-aid commands 157

e service_gateway_6
e service_prefix_6
e service_IP_mode dhcpfallback
e node_sw_version 6.4.0.0
e node_sw_build 64.8.1205180000
e cluster_sw_build 64.8.1205180000
e node_error_count 0
e fc_ports 4
e port_id 1
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680140a22f
e SFP_type Short-wave
e port_id 2
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680130a22f
e SFP_type Short-wave
e port_id 3
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680110a22f
e SFP_type Short-wave
e port_id 4
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680120a22f
e SFP_type Short-wave
e ethernet_ports 4
e ethernet_port_id 1
e port_status Link Online
e port_speed 1Gb/s - Full
e MAC 00:21:5e:db:30:38
e vnport_count 0
e ethernet_port_id 2
e port_status Not Configured
e port_speed
e MAC 00:21:5e:db:30:3a
e vnport_count 0
e ethernet_port_id 3
e port_status Not Configured
e port_speed 10Gb/s - Full
e MAC 00:00:c9:bc:6f:22
e vnport_count 0
e ethernet_port_id 4
e port_status Not Configured
e port_speed 10Gb/s - Full
e MAC 00:00:c9:bc:6f:20
e vnport_count 0
e product_mtm 2145-CF8
e
e product_serial 75HAXYA
e time_to_charge 0
e battery_charging 0
e dump_name 150434
e node_WWNN 500507680100a22f
e disk_WWNN_suffix 0A22F
e panel_WWNN_suffix 0A22F
e UPS_serial_number
e UPS_status
e enclosure_WWNN_1
e enclosure_WWNN_2
e node_part_identity
e node_FRU_part
e enclosure_identity
e PSU_count
e PSU_id

158 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e PSU_status
e PSU_id
e PSU_status
e Battery_count
e Battery_id
e Battery_status
e Battery_id
e Battery_status
e node_location_copy
e node_product_mtm_copy
e node_product_serial_copy
e node_WWNN_1_copy
e node_WWNN_2_copy
e latest_cluster_id
e next_cluster_id
e console_IP 192.168.8.241:443
e has_nas_key no
e fc_io_ports 6
e fc_io_port_id 1
e fc_io_port_WWPN 500507680140a22f
e fc_io_port_switch_WWPN 200000051e630f9a
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 1
e fc_io_port_id 2
e fc_io_port_WWPN 500507680130a22f
e fc_io_port_switch_WWPN 200400051e630f9a
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 2
e fc_io_port_id 3
e fc_io_port_WWPN 500507680110a22f
e fc_io_port_switch_WWPN 200000051e7ded49
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 3
e fc_io_port_id 4
e fc_io_port_WWPN 500507680120a22f
e fc_io_port_switch_WWPN 200400051e7ded49
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 4
e fc_io_port_id 5
e fc_io_port_WWPN 500507680150a22f
e fc_io_port_switch_WWPN 2064000573cd6201
e fc_io_port_state Active
e fc_io_port_FCF_MAC 00:05:73:CD:62:00
e fc_io_port_vlanid 100
e fc_io_port_type Ethernet
e fc_io_port_type_port_id 3
e fc_io_port_id 6
e fc_io_port_WWPN 500507680160a22f
e fc_io_port_switch_WWPN 2064000573c8a701
e fc_io_port_state Active
e fc_io_port_FCF_MAC 00:05:73:C8:A7:00
e fc_io_port_vlanid 100
e fc_io_port_type Ethernet
e fc_io_port_type_port_id 4service_IP_mode
e service_IP_mode_6

Chapter 9. Clustered system diagnostic and service-aid commands 159

lssyslogserver
The lssyslogserver command returns a concise list or a detailed view of syslog servers that are
configured on the cluster.

Syntax


lssyslogserver

-nohdr -delim delimiter syslog_server_name
syslog_server_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
syslog_server_name | syslog_server_id
(Optional) Specifies the name or ID of an existing syslog server. When you use this parameter, a
detailed view of the specified syslog server is returned. If you do not specify a syslog server name or
ID, then a concise view of all syslog servers is displayed.

Description

Use this command to display a concise list or a detailed view of syslog servers that are configured on the
cluster.

A concise invocation example

lssyslogserver -delim :

The concise resulting output

id:name:IP_address:facility:error:warning:info
0:syslog0:192.135.60.4:0:on:on:on
1:newserver:192.136.70.7:4:on:off:off

A detailed invocation example

lssyslogserver 0

The detailed resulting output

id 0
name syslog0
IP_address 192.135.60.4

160 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 facility 0
error on
warning on
info on

setlocale
The setlocale command changes the locale setting for the clustered system (system). It also changes
command output to the chosen language.

Syntax


setlocale -locale locale_id


Parameters
-locale locale_id
e Specifies the locale ID. The value must be a numeric value depending on the desired language (as
e indicated below)

Description

This command changes the language in which error messages are displayed as output from the
command-line interface. Subsequently, all error messages from the command-line tools are generated in
the chosen language. This command is run when you request a change of language (locale) and is
generally run from the web page. Issue the setlocale command to change the locale setting for the
system; all interface output is changed to the chosen language. For example, to change the language to
Japanese, type the following:

setlocale -locale 3

where 3 is the value for Japanese. The following values are supported:
v 0 US English (default)
v 1 Simplified Chinese
v 2 Traditional Chinese
v 3 Japanese
v 4 French
v 5 German
v 6 Italian
v 7 Spanish
v 8 Korean
v 9 Portuguese (Brazilian)

Note: This command does not change the front panel display panel settings.

An invocation example (where 3 is Japanese)

setlocale -locale 3

The resulting output

No feedback

An invocation example (where 8 is Korean)

setlocale -locale 8

Chapter 9. Clustered system diagnostic and service-aid commands 161

The resulting output
No feedback

svqueryclock
The svqueryclock command returns the date, time, and current time-zone of the clustered system
(system).

Syntax


svqueryclock


Description

This command returns the date, time and current time-zone of the system.

An invocation example
svqueryclock

The resulting output

Mon Nov 25 14:59:28 GMT 2002

writesernum
Use the writesernum command to write the node serial number into the planar NVRAM.

Syntax


writesernum -sernum serial_number node_id

node_name

Parameters
-sernum serial_number
(Required) Specifies the serial number to write to the nonvolatile memory of the system planar.
node_id | node_name
(Required) Specifies the node where the system planar is located. The serial number is written to this
system planar. This name is not the worldwide node name (WWNN).

Description

This command writes the node serial number into the planar NVRAM and then reboots the system. You
can find the serial number at the front of the node without having to remove it from the rack. The
seven-digit alphanumeric serial number is located on a label on the front of the node. The serial number
on the label might contain a hyphen. Omit this hyphen when typing the serial number with the
writesernum command.

Note: Once you have written the serial number to the planar NVRAM, you can issue the lsnodevpd
command to verify that the number is correct. The system_serial_number field contains the serial number.

An invocation example
writesernum -sernum 1300027 node1

162 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
The resulting output
No feedback

Chapter 9. Clustered system diagnostic and service-aid commands 163

164 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 10. Controller command
The controller command modifies the name of a storage controller.

chcontroller
The chcontroller command modifies the attributes of a controller.

Syntax


chcontroller

-name new_name -allowquorum yes
no

controller_id

controller_name

Parameters
-name new_name
(Optional) Specifies the new name to be assigned to the controller.
-allowquorum yes | no
(Optional) Specifies that the controller is allowed or is not allowed to support quorum disks. A value
of yes enables a suitable controller to support quorum disks. A value of no disables a controller from
supporting quorum disks, provided that the specified controller is not currently hosting a quorum
disk.
controller_id | controller_name
(Required) Specifies the controller to modify; use either the controller name or the controller ID.

Description

This command changes the name of the controller that is specified by the controller_id | controller_name
variable to the value that you specify with the -name parameter.

If any controller that is associated with an MDisk shows the allow_quorum attribute set to no with the
lscontroller command, the set quorum action fails for that MDisk. Before using the chcontroller
command to set the -allowquorum parameter to yes on any disk controller, check the following website to
see whether the controller supports quorum.

www.ibm.com/storage/support/2145

You can add a new disk controller system to your SAN at any time. Follow the switch zoning guidelines
in the section about switch zoning. Also, ensure that the controller is set up correctly for use with the
clustered system (system).

To add a new disk controller system to a running configuration, ensure that the system has detected the
new storage MDisks by issuing the detectmdisk command. The controller has automatically been
assigned a default name. If you are unsure of which controller is presenting the MDisks, issue the
lscontroller command to list the controllers. The new controller is listed with the highest numbered
default name. Record the controller name and follow the instructions in the section about determining a
disk controller system name.

© Copyright IBM Corp. 2003, 2012 165

Give this controller a descriptive name by issuing the following command:

chcontroller -name newname oldname

List the unmanaged MDisks by issuing the following command:

lsmdisk -filtervalue mode=unmanaged:controller_name=newname

These MDisks correspond to the RAID arrays or partitions that you have created. Record the field
controller LUN number. The field controller LUN number corresponds with the LUN number that you
assigned to each of the arrays or partitions.

Create a new managed disk group and add only the RAID arrays that belong to the new controller to
this storage pool. Avoid mixing RAID types; for each set of RAID array types (for example, RAID-5 or
RAID-1), create a new storage pool. Assign this storage pool an appropriate name; if your controller is
called FAST650-abc and the storage pool contains RAID-5 arrays, assign the MDisk a name similar to
F600-abc-R5. Issue the following command:

mkmdiskgrp -ext 16 -name mdisk_grp_name

-mdisk colon-separated list of RAID-x mdisks returned

Note: This creates a new storage pool with an extent size of 16 MB.

An invocation example
chcontroller -name newtwo 2

The resulting output

No feedback

166 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 11. Drive commands
Drive commands capture information that can assist you with managing drives.

applydrivesoftware
Use the applydrivesoftware command to upgrade drives.

Syntax
e firmware


applydrivesoftware -file name -type fpga -drive drive_id


-force

Parameters
-filename
e (Required) Specifies the firmware upgrade file name that exists in the /home/admin/upgrade/
e directory. This must be an alphanumeric string of up to 255 characters.
-type
e (Required) Specifies the type of download. This can be either firmware or fpga.

e Remember: Drives using firmware can be upgraded concurrently, but this does not affect the Field
e Programmable Gate Array (FPGA).
-drivedrive_id
e (Required) Specifies the ID of the drive to be upgraded. This must be a numeric string.
-force
e (Optional) This disables redundancy checking. In the unlikely event that a software installation causes
e the drive to fail, disabling redundancy checking might cause loss of data, or loss of access to data. If
e specified no check is performed for volumes that are dependent on this drive.

e Note: This parameter is recommended for non-redundant RAID configuration drives, but is not
e recommended for redundant RAID configuration drives.

Description
This command upgrades drives. Additionally, the system applies updates to the drive if there is an
update available for that drive type. The system should stop if any problems occur.

e Additionally, the system checks if any volumes are dependent on the drive, and the command fails if any
e are dependent. This verification is required to install software on drives that are part of non-redundant
e RAID configurations. Use the -force parameter to bypass this verification.

e For non-redundant RAID configuration drives the -force parameter is not required. For example if the
e only volumes on these drives are mirrored volumes, an attempt can be made without the -force
e parameter. (The parameter will not work if there are dependent volumes.) If the parameter does not start
e the download because there are dependent volumes, specify lsdependentvdisks -drive drive_id on the
e drive ID being upgraded to find out which volumes are dependent on the drive. After looking at the list

© Copyright IBM Corp. 2003, 2012 167

e of dependent volumes and back-up the volumes, if none are affected use the -force parameter.

An invocation example

applydrivesoftware -file drivemicrocodepackagev1 -type fpga -drive 4

The resulting output

No feedback

chdrive
Use the chdrive command to change the drive properties.

Syntax


chdrive -use drive_id

unused -allowdegraded
candidate
spare
failed
-task format
certify
recover

Parameters
-use
Describes the role of the drive:
v unused: the drive is not in use and will not be used as a spare
v candidate: the drive is available for use in an array
v spare: the drive can be used as a hot spare if required
v failed: the drive has failed.

Note: To create member drives, add the drives to arrays using the charray command.
-allowdegraded
(Optional) Permits permission for a change of drive to continue, even if a hotspare is not available.
-task
Causes the drive to perform a task:
v format: a drive is formatted for use in an array; only permitted when drive is a candidate or has
failed validation
v certify: the disk is analyzed to verify the integrity of the data it contains; permitted for any drive
that is a candidate, spare, or member
v recover: recover an offline SSD drive without losing data; permitted when the drive is offline
because a build is required, or when the drive has failed validation

Note: You can track the drive progress using the lsdriveprogress command.
drive_id
The identity of the drive.

168 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

Use this command to change the drive properties.

chdrive -use spare 1

lsdrive
Use the lsdrive command to display configuration information and drive VPD.

Syntax


lsdrive

-bytes drive_id

Parameters
2 -bytes
e (Optional) The size (capacity) of the drive in bytes.
drive_id
e (Optional) The identity of the drive.

Description

Use this command to display configuration information and drive VPD.

Note: Filtering should be permitted on all concise fields.

Table 24 describes possible outputs.

Table 24. lsdrive output
Attribute Value
id The ID of the drive.
status The summary status of the drive.
error_sequence_number The error sequence number describing the cause of the drive status:
v online: blank
v degraded: populated if associated with an error
v offline: must be populated
Note: Error sequence numbers indicate an entry in the event log. This includes entries
that are both errors, and informational messages (for example, the drive is formatting).
use The current role of the drive:
v unused: the drive which is not configured to be used by anything
v candidate: the drive is available to be configured
v spare: the drive is configured as a spare, to be used if the arrays fail members
v member: the drive is configured as a member of an array
v failed: the drive has been rejected, and is no longer available for use
UID The unique ID reported by the drive.
tech_type The drive technology used.
capacity The capacity of disk, excluding quorum area.
block_size The block size of the disk.
vendor_id The manufacturer of the drive.

Chapter 11. Drive commands 169

Table 24. lsdrive output (continued)
Attribute Value
product_id The product ID of the drive.
FRU_part_number The FRU part number of the drive.
FRU_identity The 11S number combining manufacturing part number and serial number.
RPM The specified RPM of the disk.
firmware_level Firmware level of the disk; blank if unknown.
FPGA_level The FPGA level, if applicable; blank if not applicable or unknown.
mdisk_id The ID of the array MDisk that the drive is a member of.
mdisk_name The name of the MDisk that the drive is a member of.
member_id The ID of the MDisk array member.
enclosure_id v If the drive is contained in an enclosure (not a node) and the slot position is known,
this is the ID of the enclosure in which the drive is located.
v If the drive is contained in a node (not an enclosure), this is blank.
v If the enclosure ID has not been determined yet, this is blank.
slot_id The slot_id of the drive in the enclosure or node. It can be referred to as the drive bay or
location. This can be blank.
node_name For a drive contained within a node,the node name where the drive is located. For a
drive contained within an enclosure, it is blank.
node_id For a drive contained within a node, the node ID where the drive is located. For a drive
contained within an enclosure, blank.
quorum_id The ID of quorum disk; blank if not quorum disk.
port_1_status The connectivity status of the target for MDisk enumeration, with states.
port_2_status

Concise invocation example:

lsdrive -delim :

The resulting output:

id:status:error_sequence_number:use:tech_type:capacity:mdisk_id:mdisk_name:member_id:enclosure_id:slot_id
0:online::member:sas_ssd:20GB:0:mdisk0:0:1:2
1:offline:345:member:sas_ssd:20GB:0:mdisk0:0:1:3
2:online::member:sas_ssd:20GB:0:mdisk0:0:1:4

A detailed invocation example:

lsdrive 0

The resulting output:

id:0
status:online
error_sequence_number:
use:member
UID:20000004cf4cd2c0
tech_type:ssd
capacity:20GB
block_size:512
vendor_id:IBM
product_id:I8MR1337 W00Y4Y1
FRU_part_number:AAAAAAA
FRU_identity:11S1817115Y41337171001
RPM:15000

170 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 firmware_level:3.02

FPGA_level:1.99
mdisk_id:0
mdisk_name:mdisk0
member_id:0
enclosure_id:1
slot:2
node_id:
node_name:
quorum_id:
port_1_status:online
port_2_status:online

lsdrivelba
Use the lsdrivelba command to map array MDisk logical block address (LBA) to a set of drives.

Syntax


lsdrivelba

-delim delimiter -mdisklba lba


-mdisk mdisk_id | mdisk_name

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
e -mdisklba lba
(Optional) The logical block address (LBA) on the MDisk. The LBA must be specified in hex, with a
0x prefix.
e -mdiskmdisk_id | mdisk_name
e (Optional) The ID or name of the MDisk.

Description

This command maps the array MDisk logical block address (LBA) to a set of drives.

Table 25 describes possible outputs.

Table 25. lsdrivelba output
Attribute Value
drive_id The ID of drive; blank if no configured array member exists (for example, in a degraded
array).

Chapter 11. Drive commands 171

Table 25. lsdrivelba output (continued)
Attribute Value
type The type of information on the disk:
v parity - LBA range contains parity (RAID levels 5 and 6 only)
v qparity - LBA range contains qparity (RAID level 6 only)
v data - LBA range contains data
drive_lba The LBA on the drive.
drive_start The start of range of LBAs (strip) on the drive.
drive_end The end of range of LBAs (strip) on the drive.
mdisk_start The start of range of LBAs (strip) on the array MDisk.
mdisk_end The end of range of LBAs (strip) on the array MDisk.

This is an example of a five-member RAID-5 array with strip size of 256 KB:

An invocation example
lsdrivelba -delim : -mdisklba 0x000 -mdisk 2

The resulting output

drive_id:type:drive_lba:drive_start:drive_end:mdisk_start:mdisk_end
0:data:0x0000000000000000:0x0000000000000000:0x0000000000000200:0x0000000000000000:0x0000000000000200
4:parity:0x0000000000000000:0x0000000000000000:0x0000000000000200:0x0000000000000000:0x0000000000000200

lsdriveprogress
Use the lsdriveprogress command to view the progress of various drive tasks.

Syntax


lsdriveprogress

-delim delimiter drive_id

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
drive_id
(Optional) The drive for which you want to view progress.

Description

The following outputs are possible:

drive_id
The ID for the drive with the active task.
task The type of task:

172 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 v format
v certify
v recover
progress
The percentage complete of the job.
estimated_completion_time
The estimated completion time (YYMMDDHHMMSS), where:
v 'Y' is year
v 'M' is month
v 'D' is day
v 'H' is hour
v 'S' is second
.

An invocation example
lsdriveprogress -delim :

The resulting output

drive_id:task:progress:estimated_completion_time
0:format:10:091118131056
9:certify:25:991231235959

An invocation example
lsdriveprogress -delim : 9

The resulting output

9:certify:25:991231235959

triggerdrivedump
Use the triggerdrivedump command to collect support data from a disk drive. This data can help to
understand problems with the drive, and does not contain any data that applications may have written to
the drive.

Syntax


triggerdrivedump drive_id


Parameters
drive_id
The ID of the drive to dump.

An invocation example
triggerdrivedump 1

The resulting output

Dump file created on node id [2]

Chapter 11. Drive commands 173

174 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 12. Email and event notification commands
You can use the command-line interface (CLI) to enable your system to send notifications.

chemail
The chemail command can be used to set or modify contact information for email event notifications. To
modify settings, at least one of the parameters must be specified.

Syntax


chemail

-reply reply_email_address -contact contact_name

-primary primary_telephone_number -alternate alternate_telephone_number

-location location -contact2 contact_name2

-primary2 primary_telephone_number2 -alternate2 alternate_telephone_number2


-nocontact2

Parameters
-reply reply_email_address
(Optional) Specifies the email address to which a reply is sent.
-contact contact_name
(Optional) Specifies the name of the person to receive the email.
-primary primary_telephone_number
(Optional) Specifies the primary contact telephone number.
-alternate alternate_telephone_number
(Optional) Specifies the alternate contact telephone number that is used when you cannot reach the
primary contact on the primary phone.
-location location
(Optional) Specifies the physical location of the system that is reporting the error. The location value
must not contain punctuation or any other characters that are not alphanumeric or spaces.
-contact2 contact_name2
(Optional) Specifies the name of the second contact person to receive the email.
-primary2 primary_telephone_number2
(Optional) Specifies the primary contact telephone number for the second contact person.
-alternate2 alternate_telephone_number2
(Optional) Specifies the alternate contact telephone number for the second contact person.
-nocontact2
(Optional) Removes all the contact details for the second contact person.

© Copyright IBM Corp. 2003, 2012 175

Description

This command sets or modifies contact information that is used by the email event notification facility.

Note: If you are starting the email event notification facility, the reply, contact, primary, and location
parameters are required. If you are modifying contact information used by the email event notification
facility, at least one of the parameters must be specified.

Remember: When considering e-mail addresses:

v Alphanumeric characters plus underscore (_), at (@), and dot (.) characters are permitted.
v There must be exactly one @ character in the string, and the @ characters must not start or end the
string.

An invocation example
chemail -primary 0441234567 -location ’room 256 floor 1 IBM’

The resulting output

[No feedback]

chemailserver
The chemailserver command modifies the parameters of an existing email server object.

Syntax


chemailserver

-name server_name -ip ip_address

email_server_name

-port port email_server_id

Parameters
-name server_name
(Optional) Specifies a unique name to assign to the email server object. The name must be a 1-
through 63-character string, and cannot start with a hyphen or number. When specifying a server
name, emailserver is a reserved word.
-ip ip_address
(Optional) Specifies the IP address of the email server object. This must be a valid IPv4 or IPv6
address. IPv6 addresses can be zero compressed.
-port port
(Optional) Specifies the port number for the email server. This must be a value of 0 - 65535. The
default value is 25.
email_server_name | email_server_id
(Required) Specifies the name or ID of the server object to be modified.

Description

Use this command to change the settings of an existing email server object. The email server object
describes a remote Simple Mail Transfer Protocol (SMTP) email server.

You must specify either the current name or the ID of the object returned at creation time. Use the
lsemailserver command to obtain this ID.

176 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
An invocation example
chemailserver -name newserver 0

The resulting output

none

chemailuser
The chemailuser command modifies the settings that are defined for an email recipient.

Syntax


chemailuser

-address user_address -usertype support
local

on on on
-error off -warning off -info off

userid_or_name

-name user_name on
-inventory off

Parameters
-address user_address
(Optional) Specifies the email address of the person receiving the email or inventory notifications, or
both. The user_address value must be unique.
-usertype support | local
(Optional) Specifies the type of user, either local or support, based on the following definitions:
support
Address of the support organization that provides vendor support.
local All other addresses.
-error on | off
(Optional) Specifies whether the recipient receives error-type event notifications. Set to on, error-type
event notifications are sent to the email recipient. Set to off, error-type event notifications are not sent
to the recipient.
-warning on | off
(Optional) Specifies whether the recipient receives warning-type event notifications. Set to on,
warning-type event notifications are sent to the email recipient. Set to off, warning-type event
notifications are not sent to the recipient.
-info on | off
(Optional) Specifies whether the recipient receives informational event notifications. Set to on,
informational event notifications are sent to the email recipient. Set to off, informational event
notifications are not sent to the recipient.
-name user_name
(Optional) Specifies the user name of the new email event notification recipient. The user_name value
must be unique, must not contain spaces, and must not contain all numbers. The name emailusern,
where n is a number, is reserved and cannot be specified as one of your user names.
-inventory on | off
(Optional) Specifies whether this recipient receives inventory email notifications.

Chapter 12. Email and event notification commands 177

 userid_or_name
(Required) Specifies the email recipient for whom you are modifying settings.

Description

This command modifies the settings that are established for an email recipient. Standard rules regarding
names apply; therefore, it is not possible to change a name to emailusern, where n is a number.

Note: Before the usertype parameter can be set to support, the -warning and -info flags must be set to
off.

Remember: When considering e-mail addresses:

v Alphanumeric characters plus underscore (_), at (@), and dot (.) characters are permitted.
v There must be exactly one @ character in the string.

An invocation example

The following example modifies email settings for email recipient manager2008:
chemailuser -usertype local manager2008

The resulting output

No feedback

e An invocation example

e The following example modifies email settings:

e chemailuser -address [email protected] -name Fred

e The resulting output

e No feedback

chsnmpserver
The chsnmpserver command modifies the parameters of an existing SNMP server.

Syntax


chsnmpserver

-name server_name -ip ip_address

-community community -error on -warning on
off off

snmp_server_name

-info on -port port snmp_server_id
off

Parameters
-name server_name
(Optional) Specifies a name to assign to the SNMP server. The name must be unique. When
specifying a server name, snmp is a reserved word.

178 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-ip ip_address
(Optional) Specifies an IP address to assign to the SNMP server. This must be a valid IPv4 or IPv6
address.
-community community
(Optional) Specifies the community name for the SNMP server.
-error on | off
(Optional) Specifies whether the server receives error notifications. Set to on, error notifications are
sent to the SNMP server. Set to off, error notifications are not sent to the SNMP server.
-warning on | off
(Optional) Specifies whether the server receives warning notifications. Set to on, warning notifications
are sent to the SNMP server. Set to off, warning notifications are not sent to the SNMP server.
-info on | off
(Optional) Specifies whether the server receives information notifications. Set to on, information
notifications are sent to the SNMP server. Set to off, information notifications are not sent to the
SNMP server.
-port port
(Optional) Specifies the remote port number for the SNMP server. This must be a value of 1 - 65535.
snmp_server_name | snmp_server_id
(Required) Specifies the name or ID of the server to be modified.

Description

Use this command to change the settings of an existing SNMP server. You must specify either the current
name of the server or the ID returned at creation time. Use the lssnmpserver command to obtain this ID.

An invocation example
chsnmpserver -name newserver 0

The resulting output

No feedback

chsyslogserver
The chsyslogserver command modifies the parameters of an existing syslog server.

Syntax


chsyslogserver

-name server_name -ip ip_address

-facility facility -error on -warning on
off off

syslog_server_name

-info on syslog_server_id
off

Parameters
-name server_name
(Optional) Specifies a name to assign to the syslog server. The name must be unique. When
specifying a server name, syslog is a reserved word.

Chapter 12. Email and event notification commands 179

-ip ip_address
(Optional) Specifies an IP address to assign to the syslog server. This must be a valid IPv4 or IPv6
address.
-facility facility
(Optional) Specifies a facility number to identify the origin of the message to the receiving server.
Servers configured with facility values of 0 - 3 receive syslog messages in concise format. Servers
configured with facility values of 4 - 7 receive syslog messages in fully-expanded format.
-error on | off
(Optional) Specifies whether the server receives error notifications. Set to on, error notifications are
sent to the syslog server. Set to off, error notifications are not sent to the syslog server.
-warning on | off
(Optional) Specifies whether the server receives warning notifications. Set to on, warning notifications
are sent to the syslog server. Set to off, warning notifications are not sent to the syslog server.
-info on | off
(Optional) Specifies whether the server receives information notifications. Set to on, information
notifications are sent to the syslog server. Set to off, information notifications are not sent to the
syslog server.
syslog_server_name | syslog_server_id
(Required) Specifies the name or ID of the server to be modified.

Description

Use this command to change the settings of an existing syslog server. You must specify either the current
name of the server or the ID returned at creation time. Use the lssyslogserver command to obtain this
ID.

An invocation example
chsyslogserver -facility 5 2

The resulting output

none

mkemailserver
The mkemailserver command creates an email server object that describes a remote Simple Mail Transfer
Protocol (SMTP) email server.

Syntax


mkemailserver -ip ip_address

-name server_name -port port

Parameters
-name server_name
(Optional) Specifies a unique name to assign to the email server object. The name must be a 1-
through 63-character string, and cannot start with a hyphen or number. If a name is not specified,
then a system default of emailservern is applied, where n is the object ID. When specifying a server
name, emailserver is a reserved word.
-ip ip_address
(Required) Specifies the IP address of a remote email server. This must be a valid IPv4 or IPv6
address. IPv6 addresses can be zero compressed.

180 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-port port
(Optional) Specifies the port number for the email server. This must be a value of 1 - 65535. The
default value is 25.

Description

This command creates an email server object that represents the SMTP server. The SAN Volume
Controller uses the email server to send event notification and inventory emails to email users. It can
transmit any combination of error, warning, and informational notification types.

The SAN Volume Controller supports up to six email servers to provide redundant access to the external
email network. The email servers are used in turn until the email is successfully sent from the SAN
Volume Controller. The attempt is successful when the SAN Volume Controller gets a positive
acknowledgement from an email server that the email has been received by the server.

An invocation example
mkemailserver -ip 2.2.2.2 -port 78

The resulting output

Emailserver id [2] successfully created

mkemailuser
The mkemailuser command adds a recipient of email event and inventory notifications to the email event
notification facility. You can add up to twelve recipients, one recipient at a time.

Syntax


mkemailuser -address user_address

-name user_name

-usertype support

local on on
-error off -warning off


on on
-info off -inventory off

Parameters
-name user_name
(Optional) Specifies the name of the person who is the recipient of email event notifications. The
user_name value must be unique, must not contain spaces, and must not contain only numbers. If you
do not specify a user name, the system automatically assigns a user name in the format of
emailusern, where n is a number beginning with 0 (emailuser0, emailuser1, and so on).
The name emailusern, where n is a number, is reserved and cannot be used as one of your user
names.
-address user_address
(Required) Specifies the email address of the person receiving the email event or inventory
notifications, or both. The user_address value must be unique.
-usertype support| local
(Required) Specifies the type of user, either support or local, based on the following definitions:

Chapter 12. Email and event notification commands 181

 support
Address of the support organization that provides vendor support.
local All other addresses.
-error on | off
(Optional) Specifies whether the recipient receives error-type event notifications. Set to on, error-type
event notifications are sent to the email recipient. Set to off, error-type event notifications are not sent
to the recipient. The default value is on.
-warning on | off
(Optional) Specifies whether the recipient receives warning-type event notifications. Set to on,
warning-type event notifications are sent to the email recipient. Set to off, warning-type event
notifications are not sent to the recipient. The default value is on.
-info on | off
(Optional) Specifies whether the recipient receives informational event notifications. Set to on,
informational event notifications are sent to the email recipient. Set to off, informational event
notifications are not sent to the recipient. The default value is on.
-inventory on | off
(Optional) Specifies whether this recipient receives inventory email notifications. The default value is
off.

Description

This command adds email recipients to the email event and inventory notification facility. You can add
up to twelve recipients, one recipient at a time. When an email user is added, if a user name is not
specified, a default name is allocated by the system. This default name has the form of emailuser1,
emailuser2, and so on. Email notification starts when you process the startemail command.

Note: Before you can set the usertype parameter to support, turn the -warning and -info flags off.

Remember: When considering e-mail addresses:

v Alphanumeric characters plus underscore (_), at (@), and dot (.) characters are permitted.
v There must be exactly one @ character in the string.

An invocation example
mkemailuser -address [email protected] -error on -usertype local

The resulting output

email user, id [2], successfully created

mksnmpserver
The mksnmpserver command creates an SNMP server to receive notifications.

Syntax


mksnmpserver -ip ip_address

-name server_name

-community community on on
-error off -warning off

182 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide



on -port port
-info off

Parameters
-name server_name
(Optional) Specifies a unique name to assign to the SNMP server. If a name is not specified, then a
system default of snmpn is applied, where n is the ID of the server. When specifying a server name,
snmp is a reserved word.
-ip ip_address
(Required) Specifies the IP address of the SNMP server. This must be a valid IPv4 or IPv6 address.
-community community
(Optional) Specifies the community name for the SNMP server. If you do not specify a community
name, then the default name of public is used.
-error on | off
(Optional) Specifies whether the server receives error notifications. Set to on, error notifications are
sent to the SNMP server. Set to off, error notifications are not sent to the SNMP server. The default
value is on.
-warning on | off
(Optional) Specifies whether the server receives warning notifications. Set to on, warning notifications
are sent to the SNMP server. Set to off, warning notifications are not sent to the SNMP server. The
default value is on.
-info on | off
(Optional) Specifies whether the server receives information notifications. Set to on, information
notifications are sent to the SNMP server. Set to off, information notifications are not sent to the
SNMP server. The default value is on.
-port port
(Optional) Specifies the remote port number for the SNMP server. This must be a value of 1 - 65535.
The default value is 162.

Description

This command creates an SNMP server to receive notifications.

SAN Volume Controller supports a maximum of 6 SNMP servers.

An invocation example
mksnmpserver -ip 2.2.2.2 -port 78

The resulting output

SNMP Server id [2] successfully created

mksyslogserver
The mksyslogserver command creates a syslog server to receive notifications.

Syntax


mksyslogserver -ip ip_address

-name server_name

Chapter 12. Email and event notification commands 183




-facility facility on on
-error off -warning off


on
-info off

Parameters
-name server_name
(Optional) Specifies a unique name to assign to the syslog server. If a name is not specified, then a
system default of syslogn is applied, where n is the ID of the server. When specifying a server name,
syslog is a reserved word.
-ip ip_address
(Required) Specifies the IP address of the syslog server. This must be a valid IPv4 or IPv6 address.
-facility facility
(Optional) Specifies the facility number used in syslog messages. This number identifies the origin of
the message to the receiving server. Servers configured with facility values of 0 - 3 receive syslog
messages in concise format. Servers configured with facility values of 4 - 7 receive syslog messages in
fully-expanded format. The default value is 0.
-error on | off
(Optional) Specifies whether the server receives error notifications. Set to on, error notifications are
sent to the syslog server. Set to off, error notifications are not sent to the syslog server. The default
value is on.
-warning on | off
(Optional) Specifies whether the server receives warning notifications. Set to on, warning notifications
are sent to the syslog server. Set to off, warning notifications are not sent to the syslog server. The
default value is on.
-info on | off
(Optional) Specifies whether the server receives information notifications. Set to on, information
notifications are sent to the syslog server. Set to off, information notifications are not sent to the
syslog server. The default value is on.

Description

This command creates a syslog server to receive notifications. The syslog protocol is a client-server
standard for forwarding log messages from a sender to a receiver on an IP network. Syslog can be used
to integrate log messages from different types of systems into a central repository.

SAN Volume Controller supports a maximum of 6 syslog servers.

An invocation example
mksyslogserver -ip 1.2.3.4

The resulting output

Syslog Server id [2] successfully created

rmemailserver
The rmemailserver command deletes the specified email server object.

184 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


rmemailserver email_server_name

email_server_id

Parameters
email_server_name | email_server_id
(Required) Specifies the name or ID of the email server object to be deleted.

Description

Use this command to delete an existing email server object that describes a remote Simple Mail Transfer
Protocol (SMTP) email server. You must specify either the current name or the ID of the object returned at
creation time. Use the lsemailserver command to obtain this ID.

Note: Email service stops when the last email server is removed. Use the startemail command to
reactivate the email and inventory notification function after at least one email server has been
configured.

An invocation example
rmemailserver email4

The resulting output

none

rmemailuser
The rmemailuser command allows you to remove a previously defined email recipient from your system.

Syntax


rmemailuser userid_or_name


Parameters
userid_or_name
(Required) Specifies the user ID or user name of the email recipient to remove.

Description

This command removes an existing email recipient from the system.

An invocation example

The following example removes email recipient manager2008:

rmemailuser manager2008

The resulting output

[No feedback]

An invocation example

The following example removes email recipient 2:

Chapter 12. Email and event notification commands 185

rmemailuser 2

The resulting output

[No feedback]

rmsnmpserver
The rmsnmpserver command deletes the specified SNMP server.

Syntax


rmsnmpserver snmp_server_name

snmp_server_id

Parameters
snmp_server_name | snmp_server_id
(Required) Specifies the name or ID of the SNMP server to be deleted.

Description

Use this command to delete an existing SNMP server. You must specify either the current name of the
server or the ID returned at creation time. Use the lssnmpserver command to obtain this ID.

An invocation example
rmsnmpserver snmp4

The resulting output

none

rmsyslogserver
The rmsyslogserver command deletes the specified syslog server.

Syntax


rmsyslogserver syslog_server_name

syslog_server_id

Parameters
syslog_server_name | syslog_server_id
(Required) Specifies the name or ID of the syslog server to be deleted.

Description

Use this command to delete an existing syslog server. You must specify either the current name of the
server or the ID returned at creation time. Use the lssyslogserver command to obtain this ID.

An invocation example
rmsyslogserver 2

The resulting output

none

186 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
sendinventoryemail
The sendinventoryemail command sends an inventory email notification to all email recipients who are
enabled to receive inventory email notifications. There are no parameters for this command.

Syntax


sendinventoryemail


Parameters

There are no parameters for this command.

Description

This command sends an inventory email notification to all email recipients who are enabled to receive
inventory email notifications. This command fails if the startemail command has not been processed and
at least one email recipient using the email event and inventory notification facility has not been set up to
receive inventory email notifications. This command also fails if the email infrastructure has not been set
up.

An invocation example

In the following example, you send an inventory email notification to all email recipients who are
enabled to receive them:
sendinventoryemail

The resulting output

[No feedback]

startemail
The startemail command activates the email and inventory notification function. There are no
parameters for this command.

Syntax


startemail


Parameters

There are no parameters for this command.

Description

This command enables the email event notification service. No emails are sent to users until the
startemail command has been run and at least one user has been defined to the system.

An invocation example

In the following example, you are starting the email error notification service.
startemail

Chapter 12. Email and event notification commands 187

The resulting output
[No feedback]

stopemail
The stopemail command stops the email and inventory notification function. There are no parameters for
this command.

Syntax


stopemail


Parameters

There are no parameters for this command.

Description

This command stops the email error notification function. No emails are sent to users until the startemail
command is reissued.

An invocation example

In the following example, you have stopped the email and inventory notification function:
stopemail

The resulting output

[No feedback]

testemail
The testemail command allows you to send an email notification to one user of the email notification
function or to all users of the email notification function to ensure that the function is operating correctly.

Syntax


testemail userid_or_name

-all

Parameters
userid_or_name
(Required if you do not specify -all) Specifies the user ID or user name of the email recipient that you
want to send a test email to. You cannot use this parameter with the -all parameter. The
userid_or_name value must not contain spaces.
-all
(Required if you do not specify userid_or_name) Sends a test email to all email users configured to
receive notification of events of any notification type. No attempt is made to send the test email to an
email user who does not have any notification setting set to on.

188 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

This command sends test emails to the specified email users. The email recipient expects to receive the
test email within a specified service time. If the email is not received within the expected time period, the
recipient must contact the administrator to ensure that the email settings for the user are correct. If there
is still a problem, you must contact the IBM Support Center.

The email recipient uses the test email to check that the SMTP name, the IP address, the SMTP port, and
the user address are valid.

An invocation example

The following example sends a test email to the user ID manager2008:

testemail manager2008

The resulting output

[No feedback]

Chapter 12. Email and event notification commands 189

190 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 13. Enclosure commands
Storwize V7000 only: Enclosure commands capture information that can assist you with managing
enclosures.

addcontrolenclosure
The addcontrolenclosure command is used to add control enclosures to the clustered system.

Syntax


addcontrolenclosure -iogrp io_grp_id_or_name -sernum enclosure_serial_number


Parameters
-iogrp io_grp_id_or_name
The I/O group in which you want to put the control enclosure.
-sernum enclosure_serial_number
The serial number of the control enclosure you want to add.

Description

Use this command to add a control enclosure to the system.

An invocation example
addcontrolenclosure -iogrp 0 -sernum 2361443

The resulting output

Enclosure containing Node, id [x], successfully added

chenclosure
Use the chenclosure command to modify enclosure properties.

Syntax
e

chenclosure -identify yes|no enclosure_id

-managed yes|no
-id enclosure_id
e

Parameters

Note: Optional parameters are mutually exclusive. Exactly one of the optional parameters must be set.
1 -identify yes|no
1 (Optional) Causes the identify LED start or stop flashing.
-managed yes|no
(Optional) Causes the enclosure into a managed or unmanaged enclosure.

© Copyright IBM Corp. 2003, 2012 191

 -id enclosure_id
(Optional) Changes the enclosure ID after you replace the enclosure, and enables you to control what
is on the front panel.
enclosure_id
The enclosure you want to modify.

Description

Use this command to modify enclosure properties.

To change the identity of enclosure 7 from 7 to 4:

chenclosure -id 4 7

To change enclosure 1 to unmanaged:

chenclosure -managed no 1

To make the identify LED on enclosure 1 stop flashing:

chenclosure -identify no 1

chenclosurecanister
Use the chenclosurecanister command to modify the properties of an enclosure canister.

Syntax
e

chenclosurecanister

e -excludesasport yes|no -port 1|2
-force
-identify yes|no

e
-canister canister_id enclosure_id


e

Note:
1. The -port and -excludesasport parameters must be specified together.
2. Exactly one of the optional parameters must be set.

Parameters

Note: Optional parameters are mutually exclusive.

1 -identify yes|no
1 (Optional) Changes the state of fault light-emitting diode (LED) either to or from slow_flashing.
-excludesasport yes|no
(Optional) Excludes or includes the specified SAS port. You can use the -force flag if there are
dependent VDisks (volume).

Note: Using the -force flag might result in loss of access to your data.
-port 1 | 2
(Optional) The SAS port to include or exclude.
canister_id
The canister you want to apply the change to.

192 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 enclosure_id
e The enclosure in which the canister is a member.

Description

This command enables you to modify the properties of an enclosure canister.

To make the fault LED flash on canister 1 of enclosure 3:

chenclosurecanister -identify yes -canister 1 3

Results
No feedback

To exclude SAS port 1 on canister 2 of enclosure 1:

chenclosurecanister -excludesasport yes -port 1 -canister 2 1

Results
No feedback

chenclosureslot
Use the chenclosureslot command to modify the properties of an enclosure slot.

Syntax


chenclosureslot -slot slot_id

-identify yes|no
-exclude yes|no -port port_id -force

enclosure_id


Note:
1. Optional parameters are mutually exclusive.
2. You can only specify the port parameter or the -force parameter when you also specify the -exclude
parameter.
3. Exactly one of the optional parameters must be set.
4. The -force flag will only have an effect on the operation of -exclude yes .

Parameters
-identify yes|no
Change the state of fault light-emitting diode (LED)megadsss to or from slow_flashing.
-exclude yes|no
(Optional) Ensures that an enclosure slot port is excluded. The following list gives details of the
options you can use with this parameter:
v -exclude yes-port port_id -slot slot_id enclosureid: The port you specify with port_id will be excluded.
If the current state of the port is excluded_by_enclosure, excluded_by_drive, or
excluded_by_cluster, this command will appear to have no affect. However, if the current state of
the port is online, then that state will change to excluded_by_cluster. The port will remain
excluded until you rerun this command with no selected.
Attention: This command will check for dependent volumes. If issuing this command would
result in losing access to data, then the command will fail and an error message will display. You
can use the -force flag to ignore these errors, but this could result in loss of access to data.

Chapter 13. Enclosure commands 193

 v -exclude no -port port_id -slot slot_id enclosureid : The port will be put into online state, provided
there are no other reasons to exclude the port. If you issue this command when the port is online,
then it will have no effect. However, if you issue this command when the port is excluded, then
the port state will do one of the following:
– Change to online status immediately.
– Change to online status after all other reasons for the port to be excluded have been removed.
v -exclude yes|no -slot slot_id enclosureid: If you issue this command without defining a port, then
the command will simultaneously act on both ports.
-port 1|2
(Optional) The port on the canister to be excluded. If it is not specified, -exclude will act on both
ports.
-slot slot_id
The slot ID.
enclosure_id
The enclosure that the slot is a member of.

Description

These commands enable you to modify the properties of an enclosure slot.

Turn on the identify LED on slot 7 of enclosure 1:

chenclosureslot -identify yes -slot 7 1

The results:
No feedback

Force the exclusion of port 1 of slot 7 of enclosure 1:

-exclude yes -port 1 -force -slot 7 1

The results:
No feedback

lsenclosure
Use the lsenclosure command to view a summary of the enclosures.

Syntax


lsenclosure

enclosure_id -delim delimiter

Parameters
enclosure_id
Detailed information for the enclosure that you specify.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all

194 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command enables you to view a summary of the enclosures (including current status information for
canisters and power and cooling units, and other enclosure attributes). Table 26 shows the possible
outputs:
Table 26. lsenclosure output
Attribute Description
id The ID of the enclosure.
status Indicates if an enclosure is visible to the SAS network:
v online: a managed or unmanaged enclosure is visible
v offline: a managed enclosure is not visible, and other fields hold their last known
values.
v degraded: if an enclosure is visible, but not down both strands
type The type of enclosure:
v control
v expansion
managed Whether the enclosure is managed:
v yes
v no
IO_group_id The I/O group the enclosure belongs to; blank if canisters are connected to two
different I/O groups.
IO_group_name The I/O group the enclosure belongs to; blank if canisters are connected to two
different I/O groups.
1 fault_LED The status of the fault light-emitting diode (LED) on the enclosure:
1 v on: a service action is required immediately on the enclosure or a component within
1 the enclosure (including a canister, power unit, or non-spared drive).
1 v slow_flashing: there is insufficient battery power to run I/O
1 v off: there are faults on the enclosure or its components
1 identify_LED The state of the identify LED:
1 v off: the enclosure is not identified
1 v slow_flashing: the enclosure is being identified
error_sequence_number Indicates the error log number of the highest priority error for this object. This is
typically blank; however, if there is a problem (for example, the status has degraded),
then it contains the sequence number of that error.
product_MTM The product machine type and model.
serial_number The serial number of the enclosure. This is the product serial number, which indicates
the enclosure and its contents. The enclosure has its own serial number, which is
embedded in the FRU_identity 11S data.
FRU_part_number The FRU part number of the enclosure.
FRU_identity The 11S serial number that combines the manufacturing part number and the serial
number.
total_canisters The maximum number of canisters for this enclosure type.
online_canisters The number of canisters contained in this enclosure that are online.
total_PSUs The number of power and cooling units in this enclosure.
online_PSUs The number of power-supply units (PSUs) contained in this enclosure that are online.

Chapter 13. Enclosure commands 195

 Table 26. lsenclosure output (continued)
Attribute Description
drive_slots The number of drive slots in the enclosure.
1 firmware_level_1 The version of the microcode image that is installed on the midplane.
1 firmware_level_2 The version of the midplane metadata that is installed on the midplane.

An invocation example
lsenclosure -delim :

The resulting output

id:status:type:managed:IO_group_id:IO_group_name:product_MTM:serial_number:total_canisters:online_canisters:
total_PSUs:online_PSUs:drive_slots1:degraded:expansion:no:0:io_grp0:2076-224:66G0083:2:2:2:2:24

1 A detailed invocation example

1 lsenclosure 1

1 The resulting output

1 id 1
1 status online
1 type control
1 managed no
1 IO_group_id 0
1 IO_group_name io_grp0
1 fault_LED off
1 identify_LED off
1 error_sequence_number
1 product_MTM 2076-112
1 serial_number 64G005S
1 FRU_part_number 85Y5896
1 FRU_identity 11S85Y5962YHU9994G005S
1 total_canisters 2
1 online_canisters 2
1 total_PSUs 2
1 online_PSUs 2
1 drive_slots 12
1 firmware_level_1 10
1 firmware_level_2 F6C07926

lsenclosurebattery
Use the lsenclosurebattery command to display information about the batteries in the enclosure power
supply units (PSUs).

Syntax


lsenclosurebattery

-delim delimiter


-battery battery_id enclosure_id

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of

196 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-battery battery_id enclosure_id
(Optional) Provides a detailed view of the specified enclosure battery. Valid only when an enclosure
is specified.
enclosure_id
(Optional) Lists the batteries for the specified enclosure.

Description
This command displays information about the batteries in the enclosure PSUs. The concise view will
show a line for each battery slot in every control enclosure, regardless of whether they exist. Batteries will
not be shown for expansion enclosures. Table 27 shows possible outputs.
Table 27. lsenclosurebattery outputs
Attribute Description
enclosure_id The identity of the enclosure that contains the battery.
battery_id Identifies the battery in the enclosure.
status The status of the battery:
v online: the battery is present and working as usual
v degraded: the battery is present but not working as usual
v offline: the battery could not be detected
charging_status The charging state of the battery:
e v idle: the battery is not charging nor discharging
e v charging: the battery is charging
e v reconditioning: the battery is reconditioning itself, by being discharged and
e then recharged
2 Important: A battery is unavailable when in reconditioning state. Reconditioning
2 is performed:
2 v Every three months
2 v When a battery has been used for (at least) two power failures
2 Reconditioning takes approximately 12 hours.
recondition_needed The battery needs to be reconditioned; however, this cannot be done because of
one or more errors.
percent_charged Indicates the charge of battery, in a percentage.
end_of_life_warning The battery is reaching its end of life warning, and will need to be replaced:
v yes
v no
FRU_part_number The FRU part number of the battery.
FRU_identity The 11S number, combining the manufacturing part number and the serial
number.
3 firmware_level The battery firmware version or microcode image version installed on the battery.
error_sequence_number Indicates the error log (or event log) number of the highest priority error for this
object. This is typically blank; however, if there is a problem (for example, the
status is degraded), then it contains the sequence number of that error event.

Chapter 13. Enclosure commands 197

An invocation example
lsenclosurebattery -delim :

The resulting output

enclosure_id:battery_id:status:charging_status:recondition_needed:percent_charged:end_of_life_warning
1:1:offline:idle:no:0:no
1:2:offline:idle:no:0:no

lscontrolenclosurecandidate
The lscontrolenclosurecandidate command displays a list of all control enclosures that you can add to
the current system.

Syntax


lscontrolenclosurecandidate


Parameters

None.

Description

Table 28 provides the possible values that are applicable to the attributes that are displayed as data in the
output views.
Table 28. lscontrolenclosurecandidate attribute values
Attribute Value
serial_number The serial number for the enclosure.
product_MTM The MTM for the enclosure.

A concise invocation example

lscontrolenclosurecandidate

The concise resulting output

serial_number product_MTM
G00F7GY 2076-124

lsenclosurecanister
Use the lsenclosurecanister command to view a detailed status for each canister in an enclosure.

Syntax


lsenclosurecanister

enclosure_id
-canister canister_id


-delim delimiter

198 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
enclosure_id
Lists the canisters for the specified enclosure.
-canister canister_id
Valid only when the enclosure_id is specified. Provides a detailed view of the canister for the
specified enclosure.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command enables you to view a detailed status for each canister in an enclosure. Table 29 shows the
possible outputs:
Table 29. lsenclosurecanister output
Attribute Description
enclosure_id The identity of the enclosure that contains the canister.
canister_id Identifies which of the canisters in the enclosure this is.
status The status of the canister:
v online: the canister is present and working normally.
v degraded: the canister is present but not working normally
v offline: the canister could not be detected.
type The type of canister:
v node
v expansion
node_id The node that corresponds to this canister; blank if the canister is not a node, or if the
node is offline or not part of the clustered system.
node_name The node that corresponds to this canister; blank if the canister is not a node, or if the
node is offline or not part of the clustered system.
FRU_part_number The field-replaceable unit (FRU) part number of the canister.
FRU_identity The 11S number that combines the manufacturing part number and the serial number.
WWNN The Fibre Channel worldwide node name (WWNN) of the canister (node canisters
only).
firmware_level The firmware level of the Small Computer System Interface (SCSI) Enclosure Services
(SES) code running on the canister.
1 firmware_level_2 The version of the first other microcode image that is installed on the canister.
1 firmware_level_3 The version of the second other microcode image that is installed on the canister.
1 firmware_level_4 The version of the third other microcode image that is installed on the canister.
1 firmware_level_5 The version of the canister metadata that is installed on the canister.
temperature (0 to 245) The temperature of the canister (in degrees Celsius). If the temperature goes
below 0, 0 will be displayed.

Chapter 13. Enclosure commands 199

 Table 29. lsenclosurecanister output (continued)
Attribute Description
1 fault_LED The state of the combined fault and identify light-emitting diodes (LEDs):
1 v off: no fault
1 v slow_flashing: identify mode
1 Note: When the LED is in identify mode, it conceals whether there is a fault present,
1 because it always flashes. When you remove it from identity mode, the LED will
1 become on or off.
1 v on: fault
SES_status The SCSI status of the connection between the device and the canister:
v online
v offline
error_sequence_number Indicates the error log number of the highest priority error for this object. This is
typically blank; however, if there is a problem (for example, the status is degraded),
then it contains the sequence number of that error.
SAS_port_1_status Indicates if there is damage to the cable between SAS ports:
v online
v offline
v excluded: are logged in, but cannot communicate with the canister
v degraded: the SAS cable not fully functional
SAS_port_2_status Indicates if there is damage to the cable between SAS ports:
v online
v offline
v excluded: are logged in, but cannot communicate with the canister
v degraded: the SAS cable not fully functional

An invocation example
lsenclosurecanister -delim :

The resulting output

enclosure_id:canister_id:status:type:node_id:node_name
1:1:degraded:expansion:1:node1

A detailed example
lsenclosurecanister -canister 1 1

The resulting output

enclosure_id 1
canister_id 1
status online
type node
node_id 1
node_name node1
FRU_part_number AAAAAAA
FRU_identity 11S1234567Y12345678901
WWNN 5005076801005F94
firmware_level XXXXXXXXXX
temperature 23
fault_LED flashing
SES_status online
error_sequence_number
SAS_port_1_status online

200 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 SAS_port_2_status onlinefirmware_level_2 0501
firmware_level_3 14
firmware_level_4 B69F66FF
1 firmware_level_5 5C2A6A44

lsenclosurepsu
Use the lsenclosurepsu command to view information about each power-supply unit (PSU) in the
enclosure.

Syntax


lsenclosurepsu

-psu psu_id enclosure_id -delim delimiter

Parameters
enclosure_id
(Optional) Lists the PSUs for the specified enclosure.
-psu psu_id
(Optional) Valid only when the enclosure_id is specified. Provides a detailed view of the PSU for the
specified enclosure.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command enables you to view information about each power-supply unit (PSU) in the enclosure.
Table 30 shows the possible outputs:
Table 30. lsenclosurepsu output
Attribute Description
enclosure_id The ID of the enclosure containing the PSU.
psu_id The ID of the PSU in the enclosure.
status The status of the power and cooling unit in the enclosure:
v online: a PSU is present and working normally
v offline: a PSU cannot be detected
v degraded: a PSU is present but not working normally
AC_failed v on: If the AC, DC, and fan LEDs are all on, then there is a PSU fault. If only the AC
LED is on, then there is no AC power.
v off: The AC power is OK.
DC_failed v on: If the AC, DC, and fan LEDs are all on, then there is a PSU fault. If only the DC
LED is on, then there is no DC power.
v off: The DC power is OK.

Chapter 13. Enclosure commands 201

 Table 30. lsenclosurepsu output (continued)
Attribute Description
fan_failed v on: If the AC, DC, and fan LEDs are all on, then there is a PSU fault. If only the fan
LED is on, then there is a fan failure.
v off: The fans in this PSU are OK.
redundant Indicates if you can remove this power supply:
v If the PSU is on an expansion enclosure, then the other PSU must be online.
v If the PSU is on a control enclosure, then the other PSU must be online, and the
battery on that PSU must contain enough charge to allow the canisters to dump state
and cache data before shutting down.
error_sequence_number Indicates the error log (or event log) number of the highest priority error for this object.
This is typically blank; however, if there is a problem (for example, the status is
degraded), then it contains the sequence number of that error event.
FRU_part_number The FRU part number of the PSU.
FRU_identity The 11S number, combining the manufacturing part number and the serial number.
1 firmware_level_1 The version of the microcode image that is installed on the power supply.
1 firmware_level_2 The version of the power supply metadata that is installed on the power supply.

An invocation example
lsenclosurepsu -delim :

The resulting output

enclosure_id:PSU_id:status
1:1:degraded

1 An detailed invocation example

1 lsenclosurepsu -psu 1 1

1 The resulting output

1 enclosure_id 1
1 PSU_id 1
1 status online
1 AC_failed off
1 DC_failed off
1 fan_failed off
1 redundant yes
1 error_sequence_number
1 FRU_part_number 85Y5847
1 FRU_identity 11S85Y5847YG50CG07W0LJ
1 firmware_level_1 0314
1 firmware_level_2 AF9293E5

lsenclosureslot
Use the lsenclosureslot command to view information about each drive slot in the enclosure.

Syntax


lsenclosureslot

-delim delimiter -nohdr

202 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide



-slot slot_id enclosure_id
enclosure_id

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. This ingparameter suppresses the display of these
headings.
-slot slot_id
(Optional) Valid only when an enclosure is specified. Gives detailed view for that enclosure slot.
enclosure_id
(Optional) Lists slots for that enclosure. Must be specified if -slot is used.

Description

This command enables you to view information about each drive slot in the enclosure, such as whether a
drive is present, and the port status for that drive. Table 31 shows the possible outputs:
Table 31. lsenclosureslot output
Attribute Description
enclosure_id The identity of the enclosure which contains the drive slot.
slot_id Identifies which of the drive slots in the enclosure this is.
port_1_status The status of enclosure slot port 1. If the port is bypassed for multiple reasons, only one
is shown. In order of priority, they are:
v online: enclosure slot port 1 is online
v excluded_by_drive: the drive excluded the port
v excluded_by_enclosure: the enclosure excluded the port
v excluded_by_system: the clustered system (system) has excluded the port
port_2_status The status of enclosure slot port 2. If the port is bypassed for multiple reasons, only one
is shown. In order of priority, they are:
v online: enclosure slot port 2 is online
v excluded_by_drive: the drive excluded the port
v excluded_by_enclosure: the enclosure excluded the port
v excluded_by_system: the clustered system (system) has excluded the port
fault_LED The state of the combined fault and identify light-emitting diodes (LEDs):
v off: no fault
v slow_flashing: identify mode
Note: When the LED is in identify mode, it conceals whether there is a fault present,
because it always flashes. When you remove it from identity mode, the LED will
become on or off.
v on: fault

Chapter 13. Enclosure commands 203

Table 31. lsenclosureslot output (continued)
Attribute Description
powered Indicates whether the slot is powered on.
v yes
v no
drive_present Indicates if a drive is in the slot. The drive can be working, dead, or powered off.
v yes (present)
v no (empty)
drive_id The ID of the drive in the slot; blank if there is no drive present, or if there is a drive
present but it is offline and unmanaged.
error_sequence_number Indicates the error log number of the highest priority error for this object. This is
typically blank; however, if there is a problem (for example, the status is degraded),
then it contains the sequence number of that error.

An invocation example
lsenclosureslot -delim :

The resulting output

enclosure_id:slot_id:port_1_status:port_2_status:drive_present:drive_id
1:1:online:online:yes:22
1:2:online:online:yes:23
1:3:online:online:yes:19
1:4:online:online:yes:7
1:5:online:online:yes:10
1:6:online:online:yes:18
1:7:online:online:yes:20
1:8:online:online:yes:16
1:9:online:online:yes:12
1:10:online:online:yes:11
1:11:online:online:yes:21
1:12:online:online:yes:9
1:13:online:online:yes:14
1:14:online:online:yes:5
1:15:online:online:yes:15
1:16:online:online:yes:13
1:17:online:online:yes:6
1:18:online:online:yes:17
1:19:online:online:yes:4
1:20:online:online:yes:1
1:21:online:online:yes:8
1:22:online:online:yes:0
1:23:online:online:yes:3
1:24:online:online:yes:2

An invocation example showing slot 2 in enclosure 5

lsenclosureslot -delim : -slot 2 5

The resulting output

enclosure_id:5
slot_id:2
port_1_status:online
port_2_status:online
fault_LED:off
powered:yes
drive_present:yes
drive_id:105
error_sequence_number:
IBM_2076:bobs_cluster:admin

204 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
triggerenclosuredump
Use the triggerenclosuredump command to force the specified enclosure or enclosures to dump data.

Syntax


triggerenclosuredump -port port_id -iogrp iogrp_id_or_name

-enclosure enclosure_id

Note:
1. You can only use one of the optional parameters (-port or -enclosure).
2. If -port is specified, -iogrp must also be specified.
3. If -iogrp is specified, -port must also be specified.

Parameters
-port port_id
(Optional) If the system is wired correctly, this value is identical to the ID of the chain with the
enclosures you want to dump. If the system is wired incorrectly, all the enclosures connected to port
port_id of either node canister are dumped.
-iogrp iogrp_id_or_name
(Optional) The ID or name of the I/O group the control enclosure belongs to.
-enclosure enclosure_id
(Optional) The ID of the enclosure you want to dump.

Description

Important: One of the optional parameters must be specified.

This command requests the canisters in the enclosure or enclosures specified to dump data. The dumped
data is subsequently collected and moved to /dumps/enclosure on the nodes that are connected to the
enclosure. There is one file for each canister successfully dumped and they may be located on different
nodes. Dumps are for use by IBM support, which has the tools to interpret the dump data. Use the
cpdumps command to copy the files from the system. This command does not disrupt access to the
enclosures.

To trigger enclosure dumps from all enclosures connected to port 1 of the control enclosure in iogrp 2:
triggerenclosuredump -port 1 -iogrp 2

To trigger enclosure dumps from enclosure 5:

triggerenclosuredump -enclosure 5

Chapter 13. Enclosure commands 205

206 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 14. Licensing commands
The licensing commands enable you to work with SAN Volume Controller licensed functions.

chlicense
The chlicense command changes license settings for clustered system (system) features.

Syntax


chlicense

-flash capacity_TB -remote capacity_TB

-virtualization capacity_TB -physical_flash on
off

-physical_remote on -physical_disks number
off

1


-compression compression_setting

Parameters
-flash capacity_TB
(Optional) Changes system licensing for the FlashCopy feature. To change the licensed capacity for
the FlashCopy feature, specify a capacity in terabytes (TB).

Note: Only use the optional flash parameter with the SAN Volume Controller.
-remote capacity_TB
(Optional) Changes system licensing for the Metro Mirror and Global Mirror feature. To change the
licensed capacity for the Metro Mirror and Global Mirror feature, specify a capacity in terabytes (TB).

Note: For Storwize V7000, specify the total number of internal and external enclosures that you have
licensed on your system. You must have a Remote Mirroring license for all enclosures.
-virtualization capacity_TB
(Optional) Changes system licensing for the Virtualization feature. To change the licensed capacity for
the Virtualization feature, specify a capacity in terabytes (TB).

Note: For Storwize V7000, specify the number of enclosures of external storage that you have been
authorized by IBM to use.
-physical_flash on | off
(Optional) For physical disk licensing, enables or disables the FlashCopy feature. The default value is
off.
-physical_remote on | off
(Optional) For physical disk licensing, enables or disables the Metro Mirror and Global Mirror
feature. The default value is off.

© Copyright IBM Corp. 2003, 2012 207

 -physical_disks number
(Optional) Changes the licensed settings of the system for physical disk licensing. Enter the number
of physical disks that your system is licensed to manage. The correct number is identified in your
license.
1 -compression compression_setting
e (Optional) Changes the system compression licensing value.

e Note: Not all SAN Volume Controller systems support compression. However, you can set a
e compression license value on a system that has no nodes that support compression.

1 Note:
1 v If the -physical_disks value is set to zero, the -physical_flash and -physical_remote values are
1 turned off.
1 v If the -physical_disks value is nonzero, the -flash, -remote, and -virtualization values cannot be
1 set.
1 v If the -physical_disks value is nonzero, only the FlashCopy and RemoteCopy usage is monitored and
1 appropriate error messages are logged.
1 v If the -flash, -remote, or -virtualization values are nonzero, the -physical_flash, -physical_remote,
1 and -physical_disks values cannot be set.

1 Description

1 The chlicense command changes license settings for the system. Any change that is made is logged as an
1 event in the license setting log.

1 For Storwize V7000, the enclosure license already includes virtualization of internal drives on your
1 system. You can use this command to set any additional options. The total amounts for your system or
1 systems must not exceed the total capacity authorization that you have obtained from IBM.

1 For SAN Volume Controller the default is to have no copy services functions licensed, but this does not
1 stop you from creating and using Copy Services. However, errors are placed in the license settings log
1 that state that you are using an unlicensed feature. The command-line tool return code also notifies you
1 that you are using an unlicensed feature.

1 For Storwize® V7000, the default is to have no Metro Mirror or Global Mirror function licensed, but this
1 does not stop you from creating and using Copy Services. However, errors are placed in the license
1 settings log that state that you are using an unlicensed feature. The command-line tool return code also
1 notifies you that you are using an unlicensed feature.

1 The total virtualized capacity can also be modified with this command. This is the number of terabytes
1 (TB) of virtual disk capacity that can be configured by the system.

1 When you reach 90% capacity, any attempt to create or extend Virtual Disks, Relationships, or Mappings
1 results in a message from the command-line tool. This does not stop you from creating and expanding
1 Virtual Disks, Relationships, or Mappings. When usage reaches or exceeds 100% capacity, errors are
1 placed in the license settings log.

1 Any error that is placed in the license settings log results in a generic error being placed in the system
1 error log. This occurs when you issue a command that violates the license agreement. The return code
1 also notifies you that you are violating the license settings.

1 An invocation example
1 chlicense -remote 5

208 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 The resulting output
1 No feedback

2 An invocation example for modifying a compression license value

2 chlicense -compression 4

2 The resulting output

2 No feedback

dumpinternallog
The dumpinternallog command dumps the contents of the license settings error and event log to a file
on the current configuration node.

Syntax


dumpinternallog


Description

This command dumps the contents of the internal license settings error and event log to a file on the
current configuration node.

This file is always called feature.txt and is created, or overwritten, in the /dumps/feature directory on the
configuration node.

This file can be requested by IBM service personnel.

Before making any entries, the license settings log contains only zeros. A dump of this log from the
dumpinternallog command results in an empty file.

An invocation example
dumpinternallog

The resulting output

No feedback

Chapter 14. Licensing commands 209

210 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 15. IBM FlashCopy commands
The FlashCopy commands enable you to work with FlashCopy methods and functions with the SAN
Volume Controller.

chfcconsistgrp
The chfcconsistgrp command changes the name of a consistency group or marks the group for
auto-deletion.

Syntax


chfcconsistgrp

-name new_name_arg -autodelete on | off

fc_consist_group_id

fc_consist_group_name

Parameters
-name new_name_arg
(Optional) Specifies the new name to assign to the consistency group.
-autodelete on | off
(Optional) Deletes the consistency group when the last mapping that it contains is deleted or
removed from the consistency group.
fc_consist_group_id | fc_consist_group_name
(Required) Specifies the ID or existing name of the consistency group that you want to modify.

Description
The chfcconsistgrp command changes the name of a consistency group, marks the group for
auto-deletion, or both.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
chfcconsistgrp -name testgrp1 fcconsistgrp1

The resulting output

No feedback

chfcmap
The chfcmap command modifies attributes of an existing mapping.

Syntax


chfcmap

-name new_name_arg -force

© Copyright IBM Corp. 2003, 2012 211




-consistgrp consist_group_id -copyrate rate
consist_group_name

fc_map_id

-autodelete on -cleanrate rate fc_map_name
off

Parameters
-name new_name_arg
(Optional) Specifies the new name to assign to the mapping. The -name parameter cannot be used
with any other optional parameters.
-force
(Optional) Specifies that the mapping be modified to a stand-alone mapping (equivalent to creating
the mapping without a consistency group ID). You cannot specify the -force parameter with the
-consistgrp parameter.
-consistgrp consist_group_id | consist_group_name
(Optional) Specifies the consistency group for which you want to modify the mapping. You cannot
specify the -consistgrp parameter with the -force parameter.

Note: The consistency group cannot be modified if the specified consistency group is in the
preparing, prepared, copying, suspended, or stopping state.
-copyrate rate
(Optional) Specifies the copy rate. The rate value can be 0 - 100. The default value is 50. A value of 0
indicates no background copy process. For the supported -copyrate values and their corresponding
rates, see Table 32 on page 213.
-autodelete on | off
(Optional) Specifies that the autodelete function be turned on or off for the specified mapping. When
you specify the -autodelete on parameter, you are deleting a mapping after the background copy
completes. If the background copy is already complete, the mapping is deleted immediately.
-cleanrate rate
(Optional) Sets the cleaning rate for the mapping. The rate value can be 0 - 100. The default value is
50.
fc_map_id | fc_map_name
(Required) Specifies the ID or name of the mapping to modify. Enter the ID or name last on the
command line.

Description

The chfcmap command modifies attributes of an existing mapping.

Attention: You must enter the fc_map_id | fc_map_name last on the command line.

If you have created several FlashCopy mappings for a group of VDisks that contain elements of data for
the same application, you can assign these mappings to a single FlashCopy consistency group. You can
then issue a single prepare command and a single start command for the whole group, for example, so
that all of the files for a particular database are copied at the same time.

The copyrate parameter specifies the copy rate. If 0 is specified, background copy is disabled. The
cleanrate parameter specifies the rate for cleaning the target VDisk. The cleaning process is only active if
the mapping is in the copying state and the background copy has completed, the mapping is in the
copying state and the background copy is disabled, or the mapping is in the stopping state. You can

212 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
disable cleaning when the mapping is in the copying state by setting the cleanrate parameter to 0. If the
cleanrate is set to 0, the cleaning process runs at the default rate of 50 when the mapping is in the
stopping state to ensure that the stop operation completes.

Table 32 provides the relationship of the copy rate and cleaning rate values to the attempted number of
grains to be split per second. A grain is the unit of data represented by a single bit.
Table 32. Relationship between the rate, data rate and grains per second values
User-specified rate
attribute value Data copied/sec 256 KB grains/sec 64 KB grains/sec
1 - 10 128 KB 0.5 2
11 - 20 256 KB 1 4
21 - 30 512 KB 2 8
31 - 40 1 MB 4 16
41 - 50 2 MB 8 32
51 - 60 4 MB 16 64
61 - 70 8 MB 32 128
71 - 80 16 MB 64 256
81 - 90 32 MB 128 512
91 - 100 64 MB 256 1024

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
chfcmap -name testmap 1

The resulting output

No feedback

mkfcconsistgrp
The mkfcconsistgrp command creates a new FlashCopy consistency group and identification name.

Syntax


mkfcconsistgrp

-name consist_group_name -autodelete

Parameters
-name consist_group_name
(Optional) Specifies a name for the consistency group. If you do not specify a consistency group
name, a name is automatically assigned to the consistency group. For example, if the next available
consistency group ID is id=2, the consistency group name is fccstgrp2.
-autodelete
(Optional) Deletes the consistency group when the last mapping that it contains is deleted or
removed from the consistency group.

Chapter 15. IBM FlashCopy commands 213

Description

This command creates a new consistency group and identification name. The ID of the new group is
displayed when the command process completes.

If you have created several FlashCopy mappings for a group of VDisks (volumes) that contain elements
of data for the same application, you might find it convenient to assign these mappings to a single
FlashCopy consistency group. You can then issue a single prepare command and a single start command
for the whole group, for example, so that all of the files for a particular database are copied at the same
time.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

Remember: Names representing Metro Mirror or Global Mirror consistency groups relationships are
restricted to fifteen characters in length (not sixty-three for an extended character set).

An invocation example
mkfcconsistgrp

The resulting output

FlashCopy Consistency Group, id [1], successfully created

mkfcmap
The mkfcmap command creates a new FlashCopy mapping, which maps a source VDisk (volume) to a
target volume for subsequent copying.

Syntax


mkfcmap -source src_vdisk_id -target target_vdisk_id

src_vdisk_name target_vdisk_name

-name new_name_arg -consistgrp consist_group_id
consist_group_name

-copyrate rate -autodelete -grainsize 64 -incremental
256


-cleanrate rate -iogrp iogroup_name
iogroup_id

Parameters
-source src_vdisk_id | src_vdisk_name
(Required) Specifies the ID or name of the source volume (volume).
-target target_vdisk_id | target_vdisk_name
(Required) Specifies the ID or name of the target volume (volume).
-name new_name_arg
(Optional) Specifies the name to assign to the new mapping.
-consistgrp consist_group_id | consist_group_name
(Optional) Specifies the consistency group to add the new mapping to. If you do not specify a
consistency group, the mapping is treated as a stand-alone mapping.
214 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-copyrate rate
(Optional) Specifies the copy rate. The rate value can be 0 - 100. The default value is 50. A value of 0
indicates no background copy process. For the supported -copyrate values and their corresponding
rates, see Table 33 on page 216.
-autodelete
(Optional) Specifies that a mapping be deleted when the background copy completes. The default,
which applies if this parameter is not entered, is that autodelete is set to off.
-grainsize 64 | 256
(Optional) Specifies the grain size for the mapping. The default value is 256. Once set, this value
cannot be changed.
-incremental
(Optional) Marks the FlashCopy mapping as an incremental copy. The default is nonincremental.
Once set, this value cannot be changed.
-cleanrate rate
(Optional) Sets the cleaning rate for the mapping. The rate value can be 0 - 100. The default value is
50.
-iogrp iogroup_name | iogroup_id
(Optional) Specifies the I/O group for the FlashCopy bitmap. Once set, this value cannot be changed.
The default I/O group is either the source volume, if a single target map, or the I/O group of the
other FlashCopy mapping to which either the source or target VDisks (volumes) belong.

Note: If not enough bitmap space is available to complete this command, more space will
automatically be allocated in the bitmap memory (unless you have already reached the maximum
bitmap memory).

Description

This command creates a new FlashCopy mapping. This mapping persists until it is manually deleted, or
until it is automatically deleted when the background copy completes and the autodelete parameter set
to on. The source and target VDisks (volumes) must be specified on the mkfcmap command. The mkfcmap
command fails if the source and target volumes are not identical in size. Issue the lsvdisk -bytes
command to find the exact size of the source volume for which you want to create a target disk of the
same size. The target volume that you specify cannot be a target volume in an existing FlashCopy
mapping. A mapping cannot be created if the resulting set of connected mappings exceeds 256 connected
mappings.

The mapping can optionally be given a name and assigned to a consistency group, which is a group of
mappings that can be started with a single command. These are groups of mappings that can be
processed at the same time. This enables multiple VDisks (volumes) to be copied at the same time, which
creates a consistent copy of multiple disks. This consistent copy of multiple disks is required by some
database products in which the database and log files reside on different disks.

If the specified source and target VDisks (volumes) are the target and source volumes, respectively, of an
existing mapping, then the mapping being created and the existing mapping become partners. If one
mapping is created as incremental, then its partner is automatically incremental. A mapping can have
only one partner.

You can create a FlashCopy mapping in which the target volume is a member of a Metro Mirror or
Global Mirror relationship, unless one of the following conditions applies:
v The relationship is with a clustered system that is running an earlier code level.
v The I/O group for the mapping is different than the I/O group for the proposed mapping target
volume.

Chapter 15. IBM FlashCopy commands 215

The copyrate parameter specifies the copy rate. If 0 is specified, background copy is disabled. The
cleanrate parameter specifies the rate for cleaning the target volume. The cleaning process is only active
if the mapping is in the copying state and the background copy has completed, the mapping is in the
copying state and the background copy is disabled, or the mapping is in the stopping state. You can
disable cleaning when the mapping is in the copying state by setting the cleanrate parameter to 0. If the
cleanrate is set to 0, the cleaning process runs at the default rate of 50 when the mapping is in the
stopping state to ensure that the stop operation completes.

Table 33 provides the relationship of the copy rate and cleaning rate values to the attempted number of
grains to be split per second. A grain is the unit of data represented by a single bit.

Remember: If either the specified source or target volume is defined as a change volume for a
relationship, mkfcmap is not successful.
Table 33. Relationship between the rate, data rate and grains per second values
User-specified rate
attribute value Data copied/sec 256 KB grains/sec 64 KB grains/sec
1 - 10 128 KB 0.5 2
11 - 20 256 KB 1 4
21 - 30 512 KB 2 8
31 - 40 1 MB 4 16
41 - 50 2 MB 8 32
51 - 60 4 MB 16 64
61 - 70 8 MB 32 128
71 - 80 16 MB 64 256
81 - 90 32 MB 128 512
91 - 100 64 MB 256 1024

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
mkfcmap -source 0 -target 2 -name mapone

The resulting output

FlashCopy Mapping, id [1], successfully created

prestartfcconsistgrp
The prestartfcconsistgrp command prepares a consistency group (a group of FlashCopy mappings) so
that the consistency group can be started. This command flushes the cache of any data that is destined
for the source volume and forces the cache into the write-through mode until the consistency group is
started.

Syntax


prestartfcconsistgrp fc_consist_group_id

-restore fc_consist_group_name

216 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
-restore
(Optional) Specifies the restore flag. This forces the consistency group to be prepared even if the
target volume of one of the mappings in the consistency group is being used as a source volume of
another active mapping. An active mapping is in the copying, suspended, or stopping state.
fc_consist_group_id | fc_consist_group_name
(Required) Specifies the name or ID of the consistency group that you want to prepare.

Description

This command prepares a consistency group (a group of FlashCopy mappings) to subsequently start. The
preparation step ensures that any data that resides in the cache for the source volume is first flushed to
disk. This step ensures that the FlashCopy target volume is identical to what has been acknowledged to
the host operating system as having been written successfully to the source volume.

You can use the restore parameter to force the consistency group to be prepared even if the target
volume of one or more mappings in the consistency group is being used as a source volume of another
active mapping. In this case the mapping restores as shown in the lsfcmap view. If the restore parameter
is specified when preparing a consistency group where none of the target volumes are the source volume
of another active mapping, then the parameter is ignored.

You must issue the prestartfcconsistgrp command to prepare the FlashCopy consistency group before
the copy process can be started. When you have assigned several mappings to a FlashCopy consistency
group, you must issue a single prepare command for the whole group to prepare all of the mappings at
once.

The consistency group must be in the idle_or_copied or stopped state before it can be prepared. When
you enter the prestartfcconsistgrp command, the group enters the preparing state. After the
preparation is complete, the consistency group status changes to prepared. At this point, you can start the
group.

If FlashCopy mappings are assigned to a consistency group, the preparing and the subsequent starting of
the mappings in the group must be performed on the consistency group rather than on an individual
FlashCopy mapping that is assigned to the group. Only stand-alone mappings, which are mappings that
are not assigned to a consistency group, can be prepared and started on their own. A FlashCopy
consistency group must be prepared before it can be started.

This command is rejected if the target of a FlashCopy mapping in the consistency group is in a Metro
Mirror or Global Mirror relationship, except where the relationship is one of the following types and is
the secondary target of the remote copy:
v idling
v disconnected
v consistent_stopped
v inconsistent_stopped
The FlashCopy(r) mapping also fails in the following cases:
v You use the prep parameter.
v The target volume is an active remote copy primary or secondary volume.
v The FlashCopy target (and remote copy primary target) volume is offline. If this occurs, the FlashCopy
mapping stops and the target volume remains offline.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example

Chapter 15. IBM FlashCopy commands 217

prestartfcconsistgrp 1

The resulting output

No feedback

prestartfcmap
The prestartfcmap command prepares a FlashCopy mapping so that it can be started. This command
flushes the cache of any data that is destined for the source volume and forces the cache into the
write-through mode until the mapping is started.

Syntax


prestartfcmap fc_map_id

-restore fc_map_name

Parameters
-restore
(Optional) Specifies the restore flag. This forces the mapping to be prepared even if the target volume
is being used as a source volume in another active mapping. An active mapping is in the copying,
suspended, or stopping state.
fc_map_id | fc_map_name
(Required) Specifies the name or ID of the mapping to prepare.

Description

This command prepares a single mapping for subsequent starting. The preparation step ensures that any
data that resides in the cache for the source volume is first transferred to disk. This step ensures that the
copy that is made is consistent with what the operating system expects on the disk.

The restore parameter can be used to force the mapping to be prepared even if the target volume is
being used as a source volume of another active mapping. In this case, the mapping is restoring as
shown in the lsfcmap view. If the restore parameter is specified when preparing a mapping where the
target volume is not the source volume of another active mapping, then the parameter is ignored.

Note: To prepare a FlashCopy mapping that is part of a consistency group, you must use the
prestartfcconsistgrp command.

The mapping must be in the idle_or_copied or stopped state before it can be prepared. When the
prestartfcmap command is processed, the mapping enters the preparing state. After the preparation is
complete, it changes to the prepared state. At this point, the mapping is ready to start.

Attention: This command can take a considerable amount of time to complete.

This command is rejected if the target of the FlashCopy mappings is the secondary volume in a Metro
Mirror or Global Mirror relationship (so that the FlashCopy target is the remote copy secondary).

Note: If the remote copy is idling or disconnected, even if the FlashCopy and remote copy are pointing
to the same volume, the auxiliary volume is not necessarily the secondary volume. In this case, you can
start a FlashCopy mapping.
The FlashCopy mapping also fails in the following cases:
v The remote copy is active.

218 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
v The FlashCopy target (and remote copy primary target) volume is offline. If this occurs, the FlashCopy
mapping stops and the target volume remains offline.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
prestartfcmap 1

The resulting output

No feedback

rmfcconsistgrp
The rmfcconsistgrp command deletes a FlashCopy consistency group.

Syntax


rmfcconsistgrp fc_consist_group_id

-force fc_consist_group_name

Parameters
-force
(Optional) Specifies that all of the mappings that are associated with a consistency group that you
want to delete are removed from the group and changed to stand-alone mappings. This parameter is
only required if the consistency group that you want to delete contains mappings.
fc_consist_group_id | fc_consist_group_name
(Required) Specifies the ID or name of the consistency group that you want to delete.

Description

This command deletes the specified FlashCopy consistency group. If there are mappings that are
members of the consistency group, the command fails unless you specify the -force parameter. When you
specify the -force parameter, all of the mappings that are associated with the consistency group are
removed from the group and changed to stand-alone mappings.

To delete a single mapping in the consistency group, you must use the rmfcmap command.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
rmfcconsistgrp fcconsistgrp1

The resulting output

No feedback

rmfcmap
The rmfcmap command deletes an existing mapping.

Chapter 15. IBM FlashCopy commands 219

Syntax


rmfcmap fc_map_id

-force fc_map_name

Parameters
-force
(Optional) Specifies that the target volume is brought online. This parameter is required if the
FlashCopy mapping is in the stopped state.
fc_map_id | fc_map_name
(Required) Specifies the ID or name of the FlashCopy mapping to delete. Enter the ID or name last
on the command line.

Description

The rmfcmap command deletes the specified mapping if the mapping is in the idle_or_copied or stopped
state. If it is in the stopped state, the -force parameter is required. If the mapping is in any other state,
you must stop the mapping before you can delete it.

Deleting a mapping only deletes the logical relationship between the two virtual disks; it does not affect
the virtual disks themselves. However, if you force the deletion, the target virtual disk (which might
contain inconsistent data) is brought back online.

If the target of the FlashCopy mapping is a member of the remote copy, the remote copy can be affected
in the following ways:
v If a stopped FlashCopy mapping is deleted and the I/O group associated with the FlashCopy mapping
is suspended while this delete is being processed, then all remote copy relationships associated with
the target volume of a the FlashCopy mapping that were active while the FlashCopy mapping was
copying can be corrupted. You must resynchronize them next time you start the system.
v If a stopped FlashCopy mapping that has previously failed to prepare is deleted, then all remote copy
relationships in the set of remote copy relationships associated with the target volume can be
corrupted. You must resynchronize them next time you start the system.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
rmfcmap testmap

The resulting output

No feedback

startfcconsistgrp
The startfcconsistgrp command starts a FlashCopy consistency group of mappings. This command
makes a point-in-time copy of the source volumes at the moment that the command is started.

Syntax


startfcconsistgrp fc_consist_group_id

-prep -restore fc_consist_group_name

220 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
-prep
(Optional) Specifies that the designated FlashCopy consistency group be prepared prior to starting
the FlashCopy consistency group. A FlashCopy consistency group must be prepared before it can be
started. When you use this parameter, the system automatically issues the prestartfcconsistgrp
command for the group that you specify.
-restore
(Optional) Specifies the restore flag. When combined with the prep option, this forces the consistency
group to be prepared even if the target volume of one of the mappings in the consistency group is
being used as a source volume in another active mapping. An active mapping is in the copying,
suspended, or stopping state.
fc_consist_group_id | fc_consist_group_name
(Required) Specifies the ID or name of the consistency group mapping to start.

Description
This command starts a consistency group, which results in a point-in-time copy of the source volumes of
all mappings in the consistency group. You can combine the restore parameter with the prep parameter
to force the consistency group to be prepared prior to starting, even if the target volume of one or more
mappings in the consistency group is being used as a source volume of another active mapping. In this
case, the mapping is restoring as shown in the lsfcmap view. If the restore parameter is specified when
starting a consistency group where none of the target volumes are the source volume of another active
mapping, the parameter is ignored.

If a consistency group is started and the target volume of the mapping being started has up to four other
incremental FlashCopy mappings using the target, the incremental recording is left on. If there are more
than four other incremental FlashCopy mappings using the target volume, the incremental recording for
all of these mappings is turned off until they are restarted.

Note: The startfcconsistgrp command can take some time to process particularly if you have specified
the prep parameter. If you use the prep parameter, you give additional processing control to the system
because the system must prepare the mapping before the mapping is started. If the prepare process takes
too long, the system completes the prepare but does not start the consistency group. In this case, error
message CMMVC6209E displays. To control the processing times of the prestartfcconsistgrp and
startfcconsistgrp commands independently of each other, do not use the prep parameter. Instead, first
issue the prestartfcconsistgrp command, and then issue the startfcconsistgrp command to start the
copy.

This command is rejected if the target of the FlashCopy mapping in the specified consistency group is the
secondary volume in a Metro Mirror or Global Mirror relationship (so that the FlashCopy target is the
remote copy secondary).

Note: If the remote copy is idling or disconnected, even if the FlashCopy and remote copy are pointing
to the same volume, the auxiliary volume is not necessarily the secondary volume. In this case, you can
start a FlashCopy mapping.

The FlashCopy mapping also fails in the following cases, if the target of the FlashCopy mapping in the
specified consistency group is the primary volume in a Metro Mirror or Global Mirror relationship (so
that the FlashCopy target is the remote copy primary):
v The remote copy is active.
v The FlashCopy target (and remote copy primary target) volume is offline. If this occurs, the FlashCopy
mapping stops and the target volume remains offline.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

Chapter 15. IBM FlashCopy commands 221

An invocation example
startfcconsistgrp -prep 2

The resulting output

No feedback

startfcmap
The startfcmap command starts a FlashCopy mapping. This command makes a point-in-time copy of the
source volume at the moment that the command is started.

Syntax


startfcmap fc_map_id

-prep -restore fc_map_name

Parameters
-prep
(Optional) Specifies that the designated mapping be prepared prior to starting the mapping. A
mapping must be prepared before it can be started. When you use this parameter, the system
automatically issues the prestartfcmap command for the group that you specify.

Note: If you have already used the prestartfcmap command, you cannot use the -prep parameter on
the startfcmap command; the command fails. However, if the FlashCopy has successfully prepared
before, the startfcmap command succeeds.
-restore
(Optional) Specifies the restore flag. When combined with the prep option, this forces the mapping to
be prepared even if the target volume is being used as a source volume in another active mapping.
An active mapping is in the copying, suspended, or stopping state.
fc_map_id | fc_map_name
Specifies the ID or name of the mapping to start.

Description

This command starts a single mapping, which results in a point-in-time copy of the source volume. You
can combine the restore parameter with the prep parameter to force the mapping to be prepared prior to
starting, even if the target volume is being used as a source volume of another active mapping. In this
case, the mapping is restoring as shown in the lsfcmap view. If the restore parameter is specified when
starting a mapping where the target volume is not the source volume of another active mapping, the
parameter is ignored and the mapping is not restoring as shown in the lsfcmap view.

If a mapping is started and the target volume of the mapping being started has up to four other
incremental FlashCopy mappings using the target, the incremental recording is left on. If there are more
than four other incremental FlashCopy mappings using the target volume, the incremental recording for
all of these mappings is turned off until they are restarted.

Note: The startfcmap command can take some time to start, particularly if you use the prep parameter.
If you use the prep parameter, you give additional starting control to the system. The system must
prepare the mapping before the mapping is started. To keep control when the mapping starts, you must
issue the prestartfcmap command before you issue the startfcmap command.

This command is rejected if the target of the FlashCopy mapping is the secondary volume in a Metro
Mirror or Global Mirror relationship (so that the FlashCopy target is the remote copy secondary).

222 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Note: If the remote copy is idling or disconnected, even if the FlashCopy and remote copy are pointing
to the same volume, the auxiliary volume is not necessarily the secondary volume. In this case, you can
start a FlashCopy mapping.

The FlashCopy mapping also fails in the following cases, if the target of the FlashCopy mapping is the
primary volume in a Metro Mirror or Global Mirror relationship (so that the FlashCopy target is the
remote copy primary):
v The remote copy is active.
v The FlashCopy target (and remote copy primary target) volume is offline. If this occurs, the FlashCopy
mapping stops and the target volume remains offline.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
startfcmap -prep 2

The resulting output

No feedback

stopfcconsistgrp
The stopfcconsistgrp command stops all processing that is associated with a FlashCopy consistency
group that is in one of the following processing states: prepared, copying, stopping, or suspended.

Syntax


stopfcconsistgrp fc_consist_group_id_or_name

-force
-split

Parameters
-force
(Optional) Specifies that all processing that is associated with the mappings of the designated
consistency group be stopped immediately.

Note: When you use this parameter, all FlashCopy mappings that depend on the mappings in this
group (as listed by the lsfcmapdependentmaps command) are also stopped.

If the -force parameter is not specified, the command is rejected if the target volume of the
FlashCopy consistency group is the primary in a relationship that is mirroring I/O:
v consistent_synchronized
v consistent_copying
v inconsistent_copying

If the -force parameter is specified, any Metro Mirror or Global Mirror relationships associated with
the target volumes of the FlashCopy mappings in the specified consistency group stops. If a remote
copy relationship associated with the target was mirroring I/O when the map was copying, it might
lose its difference recording capability and require a full resychronization upon a subsequent restart.
-split
(Optional) Breaks the dependency on the source volumes of any mappings that are also dependent on
the target volume. This parameter can only be specified when stopping a consistency group where all
maps in the group have progress of 100 as shown by the lsfcmap command.

Chapter 15. IBM FlashCopy commands 223

fc_consist_group_id_or_name
(Required) Specifies the name or ID of the consistency group that you want to stop.

Description

This command stops a group of mappings in a consistency group. If the copy process is stopped, the
target disks become unusable unless they already contain complete images of the source. Disks that
contain complete images of the source have a progress of 100, as indicated in the lsfcmap command
output. The target volume is reported as offline if it does not contain a complete image. Before you can
access this volume, the group of mappings must be prepared and restarted.

If the consistency group is in the idle_or_copied state, the stopfcconsistgrp command has no effect and
the consistency group stays in the idle_or_copied state.

Note: Prior to SVC 4.2.0, the stopfcconsistgrp command always caused the consistency group to go to
the stopped state, taking the target volumes offline.

The split option can be used when all of the maps in the group have progress of 100. It removes the
dependency of any other maps on the source volumes. It might be used prior to starting another
FlashCopy consistency group whose target disks are the source disks of the mappings being stopped.
Once the consistency group has been stopped with the split option, the other consistency group could
then be started without the restore option.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
stopfcconsistgrp testmapone

The resulting output

No feedback

stopfcmap
The stopfcmap command stops all processing that is associated with a FlashCopy mapping that is in one
of the following processing states: prepared, copying, stopping, or suspended.

Syntax


stopfcmap fc_map_id_or_name

-force
-split

Parameters
-force
(Optional) Specifies that all processing that is associated with the designated mapping be stopped
immediately.

Note: When you use this parameter, all FlashCopy mappings that depend on this mapping (as listed
by the lsfcmapdependentmaps command) are also stopped.
If the -force parameter is not specified, the command is rejected if the target volume of the
FlashCopy mapping is the primary in a relationship which is mirroring I/O:
v consistent_synchronized
v consistent_copying

224 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 v inconsistent_copying
If the -force parameter is specified to a FlashCopy mapping whose target volume is also in a Metro
Mirror or Global Mirror relationship, the relationship stops. If a remote copy relationship associated
with the target was mirroring I/O when the map was copying, it might lose its difference recording
capability and require a full resychronization on a subsequent restart.
-split
(Optional) Breaks the dependency on the source volume of any mappings that are also dependent on
the target disk. This parameter can only be specified when stopping a map that has progress of 100
as shown by the lsfcmap command.
fc_map_id_or_name
(Required) Specifies the name or ID of the mapping to stop.

Description

This command stops a single mapping. If the copy process is stopped, the target disk becomes unusable
unless it already contained a complete image of the source (that is, unless the map had a progress of 100
as shown by the lsfcmap command). Before you can use the target disk, the mapping must once again be
prepared and then reprocessed (unless the target disk already contained a complete image).

Only stand-alone mappings can be stopped using the stopfcmap command. Mappings that belong to a
consistency group must be stopped using the stopfcconsistgrp command.

If the mapping is in the idle_or_copied state, the stopfcmap command has no effect and the mapping
stays in the idle_or_copied state.

Note: Before SAN Volume Controller 4.2.0, the stopfcmap command always changed the mapping state to
stopped and took the target volume offline. This change can break scripts that depend on the previous
behavior.

The split option can be used when the mapping has progress of 100. It removes the dependency of any
other mappings on the source volume. It might be used prior to starting another FlashCopy mapping
whose target disk is the source disk of the mapping being stopped. Once the mapping has been stopped
with the split option, the other mapping could then be started without the restore option.

Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
stopfcmap testmapone

The resulting output

No feedback

Chapter 15. IBM FlashCopy commands 225

226 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 16. Host commands
The host commands enable you to work with host objects with the SAN Volume Controller.

addhostiogrp
The addhostiogrp command enables you to map I/O groups to an existing host object.

Syntax


addhostiogrp -iogrp iogrp_list host_name

-iogrpall host_id

Parameters
-iogrp iogrp_list
(Required if you do not use -iogrpall) Specifies a colon-separated list of one or more I/O groups that
must be mapped to the host. You cannot use this parameter with the -iogrpall parameter.
-iogrpall
(Required if you do not use -iogrp) Specifies that all the I/O groups must be mapped to the specified
host. You cannot use this parameter with the -iogrp parameter.
host_id | host_name
(Required) Specifies the host to which the I/O groups must be mapped, either by ID or by name.

Description

This command allows you to map the list of I/O groups to the specified host object.

An invocation example
addhostiogrp -iogrpall testhost

The resulting output

No feedback

addhostport
The addhostport command adds worldwide port names (WWPNs) or iSCSI names to an existing host
object.

Syntax


addhostport -hbawwpn wwpn_list host_name

-iscsiname iscsi_name_list -force host_id

Parameters
-hbawwpn wwpn_list
(Required if you do not use iscsiname) Specifies the list of Fibre Channel host ports to add to the
host. At least one worldwide port name (WWPN) or Internet Small Computer System Interface
(iSCSI) name must be specified. You cannot use this parameter with the iscsiname parameter.

© Copyright IBM Corp. 2003, 2012 227

 -iscsiname iscsi_name_list
(Required if you do not use hbawwpn) Specifies the comma-separated list of iSCSI names to add to the
host. At least one WWPN or iSCSI name must be specified. You cannot use this parameter with the
hbawwpn parameter.
-force
(Optional) Specifies that the list of ports be added to the host without the validation of any WWPNs
or iSCSI names.
host_id | host_name
(Required) Specifies the host object to add ports to, either by ID or by name.

Description

This command adds a list of host bust adapter (HBA) WWPNs or iSCSI names to the specified host
object. Any virtual disks that are mapped to this host object automatically map to the new ports.

Only WWPNs that are logged-in unconfigured can be added. For a list of candidate WWPNs, use the
lshbaportcandidate command.

Some HBA device drivers do not log in to the fabric until they can recognize target logical unit numbers
(LUNs). Because they do not log in, their WWPNs are not recognized as candidate ports. You can specify
the force parameter with the addhostport command to stop the validation of the WWPN list.

Note: When all I/O groups are removed from an iSCSI host, you cannot add a port to the iSCSI host
until you have mapped the iSCSI host to at least one I/O group. After mapping the iSCSI host to at least
one I/O group, resubmit the addhostport command. After adding the port to the host, you must create a
host authentication entry using the chhost command.

2 The addhostport command fails if the:

2 v Host is mapped to a volume with more than one I/O group in the access set and the host port being
2 added is an Internet Small Computer System Interface (iSCSI) name or the p
2 v Port being added is from a host system that does not support volumes being mapped from multiple
2 I/O groups

An invocation example
addhostport -hbawwpn 210100E08B251DD4 host_one

The resulting output

No feedback

An invocation example
addhostport -iscsiname iqn.localhost.hostid.7f000001 mchost13

The resulting output

No feedback

chhost
The chhost command changes the name or type of a host object. This does not affect any existing virtual
disk-to-host mappings.

Syntax

228 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide


chhost

-type hpux -mask port_login_mask
tpgs
generic
openvms

host_name

-name new_name_arg -chapsecret chap_secret -nochapsecret host_id

Parameters
-type hpux | tpgs | generic | openvms
(Optional) Specifies the type of host: hpux, tpgs, generic, or openvms. The default is generic. The
tpgs parameter enables extra target-port unit attentions. Refer to SAN Volume Controller host
attachment documentation for more information on the hosts that require the type parameter.
-name new_name_arg
(Optional) Specifies the new name that you want to assign to the host object.
-mask port_login_mask
2 (Optional) Specifies which node target ports a host can access and the Fibre Channel (FC) port mask
2 for the host. Worldwide port names (WWPNs) in the host object must access volumes from the node
2 ports that are included in the mask and are in the host object's I/O group. The value must be a
2 numeric string up to 64 alphanumeric characters.
-chapsecret chap_secret
(Optional) Sets the Challenge Handshake Authentication Protocol (CHAP) secret used to authenticate
the host for iSCSI I/O. This secret is shared between the host and the cluster. The CHAP secret for
each host can be listed using the lsiscsiauth command.
-nochapsecret
(Optional) Clears any previously set CHAP secret for this host.
host_name | host_id
(Required) Specifies the host object to modify, either by ID or by current name.

Description

This command can change the name of the specified host to a new name, or it can change the type of
host. This command does not affect any of the current virtual disk-to-host mappings.

The port mask applies to logins from the host initiator port that are associated with the host object. For
each login between a host HBA port and node port, the node examines the port mask that is associated
with the host object for which the host HBA is a member and determines if access is allowed or denied.
If access is denied, the node responds to SCSI commands as if the HBA port is unknown.

Note: When all I/O groups are removed from an iSCSI host, the lsiscsiauth command does not display
the authentication entry for that host. Use the addhostiogrp command to map the iSCSI host to at least
one I/O group, and then use the addhostport command to add the iSCSI port into it. You must also add
authentication for that host using the chhost command with either the chapsecret or nochapsecret
parameter.

An invocation example
2 chhost -name testhostlode -mask 111111101101 hostone

The resulting output

No feedback

Chapter 16. Host commands 229

 An invocation example
chhost -type openvms 0

The resulting output

No feedback

mkhost
The mkhost command creates a logical host object.

Syntax


mkhost -hbawwpn wwpn_list

-name new_name -iscsiname iscsi_name_list

-iogrp iogrp_list -mask port_login_mask -force


-type hpux
tpgs
generic
openvms

Parameters
-name new_name
(Optional) Specifies a name or label for the new host object.
-hbawwpn wwpn_list
(Required if you do not use iscsiname) Specifies one or more host bus adapter (HBA) worldwide
port names (WWPNs) to add to the specified host object. At least one WWPN or iSCSI name must be
specified. You cannot use this parameter with the iscsiname parameter.
-iscsiname iscsi_name_list
(Required if you do not use hbawwpn) Specifies the comma-separated list of iSCSI names to add to the
host. At least one WWPN or iSCSI name must be specified. You cannot use this parameter with the
hbawwpn parameter.
-iogrp iogrp_list
(Optional) Specifies a set of one or more I/O groups that the host can access the VDisks from. I/O
groups are specified using their names or IDs, separated by a colon. Names and IDs can be mixed in
the list. If this parameter is not specified, the host is associated with all I/O groups.
-mask port_login_mask
2 (Optional) Specifies which node target ports a host can access and the Fiber Channel (FC) port mask
2 for the host. Worldwide port names (WWPNs) in the host object must access volumes from the node
2 ports that are included in the mask and are in the host object's I/O group. The value must be a
2 numeric string up to 64 characters. The default value is all 1's.
-force
(Optional) Specifies that a logical host object be created without validation of the WWPNs.
-type hpux | tpgs | generic | openvms
(Optional) Specifies the type of host. The default is generic. The tpgs parameter enables extra
target-port unit attentions. Refer to SAN Volume Controller host attachment documentation for more
information on the hosts that require the type parameter.

230 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

The mkhost command associates one or more HBA WWPNs or iSCSI names with a logical host object.
This command creates a new host. The ID is displayed when the command completes. You can
subsequently use this object when you map virtual disks to hosts by using the mkvdiskhostmap command.

Issue the mkhost command only once. The cluster scans the fabric for WWPNs in the host zone. The
cluster itself cannot filter into the hosts to determine which WWPNs are in which hosts. Therefore, you
must use the mkhost command to identify the hosts.

After you identify the hosts, mappings are created between hosts and virtual disks. These mappings
effectively present the virtual disks to the hosts to which they are mapped. All WWPNs in the host object
are mapped to the virtual disks.

Some HBA device drivers do not log in to the fabric until they can see target logical unit numbers
(LUNs). Because they do not log in, their WWPNs are not recognized as candidate ports. You can specify
the force parameter with this command to stop the validation of the WWPN list.

This command fails if you add the host to an I/O group that is associated with more host ports or host
objects than is allowed by the limits within the cluster.

For additional information, see the mkvdiskhostmap and lshbaportcandidate commands.

An invocation example
2 mkhost -name hostone -hbawwpn 210100E08B251DD4 -force -mask 111111101101

The resulting output

Host id [1] successfully created

An invocation example
mkhost -iscsiname iqn.localhost.hostid.7f000001 -name newhost

The resulting output

Host, id [10], successfully created

An invocation example
mkhost -hbawwpn 10000000C92BB490 -type openvms

The resulting output

Host, id [1], successfully created

rmhost
The rmhost command deletes a host object.

Syntax


rmhost host_name

-force host_id

Chapter 16. Host commands 231

 Parameters
-force
(Optional) Specifies that you want the system to delete the host object even if mappings still exist
between this host and virtual disks (VDisks). When the -force parameter is specified, the mappings
are deleted before the host object is deleted.
host_name | host_id
(Required) Specifies the host object to delete, either by ID or by name.

Description

The rmhost command deletes the logical host object. The WWPNs that were contained by this host object
(if it is still connected and logged in to the fabric) are returned to the unconfigured state. When you issue
the lshbaportcandidate command, the host objects are listed as candidate ports.

If any mappings still exist between this host and virtual disks, the command fails unless you specify the
-force parameter. When the -force parameter is specified, the rmhost command deletes the mappings
before the host object is deleted.

An invocation example
rmhost host_one

The resulting output

No feedback

rmhostiogrp
e The rmhostiogrp command enables you to delete mappings between one or more input/output (I/O)
e groups and a specified host object.

Syntax


rmhostiogrp -iogrp iogrp_list host_name

-iogrpall -force host_id

Parameters
-iogrp iogrp_list
(Required) Specifies a set of one or more I/O group mappings that will be deleted from the host. You
cannot use this parameter with the -iogrpall parameter.
-iogrpall
(Optional) Specifies that all the I/O group mappings that are associated with the specified host must
be deleted from the host. You cannot use this parameter with the -iogrp parameter.
-force
e (Optional) Specifies that you want the system to remove the specified I/O group mappings on the
e host even if the removal of a host to I/O group mapping results in the loss of VDisk-to-host
e mappings (host mappings).
host_id | host_name
(Required) Specifies the identity of the host either by ID or name from which the I/O group
mappings must be deleted.

232 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

The rmhostiogrp command deletes the mappings between the list of I/O groups and the specified host
object.

e If a host is defined in two I/O groups, and has access to a volume through both I/O groups, an attempt
e to remove the host from just one of those I/O groups fails, even with -force specified. To resolve this
e problem, do one of the following:
e v Delete the host mappings that are causing the error
e v Delete the volumes or the host

e Note: When all I/O groups are removed from an Internet Small Computer System Interface (iSCSI) host,
e and you want to add an iSCSI port to the host, refer to the addhostport and chhost commands.

An invocation example
rmhostiogrp -iogrp 1:2 host0

The resulting output

No feedback

rmhostport
The rmhostport command deletes worldwide port names (WWPNs) or iSCSI names from an existing host
object.

Syntax


rmhostport -hbawwpn wwpn_list host_name

-iscsiname iscsi_name_list -force host_id

Parameters
-hbawwpn wwpn_list
(Required if you do not use iscsiname) Specifies the list of Fibre Channel host ports to delete from
the host. At least one WWPN or iSCSI name must be specified. You cannot use this parameter with
the iscsiname parameter.
-iscsiname iscsi_name_list
(Required if you do not use hbawwpn) Specifies the comma-separated list of iSCSI names to delete
from the host. At least one WWPN or iSCSI name must be specified. You cannot use this parameter
with the hbawwpn parameter.
-force
(Optional) Forces the deletion of the specified ports. This overrides the check that all of the WWPNs
or iSCSI names in the list are mapped to the host specified.
host_name | host_id
(Required) Specifies the host name or the host ID.

Description

This command deletes the list of HBA WWPNs or iSCSI names from the specified host object. If the
WWPN ports are still logged in to the fabric, they become unconfigured and are listed as candidate
WWPNs. See also the lshbaportcandidate command.

Any virtual disks that are mapped to this host object are automatically unmapped from the ports.

Chapter 16. Host commands 233

Replacing an HBA in a host: List the candidate HBA ports by issuing the lshbaportcandidate command.
A list of the HBA ports that are available to be added to host objects is displayed. One or more of these
ports corresponds with one or more WWPNs that belong to the new HBA. Locate the host object that
corresponds to the host in which you have replaced the HBA. The following command lists all the
defined host objects:

lshost

To list the WWPNs that are currently assigned to the host, issue the following:

lshost hostobjectname

where hostobjectname is the name of the host object.

Add the new ports to the existing host object by issuing the following command:

addhostport -hbawwpn one or more existing WWPNs

separated by : hostobjectname/ID

where one or more existing WWPNs separated by : and hostobjectname/id correspond to those values listed in
the previous steps.

Remove the old ports from the host object by issuing the following command:

rmhostport -hbawwpn one or more existing WWPNs

separated by : hostobjectname/ID

where one or more existing WWPNs separated by : corresponds with those WWPNs that are listed in the
previous step that belong to the old HBA that has been replaced. Any mappings that exist between the
host object and VDisks are automatically applied to the new WWPNs. Therefore, the host recognizes that
the VDisks are the same SCSI LUNs as before. See the Multipath Subsystem Device Driver: User's Guide for
additional information about dynamic reconfiguration.

An invocation example
rmhostport -hbawwpn 210100E08B251DD4 host_one

The resulting output

No feedback

An invocation example
rmhostport -iscsiname iqn.localhost.hostid.7f000001 mchost13

The resulting output

No feedback

234 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 17. Information commands
The information commands enable you display specific types of SAN Volume Controller information.

Note: IDs are assigned at run-time by the system and cannot be relied upon to be the same after
configuration restoration. Therefore, use object names instead of IDs whenever possible.

ls2145dumps (Deprecated)
Attention: The ls2145dumps command is deprecated. Use the lsdumps command to display a list of files
in a particular dumps directory.

lscimomdumps (Deprecated)
Attention: The lscimomdumps command is deprecated. Use the lsdumps command to display a list of files
in a particular dumps directory.

lscopystatus
Use the lscopystatus command to determine whether any file copies are currently in progress.

Syntax


lscopystatus

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command displays an indicator that shows if a file copy is currently in progress. Only one file can
be copied in the cluster at a time.

An invocation example
lscopystatus

© Copyright IBM Corp. 2003, 2012 235

 The resulting output
status
active

1 lscluster
1 Attention: The lscluster command has been discontinued. Use the lssystem command instead.
1
1 lsclustercandidate
1 Attention: The lsclustercandidate command has been discontinued. Use the lspartnershipcandidate
1 command instead.
1
lscluster
Attention: The lscluster command has been discontinued. Use the lssystem command instead.

lsclusterip
Attention: The lsclusterip command has been discontinued. Use the lssystemip command instead.

1 lssystem
1 The lssystem command returns a concise list or a detailed view of a clustered system.

1 Syntax

1

lssystem

1 -filtervalue attribute=value -nohdr -bytes

1


1 -delim delimiter -filtervalue?
1

1 Parameters
1 -filtervalue attribute=value
1 (Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
1 attribute value are displayed. If a capacity is specified, the units must also be included.

1 Note: Some filters allow the asterisk character (*) when you enter the command. The following rules
1 apply to the use of wildcard characters with the SAN Volume Controller CLI:
1 v The wildcard character is an asterisk (*).
1 v The command can contain a maximum of one wildcard.
1 v When you use a wildcard, you must enclose the filter entry within double quotation marks (""), as
1 follows:
1 lssystem -filtervalue "name=md*"
1 -nohdr
1 (Optional) By default, headings are displayed for each column of data in a concise style view, and for
1 each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
1 headings.

1 Note: If there is no data to be displayed, headings are not displayed.

236 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 -bytes
1 (Optional) Specifies that you want the report to display all capacities as bytes.
1 -delim delimiter
1 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
1 column is set to the maximum possible width of each item of data. In a detailed view, each item of
1 data has its own row, and if the headers are displayed, the data is separated from the header by a
1 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
1 one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
1 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
1 view, the data is separated from its header by the specified delimiter.
1 -filtervalue?
1 (Optional) displays a list of filters that can be applied against this view. The following filter attributes
1 are valid for the lssystem command:
1 v id
1 v name

1 Description

1 This command displays a concise list or a detailed view of a system.

1 Table 34 provides the attribute values that can be displayed as output view data.
1 Table 34. Attribute values
1 Attribute Possible Values
1 layer replication, storage (default)

1 Replication means the system can create partnerships

1 with SAN Volume Controller. Storage means the system
1 can present storage to SAN Volume Controller.
1 location local, remote
1 statistics status on, off
1 auth_service_type Tivoli Integrated Portal (TIP) or Native Lightweight
1 Directory Access Protocol (LDAP)
e auth_service_configured True if the auth_service_type is configured and either
e one of the following is true:
e v The auth_service_type is LDAP-only (if at least one
e LDAP server is configured)
e v The auth_service_type is TIP-only:
e – The name, password, and URL are established
e – An SSL certificate is created (if an HTTPS URL is
e available)
e auth_service_enabled
1 True if the auth_service_type is configured
1 email_state running, stopped, invalid
1 partnership fully_configured, partially_configured_local,
1 partially_configured_local_stopped, not_present,
1 fully_configured_stopped,
1 fully_configured_remote_stopped,
1 fully_configured_local_excluded,
1 fully_configured_remote_excluded,
1 fully_configured_exceeded
1 tier Which tier information is being reported

Chapter 17. Information commands 237

1 Table 34. Attribute values (continued)
1 Attribute Possible Values
1 tier_capacity The total MDisk storage in the tier.
1 tier_free_capacity The amount of MDisk storage in the tier that is unused.
1 compression_active Indicates if there are any compressed volume copies in
e the system.
1 compression_virtual_capacity The total virtual capacity for all compressed volume
e copies in the system. This is in unsigned decimal format.
1 compression_compressed_capacity The total used capacity for all compressed volume copies
e in the system. This is in unsigned decimal format.
1 compression_uncompressed_capacity The total uncompressed used capacity for all compressed
e volume copies in the system. This is in unsigned decimal
1 format.
1 rc_buffer_size The resource buffer size assigned for Metro Mirror and
1 Global Mirrored Copy Services.
1 has_nas_key yes | no
1 cluster_ntp_IP_address Shows:
1 v The value auto when the system manages the NTP
1 server settings
1 v An IP (IPv4 or IPv6) address when a user sets up the
1 NTP server
1 v No value (blank) if the NTP server is not set up.
1

1 Information about the remote system is reported by the lssystem command if the mkpartnership
1 command has been issued from the local system to the remote system; for example, if the partnership has
1 been at least partially established from the local system.

1 You can issue the lssystem command to display a detailed view of the system.

1 Detailed view shows the fields described for remote systems only; if the system Location is local, then
1 Partnership and Bandwidth do not apply (and are not defined or provided). For a remote system, these
1 fields indicate the following information:
1 v Location: remote
1 v Partnership:
1 fully_configured
1 The mkpartnership command has been issued in both directions and the remote system is
1 online and available.
1 partially_configured_local
1 The mkpartnership command has only been issued from the local system to the remote system.
1 The remote system is online and available for partnership.
1 partially_configured_local_stopped
1 The mkpartnership command has only been issued from the local system to the remote system.
1 The chpartnership command with the stop parameter has been issued from the local system,
1 and the remote system is online and available. You need to issue the chpartnership command
1 with the start parameter on the local system, and mkpartnership on the remote system.
1 not_present
1 The mkpartnership command has been issued from the local system to the remote system, and
1 the remote system is not available. Either the remote system is offline, or it is not connected to
1 the local system.

238 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 fully_configured_stopped
1 The mkpartnership command has been issued in both directions and the remote system is
1 online and available. The chpartnership command with the stop parameter has been issued
1 from the local system.
1 fully_configured_remote_stopped
1 The mkpartnership command has been issued in both directions and the remote system is
1 online and available. The chpartnership command with the stop parameter has been issued
1 from the remote system.
1 fully_configured_local_excluded
1 The mkpartnership command has been issued in both directions. The local system has excluded
1 the connection to the remote system due to too many problems, or either system in the
1 partnership is unable to sustain the I/O workload for the Metro Mirror or Global Mirror
1 relationships.
1 fully_configured_remote_excluded
1 The mkpartnership command has been issued in both directions. The remote system has
1 excluded the connection to the local system due to too many problems, or either system in the
1 partnership is unable to sustain the I/O workload for the Metro Mirror or Global Mirror
1 relationships.
1 fully_configured_exceeded
1 There are too many systems in the system network, and the partnership from the local system
1 to the remote has been disabled. Refer to the 1710/1720 errors in the system error log at the
1 local and remote system.
1 v Bandwidth: The bandwidth available on the intersystem link for background copy, in megabytes per
1 second (MBps).

1 The console_IP field displays either the:

1 v Automatically-populated in system port 1 IP Address - Internet Protocol Version 4 (IPv4) or IPv6
1 v User-populated IPv4 address
1 The port value is always 443, which requires the system to run using default Hypertext Transfer Protocol
1 Secure (HTTPS).

1 An invocation example with buffer data

1 lssystem

1 The resulting output

1 id 000002007680001A
1 cluster 1
1 name System_0.0.0.0
1 location local
1 partnership
1 bandwidth
1 total_mdisk_capacity 475.1GB
1 space_in_mdisk_grps 0
1 space_allocated_to_vdisks 0.00MB
1 total_free_space 475.1GB
1 total_vdiskcopy_capacity 0.00MB
1 total_used_capacity 0.00MB
1 total_overallocation 0
1 total_vdisk_capacity 0.00MB
1 total_allocated_extent_capacity 0.00MB
1 statistics_status on
1 statistics_frequency 15
1 system_locale en_US
1 time_zone 522 UTC
1 code_level 6.3.0.0 (build 54.0.1109120000)
1 console_IP 0.0.0.0:443

Chapter 17. Information commands 239

1 id_alias 000002007680001A
1 gm_link_tolerance 300
1 gm_inter_system_delay_simulation 0
1 gm_intra_system_delay_simulation 0
1 gm_max_host_delay 5
1 email_reply
1 email_contact
1 email_contact_primary
1 email_contact_alternate
1 email_contact_location
1 email_contact2
1 email_contact2_primary
1 email_contact2_alternate
1 email_state stopped
1 inventory_mail_interval 0
1 system_ntp_IP_address
1 system_isns_IP_address
1 iscsi_auth_method none
1 iscsi_chap_secret
1 auth_service_configured yes
1 auth_service_enabled yes
1 auth_service_url
1 auth_service_user_name
1 auth_service_pwd_set no
1 auth_service_cert_set no
1 auth_service_type auto
1 relationship_bandwidth_limit 25
1 tier generic_ssd
1 tier_capacity 0.00MB
1 tier_free_capacity 0.00MB
1 tier generic_hdd
1 tier_capacity 0.00MB
1 tier_free_capacity 0.00MB
1 has_nas_key no
1 cluster_ntp_IP_address auto
1 layer replication
1 rc_buffer_size 128
1 compression_active yes
1 compression_virtual_capacity 1000.00MB
1 compression_compressed_capacity 0.41MB
1 compression_uncompressed_capacity 512.05MB
1
1 lssystemip
1 The lssystemip command returns a list of the clustered system (system) management IP addresses
1 configured for each port.

1 Syntax

1

lssystemip

1 -nohdr -delim delimiter

1
system_id

1 -filtervalue attribute=value -filtervalue? system_name
1

1 Parameters
1 -nohdr
1 (Optional) By default, headings are displayed for each column of data in a concise style view, and for
1 each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
1 headings.

240 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 Note: If there is no data to be displayed, headings are not displayed.
1 -delim delimiter
1 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
1 column is set to the maximum possible width of each item of data. In a detailed view, each data item
1 has its own row, and if the headers are displayed, the data is separated from the header by a space.
1 The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one-byte
1 character. If you enter -delim : on the command line, the colon character (:) separates all items of
1 data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
1 data is separated from its header by the specified delimiter.
1 -filtervalue attribute=value
1 (Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
1 attribute value are displayed. If a capacity is specified, the units must also be included.

1 Note: Some filters allow the asterisk character (*) when you enter the command. The following rules
1 apply to the use of wildcard characters with the SAN Volume Controller Command-Line Interface
1 (CLI):
1 v The wildcard character is an asterisk (*).
1 v The command can contain a maximum of one wildcard.
1 v When you use a wildcard, you must enclose the filter entry within double quotation marks (""), as
1 shown in the following example:
1 lssystemip -filtervalue "system_name=md*"
1 -filtervalue?
1 (Optional) displays a list of filters that can be applied against this view. The following filter attributes
1 are valid for the lssystemip command:
1 v port_id
1 v system_name
1 v system_id
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
1 system_id | system_name
1 (Required) Specifies the name or ID of a system.

1 Description

1 This command displays a list of the system management IP addresses configured for each port.

1 A concise invocation example

1 lssystemip -delim ,

1 The concise resulting output

1 system_id,system_name,location,port_id,IP_address,subnet_mask,
1 gateway,IP_address_6,gateway_6,prefix_6
1 000002006CC0B71A,cl1,local,1,192.168.1.2,DHCP,255.255.255.0,192.168.1.1,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,2001:0db8:85a3:0000:0000:8a2e:0370:7334,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,64
1 000002006CC0B71A,cl1,local,2,192.168.1.2,DHCP,255.255.255.0,192.168.1.1,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,2001:0db8:85a3:0000:0000:8a2e:0370:7334,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,64
1 000002006CC0B7110,cl2,remote,1,192.168.1.2,DHCP,255.255.255.0,192.168.1.1,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,2001:0db8:85a3:0000:0000:8a2e:0370:7334,

Chapter 17. Information commands 241

1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,64
1 000002006CC0B7110,cl2,remote,2,192.168.1.2,DHCP,255.255.255.0,192.168.1.1,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,2001:0db8:85a3:0000:0000:8a2e:0370:7334,
1 2001:0db8:85a3:0000:0000:8a2e:0370:7334,64

1 A detailed invocation example

1 lssystemip 000002006CC0B71A

1 The detailed resulting output

1 system_id 000002006CC0B71A
1 system_name cl1
1 location local
1 port_id 1
1 IP_address 192.168.1.2
1 subnet_mask 255.255.255.0
1 gateway 192.168.1.1
1 IP_address_6 2001:0db8:85a3:0000:0000:8a2e:0370:7334
1 gateway_6 2001:0db8:85a3:0000:0000:8a2e:0370:7334
1 prefix_6 64
1
1 system_id 000002006CC0B71A
1 system_name cl1
1 location local
1 port_id 2
1 IP_address 192.168.1.2
1 subnet_mask 255.255.255.0
1 gateway 192.168.1.1
1 IP_address_6 2001:0db8:85a3:0000:0000:8a2e:0370:7334
1 gateway_6 2001:0db8:85a3:0000:0000:8a2e:0370:7334
1 prefix_6 64
1
1 lssystemstats
1 The lssystemstats command displays the most recent values of all node statistics across all nodes in a
1 clustered system. This command also can be used to display a history of values for a given subset of
1 available statistics.

1 Syntax

1

lssystemstats

-delim delimiter -history stat_list
1

1 Parameters
1 -delim delimiter
1 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
1 column is set to the maximum possible width of each item of data. In a detailed view, each item of
1 data has its own row, and if the headers are displayed, the data is separated from the header by a
1 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
1 one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
1 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
1 view, the data is separated from its header by the specified delimiter.
1 -history stat_list
1 Provides the most recent node statistical values, specific node statistical values, or historical data for
1 any node .

242 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 Description

1 This command returns one set of statistics for all the nodes in the system. The statistical values are
1 determined using samples received from each node .

1 Note: Values are rounded to the nearest integer when appropriate (for example, between 1 and 99 when
1 considering percentages).
1 Table 35. lssystemstats attribute values
1 Attribute Value
1 stat_current The current value of the statistic field.
1 sample_epoch The number of seconds since the sample's epoch time was reached.
1 stat_list The system history of the reported statistics.
1 stat_name The name of the statistic field.
1 stat_peak The peak value of the statistic field in the last five minutes.
1 stat_peak_time The time that the peak occurred.
1 sample_time The time of the sample occurrence.
1 stat_value The statistical value at the epoch interval.
1

1 Note: Filtering is supported on the node_id , node_name, and stat_name fields using only the concise view.

1 A system summary invocation example

1 lssystemstats

1 The resulting output

1 stat_name stat_current stat_peak stat_peak_time
1 cpu_pc 5 6 111123104304
1 fc_mb 321 327 111123104129
1 fc_io 2167 2368 111123103904
1 sas_mb 438 534 111123104104
1 sas_io 5784 7738 111123104314
1 iscsi_mb 0 0 111123104359
1 iscsi_io 0 0 111123104359
1 write_cache_pc 0 0 111123104359
1 total_cache_pc 0 0 111123104359
1 vdisk_mb 321 326 111123104129
1 vdisk_io 2070 2276 111123103904
1 vdisk_ms 34 52 111123103954
1 mdisk_mb 320 329 111123104029
1 mdisk_io 3135 3340 111123103904
1 mdisk_ms 15 24 111123104314
1 drive_mb 440 534 111123104104
1 drive_io 5765 6572 111123104104
1 drive_ms 14 21 111123104314
1 vdisk_r_mb 174 178 111123104324
1 vdisk_r_io 1064 1180 111123103904
1 vdisk_r_ms 31 53 111123103954
1 vdisk_w_mb 146 159 111123104129
1 vdisk_w_io 1006 1160 111123104129
1 vdisk_w_ms 38 54 111123104314
1 mdisk_r_mb 172 177 111123104259
1 mdisk_r_io 2054 2184 111123103904
1 mdisk_r_ms 11 18 111123103954
1 mdisk_w_mb 146 160 111123104129
1 mdisk_w_io 1081 1229 111123104129
1 mdisk_w_ms 25 38 111123104314
1 drive_r_mb 207 356 111123104329

Chapter 17. Information commands 243

1 drive_r_io 2940 3952 111123104104
1 drive_r_ms 11 18 111123104314
1 drive_w_mb 231 250 111123104129
1 drive_w_io 2825 3156 111123104129
1 drive_w_ms 16 24 111123104314

1 A filtered system summary invocation example

1 lssystemstats -filtervalue stat_name=cpu_pc:stat_name=fc_mb -delim :

1 The resulting output

1 The filtered system summary output:
1 stat_name:stat_current:stat_peak:stat_peak_time
1 cpu_pc:5:7:111123104547
1 fc_mb:319:339:111123104517

1 A system summary (using the historical view) invocation example

1 lssystemstats -history fc_io

1 The resulting output

1 Partial output for the historical system summary example:

1 sample_time stat_name stat_value
1 111123104224 fc_io 2120
1 111123104229 fc_io 2102
1 111123104234 fc_io 2041
1 111123104239 fc_io 2211
1 111123104244 fc_io 2204
1 111123104249 fc_io 2046
1 111123104254 fc_io 1997
1 111123104259 fc_io 2081
1 111123104304 fc_io 2123
1 111123104309 fc_io 2030
1 111123104314 fc_io 1754
1 111123104319 fc_io 1640
1 111123104324 fc_io 1759
1 111123104329 fc_io 1638
1 111123104334 fc_io 1804
1 111123104339 fc_io 2011
1 111123104344 fc_io 2028
1 111123104349 fc_io 2171
1 111123104354 fc_io 2055
1 111123104359 fc_io 2167
1 111123104404 fc_io 2140
1 111123104409 fc_io 2111
1
lscontroller
The lscontroller command returns a concise list, or a detailed view, of controllers that are visible to the
cluster.

Syntax


lscontroller

-filtervalue attrib=value -nohdr


-delim delimiter -filtervalue? controller_id
controller_name

244 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard, which must be the first or last character in
the string.
v When using a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lscontroller -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-filtervalue?
(Optional) Displays the valid filter attributes. The following filter attributes for the lscontroller
command are valid:
v controller_id
v id
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
controller_id | controller_name
(Optional) Specifies the name or ID of a controller. When you use this parameter, the detailed view of
the specific controller is returned and any value that is specified by the -filtervalue parameter is
ignored. If you do not specify the controller_id | controller_name parameter, the concise view displays
all controllers matching the filtering requirements that are specified by the -filtervalue parameter.

Description

This command returns a concise list, or a detailed view, of controllers visible to the cluster.

The following values are applicable to the data in the output views:
degraded no, yes

To differentiate the name of a storage controller from the name shown on the cluster, list the storage
controllers by issuing the lscontroller command. Record the controller name or ID for the controller
that you want to determine. For the controller in question, issue the lscontroller controller name | id
command, where controller name | id is the controller name or ID. Record the worldwide node name

Chapter 17. Information commands 245

(WWNN) for the controller. You can use the WWNN to determine the actual storage controller by
launching the native controller user interface, or by using the command line tools it provides to verify the
actual controller that has the WWNN.

Notes:
1. The mdisk_link_count value is the number of MDisks currently associated with this storage controller.
2. The max_mdisk_link_count value is the highest value that the mdisk_link_count has reached since it was
last reset to the mdisk_link_count value.

Remember: This value is reset by specific maintenance procedures or when the event log is cleared.
3. A SAN connection from a node or node canister port to a controller port for a single MDisk is a path.
The controller port path_count value is the number of paths that are currently being used to submit
input/output (I/O) data to this controller port.
4. The storage controller max_path_count value is the highest value that the storage controller path_count
has reached since it was last reset to the path_count value. This value is reset by specific maintenance
procedures or when the cluster error log is cleared.

Important: The max_path_count value is the highest value that the path_count has reached since it was
last reset to the path_count value.

Remember: This value is reset by specific maintenance procedures or when the event log is cleared.
5. The allow_quorum value identifies if the controller is currently enabled to support quorum disks.
Quorum support is either enabled or disabled depending on the controller hardware type.
6. The ctrl_s/n value is the controller serial number.

Important: This data comes from vendor-controlled sources and might not be available.

A concise invocation example

lscontroller -delim :

The concise resulting output

id:controller_name:ctrl_s/n:vendor_id:product_id_low:product_id_high
7:controller7:3EK0J5Y8:SEAGATE :ST373405:FC
8:controller8:3EK0J6CR:SEAGATE :ST373405:FC
9:controller9:3EK0J4YN:SEAGATE :ST373405:FC
10:controller10:3EK0GKGH:SEAGATE :ST373405:FC
11:controller11:3EK0J85C:SEAGATE :ST373405:FC
12:controller12:3EK0JBR2:SEAGATE :ST373405:FC
13:controller13:3EKYNJF8:SEAGATE :ST373405:FC
14:controller14:3EK0HVTM:SEAGATE :ST373405:FC

A detailed invocation example

lscontroller -delim = 7

The detailed resulting output

id=7
controller_name=controller7
WWNN=20000004CF2412AC
mdisk_link_count=1
max_mdisk_link_count=1
degraded=no
vendor_id=SEAGATE
product_id_low=ST373405
product_id_high=FC
product_revision=0003
ctrl_s/n=3EK0J5Y8
allow_quorum=no

246 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 WWPN=22000004CF2412AC
path_count=1
max_path_count=1
WWPN=21000004CF2412AC
path_count=0
max_path_count=0

1 lspartnershipcandidate
1 The lspartnershipcandidate command lists the clustered systems that are available for setting up a
1 partnership with the local system. This is a prerequisite for creating inter-system Metro or Global Mirror
1 relationships.

1 Syntax

1

lspartnershipcandidate

-nohdr -delim delimiter
1

1 Parameters
1 -nohdr
1 (Optional) By default, headings are displayed for each column of data in a concise style view, and for
1 each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
1 headings.

1 Note: If there is no data to be displayed, headings are not displayed.

1 -delim delimiter
1 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
1 column is set to the maximum possible width of each item of data. In a detailed view, each item of
1 data has its own row, and if the headers are displayed, the data is separated from the header by a
1 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
1 one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
1 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
1 view, the data is separated from its header by the specified delimiter.

1 Description

1 This command displays a list of systems that are available as candidate partner systems to form a Metro
1 Mirror or Global Mirror partnership between two systems.

1 Output from the command shows the system ID, name, and configured status of the remote candidate
1 system. The remote candidate system forms a partnership with the local system when you use the
1 mkpartnership command. The remote system shows the partnership status as
1 partially_configured_local_stopped or partially_configured_local when you use the lssystem
1 command. The lspartnershipcandidate command displays the configured status of those remote systems
1 that have formed a partnership with the local system.

1 An invocation example
1 lspartnershipcandidate

1 The resulting output

1 id configured system_name
1 0000010034E0F430 no ldsystem26

Chapter 17. Information commands 247

lscontrollerdependentvdisks
The lscontrollerdependentvdisks command lists the volumes that are dependent on the specified
controller.

Syntax


lscontrollerdependentvdisks controller_id_list

controller_name_list

Parameters
controller_id_list | controller_name_list
Specifies one or more controller IDs, controller names, or both. Separate multiple controllers using the
colon character (:).

Description

The lscontrollerdependentvdisks command lists the volumes that are dependent on the status of the
specified controllers. If a controller goes offline, the dependent volumes also go offline. Before taking a
controller offline for maintenance, you can use the command to ensure that you do not lose access to any
volumes.

If you have multiple controllers configured as a single subsystem, you must specify all of the controllers
in the subsystem, using a single command invocation.

The lscontrollerdependentvdisks command also checks for quorum disks on the specified controller list.
If any quorum disks are on the specified controller list, the command returns an error. All quorum disks
must be moved before performing any maintenance. After moving quorum disks, reissue the command to
list the dependent volumes.

Note: The command lists the volumes that are dependent on the controllers at the time the command is
run; subsequent changes to your system require rerunning the command.

An invocation example
lscontrollerdependentvdisks controller0

The resulting output

vdisk_id vdisk_name
0 vdisk0
1 vdisk1
2 vdisk2

lscurrentuser
Use the lscurrentuser command to display the name and role of the logged-in user.

Syntax


lscurrentuser

-nohdr -delim delimiter

248 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. If you enter -delim : on the command line, the colon character (:) separates all items of data
in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is
separated from its header by the specified delimiter.

Description

This command displays the name and role of the current user.

An invocation example
lscurrentuser

The resulting output

name superuser
role SecurityAdmin

lsdiscoverystatus
Use the lsdiscoverystatus command to determine whether a discovery operation is in progress.

Syntax


lsdiscoverystatus

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Chapter 17. Information commands 249

Description

This command displays the state of all discoveries in the cluster. During discovery, the system updates
the drive and MDisk records. You must wait until the discovery has finished and is inactive before you
attempt to use the system.This command displays one of the following results:
active There is a discovery operation in progress at the time that the command is issued.
inactive
There are no discovery operations in progress at the time that the command is issued.

If the Fibre Channel functions are used only to enable the nodes to cluster, then the Fibre Channel line
will not be displayed in the lsdiscoverystatus command. The fc_fabric line will only appear if there is at
least one Fibre Channel controller.

An invocation example
lsdiscoverystatus -delim :

The resulting output

id:scope:IO_group_id:IO_group_name:status
0:fc_fabric:::active
1:sas_iogrp:0:io_grp0:inactive
3:sas_iogrp:2:io_grp2:active

lsdumps
Use the lsdumps command to display a list of files in a particular dumps directory on one of the nodes in
the cluster.

Syntax


lsdumps

-nohdr -delim delimiter -prefix directory_name


node_id_or_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, then the data is separated from the header by
a space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-prefix directory_name
(Optional) Specifies the name of the directory to list files for. The default is the /dumps directory. Valid
directory names:

250 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 v /dumps
v /dumps/audit
v /dumps/cimom
v /dumps/elogs
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/mdisk
v /home/admin/upgrade
v /dumps/drive
v /dumps/enclosure
node_id _or_name
(Optional) Specifies the node ID or name to list the available dumps for. If you do not specify a node,
the available dumps on the configuration node are listed.

Description

This command displays a list of files detected by a node. You can specify the name of the directory to list
files for, and the node ID or name. If you do not specify a directory, the /dumps directory is used.

The files are listed in order of time created, with the oldest files listed first.

An invocation example

To list the files in /dumps on the configuration node:

lsdumps

The resulting output

id filename
0 svc.config.cron.bak_node1
1 svc.config.backup.xml_node1
2 recover.110584.100116.035201
3 dump.110584.100118.051550
4 ethernet.aaabbbX-1.trc

An invocation example

To list the error log files on node 2:

lsdumps -prefix /dumps/elogs 2

The resulting output

id filename
0 errlog_110584_090624_200258
1 errlog_110584_090717_231023

lsemailserver
The lsemailserver command returns a concise list or a detailed view of email servers that are configured
on the cluster.

Chapter 17. Information commands 251

Syntax


lsemailserver

-nohdr -delim delimiter email_server_name
email_server_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
email_server_name | email_server_id
(Optional) Specifies the name or ID of an existing email server that must be listed.

Description

Use this command to display a concise list or a detailed view of email servers that are configured on the
cluster.

A concise invocation example

lsemailserver -delim :

The concise resulting output

id:name:IP_address:port
0:emailserver0:192.135.60.3:25
1:emailserver1:192.135.60.4:25
2:emailserver2:192.135.60.5:25

A detailed invocation example

lsemailserver email0

The detailed resulting output

id 0
name emailserver0
IP_address 192.135.60.3
port 25

lsemailuser
The lsemailuser command generates a report that lists the email event notification settings for all email
recipients, an individual email recipient, or a specified type (local or support) of email recipient.

252 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


lsemailuser

-type support -delim delimiter id_or_name
local

Parameters
-type support | local
(Optional) Specifies the types of email recipients you want to view, either customer or support based
as determined by the following definitions:
support
Address of the support organization that provides vendor support.
local All other addresses.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, a colon separates all items of data in
a concise view; the spacing of columns does not occur. In a detailed view, the data is separated from
its header by a colon.
id_or_name
(Optional) Specifies the user ID or user name of the email event recipient for whom you want to see
the email notification settings.

Description

When you issue this command, a report is displayed that lists the email event notification settings for all
email recipients, an individual email recipient, or a specified type (local or support) of email recipient.
The concise and detailed views report the same information.

An invocation example

The following command lists information for all email recipients using the email event notification
facility, in a concise view:
lsemailuser -delim :

The resulting output

id:name:address:user_type:error:warning:info:inventory
1:Support:[email protected]:support:on:off:off:off
2:Fred:fred_house@my_company.co.uk:local:on:on:on:off
3:Log:our_log@my_company.co.uk:local:on:on:on:on

lsfabric
The lsfabric command generates a report that displays the Fibre Channel connectivity between nodes,
controllers, and hosts.

Syntax

Chapter 17. Information commands 253



lsfabric

-node node_id_or_name
-port port_id
-wwpn wwpn
-host host_id_or_name
-controller controller_id_or_name
-cluster cluster_id_or_name

Parameters
-node node_id_or_name
(Optional) Displays the output for all ports for the specified node. The only parameter that you can
specify with the -node parameter is the -port parameter.
-port port_id
(Optional) Displays a concise view of all worldwide port names (WWPNs) that are logged into the
specified port ID and node. The -port parameter must be specified with only the -node parameter. A
valid port_id value is a number from 1 - 4 that specifies the port number in the vital product data
(VPD) or the hexadecimal WWPN of the local port.
-wwpn wwpn
(Optional) Displays a list of all ports that have a login to the specified WWPN. You cannot use the
-wwpn parameter with any other parameter.
-host host_id_or_name
(Optional) Specifies a host name or ID. Issuing the lsfabric command with the -host parameter is
equivalent to issuing the lsfabric -wwpn wwpn command for every configured WWPN of the
specified host. For example, a host with two ports that are zoned to one port of every node in a
eight-node clustered system (system) produces 16 lines of output. You cannot use the -host parameter
with any other parameter.
-controller controller_id_or_name
(Optional) Specifies a controller ID or name. You cannot use the -controller parameter with any other
parameter in this command. Issuing the lsfabric command with the -controller parameter is
equivalent to issuing the lsfabric -wwpn wwpn command for every configured WWPN of the
specified controller. For example, a controller with 4 ports connected to a 8 node system with 2
counterpart SANs produces 64 lines of output.
-cluster cluster_id_or_name
(Optional) Specifies a system ID or name. You cannot use the -cluster parameter with any other
parameter. Issuing the lsfabric command with the -cluster parameter is equivalent to issuing the
lsfabric -wwpn wwpn command for every known WWPN in the specified system. Output is sorted
by remote WWPNs and then system WWPNs. This parameter can be used to check the state of
connections within the local system or between the local and remote system. When the local system
ID or name is specified, each node-to-node connection is listed twice: once from each end. For
example, an eight-node system with two counterpart SANs produces eight nodes, multiplied by
seven other nodes, multiplied by two SANs, multiplied by four point-to-point logins, equals 448 lines
of output.

e Note: The system must be configured in a remote copy partnership with the local system; it must
e appear in the lssystem view.

Description

The lsfabric command can be issued with any of the parameters to display a limited subset of
information. If the command is issued without any parameters, it provides output for every node.

3 Remember: The value of the local_port field is the number of the node's Fibre Channel (FC) port.

254 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
3 Values for the Type and State columns are:
state active
The meaning of this value depends on the object that it applies to, as follows:
v host or controller: Small Computer System Interface (SCSI) commands were issued within the
last 5 minutes.
v node: node ports can see other ports.
state inactive
No transactions have completed within the last 5 minutes.

Note: It can take up to 10 seconds after a command for a controller port to change from inactive
to active. It can take up to 5 minutes after a command for a host port to change from inactive to
active.
type One of the following values is displayed:
v host
v node
v controller
v unknown
v nas

You can issue this command to view all the information about the connections that are available to your
system.

An invocation example
lsfabric -delim :

The resulting output Each row of output contains the following colon-separated columns:
remote_wwpn:remote_nportid:id:node_name:local_wwpn:
local_port:local_nportid:state:name:cluster_name:type

lsfcconsistgrp
The lsfcconsistgrp command returns a concise list or a detailed view of FlashCopy consistency groups
that are visible to the cluster. This information is useful for tracking FlashCopy consistency groups.

The list report style can be used to obtain two styles of report:
v A list containing concise information about all of the FlashCopy consistency groups on a cluster. (Each
entry in the list corresponds to a single FlashCopy consistency group.)
v The detailed information about a single FlashCopy consistency group.

Syntax


lsfcconsistgrp

-filtervalue attribute=value -nohdr


-delim delimiter -filtervalue? object_id
object_name

Chapter 17. Information commands 255

Parameters
-filtervalue attribute=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is an asterisk character (*).
v The command can contain a maximum of one wildcard, which must be the first or last character in
the string.
v When you use a wildcard, surround the filter entry with double quotation marks (""), as follows:
lsfcconsistgrp -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each item of data in a concise view. The -nohdr
parameter suppresses the display of these headings. Detailed view is not valid for this command.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, the headers are displayed, and the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one
byte character. If you enter -delim : on the command line, the colon character (:) separates all items
of data in a concise view; the spacing of columns does not occur. In a detailed view, the data is
separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the -filtervalue parameter returns an
error message. If you do not specify the object_id or object_name parameter, the concise view of all
objects matching the filtering requirements that is specified by the -filtervalue parameter are
displayed.
-filtervalue?
(Optional) Displays the list of valid filter attributes in the report. The valid filter attributes for the
lsfcconsistgrp command are:
v name
v id
v status
v FC_group_id

Description

This command returns a concise list or a detailed view of FlashCopy consistency groups that are visible
to the cluster.

The following list provides values of the status attribute that are displayed as data in the output views:
status empty, idle_or_copied, preparing, prepared, copying, stopped, suspended, stopping

A concise invocation example

lsfcconsistgrp -delim :

The concise resulting output

256 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
id:name:status
1:ffccg0:empty
2:ffccg1:idle_or_copied
3:ffccg2:idle_or_copied

A detailed invocation example

lsfcconsistgrp -delim : 1

The detailed resulting output

id:1
name:ffccg0
status:empty

A detailed invocation example

lsfcconsistgrp -delim : fccstgrp0

The detailed resulting output

id:1
name:FCcgrp0
status:idle_or_copied
autodelete:off
FC_mapping_id:0
FC_mapping_name:fcmap0
FC_mapping_id:1
FC_mapping_name:fcmap1

lsfcmap
The lsfcmap command generates a list containing concise information about all of the FlashCopy
mappings that are visible to the cluster, or detailed information for a single FlashCopy mapping.

Syntax


lsfcmap

-filtervalue attribute=value -nohdr


-delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attribute=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is the asterisk (*).
v The command can contain a maximum of one wildcard.
v When you use a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lsfcmap -filtervalue "name=md*"
-filtervalue?
(Optional) Displays the valid filter attributes for the -filtervalue attribute=value parameter:
v name

Chapter 17. Information commands 257

 v id
v source_vdisk_id
v source_vdisk_name
v target_vdisk_id
v target_vdisk_name
v group_name
v group_id
v status
v copy_rate
v FC_mapping_name
v FC_id
v partner_FC_id
v partner_FC_name
v restoring
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The delim parameter overrides this behavior. Valid input for the delim parameter is a one-byte
character. If you enter -delim : on the command line, the colon character (:) separates all items of
data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the filtervalue parameter is
ignored. If you do not specify the object_ID or object_name parameter, the concise view of all objects
matching the filtering requirements that is specified by the filtervalue parameter are displayed.

Description

This command returns a concise list or a detailed view of FlashCopy mappings that are visible to the
cluster.

The following list shows attribute values that can be displayed as output view data:
status idle_or_copied, preparing, prepared, copying, stopped, suspended or stopping
start_time
Displays the time that the copy was last started. It is in the format YYMMDDHHMMSS. If a copy
has not been started, a blank line is displayed.

Note: Using rc_controlled indicates that the map is for internal use only. It cannot be manipulated
externally.

258 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
A concise invocation example
lsfcmap -delim :

The concise resulting output

id name source_vdisk_id:source_vdisk_name:target_vdisk_id:target_vdisk_name:group_id
group_name:status:progress:copy_rate:clean_progress:incremental:partner_FC_id:
partner_FC_name:restoring:start_time:rc_controlled
0:test:0:vdisk0:1:vdisk1:idle_or_copied:0:50:100:off:no
no0:fcmap0:0:vdisk0:1:vdisk1:0:fccstgrp0:idle_or_copied:0:50:0:on:2:fcmap2:no
1:fcmap1:2:vdisk2:3:vdisk3:0:fccstgrp0:idle_or_copied:0:0:100:off:::no
2:fcmap2:1:vdisk1:0:vdisk0:0:fccstgrp1:idle_or_copied:0:0:100:off:0:fcmap0:no

A detailed invocation example

lsfcmap 0

The detailed resulting output

id:0
name:fcmap0
source_vdisk_id:63
source_vdisk_name:vdisk63
target_vdisk_id:57
target_vdisk_name:vdisk57
group_id:
group_name:
status:idle_or_copied
progress:0
copy_rate:0
start_time:
dependent_mappings:0
autodelete:off
clean_progress:100
clean_rate:50
incremental:off
difference:100
grain_size:256
IO_group_id:1
IO_group_name:io_grp1
partner_FC_id:
partner_FC_name:
restoring:no
rc_controlled no

lsfcmapcandidate
The lsfcmapcandidate command lists all of the VDisks that are associated with fewer than 256 FlashCopy
mappings.

Syntax


lsfcmapcandidate

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, the heading is displayed for the column of data in a concise style view, and for
the item of data in a detailed style view. The -nohdr parameter suppresses the display of the heading.

Note: If there is no data to be displayed, headings are not displayed.

Chapter 17. Information commands 259

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, a colon character (:) separates all
items of data in a concise view; the spacing of columns does not occur. In a detailed view, the data is
separated from its header by the specified delimiter.

Description

This command returns a list of VDisks that are associated with fewer than 256 FlashCopy mappings.

An invocation example
lsfcmapcandidate

The resulting output

id
2
3
4

lsfcmapprogress
The lsfcmapprogress command returns the progress of the background copy of a FlashCopy mapping.
This is displayed as a percentage completed value.

Syntax


lsfcmapprogress fcmap_id

-nohdr -delim delimiter fcmap_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each item of data in a detailed style view. The
-nohdr parameter suppresses the display of these headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default, all columns of data are space-separated. The width of each column is set to the
maximum possible width of each item of data. In a detailed view, each item of data has its own row,
and if the headers are displayed the data is separated from the header by a space. The -delim
parameter overrides this behavior. Valid input for the -delim parameter is a one byte character. If you
enter -delim : on the command line, the data is separated from its header by a colon character (:).
fcmap_id | fcmap_name
(Required) Specifies that you want the report to display the progress of the background copy for the
designated FlashCopy mapping.

Description

This command reports a percentage for the progress of the background copy being done on the specified
FlashCopy mapping.

An invocation example
260 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
lsfcmapprogress 0

The resulting output

id progress
0 0

lsfcmapdependentmaps
The lsfcmapdependentmaps command displays all the FlashCopy mappings that are dependent on the
user specified mapping.

Syntax


lsfcmapdependentmaps fc_id

-nohdr -delim delimiter fc_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one
byte character. If you enter -delim : on the command line, the colon character (:) separates all items
of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
data is separated from its header by the specified delimiter.
fc_id | fc_name
(Required) Specifies the name or ID of the FlashCopy mapping to list the dependent maps for.

Description

This command returns a list of dependent FlashCopy mappings. This command can be used to determine
the list of FlashCopy mappings that would also stop if you stopped a mapping using the -force parmeter.

There is a dependent_mapping_count field in the FlashCopy map detailed view (displayed when you
process the lsfcmap command) that you can use as an indicator as to whether there are any dependent
mappings in progress. If the count is zero, there are no dependent copies.

Note: If a period of time elapses between the time you process the lsfcmap command and the
lsfcmapdependentmaps command, there could be a difference between the actual number of dependent
mappings being processed and the number that was reported by the lsfcmap command.

A concise invocation example

lsfcmapdependentmaps -delim : 2

The resulting output

Chapter 17. Information commands 261

fc_id:fc_name
1:fcmap1
3:fcmap3

lsfeaturedumps (Deprecated)
Attention: The lsfeaturedumps command is deprecated. Use the lsdumps command to display a list of
files in a particular dumps directory.

lsfreeextents
The lsfreeextents command lists the number of free extents that are available on a specified MDisk.

Syntax


lsfreeextents mdisk_id

-nohdr -delim delimiter mdisk_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
mdisk_id | mdisk_name
(Required) Specifies the ID or the name of the MDisk for which you want to know the number of
free extents.

Description

This command displays a count of the number of free extents on the specified MDisk.

An invocation example
lsfreeextents 2

The resulting output

id 2
number_of_extents 4372

lshbaportcandidate
The lshbaportcandidate command lists all of the unconfigured, logged-in host bus adapter (HBA) ports.
This information is used to find open HBA ports.

262 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


lshbaportcandidate

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command returns a list of unconfigured, logged in HBA ports.

Note: The lshbaportcandidate command presents a list of host HBA ports that are logged in to nodes.
However, there are situations when the information that is presented might include host HBA ports that
are no longer logged in or even part of the SAN fabric. For example, a host HBA port is unplugged from
a switch but lshbaportcandidate still shows the worldwide port name (WWPN) that is logged in to all
nodes. If this occurs, the incorrect entry is removed when another device is plugged in to the same
switch port that previously contained the removed host HBA port.

An invocation example
lshbaportcandidate

The resulting output

id
210100E08B2520D4

lshost
The lshost command generates a list with concise information about all the hosts visible to the clustered
system (system) and detailed information about a single host.

Syntax


lshost

-filtervalue attrib=value -nohdr -delim delimiter


-filtervalue? object_id
object_name

Chapter 17. Information commands 263

 Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller command-line interface (CLI):
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard.
v When using a wildcard character, you must enclose the filter entry within double quotation marks
("" ), as follows:
lshost -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the -filtervalue parameter is ignored.
If you do not specify the object_id | object_name parameter, the concise view of all objects matching
the filtering requirements that is specified by the -filtervalue parameter are displayed.
-filtervalue?
(Optional) Specifies that you want your report to display any or all of the list of valid filter attributes.
The valid filter attributes for the lshost command are:
v host_name
v host_id
v port_count
v name
v id
v iogrp_count
2 v status
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.

Description

This command returns a concise list or a detailed view of hosts visible to the system.

264 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 For Fibre Channel ports, the node_logged_in_count field provides the number of nodes that the host port
is logged into. For iSCSI ports, the node_logged_in_count field provides the number of iSCSI sessions
from the host iSCSI Qualified Name (IQN).

The following list provides the different states for a Fibre Channel host port:
active The host port is active if all nodes with VDisk (volume) mappings have a login for the specified
worldwide port name (WWPN) and at least one node has received SCSI commands from the
WWPN within the last five minutes.
degraded
The host port is degraded if one or more nodes with volume mappings do not have a login for
the specified WWPN.
inactive
The host port is inactive if all the nodes with volume mappings have a login for the specified
WWPN but no nodes have seen any Small Computer System Interface (SCSI) commands from the
WWPN within the last five minutes.
offline
The host port is offline if one or more input/output (I/O) groups with volume mappings do not
have a login for the specified WWPN.

If a host does not have any volume mappings it is reported as offline or inactive.

Note: The lshost command presents a list of host HBA ports that are logged in to nodes. However, there
are situations when the information presented can include host HBA ports that are no longer logged in or
even part of the SAN fabric. For example, a host HBA port is unplugged from a switch, but lshost still
shows the WWPN logged in to all nodes. If this occurs, the incorrect entry is removed when another
device is plugged in to the same switch port that previously contained the removed host HBA port.

The following list provides the different states for a specified iscsiname:
active The iscsiname is active if all I/O groups with volume mappings have at least one associated iscsi
session for the specified iscsiname.
inactive
The iscsiname is inactive if the host has no volume mappings but at least one iscsi session for the
specified iscsiname is present.
offline
The iscsiname is offline if one or more I/O groups with volume mappings do not have an
associated iscsi session for the specified iscsiname.

2 The following list provides the different states for host_status:

2 online The host has full connectivity.
2 offline
2 The host has no connectivity. This might be because the host has been powered down and is not
2 on.
2 degraded
2 The host is not fully connected, which might be introduced by a configuration error or a
2 hardware failure. This can cause a loss of access during any planned maintenance activity and
2 should be corrected as soon as possible.
2 mask The Fiber Channel (FC) I/O ports (which exist on a node) that hosts can access.

e A concise invocation example

e lshost

Chapter 17. Information commands 265

e The resulting output
e id name port_count iogrp_count status
e 0 hostone 1 4 offline
e 1 host0 1 4 degraded
e 2 host1 1 4 online

A detailed invocation example

lshost 0

The resulting output

3 id 0
3 name ined
3 port_count 1
3 type openvms
3 mask 0000000000000000000000000000000000000000000000000000000000001101
3 iogrp_count 4
3 status online
3 WWPN 10000000C92BB490
3 node_logged_in_count 1
3 state inactive

lshostiogrp
The lshostiogrp command displays a list of all the I/O groups that are associated with a specified host.

Syntax


lshostiogrp

-nohdr -delim delimiter host_id
host_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
host_id | host_name
(Required) The name or ID of the host for which the list of I/O groups is required.

Description

This command displays a list of all the I/O groups that are mapped to the specified host.

An invocation example
lshostiogrp -delim : hostone

266 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The resulting output
id:name
0:io_grp0
1:io_grp1

lshostvdiskmap
e The lshostvdiskmap command displays a list of VDisk (volume)s that are mapped to a given host. These
are the volumes that are recognized by the specified host.

Syntax


lshostvdiskmap

-nohdr -delim delimiter host_id
host_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
host_id | host_name
(Optional) Specifies the host in terms of its ID or name. The command displays a list of all the virtual
disks that are mapped to the specified host and the Small Computer System Interface (SCSI) ID by
which they are mapped. If neither a host ID or name are entered, the command displays a list of all
e recognized volume mappings.

Description

This command displays a list of volume IDs and names. These are the volumes that have been mapped
to the specified host; that is, they are visible to the specified host. The SCSI LUN ID is also displayed.
This SCSI LUN ID is the ID by which the volume is recognized by the host.

Each volume that is exported by the clustered system is assigned a unique virtual path (VPATH) number.
This number identifies the volume and determines which volume corresponds to the volume that the
hosts recognize. This procedure can only be performed using the command-line interface.

e For a specific volume based on which operating system and multipath software are used, you can use
e different commands to determine the VPATH serial number. For example, issuing datapath query device
e finds the VPATH serial number for volumes mapped to AIX sddpcm.

e Find the host that is defined to the clustered system that corresponds with the host that you are working
e with.

Chapter 17. Information commands 267

e 1. The worldwide port names (WWPNs) are an attribute of the host bus adapter (HBA). You can find
e these by looking at the device definitions stored by your operating system. For example, on AIX they
e are in the Object Data Manager (ODM), in Windows they are in the Device Manager details for the
e given HBA.
e 2. Verify which host is defined to the clustered system that these ports belong to. The ports are stored as
e part of the detailed view, so you must list each host in turn by issuing the following command:

e lshost host_name | host_id

e where host_name | host_id is the name or ID of the host. Check for matching WWPNs.

e Note: Name your hosts accordingly. For example, if the actual host is called orange, also name the
e host that is defined to the clustered system orange.
e When you have the hostname defined to the clustered system and the vpath serial number, issue the
e following command:

e lshostvdiskmap hostname

e where hostname is the name of the host. A list is displayed. Look for the volume UID that matches the
e vpath serial number and record the volume name or ID.

2 The command returns the following values:

2 id Specifies the host ID in the output for lshostvdiskmap.
2 name Specifies the host name in the output for lshostvdiskmap.
2 SCSI_id
2 Specifies the SCSI ID.
2 vdisk_id
2 Specifies the ID of the volume.
2 vdisk_name
2 Specifies the name of the volume.
2 vdisk_UID
2 Specifies the UID of the volume.
2 IO_group_id
2 Specifies the ID of the input/output (I/O) group in which the host volume mapping exists.
2 IO_group_name
2 Specifies the name of I/O group in which the host volume mapping exists.

An invocation example
lshostvdiskmap -delim : 2

The resulting output

2 id:name:SCSI_id:vdisk_id:vdisk_name:vdisk_UID:IO_group_id:IO_group_name
2 2:host2:0:10:vdisk10:6005076801958001500000000000000A:0:iogrp0
2 2:host2:1:11:vdisk11:6005076801958001500000000000000B:1:iogrp1
2 2:host2:2:12:vdisk12:6005076801958001500000000000000C:0:iogrp0
2 2:host2:3:13:vdisk13:6005076801958001500000000000000D:1:iogrp1
2 2:host2:4:14:vdisk14:6005076801958001500000000000000E:1:iogrp0

268 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 lsiogrp
e The lsiogrp command returns a concise list or a detailed view of input/ouput (I/O) groups visible to the
clustered system (system).

The list report style can be used to obtain the following two styles of report:
v A list containing concise information about all the I/O groups that are visible to the system. Each entry
in the list corresponds to a single I/O group.
v The detailed information about a single I/O group.

Syntax


lsiogrp

-filtervalue attrib=value -nohdr


-delim delimiter -filtervalue? -bytes object_id
object_name

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcard characters with the SAN Volume Controller CLI:
v The wildcard character is an asterisk (*), which must be the first or last character in the string.
v The command can contain a maximum of one wildcard.
v When you use a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lsiogrp -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one
byte character. If you enter -delim : on the command line, the colon character (:) separates all items
of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
data is separated from its header by the specified delimiter.
-filtervalue?
(Optional) Displays the valid filter attributes for the lsiogrp command:
v HWS_name
v HWS_unique_id
v node_count
v name
v id
v host_count

Chapter 17. Information commands 269

e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-bytes
(Optional) Displays all capacities as bytes.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the -filtervalue parameter is ignored.
If you do not specify the object_id | object_name parameter, the concise view of all objects matching
the filtering requirements that is specified by the -filtervalue parameter are displayed.

Description

This command returns a concise list or a detailed view of I/O groups visible to the system.

You can display the following information for this command:

1 accessible_vdisk_count
1 The number of accessible volumes in this I/O group.
2 compression_active
2 Indicates if compression is active for this I/O group.
raid_total_memory
Total bitmap space available for RAID arrays (in MB with 1 decimal place).
raid_free_memory
Bitmap space available for creating new RAID arrays (in MB with 1 decimal place).

A concise invocation example

lsiogrp -delim :

The concise resulting output

id:name:node_count:vdisk_count:host_count
0:io_grp0:1:0:0
1:io_grp1:0:0:0
2:io_grp2:0:0:0
3:io_grp3:0:0:0
4:recovery_io_grp:0:0:0

A detailed invocation example

lsiogrp -delim : 0

The detailed resulting output

e id:0
e name:io_grp0
e node_count:1
e vdisk_count:51
e host_count:0
e flash_copy_total_memory:3.0MB
e flash_copy_free_memory:1.0MB
e remote_copy_total_memory:6.5MB
e remote_copy_free_memory:2.8MB
e mirroring_total_memory:1.0MB
e mirroring_free_memory:0.3MB
e raid_total_memory:2MB
e raid_free_memory:2MB
1 compression_active:yes
e accessible_vdisk_count 75

270 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
lsiogrphost
The lsiogrphost command displays a list of the hosts that are mapped to a specified I/O group.

Syntax


lsiogrphost

-nohdr -delim delimiter iogrp_id
iogrp_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
iogrp_id | iogrp name
(Required) The ID or name of the I/O group for which a list of all mapped hosts is required.

Description

The lsiogrphost command displays a list of hosts that are mapped to a specified I/O group.

An invocation example
lsiogrphost -delim : 0

The resulting output

id:name
0:hostzero
1:hostone

lsiogrpcandidate
Use the lsiogrpcandidate command to list the I/O groups that can have nodes added to them.

Syntax


lsiogrpcandidate

-nohdr -delim delimiter

Chapter 17. Information commands 271

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description
This command displays a list of I/O groups to which nodes can be added. Only the I/O group IDs are
displayed.

An invocation example
lsiogrpcandidate

The resulting output

id
0
1
2
3
4

lsiostatsdumps (Deprecated)
Attention: The lsiostatsdumps command is deprecated. Use the lsdumps command to display a list of
files in a particular dumps directory.

lsiotracedumps (Deprecated)
Attention: The lsiotracedumps command is deprecated. Use the lsdumps command to display a list of
files in a particular dumps directory.

lsiscsiauth
The lsiscsiauth command lists the Challenge Handshake Authentication Protocol (CHAP) secret
configured for authenticating an entity to the SAN Volume Controller cluster.

Syntax


lsiscsiauth

-nohdr -delim delimiter

272 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e


-filtervalue attrib=value -filtervalue?

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
e -filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed. If a capacity is specified, the units must also be included.

Note: Some filters allow the asterisk character (*) when you enter the command. The following rules
apply to the use of wildcard characters with the SAN Volume Controller CLI:
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard.
v When you use a wildcard, you must enclose the filter entry within double quotation marks (""), as
follows:
lsiscsiauth -filtervalue "name=md*"
-filtervalue?
(Optional) displays a list of filters that can be applied against this view. The following filter attributes
are valid for the lsiscsiauth command:
v type
v id
v name
v iscsi_auth_method
v iscsi_chap_secret
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.

Description

This command lists the CHAP secret configured for authenticating an entity to the SAN Volume
Controller cluster. The command also displays the configured iSCSI authentication method. The
iscsi_auth_method field can have values of none or chap.

When you create an iSCSI host using the mkhost command with the iscsiname parameter, the host is
initially configured with the authentication method as none, and no CHAP secret is set. To set a CHAP
secret for authenticating the iSCSI host with the SAN Volume Controller cluster, use the chhost command
with the chapsecret parameter.

Chapter 17. Information commands 273

A invocation example
lsiscsiauth

The resulting output

type id name iscsi_auth_method iscsi_chap_secret
host 0 mchost20 none
host 1 mchost30 none
host 2 mchost200 none
host 3 mchost40 none
host 4 mchost240 none
host 5 mchost170 none
host 6 mchost120 none
host 7 mchost60 none
host 8 mchost180 none
host 9 mchost13 none
host 10 newhost none

lslicense
The lslicense command displays current license settings for clustered system (system) features.

Syntax


lslicense

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) Suppresses the display of these headings. By default, headings are displayed for each
column of data (in a concise style view providing general information about objects of a particular
type) and for each item of data (in a detailed style view providing much more information about a
specific object of a particular type).

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim :, a colon character (:) separates all items of data in a concise
view; for example, the spacing of columns does not occur. In a detailed view, the data is separated
from its header by the specified delimiter.

Description

The lslicense command displays license settings for system features, including remote copy and
virtualization settings. SAN Volume Controller also includes FlashCopy settings. The displayed output for
SAN Volume Controller lists capacity values in terabytes (TB) and feature enablement. The displayed
output for Storwize V7000 lists enclosure license values.

Use the chlicense command to change the feature license settings. Because the feature license settings are
entered when the system is first created, you must only update the settings if you have changed your
license.

An invocation example

274 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 lslicense

The resulting output

used_flash 0.00
used_remote 0.00
used_virtualization 0.00
license_flash 0
license_remote 20
license_virtualization 30
license_physical_disks 0
license_physical_flash off
license_physical_remote off
1 used_compression_capacity 0.02
1 license_compression_capacity 0
1 license_compression_enclosures 1

lsmdisk
The lsmdisk command returns a concise list or a detailed view of managed disks (MDisks) visible to the
cluster. It can also list detailed information about a single MDisk.

Syntax


lsmdisk

-filtervalue attribute=value -nohdr
-unit b
kb
mb
gb
pb
tb


-bytes -delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attribute=value
e (Optional) Specifies a list of one or more filter attributes matching the specified values; see
e -filtervalue? for the supported attributes. Only objects with a value that matches the filter attribute
e value are returned. If capacity is specified, the units must also be included. Use the unit parameter to
e interpret the value for size or capacity.

e Note: Some filters allow the use of a wildcard when entering the command. The following rules
e apply to the use of wildcards with the SAN Volume Controller CLI:
e v The wildcard character is an asterisk (*).
e v The command can contain a maximum of one wildcard, which must be the first or last character in
e the string.
e v When using a wildcard character, you must enclose the filter entry within double quotation marks
e (""), as follows:
e lsmdisk -filtervalue "name=md*"
e -filtervalue?
(Optional) Includes all of the valid filter attributes in the report. The following filter attributes are
valid for the lsmdisk command:
v id

Chapter 17. Information commands 275

 v name
v status
v mode
v mdisk_grp_id
v mdisk_grp_name
v capacity
v quorum_index
v block_size
v controller_name
v ctrl_WWNN
v controller_id
v path_count
v ctrl_LUN_#
v UID
v preferred_WWPN
v active_WWPN
v tier
Any parameters specified with the -filtervalue? parameter are ignored.

e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-bytes
(Optional) Specifies that you want the report to display all capacities as bytes. Capacity values
displayed in units other than bytes might be rounded. When filtering on capacity, use a unit of bytes,
-unit b, for exact filtering.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the -filtervalue parameter is
ignored. If you do not specify the object_id | object_name parameter, the concise view displays all
objects matching the filtering requirements that are specified by the -filtervalue parameter.

Description

This command returns a concise list or a detailed view of MDisks visible to the cluster. Table 36 on page
277 provides the potential output for MDisks.

276 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 36. MDisk output
Attribute Values
status v online
v offline
v excluded
v degraded_paths
v degraded_ports
v degraded (applies only to internal MDisks)
mode unmanaged, managed, image, array
quorum_index 0, 1, 2, or blank if the MDisk is not being used as a quorum disk
block_size 512, 524 bytes in each block of storage
ctrl_type 4, 6, where 6 is a solid-state drive (SSD) attached inside a node and 4 is any other
device
tier The tier this MDisk has been assigned to by auto-detection (for internal arrays) or
by the user:
v generic_ssd
v generic_hdd (the default value for newly discovered or external MDisk)
Note: You can change this value using the chmdisk command.
raid_status v offline - the array is offline on all nodes
v degraded - the array has deconfigured or offline members; the array is not fully
redundant
v syncing - array members are all online, the array is syncing parity or mirrors to
achieve redundancy
v initting - array members are all online, the array is initializing; the array is fully
redundant
v online - array members are all online, and the array is fully redundant
raid_level The RAID level of the array (RAID0, RAID1, RAID5, RAID6, RAID10).
redundancy The number of how many member disks can fail before the array fails.
strip_size The strip size of the array (in KB).
spare_goal The number of spares that the array members should be protected by.
spare_protection_min The minimum number of spares that an array member is protected by.
balanced Describes if the array is balanced to its spare goals:
v exact: all populated members have exact capability match, exact location match
v yes: all populated members have at least exact capability match, exact chain, or
different enclosure or slot
v no: anything else

Note: The automatic discovery performed by the cluster does not write anything to an unmanaged
MDisk. It is only when you add an MDisk to an MDisk group (storage pool), or use an MDisk to create
an image mode VDisk (volume), that the system uses the storage.

To see which MDisks are available, issue the detectmdisk command to manually rescan the Fibre Channel
network for any new MDisks. Issue the lsmdiskcandidate command to show the unmanaged MDisks.
These MDisks have not been assigned to an MDisk group (storage pool).

Notes:

Chapter 17. Information commands 277

1. A SAN Volume Controller connection from a node or node canister port to a storage controller port
for a single MDisk is a path. The Mdisk path_count value is the number of paths currently being used
to submit input/output (I/O) to this MDisk.
2. The MDisk max_path_count value is the highest value path_count has reached since the MDisk was last
fully online.
3. The preferred_WWPN is one of the World Wide Port Names (WWPNs) the storage controller has
specified as a preferred WWPN. If the controller has nothing specified, this is a blank field.
4. The active_WWPN indicates the WWPN of the storage controller port currently being used for I/O.
a. If no storage controller ports are available for I/O, this is a blank field.
b. If multiple controller ports are actively being used for I/O, this field's value is many.

The following define the status fields:

Online
The MDisk is online and available.
Degraded
(Internal MDisks only) The array has members that are degraded, or the raid_status is degraded.
Degraded ports
There are one or more MDisk port errors.
Degraded paths
One or more paths to the MDisk have been lost; the MDisk is not online to every node in the
cluster.
Offline
All paths to the MDisk are lost.
Excluded
The MDisk is excluded from use by the cluster; the MDisk port error count exceeded the
threshold.

A concise invocation example

lsmdisk -delim :

The concise resulting output

id:name:status:mode:mdisk_grp_id:mdisk_grp_name:capacity:ctrl_LUN_#:controller_name:UID:tier
0:mdisk0:online:unmanaged:::68.4GB:0000000000000000:controller0:
20000004cf2422aa000000000000000000000000000000000000000000000000:generic_hdd
1:mdisk1:online:unmanaged:::68.4GB:0000000000000000:
controller1:20000004cf1fd19d000000000000000000000000000000000000000000000000:generic_hdd
2:mdisk2:online:unmanaged:::68.4GB:0000000000000000:controller2:
20000004cf242531000000000000000000000000000000000000000000000000:generic_hdd

A detailed invocation example

lsmdisk mdisk1

The detailed resulting output

id:1
name:mdisk1
status:online
mode:array
mdisk_grp_id:0
mdisk_grp_name:mdgp0
capacity:136.0GB
quorum_index:
block_size:512
controller_name:controller1
ctrl_type:4

278 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
ctrl_WWNN:200400A0B80F0702
controller_id:1
path_count:2
max_path_count:2
ctrl_LUN_#:0000000000000002
UID:600a0b80000f07020000005c45ff8a7c00000000000000000000000000000000
preferred_WWPN:200400A0B80F0703
active_WWPN:200400A0B80F0703
node_id:
node_name:
location:
fast_write_state:empty
raid_status:
raid_level:
redundancy:
strip_size:
spare_goal:
spare_protection_min:
balanced:
tier:generic_hdd

A detailed invocation example

lsarray mdisk3

The resulting output

mdisk_id:3
mdisk_name:mdisk3
status:online
mode:array
mdisk_grp_id:0
mdisk_grp_name:mdiskgrp0
capacity:68.4GB
quorum_index:
block_size:
controller_name:
ctrl_type:
ctrl_WWNN:
controller_id:
path_count:
max_path_count:
ctrl_LUN_#:
UID:
preferred_WWPN:
active_WWPN:
node_id:
node_name:
location:
fast_write_state:empty
raid_status:online
raid_level:raid0
redundancy:0
strip_size:256
spare_goal:2
spare_protection_min:2
balanced:yes
tier:generic_ssd

lsmdiskdumps (Deprecated)
Attention: The lsmdiskdumps command is deprecated. Use the lsdumps command to display a list of files
in a particular dumps directory.

Chapter 17. Information commands 279

 lsmdisklba
e The lsmdisklba command lists the MDisk and logical block address (LBA) for the specified VDisk
e (volume) LBA.

Syntax


lsmdisklba -vdisklba vdisklba

-copy id -delim delimiter

-vdisk vdisk_id

- nohdr vdisk_name

Parameters
-vdisklba vdisklba
e (Required) Specifies the 64–bit hexadecimal logical block address (LBA) on the volume. The LBA
must be specified in hex, with a 0x prefix.
-copy id
e (Optional) Specifies the volume copy ID to list the MDisk and LBA for. If this parameter is not
e specified, the command lists MDisks and LBAs for all volume copies.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
vdisk_id | vdisk_name
e (Required) Specifies the volume name or ID.

Description

The lsmdisklba command returns the logical block address (LBA) of the MDisk that is associated with
e the volume LBA. For mirrored volume, the command lists the MDisk LBA for both the primary and the
copy.

e If applicable, the command also lists the range of LBAs on both the volume and MDisk that are mapped
e in the same extent, or for space-efficient disks, in the same grain. If a space-efficient volume is offline and
e the specified LBA is not allocated, the command displays the volume LBA range only.

2 The mdisk_lba field provides the corresponding LBA on the real capacity for the input LBA. For
2 compressed volume copies it is empty, and the system displays only the range of physical LBAs where
2 the compressed input LBA is located.

Table 37 on page 281 summarizes the data that can be returned with this command.

280 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Table 37. lsmdisklba command output
Mirrored VDisk with one normal copy and
one offline space-efficient copy
Fully allocated, LBA not allocated on
Field single copy VDisk space-efficient VDisk Normal copy Space-efficient copy
copy_id yes yes yes yes
mdisk_id yes no yes no
mdisk_name yes no yes no
type allocated unallocated allocated offline
1 mdisk_lba yes no yes no
mdisk_start yes no yes no
mdisk_end yes no yes no
vdisk_start yes yes yes yes
vdisk_end yes yes yes yes

2 An invocation example
2 lsmdisklba -vdisk 0 -vdisklba 0x123

2 The resulting output

2 copy_id mdisk_id mdisk_name type mdisk_lba mdisk_start mdisk_end vdisk_start vdisk_end
2 0 1 mdisk1 allocated 0x0000000000100123 0x0000000000100000 0x00000000001FFFFF 0x00000000 0x000FFFFF

lsmdiskcandidate
The lsmdiskcandidate command lists all of the unmanaged MDisks by MDisk ID.

Syntax


lsmdiskcandidate

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command displays a list of MDisks that are unmanaged. Only the MDisk IDs are displayed.

Chapter 17. Information commands 281

When back-end controllers are added to the Fibre Channel SAN and are included in the same switch
zone as a cluster, the cluster automatically detects the back-end controller to determine which storage is
presented to the node. The SCSI logical units that are presented by the back-end controller are displayed
as unmanaged MDisks. However, if the configuration of the back-end controller is modified after this has
occurred, the cluster might be unaware of these configuration changes. You can then request that the
cluster rescan the Fibre Channel SAN to update the list of unmanaged MDisks.

Note: The automatic detection performed by the cluster does not write anything to a unmanaged MDisk.
It is only when you instruct the cluster to add an MDisk to a managed disk group or use a MDisk to
create an image mode virtual disk that the storage is actually used.

Check to see which MDisks are available by issuing the detectmdisk command to manually scan the
Fibre Channel network for any MDisks. Issue the lsmdiskcandidate command to show the unmanaged
MDisks. These MDisks have not been assigned to an MDisk group. Alternatively, you can issue the
lsmdisk command to view all of the MDisks.

An invocation example
lsmdiskcandidate

The resulting output

id
5
6
7
8
9
10
11
12
13
14

lsmdiskextent
The lsmdiskextent command displays the extent allocation between managed disks and virtual disks.
The output lists a VDisk ID, VDisk copy ID, and the number of extents.

Syntax


lsmdiskextent mdisk_name

-nohdr -delim delimiter mdisk_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all

282 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
mdisk_name | mdisk_id
(Required) Specifies the specific object ID or name of the given type.

Description

The command displays a list, in which each entry contains a VDisk ID, VDisk copy ID, and the number
of extents. These VDisk copies are using extents on the specified MDisk. The number of extents being
used on each MDisk is also shown.

Every VDisk copy is constructed from one or more MDisks. At times, you might have to determine the
relationship between the two objects. The following procedure allows you to determine the relationships.

To determine the relationship between VDisk copies and MDisks, issue the following command for each
VDisk copy:

lsvdiskmember vdisk_name | vdisk_id

where vdisk_name | vdisk_id is the name or ID of the VDisk copy. This displays a list of IDs that
correspond to the MDisks that make up the VDisk copy.

To determine the relationship between VDisk copies and MDisks and the number of extents that are
provided by each MDisk, you must use the command-line interface. For each VDisk copy, issue the
following command:

lsvdiskextent vdisk_name | vdisk_id

where vdisk_name | vdisk_id is the name or ID of the VDisk copy. This displays a table of MDisk IDs and
the corresponding number of extents that each MDisk is providing as storage for the given VDisk copy.

To determine the relationship between MDisks and VDisk copies, issue the following command for each
MDisk:

lsmdiskmember mdisk_name | mdisk_id

where mdisk_name | mdisk_id is the name or ID of the MDisk. This displays a list of IDs that correspond
to the VDisk copies that are using this MDisk.

To determine the relationship between MDisks and VDisk copies and the number of extents that are used
by each VDisk copy, you must use the command-line interface. For each MDisk, issue the following
command:

lsmdiskextent mdisk_name | mdisk_id

where mdisk_name | mdisk_id is the name or ID of the MDisk. This command displays a table of VDisk
copy IDs and the corresponding number of extents that are being used by each VDisk copy.

An invocation example
lsmdiskextent -delim : mdisk0

The resulting output

id:number_of_extents:copy_id
1:1:1

Chapter 17. Information commands 283

e lsmdiskgrp
e The lsmdiskgrp command returns a concise list or a detailed view of MDisk groups (storage pools) that
e are visible to the clustered system (system).

e Syntax

e

lsmdiskgrp

e -filtervalue attrib=value -nohdr -bytes

e


e -delim delimiter -filtervalue? object_id
object_name
e

e Parameters
e -filtervalue attrib=value
e (Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
e attribute value are returned. If a capacity is specified, the units must also be included.

e Note: Some filters allow the use of a wildcard when you enter the command. The following rules
e apply to the use of wildcards with the SAN Volume Controller CLI:
e v The wildcard character is an asterisk (*).
e v The command can contain a maximum of one wildcard, which must be the first or last character in
e the string.
e v When using a wildcard, you must enclose the filter entry within double quotation marks (""), as
e follows:
e lsmdiskgrp -filtervalue "name=md*"
e -nohdr
e (Optional) By default, headings are displayed for each column of data in a concise style view, and for
e each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
e headings.

e Note: If there is no data to be displayed, headings are not displayed.

e -bytes
e (Optional) Specifies that you want the report to display all capacities as bytes.
e -delim delimiter
e (Optional) By default in a concise view, all columns of data are space-separated. The width of each
e column is set to the maximum possible width of each item of data. In a detailed view, each item of
e data has its own row, and if the headers are displayed the data is separated from the header by a
e space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one
e byte character. If you enter -delim : on the command line, the colon character (:) separates all items
e of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
e data is separated from its header by the specified delimiter.
e object_id | object_name
e (Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
e the specific object is returned and any value specified by the -filtervalue parameter is ignored. If you
e do not specify the object_id | object_name parameter, the concise view of all objects matching the
e filtering requirements specified by the -filtervalue parameter are displayed.
e -filtervalue?
e Displays a list of valid filter attributes. The valid filters for the lsmdiskgrp command are:
e v name

284 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e v storage_pool_id
e v mdisk_count
e v vdisk_count
e v extent_size
e v status
e v id
e v easy_tier
e v easy_tier_status
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.

e Description

e This command returns a concise list or a detailed view of storage pools visible to the system.

e Command output includes values for the following attributes:

e status The state of the MDisk with the highest-priority status in the group, excluding image mode
e MDisks.
e VDisk_count
e The number of VDisk (volume) copies that are in the storage pool (storage pool).
e capacity
e The total amount of MDisk storage that is assigned to the storage pool.
e extent_size
e The size of the extents for this group: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, or 8192 (MB).
e free_capacity
e The amount of MDisk storage that is assigned to the storage pool that is unused. MDisk storage
e can be used for system quorum data and volumes.
e real_capacity
e The amount of MDisk storage that is assigned to the storage pool that is assigned to volumes.
e virtual_capacity
e The total virtual size of all the volume copies that are associated with the storage pool. This is the
e same as the real_capacity value unless you have configured space-efficient volume copies in this
e storage pool.
e used_capacity
e The total used size of all the volume copies that are associated with the storage pool. This is the
e same as the real_capacity value unless you have configured space-efficient volume copies in this
e storage pool.
e overallocation
e Expressed as a percentage, the ratio of the virtual_capacity value to the capacity. An storage pool
e overallocation of over 100 is only possible if you have configured space-efficient volume copies.
e warning
e This field is a percentage. A warning is generated when the amount of space in the storage pool
e that has been assigned exceeds this level.
e easy_tier
e This value is set by the user and determines whether Easy Tier is permitted to manage the pool.

e Note:
e 1. If easy_tier is on, then easy_tier_status is active

Chapter 17. Information commands 285

e 2. if easy_tier is off, then easy_tier_status is inactive
e 3. If easy_tier is auto, then the value of easy_tier_status is determined by the number of tiers an
e storage pool has.
e easy_tier_status
e Whether the Easy Tier functions are active on an storage pool:
e v active
e v inactive
e tier Which tier information is being reported:
e v generic_ssd
e v generic_hdd
e tier_mdisk_count
e The number of MDisks in the tier.
e tier_capacity
e The total MDisk capacity assigned to the volume in the tier.

e Note: For space-efficient copies, the capacity by tier will be the real capacity.
e tier_free_capacity
e The unused amount of MDisk storage in the tier.
1 compression_active
1 Indicates if there are any compressed volume copies in the storage pool.
2 compression_virtual_capacity
2 The total virtual capacity for all compressed volume copies in the storage pool. This is in
2 unsigned decimal format.
2 compression_compressed_capacity
2 The total used capacity for all compressed volume copies in the storage pool. This is in unsigned
2 decimal format.
2 compression_uncompressed_capacity
2 The total uncompressed used capacity for all compressed volume copies in the storage pool. This
2 is in unsigned decimal format.

e The following define the status fields, from lowest to highest priority:
e Online
e The storage pool is online and available.
e Offline
e All paths to the storage pool are lost.

e A concise invocation example

e lsmdiskgrp -delim :

e The concise resulting output

e id:name:status:mdisk_count:vdisk_count:capacity:extent_size:free_capacity:
1 virtual_capacity:used_capacity:real_capacity:overallocation:warning:easy_tier:easy_tier_status:compression_active:compression_virtual_capacity:compression_compressed_capacity:compression_
1 0:mdiskgrp0:degraded:4:0:34.2GB:16:34.2GB:0:0:0:0:0:auto:inactive:yes:1.95GB:17.88MB:33.91MB
1 1:mdiskgrp1:online:4:6:200GB:16:100GB:400GB:75GB:100GB:200:80:on:active:no:0.00MB:0.00MB:0.00MB

e A detailed invocation example for an storage pool with one tier

e lsmdiskgrp -delim : mdiskgrp1

e The resulting output

286 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e id:1
e name:mdiskgrp1
e status:online
e mdisk_count:4
e vdisk_count:6
e capacity:200GB
e extent_size:16
e free_capacity:100GB
e virtual_capacity:400.00GB
e used_capacity:75.00GB
e real_capacity:100.00GB
e overallocation:200
e warning:80
e easy_tier:on
e easy_tier_status:active
e tier:generic_ssd
e tier_mdisk_count:0
e tier_capacity: 0.00MB
e tier_free_capacity:
e 0.00MB
e tier:generic_hdd
e tier_mdisk_count:4
e tier_capacity:200.00GB
e tier_free_capacity:100.00GB
e compression_active:yes
e compression_virtual_capacity:1000.00MB
e compression_compressed_capacity:0.41MB
e compression_uncompressed_capacity:512.05MB

e A detailed invocation example for an storage pool with two tiers

e lsmdiskgrp -delim : mdiskgrp2

e The resulting output

e id:2
e name:mdiskgrp2
e status:online
e mdisk_count:8
e vdisk_count:6
e capacity:200GB
e extent_size:16
e free_capacity:100GB
e virtual_capacity:400.00GB
e used_capacity:75.00GB
e real_capacity:100.00GB
e overallocation:200
e warning:80
e easy_tier:auto
e easy_tier_status:active
e tier:generic_ssd
e tier_mdisk_count:2
e tier_capacity:20.00GB
e tier_free_capacity:0.00MB
e tier:generic_hdd
e tier_mdisk_count:6
e tier_capacity:180.00GB
e tier_free_capacity:100.00GB
1 compression_active:yes
1 compression_virtual_capacity:1000.00MB
1 compression_compressed_capacity:0.41MB
1 compression_uncompressed_capacity:512.05MB

Chapter 17. Information commands 287

e
lsmdiskmember
e The lsmdiskmember command displays a list of VDisks (volumes) that use extents on the specified
e MDisk. That is, the volumes use extents on the managed disk that are specified by the MDisk ID.

Syntax


lsmdiskmember mdisk_id

-nohdr -delim delimiter mdisk_name

e Parameters
e -nohdr
e (Optional) By default, headings are displayed for each column of data in a concise style view, and for
e each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
e headings.

e Note: If there is no data to be displayed, headings are not displayed.

e -delim delimiter
e (Optional) By default in a concise view, all columns of data are space-separated. The width of each
e column is set to the maximum possible width of each item of data. In a detailed view, each item of
e data has its own row, and if the headers are displayed, the data is separated from the header by a
e space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
e one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
e items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
e view, the data is separated from its header by the specified delimiter.
e mdisk_id | mdisk_name
e (Required) Specifies the ID or name of the MDisk for which you want a list of volumes that use
e extents of that MDisk.

e Description

e This command displays a list of volumes that use extents on the managed disk that are specified by the
e ID. The list displays members of the respective object and is independent of the state of the individual
e members; that is, if they are in offline state, they are still displayed.

e Every volume is constructed from one or more MDisks. To determine the relationship between volume
e copies and MDisks, issue the following command:

e lsvdiskmember vdisk_id | vdisk_name

e where vdisk_id | vdisk_name is the name or ID of the volume copy. This displays a list of IDs that
e correspond to the MDisks that make up the volume copy.

e To determine the relationship between volume copies and MDisks and the number of extents that are
e provided by each MDisk, you must use the command-line interface. For each volume copy, issue the
e following command:

e lsvdiskextent vdisk_id | vdisk_name

e where vdisk_id | vdisk_name is the name or ID of the VDisk copy. This command displays a table of
e MDisk IDs and the corresponding number of extents that each MDisk provides as storage for the volume
e copy.

288 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e To determine the relationship between MDisks and volume copies, issue the following command:

e lsmdiskmember mdisk_id | mdisk_name

e where mdisk_id | mdisk_name is the name or ID of the MDisk. This command displays a list of IDs that
e correspond to the volume copies that are using this MDisk.

e To determine the relationship between MDisks and volume copies and the number of extents that are
e used by each volume copy, you must use the command-line interface. For each MDisk mdisk_id |
e mdisk_name, issue the following command:

e lsmdiskextent mdisk_id | mdisk_name

e where mdisk_id | mdisk_name is the name or ID of the MDisk. This command displays a table of volume
e copy IDs and the corresponding number of extents that are being used by each volume copy.

An invocation example
lsmdiskmember -delim : 1

The resulting output

id:copy_id
0:0
1:0
2:0
3:0
4:0
5:0
6:0

lsmigrate
The lsmigrate command displays the progress of all current data migration operations.

Syntax


lsmigrate

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Chapter 17. Information commands 289

 If you use multiple threads to migrate data, the progress will increment when all threads have completed
the migration of an extent. For large extent sizes with many threads, this can result in quite large
increments in the percentage progress.

Description

This command displays information of all the migrations that are currently in progress.

Note: Only user-initiated migrations are reported using this command. Easy Tier migrations are not
included in the output.

An invocation example
lsmigrate -delim :

The resulting output

migrate_type:MDisk_Group_Migration
progress:96
migrate_source_vdisk_index:33
migrate_target_mdisk_grp:4
max_thread_count:4
migrate_source_vdisk_copy_id:1

lsnode (SAN Volume Controller) / lsnodecanister (Storwize V7000)

The lsnode/ lsnodecanister command returns a concise list or a detailed view of nodes or node
canisters that are part of the clustered system (system).

The list report style can be used to obtain two styles of report:
v A list containing concise information about all the nodes or node canister on a system. Each entry in
the list corresponds to a single node or node canister.
v The detailed information about a single node or node canister.

Syntax


lsnode | lsnodecanister

-filtervalue attrib=value -nohdr

2


-delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller Command-Line Interface (CLI):
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard.
v When using a wildcard, you must enclose the filter entry within double quotation marks (""):
lsnode -filtervalue "name=md*"

290 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -filtervalue?
Displays a list of valid filter attributes for the -filtervalue attribute=value parameter. The valid filters
for the lsnode command are:
v id
v status
v IO_group_name
v IO_group_id
v name
v hardware
v service_IP_address
v UPS_serial_number
v WWNN
v partner_node_id/partner_nodecanister_id
v partner_node_id/partner_nodecanister_id
v config_node/config_nodecanister
v UPS_unique_id
v iscsi_alias
v panel_name
v enclosure_id
v canister_id
v enclosure_serial_number
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
2 object_id | object_name
2 (Optional) Specifies the object ID or name. When you use this parameter, the detailed view of the
2 specific object is returned and any value that is specified by the -filtervalue parameter is ignored. If
2 you do not specify the object_id | object_name parameter, the concise view of all objects matching the
2 filtering requirements that is specified by the -filtervalue parameter are displayed.

Description

SAN Volume Controller: This command returns a concise list or a detailed view of nodes node canisters
that are part of the system. Table 38 on page 292 provides the possible values that are applicable to the
attributes that are displayed as data in the output views.

Chapter 17. Information commands 291

 Table 38. lsnode or lsnodecanister attribute values
Attribute Value
status offline | flushing | pending | online | adding | deleting
config_node no | yes
port_status active | inactive | not installed
hardware 8F2 | 8F4 | 8G4 | CF8 | CG8 | 8A4 | other
UPS_serial_number The serial number of the UPS.
status The status of the node.
UPS_unique_id The unique ID of the UPS.
panel_name Unique identifier for the The status of the nodes.
enclosure_id Blank.
canister_id Blank.
enclosure_serial_number Blank.
1 service_IP_mode Current mode of the service IPv4
1 v Empty if IPv4 is not active
1 v One of the following:
1 – static (if the service IP is set by the user)
1 – dhcp (if the service IP is set successfully using DHCP server)
1 – dhcpfallback (if the service IP is set to a default value after a DHCP server
1 request failed)
1 service_IP_mode_6 Current mode of the service IPv6
1 v Empty if IPv6 is not active
1 v Either static (if the service IP is set by the user) or dhcp (if the service IP set
1 successfully using DHCP server).

2 The first four Fibre Channel (FC) input/output (I/O) ports display the worldwide port name (WWPN),
2 state, and speed. If there are less than four FC I/O ports, the fields display with a WWPN of
2 0000000000000000, port_status of inactive, and port_speed of N/A. To examine the FC ports, use the
2 lsportfc command.

A concise invocation example

lsnode -delim ,

The concise resulting output

IBM_2145:ldcluster-19:admin>lsnode -delim ,
id,name,UPS_serial_number,WWNN,status,IO_group_id,IO_group_name,config_node,UPS_unique_id,hardware,
iscsi_name,
iscsi_alias,panel_name,enclosure_id,canister_id,enclosure_serial_number1,hlcn114289,
10004BC018,5005076801002978,
online,0,io_grp0,no,20400001124C0048,8A4,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114289,,
114289,,,
2,hlcn114253,10004BC023,5005076801002822,online,0,io_grp0,yes,20400001124C0083,8A4,
iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114253,,114253,,,5,hdn116511,1000871087,
5005076801005CCE,online,
1,io_grp1,no,2040000207040207,CF8,iqn.1986-03.com.ibm:2145.ldcluster-19.hdn116511,,116511,,,
4,hdn116520,100062L106,5005076801005FD0,online,1,io_grp1,no,2040000182701006,CF8,
iqn.1986-03.com.ibm:2145.ldcluster-19.hdn116520,,116520,,,

A concise invocation example

lsnodecanister -delim ,

292 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The concise resulting output
IBM_2145:ldcluster-19:admin>lsnode -delim ,
id,name,UPS_serial_number,WWNN,status,IO_group_id,IO_group_name,config_nodecanister,UPS_unique_id,hardware,
iscsi_name,
iscsi_alias,panel_name,enclosure_id,canister_id,enclosure_serial_number1,hlcn114289,
10004BC018,5005076801002978,
online,0,io_grp0,no,20400001124C0048,8A4,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114289,,
114289,,,
2,hlcn114253,10004BC023,5005076801002822,online,0,io_grp0,yes,20400001124C0083,8A4,
iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114253,,114253,,,5,hdn116511,1000871087,
5005076801005CCE,online,
1,io_grp1,no,2040000207040207,CF8,iqn.1986-03.com.ibm:2145.ldcluster-19.hdn116511,,116511,,,
4,hdn116520,100062L106,5005076801005FD0,online,1,io_grp1,no,2040000182701006,CF8,
iqn.1986-03.com.ibm:2145.ldcluster-19.hdn116520,,116520,,,

A detailed invocation example

lsnode -delim , 1

The resulting lsnode output

id,1
name,hlcn114289
UPS_serial_number,10004BC018
WWNN,5005076801002978
status,online
IO_group_id,0
IO_group_name,io_grp0
partner_node_id,2
partner_node_name,hlcn114253
config_node,no
UPS_unique_id,20400001124C0048
port_id,5005076801402978
port_status,active
port_speed,4Gb
port_id,5005076801302978
port_status,active
port_speed,4Gb
port_id,5005076801102978
port_status,active
port_speed,4Gb
port_id,5005076801202978
port_status,active
port_speed,4Gb
hardware,8A4
iscsi_name,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114289
iscsi_alias,
failover_active,no
failover_name,hlcn114253
failover_iscsi_name,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114253
failover_iscsi_alias,
panel_name,114289
enclosure_id,
canister_id,
enclosure_serial_number,
service_IP_address,9.180.29.52
service_gateway,9.180.28.1
service_subnet_mask,255.255.254.0
service_IP_address_6,
service_gateway_6,
service_prefix_6,
1 service_IP_mode dhcpfallback
1 service_IP_mode_6

A detailed invocation example

lsnodecanister -delim , 1

Chapter 17. Information commands 293

 The resulting lsnodecanister output
id,1
name,hlcn114289
UPS_serial_number,10004BC018
WWNN,5005076801002978
status,online
IO_group_id,0
IO_group_name,io_grp0
partner_nodecanister_id,2
partner_nodecanister_name,hlcn114253
config_nodecanister,no
UPS_unique_id,20400001124C0048
port_id,5005076801402978
port_status,active
port_speed,4Gb
port_id,5005076801302978
port_status,active
port_speed,4Gb
port_id,5005076801102978
port_status,active
port_speed,4Gb
port_id,5005076801202978
port_status,active
port_speed,4Gb
hardware,8A4
iscsi_name,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114289
iscsi_alias,
failover_active,no
failover_name,hlcn114253
failover_iscsi_name,iqn.1986-03.com.ibm:2145.ldcluster-19.hlcn114253
failover_iscsi_alias,
panel_name,114289
enclosure_id,
canister_id,
enclosure_serial_number,
service_IP_address,9.180.29.52
service_gateway,9.180.28.1
service_subnet_mask,255.255.254.0
service_IP_address_6,
service_gateway_6,
service_prefix_6,
1 service_IP_mode dhcpfallback
1 service_IP_mode_6

lsnodecandidate (SAN Volume Controller)

The lsnodecandidate command lists all of the nodes that are available to add to the clustered system.

Syntax


lsnodecandidate

-nohdr -delim delimiter -svcconfig

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

294 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-svcconfig
(Optional) Lists all nodes in the enclosure that are in a candidate state.

Description

Note: The lsnodecandidate command is a SAN Volume Controller command. For Storwize V7000, use
the lscontrolenclosurecandidate command.

This command displays a list of nodes that are available to add to the clustered system. This includes
nodes that are not already part of a clustered system, but are compatible with theclustered system
software level. Nodes with hardware types that are incompatible with the installed software are not
listed.

The following table describes the possible outputs:

Table 39. lsnodecandidate outputs
Attribute Description
panel_name Unique identifier for the node.
UPS_serial_number The serial number of the UPS.
UPS_unique_id The unique ID of UPS.
hardware Describes the type of nodes.

An invocation example
lsnodecandidate -delim :

The resulting output

id: panel_name: UPS_serial_number: UPS_unique_id: hardware
1: 146355: 10L3ASH: 202378101C0D18D8: 8G4

lsnodedependentvdisks (Deprecated)
This command has been deprecated. Use the lsdependentvdisks command instead.

lsnodehw (SAN Volume Controller) / lsnodecanisterhw (Storwize

V7000)
The lsnodehw / lsnodecanisterhw command displays the configured and actual hardware configuration
of nodes in the clustered system.

Syntax
2

lsnodehw | lsnodecanisterhw

-delim delimiter object_id
object_name

Chapter 17. Information commands 295

 Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
2 object_id | object_name
2 (Optional) Specifies the object name or ID.

Description

Table 40 provides the possible values that are applicable to the attributes that are displayed as data in the
output views.
Table 40. lsnodehw attribute values
Attribute Value
id The node or node canister unique ID.
name The node or node canister name.
status The node or node canister status.
IO_group_id The input/output (I/O) group ID.
IO_group_name The I/O group name.
hardware The hardware model.
actual_different Indicates if the node or node canister hardware is different from the configured
hardware.
actual_valid Indicates if the node or node canister hardware is valid.
memory_configured The configured amount of memory (in GB).
member_actual The currently installed amount of memory (in GB).
memory_valid Indicates if the actual memory is a valid configuration.
cpu_count The maximum number of CPUs for the node.
cpu_socket The ID of socket the CPU fields refer to.
cpu_configured The configured CPU for this socket.
cpu_actual The currently installed CPU in this socket.
cpu_valid Indicates if the currently installed CPU is a valid configuration.
adapter_count The maximum number of adapters for the node (differs by node type).
adapter_location The location of this adapter.
adapter_configured The configured adapter for this location.
adapter_actual The currently installed adapter for this location.
adapter_valid Indicates if the adapter in this location is valid.
2 ports_different Indicates if the current hardware is able to provide more I/O ports? The values are
2 yes and no.

A lsnodehw invocation example

lsnodehw -delim , 1

296 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The resulting lsnodehw output
id,1
name,hlcn114289
status,online
IO_group_id,0
IO_group_name,io_grp0
hardware,8A4
actual_different,yes
actual_valid,no
memory_configured,8
memory_actual,8
memory_valid,yes
cpu_count,2
cpu_socket,1
cpu_configured,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_actual,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_valid,yes
cpu_socket,2
cpu_configured,none
cpu_actual,none
cpu_valid,yes
adapter_count,4
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,1
adapter_configured,Four port 8Gb/s FC adapter card
adapter_actual,Four port 8Gb/s FC adapter card
adapter_valid,yes
adapter_location,2
adapter_configured,none
adapter_actual,Four port 8Gb/s FC adapter card
adapter_valid,no
2 ports_different yes

A lsnodecanisterhw invocation example

lsnodecanisterhw -delim , 1

The resulting lsnodecanisterhw output

id,1
name,hlcn114289
status,online
IO_group_id,0
IO_group_name,io_grp0
hardware,112
...

lsnodestats (SAN Volume Controller) / lsnodecanisterstats (Storwize

V7000)
The lsnodestats / lsnodecanisterstatscommand displays the most recent values of statistics for all
nodes or node canisters, and displays all statistics for a particular node or node canister. Also, this
command can display a history of values for a given subset of available statistics.

Chapter 17. Information commands 297

 Syntax


lsnodestats

lsnodecanisterstats -delim delimiter

2


-history stat_list
object_id
object_name

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view. (For example, the spacing of columns does not occur.) In a detailed
view, the data is separated from its header by the specified delimiter.
-history stat_list
e (Optional) Provides a table of statistical values for the specified node. The stat_list is a
e colon-delimited list of one or more statistical values. A table is generated for each entry in the
e stat_list.

e Remember: If -history is specified, a node ID or name must be specified as well.

2 object_id | object_name
2 (Optional) Specifies the object name or ID.

Description

This command returns a concise list or a detailed view of nodes or node canisters that are part of the
clustered system. Table 41 provides the possible values that are applicable to the attributes that are
displayed as data in the output views.
Table 41. lsnodestats or lsnodecanister attribute values
Attribute Value
node_id The ID of the node or node canister.
node_name The name of the node or node canister.
stat_current The current value of the statistic field.
e stat_list The system history of the reported statistics. The stat_list can contain multiple items
e separated by colons.
stat_name The name of the statistic field. See Table 42 on page 302 for descriptions of available
statistics.
stat_peak The peak value of the statistic field in the last five minutes.
stat_peak_time The time that the peak occurred.
sample_time The time of the sample occurrence.
stat_value The statistical value at the epoch interval.

Note: Filtering is supported on the nodecanister_id, nodecanister_name, and stat_name fields using only the
concise view.

298 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e Output from the lsnodestats example
e node_id node_name stat_name stat_current stat_peak stat_peak_time
e 1 node1 cpu_pc 5 9 111123105330
e 1 node1 fc_mb 218 238 111123105440
e 1 node1 fc_io 1122 1501 111123105435
e 1 node1 sas_mb 282 402 111123105335
e 1 node1 sas_io 3129 4427 111123105335
e 1 node1 iscsi_mb 0 0 111123105825
e 1 node1 iscsi_io 0 0 111123105825
e 1 node1 write_cache_pc 0 0 111123105825
e 1 node1 total_cache_pc 0 0 111123105825
e 1 node1 vdisk_mb 218 238 111123105440
e 1 node1 vdisk_io 1076 1452 111123105435
e 1 node1 vdisk_ms 52 60 111123105605
e 1 node1 mdisk_mb 218 238 111123105435
e 1 node1 mdisk_io 1874 2386 111123105435
e 1 node1 mdisk_ms 15 33 111123105605
e 1 node1 drive_mb 281 401 111123105335
e 1 node1 drive_io 3130 4060 111123105335
e 1 node1 drive_ms 13 27 111123105605
e 1 node1 vdisk_r_mb 134 157 111123105440
e 1 node1 vdisk_r_io 561 885 111123105430
e 1 node1 vdisk_r_ms 37 45 111123105605
e 1 node1 vdisk_w_mb 84 89 111123105700
e 1 node1 vdisk_w_io 515 587 111123105625
e 1 node1 vdisk_w_ms 67 84 111123105330
e 1 node1 mdisk_r_mb 133 155 111123105510
e 1 node1 mdisk_r_io 1337 1789 111123105435
e 1 node1 mdisk_r_ms 15 33 111123105605
e 1 node1 mdisk_w_mb 84 89 111123105700
e 1 node1 mdisk_w_io 536 611 111123105625
e 1 node1 mdisk_w_ms 17 32 111123105605
e 1 node1 drive_r_mb 151 295 111123105335
e 1 node1 drive_r_io 1700 2904 111123105335
e 1 node1 drive_r_ms 14 30 111123105605
e 1 node1 drive_w_mb 130 137 111123105700
e 1 node1 drive_w_io 1429 1586 111123105625
e 1 node1 drive_w_ms 12 22 111123105605
e 2 node2 cpu_pc 6 7 111123105624
e 2 node2 fc_mb 132 145 111123105724
e 2 node2 fc_io 1519 1944 111123105739
e 2 node2 sas_mb 189 308 111123105619
e 2 node2 sas_io 2737 4099 111123105614
e 2 node2 iscsi_mb 0 0 111123105824
e 2 node2 iscsi_io 0 0 111123105824
e 2 node2 write_cache_pc 0 0 111123105824
e 2 node2 total_cache_pc 0 0 111123105824
e 2 node2 vdisk_mb 132 145 111123105724
e 2 node2 vdisk_io 1459 1892 111123105739
e 2 node2 vdisk_ms 47 81 111123105514
e 2 node2 mdisk_mb 132 145 111123105724
e 2 node2 mdisk_io 1635 2066 111123105739
e 2 node2 mdisk_ms 8 18 111123105619
e 2 node2 drive_mb 189 310 111123105619
e 2 node2 drive_io 2735 3750 111123105619
e 2 node2 drive_ms 9 20 111123105604
e 2 node2 vdisk_r_mb 20 21 111123105809
e 2 node2 vdisk_r_io 796 1180 111123105739
e 2 node2 vdisk_r_ms 2 8 111123105529
e 2 node2 vdisk_w_mb 112 134 111123105349
e 2 node2 vdisk_w_io 662 805 111123105504
e 2 node2 vdisk_w_ms 100 104 111123105624
e 2 node2 mdisk_r_mb 20 21 111123105809
e 2 node2 mdisk_r_io 951 1330 111123105739
e 2 node2 mdisk_r_ms 2 7 111123105529
e 2 node2 mdisk_w_mb 112 134 111123105349
e 2 node2 mdisk_w_io 684 834 111123105504

Chapter 17. Information commands 299

e 2 node2 mdisk_w_ms 16 36 111123105619
e 2 node2 drive_r_mb 17 132 111123105619
e 2 node2 drive_r_io 899 1920 111123105619
e 2 node2 drive_r_ms 6 12 111123105344
e 2 node2 drive_w_mb 171 206 111123105504
e 2 node2 drive_w_io 1837 2230 111123105504
e 2 node2 drive_w_ms 11 26 111123105619

e A node-based, filtered invocation example for lsnodestats

e lsnodestats -filtervalue stat_name=sas_io:stat_name=sas_mb node1

e Output from the node-based filtered invocation example

e node_id node_name stat_name stat_current stat_peak stat_peak_time
e 1 node1 sas_mb 212 421 111123105840
e 1 node1 sas_io 2477 4184 111123105840

e Historical view that can list multiple statistics and requires a node-based invocation
e lsnodestats -history cpu_pc:fc_mb:sas_mb node1

e Output example for the historical invocation

e node_id node_name sample_time stat_name stat_value
e 2 node2 111123105839 cpu_pc 6
e 2 node2 111123105844 cpu_pc 5
e 2 node2 111123105849 cpu_pc 5
e 2 node2 111123105854 cpu_pc 5
e 2 node2 111123105859 cpu_pc 6
e 2 node2 111123105904 cpu_pc 5
e 2 node2 111123105909 cpu_pc 5
e 2 node2 111123105914 cpu_pc 5
e 2 node2 111123105919 cpu_pc 5
e 2 node2 111123105924 cpu_pc 5
e 2 node2 111123105929 cpu_pc 5
e 2 node2 111123105934 cpu_pc 5
e 2 node2 111123105839 fc_mb 128
e 2 node2 111123105844 fc_mb 126
e 2 node2 111123105849 fc_mb 123
e 2 node2 111123105854 fc_mb 142
e 2 node2 111123105859 fc_mb 119
e 2 node2 111123105904 fc_mb 131
e 2 node2 111123105909 fc_mb 157
e 2 node2 111123105914 fc_mb 177
e 2 node2 111123105919 fc_mb 182
e 2 node2 111123105924 fc_mb 182
e 2 node2 111123105929 fc_mb 155
e 2 node2 111123105934 fc_mb 177
e 2 node2 111123105839 sas_mb 191
e 2 node2 111123105844 sas_mb 191
e 2 node2 111123105849 sas_mb 185
e 2 node2 111123105854 sas_mb 216
e 2 node2 111123105859 sas_mb 181
e 2 node2 111123105904 sas_mb 198
e 2 node2 111123105909 sas_mb 228
e 2 node2 111123105914 sas_mb 243
e 2 node2 111123105919 sas_mb 251
e 2 node2 111123105924 sas_mb 248
e 2 node2 111123105929 sas_mb 217
e 2 node2 111123105934 sas_mb 242

e Output from the lsnodecanisterstats example

e node_id node_name stat_name stat_current stat_peak stat_peak_time
e 1 node1 cpu_pc 5 9 111123105330
e 1 node1 fc_mb 218 238 111123105440
e 1 node1 fc_io 1122 1501 111123105435

300 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e 1 node1 sas_mb 282 402 111123105335
e 1 node1 sas_io 3129 4427 111123105335
e 1 node1 iscsi_mb 0 0 111123105825
e 1 node1 iscsi_io 0 0 111123105825
e 1 node1 write_cache_pc 0 0 111123105825
e 1 node1 total_cache_pc 0 0 111123105825
e 1 node1 vdisk_mb 218 238 111123105440
e 1 node1 vdisk_io 1076 1452 111123105435
e 1 node1 vdisk_ms 52 60 111123105605
e 1 node1 mdisk_mb 218 238 111123105435
e 1 node1 mdisk_io 1874 2386 111123105435
e 1 node1 mdisk_ms 15 33 111123105605
e 1 node1 drive_mb 281 401 111123105335
e 1 node1 drive_io 3130 4060 111123105335
e 1 node1 drive_ms 13 27 111123105605
e 1 node1 vdisk_r_mb 134 157 111123105440
e 1 node1 vdisk_r_io 561 885 111123105430
e 1 node1 vdisk_r_ms 37 45 111123105605
e 1 node1 vdisk_w_mb 84 89 111123105700
e 1 node1 vdisk_w_io 515 587 111123105625
e 1 node1 vdisk_w_ms 67 84 111123105330
e 1 node1 mdisk_r_mb 133 155 111123105510
e 1 node1 mdisk_r_io 1337 1789 111123105435
e 1 node1 mdisk_r_ms 15 33 111123105605
e 1 node1 mdisk_w_mb 84 89 111123105700
e 1 node1 mdisk_w_io 536 611 111123105625
e 1 node1 mdisk_w_ms 17 32 111123105605
e 1 node1 drive_r_mb 151 295 111123105335
e 1 node1 drive_r_io 1700 2904 111123105335
e 1 node1 drive_r_ms 14 30 111123105605
e 1 node1 drive_w_mb 130 137 111123105700
e 1 node1 drive_w_io 1429 1586 111123105625
e 1 node1 drive_w_ms 12 22 111123105605
e 2 node2 cpu_pc 6 7 111123105624
e 2 node2 fc_mb 132 145 111123105724
e 2 node2 fc_io 1519 1944 111123105739
e 2 node2 sas_mb 189 308 111123105619
e 2 node2 sas_io 2737 4099 111123105614
e 2 node2 iscsi_mb 0 0 111123105824
e 2 node2 iscsi_io 0 0 111123105824
e 2 node2 write_cache_pc 0 0 111123105824
e 2 node2 total_cache_pc 0 0 111123105824
e 2 node2 vdisk_mb 132 145 111123105724
e 2 node2 vdisk_io 1459 1892 111123105739
e 2 node2 vdisk_ms 47 81 111123105514
e 2 node2 mdisk_mb 132 145 111123105724
e 2 node2 mdisk_io 1635 2066 111123105739
e 2 node2 mdisk_ms 8 18 111123105619
e 2 node2 drive_mb 189 310 111123105619
e 2 node2 drive_io 2735 3750 111123105619
e 2 node2 drive_ms 9 20 111123105604
e 2 node2 vdisk_r_mb 20 21 111123105809
e 2 node2 vdisk_r_io 796 1180 111123105739
e 2 node2 vdisk_r_ms 2 8 111123105529
e 2 node2 vdisk_w_mb 112 134 111123105349
e 2 node2 vdisk_w_io 662 805 111123105504
e 2 node2 vdisk_w_ms 100 104 111123105624
e 2 node2 mdisk_r_mb 20 21 111123105809
e 2 node2 mdisk_r_io 951 1330 111123105739
e 2 node2 mdisk_r_ms 2 7 111123105529
e 2 node2 mdisk_w_mb 112 134 111123105349
e 2 node2 mdisk_w_io 684 834 111123105504
e 2 node2 mdisk_w_ms 16 36 111123105619
e 2 node2 drive_r_mb 17 132 111123105619
e 2 node2 drive_r_io 899 1920 111123105619
e 2 node2 drive_r_ms 6 12 111123105344

Chapter 17. Information commands 301

e 2 node2 drive_w_mb 171 206 111123105504
e 2 node2 drive_w_io 1837 2230 111123105504
e 2 node2 drive_w_ms 11 26 111123105619

e A node-based, filtered invocation example for lsnodecanisterstats

e lsnodecanisterstats -filtervalue stat_name=sas_io:stat_name=sas_mb node1

e Output from the node-based filtered invocation example

e node_id node_name stat_name stat_current stat_peak stat_peak_time
e 1 node1 sas_mb 212 421 111123105840
e 1 node1 sas_io 2477 4184 111123105840

e Historical view that can list multiple statistics and requires a node-based invocation
e lsnodecanisterstats -history cpu_pc:fc_mb:sas_mb node1

e Output example for the historical invocation

e node_id node_name sample_time stat_name stat_value
e 2 node2 111123105839 cpu_pc 6
e 2 node2 111123105844 cpu_pc 5
e 2 node2 111123105849 cpu_pc 5
e 2 node2 111123105854 cpu_pc 5
e 2 node2 111123105859 cpu_pc 6
e 2 node2 111123105904 cpu_pc 5
e 2 node2 111123105909 cpu_pc 5
e 2 node2 111123105914 cpu_pc 5
e 2 node2 111123105919 cpu_pc 5
e 2 node2 111123105924 cpu_pc 5
e 2 node2 111123105929 cpu_pc 5
e 2 node2 111123105934 cpu_pc 5
e 2 node2 111123105839 fc_mb 128
e 2 node2 111123105844 fc_mb 126
e 2 node2 111123105849 fc_mb 123
e 2 node2 111123105854 fc_mb 142
e 2 node2 111123105859 fc_mb 119
e 2 node2 111123105904 fc_mb 131
e 2 node2 111123105909 fc_mb 157
e 2 node2 111123105914 fc_mb 177
e 2 node2 111123105919 fc_mb 182
e 2 node2 111123105924 fc_mb 182
e 2 node2 111123105929 fc_mb 155
e 2 node2 111123105934 fc_mb 177
e 2 node2 111123105839 sas_mb 191
e 2 node2 111123105844 sas_mb 191
e 2 node2 111123105849 sas_mb 185
e 2 node2 111123105854 sas_mb 216
e 2 node2 111123105859 sas_mb 181
e 2 node2 111123105904 sas_mb 198
e 2 node2 111123105909 sas_mb 228
e 2 node2 111123105914 sas_mb 243
e 2 node2 111123105919 sas_mb 251
e 2 node2 111123105924 sas_mb 248
e 2 node2 111123105929 sas_mb 217
e 2 node2 111123105934 sas_mb 242

The following table provides the possible values that are applicable to the values that are displayed for
stat_name attribute.
Table 42. Stat_name field values
Value Description
cpu_pc The total percentage of CPU utilization for the system.

302 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 42. Stat_name field values (continued)
Value Description
fc_mb Displays the total number of megabytes transferred per second for Fibre Channel
traffic on the system. This value includes host I/O and any bandwidth that is used
for communication within the system.
fc_io Displays the total input/output (I/O) operations transferred per seconds for Fibre
Channel traffic on the system. This value includes host I/O and any bandwidth that
is used for communication within the system.
sas_mb Displays the total number of megabytes transferred per second for serial-attached
SCSI (SAS) traffic on the system. This value includes host I/O and bandwidth that is
used for background RAID activity.
sas_io Displays the total I/O operations transferred per second for SAS traffic on the
system. This value includes host I/O and bandwidth that is used for background
RAID activity.
iscsi_mb Displays the total number of megabytes transferred per second for iSCSI traffic on the
system.
iscsi_io Displays the total I/O operations transferred per second for iSCSI traffic on the
system.
write_cache_pc Displays the percentage of the write cache usage for the node.
total_cache_pc Displays the total percentage for both the write and read cache usage for the node.
vdisk_mb Displays the average number of megabytes transferred per second for read and write
operations to volumes during the sample period.
vdisk_io Displays the average amount of I/O operations transferred per second for read and
write operations to volumes during the sample period.
vdisk_ms Displays the average amount of time in milliseconds that the system takes to respond
to read and write requests to volumes over the sample period.
mdisk_mb Displays the average number of megabytes transferred per second for read and write
operations to MDisks during the sample period.
mdisk_io Displays the average amount of I/O operations transferred per second for read and
write operations to MDisks during the sample period.
mdisk_ms Displays the average amount of time in milliseconds that the system takes to respond
to read and write requests to MDisks over the sample period.
drive_mb Displays the average number of megabytes transferred per second for read and write
operations to drives during the sample period
drive_io Displays the average amount of I/O operations transferred per second for read and
write operations to drives during the sample period.
drive_ms Displays the average amount of time in milliseconds that the system takes to respond
to read and write requests to drives over the sample period.
vdisk_w_mb Displays the average number of megabytes transferred per second for read and write
operations to volumes during the sample period.
vdisk_w_io Displays the average amount of I/O operations transferred per second for write
operations to volumes during the sample period.
vdisk_w_ms Displays the average amount of time in milliseconds that the system takes to respond
to write requests to volumes over the sample period.
mdisk_w_mb Displays the average number of megabytes transferred per second for write
operations to MDisks during the sample period.
mdisk_w_io Displays the average amount of I/O operations transferred per second for write
operations to MDisks during the sample period.
mdisk_w_ms Displays the average amount of time in milliseconds that the system takes to respond
to write requests to MDisks over the sample period.

Chapter 17. Information commands 303

 Table 42. Stat_name field values (continued)
Value Description
drive_w_mb Displays the average number of megabytes transferred per second for write
operations to drives during the sample period
drive_w_io Displays the average amount of I/O operations transferred per second for write
operations to drives during the sample period.
drive_w_ms Displays the average amount of time in milliseconds that the system takes to respond
write requests to drives over the sample period.
vdisk_r_mb Displays the average number of megabytes transferred per second for read operations
to volumes during the sample period.
vdisk_r_io Displays the average amount of I/O operations transferred per second for read
operations to volumes during the sample period.
vdisk_r_ms Displays the average amount of time in milliseconds that the system takes to respond
to read requests to volumes over the sample period.
mdisk_r_mb Displays the average number of megabytes transferred per second for read operations
to MDisks during the sample period.
mdisk_r_io Displays the average amount of I/O operations transferred per second for read
operations to MDisks during the sample period.
mdisk_r_ms Displays the average amount of time in milliseconds that the system takes to respond
to read requests to MDisks over the sample period.
drive_r_mb Displays the average number of megabytes transferred per second for read operations
to drives during the sample period
drive_r_io Displays the average amount of I/O operations transferred per second for read
operations to drives during the sample period.
drive_r_ms Displays the average amount of time in milliseconds that the system takes to respond
to read requests to drives over the sample period.

lsnodevpd (SAN Volume Controller) / lsnodecanistervpd (Storwize

V7000)
The lsnodevpd / lsnodecanistervpd command displays the vital product data (VPD) for each node.

Syntax


lsnodevpd | lsnodecanister

-nohdr -delim delimiter

2
object_id

object_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each

304 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. Using the -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
2 object_id | object_name
2 (Required) Specifies the object name or ID.

Description

This command displays the VPD for the specified node or node canister. Each field is reported on a new
line. All fields are strings. The VPD is split into sections. Each section has a section heading. The number
of fields in that section follows each heading. Each section is separated by an empty line.

For example:

section name:3 fields

field1:value
field2:value
field3:value

new section:x fields

...

Some sections contain information about multiple objects of that type. Each object within the section is
separated by an empty line.

For example:

section name:4 fields

object1 field1:value
object1 field2:value

object2 field1:value
object2 field2:value

new section: x fields

...

Note: For 8F4, 8G4, and 8A4 nodes, the VPD displays the device serial number of the Fibre Channel card
as N/A.

An invocation example
lsnodevpd 1

The resulting output

id 1

system board: 21 fields

part_number 43V7072
system_serial_number KD1438A
number_of_processors 4
number_of_memory_modules 6
number_of_fans 6
number_of_FC_cards 1
3 number_of_Ethernet cards 3
Chapter 17. Information commands 305
number_of_scsi/ide_devices 2
BIOS_manufacturer IBM Corp.
BIOS_version -[D6E124AUS-1.01]-
BIOS_release_date 04/30/2009
system_manufacturer IBM
system_product IBM System x -[2145CF8]-
version 00
planar_manufacturer IBM
planar_product 49Y6498
planar_version (none)
power_supply_part_number 39Y7201
CMOS_battery_part_number 33F8354
frame_assembly_part_number
ethernet_cable_part_number
service_processor_firmware 1.01

processor: 6 fields
processor_location Processor 1
manufacturer Intel(R) Corporation
version Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
speed 2400
status Enabled
CPU_part_number 46D1266

memory module: 96 fields

part_number 44T1493
device_location DIMM01
bank_location BANK01
size (MB) No Module Installed
manufacturer Not Specified
serial_number Not Specified

part_number 44T1493
device_location DIMM02
bank_location BANK02
size (MB) 4096
manufacturer Samsung
serial_number 99062848

part_number 44T1493
device_location DIMM03
bank_location BANK03
size (MB) 4096
manufacturer Samsung
serial_number C7062848
...

fan: 12 fields
part_number 43V6929
location location1

part_number 43V6929
location location2

part_number 43V6929
location location3
...

Adapter card: 18 fields

card_type FC card
part_number 31P1337
port_numbers 1 2 3 4
location 0
device_serial_number 11S31P1333YM10MY96A206
manufacturer IBM
device QE8
card_revision 2

306 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 chip_revision 2.0

card_type SAS card

part_number 44E8690
port_numbers 1 2 3 4
location 0
device_serial_number 11S31P1299YM10MY948004
manufacturer IBMHUR
device Capri-PMC8001
card_revision Y
chip_revision 1.1

Fibre Channel
SFP: 48 fields
part_number 17P9211
manufacturer JDSU
device PLRXPLVCSH4921
serial_number C915EB06V
supported_speeds 2,4,8
connector_type LC
transmitter_type SN
wavelength 850
max_distance_by_cable_type OM1:20,OM2:50,OM3:150
hw_revision 1
port_number 1
WWPN 500507680140350d
...

device: 15 fields
part_number 31P1339
bus USB
device 0
model IBM USB Endeavour
revision 1.0
serial_number NA
approx_capacity 0
hw_revision 0

part_number 42D0673
bus scsi
device 0
model ST973452SS
revision B623
serial_number 3TA00BZ20109B623
approx_capacity 68

software: 8 fields
code_level 5.1.0.0 (build 16.1.0906240000)
1 object_name_model
ethernet_status 1

ethernet_status 0
WWNN 0x500507680100350d
id 1
MAC_address 00 21 5e 09 09 08
MAC_address 00 21 5e 09 09 0a

front panel assembly: 3 fields

part_number 31P1339
front_panel_id 161040
front_panel_locale en_US

UPS: 10 fields
electronics_assembly_part_number 64P8326
battery_part_number 31P0710
UPS_assembly_part_number 64P8326
input_power_cable_part_number CountryDependent

Chapter 17. Information commands 307

 UPS_serial_number 100084O050
UPS_type 2145UPS 1U
UPS_internal_part_number P31P0875
UPS_unique_id 0x20400002047c0140
UPS_main_firmware 1.02
UPS_comms_firmware 1.20

...

An invocation example for lsnodecanistervpd

lsnodecanistervpd 1

The resulting output for lsnodecanistervpd

id 1

system board: 21 fields

part_number 43V7072
system_serial_number KD1438A
number_of_processors 4
number_of_memory_modules 6
number_of_fans 6
number_of_FC_cards 1
3 number_of_Ethernet cards 3
number_of_scsi/ide_devices 2
BIOS_manufacturer IBM Corp.
BIOS_version -[D6E124AUS-1.01]-
BIOS_release_date 04/30/2009
system_manufacturer IBM
system_product IBM System x -[2145CF8]-
version 00
planar_manufacturer IBM
planar_product 49Y6498
planar_version (none)
power_supply_part_number 39Y7201
CMOS_battery_part_number 33F8354
frame_assembly_part_number
ethernet_cable_part_number
service_processor_firmware 1.01

processor: 6 fields
processor_location Processor 1
manufacturer Intel(R) Corporation
version Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
speed 2400
status Enabled
CPU_part_number 46D1266

memory module: 96 fields

part_number 44T1493
device_location DIMM01
bank_location BANK01
size (MB) No Module Installed
manufacturer Not Specified
serial_number Not Specified

part_number 44T1493
device_location DIMM02
bank_location BANK02
size (MB) 4096
manufacturer Samsung
serial_number 99062848

part_number 44T1493
device_location DIMM03
bank_location BANK03
size (MB) 4096

308 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
manufacturer Samsung
serial_number C7062848
...

fan: 12 fields
part_number 43V6929
location location1

part_number 43V6929
location location2

part_number 43V6929
location location3
...

Adapter card: 18 fields

card_type FC card
part_number 31P1337
port_numbers 1 2 3 4
location 0
device_serial_number 11S31P1333YM10MY96A206
manufacturer IBM
device QE8
card_revision 2
chip_revision 2.0

card_type SAS card

part_number 44E8690
port_numbers 1 2 3 4
location 0
device_serial_number 11S31P1299YM10MY948004
manufacturer IBMHUR
device Capri-PMC8001
card_revision Y
chip_revision 1.1

Fibre Channel SFP: 48 fields

part_number 17P9211
manufacturer JDSU
device PLRXPLVCSH4921
serial_number C915EB06V
supported_speeds 2,4,8
connector_type LC
transmitter_type SN
wavelength 850
max_distance_by_cable_type OM1:20,OM2:50,OM3:150
hw_revision 1
port_number 1
WWPN 500507680140350d
...

device: 15 fields
part_number 31P1339
bus USB
device 0
model IBM USB Endeavour
revision 1.0
serial_number NA
approx_capacity 0
hw_revision 0

part_number 42D0673
bus scsi
device 0
model ST973452SS
revision B623
serial_number 3TA00BZ20109B623

Chapter 17. Information commands 309

approx_capacity 68

software: 8 fields
code_level 5.1.0.0 (build 16.1.0906240000)
nodecanister_name nodecanister1
ethernet_status 1

ethernet_status 0
WWNN 0x500507680100350d
id 1
MAC_address 00 21 5e 09 09 08
MAC_address 00 21 5e 09 09 0a

front panel assembly: 3 fields

part_number 31P1339
front_panel_id 161040
front_panel_locale en_US

UPS: 10 fields
electronics_assembly_part_number 64P8326
battery_part_number 31P0710
UPS_assembly_part_number 64P8326
input_power_cable_part_number CountryDependent
UPS_serial_number 100084O050
UPS_type 2145UPS 1U
UPS_internal_part_number P31P0875
UPS_unique_id 0x20400002047c0140
UPS_main_firmware 1.02
UPS_comms_firmware 1.20

...

lspartnership
The lspartnership command provides a concise or detailed view of the current clustered systems that
are associated with the local system.

Syntax


lspartnership system_id | system_name


Parameters
system_id | system_name
(Optional) Specifies the name or ID of a clustered system. Using this parameter displays the detailed
view of the specific partner system, and any value specified by the -filtervalue (which filters a view
that is based on specific attribute values that relate to each object type) parameter is ignored. When
specifying system_id or system_name parameter, the concise view of all clustered systems that match
the filtering requirements that are specified by the -filtervalue parameter are displayed.

Description

Table 43 described attribute values.

Table 43. lspartnership attribute values
Attribute Value
ID Clustered system ID
name Clustered system name
location Clustered system location

310 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 43. lspartnership attribute values (continued)
Attribute Value
partnership Current state of the partnership; not applicable for the local clustered system and is
blank.
bandwidth Current bandwidth available on the (clustered) intersystem link for background copy
in megabytes per second (MBps); not applicable for the local clustered system and is
blank.

A concise invocation example

lspartnership

The concise resulting output

id name location partnership bandwidth
000002006BC0A0D4 system-1 local
000002006200A0EA system-2 remote partially_configured_local 20

A detailed invocation example

lspartnership cluster-2

The detailed resulting output

id 000002006200A0EA
name system-2
location remote
partnership partially_configured_local
bandwidth 20
code_level 6.2.0.0 (build 35.7.1105071000)
console_IP 9.180.28.63:443
gm_link_tolerance 300
gm_inter_system_delay_simulation 0
gm_intra_system_delay_simulation 0
relationship_bandwidth_limit 25
gm_max_host_delay 5

lspartnershipcandidate
The lspartnershipcandidate command lists the clustered systems that are available for setting up a
partnership with the local system. This is a prerequisite for creating inter-system Metro or Global Mirror
relationships.

Syntax


lspartnershipcandidate

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of

Chapter 17. Information commands 311

 data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command displays a list of systems that are available as candidate partner systems to form a Metro
Mirror or Global Mirror partnership between two systems.

Output from the command shows the system ID, name, and configured status of the remote candidate
system. The remote candidate system forms a partnership with the local system when you use the
mkpartnership command. The remote system shows the partnership status as
partially_configured_local_stopped or partially_configured_local when you use the lssystem
command. The lspartnershipcandidate command displays the configured status of those remote systems
that have formed a partnership with the local system.

An invocation example
lspartnershipcandidate

The resulting output

id configured system_name
0000010034E0F430 no ldsystem26

lsportip
Use the lsportip command to list the Internet Small Computer Systems Interface (iSCSI) Internet
Protocol (IP) addresses assigned for each port on each node in the clustered system.

Syntax


lsportip

-filtervalue attrib=value -filtervalue? -nohdr


-mtu mtu -delim delimiter ethernet_port_id
defaultmtu

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard, which must be the first or last character in
the string.
v When using a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lsportip -filtervalue "node_name=md*"

312 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -filtervalue?
(Optional) Displays the valid filter attributes. The following filter attributes for the lsportip
command are valid:
v id
v node_id
v node_name
v state
v failover
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
ethernet_port_id
(Optional) Specifies the ID of an ethernet port (1, 2, 3 or 4). If omitted, a concise view is displayed for
all ports. When you use this parameter, the detailed view of the specified port is returned and any
value that is specified by the -filtervalue parameter is ignored. If you do not use the
ethernet_port_id parameter, the concise view displays all ports matching the filtering requirements that
are specified by the -filtervalue parameter.
-mtu mtu | defaultmtu
(Optional) Specifies the maximum transmission unit (MTU). The default is 1500, with a maximum of
9000. An MTU of 9000 enables you to save central processing unit (CPU) utilization for packets of 4 K
and over in size. The increased MTU provides you with improved iSCSI performance.

Description

This command lists all port IP addresses for each node in the clustered system. The concise view displays
two rows of output for each ethernet port. Each node has two ethernet ports.

Use the lsportip command with the optional ethernet_port_id parameter to display a detailed view of
the specified port.

Both output rows for a port show the MAC address of that port if it can be determined. If the node and
the ethernet link are online, the rows also show the speed and duplex state of the link. The duplex field
can have values of Half or Full, or it is blank if the node is offline.

The first row for each port shows any Internet Small Computer System Interface, an Internet Protocol
(iSCSI) addresses that have been configured for that port and are not failed over to a different node. The
failover field on this row is set to no. The second row for each port shows any iSCSI addresses that have
been configured for the partner node, or for the local node with failover, and that are active on the port.
The failover field on this row is set to yes.

Chapter 17. Information commands 313

 The state field is set to unconfigured if there are no iSCSI addresses configured on the port. The state
field is set to offline if there are configured addresses but the link is down, and online if the link is up.
Any offline rows indicate a potential problem.

1 This command enables you to view information about system port status. The following table shows the
1 possible outputs:
1 Table 44. lsportip output
1 Attribute Description
1 unconfigured No iSCSI address configured; hardware might or might not exist.
1 offline iSCSI address configured but port is not up; hardware might or might not exist.
1 online iSCSI address configured and port is up.
e1 management_only Not configurable for input/output (I/O) operations.
1

1 In the examples below (which list different port configuration options) there are two lines for each
1 possible ethernet port, which represent the port and iSCSI behavioral effects. Port indices are assigned
1 statically, and higher indices are used for optional ports. In the example for the two-node or two-node
1 canister system (of 8A4 nodes), port 1 configuration node 1 compels the failover to come online. The
1 partner port on the other node, port 1 on node 3, also comes online. Consequently, this port assumes the
1 IP address if port 1 node 1 fails.

A concise invocation example

lsportip -delim :

The concise resulting output

id:node_id:node_name:IP_address:mask:gateway:IP_address_6:
prefix_6:gateway_6:MAC:duplex:state:speed:failover
1:1:dvt101794:9.71.47.129:255.255.254.0:9.71.46.1::::00:14:
5e:33:51:92:Half:online:100Mb/s:no
1:1:dvt101794:::::::00:14:5e:33:51:92:Half:online:100Mb/s:yes
2:1:dvt101794:::::::00:14:5e:33:51:93::unconfigured::no
2:1:dvt101794:::::::00:14:5e:33:51:93::unconfigured::yes
1:2:dvt101760:9.71.47.83:255.255.254.0:9.71.46.1::::00:14:5e:
7e:2a:58:Half:online:100Mb/s:no
1:2:dvt101760:::::::00:14:5e:7e:2a:58:Half:online:100Mb/s:yes
2:2:dvt101760:::::::00:14:5e:7e:2a:59::unconfigured::no
2:2:dvt101760:::::::00:14:5e:7e:2a:59::unconfigured::yes
1:3:dvt101761:9.71.47.253:255.255.254.0:9.71.46.1::::00:14:5e:
33:50:fa:Half:online:100Mb/s:no
1:3:dvt101761:::::::00:14:5e:33:50:fa:Half:online:100Mb/s:yes
2:3:dvt101761:::::::00:14:5e:33:50:fb::unconfigured::no
2:3:dvt101761:::::::00:14:5e:33:50:fb::unconfigured::yes
1:4:dvt101786:9.71.47.227:255.255.254.0:9.71.46.1::::00:14:5e:
33:50:da:Half:online:100Mb/s:no
1:4:dvt101786:::::::00:14:5e:33:50:da:Half:online:100Mb/s:yes
2:4:dvt101786:::::::00:14:5e:33:50:db::unconfigured::no
2:4:dvt101786:::::::00:14:5e:33:50:db::unconfigured::yes
1:5:destiny35:9.71.47.69:255.255.254.0:9.71.46.1::::00:21:5e:09:
21:44:Full:online:1Gb/s:no
1:5:destiny35:::::::00:21:5e:09:21:44:Full:online:1Gb/s:yes
2:5:destiny35:::::::00:21:5e:09:21:46::unconfigured::no
2:5:destiny35:::::::00:21:5e:09:21:46::unconfigured::yes
1:6:destiny34:9.71.46.239:255.255.254.0:9.71.46.1::::00:21:5e:09:
21:54:Full:online:100Mb/s:no
1:6:destiny34:::::::00:21:5e:09:21:54:Full:online:100Mb/s:yes
2:6:destiny34:::::::00:21:5e:09:21:56::unconfigured::no
2:6:destiny34:::::::00:21:5e:09:21:56::unconfigured::yes

A detailed invocation example

314 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
lsportip 1

The detailed resulting output

lsportip 1
id 1
node_id 1
node_name node1
IP_address 192.168.20.10
mask 255.255.255.0
gateway 192.168.20.1
IP_address_6
prefix_6
gateway_6
MAC 00:1a:64:97:1b:a0
duplex Full
state online
speed 1Gb/s
failover no
mtu 1500

id 1
node_id 1
node_name node1
IP_address
mask
gateway
IP_address_6
prefix_6
gateway_6
MAC 00:1a:64:97:1b:a0
duplex Full
state online
speed 1Gb/s
failover yes
mtu 1500

id 1
node_id 2
node_name node2
IP_address 192.168.20.11
mask 255.255.255.0
gateway 192.168.20.1
IP_address_6
prefix_6
gateway_6
MAC 00:1a:64:97:16:08
duplex Full
state online
speed 1Gb/s
failover no
mtu 1500

id 1
node_id 2
node_name node2
IP_address
mask
gateway
IP_address_6
prefix_6
gateway_6
MAC 00:1a:64:97:16:08
duplex Full

Chapter 17. Information commands 315

 state online
speed 1Gb/s
failover yes
mtu 1500

1 An invocation example displaying only installed ports

1 lsportip

1 The resulting output

1 id node_id node_name IP_address mask gateway IP_address_6 prefix_6 gateway_6 MAC duplex state speed failover
1 1 1 node1 00:21:5e:4d:7b:c9 Full unconfigured 100Mb/s no
1 1 1 node1 00:21:5e:4d:7b:c9 Full unconfigured 100Mb/s yes
1 2 1 node1 00:21:5e:4d:7b:ca unconfigured no
1 2 1 node1 00:21:5e:4d:7b:ca unconfigured yes
1 1 3 node2 00:21:5e:4d:80:e5 Full unconfigured 100Mb/s no
1 1 3 node2 00:21:5e:4d:80:e5 Full unconfigured 100Mb/s yes
1 2 3 node2 00:21:5e:4d:80:e6 unconfigured no
1 2 3 node2 00:21:5e:4d:80:e6 unconfigured yes

3 lsportfc
e Use the lsportfc command to view the status and properties of the system's Fibre Channel I/O ports.

3 Syntax

3

lsportfc

3 -filtervalue attrib=value -filtervalue? -nohdr

3


3 -delim delimiter object_id
3

3 Parameters
3 -filtervalueattrib=value
3 (Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
3 attribute value are returned. If a capacity is specified, the units must also be included.
3 -filtervalue?
3 (Optional) Displays the valid filter attributes. The following filter attributes for the lsportfc
3 command are valid:
3 v type
3 v status
3 v node_id
3 v fc_io_port_id
3 -nohdr
3 (Optional) By default, headings are displayed for each column of data in a concise style view, and for
3 each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
3 headings.

3 Note: If there is no data to be displayed, headings are not displayed.

3 -delimdelimiter
3 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
3 column is set to the maximum possible width of each item of data. In a detailed view, each item of
3 data has its own row, and if the headers are displayed, the data is separated from the header by a
3 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a

316 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
3 one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
3 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
3 view, the data is separated from its header by the specified delimiter.
3 object_id
3 (Optional) Specifies the ID of an object displayed in the view.

3 Description

3 This command enables you to view information about system port status. The following table shows the
3 possible outputs:
3 Table 45. lsportfc output
3 Attribute Description
3 id Specifies a unique value for the object. The value must be a numeric 0 or greater.
3 fc_io_port_id Specifies the FC I/O port ID. The value must be a positive integer.
3 port_id Specifies the platform port ID. The value must be a positive integer.
3 type Specifies the type of platform port. The value can be either fc or ethernet.
3 port_speed Specifies the I/O port speed. The value is XGb. The value is N/A if the port has never
3 been active. If the port is inactive it shows the last-known port speed.
3 node_id Specifies the ID of the node containing the port. The value must be a positive integer.
3 node_name Specifies the name of the node containing the port.
3 WWPN Specifies the I/O port worldwide port name (WWPN). The value must be in
3 16-character hexadecimal format.
3 nportid Specifies the most recent port NPort ID that is assigned by the switch. The value must
3 be in 6-character hexadecimal format, and all zeroes if never active. If the port is
3 inactive the last-known NPort ID is used.
3 status Specifies if the port is connected to a switch. The value is active or inactive.
3 switch_WWPN Specifies the most recent fabric port name given to the FLOG1 reply switch. The value
3 must be in 16-character hexadecimal format, or all zeroes if the port has never been
3 active. If the port is inactive the last-known switch_WWPN value is used.
3 fpma Specifies the Fabric Provided MAC Address (FPMA) assigned to the Fiber Channel over
3 Ethernet (FCoE) VN_PORT port. The value is a formatted 48-bit MAC address. If the
3 switch is connected to an FCF, the value is N/A for ports that are never active. If the
3 port is inactive the last-known FPMA is used.
3 vlan_id Specifies the VLAN ID on which a specific VN port is communicating. The value is a
3 3-hexadecimal character string. The value is N/A for ports that are never active. If the
3 port is inactive the last-known VLAN ID is used.
3 fcf_MAC Specifies the MAC address for the switch attached to the VN port. The value is N/A for
3 ports that are never active. The value is a formatted 48-bit MAC address. If the port is
3 inactive the last known fcf_MAC value is used.
3

3 An invocation example
3 lsportfc

3 The resulting output

3 id fc_io_port_id port_id type port_speed node_id node_name WWPN nportid status
3 0 1 1 fc 8Gb 4 node1 500507680140004A 010E00 active
3 1 2 2 fc 8Gb 4 node1 500507680130004A 010C00 active
3 2 3 3 fc 8Gb 4 node1 500507680110004A 010A00 active
3 3 4 4 fc 8Gb 4 node1 500507680120004A 011B00 active
3 4 5 3 ethernet 10Gb 4 node1 500507680150004A 012201 active
3 5 6 4 ethernet 10Gb 4 node1 500507680160004A 012302 active

Chapter 17. Information commands 317

3 6 1 1 fc 8Gb 6 node3 50050768014051E5 010200 active
3 7 2 2 fc 8Gb 6 node3 50050768013051E5 010600 active
3 8 3 3 fc 8Gb 6 node3 50050768011051E5 010500 active
3 9 4 4 fc 8Gb 6 node3 50050768012051E5 010300 active
3 10 5 3 ethernet 10Gb 6 node3 50050768015051E5 012701 active
3 11 6 4 ethernet 10Gb 6 node3 50050768016051E5 012501 active

3 A detailed invocation example

3 lsportfc 10

3 The resulting output

3 id 10
3 fc_io_port_id 5
3 port_id 3
3 type ethernet
3 port_speed 10Gb
3 node_id 6
3 node_name node3
3 WWPN 50050768015051E5
3 nportid 012701
3 status active
3 switch_WWPN 202700053346FA3D
3 fpma 0E:FC:00:01:27:01
3 vlanid 100
3 fcf_MAC 00:05:73:C2:CA:B4
3
lsquorum
The lsquorum command lists the managed disks (MDisks) or drives that the cluster is currently using to
store quorum data.

Syntax


lsquorum

-nohdr -delim delimiter quorum_index

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The delim parameter overrides this behavior. Valid input for the delim parameter is a one-byte
character. If you enter -delim : on the command line, the colon character (:) separates all items of
data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the
data is separated from its header by the specified character.
quorum_index
(Optional) Specifies the quorum disk or drive by its index number. The number can be either 0, 1, or
2. When you use this parameter, a detailed view of the specified disk or drive is returned. If you do
not specify a disk or drive, then a concise view of all quorum disks or drives is displayed.

318 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

This command displays a concise list or a detailed view of the MDisks or drives that the cluster is
currently using to store quorum data. This information can be used to ensure that the quorum candidates
are on separate storage subsystems.

Note: The object type is either MDisk or drive. SAN Volume Controller uses only MDisks to hold
quorum data. If the quorum object type is a drive, the controller ID and name fields are blank.

A concise invocation example

lsquorum

The concise resulting output

quorum_index status id name controller_id controller_name active object_type
0 online 1 mdisk1 1 controller1 yes mdisk
1 online 2 mdisk2 1 controller1 no mdisk
2 online 33 no drive

A detailed invocation example

lsquorum 1

The detailed resulting output

quorum_index 2
status online
id 33
name
controller_id
controller_name
active no
object_type drive

lsrcconsistgrp
The lsrcconsistgrp command returns a concise list or a detailed view of Metro or Global Mirror
consistency groups visible to the clustered system (system).

Syntax


lsrcconsistgrp

-filtervalue attrib=value -nohdr


-delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller command line interface (CLI):
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard, which must be the first or last character in
the string.

Chapter 17. Information commands 319

 v When using a wildcard, you must enclose the filter entry with double quotation marks (""), as
follows:
lsrcconsistgrp -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is displayed and any value that is specified by the -filtervalue parameter is
ignored. If you do not specify the object_id | object_name parameter, the concise view of all objects
matching the filtering requirements that is specified by the -filtervalue parameter are displayed.
-filtervalue?
(Optional) Specifies that you want your report to display any or all of the list of valid filter attributes.
The following filter attributes for the lsrcconsistgrp command are valid:
v group_id
v name
v master_cluster_id
v master_cluster_name
v aux_cluster_id
v aux_cluster_name
v primary
v state
v relationship_count
v id
v copy_type
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.

Description

This command returns a concise list or a detailed view of Global or Metro Mirror consistency groups that
are visible to the system.

Table 46 provides possible values for the attributes that are displayed as data in the output views.
Table 46. lsrcconsistgrp command output values
Attribute Value
primary n/a, master, aux

320 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 46. lsrcconsistgrp command output values (continued)
Attribute Value
state consistent_copying, inconsistent_stopped, inconsistent_copying, consistent_stopped,
consistent_synchronized, idling, idling_disconnected, inconsistent_disconnected
consistent_disconnected, empty
cycle_period_seconds The minimum period in seconds between multiple cycles (integer between 60 an 86400;
default is 300).
cycling_mode The type of Global or Metro Mirroring cycling to use: none or multi (default is none)
freeze_time The time in YY/MM/DD/HH/MM format.
status online, primary_offline, secondary_offline,
sync in_sync, out_of_sync
copy_type metro, global, empty_group

Note: The names of the Global or Metro Mirror relationships and consistency groups might be blank if
the relationship or consistency groups are intersystem and the system partnership is disconnected.

The sync attribute has a value of in_sync when the contents are synchronized (identical) between VDisks
(volumes). If write operations take place on either the primary or secondary volume after a consistent
(stopped) or idling state occurs, they will no longer be synchronized.

A concise invocation example

lsrcconsistgrp -delim :

The concise resulting output

id:name:master_cluster_id:master_cluster_name:aux_cluster_id:aux_cluster_name:
primary:state:relationship_count:copy_type

248:jdemo_BA_cons1:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
consistent_stopped:2:global
249:rccstgrp0:0000020061413ABA:clusterA:0000020061413ABA:clusterA::empty:0
:empty_group
250:jdemo_BA_cons2:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
inconsistent_stopped:1:metro
251:BA_cons1:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
consistent_stopped:4:metro
252:AB_cons2:0000020061413ABA:clusterA:0000020060406746:clusterB::empty:0
:empty_group
253:AB_cons1:0000020061413ABA:clusterA:0000020060406746:clusterB:aux:
consistent_stopped:3:global
254:AA_cons2:0000020061413ABA:clusterA:0000020061413ABA:clusterA::empty:0
:empty_group
255:AA_cons1:0000020061413ABA:clusterA:0000020061413ABA:clusterA:master:
consistent_synchronized:2:global

A detailed invocation example

lsrcconsistgrp -delim : 254

The detailed resulting output

id:254
name:rccstgrp0
master_cluster_id:0000010030A007E5
master_cluster_name:clusterA
aux_cluster_id:0000010030A007E5
aux_cluster_name:clusterA
primary:master
state:inconsistent_stopped

Chapter 17. Information commands 321

relationship_count:1
freeze_time:
status:online
sync:in_sync
copy_type:metro
cycle_period_seconds:300
cycling_mode:none
RC_rel_id:2
RC_rel_name:aaa

lsrcrelationship
The lsrcrelationship command returns a concise list or a detailed view of Metro or Global Mirror
relationships visible to the clustered system (system).

Syntax


lsrcrelationship

-filtervalue attrib=value -nohdr


-delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are returned. If a capacity is specified, the units must also be included.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is an asterisk (*).
v The command can contain a maximum of one wildcard, which must be the first or last character in
the string.
v When using a wildcard, you must enclose the filter entry with double quotation marks (" "), as
follows:
lsrcrelationship -filtervalue "name=md*"
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed even if the -nohdr parameter is
specified.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of

322 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 the specific object is returned and any value that is specified by the -filtervalue parameter is ignored.
If you do not specify the object_id | object_name parameter, the concise view of all objects matching
the filtering requirements that are specified by the -filtervalue parameter are displayed.
-filtervalue?
(Optional) Specifies that you want your report to display any or all of the list of valid filter attributes.
The valid filter attributes for the lsrcrelationship command are:
v RC_rel_id
v RC_rel_name
v master_system_id
v master_system_name
v master_vdisk_id
v master_vdisk_name
v aus_system_id
v aux_system_name
v aux_vdisk_id
v aux_vdisk_name
v primary
v consistency_group_id
v consistency_group_name
v state
v progress
v copy_type
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.

Description

This command returns a concise list or a detailed view of Metro or Global Mirror relationships visible to
the system.

Table 47 provides possible values for the attributes that are displayed as data in the output views.
Table 47. lsrcrelationship command attributes and values
Attribute Value
primary n/a, master, aux
state consistent_copying, inconsistent_stopped, inconsistent_copying,
consistent_stopped, consistent_synchronized, idling, idling_disconnected,
inconsistent_disconnected, consistent_disconnected
progress 0-100, n/a
cycle_period_seconds The minimum period in seconds between multiple cycles (integer between 60 and
86400; default is 300).
cycling_mode The type of Global or Metro Mirroring cycling to use:
v none (default)
v multi
freeze time The time in YY/MM/DD/HH/MM format.
status online, primary_offline, secondary_offline,
sync n/a, in_sync, out_of_sync

Chapter 17. Information commands 323

Table 47. lsrcrelationship command attributes and values (continued)
Attribute Value
master_change_vdisk_id The id of the Vdisk (volume) acting as the master change volume for the
relationship (blank if not defined).
Note: The master_change_vdisk_id field identifies the change volume for the
master volume if configured. For an intercluster relationship, if the master
volume is in the other clustered system (system), the master change volume is
also in the other system.
master_change_vdisk_name The name of the volume acting as the master change volume for the relationship
(blank if not defined).
Note: The master_change_vdisk_name field identifies the change volume for the
master volume if configured. For an intersystem relationship, if the master
volume is in the other clustered system (system), the master change volume is
also in the other system.
aux_change_vdisk_id The id of the volume acting as the auxiliary change volume for the relationship
(blank if not defined).
Note: The aux_change_vdisk_id field identifiesthe change volume for the
auxiliary volume, if such a volume has been configured. For an intersystem
relationship, if the auxiliary volume is in the other system, the auxiliary change
volume is also in the other system.
aux_change_vdisk_name The name of the volume acting as the auxiliary change volume for the
relationship (blank if not defined).
Note: The aux_change_vdisk_name field identifies the change volume for the
auxiliary volume if configured. For an intersystem relationship, if the auxiliary
volume is in the other system, the auxiliary change volume is also in the other
system.

Note: The names of the Global or Metro Mirror relationships and consistency groups can be blank if the
relationship or consistency groups are intersystem and the system partnership is disconnected.

The sync attribute has a value of in_sync when the contents are synchronized (identical) between
volumes. If write operations take place on either the primary or secondary volume after a consistent
(stopped) or idling state occurs, they will no longer be synchronized.

A concise and detailed invocation example

lsrcrelationship -delim : -filtervalue name=j*

The concise and detailed resulting output

id:name:master_cluster_id:master_cluster_name:master_vdisk_id:master_vdisk_name:
aux_cluster_id:aux_cluster_name:aux_vdisk_id:
aux_vdisk_name:primary:consistency_group_id:consistency_group_name:state:bg_copy
_priority:progress: copy_type
45:jrel_AB1:0000020061413ABA:clusterA:45:jdisk_B8:0000020060406746:clusterB:38:j
disk_B1:master:::consistent_stopped:50:metro
48:jrel_AB2:0000020061413ABA:clusterA:48:jdisk_A4:0000020060406746:clusterB:41:j
disk_B4:master:::consistent_synchronized:50:metro
49:jrel_BA_1:0000020060406746:clusterB:42:jdisk_B5:0000020061413ABA:clusterA:49:j
disk_A5:master:248:jdemo_BA_cons1:consistent_stopped:50:metro
50:jrel_BA_2:0000020060406746:clusterB:43:jdisk_B6:0000020061413ABA:clusterA:
50:jdisk_A6:master:248:jdemo_BA_cons1:consistent_stopped:50:metro

A detailed invocation example

lsrcrelationship -delim : AB_2

The detailed resulting output

324 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 id:9
name:AB_2
master_cluster_id:0000020061413ABA
master_cluster_name:clusterA
master_vdisk_id:9
master_vdisk_name:stripe9
aux_cluster_id:0000020060406746
aux_cluster_name:clusterB
aux_vdisk_id:9
aux_vdisk_name:stripe9_b
cycle_period_seconds:300
cycling_mode:multi
primary:master
consistency_group_id:
consistency_group_name:
state:consistent_stopped
bg_copy_priority:50
progress:
freeze_time:2006/05/05/08/26/46
status:secondary_offline
sync:in_sync
copy_type:metro

lsrcrelationshipcandidate
The lsrcrelationshipcandidate command lists VDisks (volumes) that are eligible to form Metro or Global
Mirror relationships. You can list eligible volumes that are on the local or remote clustered system
(system).

Syntax


lsrcrelationshipcandidate

-master master_vdisk_id
master_vdisk_name


-aux aux_cluster_id -nohdr -delim delimiter
aux_cluster_name

Parameters
-master master_vdisk_id | master_vdisk_name
(Required) Specifies a particular VDisk (volume) to use as the master volume. The command finds
candidates that match the size of this volume. If you are requesting candidate volumes on the local
system, this command also matches the io_group.
-aux aux_cluster_id | aux_cluster_name
(Required) Specifies a remote system with volume candidates for an intersystem relationship. If you
do not specify this parameter, the candidates on the local system are displayed.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a

Chapter 17. Information commands 325

 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.

Description

This command displays a list of volumes that can be either the master or the auxiliary disk for a Metro or
Global Mirror relationship. Volume IDs and names are displayed.

Note: Volumes that are flash disks are excluded from the view when a FlashCopy map is constructed.

An invocation example
lsrcrelationshipcandidate -delim :

The resulting output

id:vdisk_name
0:vdisk0
4:vdisk4

lsrcrelationshipprogress
You can use the lsrcrelationshipprogress command to display the progress of the background copy of a
Metro Mirror or Global Mirror relationship as a percentage. When the initial background copy process for
a relationship has completed, null is displayed for the progress of that relationship.

Syntax


lsrcrelationshipprogress

-nohdr -delim delimiter

rcrelationship_id

rcrelationship_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
rcrelationship_id | rcrelationship_name
Specifies the object ID or name of the specified type.

326 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

This command displays the progress of the background copy of a Metro Mirror or Global Mirror
relationship as a percentage.

An invocation example
lsrcrelationshipprogress -delim : 0

The resulting output

id:progress
0:58

lsrepairsevdiskcopyprogress
1 The lsrepairsevdiskcopyprogress command lists the repair progress for space-efficient volume copies
1 and displays the progress of a repair operation on a compressed volume copy that is being repaired.

Syntax


lsrepairsevdiskcopyprogress

-nohdr -delim delimiter -copy id


vdisk_name
vdisk_id

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-copy id
(Optional) Lists the repair progress for the specified copy.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

vdisk_name | vdisk_id
(Optional) Specifies the volume name or ID to list repair progress for. You must specify this
parameter last on the command line. If you do not enter this parameter, the command lists progress
for all space-efficient copies in the clustered system.

Description

The lsrepairsevdiskcopyprogress command lists the repair progress for space-efficient copies of the
specified volume. If you do not specify a volume, the command lists the repair progress for all
space-efficient copies in the clustered system.

Chapter 17. Information commands 327

 Note: Only run this command after running the repairsevdiskcopy command, which you must only run
as required by the fix procedures or by IBM support.

1 The command returns values for the following volume copy attributes:
1 progress
1 Specifies the active task.
1 compressed_repairing
1 Initiates repair for compressed volume copies.
1 task Specifies the task completion percentage, and is always 0 when task is compressed_repairing
1 estimated_completion_time
1 Specifies the expected duration of the task in the format YYMMDDHHMMSS (or blank if the
1 estimated completion time is unknown).

An invocation example
lsrepairsevdiskcopyprogress –delim :

The resulting output

id:name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:repairing:50:070301120000
0:vdisk0:1:repairing:51:070301120000
1:vdisk1:0:repairing:32:070301153500

An invocation example
lsrepairsevdiskcopyprogress –delim : vdisk0

The resulting output

id:name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:repairing:50:070301120000
0:vdisk0:1:repairing:51:070301120000

An invocation example
lsrepairsevdiskcopyprogress –delim : -copy 1 vdisk0

The resulting output

id:name:copy id:task:progress:estimated_completion_time
0:vdisk0:1:repairing:51:070301120000

lsrepairvdiskcopyprogress
The lsrepairvdiskcopyprogress command displays the progress of volume repairs and validations.

Syntax


lsrepairvdiskcopyprogress

-nohdr -delim delimiter -copy id


vdisk_name
vdisk_id

328 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-copy id
(Optional) Specifies the volume copy ID to list repair progress for. If you do not specify this
parameter, progress is displayed for all copies.
vdisk_name | vdisk_id
(Optional) Specifies the volume name or ID to list repair progress for. You must specify this
parameter last on the command line.

Description

The lsrepairvdiskcopyprogress command displays the progress of repairs and validations being made to
mirrored volumes. Use this command to track progress after running the repairvdiskcopy command. You
e can specify a volume copy using the -copy parameter. To display the volumes that have two or more
copies with an active task, specify the command with no parameters; it is not possible to have only one
volume copy with an active task.

The command displays progress for the following types of volume copies:
v All volume copies display the same task; validate, medium or resync, depending on the specified
parameter.
v All volume copies display the same percentage and estimated completion time.
v If specified, non-mirrored volumes are displayed as a single copy with a blank task; they are not
displayed in the full concise view.
v Once a task completes, the task is blank for all copies.
v If the task is blank, the percentage and the completion time are also blank.

3 The command returns values for the following volume repair attributes:
3 vdisk_id
3 Indicates the volume ID.
3 vdisk_name
3 Indicates the volume name.
3 copy_id
3 Indicates the system-assigned identifier for the volume copy.
e task
3 Indicates the active task. The values can be repairing or compressed_repairing.
3 progress
3 Indicates the task completion percentage. This value is 0 when task is in compressed_repairing
3 state.

Chapter 17. Information commands 329

3 estimated_completion_time
3 Indicates the expected time (duration) the task completion time. The value is in the
3 YYMMDDHHMMSS format, and is blank if the duration is not known.

An invocation example
lsrepairvdiskcopyprogress –delim :

The resulting output

vdisk_id:vdisk_name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:medium:50:070301120000
0:vdisk0:1:medium:50:070301120000

An invocation example
lsrepairvdiskcopyprogress –delim : vdisk0

The resulting output

vdisk_id:vdisk_name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:medium:50:070301120000
0:vdisk0:1:medium:50:070301120000

An invocation example
lsrepairvdiskcopyprogress –delim : -copy 0 vdisk0

The resulting output

vdisk_id:vdisk_name:copy id:task:progress:estimated_completion_time
0:vdisk0:0:medium:50:070301120000

3 An invocation example showing a compressed volume copy and a TP volume copy being repaired
3 lsrepairvdiskcopyprogress

3 The resulting output

3 vdisk_id vdisk_name copy_id task progress estimated_completion_time
3 0 vdisk0 0 repairing 50 070301120000
3 2 vdisk2 1 compressed_repairing 0 070301080102

lsrmvdiskdependentmaps
The lsrmvdiskdependentmaps command displays all FlashCopy mappings that must be stopped for the
specified volume to be deleted.

Syntax


lsrmvdiskdependentmaps vdisk_name

-nohdr -delim delimiter vdisk_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each

330 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
vdisk_name | vdisk_id
(Required) Specifies the name or ID of the volume for which the FlashCopy mappings are displayed.

Description

This command returns a list of the FlashCopy mappings that must be stopped before the specified
volume can be deleted. Any mappings that are returned in the list for the volume are automatically
stopped when the volume is deleted with the force option.

An invocation example
lsrmvdiskdependentmaps -delim : 0

The resulting output

id:name
2:fcmap2
5:fcmap5

lsroute
The lsroute command displays the IP routing table.

Syntax


lsroute


Description

This command displays the IP routing table. The table provides details of the gateway that is used for IP
traffic to a range of IP addresses for each ethernet port. This information can be used to diagnose
configuration node accessibility problems. The lsroute command is equivalent to the Linux route
command.

An invocation example
lsroute

The resulting output

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
9.71.46.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 9.71.46.1 0.0.0.0 UG 0 0 0 eth0
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2002:914:fc12:849::/64 :: UA 256 3675 0 eth0
fe80::/64 :: U 256 0 0 eth0
::/0 fe80::7:b4ff:fe00:500 UGDA 1024 1 0 eth0
::1/128 :: U 0 1441 1 lo
2002:914:fc12:849:214:5eff:fe33:5192/128 :: U 0 0 1 lo
fe80::214:5eff:fe33:5192/128 :: U 0 0 1 lo
ff00::/8 :: U 256 0 0 eth0

Chapter 17. Information commands 331

lssevdiskcopy
The lssevdiskcopy command lists the space-efficient copies of the specified volumes.

Syntax


lssevdiskcopy

-nohdr -bytes -delim delimiter


-copy id -filtervalue? vdisk_name
vdisk_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-bytes
(Optional) Displays all capacities as bytes. Capacity values displayed in units other than bytes might
be rounded.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-copy id
(Optional) Specifies the volume copy to list space-efficient copies for. You must specify a vdisk_name |
vdisk_id value with this parameter.
-filtervalue?
(Optional) Displays a list of valid filter attributes. The following filters for the lssevdiskcopy
command are valid:
v mdisk_grp_id
v mdisk_grp_name
v overallocation
v autoexpand
v grainsize
vdisk_name | vdisk_id
(Optional) Specifies the virtual disk name or ID to list space-efficient copies for. You must specify this
parameter last on the command line. If you do not enter this parameter, the command lists all
space-efficient thin-provisioned volume copies in the clustered system.

Description

The lssevdiskcopy command lists all space-efficient copies of the specified volume. If you do not specify
a volume, the command lists all space-efficient volume copies in the clustered system.

332 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The command provides a concise view of the space-efficient properties of the selected volume copies.
Run the lsvdiskcopy command to see a concise view of the properties that are common to space-efficient
and non-space-efficient volume copies. See the description of the lsvdisk command for a description of
the fields that are shown in the view.

The command returns values for the following volume copy attributes:
copy_id
Specifies a system-assigned identifier for the volume copy. The value can be 0 or 1.
status The value can be online or offline. A copy is offline if all nodes cannot access the storage pool
that contains the copy.
sync Indicates whether the volume copy is synchronized.
primary
Indicates whether the volume copy is the primary copy. A volume has exactly one primary copy.
The value can be Yes or No.
mdiskgrp_id/name
Specifies the name and ID of the storage pool that the volume copy belongs to.
type Specifies the virtualization type of the volume. The value can be striped, sequential or image.
mdisk_id/name
Specifies the MDisk that is used for sequential and image mode volumes.
fast_write_state
Specifies the cache state of the volume copy. The value can be empty, not_empty, corrupt, or
repairing. The value is always empty for non-space-efficient copies. A cache state of corrupt
indicates that the volume is space-efficient and requires repair that is initiated by a recovervdisk
command or the repairsevdiskcopy command.
used_capacity
Specifies the portion of real_capacity that is being used to store data. For non-space-efficient
copies, this value is the same as the volume capacity. If the volume copy is space-efficient, the
value increases from zero to the real_capacity value as more of the volume is written to.
real_capacity
Specifies the amount of physical storage that is allocated from an storage pool to this volume
copy. If the volume copy is not space-efficient, the value is the same as the volume capacity. If the
volume copy is space-efficient, the value can be different.
free_capacity
Specifies the difference between the real_capacity and used_capacity values.
overallocation
Expressed as a percentage, specifies the ratio of volume capacity to real_capacity values. This
value is always 100 for non-space-efficient volumes.
autoexpand
Specifies whether autoexpand is enabled on a space-efficient volume. The value can be on or off.
warning
Expressed as a percentage, for space-efficient volume copies only. A warning is generated when
the ratio of used_capacity to volume capacity reaches the specified level.
grainsize
For space-efficient volume copies, specifies the grain size chosen for the volume copy when it
was created.

1 Remember: This field is always blank for compressed volume copies.

Chapter 17. Information commands 333

 se_copy
1 Specifies if the copy is space-efficient. The value can be yes or no.
easy_tier
This value is set by the user and determines whether Easy Tier is permitted to manage the pool.

Note:
1. If easy_tier is on, then easy_tier_status can take on any value.
2. if easy_tier is off, then easy_tier_status is measured or inactive .
easy_tier_status
Which Easy Tier functions are active for the volume copy:
v Active : may move extents of this volume copy for performance (automatic data placement).
v Measured: statistics are being gathered for this volume copy, but no extents will be moved.
v Inactive : no Easy Tier function is active.
tier Which tier information is being reported:
v generic_ssd
v generic_hdd
tier_capacity
The total MDisk capacity assigned to the volume in the tier.

Note: For space-efficient copies, the capacity by tier will be the real capacity.
1 compressed_copy
1 Indicates whether or not the volume copy is compressed.
2 uncompressed_used_capacity
2 For compressed volumes, indicates the amount of data written to the volume before compression.

An invocation example
lssevdiskcopy –delim :

The resulting output

2 vdisk_id:vdisk_name:copy_id:mdisk_grp_id:mdisk_grp_name:capacity:used_capacity:real
2 _capacity:
1 free_capacity:overallocation:autoexpand:warning:grainsize:se_copy:compressed_copy:uncompressed_used_capacity
1 0:vv1:0:0:ppp:16.00GB:2.00GB:2.01GB:6.00GB:796:off:20:32:no:yes:3.27GB
1 1:se1:0:0:ppp:16.00GB:1.00GB:4.00GB:15.00GB:400:off:20:32:yes:no:1.0GB:yes:no:1.0GB
2 1:se1:1:0:ppp:16.00GB:2.00GB:2.01GB:14.00GB:796:off:45:256:no:yes:4.46GB

An invocation example
lssevdiskcopy -delim : -copy 0 0

The resulting output

2 vdisk_id:0
2 vdisk_name:vv1
2 capacity:16.00GB
2 copy_id:0
2 status:online
2 sync:yes
2 primary:yes
2 mdisk_grp:1
2 mdisk_grp name:mdisk_group_1
2 type:striped
2 mdisk_id:
2 mdisk_name:
2 fast_write_state:not_empty
2 used_capacity:2.00GB

334 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2 real_capacity:2.01GB
2 free_capacity:6.00GB
2 overallocation:796
2 autoexpand:on
2 warning:25
2 grainsize:256
2 se_copy:yes
2 easy_tier:on
2 easy_tier_status:active
2 tier:generic_ssd
2 tier_capacity:64.00MB
2 tier:generic_hdd
2 tier_capacity:2.00GB
2 compressed_copy:yes
2 uncompressed_used_capacity:3.27GB
2
2 lssnmpserver
2 The lssnmpserver command returns a concise list or a detailed view of SNMP servers that are configured
2 on the cluster.

2 Syntax

2

lssnmpserver

-nohdr -delim delimiter snmp_server_name
snmp_server_id
2

2 Parameters
2 -nohdr
2 (Optional) By default, headings are displayed for each column of data in a concise style view, and for
2 each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
2 headings.

2 Note: If there is no data to be displayed, headings are not displayed.

2 -delim delimiter
2 (Optional) By default in a concise view, all columns of data are space-separated. The width of each
2 column is set to the maximum possible width of each item of data. In a detailed view, each item of
2 data has its own row, and if the headers are displayed, the data is separated from the header by a
2 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
2 one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
2 items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
2 view, the data is separated from its header by the specified delimiter.
2 snmp_server_name | snmp_server_id
2 (Optional) Specifies the name or ID of an existing SNMP server that must be listed.

2 Description

2 Use this command to display a concise list or a detailed view of SNMP servers that are configured on the
2 cluster.

2 A concise invocation example

2 lssnmpserver -delim :

2 The concise resulting output

Chapter 17. Information commands 335

2 id:name:IP_address:error:warning:info:port:community
2 0:snmp0:192.135.60.4:on:on:on:78:public
2 1:newserver:192.136.70.7:on:off:off:250:newcommunity

2 A detailed invocation example

2 lssnmpserver snmp0

2 The detailed resulting output

2 id 0
2 name snmp0
2 IP_address 192.135.60.4
2 error on
2 warning on
2 info on
2 port 78
2 community public
2
2 lssoftwaredumps (Deprecated)
2 Attention: The lssoftwaredumps command is deprecated. Use the lsdumps command to display a list of
2 files in a particular dumps directory.
2
2 lssoftwareupgradestatus
2 The lssoftwareupgradestatus command displays the status of a software upgrade.

2 Syntax

2

lssoftwareupgradestatus

-nohdr
2

2 Parameters
2 -nohdr
2 (Optional) Suppresses the display of headings.

2 Description

2 The lssoftwareupgradestatus command displays the status of a software upgrade.

2 Remember:
2 v It is important to understand which volumes must have a particular node being online. If a status of
2 stalled_non_redundant is displayed, proceeding with the remaining set of node upgrades might result
2 in offline volumes (which results in data loss). Contact an IBM service representative to complete the
2 manual upgrade.
2 v In some cases before an upgrade can be performed, you must increase the -rsize value of the VDisk
2 (volume).

2 The following are the upgrade status states:

2 preparing
2 The upgrade is being prepared.
2 prepared
2 The prepare is successful.
2 prepared_failed
2 The prepare is unsuccessful.
336 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
An invocation example
lssoftwareupgradestatus

The resulting output

status
upgrading

An invocation example
lssoftwareupgradestatus

The resulting output

status
stalled_non_redundant

lstimezones
The lstimezones command lists the time zones that are available on the cluster. Each timezone is
assigned an ID that can be used in the settimezone command to set the time zone.

Syntax


lstimezones

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by a colon character.

Description

This command displays a list of all the time zones that are available on the cluster. Each time zone is
assigned an ID. This ID can be used in the settimezone command.

An invocation example
lstimezones

The resulting output

id timezone
0 Africa/Abidjan
1 Africa/Accra
2 Africa/Addis_Ababa

Chapter 17. Information commands 337

 3 Africa/Algiers
4 Africa/Asmera
5 Africa/Bamako
6 Africa/Bangui

lsuser
Use the lsuser command to display a list of the users that have been created on the cluster.

Syntax
e

lsuser

-nohdr -delim delimiter -filtervalue attrib=value


-filtervalue? userid_or_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. If you enter -delim : on the command line, the colon character (:) separates all items of data
in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is
separated from its header by the specified delimiter.
e -filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is the asterisk (*).
v The command can contain a maximum of one wildcard.
v When you use a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lsuser -filtervalue "usergrp_name=md*"
-filtervalue?
(Optional) Displays the valid filter attributes for the -filtervalue attribute=value parameter:
v password
v ssh_key
v remote
v usergrp_id
v usergrp_name

338 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 userid_or_name
(Optional) Specifies the ID or name of the user for which the association is being deleted. If this is
specified, the detailed view for the specified user is displayed in the ouput. If you do not specify an
ID or name, the concise view is displayed.

Description

This command displays a list of users that have been created on the cluster.

An invocation example
lsuser

The resulting output

id name password ssh_key remote usergrp_id usergrp_name
0 superuser yes no no 0 SecurityAdmin
1 simon no yes no 2 CopyOperator
2 jane yes no no 3 Service
3 kip yes yes yes

lsusergrp
Use the lsusergrp command to display a list of the user groups that have been created on the cluster.

Syntax


lsusergrp

-nohdr -delim delimiter

e


-filtervalue attrib=value -filtervalue? usergrp_id_or_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. If you enter -delim : on the command line, the colon character (:) separates all items of data
in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is
separated from its header by the specified delimiter.
e -filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed.

Note: Some filters allow the use of a wildcard when you enter the command. The following rules
apply to the use of wildcards with the SAN Volume Controller CLI:
v The wildcard character is the asterisk (*), which must be used as the first or last character in the
string.

Chapter 17. Information commands 339

 v The command can contain a maximum of one wildcard.
v When you use a wildcard, enclose the filter entry within double quotation marks (""), as follows:
lsusergrp -filtervalue "role=md*"
-filtervalue?
(Optional) Displays the valid filter attributes for the -filtervalue attribute=value parameter:
v role
v remote
e For more information about filtering attributes, see “Attributes of the -filtervalue parameters” on
e page xxvi.
usergrp_id_or_name
(Optional) Specifies the ID or name of the user group to view. If you do not specify an ID or name,
all groups are displayed.

Description
This command displays a list of user groups that have been created on the cluster.

An invocation example
lsusergrp

The resulting output

id name role remote
0 SecurityAdmin SecurityAdmin yes
1 Administrator Administrator no
2 CopyOperator CopyOperator no
3 Service Service yes
4 Monitor Monitor no
5 support Service no

lsvdisk
e The lsvdisk command displays a concise list or a detailed view of VDisks (volumes) that are recognized
e by the clustered system (system).

Syntax


lsvdisk

-filtervalue attrib=value -nohdr -bytes


-delim delimiter -filtervalue? object_id
object_name

Parameters
-filtervalue attrib=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter
attribute value are displayed. If a capacity is specified, the units must also be included.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

340 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note: If there is no data to be displayed, headings are not displayed.
-bytes
(Optional) Displays all capacities as bytes. Capacity values displayed in units other than bytes might
be rounded. When filtering on capacity, use a unit of bytes, -unit b, for exact filtering. For space
efficient copies, the capacity by tier will be the real capacities.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
object_id | object_name
(Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of
the specific object is returned and any value that is specified by the -filtervalue parameter is ignored.
If you do not specify the object_id | object_name parameter, the concise view of all objects matching
the filtering requirements that is specified by the -filtervalue parameter are displayed.
-filtervalue?
(Optional) Displays a list of valid filter attributes. The following filters for the lsvdisk command are
valid:
e v name
e v id
3 v IO_group_id
3 v IO_group_name
e v status
e v mdisk_grp_name
e v mdisk_grp_id
e v capacity
e v type
e v FC_id
e v FC_name
e v RC_id
e v RC_name
e v vdisk_id
e v vdisk_name
e v vdisk_UID
e v fc_map_count
e v copy_count
e v fast_write_state
e v se_copy_count
e v filesystem
e v preferred_node_id
e v mirror_write_priority
e v RC_change
2 v compressed_copy_count
2 v access_IO_group_count

Chapter 17. Information commands 341

 Note: It is not possible to filter the lsvdisk command with mdisk_grp_name=many to identify
e mirrored volumes. Instead, filter on copy_count=2.

Description

This command displays a concise list or a detailed view of attributes for all volumes and volume copies
e in the system.

e The volume is offline and unavailable if one of the following takes place:
v Both nodes in the I/O group are missing.
v None of the nodes in the I/O group that are present can access the volume.
v All synchronized copies for this volumes are in storage pools that are offline.
v The volume is formatting.
If you have a degraded volume and all of the associated nodes and MDisks are online, call the IBM
Support Center for assistance. A volume is reported as degraded if any of the following occurs:
v One of the nodes in the I/O group is missing.
v One of the nodes in the I/O group cannot access all the MDisks in the storage pool that the volume
spans. In this case MDisks are shown as degraded and the fix procedures for MDisks should be
followed to resolve the problem.
v The fast write cache pins data for one or more volumes in the I/O group and is unable to perform a
failback until the situation is resolved. An error log indicating that the cache has pinned data is
displayed. Follow the fix procedures for this error log to resolve the problem. The most common
causes of pinned data are the following:
– One or more volumes in an I/O group is offline due to an asymmetric failure and has pinned data
in the cache. Asymmetric failures can occur because of SAN Volume Controller fabric faults or
misconfiguration, back-end controller faults or misconfiguration or because repeated errors has led
e to the system excluding access to a MDisk through one or more nodes.
– One or more volumes in an I/O group is offline due to a problem with a FlashCopy mapping.

e The command returns values for the following volume attributes:

IO_groups_id/name
e Specifies the I/O Group that the volume belongs to.
status The value can be online, offline or degraded.
mdisk_grp_id/name
e Specifies the name and ID of the storage pool that the volume belongs to. If the volume has more
than one copy, these fields display many.
e type Specifies the virtualization type of the volume. The value can be striped, sequential, image or
e many. The value many indicates that the volume has more than one copy, which can have
different virtualization types.
capacity
e Specifies the total capacity of the volume.
formatted
e Indicates whether the volume was formatted when it was created. The value can be Yes or No.
mdisk_id/name
e Specifies the MDisk that is used for sequential and image mode volumes. If the volume has more
than one copy, these fields display many.
FC_id/name
e Specifies the name and ID of the FlashCopy mapping that the volume belongs to. The value
e many indicates that the volume belongs to more than one FlashCopy mapping.

342 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e RC_id Specifies the ID of the Global Mirror or Metro Mirror relationship that the volume belongs to.
The value must be numerical.
RC_name
e Specifies the name of the Global Mirror or Metro Mirror relationship that the volume belongs to.
vdisk_UID
e Specifies the UID of the volume.
throttling
e Specifies the throttle rate of the volume.
preferred_node_id
e Specifies the ID of the preferred node for the volume.

Remember: This value must be numeric. (The value is zero if no node is configured in the I/O
group that contains the preferred node.)
fast_write_state
e Specifies the cache state for the volume. The value can be empty, not_empty, corrupt, or
e repairing. A cache state of corrupt indicates that the volume requires recovery by using one of
the recovervdisk commands. A cache state of repairing indicates that repairs initiated by a
recovervdisk command are in progress.
e cache Specifies the cache mode of the volume. The value can be readwrite or none.
e udid Specifies the unit number for the volume. Only OpenVMS hosts require a unit number.
fc_map_count
e Specifies the number of FlashCopy mappings that the volume belongs to.
sync_rate
Specifies the rate for synchronization for mirrored copies.
se_copy_count
Specifies the number of space-efficient copies.

1 Remember: This value represents only space- efficient copies and is not used for compressed
1 volume copies.
filesystem
Expressed as a value string (long object name with a maximum of 63 characters), specifies the full
e name for file system which owns this volume; otherwise, it is blank.
mirror_write_priority
Specifies the mirror write algorithm priority being used if the volume is mirrored.
RC_change
Specifies if a volume is a change volume of a Global Mirror or Metro Mirror relationship.
1 compressed_copy_count
1 Specifies the number of compressed volume copies.
1 access_IO_group_count
1 Specifies the number of I/O groups in the volume access set.

e The command returns values for the following volume copy attributes:
copy_id
e Specifies a system-assigned identifier for the volume copy. The value can be 0 or 1.
status The value can be online or offline. A copy is offline if all nodes cannot access the storage pool
that contains the copy.
e sync Indicates whether the volume copy is synchronized.

Chapter 17. Information commands 343

 primary
e Indicates whether the volume copy is the primary copy. A volume has exactly one primary copy.
The value can be Yes or No.
mdiskgrp_id/name
e Specifies the name and ID of the storage pool that the volume copy belongs to.
e type Specifies the virtualization type of the volume. The value can be striped, sequential or image.
mdisk_id/name
e Specifies the MDisk that is used for sequential and image mode volumes.
fast_write_state
e Specifies the cache state of the volume copy. The value can be empty, not_empty, corrupt, or
repairing. The value is always empty for non-space-efficient copies. A cache state of corrupt
e indicates that the volume is space-efficient and requires repair that is initiated by a recovervdisk
command or the repairsevdiskcopy command.
used_capacity
Specifies the portion of real_capacity that is being used to store data. For non-space-efficient
e copies, this value is the same as the volume capacity. If the volume copy is space-efficient, the
e value increases from zero to the real_capacity value as more of the volume is written to.
real_capacity
e Specifies the amount of physical storage that is allocated from an storage pool to this volume
e copy. If the volume copy is not space-efficient, the value is the same as the volume capacity. If the
e volume copy is space-efficient, the value can be different.
free_capacity
Specifies the difference between the real_capacity and used_capacity values.
overallocation
e Expressed as a percentage, specifies the ratio of volume capacity to real_capacity values. This
e value is always 100 for non-space-efficient volumes.

1 Remember: This value can be any percentage (but not blank) for compressed volume copies.
autoexpand
e Specifies whether autoexpand is enabled on a space-efficient volume. The value can be on or off.

2 Remember: This value cannot be blank for compressed copies.

warning
Expressed as a percentage, for space-efficient volume copies only. A warning is generated when
the ratio of used_capacity to volume capacity reaches the specified level.

1 Remember: This value can be any percentage for compressed volume copies.
grainsize
e For space-efficient volume copies, specifies the grain size chosen for the volume copy when it
was created.

1 Remember: This value is always blank for compressed volume copies.

se_copy
Specifies if the copy is space-efficient.

1 Remember: This value is yes for space- efficient copies and no for compressed volume copies.
easy_tier
This value is set by the user and determines whether Easy Tier is permitted to manage the pool.

344 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note:
1. If easy_tier is on, then easy_tier_status can take on any value.
2. If easy_tier is off, then easy_tier_status is measured or inactive .
easy_tier_status
e Which Easy Tier functions are active for the volume copy:
v Active : may move extents of this volume copy for performance (automatic data placement).
v Measured: statistics are being gathered for this volume copy, but no extents will be moved.
v Inactive : no Easy Tier function is active.
tier The tier information being reported:
v generic_ssd
v generic_hdd
tier_capacity
e The total MDisk capacity assigned to the volume in the tier.

Note: For space-efficient copies, the capacity by tier will be the real capacity.
1 compressed_copy
1 Indicates if the volume copy is compressed.
2 uncompressed_used_capacity
2 For compressed volumes, indicates the amount of data written to the volume before compression.

2 A detailed invocation example for a mirrored volume with two copies

2 lsvdisk -delim : vv1

2 The resulting output

2 id:0
2 name:vv1
2 IO_group_id:0
2 IO_group_name:io_grp0
2 status:degraded
2 mdisk_grp_id:many
2 mdisk_grp_name:many
2 capacity:16.00GB
2 type:many
2 formatted:no
2 mdisk_id:many
2 mdisk_name:many
2 FC_id:
2 FC_name:
2 RC_id:
2 RC_name:
2 vdisk_UID:00000000000000AB:6005076801CF003F2800000000000000
2 throttling:0
2 preferred_node_id:1
2 fast_write_state:empty
2 cache:readwrite
2 udid:1234
2 fcmap_count:0
2 sync_rate:25
2 copy_count:2
2 se_copy_count:0
2 filesystem:filesystem1
2 mirror_write_priority:latency
2 RC_change:no
2 compressed_copy_count:1
2 access_IO_group_count:2
2
2 copy_id:0

Chapter 17. Information commands 345

2 status:online
2 sync:yes
2 primary:yes
2 mdisk_grp:1
2 mdisk_grp_name:mdisk_group_1
2 type:striped
2 mdisk_id:
2 mdisk_name:
2 fast_write_state:empty
2 used_capacity:16.00GB
2 real_capacity:16.00GB
2 free_capacity:6.00GB
2 overallocation:100
2 autoexpand:
2 warning:
2 grainsize:
2 se_copy:no
2 easy_tier:off
2 easy_tier_status:inactive
2 tier:generic_ssd
2 tier_capacity:0.00MB
2 tier:generic_hdd
2 tier_capacity:16.00GB
2 compressed_copy:no
2 uncompressed_used_copy:16.00GB
2
2 copy_id:1
2 status:offline
2 sync:no
2 primary:no
2 mdisk_grp:2
2 mdisk_grp_name:mdisk_group_2
2 type:striped
2 mdisk_id:
2 mdisk_name:
2 fast_write_state:not_empty
2 used_capacity:2.00GB
2 real_capacity:4.00GB
2 free_capacity:2.00GB
2 overallocation:400
2 autoexpand:on
2 warning:20
2 grainsize:256
2 se_copy:no
2 easy_tier:on
2 easy_tier_status:active
2 tier:generic_ssd
2 tier_capacity:64.00MB
2 tier:generic_hdd
2 tier_capacity:3.94GB
2 compressed_copy:yes
2 uncompressed_used_copy:5.56GB

2 A detailed invocation example for a volume

2 lsvdisk -delim : vv45

2 The resulting output

2 name:vv45
2 IO_group_id:0
2 IO_group_name:io_grp0
2 status:online
2 mdisk_grp_id:0
2 mdisk_grp_name:Group0
2 capacity:1000.00MB
2 type:striped
2 formatted:no

346 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2 mdisk_id:
2 mdisk_name:
2 FC_id:
2 FC_name:
2 RC_id:
2 RC_name:
2 vdisk_UID:60050768019B82328000000000000010
2 throttling:0
2 preferred_node_id:2
2 fast_write_state:empty
2 cache:readwrite
2 udid:
2 fc_map_count:0
2 sync_rate:50
2 copy_count:1
2 se_copy_count:0
2 filesystem:
2 mirror_write_priority:redundancy
2 RC_change:no
2 compressed_copy_count:0
2 access_IO_group_count:1
2 copy_id:0
2 status:online
2 sync:yes
2 primary:yes
2 mdisk_grp_id:0
2 mdisk_grp_name:Group0
2 type:striped
2 mdisk_id:
2 mdisk_name:
2 fast_write_state:empty
2 used_capacity:1000.00MB
2 real_capacity:1000.00MB
2 free_capacity:0.00MB
2 overallocation:100
2 autoexpand:
2 warning:
2 grainsize:
2 se_copy:no
2 easy_tier:on
2 easy_tier_status:inactive
2 tier:generic_ssd
2 tier_capacity:0.00MB
2 tier:generic_hdd
2 tier_capacity:1000.00MB
2 compressed_copy:no
2 uncompressed_used_capacity:1000.00MB

A concise invocation example

lsvdisk -delim :

The resulting output

id:name:IO_group_id:IO_group_name:status:mdisk_grp_id:mdisk_grp_name:capacity:type:
FC_id:FC_name:RC_id:RC_name:vdisk_UID:fc_map_count:copy_count:
3 fast_write_state:se_copy_count:RC_change:compressed_copy_count
3 0:vdisk0:0:io_grp0:degraded:0:mdiskgrp0:10.00GB:striped:::::60050768018300003000000000000000:0:1:empty:0:no0

1 lsvdiskaccess
1 The lsvdiskaccess command displays a list of all I/O groups in the volume access set.

Chapter 17. Information commands 347

1 Syntax

1

lsvdiskaccess

vdisk_id
vdisk_name
1

1 Parameters
1 vdisk_id | vdisk_name
e (Optional) Specifies the volume for which to list access I/O groups.

1 Description

1 The lsvdiskaccess command lists the I/O groups in a volume access set. A volume being accessible in an
1 I/O group does not mean the volume is mapped to any hosts. There is a detailed and concise view, but
1 the detailed view does not contain more information than the concise view.

1 This command returns values for the following volume attributes:

1 VDisk_id
1 Identifies the volume ID.
1 VDisk_name
1 Identifies the volume name.
1 IO_group_id
1 Identifies an I/O group ID in the volume access set.
1 IO_group_name
1 Identifies an I/O group name in the volume access set.

1 A detailed invocation example

1 lsvdiskaccess 0

1 The resulting output

1 vdisk_id vdisk_name IO_group_id IO_group_name
1 0 vdisk0 0 io_grp0
1 0 vdisk0 1 io_grp1
1 0 vdisk0 2 io_grp2

1 A concise invocation example

1 lsvdiskaccess

1 The resulting output

1 vdisk_id vdisk_name IO_group_id IO_group_name
1 0 vdisk0 0 io_grp0
1 0 vdisk0 1 io_grp1
1 0 vdisk0 2 io_grp2
1 3 vdisk3 1 io_grp1
1 7 vdisk7 0 io_grp0
1 7 vdisk7 2 io_grp2
1
lsvdiskcopy
The lsvdiskcopy command lists volume copy information.

348 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


lsvdiskcopy

-nohdr -bytes -delim delimiter


-filtervalue? vdisk_name
vdisk_id
-copy copy_id vdisk_name
vdisk_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-bytes
(Optional) Displays all capacities as bytes. Capacity values displayed in units other than bytes might
be rounded.
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-copy copy_id
(Optional) Specifies the volume copy to list information for. You must specify a vdisk_name | vdisk_id
value with this parameter.
-filtervalue?
(Optional) Displays a list of valid filter attributes. The following filters for the lsvdiskcopy command
are valid:
v primary
v status
v sync
v mdisk_grp_id
v mdisk_grp_name
v type
v easy_tier
v easy_tier_status
vdisk_name | vdisk_id
(Optional) Specifies the volume to list copy information for. You must specify this parameter last on
the command line. If you specify a vdisk_name | vdisk_id value only, all copies for the volume are
listed.

Chapter 17. Information commands 349

Description

The lsvdiskcopy command lists information for volume copies. If you specify the command with no
parameters, all volumes and copies in the clustered system are listed.

The command returns values for the following volume copy attributes:
copy_id
Specifies a system-assigned identifier for the volume copy. The value can be 0 or 1.
status The value can be online or offline. A copy is offline if all nodes cannot access the storage pool
that contains the copy.
sync Indicates whether the volume copy is synchronized.
primary
Indicates whether the volume copy is the primary copy. A volume has exactly one primary copy.
The value can be yes or no.
mdiskgrp_id/name
Specifies the name and ID of the storage pool that the volume copy belongs to.
type Specifies the virtualization type of the volume. The value can be striped, sequential or image.
mdisk_id/name
Specifies the MDisk that is used for sequential and image mode volumes.
fast_write_state
Specifies the cache state of the volume copy. The value can be empty, not_empty, corrupt, or
repairing. The value is always empty for non-space-efficient copies. A cache state of corrupt
indicates that the volume is space-efficient and requires repair that is initiated by a recovervdisk
command or the repairsevdiskcopy command.
used_capacity
Specifies the portion of real_capacity that is being used to store data. For non-space-efficient
copies, this value is the same as the volume capacity. If the volume copy is space-efficient, the
value increases from zero to the real_capacity value as more of the volume is written to.

Remember: This value is the same as the volume capacity value for fully-allocated copies.
real_capacity
Specifies the amount of physical storage that is allocated from an storage pool to this volume
copy. If the volume copy is not space-efficient, the value is the same as the volume capacity. If the
volume copy is space-efficient, the value can be different.

Remember: This value is the same as the volume capacity value for fully-allocated copies.
free_capacity
Specifies the difference between the real_capacity and used_capacity values.

Remember: This value is zero for fully-allocated copies.

overallocation
Expressed as a percentage, specifies the ratio of volume capacity to real_capacity values. This
value is always 100 for non-space-efficient volumes.
autoexpand
Specifies whether autoexpand is enabled on a space-efficient volume. The value can be on or off.
warning
Expressed as a percentage, for space-efficient volume copies only. A warning is generated when
the ratio of used_capacity to volume capacity reaches the specified level.

350 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 grainsize
For space-efficient volume copies, specifies the grain size chosen for the volume copy when it
was created.
se_copy
Specifies if the copy is space-efficient.
easy_tier
This value is set by the user and determines whether Easy Tier is permitted to manage the pool.

Note:
1. If easy_tier is on, then easy_tier_status can take on any value.
2. if easy_tier is off, then easy_tier_status is measured or inactive .
easy_tier_status
Which Easy Tier functions are active for the volume copy:
v Active : may move extents of this volume copy for performance (automatic data placement).
v Measured: statistics are being gathered for this volume copy, but no extents will be moved.
v Inactive : no Easy Tier function is active.
tier Which tier information is being reported:
v generic_ssd
v generic_hdd
tier_capacity
The total MDisk capacity assigned to the volume in the tier.

Note: For space-efficient copies, the capacity by tier will be the real capacity.
1 compressed_copy
1 Indicates whether or not the volume copy is compressed.
1 uncompressed_used_capacity
2 For compressed volumes, indicates the amount of data written to the volume before compression.

An invocation example
lsvdiskcopy -delim :

The resulting output

vdisk_id:vdisk_name:copy_id:status:sync:primary:mdisk_grp_id:mdisk_grp_name:
1 capacity:type:se_copy:easy_tier:easy_tier_status:compressed_copy
1 0:RAM_V2:0:online:yes:yes:2:RAM_MDG2:5.00GB:striped:yes:on:inactive:yes
1 1:RAM_V3:0:online:yes:yes:2:RAM_MDG2:5.00GB:striped:no:on:inactive:no
1 2:RAM_V4:0:online:yes:yes:1:RAM_MDG3:5.00GB:striped:no:on:inactive:yes
1 3:RAM_V5:0:online:yes:yes:2:RAM_MDG2:5.00GB:striped:yes:on:inactive:no
1 3:RAM_V5:1:online:yes:no:2:RAM_MDG2:5.00GB:striped:yes:on:inactive:yes
1 4:RAM_V1:0:online:yes:yes:3:RAM_MDG1:5.00GB:striped:no:on:inactive:no
1 5:RAM_V6:0:online:yes:yes:0:RAM_MDG4:5.00GB:striped:yes:on:inactive:yes

An invocation example
lsvdiskcopy -copy 0 –delim : vv1

The resulting output

vdisk_id:0
vdisk_name:vv1
capacity:16.00GB
copy_id:0
status:online
sync:yes

Chapter 17. Information commands 351

 primary:yes
mdisk_grp:1
mdisk_grp name:mdisk_group_1
type:striped
mdisk_id:
mdisk_name:
fast_write_state:not_empty
used_capacity:2.00GB
real_capacity:8.00GB
free_capacity:6.00GB
overallocation:200
autoexpand:on
warning:25
grainsize:256
se_copy:yes
easy_tier:on
easy_tier_status:active
tier:generic_ssd
tier_capacity:64.00MB
tier:generic_hdd
tier_capacity:7.94GB
1 compressed_copy:yes
2 uncompressed_used_capacity:1.0MB

lsvdiskdependentmaps
The lsvdiskdependentmaps command displays all FlashCopy mappings with target volumes that are
dependent upon data held on the specified volume.

Syntax


lsvdiskdependentmaps vdisk_id

vdisk_name

Parameters
vdisk_id | vdisk_name
(Required) Specifies the name or ID of a volume.

Description

The lsvdiskdependentmaps command displays FlashCopy mappings that have target volumes that are
dependent upon data held on the specified vdisk_id | vdisk_name. This can be used to determine whether
a FlashCopy mapping can be prepared. Issue the command for the target volume vdisk_id | vdisk_name of
the FlashCopy mapping to be prepared. If no FlashCopy mappings are returned, the FlashCopy mapping
can be prepared. Any FlashCopy mappings that are returned in the list must be stopped or be in the
idle_or_copied state, before the new FlashCopy mapping can be prepared.

A concise invocation example

lsvdiskdependentmaps -delim : 0

The concise resulting output

id:name
2:fcmap2
5:fcmap5

lsvdiskextent
The lsvdiskextent command lists the MDisk extents that are provided for the specified volumes.

352 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


lsvdiskextent

-copy copy_id -nohdr -delim delimiter

vdisk_name

vdisk_id

Parameters
-copy copy_id
(Optional) Displays a list of MDisks that are members of the specified volume copy.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
vdisk_name | vdisk_id
(Required) Specifies one or more volume IDs or names.

Description

The lsvdiskextent command displays a list of MDisk IDs and the number of extents that each MDisk
provides to the specified volumes.

Each volume is constructed from one or more MDisks. To determine the relationship between a volume
and its MDisks, issue the following command:

lsvdiskmember vdisk_name | vdisk_id

where vdisk_name | vdisk_id is the name or ID of the volume. This command displays a list of MDisk IDs
that make up the volume.

To determine the number of extents that are provided by each MDisk, issue the following command:

lsvdiskextent vdisk_name | vdisk_id

where vdisk_name | vdisk_id is the name or ID of the volume. This command displays a table of MDisk
IDs and the corresponding number of extents that each MDisk provides as storage for the given volume.

To determine the relationship between MDisks and volumes, issue the following command for each
MDisk:

lsmdiskmember mdisk_name | mdisk_id

Chapter 17. Information commands 353

where mdisk_name | mdisk_id is the name or ID of the MDisk. This command displays a list of IDs that
corresponds to the volumes that are using this MDisk.

To determine the relationship between MDisks and volumes, and the number of extents that are used by
each volume, you must use the command-line interface. For each MDisk, issue the following command:

lsmdiskextent mdisk_name | mdisk_id

where mdisk_name | mdisk_id is the name or ID of the MDisk. This command displays a table of volume
IDs and the corresponding number of extents that are used by each volume.

An invocation example
lsvdiskextent -delim : vdisk0

The resulting output

id:number_extents
0:0

lsvdiskfcmapcopies
The lsvdiskfcmapcopies command displays a list of all FlashCopy mappings with a target volume
containing a valid copy of the specified volume.

Syntax


lsvdiskfcmapcopies vdisk_name

-nohdr -delim delimiter vdisk_id

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
vdisk_name | vdisk_id
(Required) Specifies the name or ID of the volume for which the FlashCopy mappings are displayed.

Description

This command returns a list of the FlashCopy mappings that have a target volume with a valid copy of
the specified volume. The target volumes of these mappings can be considered as candidate source
volumes for mappings to restore from.

The mappings returned are in the copying, idle_copied, or stopping state with 100% progress.

354 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Note: Maps that are rc_controlled are not shown in the view when this command is specified.

An invocation example
lsvdiskfcmapcopies -delim : 0

The resulting output

id:name:status:progress:difference:start_time:target_vdisk_id:
target_vdisk_name:group_id:group_name
2:fcmap2:copying:80:10:060627083137:10:vdisk10::
5:fcmap5:idle_copied:100:20:060627073130:12:vdisk12:1:fccstgrp1

lsvdiskfcmappings
The lsvdiskfcmappings command displays a list of FlashCopy mappings to which the volume belongs. A
volume can be part of up to 256 FlashCopy mappings.

Syntax


lsvdiskfcmappings vdisk_name

vdisk_id

Parameters
vdisk_name | vdisk_id
(Required) Specifies the name or ID of the volume for which a list of all FlashCopy mappings is
required.

Description

The lsvdiskfcmappings command returns a list of all FlashCopy mappings that the volume is a member
of. The list is returned in no particular order.

An invocation example
lsvdiskfcmappings -delim : vdisk2

The resulting output

fc_id:fc_name
1:fcmap1
3:fcmap3

lsvdiskhostmap
e Use the lsvdiskhostmap command to list the VDisks (volumes) to the host mapping. These hosts have the
e specified volumes mapped to them; the volumes is visible to these hosts.

Syntax


lsvdiskhostmap vdisk_id

-nohdr -delim delimiter vdisk_name

Chapter 17. Information commands 355

 Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
vdisk_id | vdisk_name
e (Required) Specifies the ID or name of the volume. The clustered system displays a list of all the
e hosts to which this volume is mapped and the Small Computer System Interface (SCSI) ID by which
e the volume is mapped.

Description

e This command displays a list of host IDs and names. These hosts have the specified volume mapped to
e them; that is, the volume is visible to these hosts. The SCSI LUN ID is also displayed. The SCSI LUN ID
e is the ID by which the volume is recognized by the host.

e Determining the host that a volume is mapped to: List the hosts that this volume is mapped to, by
issuing the following command:

lsvdiskhostmap vdisk_id | vdisk_name

e where vdisk_id | vdisk_name is the name or ID of the volume. A list is displayed. Look for the host name
e or ID to determine which host this volume is mapped to. If no data is displayed, the volume is not
mapped to any hosts.

2 The command returns the following values:

2 id Specifies the ID of the volume in the output for lsvdiskhostmap.
2 name Specifies the name of the volume in the output for lsvdiskhostmap.
2 SCSI_id
2 Specifies the SCSI ID.
2 host_id
2 Specifies the ID of the host.
2 host_name
2 Specifies the name of the host.
2 vdisk_UID
2 Specifies the UID of the volume.
2 IO_group_id
2 Specifies the ID of the input/output (I/O) group in which the host volume mapping exists.
2 IO_group_name
2 Specifies the name of I/O group in which the host volume mapping exists.

356 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2 An invocation example
2 lsvdiskhostmap 0

2 The resulting output

2 id name SCSI_id host_id host_name vdisk_UID IO_group_id IO_group_name
2 0 vdisk0 0 0 ined 6005076801E000E85000000000000000 0 iogrp0
2 0 vdisk0 0 0 ined 6005076801E000E85000000000000000 1 iogrp1
2 0 vdisk0 0 1 host0 6005076801E000E85000000000000000 0 iogrp0
2 0 vdisk0 0 1 host0 6005076801E000E85000000000000000 1 iogrp1

lsvdisklba
The lsvdisklba command lists the volume and logical block address (LBA) for the specified MDisk LBA.

Syntax


lsvdisklba -mdisklba mdisklba

-delim delimiter - nohdr

-mdisk mdisk_id

mdisk_name

Parameters
-mdisklba mdisklba
(Required) Specifies the 64-bit hexadecimal LBA on the MDisk. The LBA must be specified in hex,
with a 0x prefix.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
-mdisk mdisk_id | mdisk_name
(Required) Specifies the MDisk name or ID.

Description

The lsvdisklba command returns the LBA of the volume that is associated with the MDisk LBA.

If applicable, the command also lists the range of LBAs on both the volume and MDisk that are mapped
in the same extent, or for space-efficient disks, in the same grain.

2 The vdisk_lba field provides the corresponding LBA on the virtual capacity for the input LBA. For
2 compressed volume copies it is blank, and the system provides the ranges of virtual LBAs that are
2 compressed into the input LBA.

Chapter 17. Information commands 357

 Table 48 provides command output that depends on several variables.
Table 48. lsvdisklba command output scenarios
Extent allocated to
space-efficient
disk, LBA not used
Typical Space-efficient Extent not Formatting on space-efficient
Field scenario Quorum disk metadata allocated extent disk
copy_id yes no yes no yes yes
vdisk_id yes no yes no yes yes
vdisk_name yes no yes no yes yes
type allocated metadata metadata unallocated formatting unallocated
1 vdisk_lba yes no no no no no
vdisk_start yes no no no no no
vdisk_end yes no no no no no
mdisk_start yes yes yes yes yes yes
mdisk_end yes yes yes yes yes yes

2 An invocation example
2 lsvdisklba -mdisk 1 -mdisklba 0x100123

2 The resulting output

2 vdisk_id vdisk_name copy_id type vdisk_lba vdisk_start vdisk_end mdisk_start mdisk_end
2 0 vdisk0 0 allocated 0x00000123 0x00000000 0x000FFFFF 0x0000000000100000 0x00000000001FFFFF

lsvdiskmember
The lsvdiskmember command displays a list of MDisks that are members of the specified volume.

Syntax


lsvdiskmember

-copy copy_id -nohdr -delim delimiter

vdisk_id

vdisk_name

Parameters
-copy copy_id
(Optional) Displays a list of MDisks that are members of the specified volume copy.
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a

358 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
e vdisk_id | vdisk_name
e (Required) Identifies the specific volume to query..

Description

This command displays a list of managed disks, which provide extents that make up the volume that is
specified by the ID.

Every volume is constructed from one or more MDisks. At times, you might have to determine the
relationship between the two objects. The following procedure allows you to determine the relationships.

If you use the lsmdiskmember command, the concise view displays a list of volumes. These are the
volumes that are using extents on the managed disk that is specified by the ID. The list displays the
members of the respective object and is independent of the state of the individual members; that is, if
they are in offline state, they are still displayed.

To determine the relationship between volumes and MDisks, issue the following command:

lsvdiskmember vdisk_id | vdisk_name

where vdisk_id | vdisk_name is the name or ID of the volume. This displays a list of IDs that correspond
to the MDisks that make up the volume.

To determine he relationship between volumes and MDisks, and the number of extents that are provided
by each MDisk, you must use the command-line interface. Issue the following command:

lsvdiskextent vdisk_id | vdisk_name

where vdisk_id | vdisk_name is the name or ID of the volume. This displays a table of MDisk IDs and the
corresponding number of extents that each MDisk provides as storage for the specified volume.

To determine the relationship between MDisks and volumes, issue the following command:

lsmdiskmember mdisk_id | mdisk_name

where mdisk_id | mdisk_name is the name or ID of the MDisk. This displays a list of IDs that correspond
to the volumes that are using this MDisk.

To determine he relationship between MDisks and volumes, and the number of extents that are used by
each volume, you must use the command-line interface. For a specified MDisk, issue the following
command:

lsmdiskextent mdisk_id | mdisk_name

where mdisk_id | mdisk_name is the name or ID of the MDisk. This displays a table of volume IDs and the
corresponding number of extents that are used by each volume.

An invocation example
lsvdiskmember 1

The resulting output

Chapter 17. Information commands 359

id
2

lsvdiskprogress
The lsvdiskprogress command tracks the progress during new volume formatting.

Syntax


lsvdiskprogress

-nohdr -delim delimiter vdisk_id
vdisk_name

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by a colon character.
vdisk_id | vdisk_name
(Optional) Specifies the volume ID or name. If you do not specify this parameter, the progress of all
volumes currently being formatted is displayed.

Description

This command displays the progress of the format of a new volume as a completed percentage. If the
volume has multiple copies, the command reports the average progress of the format.

An invocation example
lsvdiskprogress -delim : 0

The resulting output

id:progress
0:58

lsvdisksyncprogress
The lsvdisksyncprogress command displays the progress of volume copy synchronization.

Syntax


lsvdisksyncprogress

-copy id vdisk_name
vdisk_id

360 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
-copy id
(Optional) Specifies the volume copy ID to list synchronization progress for. You must also specify a
vdisk_name | vdisk_id value. If you do not specify this parameter, progress is displayed for all copies.
vdisk_name | vdisk_id
(Optional) Specifies the volume name or ID to list synchronization progress for.

Description

To display the volume copies that require synchronization, specify the command with no parameters. To
display the synchronization progress for all copies of a volume, specify the command with the vdisk_name
| vdisk_id parameter. Estimated completion time is displayed in the YYMMDDHHMMSS format. The
command displays progress for the following special cases as:
v A synchronized copy displays a progress of 100 and a blank estimated completion time.
v An offline copy or a copy with a zero synchronization rate displays a blank estimated completion time.
An offline copy displays (gradually) decreasing progress if the volume is being written to.
v Nonmirrored volumes are displayed as a single copy with a progress of 100, and a blank estimated
completion time.

The lsvdisksyncprogress command also displays the progress of a mirrored volume synchronization.
After you create a mirrored volume using the mkvdisk or addvdiskcopy command, you can use the
command to monitor the progress of the synchronization.

An invocation example
lsvdisksyncprogress

The resulting output

vdisk_id vdisk_name copy_id progress estimated_completion_time
0 vdisk0 1 50 070301150000
3 vdisk3 0 72 070301132225
4 vdisk4 0 22 070301160000
8 vdisk8 1 33

An invocation example
lsvdisksyncprogress vdisk0

The resulting output

vdisk_id vdisk_name copy_id progress estimated_completion_time
0 vdisk0 0 100
0 vdisk0 1 50 070301150000

lsdependentvdisks
Use the lsdependentvdisks command to view which volumes will go offline if you remove a specific
piece of hardware from the system.

Syntax


lsdependentvdisks

-node node_id_or_name

-controller controller_id_or_name_list -mdisk mdisk_id_or_name_list

Chapter 17. Information commands 361




-drive drive_id_list -enclosure enclosure_id
-canister canister_id

Parameters
-node
(Optional) Specifies the node for which volume dependency is required.
-controller
(Optional) Specifies the controllers for which volume dependency is required.
-mdisk
(Optional) Specifies the MDisks for which volume dependency is required.
-drive
(Optional) Specifies the drives for which volume dependency is required. There is a maximum of 128
entries.
-enclosure
(Optional) Specifies the enclosure for which volume dependency is required. You can remove a
control enclosure without affecting your other data.
-canister
(Optional) Specifies an enclosure canister if -enclosure. This option is not valid for any other type.

Note: Possible values are 1 and 2.

Description
Use this command to view which volumes will go offline if you remove a specific piece of hardware from
the system. Use this command before you perform maintenance, to determine which volumes will be
affected.

An invocation example
lsdependentvdisks -delim : -drive 0:1

The resulting output

vdisk_id:vdisk_name
4:vdisk4
5:vdisk5

Note: This means that if drives 0 and 1 are removed, then volume vdisk4 and volume vdisk5 will go
offline.

lssasfabric
Use the lssasfabric command to see which canisters are visible to a node, and the order of these
canisters.

Syntax


lssasfabric


362 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

Use this command to see which canisters are visible to a node, and the order of these canisters. Table 49
describes possible outputs.
Table 49. lssasfabric output
Attribute Description
enclosure_id The identity of the enclosure the strand goes to.
canister_id The canister in the enclosure that the strand goes to.
canister_port_id The canister port that the strand goes to.
control_enclosure_id The identity of the enclosure the strand comes from.
node_canister_id The identity of the canister the strand comes from.
node_canister_port_id The node canister port the strand is from. This should be the same as the chain ID.
position The position in the strand or chain.
IO_group_id The I/O group the strand belongs to. This should be the same as the enclosure IO
group.
IO_group_name The I/O group the strand belongs to. This should be the same as the enclosure IO
group.
node_id The identity of the node that the strand is from. This is the same physical object as
the node_canister
node_name The name of the node that the strand is from. This is the same physical object as
the node_canister.

An invocation example with three enclosures: Enclosure 1 is the control enclosure, Enclosure 2 is on
chain 1 (node canister port 1) using canister port 1 as its connector, and Enclosure 3 is on chain 2
(node canister port 2) using canister port 2 as its connector
lssasfabric

The resulting output

Note: In this guide, the following output is split into two parts. This is for illustrative purposes; the
output will not appear in two parts when you run this command.

Output
enclosure_id canister_id canister_port_id control_enclosure_id node_canister_id
1 1 1 1 1
1 2 1 1 2
2 1 1 1 1
2 2 1 1 2
3 1 2 1 1
3 2 2 1 2

Output, continued
node_canister_port_id position IO_group_id IO_group_name node_id node_name
2 0 0 io_grp0 1 node1
2 0 0 io_grp0 2 node2
1 1 0 io_grp0 1 node1
1 1 0 io_grp0 2 node2
2 1 0 io_grp0 1 node1
2 1 0 io_grp0 2 node2

Chapter 17. Information commands 363

showtimezone
Use the showtimezone command to display the current time zone settings for the cluster.

Syntax


showtimezone

-nohdr -delim delimiter

Parameters
-nohdr
(Optional) By default, headings are displayed for each column of data in a concise style view, and for
each item of data in a detailed style view. The -nohdr parameter suppresses the display of these
headings.

Note: If there is no data to be displayed, headings are not displayed.

-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified character.

Description

This command displays a single time zone and its associated ID. This is the current time zone setting for
the cluster. A list of available time-zones can be viewed by running the lstimezones command. The time
zone can be changed by running the settimezone command.

An invocation example
showtimezone -delim :

The resulting output

id:timezone
522:UTC

364 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 18. Livedump commands
Livedump commands are used to manage the node livedumps.

cancellivedump
Use the cancellivedump command to cancel a live dump.

Syntax


cancellivedump node_name

node_id

Parameters
node_name|node_id
Identifies the node name or ID.

Description

Use this command if you issue a preplivedump command, but then decide not to issue a triggerlivedump
command. This releases the resources you allocated for the livedump. This event is located in the node
trace (.trc) file. For this command to succeed, the node must be in a livedump prepared state.

A invocation example
cancellivedump node1

The resulting output

No feedback

lslivedump
The lslivedump command queries the livedump state of a node.

Syntax


lslivedump node_name

node_id

Parameters
node_name|node_id
Identifies the node name or ID.

Description

You can issue this command repeatedly to determine if a livedump is in progress for the node. The
following table describes the possible outputs:

© Copyright IBM Corp. 2003, 2012 365

Table 50. lslivedump outputs
Attribute Description
inactive The node has no livedump activity.
prepared The node is ready to be triggered.
dumping The node is writing the dump file.

A invocation example
lslivedump node1
status
prepared

The resulting output

No feedback

preplivedump
The preplivedump command reserves the system resources that are required for livedump.

Syntax


preplivedump node_name

node_id

Parameters
node_name|node_id
Identifies the node name or ID.

Description

You can prepare more than one node for livedump at a time by issuing the preplivedump command
consecutively. However, you can only trigger one livedump at a time, with an automatic lag time of 30
seconds between each trigger event. This helps maintain node stability.

You can issue multiple preplivedump commands on the same node; however, only a preplivedump
command followed by a triggerlivedump command results in output.

Because the livedump resource allocation can take time to execute, you can issue this command to
prepare the livedump but trigger it at a later time. This command times out after 60 seconds. The
preplivedump event is located in the node trace (.trc) file.

A invocation example
preplivedump node1

The resulting output

No feedback

triggerlivedump
The triggerlivedump command captures the metadata that you want to dump, and writes the dump file
to the internal disk on the node.

366 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


triggerlivedump node_name

node_id

Parameters
node_name|node_id
Identifies the node name or ID.

Description

You can issue this command to trigger a livedump command. Only one triggerlivedump action can be in
progress at one time, with an automatic lag time of 30 seconds between each trigger event. The node
must have a livedump state of prepared for this command to succeed. Output is recorded in the node
trace (.trc) file.

After you issue the triggerlivedump command, the command captures data and returns you to the CLI
interface so that you can issue additional commands. While you issue additional commands, the
livedump disk file is written to the disk in the background, and the livedump state shows as dumping.
After the write is complete, the state shows as inactive.

A invocation example
triggerlivedump node1

The resulting output

No feedback

Chapter 18. Livedump commands 367

368 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 19. Managed disk commands
The managed disk commands enable you to work with managed disk options with the SAN Volume
Controller.

If the clustered system (system) detects an MDisk, it automatically adds it to the list of known MDisks. If
you subsequently delete the RAID that corresponds to the MDisk, the system only deletes the MDisk
from the list if the MDisk is offline and it has a mode of unmanaged (it does not belong to an MDisk
group).

applymdisksoftware (Discontinued)
Attention: The applymdisksoftware command has been discontinued. Use the applydrivesoftware
command to upgrade drives.

chmdisk
Use the chmdisk command to modify the name of a managed disk (MDisk).

Syntax


chmdisk mdisk_id

-name new_name_arg -tier generic_ssd mdisk_name
generic_hdd

Parameters
-name new_name_arg
(Required) Specifies the new name to be applied to the managed disk.
e -tiergeneric_ssd | generic_hhd
e (Optional) Specifies the new tier of the MDisk.
mdisk_id | mdisk_name
(Required) Specifies the ID or name of the managed disk to modify.

Description

This command modifies the attributes of a managed disk.

Note: If you do not specify a new name the command cannot complete. Also, you do not use this
command to change the tier.

An invocation example
chmdisk -tier generic_hdd mdisk13

The resulting output

No feedback

chquorum
Use the chquorum command to change the quorum association.

© Copyright IBM Corp. 2003, 2012 369

Syntax


chquorum

-active -mdisk mdisk_id -override yes|no
mdisk_name
-drive drive_id

quorum_id


Parameters
-active
(Optional) Makes the specified quorum ID the active one. The active parameter must be used if
neither the mdisk nor the drive parameters are specified.
-mdisk mdisk_id | mdisk_name | -drive drive_id
(Optional) Specifies the MDisk or drive to be this quorum ID.

Note: SAN Volume Controller uses MDisks only.

quorum_id
(Required) Specifies which quorum ID to change. Permitted values are values are 0, 1, and 2.
-override yes|no
Enables the automatic quorum selection to be overridden. In this state, the quorum disk is only
moved if the resources are offline. Do not use this parameter unless a specific quorum disk is
required for the configuration.

Description

Use the chquorum command to change the quorum association. To identify the drive or MDisk that is the
current active quorum disk, use the lsquorum command.

Note: SAN Volume Controller uses MDisks only.

Attention: Only assign quorum to drives in the control enclosure or to external MDisks. Some
maintenance procedures require that quorum is moved temporarily to expansion enclosures. Once that
procedure is complete, return the quorum drives to the control enclosure.

The chquorum command is not synchronous, but usually takes only a few seconds to complete. In some
situations it can take several minutes.

The clustered system (system) uses the quorum disk or drive as a tie breaker when exactly half of the
nodes that were previously a member of the system are present.

The use of a quorum disk or drive allows the system to manage a SAN fault that splits the system
exactly in half. One half of the system continues to operate and the other half stops until SAN
connectivity is restored.

There is only one quorum disk or drive; however, the system uses three as quorum candidates. The
system selects the actual quorum disk or drive from the pool of quorum candidates. The quorum
candidates also hold a copy of important system metadata. Just over 256 MB is reserved for this purpose
on each quorum candidate disk. When using an MDisk as quorum disk, this space is allocated from the
storage pool. The number of extents required depends on the extent size for the managed disk group
containing the MDisk. Table 51 on page 371 provides the number of extents reserved for quorum use by
extent size.

370 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 51. Number of extents reserved by extent size
Extent size (MB) Number of extents reserved for quorum use
16 17
32 9
64 5
128 3
256 2
512 1
1024 1
2048 1
4096 1
8192 1

When you issue this command, the MDisk or drive that currently is assigned the quorum index number
is set to a nonquorum disk. The system automatically assigns quorum indexes.

You can set the active quorum disk or drive with the active parameter. This can be useful in a system
configuration to ensure that the most highly-available quorum disk or drive is used.

An invocation example
chquorum -mdisk 45 2

The resulting output

No feedback

dumpallmdiskbadblocks
The dumpallmdiskbadblocks command dumps bad block counts to a dump file for use by fix procedures
and the satask snap command.

Syntax


dumpallmdiskbadblocks


Parameters

None

Description

Use the dumpallmdiskbadblocks command to dump bad block counts to a readable ASCII dump file for
use by fix procedures and the satask snap command. The output contains bad blocks for which an error
log has been raised.

Use lsdumps -prefix /dumps/mdisk to list the output files. Use cleardumps -prefix /dumps/mdisk to clear
the output files.

The maximum number of dump files is 20.

An invocation example

Chapter 19. Managed disk commands 371

dumpallmdiskbadblocks

The resulting output if MDisk 2 and MDisk 5 have bad blocks

Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC

Mdisk id: 2
Mdisk name: mdisk2
Number of bad blocks: 4

Mdisk id: 5
Mdisk name: mdisk 5
Number of bad blocks: 1

Total mdisks with bad blocks: 2

Total number of bad blocks: 5

The resulting output if the MDisks have no bad blocks

Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC

Total mdisks with bad blocks: 0

Total number of bad blocks: 0

dumpmdiskbadblocks
The dumpmdiskbadblocks command writes the bad block counts and locations that are on a specified
MDisk to a dump file for use by fix procedures.

Syntax


dumpmdiskbadblocks object_id

object_name

Parameters
object_id | object_name
(Required) Specifies the MDisk for which you need to dump the bad block record table.

Description

Use the dumpmdiskbadblocks command to write the bad block counts and locations that are on a specified
MDisk to a readable ASCII dump file for use by fix procedures. The output consists of bad blocks for
which an error log has been raised.

Use lsdumps -prefix /dumps/mdisk to list the output files. Use cleardumps -prefix /dumps/mdisk to clear
the output files.

The reported error log sequence numbers correspond to the first error seen in the bad block record,
which is a 512-block region.
v If there are multiple error logs in the same region, the earliest error sequence is used.
v If there are error logs of different types in the same region, error sequence numbers for bad blocks
caused by medium errors on RAID member drives take precedence.
v If a range of bad blocks runs across record boundaries, the sequence number corresponding to the last
record is used.

The maximum number of dump files is 20.

372 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
An invocation example
dumpmdiskbadblocks 3

The resulting output if the MDisk has bad blocks

Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC

Mdisk id: 3
Mdisk name: mdisk3
Number of bad blocks: 6

Start LBA: 0x1234123412341234

Length: 2
Error log sequence number: 1

Start LBA: 0x5678567812341234

Length: 4
Error log sequence number: 2

The resulting output if the MDisk has no bad blocks

Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC

Mdisk id: 3
Mdisk name: mdisk3
Number of bad blocks: 0

includemdisk
Use the includemdisk command to include a disk that has been excluded by the cluster.

Syntax


includemdisk mdisk_id

mdisk_name

Parameters
mdisk_id | mdisk_name
(Required) Specifies the ID or name of the managed disk to add back into the cluster.

Description

The specified managed disk is included in the cluster.

You might exclude a disk from the cluster because of multiple I/O failures. These failures might be
caused by noisy links. Once a fabric-related problem has been fixed, the excluded disk can be added back
into the cluster.

Running this command against an MDisk might change its state, whether the state is reported as
excluded.

Note: If an MDisk is in the excluded state, is offline, and does not belong to an MDisk group, issuing an
include command for this MDisk results in the MDisk record being deleted from the cluster.

An invocation example
includemdisk mdisk5

Chapter 19. Managed disk commands 373

The resulting output
No feedback

setquorum (Deprecated)
Attention: The setquorum command is deprecated. Use the chquorum command to change the quorum
association.

triggermdiskdump (Discontinued)
Attention: The triggermdiskdump command is discontinued. Use the triggerdrivedump command to
collect support data from a disk drive.

374 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 20. Managed disk group commands
The following commands enable you to work with managed disk group options with the SAN Volume
Controller.

addmdisk
The addmdisk command adds one or more managed disks to an existing managed disk group.

Syntax


addmdisk -mdisk mdisk_id_list

mdisk_name_list -tier generic_ssd
generic_hdd

mdisk_group_id

mdisk_group_name

Parameters
-mdisk mdisk_id_list | mdisk_name_list
(Required) Specifies one or more managed disk IDs or names to add to the group.
-tier
Specifies the tier of the MDisk or MDisks being added.
Unless otherwise specified, the current tier value associated with the MDisk will be retained. The
default value for a newly discovered unmanaged MDisk is generic_hdd. You can change this value by
using the chmdisk command.
External SSDs cannot be detected automatically. If you want external SSDs to be known by the
system, you must either specify the tier when adding the managed disk to the mdisk group, or use
the chmdisk command.
mdisk_group_id | mdisk_group_name
(Required) Specifies the ID or name of the managed disk group to add the disks to. When an MDisk
is added, the warning threshold for the MDisk group is automatically scaled.

Description

This command adds the managed disks that you specify to the group. The disks can be specified in terms
of the managed disk ID or the managed disk name.

The managed disks must be in unmanaged mode. Disks that already belong to a group cannot be added
to another group until they have been deleted from their current group. You can delete a managed disk
from a group under the following circumstances:
v If the managed disk does not contain any extents in use by a virtual disk
v If you can first migrate the extents in use onto other free extents within the group.

An invocation example
addmdisk -mdisk mdisk13:mdisk14 -tier generic_ssd Group0

The resulting output

No feedback

© Copyright IBM Corp. 2003, 2012 375

chmdiskgrp
Use the chmdiskgrp command to modify the name that is assigned to a managed disk (MDisk) group or
to set the warning threshold for the MDisk group.

Syntax


chmdiskgrp -name new_name_arg

-warning disk_size | disk_size_percentage % -unit b
kb
mb
gb
tb
pb

mdisk_group_name

-easytier auto mdisk_group_id
on
off

Parameters
-name new_name_arg
Specifies the new name of the managed disk group.
-warning disk_size | disk_size_percentage%
(Optional) Sets a threshold at which a warning is generated. The warning is generated the first time
that the threshold is exceeded by the used-disk capacity in the MDisk group. You can specify a
disk_size integer, which defaults to megabytes (MB) unless the -unit parameter is specified; or you can
specify a disk_size%, which is a percentage of the MDisk group size. To disable warnings, specify 0 or
0%.
-unit b | kb | mb | gb | tb | pb
(Optional) Specifies the data units for the -warning parameter.
mdisk_group_id | mdisk_group_name
(Required) Specifies the ID or name of the managed disk group to modify.
-easytier
Specifies if the Easy Tier function is on or off for this MDisk group, or if it is automatically
determined.

Note: -easytier must be followed by one of the following:

v If -easytier is set to auto, SAN Volume Controller automatically enable Easy Tier functions when
the MDisk group contains MDisks from more than one tier, and disable automatic data placement
when the MDisk group contains MDisks from only one tier.
v If -easytier is set to on, then Easy Tier functions are active.
v If -easytier is set to off, then Easy Tier functions are inactive.

Description

This command modifies the name, or label, assigned to a given managed disk group. Subsequently, you
can use the new name to refer to the managed disk group.

376 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
The command can also be used to set the warning threshold for the managed disk group. The warning
threshold is the threshold at which a warning is generated when it is exceeded by the used-disk capacity
in the MDisk group.

An invocation example
chmdiskgrp -name testmdiskgrp -easytier on Group0

The resulting output

No feedback

mkmdiskgrp
The mkmdiskgrp command creates a new managed disk group (storage pool).

Syntax


mkmdiskgrp

-name new_name_arg -mdisk mdisk_id_list
mdisk_name_list

-ext extent_size

-tier generic_ssd
generic_hdd

-warning disk_size | disk_size_percentage % -unit b
kb
mb
gb
tb
pb


-easytier auto
on
off

Parameters
-name new_name_arg
(Optional) Specifies a name to assign to the new group.
-mdisk mdisk_id_list | mdisk_name_list
(Optional) Specifies a colon-separated list of managed disk IDs or names to add to the group. You
can create an empty MDisk group by not specifying the -mdisk parameter.
-ext extent_size
(Required) Specifies the size of the extents for this group in MB. The ext parameter must have one of
the following values: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, or 8192 (MB).
-warning disk_size | disk_size_percentage%
(Optional) Generates a warning when the used disk capacity in the MDisk group first exceeds the
specified threshold. You can specify a disk_size integer, which defaults to megabytes (MB) unless the
-unit parameter is specified; or you can specify a disk_size%, which is a percentage of the MDisk
group size. To disable warnings, specify 0 or 0%. The default value is 0.
-unit b | kb | mb | gb | tb | pb
(Optional) Specifies the data units for the -warning parameter.

Chapter 20. Managed disk group commands 377

 -tier
(Optional) Specifies the tier of the MDisk or MDisks being added. If you do not specify a tier, the
current tier value of the MDisk is retained. The default value for an external MDisk is generic_hdd.
e -easytiergeneric_ssd | generic_hhd
e Specifies if the Easy Tier function is active for this MDisk group, or if it is automatically determined.
e Auto is the default value.

e Note:
e v If -easytier is set to auto, SAN Volume Controller automatically enables Easy Tier functions when
e the MDisk group contains MDisk from more than one tier, and will disable Easy Tier functions
e when the MDisk group contains MDisk from only one tier.
e v If -easytier is set to on, then Easy Tier functions will be active.
e v If -easytier is set to off, then Easy Tier functions will be inactive.

e Description

The mkmdiskgrp command creates a new managed disk group and assigns the group name if specified.
The ID of the new group is returned if the command is successful. Managed disk groups are collections
of managed disks. Each group is divided into chunks, called extents, which are used to create
VDisks(volumes).

Optionally, you can specify a list of managed disks that will be added to this group. These managed
disks cannot belong to another group, and they must have a mode of unmanaged. Use the
lsmdiskcandidate command to get a list of suitable candidates. If -tier is specified, it will apply to all of
the MDisks.

Each managed disk that is a member of this group is split into extents. The storage that is available on
these disks is added to a pool of extents that is available in this group. When a virtual disk is created
from this group, free extents from the pool are used, in accordance with the policy used when the virtual
disk was first created.

All managed disks subsequently added to this group are split into extents of the same size as the size
that is assigned to the group.

When choosing an extent size, take into account the amount of storage you want to virtualize in this
group. The system maintains a mapping of extents between virtual disks and managed disks. The
clustered system (system) can only manage a finite number of extents (4 194 304). One system can
virtualize the following number of extents:
v 64 TB – if all managed disk groups have extent sizes of 16 MB.
v 32 PB – if all managed disk groups have extent sizes of 8192 MB.

Important: The extent size for the MDisk group can also limit volume size. Consider the maximum
volume size you want to use when creating MDisk groups. Refer to the information on creating MDisk
groups for a comparison of the maximum volume capacity for each extent size. The maximum is different
for space-efficient thin-provisioned volumes.

Note: When an image mode volume is created, the MDisk group increases in capacity by the size of the
image mode volume (not the MDisk capacity), because the image mode volume might be smaller than
the MDisk itself. If an extent is migrated from the image mode volume or MDisk to elsewhere in the
group, the volume becomes a striped volume (no longer image mode). At this point the available capacity
might increase, because the extra capacity available on the MDisk (for example, the capacity that was not
part of the image mode volume) becomes available.

An invocation example

378 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 mkmdiskgrp -mdisk mdisk13 -tier generic_hdd -easytier off -ext 512

The resulting output

e MDisk Group, id [13], successfully created

An invocation example
mkmdiskgrp -mdisk mdisk0:mdisk1:mdisk2:mdisk3 -ext 32

The resulting output

MDisk Group, id [0], successfully created

rmmdisk
The rmmdisk command deletes a managed disk (MDisk) from a managed disk group.

Syntax


rmmdisk -mdisk mdisk_id_list mdisk_group_id

mdisk_name_list -force mdisk_group_name

Parameters
-mdisk mdisk_id_list | mdisk_name_list
(Required) Specifies one or more managed disk IDs or names to delete from the group.
-force
(Optional) Migrates data on the specified disks to other disks in the group. The command completes
asynchronously if -force is specified.
mdisk_group_id | mdisk_group_name
(Required) Specifies the ID or name of the managed disk group to delete the disks from. The warning
threshold for an MDisk group is automatically scaled when MDisks are deleted.

Description

This command attempts to remove the managed disk or disks from the group.

Deleting a managed disk from a group can only be done if the managed disk does not contain any
extents in use by a virtual disk. If there are extents in use and you do not supply the force flag, the
command fails.

Attention: If this disk being removed has already been powered down, removed, or is experiencing a
power outage, the migration is pending and does not complete until the MDisk comes back online. The
MDisk is not removed from the list of MDisks that are contained in the group.

If the disk has been deliberately removed, the only method of removing the MDisk is to remove the
entire group itself.

Ensure that you do not destroy any controller LUNs until you have deleted them from the MDisk group
that they belong to.

The rmmdisk command fails if there are insufficient free extents on other disks in the mdisk group for
the duration of the command.

Chapter 20. Managed disk group commands 379

If you do specify the force flag, an attempt will be made to migrate the extents that are in use onto other
free extents within the group. If there are not enough free extents in the group, the command will fail
even if the force flag is specified.

When an array MDisk is in a storage pool, five extents in the storage pool are reserved for internal use. If
you attempt to remove an MDisk when an array MDisk is in the storage pool, the command will fail
(even if the -force flag is specified), if five free extents do not remain in the storage pool.

To delete the disks from the group, you have the following options:
v You can delete the virtual disk that is using the extents specified on the managed disk.
v You can add more managed disks to the group, rerun the command and specify the -force parameter.

When data is being migrated from the managed disk, it might take some time for the command to
complete. The command itself will return with a success code, notifying you that migration is in progress.
An event is logged when the migration is complete and the disk is deleted from the group at this time.
You can also check the progress of any active migrations by running the lsmigrate command.

If the -force parameter is used, the rmmdisk command fails if offline Managed Disks or no online
quorum disks will prevent the migration. Correct the offline or quorum disk condition and try reissuing
the command.

An invocation example
rmmdisk -mdisk mdisk12 -force Group3

The resulting output

No feedback

rmmdiskgrp
The rmmdiskgrp command deletes a managed disk group so that there is no possibility to recover it.

Syntax


rmmdiskgrp mdisk_group_id

-force mdisk_group_name

Parameters
-force
(Optional) Specifies that all virtual disks and virtual disk-to-host mappings be deleted.

Attention: Use this parameter with extreme caution. When you use this parameter, all managed
disks in the group are removed and the group itself is deleted.
mdisk_group_id | mdisk_group_name
(Required) Specifies the ID or name of the managed disk group that is to be deleted.

Description

The rmmdiskgrp command deletes the specified managed disk group. The -force parameter is required if
there are virtual disks that have been created from this group or if there are managed disks in the group.
Otherwise, the command fails.

Deleting a managed disk group is essentially the same as deleting a clustered system (system) or part of
a system, because the managed disk group is the central point of control of virtualization. Because virtual

380 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
disks are created using available extents in the group, mapping between virtual disk extents and
managed disk extents is controlled based on the group.

The command deletes all volume copies in the specified MDisk group. If the volume has no remaining
synchronized copies in other MDisk groups, the volume is also deleted.

Attention:
1. This command partially completes asynchronously. All virtual disks, host mappings, and Copy
Services relationships are deleted before the command completes. The deletion of the managed disk
group then completes asynchronously.
2. Before you issue the command, ensure that you want to delete all mapping information; data that is
contained on virtual disks cannot be recovered after the managed disk group has been deleted.

In detail, if you specify the -force parameter and the virtual disks are still using extents in this group, the
following actions are initiated or occur:
v The mappings between that disk and any host objects and the associated Copy Services relationships
are deleted.
v If the virtual disk is a part of a FlashCopy mapping, the mapping is deleted.

Note: If the mapping is not in the idle_or_copied or stopped states, the mapping is force-stopped and
then deleted. Force-stopping the mapping might cause other FlashCopy mappings in the system to also
be stopped. See the description for the -force parameter in the stopfcmap command for additional
information.
v Any virtual disk that is in the process of being migrated into or out of the managed disk group is
deleted. This frees up any extents that the virtual disk was using in another managed disk group.
v Virtual disks are deleted without first flushing the cache. Therefore, the storage controller LUNs that
underlie any image mode MDisks might not contain the same data as the image mode volume prior to
the deletion.
v If there are managed disks in the group, all disks are deleted from the group. They are returned to the
unmanaged state.
v The group is deleted.

Attention: If you use the -force parameter to delete all the managed disk groups in your system, you
are returned to the processing state where you were after you added nodes to the system. All data that is
contained on the virtual disks is lost and cannot be recovered.

An invocation example
rmmdiskgrp -force Group3

The resulting output

No feedback

Chapter 20. Managed disk group commands 381

382 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 21. Metro Mirror and Global Mirror commands
The Copy Service commands enable you to work with the Metro Mirror and Global Mirror services that
the SAN Volume Controller provides.

chpartnership
The chpartnership command modifies the bandwidth of the partnership between the local clustered
system (system) and the remote system that is specified in the command. This affects the bandwidth that
is available for background copy in a system partnership by either Metro Mirror or Global Mirror
operations. This command can also be used to disable and re-enable the partnership, to permit the local
system to be disconnected and then reconnected to the remote system.

Syntax


chpartnership

-bandwidth bandwidth_in_mbps -start
-stop

remote_cluster_id

remote_cluster_name

Parameters
-bandwidth bandwidth_in_mbps
(Optional) Specifies the new bandwidth in megabytes per second (MBps). This bandwidth is used to
cap the background remote copy progress. Set the bandwidth to the maximum rate that the remote
copies should resynchronize at. Write operations from the host add to the use of the system link. If
this parameter is set to a value that is greater than the inter-system links can sustain, the actual copy
rate defaults to what is available on the link.
-start | -stop
(Optional) Starts or stops a Metro Mirror or Global Mirror partnership. To start or stop a partnership,
run the chpartnership command from either system.
remote_cluster_id | remote_cluster_name
(Required) Specifies the system ID or name of the remote system. The intra-system bandwidth cannot
be modified, so if you enter the local system name or ID, an error occurs.

Description

This command modifies the bandwidth of the partnership between the local system and the remote
system that is specified in the command. This affects the bandwidth that is available for a background
copy in Metro Mirror or Global Mirror relationships, in the direction from the local to the remote system.
To modify the background copy bandwidth in the other direction (remote system–> local system), it is
necessary to issue the corresponding chpartnership command to the remote system.

When you stop the system partnership, you temporarily disable the partnership and disconnect the local
system from the remote system. The configuration is retained. The system partnership must be in either
the partially_configured_stopped or fully_configured_stopped states to be started.

An invocation example
chpartnership -bandwidth 20 cluster1
chpartnership -stop cluster1

© Copyright IBM Corp. 2003, 2012 383

The resulting output
No feedback

chrcconsistgrp
The chrcconsistgrp command modifies the name of an existing Metro Mirror or Global Mirror
consistency group.

Syntax


chrcconsistgrp

-name new_name_arg -cycleperiodseconds period

rc_consist_group_name

-cyclingmode none rc_consist_group_id
multi

Parameters
-name new_name_arg
(Optional) Specifies the new name to assign to the consistency group.
-cycleperiodseconds period
(Optional) Specifies the cycle period in seconds. The minimum cycle period value is 60 seconds, and
the default is 300 seconds.
This defines an optional cycle period that applies to Global Mirror relationships with a cycling mode
of multi. A Global Mirror relationship using the multi cycling_mode performs a complete cycle each
period. It might be provided for any relationship, but cannot be used for none when considering
Metro or Global Mirror relationships.
-cyclingmode none | multi
(Optional) Specifies the behavior of Global Mirror for this relationship.
v Specifying none, the default, gives identical behavior to Global Mirror in previous versions of SAN
Volume Controller.
v Specifying multi uses the cycling protocol.
To start a relationship with cycling_mode set to multi, change volumes must be defined for the
relationship.

Note: The cycling_mode can only be changed when the relationship is stopped and in
consistent_stopped or inconsistent_stopped states.
rc_consist_group_name | rc_consist_group_id
(Required) Specifies the ID or existing name of the consistency group that you want to modify.

Description

This command changes the name of the specified consistency group.

Note:
v All parameters are mutually-exclusive.
v One of the optional parameters must be specified.
v A Global Mirror consistency group with cycling mode set to multi requires that a change volume be
defined for the secondary volume of each relationship in the group before it can be started.
v For intersystem relationships the -cycleperiodseconds and -cyclingmode parameters can only be
specified when the two systems are connected. If the two systems become disconnected while the
384 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 command is being processed, then the command might be completed with the change having been
performed at the system that received the task invocation only (and the other system is updated upon
re-connection).

An invocation example

Change the name of the consistency group called rc_testgrp to rctestone.

chrcconsistgrp -name rctestone rc_testgrp

The resulting output

No feedback

chrcrelationship
The chrcrelationship command enables you to modify certain attributes of an existing relationship, such
as to add a relationship to a consistency group, to remove a relationship from a consistency group, and to
change the name of the relationship. You can only change one attribute at a time per command submittal.

Syntax


chrcrelationship

-masterchange
master_change_vdisk_id
master_change_vdisk_name

-auxchange -nomasterchange -noauxchange
aux_change_vdisk_id
aux_change_vdisk_name

-consistgrp consist_group_id

-name new_name_arg consist_group_name -force

-noconsistgrp -cycleperiodseconds period -cyclingmode none
multi

rc_rel_id

rc_rel_name

Parameters
-masterchange master_change_vdisk_id | master_change_vdisk_name
(Optional) Specifies a change volume association for the master volume in the relationship.
-auxchange aux_change_vdisk_id | aux_change_vdisk_name
(Optional) Specifies a change volume association for the auxiliary volume in the relationship.
-nomasterchange
(Optional) Specifies a defined change volume on the master volume should be removed from the
relationship.
-noauxchange
(Optional) Specifies a defined change volume on the auxiliary volume should be removed from the
relationship.

Note: To use this parameter the specified flash volume must no longer be in use by the relationship.

Chapter 21. Metro Mirror and Global Mirror commands 385

 -name new_name_arg
(Optional) Specifies a new label to assign to the relationship.
This parameter is required if you do not specify the -consistgrp or -force parameter.
-consistgrp consist_group_id | consist_group_name
(Optional) Specifies a new consistency group to assign the relationship to. Only relationships of the
same copy type (Global or Metro Mirror) can be assigned to the same consistency group. You cannot
use this parameter with the -name, or -force parameters.
This parameter is required if you do not specify the -name or -force parameter.
e -force
e Specifies that you want the system to process the copy operation even if it might lead to a temporary
e loss of consistency while synchronization occurs. This parameter is required if the consistency group
e is in the ConsistentStopped state, but is not synchronized or is in the Idling state, but is not
e synchronized.
-noconsistgrp
(Optional) Specifies no consistency should be assigned a relationship, and also that you want the
system to remove the relationship from a consistency group, making the relationship a stand-alone
relationship. You cannot use this parameter with the -name or -consistgrp parameters.
This parameter is required if you do not specify the -name or -consistgrp parameter.
-cycleperiodseconds period
(Optional) Specifies the cycle period in seconds. The minimum cycle period value (and default) is 300
seconds.
e This defines an optional cycle period that applies to Global Mirror relationships with a cycling mode
e of multi. A Global Mirror relationship using the multi cycling_mode performs a complete cycle at
e most once each period. It might be provided for any relationship, but cannot be used for none , single,
e Metro, or Global Mirror relationships.
-cyclingmode none | multi
(Optional) Specifies the behavior of Global Mirror for this relationship.
v Specifying none, the default, gives identical behavior to Global Mirror in previous versions of SAN
Volume Controller.
v Specifying multi uses the cycling protocol.
To start a relationship with cycling_mode set to multi, change volumes must be defined for the
relationship.

Note: The cycling_mode can only be changed when the relationship is stopped and in
consistent_stopped or inconsistent_stopped status.
rc_rel_name | rc_rel_id
(Required) Specifies the ID or name of the relationship.

Description

This command modifies the specified attributes of the supplied relationship, one attribute at a time. In
addition to changing the name of a consistency group, this command can be used for the following
purposes.

Remember:
v All parameters are mutually-exclusive.
v One of the optional parameters must be specified.

386 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 v You can add a stand-alone relationship to a consistency group by specifying the -consistgrp parameter
and the name or ID of the consistency group. The relationship and consistency group must be
connected when the command is issued and must share the following components:
– Master system
– Auxiliary system
– State (unless the group is empty)
– Primary (unless the group is empty)
– Type (unless the group is empty)
– Cycling mode (unless the group is empty)
e When the first relationship is added to an empty group, the group takes on the same state, primary
e (copy direction), type (Metro or Global Mirror), and cycling mode as the relationship. Subsequent
relationships must have the same state, copy direction, and type as the group in order to be added to
it. A relationship can only belong to one consistency group.
v You can remove a relationship from a consistency group by specifying the -noconsistgrp parameter
and the name or ID of the relationship. Although you do not have to specify or confirm the name of
the consistency group, verify which group the relationship belongs to before you issue this command.
This form of the modify relationship command succeeds in the connected or disconnected states. If the
systems are disconnected the relationship is only removed from the consistency group on the local
system, at the time the command is issued. When the systems are reconnected the relationship is
automatically removed from the consistency group on the other system. Alternatively, you can issue an
explicit modify (chrcrelationship) command to remove the relationship from the group on the other
system while it is still disconnected.

Note: If you remove all relationships from the group, the relationship type is reset to empty_group.
When you add a relationship to the empty group, the group again takes on the same type as the
relationship.
v To move a relationship between two consistency groups, you must issue the chrcrelationship
command twice. Use the -noconsistgrp parameter to remove the relationship from its current group,
and then use the -consistgrp parameter with the name of the new consistency group.

For intersystem relationships

v The -name, -consistgrp, -cycleperiodseconds and -cyclingmode parameters can only be specified
when the two systems are connected. If the two systems become disconnected while the command is
being processed, then the command might be completed with the change having been performed at the
system that received the task invocation only (and the other system is updated upon re-connection).
The -cycleperiodseconds and -cyclingmode parameters can only be specified on stand-alone
relationships (not members of a consistency group).
e v The -masterchange and -nomasterchange parameters can only be specified when running the
e chrcrelationship command on the master system for the relationship, and the -auxchange and
e -noauxchange parameters can only be specified when running the chrcrelationship command on the
e auxiliary system for the relationship.

Remember: You cannot specify a master and auxiliary change volume in the same command.

A change volume must be:

v Used by the relationship that owns it
v In the same I/O group (iogroup) as the associated master or auxiliary volume
v The same size as the associated master or auxiliary volume
A change volume is owned and used by the associated Remote Copy relationship. Consequently, it
cannot be:
v Mapped to a host

Chapter 21. Metro Mirror and Global Mirror commands 387

v Used as source or target of any FlashCopy maps
v Part of any other relationship
v A filesystem disk
Assigning a change volume to a relationship requires new Flash Copy mappings to be created between
the master or auxiliary volume and the associated change volume. Consequently, there must be sufficient
unallocated Flash Copy memory in the target I/O group or the command fails.

If the relationships cycle_period_seconds does not match that of the consistency group it is added to, the
newly-added relationship copies the cycle_period_seconds value from the group. If later removed from
the group, the copied cycle_period_seconds value remains.

When a Global Mirror relationship with a cycling_mode value of multi is added to a group that is not
empty, both the group and the relationship must be stopped.

An invocation example

Change the name of the relationship rccopy1 to testrel.

chrcrelationship -name testrel rccopy1

The resulting output

No feedback

An invocation example

Add relationship rccopy2 to group called newgroup.

chrcrelationship -consistgrp newgroup rccopy2

The resulting output

No feedback

An invocation example

Remove relationship rccopy3 from whichever consistency group it is a member of.

chrcrelationship -noconsistgrp rccopy3

The resulting output

No feedback

An invocation example
chrcrelationship -cyclingmode multi relB

The resulting output

No feedback

An invocation example
chrcrelationship -cycleperiodseconds 20 relC

The resulting output

No feedback

388 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 mkpartnership
e The mkpartnership command establishes a one-way Metro Mirror or Global Mirror relationship between
e the local clustered system (system) and a remote system. To establish a fully functional Metro Mirror or
e Global Mirror partnership, you must issue this command to both clustered systems (systems). This step is
e a prerequisite to creating Metro Mirror or Global Mirror relationships between volumes on the systems.

Syntax


mkpartnership -bandwidth bandwidth_in_mbps remote_system_id

remote_system_name

Parameters
-bandwidth bandwidth_in_mbps
(Required) Specifies the bandwidth, in megabytes per second (MBps), that is used by the background
copy process between the systems. It adjusts the bandwidth that is used by Metro Mirror or Global
Mirror for the initial background copy process. Set the bandwidth to a value that is less than or equal
to the bandwidth that can be sustained by the intersystem link. If the -bandwidth parameter is set to
a higher value than the link can sustain, the background copy process uses the actual available
bandwidth.
remote_system_id | remote_system_name
(Required) Specifies the system ID or name of the remote system. Issue the lspartnershipcandidate
command to list the remote systems that are available. If two or more remote systems have the same
name and the name is included in this command, the command fails and it requests the ID of the
system instead of the name.

Description

This command creates a one-way partnership between the local system and the remote system that you
specify in the command. To create a two-way partnership, the equivalent mkpartnership command must
be issued from the other system. The maximum supported number of systems in a partnership set is four.

Intersystem Mirror relationships can be created between primary volumes in the local system and
auxiliary volumes in the remote system. Intrasystem relationships can be created between volumes that
reside in a local system. The volumes must belong to the same I/O group within the system.

Note: Background copy bandwidth can impact foreground I/O latency. To set the background copy
bandwidth optimally, you must consider all three resources: the primary storage, intersystem link
bandwidth, and secondary storage. Provision the most restrictive of these three resources between the
background copy bandwidth and the peak foreground I/O workload.

An invocation example
mkpartnership -bandwidth 20 system1

The resulting output

No feedback

mkrcconsistgrp
The mkrcconsistgrp command creates a new, empty Metro Mirror or Global Mirror consistency group. If
the -system parameter is not specified, the consistency group is created on the local clustered system
(system) only.

Chapter 21. Metro Mirror and Global Mirror commands 389

 Syntax
e

mkrcconsistgrp

-name new_name -cluster cluster_id
cluster_name

Parameters
-name new_name
(Optional) Specifies a name for the new consistency group.
e -cluster cluster_id | cluster_name
e (Optional) Specifies the name or ID of the remote system. If -cluster is not specified, a consistency
e group is created only on the local system.

Description

This command creates a new consistency group. The ID of the new group is displayed after the
command processes. The name must be unique across all consistency groups that are known to the
systems within this consistency group. If the consistency group involves two system, the systems must be
in communication throughout the create process.

The new consistency group does not contain any relationships and will be in the empty state. You can
add Metro Mirror or Global Mirror relationships to the group using the chrcrelationship command.

Remember: Names representing Metro Mirror or Global Mirror consistency groups relationships are
restricted to fifteen characters in length (not sixty-three for an extended character set).

An invocation example
mkrcconsistgrp -name rc_testgrp

The resulting output

RC Consistency Group, id [255], successfully created

mkrcrelationship
The mkrcrelationship command creates a new Global or Metro Mirror relationship with volumes in the
same clustered system (system), forming an intrasystem relationship or intersystem relationship (if it
involves more than one clustered system).

Syntax


mkrcrelationship -master master_vdisk_id -aux aux_vdisk_id

master_vdisk_name aux_vdisk_name

-system system_id

system_name -name new_name_id

-consistgrp consist_group_id -sync -global
consist_group_name

390 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide



-cyclingmode
none
multi

Parameters
-master master_vdisk_id | master_vdisk_name
(Required) Specifies the ID or name of the master_vdisk_id or master_vdisk_name.
-aux aux_vdisk_id | aux_vdisk_name
(Required) Specifies the ID or name of the aux_vdisk_id or aux_vdisk_name.
-system system_id | system_name
(Required) Specifies the ID or name of the remote cluster.
v If you are creating an intrasystem relationship, enter the ID of the local system. The volumes in the
relationship must belong to the same I/O group within the system.
v If you are creating an intersystem relationship, enter the ID of the remote system. To create a
relationship in two different systems, the systems must be connected at the time that the
mkrcrelationship command is received.
-name new_name_id
(Optional) Specifies a label to assign to the relationship.
-consistgrp consist_group_id | consist_group_name
(Optional) Specifies a consistency group that this relationship joins. If you do not supply the
-consistgrp parameter, the relationship is created as a stand-alone relationship that can be started,
stopped, and switched on its own.

Note: Metro and Global Mirror relationships cannot belong to the same consistency group. When the
first relationship is added to the consistency group, the group takes on the same type as the
relationship. Subsequently, only relationships of that type can be added to the consistency group.
-sync
(Optional) Specifies that you want the system to create a synchronized relationship. The -sync
parameter guarantees that the master and auxiliary disks contain identical data at the point that the
relationship is created. You must ensure that the auxiliary disk is created to match the master disk
and that no input transactions take place to either disk before you issue the create command. The
initial background synchronization is skipped.
-global
(Optional) Specifies that you want the system to create a new Global Mirror relationship. If you do
not specify the -global parameter, a Metro Mirror relationship is created instead.
-cyclingmodenone | multi
(Optional) Specifies the behavior of Global Mirror for this relationship.
v Specifying none, the default, gives identical behavior to Global Mirror in previous versions of SAN
Volume Controller.
v Specifying multi uses the cycling protocol.
The minimum cycle period default value is 300 seconds. To start a relationship with cycling_mode set
to multi, change volumes must be defined for the relationship.

Description

This command creates a new Global or Metro Mirror relationship. A Metro Mirror relationship defines
the relationship between two volumes: a master volume and an auxiliary volume. This relationship
persists until it is deleted. The auxiliary virtual disk must be identical in size to the master virtual disk or
the command fails, and if both volumes are in the same system, they must both be in the same I/O

Chapter 21. Metro Mirror and Global Mirror commands 391

group. The master and auxiliary cannot be in an existing relationship. Any defined FlashCopy mappings
that have the proposed master volume as the target of the FlashCopy mapping must be using the same
I/O group as the master volume. Any defined FlashCopy mappings that have the proposed auxiliary
volume as the target of the FlashCopy mapping must be using the same I/O group as the auxiliary
volume.

Note: You cannot create a remote copy relationship with this command if the auxiliary volume is an
active FlashCopy mapping target.

The command also returns the new relationship ID.

Metro Mirror relationships use one of the following copy types:

v A Metro Mirror copy ensures that updates are committed to both the primary and secondary volumes
before sending confirmation of I/O completion to the host application. This ensures that the secondary
volume is synchronized with the primary volume in the event that a failover operation is performed.
v A Global Mirror copy allows the host application to receive confirmation of I/O completion before the
updates are committed to the secondary volume. If a failover operation is performed, the host
application must recover and apply any updates that were not committed to the secondary volume.

You can optionally give the relationship a name. The name must be a unique relationship name across
both systems.

The relationship can optionally be assigned to a consistency group. A consistency group ensures that a
number of relationships are managed so that, in the event of a disconnection of the relationships, the data
in all relationships within the group is in a consistent state. This can be important in, for example, a
database application where data files and log files are stored on separate volumes and consequently are
managed by separate relationships. In the event of a disaster, the primary and secondary sites might
become disconnected. As the disconnection occurs and the relationships stop copying data from the
primary to the secondary site, there is no assurance that updates to the two separate secondary volumes
will stop in a consistent manner if the relationships that are associated with the volumes are not in a
consistency group.

For proper database operation, it is important that updates to the log files and the database data are
made in a consistent and orderly fashion. It is crucial in this example that the log file volume and the
data volume at the secondary site are in a consistent state. This can be achieved by putting the
relationships that are associated with these volumes into a consistency group. Both Metro Mirror and
Global Mirror processing ensure that updates to both volumes at the secondary site are stopped, leaving
a consistent image based on the updates that occurred at the primary site.

If you specify a consistency group, both the group and the relationship must have been created using the
same master system and the same auxiliary system. The relationship must not be a part of another
consistency group. If the consistency group is empty, it acquires the type of the first relationship that is
added to it. Therefore, each subsequent relationship that you add to the consistency group must have the
same type.

If the consistency group is not empty, the consistency group and the relationship must be in the same
state. If the consistency group is empty, it acquires the state of the first relationship that is added to it. If
the state has an assigned copy direction, the direction of the consistency group and the relationship must
match that direction.

If you do not specify a consistency group, a stand-alone relationship is created.

392 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
If you specify the -sync parameter, the master and auxiliary virtual disks contain identical data at the
point when the relationship is created. You must ensure that the auxiliary is created to match the master
and that no data movement occurs to either virtual disk before you issue the mkrcrelationship
command.

If you specify the -global parameter, a Global Mirror relationship is created. Otherwise, a Metro Mirror
relationship is created instead.

A volume specified on the master and aux parameters must be used in a non-existing relationship. This
means it cannot be the master or auxiliary volume of an existing relationship.

An invocation example
mkrcrelationship -master vdisk1 -aux vdisk2 -name rccopy1
-cluster 0000020063432AFD

The resulting output

RC Relationship, id [28], successfully created

An invocation example
mkrcrelationship -master vdiskA -aux vdiskB
-cluster clusterB
-name new_rel
-global
-cyclingmode multi

The resulting output

RC Relationship, id [28], successfully created

rmpartnership
The rmpartnership command removes a Metro Mirror or Global Mirror partnership on one cluster.
Because the partnership exists on both clusters, it is necessary to run this command on both clusters to
remove both sides of the partnership. If the command is run on only one cluster, the partnership enters a
partially configured state on the other cluster.

Syntax


rmpartnership remote_cluster_id

remote_cluster_name

Parameters
remote_cluster_id | remote_cluster_name
(Required) Specifies the cluster ID or the name of the remote cluster.

Description

This command deletes one half of a partnership on a cluster. To remove the entire partnership, you must
run the command twice, once on each cluster.

Attention: Before running the rmpartnership command, you must remove all relationships and groups
that are defined between the two clusters. To display cluster relationships and groups, run the
lsrcrelationship and lsrcconsistgrp commands. To remove the relationships and groups that are
defined between the two clusters, run the rmrcrelationship and rmrcconsistgrp commands.

An invocation example
Chapter 21. Metro Mirror and Global Mirror commands 393
 rmpartnership cluster1

The resulting output

No feedback

rmrcconsistgrp
The rmrcconsistgrp command deletes an existing Metro Mirror or Global Mirror consistency group.

Syntax


rmrcconsistgrp rc_consist_group_id

-force rc_consist_group_name

Parameters
-force
e (Optional) Specifies that you want the system to remove any relationship belonging to a group before
e the consistency group is deleted. The relationship itself is not deleted; it becomes a stand-alone
e relationship.

e Note: The -force parameter must be used to delete a consistency group when the consistency group
e has any Metro Mirror or Global Mirror relationships that is associated with it. If you do not use the
e -force parameter, the command fails.
rc_consist_group_id | rc_consist_group_name
(Required) Specifies the ID or the name of the consistency group to delete.

Description

This command deletes the specified consistency group. You can issue this command for any existing
consistency group. If the consistency group is disconnected at the time that the command is issued, the
consistency group is only deleted on the cluster that is connected. When the clusters reconnect, the
consistency group is automatically deleted on the other cluster. Alternatively, if the clusters are
disconnected, and you still want to remove the consistency group on both clusters, you can issue the
rmrcconsistgrp command separately on both of the clusters.

If the consistency group is not empty, the -force parameter is required to delete the group. This removes
the relationships from the consistency group before the group is deleted. These relationships become
stand-alone relationships. The state of these relationships is not changed by the action of removing them
from the consistency group.

An invocation example
rmrcconsistgrp rctestone

The resulting output

No feedback

rmrcrelationship
The rmrcrelationship command deletes an existing Metro Mirror or Global Mirror relationship.

394 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


rmrcrelationship rc_rel_id

-force rc_rel_name

Parameters
-force
(Optional) Specifies that all of the mappings that are associated with a consistency group that you
want to delete are removed from the group and changed to stand-alone mappings. This parameter is
only required if the consistency group that you want to delete contains mappings.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or the name of the relationship.

Description

This command deletes the relationship that is specified.

Deleting a relationship only deletes the logical relationship between the two virtual disks; it does not
affect the virtual disks themselves.

If the relationship is disconnected at the time that the command is issued, the relationship is only deleted
on the clustered system (system) where the command is being run. When the systems reconnect, the
relationship is automatically deleted on the other system. Alternatively, if the systems are disconnected
and if you still want to remove the relationship on both systems, you can issue the rmrcrelationship
command independently on both of the systems.

If Global Mirror relationship using multicycling mode, and you attempt to delete the relationship without
enabling access first, specifying rmrcrelationship might fail with an error because the relationship does
not currently have a fully consistent secondary volume. Specifying -force overrides this test. This is not
the default behavior, and you can quiesce and delete the relationship in order to use the secondary
volume's data immediately. If the map is still performing the background copy to migrate data from the
change volume to the secondary volume, the changed volume and associated FlashCopy mappings
remain defined when rmrcrelationship completes. The FlashCopy mappings are deleted after the
background copy completes, and the change volume becomes unusable again.

If you delete an inconsistent relationship, the secondary virtual disk becomes accessible even though it is
still inconsistent. This is the one case in which Metro or Global Mirror does not inhibit access to
inconsistent data.

An invocation example
rmrcrelationship rccopy1

The resulting output

No feedback

startrcconsistgrp
The startrcconsistgrp command starts the Global or Metro Mirror consistency group copy process, sets
the direction of copy if it is undefined, and optionally marks the secondary volumes of the consistency
group as clean.

Chapter 21. Metro Mirror and Global Mirror commands 395

Syntax


startrcconsistgrp

-primary master -force -clean
aux

rc_consist_group_id

rc_consist_group_name

Parameters
-primary master | aux
(Optional) Specifies the copy direction by defining whether the master or auxiliary disk becomes the
primary (source). This parameter is required when the primary is undefined if, for example, the
consistency group is in the Idling state.
-force
(Optional) Specifies that you want the system to process the copy operation even if it might lead to a
temporary loss of consistency while synchronization occurs. This parameter is required if the
consistency group is in the ConsistentStopped state, but is not synchronized or is in the Idling state,
but is not synchronized.
-clean
(Optional) Specifies that the volume that is to become a secondary is clean for each of the
relationships belonging to the group; any changes made on the secondary volume are ignored, and
only changes made on the clean primary volume are considered during synchronization of the
primary and secondary disks. The consistency group must be in an Idling (connected) state for this
parameter to work.

Attention: This flag should only be used when the primary and secondary volumes contain
identical data. Otherwise, relationships that are not consistent are reported as consistent. Once this
has been done there is no method to determine whether these volumes ever reach a true consistent
state until a full background copy can be carried out again.
rc_consist_group_id | rc_consist_group_name
(Required) Specifies the ID or name of the consistency group to start.

Description

This command starts a Global or Metro Mirror stand-alone consistency group. You cannot use this
command to start a remote copy relationship if the primary volume is a target volume of a prepared
FlashCopy mapping.

This command can only be issued to a consistency group that is connected. For a consistency group that
is idling, this command assigns a copy direction (primary and secondary roles) and begins the copy
process. Otherwise, this command restarts a previous copy process that was stopped either by a stop
command or by an I/O error.

If the resumption of the copy process leads to a period of time when the relationship is not consistent,
then you must specify the -force parameter when you restart the relationship. This situation can arise if
the relationship had been stopped and then further input transactions had been performed on the
original primary disk of the relationship. When you use the -force parameter in this situation, the data on
the secondary disk is not usable (because it is inconsistent) in a disaster recovery circumstance.

In the idling state, you must provide the -primary parameter. In other connected states, you can provide
the -primary parameter, but it must match the existing setting.

396 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
The -force parameter is required if consistency would be lost by starting a copy operation. This can occur
if write operations on either primary or secondary volumes have taken place since the
ConsistentStopped or idling state occurred. If the command is issued without the -force parameter in
such circumstances, the command fails. In general, the -force parameter is required if the group is in one
of the following states:
v Consistent_Stopped but not synchronized (sync=out_of_sync)
v Idling but not synchronized
The -force parameter is not required if the group is in one of the following states:
v Inconsistent_Stopped
v Inconsistent_Copying
v Consistent_Synchronized

However, the command does not fail if you specify the -force parameter.

A consistency group of Global Mirror relationship using multicycling mode in ConsistentStopped or

idling state (where every relationship in the group has a change volume configured at the secondary
volume) uses the secondary change volume to prevent the loss of consistency even if written data has
been processed on one or more of the primary volumes. This means you do not need to specify
startrcrelationship-force. But if written data has been received at any of the secondary volumes and
-clean is not set:
v The consistent image is lost
v You must specify -force

Specifying startrcconsistgrp invokes this protection using a consistent secondary volume for the
duration of the resulting background copy operation. Or, this protection can be invoked for a consistent
secondary volume before the background copy that has completed the relationship is moved to idling
state (by issuing the stoprcconsistgrp -access command). This protection lasts until the FlashCopy
reverse background copy operation is complete.

The -clean parameter is used when a Global or Metro Mirror group is started and the secondary volumes
in this group are assumed to be clean, which means that any changes that have been made at the
secondary are ignored and only changes made at the primary are considered when synchronizing the
primary and secondary volumes. The -clean parameter can be used in the following scenario:
1. A consistency group is created with the -sync parameter. At this point, it does not matter if the
primary and secondary contain the same data, even though the use of the -sync parameter implies
that this is true.
2. A stoprcconsistgrp command is issued with the -access parameter. This permits access to the
secondary disk. Change recording begins at the primary.
3. An image of the primary disk is copied and loaded on to the secondary disk. It is permissible to
allow updates to the primary disk during the image copy as this image can be only a fuzzy image of
the primary disk.
4. A startrcconsistgrp command that specifies the -primary master, -force, and -clean parameters is
issued. The auxiliary disk is marked as clean and changes on the master disk that have occurred since
the relationship was stopped are copied to the auxiliary disk.
5. Once the background copy has completed, relationships in the group become consistent and
synchronized.

A Global Mirror relationship with a cycling mode of:

v none uses the non-cycling Global Mirror algorithm
v multi must have a change volume configured at the primary volume (or the command fails)
v multi must also have a change volume configured at the secondary volume (or the command fails)

Chapter 21. Metro Mirror and Global Mirror commands 397

v multi performs multiple cycles of cycling

After creating a background copy the relationship remains in copying state, waiting for the remainder of
the period time to expire before performing a new cycle. If the secondary change volume is deconfigured
when the background copy completes, the relationship stops as if there is no cycle period.

An invocation example
startrcconsistgrp rccopy1

The resulting output

No feedback

startrcrelationship
The startrcrelationship command starts the Metro Mirror or Global Mirror relationship copy process,
sets the direction of copy if undefined, and optionally, marks the secondary volume of the relationship as
clean. The relationship must be a stand-alone relationship.

Syntax


startrcrelationship

-primary master -force -clean
aux

rc_rel_id

rc_rel_name

Parameters
-primary master | aux
(Optional) Specifies the copy direction by defining whether the master or auxiliary disk becomes the
primary (source). This parameter is required when the primary is undefined if, for example, the
relationship is in the idling state.
-force
(Optional) Specifies that you want the system to process the copy operation even if it might lead to a
temporary loss of consistency while synchronization occurs. This parameter is required if the
relationship is in the ConsistentStopped state, but is not synchronized or in the Idling state, but is
not synchronized.
-clean
(Optional) Specifies that the volume that is to become a secondary is clean; any changes made on the
secondary volume are ignored, and only changes made on the clean primary volume are considered
when synchronizing the primary and secondary disks. The relationship must be in an Idling
(connected) state for this parameter to work.

Attention: This flag should only be used when the primary and secondary volumes contain
identical data. Otherwise, relationships that are not consistent are reported as consistent. Once this
has been done there is no method to determine whether these volumes ever reach a true consistent
state until a full background copy can be carried out again.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or name of the relationship that you want to start in a stand-alone
relationship.

398 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

The startrcrelationship command starts a stand-alone relationship. The command fails if it is used to
start a relationship that is part of a consistency group.

This command can only be issued to a relationship that is connected. For a relationship that is idling, this
command assigns a copy direction (primary and secondary roles) and begins the copy process.
Otherwise, this command restarts a previous copy process that was stopped either by a stop command or
by some I/O error.

Note: A command in idling state is rejected if any of the indicated secondary volumes is the target of an
existing FlashCopy map.

If the FlashCopy mapping is active, the remote copy cannot be started.

In the idling state, you must provide the -primary parameter. In other connected states, you can provide
the -primary parameter, but it must match the existing setting.

The -force parameter is required if consistency would be lost by starting a copy operation. This can
occur if input transactions have occurred on either the primary or secondary volumes since the
ConsistentStopped or idling state occurred. This happens when the relationship is in either of these
states:
v ConsistentStopped but not synchronized
v Idling but not synchronized

A Global Mirror relationship using multicycling mode ConsistentStopped or idling state (with change
volume configured at the secondary volume) can use the secondary change volume to prevent the loss of
consistency even if written data has been processed on the primary volume. Consequently, you do not
have to specify startrcrelationship-force. If the relationship is idling and written data has been
received at the secondary volume:
v The consistent image is lost
v You must specify -force

Note: If -clean is not provided, it is assumed that written data at the secondary volume represents a
divergent image that cannot represent a consistent earlier state. If -clean is provided, the image on the
secondary volume might become unusable.

After restarting a relationship in either of these states, the data on the secondary volume is not usable for
disaster recovery until the relationship becomes consistent.

The -force parameter is not required if the relationship is in one of the following states:
v InconsistentStopped
v InconsistentCopying
v ConsistentSynchronized
However, the command does not fail if you specify the -force parameter.

A Global Mirror relationship with a cycling_mode of multi in either of these states does not require the
-force parameter because a consistent secondary image is retained. However, if such a relationship is in
idling state and written data has been received at the secondary volume, the -force flag is still required,
because the secondary volume has a divergent image that cannot represent a consistent earlier state. The
-clean parameter can be used in the following circumstance:

Chapter 21. Metro Mirror and Global Mirror commands 399

1. A relationship is created with the -sync parameter specified. (At this point it does not matter if the
primary and secondary disks contain the same data, even though the use of the -sync parameter
implies that this is true).
2. A stoprcrelationship command is issued with the -access parameter specified. This permits access to
the secondary disk. Change recording begins at the primary disk.
3. An image of the primary disk is copied and loaded on to the secondary disk. It is permissible to
allow updates to the primary disk during the image copy as this image need only be a fuzzy image of
the primary disk.
4. A startrcrelationship command that specifies the -primary master, -force, and -clean parameters
is issued. The auxiliary disk is marked as clean and changes on the master disk that have occurred
since the relationship was stopped are copied to the auxiliary disk.
5. Once the background copy has completed, the relationship becomes consistent and synchronized.

A Global Mirror relationship with a cycling mode of:

v none uses the non-cycling Global Mirror algorithm
v multi must have a change volume configured at the primary volume (or the command fails)
v multi must also have a change volume configured at the secondary volume (or the command fails)
v multi performs multiple cycles of cycling

After creating a background copy the relationship remains in copying state, waiting for the remainder of
the period time to expire before performing a new cycle. If the secondary change volume is deconfigured
when the background copy completes, the relationship stops as if there is no cycle period.

An invocation example
startrcrelationship rccopy1

The resulting output

No feedback

stoprcconsistgrp
The stoprcconsistgrp command stops the copy process for a Metro Mirror or Global Mirror consistency
group. This command can also be used to enable write access to the secondary volumes in the group if
the group is in a consistent state.

Syntax


stoprcconsistgrp rc_consist_group_id

-access rc_consist_group_name

Parameters
-access
(Optional) Allows write access to consistent secondary volumes in the consistency group.
rc_consist_group_id | rc_consist_group_name
(Required) Specifies the ID or the name of the consistency group to stop all processing for.

Description

This command applies to a consistency group. You can issue this command to stop processing on a
consistency group that is copying from primary volumes to secondary volumes.

400 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
If the consistency group is in an inconsistent state, all copy operations stop and do not resume until you
issue the startrcconsistgrp command. For a consistency group in the consistent_synchronized state,
this command causes a consistency freeze.

The consistent_copying state is a consistent state. A consistency group in this state transitions to
consistent_stopped state if it receives a stoprcconsistgrp command. Because the secondary change volume
holds the consistent image, a stopped consistent_copying relationship might not have its secondary
change volume not configured. This can be achieved by enabling access or completing synchronization so
the secondary disk contains a consistent image. A relationship in consistent_copying or
consistent_stopped accepts stoprcrelationship -access transition to idling state.

The consistent image that is present on the change volume is made accessible at the secondary volume
and after the command has completed the secondary volume can serve host read and write I/O. A
FlashCopy background copy operation begins to migrate the data for the consistent image from the
change volume to the secondary volume. While the background copy operation is in progress, the change
volume for the secondary volume remains in use. It may be necessary to process I/O before the reverse
FlashCopy map can be triggered, causing the enable access command to time out. In this case, the
relationship delays transitioning to idling until the reverse map starts and write access is available. Read
access to the consistent data remains available.

When a consistency group is in a consistent state (for example, in the consistent_stopped,

consistent_synchronized, or consistent_disconnected state) you can issue the access parameter with
the stoprcconsistgrp command to enable write access to the secondary virtual disks within that group.
Table 52 shows consistency group initial and final states:
Table 52. stoprcconsistgrp consistency group states
Initial state Final state Notes
inconsistent_stopped inconsistent_stopped If access is specified, the command
is rejected.
inconsistent_copying inconsistent_stopped If access is specified, the command
is rejected with no effect and the
relationship remains in the
inconsistent_copying state.
consistent_stopped consistent_stopped If access is specified, the final state
is idling.
consistent_synchronized consistent_stopped If access is specified, the final state
is idling. If access is not specified,
the final state is
consistent_stopped.
idling idling Remains in idling state whether
access is specified or not.
idling_disconnected unchanged If specified without access, the
relationship/group remains in
idling_disconnected state. If the
clustered systems reconnect, the
relationship/group is in either
inconsistent_stopped or
consistent_stopped state.
inconsistent_disconnected inconsistent_stopped The command is rejected, with or
without the access flag.
consistent_disconnected consistent_stopped The command is rejected if specified
without access. If specified with
access, the relationship/group
moves to idling_disconnected.

Chapter 21. Metro Mirror and Global Mirror commands 401

An invocation example
stoprcconsistgrp rccopy1

The resulting output

No feedback

stoprcrelationship
The stoprcrelationship command stops the copy process for a Metro Mirror or Global Mirror
stand-alone relationship. You can also use this command to enable write access to a consistent secondary
volume.

Syntax


stoprcrelationship rc_rel_id

-access rc_rel_name

Parameters
-access
(Optional) Specifies that the system allow write access to a consistent secondary volume.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or the name of the relationship to stop all processing for.

Description

The stoprcrelationship command applies to a stand-alone relationship. The command is rejected if it is

addressed to a relationship that is part of a consistency group. You can issue this command to stop a
relationship that is copying from primary to secondary volumes.

If the relationship is in an inconsistent state, any copy operation stops and does not resume until you
issue a startrcrelationship command. For a relationship in the consistent_synchronized state, this
command causes a consistency freeze.

When a relationship is in a consistent state – in the consistent_stopped, consistent_synchronized, or

consistent_disconnected state – you can use the access parameter to enable write access to the
secondary virtual disk. Table 53 on page 403 provides consistency group initial and final states.

The consistent_copying state is a consistent state. A relationship in consistent_copying state transitions to

consistent_stopped state when you specify stoprcrelationship. The primary and secondary input/output
(I/O) contain no identical data. Because the secondary change volume holds the consistent image, a
stopped consistent_copying relationship might not have its secondary change volume deconfigured. This
can be achieved by enabling access or completing synchronization so the secondary disk contains a
consistent image. A relationship in consistent_copying or consistent_stopped accepts stoprcrelationship
-access transition to idling state.

The consistent image that is present on the change volume is made accessible at the secondary volume
and once the command has completed the secondary volume can serve host read and write I/O. A
FlashCopy background copy operation begins to migrate the data for the consistent image from the
change volume to the secondary volume. While the background copy operation is in progress, the change
volume for the secondary volume remains in use. As there might be I/O to process before the reverse
FlashCopy map might be triggered, the enable access command can time out. In this case, the
relationship delays transitioning to idling until the reverse map starts and write access is available. Read
access to the consistent data remains available.

402 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Table 53. stoprcrelationship consistency group states
Initial state Final state Notes
inconsistent_stopped inconsistent_stopped If access is specified, the command
is rejected.
inconsistent_copying inconsistent_stopped If access is specified, the command
is rejected with no effect and the
relationship remains in the
inconsistent_copying state.
consistent_stopped consistent_stopped If access is specified, the final state
is idling.
consistent_synchronized consistent_stopped If access is specified, the final state
is idling. If access is not specified,
the final state is
consistent_stopped.
idling idling Remains in idling state whether
access is specified or not.
idling_disconnected unchanged If specified without access, the
relationship/group remains in
idling_disconnected state. If the
clustered systems reconnect, the
relationship/group is in either
inconsistent_stopped or
consistent_stopped state.
inconsistent_disconnected inconsistent_stopped The command is rejected, with or
without the access flag.
consistent_disconnected consistent_stopped The command is rejected if
specified without access. If
specified with access, the
relationship/group moves to
idling_disconnected.

An invocation example
stoprcrelationship rccopy1

The resulting output

No feedback

switchrcconsistgrp
The switchrcconsistgrp command reverses the roles of the primary and secondary volumes in a Metro
Mirror or Global Mirror consistency group when that consistency group is in a consistent state. All the
relationships in the consistency group are affected by this change.

Syntax


switchrcconsistgrp -primary master rc_consist_group_id

aux rc_consist_group_name

Parameters
-primary master | aux
(Required) Specifies whether the master or auxiliary side of the relationships in the group will
become the primary volumes.

Chapter 21. Metro Mirror and Global Mirror commands 403

rc_consist_group_id | rc_consist_group_name
(Required) Specifies the ID or name of the consistency group to switch.

Description

This command applies to a consistency group. It is normally issued to reverse the roles of the primary
and secondary virtual disks in a consistency group, perhaps as part of a failover process that is associated
with a disaster recovery event. Write access to the former primary volumes is lost and write access to the
new primary volumes is acquired. This command is successful when the consistency group is in a
connected, consistent state, and when reversing the direction of the relationships would not lead to a loss
of consistency, for example, when the consistency group is consistent and synchronized. The consistency
group must be in one of the following states in order for the switchrcconsistgrp command to process
correctly:
v ConsistentSynchronized
v ConsistentStopped and Synchronized
v Idling and Synchronized

Note: This command is rejected under any of the following conditions:

– You switch consistency group relationship so that the new secondary becomes the target volume of
an active FlashCopy mapping.
– Any of the indicated secondary volumes (in the consistency group) are the target of an existing
FlashCopy mapping.
– Using Global Mirroring with the multi cycling mode
The consistency group moves to the ConsistentSynchronized state after the successful completion of this
command. If you specify the -primary parameter and it is the same as the current primary, the command
has no effect.

An invocation example
switchrcconsistgrp -primary aux rccopy2

The resulting output

No feedback

switchrcrelationship
The switchrcrelationship command reverses the roles of primary and secondary virtual disks in a
stand-alone Metro Mirror or Global Mirror relationship when that relationship is in a consistent state.

Syntax


switchrcrelationship -primary master rc_rel_id

aux rc_rel_name

Parameters
-primary master | aux
(Required) Specifies whether the master disk or the auxiliary disk is to be the primary.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or the name of the relationship to switch.

404 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

The switchrcrelationship command applies to a stand-alone relationship. It is rejected if it is used to try

to switch a relationship that is part of a consistency group. It is normally issued to reverse the roles of the
primary and secondary virtual disk in a relationship perhaps as part of a failover process during a
disaster recovery event. Write access to the old primary disk is lost and write access to the new primary
disk is acquired. This command is successful when the relationship is in a connected, consistent state, and
when reversing the direction of the relationship does not lead to a loss of consistency; that is, when the
relationship is consistent and synchronized. The relationship must be in one of the following states in
order for the switchrcrelationship command to process correctly:
v ConsistentSynchronized
v ConsistentStopped and Synchronized
v Idling and Synchronized

Note: A command in idling state is rejected if any of the indicated secondary volumes is the target of
an existing FlashCopy map.
The relationship moves to the ConsistentSynchronized state after the successful completion of this
command. If you specify the -primary parameter with the current primary, the command has no effect.

The switchrcrelationship command is rejected if you use Global Mirroring with the multi cycling mode.

An invocation example
switchrcrelationship -primary master rccopy2

The resulting output

No feedback

Chapter 21. Metro Mirror and Global Mirror commands 405

406 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 22. Migration commands
The migration commands enable you to work with migration options with the SAN Volume Controller.

migrateexts
The migrateexts command migrates extents from one managed disk to another.

Syntax


migrateexts -source source_mdisk_id -target target_mdisk_id

source_mdisk_name target_mdisk_name

-exts number_of_extents

-threads number_of_threads -copy id

-vdisk vdisk_id

vdisk_name

Parameters
-source source_mdisk_id | source_mdisk_name
(Required) Specifies the MDisk on which the extents currently reside.
-target target_mdisk_id | target_mdisk_name
(Required) Specifies the MDisk to migrate the extents to.
-exts number_of_extents
(Required) Specifies the number of extents to migrate.
-threads number_of_threads
(Optional) Specifies the number of threads to use while migrating these extents. You can specify 1 - 4
threads. The default number of threads is 4.
-copy id
(Required if the specified VDisk has more than one copy) Specifies the VDisk copy that the extents
belong to.
-vdisk vdisk_id | vdisk_name
(Required) Specifies the VDisk that the extents belong to.

Description

This command migrates a given number of extents from the source virtual disk and the managed disk
that contains extents that are used to make up the virtual disk. The target is a managed disk within the
same managed disk group.

If a large number of extents are being migrated, you can specify 1 - 4 threads. You can issue the lsmigrate
command to check the progress of the migration.

The migrateexts command fails if there are insufficient free extents on the target managed disk. To avoid
this problem, do not issue new commands that use extents until the extents migration is completed.

The migrateexts command fails if the target or source VDisk is offline, or if Easy Tier is active for the
VDisk copy. Correct the offline condition before attempting to migrate the VDisk.

© Copyright IBM Corp. 2003, 2012 407

Note: Migration activity on a single managed disk is limited to a maximum of 4 concurrent operations.
This limit does not take into account whether the managed disk is the source or the destination target. If
more than four migrations are scheduled for a particular managed disk, further migration operations are
queued pending the completion of one of the currently running migrations. If a migration operation is
stopped for any reason, a queued migration task can be started. However, if a migration is suspended,
the current migration continues to use resources and a pending migration is not started. For example, the
following setup is a possible initial configuration:
v MDiskGrp 1 has VDisk 1 created in it
v MDiskGrp 2 has VDisk 2 created in it
v MDiskGrp 3 has only one MDisk

With the previous configuration, the following migration operations are started:
v Migration 1 migrates VDisk 1 from MDiskGrp 1 to MDiskGrp 3, running with 4 threads.
v Migration 2 migrates VDisk 2 from MDiskGrp 2 to MDiskGrp 3, running with 4 threads.
Due to the previous limitations, the two migration operations do not always run at the same speed.
MDiskGrp 3 has only one MDisk and the two migration operations have a total of 8 threads that are
trying to access the one MDisk. Four threads are active. The remaining threads are in standby mode
waiting to access the MDisk.

An invocation example
migrateexts -vdisk vdisk4 -source mdisk4 -exts
64 -target mdisk6 -threads 4

The resulting output

No feedback

migratetoimage
The migratetoimage command migrates data from a volume (image mode) onto a new image mode
volume copy. The target disk does not have to be in the same MDisk group (storage pool) as the source
disk.

Syntax


migratetoimage -vdisk source_vdisk_id

-copy id source_vdisk_name

-mdisk unmanaged_target_mdisk_id

-threads number_of_threads unmanaged_target_mdisk_name

-mdiskgrp managed_disk_group_id

-tier generic_ssd managed_disk_group_name
generic_hdd

Parameters
-vdisk source_vdisk_id | name
(Required) Specifies the name or ID of the source volume to be migrated.
-copy id
(Required if the specified volume has more than one copy) Specifies the volume copy to migrate
from.

408 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-threads number_of_threads
(Optional) Specifies the number of threads to use during the migration of extents. You can specify 1 -
4 threads. The default number of threads is 4.
-mdisk unmanaged_target_mdisk_id | name
(Required) Specifies the name of the MDisk to which the data must be migrated. This disk must be
unmanaged and large enough to contain the data of the disk that is being migrated.
-mdiskgrp managed_disk_group_id | name
(Required) Specifies the MDisk group (storage pool) into which the MDisk must be placed, after the
migration has completed.
-tiergeneric_ssd | generic_hhd
Specifies the tier of the MDisk being added.

Description

The migratetoimage command migrates the data of a user-specified volume by consolidating its extents
(which might reside on one or more MDisks) onto the extents of the target MDisk that you specify. After
migration is complete, the volume is classified as an image type volume, and the corresponding mdisk is
classified as an image mode MDisk.

The managed disk that is specified as the target must be in an unmanaged state at the time that the
command is run. Running this command results in the inclusion of the MDisk into the user-specified
MDisk (storage pool) group.

The migratetoimage command fails if the target or source volume is offline. Correct the offline condition
before attempting to migrate the volume.

The following example specifies that the user wants to migrate the data from vdisk1 onto mdisk5 and
that the MDisk must be put into the MDisk group (storage pool) mdgrp2.

An invocation example
migratetoimage -vdisk vdisk1 -mdisk mdisk5 -tier generic_ssd -mdiskgrp mdgrp2

The resulting output

No feedback

migratevdisk
The migratevdisk command enables you to migrate an entire virtual disk from one managed disk group
to another managed disk group.

Syntax


migratevdisk -mdiskgrp mdisk_group_id

mdisk_group_name -threads number_of_threads

-vdisk vdisk_id

-copy id vdisk_name

Parameters
-mdiskgrp mdisk_group_id | mdisk_group_name
(Required) Specifies the new managed disk group ID or name.

Chapter 22. Migration commands 409

-threads number_of_threads
(Optional) Specifies the number of threads to use during the migration of these extents. You can
specify 1 - 4 threads. The default number of threads is 4.
-copy id
(Required if the specified volume has more than one copy) Specifies the VDisk (volume) copy to
migrate.
-vdisk vdisk_id | vdisk_name
(Required) Specifies the virtual disk ID or name to migrate in to a new managed disk group.

Description

The migratevdisk command migrates the specified virtual disk into a new managed disk group; all the
extents that make up the virtual disk are migrated onto free extents in the new managed disk group.

You can issue the lsmigrate command to view the progress of the migration.

The process can be prioritized by specifying the number of threads to use during the migration. Using
only one thread puts the least background load on the system.

The migratevdisk command fails if there are insufficient free extents on the targeted managed disk group
for the duration of the command. To avoid this problem, do not issue new commands that use extents
until the volume migration is completed.

The migratevdisk command fails if the target volume or source volume is offline. Correct the offline
condition before attempting to migrate the volume.

An invocation example
migratevdisk -vdisk 4 -mdiskgrp Group0 -threads 2

The resulting output

No feedback

410 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 23. Service information commands
Service information commands are used to view the status of the hardware and report hardware errors.

lscmdstatus
Use the lscmdstatus command to display the status of any currently running service-aid task.

Syntax


sainfo lscmdstatus

panel_name

Parameters
panel_name
The name of the panel. This command will fail if the panel_name ID is not in the list returned by
lsservicenodes.

Description

This command displays the status of any currently running service-aid task. If no task is running, then
the completion status of the last task will be displayed.

If no service-aid tasks have run since the node was last restarted, the command will return immediately
with no output. Otherwise, it will display something similar to the following:
Backup date 20100706 15:53 : quorum time 20100706 16:24

lsfiles
Use the lsfiles command to display the files on the node that you want to retrieve with the satask
cpfiles command.

Syntax


sainfo lsfiles

-prefix path panel_name

Parameters
panel_name
The name of the panel. The command will fail if the panel_name ID is not in the list returned by the
lsservicenodes command.
-prefix path
The path must exist in a permitted listable directory. You can use the following -prefix paths:
v /dumps (the default if -prefix is not set)
v /dumps/audit
v /dumps/cimom
v /dumps/configs
v /dumps/drive

© Copyright IBM Corp. 2003, 2012 411

 v /dumps/elogs
v /dumps/enclosure
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/mdisk
v /dumps/syslogs
v /home/admin/upgrade

Description

This command displays a list of the files on the node that you want to retrieve using the satask cpfiles
command.

e An invocation example
e sainfo lsfiles -prefix /dumps

e The resulting output

e filename
e sublun.trc.old
e sublun.trc
e 100050.trc.old
e eccore.100050.100305.183051
e eccore.100050.100305.183052
e ethernet.100050.trc
e 100050.trc

lshardware
The lshardware command enables you to view the configured and actual hardware configuration of a
node in the cluster.

Syntax


sainfo lshardware

-delim delimiter panel_name

Parameters
-delim delimiter
(Optional) By default in a concise view, all columns of data are space-separated. The width of each
column is set to the maximum possible width of each item of data. In a detailed view, each item of
data has its own row, and if the headers are displayed the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. If you enter -delim : on the command line, the colon character (:) separates all
items of data in a concise view; for example, the spacing of columns does not occur. In a detailed
view, the data is separated from its header by the specified delimiter.
panel_name
(Optional) The node panel name.

412 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

When the node is in a service state, use this command to view the current hardware configuration.
Table 54 provides the possible values that are applicable to the attributes that are displayed as data in the
output views.
Table 54. lshardware attribute values
Attribute Value
panel_name The node panel name.
node_id The node unique ID; blank if not in a clustered system.
node_name The node name; blank if not in a clustered system.
node_status The node status.
hardware The hardware model.
actual_different Indicates if the node hardware is different than the configured hardware.
actual_valid Indicates if the node hardware is valid.
memory_configured The configured amount of memory (in GB).
member_actual The currently installed amount of memory (in GB).
memory_valid Indicates if the actual memory is a valid configuration.
cpu_count The maximum number of CPUs for the node.
cpu_socket The ID of socket to which the CPU fields refer.
cpu_configured The configured CPU for this socket.
cpu_actual The currently installed CPU in this socket.
cpu_valid Indicates if the currently installed CPU is a valid configuration.
adapter_count The maximum number of adapters for the node (differs by node type).
adapter_location The location of this adapter.
adapter_configured The configured adapter for this location.
adapter_actual The currently installed adapter for this location.
adapter_valid Indicates if the adapter in this location is valid.
3 ports_different Indicates whether adapter ports can support more functions.

Sample output for an 8A4 node

panel_name,123456
node_id,
status,service
hardware,8A4lshardware
panel_name 116521
node_id 1
node_name node1
node_status Active
hardware IT1
actual_different,yes
actual_valid,no
memory_configured,8
memory_actual,8
memory_valid,yes
cpu_count,2
cpu_socket,1
cpu_configured,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_actual,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_valid,yes
cpu_socket,2

Chapter 23. Service information commands 413

cpu_configured,none
cpu_actual,none
cpu_valid,yes
adapter_count,4
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,1
adapter_configured,Four port 8Gb/s FC adapter card
adapter_actual,Four port 8Gb/s FC adapter card
adapter_valid,yes
adapter_location,2
adapter_configured,none
adapter_actual,Four port 8Gb/s FC adapter card
adapter_valid,no
adapter_location,
adapter_configured,
adapter_actual,
adapter_valid,
adapter_location,
adapter_configured,
adapter_actual,
adapter_valid,
ports_different

Sample output for a 300 node

panel_name,123456
node_id,
node_name
status,service
hardware,300
actual_different,no
actual_valid,yes
memory_configured,8
memory_actual,8
memory_valid,yes
cpu_count,1
cpu_socket,1
cpu_configured,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_actual,4 core Intel(R) Xeon(R) CPU E3110 @ 3.0GHz
cpu_valid,yes
cpu_socket,
cpu_configured,
cpu_actual,
cpu_valid,
adapter_count,6
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,0
adapter_configured,1Gb/s Ethernet adapter
adapter_actual,1Gb/s Ethernet adapter
adapter_valid,yes
adapter_location,0
adapter_configured,Four port 8Gb/s FC adapter card
adapter_actual,Four port 8Gb/s FC adapter card
adapter_valid,yes
adapter_location,0
adapter_configured,High-speed SAS adapter
adapter_actual,High-speed SAS adapter

414 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 adapter_valid,yes
adapter_location,0
adapter_configured,Midplane bus adapter
adapter_actual,Midplane bus adapter
adapter_valid,yes
adapter_location,1
adapter_configured,Two port 10Gb/s ethernet adapter
adapter_actual,Two port 10Gb/s ethernet adapter
adapter_valid,yes
2 ports_different,no

lsservicenodes
Use the lsservicenodes command to displays a list of all the nodes that can be serviced using the service
assistant CLI.

Syntax


sainfo lsservicenodes


Parameters

None

Description

This command displays a list of all the nodes that can be serviced using the service assistant CLI. This
list includes nodes that at a code level of at least 6.2.0, are visible on the fabric, and are one of the
following:
v The partner node in a control enclosure to the node that is running the command.
v In the same clustered system as the node running the command.
v In candidate state.
v Not in a clustered system and in service state.
v Not in an enclosure with a stored clustered system ID (which is not the clustered system ID of the
local node).
Nodes not clustered with the local node will not be shown unless they are the partner node. Table 55
shows possible outputs.
Table 55. lsservicenodes outputs
Attribute Value
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
cluster_id Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
cluster_name Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
node_id Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
node_name Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
relation v Local: the node the CLI command was issued from.
v Partner: the node in the same enclosure as the local node.
v Cluster: nodes other than the partner that are in the same clustered system as the local
node.
v Candidate: the node is not part of the clustered system.

Chapter 23. Service information commands 415

Table 55. lsservicenodes outputs (continued)
Attribute Value
node_status v Active: the node is part of a clustered system and can perform I/O.
v Service: the node is in service, standby, or node rescue.
v Candidate: the node is not part of a clustered system.
v Starting: the node is part of a clustered system and is attempting to join the clustered
system, and cannot perform I/O.
error_data Outstanding error and error data, by priority.

Storwize® V7000: This command displays a list of all the nodes that can be serviced using the service
assistant CLI. This list includes nodes that at a code level of at least 6.2.0, are visible on the fabric, and
are one of the following:
v The partner node in a control enclosure to the node that is running the command.
v In the same clustered system as the node running the command.
v In candidate state.
v Not in a clustered system and in service state.
v Not in an enclosure with a stored clustered system ID (which is not the clustered system ID of the
local node).
Nodes not clustered with the local node will not be shown unless they are the partner node. Table 56
shows possible outputs.
Table 56. lsservicenodes outputs
Attribute Value
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
cluster_id Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
cluster_name Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
node_id Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
node_name Blank if node is a candidate; otherwise, the value is determined from vpd_cluster.
relation v Local: the node the CLI command was issued from.
v Partner: the node in the same enclosure as the local node.
v Cluster: nodes other than the partner that are in the same clustered system as the local
node.
v Candidate: the node is not part of a clustered system.
node_status v Active: the node is part of a clustered system and can perform I/O.
v Service: the node is in service, standby, or node rescue.
v Candidate: the node is not part of a clustered system.
v Starting: the node is part of a clustered system and is attempting to join the clustered
system, and cannot perform I/O.
error_data Outstanding error and error data, by priority.
candidate The candidate for the node. If this option is selected, the cluster_id, cluster_name, node_id
and node_name must be blank.

An invocation example
sainfo lsservicenodes

The resulting output

416 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
panel_name cluster_id cluster_name node_id node_name relation node_status error_data
01-1 0000020073C0A0D4 Cluster_9.180.28.82 1 node1 local Active
1107812-1

lsservicerecommendation
Use the lsservicerecommendation command to determine what actions should be performed when
servicing a node.

Syntax


sainfo lsservicerecommendation

panel_name

Parameters
panel_name
(Optional) If no panel ID is provided, the service recommendation for the local node is returned. If a
panel_name from the list returned by lsservicenodes is specified, then the service recommendation
for that node is returned. The command will fail if the panel_name is not in the list returned by
lsservicenodes.

Description

This command enables you to determine what actions should be performed when servicing a node.

Example 1 for service_action:

Use fabric tools to diagnose and correct Fibre Channel fabric problem.

Example 2 for service_action

No service action required, use console to manage node.

lsservicestatus
The lsservicestatus command displays the current status of a node.

Syntax


sainfo lsservicestatus

panel_name

Parameters
panel_name
(Optional) If a panel_name is provided, the service recommendation for the local node is returned. If a
panel_name from the list returned by lsservicenodes is specified, then the service recommendation
for that node is returned. The command fails if the panel_name ID is not in the list returned by
lsservicenodes. This output is returned as the node status on all Universal Serial Bus (USB) flash
drive commands.

Note: For 2145 nodes the panel name is a six digit number on the node front panel. For 2076 nodes
the panel name is the value of the enclosure ID and canister ID or the enclosure serial number and
canister location.

Chapter 23. Service information commands 417

Description

Use this command to display the current status of a node. This command provides all the information
that can be obtained using the front panel of a SAN Volume Controller node. You can run this command
on any node, even one that is not part of a clustered system (system), to obtain the vital product data
(VPD) and error status.

Table 22 on page 153 shows possible outputs.

Table 57. lsservicestatus output
Attribute Value
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
console_ip An Internet Proticol (IP) Version 4 or 6 address
Note: This field might be blank if the node is not present in a system.
has_nas_key yes | no
Note: This field might be blank if the node is not present in a system.
system_id Specifies the ID of a system.
system_name Specifies the name of a system. When you use this parameter, the detailed view of the
specific system is displayed and any value that you specified by the -filtervalue parameter
is ignored. If you do not specify the system_name parameter, the concise view of all clusters
that match the filtering requirements that are specified by the -filtervalue parameter are
displayed.
system_status The error code is the same as the one displayed on the front panel.
system_ip_count The maximum number of management addresses you can configure.
system_ip_port This, and fields down to prefix_6, are repeated for each management address.
system_ip The IPv4 management IP address.
system_gw The IPv4 management IP gateway.
system_mask The IPv4 management IP mask.
system_ip_6 The IPv6 management IP address.
system_gw_6 The IPv6 management IP gateway.
system_prefix_6 The IPv6 management IP prefix.
node_id The ID of the node that is being configured.
node_name The name of the node that is being configured.
node_status active | starting | service | candidate
config_node yes | no
hardware 8F2 | 8F4 | 8G4 | CF8 | 8A4 | other
service_IP_address The IPv4 service address for the node.
service_gateway The IPv4 service gateway for the node.
service_subnet_mask The IPv4 service mask for the node.
service_IP_address_6 The IPv6 service address for the node.
service_gateway_6 The IPv6 service gateway for the node.
service_prefix_6 The IPv6 service gateway for the node.
node_sw_version The software version of the node.
node_sw_build The build string for software on the node.
system_sw_build The CSM build that the system is running.
node_error_count The number of node errors.

418 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Table 57. lsservicestatus output (continued)
Attribute Value
node_error_data The type of node errors.
FC_port_count The number of Fibre Channel ports.
FC_port_id The beginning of repeating fields for each Fibre Channel port; the whole set of fields
indicated is repeated for each port.
port_status This should match the port on the front panel, enclosure, or canister.
port_speed This should match the port speed on the front panel, enclosure, or canister.
port_WWPN The worldwide port number of the port.
SFP_type long-wave | short-wave
ethernet_port_count The number of detected Ethernet ports.
ethernet_port_id Specifies the ID of an Ethernet port.
port_status online | offline | not configured
port_speed 10Mbps | 100Mbps | 1Gbps | 10Gbps | full | half
MAC A single MAC address.
3 vnport_count Number of VN ports created on top of each physical Fiber Channel over Ethernet (FCoE)
3 port.
3 vnport_id The VN port ID.
3 vnport_wwpn The WWPN assigned to the VN port.
3 vnport_FCF_mac The MAC address for the FCF to which the VN port is connected.
3 vnport_vlanid The VLAN ID used by the VN port. The value is blank for FC ports.
product_mtm The machine type and model.
product_serial The node serial number.
time_to_charge The estimated start time (in minutes) needed for 50% of the battery to be charged.
battery_charging The percentage of charge of the batteries.
disk_WWNN_prefix The most recently used WWNN prefix.
node_WWNN N/A
enclosure_WWNN_1 N/A
enclosure_WWNN_2 N/A
node_part_identity N/A
node_FRU_part N/A
enclosure_part_identity N/A
PSU_count N/A
PSU_id N/A
PSU_status N/A
battery_count N/A
battery_id N/A
battery_status N/A

Storwize® V7000: Table 23 on page 155 shows possible outputs.

Note: On a node that is not part of a system, some of the fields are blank or N/A.

Chapter 23. Service information commands 419

Table 58. lsservicestatus output
Attribute Value
console_ip An Internet Proticol (IP) Version 4 or 6 address
Note: This field might be blank if the node is not present in a system.
has_nas_key yes | no
Note: This field might be blank if the node is not present in a system.
panel_name The front panel name, enclosure IDs, or canister IDs that identify the node.
system_id Specifies the ID of a system.
system_name Specifies the name of a system. When you use this parameter, the detailed view of
the specific system is displayed and any value that you specified by the -filtervalue
parameter is ignored. If you do not specify the cluster_name parameter, the concise
view of all systems that match the filtering requirements that are specified by the
-filtervalue parameter are displayed.
system_status The error code is the same as the one displayed on the front panel.
system_ip_count The maximum number of management addresses you can configure.
system_ip_port This, and fields down to prefix_6, are repeated for each management address.
system_ip The IPv4 management IP address.
system_gw The IPv4 management IP gateway.
system_mask The IPv4 management IP mask.
system_ip_6 The IPv6 management IP address.
system_gw_6 The IPv6 management IP gateway.
system_prefix_6 The IPv6 management IP prefix.
node_id The ID of the node that is being configured.
node_name The name of the node that is being configured.
node_status active | starting | service | candidate
config_node yes | no
hardware 8F2 | 8F4 | 8G4 | CF8 | 8A4 | other
service_IP_address The IPv4 service address for the node.
service_gateway The IPv4 service gateway for the node.
service_subnet_mask The IPv4 service mask for the node.
service_IP_address_6 The IPv6 service address for the node.
service_gateway_6 The IPv6 service gateway for the node.
service_prefix_6 The IPv6 service gateway for the node.
node_sw_version The software version of the node.
node_sw_build The build string for software on the node.
system_sw_build The CSM build that the system is running.
node_error_count The number of node errors.
node_error_data The type of node errors.
FC_port_count The number of Fibre Channel ports.
FC_port_id The beginning of repeating fields for each Fibre Channel port; the whole set of fields
indicated is repeated for each port.
port_status This should match the port on the front panel, enclosure, or canister.
port_speed This should match the port speed on the front panel, enclosure, or canister.
port_WWPN The worldwide port number of the port.

420 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Table 58. lsservicestatus output (continued)
Attribute Value
SFP_type long-wave | short-wave
ethernet_port_count The number of detected Ethernet ports.
ethernet_port_id Specifies the ID of an Ethernet port.
port_status online | offline | not configured
port_speed 10Mbps | 100Mbps | 1Gbps | 10Gbps | full | half
MAC A single MAC address.
product_mtm The machine type and model.
product_serial The node serial number.
time_to_charge The estimated start time (in minutes) needed for 50% of the battery to be charged.
battery_charging The percentage of charge of the batteries.
node_WWNN The last active WWNN stored in the node; blank if no system data.
enclosure_WWNN_1 Canister 1 WWNN from the enclosure VPD.
enclosure_WWNN_2 Canister 2 WWNN from the enclosure VPD.
node_part_identity The 11S string from the hardware VPD.
node_FRU_part if stored in node VPD
enclosure_part_identity The S11 data.
PSU_count The number of expected PSUs (two).
PSU_id The ID of the slot the PSU is in.
PSU_status missing | failed | active
battery_count The number of expected batteries (two).
battery_id The ID of the slot the battery is in.
battery_status missing | failed | charging | active
node_location_copy Equivalent to the panel name; blank if a node has been removed from a system.
node_product_mtm_copy Equivalent to panel product_mtm; blank if a node has been removed from a system.
node_product_serial_copy Equivalent to product_serial; blank if a node has been removed from a system.
node_WWNN_1_copy Equivalent to enclosure_WWNN_1; blank if a node has been removed from a
system.
node_WWNN_2_copy Equivalent to enclosure_WWNN_2; blank if a node has been removed from a
system.
latest_system_id The system ID running on the current enclosure; blank if a node has been removed
from a system.
next_system_id The system ID used to create the next system on this enclosure; it is blank if a node
has been removed from a system.
1 service_IP_mode Current mode of the service IPv4
1 v Empty if IPv4 is not active
1 v One of the following:
1 – static (if the service IP is set by the user)
1 – dhcp (if the service IP is set successfully using DHCP server)
1 – dhcpfallback (if the service IP is set to a default value after a DHCP server
1 request failed)

Chapter 23. Service information commands 421

 Table 58. lsservicestatus output (continued)
Attribute Value
1 service_IP_mode_6 Current mode of the service IPv6
1 v Empty if IPv6 is not active
1 v Either static (if the service IP is set by the user) or dhcp (if the service IP set
1 successfully using DHCP server).

An invocation example
lsservicestatus

The resulting output

e panel_name 150434
e cluster_id 000002006ee1445e
e cluster_name Cluster_192.168.8.241
e cluster_status Active
e cluster_ip_count 2
e cluster_port 1
e cluster_ip 192.168.8.241
e cluster_gw 192.168.8.1
e cluster_mask 255.255.255.0
e cluster_ip_6
e cluster_gw_6
e cluster_prefix_6
e cluster_port 2
e cluster_ip
e cluster_gw
e cluster_mask
e cluster_ip_6
e cluster_gw_6
e cluster_prefix_6
e node_id 1
e node_name node1
e node_status Active
e config_node Yes
e hardware CF8
e hardware IT1
e service_IP_address
e service_gateway
e service_subnet_mask
e service_IP_address_6
e service_gateway_6
e service_prefix_6
e service_IP_mode dhcpfallback
e node_sw_version 6.4.0.0
e node_sw_build 64.8.1205180000
e cluster_sw_build 64.8.1205180000
e node_error_count 0
e fc_ports 4
e port_id 1
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680140a22f
e SFP_type Short-wave
e port_id 2
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680130a22f
e SFP_type Short-wave
e port_id 3
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680110a22f

422 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
e SFP_type Short-wave
e port_id 4
e port_status Active
e port_speed 8Gb
e port_WWPN 500507680120a22f
e SFP_type Short-wave
e ethernet_ports 4
e ethernet_port_id 1
e port_status Link Online
e port_speed 1Gb/s - Full
e MAC 00:21:5e:db:30:38
e vnport_count 0
e ethernet_port_id 2
e port_status Not Configured
e port_speed
e MAC 00:21:5e:db:30:3a
e vnport_count 0
e ethernet_port_id 3
e port_status Not Configured
e port_speed 10Gb/s - Full
e MAC 00:00:c9:bc:6f:22
e vnport_count 0
e ethernet_port_id 4
e port_status Not Configured
e port_speed 10Gb/s - Full
e MAC 00:00:c9:bc:6f:20
e vnport_count 0
e product_mtm 2145-CF8
e
e product_serial 75HAXYA
e time_to_charge 0
e battery_charging 0
e dump_name 150434
e node_WWNN 500507680100a22f
e disk_WWNN_suffix 0A22F
e panel_WWNN_suffix 0A22F
e UPS_serial_number
e UPS_status
e enclosure_WWNN_1
e enclosure_WWNN_2
e node_part_identity
e node_FRU_part
e enclosure_identity
e PSU_count
e PSU_id
e PSU_status
e PSU_id
e PSU_status
e Battery_count
e Battery_id
e Battery_status
e Battery_id
e Battery_status
e node_location_copy
e node_product_mtm_copy
e node_product_serial_copy
e node_WWNN_1_copy
e node_WWNN_2_copy
e latest_cluster_id
e next_cluster_id
e console_IP 192.168.8.241:443
e has_nas_key no
e fc_io_ports 6
e fc_io_port_id 1
e fc_io_port_WWPN 500507680140a22f
e fc_io_port_switch_WWPN 200000051e630f9a
e fc_io_port_state Active

Chapter 23. Service information commands 423

e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 1
e fc_io_port_id 2
e fc_io_port_WWPN 500507680130a22f
e fc_io_port_switch_WWPN 200400051e630f9a
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 2
e fc_io_port_id 3
e fc_io_port_WWPN 500507680110a22f
e fc_io_port_switch_WWPN 200000051e7ded49
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 3
e fc_io_port_id 4
e fc_io_port_WWPN 500507680120a22f
e fc_io_port_switch_WWPN 200400051e7ded49
e fc_io_port_state Active
e fc_io_port_FCF_MAC N/A
e fc_io_port_vlanid N/A
e fc_io_port_type FC
e fc_io_port_type_port_id 4
e fc_io_port_id 5
e fc_io_port_WWPN 500507680150a22f
e fc_io_port_switch_WWPN 2064000573cd6201
e fc_io_port_state Active
e fc_io_port_FCF_MAC 00:05:73:CD:62:00
e fc_io_port_vlanid 100
e fc_io_port_type Ethernet
e fc_io_port_type_port_id 3
e fc_io_port_id 6
e fc_io_port_WWPN 500507680160a22f
e fc_io_port_switch_WWPN 2064000573c8a701
e fc_io_port_state Active
e fc_io_port_FCF_MAC 00:05:73:C8:A7:00
e fc_io_port_vlanid 100
e fc_io_port_type Ethernet
e fc_io_port_type_port_id 4service_IP_mode
e service_IP_mode_6

424 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 24. Service mode commands (Discontinued)
Attention: The service mode commands are discontinued.

applysoftware (Discontinued)
Attention: The svcservicemodetask applysoftware command is discontinued. Use the satask
installsoftware command instead.

Discontinued.

cleardumps (Discontinued)
Attention: The svcservicemodetask cleardumps command is discontinued.

dumperrlog (Discontinued)
Attention: The svcservicemodetask dumperrlog command is discontinued.

exit (Discontinued)
Attention: The svcservicemodetask exit command is discontinued. Use the satask stopservice
command instead.

© Copyright IBM Corp. 2003, 2012 425

426 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 25. Service mode information commands
(Discontinued)
Attention: The service mode information commands are discontinued.

ls2145dumps (Discontinued)
Attention: The svcservicemodeinfo ls2145dumps command is discontinued. Use the lsdumps command to
display a list of files in a particular dumps directory.

lscimomdumps (Discontinued)
Attention: The svcservicemodeinfo lscimomdumps command is discontinued. Use the lsdumps command
to display a list of files in a particular dumps directory.

lsclustervpd (Discontinued)
Attention: The svcservicemodeinfo lsclustervpd command is discontinued. Use the sainfo
lsservicestatus command instead.

lserrlogdumps (Discontinued)
Attention: The svcservicemodeinfo lserrlogdumps command is discontinued. Use the lsdumps command
to display a list of files in a particular dumps directory.

lsfeaturedumps (Discontinued)
Attention: The svcservicemodeinfo lsfeaturedumps command is discontinued. Use the lsdumps
command to display a list of files in a particular dumps directory.

lsiostatsdumps (Discontinued)
Attention: The svcservicemodeinfo lsiostatsdumps command is discontinued. Use the lsdumps
command to display a list of files in a particular dumps directory.

lsiotracedumps (Discontinued)
Attention: The svcservicemodeinfo lsiotracedumps command is discontinued. Use the lsdumps
command to display a list of files in a particular dumps directory.

lsmdiskdumps (Discontinued)
Attention: The svcservicemodeinfo lsmdiskdumps command is discontinued. Use the lsdumps command
to display a list of files in a particular dumps directory.

lssoftwaredumps (Discontinued)
Attention: The svcservicemodeinfo lssoftwaredumps command is discontinued. Use the lsdumps
command to display a list of files in a particular dumps directory.

© Copyright IBM Corp. 2003, 2012 427

428 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 26. Service task commands
e Service task command information enables you to service the node hardware.

chenclosurevpd
Use the chenclosurevpd command to cause the partner node in the enclosure to warmstart, so that it can
acquire the changed midplane vital product data (VPD), and to change fields in the control enclosure
VPD.

Syntax


satask chenclosurevpd

-serial -type
serial_number machine_type


-wwnn1 -wwnn2 -resetclusterid
wwnn1 wwnn2

Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
-serial serial_number
(Optional) The new serial number for the enclosure. The serial_number must be set on a replacement
enclosure to match the values of the enclosure being replaced.
-type machine_type
(Optional) The type of machine. The machine_type must be set on a replacement enclosure to match
the values of the enclosure being replaced.
-wwnn1 wwnn1
(Optional) The WWNN of canister 1. The wwnn1 must be set on a replacement enclosure to match the
values of the enclosure being replaced.

Note: If you change wwnn1 on an operating system, you might need to also change the host and
Fibre Channel configuration settings.
-wwnn2 wwnn2
(Optional) The WWNN of canister 2. The wwnn2 must be set on a replacement enclosure to match the
values of the enclosure being replaced.

Note: If you change wwnn2 on an operating system, you might need to also change the host and
Fibre Channel configuration settings.
-resetclusterid
(Optional) Requests that the stored cluster be zeroed out (eliminated).

Attention: The cluster ID indicates if the enclosure, and the drives it contains, are part of a cluster.
Resetting it indicates it is no longer part of a cluster, and any data required on the drives is not
required. This might result in loss of access to your data.

© Copyright IBM Corp. 2003, 2012 429

 Description

Use this command to change fields in the control enclosure VPD. The node must be in candidate or
service state when you run this command, and cannot be part of a cluster.

An invocation example
satask chenclosurevpd -serial 123456

The resulting output

No feedback

chnodeled
Use the chnodeled command to turn on or off the location light-emitting diode (LED) for the specified
canister.

Syntax


satask chnodeled -on | -off panel_name


Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
on | off panel_name
Turns on or off the location LED for the specified canister.

Description

This command turns on or off the canister location LED.

Note: The location LED is mapped onto the physical LEDs using different methods, depending on your
hardware. Refer to the documentation for your hardware platform for more information.

e An invocation example

e To turn on the LED for canister 1 in enclosure 02:

e satask chnodeled -on 02-1

e The resulting output

e No feedback

chserviceip
Use the chserviceip command to set the service address for a specific node.

Syntax

satask chserviceip -serviceip ipv4


-gw ipv4 -mask ipv4 -resetpassword panel_name

satask chserviceip -serviceip_6 ipv6


-gw_6 ipv6 -prefix_6 int -resetpassword panel_name

430 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide


satask chserviceip

-resetpassword panel_name

satask chserviceip -dhcp


-resetpassword panel_name

satask chserviceip -dhcp_6


-resetpassword panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.
-serviceip
The IPv4 address for the service assistant.

Note: The IPv4 service address can be unconfigured by setting the address to 0.0.0.0.
-gw
(Optional) The IPv4 gateway for the service assistant.
-mask
(Optional) The IPv4 subnet for the service assistant.
-serviceip_6
The IPv6 address for the service assistant.

Note: The IPv6 service address can be unconfigured by setting the address to 0:0:0:0:0:0:0:0.
-gw_6
(Optional) The IPv6 gateway for the service assistant.
-prefix_6
The IPv6 prefix for the service assistant.
-dhcp
e Attempts to obtain an IPv4 address from Dynamic Host Configuration Protocol (DHCP).
-dhcp_6
Attempts to obtain an IPv6 address from DHCP.
-resetpassword
(Optional) Sets the service assistant password to default.

Storwize V7000:
-default
Resets the IPv4 service address of a Storwize V7000 to the default address.
panel_name
(Optional) Identifies the node being serviced.
-serviceip
The IPv4 address for the service assistant.

Note: The IPv4 service address can be unconfigured by setting the address to 0.0.0.0.
-gw
(Optional) The IPv4 gateway for the service assistant.

Chapter 26. Service task commands 431

 -mask
(Optional) The IPv4 subnet for the service assistant.
-serviceip_6
The IPv6 address for the service assistant.
-gw_6
(Optional) The IPv6 gateway for the service assistant.
-prefix_6
(Optional) The IPv6 prefix for the service assistant.
-resetpassword
(Optional) Sets the service assistant password to default.

Description

This command sets the service assistant IP address for a specific node. If the node is part of clustered
system (system) then the system gateway, subnet and prefix will be used unless specified otherwise. If
the node is a candidate node, the subnet, prefix and gateway must be specified. If you specify an IPV4 or
IPV6 address, but do not provide a gateway, mask, or prefix, then the existing gateway, mask, and prefix
values are preserved.

1 When -dhcpfallback is specified, the current service interface is restarted and the new service IPv4
1 address is established using DHCP. If the DHCP request fails, the service IP address is set statically based
1 on the node's physical location.

1 The -dhcpfallback is not usable for IPv6. These flags allocate a new address because the command
1 causes the service interface to resart.

1 Consequently, you can configure both an IPv4 and an IPv6 address concurrently. Setting the IPv4 address
1 does not change the IPv6 setting, and setting the IPv6 address will not change the IPv4 setting. It is
1 possible to clear any values set by setting the IPv4 address to 0.0.0.0 or leaving the IPv6 value empty.

Remember:
2 v Issue the following command to clear the IPv4 service IP address:
2 satask chserviceip -serviceip 0.0.0.0 -gw 0.0.0.0
2 v Issue the following command to clear the IPv6 service IP address:
2 satask chserviceip -serviceip_6 0::0 -gw_6 0::0 -prefix_6 64

Input
satask chserviceip

Input (with a specific -serviceip, -gw, and -mask parameters)

satask chserviceip -serviceip 1.2.3.4 -gw 1.2.3.1 -mask 255.255.255.0

chwwnn
Use the chwwnn command to modify the node World Wide Node Name (WWNN).

Syntax


satask chwwnn -wwnnsuffix wwnn_suffix

-panel_name

432 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
-wwnnsuffix
The suffix to be used for node wwnn.
panel_name
(Optional) Identifies the node being serviced.

Description

This command modifies the WWNN. Use the lsservicestatus command to view suggested WWNNs.

Note: This applies specifically (and only) to 2145 systems.

[No feedback]

cpfiles
Use the cpfiles command to copy files from another node.

Syntax


satask cpfiles -prefix directory

file_filter -source source_panel_name


target_panel_name

Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
-prefix directory | file_filter
(Required) Specifies the directory, files, or directory and files to be retrieved. The path must exist in a
permitted listable directory. You can use the following -prefix filters:
v /dumps (retrieves all files in all subdirectories)
v /dumps/audit
v /dumps/cimom
v /dumps/configs
v /dumps/drive
v /dumps/elogs
v /dumps/enclosure
v /dumps/feature
v /dumps/iostats
v /dumps/iotrace
v /dumps/mdisk
v /dumps/syslogs
v /home/admin/upgrade
v /dumps/enclosure

Note:

Chapter 26. Service task commands 433

 v You can also specify a file filter. For example, if you specify /dumps/elogs/*.txt, all files in the
/dumps/elogs directory that end in .txt are copied.
v If you use a wildcard, the following rules apply:
1. The wildcard character is an asterisk (*).
2. The command can contain a maximum of one wildcard.
3. When you use a wildcard, you must surround the filter entry with double quotation marks
("x"). For example: satask cpfiles -prefix "/dumps/elogs/*.txt"
-source source_panel_name
(Optional) Identifies the source node files will be copied from.
target_panel_name
(Optional) Identifies the node that files will be copied to. If no panel name is provided, the files will
be copied to the local node.

Description

This command copies files from another node. You can monitor the progress of the copy using the sainfo
lscmdstatus command.

An invocation example: to get configuration information from canister 1 in enclosure 2

satask cpfiles -prefix /dumps/configs -source 02-1

The resulting output

No feedback

installsoftware
Use the installsoftware command to install a specific software package.

Syntax

satask installsoftware -file filename


-ignore | -pacedccu panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.
-file
The file name of software installation package.

Note: The argument to -file must be present on the local node; the argument will be automatically
copied to the target panel_name.
-ignore
Overrides prerequisite checking and forces installation of the software.
-pacedccu
Causes the node to initiate a paced ccu (in which you define when the node begins its upgrade)
instead of a normal ccu (in which each node in the cluster automatically upgrades in sequence).

434 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

This command installs a specific software package.

An invocation example:
satask installsoftware -file install_pkg.gpg nodeB_panel_name

leavecluster
Use the leavecluster command to remove clustered system (system) state data, location information, and
other history from a node.

Syntax


satask leavecluster -force

-panel_name

Parameters
-force
(Required)

Attention: The -force parameter is required because this service action can cause temporary or
permanent loss of access to data. Use this command only when a service procedure instructs you to
do so.
panel_name
e (Optional) Identifies the node being serviced. The default is the node on which the command is
e entered.

Description

Use this command to remove system state data, location information, and other history from a node.

An invocation example
satask leavecluster -force 78G00F3-2 /* this forces the node with panel_name=78G00F3-2 out of the clustered system */

An invocation example
satask leavecluster -force /* this forces the node on which the command is entered out of the clustered system*/

metadata
Use the metadata command to recover a virtualization table.

Syntax


satask metadata -rebuildcluster


satask metadata -scan -file filename_arg -disk UID_arg -start start_arg


-end end_arg

Chapter 26. Service task commands 435



satask metadata -dump -disk UID_arg -start start_arg


Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
e -rebuildcluster
e Creates a cluster from the metadata found in /dumps/t3_recovery.bin created by the -dump process.
e -scan
e The logical block address (LBA) at which to start scanning.
e -dump
e The LBA at which the metadata resides (as reported in the scan file)
e -endend_arg
e The last LBA in which to look for metadata on the disk.
e -file filename_arg
e Specifies the file in which you want the results of a scan operation. The file is placed into the node in
e the directory /dumps , and can be retrieved using Secure Copy (scp). The file can be subsequently
e cleaned using the cleardumps command.
e -disk UID_arg
e Specifies the UID of the MDisk or drive that you want to scan, or remove a dump from. .
e -start start_arg

e Description

Use this command to recover a virtualization table.

An invocation example
satask metadata -scan -file scan.0.xml
-disk 600a0b80000f14ee0000008e4146bdee00000000000000000000000000000000 -start 0

The resulting output

No feedback

mkcluster
Use the mkcluster command to create a new clustered system (system).

Syntax


satask mkcluster -clusterip -gw -mask

-clusterip_6 -gw_6 -prefix_6


-name cluster_name -panel_name

Parameters
-clusterip
e (Optional) The Internet Protocol Version 4 (IPv4) address for system Ethernet port 1.
-gw
e (Optional) The IPv4 gateway for system Ethernet port 1.

436 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -mask
e (Optional) The IPv4 subnet for system Ethernet port 1.
-clusterip_6
e (Optional) The Internet Protocol Version 6 (IPv6) address for system Ethernet port 1.
-gw_6
e (Optional) The IPv6 gateway for system Ethernet port 1.
-prefix_6
e (Optional) The IPv6 prefix for system Ethernet port 1.
-namecluster_name
(Optional) The name of the new system.
-panel_name
(Optional) Identifies the node being serviced.

2 Remember: You must specify one of the following:

2 v IPv4 system IP, gateway and subnet
2 v IPv6 system IP, gateway, and prefix

Description

This command creates a new system.

Input (with specific -clusterip, -gw, and -mask parameters)

satask mkcluster -clusterip 192.168.1.2 -gw 192.168.1.1 -mask 255.255.255.0

rescuenode
Use the rescuenode command to start automatic recovery for a specific node.

Syntax


satask rescuenode -force

-panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.
-force

Attention: The -force parameter is required because this service action can cause temporary or
permanent loss of access to data. Use this command only when the node reports corrupted software.

Description

This command starts automatic recovery for a specific node. Use this command only when the node
reports corrupted software.

An invocation example
satask rescuenode -force 112233

The resulting output

Chapter 26. Service task commands 437

 No feedback

resetpassword
Use the resetpassword command to reset the clustered system (system) superuser password to passw0rd.

Syntax


satask resetpassword


Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.

Description

This command resets the system superuser password to passw0rd. The next time you log in to the
graphical user interface (GUI), you will be prompted for a new password.

e An invocation example
e satask resetpassword

e The resulting output

e No feedback

restartservice
Use the restartservice command to restart a named service.

Syntax


satask restartservice -service service_name panel_name


Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
-service service_name
Specifies the name of the service that you want to restart. The following services are supported:
sshd
Secure Shell Daemon
slpd
Service Location Protocol Daemon
easy
Easy Tier
tomcat
Web server
cimom
CIMOM

438 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 panel_name
Identifies the node being serviced.

Description

When directed to do so by IBM support, use this command to restart a named service.

e An invocation example
e satask restartservice -service cimom

e The resulting output

e No feedback

setlocale (satask)
The setlocale command changes the satask and sainfo command output to the chosen language on the
current node.

Syntax


satask setlocale -locale locale_id


Parameters
-locale locale_id
Specifies the locale ID.

Description

This command changes the language in which error messages are displayed as output from the
command-line interface. Subsequently, all error messages from the command-line tools are generated in
the chosen language. This command is run when you request a change of language (locale) and is
generally run from the web page. Issue the satask setlocale command to change the locale setting for
the system; all interface output is changed to the chosen language. For example, to change the language
to Japanese, type the following:

satask setlocale -locale 3

where 3 is the value for Japanese. The following values are supported:
v 0 US English (default)
v 1 Simplified Chinese
v 2 Traditional Chinese
v 3 Japanese
v 4 French
v 5 German
v 6 Italian
v 7 Spanish
v 8 Korean
v 9 Portuguese (Brazilian)

Note: This command does not change the front panel display panel settings.

Chapter 26. Service task commands 439

An invocation example (where 3 is Japanese)
satask setlocale -locale 3

The resulting output

No feedback

An invocation example (where 8 is Korean)

satask setlocale -locale 8

The resulting output

No feedback

setpacedccu
Use the setpacedccu command to flag a node to participate in a user-paced concurrent code upgrade.

Syntax


satask setpacedccu

panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.

Description

Use this command to flag a node to participate in a user-paced concurrent code upgrade. This command
can only be used when the node is:
v In a service state
v Error-free
v Not part of a cluster when the node is out of a service state
[No feedback]

settempsshkey
Use the settempsshkey command to install a temporary Secure Shell (SSH) key for a superuser ID to run
commands in the service assistant CLI.

Syntax


satask settempsshkey -keyfile filename

-panel_name

Parameters
-keyfile filename
Specifies the name of the file that contains the Secure Shell (SSH) public key. The file identified by
filename must be on the local node (or on the USB flash drive, if you execute the command from
there).
panel_name
(Optional) Identifies the node being serviced.

440 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Description

This command installs a temporary SSH key for a superuser ID to run commands in the service assistant
CLI (for example, to copy files to or from the node).

You can only perform this command when performing a service action. Installing a temporary key will
replace any available existing keys. The key will be deleted when the node joins a cluster or is rebooted
or power cycled.
[No feedback.]

snap
Use the snap command to create a snap file on the node that you specify.

Syntax


satask snap

-dump panel_name

Parameters
-dump
(Optional) Collects the existing dump.
panel_name
(Optional) Identifies the node being serviced.

Description

This command creates a snap file on the node that you specify.

The name of the output file is snap.single.nodeid.date.time.tgz.

startservice
Use the startservice command to enter a service state.

Syntax


satask startservice

-force -panel_name

Parameters
e satask
e System Administrator task; service commands that are only used in specific circumstances.
-force
(Optional) Overrides checking of clustered system (system) membership.
panel_name
(Optional) Identifies the node being serviced.

Chapter 26. Service task commands 441

Description

This command enters a service state. For example, you might use a service state to remove a node from
the candidate list, or to prevent it from automatically being added to a system again. The -force flag is
required if the action could interrupt I/O (last node in cluster or IO group). This commands holds the
node in service state until it is cleared using the satask stopservice command, or until the I/O process
is restarted.

An invocation example
satask startservice

The resulting output

No feedback

stopnode
Use the stopnode command to power off, reboot, or warmstart a node.

Syntax


satask stopnode -poweroff | -reboot | -warmstart

panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.
-poweroff
Powers off the node.
-reboot
Reboots the node.

Attention: To use the -reboot parameter, you must first be in service state. To enter service state,
issue the satask startservice command. After the reboot completes, you can exit from service state.
-warmstart
Restarts the I/O process and issues a diagnostic dump.

Description

Use this command to power off a node, reboot a node, or restart the I/O process.

Powering off canister 1 in enclosure 2:

satask stopnode -poweroff 02-1

stopservice
Use the stopservice command to exit a service state.

Syntax


satask stopservice

-panel_name

442 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Parameters
panel_name
(Optional) Identifies the node being serviced.

Description

This command exits service state entered using the startservice command, and exits the service state on
the local node.

Input
satask stopservice

Output
Node is no longer in service state

t3recovery
Use the t3recovery command to prepare and start a T3 recovery.

Syntax


satask t3recovery -prepare

-execute panel_name

Parameters
panel_name
(Optional) Identifies the node being serviced.
-prepare
Search for T3 recovery data. This locates the date of the necessary backup file and quorum disk.
-execute
Start T3 recovery using recovered data.

Description

This command prepares and starts a T3 recovery. Progress of a T3 recovery can be displayed using the
sainfo lscmdstatus command.

Chapter 26. Service task commands 443

444 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 27. Tracing commands
Tracing commands capture information that can assist you with troubleshooting managed disks and
virtual disks.

setdisktrace
Use the setdisktrace command to set a list of disks of a given type, to include in a disk trace.

Syntax
e

setdisktrace -type mdisk -set -all

vdisk -reset -objectid -id
name_list

Parameters
-type mdisk | vdisk
(Required) Specifies the object type for the disks.
-set
(Optional) Specifies the set argument. You cannot use the -set parameter with the -reset parameter.
-reset
(Optional) Specifies the reset argument. You cannot use the -set parameter with the -reset parameter.
-all
(Optional) Traces all disks of the specified type. You cannot use the -all parameter with the -objectid
parameter.
-objectid id | name_list
(Optional) Specifies a list of one or more disk IDs or names. You cannot use the -objectid parameter
with the -all parameter.

Description

The setdisktrace command marks the disks to be included in the next triggered trace.

The command is used with the settrace command, which sets the options that result in a trace file and
the data that is included in the trace file.

An invocation example
setdisktrace -type mdisk -objectid
mdisk1:mdisk3:mdisk11:mdisk10:mdisk9:mdisk5 -reset

The resulting output

No feedback

settrace
The settrace command sets options to trace certain I/O operations through the system.

© Copyright IBM Corp. 2003, 2012 445

Syntax


settrace -type mdisk -file filename -trigger full

vdisk status
command
timeout
trigger
abort

-abort -timestamp -data -tag -detect -init

-sense -cmds -percent percentage

-cmdlist cmd_list
-cmdmask cmd_mask


-skcqlist skcq_list
-skcqmask skcq_mask

Parameters
-type mdisk | vdisk
(Required) Specifies the type of objects to trace.
-file filename
(Required) Specifies the file name prefix for the trace file.
-trigger full | status | command | timeout | trigger | abort
(Required) Specifies an action for when the trace is started (triggered).
full Specifies to stop the trace when the trace buffer is full, for MDisks and VDisks.
status Sets a trigger for when the specified SCSI status (-skcqlist) is reported in sense data, for
MDisks and VDisks.
command
Specifies a trigger for when the given SCSI command (-cmdlist) is sent, for MDisks and
VDisks.
timeout
Sets a trigger for when a timeout occurs, for MDisks only.
trigger
Specifies to keep running until the trigger event, for MDisks only.
abort Sets a trigger for when an abnormal end occurs, for VDisks only.
-abort
(Optional) Adds abnormal ending details to the trace, for VDisks only.
-timestamp
(Optional) Adds a time-stamp to each entry in the trace. A file name is created from the prefix plus a
time-stamp. The file name is in the form prefix_AAAAAA_YYMMDD_HHMMSS, where AAAAAA is
the panel name of the node generating the trace file.
-data
(Optional) Adds I/O data to the trace.

446 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
-tag
(Optional) Adds CCB tags to the trace, for MDisks only.
-detect
(Optional) Adds MDisk discovery details to the trace, for MDisks only.
-init
(Optional) Adds MDisk initialization details to the trace, for MDisks only.
-sense
(Optional) Adds SCSI sense data to the trace, for VDisks only.
-cmds
(Optional) Adds commands data to the trace, for VDisks only.
-percent percentage
(Optional) Specifies the trigger point in the trace file, which determines the amount of data to collect
after the trigger point. The default value is 50, which places the trigger point in the middle of the
trace file.
-cmdlist cmd_list
(Optional) Adds the commands in the cmd_list to the trace file.
-cmdmask cmd_mask
(Optional) Adds the commands in the cmd_mask to the trace file. The -cmdmask parameter must be
used with the -cmdlist parameter.
-skcqlist skcq_list
(Optional) Specifies an SKCQ list, which adds only those SKCQ details to the trace file.
-skcqmask skcq_mask
(Optional) Specifies an SKCQ mask, which adds only those SKCQ details to the trace file. The
-skcqmask parameter must be used with the -skcqlist parameter.

Description

The settrace command sets the various I/O tracing options for managed disks or virtual disks. When the
relevant disk type trace is subsequently triggered, the options specify the data to be included in the trace
file.

The file name specifies a file name prefix to use when you are generating a trace file. The system
appends the node panel name and a timestamp to the file name.

A maximum of 10 trace files are kept on the cluster. When the eleventh trace is made, the oldest existing
trace file is overwritten.

The directory can also hold files that are retrieved from other nodes. These files are not counted. The
cluster deletes the oldest file to maintain the maximum number of files.

An invocation example
settrace -type vdisk -file tracedump -trigger abort
-percent 100 -abort -timestamp

The resulting output

No feedback

starttrace
Use the starttrace command to begin tracing I/O operations that are based on the option currently set for
the specified object type and the list of disks to trace.

Chapter 27. Tracing commands 447

Syntax


starttrace -type mdisk

vdisk

Parameters
-type mdisk | vdisk
Specifies the object type to trigger.

Description

This command starts the collection of I/O tracing information. The trace file is generated according to the
options that you specified in the settrace command. The disks that are traced are those that are identified
in the list that is set by the setdisktrace command.

The traces are written to the /dumps/iotrace directory. You can view the contents of this directory using
the lsiotracedumps command.

An invocation example
starttrace -type vdisk

The resulting output

No feedback

stoptrace
Use the stoptrace command to stop tracing operations for the specified disk type.

Syntax


stoptrace -type mdisk

vdisk

Parameters
-type mdisk | vdisk
(Required) Specifies the object type to stop tracing.

Description

This command stops the tracing of I/O operations for the specified object type.

An invocation example
stoptrace -type mdisk

The resulting output

No feedback

448 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 28. User management commands
You can use the command-line interface (CLI) to configure remote authentication service and manage
users and user groups on the clustered system.

chauthservice
The chauthservice command can be used to configure the remote authentication service of the clustered
system (system).

Syntax


chauthservice

-enable yes -type tip -url url
no ldap

-username user_name -password -sslcert file_name
password


-refresh

1 Parameters
1 -enable yes | no
1 (Optional) Enables or disables the SAN Volume Controller system's use of the remote authentication
1 server. When the enable parameter is set to no, remote authentications are failed by the system, but
1 local authentications continue to operate normally.
1 -type tip | ldap
1 (Optional) Specifies the authentication service type (TIP or native LDAP). Before changing -type,
1 ensure that the remote authentication type selected is properly configured.

1 Remember:
1 v The remote authentication service must be enabled (-enable yes) for this setting to come into
1 effect.
1 v Before changing -type from ldap to tip, ensure that all users configured for remote authentication
1 have both an SSH key and password configured.
1 -url url
1 (Optional - Tivoli Integrated Portal only) Specifies the web address of the Tivoli Integrated Portal
1 (TIP). This must be a valid IPv4 or IPv6 network address. You can use the following characters: a - z,
1 A - Z, 0 - 9, _, ~, :, [, ], %, or /. The maximum length of the web address is 100 characters.
1 -username user_name
1 (Optional) Specifies the HTTP basic authentication user name. The user name cannot start or end
1 with a blank. The user name can consist of a string of 1 - 64 ASCII characters with the exception of
1 the following characters: %:",*' .
1 -password password
1 (Optional) Specifies the HTTP basic authentication user password. The password cannot start or end

© Copyright IBM Corp. 2003, 2012 449

1 with a blank. It must consist of a string of 6 - 64 printable ASCII characters. The password variable is
1 optional. If you do not provide a password, the system prompts you and does not display the
1 password that you type.
1 -sslcert file_name
1 (Optional) Specifies the name of the file that contains the SSL certificate, in privacy enhanced mail
1 (PEM) format, for the remote authentication server. The certificate file must be in valid PEM format
1 and have a maximum length of 4096 bytes.
1 -refresh
1 (Optional) Causes the SAN Volume Controller to invalidate any remote user authorizations that are
1 cached on the system. Use this when you modify user groups on the authentication service and want
1 the change to immediately take effect on the SAN Volume Controller.

1 Description

1 This command can be used to select and enable a remote authentication service for use with the system.
1 The system can be configured to authenticate users against Tivoli Integrated Portal (TIP) or using
1 Lightweight Directory Access Protocol (LDAP).

1 Before enabling remote authentication, ensure that the properties of the service are properly configured
1 on the system. It is not necessary to disable the remote authentication service to change its properties.
1 This command can be used to configure the TIP properties. LDAP authentication can be configured using
1 the chldap command, and LDAP servers can be added to the system using the mkldapserver command.

1 Remember: For the authentication type to be set to LDAP with authorization enabled (true), an LDAP
1 server must be configured. For authentication type to be set to TIP with authorization enabled (true), the
1 TIP settings (URL, username, password) must be configured.

1 To disable the remote authentication service in a controlled manner when it is not available, use the
1 enable parameter with the no option.

1 When the authentication service is enabled or the configuration is changed, the system does not test
1 whether the remote authentication system is operating correctly.
1 v To establish whether the system is operating correctly, issue the lscurrentuser command for a
1 remotely authenticated user. If the output lists the user roles obtained from the remote authentication
1 server, remote authentication is operating successfully. If the output is an error message, remote
1 authentication is not working correctly, and the error message describes the problem.
1 v To establish whether LDAP is operating correctly, in addition to the lscurrentuser command, issue the
1 testldapserver command. The testldapserver command can be issued whether or not remote
1 authentication is enabled, and can be used to test the connection to LDAP servers, as well as user
1 authorization and authentication.

1 The Web address in the TIP url parameter can have either of the following formats:
1 v http://network_address:http remote authentication service port number/path_to_service
1 v https://network_address:https remote authentication service port number/path_to_service

1 The network address must be an IPv4 or IPv6 address. Do not use the corresponding host name.

1 For example, if the system network IPv4 address is 9.71.45.108, you could enter either of the following
1 corresponding addresses:
1 http://9.71.45.108:16310/TokenService/services/Trust
1 https://9.71.45.108:16311/TokenService/services/Trust

1 An invocation example

450 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 To fully configure and enable authentication with Tivoli Integrated Portal:
1 chauthservice -url https://9.71.45.108:16311/TokenService/services/Trust
1 -sslcert /tmp/sslCACert.pem -username admin -password password -enable yes

1 The resulting output

1 No feedback

1 An invocation example

1 To disable remote authentication:

1 chauthservice -enable no

1 The resulting output

1 No feedback

1 An invocation example

1 To switch to an HTTPS connection to the authentication service:

1 chauthservice -url https://9.71.45.108:16311/TokenService/services/Trust
1 -sslcert /tmp/ssl_cert.pem

1 The resulting output

1 No feedback

1 An invocation example

1 To refresh the SAN Volume Controller remote authorization cache:

1 chauthservice -refresh

1 The resulting output

1 No feedback

chcurrentuser
The chcurrentuser command changes the attributes of the current user.

Syntax


chcurrentuser

-password -keyfile sshkey_filename
cleartext_password -nokey
-nopassword

Parameters
-password cleartext_password
(Optional) Specifies the new password to be associated with the current user. The password cannot
start or end with a blank. It must consist of a string of 6 - 64 printable ASCII characters. You can
optionally specify the password with the password parameter. If you do not specify the password, the
system prompts you for it before running the command and does not display the password that you
type. Either the password parameter or the nopassword parameter can be set.
-nopassword
(Optional) Specifies that the user's password is to be deleted.

Chapter 28. User management commands 451

-keyfile sshkey_filename
(Optional) Specifies the name of the file that contains the Secure Shell (SSH) public key. Either the
keyfile parameter or the nokey parameter can be set.
-nokey
(Optional) Specifies that the user's SSH key is to be deleted.

Description

Use the chcurrent user command to modify the attributes of the current user.

An invocation example
chcurrentuser -password secret -nokey

The resulting output

No feedback

chldap
The chldap command changes system-wide Lightweight Directory Access Protocol (LDAP) configuration.
This command can be used to configure remote authentication with LDAP. These settings apply when
authenticating against any of the LDAP servers configured using the mkldapserver command.

Syntax


chldap

-type
ad
itds
other
-reset

-username username -security tls
-password none
password
-encpassword
password

-userattribute user_attribute -groupattribute group_attribute


-auditlogattribute auditlogattribute -nestedgroupsearch client
server
off

Parameters
-type ad |itds|other | -reset
(Optional) Specify the LDAP server type, or reset LDAP configuration to defaults for the current
server type. Defaults for the configured server type:
v Active Directory (AD)
v IBM Tivoli Directory Server (ITDS)
v Other

452 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -username username
(Optional) Specifies a username for administrative binding. This can be:

Note:
v A distinguished name (DN)
v A user principal name (UPN) or NT login name for Active Directory
-password password
(Optional) Specifies the password for the administrative binding. You can optionally specify the
password with this parameter. If you do not specify the password, the system prompts you for it
before running the command and does not display the password that you type.
2 -encpassword password
2 (Optional) Specifies the password for the enclosure. You can optionally specify the password with this
2 parameter. If you do not specify the password, the system prompts you for it before running the
2 command and does not display the password that you type.
-security tls | none
(Optional) Specifies the type of security to use when communicating with LDAP servers.
-userattribute user_attribute
(Optional) Specifies the LDAP attribute used to determine the user name of remote users. The user
attribute must exist in your LDAP schema and must be unique for each of your users.
-groupattribute group_attribute
(Optional) Specifies the LDAP attribute used to determine the group memberships of remote users.
The attribute must contain either the DN of a group or a colon-separated list of group names.
-auditlogattribute auditlogattribute
(Optional) Specifies the LDAP attribute used to determine the identity of remote users. When a user
performs an audited action, this information is recorded in the audit.
-authcacheminutes auth_cache_minutes
(Optional) Specifies the period for which to cache authentication details.
-nestedgroupsearch client | server | off
(Optional) Specifies whether nested groups are evaluated on the client (clustered system), server
(authentication service), or are not evaluated not at all.

Description

At least one parameter must be specified.

The chldap command can be run whether or not LDAP authentication is enabled. Specifying -reset or
-type populates the default values unless otherwise specified.

e You can only specify -password or -encpassword if -username is specified.

The -type parameter values are only set to defaults for the specified type if the type is different from the
existing type.

If the type is itds, -nestedgroupsearch cannot be executed (nested groups are evaluated by default). If
the type is ad, -nestedgroupsearch can only be set to client or off because there is no server support. If
the type is other, the -nestedgroupsearch parameter is fully configurable.

Use -username to specify a distinguished name (DN), user principal name (UPN), or NT login name.
Distinguished names (DN) must be a sequence of attribute=value pairs separated by a comma (,),
semi-colon(;), or plus sign (+). A backslash (\,) should be used to escape special characters, and can also
be used to specify UTF-8 characters using their byte encoding. For example, c acute can be represented as

Chapter 28. User management commands 453

\C4\87. NT logins are valid for only the Active Directory and should be in the DOMAIN\user format. These
logins must not start or end with a period (.) and both the DOMAIN and the user should not use the
following characters: \/:?"<>| UPN logins are valid for Active Directory only and should be in the
format user@suffix. Both user and suffix not use spaces or the following characters: ()<>,;:\"[]@

Tip:
v Remember that -userattribute, -groupattribute, and -auditlogattribute accept values that:
1. Must begin with a letter
2. Only contain ASCII letters, digit characters, and hyphens
3. Are case-insensitive

The following LDAP (first-time) configuration suggestions assist with LDAP server setup:

Important:
v Ensure that the system is configured appropriately according to your LDAP schema. Issue chldap
-type to populate the system's LDAP configuration with the server type defaults. Issue chldap -reset
to return to these defaults at any time.
– (Advanced) For all server types, users are authenticated with a username configured in the LDAP
attribute user_attribute. This attribute must exist in the LDAP schema and must be unique for
each user. It is configurable by issuing chldap -userattribute. Active Directory users can also
authenticate using their UPN or NT login names.
– (Advanced) Authenticated users are assigned roles according to their LDAP group memberships.
Each user's group memberships must be stored in the LDAP attribute group_attribute. This can be
either an LDAP attribute containing the DN of the user's LDAP group, or an LDAP attribute
containing a colon-separated list of user group names. It is configurable by issuing chldap
-groupattribute.
– (Advanced) When an LDAP authenticated user runs a command that is audited, the user's login
name is placed in the audit log. The name is extracted from the LDAP attribute
audit_log_attribute, which is configurable by issuing chldap -auditlogattribute.
v Ensure that the system is able to search within the user and group trees on LDAP servers. By default
the system authenticates anonymously. Consequently, you must either permit anonymous searches of
the LDAP directory, or create an LDAP user with the appropriate permissions and issue the chldap
-username and chldap -password commands to instruct the system to search as this user.
v Ensure that the system is able to connect with the appropriate level of security. Passwords are sent to
the LDAP server as clear text, so Transport Layer Security (TLS) encryption is recommended. Issue
chldap -security to change the security level.
v (Advanced): On Active Directory and some other LDAP servers, the system (by default) identifies
groups to which users belong directly. To assign users permissions according to a parent group, enable
the nested group search on the client by issuing chldap -nestedgroupsearch. This setting has an
additional performance overhead and supports up to 8 levels of nesting.

An invocation example
chldap -type
itds -username uid=joebloggs,cn=admins,dc=company,dc=com -password passw0rd
-auditlogattribute descriptiveName

The resulting output

No feedback

chldapserver
The chldapserver command modifies a Lightweight Directory Access Protocol (LDAP) server.

454 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Syntax


chldapserver

-ip ip_address -name server_name -port port

-sslcert file_name -basedn base_dn -preferred yes
-nosslcert -nobasedn no

ldap_server_id

ldap_server_name

Parameters
-ip ip_address
(Optional) Specifies the server IP address (Internet Protocol Version 4 or 6).
-name server_name
(Optional) Specifies the LDAP server name.
-port port
(Optional) Specifies the LDAP server port.
-sslcert file_name | -nosslcert
(Optional) Set (-sslcert) or clear (-nosslcert) the secure socket layer (SSL) certificate.
-basedn base_dn | -nobasedn
(Optional) Use the base distinguished name (DN) for search (-nobasedn indicates to use the default
DN).
-preferred yes | no
(Optional) Specifies whether the server is preferred over other configured LDAP servers (or not
preferred).
ldap_server_id | ldap_server_name
(Required) Specifies the LDAP server ID or name.

Description

Important: During normal operation, LDAP requests are sent to -preferred servers depending on
availability. If no servers are marked as -preferred, LDAP requests are sent to configured servers based
on availability.

If -sslcert is specified, the server certificate is verified while authenticating. The SSL certificate must
exist on the current node. If -nosslcert is specified, any certificate file is deleted and the server certificate
is not checked.

The -basedn parameter indicates the distinguished name (DN) to use as a base from which to search for
users in the LDAP directory. If Transport Layer Security (TLS) is enabled and -sslcert is specified, the
server certificate is verified during authentication. The secure socket layer (SSL) certificate must exist on
the node being used. Otherwise, a server certificate is not checked.

The clustered system (system) must be configured with an appropriate version IP address when -ip is
specified. The IP address specified with the -ip parameter must be of a version supported by the system.
The certificate file must be in valid privacy enhanced mail (PEM) format and have a maximum length of
4096 bytes.

Chapter 28. User management commands 455

Distinguished names must be a sequence of attribute=value pairs separated by a comma (,),
semi-colon(;), or plus sign (+) escaping special characters with \ where appropriate, and specified UTF-8
characters using their byte encoding. For example, \, for commas or \C4\87 for the UTF-8 character c
acute.

This command runs whether or not LDAP authentication is enabled.

Remember: There can be a maximum of six configured LDAP servers. If you attempt to create a seventh
LDAP server an error is returned.

An invocation example with basic server details

chldapserver -ip 192.135.60.3 -port 400 ldapserver0

An invocation example specifying an SSL certificate

chldapserver -sslcert /tmp/activedirectorycert.pem 0

The resulting output

No feedback

An invocation example to remove an SSL certificate

chldapserver -nosslcert 0

The resulting output

No feedback

chuser
The chuser command changes the attributes of an existing user.

Syntax


chuser

-password -keyfile sshkey_filename
cleartext_password -nokey
-nopassword

user_id_or_name

-remote yes -usergrp group_id_or_name
no

Parameters
-password cleartext_password
(Optional) Specifies the new password to be associated with the user. The password cannot start or
end with a blank. It must consist of a string of 6 - 64 printable ASCII characters. You can optionally
specify the password with the password parameter. If you do not specify the password, the system
prompts you for it before running the command and does not display the password that you type.
Either the password parameter or the nopassword parameter can be set.
-nopassword
(Optional) Specifies that the user's password is to be deleted.
-keyfile sshkey_filename
(Optional) Specifies the name of the file that contains the Secure Shell (SSH) public key. Either the
keyfile parameter or the nokey parameter can be set.

456 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -nokey
(Optional) Specifies that the user's SSH key is to be deleted.
-remote yes | no
(Optional) Specifies whether the user authenticates to the cluster using a remote authentication
service. Either the yes or no option must be set.
-usergrp group_id_or_name
(Optional) Specifies the new group for the user.
user_id_or_name
(Required) Specifies the user whose attributes are to be changed.

Description

Use the chuser command to modify the attributes of an existing user.

You must have the Security Administrator role to create, delete, or change a user.

Only use the usergrp parameter for local users. If you change a user from local to remote, the user's
association with any group is removed.

If you change a user from remote to local, a user group must be specified. If you change a user from
local to remote, the user must have both a password and an SSH key.

If you use the keyfile parameter, the SSH key file should be placed in the /tmp directory before running
this command. When you run the command, the SSH key is copied into cluster state and activated for
the user, and the input file is deleted.

An invocation example
chuser -remote no -usergrp Monitor -nokey jane

The resulting output

No feedback

chusergrp
The chusergrp command changes the attributes of an existing user group.

Syntax


chusergrp group_id

-role role_name -remote yes group_name
no

Parameters
-role role_name
(Optional) Specifies the role to be associated with users that belong to this group. One of the
following roles must be selected: Monitor, CopyOperator, Service, Administrator, or SecurityAdmin.
-remote yes | no
(Optional) Specifies whether this user group should be used to set the role of remote users. Either the
yes or no option must be set.
e group_id | group_name
(Required) The ID or name of the user group whose attributes are to be changed.

Chapter 28. User management commands 457

Description

Use the chusergrp command to modify the attributes of an existing user group.

You must have the Security Administrator role to create, delete, or change a user.

The roles of the default groups cannot be changed.

An invocation example
chusergrp -role Administrator admin

The resulting output

No feedback

getstatus
Use this command to determine the current service state of the node canister.

Attention: Run this command only when instructed by IBM support. Running this command before
consulting IBM can affect your I/O operations.

Syntax


sainfo getstatus


Parameters

None.

Description

This command writes the output from each node to the USB flash drive.

This command calls the sainfo lsservicenodes command, the sainfo lsservicestatus command, and
the sainfo lsservicerecommendation command.

mkuser
The mkuser command creates either a local or a remote user to access a SAN Volume Controller clustered
system (system).

Syntax


mkuser -name user_name -remote

-usergrp group_id
group_name


-password -keyfile sshkey_filename
cleartext_password

458 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
-name user_name
(Required) Specifies the unique user name. The user name cannot start or end with a blank. The user
name must consist of a string of 1 - 256 ASCII characters, with the exception of the following
characters: %:",*' .
e -remote | -usergrp
e (Required) Specifies whether the user authenticates to the system using a remote authentication
e service or system authentication methods.Either the remote parameter or the usergrp parameter must
e be set. If usergrp is specified, it must be followed by group_name or group_id (see next parameter).
e group_name | group_id
e (Required if usergrp is specified) The ID or name of the user group with which the local user is to be
e associated.
-password cleartext_password
(Optional) Specifies the password to be associated with the user. The password cannot start or end
with a blank. It must consist of a string of 6 - 64 printable ASCII characters. You can optionally
specify the password with the password parameter. If you do not specify the password, the system
prompts you for it before running the command and does not display the password that you type.
-keyfile sshkey_filename
(Optional) Specifies the name of the file that contains the Secure Shell (SSH) public key.

Description

The mkuser command creates a new local or remote user to access a system. The command returns the ID
of the created user.

You must have the Security Administrator role to create, delete, or change a user.

If you create a local user, you must specify the existing user group that the user belongs to. All local
users must have a group. The user group defines roles that provide the user with access to specific
operations on the system. You must also specify either the keyfile or password parameter, or both.

If you create a remote user, you must specify both the keyfile and password parameters. Remote users
have their groups defined by the remote authentication service.

Up to 400 users can be defined on the system. You can also create new users and assign keys to them.

If you use the keyfile parameter, the SSH key file should be placed in the /tmp directory before running
this command. When you run the command, the SSH key is copied into system state and activated for
the user, and the input file is deleted.

An invocation example
mkuser -name jane -usergrp Service -password secret

The resulting output

User, id [1], successfully created

lsldap
The lsldap command displays the details for the system-wide Lightweight Directory Access Protocol
(LDAP) configuration.

Chapter 28. User management commands 459

Syntax


lsldap

-delim delimiter

Parameters
-delim delimiter
(Optional) By default, in a concise view all columns of data are space-separated, with the width of
each column set to the maximum possible width of each item of data. In a detailed view, each item of
data is an individual row, and if displaying headers, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. Enter -delim : on the command line, and the colon character (:) separates all
items of data in a concise view (for example, the spacing of columns does not occur); in a detailed
view, the specified delimiter separates the data from its header

Description
Table 59. lsldap attribute values
Attribute Value
type LDAP server type:
v Active Directory: ad
v IBM Tivoli Directory Server: itds
v Other: other
enabled Is native LDAP authentication enabled?
error_sequence_number Sequence number of non-fixed LDAP configuration error log
username Binding username or distinguished name (or blank if there is none)
security Type of security in use:
v Transport Layer Security: tls
v No security: none
user_attribute LDAP attribute representing user login
group_attribute LDAP attribute representing user group membership
audit_log_attribute LDAP attribute representing user name in audit log
auth_cache_minutes Period (in minutes) for which to cache session details
nested_group_search Handling of nested groups:
v No nested group handling: off
v Search nested groups on the client: client
v Search nested groups on the server: server

An invocation example
lsldap -delim :

The resulting output

type:ad
enabled:yes
error_sequence_number:12
username:[email protected]
security:tls
user_attribute:sAMAccountName

460 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
group_attribute:memberOf
audit_log_attribute:userPrincipalName
auth_cache_minutes:10
nested_group_search:off

lsldapserver
The lsldapserver command displays the most recent details for all configured Lightweight Directory
Access Protocol (LDAP) servers.

Syntax


lsldapserver

ldap_server_id -delim delimiter
ldap_server_name

Parameters
ldap_server_id | ldap_server_name
(Optional) Specifies the ID or name for LDAP server being used.
-delim delimiter
(Optional) By default, in a concise view all columns of data are space-separated, with the width of
each column set to the maximum possible width of each item of data. In a detailed view, each item of
data is an individual row, and if displaying headers, the data is separated from the header by a
space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. Enter -delim : on the command line, and the colon character (:) separates all
items of data in a concise view (for example, the spacing of columns does not occur); in a detailed
view, the specified delimiter separates the data from its header

Description

Remember:
v The base distinguished name (DN) is located at the end of the concise view information; other fields
must be added before the base DN.
v The command fails if a server is specified that does not exist.
Table 60. lsldapserver attribute values
Attribute Value
id ID of the LDAP server
name Name of the LDAP server
error_sequence_number Sequence number of non-fixed LDAP server error log
IP address IP address of the LDAP server (Internet Protocol Versions 4 and 6)
port LDAP server port
cert_set Certificate setting (Is a certificate configured?)
preferred Server preference (Is this server preferred?)
base_dn Base distinguished name used in LDAP searches

Description

This command displays details for the configured Lightweight Directory Access Protocol (LDAP) servers.

Note: There is a maximum of six configured LDAP servers.

Chapter 28. User management commands 461
A concise invocation example
lsldapserver -delim :

The resulting output

id:name:error_sequence_number:IP_address:port:cert_set:preferred:base_dn
0:ldapserver0::192.135.60.3:389:no:yes:ou=users,dc=company,dc=com
1:ldapserver1:12:192.135.60.4:389:no:no:ou=users,dc=company,dc=com
2:ldapserver2::192.135.60.5:389:yes:yes:ou=users,dc=company,dc=com
3:ldapserver3::192.135.60.6:389:yes:no:ou=users,dc=company,dc=com

A detailed invocation example

lsldapserver -delim : ldapserver0

The resulting output

id:0
name:ldapserver0
error_sequence_number:
IP_address:192.135.60.3
port:389
cert_set:no
preferred:yes
base_dn:ou=users,dc=company,dc=com

mkldapserver
The mkldapserver command displays the data used to create a Lightweight Directory Access Protocol
(LDAP) server.

Syntax


mkldapserver -ip ip_address

-name server_name -port port


-sslcert file_name -basedn base_dn -preferred

Parameters
-ip ip_address
(Required) Specifies the server IP address (Internet Protocol Version 4 or 6).
-name server_name
(Optional) Specifies the LDAP server name.
-port port
(Optional) Specifies the LDAP server port.
-sslcert file_name
(Optional) Set the SSL certificate.
-basedn base_dn
(Optional) Use the base distinguished name for search.
-preferred
(Optional) Specifies that this server is preferred over other configured LDAP servers.

462 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Description

Important: During normal operation, LDAP requests are sent to -preferred servers depending on
availability. If no servers are marked as -preferred, LDAP requests are sent to configured servers based
on availability.

If -sslcert is specified, the server certificate is verified while authenticating.

Note: The SSL certificate must exist on the current node.

If -nosslcert is specified, any certificate file is deleted and the server certificate is not checked.

The -basedn parameter indicates the distinguished name (DN) to use as a base from which to search for
users in the LDAP directory. If Transport Layer Security (TLS) is enabled and -sslcert is specified, the
server certificate is verified during authentication. The secure socket layer (SSL) certificate must exist on
the node being used, otherwise a server certificate is not checked.

The clustered system (system) must be configured with an appropriate version IP address when -ip is
specified. The IP address specified with the -ip parameter must be of a version supported by the system.
The certificate file must be in valid privacy enhanced mail (PEM) format and have a maximum length of
4096 bytes.

Distinguished names must be a sequence of attribute=value pairs separated by a comma (,),

semi-colon(;), or plus sign (+) escaping special characters with a backslash (\) where appropriate, and
specified UTF-8 characters using their byte encoding. For example, \, for commas or \C4\87 for the
UTF-8 character c acute.

This command runs whether or not LDAP authentication is enabled.

Remember: There is a maximum of six configured LDAP servers. Attempting to create a seventh LDAP
server returns an error.

An invocation example
mkldapserver -ip 192.135.60.3

The resulting output

LDAP Server, id [0], successfully created

mkusergrp
The mkusergrp command creates a new user group.

Syntax


mkusergrp -name group_name -role role_name

-remote

Parameters
-name group_name
(Required) Specifies the unique user group name. The group name cannot start or end with a blank.
The group name must consist of a string of 1 - 64 ASCII characters, with the exception of the
following characters: %:",*' .
-role role_name
(Required) Specifies the role to be associated with all users that belong to this user group. One of the
following roles must be selected: Monitor, CopyOperator, Service, Administrator, or SecurityAdmin.
Chapter 28. User management commands 463
-remote
(Optional) Specifies that this user group should be used to set the role of remote users. This is
disabled by default.

Description

The mkusergrp command creates a new user group to organize users of the SAN Volume Controller
cluster by role. Use the lsusergrp command to view a list of user groups that have been created on the
cluster.

You must have the security administrator role (SecurityAdmin role name) to create, delete, or change a
user group.

Each user group has one role that determines the role of users that belong to that group. Use the role
parameter to specify one of the following roles for the user group:
Monitor
Users can issue the following commands: finderr, dumperrlog, dumpinternallog, chcurrentuser,
ping, svcconfig backup, and all of the information commands.
CopyOperator
Users can issue the following commands: prestartfcconsistgrp, startfcconsistgrp, stopfcconsistgrp,
chfcconsistgrp, prestartfcmap, startfcmap, stopfcmap, chfcmap, startrcconsistgrp, stoprcconsistgrp,
switchrcconsistgrp, chrcconsistgrp, startrcrelationship, stoprcrelationship, switchrcrelationship,
chrcrelationship, and chpartnership. In addition, users can issue all of the commands allowed by
the Monitor role.
Service
Users can issue the following commands: applysoftware, setlocale, addnode, rmnode, cherrstate,
writesernum, detectmdisk, includemdisk, clearerrlog, cleardumps, settimezone, stopcluster,
startstats, stopstats, and settime. In addition, users can issue all of the commands allowed by the
Monitor role.
Administrator
Users can issue all commands except: chauthservice, mkuser, rmuser, chuser, mkusergrp,
rmusergrp, chusergrp, and setpwdreset
SecurityAdmin
Users can issue all commands.

The command returns the ID of the created user group.

An invocation example
mkusergrp -name support -role Service

The resulting output

User Group, id [5], successfully created

rmldapserver
The rmldapserver command deletes a Lightweight Directory Access Protocol (LDAP) server.

Syntax


rmldapserver ldap_server_id

ldap_server_name

464 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Parameters
ldap_server_id | ldap_server_name
(Required) Specifies the LDAP server ID or name to delete.

Description

Remember:
v If remote authentication with LDAP is enabled, the final LDAP server cannot be deleted. To delete the
final LDAP server disable LDAP authentication by specifying chauthservice -enable no.
v The rmldapserver command can be specified whether or not LDAP authentication is enabled.

An invocation example
rmldapserver ldapserver0

The resulting output

No feedback

rmuser
The rmuser command deletes a user.

Syntax
e

rmuser user_id

user_name
e

Parameters
user_id or user_name
(Required) Specifies the user to be removed.

Description

Use the rmuser command to delete a user.

You must have the Security Administrator role to create, delete, or modify a user.

An invocation example
rmuser jane

The resulting output

No feedback

rmusergrp
The rmusergrp command deletes a user group.

Syntax
e

rmusergrp group_id

-force group_name

Chapter 28. User management commands 465

 Parameters
-force
(Optional) Specifies that the user group should be deleted even if there are users in the group.
e group_id | group_name
(Required) The ID or name of the user group to be removed.

Description

Use the rmusergrp command to delete a user group.

You must have the Security Administrator role to create, delete, or change a user group.

User groups with users cannot normally be deleted. If you use the force parameter, the group is deleted
and all of the users in that group are assigned to the Monitor group. Default user groups cannot be
deleted, even if the force parameter is set.

An invocation example
rmusergrp support

The resulting output

No feedback

testldapserver
The testldapserver command tests a Lightweight Directory Access Protocol (LDAP) server.

Syntax


testldapserver

-username user_name ldap_server_id
-password ldap_server_name
password


-delim delimiter

Parameters
-username user_name
(Optional) Specifies the user name to test.
-password password
(Optional) Specifies the password to test. You can optionally specify the password with this
parameter. If you do not specify the password, the system prompts you for it before running the
command and does not display the password that you type.

Note: The -password parameter is only valid if -username is specified. The actual password does not
need to be supplied.
ldap_server_id|ldap_server_name
(Optional) Specifies the LDAP server ID or name to test.
-delim delimiter
(Optional) By default, in a concise view all columns of data are space-separated, with the width of
each column set to the maximum possible width of each item of data. In a detailed view, each item of
data is an individual row, and if displaying headers, the data is separated from the header by a

466 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a
one-byte character. Enter -delim : on the command line, and the colon character (:) separates all
items of data in a concise view (for example, the spacing of columns does not occur); in a detailed
view, the specified delimiter separates the data from its header

Description

The testldapserver command allows three levels of testing:

v Server connection test (issue testldapserver without supplying username or password). This verifies
that a connection can be established with the server while authenticating using the configured
administrator credentials according to the LDAP configuration.
v Server connection, LDAP configuration, and user authorization test (issue testldapserver with a
username). This verifies that:
– A connection can be established with the server while authenticating using the configured
administrator credentials.
– The LDAP attributes are correctly configured on the system.
– The user has been assigned a role.
v Server connection, LDAP configuration, and user authentication test (issue testldapserver with a
username and password). This verifies that:
– A connection can be established with the server while authenticating using the configured
administrator credentials.
– The user authenticates with the supplied password

No specific server errors indicates success.

Important: This command works whether or not LDAP authentication is selected or enabled with the
chauthservice command.
Table 61. testldapserver attribute values
Attribute Value
id LDAP server ID
name LDAP server name
error Critical server error (or success, depending on situation) encountered

An invocation example with one LDAP server and no specific user information
testldapserver -delim ":" ldapserver1
id:name:error
1:ldapserver1:CMMVC7075I The LDAP task completed successfully

An invocation example with all LDAP servers using a UPN

testldapserver -username [email protected] -delim ":"
id:name:error
0:ldapserver0:CMMVC6518E The task has failed because no roles are defined for the current user on the system.
1:ldapserver1:CMMVC7075I The LDAP task completed successfully.
2:ldapserver2:CMMVC7075I The LDAP task completed successfully.

Chapter 28. User management commands 467

468 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Chapter 29. Virtual disk commands
e The virtual disk commands enable you to work with virtual disk options with the SAN Volume
e Controller.

addvdiskcopy
e The addvdiskcopy command adds a copy to an existing VDisk (volume), which changes a nonmirrored
e volume into a mirrored volume.

Note: The first syntax diagram depicts the addition of a sequential or striped mode volume. The second
syntax diagram depicts the addition of an image mode volume.

Syntax

addvdiskcopy -mdiskgrp mdisk_group_id_list

mdisk_group_name_list -mirrorwritepriority latency striped
redundancy -vtype
seq

-mdisk mdisk_id_list
mdisk_name_list

1


-rsize disk_size
disk_size_percentage% -warning disk_size -autoexpand 32
auto disk_size_percentage% -grainsize 64
128
256
-compressed

vdisk_name

-fmtdisk -createsync -syncrate rate mb -easytier on vdisk_id
-unit b off
kb
gb
tb
pb

addvdiskcopy -mdiskgrp mdisk_group_id_list

-mirrorwritepriority latency mdisk_group_name_list
redundancy

-vtype image -mdisk mdisk_id_list

mdisk_name_list

1


-rsize disk_size
disk_size_percentage% -warning disk_size -autoexpand 32
auto disk_size_percentage% -grainsize 64
128
256
-compressed
-import

-fmtdisk -createsync -syncrate rate mb -tier generic_ssd -easytier on
-unit b generic_hdd off
kb
gb
tb
pb

vdisk_name

vdisk_id

addvdiskcopy

© Copyright IBM Corp. 2003, 2012 469

1


-rsize disk_size
disk_size_percentage% -warning disk_size
auto disk_size_percentage%

-compressed
-import

Parameters
-mdiskgrp mdisk_group_id_list | mdisk_group_name_list
(Required) Specifies the managed disk groups to use to create copies for the virtual disk. You must
specify a group for each copy that is being added.
-mirrorwritepriority latency | redundancy
(Optional) Specifies how to configure the mirror write algorithm priority.
1. Choosing latency indicates a copy that is slow to respond to a write I/O; it becomes
unsynchronized if the other copy successfully writes the data.
2. Choosing redundancy indicates that a copy (which is slow to respond to a write I/O) causes the
response to be delayed until completion to maintain synchronization.
3. If not specified, the current value is unchanged.
-vtype seq | striped | image
(Optional) Specifies the virtualization type for the copy: sequential, striped, or image. The type can be
different than the virtualization types for other copies on the volume. The default virtualization type
is striped.
-mdisk mdisk_id_list | mdisk_name_list
(Optional) Specifies one or more managed disks (MDisks). For sequential and image mode copies,
you must specify a single MDisk that has sufficient free extents. For image mode copies, the MDisk
must be in unmanaged mode. For sequential mode copies the MDisk must be in the managed mode.
-syncrate rate
(Optional) Specifies the copy synchronization rate. A value of zero (0) prevents synchronization. For
the supported -syncrate values and their corresponding rates, see Table 63 on page 473.
If not specified, the current value is unchanged.
-createsync
(Optional) Suppresses the synchronization of the new volume copy with the primary copy. Using this
parameter can cause data corruption if the primary copy fails and leaves an unsynchronized
secondary copy to provide data. Using this parameter can cause loss of read stability in unwritten
areas if the primary copy fails, data is read from the primary copy, and then different data is read
from the secondary copy. To avoid data loss or read stability loss, use this parameter only for a
primary copy that has been formatted and not written to, and with the -fmtdisk parameter.
-fmtdisk
(Optional) Formats a sequential or striped mode copy. You must also specify the -createsync
parameter, which labels the formatted copy as identical to the primary copy. The -fmtdisk parameter
causes the volume to go offline until new volume copy formatting completes. To query the formatting
progress, use the lsvdiskprogress command.
-rsize disk_size | disk_size_percentage% | auto
(Optional) Makes the copy space-efficient and specifies the real size of the copy. Specify the disk_size
| disk_size_percentage value using an integer, or an integer immediately followed by the percent
character (%). The default units for disk_size are megabytes (MB); to specify different units, use the
-unit parameter. The auto option creates a volume copy that uses the entire size of the MDisk; if you
specify the -rsize auto option, you must also specify the -vtype image option.

470 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
2 compressed
2 (Optional) Requires the -rsize parameter also be specified. Adds exactly one copy to an existing
2 volume that already has (only) one copy a volume, and enables compression.

2 Remember:
2 v You cannot specify this parameter with the -grainsize parameter.
2 v When you specify this parameter with the -import parameter, you must specify -rsize auto.
2 -warning disk_size | disk_size_percentage%
(Optional) Requires that the -rsize parameter also be specified. Generates a warning when the used
disk capacity on the space-efficient copy first exceeds the specified threshold. You can specify a
disk_size integer, which defaults to megabytes (MB) unless the -unit parameter is specified; or you can
specify a disk_size%, which is a percentage of the virtual disk size. If -autoexpand is enabled, the
default value for -warning is 80% of the virtual disk capacity. If -autoexpand is not enabled, the
default value for warning is 80% of the real capacity. To disable warnings, specify 0.
-autoexpand
(Optional) Requires that the -rsize parameter also be specified. Specifies that space-efficient copies
automatically expand their real capacities by allocating new extents from their managed disk group.
If the -autoexpand parameter is specified, the -rsize parameter specifies a capacity that is reserved by
the copy. This protects the copy from going offline when its managed disk group runs out of space
by allowing it to consume this reserved space first.
-grainsize 32 | 64 | 128 | 256
(Optional) Requires that the -rsize parameter also be specified. Sets the grain size (KB) for a
2 space-efficient volume copy. The grain size value must be 32, 64, 128, or 256 KB. The default is 256
2 KB.
-unit b | kb | mb | gb | tb | pb
(Optional) Specifies the data units for the -rsize and -warning parameters.
-import
e (Optional) Imports an image mode disk that contains a space-efficient volume into the clustered
e system (system). Requires that the -rsize and -vtype image parameters also be specified.
vdisk_name | vdisk_id
(Required) Specifies the virtual disk to add the volume copy to, either by ID or by name.
e -tiergeneric_ssd | generic_hhd
e (Optional) Specifies the MDisk tier when an image mode copy is added.
e -easytieron | off
e (Optional) Determines if the IBM System Storage Easy Tier function is allowed to move extents for
e this volume. If a volume copy is striped and not being migrated the following table applies:
e Table 62. Storage pool Easy Tier settings
e Storage pool Easy Tier Number of tiers in the Volume copy Easy Tier Volume copy Easy Tier
e setting storage pool setting status
e Off One Off inactive (see note 2 on page
e 472)
e Off One On inactive (see note 2 on page
e 472)
e Off Two Off inactive (see note 2 on page
e 472)
e Off Two On inactive (see note 2 on page
e 472)
e Auto (see note 5 on page One Off inactive (see note 2 on page
e 472) 472)

Chapter 29. Virtual disk commands 471

e Table 62. Storage pool Easy Tier settings (continued)
e Storage pool Easy Tier Number of tiers in the Volume copy Easy Tier Volume copy Easy Tier
e setting storage pool setting status
e Auto (see note 5) One On inactive (see note 2)
e Auto (see note 5) Two Off measured (see note 3)
e Auto (see note 5) Two On active (see note 1)
e On (see note 5) One Off measured (see note 3)
e On (see note 5) One On measured (see note 3)
e On (see note 5) Two Off measured (see note 3)
e On (see note 5) Two On active (see note 1)
e Note:
e 1. If the volume copy is in image or sequential mode or is being migrated then the volume copy Easy Tier status is
e measured instead of active.
e 2. When the volume copy status is inactive , no Easy Tier functions are enabled for that volume copy.
e 3. When the volume copy status is measured, the Easy Tier function collects usage statistics for the volume but
e automatic data placement is not active.
e 4. When the volume copy status is active, the Easy Tier function operates in automatic data placement mode for
e that volume.
e 5. The default Easy Tier setting for a storage pool is auto, and the default Easy Tier setting for a volume copy is on.
e This means that Easy Tier functions are disabled for storage pools with a single tier, and that automatic data
e placement mode are enabled for all striped volume copies in a storage pool with two tiers.
e

e Description

The addvdiskcopy command adds a copy to an existing volume , which changes a nonmirrored volume
into a mirrored volume. Use the -mdiskgrp parameter to specify the managed disk group that provide
storage for the copy; the lsmdiskgrp command lists the available managed disk groups and the amount
of available storage in each group.

The addvdiskcopy command can be specified with a filesystem volume, but must be used with the same
storage pool for that volume.

Remember: Only compressed copies are allowed to be added to filesystem volumes.

The addvdiskcopy command adds a different volume copy, such as a copy created from a uncompressed
to compressed conversion or a compressed to uncompressed conversion.

The virtualization types are defined as follows:

sequential (seq)
This policy requires the -mdisk parameter with a single managed disk as its argument. This
MDisk must be in the managed mode.
It creates the virtual disk using extents from the given managed disk (assuming there are enough
free extents on the managed disk).
striped
This is the default policy. If the -vtype parameter is not specified, this policy is used in its default
form. That is, all managed disks in the managed disk group are used to create the virtual disk.
The striping is at an extent level; one extent from each managed disk in the group is used. For
example, a managed disk group with 10 managed disks uses one extent from each managed disk,
then it uses the 11th extent from the first managed disk, and so on.
If the -mdisk parameter is also specified, you can supply a list of managed disks to use as the
stripe set. This can be two or more managed disks from the same managed disk group. The same

472 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 circular algorithm is used across the striped set. However, a single managed disk can be specified
more than once in the list. For example, if you enter -m 0:1:2:1, the extents are from the
following managed disks: 0, 1, 2, 1, 0, 1, 2, and so forth. All MDisks that are specified in the
-mdisk parameter must be in managed mode.
image This policy allows image mode virtual disks to be created when a managed disk already has data
on it, perhaps from a previrtualized subsystem. When an image mode virtual disk is created, it
directly corresponds to the (previously unmanaged) managed disk that it was created from;
therefore, virtual disk logical block address (LBA) x equals managed disk LBA x. You can use this
e command to bring a nonvirtualized disk under the control of the system. After it is under the
control of the system, you can migrate the virtual disk from the single managed disk. When it is
migrated, the virtual disk is no longer an image mode virtual disk.
e You can add image mode volumes to an already populated managed disk group (storage pool)
with other types of volumes, such as a striped or sequential.

Note: An image mode copy must be at least as large as the volume that it is being added to, but
any capacity beyond the size of the volume is not accessible.

The command returns the ID of the newly created volume copy.

Remember:
1 v Create the first compressed volume copy for an I/O group to activate compression.
2 v You cannot create or move a compressed volume copy to an I/O group that contains (at least) one
2 node that does not support compressed volumes. You must use another I/O group, but note that this
2 does not affect moving to the recovery I/O group.

Table 63 provides the relationship of the rate value to the data copied per second.
Table 63. Relationship between the rate value and the data copied per second
User-specified rate attribute value Data copied/sec
1 - 10 128 KB
11 - 20 256 KB
21 - 30 512 KB
31 - 40 1 MB
41 - 50 2 MB
51 - 60 4 MB
61 - 70 8 MB
71 - 80 16 MB
81 - 90 32 MB
91 - 100 64 MB

An invocation example
addvdiskcopy -mdiskgrp 0 -easytier off vdisk8

The resulting output

Vdisk [8] copy [1] successfully created

e An invocation example for specifying managed disk groups

e addvdiskcopy -mdiskgrp 0 -vtype image -mdisk 13 -tier generic_ssd -easytier off vdisk9

e The resulting output

Chapter 29. Virtual disk commands 473

e Vdisk [9] copy [1] successfully created

e An invocation example for configuring a mirror write algorithm priority

addvdiskcopy -mdiskgrp 0 -mirrorwritepriority latency vdisk9

1 An invocation example for adding a compressed volume copy

1 addvdiskcopy -mdiskgrp 1 -rsize 10% -compressed vdisk2

1 addvdiskaccess
e The addvdiskaccess adds an I/O group (or groups) to the set of I/O groups in which a volume can be
e made accessible to hosts.

1 Syntax

1

addvdiskaccess -iogrp iogrp_id_list vdisk_id


iogrp_name_list vdisk_name
1

1 Parameters
1 -iogrp iogrp_id_list | iogrp_name_list
1 (Required) Specifies a list of I/O groups to add to the I/O group volume access set.
1 vdisk_id | vdisk_name
e (Required) Specifies the volume to which to add access through the specified I/O groups.

1 Description

1 If an I/O group is already a member of the access set, no error is generated and no action is taken for
1 that I/O group. All host mappings for the volume are added to the I/O groups in the list. The -force
1 option is not required to extend additional mappings to other I/O groups.

1 When an I/O group is added to the access set, it creates access to the volume from the hosts that are
1 mapped to the volume from the nodes in the I/O group. If the volume is mapped twice, it is also
1 mapped twice through all additional I/O groups.

1 Remember: The -addvdiskaccess command fails if:

1 v Any host (for which the volume has a host mapping) is not associated with an I/O group in the list
1 v Any host mapped to the volume is an Internet Small Computer System Interface (iSCSI) host
1 v The host volume mapping limit is exceeded
1 v The amount of extra mappings added exceeds the clustered system limit for host volume mappings

1 Two mappings are created if a host is mapped to a volume with two I/O groups. Hosts are limited to 512
1 host-to-volume mappings, which means a host can be mapped to:
1 v 512 volumes in a single I/O group
1 v 256 volumes across two I/O groups
1 v 64 volumes across four I/O groups

e The command fails if any host mapped to the volume is detected as a host system that does not support
e volumes being mapped from multiple I/O groups.

1 This example adds I/O group 2 to the volume access set for DB_Volume:

474 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 An invocation example
1 addvdiskaccess -iogrp 2 DB_Volume

1 The resulting output

2 No feedback

1 This example adds I/O groups 2 and 3 to the volume access set for volume ID 3:

1 An invocation example
1 addvdiskaccess -iogrp 2:3 3

1 The resulting output

e No feedback
1
chvdisk
e The chvdisk command modifies the properties of a volume, such as the disk name, I/O governing rate,
e or unit number.

Syntax

chvdisk

e
-name new_name_arg

-cache readwrite
none -force
-rate throttle_rate [ -unitmb ]
-udid vdisk_udid
-warning disk_size | disk_size_percentage %
-unit b -copy id
kb
mb
gb
tb
pb
-autoexpand on
off -copy id
-primary copy_id
-syncrate rate
-easytier on
off -copy id
-mirrorwritepriority latency
redundancy

vdisk_name

vdisk_id

Parameters
-name new_name_arg
(Optional) Specifies a new name to assign to the volume. You cannot use this parameter with the
-rate or -udid parameters. This parameter is required if you do not use the -rateor -udid parameters.
-cache readwrite | none
(Optional) Specifies the caching options for the volume. Valid entries are readwrite, to enable the
cache for the volume, or none, to disable the cache mode for the volume.
-force
(Optional) The force parameter can only be used for changing the I/O group of a volume or the
caching mode. Use the force parameter with the iogrp parameter to force the volume to be removed

Chapter 29. Virtual disk commands 475

 from an I/O group. Use the force parameter with the cache parameter to specify that you want the
system to change the cache mode of the volume even if the I/O group is offline. This option
overrides the cache flush mechanism.

Attention: If the force parameter is used for changing the caching mode, the contents of the cache
are discarded and the volume might be corrupted by the loss of the cached data. This could occur if
the system is able to destage all write data from the cache or not. The force parameter should be
used with caution.
-rate throttle_rate [-unitmb]
(Optional) Specifies the I/O governing rate for the volume, which caps the amount of I/O that is
accepted. The default throttle_rate units are I/Os. To change the throttle_rate units to megabytes per
e second (MBps), specify the -unitmb parameter. The governing rate for a volume can be specified by
e I/Os or by MBps, but not both. However, you can set the rate to I/Os for some volumes and to
MBps for others.
You cannot use this parameter with the -name or -udid parameters.
-udid vdisk_udid
(Optional) Specifies the unit number (udid) for the disk. The vdisk_udid is an identifier that is
required to support OpenVMS hosts; no other systems use this parameter. Valid options are a decimal
number from 0 to 32 767 or a hexadecimal number from 0 to 0x7FFF. A hexadecimal number must be
preceded by 0x (for example, 0x1234). If you do not use the -udid parameter, the default udid is 0.
You cannot use this parameter with the -name or -udid parameters.
-warning disk_size | disk_size_percentage%
(Optional) Generates a warning when the used disk capacity on the space-efficient copy first exceeds
the specified threshold. You can specify a disk_size integer, which defaults to MBs unless the -unit
e parameter is specified; or you can specify a disk_size%, which is a percentage of the volume size. To
disable warnings, specify 0 or 0%.
-unit b | kb | mb | gb | tb | pb
e (Optional) Specifies the data units to use for the -warning disk_size parameter. The default unit value
e is MB.
-autoexpand on | off
(Optional) Specifies whether space-efficient volume copies automatically expand their real capacities
by allocating new extents from their managed disk group. To use this parameter, the volume must be
space-efficient.
-copy id
(Optional) Specifies the copy to apply the changes to. You must specify this parameter with the
-autoexpand or -warning parameter. The -copy parameter is required if the specified volume is
mirrored and only one volume copy is space-efficient. If both copies are space-efficient and the -copy
parameter is not specified, the specified -autoexpand or -warning parameter is set on both copies.
-primary copy_id
(Optional) Specifies the primary copy. Changing the primary copy only takes effect when the new
primary copy is online and synchronized. If the new primary is online and synchronized when the
command is issued, the change takes effect immediately.
-syncrate rate
(Optional) Specifies the copy synchronization rate, as a percentage of the peak synchronization rate. A
value of zero (0) prevents synchronization.
-easytier on | off
(Optional) Enables or disables the IBM System Storage Easy Tier function.

476 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 -mirrorwritepriority latency | redundancy
(Optional) Specifies how to configure the mirror write algorithm priority. A change to the mirror
write priority is reflected in the volume's view immediately and in the volume's behavior after all
prior input and output (I/O) completes.
1. Choosing latency indicates a copy that is slow to respond to a write I/O; it becomes
unsynchronized if the other copy successfully writes the data.
2. Choosing redundancy indicates that a copy (which is slow to respond to a write I/O) causes the
response to be delayed until completion to maintain synchronization.
3. If not specified, the current value is unchanged.
vdisk_name | vdisk_id
(Required) Specifies the volume to modify, either by ID or by name.

Description

3 To change the caching I/O group for a volume, use the “movevdisk” command.

3 The chvdisk command modifies a single property of a volume. To change the volume name and modify
3 the synchronization rate, for example, you must issue the command twice.

3 Note: If the volume is offline, use one of the recovervdisk commands to recover the volume and bring it
3 back online.

3 Important: To change the caching I/O group for a volume, use the movevdisk command.

e You can specify a new name or label. You can use the new name subsequently to refer to the volume.

e You can set a limit on the amount of I/O transactions that is accepted for this volume. It is set in terms of
e I/Os per second or MBs per second. By default, no I/O governing rate is set when a volume is created.

Attention: All capacities, including changes, must be in multiples of 512 bytes. An error occurs if you
specify a capacity that is not a multiple of 512, which can only happen when byte units (-b) are used. The
default capacity is in MB.

e When the volume is created, there is no throttling applied to it. Using the -rate parameter can change
e this. To change the volume back to an unthrottled state, specify 0 (zero) with the -rate parameter.

An invocation example
e chvdisk -rate 2040 1

The resulting output

No feedback

1 movevdisk
1 The movevdisk command moves the caching I/O group of a volume.

1 Syntax

1

movevdisk -iogrp iogrp_id

1 iogrp_name -force -node node_id
node_name

Chapter 29. Virtual disk commands 477

1
vdisk_id

vdisk_name
1

1 Parameters
1 -iogrp iogrp_id | iogrp_name
1 (Required) Specifies the I/O group to move the volume to.
2 -force
2 (Optional) Use the force parameter to force the volume to be removed from an I/O group. This
2 option overrides the cache flush mechanism.

2 Remember:
2 v If the force parameter is used , the contents of the cache are discarded and the volume might be
2 corrupted by the loss of the cached data. This could occur if the clustered system is able to destage
2 all write data from the cache or not. The -force parameter should be used with caution.
2 v If the force parameter is used to move a volume that has out-of-sync copies, a full
2 resynchronization is required.
2 -node node_id | node_name
e (Optional) Specifies the node ID or name in the new group that is assigned as the preferred node.
1 vdisk_id | vdisk_name
e (Required) Specifies the volume to move.

1 Description

1 The movevdisk command does not change which I/O groups can access the volume - only the caching
1 I/O group is changed. You can move a volume that is in a Flash Copy (FC) mapping, but the FC bitmaps
1 remain in the original I/O group. The volumes cannot be moved when the FC mapping is in prepare
1 state.

e If your system is running with more than one I/O group, you can (non-disruptively) change the
e preferred node using the movevdisk command.

1 A compressed volume can also be moved, and you can also specify the preferred node in the new I/O
1 group.

2 If the volume is offline, use one of the recovervdisk commands to recover the volume and bring it back
2 online. To specify a preferred node for the volume, use the -node node_id | node_name parameter with
2 the movevdisk command. Use the movevdisk command to change the I/O group with which this volume
2 is associated.

2 Important: Do not move:

2 v A volume to an offline I/O group under any circumstance; to avoid any data loss make sure that the
2 I/O group is online before moving the volumes
2 v An offline volume to the recovery I/O group

2 Use of the recovery I/O group is not required. Instead, use one of the recovervdisk commands to recover
2 the volume and bring it back online. You can migrate a volume to a new I/O group to manually balance
2 the workload across the nodes in the clustered system. You might end up with a pair of nodes that are
2 overworked and another pair that are underworked. Use the movevdisk command to migrate a single
2 volume to a new I/O group. Repeat for other volumes as required.

1 This example moves DB_Volume to I/O group 2:

478 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
1 An invocation example
1 movevdisk -iogrp 2 DB_Volume

1 The resulting output

1 No feedback

1 This example moves DB_Volume to I/O group IOGRP3, with a new preferred node id 7:

1 An invocation example
1 movevdisk -iogrp IOGRP3 -node 7 DB_Volume

1 The resulting output

1 No feedback
1
expandvdisksize
The expandvdisksize command expands the size of a VDisk (volume) by a given capacity.

Syntax


expandvdisksize -size disk_size

-rsize disk_size -mdisk mdisk_id_list
mdisk_name_list

vdisk_name

-fmtdisk -unit b -copy id vdisk_id
kb
mb
gb
tb
pb

Parameters
-size disk_size
(Optional) Specifies the capacity by which the virtual disk is expanded. Disk size is used with the
value of the unit. All capacities, including changes must be in multiples of 512 bytes. An error occurs
if you specify a capacity that is not a multiple of 512, which can only occur when byte units (-unit b)
are used. However, an entire extent is reserved even if it is only partially used. The default disk_size
unit is megabytes (MB). You cannot specify the -size parameter with the -rsize parameter. You must
specify either -size or -rsize. If the volume is space-efficient, MDisks cannot be specified.
-rsize disk_size
(Optional) Specifies the capacity by which to increase the real size of a space-efficient volume. Specify
the disk_size value using an integer. Specify the unit for a disk_size integer using the -unit parameter;
the default unit is megabytes (MB). The -rsize value can be greater than, equal to, or less than the
size of the volume. You cannot specify the -rsize parameter with the -size parameter. You must
specify either -size or -rsize.
-copy id
(Optional) Specifies the copy to change the real capacity for. You must also specify the -rsize
parameter; you can only modify the real capacity of a volume copy. The -copy parameter is required
if the specified volume is mirrored and only one copy is space-efficient. If the volume is mirrored,
both copies are space-efficient and -copy is not specified, both copies are modified by the same
amount.

Chapter 29. Virtual disk commands 479

-mdisk mdisk_id_list | mdisk_name_list
(Optional) Specifies the list of one or more MDisks to be used as the stripe set. The extents that
expand the volume come from the specified list of MDisks. All MDisks in the list must be part of the
same MDisk group. The -mdisk parameter cannot be used if the specified volume is mirrored.
-fmtdisk
(Optional) Specifies that the volume be formatted before use. This parameter formats the new extents
that have been added to the volume as a result of the expandvdisksize command. The
expandvdisksize command completes asynchronously if you use this parameter.
-unit b | kb | mb | gb | tb | pb
(Optional) Specifies the disk_size unit for the -size or -rsize parameter. The default value is megabytes
(MB).
vdisk_name | vdisk_id
(Required) Specifies the virtual disk to modify, either by ID or by name.

Description
The expandvdisksize command can be used to expand the physical capacity that is allocated to a
particular volume by the specified amount. The command can also be used to expand the virtual capacity
of a space-efficient volume without altering the physical capacity that is assigned to the volume. To
change the capacity of a non-space-efficient volume, or the virtual capacity of a space-efficient volume,
use the -size parameter. To change the real capacity of a space-efficient volume, use the -rsize parameter.

Note: The volume is a change volume for a relationship.

The default capacity units are MB.

When a volume is expanded, the virtualization policy can change. Its mode becomes striped even if it
was previously sequential. See the mkvdisk command for details of the virtualization policies.

To run the expandvdisksize command on a mirrored volume, all copies of the volume must be
synchronized. The command formats all copies of a mirrored volume automatically.

An invocation example

To increase the capacity of vdisk1 by 2048 bytes by using extents from two MDisks and to format the
new part of the volume, enter:
expandvdisksize -size 2048 -unit b -mdisk mdisk0:mdisk1 -fmtdisk vdisk1

The resulting output

No feedback

An invocation example

To increase the capacity of vdisk1 by 100 MB using extents from two MDisks, and to format the new part
of the volume, enter:
expandvdisksize -size 100 -unit mb -mdisk mdisk0:mdisk1 -fmtdisk vdisk1

The resulting output

No feedback

An invocation example

To increase the real capacity of space-efficient vdisk2 by 100 MB without changing the virtual capacity,
and to spread the extents across all MDisks in the MDisk group, enter:

480 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 expandvdisksize -rsize 100 -unit mb vdisk2

The resulting output

No feedback

An invocation example

To increase the real capacity of space-efficient volume copy id 1 of mirrored volume vdisk3 by 100 MB,
enter:
expandvdisksize -rsize 100 -unit mb -copy 1 vdisk3

The resulting output

No feedback

mkvdisk
e The mkvdisk command creates sequential, striped, or image mode VDisk (volume) objects. When they are
mapped to a host object, these objects are seen as disk drives with which the host can perform I/O
operations.

Note: The first syntax diagram depicts the creation of a striped mode volume. The second syntax
diagram depicts the creation of a sequential or image mode volume.

Syntax

1

mkvdisk -mdiskgrp mdisk_group_id_list -iogrp io_group_id -accessiogrp iogrp_id_list -size disk_size

mdisk_group_name_list io_group_name iogrp_name_list

-fmtdisk

-rsize disk_size
disk_size_percentage% -warning disk_size -autoexpand 32
auto disk_size_percentage% -grainsize 64
128
256

1


-compressed -import -copies num_copies -syncrate rate -createsync

-mirrorwritepriority latency -udid vdisk_udid -vtype striped -mdisk mdisk_id_list
redundancy mdisk_name_list

-node node_name mb -name new_name_arg readwrite -tier generic_ssd
node_id -unit b -cache none generic_hdd
kb
gb
tb
pb


-easytier on
off

1

mkvdisk -mdiskgrp mdisk_group_id_list -iogrp io_group_id -accessiogrp iogrp_id_list

mdisk_group_name_list io_group_name iogrp_name_list -fmtdisk

-rsize disk_size
disk_size_percentage% -warning disk_size -autoexpand 32
auto disk_size_percentage% -grainsize 64
128
256

Chapter 29. Virtual disk commands 481

1


-compressed -import -copies num_copies -syncrate rate -createsync

-mirrorwritepriority latency | redundancy -udid vdisk_udid -vtype seq -mdisk mdisk_id_list
image mdisk_name_list

-node node_name mb -name new_name_arg readwrite -tier generic_ssd
node_id -unit b -cache none generic_hdd
kb
gb
tb
pb


-easytier
on
off

Parameters
-mdiskgrp mdisk_group_id_list | mdisk_group_name_list
(Required) Specifies one or more managed disk groups (storage pools) to use when you are creating
this volume. If you are creating multiple copies, you must specify one managed disk group per copy.
The primary copy is allocated from the first managed disk group in the list.
-iogrp io_group_id | io_group_name
(Required) Specifies the I/O group (node pair) with which to associate this volume.

Remember:
1 v Create the first compressed volume copy for an I/O group to activate compression.
1 v You cannot create or move a volume copy that is compressed to an I/O group that contains at least
1 one node that does not support compressed volumes. You must select another I/O group to move
1 the volume copy to (but this does not affect moving to the recovery I/O group).
1 -accessiogrp iogroup_id_list | iogroup_name_list
1 (Optional) Specifies the members of the volume I/O group access set. If this option is not specified,
1 only the caching I/O group is added to the volume I/O group access set. If any access I/O groups
1 are specified, only those I/O groups are in the access set (including if that set does not include the
1 caching I/O group).
-udid vdisk_udid
(Optional) Specifies the unit number (udid) for the disk. The udid is an identifier that is required to
support OpenVMS hosts; no other systems use this parameter. Valid options are a decimal number 0 -
32 767, or a hexadecimal number 0 - 0x7FFF. A hexadecimal number must be preceded by 0x (for
example, 0x1234).
-size disk_size
(Required for sequential [seq] or striped volume creation) (Optional for image volume creation)
Specifies the capacity of the volume, which is used with the value of the unit. All capacities,
including changes, must be in multiples of 512 bytes. An error occurs if you specify a capacity that is
not a multiple of 512, which can only happen when byte units (-b) are used. However, an entire
extent is reserved even if it is only partially used. The default capacity is in MB. You can specify a
capacity of 0. Specify the size in bytes in multiples of logical block address (LBA) sizes.

Note: If you do not specify the -size parameter when you create an image mode disk, the entire
MDisk capacity is used.
-rsize disk_size | disk_size_percentage% | auto
(Optional) Defines how much physical space is initially allocated to the space-efficient volume
(thin-provisioned volume). This parameter makes the volume space-efficient; otherwise, the volume is
fully allocated. Specify the disk_size | disk_size_percentage value using an integer, or an integer
immediately followed by the percent character (%). Specify the units for a disk_size integer using the
-unit parameter; the default is MB. The -rsize value can be greater than, equal to, or less than the size

482 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 of the volume. The auto option creates a volume copy that uses the entire size of the MDisk; if you
specify the -rsize auto option, you must also specify the -vtype image option.
-fmtdisk
(Optional) Specifies that the volume be formatted before it can be used. The -fmtdisk parameter
formats (sets to all zeros) the extents that make up this volume after it is created. If this parameter is
used, the command completes asynchronously; you can query the status using the lsvdiskprogress
command.
The -fmtdisk parameter is not required when creating space-efficient volumes. Space-efficient
volumes return zeros for extents that have not been written to.
The -fmtdisk parameter synchronizes mirrored copies by default.

Note: You cannot specify this parameter with the -vtype image parameter.
1 compressed
1 (Optional) Creates a volume with one or two copies and enables compression. This option must be
1 specified with -rsize and cannot be specified with -grainsize.
-warning disk_size | disk_size_percentage%
(Optional) Requires that the -rsize parameter also be specified. Specifies a threshold at which a
warning error log is generated for volume copies. A warning is generated when the used disk
capacity on the space-efficient copy first exceeds the specified threshold. You can specify a disk_size
integer, which defaults to MBs unless the -unit parameter is specified; or you can specify a disk_size%,
which is a percentage of the volume size. If -autoexpand is enabled, the default value for -warning is
80% of the volume capacity. If -autoexpand is not enabled, the default value for warning is 80% of
the real capacity. To disable warnings, specify 0.
-autoexpand
(Optional) Specifies that space-efficient copies automatically expand their real capacities by allocating
new extents from their managed disk group. Requires that the -rsize parameter also be specified. If
the -autoexpand parameter is specified, the -rsize parameter specifies a capacity that is reserved by
the copy. This protects the copy from going offline when its managed disk group runs out of space
by having the managed disk group to consume this reserved space first.
The parameter has no immediate effect on image mode copies. However, if the image mode copy is
subsequently migrated to managed mode, the copy is then automatically expanded.
-grainsize 32 | 64 | 128 | 256
(Optional) Sets the grain size (KB) for a space-efficient volume. This parameter also requires that the
-rsize parameter be specified. If you are using the space-efficient volume in a FlashCopy map, use the
same grain size as the map grain size for best performance. If you are using the space-efficient
2 volume directly with a host system, use a small grain size. The grain size value must be 32, 64, 128,
2 or 256 KB. The default is 256 KB.
-import
(Optional) Imports a space-efficient volume from the MDisk. This parameter also requires that the
-rsize parameter be specified.
-copies num_copies
(Optional) Specifies the number of copies to create. The num_copies value can be 1 or 2. Setting the
value to 2 creates a mirrored volume. The default value is 1.
-syncrate rate
(Optional) Specifies the copy synchronization rate. A value of zero (0) prevents synchronization. The
default value is 50. For the supported -syncrate values and their corresponding rates, see Table 64 on
page 487.
-createsync
(Optional) Creates copies in sync. Use this parameter if you have already formatted the MDisks, or
when read stability to unwritten areas of the volume is not required.

Chapter 29. Virtual disk commands 483

e -mirrorwritepriority latency | redundancy
e (Optional) Specifies how to configure the mirror write algorithm priority. If not specified, the default
e value is latency.
e Choosing latency indicates a copy that is slow to respond to a write I/O and:
e 1. Goes out of sync if the other copy successfully writes the data.
e 2. Can use the full ERP time, and the response to the I/O is delayed until it completes in order to
e keep the copy in sync if possible.
-vtype seq | striped | image
(Optional) Specifies the virtualization type. When creating sequential or image mode volumes, you
must also specify the -mdisk parameter. The default virtualization type is striped.
-node node_id | node_name
(Optional) Specifies the preferred node ID or the name for I/O operations to this volume. You can
use the -node parameter to specify the preferred access node.

Note: This parameter is required for the subsystem device driver (SDD). The system chooses a
default if you do not supply this parameter.
-unit b | kb | mb | gb | tb | pb
e (Optional) Specifies the data units to use in conjunction with the capacity that is specified by the -size
e and -rsize parameters. The default unit type is MB.
-mdisk mdisk_id_list | mdisk_name_list
(Optional) Specifies one or more managed disks. For sequential and image mode volumes, the
number of MDisks must match the number of copies. For sequential mode volumes, each MDisk
must belong to the specified storage pool. For striped volumes, you cannot specify the -mdisk
parameter if the -copies value is greater than 1. When creating a single copy striped volume, you can
specify a list of MDisks to stripe across.
-name new_name_arg
(Optional) Specifies a name to assign to the new volume.
-cache readwrite | none
(Optional) Specifies the caching options for the volume. Valid entries are readwrite or none. The
default is readwrite. If you do not specify the -cache parameter, the default value (readwrite) is used.
e -tiergeneric_ssd | generic_hhd
e (Optional) Specifies the MDisk tier when an image mode copy is added.
e generic_ssd
e Refers to storage that uses solid-state drive technology
e generic_hdd
e Refers to storage that uses hard-disk drive technology

e Note: This applies to both copies if you are creating mirrored volume with two image mode copies
e using this command.
e -easytieron | off
Determines if the IBM(r) System Storage(r) Easy Tier(tm) function is allowed to move extents for this
volume.

Note: The -easytier command must be followed by one of the following:

v If set to on, then Easy Tier functions are active.
v If set to off, then Easy Tier functions are inactive.
e If a volume copy is striped and not being migrated the following table applies:

484 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
ee Storage pool Easy Tier(tm) Number of tiers in the Volume copy Easy Tier(tm) Volume copy Easy Tier(tm)
e setting storage pool setting status
e Off One Off inactive (see note {
e IDEP081A: (2) Reference id:
e inactive not found. }
e #svc_addvdiskcopy_3p7qlq/inactive)
e Off One On inactive (see note {
e IDEP081A: (2) Reference id:
e inactive not found. }
e #svc_addvdiskcopy_3p7qlq/inactive)
e Off Two Off inactive (see note {
e IDEP081A: (2) Reference id:
e inactive not found. }
e #svc_addvdiskcopy_3p7qlq/inactive)
e Off Two On inactive (see note {
e IDEP081A: (2) Reference id:
e inactive not found. }
e #svc_addvdiskcopy_3p7qlq/inactive)
e Auto (see note { IDEP081A: One Off inactive (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ inactive not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/inactive)
e #svc_addvdiskcopy_3p7qlq/auto)
e Auto (see note { IDEP081A: One On inactive (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ inactive not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/inactive)
e #svc_addvdiskcopy_3p7qlq/auto)
e Auto (see note { IDEP081A: Two Off measured (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ measured not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/measured)
e #svc_addvdiskcopy_3p7qlq/auto)
e Auto (see note { IDEP081A: Two On active (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ splat not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/splat)
e #svc_addvdiskcopy_3p7qlq/auto)
e On (see note { IDEP081A: One Off measured (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ measured not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/measured)
e #svc_addvdiskcopy_3p7qlq/auto)
e On (see note { IDEP081A: One On measured (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ measured not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/measured)
e #svc_addvdiskcopy_3p7qlq/auto)
e On (see note { IDEP081A: Two Off measured (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ measured not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/measured)
e #svc_addvdiskcopy_3p7qlq/auto)

Chapter 29. Virtual disk commands 485

e Storage pool Easy Tier(tm) Number of tiers in the Volume copy Easy Tier(tm) Volume copy Easy Tier(tm)
e setting storage pool setting status
e On (see note { IDEP081A: Two On active (see note {
e Reference id: IDEP081A: (2) Reference id:
e svc_addvdiskcopy_3p7qlq/ splat not found. }
e auto not found. } #svc_addvdiskcopy_3p7qlq/splat)
e #svc_addvdiskcopy_3p7qlq/auto)
e Note:
e 1. 1.If the volume copy is in image or sequential mode or is being migrated then the volume copy Easy Tier(tm)
e status is measured instead of active.
e 2. 2.When the volume copy status is inactive , no Easy Tier(tm) functions are enabled for that volume copy.
e 3. 3.When the volume copy status is measured, the Easy Tier(tm) function collects usage statistics for the volume but
e automatic data placement is not active.
e 4. 4.When the volume copy status is active, the Easy Tier(tm) function operates in automatic data placement mode
e for that volume.
e 5. 5.The default Easy Tier(tm) setting for a storage pool is auto, and the default Easy Tier(tm) setting for a volume
e copy is on. This means that Easy Tier(tm) functions are disabled for storage pools with a single tier, and that
e automatic data placement mode are enabled for all striped volume copies in a storage pool with two tiers.
e

e Description

This command creates a new volume object. You can use the command to create a variety of types of
volume objects, making it one of the most complex commands.

You must decide which managed disk group or groups provide the storage for the volume. Use the
lsmdiskgrp command to list the available managed disk groups and the amount of free storage in each
group. If you are creating a volume with more than one copy, each storage pool that you specify must
have enough space for the size of the volume.

Important: The extent size for the storage pool can limit volume size. Consider the maximum volume
size you want to use when creating storage pools. Refer to the information on creating storage pools for a
comparison of the maximum volume capacity for each extent size. The maximum is different for
space-efficient volume (thin-provisioned volumes).

Choose an I/O group for the volume. This determines which nodes in the system process the I/O
requests from the host systems. If you have more than one I/O group, ensure that you distribute the
volumes between the I/O groups so that the I/O workload is shared evenly between all nodes. Use the
lsiogrp command to show the I/O groups and the number of volumes that are assigned to each I/O
group.

Note: It is normal for systems with more than one I/O group to have storage pools that have volumes in
different I/O groups. FlashCopy processing can make copies of volumes whether the source and target
volumes are in the same I/O group. If, however, you plan to use intra-system Metro or Global Mirror
operations, ensure that both the master and auxiliary volume are in the same I/O group.

Specify the virtualization type using the -vtype parameter; the supported types are sequential (seq),
striped, and image. This command returns the following information:
sequential (seq)
This virtualization type creates the volume using sequential extents from the specified MDisk (or
MDisks, if creating multiple copies). The command fails if there are not enough sequential extents
on the specified MDisk.
striped
This is the default virtualization type. If the -vtype parameter is not specified, striped is the

486 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 default; all managed disks in the managed disk group are used to create the volume. The striping
is at an extent level; one extent from each managed disk in the group is used. For example, a
managed disk group with 10 managed disks uses one extent from each managed disk, then it
uses the 11th extent from the first managed disk, and so on.
If the -mdisk parameter is also specified, you can supply a list of managed disks to use as the
stripe set. This can be two or more managed disks from the same managed disk group. The same
circular algorithm is used across the striped set. However, a single managed disk can be specified
more than once in the list. For example, if you enter -mdisk 0:1:2:1, the extents are from the
following managed disks: 0, 1, 2, 1, 0, 1, 2, and so forth. All MDisks that are specified in the
-mdisk parameter must be in the managed mode.
A capacity of 0 is allowed.
image This virtualization type allows image mode volumes to be created when a managed disk already
has data on it, perhaps from a previrtualized subsystem. When an image mode volume is created,
it directly corresponds to the (previously unmanaged) managed disk that it was created from.
Therefore, with the exception of space-efficient image mode volumes, volume logical block
address (LBA) x equals managed disk LBA x. You can use this command to bring a
nonvirtualized disk under the control of the system. After it is under the control of the system,
you can migrate the volume from the single managed disk. When it is migrated, the volume is no
longer an image mode volume.
You can add image mode volumes to an already populated storage pool with other types of
volumes, such as a striped or sequential.

Note: An image mode volume must be 512 bytes or greater. At least one extent is allocated to an
image mode volume.
You must use the -mdisk parameter to specify an MDisk that has a mode of unmanaged. The
-fmtdisk parameter cannot be used to create an image mode volume.

Note: If you create a mirrored volume from two image mode MDisks without specifying a
-capacity value, the capacity of the resulting volume is the smaller of the two MDisks, and the
remaining space on the larger MDisk is not accessible.

The command returns the IDs of the newly created volume.

Attention:
1. Do not create a volume in an offline I/O group. You must ensure that the I/O group is online before
you create a volume to avoid any data loss. This applies in particular to re-creating volumes that are
assigned the same object ID.
2. To create an image mode disk, you must already have a quorum disk in the volume because an image
mode disk cannot be used to hold quorum data. Refer to information on quorum disk creation for
more details.
3. The command fails if either limit of 2048 volumes per I/O Group or 8192 volume copies per system is
reached.

Table 64 provides the relationship of the rate value to the data copied per second.
Table 64. Relationship between the rate value and the data copied per second
User-specified rate attribute value Data copied/sec
1 - 10 128 KB
11 - 20 256 KB
21 - 30 512 KB
31 - 40 1 MB

Chapter 29. Virtual disk commands 487

Table 64. Relationship between the rate value and the data copied per second (continued)
User-specified rate attribute value Data copied/sec
41 - 50 2 MB
51 - 60 4 MB
61 - 70 8 MB
71 - 80 16 MB
81 - 90 32 MB
91 - 100 64 MB

An invocation example
mkvdisk -mdiskgrp Group0 -size 0
-iogrp 0 -vtype striped -mdisk mdisk1 -node 1

The resulting output

Virtual Disk, id [1], successfully created

An invocation example for creating an image mode volume

mkvdisk -mdiskgrp Group0
-iogrp 0 -vtype image -mdisk mdisk2 -node 1

The resulting output

Virtual Disk, id [2], successfully created

An invocation example for creating a new volume

mkvdisk -mdiskgrp Group0 -size 0 -unit kb
-iogrp 0 -vtype striped -mdisk mdisk1 -node 1 -udid 1234 -easytier off

The resulting output

Virtual Disk id [2], successfully created

An invocation example for creating a space-efficient volume

mkvdisk -mdiskgrp Group0 -iogrp 0 -vtype striped -size 10 -unit gb -rsize 20% -autoexpand -grainsize 32

The resulting output

Virtual Disk id [1], successfully created

An invocation example for creating a compressed volume copy

mkvdisk -mdiskgrp 0 -iogrp 0 -size 1 -unit tb -rsize 0 -autoexpand -warning 0 -compressed

The resulting output

Virtual Disk id [1], successfully created

An invocation example for creating a mirrored image-mode volume

mkvdisk -mdiskgrp Group0:Group0 -mdisk mdisk2:mdisk3 -iogrp 0 -vtype image -copies 2

The resulting output

Virtual Disk id [1], successfully created

An invocation example for creating a mirrored volume

mkvdisk -iogrp 0 -mdiskgrp 0:1 -size 500 -copies 2

488 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 The resulting output
Virtual Disk id [5], successfully created

3 An invocation example for configuring a mirror write algorithm priority

3 mkvdisk -mdiskgrp Group0 -iogrp 0 -vtype striped -mirrorwritepriority redundancy -size 500

3 An invocation example to create a disk with default grain size

2 mkvdisk -iogrp 0 -mdiskgrp 0 -size 100 -rsize 5%

2 An invocation example for creating a volume with I/O groups 0 and 1 in its I/O group access set
2 mkvdisk -iogrp 0 -mdiskgrp 0 -size 500 -accessiogrp 0:1

mkvdiskhostmap
e The mkvdiskhostmap command creates a new mapping between a VDisk (volume) and a host, which
e makes the volume accessible for input/output (I/O) operations to the specified host.

Syntax


mkvdiskhostmap -host host_id

-force host_name -scsi scsi_num_arg

vdisk_name

vdisk_id

Parameters
-force
(Optional) Allows multiple volume-to-host assignments, which are not normally allowed.
-host host_id | host_name
e (Required) Specifies the host to map the volume to, either by ID or by name.
-scsi scsi_num_arg
e (Optional) Specifies the Small Computer System Interface (SCSI) logical unit number (LUN) ID to
e assign to this volume on the given host. The scsi_num_arg parameter contains the SCSI LUN ID that
e is assigned to the volume on the given host for all I/O groups that provide access to the volume. You
e must check your host system for the next available SCSI LUN ID on the given host bus adapter
e (HBA). If you do not specify the -scsi parameter, the next available SCSI LUN ID in each I/O group
e that provides access is provided to the host.
vdisk_name | vdisk_id
e (Required) Specifies the name of the volume that you want to map to the host, either by ID or by
name.

Description

e This command creates a new mapping between the volume and the specified host. The volume is
presented to the host as if the disk is directly attached to the host. It is only after this command is
e processed, that the host can perform I/O transactions to the volume.

Optionally, you can assign a SCSI LUN ID to the mapping. When the HBA in the host scans for devices
e that are attached to it, it discovers all volumes that are mapped to its Fibre Channel ports. When the
devices are found, each one is allocated an identifier (SCSI LUN ID). For example, the first disk found is
e usually SCSI LUN 1, and so on. You can control the order in which the HBA discovers volumes by
assigning the SCSI LUN ID, as required. If you do not specify a SCSI LUN ID, the cluster automatically

Chapter 29. Virtual disk commands 489

 assigns the next available SCSI LUN ID, if any mappings already exist with that host. When you issue
the mkvdiskhostmap command, the assigned SCSI LUN ID number is returned.

3 The mkvdiskhostmap command fails if the:

3 v Host to which this mapping is being made is not associated with any one of the I/O groups in the
3 volume access set
3 v Volume has more than one I/O group in its access set and the host being mapped to the volume does
3 not support volumes being mapped from multiple I/O groups

e If you generate different SCSI LUN IDs, only one is returned. The returned ID is for the
e highest-numbered I/O group to which the volume was mapped. To view other values, issue
e lshostvdiskmap or lsvdiskhostmap.

The SCSI LUN ID is used for the highest numbered I/O group to which the volume is mapped. < !--

Note: The command fails if the volume is accessible through more than one I/O group and the host
being mapped is known to the system.
-->

Some HBA device drivers stop when they find a gap in the SCSI LUN IDs. For example:
e v Volume 1 is mapped to Host 1 with SCSI LUN ID 1
e v Volume 2 is mapped to Host 1 with SCSI LUN ID 2
e v Volume 3 is mapped to Host 1 with SCSI LUN ID 4

e When the device driver scans the HBA, it must stop after identifying volumes 1 and 2, because no SCSI
LUN is mapped with ID 3. For optimal performance, ensure that the SCSI LUN ID allocation is
contiguous.

You can create multiple volume assignments. Normally, multiple volume-to-host assignments are not
used because corruption is likely to occur if more than one host can access a disk. However, in certain
multiple path environments, such as in the IBM SAN File System, a volume must be mapped to more
than one host. To map to more than one host, you must use the mkvdiskhostmap command with the force
parameter. For example:
mkvdiskhostmap -host host1 -force 4
mkvdiskhostmap -host host2 -force 4

These commands create two host-to-volume mappings for Volume 4 that map to host1 and host2.
Omitting the force parameter causes the mapping to fail if that volume is already mapped to a host.

The command also fails if the host object (to which this mapping is being made) is not associated with
the I/O group containing the volume.

An invocation example
mkvdiskhostmap -host host1 -scsi 1 5

The resulting output

Virtual Disk to Host map, id [1], successfully created

recovervdisk
The recovervdisk command acknowledges VDisk data loss and brings the VDisk back online.

490 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 Syntax


recovervdisk vdisk_name

-copy copy_id vdisk_id

Parameters
vdisk_name | vdisk_id
(Required) Specifies the virtual disk to recover.
-copy copy_id
(Optional) Specifies the ID of the copy to recover.

Description

The specified VDisk, and all copies if mirrored, are recovered and brought back online. If the VDisk is
space-efficient or has space-efficient copies, this command triggers the space-efficient repair process. If the
VDisk is mirrored, the recovervdisk command triggers a resynchronization from a synchronized copy.
The progress of the resynchronization can be monitored using the lsvdisksyncprogress command. The
VDisk remains online during the resynchronization process.

The recovervdisk command also starts the repair of any space-efficient copies that have a fast_write_state
of corrupt. The progress of the repair process can be monitored using the lsrepairsevdiskcopyprogress
command.

A VDisk that is still offline because it is being repaired following the recovervdisk command has a
fast_write_state of repairing. The VDisk is brought online when the repair process is complete.

An invocation example (to recover VDisk 45)

recovervdisk vdisk45

An invocation example (to recover copy 0 of VDisk 45)

recovervdisk -copy 0 vdisk45

1 recovervdiskbycluster
1 Attention: The reecovervdiskbycluster command has been discontinued. Use the recovervdiskbysystem
1 command instead.
1
1 recovervdiskbysystem
1 The recovervdiskbysystem command acknowledges data loss for all volumes in the clustered system
1 (system) with a fast_write_state of corrupt and brings the volumes back online.

1 Syntax

1

recovervdiskbysystem

1

1 Parameters

1 There are no parameters.

Chapter 29. Virtual disk commands 491

1 Description

1 All volumes in the system that have a fast_write_state of corrupt; and all copies, if mirrored, are
1 recovered and brought back online. If any of the volumes are space-efficient or have space-efficient
1 copies, the recovervdiskbysystem command triggers the space-efficient repair process. If volumes are
1 mirrored, the command triggers a resynchronization from a synchronized copy. The progress of the
1 resynchronization can be monitored by using the lsvdisksyncprogress command. Volumes remain online
1 during the resynchronization process.

1 If none of the volumes in the system have a fast_write_state of corrupt, the recovervdiskbysystem
1 command still starts the repair process for any corrupt copies of mirrored volumes. The progress of the
1 repair process can be monitored using the lsrepairsevdiskcopyprogress command. If there are no
1 corrupt volumes or no repairs to copies are required, no error is returned.

1 Volumes that are still offline because they are being repaired following the recovervdiskbysystem
1 command have a fast_write_state of repairing. Volumes are brought online when the repair process is
1 complete.

1 An invocation example
1 recovervdiskbysystem

1 The resulting output

1 No feedback
1
recovervdiskbyiogrp
The recovervdiskbyiogrp command acknowledges data loss for all VDisks in the specified I/O group
with a fast_write_state of corrupt and brings the VDisks back online.

Syntax


recovervdiskbyiogrp io_group_name

io_group_id

Parameters
io_group_name | io_group_id
(Required) Specifies the I/O group for virtual disk recovery.

Description

All VDisks in the specified I/O group that have a fast_write_state of corrupt; and all copies, if mirrored,
are recovered and brought back online. If any of the VDisks are space_efficient or have space_efficient
copies, the recovervdiskbyiogrp command triggers the space-efficient repair process. If VDisks are
mirrored, the command triggers a resynchronization from a synchronized copy. The progress of the
resynchronization can be monitored by using the lsvdisksyncprogress command. VDisks remain online
during the resynchronization process.

If none of the VDisks in the specified I/O group have a fast_write_state of corrupt, the
recovervdiskbyiogrp command still starts the repair process for any corrupt copies of mirrored VDisks.
The progress of the repair process can be monitored using the lsrepairsevdiskcopyprogress command. If
there are no corrupt VDisks or no repairs to copies are required, no error is returned.

VDisks that are still offline because they are being repaired following the recovervdiskbyiogrp command
have a fast_write_state of repairing. VDisks are brought online when the repair process is complete.

492 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
An invocation example
recovervdiskbyiogrp iogrp2

The resulting output

No feedback

repairsevdiskcopy
The repairsevdiskcopy command repairs the metadata on a space-efficient volume and starts a repair
operation on a compressed volume copy.

Syntax


repairsevdiskcopy vdisk_name

-copy 0 | 1 vdisk_id

Parameters
-copy 0 | 1
(Optional) Specifies the volume copy to repair.
vdisk_name | vdisk_id
(Required) Specifies the volume to repair.

Description

The repairsevdiskcopy command repairs the metadata on a space-efficient volume. Run this command
only when you are directed by the fix procedures or by IBM support.

Running the command automatically detects corrupted metadata. The command holds the volume offline
during the repair, but does not prevent the disk from being moved between I/O groups.

If a repair operation completes successfully and the volume was previously offline because of corrupted
metadata, the command brings the volume back online. The only limit on the number of concurrent
repair operations is the number of virtual disk copies in the configuration. Once started, a repair
operation cannot be paused or canceled; the repair can only be ended by deleting the copy.

An invocation example
repairsevdiskcopy vdisk8

The resulting output

No feedback

repairvdiskcopy
The repairvdiskcopy command detects and optionally, corrects any volume copies that are not identical.

Syntax


repairvdiskcopy -medium vdisk_name

-resync -startlba lba vdisk_id
-validate

Chapter 29. Virtual disk commands 493

 Parameters
-medium
(Optional) Converts sectors that contain different contents into virtual medium errors on the specified
volume. This parameter cannot be used with the -validate and -resync parameters; you must enter
one of the three parameters.
-resync
(Optional) Corrects sectors that contain different contents by copying contents from the primary
volume copy to other copies on the specified volume. This parameter cannot be used with the
-medium and -validate parameters; you must enter one of the three parameters.
-validate
(Optional) Reports the first difference found on synchronized online copies of the specified volume,
on or after the specified -startlba value. This parameter cannot be used with the -medium and
1 -resync parameters; you must enter one of the three parameters.This option cannot be used with
1 compressed copies.
-startlba lba
(Optional) Specifies a starting logical block address (LBA) on which to begin the command. The LBA
must be specified in hex, with a 0x prefix.
vdisk_name | vdisk_id
(Required) Specifies the virtual disk to repair. You must specify this parameter last on the command
line.

Description

The repairvdiskcopy command detects and optionally, corrects any volume copies that are not identical.
The results are logged to the SAN Volume Controller error log. The -validate parameter compares
synchronized online copies of the specified volume. The -medium parameter changes any sectors that are
not identical into virtual medium errors. The -resync parameter copies any sectors that are not identical
to the other volume copies. You must specify only one of the three parameters.

Attention:
1. Before you run the repairvdiskcopy command, ensure that all volume copies are synchronized.
2. Only one repairvdiskcopy command can run on a volume at a time. You must wait for the
repairvdiskcopy command to complete processing before running the command again.
3. Once you start the repairvdiskcopy command, you cannot use the command to stop processing.
4. The primary copy of a mirrored volume cannot be changed while the repairvdiskcopy -resync
command is running.

Use the -startlba parameter to specify a starting Logical Block Address (LBA). Enter an LBA value from 0
- full disk size minus one. The parameter logs the first error found and then stops the command. By
repeating this parameter, you can collect all of the instances where the volume copies are not identical.

During repairvdiskcopy command operation, the volume remains online. The I/O and synchronization
operations are allowed while the command is in progress.

The rate for the repairvdiskcopy command is controlled by the synchronization rate of the volume that is
being repaired. To suspend the repair process, set the synchronization rate of the volume to 0 using the
chvdisk command.

An invocation example
repairvdiskcopy -resync -startlba 0x0 vdisk8

The resulting output

494 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 No feedback

rmvdisk
The rmvdisk command deletes a VDisk (volume).

Syntax


rmvdisk vdisk_id

-force vdisk_name

Parameters
-force
(Optional) Deletes the specified volume, even if mappings still exist between this volume and one or
more hosts. This parameter deletes any host-to-volume mappings and any FlashCopy mappings that
exist for this volume. If the -force deletion of a volume causes dependent mappings to be stopped,
any target volumes for those mappings that are in Metro Mirror or Global Mirror relationships are
also stopped. The dependent mappings can be identified by using the lsvdiskdependentmaps
command on the volume that you want to delete.
vdisk_id | vdisk_name
Specifies the name of the volume to delete, either by ID or by name.

1 Note: To deactivate compression, delete the last compressed volume copy for an I/O group.

Description

This command deletes an existing managed mode volume or an existing image mode volume. The
extents that made up this volume are returned to the pool of free extents that are available on the
managed disk group, if the volume is in managed mode.

Attention: Any data that was on the volume is lost. Before you issue this command, ensure that the
volume (and any data that resides on it) is no longer required.

Deleting a managed mode volume

When you use this command to delete a managed mode volume, all the data on the volume is deleted.
The extents that make up the volume are returned to the pool of free extents that are available in the
managed disk group.

If host mappings exist for the volume, or if any FlashCopy mappings would be affected, the deletion
fails. You can use the -force parameter to force the deletion. If you use the -force parameter, mappings
that have the volume as source or target are deleted, other mappings in a cascade might be stopped, and
then the volume is deleted. The -force parameter also deletes any Metro Mirror or Global Mirror
relationships that exist for the specified volume.

If the volume is in the process of migrating to an image mode volume (using the migratetoimage
command), the deletion fails unless you use the -force parameter. If you use the -force parameter, the
migration is halted and then the volume is deleted. Before you issue this command, ensure that the
volume (and any data that resides on it) is no longer required.

Deleting an image mode volume

If the volume is mirrored and one or both copies is in image mode, you must first wait for all fast-write
data to be moved to the controller logical unit. This ensures that the data on the controller is consistent

Chapter 29. Virtual disk commands 495

with the data on the image mode volume before the volume is deleted. This process can take several
minutes to complete, and is indicated by the fast_write_state state of the volume being empty. If the -force
parameter is specified, the fast-write data is discarded and the volume is deleted immediately; the data
on the controller logical unit is left inconsistent and unusable. If the copies are not synchronized, you
must use the -force parameter.

If you run the command while data is in the cache, the system attempts to move the data out of the
cache; this process can time out, however.

If there are any virtual medium errors on the volume, the command fails. You can force the deletion by
using the -force parameter; however, this can cause data integrity problems.

Note: A virtual medium error occurs when you copy data from one disk (the source) to another (the
target). Reading the source indicates that there is a medium error. At that moment, you must have two
identical copies of data and you must then simulate a medium error on the target disk. You can simulate
a medium error on the target disk by creating a virtual medium error on the target disk.

If FlashCopy mappings or host mappings exist for the volume, the deletion fails unless you use the -force
parameter. If you use the -force parameter, mappings are deleted and the volume is deleted. If there is
any data that is not staged in the fast write cache for this volume, the deletion of the volume fails. When
the -force parameter is specified, any data that is not staged in the fast write cache is deleted. Deleting an
image mode volume causes the managed disk that is associated with the volume to be removed from the
managed disk group. The mode of the managed disk is returned to “unmanaged.”

If the relationship is in consistent_copying or consistent_stopped state, and the change volume is being
used by a Global Mirror relationship using multicycling mode, the relationship moves to
inconsistent_copying or inconsistent_stopped state.

Note: If the relationship is part of a consistency group entire group is affected by this state transition.
The secondary volume becomes corrupt, and inaccessible for host input/output I/O data if:
v A changed volume is part of an idling relationship
v The changed volume is being used for secondary protection
v The background copy process is still migrating the change volume data to the secondary volume

You must issue recovervdisk to gain access to the volume contents once more. If a change volume was
part of an idling relationship and being used for Global Mirror relationship using multicycling mode,
and the relationship was deleted but the background copy process continued and is still migrating data
to the secondary volume then the secondary volume also becomes corrupt. In any of these cases, this
recovervdisk fails without -force being specified.

Note:
v The -force parameter must be used if rmvdisk is specified and rejected if the volume is a change
volume for a relationship.
v If the volume is a change volume for a relationship, specifying rmvdisk with -force removes the
change volume from the relationship.

An invocation example
rmvdisk -force vdisk5

The resulting output

No feedback

496 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 rmvdiskcopy
The rmvdiskcopy command removes a VDisk copy from a VDisk.

Syntax


rmvdiskcopy -copy copy_id vdisk_name

-force vdisk_id

Parameters
-copy copy_id
(Required) Specifies the ID of the copy to delete.
-force
(Optional) Forces the deletion of the last synchronized copy of a VDisk, which deletes the entire
VDisk. The parameter also forces the deletion of a nonmirrored VDisk, a copy that is migrating to
image mode, or an image-mode copy that has virtual medium errors.
vdisk_name | vdisk_id
(Required) Specifies the virtual disk to delete the copy from. You must specify this parameter last on
the command line.

Description

The rmvdiskcopy command deletes the specified copy from the specified VDisk. The command fails if all
other copies of the VDisk are not synchronized; in this case, you must specify the -force parameter, delete
the VDisk, or wait until the copies are synchronized.

An invocation example
rmvdiskcopy -copy 1 vdisk8

The resulting output

No feedback

1 rmvdiskaccess
e The rmvdiskaccess command deletes one or more I/O groups from the set of I/O groups in which a
e volume can be made accessible to hosts.

1 Syntax

1

rmvdiskaccess -iogrp iogrp_id_list vdisk_id


iogrp_name_list vdisk_name
1

1 Parameters
1 -iogrp iogrp_id_list | iogrp_name_list
1 (Required) Specifies a list of I/O groups to remove from the I/O group access set of the volume.
1 vdisk_id | vdisk_name
e (Required) Specifies the volume from which to remove access I/O groups.

Chapter 29. Virtual disk commands 497

1 Description

1 The rmvdiskaccess command removes I/O groups from the volume access set. However, it cannot
1 remove all I/O groups from the access set; a volume must have at least one I/O group in an access set.
1 When an I/O group is removed from the access set, all host mappings created through that I/O group
1 (for the volume) are deleted. Consequently, you cannot access the volume through any related I/O group
1 nodes.

1 Remember: If an I/O group in the list is not in the access set, no error is generated, but no action is
1 taken for that I/O group.

1 This example removes I/O groups 2 and 3 from the volume access set for volume ID 3:

1 An invocation example
1 rmvdiskaccess -iogrp 2:3 3

1 The resulting output

1 No feedback
1
rmvdiskhostmap
e The rmvdiskhostmap command deletes an existing host mapping the volume is no longer accessible for
input/output (I/O) transactions on the given host.

Syntax


rmvdiskhostmap -host host_id vdisk_id

host_name vdisk_name

Parameters
-host host_id | host_name
e (Required) Specifies the host that you want to remove from the map with the volume, either by ID or
by name.
vdisk_id | vdisk_name
e (Required) Specifies the name of the volume that you want to remove from the host mapping, either
by ID or by name.

Description

e This command deletes an existing mapping between the specified volume and the host. This effectively
e stops the volume from being available for I/O transactions on the given host.

This command also deletes a Small Computer System Interface (SCSI) or persistent reservation that a host
e has on a volume. Once the reservation is removed, a new host is allowed to access the volume in the
future because the original host no longer has access.

1 Note: The rmvdiskhostmap deletes the host mapping for all I/O groups in the access I/O group set of
1 the volume.

e Use caution when you process this command because to the host, it seems as if the volume has been
deleted or is offline.

An invocation example

498 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 rmvdiskhostmap -host host1 vdisk8

The resulting output

No feedback

shrinkvdisksize
The shrinkvdisksize command reduces the size of a VDisk (volume) by the specified capacity.

Syntax


shrinkvdisksize

-size size_change -copy id -unit b
-rsize size_change kb
mb
gb
tb
pb

vdisk_name

vdisk_id

Parameters
-size size_change
(Optional) Specifies the size reduction (change in size) for the designated virtual disk. The -size
parameter cannot be used with the -rsize parameter. You must specify either -size or -rsize.

Important: This parameter does reduce the size of a volume (the specified virtual size capacity).

3 This does not apply to volumes with compressed copies.

-rsize size_change
(Optional) Reduces the real size of a space-efficient volume by the specified amount. This indicates
the change in size as a result of the reduction. Specify the size_change value using an integer. Specify
the units for a size_change integer using the -unit parameter; the default is MB. You must specify
either -rsize or -size.
-copy id
(Optional) Specifies the copy to change the real capacity for. You must also specify the -rsize
parameter. If the -copy parameter is not specified, all copies of the volume are reduced. This
parameter is required if the volume is mirrored and only one copy is space-efficient.
-unit b | kb | mb | gb | tb | pb
(Optional) Specifies the data units to be used in conjunction with the value that is specified by the
-size parameter.
vdisk_name | vdisk_id
(Required) Specifies the virtual disk that you want to modify, either by ID or by name.

Description

The shrinkvdisksize command reduces the capacity that is allocated to the particular virtual disk by the
amount that you specify. You cannot shrink the real size of a space-efficient volume below its used size.
All capacities, including changes, must be in multiples of 512 bytes. An entire extent is reserved even if it
is only partially used. The default capacity units are MB.

2 Remember: You cannot shrink the virtual size of VDisks (volumes) that have compressed copies.

Chapter 29. Virtual disk commands 499

The command can be used to shrink the physical capacity that is allocated to a particular volume by the
specified amount. The command can also be used to shrink the virtual capacity of a space-efficient
volume without altering the physical capacity assigned to the volume. To change the capacity of a
non-space-efficient disk, use the -size parameter. To change the real capacity of a space-efficient disk, use
the -rsize parameter. To change the virtual capacity of a space-efficient disk, use the -size parameter.

Note: The volume is a change volume for a relationship.

Volumes can be reduced in size, if required.

When the virtual size of a space-efficient volume is changed, the warning threshold is automatically
scaled to match. The new threshold is stored as a percentage.

To run the shrinkvdisksize command on a mirrored volume, all copies of the volume must be
synchronized.

Attention: If the volume contains data that is being used, do not shrink the volume without backing up
the data first.

The clustered system (system) arbitrarily reduces the capacity of the volume by removing a partial, one
or more extents from those allocated to the volume. You cannot control which extents are removed and so
you cannot assume that it is unused space that is removed.

Attention:
1. If the virtual disk contains data, do not shrink the disk.
2. This command can shrink FlashCopy target virtual disks to the same capacity as the source.
3. Before you shrink a volume, validate that the volume is not mapped to any host objects. If the
volume is mapped, data is displayed. You can determine the exact capacity of the source or master
volume by issuing the lsvdisk -bytes vdiskname command. Shrink the volume by the required
amount by issuing the shrinkvdisksize -size size_change -unit b | kb | mb | gb | tb | pb
vdisk_name | vdisk_id command.

An invocation example

To decrease the capacity of vdisk1 by

2

KB, enter:
shrinkvdisksize -size 2048 -unit b vdisk1

The resulting output

No feedback

An invocation example

To decrease the capacity of vdisk2 by 100 MB, enter:

shrinkvdisksize -size 100 -unit mb vdisk2

The resulting output

No feedback

An invocation example

500 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 To decrease the real capacity of space-efficient vdisk3 by 100 MB without changing its virtual capacity,
enter:
shrinkvdisksize -rsize 100 -unit mb vdisk3

The resulting output

No feedback

An invocation example

To decrease the real capacity of space-efficient VDisk copy ID 1 of mirrored vdisk3 by 100 MB, enter:
shrinkvdisksize -rsize 100 -unit mb -copy 1 vdisk4

The resulting output

No feedback

An invocation example

To decrease the virtual capacity of space-efficient vdisk5 by 1 GB without changing its real capacity, enter:
shrinkvdisksize -size 1 -unit gb vdisk5

The resulting output

No feedback

splitvdiskcopy
The splitvdiskcopy command creates a separate VDisk (volume) from a synchronized copy of a mirrored
e volume.

Syntax


splitvdiskcopy -copy id

-iogrp io_group_id | io_group_name

1


-accessiogrp iogrp_id_list -node node_id | node_name -name new_name
iogrp_name_list

vdisk_name

-cache readwrite | none -udid udid -force vdisk_id

Parameters
-copy id
(Required) Specifies the ID of the copy to split.
-iogrp io_group_id | io_group_name
e (Optional) Specifies the I/O group to add the new volume to. The default is the I/O group of the
e specified volume.
2 -accessiogrp iogroup_id_list | iogroup_name_list
2 (Optional) Specifies which I/O groups provide access to the volume. If the -accessiogrp parameter is
2 used, the specified I/O groups provide access even if that set includes either the caching I/O group
2 of the original volume or the caching I/O group of the new volume. If the flag is not specified and
2 the original volume has only its caching I/O group in the set of I/O groups that provide access to
2 the original volume, the new volume is assigned its caching I/O group as the only I/O group that

Chapter 29. Virtual disk commands 501

2 provides access (which might not be the same as caching I/O group of the original volume).
2 Otherwise, the new volume provides access using the same set of I/O groups used with the original
2 mirrored volume.

2 Note: The I/O groups specified are not required to include the caching I/O group.
-node node_id | node_name
e (Optional) Specifies the preferred node ID or the name for I/O operations to this volume. You can
use the -node parameter to specify the preferred access node.
-name new_name
e (Optional) Assigns a name to the new volume.
-cache readwrite | none
e (Optional) Specifies the caching options for the new volume. Enter readwrite or none; the default is
readwrite.
-udid udid
e (Optional) Specifies the udid for the new volume. The udid is a required identifier for OpenVMS
hosts; no other hosts use this parameter. Supported values are a decimal number 0 - 32 767, or a
hexadecimal number 0 - 0x7FFF. A hexadecimal number must be preceded by 0x; for example,
0x1234. The default udid value is 0.
-force
(Optional) Allows the split to proceed even when the specified copy is not synchronized, or even
e when the cache flush is likely to fail. The newly created volume might not be consistent.

Description

e The splitvdiskcopy command creates a new volume in the specified I/O Group from a copy of the
e specified volume. If the copy that you are splitting is not synchronized, you must use the -force
parameter. The command fails if you are attempting to remove the only synchronized copy. To avoid this,
e wait for the copy to synchronize or split the unsynchronized copy from the volume by using the -force
e parameter. You can run the command when either volume copy is offline.

An invocation example
splitvdiskcopy -copy 1 vdisk8

The resulting output

Virtual Disk, id [1], successfully created.

2 An invocation example for creating a volume with I/O groups 2 and 3 in it's I/O group access set
2 splitvdiskcopy -copy 1 -iogrp 2 -node 7 -accessiogrp 2:3 DB_Disk

2 The resulting output

2 Virtual Disk, copy [1], successfully created.

502 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Chapter 30. Command-line interface messages
a value for a parameter. The string is not a supported
CMMVC5000I No message was found for major rc
value for the parameter. One requirement is that the
MAJOR_RC , minor rc MINOR_RC , for
value is an even multiple of 16, and the specified string
action/view id ACTION_VIEW_ID .
does not meet that requirement.
Explanation: A message is missing.
User response: Specify a value that is supported by
User response: Contact the support center. the parameter, and resubmit the command.

CMMVC5700E The parameter list is not valid. CMMVC5705E A required parameter is missing.
Explanation: You have entered a list of parameters Explanation: The command that you have submitted
that is not supported for the command. has at least one required parameter that you have not
entered.
User response: Specify a parameter list that is
supported for the command, and resubmit the User response: Specify all of the required parameters,
command. and resubmit the command.

CMMVC5701E No object ID was specified. CMMVC5706E An invalid argument has been

entered for the PARAMETER parameter.
Explanation: The command that you have submitted
requires that you specify an object identifier name or Explanation: You have entered a value for the
ID number, and you did not specify an object identifier. specified parameter and the value is not supported for
the parameter. The parameter supports a specific set of
User response: Specify an object ID, and resubmit the
values.
command.
User response: Specify a value that is supported by
the parameter, and resubmit the command.
CMMVC5702E VALUE is below the minimum level.
Explanation: You entered the specified string as a
CMMVC5707E Required parameters are missing.
value for a parameter. The parameter requires a
minimum value, and the specified string is less than Explanation: The command that you have submitted
the required minimum value. has more than one required parameter that you have
not entered.
User response: Specify a value that is supported by
the parameter, and resubmit the command. User response: Specify all of the required parameters,
and resubmit the command.
CMMVC5703E The value or list starting with VALUE
is above the maximum permitted for CMMVC5708E The PARAMETER parameter is
that value or has exceeded the number missing its associated arguments.
of items allowed in a list.
Explanation: You have entered the specified parameter
Explanation: You have entered the specified string as without an associated value. This parameter, like most
a value for a parameter. The string is either a parameters, requires an associated value.
standalone value or the first value in a list of values. If
User response: Specify the associated value, and
the string is a standalone value, the value is greater
resubmit the command.
than the supported maximum value for the parameter.
If the string is the first value in a list of values, the list
contains more than the supported maximum number of CMMVC5709E VALUE is not a supported parameter.
entries for the parameter.
Explanation: The specified string is not a supported
User response: Specify a value or list of values that is parameter for the command that you have entered.
supported by the parameter, and resubmit the
command. User response: Specify the correct parameter, and
resubmit the command.

CMMVC5704E VALUE is not divisible by the

permitted step value. CMMVC5711E VALUE is not valid data.

Explanation: You have entered the specified string as Explanation: You have entered the specified string as

© Copyright IBM Corp. 2003, 2012 503

CMMVC5712E • CMMVC5723E

a value for a parameter. The string is not a supported

CMMVC5717E No match was found for the specified
value for the parameter.
unit.
User response: Specify a value that is supported by
Explanation: Certain parameters allow a user to
the parameter, and resubmit the command.
specify a data unit such as mb or kb. You have entered
a data unit for a parameter that supports data units,
CMMVC5712E Required data is missing. but the data unit that you have entered is not a
supported data unit for the parameter.
Explanation: You have entered an incomplete
command. User response: Specify the correct data unit, and
resubmit the command.
User response: Specify command completely, and
resubmit the command.
CMMVC5718E An unexpected return code was
received.
CMMVC5713E Some parameters are mutually
exclusive. Explanation: The command has completed, but the
acknowledgement of the command completion contains
Explanation: Certain commands have two or more a return code that is not defined.
parameters that are mutually exclusive. You have
submitted a command using at least two mutually User response: Determine whether or not the
exclusive parameters. command has succeeded. If the command has not
succeeded, resubmit the command. If the problem
User response: Specify a supported combination of persists, contact IBM technical support for assistance.
parameters, and resubmit the command.

CMMVC5719E A value of VALUE requires the

CMMVC5714E The parameter list is empty. parameter PARAMETER to be specified.
Explanation: Certain parameters require one or more Explanation: Certain commands have required
values in a colon separated parameter list. You have combinations of parameters based on either the entry of
specified at least one parameter without the required a parameter or the value for a parameter. When you
parameter list. enter the specified value, you must enter the specified
User response: Specify at least one value for all parameter.
parameters that require a value, and resubmit the User response: Specify the required parameter, and
command. resubmit the command.

CMMVC5715E The parameter list does not exist. CMMVC5721E VALUE is not a valid time stamp
Explanation: Certain parameters require one or more format. The valid time stamp format is
values in a colon separated parameter list. You have YYMMDDHHMMSS.
specified at least one parameter without the required Explanation: The specified value is not a valid time
parameter list. stamp format. The valid format is YYMMDDHHMMSS.
User response: Specify at least one value for all User response: Use the correct time stamp format, and
parameters that require a value, and resubmit the resubmit the command.
command.

CMMVC5722E VALUE contains a month value that

CMMVC5716E Non-numeric data was entered for is not valid. The valid time stamp
the numeric field FIELD . Enter a format is YYMMDDHHMMSS.
numeric value.
Explanation: The month value (MM) that you have
Explanation: You have entered the specified string as specified is not valid.
a value for a parameter that supports only numeric
values. User response: Specify a valid month value, and
resubmit the command.
User response: Specify a numeric value in the
numeric field, and resubmit the command.
CMMVC5723E VALUE contains a day value that is
not valid. The valid time stamp format
is YYMMDDHHMMSS.
Explanation: The day value (DD) that you have
specified is not valid.

504 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5724E • CMMVC5735E

User response: Specify a valid day value, and

CMMVC5730E VALUE is only valid when VALUE
resubmit the command.
has a value of VALUE .
Explanation: The specified command and parameter
CMMVC5724E VALUE contains an hour value that is
combination that you have entered requires the
not valid. The valid time stamp format
specified parameter value.
is YYMMDDHHMMSS.
User response: Ensure that you specify the correct
Explanation: The hour value (HH) that you have
parameter value for the command and parameter
specified is not valid.
combination that you enter, and resubmit the
User response: Specify a valid hour value, and command.
resubmit the command.
CMMVC5731E VALUE can only be entered when
CMMVC5725E VALUE contains a minutes value that VALUE has been entered.
is not valid. The valid time stamp
Explanation: Certain commands have required
format is YYMMDDHHMMSS.
combinations of parameters based either on the
Explanation: The minutes value (MM) that you have inclusion of a specified parameter, or on the value
specified is not valid. entered for a specified parameter. When you include
the first specified string in the command, you must
User response: Specify a valid minutes value, and enter the second specified string as a parameter.
resubmit the command.
User response: Ensure that you enter a supported
combination or parameters and values, and resubmit
CMMVC5726E VALUE contains a seconds value that the command.
is not valid. The valid time stamp
format is YYMMDDHHMMSS.
CMMVC5732E The command cannot be initiated
Explanation: The seconds value (SS) that you have because it was not run on the
specified is not valid. configuration node.
User response: Specify a valid seconds value, and Explanation: The command that you have specified
resubmit the command. must be run on the configuration node.
User response: Log off of the node service IP address,
CMMVC5727E VALUE is not a valid filter. log on to the management IP address, and run the
Explanation: You can filter the output of some views command on the configuration node.
by using the -filtervalue parameter. The specified string
that you have entered is not a supported value for the CMMVC5733E Enter at least one parameter.
-filtervalue parameter in this view.
Explanation: You must specify at least one parameter
User response: Ensure that you use a supported value for the command that you have submitted.
for the -filtervalue parameter, and resubmit the
command. User response: Specify at least one parameter, and
resubmit the command.
CMMVC5728E VALUE should be in the format
minute:hour:day:month:weekday. CMMVC5734E A combination of values was entered
that is not valid.
Explanation: The specified value should be in the
format minute:hour:day:month:weekday. Explanation: You have specified a combination of
values that is not correct.
User response: Follow the correct format, and
resubmit the command. User response: Specify a supported combination of
values, and resubmit the command.
CMMVC5729E One or more components in the list
is not valid. CMMVC5735E The name entered is not valid. Enter
an alphanumeric string that does not
Explanation: Certain parameters support one or more start with a number.
items of data in a colon separated list. At least one of
the items in the list that you have entered is not Explanation: The first character of an object name
correct. cannot be numeric.

User response: Ensure that you enter supported User response: Specify an alphanumeric string that
values in the list, and resubmit the command.

Chapter 30. Command-line interface messages 505

CMMVC5737E • CMMVC5748E

does not start with a numeric, and resubmit the User response: Ensure that you enter data values that
command. are supported for the parameter that you enter, and
resubmit the command.
CMMVC5737E The parameter PARAMETER has been
entered multiple times. Enter the CMMVC5743E A specified parameter does not
parameter only one time. comply with the step value.
Explanation: The specified parameter was entered Explanation: A parameter was specified that does not
more than once. comply with the step value.
User response: Delete all duplicate parameters, and User response: Specify the correct parameter, and
resubmit the command. resubmit the command.

CMMVC5738E The argument ARGUMENT contains CMMVC5744E Too many objects were specified in
too many characters. the command.
Explanation: The field length of the specified Explanation: There were too many objects specified in
argument is longer than the maximum supported field the command.
length for the argument.
User response: Specify the correct object, and resubmit
User response: Specify the correct argument, and the command.
resubmit the command.
CMMVC5745E Too few objects were specified in the
CMMVC5739E The argument ARGUMENT does not request.
contain enough characters.
Explanation: There were not enough objects specified
Explanation: The field length of the specified in the command.
argument is less than the minimum supported field
User response: Specify the correct object, and resubmit
length for the argument.
the command.
User response: Specify the correct argument, and
resubmit the command.
CMMVC5746E The requested operation cannot be
applied to the object specified.
CMMVC5740E The filter flag VALUE is not valid.
Explanation: The requested operation is not valid for
Explanation: You can filter the output of some views this object.
by using the -filtervalue parameter. The specified string
User response: Specify a valid operation, and
that you have entered is not a supported value for the
resubmit the command.
-filtervalue parameter in this view.
User response: Ensure that you use a supported value
CMMVC5747E The action requested is invalid -
for the -filtervalue parameter, and resubmit the
internal error.
command.
Explanation: The operation that was requested is not
valid.
CMMVC5741E The filter value VALUE is not valid.
User response: Specify the correct operation, and
Explanation: You can filter the output of some views
resubmit the command.
by using the -filtervalue parameter. Each filter has an
associated value. The syntax is -filtervalue filter=value.
The specified string that you have entered is not a CMMVC5748E The action requested is invalid -
supported value for the -filtervalue filter that you internal error.
specified in this view.
Explanation: The operation that was requested is not
User response: Ensure that you use a supported value valid.
for the -filtervalue filter that you specify, and resubmit
the command. User response: Specify the correct operation, and
resubmit the command.

CMMVC5742E A specified parameter is out of its

valid range.
Explanation: You have entered data that is not in the
range of values that is supported for the parameter that
you have entered.

506 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5749E • CMMVC5763E

CMMVC5749E The dump filename specified already CMMVC5756E Cannot perform the request as the
exists. object id is already mapped to another
object or is the subject of an FC or RC
Explanation: The dump file name that was specified
relationship.
already exists.
Explanation: The operation failed because the
User response: Specify a different dump file name,
specified object is already mapped.
and resubmit the command.
User response: Specify a different object, and resubmit
the command.
CMMVC5750E The dump file could not be created -
the file system is probably full.
CMMVC5757E Self Defining Structure (SDS)
Explanation: The dump file was not created. The file
defaults not found - internal error.
system might be full.
Explanation: The defaults for the self describing
User response: Not applicable.
structure were not found.
User response: Not applicable.
CMMVC5751E The dump file could not be written
to.
CMMVC5758E Object name already exists.
Explanation: The dump file could not be written to
disk. Explanation: The object name already exists.
User response: Not applicable. User response: Specify a unique object name, and
resubmit the command.
CMMVC5752E Request failed. The object contains
child objects, these must be deleted CMMVC5759E An internal error has occurred -
first. memory could not be allocated.
Explanation: The operation failed because the Explanation: The memory cannot be allocated.
specified object contains child objects.
User response: Not applicable.
User response: Delete the child objects, and resubmit
the command.
CMMVC5760E Failed to add the node to the cluster
member list.
CMMVC5753E The specified object does not exist or
Explanation: The node could not be added to the
is not a suitable candidate.
cluster.
Explanation: The specified object does not exist or is
User response: Not applicable.
not a suitable candidate.
User response: Specify the correct object, and resubmit
CMMVC5761E Failed to delete the node from the
the command.
cluster member list.
Explanation: The node could not be deleted from the
CMMVC5754E The specified object does not exist, or
cluster.
the name supplied does not meet the
naming rules. User response: Not applicable.
Explanation: The specified object does not exist, or the
name of the object does not meet the naming CMMVC5762E The request did not complete before
requirements. the timeout period expired.
User response: Specify the correct object name, and Explanation: The operation failed because the timeout
resubmit the command. period expired.
User response: Resubmit the command.
CMMVC5755E Cannot create as the sizes of the
specified objects do not match.
CMMVC5763E The node failed to go online.
Explanation: The sizes of the specified objects do not
match. Explanation: The node failed to go online.

User response: Not applicable. User response: Not applicable.

Chapter 30. Command-line interface messages 507

CMMVC5764E • CMMVC5780E

complete, and resubmit the command.

CMMVC5764E The mode change request is invalid -
internal error
CMMVC5773E The object selected is in the wrong
Explanation: The specified mode change is not valid.
mode to perform the requested
User response: Specify a different mode, and resubmit operation.
the command.
Explanation: The operation failed because the selected
object is in the wrong mode.
CMMVC5765E The object specified is no longer a
User response: Specify the correct mode, and resubmit
candidate - a change occurred during the
the command.
request.
Explanation: The specified object is no longer a
CMMVC5774E The userid supplied is not valid.
candidate. A change occurred during the request.
Explanation: The userid is not valid.
User response: Specify a different object, and resubmit
the command. User response: Specify a different userid, and
resubmit the command.
CMMVC5767E One or more of the parameters
specified are invalid or a parameter is CMMVC5775E The directory attribute specified is
missing. not valid.
Explanation: One or more of the specified parameters Explanation: The directory attribute is not valid.
is not valid.
User response: Specify a different directory, and
User response: Specify the correct parameter, and resubmit the command.
resubmit the command.

CMMVC5776E The directory listing could not be

CMMVC5769E The requested operation requires all retrieved.
nodes to be online - one or more nodes
are not online. Explanation: The directory listing could not be
retrieved.
Explanation: The operation requires that all nodes be
online. One or more nodes are not online. User response: Specify a different directory listing,
and resubmit the command.
User response: Check that each node is online, and
resubmit the command.
CMMVC5777E The node could not be added to the
IO Group, because the other node in the
CMMVC5770E The SSH key file supplied is invalid. IO Group is in the same power domain.
Explanation: The file for the SSH key is not valid. Explanation: The node was not added to the I/O
group because the other node in the I/O Group is in
User response: Specify a different file, and resubmit
the same power domain.
the command.
User response: Specify a different node from another
I/O group, and resubmit the command.
CMMVC5771E The operation requested could not
complete, usually due to child objects
existing. To force the operation, specify CMMVC5778E Cannot create another cluster, a
the force flag. cluster already exists.
Explanation: The operation failed, probably, because Explanation: The cluster was not created because one
the object contains child objects. already exists.
User response: Specify the -force flag to complete the User response: Not applicable.
operation, and resubmit the command.

CMMVC5780E The action could not be completed

CMMVC5772E The operation requested could not be using the Remote Cluster name. Use the
performed because software upgrade is Remote Cluster Unique ID instead.
in progress.
Explanation: The unique ID of the remote cluster is
Explanation: The operation failed because a software required for this command.
upgrade is in progress.
User response: Specify the unique ID of the remote
User response: Wait for the software upgrade to cluster, and resubmit the command.

508 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5781E • CMMVC5794E

CMMVC5781E The cluster ID specified is invalid. CMMVC5789E The cluster was not modified because
the IP address, subnet mask, service
Explanation: The cluster ID is not valid.
address, SNMP address, or gateway
User response: Specify a different cluster ID, and address is not valid.
resubmit the command.
Explanation: The cluster was not modified because the
IP address, subnet mask, service address, SNMP
CMMVC5782E The object specified is offline. address, or gateway address is not valid.

Explanation: The object is offline. User response: Specify all correct attributes, and
resubmit the command.
User response: Specify an object that is online, and
resubmit the command.
CMMVC5790E The node was not added to the
cluster because the maximum number of
CMMVC5783E The information is not available to nodes has been reached.
complete this command.
Explanation: The node was not added to the cluster
Explanation: This error is only returned when the because the maximum number of nodes has been
node is in the service state. reached.
User response: None. User response: Not applicable.

CMMVC5784E The cluster name specified is not CMMVC5791E The action failed because an object
unique, specify the cluster using the that was specified in the command does
cluster ID. not exist.
Explanation: The cluster name is not unique. Explanation: An entity that was specified in the
User response: Specify the cluster using the cluster ID, command does not exist, therefore the action failed.
and resubmit the command. User response: Specify the correct entity, and resubmit
the command.
CMMVC5785E The filename specified contains an
illegal character. CMMVC5792E The action failed because the I/O
Explanation: The filename contains an illegal group is used for recovery.
character. Explanation: The action failed because the I/O group
User response: Specify a valid filename, and resubmit is used for recovery.
the command. User response: Not applicable.

CMMVC5786E The action failed because the cluster CMMVC5793E The node was not added to the
is not in a stable state. cluster because the I/O group already
Explanation: The action failed because the cluster is contains a pair of nodes.
not in a stable state. Explanation: The node was not added to the cluster
User response: Not applicable. because the I/O group already contains a pair of
nodes.

CMMVC5787E The cluster was not created because a User response: Not applicable.
cluster already exists.
Explanation: The cluster was not created because a CMMVC5794E The action failed because the node is
cluster already exists. not a member of the cluster.

User response: Not applicable. Explanation: The node is not a member of the cluster,
therefore the action failed.

CMMVC5788E The service IP address is not valid. User response: Specify a node that is contained in the
cluster, and resubmit the command.
Explanation: The service IP address is not valid.
User response: Specify the correct service IP address,
and resubmit the command.

Chapter 30. Command-line interface messages 509

CMMVC5795E • CMMVC5805E

CMMVC5795E The node was not deleted because a CMMVC5801E The upgrade of the cluster software
software upgrade is in progress. could not proceed because every node in
the cluster must be online. Either delete
Explanation: The node was not deleted because a
the node that is offline or bring the
software upgrade is in progress.
node online and resubmit the command
User response: Wait for the software upgrade to
Explanation: The upgrade of the cluster software
complete, and resubmit the command.
could not proceed because every node in the cluster
must be online.
CMMVC5796E The action failed because the I/O
User response: Either delete the node that is offline or
group that the node belongs to is
bring the node online, and resubmit the command.
unstable.
Explanation: A previous configuration command
CMMVC5802E The upgrade of the cluster software
might not yet have completed.
could not proceed because there is an
User response: Wait for the previous command to I/O group in the cluster that contains
complete, and resubmit the command. only one node. The software upgrade
requires that each node in an I/O group
be shut down and restarted. If there is
CMMVC5797E The node was not deleted because only one node in an I/O group, I/O
this is the last node in the I/O group operations could be lost if I/O
and there are virtual disks (VDisks) operations are not stopped before
associated with the I/O group. beginning the software upgrade.
Explanation: The specified node is the last node in the Explanation: The upgrade of the cluster software
I/O group and there are volumes associated with the could not proceed because there is an I/O group in the
I/O group, therefore the node could not be deleted. cluster that contains only one node. The software
User response: Not applicable. upgrade requires that each node in an I/O group be
shut down and restarted. If there is only one node in
an I/O group, I/O operations could be lost if I/O
CMMVC5798E The action failed because the node is operations are not stopped before beginning the
offline. software upgrade.
Explanation: The action failed because the node is User response: Either upgrade the cluster using the
offline. -force option or specify a different node, and resubmit
User response: Specify a node that is online, and the command.
resubmit the command.
CMMVC5803E The entry in the error log was not
CMMVC5799E The shut down was not successful marked because the error is already
because there is only one online node in fixed or unfixed, or the sequence
the I/O group. number could not be found.

Explanation: There is only one online node is the I/O Explanation: The entry in the event log was not
group, therefore the shut down operation was not marked because the sequence number was not found.
successful. User response: Not applicable.
User response: Not applicable.
CMMVC5804E The action failed because an object
CMMVC5800E The action failed because an entity that was specified in the command does
that was specified in the command does not exist.
not exist. Explanation: The entity that was specified in the
Explanation: The entity that was specified in the command does not exist, therefore the action failed.
command does not exist, therefore the action failed. User response: Specify a different entity, and resubmit
User response: Specify a different entity, and resubmit the command.
the command.
CMMVC5805E The progress information was not
returned because the FlashCopy
statistics are not ready yet.
Explanation: The progress information was not

510 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5806E • CMMVC5817E

returned because the FlashCopy statistics are not ready

CMMVC5812E The action failed because the
yet.
managed disk (MDisk) is not in
User response: Not applicable. managed mode.
Explanation: The action is only permitted on MDisks
CMMVC5806E The action failed because an object that are currently in the managed mode.
that was specified in the command does
User response: Either add the MDisk to a group, or
not exist.
specify a different MDisk.
Explanation: The entity that was specified in the
command does not exist, therefore the action failed.
CMMVC5813E The quorum index number for the
User response: Specify a different entity, and resubmit object was not set because the object
the command. has a sector size that is not valid.
Explanation: The sector size of the specified object
CMMVC5807E The action failed because the will not allow the quorum index number for the object
managed disk (MDisk) cannot be to be set.
changed to the specified mode.
User response: Change the sector size of the specified
Explanation: The action failed because the managed object, or specify a different object, and resubmit the
disk (MDisk) cannot be changed to the specified mode. command.

User response: Not applicable.

CMMVC5814E The quorum index number for the
managed disk (MDisk) was not set
CMMVC5808E The action failed because the because quorum is not allowed on one
managed disk (MDisk) does not exist. or more associated controllers.
Explanation: The action failed because the managed Explanation: The quorum index number for the
disk (MDisk) does not exist. managed disk (MDisk) was not set because quorum is
User response: Specify a different MDisk, and not allowed on one or more associated controllers.
resubmit the command. User response: Specify an MDisk that has quorum
enabled on all of its associated controllers, and
CMMVC5809E The tracing of I/O operations was not resubmit the command.
started because it is already in progress.
Explanation: The tracing of I/O operations was not CMMVC5815E The managed disk group was not
started because it is already in progress. created because an entity that was
specified in the command does not
User response: Not applicable. exist.
Explanation: The storage pool was not created
CMMVC5810E The action failed because the because an entity that was specified in the command
specified resource was unavailable. does not exist.
Explanation: The resource specified in the action was User response: Specify a different entity, and resubmit
not available for use. the command.
User response: Fix any errors associated with the
specified resource, or reissue the command using an CMMVC5816E The action failed because an entity
alternative resource. that was specified in the command does
not exist.
CMMVC5811E The quorum index number for the Explanation: The action failed because an entity that
object was not set because the quorum was specified in the command does not exist.
disk does not exist.
User response: Specify a different entity, and resubmit
Explanation: An existing quorum disk must be the command.
specified before the quorum index number of the object
can be set.
CMMVC5817E The specified managed disk group
User response: Specify an existing quorum disk, and was invalid.
resubmit the command.
Explanation: The storage pool was not renamed
because the name was not valid.

Chapter 30. Command-line interface messages 511

CMMVC5818E • CMMVC5828E

User response: Specify a different storage pool name, deleted from the storage pool because the MDisk is
and resubmit the command. part of another storage pool.
User response: Not applicable.
CMMVC5818E The managed disk group was not
deleted because there is at least one
CMMVC5824E The managed disk (MDisk) was not
MDisk in the group.
deleted from the MDisk group because
Explanation: The storage pool was not deleted it does not belong to the MDisk group.
because there is at least one MDisk in the group.
Explanation: The managed disk (MDisk) was not
User response: Not applicable. deleted from the storage pool because it does not
belong to the storage pool.
CMMVC5819E The managed disk (MDisk) was not User response: Not applicable.
added to the MDisk group because the
MDisk is part of another MDisk group.
CMMVC5825E The managed disk (MDisk) was not
Explanation: The managed disk (MDisk) was not deleted from the MDisk group because
added to the storage pool because the MDisk is part of a virtual disk (VDisk) is allocated from
another storage pool. one or more of the specified MDisks. A
forced deletion is required.
User response: Not applicable.
Explanation: The managed disk (MDisk) was not
deleted from the storage pool because a volume is
CMMVC5820E The managed disk (MDisk) was not
allocated from one or more of the specified MDisks.
added to the MDisk group because an
entity that was specified in the User response: Specify the -force option, and resubmit
command does not exist. the command.
Explanation: The managed disk (MDisk) was not
added to the storage pool because an entity that was CMMVC5826E The virtual disk (VDisk) was not
specified in the command does not exist. created because an entity that was
specified in the command does not
User response: Specify a different entity, and resubmit
exist.
the command.
Explanation: The volume was not created because an
entity that was specified in the command does not
CMMVC5821E The managed disk (MDisk) was not
exist.
added to the MDisk group because not
enough MDisks were included in the User response: Specify a different entity, and resubmit
list. the command.
Explanation: The managed disk (MDisk) was not
added to the storage pool because not enough MDisks CMMVC5827E The command failed as a result of
were included in the list. either an inconsistency between two or
more of the entered parameters, or an
User response: Include more MDisks in the list, and
inconsistency between a parameter and
resubmit the command.
the requested action.
Explanation: The command failed as a result of an
CMMVC5822E The managed disk (MDisk) was not
inconsistency between two or more of the entered
added to the MDisk group because too
parameters.
many MDisks were included in the list.
User response: Specify one parameter, and resubmit
Explanation: The managed disk (MDisk) was not
the command.
added to the storage pool because too many MDisks
were included in the list.
CMMVC5828E The virtual disk (VDisk) was not
User response: Delete the extra MDisks in the list, and
created because the I/O group contains
resubmit the command.
no nodes.
Explanation: The volume was not created because the
CMMVC5823E The managed disk (MDisk) was not
I/O group contains no nodes.
deleted from the MDisk group because
the MDisk is part of another MDisk User response: Not applicable.
group.
Explanation: The managed disk (MDisk) was not

512 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5829E • CMMVC5839E

Explanation: The I/O group for the volume was not

CMMVC5829E The image-mode or sequential-mode
modified because the group is a recovery I/O group.
virtual disk (VDisk) was not created
because more than one managed disk User response: Specify the -force option, and resubmit
(MDisk) is specified. the command.
Explanation: The image-mode or sequential-mode
volume was not created because more than one MDisk CMMVC5835E The virtual disk (VDisk) was not
is specified. expanded because an entity that was
specified in the command does not
User response: Specify a different MDisk, and
exist.
resubmit the command.
Explanation: The volume was not expanded because
an entity that was specified in the command does not
CMMVC5830E The image-mode virtual disk (VDisk)
exist.
was not created because no managed
disk (MDisk) was specified in the User response: Specify a different entity, and resubmit
command. the command.
Explanation: The image-mode volume was not created
because no managed disk (MDisk) was specified in the CMMVC5836E The virtual disk (VDisk) was not
command. shrunk because it is locked.
User response: Specify a MDisk, and resubmit the Explanation: Commands might still be running in the
command. background.
User response: Wait for all commands to complete.
CMMVC5831E The virtual disk (VDisk) was not Use the lsmigrate command to view any migrates
created because the preferred node for running in the background.
I/O operations is not part of the I/O
group.
CMMVC5837E The action failed because the virtual
Explanation: The volume was not created because the disk (VDisk) is part of a FlashCopy
preferred node for I/O operations is not part of the mapping.
I/O group.
Explanation: The action failed because the volume is
User response: Specify a different node, and resubmit part of a FlashCopy mapping.
the command.
User response: Specify a different volume that is not
part of a FlashCopy mapping, and resubmit the
CMMVC5832E The property of the virtual disk command.
(VDisk) was not modified because an
entity that was specified in the
command does not exist. CMMVC5838E The action failed because the virtual
disk (VDisk) is part of a Remote Copy
Explanation: The property of the volume was not mapping.
modified because an entity that was specified in the
command does not exist. Explanation: The action failed because the volume is
part of a Remote Copy mapping.
User response: Specify a different entity, and resubmit
the command. User response: Specify a different volume that is not
part of a Remote Copy mapping, and resubmit the
command.
CMMVC5833E The property of the virtual disk
(VDisk) was not modified because there
are no nodes in the I/O group. CMMVC5839E The virtual disk (VDisk) was not
shrunk because an object that was
Explanation: The property of the volume was not specified in the command does not
modified because there are no nodes in the I/O group. exist.
User response: Not applicable. Explanation: The volume was not shrunk because an
object that was specified in the command does not
exist.
CMMVC5834E The I/O group for the virtual disk
(VDisk) was not modified because the User response: Specify a different object, and resubmit
group is a recovery I/O group. To the command.
modify the I/O group, use the force
option.

Chapter 30. Command-line interface messages 513

CMMVC5840E • CMMVC5851E

CMMVC5840E The virtual disk (VDisk) was not CMMVC5846E The virtual disk (VDisk) was not
deleted because it is mapped to a host migrated because an object that was
or because it is part of a FlashCopy or specified in the command does not
Remote Copy mapping, or is involved exist.
in an image mode migrate.
Explanation: The volume was not migrated because
Explanation: The volume was not deleted because it is an object that was specified in the command does not
mapped to a host or because it is part of a FlashCopy exist.
or Metro Mirror mapping.
User response: Specify a different object, and resubmit
User response: Specify a different volume, and the command.
resubmit the command.
CMMVC5847E The virtual disk (VDisk) was not
CMMVC5841E The virtual disk (VDisk) was not migrated because its associated managed
deleted because it does not exist. disk (MDisk) is already in the MDisk
group.
Explanation: The volume was not deleted because it
does not exist. Explanation: The volume was not migrated because
its associated managed disk (MDisk) is already in the
User response: Specify a different volume, and
storage pool.
resubmit the command.
User response: Not applicable.
CMMVC5842E The action failed because an object
that was specified in the command does CMMVC5848E The action failed because the virtual
not exist. disk (VDisk) does not exist or it is
being deleted.
Explanation: The action failed because an entity that
was specified in the command does not exist. Explanation: The action failed because the volume
does not exist or it is being deleted.
User response: Specify a different entity, and resubmit
the command. User response: Specify a different volume, and
resubmit the command.
CMMVC5843E The VDisk-to-host mapping was not
created because the VDisk does not CMMVC5849E The migration failed because some or
have a capacity greater than zero bytes. all of the extents are already being
migrated.
Explanation: The host map was not created because
the volume does not have a capacity greater than zero Explanation: The migration failed because some or all
bytes. of the extents are already being migrated.
User response: Specify a volume in which its capacity User response: Not applicable.
is greater than zero bytes, and resubmit the command.
CMMVC5850E The extent was not migrated because
CMMVC5844E The VDisk-to-host mapping was not there is a problem with the source
created because the SCSI logical unit extents.
number (LUN) ID is not valid.
Explanation: The extent was not migrated because
Explanation: The host map was not created because there is a problem with the source extents.
the SCSI logical unit number (LUN) ID is not valid.
User response: Not applicable.
User response: Specify the correct SCSI logical unit
number (LUN) ID, and resubmit the command.
CMMVC5851E The extent was not migrated because
there is a problem with the target
CMMVC5845E The extent was not migrated because extents.
an object that was specified in the
Explanation: The extent was not migrated because
command does not exist.
there is a problem with the target extents.
Explanation: The extent was not migrated because an
User response: Not applicable.
object that was specified in the command does not
exist.
User response: Specify a different object, and resubmit
the command.

514 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5852E • CMMVC5861E

CMMVC5852E The migration failed because there CMMVC5857E The action failed because the
are too many migrations in progress. managed disk (MDisk) does not exist or
it is not a member of the managed disk
Explanation: The migration failed because there are
group.
too many migrations in progress.
Explanation: The action failed because the managed
User response: Wait for the migration process to
disk (MDisk) does not exist or it is not a member of the
complete, and resubmit the command.
storage pool.
User response: Specify a different MDisk, and
CMMVC5853E The action failed because there was a
resubmit the command.
problem with the group.
Explanation: An attempt was made to work on a
CMMVC5858E The action failed because the virtual
volume which is using a storage pool with one of the
disk (VDisk) is in the wrong mode, the
following problems:
managed disk (MDisk) is in the wrong
v The target and source storage pools have different mode, or both are in the wrong mode.
extent sizes (group migrate).
Explanation: The action failed because the volume is
v The target and source storage pools are the same
in the wrong mode, the managed disk (MDisk) is in the
(group migrate).
wrong mode, or both are in the wrong mode.
v The target and source storage pools are different
(extents migrate). User response: Check that the volume and MDisk are
in the correct mode, and resubmit the command.
v The target group (group migrate) is not valid.
v The source group (group migrate) is not valid.
CMMVC5859E The migration did not complete
User response: Ensure that none of the above because an error occurred during the
conditions exist before reissuing the command. migration of the last extent on an
image-mode virtual disk (VDisk).
CMMVC5854E The extent information was not Explanation: The migration did not complete because
returned because the extent is not used an error occurred during the migration of the last
or does not exist. extent on an image-mode volume.
Explanation: The extent information was not returned User response: Not applicable.
because the extent is not used or does not exist.
User response: Specify the correct extent, and CMMVC5860E The action failed because there were
resubmit the command. not enough extents in the managed disk
group.
CMMVC5855E The extent information was not Explanation: This error is also returned if a stripe set
returned because the managed disk of MDisks has been specified and one or more of these
(MDisk) is not used by any virtual disk MDisks does not contain enough free extents to
(VDisk). complete the creation of the volume.
Explanation: The extent information was not returned User response: In this case, the storage pool reports
because the managed disk (MDisk) is not used by any that it has enough free capacity to create the volume.
volume. You can check the free capacity on each MDisk by
User response: Specify the correct MDisk, and submitting the command lsfreeextents
resubmit the command. <mdiskname/ID> . Alternatively, do not specify a stripe
set and let the system choose the free extents
automatically.
CMMVC5856E The action failed because the virtual
disk (VDisk) does not belong to the
specified managed disk group. CMMVC5861E The action failed because there were
not enough extents on the managed disk
Explanation: The action failed because the volume (MDisk).
does not belong to the specified storage pool.
Explanation: The action failed because there were not
User response: Specify a different volume, and enough extents on the managed disk (MDisk).
resubmit the command.
User response: Specify another extent, and resubmit
the command.

Chapter 30. Command-line interface messages 515

CMMVC5862E • CMMVC5873E

CMMVC5862E The action failed because the virtual CMMVC5868E The action failed because an entity
disk (VDisk) is being formatted. that was specified in the command does
not exist.
Explanation: The action failed because the volume is
being formatted. Explanation: The action failed because an entity that
was specified in the command does not exist.
User response: Wait for the volume to be successfully
formatted, and resubmit the command. User response: Specify a different entity, and resubmit
the command.
CMMVC5863E The migration failed because there
are not enough free extents on the target CMMVC5869E The host object was not renamed
managed disk (MDisk). because the host ID or name is not
valid.
Explanation: The migration failed because there are
not enough free extents on the target managed disk Explanation: The host object was not renamed because
(MDisk). the host ID or name is not valid.
User response: Specify another free extent, and User response: Specify a different host ID or name,
resubmit the command. and resubmit the command.

CMMVC5864E The extent information was not CMMVC5870E The host object was not deleted
returned because the source extent is not because an entity that was specified in
used. the command does not exist.
Explanation: The extent information was not returned Explanation: The host object was not deleted because
because the source extent is not used. an entity that was specified in the command does not
exist.
User response: Specify a different source extent, and
resubmit the command. User response: Specify the correct entity, and resubmit
the command.
CMMVC5865E The action failed because the extent
is out of range for the managed disk CMMVC5871E The action failed because one or
(MDisk) or virtual disk (VDisk) more of the configured port names is in
specified. a mapping.
Explanation: The extent information was not returned Explanation: The action failed because one or more of
because the extent is out of range for the managed disk the configured port names is in a mapping.
(MDisk) or volume.
User response: Specify a port name that is not in a
User response: Specify a different extent which is in mapping, and resubmit the command.
range for the MDisk or volume and resubmit the
command.
CMMVC5872E The port (WWPN) was not added to
the host object because an object that
CMMVC5866E The action failed because the extent was specified in the command does not
contains internal data. exist.
Explanation: The extent was not migrated because the Explanation: The port (WWPN) was not added to the
extent contains internal data. host object because an object that was specified in the
command does not exist.
User response: Not applicable.
User response: Specify the correct object, and resubmit
the command.
CMMVC5867E The action failed because the
worldwide port name is already
assigned or is not valid. CMMVC5873E No matching WWPN.
Explanation: The action failed because the worldwide Explanation: The action failed because there is no
port name is already assigned or is not valid. matching worldwide port name.
User response: Specify a different worldwide port User response: Not applicable.
name, and resubmit the command.

516 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5874E • CMMVC5884E

CMMVC5874E The action failed because the host CMMVC5880E The virtual disk was not created
does not exist. because a capacity of zero bytes is not
allowed for image mode disks.
Explanation: The action failed because the host does
not exist. Explanation: The host map was not created because
the volume has a capacity of zero bytes.
User response: Specify a different host, and resubmit
the command. User response: Specify a different volume, and
resubmit the command.
CMMVC5875E The action failed because the virtual
disk (VDisk) does not exist. CMMVC5881E The FlashCopy mapping was not
created because an entity that was
Explanation: The action failed because the volume
specified in the command does not
does not exist.
exist.
User response: Specify a different volume, and
Explanation: The FlashCopy mapping was not created
resubmit the command.
because an entity that was specified in the command
does not exist.
CMMVC5876E The VDisk-to-host mapping was not
User response: Specify a different entity, and resubmit
created because the maximum number
the command.
of mappings has been reached.
Explanation: The host map was not created because
CMMVC5882E The FlashCopy mapping was not
the maximum number of mappings has been reached.
created because a mapping for the
User response: Not applicable. source or target virtual disk (VDisk)
already exists.

CMMVC5877E The VDisk-to-host mapping was not Explanation: The FlashCopy mapping was not created
created because the maximum number because a mapping for the source or target volume
of SCSI LUNs has been allocated. already exists.

Explanation: The host map was not created because User response: Specify a different source or target
the maximum number of SCSI LUNs has been volume, and resubmit the command.
allocated.
User response: Not applicable. CMMVC5883E The FlashCopy mapping was not
created because the recovery I/O group
is associated with the source or target
CMMVC5878E The VDisk-to-host mapping was not virtual disk (VDisk).
created because this VDisk is already
mapped to this host. Explanation: The FlashCopy mapping was not created
because the recovery I/O group is associated with the
Explanation: The host map was not created because source or target volume.
this volume is already mapped to this host.
User response: Specify a different recovery I/O group,
User response: Specify a different volume, and and resubmit the command.
resubmit the command.

CMMVC5884E The FlashCopy mapping was not

CMMVC5879E The VDisk-to-host mapping was not created because the source or target
created because a VDisk is already virtual disk (VDisk) cannot be a
mapped to this host with this SCSI member of a Remote Copy mapping.
LUN.
Explanation: The FlashCopy mapping was not created
Explanation: The host map was not created because because the source or target volume cannot be a
this SCSI LUN is already assigned to another mapping. member of a Remote Copy mapping.
User response: Specify a different SCSI LUN, and User response: Specify a different source or target
resubmit the command. volume, and resubmit the command.

Chapter 30. Command-line interface messages 517

CMMVC5885E • CMMVC5895E

CMMVC5885E The FlashCopy mapping was not CMMVC5890E The FlashCopy mapping or
created because this source or target consistency group was not started
virtual disk (VDisk) cannot be a because starting consistency group 0 is
member of a FlashCopy mapping. not a valid operation.
Explanation: The FlashCopy mapping was not created Explanation: The FlashCopy mapping or consistency
because this source or target volume cannot be a group was not started because starting consistency
member of a FlashCopy mapping. group 0 is not a valid operation.
User response: Specify a different source or target User response: Not applicable.
volume, and resubmit the command.
CMMVC5891E The FlashCopy consistency group
CMMVC5886E The FlashCopy mapping was not was not created because the name is not
created because the source or target valid.
virtual disk (VDisk) is associated with
Explanation: The FlashCopy consistency group was
the recovery I/O group.
not created because the name is not valid.
Explanation: The FlashCopy mapping was not created
User response: Specify a different name, and resubmit
because the source or target volume is associated with
the command.
the recovery I/O group.
User response: Specify a different source or target
CMMVC5892E The FlashCopy consistency group
volume, and resubmit the command.
was not created because it already
exists.
CMMVC5887E The FlashCopy mapping was not
Explanation: The FlashCopy consistency group was
created because the source or target
not created because it already exists.
virtual disk (VDisk) must not be in
router mode. User response: Not applicable.
Explanation: The FlashCopy mapping was not created
because the source or target volume must not be in CMMVC5893E The action failed because an entity
router mode. that was specified in the command does
not exist.
User response: Specify a different source or target
volume, and resubmit the command. Explanation: The action failed because an entity that
was specified in the command does not exist.
CMMVC5888E The action failed because an entity User response: Specify the correct entity, and resubmit
that was specified in the command does the command.
not exist.
Explanation: The action failed because an entity that CMMVC5894E The FlashCopy consistency group
was specified in the command does not exist. was not deleted because you are trying
to delete consistency group 0 or the
User response: Specify the correct entity, and resubmit
name of the consistency group is not
the command.
valid.
Explanation: The FlashCopy consistency group was
CMMVC5889E The FlashCopy mapping was not
not deleted because the name of the consistency group
deleted because an entity that was
is not valid or you are trying to delete consistency
specified in the command does not
group 0.
exist.
User response: Specify the correct consistency group,
Explanation: The FlashCopy mapping was not deleted
and resubmit the command.
because an entity that was specified in the command
does not exist.
CMMVC5895E The FlashCopy consistency group
User response: Specify a different entity, and resubmit
was not deleted because it contains
the command.
mappings. To delete this consistency
group, a forced deletion is required.
Explanation: The FlashCopy consistency group was
not deleted because it contains mappings.

518 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5896E • CMMVC5904E

User response: Specify that -force option to delete the

CMMVC5900E The FlashCopy mapping was not
consistency group.
deleted because the mapping or
consistency group is in the suspended
CMMVC5896E The FlashCopy mapping was not state. The mapping or consistency group
deleted because the mapping or must be stopped first.
consistency group is in the preparing
Explanation: The FlashCopy mapping was not deleted
state. The mapping or consistency group
because the mapping or consistency group is in the
must be stopped first.
suspended state. The mapping or consistency group
Explanation: The FlashCopy mapping was not deleted must be stopped first.
because the mapping or consistency group is in the
User response: Stop the consistency group, and
preparing state. The mapping or consistency group
resubmit the command.
must be stopped first.
User response: Stop the consistency group, and
CMMVC5901E The FlashCopy mapping was not
resubmit the command.
prepared because the mapping or
consistency group is already in the
CMMVC5897E The FlashCopy mapping was not preparing state.
deleted because the mapping or
Explanation: The FlashCopy mapping was not
consistency group is in the prepared
prepared because the mapping or consistency group is
state. The mapping or consistency group
already in the preparing state.
must be stopped first.
User response: Not applicable.
Explanation: The FlashCopy mapping was not deleted
because the mapping or consistency group is in the
prepared state. The mapping or consistency group must CMMVC5902E The FlashCopy mapping was not
be stopped first. prepared because the mapping or
consistency group is already in the
User response: Stop the consistency group, and
prepared state.
resubmit the command.
Explanation: The FlashCopy mapping was not
prepared because the mapping or consistency group is
CMMVC5898E The FlashCopy mapping was not
already in the prepared state.
deleted because the mapping or
consistency group is in the copying User response: Not applicable.
state. The mapping or consistency group
must be stopped first.
CMMVC5903E The FlashCopy mapping was not
Explanation: The FlashCopy mapping was not deleted prepared because the mapping or
because the mapping or consistency group is in the consistency group is already in the
copying state. The mapping or consistency group must copying state.
be stopped first.
Explanation: The FlashCopy mapping was not
User response: Stop the consistency group, and prepared because the mapping or consistency group is
resubmit the command. already in the copying state.
User response: Not applicable.
CMMVC5899E The FlashCopy mapping was not
deleted because the mapping or
CMMVC5904E The FlashCopy mapping was not
consistency group is in the stopped
prepared because the mapping or
state. To delete the mapping, a forced
consistency group is already in the
deletion is required.
suspended state.
Explanation: The FlashCopy mapping was not deleted
Explanation: The FlashCopy mapping was not
because the mapping or consistency group is in the
prepared because the mapping or consistency group is
stopped state.
already in the suspended state.
User response: Specify the -force option to delete the
User response: Not applicable.
mapping.

Chapter 30. Command-line interface messages 519

CMMVC5905E • CMMVC5915E

CMMVC5905E The FlashCopy mapping or CMMVC5910E The FlashCopy mapping or

consistency group was not started consistency group was not stopped
because the mapping or consistency because the mapping or consistency
group is in the idle state. The mapping group is in the idle state.
or consistency group must be prepared
Explanation: The FlashCopy mapping or consistency
first.
group was not stopped because the mapping or
Explanation: The FlashCopy mapping or consistency consistency group is in the idle state.
group was not started because the mapping or
User response: Not applicable.
consistency group is in the idle state.
User response: Prepare the mapping or consistency
CMMVC5911E The FlashCopy mapping or
group, and resubmit the command.
consistency group was not stopped
because the mapping or consistency
CMMVC5906E The FlashCopy mapping or group is in the preparing state.
consistency group was not started
Explanation: The FlashCopy mapping or consistency
because the mapping or consistency
group was not stopped because the mapping or
group is in the preparing state.
consistency group is in the preparing state.
Explanation: The FlashCopy mapping or consistency
User response: Not applicable.
group was not started because the mapping or
consistency group is in the preparing state.
CMMVC5912E The FlashCopy mapping or
User response: Not applicable.
consistency group was not stopped
because the mapping or consistency
CMMVC5907E The FlashCopy mapping or group is already in the stopped state.
consistency group was not started
Explanation: The FlashCopy mapping or consistency
because the mapping or consistency
group was not stopped because the mapping or
group is already in the copying state.
consistency group is already in the stopped state.
Explanation: The FlashCopy mapping or consistency
User response: Not applicable.
group was not started because the mapping or
consistency group is already in the copying state.
CMMVC5913E The properties of the FlashCopy
User response: Not applicable.
mapping were not modified because the
mapping or consistency group is in the
CMMVC5908E The FlashCopy mapping or preparing state.
consistency group was not started
Explanation: The properties of the FlashCopy
because the mapping or consistency
mapping were not modified because the mapping or
group is in the stopped state. The
consistency group is in the preparing state.
mapping or consistency group must be
prepared first. User response: Not applicable.
Explanation: The FlashCopy mapping or consistency
group was not started because the mapping or CMMVC5914E The properties of the FlashCopy
consistency group is in the stopped state. mapping were not modified because the
mapping or consistency group is in the
User response: Prepare the mapping or consistency
prepared state.
group, and resubmit the command.
Explanation: The properties of the FlashCopy
mapping were not modified because the mapping or
CMMVC5909E The FlashCopy mapping or
consistency group is in the prepared state.
consistency group was not started
because the mapping or consistency User response: Not applicable.
group is in the suspended state.
Explanation: The FlashCopy mapping or consistency CMMVC5915E The properties of the FlashCopy
group was not started because the mapping or mapping were not modified because the
consistency group is in the suspended state. mapping or consistency group is in the
copying state.
User response: Not applicable.
Explanation: The properties of the FlashCopy
mapping were not modified because the mapping or
consistency group is in the copying state.

520 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5916E • CMMVC5923E

User response: Not applicable. User response: Perform the following steps:
1. Ensure that at least one of the nodes in the I/O
CMMVC5916E The properties of the FlashCopy group of the mapping is online.
mapping were not modified because the 2. Fix all of the unfixed events in the event log.
mapping or consistency group is in the 3. Follow the fix procedures.
suspended state.
Explanation: The properties of the FlashCopy You might be required to delete and re-add ALL of the
mapping were not modified because the mapping or FlashCopy maps and Global and Metro Mirror
consistency group is in the suspended state. relationships in the I/O group.

User response: Not applicable. Resubmit the command.

CMMVC5917E The FlashCopy mapping was not CMMVC5920E The FlashCopy mapping was not
created because there is no memory in created because the consistency group is
which to create the bitmap. not idle.
Explanation: The FlashCopy mapping was not created Explanation: The FlashCopy mapping was not created
because there is no memory to create the bitmap. because the consistency group is not idle.
User response: Not applicable. User response: Not applicable.

CMMVC5918E The FlashCopy mapping was not CMMVC5921E The properties of the FlashCopy
prepared, either because there are no mapping were not modified because the
online nodes in the I/O group or consistency group is not idle.
because there are unrecovered
FlashCopy mappings or unrecovered Explanation: The properties of the FlashCopy
Global Mirror or Metro Mirror mapping were not modified because the consistency
relationships in the I/O group. group is not idle.
Explanation: This error might be caused by a User response: Not applicable.
temporary loss of all of the nodes in the I/O group,
which causes all of the FlashCopy mappings and
CMMVC5922E The FlashCopy mapping was not
Global and Metro Mirror relationships of the I/O group
created because the destination virtual
to be unusable.
disk (VDisk) is too small.
User response: Perform the following steps:
Explanation: The FlashCopy mapping was not created
1. Ensure that at least one of the nodes in the I/O because the destination volume is too small.
group of the mapping is online.
User response: Specify a different volume, and
2. Fix all of the unfixed events in the event log.
resubmit the command.
3. Follow the fix procedures.

You might be required to delete and re-add ALL of the CMMVC5923E The FlashCopy mapping cannot be
FlashCopy maps and Global and Metro Mirror created, either because there are no
relationships in the I/O group. online nodes in the I/O group or
because there are unrecovered
FlashCopy mappings or unrecovered
Resubmit the command.
Global Mirror or Metro Mirror
relationships in the I/O group.
CMMVC5919E The FlashCopy mapping or
Explanation: This error might be caused by a
consistency group was not started, either
temporary loss of all of the nodes in the I/O group,
because there are no online nodes in the
which causes all of the FlashCopy mappings and
I/O group or because there are
Global and Metro Mirror relationships of the I/O group
unrecovered FlashCopy mappings or
to be unusable.
unrecovered Global Mirror or Metro
Mirror relationships in the I/O group. User response: Perform the following steps:
Explanation: This error might be caused by a 1. Ensure that at least one of the nodes in the I/O
temporary loss of all of the nodes in the I/O group, group of the mapping is online.
which causes all of the FlashCopy mappings and 2. Fix all of the unfixed events in the event log.
Global and Metro Mirror relationships of the I/O group 3. Follow the fix procedures.
to be unusable.

Chapter 30. Command-line interface messages 521

CMMVC5924E • CMMVC5935E

You might be required to delete and re-add ALL of the

CMMVC5930E The Remote Copy relationship was
FlashCopy maps and Global and Metro Mirror
not created because an object that was
relationships in the I/O group.
specified in the command does not
exist.
Resubmit the command.
Explanation: The Remote Copy relationship was not
created because an object that was specified in the
CMMVC5924E The FlashCopy mapping was not command does not exist.
created because the source and target
virtual disks (VDisks) are different User response: Specify the correct object, and resubmit
sizes. the command.

Explanation: The FlashCopy mapping was not created

because the source and target volumes are different CMMVC5931E The Remote Copy relationship was
sizes. not created because the master or
auxiliary virtual disk (VDisk) is locked.
User response: Specify a different source and target
volume that are the same size, and resubmit the Explanation: The Remote Copy relationship was not
command. created because the master or auxiliary volume is
locked.

CMMVC5925E The remote cluster partnership was User response: Unlock the master or auxiliary volume,
not created because it already exists. and resubmit the command.

Explanation: The remote cluster partnership was not

created because it already exists. CMMVC5932E The Remote Copy relationship was
not created because the master or
User response: Specify a different remote cluster auxiliary virtual disk (VDisk) is a
partnership, and resubmit the command. member of a FlashCopy mapping.
Explanation: The Remote Copy relationship was not
CMMVC5926E The remote cluster partnership was created because the master or auxiliary volume is a
not created because there are too many member of a FlashCopy mapping, and the partner
partnerships. cluster is running a downlevel software version.
Explanation: The remote cluster partnership was not User response: Not applicable.
created because there are too many partnerships.
User response: Not applicable. CMMVC5933E The Remote Copy relationship was
not created because the master or
CMMVC5927E The action failed because the cluster auxiliary virtual disk (VDisk) is in the
ID is not valid. recovery I/O group.

Explanation: The action failed because the cluster ID Explanation: The Remote Copy relationship was not
is not valid. created because the master or auxiliary volume is in the
recovery I/O group.
User response: Specify the correct cluster ID, and
resubmit the command. User response: Not applicable.

CMMVC5928E The action failed because the cluster CMMVC5934E The Remote Copy relationship was
name is a duplicate of another cluster. not created because the master or
auxiliary virtual disk (VDisk) is in the
Explanation: The action failed because the cluster router mode.
name is a duplicate of another cluster.
Explanation: The Remote Copy relationship was not
User response: Specify a different cluster name, and created because the master or auxiliary volume is in the
resubmit the command. router mode.
User response: Not applicable.
CMMVC5929E The Remote Copy partnership was
not deleted because it has already been
deleted. CMMVC5935E The action failed because an object
that was specified in the command does
Explanation: The Remote Copy partnership was not not exist.
deleted because it has already been deleted.
Explanation: The action failed because an object that
User response: Not applicable. was specified in the command does not exist.

522 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5936E • CMMVC5948E

User response: Specify the correct object, and resubmit

CMMVC5942E The cluster that contains the auxiliary
the command.
virtual disk (VDisk) has too many
consistency groups.
CMMVC5936E The action failed because an object
Explanation: The cluster that contains the auxiliary
that was specified in the command does
volume has too many consistency groups.
not exist.
User response: Not applicable.
Explanation: The action failed because an object that
was specified in the command does not exist.
CMMVC5943E The specified relationship is not
User response: Specify the correct object, and resubmit
valid.
the command.
Explanation: The specified relationship is not valid.
CMMVC5937E The action failed because an object User response: Specify the correct relationship, and
that was specified in the command does resubmit the command.
not exist.
Explanation: The action failed because an object that CMMVC5944E The specified consistency group is
was specified in the command does not exist. not valid.
User response: Specify the correct object, and resubmit Explanation: The specified consistency group is not
the command. valid.
User response: Specify the correct consistency group,
CMMVC5938E The Remote Copy consistency group and resubmit the command.
was not deleted because the consistency
group contains relationships. To delete
CMMVC5945E The specified master cluster is not
the consistency group, the force option
valid.
is required.
Explanation: The specified master cluster is not valid.
Explanation: Remote Copy consistency group was not
deleted because the consistency group contains User response: Specify the correct master cluster, and
relationships. resubmit the command.
User response: Specify the -force option to delete the
consistency group. CMMVC5946E The specified auxiliary cluster is not
valid.
CMMVC5939E The action failed because the cluster Explanation: The specified auxiliary cluster is not
is not in a stable state. valid.
Explanation: The action failed because the cluster is User response: Specify the correct auxiliary cluster,
not in a stable state. and resubmit the command.
User response: Not applicable.
CMMVC5947E The specified master virtual disk
(VDisk) is not valid.
CMMVC5940E The cluster that contains the auxiliary
virtual disk (VDisk) is unknown. Explanation: The specified master volume is not valid.
Explanation: The cluster that contains the auxiliary User response: Specify the correct master volume, and
volume is unknown. resubmit the command.
User response: Not applicable.
CMMVC5948E The specified auxiliary virtual disk
(VDisk) is not valid.
CMMVC5941E The cluster that contains the master
virtual disk (VDisk) has too many Explanation: The specified auxiliary volume is not
consistency groups. valid.
Explanation: The cluster that contains the master User response: Specify the auxiliary volume, and
volume has too many consistency groups. resubmit the command.
User response: Not applicable.

Chapter 30. Command-line interface messages 523

CMMVC5949E • CMMVC5962E

User response: Not applicable.

CMMVC5949E The specified relationship is
unknown.
CMMVC5957E The master virtual disk (VDisk) is
Explanation: The specified relationship is unknown.
already in a relationship.
User response: Specify a different relationship, and
Explanation: The master volume is already in a
resubmit the command.
relationship.
User response: Specify a different master volume, and
CMMVC5950E The specified consistency group is
resubmit the command.
unknown.
Explanation: The specified consistency group is
CMMVC5958E The auxiliary virtual disk (VDisk) is
unknown.
already in a relationship.
User response: Specify a different consistency group,
Explanation: The auxiliary volume is already in a
and resubmit the command.
relationship.
User response: Specify a different auxiliary volume,
CMMVC5951E The operation cannot be performed
and resubmit the command.
because the relationship is not a
stand-alone relationship.
CMMVC5959E There is a relationship that already
Explanation: The operation cannot be performed
has this name on the master cluster.
because the relationship is not a stand-alone one.
Explanation: There is a relationship that already has
User response: Not applicable.
this name on the master cluster.
User response: Specify a different name, and resubmit
CMMVC5952E The relationship and consistency
the command.
group have different master clusters.
Explanation: The relationship and consistency group
CMMVC5960E There is a relationship that already
have different master clusters.
has this name on the auxiliary cluster.
User response: Not applicable.
Explanation: There is a relationship that already has
this name on the auxiliary cluster.
CMMVC5953E The relationship and group have
User response: Specify a different name, and resubmit
different auxiliary clusters.
the command.
Explanation: The relationship and group have
different auxiliary clusters.
CMMVC5961E There is a consistency group that
User response: Not applicable. already has this name on the master
cluster.
CMMVC5954E The master and auxiliary virtual Explanation: There is a consistency group that already
disks (VDisks) are different sizes. has this name on the master cluster.
Explanation: The master and auxiliary volumes are User response: Specify a different name, and resubmit
different sizes the command.
User response: Not applicable.
CMMVC5962E There is a consistency group that
already has this name on the auxiliary
CMMVC5955E The maximum number of
cluster.
relationships has been reached.
Explanation: There is a consistency group that already
Explanation: The maximum number of relationships
has this name on the auxiliary cluster.
has been reached.
User response: Specify a different name, and resubmit
User response: Not applicable.
the command.

CMMVC5956E The maximum number of consistency

groups has been reached.
Explanation: The maximum number of consistency
groups has been reached.

524 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5963E • CMMVC5975E

2. Fix all of the unfixed events in the event log.

CMMVC5963E No direction has been defined.
3. Follow the fix procedures.
Explanation: No direction has been defined.
User response: Not applicable. You might be required to delete and re-add ALL of the
FlashCopy maps and Global and Metro Mirror
relationships in the I/O group.
CMMVC5964E The copy priority is not valid.
Explanation: The copy priority is not valid. Resubmit the command.

User response: Not applicable.

CMMVC5970E The Remote Copy relationship was
not created because there is not enough
CMMVC5965E The virtual disks (VDisks) are in memory.
different I/O groups on the local cluster.
Explanation: The Remote Copy relationship was not
Explanation: The volumes are in different I/O groups created because there is not enough memory.
on the local cluster.
User response: Not applicable.
User response: Not applicable.

CMMVC5971E The operation was not performed

CMMVC5966E The master virtual disk (VDisk) is because the consistency group contains
unknown. no relationships.
Explanation: The master volume is unknown. Explanation: The operation was not performed
User response: Specify a different master volume, and because the consistency group contains no
resubmit the command. relationships.
User response: Not applicable.
CMMVC5967E The auxiliary virtual disk (VDisk) is
unknown. CMMVC5972E The operation was not performed
Explanation: The auxiliary volume is unknown. because the consistency group contains
relationships.
User response: Specify a different auxiliary volume,
and resubmit the command. Explanation: The operation was not performed
because the consistency group contains relationships.

CMMVC5968E The relationship cannot be added User response: Not applicable.

because the states of the relationship
and the consistency group do not match. CMMVC5973E The operation was not performed
Explanation: The relationship cannot be added because the consistency group is not
because the states of the relationship and the synchronized.
consistency group do not match. Explanation: The operation was not performed
User response: Not applicable. because the consistency group is not synchronized.
User response: Specify the Force option when starting
CMMVC5969E The Remote Copy relationship was the consistency group.
not created, either because there are no
online nodes in the I/O group or CMMVC5974E The operation was not performed
because there are unrecovered because the consistency group is offline.
FlashCopy mappings or unrecovered
Global Mirror or Metro Mirror Explanation: The operation was not performed
relationships in the I/O group. because the consistency group is offline.

Explanation: This error might be caused by a User response: Not applicable.

temporary loss of all of the nodes in the I/O group,
which causes all of the FlashCopy mappings and CMMVC5975E The operation was not performed
Global and Metro Mirror relationships of the I/O group because the cluster partnership is not
to be unusable. connected.
User response: Perform the following steps: Explanation: The operation was not performed
1. Ensure that at least one of the nodes in the I/O because the cluster partnership is not connected.
group is online.
User response: Not applicable.

Chapter 30. Command-line interface messages 525

CMMVC5976E • CMMVC5987E

because the relationship is in the freezing state.

CMMVC5976E The operation was not performed
because the consistency group is in the User response: Not applicable.
freezing state.
Explanation: The operation was not performed CMMVC5982E The operation was not performed
because the consistency group is in the freezing state. because it is not valid given the current
relationship state.
User response: Not applicable.
Explanation: The operation was not performed
because it is not valid given the current relationship
CMMVC5977E The operation was not performed
state.
because it is not valid given the current
consistency group state. User response: Not applicable.
Explanation: The operation was not performed
because it is not valid given the current consistency CMMVC5983E dump file was not created. This may
group state. be due to the file system being full.
User response: Not applicable. Explanation: dump file was not created. This may be
due to the file system being full.
CMMVC5978E The operation was not performed User response: Not applicable.
because the relationship is consistent
but is not synchronized. Restarting the
relationship by using the -force CMMVC5984E The dump file was not written to
parameter will make the relationship disk. This may be due to the file system
inconsistent until the background copy being full.
has completed. Explanation: The dump file was not written to disk.
Explanation: Input transactions have occurred on This may be due to the file system being full.
either the primary or secondary volumes since the User response: Not applicable.
ConsistentStopped or Idling state has occurred. Because
the relationship is no longer synchronized, the state of
the relationship is now Stopped. CMMVC5985E The action failed because the
specified directory is not permitted for
The -force parameter of the startrcrelationship this command.
command is required when the relationship is not
synchronized because consistency would be lost by Explanation: You have attempted to copy, delete, or
starting the copy operation. Submitting the list dumps from a directory that is not valid. A list of
startrcrelationship command on an unsynchronized valid directories for these commands is provided in the
relationship without using the -force parameter is not documentation.
supported. User response: Ensure that the directory you specify
If a relationship is in the InconsistentStopped, is valid, and resubmit the command.
InconsistentCopying or ConsistentSynchronized state,
the -force parameter is not required, but is supported. CMMVC5986E The tracing of I/O operations was not
User response: Consider using the -force parameter of started because the virtual disk (VDisk)
the startrcrelationship command, if appropriate. or managed disk (MDisk) failed to
return any statistics.

CMMVC5980E The operation was not performed Explanation: The tracing of I/O operations was not
because the master and auxiliary started because the volume or managed disk (MDisk)
clusters are not connected. failed to return statistics.

Explanation: The operation was not performed User response: Not applicable.
because the master and auxiliary clusters are not
connected. CMMVC5987E VALUE is not a valid command line
User response: Not applicable. option.
Explanation: The specified string that you have
CMMVC5981E The operation was not performed entered is not a supported command line option.
because the relationship is in the User response: Specify a supported option, and
freezing state. resubmit the command.
Explanation: The operation was not performed

526 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC5988E • CMMVC6001E

v There is not enough space on the system to copy the

CMMVC5988E command should not be run by the
file.
root userid. Use the admin userid.
v The package is incomplete or contains errors.
Explanation: This command should not be issued if
you are logged in with a root user ID. Use the admin User response: If the copy failed with an error
userid. indicating that there was insufficient space on the
system, free up additional space on your system.
User response: Log off of the root user ID and log in Otherwise, ensure that the cluster time and date stamp
as admin. on the signature is correct. (For example, the time and
date cannot be in the future.)
CMMVC5989E The operation was not performed
because the relationship is offline. CMMVC5995E An error prevented the unpacking of
Explanation: The operation was not performed the upgrade package.
because the relationship is offline. Explanation: The system disk is too full to allow the
User response: Not applicable. upgrade package to be unpacked.
User response: Use the cleardumps command with the
CMMVC5990E The FlashCopy consistency group parameter -prefix /home/admin/upgrade/ to clear
was not stopped as there are no unused files, then reboot the node before attempting to
FlashCopy mappings within the group. unpack the upgrade package again.

Explanation: The FlashCopy consistency group was

not stopped as there are no FlashCopy mappings CMMVC5996E The specific upgrade package cannot
within the group. be installed over the current version.

User response: Not applicable. Explanation: The upgrade package is not compatible
with the current version or the system.

CMMVC5991E The Remote Copy consistency group User response: Check the available upgrade packages
was not stopped as there are no Remote and find the correct upgrade package for your current
Copy relationships within the group. version and for your system. If the upgrade package is
correct for your system, check the version requirements
Explanation: The Remote Copy consistency group was for the package. You might have to upgrade the current
not stopped as there are no Remote Copy relationships version to an intermediate version before you upgrade
within the group. to the latest version. (For example, if your current
User response: Not applicable. version is 1 and you are trying to upgrade to version 3,
you might need to upgrade to version 2 before
applying the version 3 upgrade.)
CMMVC5992E The Remote Copy consistency group
was not stopped as there are no Remote
Copy relationships within the group. CMMVC5999W Featurization for this facility has not
been enabled.
Explanation: The Remote Copy consistency group was
not stopped as there are no Remote Copy relationships Explanation: Featurization for this facility has not
within the group. been enabled.

User response: Not applicable. User response: Not applicable.

CMMVC5993E The specified upgrade package does CMMVC6000W Featurization for this facility has not
not exist. been enabled.

Explanation: The specified upgrade package does not Explanation: Featurization for this facility has not
exist. been enabled.

User response: Not applicable. User response: Not applicable.

CMMVC5994E Error in verifying the signature of the CMMVC6001E The FlashCopy consistency group
upgrade package. was not started as there are no
FlashCopy mappings within the group.
Explanation: The system could not verify the
signature of the upgrade package due to the following Explanation: The FlashCopy consistency group was
reasons: not started as there are no FlashCopy mappings within
the group.

Chapter 30. Command-line interface messages 527

CMMVC6002E • CMMVC6013E

User response: Create a FlashCopy within the

CMMVC6009E Unable to malloc a block of memory
appropriate group.
in which to copy the returned data.
Explanation: The command line was unable to
CMMVC6002E This command can only be run on a
allocate a block of memory in which to copy the results
node that is in the service state.
of the query.
Explanation: This command can only be run on a
User response: Resubmit the command. If the
node that is in the service state.
problem persists, contact IBM technical support for
User response: Not applicable. assistance.

CMMVC6003E This command can not be run on a CMMVC6010E Unable to complete the command as
node that is in the service state. there are insufficient free extents, or the
command requested an expansion of 0
Explanation: This command can not be run on a node size.
that is in the service state.
Explanation: There are not enough free extents to
User response: Not applicable. meet the request.
User response: Not applicable.
CMMVC6004E The delimiter value VALUE is invalid.
Explanation: The specified value is not a valid CMMVC6011E This cluster is part of a remote
delimiter value. cluster partnership. Because this
User response: Specify a different delimiter. upgrade package will make changes to
the cluster state, it cannot be applied to
the current code level until all remote
CMMVC6005E The view request failed as the cluster partnerships are deleted.
specified object is not a member of an
appropriate group. Explanation: You have attempted to apply software
when a Remote Copy relationship to a remote cluster
Explanation: A view was request on an object that has exists.
been incorrectly initialized.
User response: Delete the Remote Copy relationship
User response: Ensure that the object is correctly to the remote clusters, and resubmit the command.
initialized before resubmitting the view request.

CMMVC6012W The virtualized storage capacity is

CMMVC6006E The managed disk (MDisk) was not approaching the amount that you are
deleted because the resource was busy. licensed to use.
Explanation: An attempt was made to delete an Explanation: The requested action has completed.
MDisk from a storage pool that is being used as a However, the limits permitted by the license you
source and destination for migration operations. purchased are approaching.
User response: Ensure that the storage pool is not User response: Subsequent actions might require that
being used for migration operations before reissuing you increase your licensed limits.
the command.

CMMVC6013E The command failed because there is

CMMVC6007E The two passwords that were entered a consistency group mismatch on the
do not match. aux cluster.
Explanation: The two passwords entered for Explanation: The action has failed as there was a
verification of your password change were not the difference in attributes between the Metro Mirror
same. consistency groups involved.
User response: Re-enter the passwords. User response: Ensure that the attributes of the two
Metro Mirror consistency groups match before
CMMVC6008E The key already exists. resubmitting the command.

Explanation: An attempt was made to load a

duplicate SSH key.
User response: Not applicable.

528 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6014E • CMMVC6025E

CMMVC6014E The command failed because the CMMVC6020E The software upgrade failed because
requested object is either unavailable or the system was unable to distribute the
does not exist. software package to all of the nodes.
Explanation: The command failed because the Explanation: The system could not complete the
requested object is either unavailable or does not exist. process of updating files. A full disk is a possible cause.
User response: Ensure that all parameters have been User response: Ensure that all nodes are online, and
correctly entered. If this is the case the determine why use the cleandumps command to clean the upgrades
the object is unavailable, then resubmit the command. directory.

CMMVC6015E A delete request is already in CMMVC6021E The system is currently busy

progress for this object. performing another request. Try again
later.
Explanation: A delete request is already in progress
for this object. Explanation: The requested action failed as the system
is processing another request.
User response: Not applicable.
User response: Wait before resubmitting the request.
CMMVC6016E The action failed as there would be,
or are, no more disks in the MDisk CMMVC6022E The system is currently busy
group. performing another request. Try again
later.
Explanation: The action failed as there would be, or
are, no more disks in the I/O group. Explanation: The requested action failed as the system
is processing another request.
User response: Ensure that all parameters have been
correctly entered. User response: Wait before resubmitting the request.

CMMVC6017E A parameter or argument contains CMMVC6023E The system is currently busy

invalid characters. Ensure that all performing another request. Try again
characters are ASCII. later.
Explanation: The command-line interface (CLI) will Explanation: The requested action failed as the system
only accept ASCII input. is processing another request.
User response: Ensure that all input to the CLI is User response: Wait before resubmitting the request.
ASCII, then resubmit the command.
CMMVC6024E The auxiliary VDisk entered is
CMMVC6018E The software upgrade pre-install invalid.
process failed.
Explanation: The auxiliary volume is entered as a
Explanation: The software upgrade failed as there was parameter in the command-line interface is not a valid
an error during the preprocessing. The package is auxiliary volume.
either not valid or corrupted.
User response: Select a valid auxiliary volume, and
User response: Ensure the package is a valid upgrade resubmit the command.
package. Download the package from the source
location again as it might have been corrupted during a
CMMVC6025E The RC consistency group Master
network transfer.
cluster is not the local cluster.
Explanation: The auxiliary volume is entered as a
CMMVC6019E The software upgrade failed as a
parameter in the command-line interface is not a valid
node pended as the upgrade was in
auxiliary volume.
progress.
User response: Resubmit the command with a
Explanation: The software upgrade failed as a node
consistency group that belongs to the local cluster.
pended as the upgrade was in progress.
User response: Ensure that all nodes are online and
available before restarting the upgrade process.

Chapter 30. Command-line interface messages 529

CMMVC6026E • CMMVC6037E

CMMVC6026E The RC consistency group is not in CMMVC6031E The operation was not performed
the stopped state. because the FlashCopy consistency
group is empty.
Explanation: The action failed as the Metro Mirror
consistency group is not in the stopped state. Explanation: An attempt was made to prestart an
empty FlashCopy consistency group.
User response: Ensure that the Metro Mirror
consistency group is in the stopped state before User response: Not applicable.
resubmitting the command.
CMMVC6032E The operation was not performed
CMMVC6027E The RC consistency group is not the because one or more of the entered
primary master. parameters is invalid for this operation.
Explanation: The RC consistency group requested in Explanation: An parameter that is not valid was
the command is not the Metro Mirror primary master. entered for the command.
User response: Ensure that the parameters have been User response: If attempting to change the I/O group
entered correctly on the command line. to which the volume belongs, ensure that the volume is
not already a part of the group.
CMMVC6028E This upgrade package cannot be
applied to the current software level CMMVC6033E The action failed due to an internal
because it contains changes to the error.
cluster state and there are remote cluster
Explanation: An internal error caused the action to
partnership defined.
fail.
Explanation: The action failed because there is a
User response: Not applicable.
connected remote cluster. The upgrade cannot be
applied because it would render the remote cluster at a
different code level to the remote cluster. CMMVC6034E The action failed because the
maximum number of objects has been
User response: Ensure that the cluster partnership is
reached.
unconfigured before resubmitting the command. Ensure
that you unconfigure the remote cluster and upgrade Explanation: The action failed because the maximum
the code on it before reconfiguring the cluster number of objects has been reached.
partnership.
User response: Not applicable.

CMMVC6029E All nodes must have identical code

level before a concurrent code upgrade CMMVC6035E The action failed as the object
can be performed. already exists.

Explanation: The concurrent upgrade failed as two or Explanation: An operation was requested to create an
more nodes were at differing code levels. All nodes object that already exists.
must be at the same code level before a software User response: Ensure that the name you are
upgrade can be performed. attempting to apply to a new object does not exist, or
User response: Use the service assistant to bring all change the name before re-issuing the command.
nodes to the same level before resubmitting the
concurrent upgrade. CMMVC6036E An invalid action was requested.
Explanation: The action failed because it is not a valid
CMMVC6030E The operation was not performed action with the command that was issued.
because the FlashCopy mapping is part
of a consistency group. The action must User response: Issue an action that is valid with the
be performed at the consistency group command.
level.
Explanation: An attempt was made to stop a CMMVC6037E The action failed as the object is not
FlashCopy mapping. This failed as the FlashCopy empty.
mapping is part of a consistency group. Explanation: The action failed because an object was
User response: Issue the stop command to the specified.
FlashCopy consistency group. This will stop all User response: Resubmit the command without
FlashCopies within that group that are in progress. specifying an object.

530 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6038E • CMMVC6051E

CMMVC6038E The action failed as the object is CMMVC6045E The action failed, as the -force flag
empty. was not entered.
Explanation: The action failed because an object was Explanation: The action failed because the -force
not specified. option was not entered.
User response: Specify an object, and resubmit the User response: Specify the -force option in the
command. command.

CMMVC6039E The action failed as the object is not CMMVC6046E The action failed as too many
a member of a group. candidates were selected.
Explanation: The action failed because the object is Explanation: The action failed because too many
not a member of a group. candidates were specified.
User response: Specify an object that is part of a User response: Specify fewer candidates in the
group, and resubmit the command. command.

CMMVC6040E The action failed as the object is not CMMVC6047E The action failed as too few
a parent. candidates were selected.
Explanation: The action failed because the object is Explanation: An action was requested with too few
not a parent object. candidate objects.
User response: Specify an object that is a parent, and User response: Determine the correct number of
resubmit the command. candidates required for the specific command and
reissue the command.
CMMVC6041E The action failed as the cluster is
full. CMMVC6048E The action failed as the object is
busy.
Explanation: The action failed because the cluster is
full. Explanation: The action failed because the object is
busy.
User response: Remove data from the cluster, and
resubmit the command. User response: Not applicable.

CMMVC6042E The action failed as the object is not CMMVC6049E The action failed as the object is not
a cluster member. ready.
Explanation: The action failed because the object is Explanation: The action failed because the object is
not a member of the cluster. not ready.
User response: Specify an object that is a member of User response: Not applicable.
the cluster, and resubmit the command.
CMMVC6050E The action failed as the command
CMMVC6043E The action failed as the object is a was busy.
member of a group.
Explanation: The action failed because the command
Explanation: The action failed because the object is a is busy.
member of a group.
User response: Not applicable.
User response: Specify an object that is not a member
of a group, and resubmit the command.
CMMVC6051E An unsupported action was selected.
Explanation: The action failed because it is not valid
CMMVC6044E The action failed as the object is a
with the command.
parent.
User response: Specify an action that is valid with the
Explanation: The action failed because the object is a
command.
parent object.
User response: Specify an object that is not a parent
object, and resubmit the command.

Chapter 30. Command-line interface messages 531

CMMVC6052E • CMMVC6066E

CMMVC6052E The action failed as the object is a CMMVC6060E The action failed as the object is
member of a FlashCopy mapping. being deleted.
Explanation: The object is a member of a FlashCopy Explanation: The action failed because the object is
mapping, thus it cannot be deleted. being deleted.
User response: Specify an object that is not a member User response: Not applicable.
of a FlashCopy mapping, or remove the object from the
FlashCopy mapping.
CMMVC6061E The action failed as the object is
being resized.
CMMVC6053E An invalid WWPN was entered.
Explanation: The action failed because the object is
Explanation: A worldwide port name (WWPN) that is being resized.
not valid was specified.
User response: Check that the object is in the correct
User response: Specify a valid WWPN. mode, and resubmit the command.

CMMVC6054E The action failed as not all nodes are CMMVC6062E The action failed as the object is
online. being moved between HWS.
Explanation: One or more nodes are not online. Explanation: An attempt was made to perform an
action against an object that is currently being moved
User response: Check that each node is online, and
between I/O groups.
resubmit the command.
User response: Re-issue the command when the move
operation has completed.
CMMVC6055E The action failed as an upgrade is in
progress.
CMMVC6063E The action failed as there are no
Explanation: The action failed because a software
more disks in the group.
upgrade is in progress.
Explanation: An attempt was made to perform an
User response: Wait for the software upgrade to
action against a group that contained no disks.
complete, and resubmit the command.
User response: Either add disks to the group and
reissue the command, or select another group against
CMMVC6056E The action failed as the object is too
which to execute the action.
small.
Explanation: The action failed because the object is
CMMVC6064E The action failed as the object has an
too small.
invalid name.
User response: Specify a different object, and resubmit
Explanation: An attempt was made to create or
the command.
rename an object using a name that is not valid.
User response: Use a name that meets the naming
CMMVC6058E The action failed as the object is in
standards and reissue the command.
the recovery HWS.
Explanation: An attempt was made to perform an
CMMVC6065E The action failed as the object is not
operation on a node that is in the recovery I/O group.
in a group.
User response: Get the node into one of the other I/O
Explanation: An attempt was made to perform an
groups and reissue the command.
action on an object that was not in an appropriate
group.
CMMVC6059E The action failed as the object is in
User response: Ensure that the object is a member of
an invalid mode.
an appropriate group and reissue the command.
Explanation: The action failed because the object is in
the wrong mode.
CMMVC6066E The action failed as the system is
User response: Check that the object is in the correct running low on memory.
mode, and resubmit the command.
Explanation: The system is running low on memory.
User response: Not applicable.

532 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6067E • CMMVC6081E

CMMVC6067E The action failed as the SSH key was CMMVC6075E The expand failed as the last extent is
not found. not a complete extent.
Explanation: An attempt was made to perform an Explanation: The expand failed as the last extent is
action using an SSH key that does not exist. not a complete extent.
User response: Reissue the command using a key that User response: Assign a different extent, and resubmit
does exist. the command.

CMMVC6068E The action failed as there are no free CMMVC6076E The command failed because the
SSH keys. virtual disk cache is not empty. Either
wait for the cache to flush or use the
Explanation: An attempt was made to use an SSH key
force flag to discard the contents of the
when there are no free SSH keys.
cache.
User response: Upload additional keys and reissue the
Explanation: The command failed due to an error
command.
during the flushing of the volume.
User response: Not applicable.
CMMVC6069E The action failed as the SSH key is
already registered.
CMMVC6077E WARNING - Unfixed errors should
Explanation: An attempt was made to register an SSH
be fixed before applying software
key that was already registered.
upgrade. Depending on the nature of
User response: Not applicable. the errors, they might cause the upgrade
process to fail. It is highly
recommended to fix these errors before
CMMVC6070E An invalid or duplicated parameter, proceeding. If a particular error cannot
unaccompanied argument, or incorrect be fixed, contact the support center.
argument sequence has been detected.
Ensure that the input is as per the help. Explanation: Unfixed errors should be fixed before
applying software upgrade. Depending on the nature of
Explanation: The parameters entered for a command the errors, they might cause the upgrade process to fail.
were not valid. It is highly recommended to fix these errors before
User response: Correct the parameters and reissue the proceeding.
command. User response: If the error cannot be fixed, contact the
support center.
CMMVC6071E The VDisk-to-host mapping was not
created because the VDisk is already CMMVC6078E The action failed because the object
mapped to a host. is in an invalid mode.
Explanation: The volume is already mapped to a host. Explanation: An attempt was made to perform an
User response: Not applicable. action against an object in a mode that did not allow
for that action to be performed.

CMMVC6073E The maximum number of files has User response: Get the object into a suitable mode
been exceeded. and reissue the command.

Explanation: The maximum number of files has been

exceeded. CMMVC6079E Metadata recovery could not
complete the operation because a
User response: Not applicable. parameter is invalid.
Explanation: Metadata recovery could not complete
CMMVC6074E The command failed as the extent has the operation because a parameter is not valid.
already been assigned.
User response:
Explanation: The command failed as the extent has
already been assigned.
CMMVC6081E Metadata Recovery is busy
User response: Assign a different extent, and resubmit processing the previous operation.
the command.
Explanation: Metadata Recovery is busy processing
the previous operation.

Chapter 30. Command-line interface messages 533

CMMVC6082E • CMMVC6096E

User response:
CMMVC6088E The lba at which metadata recovery
was requested does not contain
CMMVC6082E The attempt to abort metadata metadata.
recovery failed because the previous
Explanation: The lba at which metadata recovery was
operation has completed.
requested does not contain metadata.
Explanation: The attempt to cancel metadata recovery
User response:
failed because the previous operation has completed.
User response: None.
CMMVC6089E The metadata at the requested lba is
flagged as invalid.
CMMVC6083E Metadata recovery could not find a
Explanation: The metadata at the requested lba is
valid dumpfile required for the rebuild
flagged as not valid.
operation.
User response:
Explanation: Metadata recovery could not find a valid
dumpfile required for the rebuild operation.
CMMVC6090E The metadata header checksum
User response:
verification failed.
Explanation: The metadata header checksum
CMMVC6084E Metadata recovery could not
verification failed.
create/open/write the scan file, the disk
might be full. User response:
Explanation: Metadata recovery could not
create/open/write the scan file, the disk might be full. CMMVC6091E The metadata region checksum
verification failed.
User response:
Explanation: The metadata region checksum
verification failed.
CMMVC6085E Metadata recovery could not
create/open/write the dump file, the disk User response:
might be full.
Explanation: Metadata recovery could not CMMVC6092E The metadata recovery operation was
create/open/write the dump file, the disk might be aborted.
full.
Explanation: The metadata recovery operation was
User response: cancelled.
User response:
CMMVC6086E Metadata recovery could not
create/open/write the progress file, the
CMMVC6093E Metadata recovery internal error -
disk might be full.
(read only)
Explanation: Metadata recovery could not
Explanation: Metadata recovery internal error - (read
create/open/write the progress file, the disk might be
only)
full.
User response:
User response:

CMMVC6095E Metadata recovery encountered the

CMMVC6087E Metadata recovery could not map the
end of the disk.
buffers necessary to complete the
operation. Explanation: Metadata recovery encountered the end
of the disk.
Explanation: Metadata recovery could not map the
buffers necessary to complete the operation. User response:
User response:
CMMVC6096E The metadata recovery task could not
be initiated because the required
back-end resource could not be found.
Explanation: The back-end resource that is required
for the task is unavailable.

534 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6097E • CMMVC6109E

User response: Ensure that the required back-end

CMMVC6105E Different names for source
resource is available, and reinitiate the task.
SOURCE_CLUSTER_NAME and target
TARGET_CLUSTER_NAME clusters
CMMVC6097E The metadata recovery task could not
Explanation: The backup configuration cannot be
be initiated because the system was
restored to the target cluster because the source and
unable to send the required I/O to the
target cluster have different names.
back-end resource.
User response: Perform one of the following actions:
Explanation: The back-end resource is possibly not
(1) Use a different backup configuration. (2) Delete the
configured properly.
cluster and recreate it with the same name as that
User response: Ensure that the required back-end stored in the backup configuration file.
resource is accessible, and reinitiate the task.
CMMVC6106W Target cluster has non-default
CMMVC6098E The copy failed as the specified node id_alias ALIAS .
is the configuration node.
Explanation: The specified id_alias of the target
Explanation: The copy failed because the specified cluster is a non-default value. Clusters should have the
node is the configuration node. default value. The non-default value suggests that the
cluster is customized and is not suitable for restoration.
User response: Not applicable. Restoration changes the id_alias.
User response: Change the id_alias to a default value,
CMMVC6100E OPTION not consistent with ACTION and resubmit the command.
Explanation: The specified option is not supported for
the specified action. CMMVC6107E NUMBER_OF_OBJECTS io_grp
User response: Remove the option, and resubmit the objects in target cluster;
command. NUMBER_OF_REQUIRED_OBJECTS are
required

CMMVC6101E OPTION not consistent with OPTION Explanation: The number of I/O groups in the target
cluster is not sufficient to accommodate the I/O groups
Explanation: The two specified options cannot be defined in the backup configuration file. Determine
used together. why there are not enough I/O groups.
User response: Remove one of the options, and User response: Correct the problem, and resubmit the
resubmit the command. command.

CMMVC6102E OPTION and OPTION are CMMVC6108I Disk controller system with a WWNN
alternatives of WWNN_VALUE found.
Explanation: The two specified options are Explanation: A disk controller system with the
alternatives, and cannot be used together. required WWNN has been found.
User response: Remove one of the options, and User response: Not applicable.
resubmit the command.

CMMVC6109E Disk controller system with a

CMMVC6103E Problem with FILENAME : DETAILS WWNN of WWNN_VALUE not available.
Explanation: A problem occurred when opening the Explanation: A disk controller system with the
specified file. Determine the cause of the problem and specified WWNN has been found. Ensure that the
correct it before trying again. specified disk controller system is available to the
User response: Correct the problem, and resubmit the cluster.
command. User response: Ensure that the required disk
controller system is available to the cluster, and
CMMVC6104E Action ACTION not run resubmit the command.

Explanation: An unexpected error has occurred.

User response: Contact IBM technical support for
assistance.

Chapter 30. Command-line interface messages 535

CMMVC6110E • CMMVC6123E

CMMVC6110E Bad code level: VALUE . CMMVC6117E FIX_OR_FEATURE is not available.

Explanation: An unexpected error has occurred. Explanation: An unexpected error has occurred.
User response: Contact IBM technical support for User response: Contact IBM technical support for
assistance. assistance.

CMMVC6111E The cluster code level could not be CMMVC6118I TYPE with PROPERTY
determined from VALUE . PROPERTY_VALUE and PROPERTY
PROPERTY_VALUE found.
Explanation: The code level of the cluster could not be
determined. The code level should be of the format Explanation: An object in the cluster has been found
x.y.z, where x, y, and z are integers. with the correct properties.
User response: If the cause of the problem cannot be User response: Not applicable.
determined, contact IBM technical support for
assistance.
CMMVC6119E TYPE with PROPERTY
PROPERTY_VALUE not found.
CMMVC6112W OBJECT_TYPE OBJECT_NAME has a
Explanation: An object in the cluster with the correct
default name.
properties has not been found. Restoration cannot
Explanation: An object in the cluster has a default proceed without the object.
name. This can cause problems when restoring a cluster
User response: Determine why the object cannot be
because default names are changed during restoration.
found. Ensure that the object is available, and resubmit
Object IDs are also changed during restoration.
the command.
User response: Choose an appropriate name for each
object in the cluster, and resubmit the command.
CMMVC6120E Target is not the configuration node
Explanation: The target is not the configuration node.
CMMVC6113E The command COMMAND has failed
with return code RETURN_CODE . User response: Redirect the action against the
configuration node, and resubmit the command.
Explanation: An attempt to run a command remotely
failed using secure communications.
CMMVC6121E No cluster id or id_alias in backup
User response: Determine the cause of the problem,
configuration.
and resubmit the command.
Explanation: Neither the cluster id_alias nor the ID
can be extracted from the backup configuration file.
CMMVC6114E No help for action ACTION .
User response: If the cause of the problem cannot be
Explanation: There is no help for the specified action
determined, contact IBM technical support for
topic.
assistance.
User response: Not applicable.
CMMVC6122E No TYPE with PROPERTY VALUE is
CMMVC6115W Feature FEATURE_PROPERTY present in the table.
mismatch: VALUE expected; VALUE
Explanation: An unexpected error has occurred.
found.
User response: Contact IBM technical support for
Explanation: The features in the backup configuration
assistance.
file and the target cluster do not match. There should
be an exact match between the two. Nevertheless, the
restore of the configuration can continue. CMMVC6123E No PROPERTY for TYPE NAME .
User response: Not applicable. Explanation: An unexpected error has occurred.
User response: Contact IBM technical support for
CMMVC6116I Feature match for FEATURE . assistance.
Explanation: The features in the backup configuration
file and the target cluster are an exact match.
User response: Not applicable.

536 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6124E • CMMVC6137W

CMMVC6124E No TYPE with PROPERTY VALUE CMMVC6131E No location cluster information

Explanation: An unexpected error has occurred. Explanation: An unexpected error has occurred.
User response: Contact IBM technical support for User response: Contact IBM technical support for
assistance. assistance.

CMMVC6125E No unique ID for TYPE NAME CMMVC6132E The object OBJECT of type TYPE has
a property PROPERTY with an incorrect
Explanation: An unexpected error has occurred.
value INCORRECT_VALUE . The
User response: Contact IBM technical support for operation cannot proceed until the
assistance. property has the correct value
CORRECT_VALUE . Take administrative
action to change the value and try again.
CMMVC6126E No TYPE with unique ID VALUE
Explanation: The specified object has the specified
Explanation: An unexpected error has occurred. property of the specified type with the specified
User response: Contact IBM technical support for incorrect value. The property most likely reflects the
assistance. state of the object.
User response: Change the state to the required value,
CMMVC6127I The SSH key IDENTIFIER for USER is and resubmit the command.
already defined; the SSH key will not
be restored CMMVC6133E Required TYPE property PROPERTY
Explanation: An identical SSH key for this user is not found
already defined on the cluster. Therefore, the key in the Explanation: An unexpected error has occurred.
backup file will not be restored.
User response: Contact IBM technical support for
User response: Specify a different SSH key, and assistance.
resubmit the command.

CMMVC6134E No argument for OPTION

CMMVC6128W DIRECTORY
Explanation: No argument has been supplied for the
Explanation: The files in the specified directory cannot specified option, which requires an argument.
be listed.
User response: Supply an argument, and resubmit the
User response: Determine why the files cannot be command.
listed, correct the problem, and resubmit the command.

CMMVC6135E Argument VALUE for OPTION is not

CMMVC6129E VDisk-to-host mapping objects have valid.
VDisk_UID values that are not
consistent. Explanation: The specified argument that you have
supplied is not valid for the specified option.
Explanation: All of the host mapping objects do not
have the same number for the volume LUN instance. User response: Supply an valid argument, and
Therefore, there is a possibility the backup resubmit the command.
configuration file is corrupt. The LUN instance number
should be the same for all host mapping objects that
CMMVC6136W No SSH key file FILENAME
are associated with a specific volume. The LUN
instance number is incorporated into the volume ID Explanation: The specified file, which should contain
property. the SSH key, is not present and will not be restored.
The backup operation will continue.
User response: Determine why the LUN instance
number is not the same, correct the problem, and User response: No action is required. You might have
resubmit the command. to manually restore the key.

CMMVC6130W Inter-cluster PROPERTY VALUE will CMMVC6137W No SSH key file FILENAME; key not
not be restored. restored
Explanation: The restoration of inter-cluster objects is Explanation: An SSH key cannot be restored because
not supported. the specified file, which is expected to contain the SSH
key, is not present. The restore operation will continue.
User response: Not applicable.

Chapter 30. Command-line interface messages 537

CMMVC6138E • CMMVC6149E

User response: After the restore is complete, locate the

CMMVC6144W The object with default name NAME
file containing the key, and perform one of the
has been restored as
following actions: (1) Rename the file so that it has the
SUBSTITUTE_NAME .
correct name, and resubmit the command. (2) Restore
the key manually using the addsshkey command. Explanation: An object with a default name bas been
restored with a different name. Ensure that you account
for this name change when using the restored cluster in
CMMVC6138E OPTION is required
the future. To avoid this problem in the future, choose
Explanation: An option is missing. The option might an appropriate name for each object in the cluster.
be listed as optional, but circumstances make the
User response: Choose an appropriate name for each
option mandatory.
object in the cluster.
User response: Supply the option, and resubmit the
command.
CMMVC6145I First use the COMMAND -prepare
command.
CMMVC6139E Incorrect XML tag nesting in
Explanation: This advisory is given prior to
FILENAME
CMMVC6103E when an intermediate file is missing.
Explanation: There is a problem with the content of a
User response: Not applicable.
configuration file. There is a problem parsing the XML
in the file, because the XML records are not consistent.
The file might be corrupt, or the file has been CMMVC6146E Problem parsing OBJECT_TYPE data:
truncated. LINE
User response: Replace this copy with a good copy, Explanation: An unexpected error has occurred.
and resubmit the command. If the problem persists,
User response: Contact the support center.
contact IBM technical support for assistance.

CMMVC6147E TYPE NAME has a name beginning

CMMVC6140E No default name for type TYPE
with PREFIX .
Explanation: An unexpected error has occurred.
Explanation: An object has been encountered that has
User response: Contact IBM technical support for a name beginning with the specified reserved prefix.
assistance. The only valid reason for an object with this kind of
name is that a restoration command did not complete
successfully.
CMMVC6141E The option OPTION does not support
an argument. User response: Ensure that no object uses the reserved
prefix in its name, and resubmit the command.
Explanation: An argument has been supplied for an
option that does not support one.
CMMVC6148E Target cluster has
User response: Remove the argument, and resubmit
NUMBER_OF_EXISTING_OBJECTS
the command.
objects of type TYPE instead of
NUMBER_OF_REQUIRED_OBJECTS .
CMMVC6142E Existing OBJECT_TYPE
Explanation: The target cluster does not have the
OBJECT_NAME has a non-default name.
specified required number of objects of the specified
Explanation: The specified object in the target default type.
cluster has a non-default name. This suggests that the
User response: Correct the problem, and resubmit the
cluster was customized. The cluster is therefore not
command.
suitable for restoration.
User response: Reset the cluster as per the instructions
CMMVC6149E An action is required.
for restoring the cluster configuration, and resubmit the
command. Explanation: An action is required to run the
command.
CMMVC6143E The required configuration file User response: Supply an action, and resubmit the
FILENAME does not exist. command.
Explanation: A file that is critical for successful
operation is missing.
User response: Not applicable.

538 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6150E • CMMVC6186W

User response: Resolve any hardware and

CMMVC6150E The action ACTION is not valid.
configuration problems that you are experiencing on
Explanation: The specified action that you have the 2145 cluster. If the problem persists, contact IBM
entered is not valid. technical support for assistance.
User response: Specify a valid action, and resubmit
the command. CMMVC6165E The target is not the original
configuration node with a WWNN of
WWNN_VALUE .
CMMVC6151E The option OPTION is not valid.
Explanation: A backup configuration can only be
Explanation: The specified option that you have
restored to the original configuration node.
entered is not valid.
User response: Recreate the default cluster with the
User response: Specify a valid option, and resubmit
correct configuration node, and resubmit the command.
the command.

CMMVC6166E The property PROPERTY of the

CMMVC6152E VDisk VDISK_NAME instance
object OBJECT has changed during
number INSTANCE_NUMBER is not
svcconfig restore -execute.
valid.
Explanation: The integrity of the restoration cannot be
Explanation: The volume cannot be restored because
guaranteed.
the instance number, which must be a hexadecimal
number, is not valid. User response: Resubmit the command from svcconfig
restore -prepare.
User response: Contact IBM technical support for
assistance.
CMMVC6181E The target cluster contains an object
that has a counterpart in the
CMMVC6153E OBJECT not consistent with ACTION
configuration to be restored, and has the
Explanation: The specified object is not supported for correct ID.
the specified action.
Explanation: The indicated property has an
User response: Remove the object, and resubmit the unexpected value.
command.
User response: Check that the correct (matching)
backup configuration file (svc.config.backup.xml) is
CMMVC6154E Required OBJECT_TYPE property being provided and if it is, use the -force option to
PROPERTY_NAME has a null value. ignore the discrepancy. Otherwise, provide the correct
file and try again.
Explanation: An unexpected error has occurred.
User response: Contact IBM technical support for CMMVC6182W An object that does not contribute to
assistance. the fabric of the configuration cannot be
restored because its configuration does
CMMVC6155I The command COMMAND processing not permit it to be created.
has completed successfully. Explanation: An object that does not contribute to the
Explanation: Only information and warning messages fabric of the configuration cannot be restored because
are issued. its configuration does not permit it to be created. For
example, a host can only be created if it has at least one
User response: Not applicable. port.
User response: Not applicable.
CMMVC6156W COMMAND processing completed
with errors.
CMMVC6186W The IO group IO_GROUP_NAME
Explanation: Processing was not successful. has been restored with ID ID_VALUE
User response: Not applicable. instead of ID_VALUE .
Explanation: This can occur when the configuration
CMMVC6164E The SVCCONFIG CRON job, which node is different from the node that was used to create
runs overnight on a daily overnight, has the original cluster. This affects the SCSI Inquiry value
failed. for the I/O group.

Explanation: The SVCCONFIG CRON job, which runs User response: Not applicable.
overnight on a daily overnight, has failed.

Chapter 30. Command-line interface messages 539

CMMVC6200E • CMMVC6210E

CMMVC6200E The action failed because of CMMVC6206E The software upgrade failed as a file
incompatible software. containing the software for the specified
MCP version was not found.
Explanation: The software version on one or more
nodes is incompatible with the new version. Explanation: There are two files required to
successfully complete a software upgrade. One file
User response: Refer to the compatibility requirements
contains the files that make up the base operating
for the software version you are adding. Update the
system, and the other file contains the 2145 software.
cluster to meet the compatibility requirements, and
This message appears if the OS version is incompatible
then perform the upgrade.
with the 2145 software.
User response: Upload two compatible files, and
CMMVC6201E The node could not be added because
resubmit the command.
of incompatible software. The status
code is STATUS_CODE .
CMMVC6207E The action failed because the virtual
Explanation: The node could not be added because of
disk (VDisk) is part of a Remote Copy
incompatible software.
mapping.
User response: Upgrade the software on the node that
Explanation: An action was performed against a
has been rejected to the same level of software as the
volume that is part of a Remote Copy mapping.
cluster to which it will be added, and resubmit the
command. User response: Remove the volume from the Remote
Copy mapping before resubmitting the command.
CMMVC6202E The cluster was not modified because
the IP address is not valid. CMMVC6208E The action failed because the virtual
disk (VDisk) is part of a FlashCopy
Explanation: An attempt was made to change the IP
mapping.
address of a cluster to an address that is not valid.
Explanation: An action was performed against a
User response: Correct the address and reissue the
volume that is part of a FlashCopy mapping.
command.
User response: Remove the volume from the
FlashCopy mapping before reissuing the command.
CMMVC6203E The action failed because the
directory that was specified was not one
of the following directories: /dumps, CMMVC6209E The FlashCopy mapping or
/dumps/iostats, /dumps/iotrace, consistency group could not be started
/dumps/feature, /dumps/config, in a reasonable time. The mapping or
/dumps/elogs, /dumps/ec or /dumps/pl. group is instead being prepared.
Explanation: An attempt was made to clear a file Explanation: The FlashCopy mapping or consistency
from, or copy a file to, a directory that is not valid. group could not be started in a reasonable time. The
mapping or group is instead being prepared.
User response: Ensure that the command accesses a
valid directory. User response: Resubmit the command.

CMMVC6204E The action failed as the resulting CMMVC6210E The command has failed because a
disk size would be less than, or equal virtual medium error exists on the
to, zero. image mode VDisk or copy.
Explanation: An attempt was made to shrink a disk, Explanation: When you submit this command, you
however the resulting size would have been less than cannot specify an image mode volume that has a
or equal to zero. virtual medium error on the volume or on any copy of
the volume because the medium errors cannot be
User response: Not applicable
maintained on the ejected MDisk image copy.
User response: If an exact image copy is required,
CMMVC6205E Metadata recovery can not use the
ensure that there is no virtual medium error on the
provided MDisk id - invalid or
image mode volume that you specify or on any of its
destroyed.
copies, and resubmit the command.
Explanation: Metadata recovery cannot use the
If an exact copy is not required, you can use the -force
provided MDisk id, which is not valid or destroyed.
option of the command, but all of the virtual medium
User response: errors will be lost.

540 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6211E • CMMVC6220E

User response: Select a different volume to make up

CMMVC6211E The command failed as a migrate to
the mapping.
image was in progress.
Explanation: An attempt was made to execute a
CMMVC6217E The maximum number of hosts for
command against a volume that was involved in a
the cluster is already configured.
migrate to image operation.
Explanation: You must remove at least one host
User response: Wait for the migration to complete and
definition before you can resubmit the command.
reissue the command.
User response: Determine whether the action is
required.
CMMVC6212E The command failed because data in
the cache has not been committed to If the action is required, review the current
disk. configuration to determine whether any current host
definitions are not required. Remove at least one host
Explanation: The command failed because data in the
definition that is not required, and resubmit the
cache has not been committed to disk.
command.
User response:
CMMVC6218E The maximum number of host/IO
CMMVC6213E You are trying to recover region data group pairs for the cluster is already
that was created by a code level configured.
different from the one you are currently
Explanation: You must remove at least one host I/O
running on the node.
group pair definition before you can resubmit the
Explanation: You are trying to recover region data command.
that was created by a code level different from the one
User response: Determine whether the action is
you are currently running on the node.
required.
User response:
If the action is required, review the current
configuration to determine whether any current host
CMMVC6214E Failed to recreate the cluster you are I/O group pair definitions are not required. Remove at
trying to rebuild. least one host I/O group pair definition that is not
required, and resubmit the command.
Explanation: Failed to recreate the cluster you are
trying to rebuild.
CMMVC6219E The maximum number of WWPNs
User response:
for the cluster is already configured.
Explanation: You must remove at least one WWPN
CMMVC6215E The FlashCopy mapping was not
definition before you can resubmit the command.
created or modified because the
consistency group already contains the User response: Determine whether the action is
maximum number of mappings. required.
Explanation: An attempt was made to create a If the action is required, review the current
FlashCopy mapping in, or move a FlashCopy mapping configuration to determine whether any current
to, a consistency group that has the maximum number WWPN definitions are not required. Remove at least
of FlashCopy mappings that it can contain. one WWPN definition that is not required, and
resubmit the command.
User response: Create or move the FlashCopy
mapping in another consistency group or remove an
existing FlashCopy mapping from the desired group CMMVC6220E The maximum number of hosts for
and then reissue the command. one or more IO groups is already
configured.
CMMVC6216E The Remote Copy relationship was Explanation: You must remove at least one host I/O
not created because the master or group pair definition from the I/O group that you have
auxiliary virtual disk (VDisk) is a specified before you can resubmit the command.
member of a Remote Copy mapping.
User response: Determine whether the action is
Explanation: The Remote Copy relationship was not required.
created because the master or auxiliary volume is a
If the action is required, review the current
member of a Remote Copy mapping.
configuration to determine whether any current host
I/O group pair definitions for the I/O group that you

Chapter 30. Command-line interface messages 541

CMMVC6221E • CMMVC6230E

have specified are not required. Remove at least one

CMMVC6225E An IO group cannot be removed
host I/O group pair definition that is not required from
from a host because of one or more
the I/O group that you have specified, and resubmit
associated VDisks.
the command.
Explanation: An I/O group cannot be removed from a
host because of one or more associated volumes.
CMMVC6221E The maximum number of WWPNs
for one or more IO groups is already User response:
configured.
Explanation: You must remove at least one WWPN CMMVC6226E The action was not completed
definition from the I/O group that you have specified because the cluster has reached the
before you can resubmit the command. maximum number of extents in MDisk
groups.
User response: Determine whether the action is
required. Explanation: The cluster has reached the maximum
number of extents in the storage pool; therefore, the
If the action is required, review the current
action did not complete. You are attempting to use
configuration to determine whether any current
additional extents, for example by creating or
WWPN definitions for the I/O group that you have
expanding a volume. The action cannot be initiated
specified are not required. Remove at least one WWPN
because it would cause the maximum number of
definition that is not required from the I/O group that
extents for a cluster to be exceeded.
you have specified, and resubmit the command.
User response: Free up extents by deleting other
volumes, and resubmit the command.
CMMVC6222E The maximum number of WWPNs
for the host is already configured.
CMMVC6227I The package installed successfully.
Explanation: You must remove at least one WWPN
definition for the host that you have specified before Explanation: The package installed successfully.
you can resubmit the command.
User response: None.
User response: Determine whether the action is
required.
CMMVC6228E The cluster was recovered and the
If the action is required, review the current CLI functionality is limited until the
configuration to determine whether any current cause of the failure is determined and
WWPN definitions for the host that you have specified any corrective action taken. Contact IBM
are not required. Remove at least one WWPN definition technical support for assistance.
that is not required for the host that you have specified,
Explanation: The cluster was recovered and the CLI
and resubmit the command.
functionality is limited.
User response: Contact IBM technical support for
CMMVC6223E The host does not belong to one or
assistance.
more of the IO groups specified or
inferred.
CMMVC6229E The action failed as the SSH key has
Explanation: The host does not belong to one or more
been revoked.
of the I/O groups specified or inferred.
Explanation: The action failed as the SSH key has
User response: Specify a host I/O group combination
been revoked.
that is currently defined, and resubmit the command.
User response:
CMMVC6224E The host already belongs to one or
more of the IO groups specified. CMMVC6230E The action failed as the SSH key
index (SSH_LABEL_ID) is invalid.
Explanation: The host already belongs to one or more
of the I/O groups specified. Explanation: The action failed as the SSH key index
(SSH_LABEL_ID) is not valid.
User response: None.
User response:

542 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6231E • CMMVC6241E

CMMVC6231E The action failed as the audit table is CMMVC6237E The command failed as the remote
full. cluster does not support global mirror.
Explanation: The action failed as the audit table is Explanation: The command failed as the remote
full. cluster does not support global mirror.
User response: Save the audit log to disk, and User response:
resubmit the command.
CMMVC6238E The copy type differs from other
CMMVC6232E This operation cannot be performed copies already in the consistency group.
because the cluster is currently aborting
Explanation: The copy type differs from other copies
the previous software upgrade
already in the consistency group.
command.
User response: Ensure that the copy type of the
Explanation: This operation cannot be performed
mapping that you are attempting to add is the same
because the cluster is currently cancelling the previous
copy type as the mappings in the consistency group to
software upgrade command.
which you are attempting to add the mapping, and
User response: Wait until the previous software resubmit the command.
upgrade command has cancelled successfully, and
resubmit the command.
CMMVC6239E The FlashCopy mapping was not
prepared because the mapping or
CMMVC6233E This operation cannot be performed consistency group is in the stopping
because, either a software upgrade has state. The mapping or consistency group
not been started, or a software upgrade must first complete the stop operation
is in progress but is not in a state where and then be prepared
it can be aborted.
Explanation: You cannot prepare a FlashCopy
Explanation: This operation cannot be performed mapping or consistency group when the FlashCopy
because the software upgrade is making progress. mapping or consistency group is in the stopping state.
If you want to prepare a FlashCopy mapping or
User response:
consistency group, the FlashCopy mapping or
consistency group must be in the Stopped or
CMMVC6234E The upgrade cannot be aborted idle_or_copied state.
because at least one node has already
User response: Wait until the FlashCopy mapping or
committed to a new code level.
consistency group reaches the Stopped or
Explanation: The upgrade cannot be cancelled because idle_or_copied state and then resubmit the command.
at least one node has already committed to a new code
level.
CMMVC6240E The properties of the FlashCopy
User response: mapping were not modified because the
mapping or consistency group is in the
stopping state.
CMMVC6235E An invalid response has been
entered. The command has not been Explanation: You cannot modify the consistency group
executed. Input is case sensitive. Enter of a FlashCopy mapping when the FlashCopy mapping
either yes or no. is in the stopping state. If you want to modify the
consistency group of a FlashCopy mapping, the
Explanation: A response that is not valid has been FlashCopy mapping must be in the Stopped or
entered. The command has not been executed. idle_or_copied state.
User response: Enter either yes or no. User response: Wait until the FlashCopy mapping
reaches the Stopped or idle_or_copied state and then
CMMVC6236E The command has not completed. A resubmit the command.
limited availability parameter has been
entered without the required CMMVC6241E The FlashCopy mapping was not
environment setting being set. deleted because the mapping or
Explanation: The command has not completed. A consistency group is in the stopping
limited availability parameter has been entered without state. The mapping or consistency group
the required environment setting being set. must be stopped first.

User response: Explanation: You cannot delete a FlashCopy mapping

or consistency group when the FlashCopy mapping or

Chapter 30. Command-line interface messages 543

CMMVC6242E • CMMVC6248E

consistency group is in the stopping state. If you want

CMMVC6245E The FlashCopy mapping was not
to delete a FlashCopy mapping or consistency group,
created because the source virtual disk
the FlashCopy mapping or consistency group must be
(VDisk) is already in the maximum
in the Stopped or idle_or_copied state.
number of FlashCopy mappings.
User response: Wait until the FlashCopy mapping or
Explanation: The number of FlashCopy mappings in
consistency group reaches the Stopped or
which a volume can be defined as the source volume is
idle_or_copied state and then resubmit the command.
limited. The source volume that you have specified
cannot be defined to another FlashCopy mapping
CMMVC6242E The FlashCopy mapping or because it is already defined as the source volume to
consistency group was not started the maximum number of FlashCopy mappings.
because the mapping or consistency
User response: You have two options. One option is
group is in the stopping state. The
specify a different source volume and resubmit the
mapping or consistency group must first
command. The other option is delete one of the existing
complete the stop operation and then be
FlashCopy mappings that contains the source volume
prepared.
and resubmit the command.
Explanation: You cannot start a FlashCopy mapping
or consistency group when the FlashCopy mapping or
CMMVC6246E The FlashCopy mapping was not
consistency group is in the stopping state. If you want
created because the target virtual disk
to start a FlashCopy mapping or consistency group, the
(VDisk) is already a source VDisk in a
FlashCopy mapping or consistency group must be in
FlashCopy mapping.
the Prepared state.
Explanation: A volume cannot simultaneously be both
User response: Wait until the FlashCopy mapping or
the source of a FlashCopy mapping and the target of a
consistency group reaches the Stopped or
FlashCopy mapping. The target volume that you have
idle_or_copied state and then prepare the FlashCopy
specified is currently defined as the source of a
mapping or consistency group before starting it.
FlashCopy mapping.
User response: You have two options. One option is
CMMVC6243E The FlashCopy mapping or
specify a different target volume and resubmit the
consistency group was not stopped
command. The other option is delete all of the existing
because the mapping or consistency
FlashCopy mappings that contain the target volume
group is already in the stopping state.
that you have specified and resubmit the command.
Explanation: A Stop FlashCopy mapping or
consistency group task has already been submitted and
CMMVC6247E The FlashCopy mapping was not
is still in progress. When the task has completed
created because the target virtual disk
successfully, the FlashCopy mapping or consistency
(VDisk) is already a target VDisk in a
group state will change to Stopped.
FlashCopy mapping.
User response: None.
Explanation: A volume cannot simultaneously be the
target of more than one FlashCopy mapping. The target
CMMVC6244E The FlashCopy mapping was not volume that you have specified is currently defined as
created because the source virtual disk the target of another FlashCopy mapping.
(VDisk) cannot be the target for a
User response: You have two options. One option is
FlashCopy mapping.
specify a different target volume and resubmit the
Explanation: A volume cannot simultaneously be both command. The other option is delete the existing
the source of a FlashCopy mapping and the target of a FlashCopy mapping that contains the target volume
FlashCopy mapping. The source volume that you have that you have specified and resubmit the command.
specified is currently defined as the target of a
FlashCopy mapping.
CMMVC6248E The command failed because the
User response: You have two options. One option is authorization table is full.
specify a different source volume and resubmit the
Explanation: The command failed because the
command. The other option is delete the existing
authorization table is full.
FlashCopy mapping that defines the source volume
that you have specified as the target volume, and User response:
resubmit the command.

544 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6249E • CMMVC6272E

CMMVC6249E The command failed because the CMMVC6255E The command cannot set the
authorization record was not found or is authorization record to the default role.
already set to the default role. Use rmauth to set the default role.
Explanation: The command failed because the Explanation: The command can not set the
authorization record was not found or is already set to authorization record to the default role.
the default role.
User response: Use rmauth to set the default role.
User response:
CMMVC6263E The command failed because the
CMMVC6250E The command failed because the SSH key already exists or there is a
authorization record is not set to the duplicate SSH key.
default role. Use rmauth to set the
Explanation: You have attempted to add an SSH key
default role.
that already exists, and may have a different
Explanation: The command failed because the authorization level associated with it.
authorization record is not set to the default role.
User response: Add a different SSH key if the existing
User response: Use rmauth to set the default role. SSH key of the same type does not have the authority
level that you require.
CMMVC6251E The command failed because the
specified role was not found. CMMVC6269E Sendmail error EX_USAGE. A
command or configuration line has been
Explanation: The command failed because the
used incorrectly.
specified role was not found.
Explanation: The send email task has failed because a
User response:
command or a configuration line has been used
incorrectly.
CMMVC6252E The command failed authorization
User response: Ensure that the email settings are
because the session SSH key is invalid
correct, and resubmit the task.
or was deleted.
Explanation: The command failed authorization
CMMVC6270E Sendmail error EX_DATAERR.
because the session SSH key is not valid or was
Address is wrong, or the message is too
deleted.
large for the mailbox.
User response:
Explanation: The send email task has failed because
the message sent is too large or a recipient address is
CMMVC6253E The task has failed because the user's incorrect.
role is not authorized to submit the
User response: Ensure that all addresses are correct
command.
and that the message is not too large, and resubmit the
Explanation: One example of a user role restriction is task.
that a user that has a role of Monitor cannot create a
volume.
CMMVC6271E Sendmail error EX_NOINPUT. An
User response: Either log in as a user that has a role input file (not a system file) did not
that is authorized to submit the task or change the role exist or was not readable.
of the user account that you are using to a role that is
Explanation: The send email task has failed because a
authorized to submit the task, and resubmit the task.
file is missing or cannot be read.
User response: Ensure that the email system is
CMMVC6254E The command failed because the
configured correctly. Ensure that access permissions
specified SSH key was not found.
have been specified correctly for all email configuration
NOTE This command must specify an
files, and resubmit the task.
admin key.
Explanation: The command failed because the
CMMVC6272E Sendmail error EX_NOUSER. The
specified SSH key was not found. This command must
sendmail command could not recognize
specify an admin key.
a specified user.
User response:
Explanation: The send email task has failed because
the user and domain combination that you specified
does not exist.

Chapter 30. Command-line interface messages 545

CMMVC6273E • CMMVC6282E

User response: Specify a defined user and domain

CMMVC6278E Sendmail error EX_CANTCREAT. An
combination, and resubmit the task.
output file could not be written to by
sendmail.
CMMVC6273E Sendmail error EX_NOHOST. The
Explanation: The send email task has failed because
sendmail command could not recognize
the system cannot write to a required output file.
the specified host name.
User response: Ensure that the email system is
Explanation: The send email task has failed because
configured correctly. Ensure that access permissions
the host is not known to the email system.
have been specified correctly for all email configuration
User response: Ensure that you have configured the files, and resubmit the task.
SMTP environment correctly. Ensure that you specify a
defined host, and resubmit the task.
CMMVC6279E Sendmail error EX_IOERR. A system
I/O error occurred during a sendmail
CMMVC6274E Sendmail error EX_UNAVAILABLE. operation. This could be due to a disk
A required system resource is not failure.
available.
Explanation: The send email task has failed because a
Explanation: The send email task has failed because a write or read I/O operation has failed. This error might
required system resource is not available. be caused by a disk device failure.

User response: Ensure that you have configured the User response: Correct the root cause of the I/O
SMTP environment correctly, and resubmit the task. failure, and resubmit the task.

CMMVC6275E Sendmail error EX_SOFTWARE. An CMMVC6280E Sendmail error EX_TEMPFAIL. The

internal software error occurred sendmail command could not create a
(including bad arguments). connection to a remote system.

Explanation: The send email task has failed because Explanation: The send email task has failed because
an incorrect parameter or parameter value has been the sendmail application cannot establish a connection
detected. to the remote system.

User response: Ensure that you have configured the User response: Ensure that the network connection to
SMTP environment correctly. Specify only supported the remote system is functioning correctly, and
parameters and parameter values, and resubmit the resubmit the task.
task.
CMMVC6281E Sendmail error EX_PROTOCOL. The
CMMVC6276E Sendmail error EX_OSERR. A system remote system returned something that
resource error prevented the sending of was incorrect during a protocol
an email. exchange.

Explanation: The send email task has failed because a Explanation: The send email task has failed because
system resource error has occurred. an error in the protocol exchange has occurred.

User response: Ensure that you have configured the User response: Ensure that the email system is
SMTP environment correctly, and resubmit the task. configured correctly. Ensure that you have configured
the SMTP environment correctly, and resubmit the task.

CMMVC6277E Sendmail error EX_OSFILE. Failed to

open a critical system file. CMMVC6282E Sendmail error EX_NOPERM. The
user does not have permission to
Explanation: The send email task has failed because a perform the requested operation.
required system file cannot be opened.
Explanation: The send email task has failed because
User response: Ensure that the email system is the User ID does not have authorization to submit the
configured correctly. Ensure that access permissions task.
have been specified correctly for all email configuration
files, and resubmit the task. User response: Ensure that authorizations for your
User ID in the email and SMTP configurations are
correct, and resubmit the task.

546 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6283E • CMMVC6291E

User response: Ensure that you have selected to start

CMMVC6283E Sendmail error EX_CONFIG. There is
the correct FlashCopy mapping or consistency group.
a fatal problem with the sendmail
Ensure that none of the source volumes in the
configuration.
FlashCopy mapping or consistency group that you
Explanation: The send email task has failed because specify are target volumes in another FlashCopy
the sendmail configuration is not correct. mapping that is prepared, preparing, stopped or
stopping with a progress of less than 100%. Resubmit
User response: Ensure that the email system is
the task.
configured correctly. Ensure that you have configured
the SMTP environment correctly, and resubmit the task.
CMMVC6289E The command failed because the
virtual disk (VDisk) is pending
CMMVC6284E An unknown error occurred. Please
synchronization.
ensure your SMTP server is running.
Explanation: This error occurs when at least one of
Explanation: The send email task has failed because
the volume copies is offline.
an unexpected error has occurred.
User response: Fix all of the errors that are associated
User response: Ensure that the SMTP server is
with the volume copies, and resubmit the command.
running, and resubmit the task.

CMMVC6290E The command failed because the

CMMVC6285E The email command timed out.
virtual disk (VDisk) has image mode
Please check your email server settings
copies, is pending synchronization and
as listed on the cluster.
-force has not been specified.
Explanation: The send email task has failed because a
Explanation: This error occurs when at least one of
command timeout has occurred.
the volume copies is offline.
User response: Ensure that your system settings
User response: Perform one of the following actions:
match those recommended in the sendmail application
documentation, and resubmit the task. v Fix all of the errors that are associated with the
volume copies, and resubmit the command.
v Resubmit the command and specify the -force
CMMVC6286E The email service has not been
parameter.
enabled.
Explanation: The send email task has failed because Note: When you specify the -force parameter with the
the email application is not enabled. command that caused this error, the image mode
volume copy is no longer guaranteed to have the
User response: Enable the email application, and
correct volume data.
resubmit the task.

CMMVC6291E The command failed because the

CMMVC6287E The user specified does not exist.
virtual disk (VDisk) is pending
Explanation: You must specify a User ID that exists. synchronization and -force has not been
specified.
User response: Ensure that the User ID that you
specify is defined, and resubmit the task. Explanation: The command failed because the volume
is pending synchronization and -force has not been
specified.
CMMVC6288E The FlashCopy mapping or
consistency group could not be started User response: Perform one of the following actions:
because a source VDisk is the target of v Fix all of the errors that are associated with the
another FC Map that is keeping the volume copies, and resubmit the command.
VDisk inaccessible.
v Resubmit the command and specify the -force
Explanation: You cannot start a FlashCopy mapping parameter.
or consistency group when a source volume in the
FlashCopy mapping or consistency group is the target Note: When you specify the -force parameter with the
volume of another FlashCopy mapping that is holding command that caused this error, the entire volume copy
the volume as inaccessible. The task cannot be initiated is resynchronized.
because a source volume in the FlashCopy mapping or
consistency group that you are attempting to start is
the target of another FlashCopy mapping that is either
prepared, preparing, stopped or stopping with a
progress of less than 100%.

Chapter 30. Command-line interface messages 547

CMMVC6292E • CMMVC6300E

v Ensure that the controller settings are correct and

CMMVC6292E The command failed because a repair
that the MDisk logical unit is correctly configured.
action is in progress for the virtual disk
(VDisk). v Ensure that the MDisk logical unit state is one that
passes the validation. A Read Only or faulty MDisk
Explanation: You cannot submit this command while fails the validation.
a repair action is in progress for the volume.
v Check the Fibre Channel fabric and storage controller
User response: Use the lsrepairvdiskcopyprogress for faults that might reduce the reliability of cluster
command to view the repair progress. Wait for the communication with the MDisk.
volume repair process to complete. If you want the v View the cluster event log for more information
repair process to complete more quickly, increase the about the failed validation.
rate by submitting a chvdisk command. Once the repair
action has completed, resubmit the command that
caused this error. CMMVC6298E The command failed because a target
VDisk has dependent FlashCopy
mappings.
CMMVC6296E One or more managed disks
(MDisks) have failed validation tests. Explanation: The target volume of the FlashCopy
The first failing MDisk ID is MDISK_ID mapping, or the target volume of at least one of the
. FlashCopy mappings in the consistency group, has
other FlashCopy mappings that are dependent on the
Explanation: When you add a managed MDisk to a data on the target volume.
storage pool, the new MDisk is validated to ensure that
adding it to the storage pool will not adversely impact User response: Use the lsvdiskdependentmaps
the storage pool status. Either the current status of the command and specify the target volume to determine
MDisk has not allowed the validation to be performed, which FlashCopy mappings are dependent on the
or the validation has failed. Note: You cannot add Read target volume. Either wait for these mappings to reach
Only or faulty MDisks to a storage pool. the idle_or_copied state, or stop these mappings.
Resubmit the command that produced this error.
User response:
v If the MDisk identity has changed since it was last
CMMVC6299E The create failed because the source
discovered, submit the command-line interface
and target VDisks are members of
command detectmdisk, which might correct the
FlashCopy mappings that have different
problem.
grain sizes.
v Check switch zoning and logical unit presentation on
the controller to ensure that the MDisk is physically Explanation: All FlashCopy mappings that are in a
and logically connected to all of the nodes in this tree of connected mappings must have the same grain
cluster. size. The new FlashCopy mapping that you attempted
to create would have linked two existing trees that
v Ensure that the controller settings are correct and
have different grain sizes.
that the MDisk logical unit is correctly configured.
v Ensure that the MDisk logical unit state is one that User response: You have three options. The first
passes the validation. A Read Only or faulty MDisk option is to resubmit the command and specify a
fails the validation. different source or target volume. The second option is
to delete all of the existing mappings that contain the
v View the cluster event log for more information
source volume and resubmit the command. The third
about the failed validation.
option is to delete all of the existing mappings that
contain the target volume and resubmit the command.
CMMVC6297E One or more managed disks
(MDisks) have timed out during
CMMVC6300E The create failed because the source
validation tests. The first failing MDisk
and target VDisks are members of
ID is MDISK_ID .
FlashCopy mappings that belong to
Explanation: When you add a managed MDisk to a different I/O groups.
storage pool, the new MDisk is validated to ensure that
Explanation: All FlashCopy mappings in a tree of
adding it to the storage pool will not adversely impact
connected mappings must be in the same I/O group.
the storage pool status. The current status of the MDisk
The new FlashCopy mapping that you attempted to
permits the validation to be initiated, but the allotted
create would have linked two existing trees that are in
time for the validation process elapsed before the
different I/O groups.
validation process had completed. Note: You cannot
add Read Only or faulty MDisks to a storage pool. User response: You have three options. The first
option is to resubmit the command and specify a
User response:
different source or target volume. The second option is

548 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6301E • CMMVC6307E

to delete all of the existing mappings that contain the you specified and resubmit the command, or resubmit
source volume and resubmit the command. The third the command and specify an existing volume as the
option is to delete all of the existing mappings that source.
contain the target volume and resubmit the command.
CMMVC6305E The create failed because the target
CMMVC6301E The create failed because the VDisk does not exist.
specified consistency group does not
Explanation: You must specify an existing volume as
exist.
the target of a FlashCopy mapping. The FlashCopy
Explanation: The FlashCopy mapping was not created mapping was not created because the target volume
because the consistency group that you specified does that you specified does not exist.
not exist. You must create a consistency group before
User response: Either create the target volume that
you can place a mapping in that group.
you specified and resubmit the command, or resubmit
User response: Either create the FlashCopy the command and specify an existing volume as the
consistency group that you specified and resubmit the target.
command, or resubmit the command and specify an
existing consistency group.
CMMVC6306E The create failed because the source
VDisk is the member of a FlashCopy
CMMVC6302E The create failed because the mapping whose grain size is different to
resulting tree of FlashCopy mappings that specified.
would exceed the upper limit.
Explanation: All FlashCopy mappings that are in a
Explanation: Either the source volume or the target tree of connected mappings must have the same grain
volume, or both, are already members of other size. The FlashCopy mapping was not created because
FlashCopy mappings. The FlashCopy mapping was not the source volume that you specified is either the
created because the new FlashCopy mapping that you source or the target volume of another FlashCopy
attempted to create would have linked two existing mapping, and the grain size of the other mapping is
mapping trees into a single tree that exceeds the different from the grain size that you specified for the
maximum number of mappings that are supported for mapping that you attempted to create.
a single tree.
User response: You have two options. The first option
User response: You have two options. The first option is to delete all of the FlashCopy mappings that contain
is to resubmit the command and specify a different the source volume that you specified where the grain
source or target volume. The second option is to delete size of the FlashCopy mapping is different from the
a sufficient number of the existing FlashCopy grain size that you specified, and resubmit the
mappings in which either the source or the target command. The second option is to resubmit the
volume is a member so that the combined mapping command and do not specify the grain size attribute.
tree does not exceed the maximum number of
mappings that are supported for a single tree, and
CMMVC6307E The create failed because the target
resubmit the command.
VDisk is the member of a FlashCopy
mapping whose grain size is different to
CMMVC6303E The create failed because the source that specified.
and target VDisks are the same.
Explanation: All FlashCopy mappings that are in a
Explanation: A particular volume cannot be both the tree of connected mappings must have the same grain
source and the target in a FlashCopy mapping. The size. The FlashCopy mapping was not created because
FlashCopy mapping was not created because you have the target volume that you specified is either the source
specified the same volume as both the source and the or the target volume of another FlashCopy mapping,
target. and the grain size of the other mapping is different
from the grain size that you specified for the mapping
User response: Resubmit the command and specify
that you attempted to create.
source and target volumes that are not identical.
User response: You have two options. The first option
is to delete all of the FlashCopy mappings that contain
CMMVC6304E The create failed because the source
the target volume that you specified where the grain
VDisk does not exist.
size of the FlashCopy mapping is different from the
Explanation: You must specify an existing volume as grain size that you specified, and resubmit the
the source of a FlashCopy mapping. The FlashCopy command. The second option is to resubmit the
mapping was not created because the source volume command and do not specify the grain size attribute.
that you specified does not exist.
User response: Either create the source volume that

Chapter 30. Command-line interface messages 549

CMMVC6308E • CMMVC6314E

CMMVC6308E The create failed because the source CMMVC6311E The command failed because the
VDisk is the member of a FlashCopy source VDisk is the target of a
mapping whose IO group is different to FlashCopy mapping that is in the
that specified. specified consistency group.
Explanation: All FlashCopy mappings in a tree of Explanation: A particular volume cannot be both the
connected mappings must be in the same I/O group. source of one FlashCopy mapping and the target of
The FlashCopy mapping was not created because the another FlashCopy mapping in the same consistency
source volume that you specified is the source or target group. The FlashCopy mapping was not created
volume in another FlashCopy mapping and the I/O because the source volume of the FlashCopy mapping
group of the other FlashCopy mapping is different that you attempted to create is already the target
from the I/O group that you specified. volume of a FlashCopy mapping in the consistency
group that you specified.
User response: You have two options. The first option
is to delete all of the FlashCopy mappings that contain User response: Resubmit the command and specify a
the source volume that you specified where the different consistency group.
FlashCopy mapping is in a different I/O group from
the I/O group that you specified, and resubmit the
CMMVC6312E The command failed because the
command. The second option is to resubmit the
target VDisk is the source of a
command and do not specify the I/O group attribute.
FlashCopy mapping that is in the
If you perform the second option, the default value of
specified consistency group.
the I/O group attribute is used.
Explanation: A particular volume cannot be both the
source of one FlashCopy mapping and the target of
CMMVC6309E The create failed because the target
another FlashCopy mapping in the same consistency
VDisk is the member of a FlashCopy
group. The FlashCopy mapping was not created
mapping whose IO group is different to
because the target volume of the FlashCopy mapping
that specified.
that you attempted to create is already the source
Explanation: All FlashCopy mappings in a tree of volume of a FlashCopy mapping in the consistency
connected mappings must be in the same I/O group. group that you specified.
The FlashCopy mapping was not created because the
User response: Resubmit the command and specify a
target volume that you specified is the source or target
different consistency group.
volume in another FlashCopy mapping and the I/O
group of the other FlashCopy mapping is different
from the I/O group that you specified. CMMVC6313E The command failed because the
specified background copy rate is
User response: You have two options. The first option
invalid.
is to delete all of the FlashCopy mappings that contain
the target volume that you specified where the Explanation: The command failed because the
FlashCopy mapping is in a different I/O group from background copy rate that you specified is not a
the I/O group that you specified, and resubmit the supported value.
command. The second option is to resubmit the
command and do not specify the I/O group attribute. User response: Either resubmit the command and
If you perform the second option, the default value of specify a supported value for the background copy
the I/O group attribute is used. rate, or resubmit the command and do not specify the
background copy rate attribute. If you do not specify
the background copy rate attribute, the default
CMMVC6310E The modify failed because the background copy rate value is used.
specified FlashCopy mapping does not
exist.
CMMVC6314E The command failed because the
Explanation: You cannot modify a FlashCopy specified cleaning rate is not valid.
mapping that does not exist. The modify command
failed because the FlashCopy mapping that you Explanation: The command failed because the
specified does not exist. cleaning rate that you specified is not a supported
value.
User response: Resubmit the command and specify an
existing FlashCopy mapping. User response: Either resubmit the command and
specify a supported value for the cleaning rate, or
resubmit the command and do not specify the cleaning
rate attribute. If you do not specify the cleaning rate
attribute, the default cleaning rate value is used.

550 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6315E • CMMVC6326E

A special syntax is available to compress long strings of

CMMVC6315E The command failed because the
zero bits. The use of '::' indicates multiple groups of
specified grain size is not valid.
zeros. The '::' can appear only once in an address. The
Explanation: The command failed because the grain '::' can also be used to compress the leading or trailing
size that you specified is not a supported value. zeros in an address.
User response: Either resubmit the command and v Example: 123.123.123.123
specify a supported value for the grain size, or v Example: 1080:0:0:0:8:800:200C:417A, which can be
resubmit the command and do not specify the grain compressed to 1080::8:800:200C:417A
size attribute. If you do not specify the grain size v Example: 0:0:0:0:0:FFFF:129.144.52.38, which can be
attribute, the default grain size value is used. compressed to ::FFFF:129.144.52.38
v Example: 0:0:0:0:0:0:13.1.68.3, which can be
CMMVC6319E The command has failed because a compressed to ::13.1.68.3
combination of IPv4 and IPv6
User response: Specify a valid IPv6 address, and
parameters were entered.
resubmit the task.
Explanation: The task accepts either IPv4 or IPv6
parameters. You cannot specify a combination of IPv4
CMMVC6324E The command has failed because the
and IPv6 parameters for this task.
IPv6 prefix is not valid.
User response: Specify only IPv4 or only IPv6
Explanation: The value that you entered for an IPv6
parameters, and resubmit the task.
address prefix is not a valid IPv6 address prefix.
User response: Specify a valid IPv6 address prefix,
CMMVC6320E The command has failed because the
and resubmit the task.
IPv4 address is not valid.
Explanation: The valid IPv4 address format is d.d.d.d,
CMMVC6325E The command has failed because the
where d is a decimal value from 0-255.
IPv6 gateway address is not valid.
User response: Specify a valid IPv4 address, and
Explanation: Valid IPv6 address formats are:
resubmit the task.
v x:x:x:x:x:x:x:x
v x:x:x:x:x:x:d.d.d.d
CMMVC6321E The command has failed because the
IPv4 subnet mask is not valid.
where d is a decimal value from 0-255 of an IPv4
Explanation: The valid IPv4 address format is d.d.d.d, address and x is a hexadecimal value of an IPv6
where d is a decimal value from 0-255. address.
User response: Specify a valid IPv4 subnet mask, and
resubmit the task. A special syntax is available to compress long strings of
zero bits. The use of '::' indicates multiple groups of
zeros. The '::' can appear only once in an address. The
CMMVC6322E The command has failed because the '::' can also be used to compress the leading or trailing
IPv4 gateway address is not valid. zeros in an address.
Explanation: The valid IPv4 address format is d.d.d.d, v Example: 123.123.123.123
where d is a decimal value from 0-255. v Example: 1080:0:0:0:8:800:200C:417A, which can be
compressed to 1080::8:800:200C:417A
User response: Specify a valid IPv4 gateway address,
and resubmit the task. v Example: 0:0:0:0:0:FFFF:129.144.52.38, which can be
compressed to ::FFFF:129.144.52.38
v Example: 0:0:0:0:0:0:13.1.68.3, which can be
CMMVC6323E The command has failed because the
compressed to ::13.1.68.3
IPv6 address is not valid.
User response: Specify a valid IPv6 gateway address,
Explanation: Valid IPv6 address formats are:
and resubmit the task.
v x:x:x:x:x:x:x:x
v x:x:x:x:x:x:d.d.d.d
CMMVC6326E The command has failed because the
IPv4 service state address is not valid.
where d is a decimal value from 0-255 of an IPv4
address and x is a hexadecimal value of an IPv6 Explanation: The valid IPv4 address format is d.d.d.d,
address. where d is a decimal value from 0-255.
User response: Specify a valid IPv4 service state
address, and resubmit the task.

Chapter 30. Command-line interface messages 551

CMMVC6327E • CMMVC6331E

CMMVC6327E The command has failed because the CMMVC6329E The command has failed because the
IPv6 service state address is not valid. IP address is not valid.
Explanation: Valid IPv6 address formats are: Explanation: The valid IPv4 address format is d.d.d.d,
v x:x:x:x:x:x:x:x where d is a decimal value from 0-255.
v x:x:x:x:x:x:d.d.d.d Valid IPv6 address formats are:
v x:x:x:x:x:x:x:x
where d is a decimal value from 0-255 of an IPv4
v x:x:x:x:x:x:d.d.d.d
address and x is a hexadecimal value of an IPv6
address.
where d is a decimal value from 0-255 of an IPv4
address and x is a hexadecimal value of an IPv6
A special syntax is available to compress long strings of
address.
zero bits. The use of '::' indicates multiple groups of
zeros. The '::' can appear only once in an address. The
A special syntax is available to compress long strings of
'::' can also be used to compress the leading or trailing
zero bits. The use of '::' indicates multiple groups of
zeros in an address.
zeros. The '::' can appear only once in an address. The
v Example: 123.123.123.123 '::' can also be used to compress the leading or trailing
v Example: 1080:0:0:0:8:800:200C:417A, which can be zeros in an address.
compressed to 1080::8:800:200C:417A v Example: 123.123.123.123
v Example: 0:0:0:0:0:FFFF:129.144.52.38, which can be v Example: 1080:0:0:0:8:800:200C:417A, which can be
compressed to ::FFFF:129.144.52.38 compressed to 1080::8:800:200C:417A
v Example: 0:0:0:0:0:0:13.1.68.3, which can be v Example: 0:0:0:0:0:FFFF:129.144.52.38, which can be
compressed to ::13.1.68.3 compressed to ::FFFF:129.144.52.38
User response: Specify a valid IPv6 service state v Example: 0:0:0:0:0:0:13.1.68.3, which can be
address, and resubmit the task. compressed to ::13.1.68.3
User response: Specify a valid IP address, and
CMMVC6328E The command has failed because the resubmit the task.
console address is not valid.
Explanation: The valid IPv4 address format is d.d.d.d, CMMVC6330E The command has failed because an
where d is a decimal value from 0-255. IPv6 address was specified and the
cluster does not have an IPv6 address.
Valid IPv6 address formats are:
v x:x:x:x:x:x:x:x Explanation: The cluster can only communicate with a
server through an IPv6 address if an IPv6 cluster
v x:x:x:x:x:x:d.d.d.d
management IP address is configured.

where d is a decimal value from 0-255 of an IPv4 User response: Either configure the cluster to have an
address and x is a hexadecimal value of an IPv6 IPv6 cluster management address or specify an IPv4
address. address, and resubmit the task.

A special syntax is available to compress long strings of Note: You do not need to remove the IPv4 address if
zero bits. The use of '::' indicates multiple groups of you configure the cluster to have an IPv6 cluster
zeros. The '::' can appear only once in an address. The management address.
'::' can also be used to compress the leading or trailing
zeros in an address.
CMMVC6331E The command has failed because an
v Example: 123.123.123.123 IPv4 address was specified and the
v Example: 1080:0:0:0:8:800:200C:417A, which can be cluster does not have an IPv4 address.
compressed to 1080::8:800:200C:417A
Explanation: The cluster can only communicate with a
v Example: 0:0:0:0:0:FFFF:129.144.52.38, which can be server through an IPv4 address if an IPv4 cluster
compressed to ::FFFF:129.144.52.38 management IP address is configured.
v Example: 0:0:0:0:0:0:13.1.68.3, which can be
User response: Either configure the cluster to have an
compressed to ::13.1.68.3
IPv4 cluster management address or specify an IPv6
User response: Specify a valid console address, and address, and resubmit the task.
resubmit the task.
Note: You do not need to remove the IPv6 address if
you configure the cluster to have an IPv4 cluster
management address.

552 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6332E • CMMVC6340E

CMMVC6332E The command has failed because an CMMVC6336E The virtual disk (VDisk) copy was
IPv6 email server address was specified not created because the grain size must
and the cluster does not have an IPv6 be 32, 64, 128 or 256.
address.
Explanation: You have supplied an incorrect value for
Explanation: The cluster can only communicate with a the -grainsize parameter when you attempted to create
server through an IPv6 address if an IPv6 cluster a thin-provisioned volume copy.
management IP address is configured.
User response: Specify a supported grain size, and
User response: Either configure the cluster to have an resubmit the command.
IPv6 cluster management address or use an email
server that has an IPv4 address, and resubmit the task.
CMMVC6337E The action failed because the
warning size must be a multiple of 512
Note: You do not need to remove the IPv4 address if
bytes.
you configure the cluster to have an IPv6 cluster
management address. Explanation: You are attempting to create a
thin-provisioned volume copy but you have entered an
incorrect value for the -warning parameter. The value
CMMVC6333E The command has failed because an
can either be a percentage of the volume capacity or an
IPv4 email server address was specified
absolute value that is a multiple of 512 bytes.
and the cluster does not have an IPv4
address. User response: Enter a supported warning value, and
resubmit the command.
Explanation: The cluster can only communicate with a
server through an IPv4 address if an IPv4 cluster
management IP address is configured. CMMVC6338E The action failed because the
warning size can not be larger than the
User response: Either configure the cluster to have an
virtual size.
IPv4 cluster management address or use an email
server that has an IPv6 address, and resubmit the task. Explanation: You are attempting to create a
thin-provisioned volume copy but you have entered an
Note: You do not need to remove the IPv6 address if incorrect value for the -warning parameter. The
you configure the cluster to have an IPv4 cluster warning value cannot be greater than the volume
management address. capacity.
User response: Enter a supported warning value, and
CMMVC6334E The command failed as the email resubmit the command.
port number supplied is invalid.
Explanation: The value that you entered for an email CMMVC6339E The virtual disk (VDisk) copy was
port number is not a valid email port number. not created because the virtual size was
not provided.
User response: Specify a valid email port number, and
resubmit the task. Explanation: You are attempting to create an
image-mode thin-provisioned volume but you did not
set the -size parameter.
CMMVC6335E The command failed as the
combination of parameters provided are User response: Resubmit the command using the -size
either mutually incompatible or would parameter.
leave the cluster without a functioning
protocol stack.
CMMVC6340E The action failed because the value
Explanation: You have submitted a task with a supplied for real size is not a multiple
combination of parameters and parameter values that is of 512 bytes.
not supported or that does not provide the minimum
Explanation: You are attempting to create or resize a
amount of required information.
thin-provisioned volume copy but you have entered an
User response: Ensure that you specify a supported incorrect value for the -rsize parameter. All sizes must
combination of parameters and parameter values, and be integer multiples of 512 bytes.
resubmit the task.
User response: Resubmit the command using a
supported -rsize parameter value.

Chapter 30. Command-line interface messages 553

CMMVC6341E • CMMVC6349E

User response: Delete the volume copy, and resubmit

CMMVC6341E The action failed because the virtual
the import operation using the same MDisk that was
disk (VDisk) copy is not space-efficient
exported from the original cluster.
or compressed.
Explanation: You are attempting to run a command
CMMVC6346E The repair operation cannot start
that is valid only for thin-provisioned or compressed
because the space-efficient virtual disk
volumes.
(VDisk) copy was created using -import
User response: Specify a thin-provisioned or with a real size that is too small.
compressed volume, and resubmit the command.
Explanation: You are attempting to repair a
thin-provisioned volume copy that is reporting corrupt
CMMVC6342E The virtual disk (VDisk) copy was metadata. The cluster cannot repair the volume copy
not shrunk because its real size cannot because although it was recognized as a valid
be less than its used size. thin-provisioned volume when it was imported into
this cluster, the real size allocated to the volume copy is
Explanation: You are attempting to reduce the real
too small. The most probable cause is that the incorrect
size that is allocated to a thin-provisioned volume copy,
value was supplied with -rsize parameter when the
but the command cannot be initiated because it would
volume copy was imported.
make the real size less than the size that is currently
used. User response: Delete the volume copy. Resubmit the
import operation either using a larger value for -rsize,
User response: Determine the used size of the volume
or supplying the -rsize parameter without a value to let
copy, and resubmit the command using a -rsize
the system choose a real size.
parameter value that is greater than or equal to the
used size.
CMMVC6347E The specific upgrade package cannot
be installed on this hardware level.
CMMVC6343E The virtual disk (VDisk) copy was
not shrunk because its real size can not Explanation: The version of software that you are
be negative. attempting to install does not support the hardware
level of the configuration node.
Explanation: You are attempting to reduce the real
size that is allocated to a thin-provisioned volume copy, User response: Check the release notes for the version
but the command cannot be initiated because it would of software that you want to install. Ensure that the
make the real size less than zero. version of software that you install supports the
hardware level of all of the nodes in the cluster, and
User response: Determine the real size of the volume
resubmit the task.
copy, and resubmit the command using a supported
-rsize parameter value.
CMMVC6348E The command failed as there was not
enough information provided to process
CMMVC6344E The repair operation cannot start
successfully.
because the virtual disk (VDisk) copy is
already being repaired. Explanation: You have submitted a task with a
combination of parameters and parameter values that
Explanation: You are attempting to repair a
does not provide the minimum amount of required
thin-provisioned or compressed volume copy, but the
information.
copy is already being repaired.
User response: Ensure that you specify a supported
User response: Specify the correct volume and copy
combination of parameters and parameter values, and
parameters, and resubmit the command.
resubmit the task.

CMMVC6345E The repair operation cannot start

CMMVC6349E The command was not initiated
because the virtual disk (VDisk) copy
because the VDisk cache has been lost
was created using -import but the
and you have not specified the -force
cluster could not recognize its format.
option.
Explanation: You are attempting to repair a
Explanation: You must specify the -force option when
thin-provisioned or compressed volume copy that is
you move a volume from one I/O group to another
reporting corrupt metadata. The cluster cannot repair
and the volume has lost cache data.
the volume copy because it was not recognized as a
valid thin-provisioned or compressed volume when it User response: Resubmit the command and specify
was imported into this cluster. The most probable cause the -force option.
is that the wrong MDisk was used when the volume
copy was imported.

554 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6350E • CMMVC6357E

When the copy is synchronized, resubmit the command

CMMVC6350E The command failed because there is
that caused this error.
insufficient mirror bitmap space.
Explanation: The command failed because there is
CMMVC6355E The command failed because an
insufficient free memory to allocate the bitmap needed
image mode copy is not synchronized
for volume mirroring in the I/O group.
and -force was not specified.
User response: Perform one of the following actions:
Explanation: When you specify an image mode copy
v Submit a chiogrp command to increase the bitmap for this command, the copy must be synchronized
space. unless you also specify the -force parameter.
v Remove volume mirrors from the I/O group.
User response: Perform one of the following actions:
Resubmit the command that caused this error. v Use the lsvdisksyncprogress command to view the
synchronization status. Wait for the copy to
synchronize. If you want the synchronization process
CMMVC6351E The command failed because the to complete more quickly, increase the rate by
virtual disk (VDisk) is not mirrored. submitting a chvdisk command. When the copy is
Explanation: Only mirrored volumes are supported synchronized, resubmit the command that caused
for this command. this error.
v Resubmit the command and specify the -force
User response: Perform one of the following actions: parameter.
v Submit the appropriate command for a volume that
is not mirrored. Note: When you specify the -force parameter with the
v Submit a addvdiskcopy command to add a copy to command that caused this error, the image mode copy
the volume, and resubmit the command that caused is no longer guaranteed to have the correct volume
this error. data.

CMMVC6352E The command failed because the CMMVC6356E The command failed because a copy
number of copies of this virtual disk is not synchronized and -force was not
(VDisk) would exceed the limit. specified.

Explanation: You cannot exceed the limit on the Explanation: When you specify a copy for this
number of copies that are supported for a volume. command, the copy must be synchronized unless you
also specify the -force parameter.
User response: Submit a rmvdiskcopy or
splitvdiskcopy command to decrease the number of User response: Perform one of the following actions:
volume copies, and resubmit the command that caused v Use the lsvdisksyncprogress command to view the
this error. synchronization status. Wait for the copy to
synchronize. If you want the synchronization process
CMMVC6353E The command failed because the to complete more quickly, increase the rate by
copy specified does not exist. submitting a chvdisk command. When the copy is
synchronized, resubmit the command that caused
Explanation: You must specify an existing copy for this error.
this command. v Resubmit the command and specify the -force
User response: Submit an lsvdiskcopy command to parameter.
show all of the available copies for this volume. Select
a copy that exists, and then resubmit the command that Note: When you specify the -force parameter with the
caused this error. command that caused this error, the entire volume copy
is resynchronized.

CMMVC6354E The command failed because a copy

is not synchronized. CMMVC6357E The command failed because the
copy specified is not synchronized and
Explanation: The copy that you specify for this -force was not specified.
command must be a synchronized copy.
Explanation: When you specify a copy for this
User response: Use the lsvdisksyncprogress command, the copy must be synchronized unless you
command to view the synchronization status. Wait for also specify the -force parameter.
the copy to synchronize. If you want the
synchronization process to complete more quickly, User response: Perform one of the following actions:
increase the rate by submitting a chvdisk command. v Use the lsvdisksyncprogress command to view the
synchronization status. Wait for the copy to

Chapter 30. Command-line interface messages 555

CMMVC6358E • CMMVC6368E

synchronize. If you want the synchronization process

CMMVC6365E The command timed out.
to complete more quickly, increase the rate by
submitting a chvdisk command. When the copy is Explanation: The command has not completed in a
synchronized, resubmit the command that caused reasonable amount of time. Processing of the command
this error. required the software to wait for a set of MDisk reads
v Resubmit the command and specify the -force or writes to complete, and the predefined reasonable
parameter. wait time has been exceeded.
User response: Resolve any MDisk or fabric event log
Note: When you specify the -force parameter with the entries, and resubmit the command.
command that caused this error, the created volume is
no longer guaranteed to have identical data to the
original volume when the split is performed. CMMVC6366E One or more nodes in the cluster has
hardware that is not supported by the
new software package.
CMMVC6358E The command failed because the
copy specified is the only synchronized Explanation: The version of software that you are
copy. attempting to install does not support the hardware in
at least one node in the cluster.
Explanation: The command failed because the copy
specified is the only synchronized copy. User response: Check the release notes for the version
of software that you want to install. Upgrade hardware
User response: Use the lsvdisksyncprogress so that all of the hardware in the cluster is supported
command to view the synchronization status. Wait for by the new version of software, and resubmit the task.
another copy to synchronize. If you want the
synchronization process to complete more quickly,
increase the rate by submitting a chvdisk command. CMMVC6367E A remote cluster is running software
When the copy has synchronized, resubmit the that is incompatible with the new
command that caused this error. software package.
Explanation: The version of software that you are
CMMVC6359E The command failed because there attempting to install on the local cluster does not
are insufficient online synchronized support the version of software that is installed on the
copies. remote cluster.

Explanation: This error occurs when at least one of User response: Check the release notes for the version
the volume copies is offline. of software that you want to install. Perform one of the
following actions:
User response: Fix all of the errors that are associated
v Upgrade the software on the remote cluster to a
with the volume copies, and resubmit the command.
version that is supported by the version of software
that you want to install on the local cluster before
CMMVC6363E The command failed because the you upgrade the software on the local cluster.
Logical Block Address (LBA) specified v Delete the cluster partnership to stop all remote copy
is invalid for this virtual disk (VDisk). relationships between the clusters, and resubmit the
Explanation: You must specify a Logical Block task.
Address (LBA) that is a valid address for this volume.
User response: Use the lsvdisk command to obtain CMMVC6368E The new software package might be
the volume size, and resubmit the command that incompatible with the remote cluster.
caused this error using a logical block address that is in Explanation: The software version compatibility
range. between clusters cannot be checked because the remote
cluster is not accessible.
CMMVC6364E The command failed because the User response: Perform one of the following actions:
logical block address (LBA) requested is
v Ensure that the link to the remote cluster is
too large for the disk.
functioning properly, and resubmit the task.
Explanation: You have specified an LBA in v Delete the cluster partnership to stop all remote copy
conjunction with a volume or MDisk, but the LBA is relationships between the clusters, and resubmit the
too large and does not exist on the disk. task.
User response: Check the size of the disk, and
resubmit the command using an LBA that exists on the
disk.

556 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6369W • CMMVC6399E

CMMVC6369W The FlashCopy storage capacity that CMMVC6375W The Remote Copy storage capacity
the cluster is using is approaching the that the cluster is using exceeds the
FlashCopy storage capacity that is Remote Copy storage capacity that is
licensed. licensed.
Explanation: You are being warned that the Explanation: You are being warned that the Remote
FlashCopy storage capacity license might be exceeded Copy storage capacity license has been exceeded.
soon.
User response: Upgrade the Remote Copy storage
User response: Upgrade the FlashCopy storage capacity license to prevent recurrence of this warning
capacity license to prevent recurrence of this warning message.
message.
CMMVC6394E The command failed because an
CMMVC6370W The Remote Copy storage capacity attempt to make the virtual disk cache
that the cluster is using is approaching empty took too long.
the Remote Copy storage capacity that is
Explanation: The failed command must empty the
licensed.
volume cache before attempting the requested action to
Explanation: You are being warned that the Remote ensure that data is preserved. The empty volume cache
Copy storage capacity license might be exceeded soon. subtask has taken too long, and therefore the command
that you have submitted was not initiated so that other
User response: Upgrade the Remote Copy storage
configuration activity can occur.
capacity license to prevent recurrence of this warning
message. The system continues attempting to empty the volume
cache.
CMMVC6372W The virtualized storage capacity that The storage associated with the volume is probably
the cluster is using is approaching the overloaded.
virtualized storage capacity that is
User response: Wait a few minutes to allow the
licensed.
volume cache to empty. Resubmit the command.
Explanation: You are being warned that the
Alternatively, you can use the -force parameter, if the
virtualized storage capacity license might be exceeded
command supports the -force parameter, to bypass the
soon.
empty volume cache subtask. However, specifying the
User response: Upgrade the virtualized storage -force parameter will discard cache data for the
capacity license to prevent recurrence of this warning volume. Only use the -force flag with this command if
message. you do not intend to use the existing contents of the
volume.
CMMVC6373W The virtualized storage capacity that In addition to the above actions, investigate the
the cluster is using exceeds the performance of the network storage devices associated
virtualized storage capacity that is with this volume. The performance of host applications
licensed. using these devices might be degraded.
Explanation: You are being warned that the Remedial action to resolve a performance problem
virtualized storage capacity license has been exceeded. enables host application performance to return to
optimal conditions, and prevents this error message
User response: Upgrade the virtualized storage
from recurring when you resubmit the command that
capacity license to prevent recurrence of this warning
caused this error.
message.

CMMVC6399E The command failed because there is

CMMVC6374W The FlashCopy storage capacity that
not enough memory available for
the cluster is using exceeds the
reservation.
FlashCopy storage capacity that is
licensed. Explanation: At least one node in the cluster cannot
reserve the required amount of memory. This might be
Explanation: You are being warned that the
caused by pinned data in the cache.
FlashCopy storage capacity license has been exceeded.
User response: Check for events in the event log.
User response: Upgrade the FlashCopy storage
Follow the fix procedures to resolve the problem.
capacity license to prevent recurrence of this warning
message.

Chapter 30. Command-line interface messages 557

CMMVC6400E • CMMVC6410E

CMMVC6400E The command failed because a CMMVC6405E The command failed because the
specified managed disk (MDisk) is target copy was not specified.
already in use.
Explanation: A target copy must be specified when
Explanation: You cannot specify an MDisk for this you use migrations on a volume and more than one
command if it is already in a storage pool or is being volume copy exists.
used as an image mode volume.
User response: Specify the target copy, and resubmit
User response: Specify an MDisk that is not being the command.
used as an image mode volume and is not in a storage
pool, and resubmit the command.
CMMVC6406E The command failed because the
specified managed disk group does not
CMMVC6401E The command failed because one or exist.
more of the specified managed disks
Explanation: At least one of the storage pools that you
(MDisks) that you have specified are
have specified in the parameter list does not exist.
not in the required managed disk group.
User response: Ensure that each of the storage pools
Explanation: The command requires that all of the
that you specify exists, and resubmit the command.
MDisks that you specify must be in the same storage
pool.
CMMVC6407E The command failed because the
User response: Ensure that all of the MDisks that you
managed disk group is invalid.
specify are in the same storage pool, and resubmit the
command. Explanation: At least one storage pool ID is above the
maximum value that is available for the system.
CMMVC6402E The command failed because the User response: Ensure that each storage pool ID that
managed disk (MDisk) is not in the you specify in the parameter list exists, and resubmit
required managed disk group. the command.
Explanation: All of the MDisks that you specify must
be in the required storage pool. At least one of the CMMVC6408E The command failed because too few
source MDisks that you have specified in the command managed disk groups were specified.
is not in the required storage pool.
Explanation: You must specify the number of storage
User response: Ensure that all of the MDisks that you pools that is consistent with the other parameters and
specify are in the storage pool that you specify, and parameter values that you specify with the command.
resubmit the command.
User response: Refer to the command documentation
for valid combinations of parameters and parameter
CMMVC6403E The command failed because the values. Use a valid combination of parameters and
target managed disk (MDisk) is not in values, and resubmit the command.
the required managed disk group.
Explanation: All of the MDisks that you specify must CMMVC6409E The command failed because too
be in the required storage pool. At least one of the many managed disk groups were
target MDisks that you have specified in the command specified.
is not in the required storage pool.
Explanation: You must specify the number of storage
User response: Ensure that all of the MDisks that you pools that is consistent with the other parameters and
specify are in the storage pool that you specify, and parameter values that you specify with the command.
resubmit the command.
User response: Refer to the command documentation
for valid combinations of parameters and parameter
CMMVC6404E The command failed because the values. Use a valid combination of parameters and
source and target managed disk groups values, and resubmit the command.
must be different.
Explanation: The source and target storage pools that CMMVC6410E The command failed because too few
you specify for a cross storage pool migration must be managed disks (MDisks) were specified.
different.
Explanation: You must specify the number of MDisks
User response: Ensure that the source and target that is consistent with the other parameters and
storage pools that you specify for a cross storage pool parameter values that you specify with the command.
migration are different, and resubmit the command.
User response: Refer to the command documentation

558 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6411E • CMMVC6423E

for valid combinations of parameters and parameter

CMMVC6416E The command failed because the
values. Use a valid combination of parameters and
managed disk group warning threshold
values, and resubmit the command.
is too high.
Explanation: You must specify a storage pool warning
CMMVC6411E The command failed because too
threshold size that is equal to or less than the size of
many managed disks (MDisks) were
the storage pool when all of the MDisks have been
specified.
added, or you must specify a storage pool warning
Explanation: You must specify the number of MDisks percentage that is equal to or less than the maximum
that is consistent with the other parameters and warning threshold percentage.
parameter values that you specify with the command.
User response: Specify valid values for the storage
User response: Refer to the command documentation pool warning threshold size or percentage, and
for valid combinations of parameters and parameter resubmit the command.
values. Use a valid combination of parameters and
values, and resubmit the command.
CMMVC6417E The command failed because the
managed disk group warning threshold
CMMVC6412E The command failed because the is invalid.
managed disk group extent size is above
Explanation: To specify the warning threshold there
maximum permitted size.
must be at least one managed MDisk in the storage
Explanation: You cannot specify a storage pools extent pool.
size that is larger the maximum size.
User response: Ensure that there is at least one MDisk
User response: Specify a storage pool extent size that defined for the storage pool or remove the warning
is less than or equal to the maximum size, and threshold, and resubmit the command.
resubmit the command.
CMMVC6418E The command failed because the
CMMVC6413E The command failed because the virtual disk (VDisk) is in the process of
managed disk (MDisk) is invalid. being resized.

Explanation: At least one MDisk ID is above the Explanation: When you submit this command, you
maximum value that is available for the system. cannot specify a volume that is being resized.

User response: Ensure that each MDisk ID that you User response: Wait for the resize volume operation to
specify in the parameter list exists, and resubmit the complete. If you still want to submit this command
command. after the operation has completed, resubmit the
command.

CMMVC6414E The command failed because the

managed disk (MDisk) is currently CMMVC6419E The command failed because one or
being migrated. more of the specified managed disks
(MDisks) are in the process of being
Explanation: When you submit this command, you deleted.
cannot specify an MDisk that is being migrated.
Explanation: When you submit this command, you
User response: Either wait until the migration has cannot specify an MDisk that is being deleted with the
completed for the MDisk that you specify, or specify a -force option.
different MDisk, and resubmit the command.
User response: Wait for the delete MDisk operation to
complete. Do not include any MDisks that have been
CMMVC6415E The command failed because the deleted in the list of MDisks that you specify, and
managed disk group warning threshold resubmit the command.
is too low.
Explanation: You must specify a storage pool warning CMMVC6423E The Send Inventory email operation
threshold that is equal to or greater than the minimum failed because email is not started.
size.
Explanation: The send inventory email functionality
User response: Specify a storage pool warning has been enabled but the email service has not been
threshold that is equal to or greater than the minimum started.
size, and resubmit the command.
User response: Disable the send inventory email
functionality or start the email service.

Chapter 30. Command-line interface messages 559

CMMVC6424E • CMMVC6434E

CMMVC6424E The Send Inventory email operation CMMVC6429E The command failed because the
failed because there are no inventory target managed disk (MDisk) is not in
email users. the required managed disk group.
Explanation: The send inventory functionality has Explanation: The task requires that all of the target
been enabled but no email users with the ability to MDisks that you specify must be in the same storage
receive inventory emails have been created. pool.
User response: Either turn off the send inventory User response: Ensure that all of the target MDisks
email functionality or create an email user account that that you specify are in the same storage pool, and
is capable of receiving inventory emails. Refer to the resubmit the task.
documentation for the mke-mailuser command for help
on creating email users.
CMMVC6430E The command failed because the
target and source managed disk groups
CMMVC6425E The action failed because the must be different.
maximum number of objects has been
Explanation: The cross storage pool migration task
reached.
does not support specifying the same storage pool to
Explanation: The action failed because the maximum be both the source and target storage pool.
number of objects has been reached.
User response: Specify a source storage pool and a
User response: Not applicable. target storage pool that are not identical, and resubmit
the task.
CMMVC6426E The command failed because a
specified managed disk (MDisk) is CMMVC6431E The command failed because the
already in use. target copy was not specified.
Explanation: You cannot specify an MDisk that is Explanation: When you use migrations on a volume
already configured as an image mode volume. and there is more than one copy, you must specify
which copy to use as the target copy.
User response: Specify an unmanaged disk, and
resubmit the task. User response: Specify the target copy, and resubmit
the task.
CMMVC6427E The command failed because one or
more of the specified managed disks CMMVC6432E The command failed because the
(MDisks) are not in the required specified managed disk group does not
managed disk group. exist.
Explanation: The create volume task requires that all Explanation: All of the storage pools that you specify
of the MDisks that you specify must be in the same must already exist.
storage pool.
User response: Ensure that all of the storage pools
User response: Ensure that all of the MDisks that you that you specify already exist, and resubmit the task.
specify are in the same storage pool, and resubmit the
task.
CMMVC6433E The command failed because the
managed disk group is invalid.
CMMVC6428E The command failed because the
Explanation: All of the storage pool IDs that you
source managed disk (MDisk) is not in
specify must have a value that is less than or equal to
the required managed disk group.
the maximum supported storage pool ID value.
Explanation: The task requires that all of the source
User response: Ensure that all storage pools have
MDisks that you specify must be in the same storage
supported ID values. Ensure that all of the storage
pool.
pools that you specify already exist, and resubmit the
User response: Ensure that all of the source MDisks task.
that you specify are in the same storage pool, and
resubmit the task.
CMMVC6434E The command failed because too few
managed disk groups were specified.
Explanation: The combination of parameters and
parameter values that you have specified is not
supported. The task requires that you specify more
storage pools than the number that you have specified.

560 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6435E • CMMVC6444E

User response: Specify a supported combination of

CMMVC6440E The command failed because the
parameters and parameter values, and resubmit the
managed disk (MDisk) is currently
task.
being migrated.
Explanation: When you submit this task, you cannot
CMMVC6435E The command failed because too
specify an MDisk that is being migrated.
many managed disk groups were
specified. User response: Ensure that the MDisk that you specify
is not migrating, and resubmit the task. If you want to
Explanation: The combination of parameters and
specify the same MDisk and resubmit the task, ensure
parameter values that you have specified is not
that the migration for that MDisk has completed before
supported. The task requires that you specify fewer
you resubmit the task.
storage pools than the number that you have specified.
User response: Specify a supported combination of
CMMVC6441E The command failed because the
parameters and parameter values, and resubmit the
managed disk group warning threshold
task.
is too low.
Explanation: The value that you have specified for the
CMMVC6436E The command failed because too few
storage pool warning threshold is less than the
managed disks (MDisks) were specified.
minimum supported value.
Explanation: The combination of parameters and
User response: Specify a supported value for the
parameter values that you have specified is not
storage pool warning threshold, and resubmit the task.
supported. The task requires that you specify more
MDisks than the number that you have specified.
CMMVC6442E The command failed because the
User response: Specify a supported combination of
managed disk group warning threshold
parameters and parameter values, and resubmit the
is too high.
task.
Explanation: Either the value for the storage pool
warning percentage is greater than the maximum
CMMVC6437E The command failed because too
supported value, or the storage pool warning disk size
many managed disks (MDisks) were
is greater than the storage pool capacity.
specified.
User response: Specify supported values for storage
Explanation: The combination of parameters and
pool warning percentage and disk size, and resubmit
parameter values that you have specified is not
the task.
supported. The task requires that you specify fewer
MDisks than the number that you have specified.
CMMVC6443E The command failed because the
User response: Specify a supported combination of
managed disk group warning threshold
parameters and parameter values, and resubmit the
is invalid.
task.
Explanation: If you submit this command and specify
a storage pool warning threshold percentage, you must
CMMVC6438E The command failed because the
specify a storage pool that contains at least one MDisk
managed disk group extent size is above
and you must specify a supported value for the storage
maximum permitted size.
pool warning threshold percentage.
Explanation: The storage pool extent size that you
User response: Either do not specify a storage pool
have specified is greater than the supported maximum
warning threshold percentage, or specify a supported
value.
value for the storage pool warning threshold
User response: Specify a supported storage pool percentage and specify a storage pool that contains at
extent size, and resubmit the task. least one MDisk, and resubmit the task.

CMMVC6439E The command failed because the CMMVC6444E The command failed because the
managed disk (MDisk) is invalid. virtual disk (VDisk) is in the process of
being resized.
Explanation: Each MDisk ID must have a value that is
less than or equal to the maximum supported MDisk Explanation: You cannot specify a volume that is
ID value. being resized when you submit this task.

User response: Ensure that all of the MDisks have User response: Wait for the resize volume task to
supported ID values. Ensure that all of the MDisks that complete. You can specify the same volume and
you specify already exist, and resubmit the task. resubmit this task only after the resize volume task that

Chapter 30. Command-line interface messages 561

CMMVC6445E • CMMVC6452W

is in progress has completed. relationships or consistency groups that are configured

in the local cluster and that are associated with the
remote cluster of the partnership.
CMMVC6445E The command failed because one or
more of the specified managed disks User response: Identify all of the Global or Metro
(MDisks) are in the process of being Mirror relationships or consistency groups in the local
deleted. cluster that are configured between this cluster and the
remote cluster of the partnership. Remove all of the
Explanation: You cannot specify an MDisk that is
relationships and groups that you have identified, and
being force deleted.
resubmit the task.
User response: Wait until all force delete MDisk tasks
have completed. Ensure that all of the MDisks that you Note: Do not remove relationships or groups that are
specify still exist, and resubmit the task. associated with a different cluster, and do not remove
relationships or groups that are contained entirely
within the local cluster.
CMMVC6446E The command failed because the
managed disk groups have different
extent sizes. CMMVC6450W A FlashCopy mapping was created
but physical_flash is not enabled.
Explanation: This task requires that the extent size of
the source storage pool and the extent size of the target Explanation: The create FlashCopy mapping task has
storage pool must be identical. succeeded. However, physical_flash should be enabled
when you create a FlashCopy mapping in the physical
User response: If you want to resubmit this command,
disk license scheme.
ensure that the source and target storage pools have the
same extent size. If you want to move a volume to a User response: Ensure that you have the appropriate
storage pool that has a different extent size, you must virtualization license for the cluster configuration that
use the procedure that is documented in the technical you want to enable. Ensure that the license settings for
notes. this cluster match the license.
Delete the FlashCopy mapping or enable
CMMVC6447E The command failed because the physical_flash.
virtual disk (VDisk) is currently being
migrated.
CMMVC6451W A Global Mirror or Metro Mirror
Explanation: You cannot specify a volume that is relationship was created but
being migrated. physical_remote is not enabled.
User response: Either wait until the volume migration Explanation: The create Global Mirror or Metro Mirror
process has completed and resubmit the task, or specify relationship task has succeeded. However,
a volume that is not being migrated and resubmit the physical_remote should be enabled when you create a
task. Global Mirror or Metro Mirror relationship and the
cluster uses the physical disk license scheme.
CMMVC6448E Deleting this node will cause data User response: Ensure that you have the appropriate
loss for resources associated with the virtualization license for the cluster configuration that
I/O group of this node. you want to enable. Ensure that the license settings for
this cluster match the license.
Explanation: This node contains resources which are
vital to the I/O group and unavailable elsewhere. Delete the Global Mirror or Metro Mirror relationship
Removing this node will cause a loss of customer data. or enable physical_remote.
It is recommended that this node not be removed
unless the customer data supported by it is of no CMMVC6452W You are using the physical disk
consequence. license scheme but the values for
physical_flash and physical_remote are
User response: The -force option must be used to
not set.
remove this node.
Explanation: The task has succeeded. However, you
should enable physical_flash before you create a
CMMVC6449E The operation was not performed
FlashCopy mapping and you should enable
because the partnership owns Global or
physical_remote before you create a Global Mirror or
Metro Mirror relationships or
Metro Mirror mapping.
consistency groups.
User response: Enable physical_flash before you create
Explanation: The cluster partnership cannot be
a FlashCopy mapping. Enable physical_remote before
removed while there are Global or Metro Mirror

562 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6453W • CMMVC6460E

you create a Global Mirror or Metro Mirror this cluster match the license. Resubmit the task if it
relationship. supported by the license.

CMMVC6453W You have disabled the physical disk CMMVC6457E One or more quorum disks are on the
license scheme but the capacity license specified controller.
scheme is not set.
Explanation: You cannot disable the setting that
Explanation: The task has succeeded. However, you allows a controller to support a quorum disk while a
should configure a license scheme before you create a quorum disk is configured on the controller.
FlashCopy, Global Mirror or Metro Mirror relationship.
User response: Move all quorum disks from the
You can configure a physical disk license scheme or a
controller to a different storage system using the
capacity license scheme, but not both.
setquorum command, and resubmit this task.
User response: If you do not have a virtualization
feature license that is valid for this cluster, contact your
CMMVC6458E The specified controller cannot
IBM sales representative and obtain a license. Ensure
support quorum disks.
that the license settings for this cluster match the
license that you have for this cluster. Explanation: The controller type of the controller that
you specified does not support quorum disks.
CMMVC6454E The command failed because the User response: Specify a controller that has a
physical disk license scheme is not controller type that supports quorum disks, and
enabled. resubmit the task.
Explanation: You can only enable physical_flash or
physical_remote when the physical disk license scheme CMMVC6459E The mkrcrelationship command
is enabled. failed because the same VDisk was
specified as the master and auxiliary
User response: Ensure that you have the appropriate
VDisk.
virtualization license for the cluster configuration that
you want to enable. Ensure that the license settings for Explanation: A relationship cannot be created from a
this cluster match the license. Resubmit the task if it volume to itself. The mkrcrelationship command
supported by the license. requires that you specify two different volumes for the
master and auxiliary positions. These can be two
volumes in the local cluster, or a volume in each of two
CMMVC6455E The command failed because a
different clusters.
capacity license scheme parameter was
specified but the physical disk license User response: Specify a master volume and an
scheme is enabled. auxiliary volume that are not identical to each other,
and resubmit the task.
Explanation: You cannot enable the capacity license
scheme or specify a capacity license scheme parameter
while the cluster is using the physical disk license CMMVC6460E The command failed because the
scheme. migration source is offline.
User response: Ensure that you have the appropriate Explanation: The source of the migration is offline.
virtualization license for the cluster configuration that The offline source is either an image mode MDisk or
you want to enable. Ensure that the license settings for the entire storage pool.
this cluster match the license. Resubmit the task if it
supported by the license. User response:
v If you submitted the rmmdisk command and
specified a regular MDisk, determine the storage
CMMVC6456E The command failed because a pool to which the source MDisk is defined, and
physical disk license scheme parameter follow the procedure for bringing the storage pool
was specified but the capacity license online. There will be an entry in the event log for the
scheme is enabled. corresponding storage pool.
Explanation: You cannot enable the physical disk v If you submitted the rmmdisk command and
license scheme or specify a physical disk license specified an image mode MDisk, determine the
scheme parameter while the cluster is using the source MDisk and follow the procedure for bringing
capacity license scheme. the image mode MDisk online. There will be an
entry in the event log for the corresponding MDisks.
User response: Ensure that you have the appropriate
virtualization license for the cluster configuration that v If you submitted a command to migrate a copy of an
you want to enable. Ensure that the license settings for image mode volume, determine the corresponding
source MDisk and follow the procedure for

Chapter 30. Command-line interface messages 563

CMMVC6461E • CMMVC6468E

diagnosing problems with MDisks. There will be an target MDisk, the volume would have been taken
entry in the event log for the corresponding MDisks. offline. The task cannot be initiated because this action
v If you submitted any other command to migrate a is not supported.
volume copy, determine the storage pool to which User response: Bring the target MDisk online by
the volume is defined, and follow the procedure for following the recommended procedure for bringing an
bringing the storage pool online. There will be an MDisk online, and resubmit the command.
entry in the event log for the corresponding storage
pool.
CMMVC6464E The Create FlashCopy mapping task
cannot be initiated because the size of
CMMVC6461E The command failed because starting the source VDisk is being changed by a
the migration will result in VDisks previously submitted task.
going offline in the source managed
disk group. Explanation: You cannot submit this task while the
Change volume size task is in progress.
Explanation: A migration from an image mode
volume will use the source storage pool and the source User response: Wait until the Change volume size
storage pool assumes the combined state of the image task completes, and then resubmit the task.
mode MDisk and the storage pool. If the online or
offline states of the image mode MDisk and the storage CMMVC6465E The Create FlashCopy mapping task
pool are different on different nodes, the source volume cannot be initiated because the size of
might go offline or all of the volumes in the source the target VDisk is being changed by a
storage pool might go offline. previously submitted task.
User response: For each node, note the online or Explanation: You cannot submit this task while the
offline states of the source volume and the source Change volume size task is in progress.
storage pool. If one entity is online and the other is
offline, bring online whichever is offline. Taking the User response: Wait until the Change volume size
online entity offline is not recommended because other task completes, and then resubmit the task.
volumes might go offline.
CMMVC6466E The Create FlashCopy mapping task
CMMVC6462E The command failed because starting cannot be initiated because an identical
the migration will result in VDisks map already exists.
going offline because the target
Explanation: A map between the source and target
managed disk group is offline.
volumes that you have specified is defined. You cannot
Explanation: The migration process assigns the define a map that is exactly the same as a map that is
volume an online or offline state based on the states of already defined.
the source and target storage pools. In this case, based
User response: Specify a unique map when you
on the offline state of the target storage pool the
submit this task.
volume that is currently online would have been taken
offline. The command cannot be initiated because this
action is not supported. There will be an entry in the CMMVC6467E The Create FlashCopy mapping task
event log for the corresponding storage pool. cannot be initiated because a FlashCopy
map with the same target VDisk already
User response: For each node, note the online or
exists in the consistency group.
offline state of the source and target storage pools. For
each node, if one of these two storage pools is online Explanation: You cannot create more than one
and the other is offline, bring online whichever storage FlashCopy map with the same target volume in the
pool is offline. Taking the online storage pool offline is same consistency group.
not recommended because other volumes might go
User response: Specify a target volume for the
offline.
FlashCopy map that is unique to the consistency group
when you submit this task.
CMMVC6463E The command failed because Starting
the migration will result in VDisks
CMMVC6468E The Start or Prepare FlashCopy
going offline because a target MDisk is
mapping task cannot be initiated
offline.
because the target volume is the source
Explanation: The volume is currently online. The of a different FlashCopy map that is
migration process assigns the volume an online or being restored.
offline state based on the states of the source and target
Explanation: You cannot start or prepare a map while
MDisks. In this case, based on the offline state of the
the target of the map is the source volume of another

564 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6469E • CMMVC6474E

FlashCopy mapping that is being restored.

CMMVC6472E The Create cluster partnership task
User response: Ensure that the target volume in the cannot be initiated because the remote
map that you are attempting to start or prepare is not cluster with which you are attempting to
the source volume of another FlashCopy mapping that create a partnership has a downlevel
is being restored when you submit the task. You could software version that does not support
stop the associated map that is being restored, or you this configuration.
could wait for the map that is being restored to reach
Explanation: The software versions of the clusters in
the Idle_or_Copied state.
the existing partnership do not support a partnership
with a cluster that has the software version of the
CMMVC6469E The Split stop FlashCopy map task remote cluster with which you are attempting to create
cannot be initiated because the mapping a partnership. If a cluster at version 5.1.0 or later is
is either being restored or is not in the already in a partnership with another cluster at version
copy complete state. 5.1.0 or later, you can only add a partnership to a
cluster at version 5.1.0 or later, and cannot add a
Explanation: You cannot split stop a FlashCopy map partnership to a cluster at version 4.3.1 or earlier. If a
while it is being restored or is not in the copy complete cluster at version 5.1.0 or later is already in a
state. partnership with another cluster at version 4.3.1 or
User response: Ensure that the map is not being earlier, you cannot add another partnership while the
restored and is in the copy complete state when you partnership with the cluster at version 4.3.1 exists. If a
submit this task. cluster is not in a partnership, you can create a
partnership between it and a cluster at any version.
One scenario in which this error occurs is when you
CMMVC6470E The Start or Prepare FlashCopy attempt to add a partnership with a remote cluster at
mapping task cannot be initiated version 4.3.1 or earlier to a cluster at software version
because the target VDisk is being used 5.1.0 or later that is already in partnership with another
by a different FlashCopy map. cluster at software version 5.1.0 or later.
Explanation: You cannot start or prepare a map while User response: Either upgrade the downlevel cluster
the target of the map is also the target volume of software version to a version that supports this task or
another map that is in one of the following states: remove all existing partnerships from the cluster to
copying, stopping, suspended, prepared or preparing. which you want to partner the cluster that has the
User response: Ensure that the target volume in the downlevel software version, and resubmit the task.
map that you are attempting to start or prepare is not
the target volume of another FlashCopy mapping that CMMVC6473E The partnership task cannot be
is in one of the unsupported states when you submit initiated because the supported
this task. maximum number of accessible remote
clusters would be exceeded.
CMMVC6471E The Create cluster partnership task Explanation: With multiple cluster mirroring, you can
cannot be initiated because a cluster in build a configuration of a chain of clusters. There is a
the existing partnership has a downlevel limit to the number of clusters that you can configure
software version that does not support in the chain. The task would have resulted in exceeding
this configuration. the supported maximum number of clusters in a chain.
Explanation: One scenario in which this error occurs User response: Ensure that the resulting configuration
is when a cluster at version 5.1.0 or later is partnered to is supported when you submit this task.
a cluster at version 4.3.1 or earlier and you attempt to
create another partnership to a cluster at version 5.1.0
to implement multiple cluster mirroring. Software CMMVC6474E The Create partnership task cannot
version 4.3.1 does not support multiple cluster be initiated because there is a Global
mirroring, so adding a partnership to a third cluster is Mirror or Metro Mirror relationship or
not supported while at least one cluster in the current consistency group that has a deleted
partnership is at version 4.3.1 or earlier. partnership.

User response: Either upgrade the downlevel cluster Explanation: You must resolve the unpartnered objects
software version to a version that supports this task or error that is related to the deleted partnership with a
remove the partnership to the cluster that has the Global Mirror or Metro Mirror relationship or
downlevel software version, and resubmit the task. consistency group before you can create a partnership
from the local cluster to more than one other cluster.
User response: Resolve the unpartnered objects error,
and resubmit the task. To resolve the error, either delete

Chapter 30. Command-line interface messages 565

CMMVC6475E • CMMVC6485E

the unpartnered Global Mirror or Metro Mirror

CMMVC6480E The task cannot be initiated because
relationship or consistency group from the deleted
the user group that you have specified
partnership, or create a partnership for the unpartnered
is not defined.
objects.
Explanation: You must specify a user group that exists
in the user group table.
CMMVC6475E The Add relationship to group task
cannot be initiated because the master User response: Either create the user group that you
cluster of the relationship that you are had specified or specify an existing user group, and
attempting to add to the group is the resubmit the task.
auxiliary cluster of the group, and the
auxiliary cluster of the relationship that
CMMVC6481E The Modify user group task cannot
you are attempting to add to the group
be initiated because you have specified
is the master cluster of the group.
a default user group.
Explanation: All of the relationships within a group
Explanation: Examples of default user groups are
must have the same master cluster as the group and
SecurityAdmin, Administrator, CopyOperator, Service,
must have the same auxiliary cluster as the group. The
and Monitor.
determination as to which cluster is assigned as the
master cluster when you create a relationship or User response: Specify a user group that is not a
consistency group is based on the cluster from which default user group when you submit this task.
you submit the task.
User response: Perform one of the following three CMMVC6482E The Delete user group task cannot be
options: initiated because you have specified a
v Delete the group and create the group so that the default user group.
master cluster of the group is identical to the master Explanation: Examples of default user groups are
cluster of the relationship and the auxiliary cluster of SecurityAdmin, Administrator, CopyOperator, Service,
the group is identical to the auxiliary cluster of the and Monitor.
relationship.
v Delete the relationship and create the relationship so User response: Specify a user group that is not a
that the master cluster of the relationship is identical default user group when you submit this task.
to the master cluster of the group and the auxiliary
cluster of the relationship is identical to the auxiliary CMMVC6483E The task cannot be initiated because
cluster of the group. the user group name that you have
v Specify a group and a relationship that have identical specified already exists.
master clusters and identical auxiliary clusters.
Explanation: Each user group must have a unique
name.
Resubmit the task.
User response: If you want to define a new user
group with the name that you had specified, you must
CMMVC6478E The Enable remote authentication first delete the existing user group that has that same
service task cannot be initiated because name. Specify a user group name that does not exist
the server settings are not configured. when you submit this task.
Explanation: You cannot enable the remote
authentication service until the server has been CMMVC6484E The task cannot be initiated because
configured with all of the required settings. You must the role that you have specified is not
specify the user name, password, and remote supported.
authentication server URL, and if required, the SSL
certificate. Explanation: Examples of valid roles are
SecurityAdmin, Administrator, CopyOperator, Service,
User response: Ensure that the server settings are and Monitor.
configured correctly, and resubmit the task.
User response: Specify a supported role, and resubmit
the task.
CMMVC6479E The task cannot be initiated because
the user group table is full.
CMMVC6485E The Delete user group task has failed
Explanation: The maximum supported number of user because there is at least one user that is
groups is already configured in the user group table. defined as a member of the group, and
User response: Delete a user group that is not you did not specify the -force parameter.
required from the table, and resubmit the task. Explanation: You cannot delete a user group that is

566 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6486E • CMMVC6496E

not empty unless you specify the -force parameter. If the use of the remote authentication service, but not
you use the -force parameter when you delete a user both, and resubmit the task.
group, all of the users that were in the deleted user
group are added to the Monitor user group.
CMMVC6491E The task cannot be initiated because
User response: Ensure that you specify the correct an SSH key and password were not
user group. For each member of the specified user specified for the remote authentication
group that you want to belong to a user group other service.
than Monitor, move that member to the desired group.
Explanation: An SSH key and password are required
If the user group has at least one member, specify the
for the remote authentication service.
-force parameter when you submit the task.
User response: Specify a valid SSH key and password
when issuing this task.
CMMVC6486E The task cannot be initiated because
the user table is full.
CMMVC6492E The task cannot be initiated because
Explanation: The maximum supported number of
you have specified a local user but you
users is already configured in the user table.
have not specified a user group.
User response: Delete a user that is not required from
Explanation: You must specify a user group when you
the table, and resubmit the task.
specify a local user for this task.
User response: Specify a valid user group if you
CMMVC6487E The task cannot be initiated because
specify a local user when you submit this task.
the user name that you have specified
already exists.
CMMVC6493E The task cannot be initiated because
Explanation: Each user must have a unique name.
the user that you have specified is not
User response: If you want to define a new user with defined.
the name that you had specified, you must first delete
Explanation: You must specify a user that exists in the
the existing user that has that same name. Specify a
user table.
user name that does not exist when you submit this
task. User response: Either create the user that you had
specified or specify an existing user, and resubmit the
task.
CMMVC6488E The task cannot be initiated because
you have specified a user group ID that
is not correct. CMMVC6494E The task cannot be initiated because
you cannot remove a default user.
Explanation: You must specify a valid user group ID
when you submit this task. Explanation: Examples of default users are
SecurityAdmin, Administrator, CopyOperator, Service,
User response: Specify a valid user group ID, and
and Monitor.
resubmit the task.
User response: Specify a user that is not a default user
when you submit this task.
CMMVC6489E The task cannot be initiated because
you have specified more than one
password. CMMVC6495E The task cannot be initiated because
the user superuser must be a local user.
Explanation: This task allows you to specify only one
password. Explanation: You cannot define the user superuser to
use the remote authentication service.
User response: Specify only one password, and
resubmit the task. User response: Ensure that you have specified the
correct user, and resubmit the task.
CMMVC6490E The task cannot be initiated because
you have specified both a user group CMMVC6496E The task cannot be initiated because
and the use of the remote authentication you cannot remove the superuser
service. password.
Explanation: You cannot specify a user group when Explanation: The user superuser must always have a
you specify the use of the remote authentication password defined.
service.
User response: Ensure that you have specified the
User response: Either specify a user group or specify correct user when you submit the task.

Chapter 30. Command-line interface messages 567

CMMVC6497E • CMMVC6506E

CMMVC6497E The task cannot be initiated because CMMVC6503E The FlashCopy mapping or
the user that you have specified does consistency group was not stopped
not have a password defined. because stopping consistency group 0 is
not a valid operation.
Explanation: You cannot remove a password that does
not exist. Explanation: The FlashCopy mapping or consistency
group was not stopped because stopping consistency
User response: Ensure that you have specified the
group 0 is not a valid operation.
correct user when you submit the task.
User response:
CMMVC6498E The task cannot be initiated because
the user that you have specified does CMMVC6504E The task cannot be initiated because
not have an SSH key defined. the SSH key file that you have specified
does not contain a valid SSH key.
Explanation: You cannot remove an SSH key that does
not exist. Explanation: You must specify an SSH key file that
contains a valid SSH key.
User response: Ensure that you have specified the
correct user when you submit the task. User response: Specify an SSH key file that contains a
valid SSH key, and resubmit the task.
CMMVC6499E The task has failed because the SSH
key that you have specified is already CMMVC6505E The task has failed because an error
defined for another user. has occurred while communicating with
the authentication service.
Explanation: A single SSH key cannot be defined for
more than one user. Explanation: The cluster is configured to use an
authentication service to control which users are
User response: Either specify a unique SSH key for
authorized to access the cluster. An error has occurred
the user that you had specified or delete the user that
while the cluster was attempting to contact the
has the SSH key that you had specified, and resubmit
authentication service. The error is probably the result
the task.
of an incorrect configuration, either of the cluster or of
the authentication service. This error occurs if the SSL
CMMVC6500E The action failed because the source certificate, user name or password is incorrect.
and destination virtual disks (VDisks)
User response: Ensure that the authentication service
are the same.
is functioning properly. Ensure that the cluster
Explanation: The action failed because the source and authentication service configuration is correct. Resubmit
destination volumes are the same. the task.

User response:
CMMVC6506E The task has failed because a timeout
has occurred while communicating with
CMMVC6501E The action failed because the node the authentication service.
hardware is incompatible with the
current I/O group member. Explanation: The cluster is configured to use an
authentication service to control which users are
Explanation: The action failed because the node authorized to access the cluster. A timeout has occurred
hardware is incompatible with the current I/O group while the cluster was attempting to contact the
member. authentication service. This timeout is probably the
User response: result of a TCP/IP network problem or of an incorrect
configuration. Configuring the incorrect IP address or
protocol in the authentication service URL causes this
CMMVC6502E The FlashCopy mapping was not error. The protocol can be either http or https.
prepared because preparing consistency
group 0 is not a valid operation. User response: Ensure that the cluster authentication
service configuration is correct. Ensure that the
Explanation: The FlashCopy mapping was not Ethernet network between the cluster and the
prepared because preparing consistency group 0 is not authentication service is functioning properly. Ensure
a valid operation. that the authentication service is functioning properly.
User response: Resubmit the task.

568 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6507E • CMMVC6513E

authentication, configure the cluster to use that

CMMVC6507E The task has failed because the
authentication service.
authentication service reports an
incorrect user name or password. Resubmit the task.
Explanation: The cluster is configured to use an
authentication service to control which users are CMMVC6510E The task has failed because the
authorized to access the cluster. password is not correct for the user
name that you are using.
If the password for the user name has recently been
changed on the authentication service, you might be Explanation: The password that you are using does
required to force the cluster to refresh its authentication not match the password that is configured on the
cache. You can force the refresh using the cluster cluster for the user name that you are using.
console View Cluster Properties, Remote Authentication
panel or by submitting the Command-Line Interface User response: Enter the correct password, and
command chauthservice -refresh. resubmit the task.

User response: Ensure that the user name and

password that you use is correct. CMMVC6511E The task has failed because the
cluster is not configured correctly to use
If the password for the user name has recently been the authentication service.
changed on the authentication service, force the cluster
to refresh its authentication cache. Explanation: The user name that you are using is
configured to be authenticated using an authentication
If the user name that you are using also has a service, but either the cluster is not configured to use
password configured on the cluster, ensure that the an authentication service or the function is not enabled.
password that is configured on the cluster is identical
to the password that is configured for that user name User response: If you want to use an authentication
on the authentication service. service, configure the cluster to use the service.

Resubmit the task. If you do not want to use an authentication service,

modify the configuration of the user name on the
cluster to remove the designation for the use of the
CMMVC6508E The task has failed because the authentication service.
authentication service reports that the
authentication token has expired. Resubmit the task.

Explanation: The cluster is configured to use an

authentication service to control which users are CMMVC6512E The task has failed because you
authorized to access the cluster. The authentication cannot both create a new quorum disk
token, which is saved as a browser cookie, has expired. and set that new disk to active using the
You can modify the token expiration property that is same command.
set by the authentication service to reduce the Explanation: The create new quorum disk task and set
frequency of this error in the future. disk to active task must be done using two separate
User response: Either acquire a new authentication tasks.
token or log in with a user name and password, and User response: Submit a create new quorum disk task.
resubmit the task. When that task has completed, submit a task to activate
the new disk.
CMMVC6509E The task has failed because the user
name is not configured on the cluster. CMMVC6513E The task has failed because you
Explanation: If the user name is defined on an cannot activate a quorum disk until all
authentication service and you want to use that service of the quorum disks have been
for cluster authentication, you must configure the initialized.
cluster to use that authentication service. Explanation: The initialization process for at least one
User response: Ensure that you are using the correct disk has not yet completed. You cannot select a disk as
user name. the active disk until the initialize process for all of the
quorum disks has completed.
If the user name is not configured on the cluster and
you want to use the cluster to authenticate, create a User response: Wait until the initialize quorum disk
new user with the user name that you want to use on process has completed for all of the quorum disks, and
the cluster. resubmit the task.

If the user name is defined on an authentication service

and you want to use that service for cluster

Chapter 30. Command-line interface messages 569

CMMVC6514E • CMMVC6520E

use the service, you will also have to continue to

CMMVC6514E The task has failed because the disk
specify an IPv6 cluster address even if you do not
that you have selected to activate is not
intend to manage your cluster through this address.
online.
Otherwise, re-configure the cluster so that all remote
Explanation: A disk must be online to be eligible for
services use only IPv4 addresses, and resubmit the task
activation.
to remove the IPv6 cluster address.
User response: Either bring the disk that you have
selected online or select a different disk that is already
CMMVC6518E The task has failed because no roles
online, and resubmit the task.
are defined for the current user on the
cluster.
CMMVC6515E The task has failed because at least
Explanation: The cluster has been configured to use
one quorum disk is in the Excluded
an authentication service to control which users are
state.
authorized to access the cluster. The user's credentials
Explanation: You cannot activate a quorum disk when were accepted by the authentication service, but none
one or more of the quorum disks are in the Excluded of the groups defined for the user on the authentication
state. service match any of the user groups that are defined
on the cluster.
User response: Either create additional quorum disks
or change the configuration so that none of the quorum User response: Perform the following steps in
disks is in the Excluded state. Ensure that none of the sequence:
quorum disks are in the Excluded state, and resubmit 1. Determine which user groups are defined for the
the task. user on the authentication service.
2. Ensure that at least one user group that is defined
CMMVC6516E The command has failed because an for the user on the authentication service is also
IPv4 cluster address cannot be removed defined on the cluster.
while remote IPv4 services are 3. Ensure that at least one user group that is defined
configured. for the user on both the authentication service and
Explanation: The configured management IP address the cluster has its 'remote' parameter set to
protocols determine whether IPv4 or IPv6 or both are 'enabled'.
enabled on the cluster. If a cluster does not have an 4. Resubmit the task.
IPv4 cluster address the IPv4 protocol stack will not be
enabled, and therefore remote services such as email
CMMVC6519E The task has failed because you
servers or SNMP servers cannot be accessed through an
cannot change the user group of the
IPv4 address.
'superuser' account to anything other
User response: If you can only access the service than 'SecurityAdmin'.
through an IPv4 address and you need to continue to
Explanation: The user group that is assigned to the
use the service, you will also have to continue to
user name 'superuser' must always be 'SecurityAdmin'.
specify an IPv4 cluster address even if you do not
This assignment cannot be changed.
intend to manage your cluster through this address.
User response: Ensure that you specify a user account
Otherwise, re-configure the cluster so that all remote
other than 'superuser' if you submit a task to change
services use only IPv6 addresses, and resubmit the task
the user group of a user account from 'SecurityAdmin'
to remove the IPv4 cluster address.
to a different user group.

CMMVC6517E The command has failed because an

CMMVC6520E You cannot use this task to modify
IPv6 cluster address cannot be removed
the properties of the current user
while remote IPv6 services are
because those properties are only
configured.
defined by an authentication service.
Explanation: The configured management IP address
Explanation: The current user is not defined on the
protocols determine whether IPv4 or IPv6 or both are
cluster. The current user is defined on an authentication
enabled on the cluster. If a cluster does not have an
service, and the cluster is configured to use that
IPv6 cluster address the IPv6 protocol stack will not be
authentication service. You must use the authentication
enabled, and therefore remote services such as email
service to change the current user's password.
servers or SNMP servers cannot be accessed through an
IPv6 address. If you want to enable command-line interface (CLI)
access to the cluster by using an SSH key, you must
User response: If you can only access the service
define the current user on the cluster and associate the
through an IPv6 address and you need to continue to
SSH key with that user. If you also want to continue

570 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6521E • CMMVC6528E

using the authentication service for the current user, it does not contain any of the unsupported characters
you must enable the 'remote' setting for the new listed above, and resubmit the task.
current user account that you create on the cluster.
User response: If you want to change your password, CMMVC6525E The password that you have entered
use the authentication service for that task. is not valid. The password cannot begin
or end with a space character.
If you want to enable command-line interface (CLI)
access to the cluster by using an SSH key, define your Explanation: A space cannot be the first or last
user account on the cluster and associate the ssh key character in the password that you enter.
with that definition. If you also want to continue using
User response: Ensure that the password that you
the authentication service to authorize your user
enter does not begin or end with the space character,
account, enable the 'remote' setting for your newly
and resubmit the task.
created user account on the cluster.

CMMVC6526E The Create VDisk task cannot be

CMMVC6521E The task cannot be initiated because
initiated because the number of copies
it would have resulted in a user account
that you have requested is not equal to
definition for a local user that specifies
the number of unique MDisk groups
neither a password nor an SSH key.
that you have specified.
Explanation: The definition of a local user must
Explanation: When you submit this task, you must
always specify either a password or an SSH key.
specify a unique storage pool for each volume copy
User response: When you submit this task, ensure that you request.
that you have specified the correct user account and
User response: Specify the same number of unique
parameters, and that all local user definitions would
storage pools as the number of volume copies that you
still specify either a password or an SSH key after the
request, and resubmit the task.
task completes.

CMMVC6527E The name that you have entered is

CMMVC6522E Authorization has failed.
not valid. The name can contain letters,
Explanation: An SSH login attempt has failed. This numbers, spaces, periods, dashes, and
message will be followed by a second message that will underscores. The name must begin with
contain detailed information about the cause of the a letter or an underscore. The name
error. must not begin or end with a space.
User response: Follow the instructions in the second Explanation: A number or space cannot be the first
error message to solve the problem. character and a space cannot be the last character in the
name that you enter. Also, the following characters are
not supported anywhere in the name: * : , “” ' % #
CMMVC6523E The URL that you have entered is not
valid. User response: Ensure that the name you enter does
not begin with a number, does not begin or end with a
Explanation: The URL must start with either http://
space character, and does not contain any of the
or https:// and must use only the following characters:
unsupported characters listed above, and resubmit the
A-Z, a-z, 0-9, - _ : [ ] . ~ / %.
task.
User response: Ensure that the URL that you enter
starts with one of the supported strings and contains
CMMVC6528E The command cannot be initiated
only supported characters, and resubmit the task.
because the MDisk mode is not set to
Array.
CMMVC6524E The name that you have entered is
Explanation: Any MDisk that you specify for this
not valid. The name cannot begin or
command must be a local MDisk that is an array of
end with a space character, and the
LDisks. The mode of the MDisk that you have specified
name cannot contain any of the
is not Array.
following characters: * : , \' %
User response: Either select a different MDisk that is a
Explanation: A space cannot be the first or last
local MDisk and is an array of LDisks, or configure the
character in the name that you enter. Also, the
system so that the MDisk that you have specified is a
following characters are not supported anywhere in the
local MDisk and is an array of LDisks, and resubmit
name: * : , \“”' %
the command.
User response: Ensure that the name that you enter
does not begin or end with the space character and that

Chapter 30. Command-line interface messages 571

CMMVC6529E • CMMVC6537E

CMMVC6529E The command cannot be initiated CMMVC6534E The command cannot be initiated
because the maximum supported because the drive that you have
number of MDisks already exists. specified does not exist.
Explanation: This command requires that an MDisk is Explanation: You have specified a drive ID that is not
available for array creation. There are no available defined.
MDisks for array creation because the maximum
User response: Use the lsdrive command to display
number of MDisks is already configured on the cluster.
existing drive IDs. Specify only existing drive IDs, and
User response: Ensure that a local MDisk is available, resubmit the command.
and resubmit the command. To make a local MDisk
available for this task, either delete an array on an
CMMVC6535E The command cannot be initiated
existing local MDisk or remove a SAN attached MDisk
because you have specified an
and configure a local MDisk.
insufficient number of drives to
configure an array using the RAID
CMMVC6530E The command cannot be initiated geometry that you have specified.
because the maximum supported
Explanation: Each RAID geometry requires a
number of arrays already exists.
minimum number of available drives in order to
Explanation: The cluster already has the maximum configure an array using that geometry. For example, a
number of arrays that it can support. The command RAID 6 geometry requires that you specify at least four
attempted to add a new array. available drives. The number of drives that you have
specified is less than the minimum number of drives
User response: Remove an array that is no longer
that are required for the RAID geometry that you have
needed, and resubmit the command.
specified.
User response: Ensure that you specify a sufficient
CMMVC6532E The command cannot be initiated
number of drives to accommodate the RAID geometry
because there is insufficient free
that you specify, and resubmit the command. You
memory that is available to the I/O
might want to specify a different number of drives or a
group.
different RAID geometry.
Explanation: This command requires that there is
sufficient free memory available for the specified I/O
CMMVC6536E The command cannot be initiated
group to allocate the memory that is required for the
because you have specified more drives
new array.
than the specified RAID geometry
User response: Ensure that there is sufficient memory permits.
available to the I/O group, and resubmit the command.
Explanation: The number of drives that you specify
You can increase the amount of memory that is
must be within the supported range of number of
allocated to the I/O group. You can also reduce the
drives that is supported for the RAID geometry that
amount of memory that is used by reducing the
you specify. For example, a RAID 1 geometry requires
number volume mirrors or Copy Services relationships
that you specify exactly two available drives.
in the I/O group.
User response: Specify a number of available drives
that is supported for the RAID geometry that you
CMMVC6533E The command cannot be initiated
specify, and resubmit the command.
because the specified array member
does not exist in the selected array.
CMMVC6537E The command cannot be initiated
Explanation: This command requires that the array
because the drive that you have
member that you specify is an LDisk. It is possible that
specified has a Use property that is not
the array member that you specified was an LDisk that
supported for the task.
was recently deconfigured due to an error. You can use
the lsarraymember command to display the available Explanation: You can submit the lsdrive command to
members of an array. display the Use property of a drive and to determine
which drives are available.
User response: Select an array member that has an
associated LDisk, and resubmit the command. User response: Consult the command documentation
to determine what drive Use property values are
supported for this command. Ensure that you select a
drive that has a value for the Use property that is
supported when you submit this command.

572 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6538E • CMMVC6546E

CMMVC6538E The command cannot be initiated CMMVC6542E The remote authentication task has
because at least one of the drives that failed.
you have specified has a Use property
Explanation: An error has occurred while attempting
that is not Candidate.
to authenticate a user account using a remote
Explanation: Every drive that you specify for this authentication service. You can run the svc_snap task to
command must have a Use property of Candidate. You gather cluster information that can be used in problem
can submit the lsdrive command to display the Use determination.
property of existing drives.
User response: Contact IBM technical support for
User response: Ensure that all of the drives that you assistance.
specify have a Use property of Candidate, and
resubmit the command.
CMMVC6543E The task cannot be initiated because
you can only specify a direct-attached
CMMVC6539E The command cannot be initiated managed drive when you submit the
because the array does not have task.
sufficient redundancy.
Explanation: The drive that you have specified either
Explanation: The array must have sufficient is not managed or is not a local drive.
redundancy when you submit this command. The task
User response: Specify a direct-attached MDisk when
that you have requested would have taken the array
you submit this task.
offline.
User response: Fix all errors that are related to the
CMMVC6544E The task cannot be initiated at this
array that you have specified and restore redundancy
time because the direct-attached
to the array before you resubmit the command.
managed drive that you have specified
is too busy. Resubmit the task when the
CMMVC6540E The task cannot be initiated because drive is less busy.
the space-efficient grain size is too small
Explanation: The task takes approximately thirty
to accommodate the virtual capacity that
seconds to complete. When the direct-attached
you have requested for the VDisk.
managed drive is busy, the time that is required to
Explanation: The virtual capacity that you have complete the task increases. When the drive is too busy,
requested would required a larger number of grains the task cannot complete in a reasonable amount of
than the supported maximum for the specified grain time.
size.
User response: Resubmit the task when the
User response: Either increase the grain size, decrease direct-attached managed drive is less busy.
the requested virtual capacity of the volume, or both,
and resubmit the task.
CMMVC6545E The Apply Drive Software task has
failed to access the software download
CMMVC6541E The task cannot be initiated because image.
the virtual capacity that you have
Explanation: Either the image file cannot be read, the
requested for the VDisk is larger than
validation signature is incorrect, the drive type or
the maximum capacity that is supported
firmware type is not correct, or the image file has been
for the extent size.
corrupted.
Explanation: The extent size of the storage pool that
User response: Reinstall the firmware download
you have selected would require a larger number of
image, and resubmit the task. If the problem persists,
extents than the supported maximum to accommodate
contact IBM technical support for assistance.
the virtual capacity that you have requested for the
volume.
CMMVC6546E A device error was detected during
User response: Either select a different storage pool
the Apply Drive Software task.
that has an extent size that is large enough to
accommodate the requested virtual capacity or specify Explanation: The task might have succeeded.
a virtual capacity that is supported for the extent size
of the storage pool that you had selected, and resubmit User response: View the event in the event log.
the task. Determine the firmware level from the VPD of the
node. If the VPD does not show that the downloaded
firmware version is installed, resubmit the task.

Chapter 30. Command-line interface messages 573

CMMVC6547W • CMMVC6554E

is operating correctly. Ensure that the authentication

CMMVC6547W The Download FPGA firmware task
service URL that is defined in the cluster is correct.
has been initiated. The MDisk remains
Ensure that the network connection between the cluster
Offline while the task is in progress. Do
and the authentication service is operating correctly,
not remove power from the drive or
and resubmit the task.
node while the task in is progress.
Explanation: The task might take approximately
CMMVC6551E The Authentication task has failed
fifteen minutes to complete. When the task completes,
because the combination of user name
the drive status changes to Online automatically.
and password that is defined in the
User response: Ensure that electrical power is cluster for authorization by the
continuously being supplied to the node and the drive, authentication service is not defined on
at least until the task completes and the drive status the authentication service.
changes to Online.
Explanation: The authentication service has refused an
authentication request from the cluster. You can use the
CMMVC6548E The FPGA firmware cannot be chauthservice command to change the user name or
applied because the drive has a use the password that is defined in the cluster for the
other than candidate. authentication service.
Explanation: Updating a drive FPGA level is not User response: Ensure that the user name and
guaranteed to maintain data integrity, therefore the password combination that is defined in the cluster for
drive must not be part of an array. To ensure this, the the authentication service is also defined on the
drive must have a use of "candidate" before the authentication service, and resubmit the task.
package can be applied.
User response: If the drive is currently in the "failed" CMMVC6552E The Authentication task has failed
state, run through all maintenance actions required for because an SSL connection could not be
the drive before continuing. If the drive is a spare or established with the authentication
unused, the drive use can be changed through the GUI service.
or through the chdrive command. If a drive is
Explanation: This error might be caused by an
currently part of an array, a hot spare must be
incorrect SSL configuration on the authentication
configured and the drive use changed to failed, before
service server or by a rejection by the authentication
changing the use to candidate.
service server of the SSL certificate that is configured
on the cluster. You can use the chauthservice
CMMVC6549E The Authentication task has failed command to set the SSL certificate that is defined in the
because the authentication service URL cluster for the authentication service server.
that you have specified is not a valid
User response: Ensure that the SSL configuration on
URL.
the authentication service server is correct and that the
Explanation: This error might be caused by the SSL certificate that is defined in the cluster for the
authentication service not operating correctly or by an authentication service server is correct, and resubmit
incorrect URL being defined for the authentication the task.
service. You can use the chauthservice command to
change the URL that is defined in the cluster for the
CMMVC6553E The task cannot be initiated because
authentication service.
at least one quorum disk is not in the
User response: Ensure that the authentication service correct state.
is operating correctly. Ensure that the authentication
Explanation: All of the quorum disks must have a
service URL that is defined in the cluster is correct, and
state of Online when you set an MDisk to be the active
resubmit the task.
quorum disk.
User response: Ensure that all of the quorum disks
CMMVC6550E The Authentication task has failed
have a state of Online, and resubmit the task.
because the network address that is
specified in the authentication service
URL cannot be resolved. CMMVC6554E The Authentication task has failed
because the user name that was received
Explanation: The authentication service URL that is
from the authentication service is not a
defined in the cluster has a network address that
valid cluster user name.
cannot be resolved. You can use the chauthservice
command to change the URL that is defined in the Explanation: The cluster user name cannot exceed 256
cluster for the authentication service. characters in length, and cannot contain any of the
following characters:
User response: Ensure that the authentication service

574 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6555E • CMMVC6559E

v colon : supported maximum file size for this task, and

v percent sign % resubmit the task.
v comma ,
v double quote“” CMMVC6558E The command cannot be initiated
because it might cause VDisks to go
v single quote '
Offline. Refer to the cluster
User response: Change the definition of the user name Command-Line Interface (CLI)
in the remote authentication service so that it conforms command help for this command.
to the cluster user name requirements, and resubmit
Explanation: You are being warned that this command
the task.
might result in taking volumes Offline. After you
completely understand the possible consequences by
CMMVC6555E The Authentication task has failed reading the command help, you can override the safety
because the authentication service either precautions and avoid this message by using the -force
sent an incorrect response, or it sent a flag.
response that indicates that the
User response:
authentication request has failed for a
reason other than incorrect 1. Submit the lsnode dependantvdisks command to
authentication credentials. determine which volumes will go Offline if you
resubmit this command using the -force flag. If you
Explanation: Either the format of the response from received this message when you submitted the
the authentication service is not valid or the response applysoftware command, you must submit the
indicates a failure to authenticate that is not related to lsnode dependantvdisks command for every node
the credentials that were being authenticated. in the cluster; for all other commands you must
User response: Ensure that the authentication service submit the lsnode dependantvdisks command for
is functioning correctly, and resubmit the task. If the the node that you specified as a parameter in the
problem persists, contact the authentication service command that generated this message.
technical support for assistance. 2. This step is required because it is critically
important that you understand the implications of
using the -force flag for the specific command that
CMMVC6556E The task cannot be initiated because you have submitted: Refer to the CLI command
an error has occurred while attempting help to determine what safety precautions are
to read a file. bypassed when you use the -force flag. The ignored
Explanation: The task specified the name of a file on precautions differ, depending on the command.
the file system of the cluster configuration node. The 3. If you want to bypass the safety precautions when
specified file cannot be opened. This error might be you resubmit the command, you must use the -force
caused by a typographical error in the file name that flag.
you specified or by a failover of the configuration node
to a different node than the node into which you are
currently logged in. CMMVC6559E The Add or Change email user
command has failed because you have
User response: Ensure that the file has been copied to specified a user type of 'support' and
the current configuration node and that you are logged you have specified either the -warning
in to that node, specify the correct file name, and or -info parameter value as 'on'.
resubmit the task.
Explanation: The user type 'support' is intended to be
used to indicate that the user is from a hardware
CMMVC6557E The task cannot be initiated because maintenance support service external to your
the file that you have specified is too organization. Therefore, only events with the more
large. serious notification type of 'error' can be sent to a
'support' user type.
Explanation: The task specified the name of a file on
the file system of the cluster configuration node. The User response: Ensure that you have specified the
specified file cannot be used because it exceeds the correct user type. If you want this user to receive
maximum size supported for the task. If the file has warning or information notifications, do not specify the
been corrupted, you can copy the correct version of the '-usertype support' parameter and value. If you specify
file onto the configuration node to restore the correct the user type as 'support', you must specify the
file size. The maximum file size is described in the task -warning and -info parameters as 'off'.
help.
User response: Specify the correct file name and
ensure that the size of the file does not exceed the

Chapter 30. Command-line interface messages 575

CMMVC6560E • CMMVC6568E

'on', and resubmit the command.

CMMVC6560E The command has failed because the
specified IP address is already in use by
the cluster. CMMVC6564E You cannot make this user a remote
user because the password type is not
Explanation: You cannot specify an IP address that is
valid for a remote user.
already configured to be used by the cluster.
Explanation: The remote authentication server has
User response: Ensure that the IP address that you
requirements that do not accept legacy type passwords.
specify is not already configured for use by the cluster,
This user has a legacy type password.
and resubmit the task.
User response: Either specify a new password and
resubmit the command, or first modify the password
CMMVC6561E The set quorum active task has failed
and then resubmit the command to designate remote
because either another set quorum
authentication for this user.
active task is in progress or the selected
disk cannot be set as the active quorum
disk. CMMVC6565E The command has failed because the
specified node is not online.
Explanation: This is a multi-step task and can take
from a few seconds to several minutes to complete. Explanation: The command requires that the status of
Only one set quorum active task can be in progress at the node that you specify is Online.
any specified time. This error has one of two causes.
Either another set quorum task is already in progress, User response: Ensure that the node that you specify
or the internal cluster logic did not accept your request has a status of Online when you submit this command.
to make the selected disk the active quorum disk.
User response: Check the state of the MDisks and CMMVC6566E The command cannot be submitted
complete any outstanding fix procedures. If another set because specifying the -failover
quorum active task might be in progress, wait for parameter requires that you also specify
several minutes for that task to complete, and resubmit either the -name, -iscsialias or
this task. If you have received this error when there is -noiscsialias parameter.
no other set quorum active task in progress, specify a Explanation: You have not specified the required
different disk to replace the current active quorum disk failover data that is required when you specify the
and specify the same quorum index number, and -failover parameter.
resubmit this task.
User response: Ensure that you want to specify the
-failover parameter. When you specify the -failover
CMMVC6562E The requested size exceeds the parameter with this command, ensure that you also
maximum supported value. specify either the -name, -iscsialias or -noiscsialias
Explanation: You have submitted a command that has parameter.
a size parameter and an associated unit option that has
a default value of Megabytes (MB, 2e20 bytes) when CMMVC6567E The Apply Drive Software task has
the -unit option is not specified. The value that you failed because no download images
have specified for the size parameter in combination were found in the package file.
with the specified or default unit value is greater than
the maximum supported size of (2e64 - 1) bytes. Explanation: The drive software upgrade package file
was unpacked but no download software images were
User response: Ensure that the size that you specify is found in the package.
correct for the value of the unit option that is defaulted
or specified, and that the size is not greater than the User response: Acquire a valid solid-state drive
maximum supported size, and resubmit the task. software upgrade package file, and resubmit the task
using the new package file.

CMMVC6563E The command has failed because a

user that you have specified is not CMMVC6568E The Apply Drive Software task has
configured to receive email failed because no download images
notifications. were found in the package file for this
drive type.
Explanation: All of the users that you specify as a
target recipient in the testemail command must already Explanation: The package file documentation lists the
have at least one of the following email notification drive types for which there are images.
flags set to 'on': -error, -warning, or -info. User response: Acquire a valid solid-state drive
User response: Ensure that all of the users that you software upgrade package file that contains an image
specify have at least one email notification flag set to

576 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6569E • CMMVC6576E

for this drive type, and resubmit the task using the new
CMMVC6572E The command has failed because the
package file.
I/O group that manages the virtual disk
(VDisk) that you specified is not stable.
CMMVC6569E The Apply Drive Software task has
Explanation: The unstable I/O group condition is
failed because no download images
typically transient, and usually occurs during I/O
were found in the package file of this
group failover or fail back processing.
software type.
User response: Wait a few minutes, and resubmit the
Explanation: The package file documentation lists the
command.
drive types and software types for which there are
images. The value of the -type parameter that you enter
for software type is case-sensitive. CMMVC6573E The command has failed because the
VDisk that you specified is a source or
User response: Ensure that the value that you enter
target of a FlashCopy mapping that is in
for the -type parameter exactly matches the software
the prepared state.
type that is contained in the solid-state drive software
upgrade package file, and resubmit the command. Explanation: If the volume is the source or target of a
FlashCopy mapping, the FlashCopy mapping must be
in the idle_copied state or the stopped state when you
CMMVC6570E The command was not initiated
change the cache mode of the volume.
because the cache mode of the virtual
disk (VDisk) is already in the state that User response: Either remove or stop the FlashCopy
you had requested. mapping and wait for the FlashCopy mapping state to
become idle_copied or stopped, and resubmit the
Explanation: You have issued a change volume cache
command.
mode command but requested the current mode, so
there would not have been a change. Therefore, the
command was ignored. CMMVC6574E The command has failed because the
VDisk that you specified is a source or
User response: List the volume properties to
target of a FlashCopy mapping that is in
determine the current cache mode. If you want to
the suspended state.
change the cache mode, ensure that you specify a cache
mode that is different from the current cache mode, Explanation: If the volume is the source or target of a
and resubmit the command. FlashCopy mapping, the FlashCopy mapping must be
in the idle_copied state or the stopped state when you
change the cache mode of the volume.
CMMVC6571E The command has failed because the
I/O group that manages the virtual disk User response: Either remove or stop the FlashCopy
(VDisk) that you specified was offline mapping and wait for the FlashCopy mapping state to
when you submitted the command. You become idle_copied or stopped, and resubmit the
can use the -force flag to force the command.
operation, which might result in the loss
of cache data.
CMMVC6575E The command has failed because the
Explanation: If you submit this command without the VDisk that you specified is a source or
-force flag, the I/O group that manages the volume target of a FlashCopy mapping that is in
that you specify must have a state of Online. the preparing state.
Explanation: If the volume is the source or target of a
Note: Use of the -force flag when you change the cache
FlashCopy mapping, the FlashCopy mapping must be
mode might result in loss of the cache data for the
in the idle_copied state or the stopped state when you
volume, depending on the current cache mode and
change the cache mode of the volume.
requested cache mode. One example of a risk of
potential loss of cache data would be changing the User response: Either remove or stop the FlashCopy
cache mode from readwrite to none. mapping and wait for the FlashCopy mapping state to
become idle_copied or stopped, and resubmit the
User response: Either follow service procedures to
command.
bring the I/O group online or specify the -force flag to
force the change of the cache mode of the volume, and
resubmit the task. CMMVC6576E The command has failed because the
VDisk that you specified is a source or
target of a FlashCopy mapping that is in
the stopping state.
Explanation: If the volume is the source or target of a
FlashCopy mapping, the FlashCopy mapping must be

Chapter 30. Command-line interface messages 577

CMMVC6577E • CMMVC6584E

in the idle_copied state or the stopped state when you

CMMVC6581E The command has failed because the
change the cache mode of the volume.
maximum number of allowed iSCSI
User response: Either remove or stop the FlashCopy qualified names (IQNs) has been
mapping and wait for the FlashCopy mapping state to reached, or the IQN is already assigned
become idle_copied or stopped, and resubmit the or is not valid.
command.
Explanation: IQNs cannot exceed the maximum
number allowed, must not be duplicated, must not
CMMVC6577E The command has failed because the contain a comma, and must not contain leading or
VDisk that you specified is a source or trailing spaces.
target of a FlashCopy mapping that is in
User response: If the number of IQNs is within the
the copying state.
allowed maximum, ensure that you specify a unique
Explanation: If the volume is the source or target of a and valid IQN, and resubmit the command.
FlashCopy mapping, the FlashCopy mapping must be
in the idle_copied state or the stopped state when you
CMMVC6582E The task has failed because the iSCSI
change the cache mode of the volume.
host that you specified is not mapped to
User response: Either remove or stop the FlashCopy an I/O group.
mapping and wait for the FlashCopy mapping state to
Explanation: You cannot add a port to an iSCSI host
become idle_copied or stopped, and resubmit the
until you have mapped the iSCSI host to at least one
command.
I/O group.
User response: Map the iSCSI host to at least one I/O
CMMVC6578E The command has failed because the
group, and resubmit the command.
iSCSI name is already assigned or is not
valid.
CMMVC6583E The command has failed because the
Explanation: The cluster does not support duplicate
name that you specified contains a
iSCSI names. A valid iSCSI name cannot contain a
character that is not supported for a
comma or leading or trailing spaces.
node or cluster name.
User response: Ensure that you specify a unique and
Explanation: A node or cluster name cannot contain
valid iSCSI name, and resubmit the command.
any of the following characters or ASCII hexadecimal
values:
CMMVC6579E The command cannot be initiated v 0000-001F ASCII control characters
because the cluster Ethernet port 1 must
v 0020-002C The space character !“”# $ % the
always be fully configured in either the
ampersand character ' ( ) * + ,
IPv4 or IPv6 format.
v 002F /
Explanation: This error can be caused by an attempt
v 003B-0040 ; the 'less than' character = > ? @
to delete the only address that is configured on the
primary Ethernet port on the cluster. v 005B-0060 [ \ ] ^ _ `
v 007B-007F { | } ~ and the DEL character
User response: When you delete an IP address on the
primary Ethernet port, ensure that the other supported User response: Specify a valid name, and resubmit the
IP format is already configured on that port. command.

CMMVC6580E The command cannot be initiated CMMVC6584E The command cannot be initiated
because the iSCSI alias that you because it would deconfigure the remote
specified contained either leading or authentication service while the service
trailing space characters. is enabled.
Explanation: The space character cannot be the Explanation: You cannot deconfigure the remote
starting or ending character of an iSCSI alias name. authentication service while it is enabled.
User response: Ensure that the iSCSI alias that you User response: Ensure that the remote authentication
specify does not being or end with a space character, service is not being used, disable the service, and
and resubmit the command. resubmit the task.

578 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6585E • CMMVC6593E

want to use the drive that you specified to replace an

CMMVC6585E The command cannot be initiated
existing member of the array that you specified, you
because the array that you have
must specify the -balanced parameter, which forces the
specified has a geometry of RAID 0,
array member goals to be changed to accommodate the
which is not a redundant geometry.
new drive.
Explanation: The array that you specify for this
User response: Either select a different drive that
command must have a redundant geometry, and RAID
matches the array member goals or specify the
0 is not a redundant geometry.
-balanced parameter to force a change in the array
User response: Ensure that you specify an array that member goals to accommodate the new drive, and
has a redundant geometry when you submit the resubmit the command.
command.
CMMVC6590E The command cannot be initiated
CMMVC6586E The command cannot be initiated because you did not specify the
because the action would cause array -allowdegraded parameter and the
data loss due to the unsynchronized associated array member has insufficient
state of the array. spare protection.
Explanation: To avoid data loss, this command is not Explanation: This command requires that spare drives
permitted to process an array that is not synchronized. are available to assume the function of array member
drives that are removed from the array. The
User response: Use the lsarraysyncprogress
requirement can be bypassed by using the
command to ensure that the synchronization process
-allowdegraded parameter.
completes for this array, and resubmit the task.
User response: Either configure sufficient additional
spare drives or specify the -allowdegraded parameter,
CMMVC6587E The command did not complete
and resubmit the command.
because I/O for the array was not
quiesced within the allotted time
period. CMMVC6591E The command cannot be initiated
because the specified sequence number
Explanation: All outstanding I/O for the array must
does not match the sequence number of
complete before the configuration can be changed. The
any errors in the error log.
command has failed because there is still outstanding
I/O to be processed for the array, and the maximum Explanation: The sequence number that is specified in
amount of time allotted to the command has expired. the command must be identical to the sequence
number of an event in the event log.
User response: Resubmit the task.
User response: Check the event log to verify the
sequence number of the event that you want to specify,
CMMVC6588E The command cannot be initiated
and resubmit the command using the correct sequence
because a drive that you have specified
number.
has a capacity that is smaller than the
minimum capacity that is required for
the array that you have specified. CMMVC6592E The command cannot be initiated
because at least one parameter that was
Explanation: You can use the lsarraymembergoals
specified is not supported when
command to identify the capacity requirement for a
submitting a command to view the
member of the array that you specified.
details of an error log entry.
User response: Specify a drive that has sufficient
Explanation: Filtering parameters such as '-order
capacity for the array that you specify when you
severity' or '-status alert' that are valid when listing
submit the command.
multiple event log entries are not supported for the
command to view the details of a single event log
CMMVC6589E The command was not initiated entry.
because the drive that you have
User response: Check the command syntax, and use
specified does not sufficiently match the
supported syntax when you submit the command.
array member goals and you did not
specify the -balanced parameter.
CMMVC6593E The command cannot be initiated
Explanation: If you do not specify the -balanced
because the error log entry has a status
parameter, the new drive must be an exact match for
that is not supported for the command.
the array member goals when you exchange a new
drive for an existing array member. The new drive that Explanation: Only events with a status of 'alert' or
you have specified does not match the goals. If you 'message' can be manually marked as fixed or unfixed.

Chapter 30. Command-line interface messages 579

CMMVC6594E • CMMVC6613E

Events with a status of 'monitoring' or 'expired' are not

CMMVC6608E The command cannot be initiated
required to be marked as fixed or unfixed.
because Easy Tier is active on the virtual
User response: Check the event log to verify the disk copy.
sequence number of the event that you want to specify.
Explanation: Easy Tier is active on the volume copy,
Ensure that the event that you specify has a status that
which prevents the success of the command.
is supported for the command when you submit the
command. User response: Disable Easy Tier on the volume copy
or on the storage pool in which the volume copy
resides, and resubmit the command.
CMMVC6594E The command cannot be initiated
because a drive was specified twice in
the drive list. CMMVC6609E The command cannot be initiated
because the size of the Mdisk is smaller
Explanation: The drive list cannot contain any
than the extent size of the MDisk group.
duplicate entries because the same drive cannot be a
member of an array more than once. Explanation: The sizing of the Mdisk in relation to the
storage pool is not correct, which prevents the success
User response: Ensure that the drive list that you
of the command.
specify does not contain any duplicate entries when
you submit this task. User response: Use a larger Mdisk or make the extent
size of the storage pool smaller than the Mdisk, and
resubmit the command.
CMMVC6595E The command cannot be initiated
because a drive that you have specified
has a technology type that is not CMMVC6610E The software upgrade cannot start
supported for the command. because one or more I/O groups are in
maintenance mode.
Explanation: The command supports only certain
drive technology types. You have specified at least one Explanation: Maintenance mode is used during
drive that has a technology type that is not supported system servicing, which prevents software upgrades.
for the command.
User response: Complete system servicing, turn off
User response: Consult the command documentation maintenance mode, and resubmit the command.
to determine which drive technology types are
supported for the command. Submit the lsdrive
CMMVC6611E The command has failed because the
command to determine which drives are available.
specified enclosure is offline.
Specify an available drive that has a technology type
that is supported for the command when you submit Explanation: The specified enclosure is offline, which
the command. has prevented the success of the command.
User response: Fix any errors associated with the
CMMVC6596E The command has failed because you specified enclosure, and resubmit the command.
have specified an I/O group that does
not exist.
CMMVC6612E The command has failed because of a
Explanation: You must specify an existing I/O group hardware error.
when you submit this command.
Explanation: A hardware error has occurred, which
User response: Specify an existing I/O group, and has prevented the success of the command.
resubmit the command.
User response: Fix any errors in the specified object,
and resubmit the command.
CMMVC6597E The command has failed because the
email settings are not configured.
CMMVC6613E The command has failed because the
Explanation: The email system settings must be specified enclosure type is not
configured before you can submit a command for error supported.
notifications.
Explanation: You have attempted to use an enclosure
User response: Configure the email system settings to of an unsupported type.
enable error notifications, and resubmit the command.
User response: Do not attempt to use the specified
enclosure type.

580 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6614E • CMMVC6622E

CMMVC6614E The command has failed because the CMMVC6618E All available quorum disks are
specified canister is offline. dependent on the enclosure that you
have specified.
Explanation: The specified canister is offline, which
has prevented the success of the command. Explanation: Before removing the enclosure that you
have specified, the system must be configured so at
User response: Fix any errors associated with the
least one of the drives that are allocated to hold
specified canister, and resubmit the command.
quorum will remain online when the enclosure goes
offline.
CMMVC6615E The command cannot be initiated
User response: Assign one or more drives in the
because nodes from this enclosure
control enclosure as a quorum drive. After you have
cannot be added to the specified I/O
configured the quorum drives, test for dependencies.
group, or another enclosure is in the
process of being added.
CMMVC6619E All available quorum disks are
Explanation: The nodes in the enclosure being added
dependent on the canister that you have
are used elsewhere in the cluster, the target I/O group
specified.
contains nodes of a different control enclosure, or
another enclosure has not yet completed the process of Explanation: Before removing the canister that you
being added. have specified, the system must be configured so at
least one of the drives that are allocated to hold
User response: If a node already exists in the I/O
quorum will remain online when the canister goes
group, add nodes from the same enclosure only. If the
offline.
I/O group is empty, you can use a different control
enclosure in which the nodes are not in a cluster. If you User response: Assign one or more of the drives in
are currently adding another enclosure, wait for the the control enclosure as a quorum drive. After you
completion of that process. Ensure that both nodes of have configured the quorum drives, test for
an added enclosure are online and that the enclosure is dependencies.
listed in the output of the lsenclosure command.
CMMVC6620E The command cannot be initiated
CMMVC6616E All available quorum disks are because the drives that you have
dependent on the MDisks that you have specified are in different I/O groups.
specified.
Explanation: All of the specified drives that comprise
Explanation: The list of MDisks that you have the array must be in the same I/O group.
specified contains all activated quorum disks. If all of
User response: Specify one or more drives in the same
the MDisks in the list were to become inaccessible, the
I/O group, and resubmit the command.
system would be unable to backup important data.
Operating the system without any online quorum disks
is not recommended. CMMVC6621E The command cannot be initiated
because the array member that you have
User response: Move one or more quorum disks to
specified already exists.
MDisks that will remain online.
Explanation: A drive has already been configured for
the specified array member. You can use the
CMMVC6617E All available quorum disks are
lsarraymember command to display the available
dependent on the drives that you have
members of an array.
specified.
User response: Specify an array member without a
Explanation: The list of drives that you have specified
corresponding drive, and resubmit the command.
contains all activated quorum disks. If all of the drives
in the list were to become inaccessible, the system
would be unable to backup important data. Operating CMMVC6622E The command cannot be initiated
the system without any online quorum disks is not because the drive has failed validation
recommended. tests.
User response: Move one or more quorum disks to Explanation: When a drive is made a candidate, the
drives that will remain online. new drive is validated to ensure that adding it to the
configuration will not adversely affect the existing or
future array status. Either the current status of the
drive has not allowed the validation to be performed,
or the validation has failed.
User response: Fix any errors associated with the

Chapter 30. Command-line interface messages 581

CMMVC6623E • CMMVC6998E

specified drive, or specify a different drive, and User response: Ensure that the enclosure is online and
resubmit the command. cabled correctly, and resubmit the command.

CMMVC6623E The command cannot be initiated CMMVC6628E The enclosure that you have specified
because the drive validation test has cannot be changed to unmanaged mode
timed out. because one or more drives are in use.
Explanation: When a drive is made a candidate, the Explanation: The status of the enclosure that you have
new drive is validated to ensure that adding it to the specified will not allow the enclosure to be unmanaged
configuration will not adversely affect the existing or by the cluster.
future array status. The test timed out, which caused
User response: Stop using the drives, and resubmit
the validation to fail.
the command.
User response: Fix any errors that are associated with
the specified drive, or specify a different drive, and
CMMVC6630E A drive dump was not created
resubmit the command.
because a command was rejected by the
drive that you have specified.
CMMVC6624E The command cannot be initiated
Explanation: When initiating a drive dump, a
because the drive is not in an
sequence of commands is sent to the drive. One or
appropriate state to perform the task.
more of these commands was rejected by the drive that
Explanation: The drive that you have specified is you have specified.
offline. A format task is permitted to an offline drive
User response: Fix any errors associated with the
only if the drive has indicated that a format is required
drive, enclosure, and cabling, or specify a different
and connectivity to the drive is available.
drive, and resubmit the command.
User response: Fix any errors that are associated with
the specified drive, or specify a different drive, and
CMMVC6631E The task was not completed because
resubmit the command.
the drive that you have specified was
unavailable.
CMMVC6625E The command cannot be initiated
Explanation: The drive that you have specified did
because a task is in progress on the
not have the required connectivity to complete the task.
drive.
User response: Fix any errors associated with the
Explanation: A drive can complete only one task at a
drive, or specify a different drive, and resubmit the
time. A previous task remains uncompleted. You can
command.
monitor the progress of the task using the
lsdriveprogress command.
CMMVC6988E The command cannot be initiated
User response: Wait for the previous task to complete,
because the maximum number of iSCSI
and resubmit the command.
qualified names (IQNs) for the cluster
has been reached.
CMMVC6626E The task was not initiated because a
Explanation: The specified cluster is already
command was rejected by the drive that
configured with the maximum number of IQNs.
you have specified.
User response: None.
Explanation: When attempting to initiate a task, a
sequence of commands is sent to the drive. One or
more of these commands was rejected by the drive that CMMVC6998E The command cannot be initiated
you have specified. because the maximum number of iSCSI
qualified names (IQNs) for one or more
User response: Fix any errors that are associated with
I/O groups has been reached.
the enclosure and cabling, and resubmit the command.
Explanation: One or more I/O groups are already
configured with the maximum number of IQNs.
CMMVC6627E The enclosure that you have specified
cannot be changed to managed mode User response: None.
because of a SAS configuration problem
that is described in the event log.
Explanation: The status of the enclosure that you have
specified will not allow the enclosure to be managed by
the cluster.

582 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC6999E • CMMVC7019E

CMMVC6999E The command cannot be initiated CMMVC7014E The command cannot be initiated
because the maximum number of iSCSI because one or more of the drives are
qualified names (IQNs) for the host has not supported for this RAID level.
been reached.
Explanation: Only certain RAID levels are supported
Explanation: The specified host is already configured in some configurations.
with the maximum number of IQNs.
User response: Consult the configuration guide to
User response: None. determine supported RAID levels.

CMMVC7003E The command cannot be initiated CMMVC7015E The command cannot be initiated
because the power supply unit (PSU) because one or more of the drives are
that you have specified is offline. located in the wrong node.
Explanation: The power supply unit (PSU) that you Explanation: For RAID 0, all of the members must be
specify must be online when you submit the command. located in the same node. For RAID 1 or RAID 10,
mirrored pairs must be located in different nodes.
User response: Fix any errors associated with the
specified PSU. Ensure that the PSU is online, and User response: Consult the configuration guide to
resubmit the command. determine which drives to use for the selected RAID
level.
CMMVC7005E The command cannot be initiated
because enclosures do not exist for the CMMVC7016E Authorization has failed because the
I/O group that you have specified. private key is not valid for the user
name that you have specified.
Explanation: You have submitted a command and
specified an I/O group that is not associated with an Explanation: The private key and user name that you
enclosure. You can submit the lsenclosure command to have provided do not match what has been defined on
show all of the existing enclosures and their associated the cluster.
I/O groups.
User response: Ensure that the private key is valid for
User response: Specify an I/O group that is associated the specified user name, and log in again.
with an enclosure when you submit the command.
CMMVC7017E Login has failed because the
CMMVC7010E The command cannot be initiated maximum number of concurrent CLI
because the MDisk mode is set to Array. sessions has been reached.
Explanation: This command requires the selected Explanation: The cluster supports up to 10 concurrent
MDisk to be a SAN MDisk (an MDisk that is not an CLI sessions. The login attempt would have exceeded
array made from local drives). The selected MDisk has the supported limit.
its mode set to Array.
User response: Reduce the number of open CLI
User response: Use lsmdisk to list the MDisks, and sessions, and log in again.
resubmit the command against an MDisk with a mode
other than Array.
CMMVC7018E The command failed because the
requested VDisk size is too large.
CMMVC7011E The array cannot be created because
Explanation: The system has a maximum size for
no quorum disks are currently
virtual disks (VDisks) that is currently 256 TB. While
configured.
creating a new VDisk or resizing an existing VDisk,
Explanation: When creating an array, quorum disks you requested a VDisk size that exceeds the maximum.
are required to back up metadata for the array.
User response: Resubmit the command with a smaller
Creating an array while no quorum disks are
VDisk size.
configured is not permitted. Quorum disks can be
assigned to drives in the control enclosure
automatically, or manually by using the chquorum CMMVC7019E The command failed because the
command. VDisk size is not a multiple of 512
bytes.
User response: Manage the control enclosure, and
ensure that all drives within the enclosure are online Explanation: VDisk capacity must be a complete
before resubmitting the command. number of blocks, where one block is 512 bytes. While
creating a new VDisk or resizing an existing VDisk,

Chapter 30. Command-line interface messages 583

CMMVC7020E • CMMVC7028E

you requested a VDisk size that is an incomplete has been reached. Additional file systems cannot be
number of blocks. created.
User response: Resubmit the command with a valid User response: Remove an unused file system and
VDisk size. reissue the command, or extend an existing file system
by creating the VDisk there.
CMMVC7020E The command failed because the
maximum number of VDisks for this CMMVC7025E The command failed because the
I/O group already exist. VDisk is associated with a file system
and cannot be removed under your
Explanation: The system has a limit of VDisks per
current user role.
I/O group. A new VDisk cannot be created in an I/O
group that has already reached the limit of VDisks. Explanation: You are attempting to remove a VDisk
that is associated with a file system. However, you do
User response: Choose another I/O group or delete
not possess the required role for file system actions and
some VDisks in this I/O group.
VDisk removal.
User response: Resubmit the task using the SONAS
CMMVC7021E The command failed because the
remove VDisk command.
maximum number of VDisk copies
already exist.
CMMVC7026E The command failed because VDisks
Explanation: The system has a limit on the number of
exist in the file system.
VDisk copies that can be created. An additional VDisk
copy cannot be created because the limit has been Explanation: You are attempting to delete an MDisk
reached. group with which VDisks are associated. The MDisk
group cannot be removed while the associated VDisks
User response: Delete some existing VDisk copies and
remain.
resubmit the command.
User response: Remove the file system VDisks, and
resubmit the command to remove the MDisk group.
CMMVC7022E The command failed because NTP is
active.
CMMVC7027E The command failed because the
Explanation: You have attempted to manually set the
requested action is not permitted on a
cluster time while the cluster is configured to use NTP
VDisk that is in a file system.
(network time protocol) to set its time.
Explanation: The VDisk that you have specified is
User response: Disable NTP, and resubmit the
associated with a file system, which disallows the
command. If you are trying to set the time manually
requested action.
because the cluster time is incorrect, check the settings
on the NTP server. User response: The command cannot be completed on
this VDisk. It will only succeed with a VDisk that is not
associated with a file system.
CMMVC7023E The command failed because the
requested node name is in use as the
failover name of another node. CMMVC7028E The task cannot be completed
because the FlashCopy target VDisk that
Explanation: You have attempted to add a node to a
you have specified is in a Metro Mirror
cluster or rename a node that is already in the cluster.
or Global Mirror relationship, and the
The new name that you have requested for the node is
I/O group of the VDisk is different than
not valid because one of the nodes in the cluster has
that of the proposed FlashCopy
been configured with the requested new name as its
mapping.
failover name.
Explanation: The FlashCopy map must be in the same
User response: Either resubmit the command
I/O group as the target VDisk because the VDisk is a
specifying a different node name, or modify the
component of a remote copy relationship.
configuration of the node in the cluster to change its
matching failover name to a different failover name. User response: Specify the I/O group of the target
VDisk when creating the FlashCopy map.
CMMVC7024E The command failed because the
maximum number of file systems
already exist.
Explanation: The maximum number of file systems

584 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC7029E • CMMVC7041E

CMMVC7029E The task cannot be completed CMMVC7036E The action failed because quorum is
because one or more of the target not permitted on the drive that you have
VDisks of the FlashCopy mappings is specified.
the primary of a mirroring Metro Mirror
Explanation: Quorum is only permitted on specific
or Global Mirror relationship.
drive types. The drive that you have selected will not
Explanation: The target VDisk is part of a remote support quorum.
copy relationship that is active.
User response: Reissue the command specifying a
User response: Either force stop the FlashCopy different drive.
consistency group or stop any remote copy
relationships.
CMMVC7037E The action failed because the drive
cannot be found.
CMMVC7030E The task cannot be completed
Explanation: You have specified a drive does not
because the target VDisk of the
appear to exist.
FlashCopy mapping is the primary of a
mirroring Metro Mirror or Global User response: Reissue the command specifying a
Mirror relationship. different drive.
Explanation: The target of the FlashCopy map is a
component of an active FlashCopy map. CMMVC7038E The action failed because the system
was unable to initialize the quorum
User response: Either force stop the FlashCopy map
disk.
or stop the remote copy relationship.
Explanation: A sequence of SCSI commands must be
sent to a quorum disk before it can become available
CMMVC7031E The task cannot be completed
for use. One of these SCSI commands has failed.
because the FlashCopy mapping target
VDisk is a secondary in a Metro Mirror User response: Fix any errors associated with the
or Global Mirror relationship, or is the drive or MDisk, choose a different resource for quorum,
primary in an active relationship. then reissue the command.
Explanation: The target VDisk of the FlashCopy map
is part of an active remote copy relationship. CMMVC7039E The action failed because the
specified drive is not online.
User response: Stop the remote copy relationship.
Explanation: The drive that you have specified is
offline possibly as a result of errors.
CMMVC7032E The task cannot be completed
because one or more of the target User response: Fix any errors associated with the
VDisks of the FlashCopy mappings is drive, or choose a different resource for quorum, then
either a secondary in a Metro Mirror or reissue the command.
Global Mirror relationship or the
primary of an active relationship.
CMMVC7040E The action failed because the
Explanation: A target VDisk of a FlashCopy map in specified MDisk is not online.
the consistency group is part of an active remote copy
relationship. Explanation: The MDisk that you have specified is
offline possibly as a result of errors.
User response: Stop any remote relationships
containing a target VDisk of a map in the consistency User response: Fix any errors associated with the
group. MDisk, or choose a different resource for quorum, then
reissue the command.

CMMVC7033E The task failed because the current

hardware configuration is not valid. CMMVC7041E The action failed because a better
quorum candidate is available for use as
Explanation: You have issued the “chnodehw” quorum and override has not been
command to enable new hardware that is faulty, enabled.
unsupported, or incompletely installed.
Explanation: Quorum disks are selected automatically
User response: Follow service procedures as based on a set of selection criteria. The resource that
prompted by the management GUI to correct the was selected is inferior to an alternative resource.
hardware configuration. Then reissue the command.
User response: Choose a different resource for
quorum, or refer to the quorum documentation before

Chapter 30. Command-line interface messages 585

CMMVC7042E • CMMVC7051E

using the -override parameter. not support a validation function.

User response: None.
CMMVC7042E The action failed because the
-override yes parameter was used
CMMVC7048E The action failed because the
without a specified drive or MDisk.
compressed VDisk copies are not all
Explanation: The -override yes parameter must corrupted.
specify a drive or MDisk.
Explanation: You have issued the repairsevdiskcopy
User response: Reissue the command with the correct or recovervdisk -copy command against a compressed
syntax. VDisk copy that is not marked as corrupt. Unlike
thin-provisioned VDisk copies, the repair process for
compressed VDisk copies can only be run if the system
CMMVC7043E The action failed because the
detects that they are corrupted.
required extents could not be allocated.
User response: The issued command is not required.
Explanation: When an MDisk is specified for quorum,
If the VDisk is offline, consult the Troubleshooting Guide
some extents must be allocated for use by the quorum
to resolve the problem.
disk. Sufficient extents were not available.
User response: Reissue the command using a different
CMMVC7049E The command failed because VDisks
MDisk or migrate data from the MDisk to free up
are obstructing resources required by
sufficient extents.
the compression function.
Explanation: Compression could not be enabled
CMMVC7044E The action failed because the
because a VDisk prevented internal resources from
specified drive is either degraded or
being reassigned from cache. A VDisk is offline or data
excluded.
could not be flushed from the cache quickly enough.
Explanation: The drive that you have specified either
User response: If any VDisks are offline, follow
contains errors or is in the Excluded state.
service procedures to bring them online before
User response: Fix any errors associated with the resubmitting the command.
drive, or choose a different resource for quorum, then
reissue the command.
CMMVC7050E The command failed because at least
one node in the I/O group does not
CMMVC7045E The action failed because the support compressed VDisks.
specified MDisk is either degraded or
Explanation: Compression is supported only on the
excluded.
CF8 and later models of SVC node. You have
Explanation: The MDisk that you have specified either attempted to create a compressed VDisk in an I/O
contains errors or is in the Excluded state. group that contains at least one node that does not
meet these requirements.
User response: Fix any errors associated with the
MDisk, or choose a different resource for quorum, then User response: Resubmit the command with a
reissue the command. different I/O group.

CMMVC7046E The action failed because the -rsize CMMVC7051E The command failed because the I/O
option must be set to auto. group contains compressed VDisks. The
node being added does not support
Explanation: You have run the mkvdisk or compressed VDisks.
addvdiskcopy command to import a compressed VDisk
(using -compressed and -import). The -rsize option Explanation: Compression is supported only on the
must be set with an argument of “auto”. CF8 and later models of SVC node. You have
attempted to add a node that does not support
User response: Resubmit the command with -rsize compression to an I/O group that already contains at
auto. least one compressed VDisk.
User response: Add the node to a different I/O group
CMMVC7047E The action failed because the validate or add a different node to the specified I/O group.
parameter is not supported for
compressed VDisks.
Explanation: The command repairsevdiskcopy
-validate was issued against a compressed VDisk.
Unlike thin-provisioned VDisks, compressed VDisks do

586 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC7052E • CMMVC7061E

User response: Disable the remote authentication

CMMVC7052E The nested group search parameter is
service by submitting the chauthservice command, and
not valid for the target LDAP server
reissue the task.
type.
Explanation: The LDAP server type that you have
CMMVC7058E The task cannot be initiated because
specified is predefined to perform nested group search.
no LDAP server is configured.
User response: None.
Explanation: The LDAP remote authentication service
cannot be used until at least one LDAP server has been
CMMVC7053E The task cannot be initiated because configured. To configure LDAP servers, the
the nested group search value (server) is mkldapserver command can be submitted.
not valid for the target LDAP server
User response: Configure a valid LDAP server, and
type.
reissue the task.
Explanation: The LDAP server type that you have
specified only supports client-side nested group search.
CMMVC7059E The task cannot be initiated because
User response: Reissue the task specifying client-side some remote users are not configured
nested group search. with an SSH key and password for the
specified remote authentication service.
CMMVC7054E The task cannot be initiated because Explanation: An SSH key and password are required
the user name or password of the LDAP for all users of the remote authentication service. To
administrator was not specified. identify remote users without an SSH key and
password, the lsuser command can be submitted. To
Explanation: The user name and password of the
configure the user's authentication settings, you can use
LDAP administrator are not configured on the cluster
the chuser command.
as required. Once the credentials are configured, the
user name and password can be changed separately. User response: Configure the remote users with an
SSH key and password or configure the users as local.
User response: Reissue the task specifying both the
LDAP administrator user name and password.
CMMVC7060E The task cannot be initiated because
the parameters that you have specified
CMMVC7055E The task cannot be initiated because
are not valid for the LDAP
the specified IP address, port, and base
authentication service.
distinguished name (DN) are already
configured on an LDAP server. Explanation: The authentication service URL, user
name, password, and SSL certificate are not
Explanation: The same IP address, port, and base DN
configurable for the LDAP authentication service.
exist on more than one LDAP server.
User response: Reissue the task specifying valid
User response: Reissue the task specifying an different
parameters.
IP address, port, and base DN.

CMMVC7061E The task cannot be initiated because

CMMVC7056E The task cannot be initiated because
the LDAP administrator user name that
the number of LDAP servers has
you have specified is not valid.
reached the supported maximum.
Explanation: LDAP administrator user names must be
Explanation: The cluster limits the number of LDAP
a valid Distinguished Name, NT login, or User
servers that can be configured, and the limit has been
Principal Name.
reached. To remove a configured LDAP server, the
rmldapserver command can be submitted. v Distinguished Names must be a sequence of
attribute=value pairs separated by a comma (,),
User response: Remove a configured LDAP server, semicolon (;), or plus sign (+), and include special
and resubmit the task. characters and UTF-8 characters that are
appropriately escaped with a backslash (\).
CMMVC7057E The task cannot be initiated because v NT logins are valid for Active Directory only and
the specified LDAP server is the only should be in the format DOMAIN\user. They must
configured LDAP server. not start or end with a period (.) and both DOMAIN
and user must exclude characters in the set: \ / : ? "
Explanation: Removing the specified LDAP server <>|
would result in the failure of the remote authentication
service. v UPN logins are valid for Active Directory only and
must be in the format user@suffix. Both user and

Chapter 30. Command-line interface messages 587

CMMVC7062E • CMMVC7068E

suffix must exclude spaces and the following User response: Ensure that LDAP servers and the
characters: ( ) < > , ; : \ " [ ] @ TCP/IP network between them and the cluster are
functional. Ensure that the IP address and port defined
User response: Reissue the task specifying a valid
for each LDAP server is correct, and reissue the task.
Distinguished Name, NT login, or User Principal
Name.
CMMVC7066E User authentication failed because an
SSL connection could not be established
CMMVC7062E The task cannot be initiated because
with one or more LDAP servers.
you have specified an LDAP attribute
that is not valid. Explanation: An incorrect LDAP security
configuration exists on the cluster or an SSL certificate
Explanation: An LDAP attribute name can contain
on the cluster is not valid. The event was logged and
only alphanumeric characters and hyphens, and the
the corresponding service procedure is available to
name must begin with a letter.
resolve this issue. To turn off transport layer security, a
User response: Reissue the task specifying a valid security administrator can submit the chldap command
LDAP attribute name. or submit the chldapserver command to set the SSL
certificate for an LDAP server.

CMMVC7063E The task cannot be initiated because User response: Ensure that the SSL configuration on
the Distinguished Name that you have each LDAP server is correct and that the SSL certificate
specified is not valid. defined in the cluster for each LDAP server is correct,
or ensure that Transport Layer Security is disabled.
Explanation: A Distinguished Name must be a Then reissue the task.
sequence of attribute=value pairs separated by a
comma (,), semicolon (;), or plus sign (+) that includes
special characters and UTF-8 characters escaped with a CMMVC7067E User authentication failed because
backslash (\). one or more LDAP servers rejected an
anonymous bind attempt.
User response: Reissue the task specifying a valid
Distinguished Name. Explanation: A user name and password were not
specified on the cluster for LDAP authentication and
the LDAP server has refused an attempt to bind
CMMVC7064E User authentication failed because anonymously. The event has been logged and the
one or more LDAP servers could not be corresponding service procedure can be used to resolve
contacted. this issue. To configure a user name and the password
Explanation: The LDAP server is not operating for LDAP authentication, a security administrator can
correctly or an incorrect IP address and port are submit the chldap command.
defined for the LDAP authentication service. The event User response: Ensure that all LDAP servers are
log has been logged and the corresponding service configured to allow anonymous bind, or configure a
procedure can be used to resolve this issue. To change user name and password for LDAP authentication.
the IP address and port of an LDAP server, a security Then reissue the task.
administrator role can submit the chldapserver
command.
CMMVC7068E User authentication failed because
User response: Ensure that the LDAP servers are one or more LDAP servers rejected an
operating correctly. Ensure that the IP address and port attempt to bind with the LDAP
defined for each LDAP server is correct, and reissue the administrator credentials configured on
task. the cluster.
Explanation: A user name and password were
CMMVC7065E User authentication failed because a configured on the cluster for LDAP authentication and
timeout occurred while communicating an LDAP server has refused an attempt to bind with
with one or more LDAP servers. these credentials. The event has been logged and the
Explanation: A timeout occurred while the cluster was corresponding service procedure can be used to resolve
attempting to contact the LDAP servers. This timeout this issue. To change the user name and password
might be caused by a TCP/IP network problem, the defined on the cluster, a security administrator can
LDAP servers not operating correctly, or by an incorrect submit the chldap command.
IP address and port being defined for the LDAP User response: Ensure that the LDAP credentials
servers. The event has been logged and the configured on the cluster match the credentials that are
corresponding service procedure can be used to resolve configured on all LDAP servers, and reissue the task.
this issue. To change the IP address and port of an
LDAP server, a security administrator can use the
chldapserver command.

588 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC7069E • CMMVC7075I

CMMVC7069E User authentication failed because CMMVC7072E User authentication failed because
one or more LDAP servers report an the LDAP group attribute is not in a
incorrect user name or password. valid format on one or more LDAP
servers.
Explanation: The user name and password that you
have provided do not match any user name and Explanation: The LDAP group attribute in the user
password on the configured LDAP servers. If the entry on the configured LDAP servers is in an invalid
password for the user name has recently changed on format. The event has been logged and the
the configured LDAP servers, it may be necessary to corresponding service procedure can be used to resolve
force the cluster to refresh its authentication cache. To this issue. The attribute must be a multivalued attribute
force a refresh, a security administrator can submit the containing the distinguished names of groups, or a
chauthservice -refresh command. colon-separated list of up to eight user group names.
User response: Ensure that the user name and User response: Ensure that the LDAP group attribute
password are correct. Ensure that any recently changed is correctly formatted on the LDAP servers, and reissue
passwords are flushed from the cache of the cluster, the task.
and reissue the task.
CMMVC7073E User authentication failed because
CMMVC7070E User authentication failed because the LDAP audit log attribute is not
the LDAP user attribute is incorrectly configured correctly on one or more
configured on one or more LDAP LDAP servers.
servers.
Explanation: The LDAP configuration on the cluster
Explanation: The LDAP configuration on the cluster specifies an LDAP audit log attribute that does not
specifies an LDAP user attribute that does not exist on exist on the LDAP server. The string to use in the audit
the LDAP server. Users cannot be identified by user log cannot be identified because this attribute is
name because the attribute is incorrectly configured. incorrectly configured. The event has been logged and
The event has been logged and the corresponding the corresponding service procedure can be used to
service procedure is available to resolve this issue. To resolve this issue. To specify a different audit log
specify a different user attribute, a security attribute, a security administrator can issue the chldap
administrator can submit the chldap command. command.
User response: Ensure that the LDAP user attribute User response: Ensure that the LDAP audit log
specified on the cluster is correct. Ensure that the attribute is correctly specified on the cluster. Ensure
schema on the configured LDAP servers includes the that the schema on the LDAP servers includes the
specified attribute, and reissue the task. specified attribute, and reissue the task.

CMMVC7071E User authentication failed because CMMVC7074E The task cannot be initiated because
the LDAP group attribute is incorrectly the user could not be found on any of
configured on one or more LDAP the configured LDAP servers.
servers.
Explanation: The remote user is configured but either
Explanation: The LDAP configuration on the cluster no entry for the user exists on the configured LDAP
specifies an LDAP group attribute that does not exist servers, or more than one entry was found. The event
on the LDAP server. The groups to which a user has been logged and the corresponding service
belongs cannot be identified because the attribute is procedure can be used to resolve this issue.
incorrectly configured. The event has been logged and
User response: Ensure that the user name is unique
the corresponding service procedure can be used to
on the LDAP servers. Ensure that the LDAP bind
resolve this issue. To specify a different group attribute,
credentials allow the LDAP server to be searched, and
a security administrator can submit the chldap
reissue the task.
command.
User response: Ensure that the LDAP group attribute
CMMVC7075I The LDAP task completed
specified on the cluster is correct. Ensure that the
successfully.
schema on the configured LDAP servers includes the
specified attribute, and reissue the task. Explanation: The LDAP task completed successfully.
User response: None.

Chapter 30. Command-line interface messages 589

CMMVC7076E • CMMVC8061E

CMMVC7076E VOLUME cannot be created with CMMVC7081E The compressed storage used by the
VALUE without VALUE. cluster has exceeded the capacity that is
licensed.
Explanation: You are attempting to create a thin
provisioned file system volume without compression. Explanation: You are being informed that compressed
Thin provisioned file system volumes must include storage in use by the cluster exceeds the total licensed
compression. capacity.
User response: Create a thin provisioned file system User response: Reduce the use of compressed storage
volume with compression or create a file system or purchase additional licensing.
volume without thin provisioning.
CMMVC7082E The number of control enclosures
CMMVC7077E The command failed because adding with compressed VDisks exceeds the
a thin provisioned copy to a file system number that are licensed.
volume is not allowed.
Explanation: You are being informed that the licensed
Explanation: You are attempting to add a VDisk copy number of control enclosures that can contain
to a file system volume that is not compressed but is compressed VDisks has been exceeded.
thin provisioned. Only copies with compression or
User response: Reduce or consolidate compressed
without thin provisioning can be added to file system
VDisks or purchase additional licensing.
volumes.
User response: Add a copy either with compression
CMMVC7083E The specified number of control
or without thin provisioning to the file system volume.
enclosures is not valid.
Explanation: The valid range of values for licensed
CMMVC7078E The command cannot be initiated
control enclosures is 0–4. The value that you specify
because adding a copy to the storage
must be within this range.
pool of file system VDisks is not
allowed. User response: Specify a value between 0 and 4.
Explanation: You are attempting to add a VDisk copy
to a file system volume from a different storage pool. CMMVC7084E The action failed because the
Only copies from the same storage pool can be added command is not permitted for
to file system volumes. compressed VDisks.
User response: Add a VDisk copy to a storage pool Explanation: The command that you have submitted
within the same file system VDisk, only. is not valid on compressed VDisks.
User response: Do not submit this command for a
CMMVC7079E The command failed because a compressed VDisk.
volume copy must be different when
added to a file system volume.
CMMVC8061E The command failed because the
Explanation: You are only allowed to add a different hardware configuration of the local
volume copy to perform conversions between cluster is not compatible with the
uncompressed and compressed. software of a partnered cluster.
User response: Add a compressed copy to a file Explanation: The software version of the local cluster
system volume with an uncompressed copy or an is newer than the software version of a partnered
uncompressed copy to a file system volume with a cluster, and additional hardware has been enabled that
compressed copy. is not supported by the older software on the partnered
cluster.
CMMVC7080W The compressed storage used by the User response: Either upgrade the software on the
cluster is approaching the capacity that partnered cluster, turn off the new hardware on the
is licensed. local cluster, or stop the remote copy relationship with
the remote cluster. Use the CLI command
Explanation: You are being informed that compressed
chnodehardware -legacy to disable hardware that is not
storage in use by the cluster has nearly reached the
supported by older software versions.
total licensed capacity.
User response: Compare your actual and planned
usage of compression.

590 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC8062E • CMMVC7162E

CMMVC8062E Cannot remove the latest I/O group CMMVC7158E The change VDisk could not be
from the volume access set. associated because the Metro Mirror or
Global Mirror relationship has a VDisk
Explanation: Running this command removes access
on this cluster that is already involved
to all the I/O groups in the access set.
in the maximum number of FlashCopy
User response: Before you run the command again, mappings.
either modify the I/O group list so that it does not
Explanation: The change VDisk cannot cause another
include all the I/O groups that provide access to the
VDisk to exceed the number of FlashCopy mappings
volume or add more I/O groups to the access set.
allowed.
User response: Reduce the number of FlashCopy
CMMVC7154E The task cannot be completed
mappings in the VDisk that has reached its maximum.
because the specified FlashCopy
mapping is controlled by a Metro
Mirror or Global Mirror relationship. CMMVC7159E The change VDisk could not be
associated because the Metro Mirror or
Explanation: The Metro Mirror or Global Mirror
Global Mirror relationship has a VDisk
relationship under which the specified FlashCopy
on this cluster that is in an I/O group
mapping is controlled prevents completion of the task.
with no online nodes.
User response: Check whether the specified task is
Explanation: The nodes of an I/O group must be
permitted under the configuration of the Metro Mirror
brought online before the change VDisk can be
or Global Mirror relationship.
associated.
User response: Ensure that the nodes of the I/O
CMMVC7155E The Create FlashCopy mapping task
group are online.
cannot be initiated because the source or
target VDisk is being used as a change
VDisk for a Metro Mirror or Global CMMVC7160E The change VDisk could not be
Mirror relationship. associated because the I/O group has
insufficient free bitmap space.
Explanation: A VDisk cannot become the source or
target of a FlashCopy mapping while in use as a Explanation: The I/O group must have additional
change VDisk in a Metro Mirror or Global Mirror bitmap space to allow the change VDisk to be
relationship. associated.
User response: Specify a VDisk other than the source User response: Increase the total bitmap space of the
or target that is currently in use. I/O group.

CMMVC7156E The change VDisk could not be CMMVC7161E The change VDisk could not be
associated because it is already a source associated because the master change
or target VDisk in an existing VDisk can only be configured from the
FlashCopy mapping. master cluster, and the auxiliary change
VDisk from the auxiliary cluster. The
Explanation: A change VDisk cannot be associated if
change VDisk must be configured from
the same VDisk is the source or target of a FlashCopy
the remote cluster.
mapping.
Explanation: A change VDisk must be associated from
User response: Specify a VDisk other than the source
a cluster of the same type (master or auxiliary).
or target that is currently in use.
User response: Configure the change VDisk from the
remote cluster.
CMMVC7157E The change VDisk could not be
associated because the Metro Mirror or
Global Mirror relationship has a VDisk CMMVC7162E The change VDisk could not be
on this cluster that is the target of a associated because one is already
FlashCopy mapping in a different I/O configured for the specified Metro
group. Mirror or Global Mirror relationship.
Explanation: The I/O group of the change VDisk Explanation: A change VDisk has been previously
conflicts with an I/O group in the relationship with configured for the specified Metro Mirror or Global
which an association was attempted. Mirror relationship.
User response: Ensure that no conflicting I/O groups User response: Ensure that the change VDisk is
exist.

Chapter 30. Command-line interface messages 591

CMMVC7163E • CMMVC7172E

associated where a change VDisk has not been

CMMVC7168E The VDisk-to-host mapping was not
configured.
created because the VDisk is a change
VDisk for a Metro Mirror or Global
CMMVC7163E The change VDisk could not be Mirror relationship.
associated because it is already involved
Explanation: A VDisk cannot be mapped to a host if it
in a Metro Mirror or Global Mirror
is associated as a change VDisk.
relationship.
User response: Choose a different change VDisk.
Explanation: The change VDisk is currently associated
with a Metro Mirror or Global Mirror relationship.
CMMVC7169E The Remote Copy relationship could
User response: Choose an unassociated change VDisk
not be deleted because this would
for the specified Metro Mirror or Global Mirror
corrupt the secondary VDisk.
relationship.
Explanation: The deletion of the relationship is being
prevented as a safeguard against corrupting the
CMMVC7164E The change VDisk could not be
secondary. The result can be prevented by allowing
associated because its size is different
resynchronization, or by overriding the safeguard.
from those in the Metro Mirror or
Global Mirror relationship. User response: Allow the relationship to become
synchronized before deleting, or reissue the command
Explanation: A change VDisk being cannot be
with the -force flag to allow corruption of the
associated with VDisks of a different size.
secondary.
User response: Choose a change VDisk with a size
that matches those with which it is being associated.
CMMVC7170E The Remote Copy relationship could
not be created because the specified
CMMVC7165E The change VDisk could not be master VDisk is already a change VDisk
disassociated because the Metro Mirror for a different relationship.
or Global Mirror relationship does not
Explanation: A master VDisk cannot be selected as a
have one configured.
change VDisk of a Remote Copy relationship while
Explanation: An attempt was made to disassociate a currently defined for a different relationship.
change VDisk where one does not currently exist.
User response: Choose a different master VDisk.
User response: Verify whether the intended change
VDisk was specified.
CMMVC7171E The Remote Copy relationship could
not be created because the specified
CMMVC7166E The change VDisk could not be auxiliary VDisk is already a change
disassociated because it is currently in VDisk for a different relationship.
use by the Metro Mirror or Global
Explanation: An auxiliary VDisk cannot be selected as
Mirror relationship.
a change VDisk of a Remote Copy relationship while
Explanation: An attempt was made to disassociate a currently defined for a different relationship.
change VDisk that is currently in use.
User response: Choose a different auxiliary VDisk.
User response: Verify whether the intended change
VDisk was specified.
CMMVC7172E Enabling access to the secondary
VDisk of the Remote Copy relationship
CMMVC7167E The change VDisk could not be could not be completed in a reasonable
associated because it is mapped to a time.
host.
Explanation: A timeout occurred before the task could
Explanation: A change VDisk cannot be associated if be completed. The relationship is continuing to enable
it is mapped to a host. access, and will have a state of idling when access is
enabled.
User response: Unmap the change VDisk from its
host, or choose a different change VDisk. User response: Check the event log for any events to
be resolved, and resubmit the task.

592 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC7173E • CMMVC7184E

CMMVC7173E Enabling access to the secondary CMMVC7178E The Remote Copy relationship could
VDisks of the Remote Copy consistency not be started in a reasonable time. It is
group could not be completed in a now stopped.
reasonable time.
Explanation: A timeout occurred before the task could
Explanation: A timeout occurred before the task could be completed.
be completed. The consistency group is continuing to
User response: Check the event log for any problems
enable access, and will have a state of idling when
that need to be resolved, and resubmit the task.
access is enabled.
User response: Check the event log for any problems
CMMVC7179E The Remote Copy consistency group
that need to be resolved, and resubmit the task.
could not be started in a reasonable
time. It is now stopped.
CMMVC7174E The task cannot be completed
Explanation: A timeout occurred before the task could
because the other cluster is running a
be completed.
software version that is not recent
enough. User response: Check the event log for any problems
that need to be resolved, and resubmit the task.
Explanation: The software version of the one of the
clusters is not supported.
CMMVC7180E The Remote Copy relationship could
User response: Upgrade the software version of the
not be started because no master change
cluster.
VDisk is defined.
Explanation: A master change VDisk must be defined
CMMVC7175E Enabling access to the secondary
for the Remote Copy relationship.
VDisks of the Remote Copy consistency
group could not be completed because User response: Define a master change VDisk.
the relationships in the group are not
mutually consistent.
CMMVC7181E The Remote Copy relationship could
Explanation: The relationships in the consistency not be started because no auxiliary
group must be mutually consistent before access to the change VDisk is defined.
secondary VDisks can be enabled.
Explanation: An auxiliary change VDisk must be
User response: Ensure that the relationships in the defined for the Remote Copy relationship.
Remote Copy consistency group are mutually
consistent. User response: Define an auxiliary change VDisk.

CMMVC7176E The Remote Copy relationship could CMMVC7182E The Remote Copy consistency group
not be added to the consistency group could not be started because no master
because the cycling modes do not change VDisk is defined.
match. Explanation: A master change VDisk must be defined
Explanation: The cycling modes of the Remote Copy for the Remote Copy consistency group.
relationship and the consistency group to which it is User response: Define a master change VDisk.
being added must match.
User response: Ensure that the cycling modes match. CMMVC7183E The Remote Copy consistency group
could not be started because no
CMMVC7177E The Remote Copy relationship could auxiliary change VDisk is defined.
not be added to the consistency group Explanation: An auxiliary change VDisk must be
because the cycling periods do not defined for the Remote Copy consistency group.
match.
User response: Define an auxiliary change VDisk.
Explanation: The cycling periods of the Remote Copy
relationship and the consistency group to which it is
being added must match. CMMVC7184E The Remote Copy consistency group
could not be started because no
User response: Ensure that the cycling periods match. auxiliary change VDisk is defined.
Explanation: An auxiliary change VDisk must be
defined for a Remote Copy consistency group.
User response: Define an auxiliary change VDisk.

Chapter 30. Command-line interface messages 593

CMMVC7185E • CMMVC8064E

User response: Set the service IP via DHCP without

CMMVC7185E The change VDisk could not be
fallback enabled. SVC and V7000 do not support the
associated because the Metro Mirror or
fallback option.
Global Mirror relationship has a VDisk
on this cluster that is in a different I/O
group. CMMVC8061E The command failed because the
hardware configuration of the local
Explanation: The I/O group of the change VDisk
cluster is not compatible with the
conflicts with an I/O group in the relationship with
software of a partnered cluster.
which an association was attempted.
Explanation: The software version of the local cluster
User response: Ensure that no conflicting I/O groups
is newer than the software version of a partnered
exist.
cluster, and additional hardware has been enabled that
is not supported by the older software on the partnered
CMMVC7186E The Remote Copy relationship was cluster.
not created because the master virtual
User response: Either upgrade the software on the
disk (VDisk) is in a file system.
partnered cluster, or turn off the new hardware on the
Explanation: The specified task cannot be performed local cluster, or stop the remote copy relationship with
while the master VDisk is in a file system. the remote cluster. Use the CLI command
chnodehardware -legacy to disable hardware that is not
User response: Choose a different master VDisk, if the
supported by older software versions.
specified VDisk cannot be removed from the file
system.
CMMVC8062E Cannot remove the latest I/O group
from the VDisk access set.
CMMVC7187E The Remote Copy relationship was
not created because the auxiliary virtual Explanation: Running this command would remove
disk (VDisk) is in a file system. access to all of the I/O groups in the access set.
Explanation: The specified task cannot be performed User response: Either modify the I/O group list so
while the auxiliary VDisk is in a file system. that it does not include all the I/O groups in the access
set, or add more I/O groups to the access set before
User response: Choose a different auxiliary VDisk, if
running the command again.
the specified VDisk cannot be removed from the file
system.
2 CMMVC8063E The command failed because the
2 VDisk is associated with a file system
CMMVC7188E The command failed because the
2 and your requested action can not be
master virtual disk (VDisk) is in a file
2 completed under your current user role.
system.
2 Explanation: You are attempting to complete an action
Explanation: The specified task cannot be performed
2 on a VDisk that is associated with a file system.
on a master VDisk while it is in a file system.
2 However, you do not possess the required role for file
User response: Choose a different master VDisk, if the 2 system actions.
specified VDisk cannot be removed from the file
2 User response: Execute command through SONAS
system.
2 VDisk command.

CMMVC7189E The change VDisk could not be

2 CMMVC8064E The command failed because the
associated because it is in a file system.
2 VDisk is associated with a file system
Explanation: The specified change VDisk cannot be 2 and only the real capacity of a
associated while it is in a file system. 2 compressed file system VDisk can be
2 changed.
User response: Choose a different change VDisk, if the
specified VDisk cannot be removed from the file 2 Explanation: You are attempting to resize a VDisk that
system. 2 is associated with a file system. However, you can only
2 resize the real capacity of a file system VDisk if it is
2 compressed.
CMMVC8060E DHCP fallback is not supported on
this platform. 2 User response: The command cannot be completed on
2 this VDisk. It will only succeed with a VDisk that is not
Explanation: User tried to set the service IP via DHCP 2 associated with a file system or a with a compressed
with fallback enabled. This platform does not support 2 file system Vdisk.
the fallback option.

594 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
 CMMVC8065E • CMMVC8071E

2 CMMVC8065E The action failed because the 2 higher level after the cluster was prepared with a lower
2 specified port is for management only.
2 level package.

2 Explanation: The action failed because the specified 2 User response: The user must abort the current
2 port is for management only. 2 software upgrade that is in progress and re-prepare
2 with the desired software upgrade package.
2 User response: Try another port which is not marked
2 as management_only in the output of lsportip.
2 CMMVC8069E The attempt to prepare the cluster for
2 software upgrade has failed because the
2 CMMVC8066E The action failed because the 2 previous upgrade is in prepare_failed
2 specified port is not installed. 2 state. The previous upgrade must first
2 be aborted before reattempting the
2 Explanation: The action failed because the specified
2 upgrade.
2 port is not installed.
2 Explanation: The current status of
2 User response: Use a port that is shown in the output
2 lssoftwareupgradestatus reports the upgrade as
2 of lsportip but which is not marked as
2 prepare_failed. This is an indication the user has
2 management_only.
2 already attempted to prepare a software upgrade, or
2 started a software upgrade and in either scenario, the
2 CMMVC8067E The attempt to add the node into the 2 prepare has failed due to offline vdisks. The cache flush
2 cluster has failed because the node is in 2 has failed.
2 paced ccu mode and the cluster must be
2 User response: The user needs to correct the error that
2 prepared for upgrade using the same
2 caused the prepare to fail. Offline vdisks are the most
2 package as is currently installed on the
2 likely cause, also node resets may cause the prepare to
2 paced ccu node.
2 fail too. Then the upgrade must be aborted with the
2 Explanation: The paced ccu upgrade requires that the 2 applysoftware -abort command, then the user should
2 cluster be prepared for upgrade first. The user is using 2 reattempt the upgrade.
2 paced ccu/manual upgrade mode and they are trying
2 to add a node into the cluster at the latest code level
2 CMMVC8070E The applysoftware prepare timed out
2 (they wish to ultimately end up at), however the code
2 because an attempt to make the virtual
2 level of the node they are trying to add requires that
2 disk cache empty took too long. The
2 the cluster is prepared for upgrade before attempting
2 command will be completed
2 the addnode command, or the cluster is already
2 asynchronously. Use
2 prepared but the cluster was prepared at a different
2 lssoftwareupgradestatus to monitor the
2 code level from the version of software on the adding
2 progress.
2 node.
2 Explanation: The applysoftware prepare timed out
2 User response: The user must prepare the cluster for
2 because an attempt to make the virtual disk cache
2 upgrade with the same software version as the paced
2 empty took too long. The command will be completed
2 ccu node being added, therefore the user must either
2 asynchronously. Use lssoftwareupgradestatus to
2 abort the upgrade and re-prepare the cluster with the
2 monitor the progress. The state will be reported as
2 correct package, or the user must install the correct
2 prepared when successfully completed.
2 version of code on the node they want as a paced ccu
2 so it matches the cluster version. Or if the user didn't 2 User response: Wait until the prepare completes and
2 prepare the cluster, then prepare the cluster with the 2 lssoftwareupgradestatus reports prepared.
2 same code as the paced ccu node.
2 CMMVC8071E The software upgrade package
2 CMMVC8068E The attempt to prepare the cluster for 2 supplied cannot be installed using
2 software upgrade to the requested 2 service state whilst maintaining the
2 software package has failed because the 2 cluster configuration on this node. To
2 cluster has already been prepared with a 2 maintain the cluster configuration on
2 different software package level. The 2 this node, this package can only be
2 software upgrade must first be aborted 2 installed with applysoftware or
2 before reattempting the software 2 pacedccu mode. This package can be
2 upgrade. 2 installed in service state using the
2 -ignore flag, however the cluster state
2 Explanation: The user has prepared the software
2 will be destroyed and cluster
2 upgrade with one level package and then attempted to
2 configuration will be lost from the
2 prepare the upgrade with a different, higher level
2 node.
2 package or attempted to automate the upgrade to a
2 Explanation: A software upgrade from 6.4.0.x to

Chapter 30. Command-line interface messages 595

 CMMVC8072E • CMMVC8077E

2 7.1.0.x cannot be issued using service state without

2 CMMVC8076E The entry in the event log cannot be
2 using the -ignore flag. Since -ignore removes the
2 fixed because it has expired or is in the
2 cluster configuration from the node, to maintain the
2 monitoring state.
2 cluster configuration the package can only be installed
2 with automated applysoftware or manual mode paced 2 Explanation: The entry in the event log cannot be
2 ccu. -ignore should not be used without understanding 2 fixed because it has expired or is in the monitoring
2 the consequences because it is a very dangerous 2 state.
2 command.
2 User response: Expired and monitoring entries in the
2 User response: Use the correct procedure to upgrade 2 event log cannot be fixed.
2 to the software package.
2 CMMVC8077E The MTM format must be XXXX-YYY
2 CMMVC8072E Access iogrp parameter not valid 2 where X is a numeric value, and Y is
2 when creating a filesystem vdisk. 2 numeric or upper case character.
2 Explanation: Access iogrp parameter not valid when 2 Explanation: The user has attempted to change the
2 creating a filesystem vdisk. 2 MTM but provided an incorrect format.
2 User response: Rerun mkvdisk without the 2 User response: Reissue the command with the MTM
2 -accessiogrp parameter or without the -filesystem 2 with the correct format. The format must be XXXX-YYY
2 parameter. 2 where XXXX are numeric values and YYY are
2 alphanumeric characters. Any alphabetic characters
2 must be upper case.
2 CMMVC8073E Host cannot be removed as there is a
2 vdisk that is accessible from multiple
2 iogrps including one of the iogrps
2 specified.
2 Explanation: If a vdisk is mapped to a host, it must be
2 mapped in all of the iogrps in which it is accessible.
2 The rmhostiogrp command fails if it would leave the
2 system in this state.
2 User response: Use lshostvdiskmap to find the list of
2 vdisks that are mapped to the host in multiple iogrps.
2 Then for each one either a) remove the host/vdisk
2 mapping or b) remove the iorgp that the host is being
2 removed from the vdisk's access iogrp set.

2 CMMVC8074E The entry in the event log cannot be

2 fixed because the given sequence
2 number is out of range.
2 Explanation: The event log entry sequence number
2 must be in the range 100 to 9,999,999 inclusive.
2 User response: Please supply a valid event log entry
2 sequence number in the range 100 to 9,999,999
2 inclusive.

2 CMMVC8075E An entry with the given sequence

2 number cannot be found in the event
2 log.
2 Explanation: The fix request has failed because an
2 entry with the given sequence number cannot be found
2 in the event log.
2 User response: Please supply a sequence number of
2 an entry that exists in the event log.

596 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Appendix. Accessibility
Accessibility features help a user who has a physical disability, such as restricted mobility or limited
vision, to use software products successfully.

Features

This list includes the major accessibility features in the management GUI:
v You can use screen-reader software and a digital speech synthesizer to hear what is displayed on the
screen. The following screen reader has been tested: JAWS 11.
v Most of the GUI features are accessible by using the keyboard. For those features that are not
accessible, equivalent function is available by using the command-line interface (CLI).
v When setting or changing an IP address on the SAN Volume Controller front panel, you can disable
the fast increase function to reduce the address scrolling speed of the up and down buttons to two
seconds. This feature is documented in the topic that discusses initiating cluster (system) creation from
the front panel, which is located in the IBM System Storage SAN Volume Controller Information
Center and the IBM System Storage SAN Volume Controller Software Installation and Configuration Guide.

Navigating by keyboard

You can use keys or key combinations to perform operations and initiate many menu actions that can
also be done through mouse actions. You can navigate the management GUI and help system from the
keyboard by using the following key combinations:
v To navigate between different GUI panels, select the Low-graphics mode option on the GUI login panel.
You can use this option to navigate to all the panels without manually typing the web addresses.
v To go to the next frame, press Ctrl+Tab.
v To move to the previous frame, press Shift+Ctrl+Tab.
v To navigate to the next link, button, or topic within a panel, press Tab inside a frame (page).
v To move to the previous link, button, or topic within a panel, press Shift+Tab.
v To select GUI objects, press Enter.
v To print the current page or active frame, press Ctrl+P.
v To expand a tree node, press the Right Arrow key. To collapse a tree node, press the Left Arrow key.
v To scroll all the way up, press Home; to scroll all the way down, press End.
v To go back, press Alt+Left Arrow key.
v To go forward, press Alt+Right Arrow key.
v For actions menus:
– Press Tab to navigate to the grid header.
– Press the Left or Right Arrow keys to reach the drop-down field.
– Press Enter to open the drop-down menu.
– Press the Up or Down Arrow keys to select the menu items.
– Press Enter to launch the action.
v For filter panes:
– Press Tab to navigate to the filter panes.
– Press the Up or Down Arrow keys to change the filter or navigation for nonselection.
– Press Tab to navigate to the magnifying glass icon in the filter pane and press Enter.
– Type the filter text.

© Copyright IBM Corp. 2003, 2012 597

 – Press Tab to navigate to the red X icon and press Enter to reset the filter.
v For information areas:
– Press Tab to navigate to information areas.
– Press Tab to navigate to the fields that are available for editing.
– Type your edit and press Enter to issue the change command.

Accessing the publications

You can find the HTML version of the IBM System Storage SAN Volume Controller information at the
following website:

publib.boulder.ibm.com/infocenter/svc/ic/index.jsp

You can access this information using screen-reader software and a digital speech synthesizer to hear
what is displayed on the screen. The information was tested using the following screen reader: JAWS
Version 10 or later.

598 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program,
or service that does not infringe any IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or
service.

IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some
states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this
statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

© Copyright IBM Corp. 2003, 2012 599

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
Almaden Research
650 Harry Road
Bldg 80, D3-304, Department 277
San Jose, CA 95120-6099
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before the
products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

600 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.

Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, and/or other countries.

Intel, Intel logo, Intel Xeon, and Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.

Notices 601
602 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
Index
Special characters C CLI commands
chcluster
-filtervalue argument xxvi cancellivedump command 365 modifying cluster (system) IP
catauditlog command 107 address 68
caterrlog command 145 chcurrentuser 76
A caterrlogbyseqnum command 145
cfgportip command 117
chfcmap 37
about this document chlicense 14
changing chsystem
sending comments xvii
passwords 81 changing clustered system gateway
accessibility
charray command 89 address 69
keyboard 597
charraymember command 90 changing relationship
repeat rate
chauthservice command 449 bandwidth 69
up and down buttons 597
chcluster command 119 modifying cluster (system) IP
shortcut keys 597
chcontroller commands 165 address 68
accessing
chcurrentuser command 451 chuser 76
publications 597
chdrive command 168 chusergrp 75
addcontrolenclosure command 191
chemail command 175 lscluster
addhostiogrp command 227
chemailserver command 176 changing relationship
addhostport command 227
chemailuser command 177 bandwidth 69
adding
chenclosure command 191 modifying clustered (system) IP
nodes 17
chenclosurecanister command 192 address 68
addmdisk command 375
chenclosureslot command 193 lscurrentuser 76
addnode command 115
chenclosurevpd command 429 lsfcconsistgrp 37, 38
addvdiskaccess command 474
cherrstate command 145 lsfcmap 34, 37
addvdiskcopy command 469
cheventlog command 148 lslicense 14
applydrivesoftware command 167
chfcconsistgrp command 211 lssystem
applymdisksoftware command 369
chfcmap command 211 changing clustered system gateway
applysoftware command 143, 425
chhost command 228 address 69
array commands
chiogrp command 124 displaying clustered system
charray 89
chldap command 452 properties 15
charraymember 90
chldapserver command 455 lssytem
lsarray 92
chlicense command 207 modifying clustered (system) IP
lsarrayinitprogress 95
chmdisk command 369 address 68
lsarraylba 96
chmdiskgrp command 376 lsuser 76
lsarraymember 97
chnode / chnodecanister command 127 lsusergrp 75
lsarraymembergoals 99
chnodehw / chnodecanisterhw lsvdisk 34
lsarraymemberprogress 100
command 128 mkfcconsistgrp 37
lsarraysyncprogress 101
chnodeled command 430 mkfcmap 34
mkarray 102
chpartnership command 383 mkuser 76
overview 89
chquorum command 370 mkusergrp 75
recoverarray 103
chrcconsistgrp command 384 prestartfcconsistgrp 38
recoverarraybysystem 104
chrcrelationship command 385 rmuser 76
rmarray 105
chserviceip command 430 rmusergrp 75
audit log commands
chsnmpserver command 178 setlocale 81
catauditlog 107
chsyslogserver command 179 startfcconsistgrp 38
dumpauditlog 108
chsystem command 119 cluster
lsauditlogdumps 109
chsystemip command 122 configuring for iSCSI 70
overview 107
chuser command 456 cluster commands
authentication
chusergrp command 457 cfgportip 117
SSH logins 1
chvdisk command 475 chiogrp 124
chwwnn command 432 cleardumps 129
clear command 112
B cleardumps command 129, 425
cpdumps 130
rmportip 136
backup and restore commands 111 clearerrlog command 145 settimezone 138
backup command 111 CLI (command-line interface) startstats 139
backup commands configuring PuTTY 3 stopstats 140
backup 111 getting started 13 cluster date and time
clear 112 preparing SSH client on AIX or setting 14
help 112 Linux 6 cluster diagnostic and service-aid
preparing SSH client on Windows 2 commands
using to update clustered system cheventlog 148
license 14

© Copyright IBM Corp. 2003, 2012 603

cluster diagnostic and service-aid commands (continued) commands (continued)
commands (continued) addhostport 227 finderr 147
dumperrlog 146 addmdisk 375 getstatus 458
finderr 147 addnode 115 help 112
overview 143 addvdiskaccess 474 includemdisk 373
writesernum 162 addvdiskcopy 469 installsoftware 434
cluster error log applydrivesoftware 167 leavecluster 435
displaying 145 applymdisksoftware 369 licensing 207
clustered system applysoftware 143, 425 livedump 365
authentication backup 111 ls2145dumps 235, 427
configuring clustered system cancellivedump 365 lsarray 92
iSCSI 72 catauditlog 107 lsarrayinitprogress 95
configuring iSCSI authentication 72 caterrlog 145 lsarraylba 96
recovering nodes 54 caterrlogbyseqnum 145 lsarraymember 97
clustered system commands cfgportip 117 lsarraymembergoals 99
addnode 115 charray 89 lsarraymemberprogress 100
chnode/ chnodecanister 127 charraymember 90 lsarraysyncprogress 101
chsystem 119 chauthservice 449 lsauditlogdumps 109
chsystemip 122 chcluster 119 lscimomdumps 235, 427
detectmdisk 132 chcontroller 165 lsclustervpd 427
mkcluster 436 chcurrentuser 451 lscmdstatus 411
ping 133 chdrive 168 lscontrolenclosurecandidate 198
setpwdreset 137 chemail 175 lscontroller 244
setsystemtime 137 chemailserver 176 lscontrollerdependentvdisks 248
stopsystem 140 chemailuser 177 lscopystatus 235
clustered system diagnostic and chenclosure 191 lscurrentuser 248
service-aid commands chenclosurecanister 192 lsdependentvdisks 361
applysoftware 143 chenclosureslot 193 lsdiscoverystatus 249
clearerrlog 145 chenclosurevpd 429 lsdrive 169
setlocale 161, 439 cherrstate 145 lsdrivelba 171
svqueryclock 162 cheventlog 148 lsdumps 250
clustered systems 242, 452, 455, 460, 461, chfcconsistgrp 211 lsemailserver 252
462, 464, 466 chfcmap 211 lsemailuser 253
configuring iSCSI alias 71 chhost 228 lsenclosure 194
deleting nodes 65 chiogrp 124 lsenclosurebattery 196
gateway address chlicense 207 lsenclosurecanister 198
changing 69 chmdisk 369 lsenclosurepsu 201
modifying iSCSI alias 71 chmdiskgrp 376 lsenclosureslot 202
properties 15 chnode/ chnodecanister 127 lserrlogbyfcconsistgrp 147
removing nodes 65 chnodehw / chnodecanisterhw 128 lserrlogbyfcmap 147
shutting down 82 chnodeled 430 lserrlogbyhost 147
updating chpartnership 383 lserrlogbyiogrp 147
license 14 chquorum 370 lserrlogbymdisk 147
viewing chrcconsistgrp 384 lserrlogbymdiskgp 147
license 14 chrcrelationship 385 lserrlogbynode 147
clustered sytem commands chserviceip 430 lserrlogbyrcconsistgrp 147
rmnode / rmnodecanister 134 chsnmpserver 178 lserrlogbyrcrelationship 148
clusters chsyslogserver 179 lserrlogbyvdisk 148
error logs 82 chsystem 119 lserrlogdumps 148, 427
logs 82 chsystemip 122 lseventlog 148
viewing feature logs 82 chuser 456 lsfabric 253
command 172 chusergrp 457 lsfcconsistgrp 255
command-line interface (CLI) chvdisk 475 lsfcmap 257
configuration 2 chwwnn 432 lsfcmapcandidate 259
configuring PuTTY 3 clear 112 lsfcmapdependentmaps 261
getting started 13 cleardumps 129, 425 lsfcmapprogress 260
preparing SSH clients on AIX or clearerrlog 145 lsfeaturedumps 262, 427
Linux 6 cpdumps 130 lsfiles 411
preparing SSH clients on Windows 2 cpfiles 433 lsfreeextents 262
using to update clustered system detectmdisk 132 lshardware 412
license 14 dumpallmdiskbadblocks 371 lshbaportcandidate 263
using to view clustered system dumpauditlog 108 lshost 263
license 14 dumperrlog 146, 425 lshostiogrp 266
commands 452, 455, 460, 461, 462, 464, dumpinternallog 209 lshostvdiskmap 267
466 dumpmdiskbadblocks 372 lsiogrp 269
addcontrolenclosure 191 exit 427 lsiogrpcandidate 271
addhostiogrp 227 expandvdisksize 479 lsiogrphost 271

604 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
commands (continued) commands (continued) commands (continued)
lsiostatsdumps 272, 427 mkfcmap 214 startemail 187
lsiotracedumps 272, 427 mkhost 230 startfcconsistgrp 220
lsiscsiauth 272 mkmdiskgrp 377 startfcmap 222
lslicense 274 mkpartnership 389 startrcconsistgrp 396
lslivedump 365, 366 mkrcconsistgrp 390 startrcrelationship 398
lsmdisk 275 mkrcrelationship 390 startservice 441
lsmdiskcandidate 281 mksnmpserver 182 startstats 139
lsmdiskdumps 280, 427 mksyslogserver 183 starttrace 448
lsmdiskextent 282 mkuser 458 stopcluster 140
lsmdiskgrp 284 mkusergrp 463 stopemail 188
lsmdisklba 280 mkvdisk 481 stopfcconsistgrp 223
lsmdiskmember 288 mkvdiskhostmap 489 stopfcmap 224
lsmigrate 289 movevdisk 477 stopnode 442
lsnodecandidate 294 ping 133 stoprcconsistgrp 400
lsnodedependentvdisks 295 prestartfcconsistgrp 216, 220 stoprcrelationship 402
lsnodehw / lsnodecanisterhw 295 prestartfcmap 218 stopservice 442
lsnodestats / lsnodecanisterstats 298 recoverarray 103 stopstats 140
lsnodevpd / lsnodecanistervpd 304 recoverarraybysystem 104 stopsystem 140
lspartnership command 310 recovervdisk 491 stoptrace 448
lspartnershipcandidate 247, 311 recovervdiskbyiogrp 492 svqueryclock 162
lsportfc 316 recovervdiskbysystem 491 switchrcconsistgrp 403
lsportip 312 repairsevdiskcopy 493 switchrcrelationship 404
lsquorum 318 repairvdiskcopy 493 t3recovery 443
lsrcconsistgrp 319 rescuenode 437 testemail 188
lsrcrelationship 322 resetpassword 438 triggerenclosuredump 205
lsrcrelationshipcandidate 325 restartservice 438 triggerlivedump 367
lsrcrelationshipprogress 326 restore 113 triggermdiskdump 375
lsrepairsevdiskcopyprogress 327 rmarray 105 user management 449
lsrepairvdiskcopyprogress 328 rmemailserver 185 writesernum 162
lsrmvdiskdependentmaps 330 rmemailuser 185 commands/ lsnodecanister
lsroute 331 rmfcconsistgrp 219 lsnode 290
lsservicenodes 415 rmfcmap 220 comments, sending xvii
lsservicerecommendation 417 rmhost 231 communications
lsservicestatus 153, 417 rmhostiogrp 232 determining between hosts and virtual
lssevdiskcopy 332 rmhostport 233 disks 48
lssnmpserver 335 rmmdisk 379 configuring
lssoftwaredumps 336, 429 rmmdiskgrp 380 iSNS server address 72
lssoftwareupgradestatus 336 rmnode / rmnodecanister 134 PuTTY 3
lssyslogserver 160 rmpartnership 393 remote authentication service using
lssystem 236 rmportip 136 CLI 73, 74
lssystemip 240 rmrcconsistgrp 394 remote authentication service with
lssystemstats 242 rmrcrelationship 395 Lightweight Directory Access
lstimezones 337 rmsnmpserver 186 Protocol (LDAP) using CLI 74
lsuser 338 rmsyslogserver 186 remote authentication service with
lsusergp 339 rmuser 465 Tivoli Integrated Portal (TIP) using
lsvdisk 340 rmusergrp 465 CLI 73
lsvdiskaccess 348 rmvdisk 495 Connecting to the CLI using OpenSSH 8
lsvdiskcopy 349 rmvdiskaccess 497 consistency group
lsvdiskdependentmaps 352 rmvdiskcopy 497 deleting FlashCopy 40
lsvdiskextent 353 rmvdiskhostmap 498 stoppingFlashCopy 39
lsvdiskfcmapcopies 354 sendinventoryemail 187 consistency groups, Global Mirror
lsvdiskfcmappings 355 service information 411 creating 43
lsvdiskhostmap 355 service task 429 deleting 44
lsvdisklba 357 setdisktrace 445 modifying 43
lsvdiskmember 358 setlocale 161, 439 starting and stopping 44
lsvdiskprogress 360 setpacedccu 440 consistency groups, Metro Mirror
lsvdisksyncprogress 360 setpwdreset 137 creating 43
metadata 435 setquorum 374 deleting 44
migrateexts 407 setsystemtime 137 modifying 43
migratetoimage 408 settempsshkey 440 starting and stopping 44
migratevdisk 409 settimezone 138 controller commands
mkarray 102 settrace 446 chcontroller 165
mkcluster 436 showtimezone 364 overview 165
mkemailserver 180 shrinkvdisksize 499 controllers
mkemailuser 181 snap 441 changing 165
mkfcconsistgrp 213 splitvdiskcopy 501 command 165, 244

Index 605
cpdumps command 130 email and event notification commands FlashCopy (continued)
cpfiles command 433 (continued) mappings
creating chsyslogserver 179 adding to consistency group 37
host mappings 33 mkemailserver 180 creating using CLI 34
creating users 8 mksnmpserver 182 memory 27
current time zone 364 mksyslogserver 183 stopping consistency group 39
rmemailserver 185 FlashCopy commands
rmsnmpserver 186 chfcconsistgrp 211
D rmsyslogserver 186
email commands
chfcmap 211
mkfcconsistgrp 213
data migration progress
chemail 175 mkfcmap 214
viewing 289
chemailuser 177 overview 211
date and time
lsemailuser 253 prestartfcconsistgrp 216, 220
setting cluster 14
mkemailuser 181 prestartfcmap 218
deleting
overview 175 rmfcconsistgrp 219
nodes 65
rmemailuser 185 rmfcmap 220
dependent maps
sendinventoryemail 187 startfcconsistgrp 220
viewing 261
startemail 187 startfcmap 222
detectmdisk command 132
stopemail 188 stopfcconsistgrp 223
determining
testemail 188 stopfcmap 224
communications between hosts and
email servers FlashCopy progress 260
virtual disks 48
setting up free extents 262
diagnostic and service-aid commands
CLI 80 front panel
clearerrlog
enclosure commands password 16
clustered system 145
lsenclosure 194
cluster 143
lsenclosurecanister 198
cheventlog 148
svqueryclock 162
lsenclosurepsu 201
lsenclosureslot 202
G
writesernum 162 gateway address
overview 191
clustered system changing 69
error log dump files
applysoftware 143 Generating an SSH key pair using
viewing 427
setlocale 161, 439 OpenSSH 7
error notification
dumperrlog getstatus command 458
SYSLOG 78
cluster 146 getting started
event notification commands
finderr using the CLI (command-line
overview 175
cluster 147 interface) 13
exit command 427
overview 143 using the command-line interface
expanding
discovering (CLI) 13
virtual disks 57
managed disks 21 Global Mirror
expandvdisksize command 479
disks memory 27
extent allocation
migrating 61 Global Mirror commands
viewing 282
migrating image mode 65 chpartnership 383
extents
documentation chrcconsistgrp 384
migrating
improvement xvii chrcrelationship 385
using the CLI (command-line
drive commands mkpartnership 389
interface) 60
applydrivesoftware 167 mkrcconsistgrp 390
chdrive 168 mkrcrelationship 390
lsdrive 169 overview 383
lsdrivelba 171 F rmpartnership 393
overview 167 featurization settings 274 rmrcconsistgrp 394
dump files filtering rmrcrelationship 395
listing 235, 427 FlashCopy startrcconsistgrp 396
lsfeaturedumps 262 consistency groups 255 startrcrelationship 398
dumpallmdiskbadblocks command 371 mappings 257, 330, 352, 354 stoprcconsistgrp 400
dumpauditlog command 108 finderr command 147 stoprcrelationship 402
dumperrlog command 146, 425 FlashCopy switchrcconsistgrp 403
dumpinternallog command 209 consistency group switchrcrelationship 404
dumpmdiskbadblocks command 372 deleting using CLI 40
stopping using CLI 39
consistency groups H
E creating using CLI 37
preparing using the CLI 38
help command 112
email host bus adaptor, unconfigured
starting using the CLI 38
inventory reports 79 viewing 263
deleting consistency group 40
setting up event notification 79 host commands
deleting mapping 36
email and event notification commands addhostiogrp 227
mapping
chemailserver 176 addhostport 227
deleting using CLI 36
chsnmpserver 178 addvdiskaccess 474
stopping 36

606 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
host commands (continued) information commands (continued) inventory commands (continued)
chhost 228 lshardware 412 startemail 187
mkhost 230 lshbaportcandidate 263 stopemail 188
movevdisk 477 lshost 263 testemail 188
overview 227 lshostiogrp 266 IP addresses
rmhost 231 lshostvdiskmap 267 changing 68
rmhostiogrp 232 lsiogrp 269 iSCSI alias
rmhostport 233 lsiogrpcandidate 271 configuring 71
rmvdiskaccess 497 lsiogrphost 271 modifying 71
host I/O group 266 lsiostatsdumps 272 iSNS server address
host objects lsiotracedumps 272 configuring 72
configuring using CLI 32 lsiscsiauth 272
hosts lslicense 274
commands 227
determining VDisk names 48
lsmdisk 275
lsmdiskcandidate 281
K
keyboard
mapping volumes 33 lsmdiskdumps 280
accessibility 597
viewing 263 lsmdiskextent 282
lsmdiskgrp 284
lsmdisklba 280
I lsmdiskmember 288 L
lsmigrate 289 language
image mode volumes
lsnodecandidate 294 changing locale 81
converting to managed mode
lsnodedependentvdisks 295 ldapserver command 461
using CLI (command-line
lsnodehw / lsnodecanister 295 legal notices
interface) 64
lsnodestats / lsnodecanisterstats 298 Notices 599
includemdisk command 373
lsnodevpd / lsnodecanistervpd 304 trademarks 601
information
lspartnership command 310 license
center xiv
lspartnershipcandidate 247, 311 changing settings 207
information commands 330, 354, 452,
lsportfc 316 updating
455, 460, 461, 462, 464, 466
lsportip 312 using the CLI (command-line
addcontrolenclosure 191
lsquorum 318 interface) 14
caterrlog 145
lsrcconsistgrp 319 viewing 274
caterrlogbyseqnum 145
lsrcrelationship 322 licensing commands 207
chenclosure 191
lsrcrelationshipcandidate 325 chlicense 207
chenclosurecanister 192
lsrcrelationshipprogress 326 dumpinternallog 209
chenclosureslot 193
lsroute 331 list dump command 87
chnodehw / chnodecanisterhw 128
lssnmpserver 335 livedump commands 365
ls2145dumps 235
lssoftwaredumps 336 cancellivedump 365
lscimomdumps 235
lssyslogserver 160 lslivedump 365, 366
lscontrolenclosurecandidate 198
lssystem 236 triggerlivedump 367
lscontroller 244
lssystemip 240 locale
lscopystatus 235
lssystemstats 242 changing 81
lscurrentuser 248
lstimezones 337 ls2145dumps command 235, 427
lsdependentvdisks 361
lsuser 338 lsarray command 92
lsdiscoverystatus 249
lsusergrp 339 lsarrayinitprogress command 95
lsdumps 250
lsvdisk 340 lsarraylba command 96
lsemailserver 252
lsvdiskaccess 348 lsarraymember command 97
lsenclosurebattery 196
lsvdiskdependentmaps 352 lsarraymembergoals command 99
lserrlogbyfcconsistgrp 147
lsvdiskextent 353 lsarraymemberprogress command 100
lserrlogbyfcmap 147
lsvdiskfcmappings 355 lsarraysyncprogress command 101
lserrlogbyhost 147
lsvdiskhostmap 355 lsauditlogdumps command 109
lserrlogbyiogrp 147
lsvdisklba 357 lscimomdumps command 235, 427
lserrlogbymdisk 147
lsvdiskmember 358 lsclustervpd command 427
lserrlogbymdiskgp 147
lsvdiskprogress 360 lscmdstatus command 411
lserrlogbynode 147
overview 235 lscontrolenclosurecandidate
lserrlogbyrcconsistgrp 147
showtimezone 364 command 198
lserrlogbyrcrelationship 148
stopcluster 140 lscontroller command 244
lserrlogbyvdisk 148
triggerenclosuredump 205 lscontrollerdependentvdisks
lserrlogdumps 148
information commands/ lsnodecanister command 248
lseventlog 148
lsnode 290 lscopystatus command 235
lsfabric 253
installsoftware command 434 lscurrentuser command 248
lsfcconsistgrp 255
inventory commands lsdependentvdisks command 361
lsfcmap 257
chemail 175 lsdiscoverystatus command 249
lsfcmapcandidate 259
chsystem 119 lsdrive command 169
lsfcmapdependentmaps 261
mkemailuser 181 lsdrivelba command 171
lsfcmapprogress 260
rmemailuser 185 lsdriveprogress 172
lsfeaturedumps 262
sendinventoryemail 187 lsdriveprogress command 172
lsfreeextents 262

Index 607
lsdumps command 250 lsquorum command 318 managed mode virtual disks
lsemailserver command 252 lsrcconsistgrp command 319 converting from image mode
lsemailuser command 253 lsrcrelationship command 322 using the CLI (command-line
lsenclosure command 194 lsrcrelationshipcandidate command 325 interface) 64
lsenclosurebattery command 196 lsrcrelationshipprogress command 326 mapping
lsenclosurecanister command 198 lsrepairsevdiskcopyprogress deleting FlashCopy 36
lsenclosurepsu command 201 command 327 master console
lsenclosureslot command 202 lsrepairvdiskcopyprogress configuration 2
lserrlogbyfcconsistgrp command 147 command 328 MDisk commands
lserrlogbyfcmap command 147 lsrmvdiskdependentmaps command 330 dumpallmdiskbadblocks 371
lserrlogbyhost command 147 lsroute command 331 dumpmdiskbadblocks 372
lserrlogbyiogrp command 147 lsservicenodes command 415 MDisks (managed disks)
lserrlogbymdisk command 147 lsservicerecommendation command 417 adding 25
lserrlogbymdiskgp command 147 lsservicestatus command 153, 417 volume relationships 49
lserrlogbynode command 147 lssevdiskcopy command 332 MDisks See managed disks 369, 375
lserrlogbyrcconsistgrp command 147 lssnmpserver command 335 metadata command 435
lserrlogbyrcrelationship command 148 lssoftwaredumps command 336, 429 Metro Mirror
lserrlogbyvdisk command 148 lssoftwareupgradestatus command 336 memory 27
lserrlogdumps command 148, 427 lssyslogserver command 160 Metro Mirror commands
lseventlog command 148 lssystem command 236 chpartnership 383
lsfabric command 253 lssystemip command 240 chrcconsistgrp 384
lsfcconsistgrp command 255 lssystemstats command 242 mkpartnership 389
lsfcmap command 257 lstimezones command 337 mkrcconsistgrp 390
lsfcmapcandidate command 259 lsuser command 338 mkrcrelationship 390
lsfcmapdependentmaps command 261 lsusergrp command 339 overview 383
lsfcmapprogress command 260 lsvdisk command 340 rmpartnership 393
lsfeaturedumps command 262 lsvdiskaccess command 348 rmrcconsistgrp 394
lsfeaturedumps commands 427 lsvdiskcopy command 349 rmrcrelationship 395
lsfiles command 411 lsvdiskdependentmaps command 352 startrcconsistgrp 396
lsfreeextents command 262 lsvdiskextent command 353 startrcrelationship 398
lshardware command 412 lsvdiskfcmapcopies command 354 stoprcconsistgrp 400
lshbaportcandidate command 263 lsvdiskfcmappings command 355 stoprcrelationship 402
lshost command 263 lsvdiskhostmap command 355 switchrcconsistgrp 403
lshostiogrp command 266 lsvdisklba command 357 switchrcrelationship 404
lshostvdiskmap command 267 lsvdiskmember command 358 migrateexts command 407
lsiogrp command 269 lsvdiskprogress command 360 migratetoimage command 408
lsiogrpcandidate command 271 lsvdisksyncprogress command 360 migratevdisk command 409
lsiogrphost command 271 migratingvolumes
lsiostatsdumps command 272, 427 extents
lsiotracedumps command 272
lsiotracedumps commands 427
M using the CLI (command-line
interface) 60
maintaining
lsiscsiauth command 272 migration 407
passwords 16
lsldap command 460 migration commands
managed disk commands
lslicense command 274 migrateexts 407
applymdisksoftware 369
lslivedump command 365, 366 migratetoimage 408
chmdisk 369
lsmdisk command 275 migratevdisk 409
chquorum 370
lsmdiskcandidate command 281 overview 407
includemdisk 373
lsmdiskdumps command 280, 427 mkarray command 102
lsquorum 318
lsmdiskextent command 282 mkcluster command 436
overview 369
lsmdiskgrp command 284 mkemailserver command 180
setquorum 374
lsmdisklba command 280 mkemailuser command 181
triggermdiskdump 375
lsmdiskmember command 288 mkfcconsistgrp command 213
managed disk group commands
lsmigrate command 289 mkfcmap command 214
addmdisk 375
lsnode command 290 mkhost commands 230
chmdiskgrp 376
lsnodecandidate command 294 mkldapserver command 462
mkmdiskgrp 377
lsnodedependentvdisks command 295 mkmdiskgrp command 377
overview 375
lsnodehw / lsnodecanisterhw mkpartnership command 389
rmmdisk 379
command 295 mkrcconsistgrp command 390
rmmdiskgrp 380
lsnodestats / lsnodecanisterstats mkrcrelationship command 390
managed disks
command 298 mksnmpserver command 182
viewing disks 275, 280
lsnodevpd / lsnodecanistervpd mksyslogserver command 183
viewing groups 284
command 304 mkuser command 458
managed disks (MDisks)
lspartnership command 310 mkusergrp command 463
adding 25
lspartnershipcandidate command 247, mkvdisk commands 481
discovering 21
311 mkvdiskhostmap command 489
rebalancing access 21
lsportfc command 316 movevdisk command 477
volume relationships 49
lsportip command 312

608 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
N ping command 133
plink utility
rmarray command 105
rmemailserver command 185
nodes running 4 rmemailuser command 185
adding 17, 115 port IP addresses rmfcconsistgrp command 219
addnode command 115 configuring 70 rmfcmap command 220
changing 127 prestartfcconsistgrp command 216 rmhost command 231
chnode/ chnodecanister prestartfcmap command 218 rmhostiogrp command 232
command 127 publications rmhostport command 233
deleting 65, 134 accessing 597 rmldapserver command 464
lsnodestats / lsnodecanisterstats PuTTY rmmdisk command 379
command 298 configuring 3 rmmdiskgrp command 380
removing 65 generating an SSH key pair 2 rmnode / rmnodecanister command 134
returning to clustered system 54 running the plink utility 4 rmpartnership command 393
rmnode / rmnodecanister scp (pscp) 11 rmportip command 136
command 134 PuTTY session rmrcconsistgrp command 394
statistics 298 configuring for the CLI 3 rmrcrelationship command 395
viewing 290 rmsnmpserver command 186
general details 20 rmsyslogserver command 186
Q rmuser command 465
rmusergrp command 465
O quorum disks
setting with CLI 26
rmvdisk command 495
OpenSSH, Connecting to the CLI rmvdiskaccess command 497
using 8 rmvdiskcopy command 497
OpenSSH, Generating an SSH key pair rmvdiskhostmap command 498
using 7 R running
overview reader feedback, sending xvii PuTTY plink utility 4
array commands 89 rebalancing
audit log commands 107 managed disks (MDisks) access 21
backup and restore commands 111 recoverarray command 103
recoverarraybysystem command 104
S
cluster commands 115 SAN Volume Controller
cluster diagnostic and service-aid recovering
front panel password 16
commands 143 offline volumes
properties 20
controller commands 165 using CLI 53
SAN Volume Controller library
drive commands 167 recovervdisk command 491
related publications xiv
dumps commands 87 recovervdiskbyiogrp command 492
scanning
email commands 175 recovervdiskbysystem command 491
Fibre Channel network 21
enclosure commands 191 related information xiv
rebalancing MDisk access 21
event notification commands 175 relationships, Global Mirror
scp
FlashCopy commands 211 creating 40
PuTTY application 11
host commands 227 deleting 43
secure shell
information commands 235 displaying 42
PuTTY 3
licensing commands 207 modifying 41
secure shell (SSH)
managed disk commands 369 starting and stopping 41
authenticating logins 1
managed disk group commands 375 switching 42
client
migration commands 407 relationships, Metro Mirror
AIX or Linux 6
secure shell 1 creating 40
Windows 2
service mode commands 425 deleting 43
creating keys 2
service mode information displaying 42
overview 1
commands 427 modifying 41
secure shell client
tracing commands 445 starting and stopping 41
preparing for CLI on AIX 6
user management commands 449 switching 42
preparing for CLI on Linux 7
remote authentication
security 1
configuring using CLI 73, 74
sending
P removing
nodes 65
comments xvii
partnerships, Global Mirror sendinventoryemail command 187
repairing
creating 44 service commands
space-efficient volume 53
deleting 46 chenclosurevpd 429
repairsevdiskcopy command 493
modifying 45 chnodeled 430
repairvdiskcopy command 493
starting and stopping 45 chserviceip 430
rescuenode command 437
partnerships, Metro Mirror chwwnn 432
resetpassword command 438
creating 44 installsoftware 434
restartservice command 438
deleting 46 leavecluster 435
restore command 113
modifying 45 lscmdstatus 411
restore commands
starting and stopping 45 lsfiles 411
clear 112
passwords lsservicenodes 415
help 112
changing 81 lsservicerecommendation 417
restore 113
front panel 16 lsservicestatus 153, 417

Index 609
service commands (continued)
metadata 435
SSH (secure shell)
client system
U
rescuenode 437 preparing to issue CLI Updating
resetpassword 438 commands 6 license
restartservice 438 SSH See secure shell 1 using the CLI (command-line
setpacedccu 440 SSH keys interface) 14
settempsshkey 440 creating 2 upgrading
snap 441 startemail command 187 software using the command-line
startservice 441 startfcconsistgrp command 220 interface (CLI) 83
stopnode 442 startfcmap command 222 user groups
stopservice 442 startrcconsistgrp command 396 creating using CLI 75
t3recovery 443 startrcrelationship command 398 modifying using CLI 75
service information commands 411 startservice command 435, 441 user management commands 449
service mode startstats command 139 chauthservice 449
commands 425 starttrace command 448 chcurrentuser 451
information commands 427 statistics 242, 452, 455, 460, 461, 462, chuser 456
service mode commands 464, 466 chusergrp 457
applysoftware 425 stopcluster command 140 mkuser 458
cleardumps 425 stopemail command 188 mkusergrp 463
dumperrlog 425 stopfcconsistgrp command 223 rmuser 465
exit 427 stopfcmap command 224 rmusergrp 465
overview 425 stopnode command 442 users
service mode information commands stopping creating 8
ls2145dumps 427 FlashCopy mapping 36 creating using CLI 76
lscimomdumps 427 stoprcconsistgrp command 400 modifying using CLI 76
lsclustervpd 427 stoprcrelationship command 402
lserrlogdumps 427 stopservice command 442
lsfeaturedumps 427 stopstats command 140 V
lsiostatsdumps 427 stopsystem command 140 validating
lsiotracedumps 427 stoptrace command 448 volume copies 51
lsmdiskdumps 427 storage pools VDisk (virtual disks)
lssoftwaredumps 429 creating using the CLI 22 determining mappings 48
overview 427 subnet mask VDisks (virtual disks)
service task commands 429 changing 69 determining name of 48
cpfiles 433 Summary of changes for GC27-2287-03 expanding 57
setdisktrace command 445 Command-Line Interface User's VDisks See virtual disks 469
setlocale command 161, 439 Guide xi viewing
setpacedccu command 440 svqueryclock command 162 clustered systems 236
setpwdreset command 137 switchrcconsistgrp command 403 Global Mirror
setquorum command 374 switchrcrelationship command 404 consistency groups 319
setsystemtime command 137 SYSLOG 78 relationships 322
settempsshkey command 440 system log I/O groups 269
settimezone command 138 information 78 Metro Mirror
setting consistency groups 319
quorum disks 26 relationships 322
settings
email server 80
T Viewing
t3recovery command 443 license
error notification 78 using the CLI (command-line
testemail command 188
event notification 77 interface) 14
testldapserver command 466
settrace command 446 virtual disk commands
time
shortcut keys expandvdisksize 479
setting clustered system
accessibility 597 lsrepairsevdiskcopyprogress 327
using the CLI (command-line
keyboard 597 lsrepairvdiskcopyprogress 328
interface) 13
showtimezone command 364 recovervdisk 491
time zones 337
shrinkvdisksize command 59, 499 recovervdiskbyiogrp 492
tracing commands
snap command 441 recovervdiskbysystem 491
overview 445
SNMP traps 77 repairvdiskcopy 493
setdisktrace 445
software rmvdiskcopy 497
settrace 446
upgrading using the command-line shrinkvdisksize 499
starttrace 448
interface (CLI) 83 virtual disks
stoptrace 448
software packages removing 497
trademarks 601
listing 429 virtual disks (VDisks)
triggerenclosuredump command 205
viewing 336 determining mappings 48
triggerlivedump command 367
splitvdiskcopy command 501 determining name of 48
triggermdiskdump command 375
virtual disks commands
overview 469

610 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide
vital product data (VPD)
listing 427
viewing 304
volume
copying 469
creating 28
deleting a copy 31
expanding 58
managed disks (MDisks)
relationships 49
MDisks (managed disks)
relationships 49
migrating 63
shrinkvdisksize command 59
viewing FlashCopy mappings 355
volume commands
addvdiskcopy 469
chvdisk 475
lscontrollerdependentvdisks 248
lssevdiskcopy 332
lsvdiskcopy 349
lsvdisksyncprogress 360
mkvdisk 481
mkvdiskhostmap 489
repairsevdiskcopy 493
rmvdisk 495
rmvdiskhostmap 498
splitvdiskcopy 501
volume copies
validating 51
volume extent
viewing 353
Volume Mirroring
memory 27
volume) 58
volumes
adding a copy 30
converting
from image mode to managed
mode 64
creating 481
listing node dependent 47
recovering 55
recovering from offline
using CLI 53
using the CLI 55
viewing 340
viewing disks 357

W
writesernum command 162

Index 611
612 SAN Volume Controller and Storwize V7000: Command-Line Interface User's Guide



Printed in USA

GC27-2287-03