Booting Solaris LDOMS Control Domains

We are having a discussion on what order LDOMS and control domains should be booted.
I think it should be LDOMS first then Control. Can anyone tell me why I am wrong or why I am right.

Thanks,
:confused:

How do you want to boot LDoms without the control domain started?

We are patching the systems. We want to know the proper order. Should you boot the control domain first or the LDOMS first?

:confused:

It is not possible to boot LDoms without control (primary) domain started. Control domain is the "hypervisor" for LDoms.

I understand what you are saying...but what I am really curious about is after patching a control domain and the LDOMS which should be booted first. I understand that the LDOMS cannot be booted until the CD comes back up but should you boot the LDOMS first after the patch has been added or should you boot the CD after the patches have been added?

I think by "boot" you mean "reboot". If that is the case, I would first do the whole patching process on LDoms, without touching primary domain. After all the LDoms have been patched and rebooted and no issues arose I would go ahead with patching the primary domain.

If Solaris 10:

build and patch the ABE for each Client LDOM. Then the Primary. Once all are complete, activate the client ABE's and shutdown the client LDOMs.

after that is complete, activate the Primary ABE and then reboot. If the Primary comes up OK on the alternate BE, Start and boot each Client one at a time to ensure they are coming up ok. Then proceed with any zones you have configed.

This is assuming of course that you don't have anything set to auto boot.

If Solaris 11:

Patch at will, just ensure you shutdown your guests prior to rebooting the Primary.