You are on page 1of 35

Symmetrix Access Logix

Ajay Shekhar

EMC CONFIDENTIALINTERNAL USE ONLY

An example environment

0
1
0
1
0
1

HBA

HBA

0
1
0
1
0
1

7E

050
051
052
053
054
055

7F
7G

8E
8F
8G
100

101

102

HOST
Next Generation
Symmetrix
EMC CONFIDENTIALINTERNAL USE ONLY

Storage Groups

Devices 050 through 055 need to be


made visible to a host hence, they
will be grouped together in a Storage
Group
> symaccess -sid 234 -name
TRAINING_SG -type storage
create
The desired devices are then added
to the newly created storage group
> symaccess -sid 234 -name
TRAINING_SG -type storage
add devs 050:055
The CLI allows storage group
creation and addition in one
command
> symaccess -sid 234 -name
TRAINING_SG -type storage
create devs 050:055
EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_SG
050
051
052
053
054
055
7E
7F
7G
8E
8F

100

101

102

8G

Next Generation
Symmetrix
3

Storage Groups

>

symaccess -sid 234 -type


storage show TRAINING_SG

Symmetrix ID

: 000192600234

Last updated at

: 06:30:58 AM on

Sun Nov 23,2008

Storage Group Name: TRAINING_SG


Devices

: 0050:0055

Masking View Names


{
None
}
EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_SG
050
051
052
053
054
055
7E
7F
7G
8E
8F

100

101

102

8G

Next Generation
Symmetrix
4

Common Operations on Storage Groups

Common Operations that are performed on Storage Groups include


Creating the group and optionally populating it using device lists, device ranges,
device groups or a device file
Removing devices from Storage groups. Optionally, devices can be unmapped when
they are removed from a storage group that is part of a view
Adding additional devices to Storage groups. Optionally, devices can be assigned lun
numbers, if the storage group is part of a view(s)
The contents of the storage group can be listed in varying amount of detail
It is also possible to list out the storage group(s) that a particular device belongs to
The storage group can be renamed or deleted

EMC CONFIDENTIALINTERNAL USE ONLY

Port Groups

The devices need to be exported on


three ports of the the NextGen Symm
in the example chosen here we have
ports 7E:0, 7G:1 and 8F:0

> symaccess -sid 234 -name


TRAINING_PG -type port
create
The desired ports are then added to
the newly created port group
> symaccess -sid 234 -name
TRAINING_PG -type port

dirport 7E:0,7G:1,8F:0 add


A composite CLI to do both the actions
is
> symaccess -sid 234 create
-name TRAINING_PG -type port
create 7E:0,7G:1,8F:0
Note : Only ports with ACLX enabled
will be allowed in a group
EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_PG
0
1
0
1
0
1
0
1
0
1
0
1

7E

050
051
052
053
054
055

7F
7G

8E
8F
8G
100

101

102

Next Generation
Symmetrix
6

Port Groups

> symaccess -sid 234


-type port show
TRAINING_PG
Symmetrix ID

: 000192600234

Last updated at : 06:30:58 AM on Sun


Nov 23,2008
Port Group Name : TRAINING_PG
Director Identification
{
FA-7E:0

TRAINING_PG
0
1
0
1
0
1
0
1
0
1
0
1

7E

050
051
052
053
054
055

7F
7G

8E
8F
8G

FA-7G:1
FA-8F:0

100

101

102

}
Masking View Names
{
None
}
EMC CONFIDENTIALINTERNAL USE ONLY

Next Generation
Symmetrix
7

Common Operations on Port Groups

Common Operations that are performed on Port Groups include


Creating the group and optionally populating it using a list of ports
Removing ports from Port groups. Optionally, devices can be unmapped from the
removed ports, if the port group is part of a view(s)
Adding ports to device groups
The contents of the port group can be listed in varying amount of detail
It is also possible to list out the port group(s) that a particular port belongs to
The port group can be renamed or deleted

EMC CONFIDENTIALINTERNAL USE ONLY

