Ignite UX server deployment

Hi,

I am planning to deploy a new Ignite UX server. I am having the PA-RISC Servers with 11.11 & 11.23 Versions in my setup. Please tell me the step by step procedure to deploy and to successfully integrate with all the clients.I have referred some documents.But still unclear about the exact procedure.please help me.
Thanks a lot in advance.

regards
Bobby.

8 REPLIES 8

Install the Ignite-UX software.

---Set up temporary IP addresses for boot clients.
/etc/opt/ignite/instl_boottab

---Set up tftp and instl_bootd services in /etc/inetd.conf.
tftp dgram udp wait root /usr/lbin/tftpd tftpd\

/opt/ignite\

/var/opt/ignite

...

instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

...

root@hpeos004[] inetd -c

root@hpeos004[]

root@hpeos004[] pwget -n tftp

tftp:*:510:1:Trivial FTP user:/home/tftpdir:/usr/bin/false

----Set up /etc/exports to give NFS access to the /var/opt/ignite/clients directory.

root@hpeos004[] vi /etc/exports

/var/opt/ignite/clients -anon=2

-----Set up Ignite-UX parameters to be used during the installation of the operating system.

root@hpeos004[] instl_adm -d
instl_adm -d > /tmp/instl.cfg

run_ui=false
control_from_server=true
disable_dhcp=true
root@hpeos004[] instl_adm -f /tmp/instl.cfg

also you can check the following docs

http://docs.hp.com/en/oshpux11iv2.html#Ignite-UX

http://docs.hp.com/en/5992-1999/5992-1999.pdf
http://docs.hp.com/en/5992-5274/5992-5274.pdf

All things excellent are as difficult as they are rare

Hi jupinder,

Thanks U very Much for the info..I have done everything you mentioned.But i am getting the following error.I understood that, the client was not able to take the bootable image from server.Now if i fire the make_net_recovery from client to the server,will it be sufficient or should i do any further configuration tasks..

Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/WINSTALL
19169280 + 5014424 + 8704000 start 0x390268

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3e900000.
DoCalllist done

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 4094 MB 4094 MB 4094 MB
Kernel : 4094 MB 4094 MB 4094 MB
User : 3691 MB 3215 MB 3227 MB
-------------------------------------------------------------------------

gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0

System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4192256 Kbytes, lockable: 2980492 Kbytes, available: 3501336 Kbytes

======= 02/13/10 04:22:04 EST HP-UX Installation Initialization. (Sat Feb 13
04:22:04 EST 2010)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/init (opt) $Revision: 10.526 $ $Date: 2006/06/20 22:26:23 $
version 5 layout
16384 sectors, 16384 blocks of size 1024, log size 1024 blocks
unlimited inodes, largefiles not supported
16384 data blocks, 15288 free data blocks
1 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 16384 data blocks
* Scanning system for IO devices...
* Querying disk device: 0/1/1/0.0.0 ...
* Querying disk device: 0/1/1/0.1.0 ...
NOTE: Default (boot) source does not appear to be a valid (or complete)
install source, switching source to Network
* Bringing up Network (lan0)
add net default: gateway 10.86.51.1
* Reading configuration information from server...

* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
ERROR: Failed to read "INDEX" file from install server. Check that the
install server's IP address is correct and the server has the
"Ignite-UX" product loaded and is available via the tftp(1) service.
delete net default: gateway 10.86.51.1
Failed to startup networking, user interaction required
Press Return to continue:

Please suggest me...

regards
Bobby.

Have you checked your "/etc/opt/ignite/instl_boottab"

mae an entry like below

10.8.129.137:0x0018FE2F0241::reserve
10.8.129.155:0x0018FE2F0249::reserve

All things excellent are as difficult as they are rare

have you run the inetd -c

All things excellent are as difficult as they are rare

Yes.
They are perfect. I hope the problem is the client was unable to get the bootable image from the server..Since we didn,t created / specified any bootable image for the client, it is giving this error. Will it be sufficient if i fire the backup command make_net_recivery from the client.? so that the client can take the same image from the server while restoration.

regards
Bobby.

From the forum

Step 1. Use make_net_recovery or Ignite-UX to create a system recovery image
of the source system.
Step 2. On the Ignite-UX server, if the client to be installed does not currently
have a directory in /var/opt/ignite/clients but is up and running,
use the Ignite-UX GUI to create that directory using Add New Client for
Recovery from the Actions menu. For more information, see Ã¢Â Â Adding
Clients for RecoveryÃ¢Â Â on page 231.
System Recovery
Notes on Cloning Systems
246 Chapter 9
If the client is not running, you will either need to boot it from the
Ignite-UX server or from a tape made with make_boot_tape in order for
this directory to be created.
Step 3. Copy the CINDEX and recovery directory from a source client to the target
client directory. If the target client has previously used
make_net_recovery, it will already have a CINDEX file. If the CINDEX
file for the client exists, you may want to save a copy and/or edit the file
to add the desired entries from the source client. The following
commands copy the required files. You may specify src_client and
target_client using either the LAN addresses (such as
0x0060B04AAB30), or by using the clientÃ¢Â Â s hostname (which is a symlink
to the LAN address):
cd /var/opt/ignite/clients/src_client
find CINDEX recovery | cpio -pdvma ../target_client
Step 4. Give the target client NFS access to the archive of the source system. To
do this, log in to the system that holds the archive (normally the
Ignite-UX server).
Typically each target client has its own directory for storing the archives,
and the directory is exported only to the individual client. In this case,
you will need to edit the /etc/exports file to allow access to both the
source and target clients:
a. Enter vi /etc/exports
b. Append: target-client to the end of the source-clientÃ¢Â Â s line.
c. Enter exportfs -av
Step 5. Boot the target client from the Ignite-UX server (using any method you
want). Then, when you install the system you can select from the
recovery configurations of the source system.
Step 6. Change the system networking parameters for the client during the
installation.
For additional information regarding system cloning, see the Cloning
and Recovery Issues using Ignite-UX White Paper on the "Information
Library" page available at the Ignite-UX Web site at:
http://www.docs.hp.com/en/IUX/infolib.html
System

All things excellent are as difficult as they are rare

and please let me know if you got the success now.

All things excellent are as difficult as they are rare

here is the excellent document for you help

http://docs.hp.com/en/5992-6584/ch15s02.html

All things excellent are as difficult as they are rare