Ignite-UX

Ignite-UX Information Library

To add a new client to the Ignite UX server, from the client

 # add_new_client -s <server_name> -R <release name> [-f] [-d] 

-f overwrite existing client information files in the /var/opt/ignite/clients/0xLLA

 (eg)  # add_new_client -s 216.226.174.37 -f

To change the system name on ignite:

 01. Change the IP address and hostname on /etc/hosts
 02. Change the link name to new name on /var/opt/ignite/clients
 03. Change the client_name file under /var/opt/ignite/clients/<hostname)/
 04. Change the entries in /etc/bootptab or /etc/opt/ignite/instl_boottab

---

To LAN Boot the itanium based servers

 From EFI Shell, create the Direct Boot Profile

 Shell> dbprofile
 Profile List

 Shell> dbprofile -dn ignite -sip 216.226.174.37 -cip 216.226.174.88 -gip 216.226.174.2 -m 255.255.255.0 -b "/opt/ignite/boot/nbp.efi"
 Creating profile ignite

 Shell> dbprofile
 Profile List

 Profile Name: ignite
      Network Type: IPv4
      Client IP address: 216.226.174.88
      Gateway IP address: 216.226.174.2
      Subnet Mask: 255.255.255.0
      Server IP address: 216.226.174.37
      Boot File: /opt/ignite/boot/nbp.efi
      Optional Data:

 Shell> lanboot select -dn ignite

/opt/ignite/boot/AUTO file

While trying to install HP-UX from ignite server using software depot, if the desired OS version is not available for selection to the client systems, make sure /opt/ignite/boot/AUTO files contains the necessary entry for the OS level you are trying to install.

Example: While trying to install HP-UX 11.31, the OS version selection was not available for the client. The contents of AUTO was

 # cat /opt/ignite/boot/AUTO
 KernelPrompt "Choose an operating system to install that your hardware supports:" 120 1
 reset
 "target OS is B.11.23 IA" boot Rel_B.11.23/IINSTALL
 "Exit Boot Loader" exit

After adding the follwing line, it was possible to select HP-UX 11.31

  "target OS is B.11.31 IA" boot Rel_B.11.31/IINSTALL

 # cat /opt/ignite/boot/AUTO
 KernelPrompt "Choose an operating system to install that your hardware supports:" 120 1
 reset
 "target OS is B.11.23 IA" boot Rel_B.11.23/IINSTALL
 "target OS is B.11.31 IA" boot Rel_B.11.31/IINSTALL
 "Exit Boot Loader" exit

Creating HP-UX OE Depot for client Installation

01. Copy the OE DVD contents to IGNITE-UX server. We can either use make_depot command or swcopy command

 # /opt/ignite/bin/make_depots -s /dev/dsk/c1t2d0  \ 
 -d /var/opt/ignite/depots/Rel_B.11.23/HAOE
           OR
 # swcopy -s /dev/dsk/c1t2d0 \* @ /export/ignite/depots/Rel_B.11.31/HAOE 

02. Create HP-UX OE Configuration Information on the Ignite-UX Server

 # /opt/ignite/bin/make_config -s /export/ignite/depots/Rel_B.11.31/HAOE \
 -c /var/opt/ignite/data/Rel_B.11.31/HAOE_cfg
 NOTE:    make_config can sometimes take a long time to complete. Please be
         patient!

03. Add the Configuration Information to the Ignite-UX INDEX file. First copy the default "HP-UX B.11.31 Default" clause to a new clause called "HP-UX B.11.31 HAOE March 2009". After creating the new clause, add the configuration file we created in the last step to the new clause.

 # /opt/ignite/bin/manage_index -n "HP-UX B.11.31 Default" \
 -c "HP-UX B.11.31 HAOE March 2009"

 # /opt/ignite/bin/manage_index -a -f /var/opt/ignite/data/Rel_B.11.31/HAOE_cfg \
 -c "HP-UX B.11.31 HAOE March 2009"

04. View the description of the newly created configuration clause

 # manage_index -x -c "HP-UX B.11.31 HAOE March 2009"
 This selection supplies the default system configuration that 
 HP supplies for the B.11.31 release.

05. Change the description to something meaningful

 # manage_index -c "HP-UX B.11.31 HAOE March 2009" \
 -y "HP-UX B.11.31 HAOE from March 2009 Media"

06. Verify that Description is changed

 # manage_index -x -c "HP-UX B.11.31 HAOE March 2009"
 HP-UX B.11.31 HAOE from March 2009 Media

More Information, refer Ignite-UX Quick Start Guide

Golden Image

