This post is more than 5 years old
12 Posts
0
6100
February 4th, 2015 08:00
Creation of Thin Meta volumes
I really like the way that Unisphere can create a TDEV META volume for you using new volumes.
However, I find it mind-numbingly slow.
Is there a way to do the same thing using SYMCLI?
I know you can form meta from devices, or you can add meta devices into a head - but all of these require you knowing the META head and META member device ID's, whereas Unisphere gets around that for you.
Any suggestions please?
No Events found!
echolaughmk
2 Intern
•
522 Posts
0
February 4th, 2015 08:00
Hi,
Is this perhaps the command you are looking for to create a meta all in one command:
symconfigure -sid XXX -cmd "create dev count=1, size=262080 cyl, meta_member_size=65520 cyl, meta_config=striped, config=tdev, emulation=fba, binding_to_pool=FC_Pool;" commit
This command will create a single device that is ~240GB in size and create it with meta members that are ~60GB in size, so that the end result will be the creation of 4 new TDEVs bound to the FC_Pool and formed into a meta automatically for you to start using (it will give you the meta head in the output of the CLI command).
An alternative to this can be achieved by enabling and using the autometa feature. Here is some info on that as well in case that is the route you would like to try:
https://community.emc.com/thread137330
Or you can look at the Solutions Enabler Array Controls Guide on support.emc.com under "Automatic Metadevice Creation" and it will provide the details and commands to enable it on the array so you can understand how it will impact future meta-device creations.
HTH,
-Keith
Storage_Dave
12 Posts
0
February 4th, 2015 08:00
Thanks Keith,
Spot on.
I knew it must be possible, but it wasn't immediately obvious after using the help files and the Sym IE course material
echolaughmk
2 Intern
•
522 Posts
1
February 4th, 2015 10:00
Sure can - that should work ok, just throw a comma at the end and add it to the full command. If you want to use something like SRDF with it, you can set that DRX attribute as well if that is desired in the same command and it will set it on all members/head.
-Keith
Storage_Dave
12 Posts
0
February 4th, 2015 10:00
Can I tag 'device_name=SERVER_DRIVE1' into the same symconfigure, or will it fail as the device (meta head) hasn't been created at this point?
dynamox
9 Legend
•
20.4K Posts
1
February 5th, 2015 12:00
are you sure you don't have to have autometa enabled to create it on the fly like that ?
symconfigure -sid 123 -cmd "create dev count=1,size=73656,emulation=FBA,config=TDEV ,meta_member_size=18414,binding to pool=GENERAL;" prepare
Execute a symconfigure operation for symmetrix '000000123 (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Error occurred while Defining change number 1:
Cannot perform the requested operation because the symmetrix wide meta auto meta is disabled
Terminating the configuration change session..............Done.
The configuration change session has failed.
echolaughmk
2 Intern
•
522 Posts
0
February 5th, 2015 12:00
Ahh...you might be right. I could have left it enabled previously in the quick test as I cut and paste. Looks like Dave tried it and probably enabled it as a result either way...but good catch dynamox...thx!
Storage_Dave
12 Posts
0
February 5th, 2015 13:00
5876.251.161
same autometa settings as yourself.
symcli version 7.6.2.26 (Windows)
Could be your symcli version or microcode release?
Storage_Dave
12 Posts
0
February 5th, 2015 13:00
I've just checked, and the customer does not have autometa enabled - but the command worked fine ('binding to pool' rather than 'binding_to_pool') even with the tagged device_name='my name' flag.
VMAX 10K, latest version of 5876
dynamox
9 Legend
•
20.4K Posts
0
February 5th, 2015 13:00
interesting, i am on 20k , 5876.190
symcfg list -sid 123 -v | tail -n 8
Auto Meta : Disabled
Minimum Auto Meta Size : 262669
Auto Meta Member Size : 0
Auto Meta Configuration : N/A
dynamox
9 Legend
•
20.4K Posts
1
February 5th, 2015 14:00
i am running 7.6.1
Take a look at page 10. Says starting with SE 7.6 and higher you can use autometa even if autometa setting is disabled. Wonder if they ment to say you have to be on at least 7.6.2
https://support.emc.com/docu52739_Solutions-Enabler-7.6.2-Release-Notes.pdf?language=en_US
EMCProvenSoluti
1 Rookie
•
15 Posts
0
March 25th, 2015 14:00
Provisioning Meta Volumes and Binding to a Virtual Pool via SYMCLI:
#########################################
######## No.Of Thin Devices:64 ########
######## Size Of Thin Device 480GB########
######## No.MetaMems Per TDEV 16 ########
######## Meta Member size 30GB ########
######## Drive Pool: FC_VP ########
#########################################
480 / 16 = 30GIG Meta Member Size
64 X 16 = 1024 Meta members (1024 Is Calulated by script below; just showing here for reference)
symconfigure -sid xxx -cmd “create dev count=64, size=480 GB, emulation=fba, config=tdev, meta_member_size=30GB, meta_config=striped, preallocate size=ALL, allocate_type=persistent, binding to Pool=FC_VP;” -v preview -nop
symconfigure -sid xxx -cmd “create dev count=64, size=480 GB, emulation=fba, config=tdev, meta_member_size=30GB, meta_config=striped, preallocate size=ALL, allocate_type=persistent, binding to Pool=FC_VP;” -v commit -nop
########## List Pool Details ##########
symcfg show -pool “FC_VP” -thin -detail -gb | more
symcfg list -tdev -pool “FC_VP” -gb | more
Some related posts:
http://davidring.ie/2014/01/10/emc-vmax-provisioning-meta-volumes-and-binding-to-a-virtual-pool-via-unisphere/
http://davidring.ie/2013/11/04/emc-vmax-setting-auto-meta-attributes/