Ds8100 Lun Allocation Procedure

DS8100 LUN ALLOCATION PROCEDURE
Configuring the DS8000 storage for FB volumes

This section goes through examples of a typical DS8000 storage configuration when
attaching to open systems hosts. We do the DS8000 storage configuration by going
through
the following steps:
1. Set I/O ports.
2. Install license keys
3. Create arrays.
4. Create ranks.
5. Create extent pools.
6. Create volumes.
7. Create volume groups.
8. Create host connections.
Create array
In this next step we create the arrays. Before creating the arrays, it is a good
idea to first list
the arrays sites. The command that was issued is lsarraysite;
dscli> lsarraysite
Date/Time: 27 October 2005 20:54:31 IBM DSCLI Version: 5.1.0.204 DS: IBM.2107-7503461
arsite DA Pair dkcap (10^9B) State Array
=============================================
S1 0 146.0 Unassigned -
We can now issue the mkarray command to create arrays,
dscli> mkarray -raidtype 5 -arsite S1

CMUC00004I mkarray: Array A0 successfully created.
dscli> mkarray -raidtype 5 -arsite S2
CMUC00004I mkarray: Array A1 successfully created.
dscli>
dscli> lsarray
Date/Time: 27 October 2005 21:58:27 IBM DSCLI Version: 5.1.0.204 DS: IBM.2107-
7503461
Array State Data RAIDtype arsite Rank DA Pair DDMcap (10^9B)
===================================================
==================
A0 Unassigned Normal 5 (6+P+S) S1 - 0 146.0
A1 Unassigned Normal 5 (6+P+S) S2 - 0 146.0
Example 14-8 shows the result of the lsarray command. We can see the type of RAID
array
and the number of disks that are allocated to the array (in this example 6+P+S,
which means
the usable space of the array is 6 times the DDM size), as well as the capacity of the
DDMs
that are used and which array sites were used to create the arrays.
Create ranks
Once we have created all the arrays that are required, we then create the
ranks using the
mkrank command. The format of the command is: mkrank -array Ax -stgtype
xxx, where
xxx is either fixed block (FB) or count key data (CKD), depending on whether
you are
configuring for open systems or System z hosts.
dscli> mkrank -array A0 -stgtype fb

7503461
CMUC00007I mkrank: Rank R0 successfully created.
dscli> mkrank -array A1 -stgtype fb
7503461
CMUC00007I mkrank: Rank R1 successfully created.
dscli> lsrank -l
7503461
ID Group State datastate Array RAIDtype extpoolID extpoolnam stgtype exts usedexts
===================================================
====================================
R0 - Unassigned Normal A0 5 - - fb 773 -
R1 - Unassigned Normal A1 5 - - fb 773
Create extent pools

