The following document demostrate the process to create an Ignite-UX Golden Image to clone a HP-UX system installation. This guide is designed to walkthrough all the steps requiere and can be use to facilitate first time usage of Ignite Golden Images features. Ignite-UX Administration Guide Chapters. Creating a Server for Network Booting Registered Clients.
Booting and Installing HP-UX From the Server Using the Client Console. Creating Your Own Installation Media. These chapters provides the required information to understand the procedures described on this article. Complete review of the Ignite-UX Administration Guide is an asset to understand the process. This example asummes that the Ignite-UX server itself will be used as a base for the Golden Image. In most actual deployments the Golden Image will be created from a different system.
Just add the source server as a client to update the IUX-Recovery bundle or install a copy of the Ignite-UX software on the client to be able to use the make_sys_image. Check and update current Ignite-UX version. 1. Check current Ignite-UX version. Versions greater than C.
X are highly recommended because implements direct archive to bootable DVD image creation. Starting with the latest available version of the product is highly advisable, since newer boot kernel and module drives are bundle together with every new release and that ensuare support on the latest available hardware platforms. 2. Remove old Ignite-UX release. 3.
Install the correct Ignite-UX release according to the system HP-UX release. 4. Check that the correct Ignite-UX release is installed. Prepare storage. Found or allocate enough space to keep the system golden image. For this example, will create a directory structure "image" inside /var/tmp directory:. [+]/var/tmp/image.
Creating System Image Archive. 1. Check the mounted file systems to determine which volume groups [ and or file systems ] will be [ included excluded ] on the golden image archive. In this example information under /software will not be save on the System Image Archive. 2. Create a file_content file to define the volume groups and filesystem that you want to include or exclude from the archive.
This test system is a MediaWiki Webserver. The "/software" and "/var/tmp/image" mountpoints will be exclude from the System Image Archive.
3. Use "list_expander" command to generate detailed file_list of every file or directory to be include in the System Image Archive. a) Verify what disks or volume groups will be included in the file_list (Mark by the number 1).
b) Calculate and verify the aproximate archive size with the list_expander "-s" flag. c) Create the file_list file. 4. Use "make_sys_image" to preview the Golden Image archive creation and destination capacity. 5. Stop any application that needs to be disable during the System Image Archive creation.
For example, on this system HP-UX Apache and Mysql are the system key applications:. 6. Use "make_sys_image" command to create the System Image Archive archive. 7. Check the System Image Archive final size.
Creating the Golden Image. After creating the System Image Archive, a distribution method should be choose based on the archive size and the available resource to procede to perform the system installation.
Select Golden Image distribution method. Once the Golden Image is created, is necessary to select the best distribution method for the situation. The most common three methods are discuse in this section: bootable DVD, PA-RISC bootable Tape and Using an Ignite-UX server. Manually creation of an Integrity bootable Tape is not presented, since no public information is not available on the Ignite-UX Administration Guide. Create a bootable DVD. If the System Image archive is smaller that 3. 4 GB (6.
8 GB if you have access to dual-layer media), the installation DVD is the easiest way to distribute a golden image because all tasks are handle by the make_media_install command. The result is an dvd-compatible ISO image or a bootable DVD-R if you have a supported DVD burner on the source system. If you don't have a supported DVD burner on the source system, use any third party Windows/Linux/Mac software to transfer the ISO image to a DVD-R.
The basic sintaxis to create an installation DVD is detailed in the next example. Keep attention of the available "-r" and "-o" flags:. -r release; build media (LIF volume) for the specified HP-UX OS release; default = OS release of the system where the script is run ("B. 11. 11") -o 32 64v 64w IA = specific architecture and hardware type; default = make "dual-boot" media capable of booting any PA-RISC or Itanium(R)-based (IA) systems for which Ignite-UX "install environment modules", such as install kernels and RAM file system images, are available on this (Ignite server) system for the specified OS release (see -r above); this option saves time and media space by restricting the set of bootable systems to just one type: PA-RISC 32-bit ("INSTALL"), PA-RISC 64-bit V-class ("VINSTALL"), PA-RISC 64-bit ("WINSTALL"), or IA ("IINSTALL"), respectively (you can use "64" for "64v", and any of "ipf", "IPF", or "ia" for "IA"); note: only PA-RISC wide 64-bit and IA are supported beginning with HP-UX B.
11. 23. Errors during the Step 6 are normal because no DVD writable media was on DVD burner or the DVD burner is not configure or compatible with with your system. The ISO image should be copied on a remote system in most cases to actually transfer it to dvd writable media. Create a PA-RISC installation Tape. The PA-RISC installation Tape that will be build is made of one logical interchange format (lif) volume and one compressed golden archive. Other combinations are possible, like adding serial depots, but those are outside of the scope of this example.
1. Create and modifying the archive configuration file for installation Tape.
Find the "source_type" attribute and change the value from "NET" to "MT". Find the "change_media=FALSE" attribute line and remove the comment hash mark (#). Find the "nfs_source" attribute line and place a comment hash mark before it. The sw_source clause on "/var/tmp/image/config/c3650.
cfg" configuration file will look something like:. Determinate the required space of the golden image archive using the "archive_impact" command. Update the "sw_sel" that support your platform.
The 64 bit OS is the required for almost all current running hardware. Find the "archive_path" attribute and set the value to the number of EOF markers that have to be skipped to get to the archive. There is and EOF marker after the LIF volume, so the correct value it's "1". Find the impact attributes and change for the values reported by the "archive_impact" command. Find the "sw_sel" and "description" attributes and change their values to something more descriptive and applicable for your situation. These modified values are visible on Basic tap of the Ignite-UX TUI/GUI.
Check the syntax of the changes to avoid writting errors to the installation file system:. 2. Create the LIF volume using "make_medialif" command. 3. Modify the installation file system configuration. For golden archives, it's a good advice to modify the control enviroment in which Ignite-UX operates at client installation time by changing the "run_ui" and "control_from_server" configuration paramenters in the installation file system.
To set "run_ui" to "TRUE" and "control_from_server" to "FALSE" use the "instl_adm" command. Create a temporary configuration file:. Edit the "/var/tmp/image/config/cfg" configuration file and modify the "rui_ui" and "control_from_server" attributes. Check the syntax of the changes to avoid writting errors to the installation file system:.
Write the modified temporary configuration file into the LIF volume:. 4. Create the tape using the desire density, no compression and a no-rewind device file.
Note that the no-rewind tape device file must be used. Normally, a default AT&T semantic tape device is used, for example, /dev/rmt/0mn. On this example, a DLT 8000 will be utilize. The special device file "/dev/rmt/0mn" will be use. The "timex" command is use too to leave a record of the time required for the steps.
Configure Golden Image on a Ignite-UX Server. 1. Install the latest version of Ignite-UX on the server with support for the requiere platforms. On this example, all current HP-UX releases will be supported as boot clients.
2. Add an entry on "/etc/opt/ignite/instl_boottab" with the IP and the MAC Address of the Ignite Client that will be booted. 3. Update "/etc/inetd. conf" to use Ignite-UX "tftp" and "instl_boots" daemons.
PA-RISC servers relays on bootp bootstrap protocol to assign the Client IP when booting and PA-RISC servers and Ignite-UX provied solutions to assist in this task. Integrity uses DHCP / PXE protocol to handle this task. If you already have a DHCP server setup-on on site this will assist the client to obtain an IP address before trying to reach the Ignite-UX server. If a DHCP server is not available and an Ignite-UX is on the same subnet, you may need to configure your Ignite-UX server to provied DHCP servicies. That can be done on the Ignite-UX TUI/GUI using the pulldown menu Options - Server Configuration.
For all purposes, if making the client to boot from the lan becomes difficult, creating a boot CD/DVD that contains only the requiere software to boot the system and pull the archive from the Ignite-UX server may prove time saving. There is an example at the end of the document. 4. Move the golden archive into the correct archive release. This NFS mount point is arbitrary but following the release naming convention ensure that archives are easy to organize and found based on the OS release that they support. For example, our example archive is for a HP-UX 11i v1 (11.
21) release, so /var/opt/ignite/archives/Rel_B. 11. 11 is used. 5. Configure NFS share /var/opt/ignite/archives on the Ignite-UX server to present the archive to the clients. 6.
Configuring the Ignite-UX Server to recognize the golden image. This sections follows instructions on Ignite-UX Administration Guide chapter 9. a) Create a copy of the example configuration file.
Use a name that describes the purpose of the new configuration file. b) Determinate the correct values for the impacts lines. c) Edit "/var/opt/ignite/data/Rel_B. 11. 11/golden_archive_cfg". 6.
Add a archive clause using the core_archive_cfg file to the Ignite-UX configuration. Edit the "/var/opt/ignite/INDEX" file to add the following clause entry:. Installing the Golden Image on the Client. Interrupt DHCP network configuration and use fixed values. Creating a Two-Step boot CD/DVD media.
In the Ignite-UX Administration Guide on Chapter 14 Creating Your Own Installation Media. the method to create a boot CD/DVD for an Integrity "Two-step media recovery" is discuse. This is a ISO image that can be use to create media to boot the Ignite-UX clients instead of using a bootable tape or LAN Boot. Note. Errors during the Step 6 are normal because no DVD writable media was on DVD burner or the DVD burner is not configure or compatible with with your system.
The ISO image should be copied on a remote system in most cases to actually transfer it to dvd writable media.