I need a sample symconfigure script for converting STD to BCV.

yep, before changing device DRV attributes ..device has to be unmapped. Here is a convert command:

convert dev 075C to BCV;

save it to a file and run:

symconfigure -sid xxx -f filename commit

i think you have to write disable and unmap them before you can convert them (correct me if wrong)

Hmmm I've found the same statement in S.E. 6.0 manuals .. no references to code level .. I think that you can modify the BCV attribute without unmapping. If the host doesn't care about the flags (and most hosts don't care), you can change it online.

PS if you need an OS that DO cares, look at AIX

From Solution Enabler 6.4 manuals ....

When adding/removing BCV attributes, there are no restrictions on I/O.

So it seems that you don't need to unmap.

If you want to convert a RAID5 (7+1) volume to a RAID5-BCV you need to use:

convert dev 075C to BCV+R-5;

Please remember that a RAID5 BCV is a lot different froma "real" BCV.

oh nice ..is SE 6.4 the only requirement, or do you have to be on code 72 as well ?

i am currently running code 71 on DMX3 with SE 6.2 ..and i have to unmap devices before converting to BCV ..must be new to SE 6.4 ?

I'm sorry but I don't have S.E. 6.2 available .. it's too old and we needed to upgrade every host to 6.3.2 or 6.4.1 .. But this is what I did ..

1) volume 89C is mapped and masked to my host as per "sympd list"

star2_prod/root> sympd list

Symmetrix ID: xxxxxxxx0821

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

/dev/rdsk/c0t0d6s2 0220 07A:0 01A:C6 2-Way Mir N/Grp'd RW 8723
/dev/rdsk/c0t0d7s2 064F 07A:0 11B:C3 2-Way Mir N/Grp'd (M) RW 17445
/dev/rdsk/c0t0d238s2 089C 07A:0 15D:D6 2-Way Mir N/Grp'd (M) RW 18750
/dev/rdsk/c0t0d240s2 0000 07A:0 01C:CE 2-Way Mir N/Grp'd VCM WD 11
/dev/rdsk/c0t0d243s2 0003 07A:0 11A:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d244s2 0004 07A:0 06D:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d245s2 0005 07A:0 12B:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d246s2 0006 07A:0 05C:CE 2-Way Mir N/Grp'd RW 3

2) box is a DMX3000 with code 5671.something.else

3) symcli is at 6.4.1
star2_prod/root> symcli

Symmetrix Command Line Interface (SYMCLI) Version V6.4.1.0 (Edit Level: 827)
built with SYMAPI Version V6.4.1.0 (Edit Level: 827)

4) command file (pippo.cmd) as shown below:
star2_prod/root> cat pippo.cmd
convert dev 089C to 2-Way-BCV-Mir;

5) I've ran symconfigure to execute pippo.cmd commands against box 821.

star2_prod/root> symconfigure -sid 821 -file pippo.cmd -nop commit

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.
Processing symmetrix xxxxxxxx0821
Performing Access checks..................................Allowed.
.....
.....
Step 103 of 108 steps.....................................Executing.
Step 108 of 108 steps.....................................Executing.
Local: COMMIT............................................Done.
Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

6) I've ran symcfg discover to rediscover the device configuration

7) new output from sympd list:
star2_prod/root> sympd list

Symmetrix ID: xxxxxxxx0821

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

/dev/rdsk/c0t0d6s2 0220 07A:0 01A:C6 2-Way Mir N/Grp'd RW 8723
/dev/rdsk/c0t0d7s2 064F 07A:0 11B:C3 2-Way Mir N/Grp'd (M) RW 17445
/dev/rdsk/c0t0d238s2 089C 07A:0 15D:D6 2-Way BCV Mir N/Asst'd (M) RW 18750
/dev/rdsk/c0t0d240s2 0000 07A:0 01C:CE 2-Way Mir N/Grp'd VCM WD 11
/dev/rdsk/c0t0d243s2 0003 07A:0 11A:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d244s2 0004 07A:0 06D:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d245s2 0005 07A:0 12B:CE 2-Way Mir N/Grp'd RW 3
/dev/rdsk/c0t0d246s2 0006 07A:0 05C:CE 2-Way Mir N/Grp'd RW 3

No tricks, no jokes .. Simply S.E. 6.4.1

-s-

Message was edited by: KCSCP, Symmetrix Moderator, June 20, 2007

Message was edited by:
KCSCP

awesome, thank you for doing this ...i am glad it's not a 72 code option only. I am going to load SE 6.4 when we upgrade to ECC 6.0.

AFAIK no need to wait ECC 6.0 to load SE 6.4.1 ... But I'm not an ECC Expert

i know ECC 6.0 is not a requirement ...but i would hate for ECC 5.2 SP4 to break just because i installed new cli ...who knows ..it's ECC after all

ECC 6.0 is just around the corner ..i'll load everything the latest and greatest on my new ECC 6.0 box. Do i need 2 petabytes of memory to run this new beast?

We are completly OT .. but here we have ECC 5.2 SP4 and SE 6.4/6.3.2 almost everywhere .. And everything looks fine (almost fine ;-)).

This thread has been moved to the Host Software/Solutions Enabler Support Forum.

We've got ECC 5.2 sp5 here and I'm running much better since I upgraded SE from 6.0.3 to 6.4... and the DMX3s are still at 5771.