Home > Could Not > Snapmirror Error 13102

Snapmirror Error 13102

Contents

If so, there should be details in the log.Or are you saying that StorageLink reports success and the array reports that the snapmirror errored out? 1287-272341-1489252 Back to top Derek Bezy I specified a multiplexed configuration in the snapmirror.conf to force replication to occur on a particular interface. The 1 specifies the cost metric for the route, which will always be 1 unless you need to add additional gateways. Also, you may want to take a look at the SnapMirror log file on the destination system (found in the /etc/log directory. navigate here

Subscribe Reply Topic Options Subscribe to RSS Feed Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » Options Bookmark Highlight Print Email to a Friend Report The filers are 3140's with Ontap 7.3 1287-272341-1489183 Back to top Parthasarathy Ramachandran Members #2 Parthasarathy Ramachandran 19 posts Posted 19 August 2010 - 04:13 PM What errors do you see At Scott's suggestion I ran a packet trace on the destination filer while kicking off the snapmirror initialization. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content jeras Re: Snapmirror Error 13102 (The source volume is a dense volume which could not be snapmirrored

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

Egemen TANIRER (Computer Engineer) View my complete profile PowerGui Feedjit Live Blog Stats Total Pageviews span.fullpost {display:inline;} Jump to content Citrix Citrix Discussions Log In Citrix.com Knowledge Center Product Documentation 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 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 the volume was still only in read mode.

  1. it seems to be working now.
  2. 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
  3. 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
  4. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content SUDHEER_H21 Re: snapmirror error 13102 ‎2012-06-20 12:59 PM This is the procedure if you want to make
  5. The lab is using Workstation 9, and currently usring NAT for the network configuration.
  6. StorageLink Site Recovery-NetApp Snapmirror error Started by Derek Bezy , 19 August 2010 - 02:16 PM Login to Reply 16 replies to this topic Derek Bezy Members #1 Derek Bezy 17
  7. I am only using 1 interface ips 192.168.72.151 and 152.
  8. Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content rwelshman Re: Snapmirror Error 13102 (The source volume is a dense volume which could not
  9. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content scottgelb Re: snapmirror error 13102 ‎2012-06-20 03:40 PM you need snapmirror.access set on both sides...
  10. Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

What I found was that the traffic that should have been egressing on the iSCSI VIF was actually going out on the LAN VIF. 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. 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 Snapvault Could Not Write To Socket the destination and source volumes are already deleted.

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). 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 Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-20 11:16 AM bnot sure what happened. I will share my experiences and small tips&tricks about Microsoft Server Family , Cisco Devices , HP and IBM servers and storages on this site.

not deduplicated) in the SnapMirror destination. Could Not Read From Socket Snapvault SnapMirror must be on.Dest> snapmirror status2. Other replication jobs I have set up between these two filers work in the opposite direction with the multiplexed configuration. Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

Snapmirror.access Legacy

I think I am almost there but ran into a snag creating the snapmirror. Also check if the snapmirror ports are open (I assume the latter is ok since you said you use snapmirror already today)[Inf,2304,2010-08-19,10:01:27,NETAPP]: prepareSnapmirrorTargetVolumes: going to use target aggr aggr_KFI_XEN_DR3[Inf,2304,2010-08-19,10:01:27,NETAPP]: Using StoragePool Cannot Accept Snapmirror Destination Requests: Access Denied For Snapmirror/snapvault Destination. Special thanks to NetApp's Scott Owens for pointing me in the right direction on this. Netapp Snapmirror Could Not Read From Socket I am not using snapdrive Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content scottgelb Re: snapmirror error 13102 ‎2012-06-20 04:27 PM After any resync you

Let us know How to Make NetApp Use the Correct Interface for iSCSI Toggle navigation About Blog Newsroom Free Resources Results Posted by Ben Piper on January 25, 2012 How to Break volume fas1_vol1 from the snapmirror relationshipFAS2> snapmirror break source_vol1For QSM:1. The designation destination volume does exist (I have tried this replicating both a volume and a qtree and both fail). Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by Netapp Snapmirror Could Not Write To Socket

To make the change permanent, simply add the route statement to the /etc/rd file on the filer. 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: Any ideas why I get this error in one direction only? his comment is here Finishes any write activity and then disables further updatesDest> snapmirror quiesce /vol/vol0/mymirror3.

Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by Netapp Snapmirror Cannot Connect To Source Filer 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, In this context, assign FILER01 or FILER02 hostnames to VIF1 interfaces on both sides.For more information, please check http://www.netapp.com/us/library/technical-reports/tr-3326.html 1287-272341-1489576 Back to top Derek Bezy Members #17 Derek Bezy 17 posts

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

Can you verify something in the middle isn't stopping SM traffic between the two? snapmiror, snapmirror.0, snapmirror.1). Forums Blogs Tech OnTap Newsletter Register · Sign In · Help Products and Solutions FAS, ONTAP and OnCommand Backup and Restore E-Series, SANtricity and Related Plug-ins Virtualization and Cloud Network Storage Ossv Cannot Read From Socket Netapp ONTAP is picky about certain things, and we abstract out some of the errors that it throws. 1287-272341-1489249 Back to top Derek Bezy Members #5 Derek Bezy 17 posts Posted

Unfortunately, in the case of some NetApp filers, this does not always happen. 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 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 http://phabletkeyboards.com/could-not/snapmirror-error-could-not-read-from-socket.php I confirmed with NetApp support that the Snapmirror configuration was correct for what I was trying to accomplish.

please recheck that.3. 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. but after the successful resync. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-20 02:58 PM ok now i broke the mirror, destination drive is

Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content mike_burris Re: snapmirror error 13102 ‎2012-06-20 09:07 AM How/what is the network setup between the Snapmirror works perfectly for our non-storagelink Xen volumes 1287-272341-1490195 Back to top Report abuse Back to StorageLink Manager Reply to quoted posts Clear Citrix ©1999-2016 Citrix Systems, Inc.