The next step is to create extent pools. Below are some points that should be
remembered
when creating the extent pools:
_ The number of extent pools can range from one to as many ranks that exist.
_ The extent pool has an associated rank group (either 0 or 1, for server0 or
server1).
_ They have the -stgtype attribute, that is, they are either FB or CKD.
_ Ideally, all ranks within an extent pool should have the same characteristics,
in that they
should have the same DDM type and same RAID type.
For ease of management, we create empty extent pools relating to the type of
storage that is
in this pool. For example, create an extent pool for high capacity disk, create
another for high
performance, and, if needed, extent pools for the CKD environment. For high
capacity, you
would consider using 300 GB 10k rpm DDMs, while for high performance you
might consider
73 GB 15k rpm DDMs.
It is also a good idea to note to which server the extent pool has an affinity.
Example 14-10 An extent pool layout plan
FB Extent Pool high capacity 300gb disks assigned to server 0 (FB_LOW_0)
FB Extent Pool high capacity 300gb disks assigned to server 1 (FB_LOW_1)
FB Extent Pool high performance 146gb disks assigned to server 0 (FB_High_0)
FB Extent Pool high performance 146gb disks assigned to server 0 (FB_High_1)
CKD Extent Pool High performance 146gb disks assigned to server 0 (CKD_High_0)
CKD Extent Pool High performance 146gb disks assigned to server 1 (CKD_High_1)
Example 14-10 shows an example of how we could divide your machine. Now in
Example 14-6 on page 285 we only had four array sites, so clearly we would
need more
DDMs to support this many extent pools.
Note that the mkextpool command forces you to name the extent pools. In
Example 14-11 we
first create empty extent pools using mkextpool. We then list the extent pools
to get their IDs.
Then we attach a rank to an empty extent pool using the chrank command.
Finally we list the
extent pools again using lsextpool and note the change in capacity of the
extent pool.
Example 14-11 Extent pool creation using mkextpool, lsextpool, and chrank
dscli> mkextpool -rankgrp 0 -stgtype fb FB_high_0
CMUC00000I mkextpool: Extent Pool P0 successfully created.
dscli> mkextpool -rankgrp 1 -stgtype fb FB_high_1
CMUC00000I mkextpool: Extent Pool P1 successfully created.
dscli> lsextpool
Name ID stgtype rankgrp status availstor (2^30B) %allocated available reserved numvols
=========================================================
==================================
FB_high_0 P0 fb 0 below 0 0 0 0 0
FB_high_1 P1 fb 1 below 0 0 0 0 0
dscli> chrank -extpool P0 R0
CMUC00008I chrank: Rank R0 successfully modified.
dscli> chrank -extpool P1 R1
CMUC00008I chrank: Rank R1 successfully modified.
dscli> lsextpool
=========================================================
==================================
FB_high_0 P0 fb 0 below 773 0 773 0 0
FB_high_1 P1 fb 1 below 773 0 773 0 0
After having assigned a rank to an extent pool, we should be able to see this
when we display
the ranks. In Example 14-12 on page 288 we can see that rank R0 is assigned
to extpool P0.
288 IBM System Storage DS8000 Series: Architecture and Implementation
Example 14-12 Displaying the ranks after assigning a rank to an extent pool
dscli> lsrank -l
ID Group State datastate Array RAIDtype extpoolID extpoolnam stgtype exts usedexts
=========================================================
==========================
R0 0 Normal Normal A0 5 P0 FB_high_0 fb 773 0
R1 1 Normal Normal A1 5 P1 FB_high_1 fb 773 0
14.3.4 Creating FB volumes
We are now able to create volumes and volume groups. When we create them,
we should try
to distribute them evenly across the two rank groups in the storage unit. We
should also try
and create the same number of volumes in each rank group.
The format of the command that we use is:
mkfbvol -extpool pX -cap xx -name high_fb_0# 1000-1003
In Example 14-13, we have created eight volumes, each with a capacity of 10
GB. The first
four volumes are assigned to rank group 0 and the second four are assigned to
rank group 1.
Example 14-13 Creating fixed block volumes using mkfbvol
dscli> lsextpool
=========================================================
==================================
FB_high_0 P0 fb 0 below 773 0 773 0 0
FB_high_1 P1 fb 1 below 773 0 773 0 0
dscli> mkfbvol -extpool p0 -cap 10 -name high_fb_0_#h 1000-1003
CMUC00025I mkfbvol: FB volume 1000 successfully created.
dscli> mkfbvol -extpool p1 -cap 10 -name high_fb_1_#h 1100-1103
Example 14-14 Checking the machine after creating volumes, by using lsextpool and lsfbvol
dscli> lsfbvol
Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B)
=========================================================
==================================================
high_fb_0_1000 1000 Online Normal Normal 2107-922 FB 512 P0 10.0 -
dscli> lsextpool
=========================================================
==================================
FB_high_0 P0 fb 0 below 733 5 733 0 4
FB_high_1 P1 fb 1 below 733 5 733 0 4
Creating volume groups

Fixed block volumes get assigned to open systems hosts using volume groups,
which is not
to be confused with the term volume groups used in AIX. A fixed bock volume
can be a
member of multiple volume groups. Volumes can be added or removed from
volume groups
as required. Each volume group must be either SCSI MAP256 or SCSI MASK,
depending on
the SCSI LUN address discovery method used by the operating system to
which the volume
group will be attached.
Example 14-16 Creating a volume group with mkvolgrp and displaying it

