X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CF60.C49F95CB@onstor-exch02.onstor.net>; Thu, 26 Jul 2007 00:41:32 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CF60.C49F95CB"
References: <BB375AF679D4A34E9CA8DFA650E2B04E046A5C57@onstor-exch02.onstor.net><20070725133944.73887100@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E046A5C5C@onstor-exch02.onstor.net><20070725145517.3911e089@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E046A5C60@onstor-exch02.onstor.net> <20070725160148.7b536c0b@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Bsdrl:Warning messages
Date: Thu, 26 Jul 2007 00:40:39 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E101F0D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bsdrl:Warning messages
Thread-Index: AcfPD8fS/IFq0EhwTTSU35uXf0vgrQAUN1Dt
From: "Ranga Nathan" <ranga.nathan@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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


Andy

Here is the response from the customer:

tftp boot config is the following

LABEL linux
KERNEL vmlinuz-2.6.21-2-amd64
IPAPPEND 1
APPEND root=3D/dev/nfs initrd=3Dinitrd.img-2.6.21-2-amd64-net =
nfsroot=3D10.100.0.157:/servers/debian1 =
ip=3D10.100.0.83:10.100.0.100::255.255.255.0 rw

where 10.100.0.157 - vsvr ip on bobcat that provides nfs root
10.100.0.83 - node ip itself
10.100.0.100 - dhcp and tftp server from wich we boot