Initiator Groups

The storage that has been chosen has


to be made visible to both the HBAs
on this host
> symaccess -sid 234 -name
TRAINING_IG -type initiator
create
The desired initiators are then added
to the newly created initiator group
> symaccess -sid 234 -name
TRAINING_IG -type initiator
-wwn 210000e08b04daac add
> symaccess -sid 234 -name
TRAINING_IG -type initiator
-wwn 210000e08b1ed7f1 add
Initiator names could be entered in an
input file which can be passed to the
symaccess CLI
EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_IG
HBA
WWN: 210000e08b04daac
WWN: 210000e08b1ed7f1
HBA
HOST
9

Initiator Groups
>

symaccess -sid 234 -type initiator


-detail show TRAINING_IG

Symmetrix ID

: 000192600234

Last updated at
23,2008

: 06:30:58 AM on Sun Nov

Initiator Group Name


Originator Port wwn
User-generated Name
FCID Lockdown
Heterogeneous Host
Port Flag Overrides
CHAP Enabled
RADIUS Enabled
Type

:
:
:
:
:
:
:
:
:

TRAINING_IG
210000e08b04daac
api196/HBA_1
No
No
No
N/A
N/A
Fibre

Originator Port wwn


User-generated Name
FCID Lockdown
Heterogeneous Host
Port Flag Overrides
CHAP Enabled
RADIUS Enabled
Type

:
:
:
:
:
:
:
:

210000e08b1ed7f1
api196/HBA_2
No
No
No
N/A
N/A
Fibre

EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_IG
HBA
WWN: 210000e08b04daac
WWN: 210000e08b1ed7f1
HBA
HOST

10

Common Operations on Initiator Groups

Common Operations that are performed on Initiator Groups include


Creating the group and optionally populating it using one initiator, a file containing a
list of initiators or creating a cascaded initiator group by populating the initiator group
with another initiator group. ISCSI initiators (specified by the iscsi name) or Fibre
Initiators (specified by the WWN) can be added
Removing initiators from initiator groups
Adding additional initiators to Initiator groups
The contents of the initiator group can be listed in varying amount of detail
It is also possible to list out the initiator group(s) that a particular initiator belongs to
The initiator group can be renamed or deleted

EMC CONFIDENTIALINTERNAL USE ONLY

11

Operations supported on HBAs

There are a number of operations that could be done on individual HBAs


most of these can still be done using the new symaccess CLI. These
include
setting various HBA flags

Common_Serial_Number
Disable_Q_Reset_on_UA
Environ_Set
Siemens
Volume_Set_Addressing
Avoid_Reset_Broadcast
AS400
OpenVMS
SCSI_3
Sunapee
Sequent
SPC2_Protocol_Version
SCSI_Support1

[C]
[D]
[E]
[S]
[V]
[ARB]
[AS4]
[OVMS]
[SC3]
[SCL]
[SEQ]
[SPC2]
[OS2007]

set fcid lockdown


set radius and chap credentials
EMC CONFIDENTIALINTERNAL USE ONLY

12

Masking Views

Tying these three different groups


together into a VIEW makes the
chosen devices visible on the host

TRAINING_PG

0
1
0
1
0
1
7E

7F

7G

8E

8F

8G

050
051
052
053
054
055

101 102

EMC CONFIDENTIALINTERNAL USE ONLY

TRAINING_VIEW

100

During view creation (or later on when


devices are added to an existing
view), if the devices are unmapped,
they will be mapped to the ports
contained in the port group. This
feature has been requested by
numerous customers, but will result in
the slowing down of the masking
operation

TRAINING_IG

0
1
0
1
0
1

symaccess -sid 234 create view


name TRAINING_VIEW storgrp
TRAINING_SG portgrp
TRAINING_PG initgrp
TRAINING_IG

TRAINING_SG
13

Displaying the View

>symmask sid 237 show view TRAINING_VIEW


