LINUX Jumpstart - bpgetfile error
Manfred Durban
I am still trying to port a Jumpstartserver onto LINUX. After a lot of
hacking and testing I am getting it to boot.
BUT:
After configuring the Networkadapter el0 it freezes, telling me:
"ERROR: bpgetfile unable to access network information"
Maybe that has something to do, that we are using a 255.255.248.0 netmask???
Any hints???
-- Manfred
Darren Dunham
> BUT:
> Any hints???
Well, bpgetfile is associated with retreiving information via
bootparams.
#1 Where exactly did it die?
#2 Have you tcpdumped/snooped the network at the time of the failure to
see what the client requested?
#3 Have you run rpc.bootparamd on the server in debug mode to see what
it thought about the request?
--
Darren Dunham ddu...@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Manfred Durban
> Manfred Durban <manni....@myskoda.de> wrote:
>
>>Hi again!
>
>
>>I am still trying to port a Jumpstartserver onto LINUX. After a lot of
>>hacking and testing I am getting it to boot.
>
>
>>BUT:
>
>
>>After configuring the Networkadapter el0 it freezes, telling me:
>
>
>>"ERROR: bpgetfile unable to access network information"
>
>
>>Maybe that has something to do, that we are using a 255.255.248.0 netmask???
>
>
>>Any hints???
>
>
> Well, bpgetfile is associated with retreiving information via
> bootparams.
>
> #1 Where exactly did it die?
the last lines are:
Using RPC Bootparams for network configuration information.
Configured interface le0
ERROR: bpgetfile unable to access network information
> #2 Have you tcpdumped/snooped the network at the time of the failure to
> see what the client requested?
I sniffed it with ethereal
It basically says:
FROM: clientip
TO: 10.255.255.255
BOOTPARAMS request
Procedure: GETFILE
client: myclient.domain
File contents: root
> #3 Have you run rpc.bootparamd on the server in debug mode to see what
> it thought about the request?
>
Yes! I doesn't receive any request!
manni....@myskoda.de
Manfred Durban
>
> #1 Where exactly did it die?
the last lines are:
Using RPC Bootparams for network configuration information.
Configured interface le0
ERROR: bpgetfile unable to access network information
> #2 Have you tcpdumped/snooped the network at the time of the failure to
> see what the client requested?
I sniffed it with ethereal
It basically says:
FROM: clientip
TO: 10.255.255.255
BOOTPARAMS request
Procedure: GETFILE
client: myclient.domain
File contents: root
> #3 Have you run rpc.bootparamd on the server in debug mode to see what
> it thought about the request?
>
Yes! I doesn't receive any request!
aryzhov
Exotic masks are certainly known as Jumpstart killers.
To me, it seems like a bug in network-based bootstrapping
of Solaris: at early stages, the client gets a correct mask from
the RARP server (?), and then in the middle of something
(/sbin/rcS or sysconfig - can't remember) changes the mask
to a default one, resulting in bootparamd not seeing the client's
broadcasts.
You might want to call interactive shell from different places of
/sbin/rcS in the client's root image to see where exactly the
mask goes wrong, and whether bpgetfile broadcasts are still
regarded by the server. Combine it with snooping on the server.
Run bootparamd with -d option.
Good luck
Andrei
David Williams
> Darren Dunham wrote:
> >
> > #1 Where exactly did it die?
>
> the last lines are:
>
> Using RPC Bootparams for network configuration information.
> Configured interface le0
> ERROR: bpgetfile unable to access network information
>
> > #2 Have you tcpdumped/snooped the network at the time of the failure to
> > see what the client requested?
>
>
> I sniffed it with ethereal
>
> It basically says:
> FROM: clientip
> TO: 10.255.255.255
> BOOTPARAMS request
> Procedure: GETFILE
> client: myclient.domain
> File contents: root
>
Is the bootparams server on 10.255.255.255? Isn't that a reserved address?
Try
10.255.255.100.
Does bootparams send a route to 10.255.255.255? Does the server you are
trying to install
on have a 10.255.255.x address?
Manfred Durban
I finally got it working!
Thx to aryzhov for the hint on rcS. I did not know, that this is the
install-script!
I started some debugging in that file (added some echos and ifconfigs)
and found out, that the client tries to send a broadcast on
10.255.255.255 over the network. But this broadcast does never reach the
server because of the wrong netmask config (255.0.0.0). So I added an
"ifconfig le0 netmask 255.255.248.0 broadcast 10.10.95.255"
After that... it works!!!!
Thx to everybody!!!
-- Manfred