Solved!
Go to SolutionCreating metas using symcli
I'm trying to create a 20Gb meta of 2 10Gb RAID1 devices using symcli and I'm running into a problem. The command file contains the following:
create dev count=1, size=21846,emulation=FBA,config=2-Way-Mir,meta_member_size=10923,meta_config=striped,disk_group=1;
When I run the symconfigure command I get the following response:
# symconfigure -sid 804 -f meta.cmd preview
Execute a symconfigure operation for symmetrix '000123451234' (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.
Is my command file setup correctly for what I'm looking to do? Reading the man page for symconfigure it looks like I need to set some auto_meta parameter, but I'm not sure how to do it and if it is something I should be doing anyway.
Ultimately, I need to create 64 metas like this and I do not currently have the RAID1 devs built. Creating 128 10Gb devices and then creating the metas through ECC or SMC is not looking fun. I appreciate the help in advance.
1684
0
Posted November 14th, 2010 17:00
1684
0
Posted November 14th, 2010 19:00
that link does not work
1684
0
Posted November 15th, 2010 06:00
"Error message: Cannot perform the requested operation because the symmetrix wide meta auto meta is disabled"
ID: emc215979 Usage: 13 Date Created: 06/08/2009 Last Modified: 05/13/2010 STATUS: Approved Audience: Customer Knowledgebase Solution Environment: OS: Microsoft Windows 2003 Environment: EMC SW: Solutions Enabler SYMCLI 7.0.0 Environment: Enginuity: 5772 or lower Problem: Error running symconfigure: Cannot perform the requested operation because the symmetrix wide meta auto meta is disabled Problem: Unable to create FBA devices. Root Cause: This is caused by a bug in Solutions Enabler. The "Auto Meta" setting is a new feature that was added to 5773 microcode. Solutions Enabler is errantly checking for the "Auto Meta" setting in arrays that do not support this feature, which in turn, causes this error message. Solutions Enabler was updated to skip these checks for 5772 or lower microcode.
Fix: This issue is fixed in Solutions Enabler 7.0.1. Notes: If you are using 5773 or higher microcode, this same error condition will occur if you attempt to create devices larger than 65520 cylinders with the auto meta feature disabled. In these cases, you will either need to enable auto meta on the array, or create smaller devices. For more details regarding configuring the "auto meta" feature, see emc193175 or review the Solutions Enabler Symmetrix Array Controls CLI Product Guide. 1684
0
Posted November 15th, 2010 14:00
So, we are running 5773 and I'm using symcli 6.5.2. Can we just install Solutions Enabler 7.0.1 without any concerns for what it might do to the environment? I'd like to install it on a single host to try doing these changes there.
As far as breaking it into 2 commands, I haven't tried that. I was reading and I wasn't exactly sure what I'd need to do. I didn't do enough research yet. If I do this, do I have to specify which luns I need to use per meta or does it have the ability to just create the metas out of any free disk?
1683
1
Posted November 15th, 2010 16:00
typically you can simply upgrade Solutions Enabler version, do check Solutions Enabler release notes as there were certain Enginuity versions that were removed from support. Also if you have SMC/SPA or ECC in the environment ..make sure all is compatible with the new version. Like Robert i always break it down into two step process, first i create my devices, second i create meta out of those devices. While you can tell symlci to automatically select meta members ..i don't like that and manually select my meta head and meta members. One of the reasons i do that is because we have some clone target devices that are part of a device group but they are not actually mapped nor masked. If you let symlci auto select the devices ..it may grab one of those devices.
1683
1
Posted November 16th, 2010 07:00
that looks good, you don't need to specify striped size, it's fixed and can't be changed on DMX/VMAX
1683
0
Posted November 16th, 2010 07:00
So, I would just go through the regular process to create a bunch of 10Gb mirrors and then use the following to create the metas? Then, I'll have to figure out some way (manually most likely for now) to populate the XXXX and YYYY with the device names.
form meta from dev XXXX config=striped,
stripe_size=2 cyl;
add dev YYYY to meta XXXX;
1683
0
Posted November 16th, 2010 11:00
Nice. It wasn't as seamless and easy as I had originally hoped, but it is definately better than SMC/ECC and pretty easy to do.
Now the hard part. Who gets the credit?
450
0
Posted November 16th, 2010 14:00
haha...Trouphaz asked the question in the first place. RRR ..i think it's too late for you, go to bed man
RobertDudley
2 Intern
•
448 Posts
1958
0
Posted November 15th, 2010 06:00
have you tried breaking it into two changes? Create your new devices and then turn them into meta's? You may be running into a compare problem. The compare is done as part of the prepare and commit, if you are creating devices and turning them into meta's in one change the compare may be failing on the meta's since the new volumes arent actually there.