How To Repair Snapmirror Error 13102 (Solved)

Home > Could Not > Snapmirror Error 13102

Snapmirror Error 13102

Contents

Cleaning up... 1287-272341-1489317 Back to top Derek Bezy Members #11 Derek Bezy 17 posts Posted 19 August 2010 - 08:56 PM DNS resolution is fine between the filers.The ports are fine Special thanks to NetApp's Scott Owens for pointing me in the right direction on this. Also, you may want to take a look at the SnapMirror log file on the destination system (found in the /etc/log directory. Found this article: https://kb.netapp.com/support/index?page=content&id=1011333 Something else to check, has snapmirror.access been setup on each system so they can talk to each other? navigate here

Is there a firewall between them? SnapMirror must be on.Dest> snapmirror status2. Reply 0 Kudos « Previous 1 2 Next » « Message Listing « Previous Topic Next Topic » MORE IN COMMUNITY Learn How to Get Started Community Help Community Code of please recheck that.3. my response

Cannot Accept Snapmirror Destination Requests: Access Denied For Snapmirror/snapvault Destination.

any idea? Other Posts ← Windows VMs on XenServer Mysteriously Jumping a Day AheadWindows Server Core Full Configuration with PowerShell → FREE TECH TIPS, TOOLS, AND RESOURCES Sign up for Ben's FREE Finishes any write activity and then disables further updatesDest> snapmirror quiesce /vol/vol0/mymirror3. Not only that, the filer was using its iSCSI address on the LAN VIF!

  1. Traffic was exiting on the wrong interface.
  2. so both systems need to allow each other Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-20 03:55 PM ok
  3. it seems to be working now.
  4. I currently am running 2 simulators NAFiler01 and 02.
  5. Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by
  6. There may be several versions of the log file there (i.e.
  7. For example, if your storage appliance is directly connected to the 172.16.1.0/24 network, and you want to send a packet to a device with the IP of 172.16.1.55, traffic should egress
  8. SEE THE SOLUTION 1 person had this problem Me too Tags: 2240-2error13102fasfas2020fas2240-4 View All (8) Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content bsti Re:
  9. becouse i need both san2 and san4 to be able to sync the data with san1.

We think that snapmirror is running fine and it should work fine. Please re-enable javascript to access full functionality. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content GARCIA88JOSE Re: Snapmirror Error 13102 (The source volume is a dense volume which could not be snapmirrored Netapp Snapvault Could Not Write To Socket Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

I fixed it by adding a route statement on the destination filer that specifically directs traffic to the source filer to use the desired interface (in this case, the iSCSI VIF). 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 Just the alerts pop up for the netapp error. 1287-272341-1489247 Back to top Parthasarathy Ramachandran Members #4 Parthasarathy Ramachandran 19 posts Posted 19 August 2010 - 05:14 PM As long as over here Several functions may not work.

Reply 0 Kudos « Message Listing « Previous Topic Next Topic » MORE IN COMMUNITY Learn How to Get Started Community Help Community Code of Conduct Provide Community Feedback Forums Blogs Could Not Read From Socket Snapvault I havent seen this happen in our setup in house, except for cases where the DNS was not correctly configured. To troubleshoot, I started a packet trace on the destination filer using the command: pktt start all -d /etc I then kicked off the snapmirror initialization, waited for it to fail, But when you say undedupe thevolume, you mean ?myfilser> sis undo /vol/vol1If is the above command i did not.*Could it be the issue???*2) A: I am using Volume SnapMirror in DOT

Snapmirror.access Legacy

Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-21 09:46 AM the source and destination volumes do not exist anymore. Make sure you have entries in the /etc/hosts ve file for both Source and Destination, otherwise name lookup will not work. Cannot Accept Snapmirror Destination Requests: Access Denied For Snapmirror/snapvault Destination. Then do the sync the other way after again Sent from my iPhone 4S Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror Netapp Snapmirror Could Not Read From Socket I will share my experiences and small tips&tricks about Microsoft Server Family , Cisco Devices , HP and IBM servers and storages on this site.

I'll send you a private message 1287-272341-1489566 Back to top RACHEL ZHU Members #16 RACHEL ZHU 7 posts Posted 20 August 2010 - 06:39 PM SnapMirror seems to be using the but a reverse resync gives another error.SnapMirror transfer request from lun_19Jun2012_175417_vol_SnapMirror_20Jun2012_074939 to host eq-ntap2 at IP address 10.51.1.11 denied: check options snapmirror.access. Any new data added to the volume after dedupe is disabled will not be deduplicated. but I am trying to setup a ms cluster across sites so I have snapmirror from source vol to destination vol. Netapp Snapmirror Could Not Write To Socket

Some errors in syslog on the filer do not interfere with the actual snapmirror setup 1287-272341-1489235 Back to top Derek Bezy Members #3 Derek Bezy 17 posts Posted 19 August 2010 I do have snap mirror access enabled but I think I might be missing something. thanks in advance. http://unordic.com/could-not/snapmirror-error-could-not-read-from-socket.html The remedy was as simple as adding a route statement similar to this: route add inet 172.16.1.0/24 172.16.2.1 1 where 172.16.1.0/24 is the iSCSI network I want to traverse to reach

Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content soper_2010 Re: snapmirror error could not read from socket (error 13102) ‎2013-01-30 06:37 AM Thanks for answer!now Netapp Snapmirror Cannot Connect To Source Filer Unfortunately, in the case of some NetApp filers, this does not always happen. Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

I've found that you can get more details in the snapmirror log file than appears on the console when trying to troubleshoot SnapMirror.Ken Reply 0 Kudos Options Bookmark Highlight Print Email

Other replication jobs I have set up between these two filers work in the opposite direction with the multiplexed configuration. The error I am getting is below:==ERROR==com.netapp.sysmgr.client.api.NaApiFailureException==TIME==2012-01-11 11:46:55,282==MESSAGE==Snapmirror error: cannot connect to source filer (Error: 13102)==DETAILS==No details are available.==CORRECTIVE ACTION==No suggested corrective action is available.==LOCATION==Location is not specified.==BROWSER INFO==App Name: Microsoft I ran into a peculiar issue when trying to force NetApp's Snapmirror to replicate across a specific interface, only to be met with an ugly "Snapmirror error: cannot connect to source Ossv Cannot Read From Socket What are the volume sizes for both the source & the destination volumes (df -g & df -g -S would be helpful)Do you have dedupe enabled on

Try this just to make sure:SAN1 snapmirror.allow:10.10.10.20 # Assuming this is for SAN210.10.10.44 # Assuming this is for SAN4 Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Finish writes to fas1_vol1Dest> snapmirror quiesce source_vol13. 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 weblink not deduplicated) in the SnapMirror destination.

the content of file was :san210.10.10.20and i put san4 int´a new line so it become:san210.10.10.20san410.10.10.44and the result is the same, and get the same error. the volume was still only in read mode. I'm always hesitant to label every quirk a "bug," but this is definitely not correct behavior.