I had the same issue years ago. First of all best practice is to avoid to put e0M/SP on the same subnet of other LAN/VLANs and they should be on a separate one. But I can understand this is not always possibile. There are a couple of options you could use to avoid the SM use the slow e0M.
interface.snapmirror.blocked The option is set to a comma-separated list of interface names for which snapmirror is blocked. The default is the empty list, "", which means that snapmirror is not blocked on any interface. The interface list cannot include TOE-enabled interfaces or iSCSI HBAs. See the NMG for details
ip.match_any_ifaddr If the option is on, the filer will accept any packet that is addressed to it even if that packet came in on the wrong interface. If you are concerned about security, you should turn this off. Valid values for this option are on or off. The default value for this option is on.
.
Regards,
-----Messaggio originale----- Da: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Per conto di Jan-Pieter Cornet Inviato: giovedì 21 marzo 2013 22.36 A: Chris Picton Cc: toasters@teaparty.net Oggetto: Re: Separating management and data traffic (e0M vs replication interfaces)
On 2013-3-21 16:30 , Chris Picton wrote:
I have two pairs of 3210s. The default gateway of the systems are via the management interface IP range, so that they are reachable remotely on the e0M interfaces.
However, this is causing snapmirror replication to use those interfaces as well, which is undesirable from a speed/data path persepctive.
I have considered putting e0M into its own ipspace, but then how would I manipulate its routing table as it would not be in a vfiler.
Any other ideas about having e0M reachable from anywhere, but still use a different vif as the default gateway for generic traffic on the system?
There's nothing special about snapmirror, it just uses the standard routing table like it would on a regular unix host. If you want to send your snapmirror traffic over a specific interface, then make sure that the target filer is reachable via that interface, for example by making sure that the target is in the same VLAN as the source.
What we do is send all production (NFS) traffic over private IP space in vlan's that aren't routed (no default gateway). Our vif interfaces are divided into multiple different vlan interfaces. If necessary, you can send the snapmirror traffic over such a vlan interface by making sure that the destination is in the right vlan.