Using with SYMCLI

In order to perform SRDF/Synchronous operations we need to perform following operations:

1.Create dynamic srdf devices as per your requirement on both the sites(not mandatory) if any devices
are already in production just set the "dyn_rdf" attribute
2. list SRDF environment
3.Create dynamic srdf groups
4.add srdf devices into Device Group(not mandatory) or we can use file for creating pair
5.creating pair
6.change srdf operational mode suspend/restore/resume the srdf links for one/all devices in device group.
IMPORTANT: The dynamic_rdf option became obsolete in Solutions Enabler 7.4.

Identify RDF connections between source and target arrays

1. symcfg list command to display the local and remote Symmertrix visible to this host.
symcfg list

2. Display the local and remote arrays, their RDF directors, and RA groups connected in the open RDF
switch fabric.
symcfg list -ra all switched
or
symcfg sid 1234 list ra all switched
symcfg sid 5678 list ra all switched

3. Examine the output for both local and remote Symmetrix arrays to identify the best RDF connection
between the two arrays.
Best practice: Choose ports that are lightly populated for the RDF dynamic group assignment.

Task 1: Enable dynamic SRDF on the array

1. Type the symcfg list v command to display detailed information about attached arrays.
symconfigure list v

View the output to check if the Dynamic RDF Configuration State is Enabled or disabled.
If Dynamic RDF Configuration State is set to Disabled, proceed with below command.
2. symconfigure sid 1234 cmd set symmetrix dynamic_rdf=enabled;

Task 2: Create standard devices as RDF capable

1. Use a text editor (NotePad, vi) to create a text file containing the following line:
vi create_std.txt
symconfigure sid 1234 cmd create dev, count=6, size=10 gb, emulation=fba,
config=2-Way-Mir, dynamic_capability=dyn_rdf;

Task 3: Verify the new devices are created and dynamic RDF enabled
1. Type the symdev sid SID list command to verify that the new devices were created.
For example:
symdev sid 1234 list - dynamic
symdev sid 1234 list dynamic -r1/-r2

Note: To show only R1 or R2 devices, include the r1 or r2 option in the command line.

Task 4: Find available addresses (Ldev IDs) for the director and port
1. To display available addresses for front-end director 04A port 0 on Symmetrix 1234:
symcfg sid 1234 list sa 04A p 0 -addresses available

The output displays:

VBUS, TID and LUN addresses associated with front-end director 04A, port 0,
Indicates the next available address in the run.
In the following output, there is a large run of available LUN addresses between 004 and 060:

Symmetrix ID: 0000000051234 (Local)

Director
Device Name
Attr
Address
---------------------- -------------------------- ---- -------------Ident
Symbolic Port Sym
Physical
VBUS TID LUN
------ -------- ---- ---- ----------------------- --- --FA-4A

04A

0001
0002
0003
0040
0041
0042
0043
-

AVAILABLE
/dev/rdsk/c1t0d1s2
/dev/rdsk/c1t0d2s2
/dev/rdsk/c1t0d3s2
AVAILABLE
/dev/rdsk/c1t0d96s2
/dev/rdsk/c1t0d97s2
/dev/rdsk/c1t0d98s2
/dev/rdsk/c1t0d99s2
AVAILABLE

0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0

000 *
001
002
003
004 *
060
061
062
063
064 *

2. Select LUN values for the new devices.

IMPORTANT: Consider the LUN conventions for your host platform.
In this example, there is a large run of available LUN addresses between 004 and 060.
The next task uses LUN addresses 004 through 009 for mapping the six new devices.

Task 5: Map the LUN numbers to new dynamic devices

1. Use a text editor (Note Pad, vi) to create a text file containing the mapping instructions for the new
devices.

vi map_dyn_devices.txt
map dev 091 to dir 04A:0,
map dev 092 to dir 04A:0,
map dev 093 to dir 04A:0,
map dev 094 to dir 04A:0,
map dev 095 to dir 04A:0,
map dev 096 to dir 04A:0,

lun=004;
lun=005;
lun=006;
lun=007;
lun=008;
lun=009;

2. To map the 6 devices listed in text file map_dyn_devices.txt on Symmetrix 1234:

symconfigure sid 1234 commit file map_dyn_devices.txt

Task 6: View host connections to assign devices to host

1. To display the connections from this host to Symmetrix 1234:
symcfg sid 1234 list connections

2. Note which front-end director (for example, FA-4A) your host uses to reach the Symmetrix array.

Task 7: Mask the new dynamic devices

To mask devices 091 through 096 on Symmetrix 1234 for access to HBA 10:00:00:00:c9:40:a8:a3
using director 04A, port 0:
symmask -sid 1234 wwn 10000000c940a8a3 add devs 091,092,093,094,095,096 -dir
04A -p 0
Note: If the devices are not addressed to the specified FA, a warning message is displayed.
A message is displayed if the devices are already assigned in the database to any WWN. To turn off
this functionality, use the -noprompt option.

Task 8: Update the SYMAPI database

