HP vPar : Subsequent vpar os deployment [itamiun] automation when vPar does not have any OE already

[willsfrazer]

Hi,

I am looking for a solution where in I can deploy OS [HP UX 11i V3] on a subsequent vpar where in I have a vpar which is up and running and MP console to manage the subsequent vpar. Now when I see at options I see bootsys, but it requires an OS to be already installed on target which I want to deploy OS on, so this does not help me. Now I am left with only "vparboot -p vparname -I" atleast by what I know. Is there any way I can make this command to read configuration files which actually bootsys reads so that I can overcome the need of an OS being installed on target vPar. Can I drive Ignite UI with expect, looks typical as it requires too much of navigation for file system configuration. Is there any way I can get some default configuration to be read by vparboot -I command so that I need not do anything on Ignite UI except root password setting as Network configuration is read from Ignite bootptab only and hostname could be set later on once system is up. So file system and root password are the things left to setup during Ignite installation. In which I can try getting root password set using expect but driving file system configuration by expect seems to be not happening.

Any help is great.

Thanks.