topic Re: Troubles with snapmirror: cannot connect to source filler in ONTAP Discussions

Troubles with snapmirror: cannot connect to source filler

raef_mansour — Thu, 05 Jun 2025 06:36:55 GMT

Guys,

I’m having an issue 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 relationship

on local i have DOT 7.3.3 on DR site I ave 7.3.6

i have set options snapmirror.access to all on both controller

options snapmirror.checkip.enable to on also

I have modified the etc/snapmirror.allow (adding all ip and name of other side storage machine)

rdfile /etc/snapmirror.allow

192.168.141.101

192.168.141.103

192.168.141.104

192.168.141.106

AFDB_NSERIES_HAUT

AFDB_NSERIES_BAS

AFDB_NSERIES_BAS-e0a

AFDB_NSERIES_BAS-e0b

I 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_133245

snapmirror initialize -S AFDB_NSERIES_BAS-e0a:vol_test AFDB_DR_NSERIES_BAS-e0a:vol_test_SnapMirror_21Jan2012_133245

snapmirror initialize -S AFDB_NSERIES_BAS:vol_test AFDB_DR_NSERIES_BAS:vol_test_SnapMirror_21Jan2012_133245

I need your advises please

Re: Troubles with snapmirror: cannot connect to source filler

TECHNOCIS — Sun, 22 Jan 2012 09:49:46 GMT

Please try and log onto the source filer ssh name of filer and type

options.snapmirror.access host=nameofdestserver1,nameofdestserver2

Make sure you have dns or wins setup and is resolvebale on source and dest other put some static entries in host files if you dont have it.

/etc/hosts

Technocis

http://www.technocis.com

Re: Troubles with snapmirror: cannot connect to source filler

TECHNOCIS — Sun, 22 Jan 2012 09:50:02 GMT

Please try and log onto the source filer ssh name of filer and type

options.snapmirror.access host=nameofdestserver1,nameofdestserver2

Make sure you have dns or wins setup and is resolvebale on source and dest other put some static entries in host files if you dont have it.

/etc/hosts

Technocis

http://www.technocis.com

Re: Troubles with snapmirror: cannot connect to source filler

TECHNOCIS — Sun, 22 Jan 2012 10:01:27 GMT

Hi Raef:

Also forgot to say make sure you have a valid snapmirror license on bothe boxes:

type

license

and check there us a code for snapmirror

This could be the culprit, also make sure that the snapmirror port number is allowed in the network.

Hope these tips help:

http://www.technocis.com

Re: Troubles with snapmirror: cannot connect to source filler

kumaraysun — Mon, 23 Jan 2012 07:19:28 GMT

Hi,

For this issue, please make sure you have range of TCP ports from 10565 to 10569 is open.

Regards

Kumaresan

Re: Troubles with snapmirror: cannot connect to source filler

VIRDIHARMEET — Thu, 05 Jul 2012 08:23:34 GMT

Hi There....

Even I am facing the same issue while configuring snapmirror. "the error which I am getting is 'cannot connect to source filer'.."

I am able to ping from either side but traceroute is not getting completed.

******************************************************************************************************

NAS1A>

traceroute 10.103.5.72

traceroute to 10.103.5.72 (10.103.5.72), 30 hops max, 40 byte packets

1 10.24.237.193 (10.24.237.193) 0.999 ms 0.000 ms 0.000 ms

2 10.24.237.17 (10.24.237.17) 0.999 ms 0.999 ms 0.000 ms

3 10.24.237.10 (10.24.237.10) 6.993 ms 2.997 ms 0.999 ms

4 10.24.237.3 (10.24.237.3) 0.999 ms 0.999 ms 0.999 ms

5 * * *

6 * * *

7 * * *

8 * * *

9 * * *

10 * * *

11 * * *

12 * * *

13 * * *

14 * * *

15 * * *

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 *Thu Jun 21 16:00:00 IST [NAS1A: kern.uptime.filer:info]: 4:00pm up 11 days, 22:06 0 NFS ops, 5759 CIFS ops, 180 HTTP ops, 105401522 FCP ops, 40 iSCSI ops

* *

30 * * *

******************************************************************************************************

and on DR filer

HYDNAS1A> traceroute 10.24.237.203

traceroute to 10.24.237.203 (10.24.237.203), 30 hops max, 40 byte packets

1 10.103.5.65 (10.103.5.65) 0.000 ms 0.000 ms 0.000 ms

2 10.103.5.209 (10.103.5.209) 1.000 ms 0.000 ms 0.000 ms

3 * * *

4 * * *

5 * * *

6 * * *

7 * * *

8 * * *

9 * * *

10 * * *

11 * * *

12 * * *

13 * * *

14 * * *

15 * * *

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

30 * * *

HYDNAS1A>

******************************************************************************************************

Do we need traceroute complete ?

So, what could be the problem ?

snapmirror license is there.

Please help.

Thanks and regards

Harmeet Singh

Re: Troubles with snapmirror: cannot connect to source filler

ARTH_CANLAS — Fri, 09 Nov 2012 07:58:28 GMT

Hi,

There are things that need to be consider.

-The gateway both source and destination is reachable.

-ip address and hostname is reachable.

-set options snapmirror.access all in both filers (source and destination)

-snapmirror license must be set in both filers (source and destination)

Then do this,

destination_filer>snapmirror initialize -S source_filer:volume1 destination_filer:volume2

destination_filer>snapmirror initialize -S 10.10.10.10:volume1 destination_filer:volume2

use either hostname or ip address of source.

Hope this could help you.

Regards,

Arth

Re: Troubles with snapmirror: cannot connect to source filler

frank_iro — Fri, 09 Nov 2012 08:22:20 GMT

Had a similar issue some time back. In my case, it turned out to be a name resolution problem. Try to ping the destination filer from the source filer (and vice versa) using it's hostname and see if you get a response. You may find that while the IP is ping-able, the hostname is not, which may point to the absence of a DNS entry for your filers in your locally configured DNS server. If this is the case, create a DNS entry for both filers. A workaround could be to add an entry in /etc/hosts for the partner filer.