Unsolved
This post is more than 5 years old
16 Posts
0
5798
Mirrorview /A over ISCSI Error
Iam experincing an error with mirrorview /A over iscsi when there is a link failure replication doesn't resume automatically once the link comes up. Autorecover policy is set to automatic and this policy doesn't seem to work. When the clariion cx4-120 was running flare code 29 it was working fine but after upgrading to flare code 04.30.000.5.517 we noted this problem. EMC support has looked into this issue but are yet to come up with any tangible solution , The only answer I got was there could be a bug with this flare code and that it will be fixed in next patch release of first quarter 2012 but no official documatation or technical advisories from EMC on thise issue.
What I have noted is the ISCSI Login is not automatic when the link resumes and according to EMC Support the only solution is to disable and enable ISCSI connection from manage connections for the replication to continue which is a manual way not automatic.
Has anyone experienced thise problem ?
JoeCap2
18 Posts
0
January 7th, 2015 12:00
I am having the same problem i keep getting mirrors that admin fracture and say they cannot communicate with the secondary SP. I am running flare 4.30.000.5.525 on the primary side and 4.30.000.5.526 on the DR side. We checked all network setting and everything is good is it a bug in flare code 525?
Thanks
lfmarrero
4 Posts
0
January 7th, 2015 12:00
After dealing with this and several issues like it, the problem has always been with either the network itself (physical cables,switches,bandwidth) or that the port or sfp on the I/O module is failing. Since this is ISCSI Try replacing the I/O module, if you are sure the network isnt the issue.
JoeCap2
18 Posts
0
January 14th, 2015 07:00
This is very strange not all of the mirrors fracture some keep going. I am seeing this on both SPA and SPB
kelleg
4.5K Posts
0
January 14th, 2015 14:00
You might want to open a service request with EMC to see if there is anything on the array's that might be causing this. If you do, be sure to get new spcollects from both arrays and attach to the case.
glen
Jsang2
16 Posts
0
February 2nd, 2015 08:00
A patch sorted out the problem , suspect there might have been a bug
kelleg
4.5K Posts
0
February 6th, 2015 10:00
It would be useful for others here if you could provide more details on the patch that fixed your issue. Was it a specific flare patch update? if so, which version did you install that fixed the issue?
glen