On Thu, Aug 09, 2012 at 10:54:57PM +0000, Jayanathan, David wrote:
> Hi Ray,
>
> We allow all management activity to go through the same interfaces
> that data goes through. Only on our Cluster Mode implementations do
> we use e0M for management ports, otherwise we only plug in e0M in
> order to have the RLM/SP connections on the network.
>
> Hope this helps!
>
> -David
Thanks, David.
We are running cluster mode on these systems (two controllers).
Key thing we're seeing is that NFS/CIFS file serving activity grinds to
a halt when we lose connectivity to AD/NIS servers (the communication
for which currently goes through e0M due to default gateway setup).
I presume this is expected behavior, but am a bit surprised that NFS
file serving would hang for activity not involving an NIS UID.
Presumably any NFS requests gets mapped to a UID and would require an
NIS lookup?
Anyone run into this before?
Ray
>
> -----Original Message-----
> From: toasters-bounces(a)teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Ray Van Dolson
> Sent: Thursday, August 09, 2012 2:26 PM
> To: toasters(a)teaparty.net
> Subject: e0M port as default gateway?
>
> Hello all;
>
> We have some N6240's (rebadged FAS3xxx series) on which the default
> gateway is set to an IP that routes out the e0M interface.
>
> As such, if the e0M port (wrench port) goes offline, essentially
> functionality on that controller ceases as communication with AD,
> NIS, etc. stops working.
>
> We have 10GbE ports on these devices -- we could easily configure the
> default gateways to use one of those instead, but I am unclear as to
> what best practice is here. We access management functionality
> through the IP bound on the e0M port now.
>
> How do the rest of you set things up?
>
> Ray