Don't the 3000 series boxes have an inbuilt RLM port for console management over IP?


From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Linux Admin
Sent: Thursday, 4 January 2007 10:25 AM
To: Blake Golliher; NetApp Toasters List
Subject: Re: 3020 Cluster: which one is management interface

so i can do

level 1vif : multi1 + mutli2
level 2 vif:  single1 (out of 2 multi)
vlans: 2 vlans on top of single 1

in cluster config?
Have this been done?

On 1/3/07, Blake Golliher <thelastman@gmail.com> wrote:
There is no default management interface on a 3020 or a 3050 (or a
3070 for that matter).  There are 4 interfaces that come with the
system.  You can use them in the way you had described in your first
post, then use vlan tagging, to segment your management traffic from
your production traffic.  So your production still gets 4 interfaces,
and your management interface is on a separate vlan from your
production network.

This is a different configuration then you were previously using, but
that's the nature of this device.  Alternately, you could purchase
another nic from Netapp for management use.  I'm sure you could
negotiate a lower price then usual, since it's only going to be used
as a management interface.

-Blake

On 1/3/07, Linux Admin <sysadmin.linux@gmail.com> wrote:
> Blake,
> Thanks again.
> so is there a "default" management interface out the 4?
> i was going to use 2 nicks to 1 switch (active) and 2 nicks to 2 switch
> (passive)
> 3 nics, odd number to work with vifs is very strange.
> Now some people say they vif all 4 into one vif and use that for mgmt and
> data.
> how is it possible?
> i am still confused
>
>
>
> On 1/3/07, Blake Golliher <thelastman@gmail.com> wrote:
> > I meant using vlans to separate your management traffic from your
> > production data traffic.  Most filers before the 3000 had one on board
> > interface.  Even on the 980 it had a 100mb interface.  With the 3000's
> > and the 6000's there are now 4 or 6 on board 1g interfaces that can be
> > used for either management or data throughput.
> >
> > If you workload is dispersed enough that you need 4 full 1g interfaces
> > for just production traffic, or your security need to be segmented
> > that management traffic can't touch production traffic, then perhaps a
> > separate gig card is required.
> >
> > -Blake
> >
> > On 1/3/07, Linux Admin < sysadmin.linux@gmail.com> wrote:
> > > Blake,
> > > Thanks! So which one is managment then?
> > > I see dedicated managemnet iterface on all filers but 3020.
> > > Or do you manage over the data IP?
> > > Thanks
> > >
> > >
> > > On 1/3/07, Blake Golliher <thelastman@gmail.com > wrote:
> > > > You can use vlan tagging on it that final multi mode trunk vlan.
> > > > There should be 3 slots available for expansion cards if you need a
> > > > dedicated interface for managment.  Depending on how much storage is
> > > > attached to this config, you should be able to use one of those slots
> > > > for a network card.
> > > >
> > > > -Blake
> > > >
> > > > On 1/3/07, Linux Admin < sysadmin.linux@gmail.com > wrote:
> > > > > Folks,
> > > > > Not familiar with 3020 series at all. I see 4 nics (e0a, e0b,
> e0c,e0d)
> > > on
> > > > > the back of each head.
> > > > > Does it mean I have sacrifice one to be management and only 3 are
> > > available
> > > > > as data?
> > > > > Have NetApp change things? Or can I used all 4 in single/multi vips?
> > > > > I was going to do e0a and e0c in single A, e0b and and e0d in single
> B,
> > > and
> > > > > Multi VIP C on top of Sinlge A and Single B.
> > > > > Not sure what to do about management.
> > > > > Thanks for help
> > > > >
> > > >
> > >
> > >
> >
>
>

 

 

"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."