Ignite Recovery

[Surey]

Hello All,

I have an Ignite server and a client. Both are PA-RISC running 11.11. I made a make_net_recovery image and stored the image on the server. I am trying to restore the image onto the client by rebooting from the server.

1. I made sure that the server and client are in the same subnet.
2. Made sure the tftp entry exists in the /etc/services & /etc/inetd.conf files.
3. Made sure that the bootps is entered in /etc/services and enabled in inetd.
4. Uncommented the "instl_boots allow 0.0.0.0" in /var/adm/inetd.sec file.
5. Made sure the IP of the client is in the /etc/opt/ignite/instl_boottab file.

When I try to boot the client by typing "boot lan.10.1.16.200 install" at the PDC prompt, the client fails to boot with a message "Failed to initialize with ENTRY_INIT Status = -7"

Any idea what is causing these boot failures?

Best Regards,
Suren

[likid0]

Are your client and server on the same network?

if not you will need to configure a boot helper

[Ramesh S · Accepted solution]

Hi Surey

"Failed to initialize with ENTRY_INIT Status = -7" -- It tells that "Nonexistent device - The device address specified is a valid device address. However, it points to either a device that is not installed and/or not responding"

So Please,

* Make sure that spare IP address entry is in /var/adm/instl_boottab file.

* Make sure that "instl_boots" entry is in /etc/inetd.conf and do "inetd =-c"

* Check the current configuration by "instl_adm -t"

Thanks & Regards

Ramesh S

[Sandman!]

See if the server shows up as a bootable device in the BCH menu. Reboot the client interrupt the boot process and type "sea ipl" at the BCH prompt. This will list the remote server if it is bootable or not. It is possible that there has been a hardware failure on the recovery server.

~cheers

[Bill Hassell]

Did you create a pool of temporary IP addresses for the Ignite server? Check the Ignite log on the server.

[wittie]

Hi,

the disk you are trying to boot from, is it a local disk on the Ignite server? Can you see its actual HW path using "sea ipl" command in BCH menu on the Ignite Client? Check if the HW path is correct.