Ignite Recovery

 
SOLVED
Go to solution
Surey
Occasional Advisor

Ignite Recovery

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
Knowledge is power!
4 REPLIES 4
Sandy Chen
Honored Contributor

Re: Ignite Recovery

Hi Suren,

What is your machine type and the firmware level. I have experienced this one, with the same error message on rp7400 and it was a firmware related issue.

Regards,
Sandy
I never think of the future. It comes soon enough.
LucianoCarvalho
Respected Contributor

Re: Ignite Recovery

Hi,

I think it's a good idea to check /etc/opt/ignite/instl_boottab file. You have to have configured a line something like this:

192.168.10.1:0x00306E1CD330::reserve

Best Regards.


LucianoCarvalho
Respected Contributor
Solution

Re: Ignite Recovery

You can also try to boot using bootptab.
The config would be as follow:

ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48


rp7410_0:\
tc=ignite-defaults:\
ha=00306E4AE07F:\
ip=150.9.10.80:\
sm=255.255.255.0:\
gw=150.9.10.1:\
ds=150.9.10.168
Mridul Shrivastava
Honored Contributor

Re: Ignite Recovery

a PA-RISC system is usually using the core I/O card for a network boot.
Make sure this card is connected to the right network.

Did the client and the ignite server on the same subnet? If not you will need to configure a boot helper with the same segment of the client.

Did you configure the ignite server correctly for the client to boot? /etc/bootptab is configured properly as your dhcp alternative.
Time has a wonderful way of weeding out the trivial