Вы находитесь на странице: 1из 24

Provisioning Gatekeepers to a Management Host

Provisioning Gatekeepers to a Management Host


In this example, gatekeepers are provisioned to a management host that will monitor and manage the
Symmetrix using Solutions Enabler.
Best practice for assigning gatekeepers to hosts specifies that gatekeeper device be assigned
on only a single front-end path.

Steps for provisioning storage:


for simple configurations you can create a masking view for a single initiator on a single port with any
number of devices using just one symaccess command...
After the masking view has been created, devices are available to the initiators on the storage ports.
Run host-specific commands to configure the devices to the host operating system.

Step 1 - Create a view and specify a view name, HBA pWWN, front-end port, and Symmetrix
volumes for the first path.
the view is assigned a name by the user and that name is used for the initiator, port, and storage
groups. To display the HBA pWWNs and the ports that they are zoned to:
# symaccess list hba
Identifier Physical Device Path Symmetrix ID Dir:P
---------------- -------------------------------- ------------ ----10000000c9767816 c3t5000097208139918d0s2 000192601254 07E:0
10000000c9767817 c4t5000097208139959d0s2 000192601254 07F:1

To make gatekeepers 08F - 092 available on the first path (first HBA), do the following:
# symaccess create view -name mgmtGKpath0 -wwn 10000000c9767816 -dirport 7E:0 devs
08F:092 -sid 1254
the view is assigned a name by the user and that name is used for the initiator, port, and storage
groups.

Step 2 - Create a view and specify a view name, HBA WWN, front-end port, and Symmetrix
volumes for the second path.
To make gatekeepers 093 096 available on the second path (2nd HBA), do the following:
# symaccess create view -name mgmtGKpath1 -wwn 10000000c9767817 -dirport 7F:1 devs
093:096 -sid 1254

devices are now available to the initiators on the storage ports. After the host configures the devices,
they are available to the operating system on both paths:
# symaccess list view -sid 1254

Symmetrix ID : 000192601254
Masking View Name Initiator Group Port Group Storage Group
------------------- ------------------- ------------------- ----------------mgmtGKpath0 mgmtGKpath0 mgmtGKpath0 mgmtGKpath0
mgmtGKpath1 mgmtGKpath1 mgmtGKpath1 mgmtGKpath1

# syminq
Device Product Device
---------------------------- -------------------------- --------------------Name Type Vendor ID Rev Ser Num Cap (KB)
---------------------------- -------------------------- --------------------/dev/rdsk/c3t50*8d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c3t50*8d1s2 GK EMC SYMMETRIX 5874 540008F000 5760
/dev/rdsk/c3t50*8d2s2 GK EMC SYMMETRIX 5874 5400090000 5760
/dev/rdsk/c3t50*8d3s2 GK EMC SYMMETRIX 5874 5400091000 5760
/dev/rdsk/c3t50*8d4s2 GK EMC SYMMETRIX 5874 5400092000 5760
/dev/rdsk/c4t50*9d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c4t50*9d1s2 GK EMC SYMMETRIX 5874 5400093000 5760
/dev/rdsk/c4t50*9d2s2 GK EMC SYMMETRIX 5874 5400094000 5760
/dev/rdsk/c4t50*9d3s2 GK EMC SYMMETRIX 5874 5400095000 5760
/dev/rdsk/c4t50*9d4s2 GK EMC SYMMETRIX 5874 5400096000 5760

# symcfg discover
# symaccess show view mgmtGKpath0 -sid 1254
Symmetrix ID : 000192601254
Masking View Name : mgmtGKpath0
Initiator Group Name : mgmtGKpath0
Host Initiators
{
WWN : 10000000c9767816
}
Port Group Name : mgmtGKpath0

Director Identification
{
FA-7E:0
}
Storage Group Name : mgmtGKpath0
Sym Dev Host
Name Dir:P Physical Device Name Lun Attr Cap(MB)
------ ----- ----------------------- ---- ---- ------008F 07E:0 c3t5000097208139918d1s* 1 5
0090 07E:0 c3t5000097208139918d2s* 2 5
0091 07E:0 c3t5000097208139918d3s* 3 5
0092 07E:0 c3t5000097208139918d4s* 4 5

