VMAX Autoprovisioning Group Standards

V-MAX Autoprovisioning Group Standards
RESTRICTED - PROPRIETARY INFORMATION

Not for disclosure outside of AT&T Page 1

AT&T
Standards and Script Testing

Sejal Joshi and Ken Guest
8/26/2009

Trademarks Product or Company names mentioned in this document may be
trademarks or registered trademarks of their respective companies and are
hereby acknowledged.
Confidentiality The information in this document will not be disclosed, in whole or in part
unless written permission is obtained, in advance, from AT&T Mobility.


Relevant Revision History

Date Version Description Author
08/26/09 1.0 Initial Draft Sejal Joshi/Ken Guest



Autoprovisioning Groups:

Solutions Enabler V7.0 with Enginuity 5874 introduces new way to provision the storage called auto
provisioning groups. Auto provisioning Groups allow storage administrators to create groups of host
initiators, front-end ports, and logical devices. These groups are then associated to form a masking view,
from which all controls are managed.

Storage provisioning with symaccess allow creating a group of devices, a group of director ports, a group
of host initiators, and with one command, associate them in what is called a masking view. Once a
masking view exists, devices, ports, and initiators can be easily added or removed from their respective
groups. This feature reduces the number of commands needed for masking devices, and allows for easy
management of the masking view.

The symaccess command is used to create and manage the groups and views. This command also
contains some features similar to those found in the symmask and symmaskdb commands (a login
history command and initiator attributes).

Note: The symaccess command is not supported on Symmetrix DMX arrays.

The steps for creating a masking view are:

1. Create a storage group (one or more devices).
2. Create a port group (one or more director/port combinations).
3. Create an initiator group (one or more host WWNs).
4. Create a masking view containing the storage group, port group, and initiator group.

When a masking view is created, the devices are automatically masked and mapped.



Creating initiator groups:
Initiator group is a container of one or more host initiators. We will group 2 initiators/WWN and add them
to single initiator group.
Naming Convention will be IG_Hostname_{numerical number}
For Example first IG name for host Dorsey for 2 WWN will be IG_dorsey_1
If Host has more than 2 WWN than name for next Initiator group will be IG_Hostname_2 and so on if
host have more than 4 HBA ports.



Creating port groups:
Port groups may contain any number of valid front-end ports and a FA port can belong to more than one
port group. We will group pair of FA ports together and add that to single port group. We will still using
rule of 17 and FA pairing is still same as older DMX frames.

Naming Convention will be PG_FA1_FA2
For Example PG_8EA_9EB



Creating storage groups:

We can create a storage group using a range of devices, device names, device group devices, or a
device file. Symmaccess by default use dynamic lun addressing and lun numbers, for each individual
device in SG group, will be assigned while masking view gets created.

Naming Convention will be SG_{numerical number}
For Example SG_1
Each Storage Group (SG) will be assigned ONLY to ONE masking view. That mean each Cluster
member will get different SG numbers even though they could have same devices assigned. This will
make partial reclamation process easier and less risky from Storage Operation prospective.



Creating a masking view:
A masking view is a container of a storage group, a port group, and an initiator group. When we create a
masking view, the devices in the storage group become visible to the host. The devices are masked and
mapped automatically. Volume dynamic addressing is enabled by default. The Symmetrix array assigns
the next available LUN address on the FA port when the masking view is created.

Naming Convention will be MV_Hostname_{numerical number}
For Example masking view name for host Dorsey for first 2 WWN will be MV_dorsey_1
We will create multiple masking views for same host if they have more than 2 WWN or devices are
assigned to more than 2 FA ports. Numerical number in naming convention will get incremented on per
host basis.
Host with Gatekeeper will also have their own masking view. This is due to EMC Policy not to dual assign
GKs.



Script Example:
Note: Picking up devices from free pool, running Symconfigure, mapping devices to FA ports, setting SCSI-3 persistent
reservation bit on a device and setting BCV flag on a device portion of script still remain exactly same. Following example
is masking and HBA flag portion using auto provisioning group/symaccess. We will do all front end mapping using
symconfigure to keep the process same for legacy frames. Symaccess by default use dynamic lun addressing and lun
number were assigned when masking view created. That means lun number assigned on FA ports and what assigned by
dynamic lun addressing is different and for troubleshooting we have to use dynamic lun addressing not what assigned to
FA ports.
1> New Host allocation
HP Host bhprd400 (HP-UX 11iv3), bhprd401 (HP-UX 11iv2)
SUN Host bsprd500, bsprd501
All hosts other than bsprd501 have 4 HBA.
All devices assigned to all HBA.

