Trying to Ignite from Client Console

[KPS]

Hi,

I have a server with an HP-UX 11.11 OS image on it as an Ignite Client and i'm trying to re-ignite it with a different image from the Client Console. When I'm at the Boot Menu I type in:

boot lan.xxx.xxx.xxx.xxx install
(IP of Ignite Server)

(This should allow me to boot and direct me to my Ignite Server over my Core I/O LAN Port)

I've tried this and this is not working; it just brings me back to the BCH and Boot Menu.

I then type in:

search lan install

The above me tells me "No Devices were found".

I'm curious why this does not see the core i/o interface on my client server to boot off of an image that I define on my Ignite Server and I'm out of ideas...

[Steven E. Protter]

Joy of ignite.

You can only boot off the internal NIC card. AS in the built in nic, not any add in cards.

If you don't have a hub or switch connecting them, you will need to connect them and have the ip addresses activated either in /etc/rc.config.d/netconf or with ifconfig commands.

Are you trying to boot off the internal NIC.

next idea is ignite boot config.

inst_adm -D

Let us see what we are dealing with.

Note the boot must be off the built in NIC, but the transfer can be over your fast add in cards.

SEP

[KPS]

Hi,

I'm attempting to reboot off of lan0 (Which is the Internal Nic or Core I/O)

I'm not familiar with inst_adm -D.

Can you give me some more insight to how and where I should run that and what it might tell me?

Also any other ideas?

Thanks,
Ken

[Florian Heigl (new acc)]

inst_adm -D must be run on the Ignite server, from Your messages I'd guess that bootpd or tftpd is not properly running.

[Bharat Katkar]

Hi Ken,
There are certain things to make sure on Ignite Server before you start booting through NIC card of client.

After your Ignite-UX server has been set up, ensure that bootpd is enabled in /etc/inetd.conf :

bootps dgram udp wait root /usr/lbin/bootpd bootpd

Restart the inetd daemon:
/usr/sbin/inetd -c

You will need to add your clientâ s entries to /etc/bootptab on the Ignite-UX server.
Get the MAC address of the client Machine that can be found from the firmwareâ s user interface when adding a boot option at clients machine.

hostname1:\
ht=ethernet:\
ha=:\
ip=:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
sm=

In addition to this you need to set Ignite Server IP address and Gateway address using instl_adm command:
# /opt/ignite/bin/instl_adm â t
# /opt/ignite/bin/instl_adm -g
# /opt/ignite/bin/instl_adm -d { Displays your Instl_adm settings }
# /opt/ignite/bin/instl_adm -T { Checks your Config files }

Hope that helps.

[Bharat Katkar]

Ken,
Any updates further...!!
Regards,

[John Payne_2]

Ken,

One other thing to remember:

Unless you have a 'boot helper' machine, your client and server need to be on the same subnet. Other than that, you want to look at your Ignite server as others have indicated.

Hope it helps

John

[KPS]

My Ignite Server and Ignite Client are both on the same Subnet, so a Boot Helper shouldn't be needed.

I've gotten past the point where I couldn't boot over my Core IO Interfaace on my client to the Ignite Server. (This was due to bootpd not being open on Client)

Now, I successfully boot and talk to the Ignite Server and pick the Golden Image I want to install from. I get this all setup to install and when I proceed to install, it comes right back instantaneously and tells me:

"An error has occured and the installation may not proceed until these errors are resolved"

[KPS]

Thanks everyone,

My troubles have been resolved by clearing up some inconsistencies in my INDEX file on my Ignite Server. I'm now installing my Golden Image that I needed to.

Thanks again,

-Ken