I upgraded SRM 4.1 to 5.0 without issues. I was able to PAIR the two sites successfully.. Have two CX4s arrays with MirrorView.
I did install the following for Storage Array Management:
- Solution Enabler 7.301 32 bits.
- Navisphere CLI 32 bits . Tried it with { Do not create security file AND Create security file} , default Low level for Certificate checking}
- EMC_VNX_SRA_v5.0.1
- EMC_Mirrorview_Enabler_for_VNX_SRA_v5.0.2
When I tried to add storage array, the only choice under “SRA type “ was VNX . I added the protected CX4 Array under the first Protected Site supplying "SPA IP" address on the Management IP/Hostname and "SPB IP" address on the secondary Managmenet IP/Hostname .
When I clicked on enable, I got the following errors. “SRA command 'discoverDevices' didn't return a response”
The whole setup used to work fine in 4.1 , and there is no network restrictions between vCenter|SRM|CX4s servers.
We are looking at a similar issue and will let you know when the cause is determined. Meanwhile, would it be possible to get your log files (you have private message with contact info)?
I am glad you are up and running! Did you perhaps restart the SRM services? The EMC VNX SRA & corresponding MirrorView Enabler do not require EMC Solutions Enabler or VSI.
Please send me a private message with your contact info and I will send you a link to the updated MirrorView Enabler (soon to be available on PowerLink).
Indeed the software worked for us. Now i'm able to see the mirrored luns. Unfortunatly we have a new problem.
i have created 1 LUN (HLU 17 in SG CC) + snapshot (HLU 37 in SG CC) on 1 site and created exactly the same on the other site (only used a different storage group). I created a mirror from CC to AMS (those are site names). Created a datastore on site CC (VMFS5). Put a VM (with tools upgraded) on it (On vSphere 5). SRM placeholder LUN's are also VMFS 5.
Configured SRM (Resource mapping, placeholder, protection group, recovery plan, pair sites, pair array) and when i do a test recovery everything works perfectly.
But when i do a real recovery plan (with the migration option) the plan failed.
.1. TESTPC
Error - Failed to promote replica devices. Failed to promote replica device 'sync-RM_CC-VMFS5-01-R5-MIX-P0'. SRA command 'failover' failed for device 'sync-RM_CC-VMFS5-01-R5-MIX-P0'. Could not add device to the storage group. Please check log file for more information.
2011-12-14 14:33:00 (UTC 0)
2011-12-14 14:33:00 (UTC 0)
11.1.1. Configure Storage
Error - Failed to promote replica devices. Failed to promote replica device 'sync-RM_CC-VMFS5-01-R5-MIX-P0'. SRA command 'failover' failed for device 'sync-RM_CC-VMFS5-01-R5-MIX-P0'. Could not add device to the storage group. Please check log file for more information.
It says SRM is not able to add the secondairy lun (that is now promoted correctly by srm on the failover site AMS
) to the storage group. That is strange because it is already in. So i tried removing the secondairy lun from the failover array storage group but that didn't work either.
Problem we have now is the following. I'm in a failover state where i can see (After a manual rescan of the failover esx hosts) the datastore. It is now mounted as SNAP.....(datastore name). I can confirm that i run a test before and that the cleanup was succesfull (including multiple rescans to be sure everything was ok). Because (i think
) it is in snap state srm wont continue the recovery plan. So i can browse the datastore and i think i can reregister the vm again but that is not how it suppose to work. So i think their might be an issue with the recovery plan steps in SRM. I use the new mirrorview enabler. Because of this problem i removed all the SRM, SRA and MV enabler, Rebooted the servers, reinstalled it again (using the same SRM database) and run the same test again. Result is the same problem.
Do you have experiance with this problem? I also opened a case with EMC and VMware but didn't hear anything yet from them and because you found the previous sollution i thought lets give it another try :-)
isgdev
25 Posts
1128
0
Posted November 30th, 2011 09:00
We are looking at a similar issue and will let you know when the cause is determined. Meanwhile, would it be possible to get your log files (you have private message with contact info)?
Best Regards,
Bryan