2012-12-31 02:07 PM
I am trying create a lab for Site Recovery Manager in VMware. I think I am almost there but ran into a snag creating the snapmirror. I currently am running 2 simulators NAFiler01 and 02. When trying to create a snap mirror for my test volume the volume gets created on the destination (NAFiler02) but I get the error message Snapmirror error: cannot connect to source filer (Error: 13102). I am only using 1 interface ips 192.168.72.151 and 152. I do have snap mirror access enabled but I think I might be missing something. The lab is using Workstation 9, and currently usring NAT for the network configuration. I get that error when I try to initialize the snapmirror.
Snapmirror error: cannot connect to source filer
No details are available.
No suggested corrective action is available.
Location is not specified.
App Name: Microsoft Internet Explorer
App Version: 5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
App Codename: Mozilla
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Cookie Enabled: true
2013-01-01 06:24 AM
You may wish to double check the /etc/hosts file (#rdfile /etc/hosts) to make sure both the source/target filer are in the file.
Good luck & Happy New Year
2013-01-04 03:51 AM
Please check the network setting on vmware workstation.
1. Assign the same network for both host of netapp simulator machine.
2. try to ping from secondry filer to primary. If ping is not available then probelm is vmware network settings. please recheck that.
3. on filer lable just check that proper access is givine for both host on snapmiror.access list also check the /etc/hosts entry and /etc/hosts.equiv.
Please let us know if still your problem is existing.
2013-01-06 07:58 AM
Check that you are able to ping your destination Filer/Simulator. Make sure you have entries in the /etc/hosts ve file for both Source and Destination, otherwise name lookup will not work. If your snapmirror.conf is using names fo rthe relationship, then these entries need to be in there.
Checking these options will not help, as they are related to the FilerView adminstration page.
options httpd.admin.access all
options httpd.admin.enable on
Check the following option for both systems. Make sure that the source IP is allowed on the destination system. etc.
2014-09-03 11:58 AM
Its simply because of the etc hosts file. We think that snapmirror is running fine and it should work fine. It will work fine in case of SRM failover but while doing failback it actually runs snapmirror resync, in this case our source becomes destination and destination becomes source so our /etc/hosts file should be updated accordingly means it should have name and IP of both the storage filers on both end. Hope it will help