Ignite Notes

To see what's recently changed on this page - please look at the Changes page.

These instructions assume you would like to use Ignite to make an image of your workstation or server using the "make_tape_recovery" command for making a bootable tape or to be used with the Ignite GUI which run's on an Ignite server.

Two reasons for using Ignite are:

  1. One or more (O/S) drives have been replaced on the target box. Because the O/S is now FuBar, you can do one of two things.
  2. You have to upgrade more than one box with: All of which could take an hour or more to complete.
How to start
Create a bootable tape

In order to copy ALL of vg00 - use the following command:

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

The "-I" parameter will automatically stop the install process in order for
you to make adjustments if needed, i.e.; logical volume size adjustments, etc.
If you do not use this parameter you will have a ten second window to stop the
process before your install starts. See Ignite from a bootable tape
for more information.
Another NOTE:
IF you get:

    NOTE: File: /var/opt/ignite/recovery/<date>,<time>/<file_name> is not
          world-readable, this may cause clients to fail to read it during an

you may need to run "umask 022" before the make_tape_recovery command is run.
Ignite from a bootable tape

Additional issues you may have when trying to Ignite from Tape:

Duplicate [copy] the tape

A tape created with "make_tape_recovery" contains 2 tape files. The first tape file is written with a 2k block size, and the second with a 10k block size. The first file is a LIF file, and the second is a tar archive. If you have 2 tape drives on a system, then you can easily duplicate the tapes using 2 "dd" commands with a no-rewind-on-close device file for the first command. For example:

    dd if=/dev/rmt/0mn of=/dev/rmt/1mn bs=2k
    dd if=/dev/rmt/0m  of=/dev/rmt/1m bs=10k
    (Your main tape drive is "0m" and your second tape drive is "1m")
If you only have 1 tape drive, and have enough disk space to hold the contents of both tape files, then use something like this:
    dd if=/dev/rmt/0mn of=/someplace/special/file1 bs=2k
    dd if=/dev/rmt/0m  of=/someplace/special/file2 bs=10k
(Insert blank tape now)
    dd if=/someplace/special/file1 of=/dev/rmt/0mn bs=2k
    dd if=/someplace/special/file2 of=/dev/rmt/0m bs=10k 
You can also use this command: /opt/ignite/bin/copy_boot_tape. It has a number of options you'll need to work out. See the man page for this beast.
Configure Ignite

Specific information concerning how to further configure the following files can be accessed from the Ignite URL listed above. All files listed below are located on the Ignite server.

  1. /var/opt/ignite/INDEX -
    Initial file which will indicate other files to be used. Its description will show in the "Configuration:" menu selection.
  2. /var/opt/ignite/data/Rel_B.10.20/apps_7xx.cfg -
    This file tells ignite where to get the "Golden" image. It also has information that you change when the "impacts" statements are run. To get the impact statement, run:
    /opt/ignite/lbin/archive_impact -t -g /var/opt/ignite/archives/Rel_B.10.20/image_name.gz
  3. /var/opt/ignite/config.local.7xx -
    This file contains DNS, NIS, XNTP, Kernel modifications, and the location of any post configurations files which will need to run. Shown in the "Systems" tab area when the GUI is run.
  4. /opt/ignite/data/Rel_B.10.20/config.7xx -
    Generic LVM layout.
  5. /var/opt/ignite/saved_cfgs/7xx_Install -
    Final LVM layout. Shown in the "File System" tab area when the GUI is run.

Create an Image
  1. Copy the make_sys_image file to the target box:
    ignite_server # rcp /opt/ignite/data/scripts/make_sys_image target_box:/tmp
  2. Log onto the target box.
  3. SU to root.
  4. Change init level to two and kill automount process if running. Disable users from logging on to target box.
  5. Run the following command:
    target_server # /tmp/make_sys_image -d /var/opt/ignite/archives/Rel_B.10.20 -s ignite_server_IP
    You may need to temporarily add the target box to the Ignite servers
    /.rhost file.
  6. Restore init level and user access.

Ignite from the LAN

  1. Turn on target box.
  2. Press and hold the "ESC" key when prompted for:
    Selecting a system to boot, and
    Searching for Potential Boot Devices.
  3. Enter the boot administration mode:
    Select from menu: a.
  4. Access the boot server:
    BOOT_ADMIN> boot lan install.
  5. Get a kernel:
    ISL> hpux (;0)/boot/INSTALL.
  6. Press the "Enter" key within three minutes at this next screen.
  7. Select:
  8. Three things to do on this screen:
    1. Use the "Tab" key to navigate your cursor to the "Remote graphical..." selection.
    2. Press the "Space Bar" to change your selection.
    3. Select "Ok" when complete.
  9. Press "Crtl-C" to stop the DHCP search.
  10. Using the "Tab" key to navigate:
    1. Add the hostname
    2. Add an IP
    3. Add the netmask
    4. All other info should be correct. Select "Ok" when complete.
  11. At this point, an icon that represents the target box your on will appear on the Ignite GUI. You can run the remainder of the install from the GUI using the information noted in Ignite New Box.
    If you really need to, you can run the rest of ignite from the target box.
    It just ain't pretty.
Ignite GUI
  1. Log onto Ignite server.
  2. SU to root.
  3. Export your display.
  4. Set your PATH
    io # export PATH=$PATH:/opt/ignite/bin:/opt/ignite/lbin
  5. Start ignite
    ignite_server # ignite.
  6. When the GUI comes up, you will notice one or more icons which represent a box on our network.
  7. Click (highlight) the desired icon. Right click to bring up the menu and select "Install Client -> New Install..."
  8. Click "Ok" on the first screen that comes up (unless you want to do some typing).
  9. The "Configuration:" menu selection is where you pick which type of install you want to perform. For this example we will chose the "7xx Series Install."
  10. Click on the "Systems" tab at the top of the window.
  11. Click on "Set Root Password..." to enter the current root password.
  12. Click on the "File System" tab at the top of the window and make sure you are not going to go over the file system limits.
  13. Click on the "Advanced" tab. Highlight the "/var/opt/ignite/scripts/7xx_on_13x_net.post.install" selection were 13x indicates which subnet your box is NOT going to be on.
  14. Click on the "Remove" button to remove this script.
  15. Click on "Go!."
  16. Click on "Go!" in the "itool Confirmation (target_hostname)" window.
  17. Double click on the icon to get a "Client Status..." window just in case you want to see the ongoing status of your ignite installation.
  18. Test to make sure all is well with the newly installed box.
  19. If the box is a server where users are going to logon using Exceed, you need to uncomment the following lines located in the /etc/vue/config/Xacceess file:
    #* # grant service to all remote displays

I developed this site so please send comments to dburton3@tampabay.rr.com. Thanks!

Search my site:
Locations of visitors to this page QRcode

Ok.. so I put this waaay down at the bottom of this web page. I don't expect anyone to actually toss a buck or two my way as a thank you for all the work I've done on this site (Hmmm... feel guilty yet?), but it sure would be nice.

Please donate!

This donation link uses a secure PayPal connection.
Valid CSS!
free counter
free counter