X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78EA1.45016BC7@onstor-exch02.onstor.net>; Fri, 4 May 2007 16:09:30 -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: Fri, 4 May 2007 16:09:29 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03994359@onstor-exch02.onstor.net>
In-Reply-To: <20070504155530.537a5ef5@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Zonda] Network initial config via WebUI -- system component
Thread-Index: AceOn1EO5eJEajEZThGwQvrJr3c9pwAAWT8A
From: "John VanderWerf" <john.vanderwerf@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Charissa Willard" <charissa.willard@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>,
	"Eric Crutchlow" <eric.crutchlow@onstor.com>,
	"Bill Duffy" <bill.duffy@onstor.com>

If the filer with the running DHCP server is inadvertently plugged into
a corporate network, that could cause undesirable problems.

--John

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, May 04, 2007 3:56 PM
> To: Charissa Willard
> Cc: dl-Design Review; Eric Crutchlow; Bill Duffy
> Subject: Re: [Zonda] Network initial config via WebUI --=20
> system component
>=20
> Not sure why you left off my original idea from the list. =20
> Certainly it
> should be listed before #2.  IMHO.  I'll include it again here.  Keep
> in mind that my idea, a static IP address, and a "static DHCP" address
> can all coexist happily.
>=20
> a
>=20
>=20
>=20
>                  First Install/Config Design Specification
>                  =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Problem
> -------
>=20
> Doing initial install configurations is physically awkward and
> inconvenient due to the serial port requirement.  Most laptops built
> in the last several years have no serial port.
>=20
> Furthermore, the text-based config system is aesthetically unappealing
> compared to our competitors, and also clumsy and slow.
>=20
> Overall ease-of-use rating is very low.
>=20
> Custmer impression: this thing is not slick.  These folks are not
> brilliant.
>=20
> Solution
> --------
>=20
> Network based install with Web UI configuration.
>=20
> Scope
> -----
>=20
> Web UI based install configurator already on the schedule for 3.1
> (Zonda)
>=20
> Network component scope: minimal (1 week) Zonda deliverable
>=20
> Design
> ------
>=20
> The network method has been thought to be solved by having the
> filer boot up with a default static IP address, and require=20
> the user to
> configure their laptop to conform with that.  The user would have to
> configure the laptop by hand to set the IP address, the netmask, the
> DNS server, etc.
>=20
> That design is deficient in 2 ease-of-use categories: it requires the
> user successfully configure the laptop with a fixed IP address,
> which is possibly beyond the capabilities of all potential customers;
> and it's difficult to diagnose what is wrong if the user has=20
> configured
> the laptop incorrectly.
>=20
> Instead, the filer will boot up in initial install mode with a DHCP
> server listening on a management port.  The user plugs the laptop
> ethernet into the management interface of the filer, boots the laptop,
> and fires up the web browser to http://onstor/ and Eureka!, there is
> the Web UI ready to start the initial config.
>=20
> The way this all works is that the DHCP server on the filer=20
> assigns the
> laptop an IP address, and of course the filer already has an=20
> IP address.
> The filer also serves the DNS request for 'onstor' to the=20
> laptop so the
> browser connects appropriately.
>=20
> Virtually all laptops are configured to get their IP address from DHCP
> already, so this should work with any laptop, so long as it has an
> ethernet port, which is already required.
>=20
> During the config process, the user will set the IP address for the
> management interfaces as per usual.  At the end of the config process,
> the DHCP server is disabled, the filer is rebooted, the laptop
> disconnected, and the filer connected to the switch or hub as per
> normal.  Finito.
>=20
> As a backup safety net, the static laptop IP config method would still
> work.
>=20
>=20
>=20
> On Fri, 4 May 2007 15:37:15 -0700 "Charissa Willard"
> <charissa.willard@onstor.com> wrote:
>=20
> > 1.) I discussed the initial configuration wizard with the SEs a few
> > months ago. Both Eric Crutchlow and Bill Duffy thought that using a
> > static IP address would be okay for now. However, the issue still
> > remains as to selecting an IP address that has a high probability of
> > being unique. Also, is there an issue with just going with a class C
> > private address? These are the available private IP=20
> addresses for each
> > class:
> >=20
> > =20
> >=20
> >      Class A: 10.0.0.0    - 10.255.255.255  (10/8 prefix)=20
> >=20
> >      Class B: 172.16.0.0  - 172.31.255.255  (172.16/12 prefix)
> >=20
> >      Class C: 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
> >=20
> > =20
> >=20
> > =20
> >=20
> > 2.) We could also configure a static DHCP IP address like=20
> NetApp does.
> > Below are the instructions NetApp uses to set up a static DHCP IP
> > address.
> >=20
> > =20
> >=20
> >    The NetApp QuickSetup wizard, version 1.01, has the following
> > system requirements:
> >=20
> > =20
> >=20
> > * A NetApp filer with Data ONTAP 6.1 software or later attached to a
> > network with a DHCP server=20
> >=20
> > * The CIFS license installed on the filer=20
> >=20
> > * A Windows NT 4.0 or Windows 2000 workstation within the=20
> same domain
> > or workgroup as the new filer that has access to any remote subnet
> > that contains the filer=20
> >=20
> > =20
> >=20
> >     Configure the following information into your DHCP server:
> >=20
> > =20
> >=20
> > * Filer MAC address=20
> >=20
> > * Filer IP address with an infinite lease=20
> >=20
> > * Any of the following optional information:=20
> >=20
> > O Routers=20
> >=20
> > O Default route=20
> >=20
> > O DNS domain name=20
> >=20
> > O DNS servers=20
> >=20
> > O NIS domain name=20
> >=20
> > O NIS servers=20
> >=20
> > O WINS servers=20
> >=20
> > O SMTP server=20
> >=20
> > =20
> >=20
> > 3.) Lastly, there is still the possibility of using one of Zero
> > Configuration (ZeroConf) technologies. There is no need to configure
> > anything for this, hence the name - Zero Configuration). A browser
> > plug-in is required though. Note that ZeroConf is Apple's version of
> > Microsoft's UPnP. The link-local (LL) addressing feature uses
> > addresses in the 169.254.0.0/16 range. Microsoft refers to this as
> > "Automatic Private IP Addressing". This technology is defined in RFC
> > 3927 (for IPv4).
> >=20
> > =20
> >=20
> > Bonjour is Apple's implementation of ZeroConf. Avahi is the ZeroConf
> > implementation for Linux and BSD. Avahi contains an=20
> implementation of
> > IPv4LL in the avahi-autoipd tool
> > (http://avahi.org/download/avahi-autoipd.8.xml). This tool=20
> can be used
> > stand-alone or as a plug-in for a DHCP client.
> >=20
> > =20
> >=20
> > -Charissa
> >=20
> > =20
> >=20
> > =20
> >=20
> > =20
> >=20
> > -----Original Message-----
> > From: Jonathan Goldick=20
> > Sent: Tuesday, May 01, 2007 1:37 PM
> > To: Andy Sharp; dl-designreview
> > Subject: RE: [Zonda] Network initial config via WebUI -- system
> > component
> >=20
> > =20
> >=20
> > In your backup method with a static IP, what number do we=20
> choose?  We
> > discussed this years back and could never come up with one that was
> > known to be safe.  We even went as far as talking about=20
> having a small
> > input device to key in the static IP address (not a popular idea). =20
> >=20
> > =20
> >=20
> > In general I like the new idea, we should vet some of the=20
> assumptions
> > with customers, like our newly formed customer advisory=20
> board, to see
> > if this is what they want.  Just thinking of possible=20
> issues relating
> > to plugging a laptop directly into the 10x100 BaseT.  Do we=20
> supply the
> > cables?  Must they have one of their own?
> >=20
> > =20
> >=20
> > =20
> >=20
> > =20
> >=20
> > =20
> >=20
> > -----Original Message-----
> >=20
> > From: Andy Sharp=20
> >=20
> > Sent: Tuesday, April 24, 2007 3:48 PM
> >=20
> > To: dl-designreview
> >=20
> > Subject: [Zonda] Network initial config via WebUI -- system=20
> component
> >=20
> > =20
> >=20
> > I've heard that we are going to try and have a WebUI=20
> initial (install)
> >=20
> > config thing for Zonda release, so I thought I would write up how I
> >=20
> > think we should make the system level network part of that equation
> >=20
> > happen.  This what I planned to do for Linux regardless of how the
> >=20
> > config was done, rather than use a serial port.
> >=20
> > =20
> >=20
> > I'm asking for RFC at this time.  If there are no objections or
> >=20
> > questions, I'll schedule a meeting if people think it's necessary.
> >=20
> > =20
> >=20
> > Cheers,
> >=20
> > =20
> >=20
> > a
> >=20
>=20
