X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78769.4291B692@onstor-exch02.onstor.net>; Wed, 25 Apr 2007 11:40:56 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: [Zonda] Network initial config via WebUI -- system component
Date: Wed, 25 Apr 2007 11:40:55 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E036D304D@onstor-exch02.onstor.net>
In-Reply-To: <20070425113256.4cc32162@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Zonda] Network initial config via WebUI -- system component
Thread-Index: AceHaCTyi2sr7kG5TbGl8bo8YmoJqgAAJhrA
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>

Why don't we just do like NetApp does?
If DHCP is enabled on the network, the filer configures its SC port
using DHCP. Admin then uses a browser to complete configuration.
If no DHCP, you have to use the console port.

Take a look at the netapp install docs at
\\mightydog\docs\netapp_docs_64

Tim

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, April 25, 2007 11:33 AM
Cc: dl-Design Review
Subject: Re: [Zonda] Network initial config via WebUI -- system
component

Again, not simple enough to implement.  We can't always stop the
customer from doing lots of stupid things to themselves.  We could run
the dhcp server only on the second interface or other things to
ammeliorate this.

In addition to this scheme, we can also pre-configure boxes before
shipping them to customers in some cases.  This would be a good
additional capability for ops.

Cheers,

a

On Wed, 25 Apr 2007 11:10:13 -0700 "Jeseem S" <jeseem@onstor.com> wrote:

> Hi Andy,
> 	IMHO
>    The one drawback I see is if the customer plugs in the filer
> without configuring it. He will introduce a new DHCP server in the
> server farm and may potentially destablise other devices (other
> pcs/servers or phones may pick up ip from the filer's dhcp server).
> So not many administrators will accept devices which have default
> dhcp server into their network.
>=20
> The alternative solution is to have default dhcp client behaviour and
> if it fails to fallback to 169.254.0.0 subnet as windows pcs do
> currently. If we get a valid dhcp ip , then update dynamic dns (bind
> or windows dns) with a default name.
>=20
> =20
> -----Original Message-----
> From: Ian Brown=20
> Sent: Wednesday, April 25, 2007 10:57 AM
> To: Andy Sharp; Charissa Willard
> Cc: dl-Design Review
> Subject: Re: [Zonda] Network initial config via WebUI -- system
> component
>=20
> Andy, it would be even easier if you add support for boujour which =20
> will take your idea to the next level and make it so you don't have =20
> to plug your laptop's ethernet cable directly into the gateway, but =20
> will allow you to do the same thing by just plugging the gateway =20
> directly into the network as it would be normally would be, and
> would allow you to configure it that way (via boujour (i.e. dhcp)),
> and it would allow you to have any number of gateways plugged in and
> still it would work fine, and it would continue to work as an dynamic
> dns/ dhcp after it is configured.
>=20
> http://developer.apple.com/networking/bonjour/
>=20
> Ian
>=20
>=20
> On Apr 24, 2007, at 3:48 PM, Andrew Sharp wrote:
>=20
> > I've heard that we are going to try and have a WebUI initial
> > (install) config thing for Zonda release, so I thought I would
> > write up how I think we should make the system level network part
> > of that equation happen.  This what I planned to do for Linux
> > regardless of how the config was done, rather than use a serial
> > port.
> >
> > I'm asking for RFC at this time.  If there are no objections or
> > questions, I'll schedule a meeting if people think it's necessary.
> >
> > Cheers,
> >
> > a
> > <dhcpd_initial_ip.txt>
>=20
