Error mapping meta lun

take a look at this solution: emc31224

the metalun i created only consists of 3 member -- 25GB with striped option of 1 CYL. It is indeed unprotected metalun but definately not exceed 20 CYL. We already have some unprotected metaluns in the system. It is weird it cannot be done now. I am using SE5.4. Does it mean it can only be mapped by EMC engineer by bin file change but we cannot map it via SE?

By the way, I did not use the "add dev to meta" but rather I use "count=3" when form the meta. Does it matter?

Exactly .. You can NOT map unprotected volumes bigger then X cyls (where X depends on code).

Correct me if I'm wrong .. But probably you can map unprotected BCV devices ...

Please be aware that EMC won't be responsible in case you loose valuable data stored on BCV devices.

OK. i did a symdev show:
Device Capacity
{
Cylinders : 27621
Tracks : 414315
512-byte Blocks : 53032320
MegaBytes : 25895
KiloBytes : 26516160
}
So the meta lun that have 3x 8.6GB devs are actually 27621 CYLs. That mean even if it is a simple lun, it will be some 8000+ CYLs and we cannot map it using SE? Must pay for EMC for bin file change?!

Gialone please read carefully all other posts ...

1) any unprotected STD device bigger then 48 cyls can NOT be mapped via symconfigure on the frontend (and your device is 27621 cyls big).

2) you can legally map an unprotected BCV device to the frontend.

3) EMC won't be responsible in case you loose data stored on BCV devices due to a drive failure (thus affecting your unprotected BCV device).

Can you please post full symdev output ??

the microcode:
Microcode Version (Number) : 5771 (168B0000)

I use this command;
FORM META FROM DEV xxxx CONFIG=STRIPED, COUNT=3;

I dissolved the meta device and try to map just 1 simple dev. It failed with the same error.

Some extracted part of the log:
02/25/2009 12:59:48.879 13509 1 EMC:SYMCONFIGURE iCfgChgSessionStart Starting a local CfgChg session for SID
000190xxxxxx, symapi V6.5-891 (2.0) ucode 5771
02/25/2009 12:59:51.683 13509 Establishing session with Local cfg srvr (00019030xxxx)...Established.
02/25/2009 12:59:52.314 13509 SymConfigChange Define error in dfn 1:
02/25/2009 12:59:52.314 13509 map dev XXXX to dir 1C:1 lun=06B;
02/25/2009 12:59:52.314 13509 The specified device has a configuration that is not legal for mapping: DRV, SPARE, or
unprotected and greater than 48 cylinders in size.
02/25/2009 12:59:52.315 13509 Device XXXX generated the failure
02/25/2009 12:59:55.114 13509 Terminating session with configuration server.............Done.

Message was edited by:
Stefano Del Corno
removed box sn

Can you give me the microcode in this box?
Also you can see this devices status with:
symdev -sid xxx list -noport
I put this devices in simulation configuration an all is ok.
10 FBA Server 27621 3 NORM Non 1C8..1CA 3 LC
Can you give me the error text for symapi.log?
What is de command you used for this new metavolume?
form meta from dev xxxx, config = striped , stripe_size = 1 cyl;
add dev yyyy:zzzz to meta xxxx;

I did read all the posts carefully and I understand the posts telling me that unprotected STD device bigger then 48 cyls can NOT be mapped via symconfigure on the frontend.

How these unprotected STD devs which is bigger than 48 CYLs were mapped previously?

Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA :P DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------

0023 /dev/vx/rdmp/EMC0_9s2 16C:1 01B:D4 Unprotected N/Grp'd RW 8632
0024 /dev/vx/rdmp/EMC0_8s2 16C:1 15B:D4 Unprotected N/Grp'd RW 8632
0025 /dev/vx/rdmp/EMC0_49s2 16C:1 16B:C4 Unprotected N/Grp'd RW 8632
0026 /dev/vx/rdmp/EMC0_44s2 01C:1 02B:C4 Unprotected N/Grp'd RW 8632
0027 /dev/vx/rdmp/EMC0_12s2 16C:1 16A:C1 Unprotected N/Grp'd RW 8632
0028 /dev/vx/rdmp/EMC0_2s2 16C:1 02A:C1 Unprotected N/Grp'd RW 8632
0029 /dev/vx/rdmp/EMC0_13s2 16C:1 01A:D1 Unprotected N/Grp'd RW 8632
0067 Not Visible ***:* 01A:C2 Unprotected N/Grp'd (M) RW 17263
0068 Not Visible ***:* 15A:C2 Unprotected N/Grp'd (m) RW -
0069 Not Visible ***:* 16A:D2 Unprotected N/Grp'd (M) RW 34526
006A Not Visible ***:* 02A:D2 Unprotected N/Grp'd (m) RW -
006B Not Visible ***:* 01B:D2 Unprotected N/Grp'd (m) RW -
006C Not Visible ***:* 15B:D2 Unprotected N/Grp'd (m) RW -

Thanks for all the helps!!

Are you planning to convert your unprotected STD devices into something different ??

Let me whisper something at your ear .. "bee cee vee" ...

Actually this is the first time I come across a DMX using unprotected STD devs
This box is used for DR. I unmapped 3 devs which now I cannot map back via SE. I would probably need to get EMC CE to map it back the next time we upgrade the capacity lol. Any suggestion what I can convert it to for time being so that I can use it?

Got it! 1 last ques... if I make it a bee thingy, I can then map it back and assign and use it like STD dev. beside EMC will not cover for data loss, any other limitation to this approach?