Loopback as IP or gateway?

[Daniel Penrose]

I am setting up a generic image (HP-UX 10.20+Applications) to be used on any given processor that may need recovery in the field. The only difference among the processors is the networking info.

If I remember correctly, there is a way to configure IP address and/or route gateway so the machine won't take forever booting up. Is this still possible? After the machine is booted I will login from the console and update the networking configuration.

[James R. Ferguson]

Hi Daniel:

I assume that you are using Ignite to install the server, perhaps cloning it from an Ignite make_tape_recovery tape. If this is the case, you can select the advanced installation feature and elect to run /sbin/set_parms after installation. In disaster recovery tests using Ignite recovery tapes, I have found that this is a great way to get-up-and-running and then address network issues secondarily.

Later, when you are ready to setup networking, do:

# /sbin/set_parms ip_address #...for IPaddress...

# /sbin/set_parms addl_netwrk #...for gateways, DNS, NIS...

...JRF...

[Daniel Penrose]

Thanks James,

Yes, you are correct, I am planning on using ignite (make_recovery -A) to create the image. And I was also planning on using set_parms to secondarily address the networking issues. However, I'm not familiar with the "advanced installation feature" you mentioned. Could you please explain it to me? Also, is make_tape_recovery different from make_recovery? I thought I would just set the IP or default route to 127.0.0.1 prior to creating the image in order to speed up the boot process upon recovery and then go in and set_parms accordingly.

[James R. Ferguson · Accepted solution]

Hi (again) Daniel:

With regard to Ignite, download the latest version from the site below. 'make_tape_recovery' is the replacement for the older (less robust) 'make_recovery'. For vg00, I use the following:

# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

Notice the new 'inc_entire' option. This allows you to collect data from volume groups other than vg00. 'vgexport' map files of all volume groups are captured by 'make_tape_recovery' and placed on its tape regardless. Ignite will use these to 'vgimport' non-vg00 volumes during a recovery. This is nice if you are merely using Ignite to resize or repair vg00.

For current Ignite software, go to:

http://www.software.hp.com/products/IUX/download.html

When booting from the tape thusly created, the Ignite process will be interactive because you specified the "-I" option.

If you are familiar with the syntax of the old 'make_recovery', don't confuse its '-i' option with the '-I' option of 'make_tape_recovery'. The '-I' option of 'make_tape_recovery' is the *same* as the '-i' option of 'make_recovery'. '-I' causes the Ignite process to be interactive when booting from tape.

By making the tape this way, you will be prompted for an interactive installation. Choose "install", and select the "advanced options" tab to resize filesystems and/or set a variety of configuration options. It's that simple.

Regards!

...JRF...