# symaccess show view mgmtGKpath1 -sid 1254


Symmetrix ID : 000192601254
Masking View Name : mgmtGKpath1
Initiator Group Name : mgmtGKpath1
Host Initiators
{
WWN : 10000000c9767817
}
Port Group Name : mgmtGKpath1
Director Identification
{
FA-7F:1
}
Storage Group Name : mgmtGKpath1
Sym Dev Host
Name Dir:P Physical Device Name Lun Attr Cap(MB)
------ ----- ----------------------- ---- ---- ------0093 07F:1 c4t5000097208139959d1s* 1 5
0094 07F:1 c4t5000097208139959d2s* 2 5
0095 07F:1 c4t5000097208139959d3s* 3 5
0096 07F:1 c4t5000097208139959d4s* 4 5

Present storage to a backup and production hosts


Present storage to a backup and production hosts
In this example, two new hosts have been added to the SAN and storage needs to be provisioned.
Storage groups, port group, and initiator groups are first created. Then the applicable groups must be
combined into a masking view for each host, which will do the mapping and masking so that the storage
is accessible. In this example a Symmetrix device group will be created and will be used to provide the
device lists for the storage groups.

Steps for provisioning storage:


Step 1 - Create a device group, add the production volumes, add the clone target volumes:
# symdg create proddb_dg
# symld -g proddb_dg addall dev -range 798:79B -sid 1254
# symld -g proddb_dg addall dev -range 912:915 tgt
The device group now contains the standard volumes (STD) for the production host and the target
volumes (TGT) for the backup host:
# symdg show proddb_dg
Group Name: proddb_dg
Group Type : REGULAR
Device Group in GNS : No
Valid : Yes
Symmetrix ID : 000192601254
Group Creation Time : Fri Jan 30 16:06:03 2009
Vendor ID : EMC Corp
Application ID : SYMCLI
Number of STD Devices in Group : 4
Number of Associated GK's : 0
Number of Locally-associated BCV's : 0
Number of Locally-associated VDEV's : 0
Number of Locally-associated TGT's : 4
Number of Remotely-associated VDEV's(STD RDF): 0
Number of Remotely-associated BCV's (STD RDF): 0
Number of Remotely-associated TGT's(TGT RDF) : 0
Number of Remotely-associated BCV's (BCV RDF): 0

Number of Remotely-assoc'd RBCV's (RBCV RDF) : 0


Number of Remotely-assoc'd BCV's (Hop-2 BCV) : 0
Number of Remotely-assoc'd VDEV's(Hop-2 VDEV): 0
Number of Remotely-assoc'd TGT's (Hop-2 TGT) : 0
Standard (STD) Devices (4):
{
-------------------------------------------------------------------Sym Cap
LdevName PdevName Dev Att. Sts (MB)
-------------------------------------------------------------------DEV001 N/A 0798 RW 4314
DEV002 N/A 0799 RW 4314
DEV003 N/A 079A RW 4314
DEV004 N/A 079B RW 4314
}
TGT Devices Locally-associated (4):
{
-------------------------------------------------------------------Sym Cap
LdevName PdevName Dev Att. Sts (MB)
-------------------------------------------------------------------TGT001 N/A 0912 RW 4314
TGT002 N/A 0913 RW 4314
TGT003 N/A 0914 RW 4314
TGT004 N/A 0915 RW 4314
}

Step 2 - Create the production storage group that contains the production volumes.
For this step, the device group will be used to provide the device list for the symaccess command. The
standard devices will be added to the group by default:
# symaccess create -name dbprod_stor -type storage -g proddb_dg -sid 1254
Groups that have been created can be viewed using symaccess list and symaccess show commands:
# symaccess list -type storage -name dbprod_stor -sid 1254 -v
Symmetrix ID : 000192601254
Storage Group Name : dbprod_stor