srNumber|itemNo|device_item_no|HostWWNInfo|cluster|complete|design_device_id|designedArrayPort|designedHyperSize|designe
dLunQty|designedMetaStripWidth|designedNotes|designedStorageFrame|fileSystemName|floorLocation|hostPlatformType|nasHead
Name|nasHostGateway|nasShare|newConnection|serverName|serverType|snapShot|storageAmount|storageType|volumeName
13761|1|1_1|,,|N|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||HPv3||||Y|bhprd400|PROD|N|22|EMC|
13761|1|1_2|,,|N|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||HP||||Y|bhprd401|PROD|N|22|EMC|
13761|1|1_4|,,|N|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||SUN||||Y|bsprd500|PROD|N|22|EMC|
13761|1|1_5|,,|N|N|245901|7EA/10EB|11|2|1|2|1379|/opt/app/introscope ||SUN||||Y|bsprd501|PROD|N|22|EMC|

symaccess -sid 1379 -name IG_bsprd501_1 -type initiator -wwn 2006000000001006 create
symaccess -sid 1379 rename -wwn 2006000000001006 -alias bsprd501/2006000000001006
symaccess -sid 1379 -name IG_bsprd501_1 -type initiator -wwn 2006000000001007 add
symaccess -sid 1379 -name SG_17 -type storage devs 0746,0747 create
symaccess -sid 1379 create view -name MV_bsprd501_1 -sg SG_17 -pg PG_7EA_10EB -ig IG_bsprd501_1

symaccess -sid 1379 -name IG_bhprd400_1 -type initiator -wwn 8006000000001000 create
symaccess -sid 1379 rename -wwn 8006000000001000 -alias bhprd400/8006000000001000
symaccess -sid 1379 -wwn 8006000000001000 set hba_flags on OS2007,SPC2 -enable
symaccess -sid 1379 -name IG_bhprd400_1 -type initiator -wwn 8006000000001001 add
symaccess -sid 1379 -name IG_bhprd400_1 -type initiator set ig_flags on V -enable
symaccess -sid 1379 -name SG_18 -type storage devs 073E,073F create
symaccess -sid 1379 create view -name MV_bhprd400_1 -sg SG_18 -pg PG_7EA_10EB -ig IG_bhprd400_1






2> BAU request for existing hosts as in example 1

HP Host (already exist on frame) bhprd400 (HP-UX 11iv3), bhprd401 (HP-UX 11iv2)
SUN Host (already exit on frame) bsprd500, bsprd501
All hosts other than bsprd501 have 4 HBA.
All devices assigned to all HBA.

13761|1|1_1|,,|N|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||HPv3||||Y|bhprd400|PROD|N|22|EMC|
13761|1|1_4|,,|N|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||SUN||||Y|bsprd500|PROD|N|22|EMC|
13761|1|1_5|,,|N|N|245901|7EA/10EB|11|2|1|2|1379|/opt/app/introscope ||SUN||||Y|bsprd501|PROD|N|22|EMC|

symaccess -sid 1379 -name SG_17 -type storage devs 0750,0751 add
symaccess -sid 1379 -name SG_19 -type storage devs 074C,074D add
symaccess -sid 1379 -name SG_20 -type storage devs 074A,074B add
symaccess -sid 1379 -name SG_22 -type storage devs 074E,074F add

3> New Cluster Hosts

HP Host bhprd405 and bhprd406 (cluster host) HP-UX 11iv3
SUN Host bsprd505 and bsprd506 (cluster host)
All hosts has 2 HBA

13761|1|1_1|,,|Y|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||HPv3||||Y|bhprd405:bhprd406|PROD|N|22|EMC|
13761|1|1_2|,,|Y|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||SUN||||Y|bsprd505:bsprd506|PROD|N|22|EMC|







4> BAU Cluster request for existing hosts in example 3

HP Host (existing hosts) bhprd405 and bhprd406 (cluster host) HP-UX 11iv3
SUN Host (existing host) bsprd505 and bsprd506 (cluster host)
All hosts has 2 HBA

13761|1|1_1|,,|Y|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||HPv3||||Y|bhprd405:bhprd406|PROD|N|22|EMC|
13761|1|1_2|,,|Y|N|245901|7EA/10EB|11|2|1||1379|/opt/app/introscope ||SUN||||Y|bsprd505:bsprd506|PROD|N|22|EMC|


5> Split line request. Host has 4 HBA and some devices assigned to first 2 HBA and some on next 2. This example we
normally see for HP-UX 11iv2 hosts and dont have enough controller number on host.