Symmetrix ID
: 000192600234
Last updated at
: 08:46:54 AM
on Tue Jul 29,2008
Masking View Name
: TRAINING_VIEW
Initiator Group Name
: TRAINING_IG
Host Initiators
{
210000e08b04daac
210000e08b1ed7f1
}
Port Group Name
: TRAINING_PG
Director Identification
{
FA-7E:0
Storage Group Name
: TRAINING_SG
FA-7G:1
Sym Dev
Host
FA-8F:0
Name
Dir:P Physical Device Name Lun Attr Cap(MB)
}
------ ----- --------------------- ---- ---- ------0050
7E:0 /dev/rdsk/c6t2d1s2
1
2048
7F:1 /dev/rdsk/c6t2d1s2
1
2048
8F:0 /dev/rdsk/c6t2d1s2
1
2048
0051
7E:0 /dev/rdsk/c6t2d1s2
2
2048
...
EMC CONFIDENTIALINTERNAL USE ONLY

14

Adding Devices to this VIEW


If devices 101, 102 and 103 need to
be visible to the host through the
same ports and on the same initiators,
they can be added to the existing
storage group

TRAINING_PG

7E

7F

7G

050
051
052
053
054
055

102

100
101

EMC CONFIDENTIALINTERNAL USE ONLY

0
1
0
1
0
1

8E

8F

8G

In a similar fashion, if the existing


devices needed to be masked to a
different port or to more initiators,
these elements can be added/deleted
from their respective groups

TRAINING_VIEW

0
1
0
1
0
1

symaccess -sid 234name


TRAINING_SG type storage
add devs 101:103

TRAINING_IG

TRAINING_

15

Making more devices visible to the host comparison

There is some upfront work required to create the three


groups and tying them into a view. However, the addition of
devices to the storage group illustrates one of the benefits of
this new scheme of masking over the one used in DMX. In
DMX, to make these three additional devices visible would
have required SIX commands
> symmask sid 234 wwn 210000e08b04daac p 7E:0 add devs 101:103
> symmask sid 234 wwn 210000e08b04daac p 7G:1 add devs 101:103
> symmask sid 234 wwn 210000e08b04daac p 8F:0 add devs 101:103
> symmask sid 234 wwn 210000e08b1ed7f1 p 7E:0 add devs 101:103
> symmask sid 234 wwn 210000e08b1ed7f1 p 7G:1 add devs 101:103
> symmask sid 234 wwn 210000e08b1ed7f1 p 8F:0 add devs 101:103

EMC CONFIDENTIALINTERNAL USE ONLY

16

Common Operations on Views

Common operations on views include


View creation : When a view is created, a populated storage group, a populated port
group and an initiator group need to specified
Views containing a single HBA, single port and a single range of devices can be specified on
the command line, along with a name prefix. The symaccess CLI will create the underlying
storage group, port group, initiator group and the view naming them according to the
supplied prefix

Views can be deleted and renamed


The contents of views can be displayed in varying amounts of detail

EMC CONFIDENTIALINTERNAL USE ONLY

17

Mapping devices will happen within masking

Mapping
In prior versions of Solutions Enabler, mapping of devices was an essential step that
had to be done using the symconfigure CLI. Devices that were mapped and masked
were the ones that were visible to the host
In Solutions Enabler 7.0, mapping devices is still needed. However, if the symaccess
CLI finds unmapped devices during view creation, it will map the unmapped devices
to all the ports in the port group associated with the view

Unmapping
The user has a choice of optionally unmapping the device(s)
Unmapping all the devices when the view is deleted
Unmapping devices that are removed from a storage group while that storage group is part
of a view
Unmapping devices from the port if that port is removed from a port group (the port group
has to be part of a view for this to happen)

Note that if the user requests devices to be unmapped, all affected devices will be
unmapped. This includes devices that were automatically mapped by the symaccess
CLI and devices that were explicitly mapped by the user using the symconfigure CLI

EMC CONFIDENTIALINTERNAL USE ONLY

18

Cascaded Initiator Groups

In a clustered environment, some