dhcp line is
subnet 10.100.0.0 netmask 255.255.255.0 {
option broadcast-address 10.100.0.255;
option domain-name "dir.bg";
range 10.100.0.83 10.100.0.85;
next-server 10.100.0.100;

host debian1 {
hardware ethernet 00:30:48:8B:34:A3;
fixed-address 10.100.0.83;
# option root-path "10.100.0.157:/servers/debian1";
filename "/pxelinux.0";
}


As he indicates, 10.100.0.157 is the vsvr that he is using on the =
onstor.=20

Are you saying he needs to specify the ssc ip?

Ranga.

-----Original Message-----
From: Andy Sharp
Sent: Wed 7/25/2007 4:01 PM
To: Ranga Nathan
Subject: Re: Bsdrl:Warning messages
=20
On Wed, 25 Jul 2007 15:06:21 -0700 "Ranga Nathan"
<ranga.nathan@onstor.com> wrote:

> If you are referring to the IP addresses in the "hangup_process.jpg"
> file,  here are the assignments:
>=20
> 10.100.0.53 is nfs server 64 bit Debian Etch
> 10.100.0.83 - is node ip (64 bit Debian etch)
> 10.100.0.100 - is ftfp and bootp server (32 bit debian Etch)

Notice you didn't mention the gateway address.

That is what needs to be specified, and isn't.

> But the packet trace is captured when trying to boot from the gateway
> with IP 10.100.0.157 (the "servers" vsvr). Of course, it would help if
> we get the actual command being used to do the boot.

I can see the boot command in the jpeg, the gateway address is clearly
not specified.

>=20
> Ranga Nathan=20
> Customer Support 		Direct: 408 963 2493
> ONStor US Support:=20
> Phone: 1-866-726-3453	E-mail: support@ONStor.com
> ___________________________________________________
> ONStor, Inc. | 254 E Hacienda Ave | Campbell, CA 95008=20
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, July 25, 2007 2:55 PM
> To: Ranga Nathan
> Subject: Re: Bsdrl:Warning messages
>=20
> I'm not completely getting everything from the screenshots, but I can
> see that they are not specifying a gateway but are specifying and
> address that is not on their subnet, so they really should be
> specifying a gateway.  That will probably fix the problem.
>=20
> Cheers,
>=20
> a
>=20
>=20
> On Wed, 25 Jul 2007 13:48:09 -0700 "Ranga Nathan"
> <ranga.nathan@onstor.com> wrote:
>=20
> > I have asked for it. Meanwhile, here are links to screen captures
> > for a normal and hung boot, along with a packet trace during the
> > boot failure:
> >=20
> > =
http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5454/
> > no
> > rmal_boot.JPG
> > =
http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5454/
> > ha
> > ngup_process.jpg
> >=20
> > /n/dw/bycase/case0004001-case0006000/case5454/en3.cap
> > =20
> >=20
> >=20
> > Ranga Nathan=20
> > Customer Support 		Direct: 408 963 2493
> > ONStor US Support:=20
> > Phone: 1-866-726-3453	E-mail: support@ONStor.com
> > ___________________________________________________
> > ONStor, Inc. | 254 E Hacienda Ave | Campbell, CA 95008
> >=20
> >=20
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Wednesday, July 25, 2007 1:40 PM
> > To: Ranga Nathan
> > Subject: Re: Bsdrl:Warning messages
> >=20
> > Can you get the boot command they are using to boot the linux
> > clients? Possibly the problem can be fixed there.
> >=20
> >=20
> > On Wed, 25 Jul 2007 13:29:16 -0700 "Ranga Nathan"
> > <ranga.nathan@onstor.com> wrote:
> >=20
> > >=20
> > > Customer is unable to remote boot his linux clients off of the=20
> > > onstor.
> >=20
> > > I see the following elog message:
> > >=20
> > > Jul 18 15:31:56 dir-nfs-2 : 1:0:bsdrl:WARNING: 79: udp_connect:
> > > 988: in_pcbroute failed for local ip=3D 10.100.0.157, local port =
=3D
> > > 111, remo te ip =3D 194.145.63.83, remote port =3D 32768, error =
=3D 65
> > > Jul 18 15:31:56
> >=20
> > > dir-nfs-2 : 1:0:bsdrl:WARNING: 80: udp_input: 546:
> > > udp_connect failed for 194.145.63.83, error =3D 65 Jul 18 15:31:56
> > > dir-nfs-2 : 1:0:bsdrl:WARNING: 81: arp for ip
> > > 194.145.63.83 not found remove sock
> > >=20
> > > The vsvr that is being used for the boots is 10.100.0.157.
> > >=20
> > > Any idea if these messages could cause the boots to fail?
> > >=20
> > > Ranga Nathan=20
> > > Customer Support 		Direct: 408 963 2493
> > >=20
> > > ONStor US Support:=20
> > > Phone: 1-866-726-3453            E-mail: support@ONStor.com
> > >=20
> > >  <<Picture (Metafile)>>  254 E Hacienda Ave, Campbell, CA 95008
> > >=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Bsdrl:Warning messages</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>Andy<BR>
<BR>
Here is the response from the customer:<BR>
<BR>
tftp boot config is the following<BR>
<BR>
LABEL linux<BR>
KERNEL vmlinuz-2.6.21-2-amd64<BR>
IPAPPEND 1<BR>
APPEND root=3D/dev/nfs initrd=3Dinitrd.img-2.6.21-2-amd64-net =
nfsroot=3D10.100.0.157:/servers/debian1 =
ip=3D10.100.0.83:10.100.0.100::255.255.255.0 rw<BR>
<BR>
where 10.100.0.157 - vsvr ip on bobcat that provides nfs root<BR>
10.100.0.83 - node ip itself<BR>
10.100.0.100 - dhcp and tftp server from wich we boot<BR>
<BR>
dhcp line is<BR>
subnet 10.100.0.0 netmask 255.255.255.0 {<BR>
option broadcast-address 10.100.0.255;<BR>
option domain-name &quot;dir.bg&quot;;<BR>
range 10.100.0.83 10.100.0.85;<BR>
next-server 10.100.0.100;<BR>
<BR>
host debian1 {<BR>
hardware ethernet 00:30:48:8B:34:A3;<BR>
fixed-address 10.100.0.83;<BR>
# option root-path &quot;10.100.0.157:/servers/debian1&quot;;<BR>
filename &quot;/pxelinux.0&quot;;<BR>
}<BR>
<BR>
<BR>
As he indicates, 10.100.0.157 is the vsvr that he is using on the =
onstor.<BR>
<BR>
Are you saying he needs to specify the ssc ip?<BR>
<BR>
Ranga.<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 7/25/2007 4:01 PM<BR>
To: Ranga Nathan<BR>
Subject: Re: Bsdrl:Warning messages<BR>
<BR>
On Wed, 25 Jul 2007 15:06:21 -0700 &quot;Ranga Nathan&quot;<BR>
&lt;ranga.nathan@onstor.com&gt; wrote:<BR>
<BR>
&gt; If you are referring to the IP addresses in the =
&quot;hangup_process.jpg&quot;<BR>
&gt; file,&nbsp; here are the assignments:<BR>
&gt;<BR>
&gt; 10.100.0.53 is nfs server 64 bit Debian Etch<BR>
&gt; 10.100.0.83 - is node ip (64 bit Debian etch)<BR>
&gt; 10.100.0.100 - is ftfp and bootp server (32 bit debian Etch)<BR>
<BR>
Notice you didn't mention the gateway address.<BR>
<BR>
That is what needs to be specified, and isn't.<BR>
<BR>
&gt; But the packet trace is captured when trying to boot from the =
gateway<BR>
&gt; with IP 10.100.0.157 (the &quot;servers&quot; vsvr). Of course, it =
would help if<BR>
&gt; we get the actual command being used to do the boot.<BR>
<BR>
I can see the boot command in the jpeg, the gateway address is =
clearly<BR>
not specified.<BR>
<BR>
&gt;<BR>
&gt; Ranga Nathan<BR>
&gt; Customer Support &nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Direct: 408 963 2493<BR>
&gt; ONStor US Support:<BR>
&gt; Phone: 1-866-726-3453 E-mail: support@ONStor.com<BR>
&gt; ___________________________________________________<BR>
&gt; ONStor, Inc. | 254 E Hacienda Ave | Campbell, CA 95008<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Wednesday, July 25, 2007 2:55 PM<BR>
&gt; To: Ranga Nathan<BR>
&gt; Subject: Re: Bsdrl:Warning messages<BR>
&gt;<BR>
&gt; I'm not completely getting everything from the screenshots, but I =
can<BR>
&gt; see that they are not specifying a gateway but are specifying =
and<BR>
&gt; address that is not on their subnet, so they really should be<BR>
&gt; specifying a gateway.&nbsp; That will probably fix the problem.<BR>
&gt;<BR>
&gt; Cheers,<BR>
&gt;<BR>
&gt; a<BR>
&gt;<BR>
&gt;<BR>
&gt; On Wed, 25 Jul 2007 13:48:09 -0700 &quot;Ranga Nathan&quot;<BR>
&gt; &lt;ranga.nathan@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt; &gt; I have asked for it. Meanwhile, here are links to screen =
captures<BR>
&gt; &gt; for a normal and hung boot, along with a packet trace during =
the<BR>
&gt; &gt; boot failure:<BR>
&gt; &gt;<BR>
&gt; &gt; <A =
HREF=3D"http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case=
5454/">http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5=
454/</A><BR>
&gt; &gt; no<BR>
&gt; &gt; rmal_boot.JPG<BR>
&gt; &gt; <A =
HREF=3D"http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case=
5454/">http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5=
454/</A><BR>
&gt; &gt; ha<BR>
&gt; &gt; ngup_process.jpg<BR>
&gt; &gt;<BR>
&gt; &gt; /n/dw/bycase/case0004001-case0006000/case5454/en3.cap<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Ranga Nathan<BR>
&gt; &gt; Customer Support &nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Direct: 408 963 2493<BR>
&gt; &gt; ONStor US Support:<BR>
&gt; &gt; Phone: 1-866-726-3453&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
E-mail: support@ONStor.com<BR>
&gt; &gt; ___________________________________________________<BR>
&gt; &gt; ONStor, Inc. | 254 E Hacienda Ave | Campbell, CA 95008<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; -----Original Message-----<BR>
&gt; &gt; From: Andy Sharp<BR>
&gt; &gt; Sent: Wednesday, July 25, 2007 1:40 PM<BR>
&gt; &gt; To: Ranga Nathan<BR>
&gt; &gt; Subject: Re: Bsdrl:Warning messages<BR>
&gt; &gt;<BR>
&gt; &gt; Can you get the boot command they are using to boot the =
linux<BR>
&gt; &gt; clients? Possibly the problem can be fixed there.<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; On Wed, 25 Jul 2007 13:29:16 -0700 &quot;Ranga =
Nathan&quot;<BR>
&gt; &gt; &lt;ranga.nathan@onstor.com&gt; wrote:<BR>
&gt; &gt;<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Customer is unable to remote boot his linux clients off =
of the<BR>
&gt; &gt; &gt; onstor.<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; I see the following elog message:<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Jul 18 15:31:56 dir-nfs-2 : 1:0:bsdrl:WARNING: 79: =
udp_connect:<BR>
&gt; &gt; &gt; 988: in_pcbroute failed for local ip=3D 10.100.0.157, =
local port =3D<BR>
&gt; &gt; &gt; 111, remo te ip =3D 194.145.63.83, remote port =3D 32768, =
error =3D 65<BR>
&gt; &gt; &gt; Jul 18 15:31:56<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; dir-nfs-2 : 1:0:bsdrl:WARNING: 80: udp_input: 546:<BR>
&gt; &gt; &gt; udp_connect failed for 194.145.63.83, error =3D 65 Jul 18 =
15:31:56<BR>
&gt; &gt; &gt; dir-nfs-2 : 1:0:bsdrl:WARNING: 81: arp for ip<BR>
&gt; &gt; &gt; 194.145.63.83 not found remove sock<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; The vsvr that is being used for the boots is =
10.100.0.157.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Any idea if these messages could cause the boots to =
fail?<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Ranga Nathan<BR>
&gt; &gt; &gt; Customer Support&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Direct: 408 963 2493<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; ONStor US Support:<BR>
&gt; &gt; &gt; Phone: =
1-866-726-3453&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; E-mail: support@ONStor.com<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt;&nbsp; &lt;&lt;Picture (Metafile)&gt;&gt;&nbsp; 254 E =
Hacienda Ave, Campbell, CA 95008<BR>
&gt; &gt; &gt;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7CF60.C49F95CB--
