Showing results for 
Search instead for 
Did you mean: 


Super Advisor


Hello All,
We have a ignite server in our environment. I have to configure couple of pa risc servers as a client to the ignite server. So that i can save the golden image of the client servers on to the ignite server. I have done this in the past during 2001 . But it's been a long time - so i lost track.Can some one please assist with the procedure for this. Note - i do not see make_sys_image or /opt/ignite/scripts directory in the client systems .Also the swlist does not return any ignite software product.
Thanks in advance
Learning ...
Michael Allmer
Frequent Advisor

Re: ignite

Copy /opt/ignite/data/scripts/make_sys_image to /tmp on the systems you ar planning to create a golden image of.
For further detail check out the documentation;
Trusted Contributor

Re: ignite


Here is the procedure I have followed for Ignite

1.Steps to setup On a Itanium Server

A>On the Server Side

a) Install Ignite-UX-11-ALL_C.7.6.100.depot from

#swinstall â s Ignite-UX-11-ALL_C.7.6.100.depot

b) Created the depots on the Server HP UX 11i V3[Both DVD 1 of 2 & 2 of 2]

#/opt/ignite/bin/make_depots -s /dvdrom \-d /var/opt/ignite/depots/Rel_B.11.31/core_media

c) Create the HP-UX OE Configuration Information on the Ignite-UX Server

#/opt/ignite/bin/make_config -s /var/opt/ignite/depots/Rel_B.11.31/core_media \-c /var/opt/ignite/data/Rel_B.11.31/core_media_cfg

d) Add the configuration information to the Ignite-UX /var/opt/ignite/INDEX file.

#/opt/ignite/bin/manage_index -n "HP-UX B.11.31 Default" \-c "B.11.31 From OE Media"

e) I have added the core_media_cfg file is added to the â B.11.23 From OE Mediaâ clause.

#/opt/ignite/bin/manage_index -a \-f /var/opt/ignite/data/Rel_B.11.31/core_media_cfg \-c "B.11.31 From OE Media"

#manage_index -x -c "B.11.31 From OE Media"

#manage_index -c "B.11.31 From OE Media" -y "B.11.31 0803 OE"

f) Configure the System as an Ignite-UX Server

# /opt/ignite/lbin/setup_server -n

g) Enable the bootpd daemon with the following Procedure:

i. Edit the /etc/inetd.conf file:
# vi /etc/inetd.conf
ii. Remove the comment character (#) from the bootpd line:
bootps dgram udp wait root /usr/lbin/bootpd bootpd
iii. Save the /etc/inetd.conf file and exit vi:wq!
iv. Make the inetd daemon reread the /etc/inetd.conf file:
# inetd -c

And after modification it looks as below:-

Entries in /etc/inetd.conf
bootps dgram udp wait root /usr/lbin/bootpd bootpd
#finger stream tcp nowait bin /usr/lbin/fingerd fingerd
login stream tcp6 nowait root /usr/lbin/rlogind rlogind
shell stream tcp6 nowait root /usr/lbin/remshd remshd
exec stream tcp6 nowait root /usr/lbin/rexecd rexecd
#uucp stream tcp nowait root /usr/sbin/uucpd uucpd
ntalk dgram udp wait root /usr/lbin/ntalkd ntalkd
auth stream tcp6 wait bin /usr/lbin/identd identd

h) To Ignite a Client across the Network, add the Network Entry for the Client to the IP Address File on the Server @ /etc/bootptab.

Entries in /etc/bootptab looks like:-