devices need to be seen by the entire
cluster. Other devices (e.g.
Gatekeepers) may need to be seen
only by individual hosts in the cluster
To achieve this in the example on the
right, THREE initiator groups and
FOUR storage groups, are created
first assume one PG
IG1: WWN1; IG2 : WWN2; IG3:
WWN3
SG1: 101,102 ; SG2: 201, 202 ;
SG3: 301, 302 and
SG4: 050:055
PG1 : 7E:0

EMC CONFIDENTIALINTERNAL USE ONLY

H
O
S
T
1
H
O
S
T
2
H
O
S
T
3

100
101
WWN 1
200
201
050
051
052
053
054
055
WWN 2
7E:0
300
301
WWN 3

19

Cascaded Initiator Groups


C
L
U
A new Initiator Group is created which
S
consists of
T
CLUSTER_IG : IG1, IG2, IG3
E
Four views are now created
R
CLUSTER_VIEW : CLUSTER_IG, PG1 and
SG4
_
This view makes all the cluster devices
I
visible to all hosts
GK1_VIEW : IG1, PG1, SG1
G
The single port group PG1 is omitted
to make it less cluttered

GK1_VIEW

EMC CONFIDENTIALINTERNAL USE ONLY

SG1
101

WWN 1
200 SG2
201

050
051
052
053
054
055

IEW
V
2_
GK

WWN 2

This makes the GK 101 and 102 visible only


to Host1
GK2_VIEW and GK3_VIEW are created to
make GKs visible to these hosts

Cascading of Initiator Groups in only


allowed to a depth of 1 i.e. an
Initiator can be part of an IG, which in
turn can be part of another IG

100

CLUSTER_
VIEW

W
VIE
_
3
GK

300

SG4

SG3
301

WWN 3

20

Compatibility Mode

Customers doing masking operations on older generation Symms have


scripts that are being used. Since the way masking is being done in the
Next Generation Symmetrix has changed fundamentally, these scripts
will now break. To ease the migration of customers to this new way of
masking, a compatibility mode is being provided
The older masking commands will automatically create the masking
groups and views for the users. This mode has significant limitations
especially in the area of naming these groups
Users also need to keep in mind that even though these commands
have the same (or similar) syntax to the commands that existed, on the
Next Generation Symmetrix, they are creating the masking groups.
Hence, end users need to be cognizant of these groups and need to
know how to manipulate them

EMC CONFIDENTIALINTERNAL USE ONLY

21

Compatibility Mode (cont.)

The names of the automatically created groups will be based on


For fibre HBAs, no script modification is needed as the WWN of the HBA will be used
to generate the group names
A new argument -name that is required for iSCSI initiators and will form the basis of
the group names

Example
symmask -sid 234 -wwn 210000e08b04daac -dir 7E -p 1 add devs 0026:0028
The above command will create
An Initiator Group
210000e08b04daac
A Port Group
210000e08b04daa2_7E_1
A Storage Group
210000e08b04daa2_7E_1
A View
210000e08b04daa2_7E_1

for the user


The user has to be aware that these entities were created, as the groups
now have to obey the rules of the new masking scheme
EMC CONFIDENTIALINTERNAL USE ONLY

22

Compatibility Mode - Restrictions

Groups that are created using the compatibility mode (symmask) can be
manipulated using the symmask commands. However, if symaccess is
used to edit any of these groups, then symmask can no longer be used
to view/edit them.
Users should be using the new symaccess CLI for all masking operations. The old
symmask/symmaskdb commands are provided as a limited means of easing
migration to the symaccess commands. Once symaccess is used, it will be the only
command that will be allowed

symmask and symmaskdb commands will list out the details of only the
groups and views created using these commands. The symaccess CLI
should be used to view the entire masking picture

EMC CONFIDENTIALINTERNAL USE ONLY

23

Backing up Masking information

The masking information can be backed up to a file using the syntax


symaccess -sid <SymmID> -f <backup_filename> [-noprompt] backup

