|
ContentsIndex |
SummaryStarting with Solaris Cluster 3.2, Solaris Cluster is now supported in Logical Domains (LDoms) I/O domains. I/O domains are domains that include physical devices and are not dependent on other domains (such as a service domain) for their operation. The following minimum software versions are required:
The following configurations are currently qualified:
Solaris Cluster licensing remains unchanged: one server license per server is required regardless of the number of I/O domains that are running on the server (currently limited to two I/O domains in the supported servers). The required Solaris Cluster license is for the physical servers themselves, regardless of any guest domains that might be created on the server. In other words, you buy a Solaris Cluster license as you otherwise would for the servers in question. More InformationYou can create additional guest domains on the systems that are running Solaris Cluster 3.2 software in one or more of the I/O domains on the system. I/O domains that are running Solaris Cluster can be used as service domains for the other guest domains. Running nonclustered applications in such guest domains is allowed. However, Solaris Cluster software itself is not supported inside such guest domains at this time. You can find an example that shows how to use Solaris Cluster in such a configuration in the blog Announcing Solaris Cluster support in LDoms I/O domains. Here's a diagram of how to set up LDoms: Questions and Answers
Release NotesThe following issues are currently known to affect Solaris Cluster 3.2 software that is running in LDoms I/O domains. 6528556 LDOM shutdown prompt for reboot/ok-prompt/halt, selecting ok will panic when running cluster s/w Attempts to shutdown a LDoms service domain would yield a reboot/ok-prompt/halt prompt if guest domains are present on the system. If Solaris Cluster is running in such a service domain, selecting ok on this prompt may panic the node. This panic can be avoided by making your selection within 5 seconds. If the panic does happen, allow the panic to complete and the service domain then boots normally. If you want to display an OpenBoot PROM prompt, you need to use the break command from the system controller. Refer to system controller documentation for details. References |
