I am installing SRM on a customer site and have configured the array pairs, their appears to be no errors but the Enable/Disable link is greyed out. I therefore cannot bring these on line
I am using SRM 5.0.1 and NetApp FAS/V 2.0. against 3200 series Filers
Bump, anybody any more Ideas?
I would check the following:
NetApp SRA 2.x
Enter the NFS IP address when adding Array - I ran into other issues with NetApp and this made a difference for me.
Test with root first before using RBAC
Alos, check the Snapmirrors on the NetApp heads.
Check this out. https://communities.netapp.com/thread/19380
Thanks for those ideas, but there is not NFS on this Array it is all FC, also spent most of today on that post, and it unfortunately does not apply both my source and desitnation are using short name.
How are the volumes mounted to your ESX hosts? I found that I had to mount them by IP address in order to properly pair them in the SRM array manager. When I mounted them by short hostname or FQDN it wouldn't work.
Mounting by IP in ESX is a best practice thing anyway, if I recall.
There is no IP on the volumes the array presents fiber to the ESX environment, on NFS or iSCSI niceness on this site. all FC
Bump, anybody any more Ideas?
I can only I've run into the same problem. Any solutions yet?
In my case I use the EMC Recoverpoint adapter
For RecoverPoint check that you have your Consistency Groups all in SRM managed mode.
Do you mean ALL, Or just the ones I need to recover from SRM?
Anyway? I did both. Also performed a Rescan and no luck. Still Greyed Out
Apologies, just the CGs used by SRM. The RecoverPoint SRA has been pretty reliable for me. Do you get anything of interest from the SRA or SRM logs?
Thanks for your response. I got nothing out of the logs. I think because there's nothing to click on. A difficult one!
Problem solved. I entered the same Recoverpoint management IP addresses in both SRM adapter sites. Changing that solved my problem.
Hi,
have a look @ https://communities.netapp.com/message/74989
We had the same issue and found it was due to a missmatch in the snapmirrow.conf names. On one side the pairing was Hostname Hostname on the other side it was hostname FQDN hostname. as soon as we changed that it worked.
D