Help!! rebuild INDEX file of ignite server ?

[jack_31]

Hi experts,

I deleted all of hp10.20 clauses in the INDEX file of my ignite server by mistake, can I rebuild the INDEX file of ignite server?

BTW, my ignite is 3.6.82 and OS is hp-ux11.0.

Thanks

Jack

[Luc Bussieres_1]

You could do it by installing a void patch:

To rebuild the INDEX file, use the following procedure which will install a
"fake" product on the system. During the installation of this product, the INDEX
file will be regenerated.


# cd /tmp
# vi void.psf
product
tag void
fileset
tag void
:wq!
# swpackage -s /tmp/void.psf
# swinstall void
# swremove void
# rm void.psf
# swremove -d void

regards,
Luc

[jack_31]

Hi Luc,

Thanks for your help.
I did the swinstall following your steps,but I got a error messages when I run the "swinstall void" as below:

* Session started for user "root@server".

* Beginning Selection
* Target connection succeeded for "server:/".
* Source connection succeeded for "server:/var/spool/sw".
ERROR: Could not apply the software selection "void"; it is not
available from depot or root "server:/var/spool/sw".
* Software selection failed for "server:/var/spool/sw".
ERROR: No software has been selected.
ERROR: Cannot continue the "swinstall" task.
* Selection had errors

and my INDEX keep unchanged.

could you give more advices?

thanks
jack

[jack_33]

up

[Erik Heckers]

Hello!

Solution A)
If you have already
installed one or more
clients check the
file config.full in
the client directories.

If I'm right the beginning
of those files is a complete
copy of the INDEX file.

Solution B)
It may also work to reconfigure the Ignite bundle
for 10.20 (or to reinstall it).

Solution C)
The attachment is a
default cfg clause for
HP-UX 11.11
Replace '11.11' with
'10.20' everywhere and it
should work.

Erik

[jack_33]

Hi, Erik
thanks for your response.Now I found a config.full file but I am also curious about your solution B:

Solution B)
It may also work to reconfigure the Ignite bundle
for 10.20

do you have any idea how can I reconfigure the ignire?

thanks
jack

[Martin Burnett_2]

Hello Jack,

We are talking about the ignite INDEX file correct? /var/opt/ignite/INDEX?

Ok, first of all ignore the response from Luc as he is talking about recreating the IPD (also an index file) for SD-UX which has nothing to do with the INDEX file for Ignite which is used to install clients.

Second, there is no way to automatically recreate the INDEX file. You will have to add the information back. This would be a modified version of the same procedure outlined in the Ignite Administrator's manual (http://docs.hp.com/hpux/onlinedocs/B2355-90738/B2355-90738.html) "Configuring Ignite-UX Server to Recognize the OS Archive" Step 2-3-4:
....

Add impacts lines in the init sw_sel clause by executing: /opt/ignite/lbin/archive_impact -t -g /opt/ignite/data/Rel_B.10.20/config
and including the results in the file, replacing the example impacts lines. By default, this assumes that we created a tar archive that was gzipd.

Here is the complete sw_sel clause (some extra clauses in the example have been deleted for simplicity):

init sw_sel "golden image" {
description = "Archive HP-UX 10.20 CDE"
sw_source = "core archive"
sw_category = "HPUXEnvironments"
archive_type = gzip tar
# For NFS, the path to the archive is relative to the mount
# point specified in the sw_source:
archive_path = "hpfcnjm2.gz"
# ftp/remsh sources can use a full path:
# archive_path = "/pub/IUXarchives/B.10.20_700_CDE.gz"
impacts = "/" 23Kb
impacts = "/.dt" 35Kb
impacts = "/TT_DB" 18Kb
impacts = "/etc" 1375Kb
impacts = "/export" 1Kb
impacts = "/opt" 74079Kb
impacts = "/sbin" 13449Kb
impacts = "/stand" 1Kb
impacts = "/tmp" 1Kb
impacts = "/usr" 225459Kb
impacts = "/var" 5736Kb
= TRUE

Step 3. Add the new configuration file to Ignite-UX:

Edit the /var/opt/ignite/INDEX file to install a new "configuration" to Ignite-UX. For this example, add a new "cfg" clause as follows:

cfg "HP-UX B.10.20 archive" {
description "some description of this archive..."
"/opt/ignite/data/Rel_B.10.20/config"
"/var/opt/ignite/data/Rel_B.10.20/core_700_archive_cfg"
"/var/opt/ignite/config.local" }

The line of most interest is the one containing the core_700_archive_cfg, which is the config file we added in Step 2a. The "config" and "config.local" are standard configurations.

/var/opt/ignite/config.local should be last. The last config file has the highest priority and can override values in prior config files.

The file /opt/ignite/data/Rel_B.11.00/config supplies the disk and file-system layout defaults, plus other control information required by Ignite-UX. It must be first in every cfg clause.

Each cfg clause appears as an available configuration to Ignite-UX. Therefore, the string HP-UX B.11.00 archive will now appear as a valid configuration.

Step 4. Ensure NFS file system is exported correctly.

In the above sw_source clause, we specified the location of the OS archive to be a file on an NFS server. You need to ensure target systems have access to this directory.

Make sure the NFS configuration is correct. To view the current status and ensure the directory containing the archive is correctly exported, enter:

exportfs -v

Ignite-UX will automatically try to export /var/opt/ignite/clients for its use. In our example, /var/opt/ignite/archives/Rel_B.11.00 must also be exported because that is where we placed the OS archive.

Here's our /etc/exports file:
/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives/Rel_B.10.20 -ro,anon = 2
If these are not correct, use SAM to set them up correctly.

Thanks for participating in the forums,

Martin
Chaos reigns within. Reflect, repent, and reboot. Order shall return.

[Erik Heckers]

Hello Jack!

If you do
swlist -l bundle |grep -i ignite
or
swlist -l product |grep -i ignite

you get a list of installed
Ignite bundles and ignite
products.
To reconfigure a product (e.g. the one for 10.20)
try

swconfig -x reconfigure=true

Try this at your own risk ...

Erik