You can find a nice description of multihop configurations in Solution Enabler manual "EMC Solutions Enabler Symmetrix SRDF Family CLI Version 6.5 Product Guide" .. Look at page 140. Manual part number is P/N 300-000-877 REV A10.

You can find examples on how to setup devicegroups, how to split devices at various locations, a nice picture showing explaining the infrastructure and a table with various commands you can use to manage devices at various sites

Message was edited by:
Stefano Del Corno

I've read the 6.4 manual. For the local frames I use createpair to build the R1/R2 relationship. What I don't understand is how does the local R1/BCV know which remote R2 device it is to be partnered with?.

OK, so the steps in a plan to accomplish this are:

validate attribute=dyn_rdf

symrdf createpair -file src2tgt_hop1.txt -sid 0001 -rdfg RG -type RDF1 -invalidateR2
symdg -type RDF1 create DG
symld -sid 0001 -g DG add dev XXXX
symrdf -g DG set mode acp_disk
symrdf -g DG establish -full
symrdf -g DG set mode sync

symbcv -sid 0002 -g DG -rdf associate dev XXXX
symmir -g DG -rdf establish -full
symmir -g DG -rdf split

symrdf createpair -file src2tgt_hop2.txt -sid 0002 -rdfg RG -type RDF1 -invalidate R2
symrdf -g DG establish -full -rbcv

symbcv -sid 0003 -g DG -rrdf associate dev XXXX
symmir -g DG -rrbcv establish -full
symmir -g DG -rrbcv split

6.4 have the same pics and same examples .. they are the same since 5.x AFAIK .. Maybe changes the page # .. but everything else is exactly the same

When you create an RDF pair via "symrdf createpair" you create a relationship between a local volume and a remote one. Your local volume is a BCV device (thus becoming a R1/BCV right before the createpair) and your remote R2 is almost any device in the remote box. So, in a word, createpair creates the relationship (the pair ).

Solution enabler can be upgraded easily .. And you can always ask EMC to upgrade your code .. Request a quote .. Maybe your account manager will be pleased to hear such a request from you

at a first glance it's OK ..

However let me ask you a question .. Do you really need BCV devices at middle box ??
Did you ever heared of Cascading/SRDF ??

Cascading requires a DMX3 frame in between with a recent code .. The DMX3 "in the middle" will have very special devices that will behave both as R2 (with respect of your R1 devices in your DMX3000) and as R1 (for the R2 devies on the other coast). You don't need BCV devices in the middle. The RDF links are SRDF/S from source box to middle box and SRDF/A from middle to far end. You can find better details in the same manual I quoted before .. I think you can download recent manuals from Powerlink and dig a little what Cascading is

Yeah I read a little on it. This new fangled contraption requires Enginuity 5671/5772 to DMX3 / DMX4 running 5773 and at least SE 6.5. Unfortunately, we're currently at 5671/5771 and SE 6.4.

I haven't heard of Cascading/SRDF, but I'll do some research. FYI, the middle frame to end frame will be SRDF/A since one is located on the West coast and the other on the East.

Look Dave, I can see you're really upset about this. I honestly think you ought to sit down calmly, take a stress pill, and think things over.