make_net_recovery

[SSS_4]

HI Experts,

I am facing some difficulties with "make_net_recovery", below is the scenario.

Host A=rp3440 , hpux11.11
Host B=rp4440 , hpux11.11
Host C=N4000, hpux11.00

Host A is Ignite Server & rest 2 i.e. B & C are clients.

Now the problem is ,
I have created host A as Ignite Server v6.7.79. I want host C to make similar to host B hence I am creating a network recovery archive of host B on server A and then I will push this archive to host C to ignite it & make it similar to host B.

My queries are , is it practically possible as the hardwares on 2 hosts are different [N4000 and rp4440] ? Also I know abt creating an archive of first host with "make_net_recovery" but what is the syntax to push/ignite it to another host that I am not aware, is same "make_net_recovery" does it?

Please provide ur sugestions, any help is appreciated & would be awarded with pts.

[Sandy Chen · Accepted solution]

Hi,

About the hardware different, I never tried this on rp4440 (pa8900) to N4000 (pa8700), I've tried from SD-32 (pa8700) to rp7420(pa8900) and it's failed, but for restoring as below:

Follow these steps to configure your Ignite-UX server to run instl_bootd as a replacement
for bootpd:

1. After you have set up your Ignite-UX server, ensure that bootpd is disabled on
ports 67/68 by commenting out the following line in the /etc/inetd.conf file:
bootps dgram udp wait root /usr/lbin/bootpd bootpd

2. Enable the instl_bootd daemon on ports 67/68 by adding the following line to
/etc/inetd.conf:
bootps dgram udp wait root /opt/ignite/lbin/instl_bootd \
instl_bootd

3. Restart the Internet daemon, inetd, to implement the port changes made in the
previous step:
/usr/sbin/inetd

4. # vi /etc/opt/ignite/instl_boottab
Add the ignite server client IP address and NIC mac address.

To push the image of ignite on the other host, you put host C to BCH an then just type:

BCH> boot lan.x.x.x.x install

where x is the IP address of ignite-ux server

regards,
Sandy

[Steven E. Protter]

Shalom SSS,

make_net_recovery is designed to make a recovery image that is server specific to a network (NFS) mount point.

It is possible to use this image to recover other servers than the one that created it.

N4000 and rp4440 are different hardware designs and the images may not work across taht barrier.

You might find more success with Ignite Golden images, which take a lot of the hardware issue out of the mix. A Golden image is a software image that can be used to replicate configurations and even third party software across many different kinds of hardware.

SEP

[SSS_4]

Hi Sandy,

Could U please elaborate it in details. i.e. how to boot the client with that ip & what shud be the entree in "/etc/opt/ignite/instl_boottab" file.

HI Steve,
Thanks a lot but more details of golden image would be helpful

shripad

P.S. = for sme reasons I can not allocate the points now as there is some problem in portal, will allocate it afterwards at once itself.