Device Count : 4
Masking View Count : 0
Last updated at : 09:47:30 PM on Fri Jan 30,2009
# symaccess show dbprod_stor -type storage -sid 1254
Symmetrix ID : 000192601254
Last updated at : 09:47:30 PM on Fri Jan 30,2009
Storage Group Name : dbprod_stor
Devices : 0798:079B
Masking View Names
{
None
}

Step 3 - Create the backup storage group that contains the clone target volumes.
For this step, the device group will be used with the tgt flag to add the target devices:
# symaccess create -name dbbackup_stor -type storage -g proddb_dg -tgt -sid 1254
# symaccess show dbbackup_stor -type storage -sid 1254
Symmetrix ID : 000192601254
Last updated at : 10:48:42 PM on Fri Jan 30,2009
Storage Group Name : dbbackup_stor
Devices : 0912:0915
Masking View Names
{
None
}
Step 4 Create the port group containing the two Symmetrix ports to which the HBAs are zoned:
# symaccess create -name dbsrv_port -type port -dirport 7E:0,7F:1 -sid 1254
# symaccess show dbsrv_port -type port -sid 1254
Symmetrix ID : 000192601254
Last updated at : 04:09:19 PM on Mon Feb 02,2009
Port Group Name : dbsrv_port
Director Identification
{
FA-7E:0
FA-7F:1
}

Masking View Names


{
None
}
The detail option can also be used with symaccess list to generate output with the port and view
counts in columns:
# symaccess list -type port -name dbsrv_port -sid 1254 -detail
Symmetrix ID : 000192601254
Port View
Port Group Name Count Count
-------------------------------- ----- ----dbsrv_port 2 0

Step 5 Create the production server initiator group.


In this example, the HBA pWWNs are entered by using a file. They can also be entered manually on the
command line. Each pWWN in the file must contain the string WWN: followed by the 16-digit WWN. It
cannot contain blank spaces or empty lines:
# cat /prod_WWN_file
WWN:10000000c9767816
WWN:10000000c9767817

# symaccess create -name dbprodsrv_init -type initiator -file /prod_WWN_file -sid 1254
# symaccess show dbprodsrv_init -type initiator -sid 1254
Symmetrix ID : 000192601254
Last updated at : 04:34:31 PM on Mon Feb 02,2009
Initiator Group Name : dbprodsrv_init
Host Initiators
{
WWN :10000000c9767816
WWN :10000000c9767817
}
Masking View Names
{
None
}

Parent Initiator Groups


{
None
}

Step 6 Create the backup server initiator group:


# symaccess create -name dbbackupsrv_init -type initiator -file /backup_WWN_file -sid 1254
# symaccess show dbbackupsrv_init -type initiator -sid 1254
Symmetrix ID : 000192601254
Last updated at : 08:34:22 PM on Mon Feb 02,2009
Initiator Group Name : dbbackupsrv_init
Host Initiators
{
WWN :10000000c97683e0
WWN :10000000c97683e1
}
Masking View Names
{
None
}
Parent Initiator Groups
{
None
}

Step 7 Create the production server masking view containing the production storage group,
port group, and production initiator group.
Once the masking view command completes and the prompt returns, the devices will be mapped and
masked and available to the production host:
# symaccess create view -name dbprodsrv_view -storgrp dbprod_stor -portgrp dbsrv_port
initgrp dbprodsrv_init sid 1254
The production masking view has now been created. Both symaccess list and symaccess show display
the view along with its associated initiator group, port group, and storage group:
# symaccess list view -name dbprodsrv_view -sid 1254

Symmetrix ID : 000192601254
Masking View Name Initiator Group Port Group Storage Group
------------------- ------------------- ------------------- -----------------dbprodsrv_view dbprodsrv_init dbsrv_port dbprod_stor
# symaccess show view dbprodsrv_view -sid 1254
Symmetrix ID : 000192601254
Masking View Name : dbprodsrv_view
Initiator Group Name : dbprodsrv_init
Host Initiators
{
WWN : 10000000c9767816
WWN : 10000000c9767817
}
Port Group Name : dbsrv_port
Director Identification
{
FA-7E:0
FA-7F:1
}
Storage Group Name : dbprod_stor
Sym Dev Host
Name Dir:P Physical Device Name Lun Attr Cap(MB)
------ ----- ----------------------- ---- ---- -------