HP Host bhprd410 (HP-UX 11iv3)
SUN Host bsprd510
Each Host has 4 HBA
Assigned 4 devices to each host
2 Devices on FA 7EA/10EB go to first pair of HBA
2 Devices on FA 8EA/9EB go to second pair of HBA

13761|1|1_1|,,|Y|N|245901|7EA/10EB|11|2|1|wwn1|1379|/opt/app/introscope ||HPv3||||Y|bhprd410|PROD|N|22|EMC|
13761|1|1_3|,,|Y|N|245901|7EA/10EB|11|2|1|wwn1|1379|/opt/app/introscope ||SUN||||Y|bsprd510|PROD|N|22|EMC|

symaccess -sid 1379 -name SG_27 -type storage devs 075E,075F create

symaccess -sid 1379 -name SG_28 -type storage devs 075C,075D create



symaccess -sid 1379 -name SG_29 -type storage devs 075A,075B create


6> Split line request for existing hosts used in example 5

HP Host (existing host) bhprd410 (HP-UX 11iv3)
SUN Host (existing host) bsprd510
Each Host has 4 HBA
Assigned 4 devices to each host
2 Devices on FA 7EA/10EB go to first pair of HBA
2 Devices on FA 8EA/9EB go to second pair of HBA



7> How to list device assignment?

parse_devs.pl -s 1379 -devs 0766,0767

Symmetrix ID : 1379

Device Identifer Dir:P Masking View
------ --------------- ----- --------------

0766 2006000000009905 07E:0 MV_bsprd510_1
2006000000009906 07E:0 MV_bsprd510_1

0767 2006000000009905 07E:0 MV_bsprd510_1
2006000000009906 07E:0 MV_bsprd510_1

perl ./parse_devs.pl_v1 -s 1379 -devs 0766,0767

Symmetrix ID : 1379

Device Identifer Type Dir:P Masking View InitiatorGrp PortGrp Storage Grp
------ --------------- ----- ----- -------------- ------------ ------- -----------

0766 2006000000009905 FIBRE 07E:0 MV_bsprd510_1 IG_bsprd510_1 PG_7EA_10EB SG_27
2006000000009906 FIBRE 07E:0 MV_bsprd510_1 IG_bsprd510_1 PG_7EA_10EB SG_27

0767 2006000000009905 FIBRE 07E:0 MV_bsprd510_1 IG_bsprd510_1 PG_7EA_10EB SG_27
2006000000009906 FIBRE 07E:0 MV_bsprd510_1 IG_bsprd510_1 PG_7EA_10EB SG_27

8> How to get information based on Group name or WWN?


./get_view.pl

usage: ./get_view.pl s <sid> || -w <wwn> || -ig <IG Name> || -sg <SG Name> || -pg <PG Name> || -mv <Masking View>

-s : sid
-w : HBA WWN
-ig : Initiator Group Name
-pg : Port Group Name
-sg : Storage Group Name
-mv : Masking View Name

kg7008@wslbasf04:/export/home/kg7008>./get_view.pl -s 1379 -ig IG_bsprd510_2

Symmetrix ID : 1379

Initiator Group: IG_bsprd510_2

MV: MV_bsprd510_2

kg7008@wslbasf04:/export/home/kg7008>./get_view.pl -s 1379 -w 2006000000009905

Symmetrix ID : 1379

Initiator Group: IG_bsprd510_1
MV: MV_bsprd510_1

kg7008@wslbasf04:/export/home/kg7008>./get_view.pl -s 1379 -sg SG_26

Symmetrix ID : 1379

Storage Group: SG_26

MV: MV_bhprd406_1

kg7008@wslbasf04:/export/home/kg7008>./get_view.pl -s 1379 -pg PG_8EA_9EB

Symmetrix ID : 1379

Port Group: PG_8EA_9EB

MV: MV_bhprd401_1
MV: MV_bhprd180_1
MV: MV_wslenv47_vTIL_1121
MV: MV_bhprd179_3
MV: MV_bsprd510_2
MV: MV_bhprd181_1
MV: MV_dspcvdb01_1
MV: MV_bhprd179_1
MV: MV_bhprd410_1
MV: MV_bsprd178_1
MV: MV_bsprd175_2

VMAX Autoprovisioning Group Standards

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

VMAX Autoprovisioning Group Standards

Enviado por

Direitos autorais:

Formatos disponíveis

V-MAX Autoprovisioning Group Standards

RESTRICTED - PROPRIETARY INFORMATION

Você também pode gostar