Select Page Home Interleaf Notes Links

Select Page Unix Notes Build an HP-UX server Ignite Notes GSP Notes inetd.conf and inetd.sec Notes Changes to Unix pages

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.
   • Reload the O/S from CD or tape including all patches and applications (one or more days), or
   • You can ignite the target box using an image that was created from a similar box, which had the O/S configured, patches added and applications installed (35 minutes to one hour).
2. You have to upgrade more than one box with:
   • An O/S upgrade.
   • A patch or patches.
   • An application.
   • All the above.
   All of which could take an hour or more to complete.

• Download/install the latest version of Ignite from: http://www.software.hp.com, or install Ignite from an application CD.
• Identify which box will be your "Golden" box. This box should be updated, configured, and patched to the highest levels possible.
• Create a bootable tape to use off your Golden box, and then Ignite from a bootable tape
  (you may also want to duplicate [copy] the tape), or
• Configure Ignite to use an image, and then
• Create an image to use with the LAN or GUI install.
• Running Ignite:
  • Ignite from the LAN.
  • Ignite GUI - To ignite or re-ignite a box that is up and running.

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

NOTE:
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
          installation.

you may need to run "umask 022" before the make_tape_recovery command is run.

• Halt boot process by pressing the "Esc" key.
• Search for a bootable device: "sea ipl"
• Boot to your tape device: "bo p1" ("p0" would most likely represent your hard drive).
• Do not interact with IPL: "n"
• Enter the language you wish to use - "62" - then press the "Enter" key to confirm the language selection.
• Note the hostname the tape was created from and the date/time of creation. Make sure it's the tape you want to use. The tape could have been mislabeled.
• Select "Install HP-UX" and press the "Enter" key.
• Select how you want to install the data off of the tape:
  • If this is a simple reinstall of what was on the tape then select "Media only installation" and "No user interface - use all the defaults and go" selections.
  • If you need to make changes - i.e.; logical volume size - then choose "Media only installation" and "Advanced Installation (recommended for disk and filesystem management)". Basic changes you may want to make are:
    • Under the "System" tab - change the date and time and root password.
    • Under the "File System" tab - make logical volume changes - size, HFS or VxFS, etc.
• Select "Go" twice.

   WARNING: The configuration information calls for a non-interactive
            installation.

            Press <Return> within 10 seconds to cancel batch-mode installation:

            Really cancel non-interactive install and start the
            user-interface? ([y]/n):

The last warning you may get when not choosing to run an interactive Ignite session is if you have a filesystem/boot area on your drive:

   WARNING: The disk at: 8/0.6.0 (SEAGATE_ST123456WC) appears to contain a file
            system and boot area. Continuing the installation will destroy any
            existing data on this disk.

            Press <Return> within 10 seconds to cancel batch-mode installation:

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")

    dd if=/dev/rmt/0mn of=/someplace/special/file1 bs=2k
    dd if=/dev/rmt/0m  of=/someplace/special/file2 bs=10k

    dd if=/someplace/special/file1 of=/dev/rmt/0mn bs=2k
    dd if=/someplace/special/file2 of=/dev/rmt/0m bs=10k 

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.

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
   

   NOTE:
   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:
   Install-HPUX.
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.
    

    NOTE:
    If you really need to, you can run the rest of ignite from the target box.
    It just ain't pretty.
    

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.
   • If the desired icon is not present, select from the pull down menu "Actions -> Boot New Client..." Input the desired hostname. After you click "Ok", Ignite will reboot your desired box. In a few minutes the icon will appear.
   • If this does not work, you will need to Ignite from the LAN.
7. Click (highlight) the desired icon. Right click to bring up the menu and select "Install Client -> New Install..."
   • If you chose "Install Client -> Repeat Install...", a window will appear which will have your currently selected box highlighted. Just like it sounds, you can repeat the previous install that was executed on this box.
8. Click "Ok" on the first screen that comes up (unless you want to do some typing).
   • If a "Confirmation" window comes up due to your reinstall of an (already) installed box, click on "No" to pick or re-pick new settings.
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."
   • The "7xx Series Install" and all other selections in this menu are listed in the INDEX file.
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.
    • The limits may go over by 4 meg or so due to the image being made from a box which had drives with less defective blocks. Simply reduce the amount of disk space used on a file system. I recommend reducing /usr.
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
#* CHOOSER BROADCAST

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.