What you can do is modify your rc file so that the other networks that are non-production would be defined first and set appropriate routes. Then leave defining e0M for after the others are defined. Also, depending on your ONTAP version, there are the options to limit/prevent protocol or snapmirror traffic over certain interfaces "options interface.xxxx.blocked".
Regards, André M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems | 917.388.8236 Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Chris Picton Sent: Thursday, March 21, 2013 11:31 To: toasters@teaparty.net Subject: Separating management and data traffic (e0M vs replication interfaces)
Hi all
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? Chris _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
In your snapmirror.conf you can define connections.
fridge-con = multi(fridge-gig,icebox-gig)(fridge-slow,icebox-slow) fridge-con:db icebox:db - sync
On Mar 21, 2013, at 1:59 PM, "Clark, Andre" aclark@insightinvestments.com wrote:
What you can do is modify your rc file so that the other networks that are non-production would be defined first and set appropriate routes. Then leave defining e0M for after the others are defined. Also, depending on your ONTAP version, there are the options to limit/prevent protocol or snapmirror traffic over certain interfaces "options interface.xxxx.blocked".
Regards, André M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems | 917.388.8236 Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Chris Picton Sent: Thursday, March 21, 2013 11:31 To: toasters@teaparty.net Subject: Separating management and data traffic (e0M vs replication interfaces)
Hi all
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? Chris _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Clark, Andre -
Nicholas Bernstein