Shutting down the control domain may cause the guest domain to crash (1631762)

Last published : Jun 10, 2026
Set up Two Oracle SPARC Enterprise T5240 server physical boxes, each with a control domain and a guest domain. The guest domains in each of the physical boxes form a two node cluster. The nodes are named node 0 and node 1 in the following text.
Symptom Gracefully shutting down the control domain of node 0 causes the guest domain of node 0 to crash.
Analysis Even though the guest domain can continue to function when the control domain is shut down, the heartbeats between node 0 and node 1 are lost as the control domain shuts down. As a result, the cluster forms two separate sub-clusters without the sub-clusters being able to see each others' heartbeats.
I/O fencing resolves the split brain situation and determines that only one sub-cluster will continue to function while the other sub-cluster should panic. Therefore, the panic of node 0 is expected behavior.
Resolution None; this is expected behavior. However, Arctera recommends keeping the control domain highly available for the proper function of the InfoScale Enterprise and InfoScale for Oracle RAC stack in the guest domains.
If you have set up a virtual private LLT heartbeats between the two guests (node 0 and node1), the guest will not crash.
Related information