SMcli and Script Commands Quick Reference For SANtricity Ver 9.25 ES1790-0-E1
SMcli and Script Commands Quick Reference For SANtricity Ver 9.25 ES1790-0-E1
Storage Manager
Command Line Interface and
Script Commands
Quick Reference for Version 9.25
ES1790-0-E1, First Edition
Document Description
Document ES1790-0-E1, First Edition. July 2006
This document will remain the official reference source for all revisions and releases of this product until
rescinded by an update.
Disclaimer
It is the policy of LSI Logic Corporation to improve products as new technology, components, software, and
firmware become available. LSI Logic reserves the right to make changes to any products herein at any time
without notice. All features, functions, and operations described herein may not be marketed by LSI Logic
in all parts of the world. In some instances, photographs and figures are of equipment prototypes. Therefore,
before using this document, consult your LSI Logic representative for information that is applicable and
current. LSI LOGIC DOES NOT ASSUME ANY RESPONSIBILITY OR LIABILITY FOR THE USE OF
ANY PRODUCTS DESCRIBED HEREIN EXCEPT AS EXPRESSLY AGREED TO IN WRITING BY
LSI LOGIC.
License Restriction
The purchase or use of an LSI Logic Corporation product does not convey a license under any patent,
copyright, trademark, or other intellectual property right of LSI Logic or third parties.
Copyright Notice
2006. LSI Logic Corporation. All rights reserved.
Trademark Acknowledgments
Engenio, the Engenio design, HotScale, SANtricity, and SANshare are trademarks or registered trademarks
of LSI Logic Corporation. All other brand and product names may be trademarks of their respective
companies.
Contents
COMMAND LINE INTERFACE AND SCRIPT COMMANDS QUICK REFERENCE
About the Command Line Interface............................................................................................ 2
Command Line Interface Structure........................................................................................ 2
Usage Notes ........................................................................................................................... 3
CLI Commands ...................................................................................................................... 3
CLI Command Formatting ........................................................................................................ 12
Usage Examples ................................................................................................................... 13
About the Script Commands ..................................................................................................... 14
Script Command Structure................................................................................................... 14
Recurring Syntax Elements.................................................................................................. 15
Script Command Formatting ..................................................................................................... 21
Script Commands ...................................................................................................................... 23
Commands Listed by Function ................................................................................................. 46
Controller Commands .......................................................................................................... 46
Host Topology Commands .................................................................................................. 46
Module Commands .............................................................................................................. 47
Physical Disk (Drive) Commands........................................................................................ 47
Remote Volume Mirroring Commands ............................................................................... 47
Session Command................................................................................................................ 48
Snapshot Commands............................................................................................................ 48
Storage Array Commands .................................................................................................... 48
Uncategorized Command..................................................................................................... 49
Volume Commands.............................................................................................................. 50
Volume Copy Commands .................................................................................................... 50
Volume Group Commands .................................................................................................. 51
ii
List of Tables
COMMAND LINE INTERFACE AND SCRIPT COMMANDS QUICK REFERENCE
Table 1. Command Name Conventions .................................................................................... 3
Table 2. Command Line Parameters ......................................................................................... 5
Table 3. Exit Status ................................................................................................................. 10
Table 4. Object Types and Identifiers ..................................................................................... 15
Table 5. Recurring Syntax Elements ....................................................................................... 16
Table 6. Script Commands ...................................................................................................... 23
iii
iv
Document Conventions
Definitions of Safety Notices
DANGER
CAUTION
Indicates a potentially hazardous situation that could result in data loss (or
other interruption) or equipment damage.
NOTE
Typographic Conventions
Italic indicates the title of documents, variables and placeholders in text, emphasized
words, and new terms.
Bold indicates choices in procedures and other emphasized text.
Monospace indicates arguments, code examples, command-line text, command options,
commands, directories, error messages, file names, folders, on-screen text, and user input.
Monospace italic indicates command variables in code, parameters, and
placeholders and variables in code.
Monospace bold indicates keywords and values.
vi
Intended Readers
This document is intended for system operators, system administrators, and service
personnel who are responsible for operating, maintaining, troubleshooting, and servicing a
storage array. Users must be familiar with computer system operation, maintenance, and
repair. In addition, they should understand disk array, Redundant Array of Independent
Disks (RAID) concepts, network, and Fibre Channel technologies. The reader must have a
basic knowledge of SAN hardware functionality (controllers, drives, hosts) and SAN
cabling.
Related Publications
SANtricity Storage Manager Command Line Interface and Script Commands
Programming Guide for Version 9.25
Storage System Product Release Notes for Version 9.25
vii
viii
A list of the commands and parameters for the command line interface (CLI)
A table that alphabetically lists the script commands and briefly describes the
purpose of each command
This quick reference helps you find the correct syntax and parameters for the commands
that you are using. It is not intended to be a complete programming guide. This quick
reference is for users who have read and understood the information in the SANtricity
Storage Manager Command Line Interface and Script Commands Programming Guide. If
you have questions related to the commands or parameters listed in this quick reference,
refer to the programming guide for additional information.
The parameters
parameters are CLI parameters that define the environment and purpose for the
command
Usage Notes
If you enter SMcli and a storage array name, but do not specify CLI parameters, script
commands, or a script file, the command line interface runs in interactive mode.
Interactive mode enables you to run individual commands without prefixing the
commands with SMcli. In interactive mode, you can enter a single command, view the
results, and enter the next command without typing the complete SMcli string.
Interactive mode is useful for determining configuration errors and quickly testing
configuration changes.
If you enter SMcli without any parameters or with an incorrect parameter, the script
engine returns usage information.
CLI Commands
This section lists the CLI commands that you can use to perform the following actions:
Specify passwords
Table 1 lists the conventions used in the general form of a CLI command.
Definition
a | b
Alternative (a or b)
italicized-words
Terminals
(a | b | c)
bold
Terminals
The following are general forms of the CLI commands, showing the parameters and
terminals used in each command. Table 2 on page 5 lists definitions for the parameters
shown in the general form of the CLI commands.
SMcli host-name-or-IP-address [host-name-or-IP-address]
[-c command; {command2};]
[-n storage-array-name | -w WWN]
[-o outputfile][-p password][-e][-S][-quick]
SMcli host-name-or-IP-address [host-name-or-IP-address]
[-f scriptfile]
[-n storage-array-name | -w WWN]
[-o outputfile][-p password][-e][-S][-quick]
SMcli (-n storage-array-name | -w WWN)
[-c command; {command2};]
[-o outputfile][-p password][-e][-S][-quick]
SMcli (-n storage-array-name | -w WWN)
[-f scriptfile]
[-o outputfile][-p password][-e][-S][-quick]
SMcli -a email:email-address
[host-name-or-IP-address1 [host-name-or-IP-address2]]
[-n storage-array-name | -w WWN | -h host-name |
-r (host_sa | direct_sa)]
[-I information-to-include][-q frequency][-S]
SMcli -x email:email-address
[host-name-or-IP-address1 [host-name-or-IP-address2]]
[-n storage-array-name | -w WWN | -h host-name |
-r (host_sa | direct_sa)] [-S]
SMcli (-a | -x) trap:community, host-name-or-IP-address
[host-name-or-IP-address1 [host-name-or-IP-address2]]
[-n storage-array-name | -w WWN | -h host-name |
-r (host_sa | direct_sa)] [-S]
SMcli -d [-w][-i][-s][-v][-S]
SMcli -m host-name-or-IP-address -F email-address
[-g contactInfoFile][-S]
SMcli -A [host-name-or-IP-address [host-name-or-IP-address]]
[-S]
SMcli -X (-n storage-array-name | -w WWN | -h host-name)
SMcli -?
Definition
host-name-or-IP-address
You can specify either the host name or the Internet Protocol (IP)
address (xxx.xxx.xxx.xxx) of an in-band managed storage array or
an out-of-band managed storage array.
-A
-a
Parameter
Definition
-c
Use this parameter to indicate that you are entering one or more
script commands to run on the specified storage array. Terminate
each command by a semicolon (;).
You cannot place more than one -c parameter on the same
command line. You can include more than one script command
after the -c parameter.
-d
-e
-F (uppercase)
Use this parameter to specify the email address from which all
alerts will be sent.
-f
-g
-h
Use this parameter to specify the host name that is running the
SNMP agent to which the storage array is connected. Use this
parameter with the -a and -x parameters.
Parameter
Definition
-I
-i
eventOnly
profile
supportBundle
-m
-n
-o
-p
Use this parameter to specify the password for the storage array on
which you want to run commands. A password is not necessary
under the following conditions:
1.
2.
3.
Parameter
Definition
-q
-quick
-r
Parameter
Definition
-S (uppercase)
-s (lowercase)
-v
-w
Use this parameter to specify the WWN of the storage array. This
parameter is an alternate to the -n parameter. Use the -w
parameter with the -d parameter to display the WWNs of the
known storage arrays. The format of the file content is:
storage-array-name world-wide-name
IP-address-1 IP-address-2
-X (uppercase)
-x (lowercase)
-?
Exit Status
After you run a CLI command, status is displayed that indicates the success of the
operation that is defined by the command. The statuses are shown in Table 3 .
Table 3
10
Exit Status
Status
Value
Meaning
A storage array name does not exist for the host agent connected.
10
11
12
13
14
15
16
17
18
19
20
21
Status
Value
Meaning
22
23
24
25
26
27
28
29
30
31
32
33
11
When double quotation marks ( ) are part of a name or argument, you must insert a
backslash (\) before each double quotation mark character. For example:
-c set storageArray userLabel=\Engineering\;
where Engineering is the storage array name. A second example is:
-n \My\_Array
where My_Array is the name of the storage array.
You cannot use double quotation marks ( ) as part of a character string (also called
string literal) within a script command. For example, you cannot enter the following
string to set the storage array name to Finance Array:
-c set storageArray userLabel=\\Finance\Array\;
In the UNIX and Solaris operating systems, the delimiters around names or labels are
single quotation marks ( ). The UNIX versions of the previous examples are:
-c set storageArray userLabel=Engineering;
-n My_Array
In a Windows operating system, if you do not use double quotation marks ( ) around a
name, you must insert a caret (^) before each special script character. Special characters
are ^, |, <, and >.
Insert a caret before each special script character when used with the -n, -o, -f,
and -p parameters. For example, to specify storage array CLI>CLIENT, enter the
following string:
-n CLI^>CLIENT
Insert one caret (^) before each special script character when used within a script
command string literal. For example, to change the name of a storage array to
FINANCE_|_PAYROLL, enter the following string:
-c set storageArray userLabel=\FINANCE_^|_PAYROLL\;
12
Usage Examples
The following examples show how to enter CLI commands on a command line. The
examples show the syntax, form, and, in some examples, script commands. Examples are
shown for both Windows and UNIX systems. Note that the usage for the -c parameter
varies depending on your operating system. On Windows operating systems, enclose the
script command following the -c parameter in double quotation marks ( ). On UNIX
operating systems, enclose the script command following the -c parameter in single
quotation marks ( ).
This example shows how to delete an existing volume and create a new volume on a
storage array. The existing volume name is Stocks_<_Bonds. The new volume name
is Finance. The controller host names are finance1 and finance2. The storage array
is protected, requiring the password TestArray.
Windows operating system:
SMcli finance1 finance2 -c set session
password=\TestArray\; delete volume[\Stock_^<_
Bonds\]; create volume driveCount[3] RAIDLEVEL=3
capacity=10GB userLabel=\Finance\; show storageArray
healthStatus;
UNIX and Solaris operating systems:
SMcli finance1 finance2 -c set session
password=TestArray; delete volume[Stock_<_Bonds];
create volume driveCount[3] RAIDLEVEL=3 capacity=10GB
userLabel=Finance; show storageArray healthStatus;
This example shows how to run commands in a script file named scriptfile.scr on a
storage array named Example. In this example, the storage array is protected by the
password My_Array. Output, as a result of commands in the script file, goes to file
output.txt.
Windows operating system:
SMcli -n Example -f scriptfile.scr -p My_Array -o
output.txt
UNIX operating system:
SMcli -n Example -f scriptfile.scr -p My_Array -o
output.txt
13
At the storage array, the script commands are run by the storage array controllers.
operand-data represents the objects associated with a storage array that you want to
configure or manage
14
Object type Use an object type when the command is not referencing a specific
object
all parameter All objects of the specified type in the storage array (for example,
allVolumes)
Identifier
controller
a or b
drive
drivechannel
host
User label
hostchannel
hostgroup
User label
hostport
User label
remote mirror
snapshot
storagearray
Not applicable
tray
Tray ID
volume
volumecopy
volumegroup
15
Syntax Value
raid-level
(0 | 1 | 3 | 5)
repository-raid-level
(1 | 3 | 5)
capacity-spec
segment-size-spec
integer-literal
boolean
(TRUE | FALSE)
user-label
string-literal
user-label-list
user-label {user-label}
create-raid-vol-attr-value-list
create-raid-volume-attribute-value-pair
{create-raid-volume-attribute-value-pair}
create-raid-volume-attribute-value-pair
capacity=capacity-spec |
owner=(a | b) |
readAheadMultiplier=integer-literal |
segmentSize=integer-literal
trayId
(099)
slot-id
(132)
port-id
(0127)
drive-spec
trayID, slotID
drive-spec-list
drive-spec {drive-spec}
tray-id-list
trayID {trayID}
hex-literal
0xhexadecimal-literal
volume-group-number
integer-literal
filename
string-literal
error-action
(stop | continue)
drive-channel-identifier
(1 | 2 | 3 | 4)
drive-channel-identifier-list
drive-channel-identifier {drive-channel-identifier}
host-channel-identifier
(all command modules except E6000)
(a1 | a2 | b1 | b2)
host-channel-identifier
(E6000 command module only)
(a1 | a2 | a3 | a4)
(b1 | b2 | b3 | b4)
16
Recurring Syntax
Syntax Value
drive-type
feature-identifier
(storagePartition2 | storagePartition4 |
storagePartition8 | storagePartition16 |
storagePartition64 | storagePartitionMax |
snapshot | remoteMirror | volumeCopy)
repository-spec
instance-based-repository-spec |
count-based-repository-spec
instance-based-repository-spec
repositoryRAIDLevel=repository-raid-level
repositoryDrives=(drive-spec-list)
[trayLossProtect=boolean1]
repositoryVolumeGroup=volume-group-number
[freeCapacityArea=integer-literal2]
Specify repositoryRAIDLevel with
repositoryDrives. Do not specify RAID level or
drives with volume group. Do not set
trayLossProtect when specifying a volume group.
count-based-repository-spec
repositoryRAIDLevel=repository-raid-level
repositoryDriveCount=integer-literal
[driveType= drive-type3]
[trayLossProtect=boolean4]
WWN
string-literal
nvsram-offset
hex-literal
host-type
nvsram-byte-setting
nvsram-bit-setting
ip-address
(0255).(0255).(0255).(0255)
autoconfigure-vols-attr-value-list
autoconfigure-vols-attr-value-pair
{autoconfigure-vols-attr-value-pair}
17
Recurring Syntax
Syntax Value
autoconfigure-vols-attr-value-pair
driveType=drive-type5 |
raidLevel=raid-level |
volumeGroupWidth=integer-literal |
volumeGroupCount=integer-literal |
volumesPerGroupCount=integer-literal6 |
hotSpareCount=integer-literal |
segmentSize=segment-size-spec |
readAheadMultiplier=integer-literal
create-volume-copy-attr-value-list
create-volume-copy-attr-value-pair
{create-volume-copy-attr-value-pair}
create-volume-copy-attr-value-pair
recover-raid-volume-attr-value-list
recover-raid-volume-attr-value-pair
{recover-raid-volume-attr-value-pair}
recover-raid-volume-attr-value-pair
owner=(a | b) |
readAheadMultiplier=integer-literal
cache-flush-modifier-setting
For tray loss protection to work, each physical disk in a volume group must be on a separate
module. If you set trayLossProtect=TRUE and have selected more than one physical disk
from any one module, the storage array returns an error. If you set
trayLossProtect=FALSE, the storage array performs operations, but the volume group you
create might not have tray loss protection.
To determine if a free capacity area exists, issue the show volumeGroup command.
If you set trayLossProtect=TRUE, the storage array returns an error if the controller
firmware cannot find drives that will enable the new volume group to have tray loss protection. If
you set trayLossProtect=FALSE, the storage array performs the operation even if it means
that the volume group might not have tray loss protection.
The driveType parameter is not required if only one type of physical disk is in the storage
array. If you use the driveType parameter, you must also use the hotSpareCount and
volumeGroupWidth parameters. If you do not use the driveType parameter, the
configuration defaults to Fibre Channel physical disks.
18
Usage Notes
The following list provides guidelines for writing script commands on the command line:
You can enter more than one command on a line, but you must separate each
command with a semicolon (;).
You must separate each base command and its associated primary and secondary
parameters with a space.
The script engine is not case sensitive. You can enter commands using uppercase,
lowercase, or mixed-case letters.
Add comments to your scripts to make it easier for you and future users to
understand the purpose of the script commands. For information on how to add
comments, see Adding Comments to a Script File on page 20.
NOTE:
While the CLI and script commands are not case sensitive, user labels (such
as for volume, hosts, or host ports) are case sensitive. If you try to map to an
object identified by a user label, you must enter the user label exactly as it is
defined, or the CLI and script commands will fail.
19
The script engine interprets as a comment any text typed after two forward slashes (/
/) until an end-of-line character is reached. If the script engine does not find an
end-of-line character in the script after processing a comment, an error message is
displayed, and the script operation is terminated. This error commonly occurs when
a comment is placed at the end of a script and you have forgotten to press the Enter
key.
// Deletes the existing configuration.
set storageArray resetConfiguration=true;
The script engine interprets any text typed between / * and * / as a comment. If the
script engine does not find both a beginning and ending comment notation, an error
message is displayed, and the script operation is terminated.
/* Deletes the existing configuration */
set storageArray resetConfiguration=true;
Use the show statement to embed comments in a script file that you want to display
while the script file is running. Enclose the text you want to display by using double
quotation marks ( ).
show Deletes the existing configuration;
set storageArray resetConfiguration=true;
20
The script commands are not case sensitive. You can type the commands in
lowercase, uppercase, or mixed-case letters. (In the following command
descriptions, mixed-case letters are used as an aid to reading the command names
and understanding the purpose of the command.)
You must enter spaces in the commands as they are shown in the command
descriptions.
The description of each parameter tells you if you need to enclose a parameter value
in square brackets.
Parentheses shown in the command syntax enclose specific choices for a parameter;
that is, if you want to use the parameter, you must enter one of the values enclosed in
parentheses. Generally, you do not include parentheses in a command; however, in
some instances, when you enter lists, you must enclose the list in parentheses. Such a
list might be a list of tray ID values and slot ID values. The description of each
parameter tells you if you need to enclose a parameter value in parentheses.
Vertical bars in a command indicate or and separate the valid entries for the
parameter. For example, the syntax for the raidLevel parameter in the command
description appears as:
raidLevel=(0 | 1 | 3 | 5)
To use the raidLevel parameter to set a RAID level of 5, enter:
raidLevel=5
When you specify physical disk locations using tray ID and slot ID values, separate
the ID values by a comma. If you are entering more than one set of ID values,
separate each set of values by a space. Enclose the set of values in parentheses. For
example:
(1,1 1,2 1,3 1,4 2,1 2,2 2,3 2,4)
21
Italic terms in the command indicate a value or information that you need to provide.
For example, when you encounter the italicized term:
numberOfDrives
replace the italicized term with a value for the number of physical disks you want to
include with the command.
You can use any combination of alphanumeric characters, hyphens (-), and
underscores (_) for the names of the following components:
Storage arrays
Host groups
Hosts
Volume groups
Volumes
Host ports
Names can have a maximum of 30 characters. If the label contains more than one
word, underscores, or hyphens, enclose the name in double quotation marks. In some
usages, you must also surround the name with square brackets. The description of
each parameter indicates whether you need to enclose a parameter in double
quotation marks or square brackets. The character string cannot contain a new line.
You must use unique names; if you do not use unique names, the controller firmware
returns an error.
On Windows operating systems, the name must be enclosed between two
backslashes (\) in addition to other delimiters. For example, the following name is
used in a command running under a Windows operating system:
[\Engineering\]
For a UNIX system, and when used in a script file, the name appears as:
[Engineering]
When you enter a World Wide Name (WWN) of a host port, some usage requires
you to surround the WWN with double quotation marks. In other uses, you must
surround the WWN with angle brackets (< >). The description of the WWN
parameter indicates whether you need to enclose the WWN in double quotation
marks or angle brackets.
22
Script commands must end with a semicolon (;). You can enter more than one script
command on the command line each time you enter a CLI command.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
Script Commands
Table 6 Script Commands
activate
activate storageArray feature=remoteMirror
repositoryRAIDLevel=(1 | 3 | 5)
repositoryDrives=(trayID1,slotID1 ... trayIDn,slotIDn)
[trayLossProtect=(TRUE | FALSE)]
This command creates the mirror repository volume and activates the Remote
Volume Mirror feature. This command enables users to define which physical
disks will be used for the repository volume.
activate storageArray feature=remoteMirror
repositoryVolumeGroup=volumeGroupNumber
[freeCapacityArea=freeCapacityIndexNumber
trayLossProtect=(TRUE | FALSE)]
This command creates the mirror repository volume and activates the Remote
Volume Mirroring feature. This command enables users to define the volume
group in which the repository volume will be located.
activate storageArray feature=remoteMirror
repositoryRAIDLevel=(1 | 3 | 5)
repositoryDriveCount=numberOfDrives
[driveType=(fibre | SATA | PATA)
trayLossProtect=(TRUE | FALSE)]
This command creates the mirror repository volume and activates the Remote
Volume Mirroring feature. This command enables users to define the number
of physical disks to be used for the repository volume.
activate storageArray firmware
This command activates firmware previously downloaded to the pending
configuration area on the controllers in the storage array.
23
autoConfigure
autoConfigure storageArray [driveType=(fibre | SATA | PATA)
raidLevel=(0 | 1 | 3 | 5) volumeGroupWidth=numberOfDrives
volumeGroupCount=numberOfVolumeGroups
volumesPerGroupCount=numberOfVolumesPerGroup
hotSpareCount=numberOfHotspares segmentSize=segmentSizeValue
readAheadMultiplier=multiplierValue]
This command automatically configures a storage array. Before entering the
this command, enter the show storageArray autoConfiguration
command to return a list of valid physical disk types, RAID levels, volume
information, and hot spare information. If you want to modify the
configuration, you can change the parameters to meet your configuration
requirements. You can change a single parameter or all parameters. After you
enter the autoConfigure storageArray command, the controllers set
up the storage array by using either the default parameters or those you
selected.
autoConfigure storageArray hotSpares
This command automatically defines and configures the hot spares in a storage
array. You can run this command at any time. This command provides the best
hot spare coverage for a storage array.
check
check remoteMirror localVolume [volumeName] optimalStatus
timeout=timeoutValue
This command returns the status of a Remote Volume Mirror. Use this
command to determine when Remote Volume Mirror status becomes Optimal.
check volume [volumeName] parity [parityErrorFile=filename]
[mediaErrorFile=filename] [priority=(highest | high | medium |
low | lowest)] [startingLBA=LBAvalue] [endingLBA=LBAvalue]
[verbose=(TRUE|FALSE)]
This command checks a volume for parity and media errors and writes the
results of the check to a file.
clear
clear allDriveChannels stats
This command resets the statistics for all physical disk channels.
24
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
25
26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
27
28
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
delete
delete host [hostName]
This command deletes a host.
delete hostGroup [hostGroupName]
This command deletes a host group.
delete hostPort [hostPortName]
This command deletes a host port.
delete (allVolumes | volume [volumeName] |
volumes [volumeName1 ... volumeNamen])
This command deletes one or more standard volumes or snapshots and
snapshot repository volumes.
Caution:
Potential storage array configuration damage All data in the volume is
lost as soon as you run this command.
delete volumeGroup [volumeGroupNumber]
This command deletes an entire volume group and its associated volumes.
Caution:
Potential storage array configuration damage All data in the volume
group is lost as soon as you run this command.
diagnose
diagnose controller [(a | b)]
loopbackDriveChannel=(allchannels | (1 | 2 | 3 | 4))
testID=(1 | 2 | 3 | discreteLines) [patternFile=filename]
This command runs diagnostic tests on the controller. The diagnostic tests
consist of loop-back tests in which data is written to physical disks and read
from the physical disks.
diagnose remoteMirror (primary [primaryVolumeName] |
primaries [primaryVolumeName1 ... primaryVolumeNamen])
testID=connectivity
This command tests the connection between the specified primary volumes and
mirror volumes on a storage array with the Remote Volume Mirroring feature
installed.
29
disable
disable storageArray feature=(storagePartition2 |
storagePartition4 | storagePartition8 | storagePartition16 |
storagePartition64 | storagePartitionMax | snapshot |
remoteMirror | volumeCopy)
This command disables a storage array feature. Issue the show
storageArray command to display a list of the feature identifiers for all
enabled features in the storage array.
download
download drive [trayID,slotID] firmware file=filename
This command downloads a firmware image to a physical disk.
download (allTrays | tray [trayID]) firmware file=filename
This command downloads module firmware.
download storageArray driveFirmware file=filename
[file=filename2...file=filenameN]
This command downloads firmware images to all physical disks in the storage
array.
download storageArray firmware [, NVSRAM ] file=filename
[, NVSRAM-filename] [downgrade=(TRUE | FALSE)]
[activateNow=(TRUE | FALSE)]
This command downloads firmware and, optionally, NVSRAM values for the
storage array controller. If you want to download only NVSRAM values, use
the downLoad storageArray NVSRAM command.
download storageArray NVSRAM file=filename
This command downloads NVSRAM values for the storage array controller.
enable
enable controller [(a | b)] dataTransfer
This command revives a controller that has become quiesced while running
diagnostics.
enable storageArray feature file=filename
This command enables a feature using a feature key file.
30
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
recopy
recopy volumeCopy target [targetName] [source [sourceName]]
[copyPriority=(highest | high | medium | low | lowest)
targetReadOnlyEnabled=(TRUE | FALSE)]
This command reinitiates a volume copy operation using an existing volume
copy pair.
recover
recover volume (drive=(trayID,slotID) |
drives=(trayID1,slotID1 ... trayIDn,slotIDn) |
volumeGroup=volumeGroupNumber userLabel=volumeName
capacity=volumeCapacity offset=offsetValue
raidLevel=(0 | 1 | 3 | 5) segmentSize=segmentSizeValue
[owner=(a | b) readAheadMultiplier=multiplierValue]
This command creates a RAID volume with the given properties without
initializing any of the user data areas on the disks. Parameter values are derived
from the Recovery Profile data file for the storage array.
recreate
recreate storageArray mirrorRepository
repositoryRAIDLevel=(1 | 3 | 5)
repositoryDrives=(trayID1,slotID1 ... trayIDn,slotIDn)
[trayLossProtect=(TRUE | FALSE)]
This command creates a new Remote Volume Mirror repository volume using
the parameters defined for a previous Remote Volume Mirror repository
volume. The underlying requirement is that you have previously created a
Remote Volume Mirror repository volume. This command enables users to
define which physical disks will be used for the Remote Volume Mirror
repository volume.
recreate storageArray mirrorRepository
repositoryVolumeGroup=volumeGroupNumber
[freeCapacityArea=freeCapacityIndexNumber]
This command creates a new Remote Volume Mirror repository volume using
the parameters defined for a previous Remote Volume Mirror repository
volume. The underlying requirement is that you have previously created a
Remote Volume Mirror repository volume. This command enables users to
define the volume group in which the Remote Volume Mirror repository
volume will be located.
31
32
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
reset
reset controller [(a | b)]
This command resets a controller.
Important:
When you reset a controller, the controller is not available for I/O operations
until the reset is complete. If a host is using volumes owned by the controller
being reset, the I/O directed to the controller will be rejected. Before resetting
the controller, either verify that the volumes owned by the controller are not in
use or ensure that a multi-path driver is installed on all hosts using these
volumes.
reset storageArray batteryInstallDate [controller=(a | b)]
This command resets the age of the batteries in a storage array to zero days.
You can reset the batteries for an entire storage array or the battery in a specific
controller. The E6000 command module does not support this command.
reset storageArray diagnosticData
This command resets the NVSRAM that contains the storage array diagnostic
data. This command, however, does not delete the diagnostic data. This
command replaces the Needs Attention status with the Diagnostic Data
Available status. The old diagnostic data is then automatically written over
when new data is captured. The memory that contains the diagnostic data is
also cleared when the controllers reboot. Before resetting the diagnostic data,
use the save storageArray diagnosticData command to save the
diagnostic data to a file.
reset storageArray RLSBaseline
This command resets the Read Link Status (RLS) baseline for all devices.
reset storageArray SOCBaseline
This command resets the baseline for all switch-on-a-chip (SOC) devices
accessed through the controllers. This command resets the baseline by setting
all SOC counts to 0. This command is valid only for Fibre Channel devices in
an Arbitrated Loop topology.
reset storageArray volumeDistribution
This command reassigns (moves) all volumes to their preferred controller.
33
resume
resume remoteMirror (primary [volumeName] |
primaries [volumeName1 ... volumeNamen])
writeConsistency=(TRUE | FALSE)
This command resumes a suspended Remote Volume Mirroring operation.
revive
revive drive [trayID,slotID]
This command forces the specified physical disk to the Optimal state.
revive volumeGroup [volumeGroupNumber]
This command forces the specified volume group and associated failed
physical disks to the Optimal state.
Caution:
Possible data corruption or data loss Correct use of this command depends
on the data configuration on all physical disks in the volume group. Never
attempt to revive a physical disk unless supervised by a Customer and
Technical Support representative.
save
save controller [(a | b)] NVSRAM file=filename
This command saves a copy of the controller NVSRAM values to a file. This
command saves all regions.
save allDrives logFile=filename
This command saves the log sense data to a file. Log sense data is maintained
by the storage array for each physical disk.
save storageArray configuration file=filename
[(allconfig | globalSettings=(TRUE | FALSE)
volumeConfigAndSettings=(TRUE | FALSE)
hostTopology=(TRUE | FALSE) lunMappings=(TRUE | FALSE))]
This command creates a script file that you can use to create the current storage
array volume configuration.
34
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
35
set
set controller [(a | b)]
availability=(online | offline | serviceMode) |
bootp |
ethernetPort [(1 | 2)] ipAddress=ipAddress |
gatewayIPAddress=ipAddress |
globalNVSRAMByte [nvsramOffset]=(nvsramByteSetting |
nvsramBitSetting) |
hostNVSRAMByte [hostType, nvsramOffset]=(nvsramByteSetting |
nvsramBitSetting) |
ipAddress=ipAddress |
rloginEnabled=(TRUE | FALSE) |
subnetMask=ipAddress
This command defines the properties for the controllers.
set controller=[(a | b)] serviceAllowedIndicator=(on | off)
This command turns on or turns off the Service Action Allowed indicator light
on an E6000 command module controller. This command is valid only for
E6000 command modules. (To turn on or turn off the Service Action Allowed
indicator light on the power-fan canister or interconnect-battery canister in an
E6000 command module, use the set tray
serviceAllowedIndicator command.)
set driveChannel [(1 | 2 | 3 | 4)] status=(optimal | degraded)
This command defines how the physical disk channel performs.
set (drive [trayID,slotID] |
drives [trayID1,slotID1 ... trayIDn,slotIDn])
hotSpare=(TRUE | FALSE)
This command assigns or unassigns one or more physical disks as a hot spare.
set drive [trayID,slotID] operationalState=failed
This command sets a physical disk to the failed state. (To return a physical disk
to the Optimal state, use the revive drive command.)
set (drive [trayID,slotID] | drives [trayID1,slotID1 ...
trayIDn,slotIDn]) serviceAllowedIndicator=(on | off)
This command turns on or turns off the Service Action Allowed indicator light
on a physical disk in the FC-4 16x drive module. If the storage array does not
support the Service Action Allowed indicator light feature, this command
returns an error. If the storage array supports the command but is unable to turn
on or turn off the indicator light, this command returns an error.
36
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
37
38
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
39
40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
41
42
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
43
44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Commands
45
Controller Commands
Clear Drive Channel Statistics
Diagnose Controller
Enable Controller
Reset Controller
Save Controller NVSRAM
Set Controller
Set Controller Service Action Allowed Indicator
Set Drive Channel Status
Set Host Channel
Show Controller
Show Controller NVSRAM
Show Drive Channel Stats
Start Drive Channel Locate
Stop Drive Channel Locate
46
Module Commands
Download Environmental Card Firmware
Set Tray Identification
Set Tray Alarm
Set Tray Service Action Allowed Indicator
Start Tray Locate
Stop Tray Locate
47
Session Command
Set Session
Snapshot Commands
Create Snapshot Volume
Re-create Snapshot
Set Snapshot Volume
Stop Snapshot
48
Uncategorized Command
Show String
49
Volume Commands
Check Volume Parity
Clear Volume Reservations
Clear Volume Unreadable Sectors
Create RAID Volume (Automatic Drive Select)
Create RAID Volume (Free Capacity Base Select)
Create RAID Volume (Manual Drive Select)
Delete Volume
Recover RAID Volume
Remove Volume LUN Mapping
Repair Volume Parity
Set Volume
Show Volume
Show Volume Action Progress
Show Volume Performance Statistics
Show Volume Reservations
Start Volume Initialization
50
51
52