IG-UX custom config script

[Nivesh Patnaik]

I need to create a custom config file that will have pre-set
values so the user won't have to do anything with disk/FS
configurations.

I have searched instl_adm(4) for the syntax.

What is the default index of the root disk? Is it 1?

If I have 4 disks and I want to configure the three non-boot disks
to be in vg01, and create /home that will be striped across the
3 disks. Is the syntax below correct?

volume group "vg00"
{
physical_volume disk[1]
max_physical_extents=2500
...
logical volume {
mount_point = "/"
...
}
}
volume group "vg01"
{
physical_volume disk[2..num_disks]
max_physical_extents=2500
...
logical volume {
mount_point = "/home"
usage = VxFS
size = 2000Mb
stripes = *
}
}



Thanks,
-

[Eileen Millen · Accepted solution]

After you do an install over the network, you can go into the Ignite GUI, select the client, then start to push install it out again. Then you can save the last configuration to a file.
You can cancel the install. Ignite creates the configuration file for you with the correct syntax.
Eileen

[James R. Ferguson]

Hi:

Edit the 'post_config_cmd' in '/var/opt/ignite/recovery/config.recover'.

Regards!

...JRF...

[Nivesh Patnaik]

I saved the disk/FS layout configuration after picking the disks and striping, etc.

However, the config file has hardware paths in it specific to the machine I am Igniting.

Below is the extract:
volume_group "vg01" {
usage=LVM
physical_volume disk[2/0/1.6.0] {
} # end pv_options
physical_volume disk[2/0/1.4.0] {
} # end pv_options
physical_volume disk[2/0/1.2.0] {
} # end pv_options
logical_volume "lvol1"{
mount_point="/home"
usage=VxFS
size=2052096K
stripes=*
} # end logical_volume


I am trying to write a generic script that does not have hardware paths hardcoded in it, nor does it have the number of disks hardcoded for vg01.

I am trying to add logic so that if # of disks > 1 then create separate volumes with striping using vg01 volume group which contains all disks except the boot disk (asigned to vg00).

I still haven't figured out the answer to my original question

[Eileen Millen]

Hello Nivesh,

The Ignite course did not go into much details about the config files. I also could use help.
HP lists an Online course
Configuration Files for Ignite-UX.
They didn't have one scheduled, so I sent a message saying that I would like to be notified when they do have one scheduled.
It sounds like it could be very useful.

When using Ignite across the network, you can choose which disk will be the root. We had an 18GB and a 36GB, I could select the 18Gb disk. I think it is on the 1st install screen.

Eileen

[Eileen Millen]

Nivesh,
This is the link to the online course:
http://education.itresourcecenter.hp.com/Trainer/education/seminar/sem_detail.asp?comm=7&ctgry=2∏=655

It should all be on one line.
Eileen

[Nivesh Patnaik]

The problem is that I cannot have NFS running on our workstations. I have to create Ignite tapes for different models (715, 725, C, J), and my directive is to preconfigure as much as possible. The end user never has to do anything except put in the network and host information during the Ignite process. Everything else, including the disk and filesystem layout must be preconfigured and dynamic, based on the type of system that is being Ignited. Therein lies my problem. I can have Ignite pick the boot disk for me, but then I must automatically detect and configure additional disks.

I took the Ignite course with HP, but they only scratch the surface of configuration files