2011-04-07 07:36 AM
For source it can may be possibly controlled using options snapmirror.access, although your target should really not try to connect to e0M.
For target I do not think it is possible at all. It just tries to connect to source; which (outgoing) interface is used is determined by routing tables. If your source is on a network that happens to be reachable via e0M, there is nothing filer can do about it.
2011-04-07 08:37 AM
options interface.blocked.snapmirror e0M you can also block nfs, cifs, iscsi on a per interface basis using these... check "options interface.blocked" to see all the ways to block a protocol per interface.
2011-04-07 08:39 AM
Are you using DPM or manual snapmirror?
The way i have done it is to create a hosts file entry on the snapmirror destination that has the IP address of the interface on the source filer that you wish to use.
Note if you are doing manual snapmirror it uses the short name (example: sourcefiler) and if you are using DPM it uses the FQDN (sourcefiler.domain.com) so I would create both entries.
Note as the destination filer is the one that controls replication this is the only place you have to make that entry.
This is the simplest way i have been able to do it I have seen some recomendations of creating an alias in the snapmirror.conf file or if using DPM setting the NDMP preffered interface but I have not personally tried either method.