0798 07E:0 Not Visible 1 4314


07F:1 Not Visible 1 4314
0799 07E:0 Not Visible 2 4314
07F:1 Not Visible 2 4314
079A 07E:0 Not Visible 3 4314
07F:1 Not Visible 3 4314
079B 07E:0 Not Visible 4 4314
07F:1 Not Visible 4 4314
After running the host-specific commands to configure new devices,
the Symmetrix volumes in the storage group are available to the host:
# syminq
Device Product Device
---------------------------- -------------------------- ---------------------

Name Type Vendor ID Rev Ser Num Cap (KB)


---------------------------- -------------------------- --------------------/dev/rdsk/c3t50*8d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c3t50*8d1s2 EMC SYMMETRIX 5874 5400798000 4417920
/dev/rdsk/c3t50*8d2s2 EMC SYMMETRIX 5874 5400799000 4417920
/dev/rdsk/c3t50*8d3s2 EMC SYMMETRIX 5874 540079A000 4417920
/dev/rdsk/c3t50*8d4s2 EMC SYMMETRIX 5874 540079B000 4417920
/dev/rdsk/c4t50*9d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c4t50*9d1s2 EMC SYMMETRIX 5874 5400798000 4417920
/dev/rdsk/c4t50*9d2s2 EMC SYMMETRIX 5874 5400799000 4417920
/dev/rdsk/c4t50*9d3s2 EMC SYMMETRIX 5874 540079A000 4417920
/dev/rdsk/c4t50*9d4s2 EMC SYMMETRIX 5874 540079B000 4417920

Step 8 Create the backup server masking view that contains the backup storage group, port
group, and backup initiator group:
# symaccess create view -name dbbackupsrv_view -storgrp dbbackup_stor -portgrp dbsrv_port
initgrp dbbackupsrv_init sid 1254
The backup masking view has now been created. Both symaccess list and symaccess show display the
view along with its associated initiator group, port group, and storage group:
# symaccess list view -name dbbackupsrv_view -sid 1254
Symmetrix ID : 000192601254
Masking View Name Initiator Group Port Group Storage Group
------------------- ------------------- ------------------- -----------------dbbackupsrv_view dbbackupsrv_init dbsrv_port dbbackup_stor

# symaccess show view dbbackupsrv_view -sid 1254


Symmetrix ID : 000192601254
Masking View Name : dbbackupsrv_view
Initiator Group Name : dbbackupsrv_init
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Port Group Name : dbsrv_port
Director Identification

{
FA-7E:0
FA-7F:1
}
Storage Group Name : dbbackup_stor
Sym Dev Host

Name Dir:P Physical Device Name Lun Attr Cap(MB)

------ ----- ----------------------- ---- ---- -------

0912

07E:0 Not Visible 1 4314

07F:1 Not Visible 1 4314

0913

07E:0 Not Visible 2 4314

07F:1 Not Visible 2 4314

0914

07E:0 Not Visible 3 4314

07F:1 Not Visible 3 4314

0915

07E:0 Not Visible 4 4314

07F:1 Not Visible 4 4314

After running the host-specific commands to configure new devices, the Symmetrix volumes in the
storage group are available to the host:

# syminq

Device Product Device


---------------------------- -------------------------- --------------------Name Type Vendor ID Rev Ser Num Cap (KB)
---------------------------- -------------------------- --------------------/dev/rdsk/c3t50*8d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c3t50*8d1s2 EMC SYMMETRIX 5874 5400912000 4417920
/dev/rdsk/c3t50*8d2s2 EMC SYMMETRIX 5874 5400913000 4417920
/dev/rdsk/c3t50*8d3s2 EMC SYMMETRIX 5874 5400914000 4417920
/dev/rdsk/c3t50*8d4s2 EMC SYMMETRIX 5874 5400915000 4417920
/dev/rdsk/c4t50*9d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c4t50*9d1s2 EMC SYMMETRIX 5874 5400912000 4417920
/dev/rdsk/c4t50*9d2s2 EMC SYMMETRIX 5874 5400913000 4417920
/dev/rdsk/c4t50*9d3s2 EMC SYMMETRIX 5874 5400914000 4417920
/dev/rdsk/c4t50*9d4s2 EMC SYMMETRIX 5874 5400915000 4417920