1. Type the symcfg discover command to update the SYMAPI database.
symcfg discover

Note: This operation may take a few minutes to complete.

2. Type the sympd sid SID list command to verify that the newly mapped devices are visible to the
host.
To display SID 1234:
sympd sid 1234 list

3. To verify that the masking for devices 91 through 96 succeeded:

symmaskdb -sid 1234 list assignment dev 91:96
or
symmaskdb -sid 1234 list devs wwn 10:00:00:00:c9:40:a8:a3

The display lists the host WWNs and shows the devices masked to the corresponding HBAs.

Task 9: Create and map another set of devices on the remotely attached Symmetrix
1. Repeat Task 1: through Task 8: to create the same number of dynamic devices on the remotely
attached Symmetrix.
Note: You must perform the steps to mask devices (Task 7: and Task 8:) from a host that is local to the
remote Symmetrix.
Your dynamic R1 and R2 devices are now created mapped and masked.

We have the below details

source array - 1234
Target array 5678
Source: 091(lun=004), 092(lun=005), 093(lun=006), 094(lun=007), 095(lun=008), 096(lun=009)
Destination: 061(lun=014), 062(lun=015), 063(lun=016), 064(lun=017), 065(lun=018), 066(lun=016)

dynamic rdf group for 1234 <=> 5678 is 50

Create a pair file, pair_1234_to_5678_Dg50.txt as below

091 061
092 062
093 063
094 064
095 065
096 066

4 Create and Establish

Create the SRDF pairing between source and target devices and start a full
copy from R1 to R2.
symrdf -sid 1234 -rdfg 50 -type rdf1 -file pair_1234_to_5678_Dg50.txt
createpair -establish

5 Qeury

You can query the the pair to know the status by using the below command.
symrdf -sid 1234 -rdfg 50 -file pair_1234_to_5678_Dg50.txt query

6 SPLIT pair
Suspends the replication, Enables writes on both Source R1s and Destination
R2s.
No replication in any direction after the split. To invoke a split, the SRDF
pair(s) must already be in synchronised/Suspended/R1 Updated status.
symrdf -sid 1234 -rdfg 50 -file pair_1234_to_5678_Dg50.txt split

7 Delete pair
Once the devices are in split state , we can delete the relation and make
them as STD(Standard) devices.
symrdf -sid 1234 -rdfg 50 -file pair_1234_to_5678_Dg50.txt deletepair

=====================================================
Using with Groups
Task 10: Add a dynamic SRDF device group
1. Display the SRDF groups already configured on the local and remote arrays.
symcfg list sid 709 rdfg all
symcfg list sid 774 rdfg all

2. Create local SRDF group 140 with label Group_140 on director 16d on local Symmetrix 709, remote
SRDF group 140 on director 16d on remote Symmetrix 774, using the Fibre Channel protocol:
symrdf addgrp label Group_140 sid 709 rdfg 140 dir 16d remote_sid 774
remote_dir 16d remote_rdfg 140 -fibre

Best practice

Specify an RDF group number that is not already in use.

Specify the same number for remote_rdfg and rdfg.
For optimal performance, configure no more than 6 groups per switched Fibre RA.

Optional arguments:
Note: Link limbo may be set after the group is created using the symrdf set command. The auto link
recovery and link domino parameters can only be set at group creation time
-link_domino Enabled | Disabled When enabled, if the last available link in the SRDF group
fails, the next host write to any R1 device in the SRDF group causes all R1 devices in the
SRDF group become Not Ready to their hosts. Link domino ensures that data on the source
(R1) and the target (R2) devices are always in sync.
The default is disabled.
-remote_link_domino Enabled | Disabled Enables/disables link domino at the remote
Symmetrix.
The default is disabled.
-auto_link_recovery Enabled | Disabled When enabled, if all SRDF links fail, the Symmetrix
array remembers the SRDF states of the affected SRDF devices and can automatically
restore the devices to these states once the SRDF links become operational.
Default is disabled.
-remote_auto_link_recovery Enabled | Disabled Enables/disables auto link recover ay the
remote Symmetrix.
-link_limbo Secs Sets the number of seconds for Enginuity to wait when a down link is
detected before updating the link status. If the link status is still not ready after the link limbo
time expires, devices are marked not ready to the link.
The default is 10 (seconds).
The range is 0 120 (seconds).
-rem_link_limbo Secs Sets link limbo timer for the remote link.
The default is 10 (seconds).
The range is 0 120 (seconds).

4. Verify that the new device group was created.

symcfg list rdfg 140
Symmetrix ID : 000190300709
S Y M M E T R I X
Local
-------------LL
RA-Grp (sec)
-------------140 (8B)
10

R D F

Remote
--------------------RA-Grp SymmID
--------------------140 (8B) 000190300774

G R O U P S

Group
----------------------Flags Dir
T
Name
LPDS Cfg
----------------------D Group_140
XX.. F-S

RDFA Info
----------------Flags Cycle
CSRM
time
Pri
----- ----- ---IS30
33

