boot lan.0060b0-f9fc69

[Donny Jekels]

I am trying to boot a K-class 570 box from our Ignite-UX server.

On the server I am running both rbootd & bootp.
and they are on the same subnet.

the box fails to find the boot device.
and retries.

Also, if I do a search for bootable devices. I see the lan interface comes up as lan.0

I also tried

boot lan.0.0060b0-f9fc69

& of course

boot lan.0060b0-f9fc69

Is there anything that I have missed?

On the I-UX Server this is running:

root 2561 1 0 09:03:16 ? 0:00 /usr/sbin/rbootd /usr/sbin/rbootd
root 2769 1267 0 Jun 18 ? 0:00 bootpd

[John Poff]

Hi Donny,

I think you need to do:

boot lan. install

I've never tried it with a MAC address before.

JP


P.S. I just spent the last three days playing with this stuff.

[Donny Jekels]

boot lan. install

is for newer systems

older ones including K-class must use

boot lan.

without install.

[S.K. Chan]

In addition to ...
boot lan.0060b0-f9fc69 install
you can also try ..
boot lan. install
which might work if you got the later version of bootrom on your K.

[Sridhar Bhaskarla]

Hi Donny,

Did you try a "search lan install" before actually booting?. It should show up your ignite server in the list.

Look at your 'instl_adm -T" output and '/etc/opt/ignite/instl_boottab to see if you listed some free IPs in there.

-Sri

[Steven E. Protter]

Every once in a while those processes on the server get hung up for some reason.

Sometimes stopping and starting them will do the trick.

As a reference i will chime in saying I've only booted using numeric IP addresses.

SEP

[Con O'Kelly]

Hi Donny

You need to ensure some free IP addresses have been defined on your Ignite server. This can be done in Server Configuration tab from the Ignite GUI.

A temporary IP Address is assigned by the Ignite Server to the client when it initially boots. If no free IP addresses are available (or IP addresses are for the wrong subnet) the client boot will fail. This IP address must not be in use by any other device on the network. Also obviously ensure the IP address is correct for the subnet that your Ignite server is on. I have run into problems before when IP addresses have been defined but they were for the wrong subnet (especially when non standard subnet masks are in use.)

Cheers
Con

[Donny Jekels]

switched gears to a L-class box.

boot lan. install works perfectly.

I am going to upgrade the boot rom this Monday. Will keep the thread updated.

Donny

[Bill Hassell]

Note that booting from the LAN requires the server and the client be on the same subnet. Since there is no way to configure a subnet mask and router, this is a requiremnent for Ignite/UX on a network.

[Buddy Mohmedi]

There were no errors provided in the details logged.

Did you check syslog.log for errors?

It might be worth adding -d3 to the end of the instl_boots line in /etc/inetd.conf to enable debugging.


Hope it helps.


Cheers!