VMAX: Add Disk Examples


EMC VMAX: Example of Disk Add

adding 8 x 30GB disks for replication

adding 8 x 120GB disks non-replicated

replicating from frame 2146 to 1826

Production - reservations

1. symconfigure script to create thin devices on frame 2146.


symconfigure -sid 2146 -cmd "create dev count=8, size=30 gb, emulation=fba, config=TDEV;" commit
New symdevs: 0A99:0AA0 - 30gb replicated
symconfigure -sid 2146 -cmd "create dev count=8, size=120 gb, emulation=fba, config=TDEV;" commit
New symdevs: 0AA1:0AA8 - 120gb

2. symconfigure script to bind the thin devices to frame 2146.


symconfigure -sid 2146 -cmd "bind tdev 0A99:0AA8 to pool <pool name>;" commit
3. check that devices are bound
symcfg -sid 2146 list -tdev -bound -gb
4. set SCSI3 attribute on the devices
symconfigure -sid 2146 -cmd "set dev 0A99:0AA8 attribute=SCSI3_persist_reserv;" commit
5. set dyn rdf attribute
symconfigure -sid 2146 -cmd "set dev 0A99:0AA0, attribute=dyn_rdf;" commit
6. script to create the storage group.
symaccess -sid 2146 add -name <PROD hostname01_strg> -type storage devs 0A99:0AA8
symaccess -sid 2146 add -name <PROD hostname02_strg> -type storage devs 0A99:0AA8
7. check devices
symaccess -sid 2146 show view <production host name01_02_mask>

DR - reservations
1. symconfigure script to create thin devices on frame 1826.

symconfigure -sid 1826 -cmd "create dev count=8, size=30 gb, emulation=fba, config=TDEV;" commit
New symdevs: 0AEE:0AF5 - 30gb replicated

symconfigure -sid 1826 -cmd "create dev count=8, size=120 gb, emulation=fba, config=TDEV;" commit
New symdevs: 0AF6:0AFD - 120gb

2. symconfigure script to bind the thin devices to frame 2146.


symconfigure -sid 1826 -cmd "bind tdev 0AEE:0AFD to pool <pool name>;" commit

3. check that devices are bound


symcfg -sid 1826 list -tdev -bound -gb

4. set SCSI3 attribute on the devices


symconfigure -sid 1826 -cmd "set dev 0AEE:0AFD attribute=SCSI3_persist_reserv;" commit

5. set dyn rdf attribute


symconfigure -sid 1826 -cmd "set dev 0AEE:0AF5, attribute=dyn_rdf;" commit

6. script to create the storage group.

symaccess -sid 1826 add -name <DR Hostname01_strg> -type storage devs 0AEE:0AFD
symaccess -sid 1826 add -name <DR Hostname02_strg> -type storage devs 0AEE:0AFD

7. check devices
symaccess -sid 1826 show view <DR Hostname01_mask>

RDF setup

symrdf addgrp -label <PROD Host label> -rdfg 38 -sid 2146 -dir 7h,10h -remote_rdfg 38 -remote_sid
1826 -remote_dir 7h,10h -link_limbo 60 -rem_link_limbo 60

cat > rdf_setup.txt


0A99 0AEE
0A9A 0AEF
0A9B 0AF0
0A9C 0AF1
0A9D 0AF2
0A9E 0AF3
0A9F 0AF4
0AA0 0AF5

symrdf -sid 2146 -file rdf_setup.txt -rdfg 38 query

symrdf -sid 2146 -file rdf_setup.txt -rdfg 38 set mode acp_disk


symrdf -sid 2146 -file rdf_setup.txt -rdfg 38 set mode async

symrdf -sid 2146 -file rdf_setup.txt -rdfg 38 set mode enable

BCV Setup

DR servers plus Dev needs access to clones


