X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7D072.8442ECAD@onstor-exch02.onstor.net>; Fri, 27 Jul 2007 09:21:06 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Bsdrl:Warning messages
Date: Fri, 27 Jul 2007 09:21:06 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E046A5C67@onstor-exch02.onstor.net>
In-Reply-To: <20070726100017.65358f53@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bsdrl:Warning messages
Thread-Index: AcfPpnIje8qTqm2xQBK2aNBpHB6OZwAy7M9g
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><BB375AF679D4A34E9CA8DFA650E2B04E101F0D@onstor-exch02.onstor.net> <20070726100017.65358f53@ripper.onstor.net>
From: "Ranga Nathan" <ranga.nathan@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy

Didn't see this reply from you. When you say gateway/default router, I
assume you mean a gateway on their network? Apparently they do not have
a default gateway on this network and this syntax works for them when
they use a linux server (not onstor).


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


-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, July 26, 2007 10:00 AM
To: Ranga Nathan
Subject: Re: Bsdrl:Warning messages

On Thu, 26 Jul 2007 01:40:39 -0700 "Ranga Nathan"
<ranga.nathan@onstor.com> wrote:

>=20
> Andy
>=20
> Here is the response from the customer:
>=20
> tftp boot config is the following
>=20
> 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
                             ^^
they need to supply the gateway/default router address.
it goes in between these two colons

> 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
>=20
> dhcp line is
> subnet 10.100.0.0 netmask 255.255.255.0 { option broadcast-address=20
> 10.100.0.255; option domain-name "dir.bg"; range 10.100.0.83=20
> 10.100.0.85; next-server 10.100.0.100;
>=20
> 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=20
> "/pxelinux.0"; }
>=20
>=20
> As he indicates, 10.100.0.157 is the vsvr that he is using on the=20
> onstor.
>=20
> Are you saying he needs to specify the ssc ip?
>=20
> Ranga.
>=20
> -----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:
>=20
> > 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)
>=20
> Notice you didn't mention the gateway address.
>=20
> That is what needs to be specified, and isn't.
>=20
> > But the packet trace is captured when trying to boot from the=20
> > gateway with IP 10.100.0.157 (the "servers" vsvr). Of course, it=20
> > would help if we get the actual command being used to do the boot.
>=20
> I can see the boot command in the jpeg, the gateway address is clearly

> not specified.
>=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 2:55 PM
> > To: Ranga Nathan
> > Subject: Re: Bsdrl:Warning messages
> >=20
> > I'm not completely getting everything from the screenshots, but I=20
> > can see that they are not specifying a gateway but are specifying=20
> > and address that is not on their subnet, so they really should be=20
> > 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=20
> > > for a normal and hung boot, along with a packet trace during the=20
> > > boot failure:
> > >=20
> > > http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5
> > > 454/
> > > no
> > > rmal_boot.JPG
> > > http://cs-web.onstor.net/data/bycase/case0004001-case0006000/case5
> > > 454/
> > > 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=20
> > > 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
>=20
