Trouble booting clients from ignite server......

[Snehal Patel]

Booting a client C360 (bo lan INSTALL).
Generates a Cannot find ENTRY_TEST

Failed I/O operation with ENTRY_TO
status = -3

Error Reading IPL

Any ideas.....

[magnus linner]

Are the client on the same subnet as the Ignite Server?
Are you using the internal NIC?
I don't know if you are supposed to use capital letters,
try boot lan install instead

[Carl Zabel]

Try "bo lan.ipaddress install" like this sample

bo lan.127.73.38.119 install

where the ip address is the ignite server. Also the ignite server must be on the same subnet unless you have a boot helper. Also make sure the ignite directories are listed in the /etc/inetd.conf file.

[Shahul]

Hi

I hope ur IU server and client are in same subnet.

If U have only one IU server in that subnet type like this

boot lan install

I f U have more than one IU server
boot lan.AA.AA.AA.AA install

Make sure that free IP address is available in server for assigning to client.

Best of luck

Shahul

[Bill McNAMARA_1]

on the ignite server,
exportfs -av
and ensure that the /var/opt/ignite/clients
is exported anon with read permissions

You can enter in the h/w path of the lan interface.

BO lan
or BO 8/16/4
should work also if 8/16/4 is the hw path of the nic.

Make sure you're on the same network as the ignite server.

Bill

[Michael Roberts_3]

The error message means that
firmware was unable to read ISL. This is usually because
no server replied to the udp broadcast for bootp services, and therefore there wasn't a LIF from which to access ISL.

Doing a directed boot, as someone else suggested may help if it was just a matter of the bootp querry timing out before someone responded. Also make sure that there is at least one available IP address in /etc/opt/ignite/instl_boottab on the Ignite server that you expect to answer the boot request. If that file contains only comments (and you haven't setup /etc/bootptab instead) then you can't do network boot.

[Huyen Nguyen]

I'm having the same problem, except with a D-class system. I'm using a boothelper

On the boot-helper server, I do have an entry in /etc/opt/ignite/instl_boottab file for an IP-address.

On both the boot helper and the Ignite server, i have /var/opt/ignite/clients -anon=2 (/etc/exports) along with /var/opt/ignite/recovery/archives/ -anon=2, access=

This is what's happening:

Main Menu: Enter command > boot lan. install
Interact with IPL? > n

WARN 80F9
Cannot find ENTRY_TEST.

Failed to initialize
ENTRY_INIT
Status = -7


Thanks for your help!

[Sachin Patel]

Hi Snehal
Welcome to forum,
I have found tape from make_boot_tape is the easy solution for this.

Sachin Patel

[Hooi Siew Hoong]

I used to encounter the same errors, maybe you should check the following

1) Check that there is available IP address in /etc/opt/ignite/instl_boottab
2) chmod 755 /etc/opt/ignite/instl_boottab
3) Make sure that there is entry for tftp and instl_bootd in your /etc/inetd.conf

Hope this helps.

[Sanjay_6]

Hi,

I think you should use
bo lan.A.B.C.D INSTALL
here A.B.C.D is the ip address of the Ignite Server, Make sure "INSTALL" is in Capital characters. You should be able to boot using this if your server is connected to the network thru the Lan port on the Core Adapter.

Hope this helps

Thanks

[Bill McNAMARA_1]

I think he's either fixed it or given up on it!
It was posted May 01, 2001!

Later,
Bill

Thanks not the worst, I once replied to some question over 1 year old!!