DR Server 01, DR Server 02
DEV Server 01

symconfigure -sid 1826 -cmd "create dev count=8, size=30 gb, emulation=fba, config=TDEV;" commit
New symdevs: 0AFE:0B05

symconfigure -sid 1826 -cmd "bind tdev 0AFE:0B05 to pool r5_fc15k_gp1;" commit

symaccess -sid 1826 add -name <DR Server 01_strg> -type storage devs 0AFE:0B05
symaccess -sid 1826 add -name <DR Server 02_strg> -type storage devs 0AFE:0B05
symaccess -sid 1826 add -name <DEV Server 01_strg> -type storage devs 0AFE:0B05

cat > clone_devs.txt


0AFE
0AFF
0B00
0B01
0B02
0B03
0B04
0B05

symrdf -sid 1826 -g werner_IB -rdfg 38 query

cat clone_devs.txt | while read line


do
symld -g werner_IB add dev $line -tgt
done

symclone -g werner_IB create DEV001 sym ld TGT001 -precopy -differential -noprompt


symclone -g werner_IB create DEV002 sym ld TGT002 -precopy -differential -noprompt
symclone -g werner_IB create DEV003 sym ld TGT003 -precopy -differential -noprompt
symclone -g werner_IB create DEV004 sym ld TGT004 -precopy -differential -noprompt
symclone -g werner_IB create DEV005 sym ld TGT005 -precopy -differential -noprompt
symclone -g werner_IB create DEV006 sym ld TGT006 -precopy -differential -noprompt
symclone -g werner_IB create DEV007 sym ld TGT007 -precopy -differential -noprompt
symclone -g werner_IB create DEV008 sym ld TGT008 -precopy -differential -noprompt

symclone -g werner_IB query

symclone -g werner_IB activate -tgt


symclone -g werner_IB recreate -precopy -tgt

###Terminate the relationship - do not need to run normally


symclone -g clone1 terminate DEV001 sym ld TGT001 -noprompt

EMC Symmetrix Steps


Collect Host Information
hostname
server vendor
os and version
new or existing server
does it already have san storage
what san storage arrays does it already use
HBA Information
for each hba port to be used:
o hba port x pwwn
o switch and port hba is connected
o alias name of server/hba port
o zoneset or configuration name for zoning on fabric
o create or record zone info for server hba port
HBA to FA Information
determine FA/ports currently used or
determine which FA/ports to use
Note: Disk/Dev availability first determined via reservation database
get list of available devices (check below)
Determine Available devices
check if devs are available
symmask -sid #### -dev ####:#### list assignment -v
check for existing device mappings
symmdev sid #### show | grep "Front Director Paths"
if dev is mapped, it will return a value
if not mapped, then no matching text found
Determine available LUNs
export SYMCLI_CONNECT=datacenter
symcfg -sid #### -dir ## -p # -address -available list
Zoning (brocade, if required or applicable)
perform for each fabric to which server hbas are connected:
o create aliases
o alicreate "servername_hba_alias", "10:00:00:00:c9:xx:xx:xx"
o
o

create zones
zonecreate "zonename", "member_hba; member_fa"

o
o
o

add zones to config and save


cfgadd "fab_cfg", "zone_name"
cfgsave

activate saved configuration


cfgenable "fab1_cfg"
Convert DEVs to 2-way mirrors if applicable
symdev -noprompt -sid #### not_ready ####
cat > convert_sid_servername.txt <<EOF
#*start*
convert dev #### to 2-Way-Mir;
convert dev #### to 2-Way-Mir;
convert dev #### to 2-Way-Mir;
#*end*
EOF
symconfigure -sid #### -f convert_sid_servername.txt preview
symconfigure -sid #### -f convert_sid_servername.txt commit
o
o

Dissolve old METAs if applicable


- not ready DEVs
- symdev -noprompt -sid #### not_ready ####

- cat > dissolve_sid_servername.txt <<EOF