Task 11: Enable dynamic RDF Attribute for devices

Source Devices: 0918 (DEV001), 0919 (DEV002), 091A (DEV003), 091B (DEV004) &
Remote Devices: 072B, 072C, 072D, 072D are created
symconfigure sid 709 cmd set dev 0918:091B attribute=dyn_rdf;

3. Repeat the above Step on the remote Symmetrix.

Task 12: Create pairs to the dynamic group on remote array

1. Make R2 devices should not access by the host at all.
symdev
symdev
symdev
symdev

sid
sid
sid
sid

774
774
774
774

not_ready
not_ready
not_ready
not_ready

072B
072C
072D
072D

2. Use a text editor (NotePad, vi) to create a device file containing two columns, R1 devices in one
column, R2 devices in the other column.

All devices for one side of the SRDF pair must be in the first column, and all devices for the other
side of the SRDF pair must be in the second column. It does not matter which side (R1 or R2) is
in which column, because the type option of the symrdf createpair command determines which
columns is R1 or R2.

vi create_pair.txt
0918 072B
0919 072C
091A 072D
091B 072E
symrdf createpair file create_pair.txt type r1 sid 709 rdfg 140 invalidate r2
g dg_rdfg140

=====================================================================================

Task 13: Set the mode to adaptive copy disk

1. Type the symrdf g GroupName set mode acp_disk command to set the mode for the new group to
adaptive copy disk.
Best practice
Adaptive copy disk (acp_disk) mode is designed to transfer large amounts of data without loss of
performance. Set the mode for the group to adaptive copy disk before establishing the SRDF pairs to
avoid I/O latency issues for the host application during the device synchronization.
To set the mode for group dg_rdfg140 to adaptive disk:
symrdf -g dg_rdfg140 set mode acp_disk noprompt

2. Type the symrdf g GroupName query command to display the group.

To display group dg_rdfg140:
symrdf g dg_rdfg140 query
Device Group (DG) Name
DG's Type
DG's Symmetrix ID
Remote Symmetrix ID
RDF (RA) Group Number

:
:
:
:
:

dg_rdfg140
RDF1
000190300709
000190300774
140 (8B)

(Microcode Version: 5773)

(Microcode Version: 5773)

Source (R1) View

Target (R2) View
------------------------------------------------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv
R2 Inv K
T R1 Inv
R2 Inv
Device Dev
E Tracks
Tracks S Dev
E Tracks
Tracks
-------------------------------- -- ------------------------

MODES
----- ------------

DEV001
DEV002
DEV003
DEV004

C.D
C.D
C.D
C.D

0918
0919
091A
091B

Total
Track(s)
MB(s)

RW
RW
RW
RW

0
0
0
0

16500
16500
16500
16500

NR
NR
NR
NR

072B
072C
072D
072E

WD
WD
WD
WD

-------- -------0
66000
0.0
4125.0

0
0
0
0

16500
16500
16500
16500

RDF Pair
MDA
STATE
----- -----------Suspended
Suspended
Suspended
Suspended

-------- -------0
66000
0.0
4125.0

Legend for MODES:

M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy
D(omino)
: X = Enabled, . = Disabled
A(daptive Copy)
: D = Disk Mode, W = WP Mode, . = ACp off

3. Check the output to verify that the devices in the group are now in adaptive copy disk mode.

Task 14: Establish the device pairs in the group

1. (Optionally) type the symqos g GroupName set RDF priority Priority command to specify how
many resources will be used to establish the device pairs.
The establish operation merges the track tables between the R1 and the R2 devices. It then enables
the RDF link (makes it enabled for read and write requests) and begins to copy data from the source
device to the device which has been designated as invalid.
The establish operation can take a long time. Best practice is to launch establish operations during
non-peak hours to minimize the impact of the synchronization traffic over the RDF link.
If there are no non-peak hours of operation, use the the symqos set RDF priority command to
minimize the impact of the RDF synchronization for the device group.
The value for priority is an interger from 0 (no delay, most impact) to 16 (most delay, least impact).
Note: Prior to Enginuity 5772, the maximum value for priority is 10.
To set the RDF priority value for device group dg_rdfg_140 to 5:
symqos -g dg_rdfg140 set RDF priority 5

2. Type the symrdf g GroupName establish full command to start the establish operation for the
specified device group.
To start the establish operation for group dg_rdfg140:
symrdf g dg_rdfg140 establish full noprompt

3. Type the symrdf g GroupName query command to monitor the progress of the establish operation.
Check the output of the query command to make sure the number of invalid tracks owed from the R1
to the R2 is decreasing. This value is in the R2 Inv Tracks column.

Repeat the query until the devices are Synchronized.

Task 15: Set the group mode

When all the device tracks have finished copying, the RDF device state is Synchronized.
1. Type the symrdf g GroupName set mode Mode to set the replication mode for the group.
To set the the replication mode for group dg_rfdg40 to synchronous:
symrdf -g dg_rdfg140 set mode sync noprompt
==========================================================================