I had seen the suggestion elsewhere.  Is there any real point to the e0M interface then, as is it not truly out of band.

Do you then do other remote management (system manager/snmp monitoring/etc) via the data interfaces?

On 2013/03/21 5:37 PM, Brian Beaulieu wrote:
Same here.

On Thu, Mar 21, 2013 at 10:34 AM, Klise, Steve <klises@sutterhealth.org> wrote:
What I do is just disable the management port, and use the RLM, or SP for management.  It's an additional hop, but is your saving grace to entry if the filer panics..

-----Original Message-----
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Chris Picton
Sent: Thursday, March 21, 2013 8:31 AM
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