- #*start*
- convert dev #### to 2-Way-Mir;
- convert dev #### to 2-Way-Mir;
- convert dev #### to 2-Way-Mir;
- unmap dev #### from dir ##:#;
- unmap dev #### from dir ##:#;
- dissolve meta dev ####;
- dissolve meta dev ####;
- #*end*
- EOF

- symconfigure -sid #### -f dissolve_sid_servername.txt preview


- symconfigure -sid #### -f dissolve_sid_servername.txt commit

Unmap if applicable
- not ready DEVs
- symdev -noprompt -sid #### not_ready ####
- cat > unmap_sid_servername.txt <<EOF
- #*start*
- unmap dev #### from dir ##:#;
- unmap dev #### from dir ##:#;
- unmap dev #### from dir ##:#;
- #*end*
- EOF
- symconfigure -sid #### -f unmap_sid_servername.txt preview
- symconfigure -sid #### -f unmap_sid_servername.txt commit
Create METAs if applicable
- find available devices to use to create metas
- cat > metas_sid_servername.txt <<EOF
- #*start*
- form meta from dev #### config=striped;
- add dev ### to meta ####;
- add dev ### to meta ####;
- #*end*
- EOF

- symconfigure -sid #### -f metas_sid_servername.txt preview


- symconfigure -sid #### -f metas_sid_servername.txt commit
- validate the METAs just created:
- symdev -sid #### show ####
Mapping
- map the devices found/created to FA directors and ports, assigning LUNs
- cat > map_sid_servername.txt <<EOF
- #*start*
- map dev #### to dir ##:#, lun=####;
- map dev #### to dir ##:#, lun=####;
- #*end*
- EOF
- symconfigure -sid #### -f map_sid_servername.txt preview
- symconfigure -sid #### -f map_sid_servername.txt commit
- validate mapping
- symdev -sid #### show ####
Masking
- define what devices are visible to server HBAs through which FA ports
- backup the masking db
- symmaskdb -sid #### backup -file backup_sid_servername.bkup
- symmask -sid #### -dir ## -p # -wwn 10000000c9xxxxxx add devs #### -noprompt
- symmask -sid #### -dir ## -p # -wwn 10000000c9xxxxxx add devs ####
-noprompt
- symmask -sid #### refresh
- validate masking

- symmaskdb -sid #### -wwn 10000000c9xxxxxx list database


- symmaskdb -sid #### -wwn 10000000c9xxxxxx list database
Device Status Check
- verify devices are in correct state
- symdev -sid #### show #### | grep "Device Status"
Symacl Configuration
* if this is a new deploy, then create accgroup
- cat > add.lob.hosts.txt<<EOF
- #*start*
- create accgroup <ssid>;
- add host accid <uniq id> name <ssid> to accgroup <ssid>;
- create accpool <ssid>;
- add dev <devs or dev range> to accpool <ssid>;
- grant access=BASE to accgroup <ssid> for ALL DEVS;
- grant access=BASECTRL to accgroup <ssid> for accpool <ssid>;
- grant access=RDF to accgroup <ssid> for accpool <ssid>;
- grant access=BCV to accgroup <ssid> for accpool <ssid>;
- grant access=SNAP to accgroup <ssid> for accpool <ssid>;
- #*end*
- symacl -a <symacl_access_pin> -sid #### preview -file add.lob.host.txt
- symacl -a <symacl_access_pin> -sid #### prepare -file add.lob.host.txt
- symacl -a <symacl_access_pin> -sid #### commit -file add.lob.host.txt
* for allocation to an existing prod server, add new devs to device pool
- symacl -sid #### list -accpool

- cat > add.prod.devs.txt <<EOF


- #*start*
- add devs <devs or dev range> to accpool <ssid>;
- #*end*
- symacl -a <symacl_access_pin> -sid #### preview -file add.prod.devs.txt
- symacl -a <symacl_access_pin> -sid #### prepare -file add.prod.devs.txt
- symacl -a <symacl_access_pin> -sid #### commit -file add.prod.devs.txt

Host Validation (are LUNs visible to server)


