Virtual machine, vxvm daemon and ignite process

[Kim Tran_4]

We ignite our virtual machine with 11.23, on a IA64 physical machine. After igniting, we have to start vxconfigd manually, which is done automatically with physical machine. Is there something we should fix through the ignite process to make this daemon run automatically? Please note that this happens to virtual machine only. Thanks.

[Alzhy]

I tust you are using VxVM on your vPar environments?

vxconfigd should start automatically. If it does not - check your /etc/rc.log as it may have clues as to why it is not starting at boot time.

Also, vxconfigd will not normally auto start IF you are not using VxVM actively.

[Kim Tran_4]

Thanks. All the log files (ignite and rc.log) are normal, no errors related to Vxvm. Could you give me more detail on how to use Vxvm actively?

[Bharat Katkar]

Not sure about this but is there any configuration file in /etc or /etc/rc.config.d wherein you can set autostart at bootup just like we do for other e.g there are files called netconf, nddconf, namesvrs etc.
You just have to change the value of the concerned parameter to 1.

Hope that helps.
Regards,

[Alzhy]

This file is normally there if you are not using VxVM:

/etc/vx/reconfig.d/state.d/install.db

If you remove it, then it will attempt to bring up VxVM. It will find your rootdg, discover your disks and actiavte the diskgroups/import them and start the volumes.

You will need to know what you're doing to use VxVM. If you have the facility to understand things rather quickly -- then use SAM in a GUI environment which will launch VMSA Ithe VxVM Admin GUI).

HTH.

[Ted Buis]

Are you running 11.23 vPARs or do you have a copy of Integrity Virtual Machines. As these are radically different virtual machines it would be good to make sure your are talking about vPars or IVM.

[Kim Tran_4]

Thanks for all the help. I'm using virtual machine, not vPar.