X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8635C.7E070195@onstor-exch02.onstor.net>; Wed, 30 Jan 2008 09:23:48 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8635C.7E070195"
References: <BB375AF679D4A34E9CA8DFA650E2B04E07BBFDEA@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04EC247A4@onstor-exch02.onstor.net> <20080129105849.40f579a7@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Need a help on dhcp issue
Date: Wed, 30 Jan 2008 09:20:49 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04EC247AC@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Need a help on dhcp issue
Thread-Index: AchiqPwqR3cmMsY2QMq7M6rovUGQZgAsxdTg
From: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8635C.7E070195
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Andy,
=20
I have one more question. I could find the dhclient configuration file =
in filer at /etc/dhcp3/dhclient.conf. But I could not trace it in the =
//depot/dev/linux/ path.I believe these files are extracted to release =
directory from=20
=20
//depot/dev/linux//Pkgs/binary/Deb/dhcp3-client_3.0.4-13_mipsel.deb
=20
during build process.
=20
What should I do if I have to edit the configuration files before =
extraction?
=20
-Sripal.

________________________________

From: Andy Sharp
Sent: Wed 1/30/2008 12:28 AM
To: Sripal Surendiran (HCL)
Cc: Maxim Kozlovsky
Subject: Re: Need a help on dhcp issue



Howdy,

I'll look into it.  It might be fixable in the kernel (by making the
hardware address type something "known" or by configuring or invoking
dh-client a certain way.

The problem is mostly that the dh-client doesn't seem to want to mind
it's own business when it comes to interfaces that we want it ignore.


On Tue, 29 Jan 2008 06:38:39 -0800 "Sripal Surendiran (HCL)"
<sripal.surendiran@onstor.com> wrote:

> Hi Andy,
>=20
> I am working on Cougar FTI and facing some issue with running DHCP
> client in the Bobcat linux filer ( I don't have cougar system :-( ).
> Following error message got displayed, when DHCP client tried to
> contact the DHCP server.
> webui8:~# /etc/init.d/networking start
> Configuring network interfaces...Internet Systems Consortium DHCP
> Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> bp0: unknown hardware address type 65535
>=20
> Filer hangs after the above message. Even my console is not
> responding. I have to hard reboot the filer.
> Details of my configuration file
>=20
> 1. /etc/network/interfaces
>=20
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet dhcp
> #  address 10.25.0.8
> #  netmask 255.255.0.0
> #  gateway 10.25.0.1
>
> 2. /etc/dhcp3/dhclient.conf
>
> timeout 60;
> retry 60;
> reboot 10;
> select-timeout 5;
> initial-interval 2;
>
>
> interface "eth0" {
>         send dhcp-client-identifier 0:7:34:1:f0:0;
>         send dhcp-lease-time  -1;
>         request subnet-mask, routers,
> domain-name,domain-name-servers, host-name, ntp-servers; require
> host-name; script "/sbin/dhclient-script";
> }
>
> alias {
>         interface "eth0";
>         fixed-address 172.18.250.250;
>         option subnet-mask 255.255.0.0;
> }
>
> Whether I am missing something? Any help on this regards will be
> grateful.
>
> Thanks in advance,
> Sripal.
>
> ________________________________
>
> From: Brian DeForest
> Sent: Fri 1/18/2008 6:58 AM
> To: Sudharsan Srinivasan-TLS,Chennai; Sripal Surendiran (HCL)
> Cc: Charissa Willard
> Subject: Cougar FTI
>
>
>
> There have been some discussions about who should own the Cougar FTI
> port/development.  Since this was implemented in R98, after the
> Cougar porting was started, it wasn't really clear whether the
> offshore team or Cougar team should own this.  After some
> discussions, it was decided that the offshore team would be the right
> team to implement this given your familiarity with the R98 work.=20
>
> Currently the Cougar FTI is based on the "old" pre-R98 FTI so the
> porting/development of Cougar (R98-based) FTI is not gating any
> developers.  Also this is not a requirement for the upcoming Cougar
> beta in February.=20
>
> We'll need a schedule for the work.  Tim requested this by Monday if
> possible, however let me know if that's feasible, or an alternative
> date for a schedule.  Andy Sharp is the primary Linux technical
> contact, and feel free to consult with Charissa (or I) as needed also.
>
> Thanks.
> Brian
>



------_=_NextPart_001_01C8635C.7E070195
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: Need a help on dhcp issue</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText71203 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Andy,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV>I have one more question. I could find the dhclient configuration =
file&nbsp;in filer&nbsp;at /etc/dhcp3/dhclient.conf. But I could not =
trace it in the //depot/dev/linux/ path.I believe these files are =
extracted to release directory from </DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV>//depot/dev/linux//Pkgs/binary/Deb/dhcp3-client_3.0.4-13_mipsel.deb<=
/DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV>during build process.</DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV>What should I do if I have to edit the configuration files before =
extraction?</DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV>-Sripal.</DIV></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Wed =
1/30/2008 12:28 AM<BR><B>To:</B> Sripal Surendiran (HCL)<BR><B>Cc:</B> =
Maxim Kozlovsky<BR><B>Subject:</B> Re: Need a help on dhcp =
issue<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Howdy,<BR><BR>I'll look into it.&nbsp; It might be =
fixable in the kernel (by making the<BR>hardware address type something =
"known" or by configuring or invoking<BR>dh-client a certain =
way.<BR><BR>The problem is mostly that the dh-client doesn't seem to =
want to mind<BR>it's own business when it comes to interfaces that we =
want it ignore.<BR><BR><BR>On Tue, 29 Jan 2008 06:38:39 -0800 "Sripal =
Surendiran (HCL)"<BR>&lt;sripal.surendiran@onstor.com&gt; =
wrote:<BR><BR>&gt; Hi Andy,<BR>&gt;&nbsp;<BR>&gt; I am working on Cougar =
FTI and facing some issue with running DHCP<BR>&gt; client in the Bobcat =
linux filer ( I don't have cougar system :-( ).<BR>&gt; Following error =
message got displayed, when DHCP client tried to<BR>&gt; contact the =
DHCP server.<BR>&gt; webui8:~# /etc/init.d/networking start<BR>&gt; =
Configuring network interfaces...Internet Systems Consortium =
DHCP<BR>&gt; Client V3.0.4 Copyright 2004-2006 Internet Systems =
Consortium.<BR>&gt; All rights reserved.<BR>&gt; For info, please visit =
<A =
href=3D"http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</A><BR>&=
gt; bp0: unknown hardware address type 65535<BR>&gt;&nbsp;<BR>&gt; Filer =
hangs after the above message. Even my console is not<BR>&gt; =
responding. I have to hard reboot the filer.<BR>&gt; Details of my =
configuration file<BR>&gt;&nbsp;<BR>&gt; 1. =
/etc/network/interfaces<BR>&gt;&nbsp;<BR>&gt; # The loopback network =
interface<BR>&gt; auto lo<BR>&gt; iface lo inet loopback<BR>&gt;<BR>&gt; =
# The primary network interface<BR>&gt; auto eth0<BR>&gt; iface eth0 =
inet dhcp<BR>&gt; #&nbsp; address 10.25.0.8<BR>&gt; #&nbsp; netmask =
255.255.0.0<BR>&gt; #&nbsp; gateway 10.25.0.1<BR>&gt;<BR>&gt; 2. =
/etc/dhcp3/dhclient.conf<BR>&gt;<BR>&gt; timeout 60;<BR>&gt; retry =
60;<BR>&gt; reboot 10;<BR>&gt; select-timeout 5;<BR>&gt; =
initial-interval 2;<BR>&gt;<BR>&gt;<BR>&gt; interface "eth0" =
{<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
dhcp-client-identifier =
0:7:34:1:f0:0;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
send dhcp-lease-time&nbsp; =
-1;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; request =
subnet-mask, routers,<BR>&gt; domain-name,domain-name-servers, =
host-name, ntp-servers; require<BR>&gt; host-name; script =
"/sbin/dhclient-script";<BR>&gt; }<BR>&gt;<BR>&gt; alias =
{<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface =
"eth0";<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
fixed-address =
172.18.250.250;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
option subnet-mask 255.255.0.0;<BR>&gt; }<BR>&gt;<BR>&gt; Whether I am =
missing something? Any help on this regards will be<BR>&gt; =
grateful.<BR>&gt;<BR>&gt; Thanks in advance,<BR>&gt; =
Sripal.<BR>&gt;<BR>&gt; ________________________________<BR>&gt;<BR>&gt; =
From: Brian DeForest<BR>&gt; Sent: Fri 1/18/2008 6:58 AM<BR>&gt; To: =
Sudharsan Srinivasan-TLS,Chennai; Sripal Surendiran (HCL)<BR>&gt; Cc: =
Charissa Willard<BR>&gt; Subject: Cougar =
FTI<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; There have been some discussions =
about who should own the Cougar FTI<BR>&gt; port/development.&nbsp; =
Since this was implemented in R98, after the<BR>&gt; Cougar porting was =
started, it wasn't really clear whether the<BR>&gt; offshore team or =
Cougar team should own this.&nbsp; After some<BR>&gt; discussions, it =
was decided that the offshore team would be the right<BR>&gt; team to =
implement this given your familiarity with the R98 =
work.&nbsp;<BR>&gt;<BR>&gt; Currently the Cougar FTI is based on the =
"old" pre-R98 FTI so the<BR>&gt; porting/development of Cougar =
(R98-based) FTI is not gating any<BR>&gt; developers.&nbsp; Also this is =
not a requirement for the upcoming Cougar<BR>&gt; beta in =
February.&nbsp;<BR>&gt;<BR>&gt; We'll need a schedule for the =
work.&nbsp; Tim requested this by Monday if<BR>&gt; possible, however =
let me know if that's feasible, or an alternative<BR>&gt; date for a =
schedule.&nbsp; Andy Sharp is the primary Linux technical<BR>&gt; =
contact, and feel free to consult with Charissa (or I) as needed =
also.<BR>&gt;<BR>&gt; Thanks.<BR>&gt; =
Brian<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C8635C.7E070195--
