I'm trying to setup VMware SRM with netapp simulator 8.1.1,
I created the volume in the PR site and its snapmirred to the DR, .
during the SRM configuration, in the array managers, I added SRA on both sites and it added successfully.
But when I tried to enable the array pair, the PR site get paired with DR site with out any issue, the DR site is showing error as follows.
SRA command 'discoverDevices' failed. SAN or NAS device not found
Ensure that the SAN device is configured and mapped to an igroup of ostype vmware and the NAS device is configured and exported with rw rules.
I checked the options httpd on the simulator, it shows as follows.
DR-NODE1> options httpd
Please find the attachment for the SRM error screen.
I had a similar issue on a production system, but it was the "options httpd.admin.enable on" that fixed it for me.
EDIT: I ran into this again on a re-installation and reconfiguration run, and discovered an old export from a previous test run laying around that it was attempting to remount. Once I cleaned up the /etc/exports and did a "exportfs -a" it went fine.
I'm not sure if you found a permanent response to this, but there are a couple of things I wanted to add in case you're hitting them:
We often see this when snapmirror.conf is setup incorrectly, or DNS between all of the sites and hosts isn't working properly. If the snapmirror update functions between the simulators (snapmirror update), then make sure that the DNS to the simulators works from the hosts that are running the SRA.
If you are running SRA 2.0.1, which is required for use with SRM 5.1, then you must list all volumes in the "Volume Include List" within the array managers to force the DiscoverArrays to match replicated devices properly. This is documented in BURT http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=642115
If you have any "mistakes" in the exports file, or are listing the exports with the -actual option, or you've got a volume in the exports list more than once, you will also end up with this error.
To help troubleshoot and narrow down "where" the problem is coming from, you can check the audit logs from the simulator to see if the IP address of the SRA is actually sending ZAPI calls to the simulator, if it's not, then you will know the problem is within the configuration of the SRA; if it is, then you know the problem is with the configuration on the controller itself.