Before taking golden image, Install Fresh OS. Apply required patches. Install additional software. Customize the system as required. Do not use the system while taking the Golden Image. While running make_sys_image, the device files are removed, the host and networking information on the system is reset. After the command is complete, these files are put back. By default, make_sys_image stores the archive in /var/tmp directory. We can also the save the archive in remote system.

01. Copy /opt/ignite/data/scripts/make_sys_image to /tmp. Set the permission to 755.
02. Create a directory to store the golden image
03. Take the Golden Image

    # /tmp/make_sys_image -d <directory_to_place_Image> -s local -n image_name.gz

    or to store the image in a remote system

    # /tmp/make_sys_image -d <directory_to_place_Image> -s <remote_system_IP address>

make_sys_image is a shell script. By default, certain files are reset to default initial settings while we use level 2 (-l 2) backup which is the default level. These files are listed under LEVEL2_RESET variable in make_sys_image script. There is also another variable called LEVEL2_NO_ARCHIVE. Files listed under this variable are altogether skipped from backup. If we don't want to exclude the files listed under this sections, simply edit the script.

Configure the Ignite Server to recognize the golden Image


Create the Ignite-UX configuration file for the golden image. We can use the example file /opt/ignite/data/examples/B.11.31.golden_image.cfg

01. Copy the example configuration file to /var/opt/ignite/data/Rel_B.11.31 directory

 # cp /opt/ignite/data/examples/B.11.31.golden_image.cfg\ 
   /var/opt/ignite/data/Rel_B.11.31/golden_image_11.31_cfg

02. Modify the golden_image_11.31_cfg file to set up the golden image NFS transfer. In the sw_source clause, change the nfs_source to the NFS server name and exported directory name. Make sure to use the IP address instead of hostname since the loading of NFS image may fail if hostname is used.

    nfs_source = "192.168.248.237:/backup/AEM/ignite/golden_images"

03. In the sw_sel clause, change the archive path. If the full path of the archive is 192.168.248.237:/backup/AEM/ignite/golden_images/Rel_B.11.31/goldserver.gz, just add Rel_B.11.31/goldserver.gz alone.

    archive_path = "Rel_B.11.31/aemtest2.gz"

04. Run the archive_impact command and get archive impact values

    /opt/ignite/lbin/archive_impact -t -g <archive_file_name>

05. Include the results in the configuration file, replacing the example impacts line.

06. Add the new configuration file (golden_image_11.31_cfg) to /var/opt/ignite/INDEX file.

 cfg "HP-UX B.11.31 Golden Image" {
        description "Default system configuration for B.11.31 release."
        "/opt/ignite/data/Rel_B.11.31/config"
        "/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
        "/var/opt/ignite/data/Rel_B.11.31/golden_image_cfg"
        "/var/opt/ignite/config.local"
 }

The config and config.local files contains default configuration. config.local should be the last file in the cfg clause. The opt/ignite/data/Rel_B.11.31/config supplies the disk and file system layout default plus other control information required by Ignite-UX.

07. Make sure the the target system can access the archive file using NFS.

Now, the above cfg clause appears as an available configuration to Ignite-UX.

Cloning a system using make_net_recovery

01. Create the system recovery image of the system to be cloned using "make_net_recovery" command

02. The recovery configurations and archives created by make_net_recovery are stored in a separate directory on Ignite-UX server for each client. If the client to be installed does not currently have a directory in /var/opt/ignite/clients but is up and running, create the directory using "Add new Client for Recovery" from Actions menu on Ignite-UX GUI (From server). Alternatively, we can also run add_new_client -s <ignite-ux_server_name> from the client. If the client is not running, you will have to boot the system from the Ignite-UX server to get the directory created.
03. Copy the CINDEX and recovery directory from the source client to the target client directory. If the CINDEX file already exits, either create a backup copy of the CINDEX or edit the CINDEX file to add the desired entries from the source client.

 cd /var/opt/ignite/clients/src_client_name
 find CINDEX recovery | cpio -pdvma ../target_client_name 

04. Give the target client NFS access to recovery image of the source system
05. Boot the target client from the ignite-UX server
06. Change the system networking parameters for the client during installation

For more information, refer Cloning Using Ignite-UX.PDF

To restore individual files form make_net_recovery


01. Using gzcat and pax to restore /etc/hosts file

    # gzcat <image_name> | pax -r -f - etc/hosts

Note: There should not be any leading slash in the file to be recovered. The file will be restored to the current directory.

02. Usng gzcat and tar

    # gzcat <image_name> | tar -xvf - etc/hosts

/etc/opt/ignite/instl_boottab

/etc/bootptab