*Windows*
- rescan disks in windows disk management twice
- run powermt display dev=all (or check powerpath administrator)
- still not visible?...
- reboot host
- run powermt display dev=all (or check powerpath administrator)
*LINUX*
- lun_scan all
- powermt config
- powermt display dev=all
*AIX*
- cfgmgr
- powermt config
- powermt display dev=all

*Solaris*
- note: assumes sd.conf is fully populated, if not:
- reboot -- -r
- or touch /reconfigure and then reboot normally
- run devfsadm -C
- for powerpath ->
- powercf -q
- powermt config
- powermt display dev=all
- for veritas vm ->
- vxdctl enable
*HP-UX*
- ioscan -fnC disk
- insf -e
- powermt config
- powermt display dev=all
Powerpath
Command
powermt
check_registration
powermt config
powermt display
options
powermt display
unmanaged
powermt display
dev=all
powermt config
powermt check
powermt load
powermt manage
powermt remove
powermt restore
powermt save

Description
Check the state of the PowerPath license
Configure logical devices as PowerPath devices
Display options settings for storage system classes
Display logical devices that have been excluded from PowerPath management
(third-party storage systems only)

Check for, and optionally remove, dead paths


Load a PowerPath configuration
Place a specified logical device, or specified storage system class, under
PowerPath management (third-party storage systems only)
Remove a path from the PowerPath configuration
Test and restore paths
Save a custom PowerPath configuration

powermt set mode


powermt set policy
powermt set priority
powermt version

Set paths to active or standby mode


Change the load balancing and failover policy
Set the I/O priority
Return the version of PowerPath that is installed on the host

* powermt check

[class=symm|clariion|hitachi|hpxp|hphsx|ess|all]
[force] [hba=hba#|all] [dev=path|device|all]

EMC OpenMigrator Overview

Open Migrator/LM operates at the filter-driver level to manage and move Windows data from a source to
a target volume with minimal disruption to the server or applications. Open Migrator/LM requires one
potential restart of the server to install the application.

During and after migration, Open Migrator/LM captures all I/O to the source volume and writes it to both
the source and the target volumes. Open Migrator/LM synchronizes the source volume and target
volume until the final reboot

Note the following considerations for Open Migrator/LM:

Both source and target volumes remain synchronized until the migration is completed.

Windows NT file system (NTFS) can be migrated from smaller to larger volumes, or between
equal-sized volumes. Open Migrator/LM adjusts the NTFS file systems automatically for the
target volumes.

Open Migrator/LM does not support migration of FAT and FAT32 file systems.

Data migration for Microsoft Cluster Servers (MSCS) is supported. Open Migrator/LM can only
be installed on a single node of a cluster.

Open Migrator/LM cannot be used with the following:


Microsoft Terminal Server
EMC Celerra systems

Open Migrator/LM does not support boot or system volume migration.

Migration Persistence
Open Migrator/LM persists migrations across system reboots. If, in the course of copying data from the
source to the target, the system experiences an outage, the software continues the migration from the
place it left off prior to the disruption. Open Migrator/LM does not require any user intervention to
continue after reboot. The Open Migrator/LM service and filter drivers automatically work together to
complete the migration once the operating system (OS) loads and the respective disks become
available to the system.

Migration persistence across reboot is not guaranteed for cluster migrations.

It highly recommended to keep all the cluster nodes up during MSCS migration. MSCS provides failover capability. When other cluster nodes are running while data is being migrated and the system is
disrupted or restarted, migrations will fail immediately, and all participating devices are automatically
failed-over to their designated nodes.

Mount Point Migration


When you reboot to complete the migration (at system boot time), the software's filter driver transfers
the source volume's drive letter to the target volume. At system startup time, the Open Migrator/LM
Service maps the mount points previously associated with the source volume to the target volume.

To ensure that all mount points are properly reassigned from the source volume to the target volume
before users access them, you must add the Open Migrator/LM Service to the DependOnService list of
any Windows Services using the source's mount points. For example, if the source volume has a mount
point that is shared out, you must make the Lanmanager Service dependent on the Open Migrator/LM
Service before this volume is migrated. Note: The above operation is not needed if the migration is
completed manually by selecting "Complete migration". All mount points are moved to the target volume
during the completing process.