IBM BladeCenter S SAS RAID Controller Module, Installation And User Manual

Page: 48 / 216

create volume -name CannedDG1:vol4 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on
create volume -name CannedDG1:vol5 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on
create volume -name CannedDG1:vol6 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on
global spare -add -slot 1:6
-autocopyback off
event log -setlevel -tlc 2622232552222200000066000 -alsal 3363333363333633383333 -arts 333333333353353333333
datascrub -set -auto off
Note: The autocopyback feature allows you to copy the data from a source drive
of a virtual drive to a destination drive that is not part of the virtual drive.
Autocopyback is often used to create or to restore a specific physical configuration
for a drive group (for example, a specific arrangement of the drive group members
on the device I/O buses). In general, when a drive fails or is expected to fail, the
data is rebuilt on a global spare. After the failed drive is replaced by a new hard
disk drive, the data is copied from the global spare to the new drive, and the
global spare reverts from a rebuild drive to its original global spare status. The
autocopyback operation runs as a background activity, while the virtual drive is
still available online to the host.
For more information on the controller config command, see “controller config”
on page 65
After you issue the command that loads the predefined configuration, define the
hosts and the volumes that require access to them.
Configuring volumes for use with VMware
This topic describes the steps to configure volumes for use with the VMware
operating system.
To properly failover the VI client, perform the following steps to set multipath
configuration settings for the VMware:
1. Check the controller states and the preferred path from the RAID Controller
command line interface (CLI) or IBM Storage Configuration Manager (SCM).
Using the RAID Controller command line interface (CLI)
a. Run the
list controller
command to ensure the controllers are in the
bound state.
<CLI> list controller
Current Machine Local Time: 10/02/2009 09:11:55 AM
_______________________________________________
| Ctlr# | Controller | Status | Ports | LUNs |
|_______|____________|___________|_______|______|
|
0 | Ctlr0 | PRIMARY | 1 | 186 |
| 1 | Ctlr1 | SECONDARY | 1 | 186 |
|_______|____________|___________|_______|______|
b. Run the
list pool
command to check your preferred path. In the following
example, the
raid1
pool has a preferred path set to controller 1 as indicated
by
slot 1
. All volumes belonging to
raid1
will have a preferred path to
controller 1. Similarly, the
raid5
pool has a preferred path set to controller 0
as indicated by
slot 0
.
<CLI> list pool
Current Machine Local Time: 10/02/2009 09:12:01 AM
_________________________________________________________________________
|Pool#|ID| Name|RaidType|OwnerCtlr|TotalCap|AvailCap|Status|State|Degraded|
|_____|__|_____|________|_________|_______ |_______ |______|_____|________|
|
0 | 2|raid5| 5 | Slot 0 | 3832GB| 366GB|Viable| ONV | No |
| 1 | 1|raid1| 1 | Slot 1 | 279GB| 247GB|Viable| ONV | No |
|____ |__|_____|________|_________|________|________|______|_____|________|
Using IBM Storage Configuration Manager (SCM)
38
IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module