On the CX, a collection of disks get assigned a raid protection, then you carve up LUNs on those. As far as I know, once you have assigned a raid protection to a set of disks on CX, all the capacity on those disks are that chosen protection.
On Symmetrix, when you create a logical volume, that creates the hypers or splits on the disk that form the protection. The rest of the disk is still free to form any other protection type. The choices are, unprotected (mostly for use as BCVs), RAID1, 3+1, 7+1, 6+2 and 14+2. All of these could be mixed on the same drives, however that is not the normal practice.
If you need more drives active in your LUN, you can stitch the Symmetrix logical volumes together into a Meta Volume.
The attached document describes the steps required to Map, Mask and Discover an DMX "HyperVolume" to a Server with Symcli Commands. You could also use EMC Control Center, which is a GUI and a little easier if you have never used these commands before.
The DMX is different than the CLARiiON. It doesn't have a RAID Group/LUN architecture like the CX has. It uses HyperVolumes which are sliced out of physical disks. You dont' create any RAID Groups. They already exist on the Array.
Use SymCli Commands to add Volumes to Servers.
A.Outline
1.Identify HBA WWNs and FA Ports on this Server.
2.Identify un-mapped HVs/MVs available on DMX.
3.Identify addresses available on this FA Port.
4.Use “symconfigure” to assign volumes to FA Port.
dynamox
9 Legend
•
20.4K Posts
0
March 27th, 2010 20:00
to create a raid-5 device that is striped across four physical spindles you would run this command (substitute for your disk group)
create dev count=1,size=9207,emulation=FBA,config=RAID-5,data_member_count=3,disk_group=0;
this will create one ~8.6G symdev.
I am not sure what you mean by creating two volumes, did you mean windows partitions, Solaris slices ?
vsa2
11 Posts
0
March 28th, 2010 10:00
Thanks for your reply.
What is size=9207, I would like to present two LUNs to the windows server..
Quincy561
1.3K Posts
0
March 28th, 2010 11:00
Could be VSA is familiar with CLARiiON, where you first pick drives and make a raid group out of them, and then add LUNs to those RAID groups.
Symmetrix has two flavors of RAID5, 3+1 and 7+1. These raid types, along with all the others can be mixed on the same drives.
The 9207 is in cylinders, which are 960k each.
vsa2
11 Posts
0
March 28th, 2010 13:00
You got it, I am Clarion guy.
Thanks for your reply
vsa2
11 Posts
0
March 29th, 2010 09:00
Is Clarion RAID group is equl to symmetrix Disk Group ?
SKT2
2 Intern
•
1.3K Posts
0
March 30th, 2010 00:00
yes, RG on Clar has a limitation of 16 disks. Not sure what is the limit for DG on SYM
Quincy561
1.3K Posts
0
March 30th, 2010 03:00
On the CX, a collection of disks get assigned a raid protection, then you carve up LUNs on those. As far as I know, once you have assigned a raid protection to a set of disks on CX, all the capacity on those disks are that chosen protection.
On Symmetrix, when you create a logical volume, that creates the hypers or splits on the disk that form the protection. The rest of the disk is still free to form any other protection type. The choices are, unprotected (mostly for use as BCVs), RAID1, 3+1, 7+1, 6+2 and 14+2. All of these could be mixed on the same drives, however that is not the normal practice.
If you need more drives active in your LUN, you can stitch the Symmetrix logical volumes together into a Meta Volume.
StuartA461
1 Rookie
•
63 Posts
2
March 30th, 2010 13:00
The attached document describes the steps required to Map, Mask and Discover an DMX "HyperVolume" to a Server with Symcli Commands. You could also use EMC Control Center, which is a GUI and a little easier if you have never used these commands before.
The DMX is different than the CLARiiON. It doesn't have a RAID Group/LUN architecture like the CX has. It uses HyperVolumes which are sliced out of physical disks. You dont' create any RAID Groups. They already exist on the Array.
Use SymCli Commands to add Volumes to Servers.
A. Outline
1. Identify HBA WWNs and FA Ports on this Server.
2. Identify un-mapped HVs/MVs available on DMX.
3. Identify addresses available on this FA Port.
4. Use “symconfigure” to assign volumes to FA Port.
5. Update symcfg database.
6. Add access with symmask.
7. Discover on Server.
8. Add to PowerPath Database.
B. Commands:
1. Identify HBA WWNs and FA Ports on this Server.
· # syminq list hba
· # inq –hba
· # symmask list hba
Identifier Type Adapter Physical Device Dir:P
---------------- ----- ---------- ----------------- -----
50060b000010428c Fibre 0-0-12-0-0 /dev/rdsk/c10t0d0 04A:0
50060b0000118076 Fibre 1-0-6-0-0 /dev/rdsk/c11t0d0 13A:0
2. Identify un-mapped HVs/MVs available on DMX.
· # symdev list –noport
# symdev list -noport -cap 8632
Symmetrix ID: 000xxxxxxxxx
Device Name Directors Device
--------------------------- ------------- --------------------
Sym Physical SA
DA :IT Config Attribute Sts (MB)
--------------------------- ------------- --------------------
00C6 Not Visible ???:? 16D:C6 BCV N/Asst'd RW 8632
00EB Not Visible ???:? 16A:DA BCV N/Asst'd RW 8632
00EC Not Visible ???:? 01D:DA BCV N/Asst'd RW 8632
00ED Not Visible ???:? 16C:DA BCV N/Asst'd RW 8632
00EE Not Visible ???:? 01B:DA BCV N/Asst'd RW 8632
0593 Not Visible ???:? 16A:C1 RAID-5 N/Grp'd RW 8632
05B3 Not Visible ???:? 16A:C11 RAID-5 N/Grp'd RW 8632
05B4 Not Visible ???:? 01A:D11 RAID-5 N/Grp'd RW 8632
05CD Not Visible ???:? 16A:D8 RAID-5 N/Grp'd RW 8632
05CE Not Visible ???:? 01A:C8 RAID-5 N/Grp'd RW 8632
0655 Not Visible ???:? 16A:C5 RAID-5 N/Grp'd RW 8632
0656 Not Visible ???:? 01A:D5 RAID-5 N/Grp'd RW 8632
06F3 Not Visible ???:? 01C:D9 Unprtctd N/Grp'd RW 8632
06FC Not Visible ???:? 01C:CA Unprtctd N/Grp'd RW 8632
06FD Not Visible ???:? 16B:CA Unprtctd N/Grp'd RW 8632
06FE Not Visible ???:? 01A:CA Unprtctd N/Grp'd RW 8632
06FF Not Visible ???:? 16D:CA Unprtctd N/Grp'd RW 8632
3. Identify addresses available on this FA Port.
· (Do both “paired” ports.)
· $ symcfg list -fa 7b -p 0 -sid 1130 -addresses -available
Symmetrix ID: 000xxxxxxxxx
Director Device Name Attr Address
-------------------- --------------------- ---- ------------
Ident Symb. Port Sym Physical VBUS TID LUN
------ ------ ---- ---- --------------- ---- --- ---
FA-7B 07B 0 0040 /dev/sdq VCM 0 00 000
0046 /dev/emcpowerm 0 00 001
0047 /dev/emcpowerk 0 00 002
0048 /dev/emcpowerj 0 00 003
0049 /dev/emcpoweri 0 00 004
0641 /dev/emcpowert 0 00 005
0642 /dev/emcpoweru 0 00 006
0643 /dev/emcpowerv 0 00 007
0644 /dev/emcpowerw 0 00 008
0645 /dev/emcpowerx 0 00 009
00AA /dev/emcpowerp (M) 0 00 00A
00B0 /dev/emcpowerq (M) 0 00 00B
00B6 /dev/emcpowerr (M) 0 00 00C
00BC /dev/emcpowers (M) 0 00 00D
- AVAILABLE 0 00 00E*
Total ----
Mapped Devices: 14
Incl. Metamembers: 34
Available Addresses: 4062 (s)
Legend for Available address:
(*): The VBUS, TID, LUN address values represent a gap in the
address assignments or are the next available address in
the run
(s): The Available Addresses for a director are shared among
its ports (shared)
4. Use “symconfigure” to map volumes to FA Port.
· This is an HP-UX example:
##
# add_u62.cmd SDA 05/28/03
#
# Use symconfigure to present new HVs:
#
# symconfigure preview -file add_bcvs.cmd
# # symconfigure prepare -file add_bcvs.cmd
# symconfigure commit -file add_bcvs.cmd
#
# One group for each of two access paths:
map dev 04C to dir 04a:0, vbus=1, target=0, lun=0;
map dev 04D to dir 04a:0, vbus=1, target=0, lun=1;
map dev 04E to dir 04a:0, vbus=1, target=0, lun=2;
map dev 04F to dir 04a:0, vbus=1, target=0, lun=3;
map dev 050 to dir 04a:0, vbus=1, target=0, lun=4;
map dev 051 to dir 04a:0, vbus=1, target=0, lun=5;
map dev 052 to dir 04a:0, vbus=1, target=0, lun=6;
map dev 053 to dir 04a:0, vbus=1, target=0, lun=7;
#
map dev 04C to dir 13a:0, vbus=1, target=0, lun=0;
map dev 04D to dir 13a:0, vbus=1, target=0, lun=1;
map dev 04E to dir 13a:0, vbus=1, target=0, lun=2;
map dev 04F to dir 13a:0, vbus=1, target=0, lun=3;
map dev 050 to dir 13a:0, vbus=1, target=0, lun=4;
map dev 051 to dir 13a:0, vbus=1, target=0, lun=5;
map dev 052 to dir 13a:0, vbus=1, target=0, lun=6;
map dev 053 to dir 13a:0, vbus=1, target=0, lun=7;
#
5. Update symcfg database.
· # symcfg discover
· # symcfg list –sa 14b –p 0 -addresses
6. Add access with symmask.
· Verify this WWN logged in to this FA:
- # symmask list -wwn $WWN logins
· Verify that this HV is mapped to this FA:
- # symdev list -sa $FA -RANGE ${HV}:${HV}
· Add access:
- # symmask -wwn $WWN -dir $FA -p 0 add devs $HV –noprompt
· Set up “alias” in symmaskdb database if not already done.
- # symmask –sid 5568 –wwn 2100…6333 rename “Server/HBA0”
· Refresh Symmask Database
- # symmask refresh
· Verify Access
- # symmaskdb list database
7. Discover on Server.
8. Add to PowerPath Database
· # powermt config
· # powermt save
· # powermt display