dscli> mkvolgrp -type scsimask -volume 1000-1002,1100-1102 AIX_VG_01
CMUC00030I mkvolgrp: Volume group V11 successfully created.
dscli> lsvolgrp
Name ID Type
=======================================
ALL CKD V10 FICON/ESCON All
AIX_VG_01 V11 SCSI Mask
ALL Fixed Block-512 V20 SCSI All
ALL Fixed Block-520 V30 OS400 All
dscli> showvolgrp V11
Name AIX_VG_01
ID V11
Type SCSI Mask
Vols 1000 1001 1002 1100 1101 1102
In this example, we added volumes 1000 to 1002 and 1100 to 1102. We did this
to spread the
workload evenly across the two rank groups. We then listed all available
volume groups using
lsvolgrp. Finally, we listed the contents of volume group V11, since this was
the volume
group we created.
Clearly we may also want to add or remove volumes to this volume group at a
later time. To
achieve this we use chvolgrp with the -action parameter. In Example 14-17 on
page 291 we
added volume 1003 to the volume group V11. We display the results, and then
removed the
volume.
Example 14-17 Changing a volume group with chvolgrp

dscli> chvolgrp -action add -volume 1003 V11
CMUC00031I chvolgrp: Volume group V11 successfully modified.
Name AIX_VG_01
ID V11
Type SCSI Mask
Vols 1000 1001 1002 1003 1100 1101 1102
dscli> chvolgrp -action remove -volume 1003 V11
CMUC00031I chvolgrp: Volume group V11 successfully modified.
Name AIX_VG_01
ID V11
Type SCSI Mask
Vols 1000 1001 1002 1100 1101 1102
Creating host connections

The final step in the logical configuration process is to create host
connections for your
attached hosts. You will need to assign volume groups to those connections.
Each host HBA
can only be defined once, and each host connection (hostconnect) can only
have one volume
group assigned to it. Remember though that a volume can be assigned to
multiple volume
groups.
Example 14-18 Creating host connections using mkhostconnect and lshostconnect

dscli> mkhostconnect -wwname 100000C912345678 -hosttype pSeries -volgrp V11
AIX_Server_01
CMUC00012I mkhostconnect: Host connection 0000 successfully created.
dscli> lshostconnect
Name ID WWPN HostType Profile portgrp volgrpID ESSIOport
=========================================================
================================
AIX_Server_01 0000 100000C912345678 pSeries IBM pSeries - AIX 0 V11 all
dscli>
Note that you can also use just -profile instead of -hosttype. However, we do
not
recommend that you do this. If you use the -hosttype parameter, it actually
invokes both
parameters (-profile and -hosttype), where using just -profile leaves the
-hosttype
column unpopulated.
There is also the option in the mkhostconnect command to restrict access to
only certain I/O
ports. This is done with the -ioport parameter. Restricting access in this way
is usually
Important: Not all operating systems can deal with the removal of a volume.
Consult your
operating system documentation to determine the safest way to remove a
volume from a
host.
292 IBM System Storage DS8000 Series: Architecture and Implementation
unnecessary. If you want to restrict access for certain hosts to certain I/O
ports on the
DS8000, do this through zoning on your SAN switch.

Ds8100 Lun Allocation Procedure

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ds8100 Lun Allocation Procedure

Hochgeladen von

Copyright:

Verfügbare Formate

DS8100 LUN ALLOCATION PROCEDURE

Configuring the DS8000 storage for FB volumes

We can now issue the mkarray command to create arrays,

dscli> mkarray -raidtype 5 -arsite S1

dscli> mkrank -array A0 -stgtype fb

Create extent pools

Creating volume groups

Example 14-16 Creating a volume group with mkvolgrp and displaying it

Example 14-17 Changing a volume group with chvolgrp

Creating host connections

Example 14-18 Creating host connections using mkhostconnect and lshostconnect

Das könnte Ihnen auch gefallen