boot lan on ignite UX server

[Denis Goffinet]

Hi all,

I have setup an ignite server ( B.4.1.61 ) on a superdome cell and I want to boot on lan on the ignite server from another cell.

One of the ignite server lan card has IP: 163.243.179.41 within subnet 255.255.255.192 and i have setup a temporary IP address 163.243.179.5 in /etc/opt/ignite/instl_boottab

When I try to boot ( BO lan.163.243.179.41 install ), i get the following error messages


Initializing boot Device.


Boot IO Dependent Code (IODC) Revision 2


IODC ENTRY_INIT failed. Error Status: -4

The IODC for this boot device was unable to provide text describing the failure.
IODC ENTRY_INIT[Return Messages] failed. Error Status: -2

0x0000 0000000000000000 0000000000000000 0000000000000010 0000000083fdddb0
0x0004 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0008 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x000c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0010 0000000000000005 0000000000000000 0000000000000000 0000000000000000
0x0014 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0018 0000000000000007 0000000000000000 0000000000000000 00000000f3ffa029
0x001c 00000000f0660006 0000000002202022 0000000000007580 0000000088880001

When I try to find a boot device ( SEA lan install OR SEA ALL install ), it discovers all hard disks, DDS tape drive, DVD drive, fiber channel adapter but any lan card.

Did anyone got an idea ? As I have different lan cards on the ignite server, is this possible that instl_bootd listen only on another LAN interface with a different subnet?

[Jean-Guy GROSSE]

Hello,

It's strange , i think normaly we can see lan card when we run SEA.
But the best way maybe is a boot with tape .

from a server :
Check parameter with instl_adm -d
( put line
_hp_lanadmin_args="-X 100FD" ) if you need.

run make_boot_tape on your server

After boot your client with tape and we 'll have a menu with lan choise.

[Jean-Louis Phelix]

Hi,

I would suspect an hardware or connection problem. Status -4 should mean that there is an hardware problem on the device (especially if you can't see it with SEA).

Regards.

[Ravi_8]

Hi

Could you try pushing the OS from ignite server cell to client cell.

pls post whether it's working or not?

[Denis Goffinet]

In fact, I need to boot on lan to install two virtual partitions on my Superdme cell.

Jean-Guy > I will try to do a make_boot_tape when I will have a little bit time to drive to the other computer room

Jean-Louis > As my hardware partition ( superdome cell) works fine, I didn't think an hardware failure could be part of my problem

Ravi > Pushing OS from ignite server to the hard partitions works fine but as my virtual partitions boot disk are not the one form witch I made the make_net_recovery, I think couldn t use it to install OS on my 2 virtual partitions boot disks.

Thanks all for your help
I m still looking by myself for an answer when I got a litlle bit more free time.

[Denis Goffinet]

I plugged a cable into the core IO lan card and now the error code has changed. I ve got the same eroor message except that "IODC ENTRY_INIT failed. Error Status: -4" has become "IODC ENTRY_INIT failed. Error Status: -7"

after having define an ip addresse in /etc/opt/ignite/instl_bottab

it booted on the Ignite UX, but due to errors into my NFS export, I had to reboot again to restart the installation.

I've reedited the /etc/opt/ignite/instl_bottab and removed MAC address and timestamp parts to allow the system to take the same ip again and now, lines appears into /var/adm/syslog/syslog.log

Mar 28 09:29:22 eclsh71 instl_bootd[26997]: instl_bootd: No suitable IP address found in: /etc/opt/ignite/instl_boottab

and it wont boot again. If I gave another free IP address on the same subnet, error still occurs ... so strange that it works once then nerver again

[Denis Goffinet]

and now , without changes, it works ... I do not understand anymore

[dell'avanzata_1]

sorry for my english, i'm french.

I hve the same pb.
For me, the core IO of the client and the lan interface of my server are not on the same subnet.
In fact you need have the 2 interface on the same subnet.

Didier

[Michael Duthie]

The way I know IUX to work the initial boot from the IUX server can only be done through the Core I/O lan port. After contact has been made with the server you can choose to use another Lan card.

ie K class client boots from the IUX server from the 10mb LAN port on the core IO, you are then prompted which card you wish to use and you can select an HSC 100Mb card.