This post is more than 5 years old
22 Posts
0
6674
July 16th, 2013 13:00
VMAX to DMX SRDF/A goes invalid
I am seeing a new issue in my environment when I try to setup replication between VMAX and DMX.
All existing replication is working fine between the frames, but when I create new RDF group and new pairs , and establish them ..they are immediately going into invalid state.
Support told me to fully allocate thin device on source side and then try sync.
Does anyone faced similar issues ?? Is there any fix for this problem.
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
DEV001 2BC2 RW 0 2015344 NR 555C WD 0 0 C.D. Invalid
DEV002 2BDA RW 0 5485591 NR 5574 WD 0 0 C.D. Invalid
DEV003 3D34 RW 0 3318588 NR 558C WD 0 0 C.D. Invalid
urs_rams2005
22 Posts
0
July 18th, 2013 06:00
Below is the response from L2 support
Referred primus :emc312873
This is due to an Enginuity issue. There is a generic problem on THIN to 73 THICK NULL group copy. If THIN is unallocated and R2 is IVTOC, the code processes up to the end of the device.
A temporary workaround is to fully allocate the R1 device, including special cylinders. OPT 412611 has been opened for this issue and a permanent fix is in progress.
Then you can do full establish.
Avinash V
91 Posts
0
July 16th, 2013 23:00
Please let us know the set of command you are performing.
Also i would appreciate if you would be able to provide me with the knowledgebase article(if any) provided by the support.
- Support told me to fully allocate thin device on source side and then try sync.-
* Did you try this, and did this work ??
taz_at_emc
54 Posts
0
July 16th, 2013 23:00
3 Questions from me:
1) What is the command you are running for establishing pairs ?
2) Whichcode level you are at for both VMAX and DMX ?
3) What is the symcli version ?
Roshan_Raju
53 Posts
0
July 17th, 2013 06:00
Hello,
Can you try with the invalidate R2 switch. Also SE 7.4 is minimum needed to manage 5876 code.
Thanks!
Roshan Raju.
urs_rams2005
22 Posts
0
July 17th, 2013 06:00
1) symrdf -g < > establish -full
2) Source VMAX - 5876.163.105
Target DMX -> 5773.184
3) SYMCLI Version -> 7.3.2
and I havnt tried fully allocating the thin device as i dont want to do it .We do all thin provisioning.
If I do it for one lun , I need to use the same for every lun and it jeopardizes our ability to do thin provisioning.
urs_rams2005
22 Posts
0
July 17th, 2013 06:00
When the pair was initial setup, we used invalidate r2 option.
V7.4 - do you think SE version might be causing an issue here ??
Avinash V
91 Posts
0
July 17th, 2013 06:00
We need to ensure we have SE 7.4 at minimum to support enguinity 5876.
Could you please upgrade SE and then let us know the result.
Roshan_Raju
53 Posts
0
July 17th, 2013 07:00
When running in un-supported or non-compatible versions, we can never predict how issues pan out. If it were me, i would move to 7.4 and check. Its better that way.
urs_rams2005
22 Posts
0
July 17th, 2013 08:00
Installed SE7.6 on my test machine and established the pair ,but the result is still the same..
Goes into sync in progress and immediately going into Invalid state.
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
N/A 2BC2 RW 0 2111381 RW 555C WD 0 0 C.D. SyncInProg
N/A 2BDA RW 0 5530861 RW 5574 WD 0 0 C.D. SyncInProg
Total -------- -------- -------- --------
Track(s) 0 7642242 0 0
MB(s) 0 477640 0 0
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
N/A 2BC2 RW 0 2100383 RW 555C WD 0 0 C.D. Invalid
N/A 2BDA RW 0 5529726 RW 5574 WD 0 0 C.D. SyncInProg
Total -------- -------- -------- --------
Track(s) 0 7630109 0 0
MB(s) 0 476882 0 0
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
N/A 2BC2 RW 0 2092173 NR 555C WD 0 0 C.D. Invalid
N/A 2BDA RW 0 5529606 RW 5574 WD 0 0 C.D. Invalid
Total -------- -------- -------- --------
Track(s) 0 7621779 0 0
MB(s) 0 476361 0 0
Roshan_Raju
53 Posts
0
July 17th, 2013 23:00
Can you confirm if both the R1 and the R2 pools are not full?
Avinash V
91 Posts
0
July 18th, 2013 01:00
Please provide the symapi logs after masking the symm id.
urs_rams2005
22 Posts
0
July 18th, 2013 05:00
As I told earlier source is VMAX and target is DMX .We do have lot of free space on Source and on DMX its thick allocated.
urs_rams2005
22 Posts
0
July 18th, 2013 05:00
I am not fiding any errors in the symapi log , the log reports successfull establishment of pair...
07/17/2013 16:09:51.892 8632 3996 Initialize device track tables in (xxxx,xxx).....................Not Needed.
07/17/2013 16:09:52.118 8632 3996 Mark target device(s) in (xxxx,xxx) to refresh from source.......Not Needed.
07/17/2013 16:09:52.118 8632 3996 Merge track tables between source and target in (xxxx,xxx).......Not Needed.
07/17/2013 16:09:52.119 8632 3996 Read/Write Enable device(s) in (xxxx,xxx) on SA at source (R1)...Not Needed.
07/17/2013 16:09:52.119 8632 3996 Set device(s) in (xxxx,xxx) to be RDF Ready at source (R1).......Not Needed.
07/17/2013 16:09:52.264 8632 3996 EMC:SYMRDF ASCrasusres250_03 remote: (0), RA Grp: (47), Flags: (0), ASCrasusres250_03: SYSCALL_NON_ZERO_RC, Order 17 code: 0x29, Order 17: SRR1_NEED_DD_TO_RESUME, SYMAPI sts: SYMAPI_C_NEED_MERGE_TO_RESUME
07/17/2013 16:09:52.289 8632 3996 Merge track tables between source and target in (xxxx,xxx).......Started.
07/17/2013 16:10:22.549 8632 3996 Result of locally Polling TAG:0161007F#67: (D0 is done running) on SID: 000xxxxxxxx
07/17/2013 16:10:22.551 8632 3996 Devices: 2BDF-2BF1 in (xxxx,xxx).................................Merged.
07/17/2013 16:10:34.562 8632 3996 Result of locally Polling TAG:0161007E#67: (D0 is done running) on SID: 000xxxxxxxx
07/17/2013 16:10:34.563 8632 3996 Devices: 2BC2-2BDE in (xxxx,xxx).................................Merged.
07/17/2013 16:10:34.581 8632 3996 Merge track tables between source and target in (xxxx,xxx).......Done.
07/17/2013 16:10:34.617 8632 3996 Resume RDF link(s) for device(s) in (xxxx,xxx)...................Done.
07/17/2013 16:10:34.727 8632 3996 The RDF 'INCREMENTAL ESTABLISH' operation SUCCEEDED.
Avinash V
91 Posts
0
July 18th, 2013 06:00
* There would be something in the backend which is causing the device pair to go to INVALID state.
* As you have already logged a call with the support, you may have the only workaround suggested to try and find out. Try it on one of the device pair and check.
* For better understanding for forum users, could you share the details as to why we need to fully allocate thin device on source side(in case if the support had shared the cause)