Home > HP-UX > Setting up an HP-UX Ignite-UX server

Setting up an HP-UX Ignite-UX server

For the purposes of this installation guide, I will be using an HP-UX 11.11 PA-RISC (rp3440) server.

First, download the Ignite-UX software from HP’s website, http://software.hp.com.  It is freely available and the version I’ve chosen is all “3 bundles.”

Documentation can be found here:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01942571/c01942571.pdf

I’ve downloaded to /var/tmp directory and now will install the software:
#swinstall -s /var/tmp/Ignite-UX-11-ALL_C.7.10.474.depot \*

To verify your installation:
#swlist | grep -i ignite
  IGNITE                        C.7.10.474     HP-UX Installation Utilities (Ignite-UX)
  Ignite-UX-11-11               C.7.10.474     HP-UX Installation Utilities forInstalling 11.11 Systems
  Ignite-UX-11-23               C.7.10.474     HP-UX Installation Utilities forInstalling 11.23 Systems
  Ignite-UX-11-31               C.7.10.474     HP-UX Installation Utilities forInstalling 11.31 Systems

From a client you want to make the “golden image” from, you’ll only need “make_sys_image” script and can be copied to /tmp without having to install the Ignite software.
#chmod +x /tmp/make_sys_image
For this image I will place it on an NFS server (already mounted).  Reason I am doing this is because the Ignite-UX server shares this same mount point.  Other option is to use “-s dest_IP” if you have a server to send it to.  I’ve also declined not to use compression (-c n, gzip is default).
#/tmp/make_sys_image -s local -d /directory_to_place_image -c n

Now configure the Ignite-UX server to recognize the new golden image.
#cp /opt/ignite/data/examples/B.11.11.golden_image.cfg /var/opt/ignite/data/Rel_B.11.11/golden_image.cfg
Make sure your /etc/exports contains the /var/opt/ignite/clients directory.
#cat /etc/exports
/var/opt/ignite/clients -anon=2
### Next 2 lines below don’t actually work since you can’t share NFS mounts from an NFS mount, but added as examples
/netapp/testoutput/ignite/REL_B.11.11 -anon=2,ro
/netapp/testoutput/ignite/REL_B.11.23 -anon=2,ro
#exportfs -a

Ignite-UX manages the directories for images from /var/opt/ignite/data/INDEX file.  Below, I’ve created an additional golden image cfg stanza:
cfg “HP-UX B.11.11 hpapp1 parisc archive” {
        description “This image is from a preconfigured B.11.11 release.”
        “/opt/ignite/data/Rel_B.11.11/config”
        “/var/opt/ignite/data/Rel_B.11.11/hpapp1_archive.cfg”
        “/var/opt/ignite/data/config.local”
}

Modify /var/opt/ignite/data/Rel_B.11.11/golden_image.cfg for sw_sel and sw_source:
nfs_source = “172.25.101.179:/netapp/testoutput/ignite/REL_B.11.11/hpapp1.none”
Remove the “init sw_sel” clauses that will not be used (i.e. “golden image – 32 bit OS”)
Change “init sw_sel” for your appropriate image’s description:
description = “hpapp1 archive HP-UX 11.11 CDE – 64 Bit OS”
archive_path = “hpapp1.none”
Replace “impacts” lines in the “init sw_sel” clause by executing “archive_impact”
#/opt/ignite/lbin/archive_impact -t /netapp/testoutput/ignite/REL_B.11.11/hpapp1.none
My example output:
init sw_sel “golden image – 64 bit OS” {
    description = “hpapp1 archive HP-UX 11.11 CDE – 64 Bit OS”
    sw_source = “core archive”
    sw_category = “HPUXEnvironments”
    archive_type = tar
    archive_path = “hpapp1.none”
    impacts = “/” 34Kb
    impacts = “/.ssh” 8Kb
    impacts = “/dev” 13Kb
    impacts = “/etc” 95311Kb
    impacts = “/opt” 2710993Kb
    impacts = “/sbin” 44769Kb
    impacts = “/stand” 1337Kb
    impacts = “/u01” 6199689Kb
    impacts = “/usr” 1253929Kb
    impacts = “/var” 3134736Kb
 } = TRUE

Verify and fix, if needed, the syntax of the INDEX file:
# /opt/ignite/binpa/instl_adm -T

Register clients to the Ignite-UX server:
#/opt/ignite/binpa/ignite
Click on server setup, configure booting IP addresses now and add IP and MAC address info.  You can choose the same IP you made the archive from since you would use it for a restoration procedure.  Skip DHCP Setup.

Configure the client to install the golden image:
If the client is already running HP-UX, boot it by:
#bootsys -v -w client_hostname 
client_hostname = name of the client
If the client is not running HP-UX, boot the system from the console and interrupt the boot process.
firmware prompt>boot lan.n.n.n.n install
where: n.n.n.n is the IP of the Ignite-UX server.

Using make_net_recovery
In short, make_net_recovery takes the place of make_tape_recovery so you won’t have to have a backup tape drive and tapes.  As long as you have available disk space, this method seems to be the best for administration and manageability.

For HP-UX IA server example:
#/opt/ignite/binia/make_net_recovery -s 172.25.101.179 -a 172.28.2.7:/vol/IandT/testoutput/ignite/REL_B.11.23/birch -x inc_entire=vg00 -N
The “-a” specifies an alternative NFS server to place the archive in, “-x” says to include only volume group vg00, and “-N” dictates no compression will be used.

For HP-UX PARISC example:
#/opt/ignite/binpa/make_net_recovery -s 172.25.101.179 -a 172.28.2.7:/vol/IandT/testoutput/ignite/REL_B.11.23/birch -x inc_entire=vg00 -N
The “-a” specifies an alternative NFS server to place the archive in, “-x” says to include only volume group vg00, and “-N” dictates no compression will be used.

Categories: HP-UX
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: