Problem Igniting RP7410 Servers

[sinhass]

When I am trying to boot RP7410 boxes from Ignite Server it shows all the depots. But whenever I choose the files to boot it fails. (my Ignite version is 6.1.44 with Dec 2004 patches and Ignite Server is RP2470) My depot and server is running perfect for all other boxes. But at the same time if I try to push the image it works. Any answer/solution ?

[Pedro Cirne]

Hi,

Is your rp7410 on the same network as your ignite server? If they are on diferent networks you'll need a server to act as a boot helper.

Enjoy :)

Pedro

[sinhass]

Yes. They are in same network.

[Pedro Cirne]

Hi,

What kind of errors do you have?

Pedro

[sinhass]

When I typed bo lan.xxx.xxx.xxx.x install
it shows all the three OS version I have. Then I choose 2 for Terget OS B.11.11 . It shows
Boot
: lan(1/0/1/0/0/4/0.0)/boot/rel_B_11.11/WINSTALL

lan(1/0/1/0/0/4/0.0)/boot/rel_B_11.11/WINSTALL:
cannot open or not executabble.

My depots are fine as I am using the same depot and same procedurefor rest of my boxes without any problem.

[Michael Roberts_3]

On your ignite server what does:
ll /opt/ignite/boot/Rel_B.11.11

show?

And

/opt/ignite/bin/auto_adm -f /opt/ignite/boot/boot_lif

[sinhass]

Hi Michael,

The outputs are as follows

ls /opt/ignite/boot/Rel_B.11.11

INSTALL, INSTALLFS, VINSTALL, VINSTALLFS->INSTALLFS, WINSTALL, WINSTALLFS->INSTALLFS, auto_conf

output from /opt/ignite/bin/auto_adm -f /opt/ignite/boot/boot_lif

timeout=0
default=1
message = choose a boot action

label = target os is B.11.00
bootcmd = boot
boot = (;0)
image=/boot/Rel_B.11.00/INSTALL

label = target os is B.11.11
bootcmd = boot
boot = (;0)
image=/boot/Rel_B.11.11/INSTALL

label = target os is B.11.23 PA
bootcmd = boot
boot = (;0)
image=/boot/Rel_B.11.23/WINSTALL


-With thanks

[Michael Roberts_3]

I assume that the lower case 'rel' is just a
typo, it should be 'Rel' in the line below for
your post:
lan(1/0/1/0/0/4/0.0)/boot/rel_B_11.11/WINSTALL

We know that there is network connectivity because the instl_bootp communication with the server was successful. We know that the kernel being requested does exist because 'ls' shows it.

We do not know if tftp to the server is working because the kernel is the first tftp attempt. You indicate that other installs from this server are working which suggests that tftp is working.

Are there any filesystem mount points below '/opt/ignite' on the ignite server? If there is then those mount points must be added to the list of 'tftp-able' directories in /etc/inetd.conf. From some other running system on your network can you tftp that kernel?

tftp IgniteServer
get /opt/ignite/boot/Rel_B.11.11/WINSTALL
quit

It is possible to get verbose log messages from the bootloader by invoking it manually from the client. When you 'boot lan.... install' indicate that you DO want to interact with IPL. When you get the 'ISL>' prompt, type:

hpux -D0x2a (;0)boot/Rel_B.11.11/WINSTALL

This will print the bootloader activity as it tries to load the kernel. It may help understand the problem.

[sinhass]

Hi Michael,

Yes, first was a typo. tftp working fine. this is the output hpux -D0x2a(;0)/boot/Rel_B.11.11/WINSTALL

error returned from boot device driver
Status returned from driver = -3

Information returned from driver

00000000 0000000 0000000 0000000
00000000 0000000 0000000 0000000

boot device error:reading utility file header


It looks like a driver issue ? I am using core IO card ( Gigabit copper) for this installation. I know my ignite server is in working condition as I loaded 2 rp2470 boxes just now which took exactly 13 minutes.

[sinhass]

Another information.

If I load OS from tape and then push the image from Ignite Server it works fine. But it can't pull the image. The difference is that when I push the image then RP7410 boots from own harddisk and gets all the related drivers. But in case of pulling the image it can't load the kernel may be because of driver ? Is it firmware related issue ? firmwares are as follows MP1-4.018, PDHC1-2.004, PDC1-17.006

[Michael Roberts_3]

According to the whitepaper (page 11):
Troubleshooting Ignite-UX Installation Booting
http://www.docs.hp.com/en/5991-0690/5991-0690.pdf

'-3' means
Cannot complete call without error â An error of unknown type prevented the call from completing correctly.

Not terribly helpful. I will try to find out more information. Looking at the firmware info on ITRC shows the most recent revs:
firmware patch PF_CKEYMAT0604
MP version 4.022
PDC version 17.009:
Firmware Release Version 6.4

[Armin Kunaschik]

Try to boot explicitly from a certain boot path e.g.
bo 0/0/8/0/0/4/0 install
and not
bo lan install

The reason is, if you don't partition the system, MP1 is the primary management processor (MP0 is disabled).
This means that lan0 is not bootable anymore.
The name of the bootable interface depends on how much lan interfaces are installed.
On my hosts. for instance, it's lan3.
But if you want, you can change this after installation. Search for ioinit/ioconfig in this forum.

Hope this help,
Armin

[Armin Kunaschik]

BTW: Please assign points!

[Bob_Vance]

I notice that when you do the boot, you get:

lan(1/0/1/0/0/4/0.0)/boot/rel_B_11.11/WINSTALL

Yet, the output from
/opt/ignite/bin/auto_adm -f /opt/ignite/boot/boot_lif
shows:

label = target os is B.11.11
bootcmd = boot
boot = (;0)
image=/boot/Rel_B.11.11/INSTALL


Why would the boot be getting WINSTALL instead of INSTALL ?

Is this a vpar'ed system?

Note that the boot retrieved the boot image name,
"/boot/rel_B_11.11/WINSTALL"
so if other boxes can tftp from the server from /boot/rel_B_11.11/, I can't see any reason why this one wouldn't.

You gave us a
ls /opt/ignite/boot/Rel_B.11.11

what about

ll /opt/ignite/boot/Rel_B.11.11


bv

[Michael Roberts_3]

The bootloader checked the bitness of the system, found it
was 64bit only and changed INSTALL to WINSTALL. This is standard
and expected behavior.

Because B.11.00 and B.11.11 support both 32bit and 64bit systems the
bootloader was enhanced to make a runtime decision to change INSTALL to
WINSTALL in the case of 64bit only (non-Vclass) hardware. It does not
translate in the other direction. If you specify WINSTALL to be loaded
on a 32bit system you will get an error.

[Bob_Vance]

(thanks, Michael
bv
)

[sinhass]

This is a cell based system with cell 1 active. cell0 is not connected al all. Also same problem for 3 RP7410 systems I have here.

[sinhass]

Loaded latest firmware PF_CKEYMAT0604 and its working now !

Thanks everybody for the help and time.