Netapp Snapmirror Error Cannot Connect To Source Filer
Contents |
your search results by suggesting possible matches as you type. Forums Blogs Tech OnTap Newsletter Register · Sign In · Help Products and Solutions FAS, ONTAP and
Transfer Aborted: Cannot Connect To Source Filer.
OnCommand Backup and Restore E-Series, SANtricity and Related Plug-ins Virtualization cannot connect to source filer snapvault and Cloud Network Storage Protocols AutoSupport and My AutoSupport All Flash FAS, EF-Series, and SolidFire
Snapmirror Ports
Systems FlexPod and Converged Infrastructure Developer Network NetApp University and Training Community Base Camp NetApp Community : Forums : Products and Solutions : FAS, ONTAP snapmirror break and OnCommand : Data ONTAP Discussions : Snapmirror error: cannot connect to source filer (Error: 13102) 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 Inappropriate Content DZEMBOC77 netapp snapmirror commands Snapmirror error: cannot connect to source filer (Error: 13102) 2012-12-31 02:07 PM Labels: SnapMirror Hello,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.==ERROR==com.netapp.sysmgr.client.api.NaApiFailureException==TIME==2012-12-31 17:04:30,854==MESSAGE==Snapmirror error: cannot connect to source filer (Error: 13102)==DETAILS==No details are available.==CORRECTIVE ACTION==No suggested c
your search results by suggesting possible matches as you type. 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 Protocols AutoSupport and My AutoSupport All Flash FAS, EF-Series, and SolidFire Systems FlexPod and Converged Infrastructure Developer Network NetApp University and Training Community Base Camp NetApp Community : Forums : Products and Solutions : FAS, ONTAP and OnCommand : Data ONTAP Discussions : Troubles with snapmirror: cannot https://community.netapp.com/t5/Data-ONTAP-Discussions/Snapmirror-error-cannot-connect-to-source-filer-Error-13102/td-p/7729 connect to source filler 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 Inappropriate Content raef_mansour Troubles with snapmirror: cannot connect to source filler 2012-01-21 02:08 PM Labels: SnapMirror Guys,I’m having an issue http://community.netapp.com/t5/Data-ONTAP-Discussions/Troubles-with-snapmirror-cannot-connect-to-source-filler/td-p/45538 and need some help. My destination filer cannot connect to the source for some reason and my snap mirror is failing. Both are up on the network, pingable.I m not familiar with the use of file like snapmirror conf or /etc/file thats why i used the storage manager to set the snap mirror relationshipon local i have DOT 7.3.3 on DR site I ave 7.3.6i have set options snapmirror.access to all on both controlleroptions snapmirror.checkip.enable to on alsoI have modified the etc/snapmirror.allow (adding all ip and name of other side storage machine)rdfile /etc/snapmirror.allow192.168.141.101192.168.141.103192.168.141.104192.168.141.106AFDB_NSERIES_HAUTAFDB_NSERIES_BASAFDB_NSERIES_BAS-e0aAFDB_NSERIES_BAS-e0bI have tried a lot of syntax for snapmirror but always the same message: cannot connect to source filer...snapmirror initialize -S 192.168.141.103:vol_test AFDB_DR_NSERIES_BAS:vol_test_SnapMirror_21Jan2012_133245snapmirror initialize -S AFDB_NSERIES_BAS-e0a:vol_test AFDB_DR_NSERIES_BAS-e0a:vol_test_SnapMirror_21Jan2012_133245snapmirror initialize -S AFDB_NSERIES_BAS:vol_test AFDB_DR_NSERIES_BAS:vol_test_SnapMirror_21Jan2012_133245I need your advises please 1 person had this problem Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TECHNOCIS Re: Troubles with snapmirror: cannot connect to source filler 2012-01-22 01:49 AM Hi Please try
your search results by suggesting possible matches as you type. 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 Protocols AutoSupport https://community.netapp.com/t5/Backup-and-Restore-Discussions/snapmirror-error-13102/td-p/15426 and My AutoSupport All Flash FAS, EF-Series, and SolidFire Systems FlexPod and Converged Infrastructure Developer Network NetApp University and Training Community Base Camp NetApp Community : Forums : Products and Solutions : Backup http://benpiper.com/2012/01/forcing-netapp-to-use-the-correct-network-interface/ and Restore : Backup and Restore Discussions : snapmirror error 13102 Subscribe Reply Topic Options Subscribe to RSS Feed Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » cannot connect « Previous 1 2 Next » Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 snapmirror error 13102 2012-06-20 08:00 AM Labels: SnapDrive I keep getting a snapmirror error or 13102.cannot connect to source filer. any idea? 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 cannot connect to network setup between the two systems? Is there a firewall between them? If so, are the required ports open? 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? 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. it seems to be working now. but I am trying to setup a ms cluster across sites so I have snapmirror from source vol to destination vol. when i failover the ms cluster resource from source to destination, the destination drive remains as eadable only and not writable. what do I have to do to make that writable? Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content mike_burris Re: snapmirror error 13102 2012-06-20 11:27 AM You'll have to break the SnapMirror (or clone the destination possibly). If this is a SnapManager program, which should be utilizing SnapDrive, SnapDrive should be able to break the mirror from what I've glimpsed over documentation wise... Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report In
by benpiper If you're familiar with networking you know that when a device is directly connected to two separate IP networks, traffic destined for one of those networks should egress on the interface that is directly connected to that network. 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 on the interface connected to that network. Unfortunately, in the case of some NetApp filers, this does not always happen. 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 filer (Error: 13102)". I confirmed with NetApp support that the Snapmirror configuration was correct for what I was trying to accomplish. 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, then stopped the packet trace with pktt stop all Since I directed the trace files to be placed in /etc on the filer I just browsed to the hidden etc$ CIFS share on the filer and opened the traces in Wireshark. What I found was that the traffic that should have been egressing on the iSCSI VIF was actually going out on the LAN VIF. Not only that, the filer was using its iSCSI address on the LAN VIF! I'm always hesitant to label every quirk a "bug," but this is definitely not correct behavior. 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 the Snapmirror partner, and 172.16.2.1 is the gateway on my locally connected iSCSI network. The 1 specifies the cost metric for the route, which will always be 1 unless you need to add additional gateways. To make the change permanent, simply add the route statement to the /etc/rd file on the filer. Special thanks to NetApp's Scott Owens for pointing me in the right direction on this. 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 monthly newsletter Email: Name: Sign Up (803) 569-5728 [emailprotected] Copyright © http://benp