Chapter 13. Example Script Files; Configuration Script Example 1 - IBM System Storage DS3000 Programming Manual

Hide thumbs Also See for System Storage DS3000:
Table of Contents

Advertisement

Chapter 13. Example Script Files

This appendix provides example scripts for configuring a storage subsystem. These examples show how
the script commands appear in a complete script file. Also, you can copy these scripts and modify them
to create a configuration unique to your storage subsystem.
You can create a script file in two ways:
v Using the save storageSubsystem configuration command
v Writing a script
By using the save storageSubsystem configuration command, you can create a file that you can use to
copy an existing configuration from one storage subsystem to other storage subsystems. You can also use
this file to restore an existing configuration that has become corrupted. You also can copy an existing file
to serve as a pattern from which you create a new script file by modifying portions of the original file.
The default file extension is .scr.
You can create a new script file by using a text editor, such as Microsoft Notepad. The maximum line
length is 256 characters. The command syntax must conform to the usage guidelines that are described in
Chapter 2, "About the Script Commands," on page 2-1 and the command formatting rules that are listed
in "Formatting rules for script commands" on page 3-2. When you create a new script file, you can use
any file name and extension that will run on the host operating system.
This example shows how to run a script file from the command line.
c:\...\...\client>smcli 123.45.67.89 -f scriptfile.scr;

Configuration Script Example 1

This example creates a new logical drive by using the create logicalDrive command in the free space of
an subsystem.
Show "Create RAID 5 Logical Drive 7 on existing subsystem 1";
//Create logical drive on subsystem created by the create logical drives command
//Note: For subsystems that use all available capacity, the last logical drive
on the group is created using all remaining capacity by omitting
the capacity=logical drive creation parameter
create logicalDrive subsystem=1 RAIDLevel=5 userLabel="7" owner=A segmentSize=16
cacheReadPrefetch=TRUE capacity=2GB securityType=true;
show "Setting additional attributes for logical drive 7"; //Configuration settings
that cannot be set during logical drivecreation
set logicalDrive["7"] cacheFlushModifier=10;
set logicalDrive ["7"] cacheWithoutBatteryEnabled=false;
set logicalDrive ["7"] mirrorEnabled=true;
set logicalDrive ["7"] readCacheEnabled=true;
set logicalDrive ["7"] writeCacheEnabled=true;
set logicalDrive ["7"] mediaScanEnabled=false;
set logicalDrive ["7"] redundancyCheckEnabled=false;
set logicalDrive ["7"] modificationPriority=high;
This example shows blank lines between the lines beginning with Show, Create, //Note, and create. The
blank lines are included in this example only for clarity. Each command is actually written on one line in
the script file; however, the size of this page has caused the command text to wrap. You might want to
include blank lines in your script files to separate blocks of commands or make a comment that stands
out. To include a comment, enter two forward slashes (//), which causes the script engine to treat the line
as a comment.
13-1
© Copyright IBM Corp. 2008, 2012

Advertisement

Table of Contents
loading

This manual is also suitable for:

System storage ds4000System storage ds5000

Table of Contents