# Example /etc/bootptab: database for bootp server (/usr/lbin/bootpd).
#@(#)B11.23_LR $Revision: $ $Date: 96/10/08 12:46:42 $
# Format:
# nodename:tag=value:tag=value: ... :tag=value
# first field -- nodename (hostname) of terminal followed by colon
# (should be full domain name)
# Blank lines and lines beginning with '#' are ignored.
# Make sure you include a colon and a backslash to continue a line.
# Don't put any spaces in the tag=value string.
# The ht tag MUST precede the ha tag.
# The options listed below are commonly used for HP X Window terminals
# see the bootpd.1m man page.
# ba -- broadcast bootp reply for testing with bootpquery
# bf -- bootfile (for tftp download)
# bp -- bootp server IP addresses to relay the bootp requests
# bs -- bootfile size in 512-octet blocks
# ci -- client ID (for dhcp clients only)
# cs -- cookie server IP address
# dn -- domain name
# ds -- domain name server IP address
# ef -- extensions file, containing more options for the client
# gw -- gateway IP address (must have sm tag defined also)
# ha -- hardware address (link level address) (hex)
# hd -- home directory for bootfile (chrooted to tftp home directory)
# hn -- send nodename (boolean flag, no "=value" needed)
# hm -- hardware mask (hex) (must be preceded the ht tag)
# hp -- maximum hops value (cannot exceed 16)
# ht -- hardware type (ether) (must precede the ha and hm tag)
# im -- impress server IP address
# ip -- (client) IP address
# lg -- (MIT-LCS UDP) log server IP address
# lp -- LPR (line printer) server IP address
# md -- file to dump core image to in the event of a crash
# na -- NETBIOS name server IP address
# nb -- NETBIOS datagram distribution server IP address
# nc -- NETBIOS over TCP/IP node type (B-node, P-node, M-node, or H-node)
# nd -- NETBIOS over TCP/IP scope
# ns -- name server (IEN 116) IP address
# nt -- network time protocol server IP address
# rl -- resource location server
# rp -- path name to client's root disk
# sm -- network subnet mask
# ss -- swap server IP address
# tc -- template for common defaults (should be the first option listed)
# th -- threshold value in seconds
# to -- time offset in seconds from Coordinated Universal Time
# tr -- renewal (T1) time value (a percentage of the lease time)
# ts -- time server IP address
# tv -- rebinding (T2) time value (a percentage of the lease time)
# vm -- vendor magic cookie selector (should be rfc1048)
# xd -- X window system display manager IP address
# xf -- X window system font server IP address
# yd -- NIS domain name
# ys -- NIS server IP address
# Tn -- generic option tag n
# T144 remote config file name (file name must be enclosed in "")
# Vn -- vendor specific information for vendor option tag of n

B>At the client side(Itanium):

Shell>lanboot select â dn

C>Direct Boot Profiles for Itanium-Based Systems at the Clint side

The following dbprofile command, when run from EFI,

Shell>dbprofile -dn testprofile -sip -cip -gip -m -b "/opt/ignite/boot/nbp.efi"

creates a new direct boot profile (or updates the profile if it exists) called testprofile.
The profile contains the following information:
Ignite-UX server IP address (-sip)
Ignite client IP address (-cip)
Gateway IP address (-gip)
Network mask (-m)
Boot file name (-b) /opt/ignite/boot/nbp.efi

Shell>lanboot select -dn testprofile

2.Steps to setup On a PA-RISC Server

A>On the Server Side

a) Edit the /etc/opt/ignite/instl_boottab file (don't worry that it appears to be [Read-only]):

# vi /etc/opt/ignite/instl_boottab

b) Add an entry for your client. If a network entry already exists for your client, you may edit it so it looks like the entry below. The client's MAC address should be in hexadecimal, with a leading â 0xâ .


c) Save the /etc/opt/ignite/instl_boottab file and exit vi:


B>At the client side(Itanium):

Shell>boot lan

Andrew Rutter
Honored Contributor

Re: ignite


first thing to do is install in=gnite/ux on the clients then.

keep it the same version as on the server if you can to avoid further problems. If you cannot update them all to the same version

then all the docs on how to use it fully can be found here

Michael Allmer
Frequent Advisor

Re: ignite


I have reread your question and am that for what you are asking all you need to do is the follwing.

1-On the server; Copy /opt/ignite/data/scripts/make_sys_image to /tmp on the client that you are making a golden image of.

2- On the server create an archive directory to store the golden image.
mkdir -p /var/opt/ignite/archives/Rel_B.11.11

3- On the client run /tmp/make_sys_image [options]
by default it creates a gzip-compressed file. cleinthostname.gz all specific host information device files log files and network information are removed. If you want to skip step two above you can use;
/tmp/make_sys_image -d directory_you _want_to_store_image -d destination_system_ip_address.
The storeage location must be served out via NFS and be writable.

Again you do not need any cleint software installed for you to run the above, just read the documentation and follow the steps.