The file that contains the backup can now be used with all the
symaccess commands that retrieve masking information
The backup can be restored by specifying the restore switch instead of
the backup switch
A restore will wipe out the settings on the Symmetrix it will restore the
settings from the backup file

Ports will be returned to port groups if they have the ACLX attribute set
Devices will be returned to storage groups if they are devices that can be masked
Views will be restored only if the port and storage groups contain valid entries
LUN information will be restored if its valid for port settings

EMC CONFIDENTIALINTERNAL USE ONLY

24

Masking alias enhancements for DMX

Aliasing is a technique that allows a user to give human-readable names


to an Initiator. SE Masking commands allow the alias name to be used
instead of the WWN, in a number of commands. An alias is a two part
name that usually takes the form
host name / adapter

In a lot of customer environments, devices are masked on several ports


of the DMX to all the initiators of a host. This requires (# of initiators * #
of ports) number of symmask commands to be run to map a range of
devices
SE 7.0 allows this action to be performed using one symmask
command, if the alias is set so that the first part of the alias for all HBAs
belonging to the same host is the same (the recommendation is to use
the hostname as this first part)

EMC CONFIDENTIALINTERNAL USE ONLY

25

Masking by Alias Enhancements for DMX Examples

If devices 050:054 are visible on all


four of the ports in the picture on the
left and through both the HBAs on the
host, to make device 055 visible
similarly would take four commands
symmask sid 345 awwn api1182/hba1 dir 2C p 0
add dev 055
symmask sid 345 awwn api1182/hba1 dir 2C p 1
add dev 055
symmask sid 345 awwn api1182/hba2 dir 2D p 0
add dev 055
symmask sid 345 awwn api1182/hba2 dir 2D p 1
add dev 055

This can now be accomplished by


using the single command
symmask sid 345 host api1182
dir ALL p ALL add dev 050:055

NOTE : These records must already


exist in the database for these options
to work
EMC CONFIDENTIALINTERNAL USE ONLY

DMX
0
1

2D
050
051
052
053
054

HBA
WWN : 210000e08b04daac
Alias : api1182/hba1

055
WWN : 210000e08b1ed7f1
Alias : api1182/hba2

0
1

2C

HBA
Host :
api1182

26

Beta Use Case : Database server and backup


Use Case One Assign storage for primary database application on a new production server.
Requires multiple storage paths and local replication to a backup server
app1dg

prodserv_hbas

backupserv_hbas

production_ports

app1_std app1_bcv

1) Create Device Group. Add Application STDs and BCVs: app1dg

7) Create Production Server View: prodserv_app1 = app1_std + production_ports + prodserv_hbas

2) Create Storage Group from DG STDs: app1_std

8) Create Backup Server View: backupserv_app1 = app1_bcv + production_ports + backupserv_hbas

3) Create Storage Group from DG BCVs: app1_bcv


4) Create Port Group: production_ports
5) Create Initiator Group for Production Server: prodserv_hbas
6) Create Initiator Group for Production Server: backupserv_hbas

EMC CONFIDENTIALINTERNAL USE ONLY

27

Beta Use Case : Development Server

Use Case Two Assign storage to a development server for a test application. Development server has a single path to storage. No
replication is required.

Create View with single symaccess command:


symaccess -sid <beta Tigon sid> create view -name dev_app1 -wwn <Dev Server HBA WWN HBA 7> -dirport 3A:0 devs <startdev:enddev>

Command Automatically creates:


View:
dev_app1;
Storage group:
dev_app1
Initiator group:
dev_app1
Port group:
dev_app1

EMC CONFIDENTIALINTERNAL USE ONLY

28

Beta Use Case : Storage for a second application

Use Case Three - Assign storage for a second primary application on the production server. Requires multiple paths and associated local
replication to a backup server

prodserv_hbas

app2dg

production_ports

backupserv_hbas
1) Create Device Group for New Application. Add Application STDs and BCVs into DG

app2_std app2_bcv

2) Create Storage Groups for Production and Backup Server from DG STDs and BCVs
3) Create View utilizing pre-existing port and initiator groups for production server
4) Create View utilizing pre-existing port and initiator groups for backup server
EMC CONFIDENTIALINTERNAL USE ONLY

29

Beta Use Case : Additional Storage for


development server

Use Case Four Add a second HBA to the initiator group for the development server

SG - dev_app1
IG - dev_app1

PG - dev_app1

Update entire view with a single symaccess command:


symaccess -sid <beta Tigon sid> -name dev_app1 -type initiator -wwn <Dev Server HBA WWN - HBA8> add

EMC CONFIDENTIALINTERNAL USE ONLY

30

Beta Use Case : Masking gatekeepers

Use Case Five - Provisioning SYMAPI Control Servers

Single command can now be used to map and mask gatekeepers to individual HBAs
1) symaccess -sid <beta Tigon sid> create view -name CS1_path1 -wwn <CS HBA WWN HBA 1> -dirport 3A:0 devs <gkstartdev:gkenddev>
2) symaccess -sid <beta Tigon sid> create view -name CS1_path2 -wwn <C S HBA WWN HBA 2> -dirport 4A:0 devs <gkstartdev:gkenddev>

EMC CONFIDENTIALINTERNAL USE ONLY

31

Beta Use Case : Storage in a database cluster

Use Case Six Assign storage for primary database application on a new production database cluster. Requires multiple storage paths and local replication
to a backup server

1) Create Boot Disk View for Cluster Node 1


2) Create Boot Disk View for Cluster Node 2
3) Expand View for Node 1 to include HBA 2 and FA 2:0

9) Create Cluster Port Group


10) Create Cascaded Initiator Group Using Existing Node 1 and Node2 Initiator Groups
11) Create Cluster Storage View using Cluster Storage, Port, and Initiator Groups

4) Expand View for Node 2 to include HBA 4 and FA 4:0


5) Create Device Group for Cluster Application. Add Application STDs and BCVs
6) Create Storage Groups for Cluster and Backup Server from DG STDs and BCVs

12) Create Backup View for Application Using Pre-existing IG and PG for Backup Server

7) Add Quorum Disk into Cluster Storage Group

EMC CONFIDENTIALINTERNAL USE ONLY

32

Beta Use Case : Second Application in a cluster

Use Case Seven - Assign storage for a second primary application on the production database cluster. Requires multiple paths and
associated local replication to a backup server

app4dg

1) Create Device Group for Cluster Application. Add Application STDs and BCVs
2) Add DG STDs into pre-existing production cluster storage group
3) Add DG BCVs into pre-existing backup server storage group

EMC CONFIDENTIALINTERNAL USE ONLY

33

Beta : Ease of use comparison


Use
Case

Task

Number of
symmask &
symconfigure
commands

Number of
symaccess
commands

Commands
Reduced %

Use
Case 1

Assign storage for primary database application on the production server. Requires multiple
storage paths and local replication to a backup server

13

10

23%

Use
Case 2

Assign storage to a development server for a test application. Development server has a
single path to storage. No replication is required.

75%

Use
Case 3

Assign storage for a second primary application on the production server. Requires multiple
paths and associated local replication to a backup server

13

46%

Use
Case 4

Add a second HBA to the initiator group for the development server.

0%

Use
Case 5

Provisioning SYMAPI Control Servers 6 Unique GKs/path/symm

71%

Use
Case 6

Provisioning Production Database Clusters Requires multiple paths to storage from each
node and associated local replication to a backup server

25

17

32%

Use
Case 7

Assign storage for a second primary application on the production database cluster. Requires
multiple paths and associated local replication to a backup server

17

EMC CONFIDENTIALINTERNAL USE ONLY

(Utilizes preexisting
port and initiator
groups from Use
Case 1)

(Utilizes preexisting
port and initiator
groups from Use
Case 1 for backup
server)

5
(Utilizes preexisting
views from Use
Case 6 for cluster
and backup
server )

71%

34